HP3000-L Archives

September 2008, 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:
John Pitman <[log in to unmask]>
Reply To:
John Pitman <[log in to unmask]>
Date:
Mon, 15 Sep 2008 11:32:44 +1000
Content-Type:
text/plain
Parts/Attachments:
text/plain (71 lines)
Further to this, and my recent problems with a remote system (date came up as Oct 2013), I thought I had it fixed, but now see this issue - Sept 15 calls to time() produce a date of Sep 14, but correct time of day for zone- China, GMT+8. Looking deeper in dbx, I see in the tm structure tm_isdst is TRUE, where in our local system in Oz (GMT+10) it is False.
I know the TZ looks wrong, but in every other respect it works. It seems to me that DST set should not give an error of 1 whole day? Also , why is the month in the tm struct off by 1 - it returns 8?
Anybody ?
tks
jp

RELEASE: C.75.00   MPE/iX HP31900 C.45.05   USER VERSION: C.75.00
:date
Mon Sep 15 08:53:23 E 2008
:showclock

SYSTEM TIME: MON, SEP 15, 2008,  8:55:55 AM
CURRENT TIME CORRECTION:            0 SECONDS
TIME ZONE:    8 HOURS  0 MINUTES EASTERN HEMISPHERE

:sl05.c
Date=14/09/2008   <<<<<<<<<<<<<<<<< C prog that calls time()
time=09:01:30


and


TZ = E-8:00

-----Original Message-----
From: HP-3000 Systems Discussion [mailto:[log in to unmask]] On Behalf Of Stan Sieler
Sent: Friday, 5 September 2008 6:28 AM
To: [log in to unmask]
Subject: Re: [HP3000-L] CPU Clock problem!!!

Hi,
> One of my customers called stating that whenever they shutdown the system,
> during the startup (right after issuing START NORECOVERY) the clock displays
> 1/1/1970 and asks if the time is correct... they would go ahead and reply 'N'
> and change the clock.
>
> After the system was up and they would do 'SYSDATE' it would show Internal
> clock correct, but the external clock would still say 1/1/1970... the only way
> we could correct this was via SETCLOCK;TIMEZONE=W7:00
>
>
> (Setclock with date and time;now would not correct the problem)
>
> Thinking that the battery is gone, I replaced their CPU battery, but they
> are still having the same problem.
> Is there something else that needs to be changed other then the battery or
> does it have to do with the CPU board?

Have you used the SETCLOCK utility (available from the ISL prompt)
or (availabilty depends upon hardware model:) the below-the-ISL command to
set the hardware clock?

Using one of the above two, set the hardware clock to GMT.

Then, boot MPE (being sure to watch for the date/time prompt to set it
to correct local time).

Stan Sieler

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

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

ATOM RSS1 RSS2