HP3000-L Archives

October 2000, Week 5

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:
"David N. Lukenbill" <[log in to unmask]>
Reply To:
Date:
Mon, 30 Oct 2000 11:13:39 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (81 lines)
Has anyone had any "wierd" experiences with their timezone change over the
weekend?  On my system, I streamed a job for Sunday at 2 AM.  The job
changed the time, paused 60 seconds, then re-streamed the same job for the
following Sunday (in case it's streamed on the wrong week).  What happened
is that the job checked the current date, then executed the setclock
command.  After pausing for 60 seconds, it re-streamed itself.  The 60
second pause should have caused the job to re-stream itself the following
week, but it instead re-streamed itself the same week.

Shouldn't the "Pause 60" command have caused the time to be 2:01 AM, and
the job to re-stream the following week?  I thought processes on the system
would not see the gradual time change.  Am I having a "DUH" moment??

Snipets:

First job:

:COMMENT **********************************************
:COMMENT * Check for the last Sunday in October for a *
:COMMENT * change from EDT to EST, which is "setting  *
:COMMENT * the clock back one hour".                  *
:COMMENT **********************************************
:IF HPMonth=10 and HPDay=1 and HPDate>24 Then
*** EXPRESSION TRUE
:   SHOWCLOCK

SYSTEM TIME: SUN, OCT 29, 2000,  2:00:00 AM
CURRENT TIME CORRECTION:            0 SECONDS
TIME ZONE:    4 HOURS  0 MINUTES WESTERN HEMISPHERE

:   SETCLOCK TimeZone=W5:00

SYSTEM TIME: SUN, OCT 29, 2000,  2:00:01 AM
CURRENT TIME CORRECTION:        -3599 SECONDS
TIME ZONE:    5 HOURS  0 MINUTES WESTERN HEMISPHERE

:   SHOWCLOCK

SYSTEM TIME: SUN, OCT 29, 2000,  2:00:01 AM
CURRENT TIME CORRECTION:        -3599 SECONDS
TIME ZONE:    5 HOURS  0 MINUTES WESTERN HEMISPHERE

:   TELLOP NOTE: The system clock is being changed to
:   TELLOP       eastern standard time.  The clock will
:   TELLOP       slow down until it has fallen back one
:   TELLOP       hour.
:ENDIF
:COMMENT ****************************
:COMMENT * Re-stream this same job. *
:COMMENT ****************************
:PAUSE 60
:STREAMX TimeZone.Job.System;Day=Sunday;At=02:00
 #J8609
:COMMENT ***************
:COMMENT * End of job. *
:COMMENT ***************
:EOJ
CPU sec. = 1.  elapsed min. = 1.  SUN, OCT 29, 2000,  2:00 AM.  <<<<<<< Note the time.



When the job re-streamed:

:COMMENT **********************************************
:COMMENT * Check for the last Sunday in October for a *
:COMMENT * change from EDT to EST, which is "setting  *
:COMMENT * the clock back one hour".                  *
:COMMENT **********************************************
:IF HPMonth=10 and HPDay=1 and HPDate>24 Then
*** EXPRESSION TRUE
:   SHOWCLOCK

SYSTEM TIME: SUN, OCT 29, 2000,  2:00:31 AM     <<<<<<<<<<<<<<< Note the time.
CURRENT TIME CORRECTION:        -3568 SECONDS
TIME ZONE:    5 HOURS  0 MINUTES WESTERN HEMISPHERE

:   SETCLOCK TimeZone=W5:00
A current correction is in effect.  Use SETCLOCK;CANCEL. (CIERR 11718)
REMAINDER OF JOB FLUSHED.
CPU sec. = 1.  elapsed min. = 1.  SUN, OCT 29, 2000,  2:00 AM.

ATOM RSS1 RSS2