|
>Why not simply always use ACTGRP(*CALLER) >then you can dispose of the problem altogether. It's more a life cycle question than anything else. The time will come when a service program needs to be replaced during production hours. If the service program runs in the default AG, the new version won't be activated and pointer errors will result. If the service program runs in a named AG, you can direct the users to go to the 'refresh programs' menu running in the default AG which destroys the named AG, enabling all new programs to be re-activated when the AG is re-created. --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.