|
The job is submitted by the built-in job scheduler; and scheduled for submission at midnight. I was surprised (shocked, actually) to see that the job had an 'Entered system time' and 'Start time' of 00:00:01 on August 15, but that the 'Job date' was August 14. Anyone have any explanation for this weirdness, for lack of a better term?
I suspect that when the job was submitted, QDATE was still Aug 14. By the time the job actually started, it had changed to Aug 15. In other words, it was submitted right on the cusp over the date changeover.
I know that you can set the job date to any value you like. You can put a hard-coded date in the job description if you like, therefore causing the job date for a job to always be the same Or you can specify the date for the job on the SBMJOB command.
Frankly, software that wants to create a file using the current date should never use the job date. It should always use the system date. I can't think of a good reason you'd want to use the job date.
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.
midrange.com
