Compiling

Joe,

I call a standard program on the i5 for every compile.

It will create workfiles and then delete them, override file names if a
filename has to be changed in the F specs.
Also, it will work if its CLP, RPGLE or SQLRPGLE.

The downside is that I don't get the error messages returned to WDSc of
course.



----- Original Message -----
From: "Joe Pluta" <joepluta@xxxxxxxxxxxxxxxxx>
To: "'Websphere Development Studio Client for iSeries'"
<wdsci-l@xxxxxxxxxxxx>
Sent: Friday, October 26, 2007 3:36 PM
Subject: Re: [WDSCI-L] SEP Its enough to make a grown man cry

From: David Foxwell

I've recompiled from WDSc although my recompile option calls a program

on

the i5 that compiles for me with the right library list.

This part bothers me a little bit. This implies that your WDSC connection
to the System i does not have the library list necessary to compile your
program. Why is that? Typically I either set up a connection with the
right library list, or I have a program I can call to set my library list
correctly.

This shouldn't be an issue, since the debugger should get the source file
name, library and member from the module, but it's possible it's getting
confused and finding a different source file in the library list.

Second is that you're using WDSC 6, but I guess you have to live with that
for now.

Finally, I would suggest using the DBGVIEW(*LIST) rather than

DBGVIEW(*ALL).

*ALL contains both *SOURCE and *LIST information, and the presence of the
source information may be causing the debugger to use the source view.

Joe

--
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.