|
> Do you mean it's better if you do not have to modify the target job? If so, > I agree, but I think both methods require the target job to do something to > make its QTEMP available to other jobs, either by modifying the PCO or > setting up a message queue. If I'm wrong, someone (Gary? Leif?) please Not wrong per se, maybe too restrictive. It *is* possible (at all security levels) to have one job install another library as QTEMP for any other job. It is not for the faint of heart, but it can be done. I've just demonstrated this to several people. This is a great debugging feature. You start a batch job and now you want to check what is writes to its QTEMP. Start an interactive job, create a permanent library, say, DEBUG, then attach DEBUG as QTEMP for the batch job and watch what the batch job is doing by inspecting files in DEBUG. +--- | This is the MI Programmers Mailing List! | To submit a new message, send your mail to MI400@midrange.com. | To subscribe to this list send email to MI400-SUB@midrange.com. | To unsubscribe from this list send email to MI400-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: dr2@cssas400.com +---
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.