ANS9400W program-name: Recoveredprogram-name. The daemon was either not started or
in corrupted state.
Explanation: TSM HSM daemon breakdown with automatic recovery by the
dsmwatchd.
SystemAction: Restarting the daemon.
User Response: Continuewith normal operation.
ANS9401E program-name: Cannot kill recalldaemon.
Explanation: TSMA request for killing the recall daemon failed. This may happen
during node failover.
SystemAction: none.
User Response: Continuewith normal operation unless further errors occur.
ANS9402E program-name: Cannot notify to recoverHSM operations on a failure node.
Explanation: TSM In order to takeover the functionality of a malfunctional
partner node the dsmwatchd must notify the local daemons.
SystemAction: none.
User Response: Contactservice representative.
ANS9403E program-name:The local HSM functionality cannot be recovered. Trying to
initiate failover to another node.
Explanation: TSM If the GPFS daemon crashes or the local HSM daemons cannot
perform their function for whatever reason the dsmwatchd will try to migrate the
functionality to another node.
SystemAction: Migrate HSM functionality to another node.
User Response: Checkfailure node. It may be necessary to recover the local
GPFS daemon.
ANS9404W program-name: Received failoverrequest from node ID with frame ID . Trying
to takeover remote filesystems.
Explanation: TSM The local dsmwatchd received a notification about a failing
HSM node. It will try to takeover its managed filesystems.
SystemAction: HSM will try to takeover the managed filesystems from a failure
node.
User Response: Checkfailure node.
1279
Tivoli Storage Manager Messages
15. Tivoli Space Manager