RE: SQLRPGLE won't compile...

[rob@xxxxxxxxx]

Physically or logically?  Since it's a precompiler option then I assume 
Physically.

For example, since sql buggers up free format, we all do:

PrepareCursorC1();
OpenCursorC1();
if sqlcod<>*zeros;
  return;
Endif;
....

We could then have the subprocedures all down here that do the actual 
work.
And, it would work as long as the subprocedure doing the SET OPTION is 
physically first.  Right?
And, would we even need to call the subprocedure that does the SET OPTION? 


Rob Berendt
-- 
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





Gina M Whitney <whitneyg@xxxxxxxxxx> 
Sent by: rpg400-l-bounces@xxxxxxxxxxxx
04/06/2005 10:09 AM
Please respond to
RPG programming on the AS400 / iSeries <rpg400-l@xxxxxxxxxxxx>


To
rpg400-l@xxxxxxxxxxxx
cc

Subject
RE: SQLRPGLE won't compile...






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

It must precede any other SQL statements.





-- 
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.