Well, nobody's perfect: I must admit that I answered too quick in my first
reply:

 > 1998.04.09 15:27:14 ANR0800I
 >                              DELETE FILESPACE: /886084568 for node
 >                              HD004 started as process 248.
 > 1998.04.09 16:27:14 ANR0802I
 >                              Delete Filespace /886084568 (backup/
 >                              archive data) for node HD004 started.
 > 1998.04.09 16:29:09 ANR0806I
 >                              Delete Filespace /886084568 complete
 >                              for node HD004: 5246 files deleted.
 >
 > The correct time for the message-id ANR0800I must be 16:27:14
I assumed that all ADSM msgs come asynchronously and from processes
which ADSM schedules internally. In addition, I had no performance
figures from the machine on which ADSM runs here. ANR0802I should
occur also roughly at the same time as ANR0800I.

 > 1998.04.09 18:15:53 ANR0802I
 >                              Delete Filespace /892031471 (backup/
 >                              archive data) for node HD004 started.
 > 1998.04.09 20:15:53 ANR0800I DELETE FILESPACE: /892031471 for node
 >                              HD004 started as process 250.
 > 1998.04.09 20:17:39 ANR0806I Delete Filespace /892031471 complete
 >                              for node HD004: 4757 files deleted.
 >
 > The correct time for the message-id ANR0802I must be 20:15:53

Well, here I read too quick. ANR0800I should not occur 2 hours later
and ...

the question from Mr. Flemming stays unanswered.

Concerning this question, I just remember some very nasty side
effects on WinNT 4.0 with different service packs and Lotus Notes
4.0/4.5. Lotus Notes switched the time stamps of notes documents
around after switching daylight savings time but I don't remember
the exact scenario.

Maybe AIX plays a role here as well - or was the problem just
observed with exactly and only this release of ADSM?

Best regards

Andreas Peikert, Systems Programmer
   Fon: +49 (0)8122 43-5805 / Fax: +49 (0)8122 43-3260
   aMaDEUS Data Processing GmbH,   P.O. Box,   D-85424 Erding,   Germany