And by reused, I mean the connection is ended by the "app" and the i reuses
the job for a new incoming connection.
The problem occurs when connection pooling on the app or app server comes
into play. When the connection pool reuses an existing connection, from
the IBM i perspective the connection has not been "reused" as it's been
I suspect the issue with library lists manifests when multiple applications
are using the same connection pool to an individual host. Bad idea,
instead an application specific connection pool should be used. Besides
the library list, you'd then be able to have application specific users for
On Wed, Apr 2, 2014 at 12:52 PM, Charles Wilt <charles.wilt@xxxxxxxxx>wrote:
I just ran a test..
The library list is indeed reset when the QZDASOINIT job is reused.
On Wed, Apr 2, 2014 at 11:01 AM, <dkimmel@xxxxxxxxxxxx> wrote:
I think you'll find that the initial library list for QZDASOINIT is
the job description used in the prestart job entry in the QUSRWORK
definition. This may or may not be the job description associated with
When a JDBC user connects to a prestart job, the user profile of the job
changed, but the library list is not necessarily changed.
As you have noted, once the library list of the job is changed, it remains
changed through reuses of the job by other users.
A library list is a unique IBMi dimension of JDBC. As such, it is
set the library list explicitly any time you are going to rely on its
Make that part of your standard.
Quoting Chris Bipes <chris.bipes@xxxxxxxxxxxxxxx>:
I ran into an interesting problem regarding library lists and JDBC.
I had a Linux Tomcat programmer define his connection to our iSeries
at V6R1 using the libraries parameter. This changed the user library
list of the QZDASOINIT job. Future connections to this job held the
library list specified in the previous job and did not pick up the
user library list form the job description assigned to the user
profile that logged in.
I have determined that if you do not use the libraries parameter the
user library list is set according to the job description of the user
This was a frustrating lesson learned when all sorts of jobs either
wrote to development or could not find programs called by triggers.
My question is this: How do you keep something like this from
happening? 1. Do you always specify the library list you need for
your connection or do you always use the job description to control
I want to define a standard and move in that direction to avoid
library list issues in the future.
Has anyone published a standard they would like to share?
Director of Information Services
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives