HP 5.3.2 dsm client log problem

[usupport]

Old client kept giving error Destroy Mutex failed: 22. and cored.



Upgraded to 5.3.2 on HP-UX 11.11.



Now, the dsmerror.log and dsmsched.log are interchanging messages.



That is, dsmsched.log has error messages and dsmerror.log has schedule messages but not a complete switch.



We're trying to:

-shutdown dsm client

-delete the old logs

-update dsm.sys

from: schedlogretention 15

to: schedlogretention 15 D

- started up dsm client



Anyone else have this issue and any possible solutions.

 

[ricardoa]

Hello...



Is TSM Server at 5.2 or 5.3 levels?...If so, quit of dsmc session and edit dsm.sys file:



Be sure that these lines exists:



SERVERNAME <name of TSM server>

NODENAME <name of the TSM client>

TCPSERVERADDRESS <IP address of TSM Server>

TCPCLIENTADDRESS <IP address of TSM client>

ERRORLOGNAME <full path to dsmerror.log - like - /opt/tivoli/tsm/client/ba/bin/dsmerror.log>

ERRORLOGRETENTION <7 D, for example>

SCHEDLOGNAME <full path to dsmsched.log - like - /opt/tivoli/tsm/client/ba/bin/dsmsched.log>

SCHEDLOGRETENTION <7 D, for example>



Retest.



Best Regards,

Alan