Re: Re: compiling sqlrpgle -- WDSCI-L

Are you running against V5R3 of OS/400? If so, there is a PTF that issupposed to help. SI12763 (included in CUME 4118?) has the followingin the cover letter:


DESCRIPTION OF PROBLEM FIXED FOR APAR SE13693 :
-----------------------------------------------
  When CRTSQLRPGI is used with OPTION(*EVENTF) and RPGPPOPT has a
  parameter other than *NONE, event-file processing by WDSC cannot
  handle all the generated errors because the source file used
  by the SQL-precompile phase of the compile is a temporary file
  in QTEMP.  When the line in the Error List window of RSE is
  double-clicked, msgEVFF5033I is issued, saying that the member
  in file QSQLPRE cannot be opened because it is in QTEMP.

CORRECTION FOR APAR SE13693 :
-----------------------------
  The ILE RPG compiler will be changed so that errors generated
  during the RPG preprocessor phase of the CRTSQLRPGI command
  will be handled correctly by eventfile processing.  The
  temporary source file generated by the RPG preprocessor will
  be copied to the target library specified on the OBJ parameter
  of CRTSQLRPGI, making the source file available to event-file
  processing.

I don't think there is anything for earlier releases of OS/400. But Irepeat something from my earlier post - try interactive compiles.This can be set in Windows->Preferences->RemoteSystems->iSeries->Command Execution.

Another alternative is to do only the precompile, putting theintermediate source in a non-QTEMP liberar, then compiling from that.An old technique, I believe.


HTH
Vern


At 12:38 PM 12/22/2005, you wrote:

Diane,

You might try changing your compile option to add
'TOSRCFILE(library-name/QSQLTEMP1)'  That way a copy of the pre-compiler
generated source is saved in the specified source file.  It still leaves
you with a *gotcha*.  If you double-click on an error in the error list,
you'll end up being positioned in the QSQLTEMP1 source not the original
source.  I'm believing IBM will someday fix this all the way.  But at
least it helps you see what and where the error really is.

Also, if the "/copy" program is being opened, that may be where the error
is actually being trapped.  You should be able to read what member the
error was in from the error list.

Michael Quigley
AS/400 Programming Coordinator
The Way International
www.TheWay.org

Original message:

------------------------------
date: Thu, 22 Dec 2005 11:06:21 -0600
from: infosys5@xxxxxxx
subject: RE: [WDSCI-L] RE: compiling sqlrpgle

Rick,
Adding the   keyword OPTION(*SRCSTMT)did not help,the line #'s don't match

up.  Also, I noticed today, when I double click the error, it opens the
"/copy" program and displays the dialog box that it can't find the
indicated line #.  So why double clicking the error would open my
procedure program and not the program that I'm compiling??   It is
definitely an aggravation but not enough to give up WDSC - can't work
without it.  If I have to, I'll compile on the 5250 and code in WDSC.
Thanks for your suggestion.

Diane


--

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.