In 011401ceaa8d$7b6acab0$72406010$@mcn.org, on 09/05/2013
at 04:13 PM, Charles Mills charl...@mcn.org said:
EST5EDT
Due to parsing ambiguity, that doesn't tell you when to switch.
--
Shmuel (Seymour J.) Metz, SysProg and JOAT
ISO position; see
On Sun, Sep 8, 2013 at 5:52 AM, Shmuel Metz (Seymour J.)
shmuel+ibm-m...@patriot.net wrote:
In 011401ceaa8d$7b6acab0$72406010$@mcn.org, on 09/05/2013
at 04:13 PM, Charles Mills charl...@mcn.org said:
EST5EDT
Due to parsing ambiguity, that doesn't tell you when to switch.
--
Shmuel
http://en.wikipedia.org/wiki/Tz_database does tell you when to switch.
And when to add or subtract leap seconds.
On Sun, Sep 8, 2013 at 5:52 AM, Shmuel Metz (Seymour J.)
shmuel+ibm-m...@patriot.net wrote:
In 011401ceaa8d$7b6acab0$72406010$@mcn.org, on 09/05/2013
at 04:13 PM, Charles Mills
http://en.wikipedia.org/wiki/Tz_database Does tell you the offset,
when to switch.
And when to add or subtract leap seconds.
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to
On Sun, 8 Sep 2013 08:04:35 -0500, Mike Schwab wrote:
http://en.wikipedia.org/wiki/Tz_database Does tell you the offset,
when to switch.
And when to add or subtract leap seconds.
z/OS is the only OS of which I know that accommodates leap
seconds in its hardware clock (are there others?)
I
I'm not sure I understand Paul's last post.
z/OS does keep the current leap-second count at hand. This value
changes at most twice a year, at the end of June and at the end of
December; and ample advance notice, at least six months' notice under
BIPM's rules, is given of an impending increment
In
cajtoo5-bqbx01z2xwzf_z0eoc5nzua+5pxat6rep1oazzwc...@mail.gmail.com,
on 09/08/2013
at 08:02 AM, Mike Schwab mike.a.sch...@gmail.com said:
http://en.wikipedia.org/wiki/Tz_database does tell you when to
switch.
The Devil is in the details. The string EST5EDT doesn't have enough
information to
On Sun, 8 Sep 2013 16:22:53 -0400, John Gilmore wrote:
I'm not sure I understand Paul's last post.
z/OS does keep the current leap-second count at hand. This value
changes at most twice a year, at the end of June and at the end of
December; and ample advance notice, at least six months' notice
It is your thread, and I have no wish to hijack it. This will
therefore be my last post for it.
I chose Australian local times advisedly. They illustrate the
differences between Daylight|Summer|Official times and Standard ones
in the northern and southern hemispheres.
You mentioned that you
Subject: Re: timezone_name?
It is your thread, and I have no wish to hijack it. This will therefore be
my last post for it.
I chose Australian local times advisedly. They illustrate the differences
between Daylight|Summer|Official times and Standard ones in the northern and
southern hemispheres.
You
Charles Mills wrote:
But I'm not processing the name portions of the TZ string. I'm not going
EDT! Aha! I know what that means... Here's the problem I am trying to solve:
What goes in timezone_name?
One possible solution: use a standard time zone, say Greenwich and base your
names on that
I haven't specifically looked, but IIRC, TZ can be specified as GMT plus/minus
offset
HTH,
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO
On Fri, 6 Sep 2013 15:38:05 +, Staller, Allan wrote:
I haven't specifically looked, but IIRC, TZ can be specified as GMT
plus/minus offset
Does the code then need to be changed semiannually?
-- gil
--
For IBM-MAIN
It can, but that was not the question. :-)
Charles
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of Staller, Allan
Sent: Friday, September 06, 2013 8:38 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: timezone_name?
I haven't
In the OMVS profile we set timezone like this:
TZ=CST6CDT5
-6 for Central Standard and -5 for Central Daylight.
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Charles Mills
Sent: Thursday, September 05, 2013 6:13 PM
To:
On Thu, 5 Sep 2013 16:13:07 -0700, Charles Mills wrote:
I'm looking at my C++ code. I wrote it, but I wrote it before I understood
as much (?) as I do now, and before GSK surprised me and made me run
POSIX(ON).
Background: the code runs on many different systems and customers set their
machines
On Fri, Sep 6, 2013 at 8:47 AM, Charles Mills charl...@mcn.org wrote:
I'm currently sticking the first three characters of TZ or a string such as
EST5EDT in timezone_name, and I know that's wrong. What *should* I be doing
instead?
Charles
You should use the portion in front of the offset
Mike Schwab's point is well made. Some of these values are
three-character ones, some of them are four-character ones, and
five-character ones are obviously in the womb of time. A parse that
deals swith this variability is, finally, trivial; but the issue
should not be ignored.
John Gilmore,
you get to a non-alpha character.
Charles
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of John Gilmore
Sent: Friday, September 06, 2013 7:01 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: timezone_name?
Mike Schwab's point is well made
If you are thinking in international rather than local American terms
some timezone names are problematic/ambiguous. An example. Australia
has three time zones:
o AEST, Australian Eastern Standard Time, which becomes AEDT,
Australian Eastern Daylight Time for part of the year, with
conventions
posts I
hate local time.
Charles
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of John Gilmore
Sent: Thursday, September 05, 2013 4:40 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: timezone_name?
If you are thinking in international
On Thu, 5 Sep 2013 16:13:07 -0700, Charles Mills wrote:
2. Does setting timezone_name to EST or PDT make sense? Is EST or PDT an
appropriate sort of setting?
To be POSIXly correct, you should follow:
Title: z/OS V1R13.0 XL C/C++ Programming Guide
Document Number: SC09-4765-12
8.4.1 Using the
22 matches
Mail list logo
