RE: SQL set options in SQLRPGLE source member (NOMAIN)

That was my understanding too, Jeff. My real concern was how it is (or isn't?) integrated into each procedure if I located it within the first Procedure. If the precompiler applies it to all Procedures in the source member that use sql, all's cool. If that's not the case, I need to do something else.
Thanks,
-- Michael

-----Original Message-----
From: RPG400-L [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Jeff
Young
Sent: Thursday, January 15, 2015 3:44 PM
To: RPG programming on the IBM i (AS/400 and iSeries)
Subject: Re: SQL set options in SQLRPGLE source member (NOMAIN)

The Set Options SQL statement must be the *first* SQL statement that the
SQL Precompiler sees.
As long as it is the first statement that is seen, it can be anywhere in
your source.

Jeff Young
Sr. Programmer Analyst

On Thu, Jan 15, 2015 at 3:37 PM, Joe Pluta <joepluta@xxxxxxxxxxxxxxxxx>
wrote:

If I recall correctly, the SET OPTIONS simply needs to be anywhere in
the source (in the calculations, obviously). It's more of a
pre-processor directive that the SQL precompiler looks for before

starting its work.

Joe


After a good long time of probably not doing things right, I'm trying
to

improve my processes. I am putting a bunch of procedures into a
single NOMAIN source member. Some (most?) of these procedures have
embedded SQL, so I know that my standard "exec sql set options(...)"

statement needs to

be the first calculation of the source. Most all of the procedures

are

EXPORTs, but the whole set gets compiled into a single module used in
a service program, where the procedures are executed by a *pgm that
does not have embedded SQL.

Is it okay to put my "exec sql set options(...)" in just the first
procedure (ProcedureA) in the source member? Does a program that
executes ProcedureB (but not ProcedureA) get those standard options?
Or does the sql precompiler somehow make that "set options"
instruction available to all the procedures in the module? If so,
would it be just as good to code it outside (as in, before the DCL-PI)

of the first procedure?.

Or, do I need to locate it where each procedure must execute it (like
maybe coded just once, but as a private procedure that must be called
by each sql procedure...) ?

Many thanks as always,

Michael Koester
Programmer/Analyst

DataEast