Re: RE: compiling sqlrpgle -- WDSCI-L

Diane, the standard way to see errors from an SQLRPGLE compile is tochange the create command to put the intermediate source into anon-QTEMP library - the problem with the default use of QTEMP is thatyou are dealing with 2 jobs here, esp. is compiling in batch. It'sthe same problem in SEU when trying to view the source listing withF15. Or some such thing.

The other way is to compile interactively, I think. This setting mayhave changed with the installation to 6. It's in the preferences somewhere.


HTH
Vern

At 03:12 PM 12/21/2005, you wrote:

Bruce,
I feel certain prior to my 6.0.1 install, I never had this issue.  As it
stands now, it's useless for me to compile my sqlrpgle program in
WDSC/Rational (or whatever I should be calling it) - since I can't see my
errors.  I have to jump over to the 5250 session, compile it there, and
then get my errors.
With version 5.xxx, my errors were visible.

Thanks for your reply, maybe an IBMer will jump in on this and set me
straight.
Diane



"Bruce Guetzkow" <bruceg@xxxxxxxxxxxxxxxxxxxxxxx>
Sent by: wdsci-l-bounces+infosys5=amm.org@xxxxxxxxxxxx
12/21/05 02:00 PM
Please respond to
Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx>


To
<wdsci-l@xxxxxxxxxxxx>
cc

Subject
[WDSCI-L] RE: compiling sqlrpgle






Diane:

<snip>
I'm trying to compile an SQLRPGLE program with Rational .  When my compile

errors, I try to select the error from the "error list" and it will not
display, instead I get an error dialog "File QSQLTEMP1 in library QTEMP
not found."  I've checked my compile options, I do not see where I am
compiling in QTEMP/QSPLTEMP1.  Prior to the 6.0.1 install, this issue
never existed.  Also, if I am compiling an RPGLE program, I do not have
this QTEMP issue.

What & where is the setting that needs changed?
</snip>

This is a "feature".  Actually, this problem has been around since the
beginning.  When you compile a program/module with embedded SQL the
pre-compiler takes over, creating a temporary version of the code
in...QTEMP.  This is the version that is compiled, with all of your SQL
statements changed to API calls.  The errors are from the listing of the
compiled source member (in QTEMP), which doesn't correspond directly to
your
original source, hence the problem.  Plain RPGLE source doesn't have this
problem because the source you create is the source being compiled.

Perhaps an IBMer can comment on a proposed time-frame for addressing this
issue...it sure would be nice if it could be changed to link back to the
original source.

--Bruce Guetzkow


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



--

This is the Websphere Development Studio Client foriSeries (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.