|
I have checked the archives and found some items relating to accessing another job's qtemp files. The problem is that they are a little over my head - I am completely new to this area. The situation is this: for whatever reasons, misguided or otherwise, we use QTEMP files heavily in batch processes. Some of these batch jobs are started by ROBOT software. Our security is setup so that programmers can not even see the job log of a ROBOT job. There are times when there is no one around with *ALLOBJ authority and when a job starts to loop, we have no way to recover the data from QTEMP before ending the job. Management is unlikely to come up with a solution to resolve the problem, especially if the solution involves assigning *ALLOBJ authority to any programmer. What I want to do, and I assume it is possible from what I have read, is create an object that will allow us the specify the qualified job and perhaps the file names in question, and either CRTDUPOBJ or display the file contents from QTEMP so that we can safely end the job without losing the interim data - something that we can call when we need it. Can this be done without adopting *ALLOBJ authority? We don't want to have to go back and modify every program that stores data in QTEMP files. Could someone give me some direction on how I can do this or point me to a primer so that I can understand more of what I am reading in the archives about accessing another job's QTEMP files? thanks much jw +--- | 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.