Re: SQL question on default *LIBL at connection

[CRPence <CRPbottle@xxxxxxxxx>]

CRPence wrote:
> <<SNIP>> I infer the NAMING must be set for each procedure,
> but only from the environment of the /compile-time/, not
> from either of SET OPTION nor /run-time/.  If the naming
> is an attribute of the procedure, it seems odd both that
> SET OPTION NAMING is not allowed and that it is not an
> attribute maintained\presented in SYSFUNCS like with PATH.

  FWiW, for reference, from Support Line KB document 9951625:

"Can a stored procedure search the library list?"

"The naming convention and default collection used by a program with 
embedded dynamic SQL is set by the SQL precompiler options in affect 
when the program is compiled. <<ed:> snip odd comment>> The 
precompiler options used are picked up from the job running the 
CREATE PROCEDURE statement. If the procedure is created under a job 
running *SYS naming convention then it will resolve objects as 
defined for *SYS."

Regards, Chuck