RE: SQLRPGLE won't compile...

[Gina M Whitney <whitneyg@xxxxxxxxxx>]

Physically.  The SET OPTION statement is not executable, so no the
subprocedure does not even need to be called.

---------------------------------
from: rob@xxxxxxxxx
subject: RE: SQLRPGLE won't compile...

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
--------------------------


Gina M Whitney <whitneyg@xxxxxxxxxx>
Subject
RE: SQLRPGLE won't compile...

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

It must precede any other SQL statements.