Filter
Top Products
ANS1307E Node in use
Explanation: The node you are running on is in use by another operation on the
server. This might be from another client or from some activity on the server.
System Action: Processing stopped.
User Response: Retry the operation, or see your system administrator to see what
other operations are running for your node.
ANS1308E Expiration date must be greater than today’s date
Explanation: Archive expiration date is too low, the date must be greater than
today’s date.
System Action: TSM canceled the current operation.
User Response: Retry archiving the file with an expiration date that is higher than
today’s date.
ANS1309W Requested data is offline
Explanation: For the restore or retrieve operation, one or more of the requested
files must be recalled from offline storage media (generally tape). The wait time
depends on your site’s offline storage management policies.
System Action: TSM waits for offline storage media to become available and then
continues.
User Response: None.
ANS1310E Object too large for server limits
Explanation: The object is too large. The configuration of the server does not
have any data storage space that accepts the object.
System Action: File skipped.
User Response: See your system administrator to determine the maximum file
(object) size for which your site’s server is configured.
ANS1311E Server out of data storage space
Explanation: The server does not have any space available to store the object.
System Action: TSM ended the current operation.
User Response: You can take any of the following actions:
¶ Request the system administrator to add space to the storage pool.
¶ Set COMPRESSALWAYS=NO and COMPRESSIon=YES in the options file
(DSM.OPT). If the file grows during compression, then TSM will resend it
uncompressed.
¶ Turn off disk caching in the disk storage pool, and issue MOVE DATA
commands to each disk pool volume to clear out the cached bitfiles.
1170
Version 3 Release 7