HP3000-L Archives

July 1995, 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:
Brian Abernathy <[log in to unmask]>
Reply To:
Brian Abernathy <[log in to unmask]>
Date:
Mon, 10 Jul 1995 14:26:23 GMT
Content-Type:
text/plain
Parts/Attachments:
text/plain (38 lines)
Jeff Woods ([log in to unmask]) wrote:
 
: My guess is that the hardware clock and the software clock have a *very*
: large relative offset.  Use the :SHOWCLOCK command on the customer's
: system.  The TIME ZONE offset is the difference used by MPE between the
: two.  I have seen situations where the hardware clock is way off but the
: software clock was reasonably close to correct.  The TIME ZONE field
: showed 5 digit hours.
 
 
The POST85 functions, which include the FUNCTION CURRENT-DATE, follow the
TZ environment variable, just like the ctime functions do.  Consider the
following snippet of code:
 
   MOVE FUNCTION CURRENT-DATE TO CUR-DTE.
   DISPLAY "CURRENT DATE: " CUR-DTE.
   STOP RUN.
 
Now, when run, the result is:
 
CURRENT DATE: 1995071010214200-0400
 
Setting the TZ environment variable to PST8PDT gives the result:
 
CURRENT DATE: 1995071007225700-0700
 
If TZ is not defined, then the code will default to EST5EDT.
 
 
 ______________________________________________________________________________
 
   Humanoid creatures who abide in a    |       Brian Abernathy
   vitreous structure should never      |       Hewlett-Packard Company
   attempt to apply kinetic force to    |       Atlanta Response Center
   a petrous formation.                 |       Internet: [log in to unmask]
                                        |       CIS:  70223,167
 ______________________________________________________________________________

ATOM RSS1 RSS2