Re: We're IST-2IDT, and switching back from UTC+3 to UTC+2 at 2AM Oct. 28th
Here is something confusing me for several years: The publication https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.3.0/com.ibm.zos.v2r3.bpxa400/dtcutz.htm states TZ should be set at your /etc/csh.login, but I will add your suggestion (/etc/rc) to my list of locations requiring modification whenever TZ's startdate/enddate are to be adjusted, just to be on the safer side. Thank You and all contributors of insights into this issue. On Mon, 29 Oct 2018 12:32:41 +, Allan Staller wrote: >You also need to modify /etc/rc > >-Original Message- >From: IBM Mainframe Discussion List On Behalf Of >Giliad Wilf >Sent: Sunday, October 28, 2018 4:40 AM >To: IBM-MAIN@LISTSERV.UA.EDU >Subject: Re: We're IST-2IDT, and switching back from UTC+3 to UTC+2 at 2AM >Oct. 28th > >Yes, > >I did set TZ to IST-2TDT five months ago on /etc/profile, and at additional >places , such as: > >/etc/init.options >/etc/httpd.envvars >/etc/csh.login >/usr/local/zoneinfo > >...and, of cosrse, also on CEEDOPT, CEECOPT, and on CELQDOPT sectors of >CEEPRM00...to no avail. > >Something is still missing. >I can't believe an IPL is required for USS to pick timezone switch back. > > >On Sun, 28 Oct 2018 08:45:17 +,aGadi Ben-Avi wrote: > >>For USS stuff, look in /etc/profile. There might be a TZ varable being set >>there. >> >>-Original Message- >>From: IBM Mainframe Discussion List On >>Behalf Of Giliad Wilf >>Sent: Sunday, October 28, 2018 10:26 AM >>To: IBM-MAIN@LISTSERV.UA.EDU >>Subject: Re: We're IST-2IDT, and switching back from UTC+3 to UTC+2 at >>2AM Oct. 28th >> >>Well, something did not work as I expected. >>(My original post: >>https://apac01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flist >>serv.ua.edu%2Fcgi-bin%2Fwa%3FA2%3Dind1810%26L%3DIBM-MAIN%26O%3DD%26P%3D >>420113data=02%7C01%7Callan.staller%40HCL.COM%7C92275959a09c4ce5a5c >>a08d63cb94ffd%7C189de737c93a4f5a8b686f4ca9941912%7C0%7C0%7C636763163967 >>475966sdata=QWDCq95Cyept91rYe3HgFb7%2FmdHYS%2BOKnPRRrZF7GEk%3D >>;reserved=0 ) >> >>The command... >>$TA STTZ,T=98.00,'$VS,''SET TIMEZONE=E.02.00''' >>...issued on Wed. Oct. 24th did switch local time back from IDT (UTC+3) to >>IST (UTC+2) this morning at 2AM (local time switched back to 1AM), and I've >>corrected TIMEZONE statement at CLOCK00 to read "E.02.00.00" rather than >>"E.03.00.00", but USS still thinks we're on IDT. >> >>Here are some USS commands I've issued this morning (I did not change >>anything on USS parameters since May): >> >>IBMUSER:/u/ibmuser: >env >>MAIL=/usr/mail/IBMUSER >>_BPX_TERMPATH=OMVS >>PATH=/Z22D/opt/SP/bin:/Z22D/opt/GIT/bin:/bin:. >>SHELL=/bin/sh >>PS1=$LOGNAME:$PWD: > >>COLUMNS=134 >>_=/bin/env >>LOGNAME=IBMUSER >>STEPLIB=none >>LANG=C >>LIBPATH=/lib:/usr/lib:. >>TERM=dumb >>HOME=/u/ibmuser >>LINES=62 >>TZ=IST-2IDT >>MANPATH=/usr/man/%L >>NLSPATH=/usr/lib/nls/msg/%L/%N:/usr/lib/nls/msg/%L/%N.cat >>TR_Options=noResumableTrapHandler >>IBMUSER:/u/ibmuser: >date >>Sun Oct 28 10:56:09 IDT 2018 >>IBMUSER:/u/ibmuser: >date -u >>Sun Oct 28 07:56:18 GMT 2018 >>IBMUSER:/u/ibmuser: > >> >>=End of Display = >> >>UTC is correct, and one can see 'TZ=IST-2IDT', and everything on z/OS is >>absolutely OK, except for USS. >>USS still thinks we're three hours East. >> >>Is IPL required anyway (which I don't believe is necessary), or am I missing >>something obvious ? >> >>Regards, >>Giliad >> >>On Thu, 25 Oct 2018 02:39:41 -0500, Giliad Wilf wrote: >> >>>Good question. >>>Developers here do not rely on local time, but I want them to always see >>>local time. >>>It has something to do with human perception of "reality". >>> >>>Giliad >>> >>>On Wed, 24 Oct 2018 16:30:24 -0500, Paul Gilmartin >>>wrote: >>> On Wed, 24 Oct 2018 02:38:39 -0500, Giliad Wilf wrote: > >At 2AM on Sunday, Oct. 28th, Israel is switching from IDT to IST. >... >... We ... as far as I know, do not rely on local time. > ??? If you "do not rely on local time", how can timezones and offsets matter to you? -- gil - - For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN >>> >>>-- >>>For IBM-MAIN subscribe / signoff / archive access instructions, send >>>email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN >> >>-- >>For IBM-MAIN subscribe / signoff / archive access instructions, send >>email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN >> >>. >>הודעה זו נשלחה אליך מטעם חברה בקבוצת מלם תים וייתכן שהיא מוגנת תחת סודיות >>מסחרית. כל הצעה, התחייבות או מצג מטעם החברה, מחייבים מסמך נפרד וחתום על ידי >>מורשה החתימה של החברה. החברה רשאית לנטר כל תכתובת העוברת בשרתיה והיא לא תישא >>באחריות לכל נזק, ו/או אובדן,
Re: We're IST-2IDT, and switching back from UTC+3 to UTC+2 at 2AM Oct. 28th
You also need to modify /etc/rc -Original Message- From: IBM Mainframe Discussion List On Behalf Of Giliad Wilf Sent: Sunday, October 28, 2018 4:40 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: We're IST-2IDT, and switching back from UTC+3 to UTC+2 at 2AM Oct. 28th Yes, I did set TZ to IST-2IDT five months ago on /etc/profile, and at additional places , such as: /etc/init.options /etc/httpd.envvars /etc/csh.login /usr/local/zoneinfo ...and, of course, also on CEEDOPT, CEECOPT, and on CELQDOPT sectors of CEEPRM00...to no avail. Something is still missing. I can't believe an IPL is required for USS to pick timezone switch back. On Sun, 28 Oct 2018 08:45:17 +, Gadi Ben-Avi wrote: >For USS stuff, look in /etc/profile. There might be a TZ varable being set >there. > >-Original Message- >From: IBM Mainframe Discussion List On >Behalf Of Giliad Wilf >Sent: Sunday, October 28, 2018 10:26 AM >To: IBM-MAIN@LISTSERV.UA.EDU >Subject: Re: We're IST-2IDT, and switching back from UTC+3 to UTC+2 at >2AM Oct. 28th > >Well, something did not work as I expected. >(My original post: >https://apac01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flist >serv.ua.edu%2Fcgi-bin%2Fwa%3FA2%3Dind1810%26L%3DIBM-MAIN%26O%3DD%26P%3D >420113data=02%7C01%7Callan.staller%40HCL.COM%7C92275959a09c4ce5a5c >a08d63cb94ffd%7C189de737c93a4f5a8b686f4ca9941912%7C0%7C0%7C636763163967 >475966sdata=QWDCq95Cyept91rYe3HgFb7%2FmdHYS%2BOKnPRRrZF7GEk%3D >;reserved=0 ) > >The command... >$TA STTZ,T=98.00,'$VS,''SET TIMEZONE=E.02.00''' >...issued on Wed. Oct. 24th did switch local time back from IDT (UTC+3) to IST >(UTC+2) this morning at 2AM (local time switched back to 1AM), and I've >corrected TIMEZONE statement at CLOCK00 to read "E.02.00.00" rather than >"E.03.00.00", but USS still thinks we're on IDT. > >Here are some USS commands I've issued this morning (I did not change anything >on USS parameters since May): > >IBMUSER:/u/ibmuser: >env >MAIL=/usr/mail/IBMUSER >_BPX_TERMPATH=OMVS >PATH=/Z22D/opt/SP/bin:/Z22D/opt/GIT/bin:/bin:. >SHELL=/bin/sh >PS1=$LOGNAME:$PWD: > >COLUMNS=134 >_=/bin/env >LOGNAME=IBMUSER >STEPLIB=none >LANG=C >LIBPATH=/lib:/usr/lib:. >TERM=dumb >HOME=/u/ibmuser >LINES=62 >TZ=IST-2IDT >MANPATH=/usr/man/%L >NLSPATH=/usr/lib/nls/msg/%L/%N:/usr/lib/nls/msg/%L/%N.cat >TR_Options=noResumableTrapHandler >IBMUSER:/u/ibmuser: >date >Sun Oct 28 10:56:09 IDT 2018 >IBMUSER:/u/ibmuser: >date -u >Sun Oct 28 07:56:18 GMT 2018 >IBMUSER:/u/ibmuser: > > >=End of Display = > >UTC is correct, and one can see 'TZ=IST-2IDT', and everything on z/OS is >absolutely OK, except for USS. >USS still thinks we're three hours East. > >Is IPL required anyway (which I don't believe is necessary), or am I missing >something obvious ? > >Regards, >Giliad > >On Thu, 25 Oct 2018 02:39:41 -0500, Giliad Wilf wrote: > >>Good question. >>Developers here do not rely on local time, but I want them to always see >>local time. >>It has something to do with human perception of "reality". >> >>Giliad >> >>On Wed, 24 Oct 2018 16:30:24 -0500, Paul Gilmartin >>wrote: >> >>>On Wed, 24 Oct 2018 02:38:39 -0500, Giliad Wilf wrote: At 2AM on Sunday, Oct. 28th, Israel is switching from IDT to IST. ... ... We ... as far as I know, do not rely on local time. >>>??? >>> >>>If you "do not rely on local time", how can timezones and offsets matter to >>>you? >>> >>>-- gil >>> >>>- >>>- For IBM-MAIN subscribe / signoff / archive access instructions, >>>send email to lists...@listserv.ua.edu with the message: INFO >>>IBM-MAIN >> >>-- >>For IBM-MAIN subscribe / signoff / archive access instructions, send >>email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > >-- >For IBM-MAIN subscribe / signoff / archive access instructions, send >email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > >. >הודעה זו נשלחה אליך מטעם חברה בקבוצת מלם תים וייתכן שהיא מוגנת תחת סודיות >מסחרית. כל הצעה, התחייבות או מצג מטעם החברה, מחייבים מסמך נפרד וחתום על ידי >מורשה החתימה של החברה. החברה רשאית לנטר כל תכתובת העוברת בשרתיה והיא לא תישא >באחריות לכל נזק, ו/או אובדן, שיבוש או פגיעה במידע כלשהו שנגרם מסיבות של תקיפה >חיצונית ו/או זדונית על הארגון. > >-- >For IBM-MAIN subscribe / signoff / archive access instructions, send >email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ::DISCLAIMER::
Re: We're IST-2IDT, and switching back from UTC+3 to UTC+2 at 2AM Oct. 28th
On Sun, 28 Oct 2018 14:12:21 -0400, Steve Smith wrote: >Not a complete answer, but USS (& I assume Unix in general) lets each user >set the timezone as they wish. Now I wish I could on TSO. > Yup. And DST boundaries are handled automatically for most locales. IIRC, a couple weeks ago, Peter Relson said, make a business case and submit an RFE. The archives of this list should be an indicator of how much human resource is being spent. >On Sun, Oct 28, 2018 at 10:51 AM Giliad Wilf wrote: > >> Sigh...why couldn't USS pick this info from the CVTTZ? Why is it >> necessary to maintain this switching date in two different formats? > Conway's Law. -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: We're IST-2IDT, and switching back from UTC+3 to UTC+2 at 2AM Oct. 28th
Not a complete answer, but USS (& I assume Unix in general) lets each user set the timezone as they wish. Now I wish I could on TSO. sas On Sun, Oct 28, 2018 at 10:51 AM Giliad Wilf < 00d50942efa9-dmarc-requ...@listserv.ua.edu> wrote: > My fault ! > > TZ had to be expressed with startdate and enddate like this: > > IST-2IDT,M3.4.5,M10.5.0 > > ...where M.3.4.5 means start date is month 3, week 4, day 5 (Friday) > ...and M10.5.0 means end date is month 10, week 5, day 0 (Sunday). > > I suddenly recalled raising this issue half a year ago, searched the > archives and found what was missing. > Maybe I'm dealing with too many issues in parallel, and this one slipped > away. > > Sigh...why couldn't USS pick this info from the CVTTZ? Why is it > necessary to maintain this switching date in two different formats? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: We're IST-2IDT, and switching back from UTC+3 to UTC+2 at 2AM Oct. 28th
My fault ! TZ had to be expressed with startdate and enddate like this: IST-2IDT,M3.4.5,M10.5.0 ...where M.3.4.5 means start date is month 3, week 4, day 5 (Friday) ...and M10.5.0 means end date is month 10, week 5, day 0 (Sunday). I suddenly recalled raising this issue half a year ago, searched the archives and found what was missing. Maybe I'm dealing with too many issues in parallel, and this one slipped away. Sigh...why couldn't USS pick this info from the CVTTZ? Why is it necessary to maintain this switching date in two different formats? On Sun, 28 Oct 2018 04:39:30 -0500, Giliad Wilf wrote: >Yes, > >I did set TZ to IST-2IDT five months ago on /etc/profile, and at additional >places , such as: > >/etc/init.options >/etc/httpd.envvars >/etc/csh.login >/usr/local/zoneinfo > >...and, of course, also on CEEDOPT, CEECOPT, and on CELQDOPT sectors of >CEEPRM00...to no avail. > >Something is still missing. >I can't believe an IPL is required for USS to pick timezone switch back. > > >On Sun, 28 Oct 2018 08:45:17 +, Gadi Ben-Avi wrote: > >>For USS stuff, look in /etc/profile. There might be a TZ varable being set >>there. >> >>-Original Message- >>From: IBM Mainframe Discussion List On Behalf Of >>Giliad Wilf >>Sent: Sunday, October 28, 2018 10:26 AM >>To: IBM-MAIN@LISTSERV.UA.EDU >>Subject: Re: We're IST-2IDT, and switching back from UTC+3 to UTC+2 at 2AM >>Oct. 28th >> >>Well, something did not work as I expected. >>(My original post: >>https://listserv.ua.edu/cgi-bin/wa?A2=ind1810=IBM-MAIN=D=420113 ) >> >>The command... >>$TA STTZ,T=98.00,'$VS,''SET TIMEZONE=E.02.00''' >>...issued on Wed. Oct. 24th did switch local time back from IDT (UTC+3) to >>IST (UTC+2) this morning at 2AM (local time switched back to 1AM), and I've >>corrected TIMEZONE statement at CLOCK00 to read "E.02.00.00" rather than >>"E.03.00.00", but USS still thinks we're on IDT. >> >>Here are some USS commands I've issued this morning (I did not change >>anything on USS parameters since May): >> >>IBMUSER:/u/ibmuser: >env >>MAIL=/usr/mail/IBMUSER >>_BPX_TERMPATH=OMVS >>PATH=/Z22D/opt/SP/bin:/Z22D/opt/GIT/bin:/bin:. >>SHELL=/bin/sh >>PS1=$LOGNAME:$PWD: > >>COLUMNS=134 >>_=/bin/env >>LOGNAME=IBMUSER >>STEPLIB=none >>LANG=C >>LIBPATH=/lib:/usr/lib:. >>TERM=dumb >>HOME=/u/ibmuser >>LINES=62 >>TZ=IST-2IDT >>MANPATH=/usr/man/%L >>NLSPATH=/usr/lib/nls/msg/%L/%N:/usr/lib/nls/msg/%L/%N.cat >>TR_Options=noResumableTrapHandler >>IBMUSER:/u/ibmuser: >date >>Sun Oct 28 10:56:09 IDT 2018 >>IBMUSER:/u/ibmuser: >date -u >>Sun Oct 28 07:56:18 GMT 2018 >>IBMUSER:/u/ibmuser: > >> >>=End of Display = >> >>UTC is correct, and one can see 'TZ=IST-2IDT', and everything on z/OS is >>absolutely OK, except for USS. >>USS still thinks we're three hours East. >> >>Is IPL required anyway (which I don't believe is necessary), or am I missing >>something obvious ? >> >>Regards, >>Giliad >> >>On Thu, 25 Oct 2018 02:39:41 -0500, Giliad Wilf wrote: >> >>>Good question. >>>Developers here do not rely on local time, but I want them to always see >>>local time. >>>It has something to do with human perception of "reality". >>> >>>Giliad >>> >>>On Wed, 24 Oct 2018 16:30:24 -0500, Paul Gilmartin >>>wrote: >>> On Wed, 24 Oct 2018 02:38:39 -0500, Giliad Wilf wrote: > >At 2AM on Sunday, Oct. 28th, Israel is switching from IDT to IST. >... >... We ... as far as I know, do not rely on local time. > ??? If you "do not rely on local time", how can timezones and offsets matter to you? -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN >>> >>>-- >>>For IBM-MAIN subscribe / signoff / archive access instructions, send >>>email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN >> >>-- >>For IBM-MAIN subscribe / signoff / archive access instructions, send email to >>lists...@listserv.ua.edu with the message: INFO IBM-MAIN >> >>. >>הודעה זו נשלחה אליך מטעם חברה בקבוצת מלם תים וייתכן שהיא מוגנת תחת סודיות >>מסחרית. כל הצעה, התחייבות או מצג מטעם החברה, מחייבים מסמך נפרד וחתום על ידי >>מורשה החתימה של החברה. החברה רשאית לנטר כל תכתובת העוברת בשרתיה והיא לא תישא >>באחריות לכל נזק, ו/או אובדן, שיבוש או פגיעה במידע כלשהו שנגרם מסיבות של תקיפה >>חיצונית ו/או זדונית על הארגון. >> >>-- >>For IBM-MAIN subscribe / signoff / archive access instructions, >>send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > >-- >For IBM-MAIN subscribe / signoff / archive access instructions, >send email to
Re: We're IST-2IDT, and switching back from UTC+3 to UTC+2 at 2AM Oct. 28th
Yes, I did set TZ to IST-2IDT five months ago on /etc/profile, and at additional places , such as: /etc/init.options /etc/httpd.envvars /etc/csh.login /usr/local/zoneinfo ...and, of course, also on CEEDOPT, CEECOPT, and on CELQDOPT sectors of CEEPRM00...to no avail. Something is still missing. I can't believe an IPL is required for USS to pick timezone switch back. On Sun, 28 Oct 2018 08:45:17 +, Gadi Ben-Avi wrote: >For USS stuff, look in /etc/profile. There might be a TZ varable being set >there. > >-Original Message- >From: IBM Mainframe Discussion List On Behalf Of >Giliad Wilf >Sent: Sunday, October 28, 2018 10:26 AM >To: IBM-MAIN@LISTSERV.UA.EDU >Subject: Re: We're IST-2IDT, and switching back from UTC+3 to UTC+2 at 2AM >Oct. 28th > >Well, something did not work as I expected. >(My original post: >https://listserv.ua.edu/cgi-bin/wa?A2=ind1810=IBM-MAIN=D=420113 ) > >The command... >$TA STTZ,T=98.00,'$VS,''SET TIMEZONE=E.02.00''' >...issued on Wed. Oct. 24th did switch local time back from IDT (UTC+3) to IST >(UTC+2) this morning at 2AM (local time switched back to 1AM), and I've >corrected TIMEZONE statement at CLOCK00 to read "E.02.00.00" rather than >"E.03.00.00", but USS still thinks we're on IDT. > >Here are some USS commands I've issued this morning (I did not change anything >on USS parameters since May): > >IBMUSER:/u/ibmuser: >env >MAIL=/usr/mail/IBMUSER >_BPX_TERMPATH=OMVS >PATH=/Z22D/opt/SP/bin:/Z22D/opt/GIT/bin:/bin:. >SHELL=/bin/sh >PS1=$LOGNAME:$PWD: > >COLUMNS=134 >_=/bin/env >LOGNAME=IBMUSER >STEPLIB=none >LANG=C >LIBPATH=/lib:/usr/lib:. >TERM=dumb >HOME=/u/ibmuser >LINES=62 >TZ=IST-2IDT >MANPATH=/usr/man/%L >NLSPATH=/usr/lib/nls/msg/%L/%N:/usr/lib/nls/msg/%L/%N.cat >TR_Options=noResumableTrapHandler >IBMUSER:/u/ibmuser: >date >Sun Oct 28 10:56:09 IDT 2018 >IBMUSER:/u/ibmuser: >date -u >Sun Oct 28 07:56:18 GMT 2018 >IBMUSER:/u/ibmuser: > > >=End of Display = > >UTC is correct, and one can see 'TZ=IST-2IDT', and everything on z/OS is >absolutely OK, except for USS. >USS still thinks we're three hours East. > >Is IPL required anyway (which I don't believe is necessary), or am I missing >something obvious ? > >Regards, >Giliad > >On Thu, 25 Oct 2018 02:39:41 -0500, Giliad Wilf wrote: > >>Good question. >>Developers here do not rely on local time, but I want them to always see >>local time. >>It has something to do with human perception of "reality". >> >>Giliad >> >>On Wed, 24 Oct 2018 16:30:24 -0500, Paul Gilmartin >>wrote: >> >>>On Wed, 24 Oct 2018 02:38:39 -0500, Giliad Wilf wrote: At 2AM on Sunday, Oct. 28th, Israel is switching from IDT to IST. ... ... We ... as far as I know, do not rely on local time. >>>??? >>> >>>If you "do not rely on local time", how can timezones and offsets matter to >>>you? >>> >>>-- gil >>> >>>-- >>>For IBM-MAIN subscribe / signoff / archive access instructions, send >>>email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN >> >>-- >>For IBM-MAIN subscribe / signoff / archive access instructions, send >>email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > >-- >For IBM-MAIN subscribe / signoff / archive access instructions, send email to >lists...@listserv.ua.edu with the message: INFO IBM-MAIN > >. >הודעה זו נשלחה אליך מטעם חברה בקבוצת מלם תים וייתכן שהיא מוגנת תחת סודיות >מסחרית. כל הצעה, התחייבות או מצג מטעם החברה, מחייבים מסמך נפרד וחתום על ידי >מורשה החתימה של החברה. החברה רשאית לנטר כל תכתובת העוברת בשרתיה והיא לא תישא >באחריות לכל נזק, ו/או אובדן, שיבוש או פגיעה במידע כלשהו שנגרם מסיבות של תקיפה >חיצונית ו/או זדונית על הארגון. > >-- >For IBM-MAIN subscribe / signoff / archive access instructions, >send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: We're IST-2IDT, and switching back from UTC+3 to UTC+2 at 2AM Oct. 28th
For USS stuff, look in /etc/profile. There might be a TZ varable being set there. -Original Message- From: IBM Mainframe Discussion List On Behalf Of Giliad Wilf Sent: Sunday, October 28, 2018 10:26 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: We're IST-2IDT, and switching back from UTC+3 to UTC+2 at 2AM Oct. 28th Well, something did not work as I expected. (My original post: https://listserv.ua.edu/cgi-bin/wa?A2=ind1810=IBM-MAIN=D=420113 ) The command... $TA STTZ,T=98.00,'$VS,''SET TIMEZONE=E.02.00''' ...issued on Wed. Oct. 24th did switch local time back from IDT (UTC+3) to IST (UTC+2) this morning at 2AM (local time switched back to 1AM), and I've corrected TIMEZONE statement at CLOCK00 to read "E.02.00.00" rather than "E.03.00.00", but USS still thinks we're on IDT. Here are some USS commands I've issued this morning (I did not change anything on USS parameters since May): IBMUSER:/u/ibmuser: >env MAIL=/usr/mail/IBMUSER _BPX_TERMPATH=OMVS PATH=/Z22D/opt/SP/bin:/Z22D/opt/GIT/bin:/bin:. SHELL=/bin/sh PS1=$LOGNAME:$PWD: > COLUMNS=134 _=/bin/env LOGNAME=IBMUSER STEPLIB=none LANG=C LIBPATH=/lib:/usr/lib:. TERM=dumb HOME=/u/ibmuser LINES=62 TZ=IST-2IDT MANPATH=/usr/man/%L NLSPATH=/usr/lib/nls/msg/%L/%N:/usr/lib/nls/msg/%L/%N.cat TR_Options=noResumableTrapHandler IBMUSER:/u/ibmuser: >date Sun Oct 28 10:56:09 IDT 2018 IBMUSER:/u/ibmuser: >date -u Sun Oct 28 07:56:18 GMT 2018 IBMUSER:/u/ibmuser: > =End of Display = UTC is correct, and one can see 'TZ=IST-2IDT', and everything on z/OS is absolutely OK, except for USS. USS still thinks we're three hours East. Is IPL required anyway (which I don't believe is necessary), or am I missing something obvious ? Regards, Giliad On Thu, 25 Oct 2018 02:39:41 -0500, Giliad Wilf wrote: >Good question. >Developers here do not rely on local time, but I want them to always see local >time. >It has something to do with human perception of "reality". > >Giliad > >On Wed, 24 Oct 2018 16:30:24 -0500, Paul Gilmartin >wrote: > >>On Wed, 24 Oct 2018 02:38:39 -0500, Giliad Wilf wrote: >>> >>>At 2AM on Sunday, Oct. 28th, Israel is switching from IDT to IST. >>>... >>>... We ... as far as I know, do not rely on local time. >>> >>??? >> >>If you "do not rely on local time", how can timezones and offsets matter to >>you? >> >>-- gil >> >>-- >>For IBM-MAIN subscribe / signoff / archive access instructions, send >>email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > >-- >For IBM-MAIN subscribe / signoff / archive access instructions, send >email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN . הודעה זו נשלחה אליך מטעם חברה בקבוצת מלם תים וייתכן שהיא מוגנת תחת סודיות מסחרית. כל הצעה, התחייבות או מצג מטעם החברה, מחייבים מסמך נפרד וחתום על ידי מורשה החתימה של החברה. החברה רשאית לנטר כל תכתובת העוברת בשרתיה והיא לא תישא באחריות לכל נזק, ו/או אובדן, שיבוש או פגיעה במידע כלשהו שנגרם מסיבות של תקיפה חיצונית ו/או זדונית על הארגון. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: We're IST-2IDT, and switching back from UTC+3 to UTC+2 at 2AM Oct. 28th
Well, something did not work as I expected. (My original post: https://listserv.ua.edu/cgi-bin/wa?A2=ind1810=IBM-MAIN=D=420113 ) The command... $TA STTZ,T=98.00,'$VS,''SET TIMEZONE=E.02.00''' ...issued on Wed. Oct. 24th did switch local time back from IDT (UTC+3) to IST (UTC+2) this morning at 2AM (local time switched back to 1AM), and I've corrected TIMEZONE statement at CLOCK00 to read "E.02.00.00" rather than "E.03.00.00", but USS still thinks we're on IDT. Here are some USS commands I've issued this morning (I did not change anything on USS parameters since May): IBMUSER:/u/ibmuser: >env MAIL=/usr/mail/IBMUSER _BPX_TERMPATH=OMVS PATH=/Z22D/opt/SP/bin:/Z22D/opt/GIT/bin:/bin:. SHELL=/bin/sh PS1=$LOGNAME:$PWD: > COLUMNS=134 _=/bin/env LOGNAME=IBMUSER STEPLIB=none LANG=C LIBPATH=/lib:/usr/lib:. TERM=dumb HOME=/u/ibmuser LINES=62 TZ=IST-2IDT MANPATH=/usr/man/%L NLSPATH=/usr/lib/nls/msg/%L/%N:/usr/lib/nls/msg/%L/%N.cat TR_Options=noResumableTrapHandler IBMUSER:/u/ibmuser: >date Sun Oct 28 10:56:09 IDT 2018 IBMUSER:/u/ibmuser: >date -u Sun Oct 28 07:56:18 GMT 2018 IBMUSER:/u/ibmuser: > =End of Display = UTC is correct, and one can see 'TZ=IST-2IDT', and everything on z/OS is absolutely OK, except for USS. USS still thinks we're three hours East. Is IPL required anyway (which I don't believe is necessary), or am I missing something obvious ? Regards, Giliad On Thu, 25 Oct 2018 02:39:41 -0500, Giliad Wilf wrote: >Good question. >Developers here do not rely on local time, but I want them to always see local >time. >It has something to do with human perception of "reality". > >Giliad > >On Wed, 24 Oct 2018 16:30:24 -0500, Paul Gilmartin >wrote: > >>On Wed, 24 Oct 2018 02:38:39 -0500, Giliad Wilf wrote: >>> >>>At 2AM on Sunday, Oct. 28th, Israel is switching from IDT to IST. >>>... >>>... We ... as far as I know, do not rely on local time. >>> >>??? >> >>If you "do not rely on local time", how can timezones and offsets matter to >>you? >> >>-- gil >> >>-- >>For IBM-MAIN subscribe / signoff / archive access instructions, >>send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > >-- >For IBM-MAIN subscribe / signoff / archive access instructions, >send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: We're IST-2IDT, and switching back from UTC+3 to UTC+2 at 2AM Oct. 28th
Good question. Developers here do not rely on local time, but I want them to always see local time. It has something to do with human perception of "reality". Giliad On Wed, 24 Oct 2018 16:30:24 -0500, Paul Gilmartin wrote: >On Wed, 24 Oct 2018 02:38:39 -0500, Giliad Wilf wrote: >> >>At 2AM on Sunday, Oct. 28th, Israel is switching from IDT to IST. >>... >>... We ... as far as I know, do not rely on local time. >> >??? > >If you "do not rely on local time", how can timezones and offsets matter to >you? > >-- gil > >-- >For IBM-MAIN subscribe / signoff / archive access instructions, >send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: We're IST-2IDT, and switching back from UTC+3 to UTC+2 at 2AM Oct. 28th
On Wed, 24 Oct 2018 02:38:39 -0500, Giliad Wilf wrote: > >At 2AM on Sunday, Oct. 28th, Israel is switching from IDT to IST. >... >... We ... as far as I know, do not rely on local time. > ??? If you "do not rely on local time", how can timezones and offsets matter to you? -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: We're IST-2IDT, and switching back from UTC+3 to UTC+2 at 2AM Oct. 28th
Yup! -Original Message- From: IBM Mainframe Discussion List On Behalf Of Giliad Wilf Sent: Wednesday, October 24, 2018 2:39 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: We're IST-2IDT, and switching back from UTC+3 to UTC+2 at 2AM Oct. 28th Hi All, At 2AM on Sunday, Oct. 28th, Israel is switching from IDT to IST. I have issued this morning a JES2 Automatic Command on all z/OS instances: $TA STTZ,T=98.00,'$VS,''SET TIMEZONE=E.02.00''' Currently, our CLOCK00 is: TIMEZONE E.03.00.00 SIMETRID 00 ETRMODE NO ETRZONE NO ETRDELTA 10 STPMODE NO STPZONE NO When I show at office Sunday morning 9AM, I will also modify the line "TIMEZONE E.03.00.00" to read "TIMEZONE E.02.00.00". Will this work, assuming no IPL will occur until Sunday morning? Ah, I forgot to mention. We are a zDPT installation, running z/VM 6.4 and several z/OS guests on top, and as far as I know, do not rely on local time. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ::DISCLAIMER:: -- The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents (with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates. Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of authorized representative of HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any email and/or attachments, please check them for viruses and other defects. -- -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
