RE: Verifying SQLRPGLE

["Chevalier, Rick" <Rick.Chevalier@xxxxxxxxxxxxxxx>]

Probably doable but I can just compile and get the returned errors in WDSc
which sounds a lot easier than tracking down the intermediate source from a
compile and verifying that.  I just wanted to play with the new features and
try to keep as much off of the iSeries as possible.   It seems to work fine
for non SQLRPG programs.

Rick

-----Original Message-----
From: Vern Hamberg [mailto:vhamberg@xxxxxxxxxxxxxxxxxxxxxxxxx]
Sent: Wednesday, May 28, 2003 8:36 AM
To: CODE/400 Discussion & Support
Subject: RE: Verifying SQLRPGLE

Rick

There's an option in the CRT commands for embedded SQL, to save the
generated source. Then you could compile from this, or perhaps verify that.
Not the ideal, but doable?

HTH

Vern

At 07:38 AM 5/28/2003 -0500, you wrote:
>I experience the same situation using 5.0.  I do a lot of embedded SQL and
>would sure like to be able to verify the SQLRPGLE source members if there
is
>a way to do it.
>
>Rick


_______________________________________________
This is the CODE/400 Discussion & Support (CODE400-L) mailing list
To post a message email: CODE400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/code400-l
or email: CODE400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/code400-l.

NOTE: WDSc for iSeries disucssion has it's own mailing list.
Information can be found at
http://lists.midrange.com/cgi-bin/listinfo/wdsc-l