|
David - maybe it's too late in the day but I'm not sure I understand what you mean by the following statement - or exacly what you are trying to achieve. >> "We didn't think about QCMD and PDM. Quite a bit of testing goes on where calls are made from these programs." << Using the base program in a menu chain as the program that names the AG and having the rest of the chain specify *CALLER is what I'd normally recommend. If you can elaborate on what your problems are I may be able to help more. Do you mean that when you're testing you call the program from the command line (or PDM) - the more I think about it the more I think that's what you meant. If you do, then using a named AG for all programs would probably work best. In V4R2 they are allowing you to change the AG name of any program running in a named AG - perhaps that will help? Jon Paris - AS/400 AD Market Support - paris@ca.ibm.com Phone: (416) 448-4019 - Fax: (416) 448-4414 +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to "MIDRANGE-L@midrange.com". | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.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.