.. putting all libraries to the syslibl seems a bad idea to me. better would
be to have a menu system starting diffrent applications in diffrent group
jobs, setting the libl for each application to its needs. Second choice
would be to set the libl in the startjob of your users.
Further on should each application have sufficient support to run in it's
own namespace (most of them don't). ArdGate (the universal database bridge
from DB2 to JDBC) for instance is completely self containing, you could have
even multiple instances on the same box, each of them operating independeant
from each other, not depending on libl.
D*B
This mailing list archive is Copyright 1997-2025 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.
midrange.com
