On Tue, 31 Dec 2019 05:51:40 +0000, Gadi Ben-Avi wrote:
>I changed TZ to the value you suggested, and when I issue the time command I
>get UTC.
>
So the TZ mailing list gently scolded me for rehashing old news and mentioned:
http://austingroupbugs.net/view.php?id=1252
This proposal would address Austin Group issue 0000661 "grammar of TZ variable
is insufficient for describing Israel Daylight-saving time", as
TZ='IST-2IDT,M3.4.4/26,M10.5.0' represents current rules for Israel, with the
'/26' exercising the proposed extension. It would also let POSIX TZ strings
represent the current daylight-saving scheme for Godthab, via
TZ='<-03>3<-02>,M3.5.0/-2,M10.5.0/-1' where the '/-2' and '/-1' exercise the
proposed extension.
...
The two minor extensions are specified in Internet RFC 8536 section 3.3.1 "TZ
String Extensions" <https://tools.ietf.org/html/rfc8536#page-13>, [^] and the
proposed action is to add these to POSIX.
And in RFC 8536:
...
Example: <-03>3<-02>,M3.5.0/-2,M10.5.0/-1
This represents a time zone that observes daylight saving time
from 22:00 on the day before March's last Sunday until 23:00 on
the day before October's last Sunday. Standard time is 3 hours
west of UT and is abbreviated "-03"; daylight saving time is 2
hours west of UT and is abbreviated "-02".
So Israel needs only wait until POSIX assimilates RFC 8536 then z/OS
conforms to the updated POSIX.
RFE, anyone?
>-----Original Message-----
>From: Paul Gilmartin
>Sent: Monday, December 30, 2019 9:28 AM
> ...
>A better approach, extracting information from Linux, which does it right:
>
> 503 $ tail -1 /usr/share/zoneinfo/Asia/Tel_Aviv
> IST-2IDT,M3.4.4/26,M10.5.0
-- gil
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
