Todd,

I checked with Birgitta Hauser. As I understand it, the naming mode under which the procedure is called will be less important than the naming mode used to create the procedure.

Birgitta replied:

If a stored procedure is created with System Naming, the library list is accessed at run time, even though the procedure is called from within an environment where SQL Naming is used.

If static SQL was used within the stored procedures the library is always used, independent whether a CURRENT SCHEMA is explicitly set at runtime or not.

If dynamic SQL was used within the stored procedures the library list is only used if NO CURRENT SCHEMA is set in the environment where the procedure is called.


Todd, I'd be interested to hear whether these ideas work for you.

Alan

Allen, Todd <mailto:Todd.Allen@xxxxxxxxxxxxxxxxx>
February 13, 2013 9:01 AM
Thanks for the article links. Those contain great info. Most of the material I had read before. One thing I did not know is that the owner of a schema will be the user profile if that schema name matches an existing user profile.

To my original question, it seems there is no way to use a library list on a stored procedure call with SQL naming.

Thanks,
Todd


-----Original Message-----
From: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx] On Behalf Of Alan Seiden
Sent: Wednesday, February 13, 2013 1:54 AM
To: Web Enabling the IBM i (AS/400 and iSeries)
Subject: Re: [WEB400] SQL naming + library list

Hi, Todd,

In some cases, the naming mode used to create the stored procedure may supersede the manner in which the procedure is called.

This topic is more complex than it seems. For details, I recommend Birgitta Hauser's thorough, authoritative articles about SQL and System
naming:
http://www.ibm.com/developerworks/ibmi/library/i-sqlnaming/index.html
http://www.ibm.com/developerworks/ibmi/library/i-system_sql2/index.html

Alan


For More Than 80 Years—Delivering Solutions That Exceed Expectations.

This communication and any transmitted documents are intended to be confidential. If there is a problem with this transmission, please contact the sender. If the reader of this message is not the intended recipient, or the employee or agent responsible to deliver it to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited.
Alan Seiden <mailto:alan@xxxxxxxxxxxxxx>
February 13, 2013 1:54 AM
Hi, Todd,

In some cases, the naming mode used to create the stored procedure may supersede the manner in which the procedure is called.

This topic is more complex than it seems. For details, I recommend Birgitta Hauser's thorough, authoritative articles about SQL and System naming:
http://www.ibm.com/developerworks/ibmi/library/i-sqlnaming/index.html
http://www.ibm.com/developerworks/ibmi/library/i-system_sql2/index.html

Alan

Allen, Todd <mailto:Todd.Allen@xxxxxxxxxxxxxxxxx>
February 8, 2013 4:09 PM
Is there any way to use SQL naming in an unqualified (no library) call to a stored procedure and have the library list used? I seem to recall that an alias can be used to mimic the library list behavior when using SQL naming.

I know system naming would be much easier but that is not an option at this time.

Thanks,
Todd Allen
Estes Express Lines
tallen@xxxxxxxxxxxxxxxxx<mailto:tallen@xxxxxxxxxxxxxxxxx>


For More Than 80 Years-Delivering Solutions That Exceed Expectations.

This communication and any transmitted documents are intended to be confidential. If there is a problem with this transmission, please contact the sender. If the reader of this message is not the intended recipient, or the employee or agent responsible to deliver it to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited.

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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.