|
Alan,
Someone mentioned using a data area. This might help solve both your needs (albeit, one of them in an ugly way).
Create the data area with a numeric value (let's say 30). Instead of a straight delay, have your CL pgm loop thru reading the data area 10 times (10 x 30 = 300 seconds (5 minutes)). At any point during the delay, you could change the data area's value to zero and the most you'd have to wait would be 30 seconds (a lot more palatable than 5 minutes). Within this loop, you could send a message to the job log, or even do a brkmsg giving the elapsed time (number of iterations x data area value). Yes it's ugly but it works.
Thanks to whoever originally mentioned this.
"Alan Shore" <ashore@xxxxxxxx> wrote in message news:mailman.2036.1325706670.2619.midrange-l@xxxxxxxxxxxx...
Hi everyone
I am in the process of testing a change that I have made to a CL program
At the moment, the program is on a DLYJOB DLY(300) command
My questions are:-
1. Is there any way of knowing the amount of elapsed time, and therefore the amount of time left?
2. Is there a way of changing this timespan while the program is running?
These are not deal breakers, but while I am waiting for the program to continue (using STRDBG), it seems MUCH longer than 5 minutes have elapsed
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.