|
The systems I've worked on signed them off after some three hours. If you don't have some limit, you can get some jobs lasting for three days (I have found them!).
There is good sense to having the job date stay the same, to handle precisely the report programs that run past midnight, plus in a few instances to get between certain date parameters and run the report or update or some other function, where it must run with such a date.
Also, methinks it's less confusing to the users who get print reports if the report time is printed on each page is the initial start time for the program, to keep it the same. I usually label it Run Time, and it is the system time, not the job time.
-- Alan
...I pulled that from a report program.
Normally for display programs, I just use the DDS keywords and don't even bother with date & time in the program, unless file output with a timestamp is included, in which case it's always a TIME to a timestamp. Never UDATE.
Thanks for being persistent, Rob!
db
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.