Re: Recognizing the Library list using the AS/400 JavaDevelopment toolkit

Up until V5R2, you could set the library for the native drive in 
a CLI exit program and it would keep that library list for all threads.

On V5R2, each new thread starts with the user's jobd library 
list so you can't use the exit to set the library list. There is no 
mention of this change in the memo to users and the documentation 
for the CLI exit still says it can be used to set the library list.
Anyone 
have any insight on why this changed and how to set it back to the old

way? I sent this on to IBM a couple of weeks ago but haven't heard 
back.

David Morris


>>> kulkarni_ash1312@xxxxxxxxx 7/18/2003 11:10:47 AM >>>
Hi,

If u dont provide any library for connection and set
naming=system while creating connection, then the
connection will have the library list from the job
description of the user who has created the
connection.
so u can change the jobdescription to have the
neccessary libraries
Ashish
--- Franco Biaggi <fbiaggi@xxxxxxxxxx> wrote:
> If I right understand your problem,
> you van set the LIBL in the connection URL:
> example:
> 
> jdbc:as400://10.1.1.50;translation
>
isolation=none;naming=system;libraries=lib1,lib2,qgpl,qtemp;block
> size=128;extended 
> dynamic=true;package=MYPKG;package
> cache=true;package library=qgpl
> 
> On Fri, 18 Jul 2003 10:43:56 -0400, McNeal, John
> wrote:
> 
> >  We are using the AS/400 Java Development toolkit.
>  In our environment,
> >our library list changes with each release and
> environment (production
> >verses QA,  ECT).  Is there a way to have the
> classes provided by the AS/400
> >Java Development toolkit to recognize the *LIBL ? 
> It would be a major
> >configuration nightmare for use to have to hard
> code the library name,  or
> >store it in a configuration files since our objects
> reside in multiple
> >libraries (and programs in multiple libraries). 
> Has anyone else had this
> >problem,  and do you know if a work around exist. 
> 
> >     John McNeal