|
Buck, > One of the things I find annoying about the AG concept is that the AG is a > property of the program/service program rather than a job property. That > is, I can't set AG names on the fly - I need to compile my > program. I can't > even do a CHGPGM to set the AG - it must be a re-compile. I > guess that's my > hint that I should plan my AG strategy carefully, eh? Well, actually you can change the activation group with the UPDPGM command: UPDPGM PGM(PHILLIB/PRMORG01) MODULE(*NONE) ACTGRP(PHILAG) It creates a new program - the old one is moved to QRPLOBJ. If you call the pgm, don't reclaim the ag, change the ag with UPDPGM, then call it again, both ag's will show in option 18 of wrkjob. > > How would making AG05 *NEW change things? > Can't change the ACTGRP with the UPDPGM command if the activation group is *NEW. Phil _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com
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.