<SNIP>
To wrap this up ... what can we recommend that Brian P. and his user
do?
(1) Change the hardware clock to keep it in sync with the software
clock
and use PARMLIB TIMEZONE offsets?
(2) Change any affected COBOL programs to use a FUNCTION or CALL to
COBOL- or LE-date/time routines that retrieve their data from the
software clock, local time, instead of the hardware clock?
(3) ??? Any other suggestions?
</SNIP>
Our shop has been moving to the LE (Cobol Intrinsic Function) (option 2)
for getting the clock, in both Batch and CICS regions. So that would me
my suggestion. Sample attached:
MOVE FUNCTION CURRENT-DATE TO SYSTEM-DATE-TIME.
Where
* FILEDS FOR LANG ENV DATETIME FUNCTION
01 SYSTEM-DATE-TIME.
05 SYSTEM-DATE.
10 SD-CC PIC 9(2).
10 SD-YY PIC 9(2).
10 SD-MM PIC 9(2).
10 SD-DD PIC 9(2).
05 FILLER REDEFINES SYSTEM-DATE.
10 SD-FULL-DATE PIC 9(8).
05 FILLER REDEFINES SYSTEM-DATE.
10 FILLER PIC X(2).
10 SD-PARTIAL-DATE PIC 9(6).
05 FILLER REDEFINES SYSTEM-DATE.
10 SD-CCYY PIC 9(4).
10 SD-MMDD PIC 9(4).
05 SYSTEM-TIME.
10 ST-HOUR PIC 9(2).
10 ST-MINS PIC 9(2).
10 ST-SECS PIC 9(2).
10 ST-HSEC PIC 9(2).
05 FILLER REDEFINES SYSTEM-TIME.
10 ST-PARTIAL-TIME PIC 9(6).
10 FILLER PIC X(2).
05 GMT-FLAG PIC X(1).
88 BEHIND-GMT VALUE '-'.
88 AHEAD-OF-GMT VALUE '+'.
88 GMT-DISABLED VALUE '0'.
05 GMT-OFFSET.
10 GMT-HOUR PIC 9(2).
10 GMT-MINS PIC 9(2).
This gives you all the information about local time, and the offset from
GMT.
Darren M. Gavin
Systems Analyst, Enterprise Application Services
(503) 373-1384
Department of Administrative Services
Operations Division
155 Cottage St. NE U90
Salem, OR 97301-3966
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
