× 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,

Do you have WDSC configured to do your compiles in batch or interactive? 
If the latter, then the only "joblog" would be your interactive log which 
you could get to from the "Your Active Jobs" filter.  If it is in batch, 
you may need to configure it to use a job description that always produces 
a joblog because I seem to recall that the WDSC batch jobs always end 
normally, even if the compile fails.  Consequently, in a "normal" job no 
joblog will be produced.

Are you using the spooled file plugin OK?  I posted an update last week. 
It mainly contains some internal changes that make it easier for 3rd 
parties to extend the plugin, but it also contains one bug fix and a new 
feature.  Double-click on spooled file opens it in editor.

Mark






"Bartell, Aaron L. (TC)" <ALBartell@xxxxxxxxxxxxxx>
Sent by: wdsci-l-bounces@xxxxxxxxxxxx
05/29/2003 12:09 PM
Please respond to Websphere Development Studio Client for iSeries 
 
        To:     "'Websphere Development Studio Client for iSeries'" 
<wdsci-l@xxxxxxxxxxxx>
        cc: 
        Subject:        [WDSCI-L] Finding Binding Errors


I am trying to use the Compile commands in WDSc now that I am up to date
with PTF's.  I have a program the compiles but doesn't bind...

"Errors were found during the binding step. See the job log for more
information."

First off, it would be nice if the 'iSeries Error List' showed this 
instead
of "Program MyProg in library MyLib not created." - which doesn't tell me
much.  I now need to go to the spool file and find out why it didn't
compile.  Once there it tells me to look in the job log for why it didn't
compile.  No problem, I am very familiar with how to find binding errors,
except when I compile from WDSc it doesn't seem to create a job log spool
file under my profile.  Now I must go back to green screen to compile so I
can get a job log.

Anybody have tips around this?  I would like to start compiling from WDSc
more often because it saves me from having to back to the green screen.

Aaron Bartell
_______________________________________________
This is the Websphere Development Studio Client for iSeries  (WDSCI-L) 
mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/wdsci-l.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

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.