I do not think that the LIBL changes persist - it looks like the service
jobs have their LIBL reset to the default of the user when assigned to
do the task. We just cannot use that, as our library list is
constructed by our legacy system instead of being statically assigned to
the user.
I had the same problem before on a MQ-to-Java-to-RPG call, which wasn't a
database trigger or service program, but for similar reasons it had the
same issue of the RPG program being ran with zero library list. Our
problem was our dev box houses multiple environments, a set of dev
libraries and a set of test libraries, so hard coding a CHGLIBL command at
the top of the RPG program wasn't an option. The way I got around it was
to pass in the whole CHGLIBL command as an input parameter - then I just
build up the CHGLIBL command in Java beforehand and pass it through, and
the RPG program simply executes whatever CHGLIBL command it gets in that
first parameter as one of the first things it does. This worked well for
us.

Regards,

Nigel Gay,
Computer Patent Annuities.


********************************************************************************
The information in this message is confidential and may be legally
privileged. It is intended solely for the addressee; access to this
email by anyone else is unauthorised.

If you are not the intended recipient: (1) you are kindly requested
to return a copy of this message to the sender indicating that you
have received it in error, and to destroy the received copy; and (2)
any disclosure or distribution of this message, as well as any action
taken or omitted to be taken in reliance on its content, is prohibited
and may be unlawful.
********************************************************************************

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 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.