|
On Tue, 5 Mar 2002, Ken Sims wrote: > > The one statement you made that I would take exception to is: > >They don't leave overrides laying around that can randomly affect other > >jobs. > Overrides inside of a named activation group aren't going to affect any > other activation group, much less another job. > Oops... I mean other programs, not other jobs. What I was getting at is that if you put all of your programs in QILE, and then scope the overrides to the default *ACTGRPDFN, the override will affect any other programs running in the QILE actgrp. This is different than DFTACTGRP(*YES) because in that situation it goes by call-level, and when that call level ends, so does the override. This is why I think *NEW/*CALLER is easier for new people to understand.
As an Amazon Associate we earn from qualifying purchases.
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.