|
jobIt seems that a lot of people have gotten into the habit of using the
guessdate to determine the current date. I'm not really sure why, but I
oneit is probably because most interactive jobs don't run for more than
UDATE.day, or over midnight.
In the days of yore, we might want to run our end of month batch jobs
over a weekend. We'd insert a //DATE OCL card in the job stream to set
the job date to say 30 June 2007. Then, no matter which calendar day
the job was run, all the reports would use 30 June as their date via
In modern times, CHGJOB DATE() does the same thing. So if you needed
to, you could set your current job date back a month and re-run your end
of month.
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.