I understand and agree with the DAG issue. I'm eating the proverbial
elephant here.
You are correct regarding the reason for putting service programs in a
named group - it was to prevent them from going away.
Most users never switch their library lists so that was working. We have a
few users jumping between environments and want to make this work without
signing off. And, even those that jump between environments will run
multiple commands in each environment so I think having the service
programs in one activation group still makes sense.
I'll have to work on getting our CLLE into a named activation group
(instead of *NEW) and converting our CLP to CLLE. A bit of a long-term
project.
--
Brian J. Garland
Vermont Information Processing, Inc.
brian.garland@xxxxxxxxxx
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2026 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
