× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. MIDRANGE-L
  3. April 2009

Re: SQL question on default *LIBL at connection

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

As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.