Which naming conventions (System or SQL) were used when creating the stored
procedure?
If System Naming was used, the library list at runtime is searched.
If SQL Naming is used, the default library/schema (at least for static SQL
statements) is determined at compile time. Unqualified specified Tables and
views are searched (at runtime) in the default schema determined at compile
time. For dynamic SQL it depends on the compile option DYNDFTCOL whether the
unqualified specified database objects are searched at runtime in the
default schema determined at compile time or the current schema.

Independent which naming convention is used when calling a stored procedure
or UD(T)F, the stored procedure/UDTF is executed with the same naming
convention under which they are created.

Mit freundlichen Grüßen / Best regards

Birgitta Hauser

"Shoot for the moon, even if you miss, you'll land among the stars." (Les
Brown)
"If you think education is expensive, try ignorance." (Derek Bok)
"What is worse than training your staff and losing them? Not training them
and keeping them!"

-----Ursprüngliche Nachricht-----
Von: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] Im Auftrag von
Chella R
Gesendet: Tuesday, 13.10 2015 04:58
An: midrange-l@xxxxxxxxxxxx
Betreff: Library list for Stored procedure

Hi,

I have three environments in my test server and have stored procedure entry
in 2 libraries. When the stored procedure is invoked by the .net program
outside of this server, it is executing the program as per the stored
procedure logic, but the PF/LF that is being referred to is being fetched
from another environment's library. I suppose this is down to the logic in
which the job description is assigned for the job that executes the stored
procedure. Though the QZ* job is running under QUSER, the library list I
suppose is decided by something else? Can this please be clarified on how it
is assigned, so that I can fix my issue accordingly?

Best Regards
Chella Govindarajan R


~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~Disclaimer~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Information contained and transmitted by this e-mail is confidential and
proprietary to IGATE and its affiliates and is intended for use only by the
recipient. If you are not the intended recipient, you are hereby notified
that any dissemination, distribution, copying or use of this e-mail is
strictly prohibited and you are requested to delete this e-mail immediately
and notify the originator or mailadmin@xxxxxxxxx
<mailto:mailadmin@xxxxxxxxx>. IGATE does not enter into any agreement with
any party by e-mail. Any views expressed by an individual do not necessarily
reflect the view of IGATE. IGATE is not responsible for the consequences of
any actions taken on the basis of information provided, through this email.
The contents of an attachment to this e-mail may contain software viruses,
which could damage your own computer system. While IGATE has taken every
reasonable precaution to minimise this risk, we cannot accept liability for
any damage which you sustain as a result of
software viruses. You should carry out your own virus checks before
opening an attachment. To know more about IGATE please visit www.igate.com
<http://www.igate.com>.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe,
or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/midrange-l.



This thread ...

Follow-Ups:
Replies:

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

This mailing list archive is Copyright 1997-2019 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].