> 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, +
ERRET=ERR_MIDNITE,PARM=AWORKAR,MF=(E,STIMERML_SET)
all the time, where
MIDNITE DC CL8'00000100' Midnight + 1 second 00:00:01.00
Charles
-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf
Of Paul Gilmartin
Sent: Friday, July 03, 2015 1:00 PM
To: [email protected]
Subject: Re: Leap Second today!
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 second via STP or ETR.
>It would expire in 2 seconds if you aren't using leap seconds
>
OK. I imagine that there's a queue of Clock Comparator Register values, and
that Leap Second processing scans that queue and adds one second to each value.
>> 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 duration, it assumes the former and adds the second regardless.
Particularly silly if the wait spans midnight since the syntax of STIMER macro
provides no way to specify a time past midnight, so it must have been a
duration.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
