|
Don,
The deficiencies with compiling embedded SQL have been around and known
for a very long time. Given that IBM has been encouraging us to use SQL,
are then any immediate plans to put something practical in place?
I use a fair amount of embedded SQL and the best way I've found is still
to compile thru PDM, browse the compile errors on the green screen and
alt-tab to WDSC to make the fixes. But I'd love to have the errors
downloaded and inserted into the source like non-SQL does.
Sam
>From: Don Yantzi <YANTZI@xxxxxxxxxx>
>Brandon,
>
>You will need to override the TOSRCFILE parameter for the CRTSQLRPGI
>command to write the temporary file created by the SQL preprocessor to a
>library other than QTEMP so it can be downloaded to display the errors.
>WDSc cannot access the one in QTEMP after the compile completes. You can
>do this by either prompting the command in WDSc or defining your own
>compile command for the sqlrpgle member type.
>
>Don Yantzi
>WebSphere Development Studio Client for iSeries
>IBM Toronto Lab
>Phone: (905) 413-4476
>IBM internal: IBMCA(yantzi) - Internet: yantzi@xxxxxxxxxx
----------------------------------------------------------------------
Frustrated with dial-up? Get high-speed for as low as $26.95.*
* Prices may vary by service area
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.