HP3000-L Archives

November 1999, Week 2

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Stan Sieler <[log in to unmask]>
Reply To:
Stan Sieler <[log in to unmask]>
Date:
Thu, 11 Nov 1999 09:39:21 -0800
Content-Type:
text/plain
Parts/Attachments:
text/plain (76 lines)
Hi Ceil,

> Does anyone out there have the instructions for correctly setting the
> hardware clock on the HP3000?? Just need to make sure that we get it
> correct!  Thank you in advance!

If no one answered you...

there are two basic methods you can use:

  1) (without reboot)

     a) make sure your system time zone is correct:

          :showclks.pubxl.telesup

        look for:

           GMT/MPE offset      : -8:00:00

        (We're in PST, so 8 hours before GMT is correct for us)

     b) if the system time zone is wrong, change it:

          :setclock timezone=w4:00      (example for EST time)
          :setclock ;cancel

     c) set the correct time (particularly necessary if (b) was done):

          :setclock 11/15/99;time=12:23; now

     d) verify result:

          :showclks.pubxl.telesup

        Be sure to check that both the GMT date/time is correct and
        the local system time is correct.

        BTW, the SHOWCLKS output line of:
              CTIME function return :  Thu Nov 11 13:30:17 1999
        will probably show the wrong time if you don't have the
        TZ variable setup correctly.

   Note: the above may cause some processes to see a strange "bump" in
   the date/time (i.e., they might have checked the date before you
   started the process and again after you're done, and seen something
   odd).  Although we might ameliorate this for step (c), we can't
   ameliorate the step (b) affects, so I chose to do the ";now" on
   step (c).  The alternative (reboot) method doesn't have this
   (usually minor) problem.

or:

   2) (at next reboot)

     a) at the ISL prompt, *don't* type START

     b) type:  CLKUTIL

     c) set the clock via the "s" command

        ...set it to *GMT* date/time...that's important, not local time!

     d) verify via the "r" command

     e) exit CLKUTIL (<cr>, I think)

     f) START   (with or without NORECOVERY, as you wish)

     g) during startup dialog, enter the correct MPE system time (local time).


--
Stan Sieler                                           [log in to unmask]
www.allegro.com/sieler/wanted/index.html          www.allegro.com/sieler

ATOM RSS1 RSS2