RE: Time change this weekend

Dave, I will also keep our IBM i (POWER6) up all this weekend and see
the effect that Time change has on our JD Edwards World and High
Availabilty machines.
++++++++++++++++++++
In my 'upgrade the Operating System CL program' that runs daily, I have:
/* the *NTP server connects to TIME server for time correction.
/* See J55QSTRUP for other command nd needed for this to work.
CHGNTPA RMTSYS('0.POOL.NTP.ORG' '1.POOL.NTP.ORG' '2.POOL.NTP.ORG')
AUTOSTART(*YES) +
POLLITV(120) MINADJ(1000) MAXADJ(23) ADJTHLD(*MAXADJ) ACTLOG(*POLL) +

SVRAUTOSTR(*YES) SVRACTLOG(*ALL)
MONMSG MSGID(CPF0000 CPC0000 CPD0000)
+++++++++++++++++++++++++++++++
In our QSTRUP program that runs at each IPL, we have:

QSYS/STRTCPSVR SERVER(*NTP)
MONMSG MSGID(CPF0000 CPC0000 CPD0000)

+++++++++++++++++++
The command EDTF STMF('/QIBM/USERDATA/OS400/TCPIP/NTP/QTOT20091028')
today shows:

Record : 1 of 62 by 8 Column : 1 92 by
74
Control :



CMD
....+....1....+....2....+....3....+....4....+....5....+....6....+....7..
..+
************Beginning of data**************

SNTP Client Activity Log QTOTNTP/QNTP/116630 10/28/09 12:49:32.504
AM
TCP9136 SNTP Client started.

TCP9146 Using time server 1.POOL.NTP.ORG.

TCP9162 10/28/09 12:49:32.535 AM Time remaining for adjustment is
0.000 sec
TCP9116 10/28/09 12:49:32.535 AM NTP server UTC time is 10/28/09
5:49:33.14
TCP9117 10/28/09 12:49:32.535 AM Client clock UTC time is 10/28/09
5:49:32.
TCP9120 10/28/09 12:49:32.535 AM Client clock adjusted = 0 (0 = not
adjust
TCP9146 Using time server 1.POOL.NTP.ORG.

TCP9162 10/28/09 2:49:36.769 AM Time remaining for adjustment is
0.000 seco
TCP9116 10/28/09 2:49:36.769 AM NTP server UTC time is 10/28/09
7:49:37.543
TCP9117 10/28/09 2:49:36.769 AM Client clock UTC time is 10/28/09
7:49:36.7
TCP9120 10/28/09 2:49:36.769 AM Client clock adjusted = 0 (0 = not
adjuste
TCP9146 Using time server 1.POOL.NTP.ORG.

TCP9162 10/28/09 4:49:40.975 AM Time remaining for adjustment is
0.000 seco