× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Aaron,

To address only your point #3, what I do is change my preferences in
WDSC to NOT compile in batch. That lets me see binding errors directly
in WDSC. Specifically in the bottom right section of the screen there
is a tab that says "iSeries Commands Log."

I figure it's already running as a batch job so there is no need to
re-submit the compile.

If you use projects, to change this you go to Window -> Preferences ->
iSeries Projects -> Build and Compile -> Un-check "Run compiles as batch
jobs". The other place you change it is in Window -> Preferences ->
Remote Systems -> iSeries -> Command Execution.

Brandon

-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx]
On Behalf Of Aaron Bartell
Sent: Friday, February 01, 2008 12:52 PM
To: 'Websphere Development Studio Client for iSeries'
Subject: Re: [WDSCI-L] EGL vs. Java

In my mind it comes down to this: Why would people still want ADTS?
Note I
am taking pricing out of the picture for these comments.

[snip]

3) When I want to find out about binding errors with CRTBNDRPG I use
PDM. I
could of course type it all out on the command line, but PDM get's me
there
in 3 seconds vs. 30 seconds.

[snip]

- #3 bothers me because I don't have an easy way to do this through WDSC
unless I start hacking.

[snip]

Aaron Bartell
http://mowyourlawn.com


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.