By some of these answers, one can easily tell who the old timers here are.
:-)
Paul Nelson
Cell 708-670-6978
Office 409-267-4027
nelsonp@xxxxxxxxxxxxx
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Lindstrom, Scott R.
Sent: Tuesday, March 13, 2018 3:16 PM
To: Midrange Systems Technical Discussion
Subject: RE: Robot Schedule failed across daylight savings time change
So it's down for a couple minutes before and after. Doesn't that eliminate
all the ambiguity about how to run jobs scheduled for 02:00?
A side note - I never schedule jobs on any on the OS'es I support at exactly
midnight; I do 23:59 or 00:01 instead. It eliminates the ambiguity about
when jobs is supposed to run. (ie, the conversation with the user "did you
mean midnight Wednesday or midnight Thursday"?)
Scott
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Justin Taylor
Sent: Tuesday, March 13, 2018 2:59 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: RE: Robot Schedule failed across daylight savings time change
Here's a snippet from this discussion:
"HelpSystems has always said to take SCHEDUEL down before the time changed
and not bring it back up until after."
-----Original Message-----
From: Lindstrom, Scott R. [mailto:Scott.Lindstrom@xxxxxxxxxxxxxx]
Sent: Tuesday, March 13, 2018 2:54 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: RE: Robot Schedule failed across daylight savings time change
I am not sure how ROBOT/Scheduler is not supporting DST.
The original poster had this problem which no one else has come forward and
said they have:
"Robot jobs failed to start at 3:45 am and 4:00 am."
Scott
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Justin Taylor
Sent: Tuesday, March 13, 2018 2:19 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: RE: Robot Schedule failed across daylight savings time change
As an outsider here, I am shocked that a commercial task scheduling package
can't support DST.
-----Original Message-----
From: Rob Berendt [mailto:rob@xxxxxxxxx]
Sent: Tuesday, March 13, 2018 12:03 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: Re: Robot Schedule failed across daylight savings time change
The OS, and IBM's job scheduler, were. Not so sure about ROBOT's scheduler.
Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600 Mail
to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
https://urldefense.proofpoint.com/v2/url?u=http-3A__www.dekko.com&d=DwICAg&c
=_2JymsjkoSdpgdT4DmA4bg&r=-518Ilz5cVhEAzb0mENLKbaCPCUJ_jWIaTTDYAFSng4&m=0hfd
6CNE-IVNGvk05aQSpIn0X4fp7OCHjrTK54b8pog&s=lQlA-zLCeg6qymUIvs2I0QlA3TtP3h4DTh
P-rqs90s8&e=
From: Roger Harman <roger.harman@xxxxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 03/13/2018 12:42 PM
Subject: Re: Robot Schedule failed across daylight savings time
change
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>
That is exactly what I used to do with AJS at a previous employer. Just
peace of mind. Fortunately, we had a big enough window to allow it.
Others don't have that luxury.
I'm a bit surprised at all these DST issues. Wasn't the OS changed some
time ago to do a clock slowdown or speedup to compensate and not do a flat
jump to new time?
Roger Harman
COMMON Certified Application Developer - ILE RPG on IBM i on Power
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxx> on behalf of Jeff
Crosby <jlcrosby@xxxxxxxxxxxxxxxx>
Sent: Tuesday, March 13, 2018 5:49 AM
To: Midrange Systems Technical Discussion
Subject: Re: Robot Schedule failed across daylight savings time change
Don't use Robot Schedule, so I know nothing about it. We're using AJS
(Advanced Job Scheduler) which has no issues with DST. So it can be done.
That being said, I never schedule jobs on AJS from 2am-3am. It's always
either 1:59am or 3:01am. Not because AJS can't do it, it's for MY peace
of
mind.
On Tue, Mar 13, 2018 at 8:45 AM, Steinmetz, Paul <PSteinmetz@xxxxxxxxxx>
wrote:
I'm not understanding why Robot Schedule needs to be recycled.
It must not be checking the system time, but using their own internal
clock.
Support sent me this link, illustrating a new feature for daylight
savings
time they just added in 12.13 or higher , available in the GUI only.
https://urldefense.proofpoint.com/v2/url?u=https-3A__www.helpsystems.com_how
-2Dto-2Dguides_robot_using-2D&d=DwICAg&c=_2JymsjkoSdpgdT4DmA4bg&r=-518Ilz5cV
hEAzb0mENLKbaCPCUJ_jWIaTTDYAFSng4&m=0hfd6CNE-IVNGvk05aQSpIn0X4fp7OCHjrTK54b8
pog&s=zRuVeuO-Ln2f3D-IDJUH6PeHPh0XDvE3pEGg8FgCssM&e=
robot-schedule-automate-daylight-saving-time-change
Paul
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Lindstrom, Scott R.
Sent: Monday, March 12, 2018 2:10 PM
To: Midrange Systems Technical Discussion
Subject: RE: Robot Schedule failed across daylight savings time change
To the original question; I have never seen Robot have problems after
the
time change.
Like Jerry - we have automated our shutdown/restart of Robot Schedule
during the time change.
For "Spring Ahead" We have a job that run *every* second Sunday of the
month at 01:58. It then has an OPAL object attached that skips the job
if
it's NOT March:
Execute schedule instructions in OPAL Object CHGTIME_S
@@MONNO NE 03
SKIP
END
If the job DOES run, it:
shuts down Robot
waits 4 minutes
starts up robot
sends me an email that it ran
submits a job to run at 0900 to text me and say 'the time is now 0900'.
When I get this text I make sure it actually is 9 am.
Scott
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Jerry Draper
Sent: Monday, March 12, 2018 12:41 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: Re: Robot Schedule failed across daylight savings time change
We use Robot extensively at several sites.
We have a job scheduled in Robot to end Robot Schedule at 1:58am and
restart it at 2:02am. It then puts itself on hold for next DST change.
This job is scheduled for Sundays. Normally it is on hold. We release
it
sometime during the week before DST although that could be put on a
calendar so you can spend more time loafing.
Jerry
Commands for job . . . : CHGDST
Opt Seq Command
1 CALL PGM(ROBOTLIB/RBT107)
2 DLYJOB DLY(240)
3 CALL PGM(ROBOTLIB/RBT103)
4 ROBOTLIB/RBTBCHUPD JOBNUMBER(2029) SCHEDULE(H)
On 3/12/2018 7:01 AM, Steinmetz, Paul wrote:
We just started using Robot Schedule / Robot Replay the last several
months.
This was our first experience of a daylight savings time change with
the
product.
System time auto changed from 2:00 am to 3:00 am on 3/11.
Robot jobs failed to start at 3:45 am and 4:00 am.
Recycling Robot Schedule resolved the issue.
Anyone from the group using these products and experiencing similar
issue?
----------------------------------------------------------------------
DISCLAIMER: This electronic message together with any attachments is
confidential. If you are not the intended recipient, do not copy, disclose
or use the contents in any way. Please also advise us by return e-mail that
you have received the message and then please destroy. The sender is not
responsible for any changes made to this message and / or any attachments
after the message and attachments are initial sent. We use virus scanning
software but exclude all liability for viruses or anything similar in this
email or any attachment.
RLSAutogeneratedDisclaimer
midrange.com
