In 023001d0b5d9$b8e488a0$2aad99e0$@mcn.org, on 07/03/2015
at 02:46 PM, Charles Mills charl...@mcn.org said:
Can a prisoner serving a 30-year sentence demand to be released 'n'
seconds early to account for the leap seconds of incarceration?
Can he be kept 'n' seconds late? How is the sentence
In my time zone, the leap second occurred at 17:59:60. So, I wonder
about the z/OS STIMER macro:
If, at 17:59:59 I had issued STIMER WAIT,LT=[18:000:01]
would the wait have expired in 3 seconds?
Yes, if you scheduled the leap second via STP or ETR.
It would expire in 2 seconds if
At 16:24 -0500 on 07/03/2015, Paul Gilmartin wrote about Re: Leap
Second today!:
Actually, you could have known that for 4 months, ever since the
IERS announced the leap second. (Less the time it takes for a
PTF to be created, distributed, and installed.)
Since the leap second can only
At 18:07 -0500 on 07/03/2015, Paul Gilmartin wrote about Re: Leap
Second today!:
On 2011-12-29 24:00:00, Independent Samoa advanced its clocks
by 24 hours, to 2011-12031 00:00:00. There was no December 30.
This was announced well in advance, and published in advance in
the IANA database
Also, the moons orbital distance increases by 4 cm a year, slowing the
earth. We will be adding leap seconds more often until in a few
thousand years our days will be 1 second longer.
On Sat, Jul 4, 2015 at 10:44 PM, Jim Carpenter j...@deitygraveyard.com wrote:
On Sat, Jul 4, 2015 at 2:25 PM,
On Sat, Jul 4, 2015 at 2:25 PM, Robert A. Rosenberg hal9...@panix.com wrote:
Since the leap second can only occur on June 30 or December 31, it is not
that hard to write the PTF and stockpile it.
As Mike has previously said, it is possible for a leap second to be
inserted on the last day of ANY
about?
Charles
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of Paul Gilmartin
Sent: Friday, July 03, 2015 2:24 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Leap Second today!
On Fri, 3 Jul 2015 15:33:37 -0500, George Kozakos wrote
On Fri, 3 Jul 2015 16:41:03 -0500, George Kozakos wrote:
Leap seconds are scheduled via STP or the sysplex timer.
z/OS can only know about a leap second when it gets the Time Control
Parameter Change event external interrupt for STP or the ETR Alert
event external interrupt for ETR.
Tunnel
@LISTSERV.UA.EDU
Subject: Re: Leap Second today!
On Fri, 3 Jul 2015 15:33:37 -0500, George Kozakos wrote:
So it actually waits for 4 seconds rather than the 3 requested.
The problem is that at 17:59:59 when the STIMER is processed we don't
know that a leap second will occur at 18:00.
Actually, you could
On Fri, 3 Jul 2015 14:42:31 -0500, George Kozakos wrote:
In my time zone, the leap second occurred at 17:59:60. So, I wonder
about the z/OS STIMER macro:
If, at 17:59:59 I had issued STIMER WAIT,LT=[18:000:01]
would the wait have expired in 3 seconds?
Yes, if you scheduled the leap
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Leap Second today!
In my time zone, the leap second occurred at 17:59:60. So, I wonder
about the z/OS STIMER macro:
If, at 17:59:59 I had issued STIMER WAIT,LT=[18:000:01]
would the wait have expired in 3 seconds?
Yes, if you scheduled the leap
MIDNITE DCCL8'0100' Midnight + 1 second 00:00:01.00
Charles
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Paul Gilmartin
Sent: Friday, July 03, 2015 1:00 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Leap Second today
Gilmartin
Sent: Friday, July 03, 2015 2:07 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Leap Second today!
On Fri, 3 Jul 2015 13:13:32 -0700, Charles Mills wrote:
the syntax of STIMER macro provides no way to specify a time past
midnight
Au contraire (assuming STIMER includes STIMERM). I issue
-MAIN@LISTSERV.UA.EDU] On Behalf
Of Jakubek, Jan
Sent: Friday, July 03, 2015 4:06 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Leap Second today!
I think leap second is magical.
All time measuring devices that respect it - stop for one second to observe it.
Do I have it right
and subtracting the leap second offset.
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Jakubek, Jan
Sent: Friday, July 03, 2015 6:52 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Leap Second today!
Replying to myself...likely I'm
If, at 17:59:59 I had issued STIMER WAIT,BINTVL=[3 seconds]
would the wait have expired at 18:00:01?
No, it would expire at 18:00:02 regardless of whether you are using
leap seconds
And since the Leap Second code is ignorant of whether an entry
corresponds to a clock time or a
So it actually waits for 4 seconds rather than the 3 requested.
The problem is that at 17:59:59 when the STIMER is processed we
don't know that a leap second will occur at 18:00.
Actually, you could have known that for 4 months, ever since the
IERS announced the leap second. (Less the
In my time zone, the leap second occurred at 17:59:60. So, I wonder
about the z/OS STIMER macro:
If, at 17:59:59 I had issued STIMER WAIT,LT=[18:000:01]
would the wait have expired in 3 seconds?
Yes, if you scheduled the leap second via STP or ETR.
It would expire in 2 seconds if you
On Fri, 3 Jul 2015 13:13:32 -0700, Charles Mills wrote:
the syntax of STIMER macro provides no way to specify a time past midnight
Au contraire (assuming STIMER includes STIMERM). I issue
STIMERM SET,LT=MIDNITE,EXIT=POP_MIDNITE,ID=ID_MIDNITE,+
, depending on what
day you are talking about?
Charles
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Paul Gilmartin
Sent: Friday, July 03, 2015 2:24 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Leap Second today!
On Fri, 3 Jul 2015
On Fri, 3 Jul 2015 15:33:37 -0500, George Kozakos wrote:
So it actually waits for 4 seconds rather than the 3 requested.
The problem is that at 17:59:59 when the STIMER is processed we
don't know that a leap second will occur at 18:00.
Actually, you could have known that for 4 months, ever
On Thu, 2 Jul 2015 00:30:16 -0400, Ed Finnell wrote:
On the red Hat page Linus Torvil tries to explain that much of the
application software was designed and built in an ERA(1999-2005) that had no
leap
seconds. 'It's always something' R. Rosanadan
??? The first (two?) leap seconds were in
[mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Paul Gilmartin
Sent: Friday, 3 July 2015 11:27 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Leap Second today!
On Thu, 2 Jul 2015 13:36:26 -0400, Ed Finnell wrote:
Yikes. Too much hasenpfeffer...
http://www.wired.com/2012/07/leap-second-glitch
On Thu, 2 Jul 2015 13:36:26 -0400, Ed Finnell wrote:
Yikes. Too much hasenpfeffer...
http://www.wired.com/2012/07/leap-second-glitch-explained/
In my time zone, the leap second occurred at 17:59:60. So, I wonder
about the z/OS STIMER macro:
If, at 17:59:59 I had issued STIMER
Yikes. Too much hasenpfeffer...
http://www.wired.com/2012/07/leap-second-glitch-explained/
In a message dated 7/2/2015 11:04:05 A.M. Central Daylight Time,
jayare...@hotmail.com writes:
Ah, yes, Torvil! Quite the ice dancer in her day, too.
On the red Hat page Linus Torvil ...
Ah, yes, Torvil! Quite the ice dancer in her day, too.
===
Date: Thu, 2 Jul 2015 00:30:16 -0400
From: 000248cce9f3-dmarc-requ...@listserv.ua.edu
Subject: Re: Leap Second today!
To: IBM-MAIN@LISTSERV.UA.EDU
On the red Hat page Linus
Jon Butler wrote:
Personally, I appreciated the extra sleep. ;-))
Let see, I had to decide what to do with that extra second: running another
job, eat more, sleep more, bitching with someone... play more... etc...
Hmmm, but I could not do that... because I wasted that precious second trying
Personally, I appreciated the extra sleep. ;-))
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Jousma, David
Sent: 30 June, 2015 20:35
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Leap Second today!
Is this going to be the next Y2K? In the eastern part of the US, that's
19:59:60 this evening
sigh/You Earthers! Just for for TAI. You have nothing to lose but your
Earth-centric chains! Note: offer does not extend to users travelling at
relativistic speeds or in high gravity environments, such as on a Neutron
star.
On Jul 1, 2015 23:30, Ed Finnell
The people most concerned were (automated) equity traders. Bloomberg reports
1.4 million trades per second. And, of course, they only count (continental)
USA.
That's a lot of capital that can go missing. And it was a trading day, not like
2012.
Different parts of the world managed this
On the red Hat page Linus Torvil tries to explain that much of the
application software was designed and built in an ERA(1999-2005) that had no
leap
seconds. 'It's always something' R. Rosanadan
In a message dated 7/1/2015 10:52:03 P.M. Central Daylight Time,
hal9...@panix.com writes:
On Wed, Jul 1, 2015 at 10:50 PM, Robert A. Rosenberg hal9...@panix.com wrote:
At 11:40 + on 07/01/2015, Vernooij, CP (ITOPT1) - KLM wrote about Re:
Leap Second today!:
One of the particular appearances of the problem was, that the software
could not cope with the 60th second presented
http://money.cnn.com/2015/06/30/technology/leap-second/
In a message dated 7/2/2015 12:20:52 A.M. Central Daylight Time,
ibm-m...@tpg.com.au writes:
The people most concerned were (automated) equity traders. Bloomberg
reports 1.4 million trades per second. And, of course, they only count
At 11:40 + on 07/01/2015, Vernooij, CP (ITOPT1) - KLM wrote about
Re: Leap Second today!:
One of the particular appearances of the problem was, that the
software could not cope with the 60th second presented by time
servers in the last minute of the day.
These program are IMO BAD
On 7/1/2015 at 12:34 AM, Peter dbajava...@gmail.com wrote:
What actually those fixes do ? Automatically corrects the time ?
Handles them in a way that won't upset any user space applications. Beyond
that, I would direct you to the source, as I'm not that familiar with them to
comment
Hi Mark
What actually those fixes do ? Automatically corrects the time ?
Peter
On 1 Jul 2015 01:36, Mark Post mp...@suse.com wrote:
On 6/30/2015 at 03:24 PM, Andre Massena andre_mass...@lavache.com
wrote:
European precision perhaps - no reports of zLinux SuSe being affected,
Well, we're
Is this going to be the next Y2K? In the eastern part of the US, that's
19:59:60 this evening.
_
Dave Jousma
Assistant Vice President, Mainframe Engineering
david.jou...@53.com
1830 East Paris, Grand Rapids, MI 49546 MD RSCB2H
p
European precision perhaps - no reports of zLinux SuSe being affected,
Andre
Message d'origine
De : Ed Finnell 000248cce9f3-dmarc-requ...@listserv.ua.edu
À : IBM-MAIN@LISTSERV.UA.EDU
Objet : Re: Leap Second today!
Date : 30/06/2015 21:05:13 CEST
If you're just now researching
On 6/30/2015 at 03:24 PM, Andre Massena andre_mass...@lavache.com wrote:
European precision perhaps - no reports of zLinux SuSe being affected,
Well, we're affected but the fixes to avoid the problem have been available
for a while now. I'm pretty (nearly absolutely) sure the case is the
But who is to leap first so I will know when to leap?
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
If you're just now researching this it may be too late. It does affect Red
Hat Linux and a few others.
Last time it was added it knocked several 'high profile' sites offline.
In a message dated 6/30/2015 1:35:32 P.M. Central Daylight Time,
david.jou...@53.com writes:
next Y2K? In the
Second adjustments are the last second of a month UTC (corrected GMT),
regardless of time zone. So far they have been the last second of
December and June.
On Tue, Jun 30, 2015 at 3:03 PM, Steve Thompson ste...@copper.net wrote:
But who is to leap first so I will know when to leap?
43 matches
Mail list logo
