|
> It would seem that _IF_ an ACTGRP could > be specified at module creation, then a > CRTPGM ACTGRP(*ENTMOD) > _COULD_ use this value rather than > the new defaults (QILE or *NEW). There are a few issues with that concept. How would one do CRTPGM on MODULE(MOD_A MOD_B) if each module had a separate activation group specified? How would one include a single hard-AG module into separate service programs if one wanted each service program to run in a different AG? I think the typical answer to creating service programs (or even *PGMs with multiple modules) is to use some variant of MAKE. That is, any time one uses PDM 15 followed by CRTPGM or CRTSRVPGM, one should probably use an automated tool to properly bind the modules and set the activation group attribute. A CL program would be good enough. --buck
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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.