I use a different approach.
The library list is defined in a job description that is specified for a user profile that is being used to open connection to AS/400.
This way it will be consistent in all connection related jobs.
Get rid of library list properties in connection URL. Use naming=system;
And do not specify any libraries references in SQL and program calls.
From: java400-l-bounces@xxxxxxxxxxxx [mailto:java400-l-bounces@xxxxxxxxxxxx] On Behalf Of Thorbjoern Ravn Andersen
Sent: Wednesday, September 09, 2009 4:04 PM
To: Java Programming on and around the iSeries / AS400
Subject: Re: Library list when calling RPG from Java
Wintermute, Sharon skrev:
Now I know it is actually calling the RPG and getting it resolved. The
problem is that although I started from a job with the correct library
list, it apparently starts another job in order to actually call the
RPG. I could live with that but the library list is not set. How do I
do such a thing without doing it in the RPG?
The library list is not inherited to the prestarted jobs servicing
I usually do a CHGLIBL command call as the first thing after retrieving
the as400 object. The most robust way to get the correct library list,
is to pass it as a property or argument to the Java program.