Am interested in knowing if most people still IPL for time change - spring
and
fall - and if anyone does not, how they handle this.
Thanks, Tom
We did something interesting, and had an interesting problem as a result.
Because of
data center consolidation we had mainframes in the same room running in
different time
zones. In years past, this caused confusion among operators, and various
systems got
set to various times on more than one occasion.
This problem was solved by writing automation that would, on operator
command, get the
current time, perform the proper arithmetic on the hour, and issue a set
clock command.
Which worked wonderfully, except...
For whatever reason, it took OPS/MVS about 2.6 seconds to do all this. So
the MVS clock
was actually set back by one hour and 2.6 seconds. This wouldn't matter
really, except...
It appears that OMVS works out the time of day at bring up, and just goes
from there.
So, in the end, various OMVS apps were getting to midnight about 2.6 seconds
before MVS.
Therefore, CRON ran, invoked a REXX exec to create a new HFS file for todays
FTP log,
REXX queried MVS for the time of day, decided it wasn't tomorrow yet, and we
got a sev 4
PMR because the FTP log was in yesterdays file.
I've recommended that the automation be changed to use set timezone, but
first there are
some management issues to be addressed.
For us at least, daylight savings time is not a technical issue, it is an
emotional issue.
The amount of meeting time spent to talk about all this is growing at an
exponential rate,
with no end in sight.
Lance
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
