Initial library list comes from your system settings.
You can typically influence on the connection string to make sure only correct libraries in library list.
I believe initial library list probably comes from user info plus system settings for library lists.
If you have any system libraries in the library list you may need to qualify table names with library prefix. EX: QIWS/QCUSTCDT or QIWS.QCUSTCDT
Richard Schoen | Director of Document Management Technologies, HelpSystems
T: + 1 952-486-6802
RJS Software Systems | A Division of HelpSystems
Visit me on: Twitter | LinkedIn
date: Tue, 13 Oct 2015 02:57:44 +0000
from: Chella R <chella.r@xxxxxxxxx>
subject: Library list for Stored procedure
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?
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