Lucas Rosalen wrote:
Mike is right.
At 2:01 you've added 3600s (to make it 3:01), so JES2 tried to catch up as
the interval had already been more than satisfied.
Indeed and this is documented,
quote
If, at 1:15 a.m., the clock is set ahead two hours, making the current time
3:15 a.m., the
Mike is right.
At 2:01 you've added 3600s (to make it 3:01), so JES2 tried to catch up
as the interval had already been more than satisfied.
This reminds me of our last fallback timechange when one of the techies
issued a JES2 command to schedule the SET CLOCK before midnight. JES2 tried
to catch
I would say it ran at 0145 xST. At 0301 xDT, the 1 hour had elapsed,
so it ran it immediately.
On Tue, Mar 10, 2015 at 3:51 PM, J O Skip Robinson
jo.skip.robin...@sce.com wrote:
I'm 90% sure of the answer but would like confirmation. We have a JES2
automatic command that's executes once an
I'm 90% sure of the answer but would like confirmation. We have a JES2
automatic command that's executes once an hour (T=3600) with no specific start
time. Before the Sunday Daylight Saving Time switch, this command was executing
at 45 minutes past the hour. Immediately after the time switch,
On Tue, 10 Mar 2015 21:53:46 +, Pommier, Rex wrote:
I don't know if I would infer that JES2 resyncs to the top of the hour. I
would infer that JES2 simply restarted its 3600 second timer at the point of
time the time changed. I would guess that if, for example, at 5:35 PM you
changed
start
faithfully executing every hour at 36 minutes after the hour.
Rex
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of J O Skip Robinson
Sent: Tuesday, March 10, 2015 3:51 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Time change effect
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Time change effect on JES2 AUTO commands
I don't know if I would infer that JES2 resyncs to the top of the hour. I
would infer that JES2 simply restarted its 3600 second timer at the point of
time the time changed. I would guess that if, for example
