On 2014-01-27, at 05:33, Hunkeler, Peter wrote: >> I'm in a thread on MVS-OE about a bug that suggests that >> Unix System Services is CVTLSO-ignorant. Tests and >> statistics welcomed. Rexx: >> >> address TSO time; address SH date; address TSO time > > I just ran: > > /* rexx */ > address TSO "time"; address SH "date"; address TSO "time" > CVTaddrx = c2x( storage( '00000010', 4 ) ) > CVTEXT2addr = c2x( storage( d2x( x2d( CVTaddrx ) + 328 ), 4 ) ) > CVTLSOaddr = d2x( x2d( CVTEXT2addr ) + 80 ) > say "CVTLSO is x'" || c2x( storage( CVTLSOaddr, 8 ) ) || "'" > > Result: > IKJ56650I TIME-01:31:30 PM. CPU-00:00:00 SERVICE-729 SESSION-00:00:00 JANUARY > 27,2014 > Mo 27 Jan 13:31:30 2014 > IKJ56650I TIME-01:31:30 PM. CPU-00:00:00 SERVICE-777 SESSION-00:00:00 JANUARY > 27,2014 > CVTLSO is x'00000017D7840000' > > /u/a618725 $> uname -a > OS/390 X22 23.00 03 2817 > Thanks. That's reassuring. The OP's on MVS-OE problem may be soomehow idiosyncratic.
I'm still (idly) curious: What problems have people experienced with timestamp skew due to inconsistent application of CVTLSO? Ten years ago, they were so severe that we turned it off. Thanks, gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
