SETCLOCK

or

:SETCLOCK CORRECTION= 3600

Both of the abo ve examples cause Univ ersal Time (GMT) to c hange as well as local time, and therefore while they are useful in correcting the system time for drift (time gain or loss), they are not accurate w ays to change time zones.

The following example illustrates setting a time correction, executing a :SHOWCLOCK command, cancelling the correction, then again executing a :SHOWCLOCK command. Note that b y the time of the ￿rst :SHO WCLOCK the correction has already begun to be consumed.

:SETCLOCK CORRECTION= -3600

:SHOWCLOCK

SYSTEM TIME: FRI, JUL 24, 1987, 8:47:35 AM

CURRENT TIME CORRECTION: -3568 SECONDS

TIME ZONE: 7 HOURS 0 MINUTES WESTERN HEMISPHERE

:SETCLOCK; CANCEL

CORRECTION OF -3550 SECONDS HAS BEEN CANCELLED

:SHOWCLOCK

SYSTEM TIME: FRI, JUL 24, 1987, 8:52:53 AM

CURRENT TIME CORRECTION: 0 SECONDS

TIME ZONE: 7 HOURS 0 MINUTES WESTERN HEMISPHERE

Note that in the example abo ve the system cloc k was slower than normal for several minutes. Cancelling the correction did not undo that c hange; it merely prevented any further time change. Thus after this sequence of commands, the system cloc k is set to a slightly earlier time than if no :SETCLOCK command had been issued.

2-244 MPE/iX Commands