Charles Mills wrote:
*Most* time fields are built by the individual record cutting product. If a
product wants to record time as Latvian Summer Time expressed in Roman
numerals in its SMF records it is free to do so. Thus one cannot say SMF
time fields are thus and such (unfortunately).
Engelbrecht
Sent: Wednesday, September 18, 2013 3:09 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: CVTLSO, SMF, and RMF (was: Where environment variables ...)
Charles Mills wrote:
*Most* time fields are built by the individual record cutting product. If a
product wants to record time as Latvian Summer
Charles Mills wrote:
Yes, the first 18 bytes are consistent. I know of no inconsistencies there for
IBM or non-IBM products.
Neither me, unless I missed something.
But beyond that point there is no consistent standardization of time (or
other) even within IBM products (Types 0 - 127).
Thus
SMF records are various. In particular, they confront very different
temporal granularities. For some the resolution of an STCKE value
is appropriate; for others the millisecond is the appropriate unit
A standard header is innocuous, but standardizing their substantive
timestamp formats would
] On
Behalf Of John Gilmore
Sent: Wednesday, September 18, 2013 8:42 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: CVTLSO, SMF, and RMF (was: Where environment variables ...)
SMF records are various. In particular, they confront very different
temporal granularities. For some the resolution of an STCKE
I still, perversely(?), wish that every product which produces an SMF
record would have a routine which can be invoked by the IFASMFDP routine
which would reformat the record into a text only type output record.
Perhaps in a documented XML format. Users could then fairly easily be able
to read
] On Behalf
Of Charles Mills
Sent: Tuesday, September 17, 2013 5:29 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: CVTLSO, SMF, and RMF (was: Where environment variables ...)
SMF time fields are all over the map. Some are local, some are GMT, some are in
STCK format, some are in hundredths
On 17 September 2013 17:32, Charles Mills charl...@mcn.org wrote:
Is my first sentence correct if I change it to The z/OS system clock is (if
your shop follows best practices) set to Universal Coordinated Time (UTC,
similar to Greenwich Mean Time or GMT).?
I think it's Coordinated Universal
Gilmartin
Sent: Tuesday, September 17, 2013 4:56 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: CVTLSO, SMF, and RMF (was: Where environment variables ...)
On Tue, 17 Sep 2013 16:08:26 -0400, Charles Mills wrote:
Time Settings
The zArchitecture hardware clock is (if your shop follows best
practices) set
On Tue, 17 Sep 2013 17:28:44 -0400, Charles Mills wrote:
*Most* time fields are built by the individual record cutting product. If a
product wants to record time as Latvian Summer Time expressed in Roman
numerals in its SMF records it is free to do so. Thus one cannot say SMF time
fields are
On Tue, 17 Sep 2013 16:08:26 -0400, Charles Mills wrote:
Time Settings
The zArchitecture hardware clock is (if your shop follows best practices)
set to Universal Coordinated Time (UTC, similar to Greenwich Mean Time or
GMT).
I believe not. By best practice it is set (and steered by STP) to TAI
11 matches
Mail list logo
