SETCLOCK

requests, ￿le accesses and frequen t operating system activity suc h as context switches.

Results of the ;CANCEL P arameter

Any time during an on-going correction, issuing this command with the ;CANCEL parameter will immediately set the correction to zero and cause the system cloc k to resume its normal pace. An y previous correction will remain. When this option is used, the system will report the amoun t of correction which was cancelled.

How a System Time Change A￿ects Accoun ting Information

Changing the system time, ev en gradually, may cause accounting CONNECT-MINUTES to be distorted. An yone logging on before the c hange and then logging o￿ after the c hange is completed will ha ve their accounting CONNECT-MINUTES data distorted; if the time c hange is forward, CONNECT-MINUTES will be increased b y the amount of the time change, and if the time c hange is backward, CONNECT-MINUTES will be decreased by the amount of the time change.

Dangers in Using the ;NO W Parameter

The ;NOW parameter permits immediate forward or bac kward time changes. However, several dangerous situations can occur:

Any applications whic h rely on the forward progression of time ma y give inconsistent results if the time is immediately set bac kwards. Such applications include the processing of timestamped transactions in whic h the sequence of those transactions is important.

In order to recover data in case of an unexpected hardw are or software failure, some applications require that the system time m ust never seem to go backwards. For instance, some applications log transactions to a circular ￿le. These transactions are timestamped, and if the transactions m ust be recovered, the recovery program determines the end of data b y looking for timestamps whic h are out of sequence. If the system time is set bac kwards immediately, transactions whic h occur after the time c hange may not be recovered. Therefore, do not set the time bac kwards using the ;NOW option if there are applications whic h log their transactions using timestamps.

Accounting CPU-SECONDS data ma y be distorted. The user whose process was active during an immediate forward or bac kward change might seem to

2-242 MPE/iX Commands