That's how I compile also, but I didn't realize the bind errors went to the
WDSC job log. I am going to check that out!!
Thanks Brandon!
Aaron Bartell
http://mowyourlawn.com
-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On
Behalf Of Brandon Peterson
Sent: Friday, February 01, 2008 2:45 PM
To: Websphere Development Studio Client for iSeries
Subject: Re: [WDSCI-L] binding errors in WDSC (was: EGL vs. Java)
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
midrange.com
