[Info-vax] set time/cluster and February 29 problem?

[Scott Greig]

In an attempt (poor) to synchronize cluster clocks, a batch job
issues a $ SET TIME/CLUSTER nightly, specifically on the node
with the "faster" clock.  When performed last night (on February
29th, at 10:30 pm) the cluster clocks were reset to February 28th
at 10:30 pm.  Here is the "offending" SET TIME accounting log  entry

SET Image Termination
---------------------
Username:          SYSTEM            UIC:
[SYSTEM]
Account:           SYSTEM            Finish time:       28-FEB-2012
22:30:00.00 <---------Yikes
Process ID:        20233624          Start time:        29-FEB-2012
22:30:00.45  <--|
Owner ID:                            Elapsed time:              ***
00:00:00.45
Terminal name:                       Processor time:              0
00:00:00.00
Remote node addr:                    Priority:          3
Remote node name:                    Privilege <31-00>: BFFFFFFF
Remote ID:                           Privilege <63-32>: FFFFFFFF
Remote full
name:
Posix UID:         -2                Posix GID:         -2
(%XFFFFFFFE)
Queue entry:       2338              Final status code: 10000001
Queue name:        nodename_BATCH
Job name:          SETTIME
Final status text: %SYSTEM-S-NORMAL, normal successful completion
Page faults:               31        Direct IO:                  1
Page fault reads:           3        Buffered IO:                0
Peak working set:        2992        Volumes mounted:            0
Peak page file:          6560        Images executed:            1

Image name: $1$DGA100:[SYS0.SYSCOMMON.][SYSEXE]SET.EXE

I'll be calling HP support about this.

Scott