|
midrange.com
From the RPG Reference Manual for V4R5.
This is for fields in the PSDS
| 191 | 198 | Character | 8 | | Date (*DATE format)
the job entered the |
| | | | | | system. In the case
of batch jobs submitted |
| | | | | | for overnight
processing, those that run |
| | | | | | after midnight will
carry the next day's |
| | | | | | date. This value is
derived from the job |
| | | | | | date, with the year
expanded to the full |
| | | | | | four years. The date
represented by this |
| | | | | | value is the same
date represented by |
| | | | | | positions 270 - 275.
|
| 270 | 275 | Zoned decimal | 6,0 | | Date (in UDATE
format) the program started |
| | | | | | running in the
system (UDATE is derived from |
| | | | | | this date). See
"User Date Special Words" in |
| | | | | | topic 1.1.3 for a
description of UDATE. This |
| | | | | | is commonly known as
the 'job date'. The |
| | | | | | date represented by
this value is the same |
| | | | | | date represented by
positions 191 - 198. |
|_______|_______|_______________|_______|___________|______________________________________________|
This confirms two things:
1) You can use the PSDS to get the date the job started running. Note,
that it is not the date the job was submitted, but the date it starts
running.
2) UDATE is the same date as this date. In other words, UDATE does NOT
change after midnight. I know from experience that this is absolutely true.
If you need the actual date, the TIME op-code is the way to get it. UDATE
is always the date the job started running.
Hope this helps.
Mark Phippard
SoftLanding Systems
dkeck@idt.net
Sent by: To: MIDRANGE-L@midrange.com
owner-midrange-l@mi cc:
drange.com Subject: RE: PSDS System
Date / InternalJobID
08/21/00 11:49 AM
Please respond to
MIDRANGE-L
To put things in perspective ... the application is a utility that a
programmer
may fire up and close down several times during the day. I want to
preserve
session-level (duration is life of interactive job) settings established in
the
morning so that they do not need to be re-established repeatedly during the
day. The utility should not impact the LDA as that could interfere with
the
programmers other actvities. The activation group in which the utility
runs
may even be shut down, only to have the programmer fire up the utility
again.
I don't want the session defaults lost during this sequence. Now it is
true
that "anything that _can_ be changed _can_ be changed", and I am mindful of
this. That's why the LDA, UDATE, and QDATE don't work. The system date in
the
PSDS and the Internal Job ID from QRTVJOBI are good only if my original
concerns about them are resolved.
> >
> > UDATE is in adequate because it can change during the interactive
session,
> > albeit not automatically at midnight. -Dave
> >
>
> If this can happen deliberately then is you're best bet is to put the
date
> into a *LDA when you first get it, and use that subsequently?
>
> After all, anything that _can_ be changed _can_ be changed?
>
>
> +---
> | 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 message was sent through IDT.
http://www.idt.net/
+---
| 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.
