Actually, there was no need to change the TZ variable. What we did is issue the command SET TIMEZONE=E.03.00 at 2 am on March 24th. On Sunday (our next regular work day), I changed the CLOCKxx member to reflect the change, in case we decide to IPL at some time in the future.
Gadi -----Original Message----- From: IBM Mainframe Discussion List <[email protected]> On Behalf Of Paul Gilmartin Sent: יום ב 27 מרץ 2023 11:45 To: [email protected] Subject: Re: What time is it in Lebanon? On Mon, 27 Mar 2023 06:48:49 +0000, Gadi Ben-Avi wrote: >We changed the time on Friday March 24th at 2 am. > Do you mean you changed the TZ variable on March 24? >-----Original Message----- >On Mon, 27 Mar 2023 04:49:32 +0000, Gadi Ben-Avi wrote: > >>When I install a new version of z/OS in Israel I set the time zone in >>SYS1.PARMLIB(CLOCKxx) and in /etc/profile. I set TZ to IST-2IDT. >> That variable causes the offset to change on March 12, American rules, not Israeli, according to: <https://www.ibm.com/docs/en/zos/2.5.0?topic=variable-command-format> If this Daylight Saving Time rule is omitted altogether, the values in the rule default to the standard rules for American Daylight Saving Time. -- 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
