see the archives of hp3000-L keyword Daylight - we've been over this a few
times!  but here's a job I run EVERY sunday that takes care of it quite
nicely.  we have a scheduler (MBQ) to do this, but you could just have it
stream itself and let the spooler take care of the timing.

!job clockjob,manager.sys,pub;outclass=lp,1;pri=cs
!
!comment This runs every Sunday at 2am. KTP 991018
!comment BEWARE: GGB's SETCLOCK is subverted via System UDC.
!
!comment ***************************** NORMAL PST-to-PDT & back...
!comment if it's the proper day, change system clock to proper choice of
!comment PACIFIC STANDARD TIME or PACIFIC DAYLIGHT TIME...
!
!if ( hpday = 1 and hpmonth = 4 and hpdate <= 7 ) &
!or ( hpday = 1 and hpmonth = 10 and hpdate >= 25 )
!  showtime
!  set stdlist = save
!  if ( hpmonth = 4 and hpdate <= 7 )
!    comment first sunday in april, switch to PDT, = GMT - 7
!    continue
!    setclock "timezone=w7:00"
!  endif
!  if hpday = 1 and hpmonth = 10 and hpdate >= 25
!    comment last sunday in october; switch to PST, = GMT - 8
!    continue
!    setclock "timezone=w8:00"
!  endif
(24/33) Continue?
!  while hphour < 3 do
!    comment this pause cycle actually slows down the reset, but
!    comment it's interesting to watch, so so sorry about the cpu.
!    pause 300
!    showtime
!  endwhile
!else
!  set stdlist = delete
!endif
!eoj



and here's the GGB subversion of setclock, actually just a passthru but with
some other goodies thrown in...
YODA:MANAGER.SYS,PUB:help setclock
User-defined command:

SETCLOCK ANYPARM=" "
OPTION LIST
comment SETCLOCK is in SYSUDCxx, which in turn invokes MPE/ix SETCLOCK.
comment
comment To use it, you must be "GOD"(.pub.vesoft) or SM & OP maybe
comment     (for both the cross-account COPY and the
comment       'master operator' requirement of SETCLOCK.)
comment
comment This is to ensure that when SETCLOCK is used, the BETASYS
comment clock tracking mechanism is kept in forward motion by always
comment replacing it with a 'virgin' version, capable of operation
comment through 12/31/2027 (clock intrinsic limit).
comment
comment Note that the BETASYS instructions say "make a backup every
comment time you change your clock for testing"; what we're really
comment doing here is installing the 'new' file everytime, which
comment contains a last-run date of 1/21/99.
comment (if this gets goofed up, there's another copy in LEARN.)
comment
comment For SETCLOCK help, invoke MPE HELP, then type SETCLOCK.
comment
comment REMEMBER to do MBQ SHUTDOWN when setting date forward for testing!
comment
comment NOTE setclock's parms must be entirely in quotes, as in
comment   SETCLOCK "DATE=1/1/2000;TIME=8:05;NOW"
CONTINUE
SETCLOCK !ANYPARM
CONTINUE
PURGE FKERRHLP.DATA.BETASYS
CONTINUE
COPY FKERRHLX.DATA.BETASYS,FKERRHLP.DATA.BETASYS

> -----Original Message-----
> From: Stuart Diamond [mailto:[log in to unmask]]
> Sent: Thursday, April 01, 2004 9:19 AM
> To: [log in to unmask]
> Subject: Daylight Savings Time
>
>
> Can=20someone=20remind=20me=20the=20command=20I=20need=20to=20
> run=20to=20c=
> hange=20the=20time=20for=20Daylight=20savings=20time,=20withou
> t=20bouncing=
> =20the=20box.
> =20
> I=20am=20on=20an=20HP989/650=20running=20MPE=20version=205.5
> =20
> Stu=20Diamond
> HP=20Systems=20Manager
> Hours:=20=20Tues-Thurs=2010:15=20AM=20-=209:00=20PM
> =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20Friday=20=20=2
> 0=20=20=20=20=
> =20=20=20=20=20=206:00=20AM=20-=203:30=20PM=20
> =20
> Phone:=20=20=20=201=20631=20738-5521
> Beeper:=20=201=20877=20409-1239
> =20
> Symbol.=20The=20Enterprise=20Mobility=20Company.=20(TM)
>
>
>
> ______________________________________________________________
> __________
> This=20email=20has=20been=20scanned=20for=20computer=20viruses.
>
> * 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 *