On Mon, 13 Mar 2023 09:15:35 +1100, Attila Fogarasi wrote:
>For leap seconds z/OS provides the value in field CVTLSO. The TIME macro
>available to applications also has options to include all 3 time values
>(raw clock, adjusted by leap seconds, and further adjusted by timezone).
>The z/OS console command "D ETR" shows the STP configuration info, much the
>same as lsstp
>
What 3 distinct values of the ZONE= parameter to the TIME macro yield those 3
different values?
Which is recommended for logging events?
The description of the TIME macro says:
,ZONE=LT ,ZONE=UTC|GMT
LT specifies that the local time and date are to be returned. UTC or GMT
specifies that an externally- sourced time and date such as Coordinated
Universal Time (UTC) or Greenwich Mean Time (GMT) are to be returned.
Refer to the information on time in z/Architecture Principles of
Operation,
SA22-7832 for a discussion of the differences between UTC and GMT.
ZONE is not meaningful if STCK or STCKE is specified.
The PoOps says:
The former term, Greenwich Mean Time (GMT), is now obsolete and
has been replaced with the more precise UTC.
( Do they mean to say "more precise" or "more accuratre"?) GMT is (was?)
Mean Solar Time at the Prime Meridian. UTC is atomic time (TAI) adjusted
by occasional by occasional Leap Seconds. Why is one called "more precise"
than the other?
Should the Assembler Services Ref. mention that GMT is obsolete and should
be deprecated?
If an administrator in my timezone, (POSIX) MST7MDT,M3.2.0,M11.1.0 wishes
tomorrow to convert a timestamp recorded yesterday to displayable UTC and
local time, what services does z/OS provide?
--
gil
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
