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

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