Shawn Gordon wrote:
>
> No it won't.  You need to use SETCLOCK to fix it, but that's only if you have
> the clock correct to begin with.  What I will be doing on Sunday since I am on
> the left coast is SETCLOCK TIMEZONE=W7:00
>
> This takes anywhere from an hour to a really long time depending on if it is
> already set or not.


Okay, I know about SETCLOCK... But what about the system-wide TZ
variable?  Ours is currently set to "CST6CDT" -- do we need to change
that to "CDT5" or leave it alone or what???  And if we do need to change
it, is there any way to do so other than in a system-wide logon udc (we
have 5.0 and 5.5 boxes)?

Patrick, who *thought* he was ready for the weekend until about 5 min
ago.

P.S. Thanks for the JCL, Frank (and thank Michael for me, too)!
--
Patrick Santucci
Technical Services Systems Programmer
Kirke-Van Orsdel, Inc.
mailto:[log in to unmask]
Visit our site! http://www.kvi-ins.com
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
"MPE - To the Millenium and Beyond!!"  - Buzz Oughtyear