My client experienced a problem that we can't explain, but we suspect it may
have something to do with the time zone change.  That's just because the
time zone change seems to be the most significant thing happening today.

The System Manager changed the time with SETCLOCK on Saturday evening,
about 10:30 PM, because that is the quietest time.  The EXPRESS job
scheduler kicks off all sorts of weekend processing shortly after midnight,
early Sunday morning.  Well, things kicked off, all right, way too many times.
Jobs logged and ran multiple times, filling up files that should not
logically
fill up.  The files that filled up, at least those I looked at, were data
extractions,
and it seemed as though date selections were done as though everything
that was selected by date qualified.  It almost seemed as though the programs
were getting the wrong system date.  We decided that we could not possibly
analyze and correct all the messed-up in time to run weekly MRP and other
jobs in time for Monday morning, so we elected to restore all production from
the Saturday evening backup and then see if we can figure out the problem.
The restore is running right now.  The production machine with the problem
is a 969-220 running 7.0, PP1.  The N-class machine is currently the test and
development machine, and it does not appear to have any problem, but then
the job scheduler is not running there.

I know this is not enough information to identify our problem, but we did not
feel we have the time available to do anything other than restore the data.
I'm just wondering if anyone else is having any problems related to the time
change.

Cecile Chi

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *