This was a misstatement: I change the SETVAR TZ to "PST8PST" and "PST8PDT" for Pacific Standard Time and Pacific Daylight Time, respectively.
It was the :SETCLOCK TIMEZONE=W7:00 or W8:00 that we have to do for sure.

I take the opportunity to "clear things out", restarting the HP.
This helps eliminate questions about when jobs start and end, particularly those like Apache, VESOFT's Scheduler, JINETD, and several other things which might run months at a time without interruption.

It just seems to me that we had some trouble with NSD's Job Rescue if I didn't change the "PST8PxT".
I think they would start the log rollover an hour different from what we expected if I didn't, but I could be wrong and I think the times could be off for several other third party packages.

___________________________________________________________________________________________

>>> Walter Murray <[log in to unmask]> 03/29 4:02 PM >>>
"Doug Becker" <[log in to unmask]> wrote in message
news:99tpim01lc@enews3.newsguy.com...

[snip]
>  ... and change our LOGINIT file with a SETVAR TZ "PST7PST", referenced by
a logon UDC, ...

I don't know why you would need to change the TZ variable.  If you are in
California, for example, your TZ variable should be "PST8PDT" year-round.
The functions that use TZ will know to "spring forward" this Sunday.  You
might be making this more complicated than it really is.

Walter Murray
Hewlett-Packard
ESSO R&D
C/iX Library project