×
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.
I hear you but I know that the RHEL is setting the user library list to libraryA using the libraries parameter. When looking at the job log for the QZADOSINIT job, I see the connection and nothing about changing the library list. When looking at the library list, I see it has just the one libraryA in the user library list. But I have not looked at the WAS connection. That is my next thing to do.
Chris Bipes
Director of Information Services
CrossCheck, Inc.
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Charles Wilt
Sent: Wednesday, April 02, 2014 11:12 AM
To: Midrange Systems Technical Discussion
Subject: Re: JDBC connections and library lists
If the i is closing the connection, you shouldn't see this problem.
What do you see in the joblog of the connections being used by WAS?
User WILTC from client 192.168.1.192 connected to server. Anything about
the library list changing?
Try the following test...
Start iNav Run SQL Scripts...
do WRKJOB on whatever QZDASOINIT job iNav reports as being connected to...
look at the library list of the QZDASOINIT job
in run SQL scripts, do CL: addlible somelib
now look again at the library list of the QZDASOINIT job
close run SQL scripts
look at the library list of the QZDASOINIT job again, should be back to the
original.
I don't think your REHL app is the problem. The problem is in you WAS app.
I think it's opening a connection and setting the library list and you're
not expecting it to be.
As an Amazon Associate we earn from qualifying purchases.
This thread ...
RE: JDBC connections and library lists, (continued)
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.