Team,

Does any one know where db2 pick the time in order to write diaglog file.
Here is the db2diag.log has some mismatch in daylight savings time and EST(eastern standard time).

Current time : 2005-11-18-18.03
Scenario : Bringing down Multi partition instance (1 physical, 4 logical)
Flavour : AIX 5.2 (64bit), DB2 V8.2 FP7

DB2DIAG.log OUTPUT
===============
2005-11-18-18.03.14.291909-240 I5456267A403 LEVEL: Warning
PID : 2687088 TID : 1 PROC : db2sysc 2
INSTANCE: inst114 NODE : 002
FUNCTION: DB2 UDB, routine_infrastructure, sqlerKillAllFmps, probe:5
MESSAGE : Bringing down all db2fmp processes as part of db2stop
DATA #1 : Hexdump, 4 bytes
0x0FFFFFFFFFFFE480 : 0000 0000 ....

2005-11-18-18.03.13.813624-240 I5456671A401 LEVEL: Warning
PID : 2511040 TID : 1 PROC : db2pdbc 3
INSTANCE: inst114 NODE : 003
FUNCTION: DB2 UDB, base sys utilities, sqleCheckForDynDBMUpdate, probe:50
MESSAGE : Attempted to recover dynamic config updates =
DATA #1 : Hexdump, 4 bytes0x0FFFFFFFFFFF7880 :

2005-11-18-17.03.13.910057-300 I5457073A288 LEVEL: Severe
PID : 2777264 TID : 1 PROC : db2fmp (idle) 0
INSTANCE: inst114 NODE : 000
FUNCTION: DB2 UDB, common communication, sqlccipcdarihandshake, probe:3
RETCODE : ZRC=0x83000024=-2097151964

2005-11-18-18.03.13.910254-240 I5457362A288 LEVEL: Severe
PID : 1413326 TID : 1 PROC : db2fmp (idle) 0
INSTANCE: inst114 NODE : 000
FUNCTION: DB2 UDB, common communication, sqlccipcdarihandshake, probe:3
RETCODE : ZRC=0x83000024=-2097151964

2005-11-18-18.03.14.441029-240 I5457651A362 LEVEL: Severe
PID : 1282230 TID : 1 PROC : db2hmon 0
INSTANCE: inst114 NODE : 000
FUNCTION: DB2 UDB, routine_infrastructure, sqlerFmpOneTimeInit, probe:100
MESSAGE : DiagDataDATA #1 : Hexdump, 4 bytes
0x0FFFFFFFFFFFF4E0 : FFFF FBEE ....

2005-11-18-18.03.14.529341-240 I5458014A362 LEVEL: Severe
PID : 938212 TID : 1 PROC : db2hmon 2
INSTANCE: inst114 NODE : 000
FUNCTION: DB2 UDB, routine_infrastructure, sqlerFmpOneTimeInit, probe:100
MESSAGE : DiagData
DATA #1 : Hexdump, 4 bytes
0x0FFFFFFFFFFFF4E0 : FFFF FBEE ....

2005-11-18-18.03.14.762787-240 I5458377A403 LEVEL: Warning
PID : 450594 TID : 1 PROC : db2sysc 3
INSTANCE: inst114 NODE : 003
FUNCTION: DB2 UDB, routine_infrastructure, sqlerKillAllFmps, probe:5
MESSAGE : Bringing down all db2fmp processes as part of db2stop
DATA #1 : Hexdump, 4 bytes
0x0FFFFFFFFFFFE480 : 0000 0000 ....

2005-11-18-17.03.13.910057-300 I5458781A288 LEVEL: Severe
PID : 2801744 TID : 1 PROC : db2fmp (idle) 0
INSTANCE: inst114 NODE : 000
FUNCTION: DB2 UDB, common communication, sqlccipcdarihandshake, probe:3
RETCODE : ZRC=0x83000024=-2097151964

2005-11-18-17.03.15.013943-300 E5459070A301 LEVEL: Event
PID : 733184 TID : 1 PROC : db2stop2
INSTANCE: inst114 NODE : 000
FUNCTION: DB2 UDB, base sys utilities, DB2StopMain, probe:911
MESSAGE : ADM7514W Database manager has stopped.
STOP : DB2 DBM

2005-11-18-18.03.15.044584-240 I5459372A362 LEVEL: Severe
PID : 1056958 TID : 1 PROC : db2hmon 3
INSTANCE: inst114 NODE : 000
FUNCTION: DB2 UDB, routine_infrastructure, sqlerFmpOneTimeInit, probe:100
MESSAGE : DiagData
DATA #1 : Hexdump, 4 bytes
0x0FFFFFFFFFFFF4E0 : FFFF FBEE ....

2005-11-18-18.03.15.200942-240 I5459735A403 LEVEL: Warning
PID : 1294590 TID : 1 PROC : db2sysc 1
INSTANCE: inst114 NODE : 001
FUNCTION: DB2 UDB, routine_infrastructure, sqlerKillAllFmps, probe:5
MESSAGE : Bringing down all db2fmp processes as part of db2stop
DATA #1 : Hexdump, 4 bytes
0x0FFFFFFFFFFFE480 : 0000 0000 ....

2005-11-18-17.03.15.408627-300 E5460139A301 LEVEL: Event
PID : 807076 TID : 1 PROC : db2stop2
INSTANCE: inst114 NODE : 002
FUNCTION: DB2 UDB, base sys utilities, DB2StopMain, probe:911
MESSAGE : ADM7514W Database manager has stopped.
STOP : DB2 DBM

2005-11-18-18.03.15.532709-240 I5460441A362 LEVEL: Severe
PID : 794874 TID : 1 PROC : db2hmon 1
INSTANCE: inst114 NODE : 000
FUNCTION: DB2 UDB, routine_infrastructure, sqlerFmpOneTimeInit, probe:100
MESSAGE : DiagData DATA #1 : Hexdump, 4 bytes
0x0FFFFFFFFFFFF4E0 : FFFF FBEE ....

Thanks
RJ

Any wild guess also accepted and appreciated.

Suggestions regarding opening IBM's PMR for this issue....

Team......

Opened IBM ticket and IBM comes with APAR IY68629 and fixed in Fixpak 9a.

Planned to upgrade our servers.

Cheers :-)
RJ