RE: Robot Schedule failed across daylight savings time change

Buck,

Very interesting comments.

What version of Robot Schedule are you running?
I'm on R12M131170915.

Also, this is simply the I version, not the "Enterprise" version.

Paul


-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Buck Calabro
Sent: Wednesday, March 14, 2018 9:53 AM
To: midrange-l@xxxxxxxxxxxx
Subject: Re: Robot Schedule failed across daylight savings time change

On 3/13/2018 5:22 PM, John Yeung wrote:

On Tue, Mar 13, 2018 at 3:53 PM, Lindstrom, Scott R.
<Scott.Lindstrom@xxxxxxxxxxxxxx> wrote:

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."

His point was that Robot stopped worked *at some point* and had to be
recycled to "snap out of it".

We run Robot Schedule here, and have done for a long time - way more than ten years.
We have no jobs scheduled for 0200 through 0300.
We have never taken Schedule down around the time change.
We have never seen Schedule lock up / fail to run jobs after a time change.

--
--buck

http://wiki.midrange.com
Your updates make it better!

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link: http://amzn.to/2dEadiD