Text item: Body.822
I have been thru a couple of time changes and seen a very small error.  We
have some unix boxes which backup daily with a small window (1 hour)
schedule.  Here is the scenario;  the clients get a 'next backup time' at 5
am saturday.  At 2 am sunday the unix system jumps the clock to 3 am.  The
server, on MVS, doesn't jump ahead; it must wait for an ipl later.  When
the client starts the backup, say at 10 minutes into the window, the server
thinks it is 50 minutes before the window so strange messages are generated
at the client, and a scheduled backup is missed.  (This scenario happens in
the fall too, with different messages).

As I said, it is a small problem, and I am going to ignore it now that I
understand it.
_________________________Reply Header_________________________
Author: ADSM-L AT vm.marist DOT edu
Subject: TIME CHANGE CONCERNS.....?
04-05-96 01:43 PM

Date:         Fri, 5 Apr 1996 13:43:35 -0600
From:         Dwight Cook <decook AT amoco DOT com>
Subject:      TIME CHANGE CONCERNS.....?
To:           Multiple recipients of list ADSM-L <ADSM-L AT vm.marist DOT edu>

Item Subject: Text_1
     Any one know how ADSM is going to deal with the time change...
     I guess since we are "Springing forward" we won't have duplicates try
     to kick off but what if through staggered scheduling there is a backup
     window that runs from 15 to 45 min past the hour that will be skipped?
     In all of actuality I don't suffer from that here but would toss it
     out as food for thought.... We are running on RS/6000 w/ AIX 4.1 and
     have been told it automatically adjusts the system clock.

     I can't think of anyway this time change would cause major problems
     but I have this gut feeling that I'm just not hearing the wind whistle
     or noticing the growing shadow caused by the 2 ton safe that is
     falling my way.

     Just thinking out loud mainly
     Dwight