Hello all,



after upgrading some TSM clients (on AIX and Solaris) to version 5.3.2.0
I have noticed that there's always a 'new' dsmerror.log file existing,
even if there hasn't been an error.

If dsmerror.log wasn't existing then the file size is 0 (zero) bytes and
it seems dsmerror.log was created like the Unix 'touch' command is
doing. On the other hand, if dsmerror.log was existing and had entries
in, the timestamp has been updated with the one of the last scheduled
backup even if the wasn't an error in that backup operation.

Has this something to do with IBM's changes for the DSM_LOG environment
variable and the check that dsmerror.log is writable?



Thanks, Rainer



--------------------------------

RHo-Consulting

Rembrandtstr. 12

D-93093 Donaustauf

phone:   +49 9403 969188

mobile:  +49 162 2807 888

email:    rainer.holzinger AT t-online DOT de

             rainer.holzinger AT web DOT de