|
Roger, Create a service job. Sounds like it will work. Next question is: How do you create a service job? I've run debug for programs but not on job that's running. Art -----Original Message----- From: Roger Boucher [mailto:RBoucher@stanpac.com] Sent: Thursday, July 15, 1999 3:21 PM To: 'MIDRANGE-L@midrange.com' Subject: RE: temporary files If the program is submitted to batch you will have to make program modifications to copy the files in QTEMP to new files in another library (where you could then review them at your leisure). You would have to do this because a submitted job's QTEMP goes away when the job ends. Or you could run a service job to debug the program while it is running in batch and then you could stop the program and view what is in QTEMP. I don't believe there is any other way (besides debug) for you to "enter" that job and look at what it has in QTEMP. If the program is running interactively you could run it in debug and stop it at any point you like and then you can look at what is in QTEMP. Or you could (as described above) modify the program to copy the files from QTEMP. If you need any help with any of this, let me know. Disclaimer: The above assumes that one of the many brilliant minds on this list don't know some beautiful way to accomplish what you want without debug or program modifications... which I certainly wouldn't rule out! -----Original Message----- From: Art Baker [mailto:Art_Baker@baan.com] Sent: Thursday, July 15, 1999 12:58 PM To: 'MIDRANGE-L@midrange.com' Subject: temporary files Hello, How do you capture data from a temporary file. What I'm trying to look at is a file that is created in QTEMP and deleted when the process is complete. The process is a HLL financial program which runs payments fine but I'd like to see the data that is created in this temporary file. In all there are three files iastl089, iastl090 and iastl091. The TL meaning a temporary logical. Thanks in advance, Art +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@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 +--- +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@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 +--- +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@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-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.