> I hope not.
What do you have against ETOD?
> TIME macro
TIME STCKE,foo
Or doesn't that do the adjustments?
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
________________________________________
From: IBM Mainframe Discussion List [[email protected]] on behalf of
Paul Gilmartin [[email protected]]
Sent: Monday, April 27, 2020 10:46 AM
To: [email protected]
Subject: Re: Friday OT, cheerful program for gloomy times
On 2020-04-27, at 04:57:13, Seymour J Metz wrote:
>
> Is there a statement of direction for using ETOD for all timestamping?
>
I hope not.
I once went to SR because the timestamps in IEBCOPY SYSPRINT were
about 20 seconds ahead of those in job log. Suggested I suspected
a leap second problem.
Level 1> Whatsa Leap Second?
gil> [lotsa URLs; GIYF]
Level 1> Wow! Thanks!
They fixed it; closure text said they switched to TIME macro --
much better idea than RYO from ETOD, CVTLSO, CVTLDTO, ...
> On 2020-04-27, at 03:41:14, ITschak Mugzach wrote:
>
> צ
>
> בתאריך יום ב׳, 27 באפר׳ 2020, 12:38, מאת David Crayford ...
>
Year 5800/Y6K problem?
-- gil
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
