RE: SQLRPGLE won't compile...

>> It must precede any other SQL statements.
>Not true.
The SQL Reference book states that "it is not executable and must precede
any other SQL statement."  Obviously, on your release the precompiler is
not enforcing it.   There is a high probability that in a future release
the precompiler will enforce this.  However, on a positive note, it comes
along with a few things that I know have been on your wish list. :-)


message: 1
date: Wed, 6 Apr 2005 11:06:11 -0600
from: "Tyler, Matt" <mattt@xxxxxxxxxxxxxx>
subject: RE: SQLRPGLE won't compile...

>> It must precede any other SQL statements.
Not true.

I place my set options in the *INZSR and its at the bottom of all other
subroutines (source sequence wise).  The SQL PREPARE and DECLARE all must
occur source sequence wise before any other use.

A WDSC filtered view of the SQL statement in source sequence;
     C+ PREPARE SQLST FROM :SQLSTMT
     C+ DECLARE SQLCSR SCROLL CURSOR FOR SQLST
     C+ FETCH RELATIVE :PUROWS FROM SQLCSR
     C+ FETCH BEFORE FROM SQLCSR
     C+ FETCH RELATIVE :purows FROM SQLCSR
     C+ FETCH NEXT FROM SQLCSR FOR 1 ROWS INTO :RSDATA
     C+ FETCH NEXT FROM SQLCSR
     C+ FETCH AFTER FROM SQLCSR
     C+ FETCH PRIOR FROM SQLCSR
     C+ CLOSE SQLCSR
     C+ OPEN SQLCSR
     C+ FETCH BEFORE FROM SQLCSR
     C+ SET OPTION DATFMT = *USA
     C+   ,ALWCPYDTA = *NO
     C+   ,CLOSQLCSR = *ENDMOD
     C+   ,DLYPRP = *YES


Thank you,
Matt Tyler
WinCo Foods, LLC
mattt@xxxxxxxxxxxxxx


-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx]
On Behalf Of Gina M Whitney
Sent: Wednesday, April 06, 2005 9:09 a
To: rpg400-l@xxxxxxxxxxxx
Subject: RE: SQLRPGLE won't compile...

>> Second, the SET OPTION statement can be about anywhere.

It must precede any other SQL statements.