HP3000-L Archives

June 1998, 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:
"Bleazard, John" <[log in to unmask]>
Reply To:
Bleazard, John
Date:
Thu, 11 Jun 1998 13:55:52 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (26 lines)
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

ATOM RSS1 RSS2