Filter
Top Products
ANS9400W program-name: Recovered program-name. The daemon was either not started or
in corrupted state.
Explanation: TSM HSM daemon breakdown with automatic recovery by the
dsmwatchd.
System Action: Restarting the daemon.
User Response: Continue with normal operation.
ANS9401E program-name: Cannot kill recall daemon.
Explanation: TSM A request for killing the recall daemon failed. This may happen
during node failover.
System Action: none.
User Response: Continue with normal operation unless further errors occur.
ANS9402E program-name: Cannot notify to recover HSM 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.
System Action: none.
User Response: Contact service 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.
System Action: Migrate HSM functionality to another node.
User Response: Check failure node. It may be necessary to recover the local
GPFS daemon.
ANS9404W program-name: Received failover request 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.
System Action: HSM will try to takeover the managed filesystems from a failure
node.
User Response: Check failure node.
1279
Tivoli Storage Manager Messages
15. Tivoli Space Manager