You actually have two steps, neither of which require rebooting the
     system.  You have to do a SETVAR TZ,"CST6CDT" and then you will need
     to issue the following command;

        SETCLOCK TIMEZONE = W5:00

     Come late October you will need to issue;

        SETCLOCK TIMEZONE = W6:00

     Your value for TZ can and should remain the same.  The setclock
     command for TIMEZONE can take anywhere from seconds to many hours to
     correct.  If you want you can issue SETCLOCK;CANCEL.  For adjusting
     TIMEZONE this appears to have the affect of using NOW as opposed to
     GRADUAL.  The NOW and GRADUAL options are not available when adjusting
     TIMEZONE, only when adjusting the clock.

     I imagine with 333 hours in your timezone, if you set TZ you should
     get some pretty wild results.

     Hope that helps.

     Shawn Gordon
     SMGA
     www.smga3000.com


______________________________ Reply Separator _________________________________
Subject: SHOWCLOCK and Function CURRENT-DATE
Author:  [log in to unmask] at Internet-Mail
Date:    6/11/98 11:55 AM


Thanks for the replies.  This all sounds vaguely familiar.  We are a
very small HP3000 shop and don't have a real system administrator.
Kansas is in the Central Time Zone, most of it is.

Here's what I got with SHOWCLOCK:

SYSTEM TIME: THU, JUN 11, 1998,  1:47:41 PM
CURRENT TIME CORRECTION:            0 SECONDS
TIME ZONE:  333 HOURS  0 MINUTES EASTERN HEMISPHERE

It looks bad, huh?  I am just a lowly applications programmer, and a
contractor to boot, so I will have turn this info over to the client.

From what Shawn Gordon writes, it appears TIMEZONE needs to be set when
they boot the system, or I can SETVAR TZ in a logon UDC.

If I go this latter route, I assume I am not changing anything at the
system level, rather just for the current session.  Is that correct?

Thanks again to all who reply.

John Bleazard
Boeing Computer Services
Wichita, KS
(316)526-2365