(I guess Peter R. overlooked that you appear to be operating
near the Prime Meridian.)
On Mon, 10 May 2021 09:52:16 +0100, Steve Austin wrote:
>I've just found out that PARMLIB(CLOCKxx) here specifies;
>
> TIMEZONE E.01.01.00
>
Ouch! Does that mean that SYSLOG, etc. timestamps are a minute
ahead of your smartphone? Will that adjust to:
TIMEZONE E.00.01.00
next Fall? (Does STP handle that?)
How does that affect OMVS? A test might be:
//WHEN EXEC PGM=BPXBATCH,PARM='SH date >/dev/console'
>Something to do with synchronising with SVN and Jenkin apparently. Didn't
>think I'd need to code for ad-hoc tweaks like that.
>
Does the TIME LT macro avoid tweaks required by STCKE; STCKCONV?
May I infer that SVN and Jenkin (subversion?) is broken and admins
introduced an offsetting breakage? That's *just*wrong*!
>Sorry to waste your time.
>
Rather, the feckless morons who made that accommodation should
apologi[sz]e to Peter and to you.
On Mon, 10 May 2021 09:22:16 +0100, Steve Austin wrote:
> ...
> +0038 LDTO..... 00000DA2 72B00000 ATCVT.... 80BFC000
>
1 *-* say x2d( 00000DA2 72B00000 ) * 2 ** ( 51 - 63 ) * 1e-6
3660.00000
Yup.
-- gil
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
