RE: Embedded sql Set Option on V5R4

Scott,

Your missing the fact that the pre-complier knows nothing (or very
little) about sub-routines or sub-procedures.  The pre-compiled
processes the source file line by line.

In addition, as mentioned in the quote, the SET OPTION statement isn't
executable.  The set option statement controls how the pre-compiler
works.  Kind of like an h-spec.  If you look at the pre-compiler output,
you won't find SET OPTION embedded SQL statement replaced by a call to
SQLROUTE.  Nor can you have more than 1 SET OPTION statement.

HTH,


Charles Wilt
--
iSeries Systems Administrator / Developer
Mitsubishi Electric Automotive America
ph: 513-573-4343
fax: 513-398-1121
  

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx 
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Scott Klement
Sent: Tuesday, July 25, 2006 12:31 PM
To: RPG programming on the AS400 / iSeries
Subject: Re: Embedded sql Set Option on V5R4

This rule is enforced by the other precompilers available 

with the IBM DB2

Query Manager and SQL Development Kit for iSeries product, 

and has been

previously documented in the DB2 UDB for iSeries SQL 

Reference topic: "If

embedded in an application program, [the SET OPTION 

statement] is not

executable and must precede any other SQL statements."

Seems to me that this should make *INZSR a *good* place to 
put the Set 
Option, rather than making it an error!   Doesn't *INZSR get 
run before 
the rest of your calcs?  What am I missing?

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