IBM Tivoli Storage Manager: Messages

Chapter 5. Client and Data Protection for Lotus Notes Messages (ANS0100-ANS9999)

This section contains a listing of messages for the following clients:

• TSM administrative clients
• Application program interface clients
• Backup-archive and Space Management (HSM) clients
• Data Protection for Lotus Notes

The messages for these clients contain a common ANS message prefix and a unique message number. The messages are listed in numeric order.

This section also contains Diagnosis, Modification, or Tuning Information. Some of these messages include information about the TSM error log that you can use when working with your service representative.

Explanation: The system encountered an internal program error due to an invalid parameter.

System Action: The system returns to the calling procedure.

User Response: Ask your service representative to check the error log.

Explanation: The client is not authorized to restore the other node's data.

System Action: The system returns to the calling procedure.

User Response: Get authorization from the other node.

Explanation: The objName field does not have a leading directory separator.

System Action: The system returns to the calling procedure.

User Response: Correct the value for the objName.

Explanation: Wildcards are not allowed in the objName directory path.

System Action: The system returns to the calling procedure.

User Response: Correct the value for the objName.

Explanation: The system is unable to open the error log file.

System Action: The system returns to the calling procedure.

User Response: Verify the DSMI_LOG value and access permission. On the AS/400 platform, verify the value specified for ERRORLOGNAME in the API options file.

Explanation: There was an error writing to the log file.

System Action: The system returns to the calling procedure.

User Response: Verify the DSMI_LOG value and access permission. on the AS/400 platform, verify the value specified for ERRORLOGNAME in the API options file.

Explanation: The system is unable to open the error log file.

System Action: The system returns to the calling procedure.

User Response: Verify the DSMI_LOG value and access permission. On the AS/400 platform, verify the value specified for ERRORLOGNAME in the API options file.

Explanation: The TCP/IP WINSOCK.DLL file cannot be found.

System Action: Processing stopped.

User Response: Verify your TCP/IP installation.

Explanation: An error occurred while loading a library. The TCP/IP DLL load failed.

System Action: Processing stopped.

User Response: Verify your TCP/IP installation.

Explanation: An error occurred while locating a function. The TCP/IP load function failed.

System Action: Processing stopped.

User Response: Verify your TCP/IP installation.

Explanation: There is no value provided for the object name pointer.

System Action: The system returns to the calling procedure.

User Response: Provide an address for the dsmObjName structure.

Explanation: There is no value provided for the data block pointer.

System Action: The system returns to the calling procedure.

User Response: Provide an address for the DataBlk structure.

Explanation: There is no value provided for the object attribute pointer.

System Action: The system returns to the calling procedure.

User Response: Provide an address for the ObjAttr structure.

Explanation: The server did not respond with the session information.

System Action: The system returns to the calling procedure.

User Response: Verify the server status.

Explanation: The server did not respond with the policy information.

System Action: The system returns to the calling procedure.

User Response: Verify the server policy definitions.

Explanation: The value for the dataBlk bufferLen is zero.

System Action: The system returns to the calling procedure.

User Response: Provide a non-zero value for the bufferLen.

Explanation: There is no value provided for the dataBlk bufferPtr.

System Action: The system returns to the calling procedure.

User Response: Provide an address for the bufferPtr.

Explanation: The value for the objType is invalid.

System Action: The system returns to the calling procedure.

User Response: The value for dsmObjName.objType must be:

DSM_OBJ_FILE or DSM_OBJ_DIRECTORY for Backup, or

DSM_OBJ_FILE for Archive.

Explanation: The dsmEndTxn vote is invalid.

System Action: The system returns to the calling procedure.

User Response: The vote must be DSM_VOTE_COMMIT or DSM_VOTE_ABORT.

Explanation: An invalid option was found.

System Action: The system returns to the calling procedure.

User Response: Verify the options in dsm.opt, dsm.sys, and the options string. Check the error log for more details about the error. on the AS/400 platform, verify the options in *LIB/QOPTITSM(APIOPT).

Explanation: The system encountered an error in the API internals.

System Action: The system returns to the calling procedure.

User Response: Shut down the process and retry the operation. Verify that any previous dsmInit calls were cleaned up and terminated by a dsmTerminate call. If the problem continues, contact your system administrator or service representative.

Explanation: The repository type is invalid.

System Action: The system returns to the calling procedure.

User Response: For dsmDeleteFS the repository must be one of the following:

• DSM_ARCHIVE_REP
• DSM_BACKUP_REP
• DSM_REPOS_ALL.

Explanation: The filespace name is invalid.

System Action: The system returns to the calling procedure.

User Response: Filespace name should start with the directory delimiter.

Explanation: The object name is invalid because of an empty string or there is no leading delimiter.

System Action: The system returns to the calling procedure.

User Response: Verify the format of the dsmObjName full path.

Explanation: The low level qualifier for the object name is invalid.

System Action: The system returns to the calling procedure.

User Response: Start the low level qualifier of the object name with the directory delimiter.

Explanation: The object owner must be either the root user, or the object owner must be the same as the session owner.

System Action: The system returns to the calling procedure.

User Response: Verify the session owner and object owner.

Explanation: The dsmBindMC sendType is invalid.

System Action: The system returns to the calling procedure.

User Response: The sendType must be one of the following:

stBackup

stArchive

stBackupMountWait

stArchiveMountWait

Explanation: The dsmSendObj sendType is invalid.

System Action: The system returns to the calling procedure.

User Response: The sendType must be one of the following:

stBackup

stArchive

stBackupMountWait

stArchiveMountWait

Explanation: The dsmDeleteObj delType is invalid.

System Action: The system returns to the calling procedure.

User Response: The delType must be dtBackup or dtArchive.

Explanation: The query Backup objState is invalid.

System Action: The system returns to the calling procedure.

User Response: The qryBackupData.objState must be one of the following:

DSM_ACTIVE

DSM_INACTIVE

DSM_ANY_MATCH

Explanation: A query or send operation is unable to find the management class name.

System Action: The system returns to the calling procedure.

User Response: Verify the management class name.

Explanation: The drive letter is not an alphabetic character. This return code is valid on Microsoft Windows only.

System Action: The system returns to the calling procedure.

User Response: Verify that the drive designation is an alphabetic character. The referenced field is dsmDosFSAttrib.driveLetter.

Explanation: There is no value provided for the Register Filespace name.

System Action: The system returns to the calling procedure.

User Response: Provide a filespace name on dsmRegisterFS.

Explanation: There is no value provided for new password.

System Action: The system returns to the calling procedure.

User Response: Provide a new password on dsmChangePW.

Explanation: There is no value provided for old password.

System Action: The system returns to the calling procedure.

User Response: Provide an old password on dsmChangePW.

Explanation: PASSWORDACCESS=generate establishes a session with the current login user as the owner.

System Action: The system returns to the calling procedure.

User Response: When using PASSWORDACCESS=generate, set clientOwnerNameP to NULL.

Explanation: PASSWORDACCESS=generate establishes a session with the current hostname as the node.

System Action: The system returns to the calling procedure.

User Response: When using PASSWORDACCESS=generate, set clientNodeNameP to NULL.

Explanation: The sequence of calls is invalid.

System Action: The system returns to the calling procedure.

User Response: Verify the transaction call sequence.

Explanation: On dsmSendObj, wildcards are not allowed for the objName.

System Action: The system returns to the calling procedure.

User Response: Provide a fs, hl, and ll on the dsmObjName.

Explanation: The filespace to delete cannot be found.

System Action: The system returns to the calling procedure.

User Response: Verify the filespace name.

Explanation: On dsmSendObj, dsmDeleteObj, or dsmUpdateFS, the filespace is not registered.

System Action: The system returns to the calling procedure.

User Response: Verify the filespace name.

Explanation: On dsmRegisterFS the filespace is already registered.

System Action: The system returns to the calling procedure.

User Response: Verify the filespace name.

Explanation: On dsmBeginGetData, the objID is NULL.

System Action: The system returns to the calling procedure.

User Response: Verify the following:

The dsmGetList is not NULL.

Each objID is not NULL.

The dsmGetList numObjId is not zero.

Explanation: On dsmInit the caller's API version has a higher value than the ITSM library version.

System Action: The system returns to the calling procedure.

User Response: Install the latest ITSM API library and trusted agent module.

Explanation: The caller's structure version is different than the ITSM library version.

System Action: The system returns to the calling procedure.

User Response: Ensure that the stVersion field is set with the value in the header file. Recompile the application with the latest header files.

Explanation: This transaction must be ended and a new one must be started due to one of the following reasons:

The destination changed.

The byte limit is exceeded

The maximum number of objects is exceeded.

System Action: The system returns to the calling procedure.

User Response: Issue dsmEndTxn and start a new transaction session.

Explanation: The backup or archive object is excluded from processing.

System Action: The system returns to the calling procedure.

User Response: Verify the objName and Exclude lists.

Explanation: The backup object does not have a copy group.

System Action: The system returns to the calling procedure.

User Response: Verify server policy definitions.

Explanation: The archive object does not have a copy group.

System Action: The system returns to the calling procedure.

User Response: Verify server policy definitions.

Explanation: Memory used by the ITSM API has been corrupted.

System Action: The system returns to the calling procedure.

User Response: Retry the operation. If the problem continues, contact your system administrator or service representative.

Explanation: The sendObj Archive description is too long.

System Action: The system returns to the calling procedure.

User Response: The sndArchiveData.descr string must be less than or equal to DSM_MAX_DESCR_LENGTH.

Explanation: The sendObj ObjAttr.objInfo is too long.

System Action: The system returns to the calling procedure.

User Response: The objInfo field must be less than or equal to DSM_MAX_OBJINFO_LENGTH.

Explanation: The sendObj dsmObjName.hl is too long.

System Action: The system returns to the calling procedure.

User Response: The hl field must be less than or equal to DSM_MAX_HL_LENGTH.

Explanation: The dsmChangePW password is too long.

System Action: The system returns to the calling procedure.

User Response: The password field must be less than or equal to DSM_MAX_VERIFIER_LENGTH.

Explanation: The sendObj dsmObjName.fs is too long.

System Action: The system returns to the calling procedure.

User Response: The fs field must be less than or equal to DSM_MAX_FS_LENGTH.

Explanation: The sendObj dsmObjName.ll is too long.

System Action: The system returns to the calling procedure.

User Response: The ll field must be less than or equal to DSM_MAX_LL_LENGTH.

Explanation: On RegisterFS or UpdateFS the fsAttr's fsInfo is too long.

System Action: The system returns to the calling procedure.

User Response: The fsInfo field must be less than or equal to DSM_MAX_FSINFO_LENGTH.

Explanation: On dsmGetNextQObj or dsmGetData there is more available data.

System Action: The system returns to the calling procedure.

User Response: Call the function again.

Explanation: The dataBlk buffer is too small for the query response.

System Action: The system returns to the calling procedure.

User Response: On dsmGetNextQObj ensure that the dataBlk buffer is at least as big as the query response structure.

Explanation: An invalid option keyword was found in the dsmInit configuration file, the option string, dsm.sys, or dsm.opt.

System Action: The system returns to the calling procedure.

User Response: Correct the spelling of the option keywords. Verify that the dsmInit configuration file only has a subset of the dsm.sys options. Check the error log for more details about the error.

Explanation: The configuration file specified on dsmInit cannot be opened.

System Action: The system returns to the calling procedure.

User Response: Verify the file name.

Explanation: The Include/Exclude definition file was not found.

System Action: The system returns to the calling procedure.

User Response: Verify the file name on the Inclexcl option.

Explanation: Either the dsm.sys file was not found, or the Inclexcl file specified in dsm.sys was not found.

System Action: The system returns to the calling procedure.

User Response: The dsm.sys file must be in the directory referenced by the environment variable DSMI_DIR. Verify the file name on the Inclexcl option in the dsm.sys file.

Explanation: Only a UNIX root user can execute dsmChangePW or dsmDeleteFS.

System Action: The system returns to the calling procedure.

User Response: Run this program as a root user.

Explanation: You must issue dsmBindMC before dsmSendObj.

System Action: The system returns to the calling procedure.

User Response: Modify your program.

Explanation: After a dsmEndTxn call, the transaction is aborted by either the server or client with a DSM_VOTE_ABORT and the reason is returned.

System Action: The system returns to the calling procedure.

User Response: Check the reason field for the code which explains why the transaction has been aborted.

Explanation: The option is not valid on this command line.

System Action: Processing stops

User Response: Verify that the option and value are not misspelled and are valid with the current command.

Explanation: Server problem: Destination not defined.

System Action: Processing stopped.

User Response: Have your service representative check the error log.

Explanation: An unknown and unexpected error code occurred within the client program. The structured file data type is unknown. This is a programming failure and the client program ends.

System Action: Processing stopped.

User Response: Retry the operation. If the problem continues, contact your system administrator.

Explanation: The data buffer overflowed. This is a programming failure and the client program ends.

System Action: Processing stopped.

User Response: Retry the operation. If the problem continues, contact your system administrator.

Explanation: No more files can be restored or retrieved since the destination directory is full.

System Action: Processing stopped.

User Response: Free up disk space, or restore or retrieve the file to another disk.

Explanation: The operation is finished.

System Action: The system returns to the calling procedure.

User Response: Proceed with next function call.

Explanation: The trusted agent execution/owner permissions are invalid.

System Action: Processing stopped.

User Response: Have your system administrator check the installation instructions for the client to ensure that the trusted agent permissions are set correctly.

Explanation: Processing stopped. This is a programming failure and the client program ends.

System Action: Processing stopped.

User Response: Retry the operation. If the problem continues, contact your system administrator.

Explanation: The trusted agent blocks the operation. This is a programming failure and the client program ends.

System Action: Processing stopped.

User Response: Retry the operation. If the problem continues, contact your system administrator.

Explanation: The area for the include/exclude pattern is too small. This is a programming failure and the client program ends.

System Action: Processing stopped.

User Response: Retry the operation. If the problem continues, contact your system administrator.

Explanation: There is no closing bracket in the pattern. This is a programming failure and the client program ends.

System Action: Processing stopped.

User Response: Retry the operation. If the problem continues, contact your system administrator.

Explanation: The server encountered an error and will abort the transaction.

System Action: The transaction will be aborted. The reason code is passed on the dsmEndTxn call.

User Response: Issue the dsmEndTxn with a vote of DSM_VOTE_COMMIT and examine the reason code.

Explanation: A file was skipped during a restore operation because the file is off line and the application has chosen not to wait for a tape mount.

System Action: File skipped.

User Response: Verify the application sets the mountWait value correctly on dsmBeginGetData.

Explanation: ITSM was unable to find the ITSM Trusted Agent module in the specified directory. The name of the ITSM Trusted Agent module is dsmtca.

System Action: ITSM ends.

User Response: Make sure the Trusted Agent module is in the directory specified by DSMI_DIR.

Explanation: An attempt to access a system function has been denied.

System Action: Processing stopped.

User Response: Contact your system administrator.

Explanation: The file containing the stored password for the specified server-name is unavailable.

System Action: ITSM ends.

User Response: The root user must set and store a new password.

Explanation: The high level qualifier for the object name is invalid.

System Action: The system returns to the calling procedure.

User Response: High level qualifier of the object name should start with the directory delimiter.

Explanation: The number of objects (numObjId) specified on the dsmBeginGetData call exceeds DSM_MAX_GET_OBJ | DSM_MAX_PARTIAL_GET_OBJ.

System Action: The system returns to the calling procedure.

User Response: Check the number of objects before calling dsmBeginGetData. If it is greater than DSM_MAX_GET_OBJ | DSM_MAX_PARTIAL_GET_OBJ, then issue multiple Get call sequences.

Explanation: The dsmUpdateFS or dsmUpdateObj action is invalid.

System Action: The system returns to the calling procedure.

User Response: Correct the action value. Valid values are defined in dsmapitd.h and documented in our Using the API book.

Explanation: The key file for Tivoli Storage Manager data protection application client for Oracle cannot be found.

System Action: The system returns to the calling procedure.

User Response: Ensure that you have ordered the Tivoli Storage Manager data protection application client which contains TDP for Oracle, and install the key file.

Explanation: The key file content for Tivoli Storage Manager data protection application client for Oracle is invalid.

System Action: The system returns to the calling procedure.

User Response: Ensure that you have ordered the Tivoli Storage Manager data protection application client which contains the TDP for Oracle, and install the key file.

Explanation: ITSM found that the encryption key passwords do not match.

System Action: You are prompted for the encryption key password.

User Response: Enter the correct encryption key password.

Explanation: The specified file could not be located or opened.

System Action: Attempts to open file failed.

User Response: Make sure the file exists.

Explanation: The user id you specified is currently locked on the server.

System Action: Session was not started.

User Response: Check with your system administrator to find out why your user id is locked.

Explanation: if MANAGEDSERVICES SCHEDULE is indicated in the option file, the ITSM scheduler cannot be started in the traditional manner.

System Action: Scheduler stopped.

User Response: If you are not going to use dsmcad to manage the schedule anymore, stop dsmcad and remove MANAGEDSERVICES option from the option file.

Explanation: The ITSM DLL dsm3270.dll cannot be found in the user's path.

System Action: Communications link is not established.

User Response: Make sure that the ITSM DLL dsm3270.dll is in a directory that is included in the user's path.

Explanation: The operation successfully completed.

System Action: None.

User Response: None.

Explanation: User issued the Generate Password command, but password access is not set to GENERATE in the options file.

System Action: ITSM none.

User Response: Add PASSWORDACCESS GENERATE to your dsm.opt file .

Explanation: User issued the Generate Password command with class=NAS, but no NAS node was specified.

System Action: None.

User Response: Retry the command and use the -nasnodename option.

Explanation: User issued the Generate Password command with an invalid or unknown class.

System Action: None.

User Response: Retry the command and use a supported class type option (class=CLIENT or class=NAS).

Explanation: User issued the Generate Password command and it was successful.

System Action: None.

User Response: None.

Explanation: The request to start a remote operation has failed for the indicated node and filespace. The status and the reason for the failure are shown.

System Action: ITSM ended the current operation.

User Response: Contact your system administrator for more information.

Explanation: The request to start a remote operation has failed for the indicated node and filespace. The status of the failure is shown.

System Action: IBM Tivoli Storage Manager ended the current operation.

User Response: Contact your system administrator for more information.

Explanation: The system is unable to open the message txt file (dscenu.txt or dsmclientV3.cat for AIX). On the AS/400 platform this file is QANSAPI/QAANSENU(TXT).

System Action: The system returns to the calling procedure.

User Response: Verify that the dscenu.txt file is in the directory pointed to by DSMI_DIR. For AIX, verify that the dsmclientV3.cat file has a symbolic link to /usr/lib/nls/msg/<locale>/dsmclientV3.cat .

Explanation: The system is unable to use the message text file (dscenu.txt or dsmclientV3.cat for AIX) because of an invalid header. On the AS/400 platform this file is QANSAPI/QAANSENU(TXT).

System Action: The system returns to the calling procedure.

User Response: Install the message text file again.

Explanation: The system is unable to use the message txt file (dscenu.txt or dsmclientV3.cat for AIX) because of an invalid control record. On the AS/400 platform this file is QANSAPI/QAANSENU(TXT).

System Action: The system returns to the calling procedure.

User Response: Install the message text file again.

Explanation: An invalid value is specified for DATEFORMAT.

System Action: The system returns to the calling procedure.

User Response: Specify a valid value.

Explanation: An invalid value is specified for TIMEFORMAT.

System Action: The system returns to the calling procedure.

User Response: Specify a valid value.

Explanation: An invalid value is specified for NUMBERFORMAT.

System Action: The system returns to the calling procedure.

User Response: Specify a valid value.

Explanation: The message parameter for dsmRCMsg is a NULL pointer.

System Action: The system returns to the calling procedure.

User Response: Allocate enough space for the message parameter.

Explanation: The dsmRC parameter for dsmRCMsg is an unsupported return code.

System Action: The system returns to the calling procedure.

User Response: Specify a valid value.

Explanation: The partialObjOffset value for partial object retrieve is invalid.

System Action: The system returns to the calling procedure.

User Response: Specify a valid value.

Explanation: partialObjLength value for partial object retrieve is invalid.

System Action: The system returns to the calling procedure.

User Response: Specify a valid value.

Explanation: The ITSM server specified by the user does not support partial object retrieve.

System Action: The system returns to the calling procedure.

User Response: Specify a ITSM server which supports the partial object retrieve function.

Explanation: All the tape mount points for this node are in use.

System Action: The system returns to the calling procedure.

User Response: Increase the number of allowed tape mounts for this node on the server.

Explanation: A duplicate object was found, operation cannot complete.

System Action: The requested operation failed.

User Response: Try the operation with a different file specification.

Explanation: The specified objects failed the merge test, operation cannot complete.

System Action: The requested operation failed.

User Response: See documentation for the merge test parameters.

Explanation: The dsmSetAccess accessType is invalid.

System Action: The system returns to the calling procedure.

User Response: The accessType must be one of the following:

atBackup

atArchive

Explanation: You tried to set access to files when no files for the specified filename, drive or file system were previously backed up.

System Action: Processing stopped.

User Response: Ensure that the correct drive or file system was specified and that files are backed up for you to set access.

Explanation: You tried to set access to files when no files for the specified filename, drive or file system were previously archived.

System Action: Processing stopped.

User Response: Ensure that the correct drive or file system was specified and that files are archived for you to set access.

Explanation: The specified Remote Mover type is unknown.

System Action: ITSM ended the current operation.

User Response: Contact your system administrator for more information.

Explanation: A request has been made to use a data mover to perform an operation for the indicated node and filespace. Since an operation for this node and filespace is already in progress, the new operation cannot be performed.

System Action: ITSM ended the current operation.

User Response: Retry the operation at a later time.

Explanation: A required resource is in use by another command or process.

System Action: ITSM ended the current operation.

User Response: Retry the operation at a later time.

Explanation: Communication between a server plugin module and a NAS filer failed.

System Action: ITSM ended the current operation.

User Response: Contact your system administrator for more information.

Explanation: A plugin module detected that a NAS filer is running an unsupported operating system or operating system level.

System Action: ITSM ended the current operation.

User Response: Contact your system administrator for more information.

Explanation: The operation is not valid.

System Action: ITSM ended the current operation.

User Response: Contact your system administrator for more information.

Explanation: The storage pool is not defined.

System Action: ITSM ended the current operation.

User Response: Contact your system administrator for more information.

Explanation: none

System Action: ITSM ended the current operation.

User Response: Contact your system administrator for more information.

Explanation: none

System Action: ITSM ended the current operation.

User Response: Contact your system administrator for more information.

Explanation: The server sent a CRC for a buffer. The client calculated a CRC for the same buffer. These did not match. The mismatch indicates a communication failure.

System Action: In some cases, the client can indicate the failure to the server and retry the operation.

User Response: Check the trace log for additional information and retry the operation. If the problem persists, contact your system administrator.

Explanation: An invalid operation was attempted on a logical group.

System Action: The current operation stops.

User Response: Retry a valid operation.

Explanation: You cannot send data for an object with size estimate = 0.

System Action: The system returns to the calling procedure.

User Response: Set size estimate greater than 0 in dsmSendObj.

Explanation: An operation was attempted on a remote disk that is not defined.

System Action: The current operation stops.

User Response: Define the proper remote disk.

Explanation: Input destination does not match expected destination.

System Action: The current operation stops.

User Response: Retry operation with proper destination.

Explanation: Data mover is not available.

System Action: The current operation stops.

User Response: Retry operation with a proper Data mover.

Explanation: Operation failed because the copy continue option was set to NO.

System Action: The current operation stops.

User Response: This abort code indicates that a store operation, like backup or archive failed because the copy continue option was set to NO. The sysadmin will need to resolve the problem on the server end.

Explanation: Transaction failed because of a problem during a store operation. This error is typical when the next storage pool has a different copy storage pool list and we switch to this pool in the middle of a transaction.

System Action: Transaction is aborted.

User Response: Resend objects in seperate txn's.

Explanation: The license file was not found, or could not be opened because of permissions or the file is corrupted.

System Action: The system returns to the calling procedure.

User Response: Check permissions on file. See if the license file is in the correct place.

Explanation: The license file was not found, or could not be opened because of permissions, or the file is corrupted.

System Action: The system returns to the calling procedure.

User Response: Check permissions on file. See if the license file is in the correct place.

Explanation: The license file was not found, or could not be opened because of permissions or the file is corrupted.

System Action: The system returns to the calling procedure.

User Response: Check permissions on file. See if license file is in the correct place.

Explanation: The license file is not valid.

System Action: The system returns to the calling procedure.

User Response: User needs to obtain a new license.

Explanation: The registration string is not valid.

System Action: The system returns to the calling procedure.

User Response: User needs to obtain a new license.

Explanation: The registration string is not valid.

System Action: The system returns to the calling procedure.

User Response: User needs to obtain a new license.

Explanation: Invalid mode passed by Oracle.

System Action: The system returns to the calling procedure.

User Response: Contact your system administrator.

Explanation: Null filename passed by Oracle.

System Action: The system returns to the calling procedure.

User Response: Contact your system administrator.

Explanation: Wrong Block Size

System Action: The system returns to the calling procedure.

User Response: Contact your system administrator.

Explanation: Backup or Restore Object already exists.

System Action: The system returns to the calling procedure.

User Response: If backing up an object, be sure to generate a unique object name.

Explanation: The handle passed from Oracle is not the same handle that ITSM passed back.

System Action: The system returns to the calling procedure.

User Response: Contact your system administrator.

Explanation: End of file reached.

System Action: The system returns to the calling procedure.

User Response: None

Explanation: The operation must be in READ state.

System Action: The system returns to the calling procedure.

User Response: Contact your service representative.

Explanation: Runtime API is lower than compile time API.

System Action: The system returns to the calling procedure.

User Response: Use the WHAT command to find out the compile time API level. Obtain the same or higher level of API library.

Explanation: The operation must be in WRITE state.

System Action: The system returns to the calling procedure.

User Response: Contact your service representative.

Explanation: Invalid flag passed from Oracle.

System Action: The system returns to the calling procedure.

User Response: Contact your system administrator.

Explanation: The dsmnotes command completed successfully.

System Action: The program completes.

User Response: Not Applicable.

Explanation: An attempt was made to allocate memory but failed.

System Action: Processing stops.

User Response: Check the LOG.DSM file for further details about the failure.

Explanation: An I/O error occurred when an attempt was made to open one of the supporting files (for example: a trace file or log file). This message does not suggest an I/O error in a Notes database.

System Action: Processing stops.

User Response: Check all supporting files, including the log file, and trace file. Consider updating the environment variables in the NOTES.INI file to avoid using the problem file, or check access permission on the file.

Explanation: An I/O error occurred when an attempt was made to write to a supporting file like a trace file or log file. This message does not suggest an I/O error in a Notes database.

System Action: Processing stops.

User Response: Check all supporting files, including the log file, and trace file. Consider updating the environment variables in the NOTES.INI file to avoid using the problem file. Also check your available disk space.

Explanation: An error occurred while trying to retrieve the current working directory.

System Action: Processing stops.

User Response: Check the LOG.DSM file for any further details on the specific error. There may be an error in your operating system since it cannot determine your current working directory.

Explanation: An error was encountered when an attempt was made to obtain the file system information for the drive on which the Notes database resides.

System Action: Processing stops.

User Response: Check the drive on which the Notes database you are processing resides. Be sure that the volume has a label and your disk is attached. Check the LOG.DSM file for details about the error.

Explanation: An error was encountered when an attempt was made to obtain the volume label of the drive on which the Notes database resides.

System Action: Processing stops.

User Response: Check the drive on which the Notes database you are processing resides. Be sure that the volume has a label and your disk is attached.

Explanation: A general parsing error occurred on a dsmnotes command. Either you entered too many path names, or a hyphen (-) or an equal (=) sign is missing in the option.

System Action: Processing stops.

User Response: Check the syntax of the command. Correct the syntax and reissue the command.

Explanation: An invalid option keyword was specified on a dsmnotes command.

System Action: Processing stops.

User Response: Identify and correct the invalid keyword. Then reissue the command.

Explanation: The ITSM password you entered is too long.

System Action: Processing stops.

User Response: If you are resetting a new ITSM password, you need to choose a shorter password. If you are entering a current ITSM password, check that the password is correct. If the password is correct but the problem still occurs, ask your ITSM administrator to reset your password to a new value. If you do this, choose a shorter password.

Explanation: An invalid value was specified for an option on a dsmnotes command.

System Action: Processing stops.

User Response: Identify and correct the invalid value. Then reissue the dsmnotes command.

Explanation: One or more required keywords are missing from the dsmnotes command.

System Action: Processing stops.

User Response: Identify and check the proper syntax and provide the missing keywords and values. Then reissue the dsmnotes command.

Explanation: An invalid date value was entered. Either the syntax of the value was not correct, or an actual value (for example, "45" for month) was invalid.

System Action: Processing stops.

User Response: Identify and correct the invalid date value. Refer to the user's guide of the corresponding platform for the correct date syntax.

Explanation: An invalid time value was entered. Either the syntax of the value was not correct, or an actual value (for example, "75" for hour) was invalid.

System Action: Processing stops.

User Response: Identify and correct the invalid date value. Refer to the user's guide of the corresponding platform for the correct time syntax.

Explanation: No parameters were specified on the dsmnotes command. Some parameters are required such as action parameter and database name parameter.

System Action: Processing stops.

User Response: Refer to the user's guide of the corresponding platform for the correct syntax of your command, including required parameters. Correct the syntax and reissue the command.

Explanation: A syntax error was made on a dsmnotes command. The first parameter on the command is generally used to identify what kind of action is to be performed (for example, "INCR" for incremental backup), but this first parameter on the command was not recognized as a valid action.

System Action: Processing stops.

User Response: Refer to the user's guide of the corresponding platform for the correct command syntax. Correct the syntax and reissue the command.

Explanation: A syntax error occurred on the incremental backup command.

System Action: Processing stops.

User Response: Refer to the user's guide of the corresponding platform for the correct syntax. Correct the syntax and reissue the command.

Explanation: A syntax error occurred on the incremental backup command.

System Action: Processing stops.

User Response: Refer to the user's guide of the corresponding platform for the correct syntax. Correct the syntax and reissue the command.

Explanation: A syntax error occurred on the restore deletion stubs command.

System Action: Processing stops.

User Response: Refer to the user's guide of the corresponding platform for the correct syntax. Correct the syntax and reissue the command.

Explanation: The given path name does not resolve to a valid Notes database file name.

System Action: Processing stops.

User Response: Validate that the given path name is correct. If wildcard symbols are used, refer to the user's guide of the corresponding platform for the correct usage of these symbols. Also check for defaulting to the Notes data directory to ensure that the path name is not defaulting incorrectly.

Explanation: An attempt was made to rebuild a Notes database from backup copies of notes, but the original database file was specified as the target database.

System Action: Processing stops.

User Response: Choose an original name for the target database. The name cannot belong to an existing file.

Explanation: Only a positive number of days can be specified.

System Action: Processing stops.

User Response: Either specify a positive number of days or let the system default to restore all the deleted documents that it can identify.

Explanation: An attempt to open a Notes database was unsuccessful.

System Action: Processing stops.

User Response: Check the LOG.DSM file for more information about the error. Verify the path name of your database. If the path name is correct, then verify the database itself to ensure that it can be opened through the Notes workspace.

Explanation: Restoration of one or more notes was successful.

System Action: The program completes successfully.

User Response: None.

Explanation: The user has interrupted the operation (for example, by pressing an interrupt key such as <Ctrl C>).

System Action: Processing stops.

User Response: None

Explanation: Database rebuild from backup copies of notes was successfully completed.

System Action: The program completes successfully.

User Response: None.

Explanation: An attempt was made to initiate error logging, which includes either opening or creating a LOG.DSM file. The attempt failed.

System Action: Processing stops.

User Response: Check the LOG.DSM file to see why it cannot be opened or created.

Explanation: An attempt was made to query one or more backup copies of notes on the ITSM server, but no copies existed or an attempt was made to merge the data notes (documents) from the ITSM server into the original database, but no data notes existed.

System Action: The program ends.

User Response: If you believe that some matching data should exist on the server, check your database path name to ensure that you are using the correct database file name. If the -merge keyword is used, your database might only have nondata notes (documents).

Explanation: The days value is either negative or greater than 65535.

System Action: Processing stops.

User Response: Use correct days value.

Explanation: An attempt was made to change the ITSM password through the Lotus Notes workspace but the two new ITSM passwords entered did not match.

System Action: Processing stops.

User Response: Retry the command with matching new ITSM passwords.

Explanation: Either the given database file was not backed up on the server, or the database file space was removed from the server.

System Action: Processing stops.

User Response: Check the name of the database to ensure that it is the correct database, and check the DSM.OPT file to ensure that you are accessing the correct ITSM server. You can ask the ITSM administrator to check the filespaces for your node. A database name is equivalent to a filespace.

Explanation: The action you tried to perform is not allowed on a database that is not local.

System Action: Processing stops.

User Response: If the action is not allowed through the Notes workspace interface, but allowed through the ITSM Notes application client command-line interface, then use the appropriate dsmnotes command. An alternative is to complete the action on the appropriate machine.

Explanation: You are not allowed to enter a new target database name for this restore operation.

For OS/2, refer to the dsmnotes restore -FROMDATE option in the user's guide documentation.

System Action: Processing stops.

User Response: If your interface is the Notes workspace, then replace the database name in the entry field with blanks. If your interface is a command, then do not specify a target ("-TO") database.

Explanation: You are required to enter a database name.

System Action: Processing stops.

User Response: Enter the database name.

Explanation: There are no deletion stubs in the given database.

System Action: The program ends.

User Response: If there are no deletion stubs in the database to initiate the restore, then you may need to rebuild the database by restoring the older version of the database file through the ITSM client.

Explanation: Some of the options specified are mutually exclusive. For example:

• For OS/2, the options "-MERGE=NO", "-TO" and "-FROMDate" cannot all be specified simultaneously because a new target database may not be operable if some documents (such as view and form design documents) are excluded.

  Design documents are normally backed up with the initial incremental, and not subsequently modified. In this situation, allowing the FROMDate option would cause some design documents to be excluded when creating the new database.

• For AIX and Windows NT, the options "-MERGE" and "-TO" are mutually exclusive because a new target database cannot be specified for a merge.

System Action: Processing stops.

User Response: Correct the syntax of the command and then reissue the command.

Explanation: An invalid date or time range was given. For example, the "TO" time is earlier than the "FROM" time.

System Action: Processing stops.

User Response: Correct the date or time range and rerun the program. Be sure that all year, month, day, hour, and minute values are in the correct order and are valid values.

Explanation: An attempt was made to restore a note or notes, but no notes documents were chosen.

System Action: Processing stops.

User Response: On the lotus Notes Workspace, select the notes to be restored by placing a checkmark next to the notes.

Explanation: Errors occurred on one or more databases.

System Action: The program partially completes.

User Response: Check the LOG.DSM file for further details about the failure.

Explanation: Error occurred while initializing the Lotus Notes runtime system.

System Action: Processing stops.

User Response: Check the Lotus Notes environment. Try to bring up your Notes workspace if you have not already done so. Also, check the NOTES.INI file to see if it has the correct setup for the Tivoli Storage Manager data protection application client. Refer to the user's guide of the corresponding platform.

Explanation: An attempt was made to restore a single Database but the pathname specified was a directory.

System Action: Processing stops.

User Response: If you want to restore a single database, make sure your database name ends with a ".nsf" extension.

Explanation: Data structure for the application is not compatible with the data stored on the server.

System Action: Processing stops.

User Response: Check the user's software version.

Explanation: A Lotus Notes error has occurred but the Tivoli Storage Manager data protection application client was not able to translate the error code into a valid Lotus Notes error message.

System Action: Processing stops.

User Response: The supported Lotus Notes version is 4.50 for AIX and NT, or 4.52 or above for OS/2. You probably have a downlevel Lotus Notes software installed on your system. Check with your Lotus Notes Administrator for assistance.

Explanation: A ITSM error has occurred but the Tivoli Storage Manager data protection application client was not able to translate the error code into a valid ITSM error message.

System Action: Processing stops.

User Response: Check with your ITSM Administrator for assistance.

Explanation: You do not have a valid Tivoli Storage Manager data protection application client license or your license has already expired.

System Action: Processing stops.

User Response: Refer to the user's guide of the corresponding platform or call the IBM sales representatives for license information.

Explanation: An attempt was made to back up a database that has the same path and name as a database that is previously backed up to the ITSM server. These two databases have the same name, but they have different database IDs. As a result, they were treated as two different databases.

System Action: Processing stops.

User Response: Rename the database to be backed up. If the database that is previously backed up in the ITSM server is no longer needed, ask your ITSM administrator to delete the database's filespace on the server.

Explanation: A ITSM password is required.

System Action: Processing stops.

User Response: If the ITSM PASSWORDACCESS PROMPT option in the option file is used, you are required to enter the password by using the -adsmpw keyword.

If the ITSM PASSWORDACCESS GENERATE option is used, issue the dsmnotes change command with appropriate parameters to create a password file. Refer to the user's guide of the corresponding platform for the correct syntax to use.

Explanation: An active restore operation is being processed.

System Action: Processing stops.

User Response: Wait for the active restore operation to complete before starting a second one.

Explanation: The syntax of the dsmnotes change command is incorrect.

System Action: Processing stops.

User Response: Use correct syntax. Refer to the user's guide of the corresponding platform for the correct syntax.

Explanation: The ITSM password has been changed successfully.

System Action: The program completes successfully.

User Response: None.

Explanation: An attempt was made to overwrite valid data in the buffer.

System Action: Processing stops.

User Response: Check the integrity of the database by opening it in the Lotus Notes workspace. If the database opens successfully, reissue the command. If the error is persistent, contact the IBM technical support.

Explanation: A database name is not allowed with this command.

System Action: Processing stops.

User Response: Remove the database name and reissue the command.

Explanation: A filespace name is not allowed with this command.

System Action: Processing stops.

User Response: Remove the filespace name and reissue the command.

Explanation: A wrong version of Tivoli Storage Manager data protection application client is being used.

System Action: Processing stops.

User Response: Check the Tivoli Storage Manager data protection application client Readme file to verify if the installed Tivoli Storage Manager data protection application client supports the current version of Lotus Notes on your workstation. Uninstall the current version of Tivoli Storage Manager data protection application client. Then reinstall and be sure to select the correct version of Tivoli Storage Manager data protection application client during the installation.

Explanation: The Tivoli Storage Manager data protection application client's log file is being processed.

System Action: Program continues.

User Response: None.

Explanation: One or more parameters are required.

System Action: Processing stops.

User Response: Refer to the user's guide of the corresponding platform for the correct number of parameters. Enter the correct number of parameters and reissue the command.

Explanation: Too many parameters were passed to the command.

System Action: Processing stops.

User Response: Refer to the user's guide of the corresponding platform for the correct number of parameters. Enter the correct number of parameters and reissue the command.

Explanation: An invalid parameter is entered.

System Action: Processing stops.

User Response: Correct the invalid parameter. Reissue the command.

Explanation: The Tivoli Storage Manager data protection application client's log file is not entered.

System Action: Processing stops.

User Response: Enter a fully qualified Tivoli Storage Manager data protection application client log file, then reissue the command.

Explanation: The Lotus Notes log database is not entered.

System Action: Processing stops.

User Response: Enter the Lotus Notes log database (usually log.nsf). Refer to the user's guide of the corresponding platform for further information.

Explanation: The specified log database cannot be opened.

System Action: Processing stops.

User Response: Verify the path name of your log database. If the path name is correct, verify the log database itself to ensure that it can be opened through the Notes workspace.

Explanation: The program cannot verify that the input log database is a valid database.

System Action: Processing stops.

User Response: Verify the path name of your log database. If the path name is correct, then verify the log database itself to ensure that it can be opened in the Notes workspace.

Explanation: An invalid database has been specified.

System Action: Processing stops.

User Response: Verify the path name of your log database. If the path name is correct, verify the log database itself to ensure that it can be opened in the Notes workspace.

Explanation: An I/O error occurred when an attempt was made to close the Tivoli Storage Manager data protection application client's log file.

System Action: Processing stops.

User Response: Check the access permission on the Tivoli Storage Manager data protection application client's log file.

Explanation: An I/O error occurred when an attempt was made to delete the Tivoli Storage Manager data protection application client's log file.

System Action: Processing stops.

User Response: Check the access permission on the Tivoli Storage Manager data protection application client's log file.

Explanation: The program is not able to interpret the first date/time stamp in the Tivoli Storage Manager data protection application client's log file. The first date/time stamp format either does not match the date/time stamp format of your operating system, or it is corrupted.

System Action: Processing stops.

User Response: For consistency reason, the date/time stamp format of the log file must match the date/time stamp format of your operating system. Check the locale of your operating system to ensure that you have matching date/time stamp formats.

Explanation: The program is not able to interpret the last date/time stamp in the ITSMConnect Agent's log file. The last date/time stamp format either does not match the date/time stamp format of your operating system, or it is corrupted.

System Action: Processing stops.

User Response: For consistency reason, the date/time stamp format of the log file must match the date/time stamp format of your operating system. Check the locale of your operating system to ensure that you have matching date/time stamp formats.

Explanation: One of the records in the Tivoli Storage Manager data protection application client is too large, or there is no carriage return character in the log file.

System Action: Program continues.

User Response: If the command is successful, check the log database to ensure that the correct record was added to the database. If the command fails, verify that the data in the Tivoli Storage Manager data protection application client's log file is valid.

Explanation: An I/O error occurred when an attempt was made to open the Tivoli Storage Manager data protection application client's log file.

System Action: Processing stops.

User Response: Verify the path name of the log file. Also Check the access permission on the log file.

Explanation: An I/O error occurred when an attempt was made to close the log database.

System Action: Processing stops.

User Response: Check the access permission on the log database.

Explanation: The Tivoli Storage Manager data protection application client's log file has been successfully written to the log database.

System Action: The program completes successfully.

User Response: None.

Explanation: The Tivoli Storage Manager data protection application client's log file was not written to the log database due to error.

System Action: Processing stops.

User Response: Check the error messages that preceded this message.

Explanation: The Tivoli Storage Manager data protection application client's log file was deleted because the "-d" option was used.

System Action: The program completes successfully.

User Response: None.

Explanation: The user has used the option "-d" but the Tivoli Storage Manager data protection application client's log file was NOT deleted due to error.

System Action: Processing stops.

User Response: Check the error messages that preceded this message.

Explanation: You specified a communication method that is not supported.

System Action: Processing stopped.

User Response: Specify a valid communication interface for the ITSM client and your operating system.

Explanation: User specified to back up system volume only. This volume was not backed up since this volume is not a system volume.

System Action: Volume was not backed up.

User Response: Use All option or use image backup command to backup this volume.

Explanation: Mini Operating System image is beging created. It may take a while to create it.

System Action: ITSM is gathering necessary information.

User Response: None.

Explanation: An attempt to start backup for remote node failed.

System Action: Backup fails.

User Response: Retry the operation. If the problem persists, contact the server administrator.

Explanation: Node has exceeded max tape mounts allowed. The operation will be tried again later.

System Action: The operation will be retried.

User Response: Increase the number of allowed tape mounts for this node on the server to avoid this situation again.

Explanation: An attempt to receive data using TCP/IP connection failed. If reason : 'Connection reset by peer', it is possible that the server control connection timed out. This can occur if the file transfer time is greater than the IDLETIMEOUT value set on the server.

System Action: TCP/IP connection to server fails.

User Response: If the timeout was due to a large file transfer time, you can ignore this message. The client will reconnect with the server automatically, finish transferring the data, and send statistics. You can also consider increasing the IDLETIMEOUT value in the server options file.

Explanation: An attempt to send data using TCP/IP connection failed.

System Action: Connection to server fails.

User Response: Retry the operation. If the problem persists, contact your system administrator.

Explanation: The management class for this file (object-name) did not have a backup copy group specified.

System Action: TSM did not back up the file.

User Response: See your system administrator.

Explanation: The management class for this file (object-name) did not have an archive copy group specified.

System Action: TSM did not back up the file.

User Response: See your system administrator.

Explanation: The client encountered an error while obtaining the automatic include/exclude statements from the operating system.

System Action: Processing continues without the full list of operating system include/exclude statements.

User Response: Please report the error to your service representative.

Explanation: The file or directory being restored or retrieved from the server cannot be written to because the destination file system does not support performed operation.

System Action: File skipped.

User Response: Restore the file to another location.

Explanation: The backup or archive operation completed, but no files were processed. Possible reasons for this include:

The directory that was backed up or archived contains no files

The files are excluded from backup or archive

System Action: None

User Response: Check the path you entered.

Explanation: An attempt to connect to the server using TCP/IP communications failed. This error can occur if the LAN connection went down or if your system administrator canceled a backup operation.

System Action: Session rejected. Processing stopped.

User Response: Retry the operation, or wait until the server comes back up and retry the operation. If the problem continues, see your system administrator for further help.

Explanation: The port specified by the TCPCLIENTPORT option is in use by a different process.

System Action: Processing stopped.

User Response: Contact the server administrator to set up a different port for server-initiated connections. Update the TCPCLIENTPORT with this new port number.

Explanation: An error occurred while opening the volume for backup/restore operations.

System Action: The requested logical volume operation is not performed.

User Response: Re-try the operation, check error log for more information. Make sure the volume is available and is not exclusively locked by a different process.

Explanation: The request to cancel a remote operation has failed. The node, filespace, operation and reason for the failure are shown.

System Action: ITSM operation not cancelled.

User Response: Contact your system administrator for more information.

Explanation: Your node name is associated with a different type of operating system (such as OS/2 or AIX) and cannot be used on this system.

System Action: ITSM canceled the current operation.

User Response: If you need a new node name, see your system administrator to assign a new one to you. Generally, you have a unique node name for each machine and operating system pair that requires access to the server.

Explanation: The 32-Bit Windows Sockets DLL WSOCK32.DLL could not be located

System Action: Communications link is not established. Session rejected.

User Response: See your system administrator.

Explanation: Authentication failure. You entered an incorrect password.

System Action: ITSM canceled the current operation.

User Response: Enter your correct password. If you cannot remember the correct password, see your system administrator to have a new one assigned for your node name.

Explanation: Communications protocol error. An unexpected communications message was received by the client.

System Action: ITSM canceled the current operation.

User Response: Verify that your communication path is functioning properly. If the problem continues, have your service representative check for a possible program error.

Explanation: An unexpected program failure occurred.

System Action: Processing stopped.

User Response: Retry the operation. If the problem continues, see your system administrator or your service representative.

Explanation: Communications with the server dropped.

System Action: Processing stopped.

User Response: Restart the ITSM client and retry the operation.

Explanation: ITSM cannot allocate storage for the specified operation.

System Action: ITSM cannot complete the requested operation.

User Response: Stop ITSM, restart ITSM, and retry the operation. If unsuccessful, close all unneeded applications and retry the operation. For UNIX systems that support resource limits, you can check if the memory resource limit is too low by entering the following command: ulimit -a Based on the resulting data, you can ask the UNIX system root user to increase resource limits so that it will override the current default. The UNIX system root user has the authority to increase resource limits.

Explanation: The attempt to establish a TCP/IP connection timed out before the connection was made.

System Action: Processing stopped.

User Response: Check for a networking problem. If the problem continues, see your system administrator. API applications should close the session with dsmTerminate.

Explanation: An attempt to establish a TCP/IP connection was rejected by the server.

System Action: Processing stopped.

User Response: The server was not fully initialized, is not currently running, was not enabled for TCP/IP communications, or an incorrect TCP/IP port number was specified. If the problem continues, see your system administrator.

Explanation: An invalid TCP/IP host name or address was specified.

System Action: Processing stopped.

User Response: Check your options file for the correct TCPSERVERADDRESS statement. See your administrator for the correct name of the server.

Explanation: The TCP/IP host name specified in the TCPSERVERADDRESS statement cannot be reached.

System Action: Processing stopped.

User Response: Check your options file for the correct TCPSERVERADDRESS statement. See your administrator for the correct name of the server.

Explanation: The options file specified by file-name cannot be found.

System Action: The ITSM client ends.

User Response: See if you have the environment variable DSM_CONFIG (or DSMI_CONFIG for the API) set, which explicitly identifies the ITSM options file. ( You can do this by entering the SET command at your system.) If this environment variable is set, ensure the file indicated by the variable exists. If it is not set, then ITSM looks for the file dsm.opt in the current directory. If neither of these cases is met, you receive this error message.

Explanation: The specified option in the ITSM options file (file-name) is in error.

System Action: Processing stopped.

User Response: Correct the options file entry.

Explanation: ITSM found an incorrect keyword in the options file.

System Action: Processing stopped.

User Response: Correct the options file with valid entries.

Explanation: An incorrect option was specified to ITSM.

System Action: Processing stopped.

User Response: Correct the options used for running ITSM.

Explanation: The include or exclude pattern issued is too complex to be accurately interpreted by ITSM.

System Action: Processing stopped.

User Response: Recode the include or exclude pattern as shown in one of the examples in the appropriate Using the Backup-Archive Client book for the particular operating system.

Explanation: The include or exclude pattern is incorrectly constructed. The closing bracket is missing.

System Action: Processing stopped.

User Response: Correct the syntax for the pattern.

Explanation: The include or exclude pattern must start with a directory delimiter.

System Action: Processing stopped.

User Response: Correct the syntax for the pattern.

Explanation: The include/exclude pattern has a '...' without a beginning or ending directory delimiter.

System Action: Processing stopped.

User Response: Correct the syntax for the pattern.

Explanation: The quotes specified in the pattern are not the same and do not make a set.

System Action: Processing stopped.

User Response: Correct the pattern by using matching quotes in the syntax.

Explanation: The specified environment-name in the options file is invalid.

System Action: ITSM attempts to continue the current operation.

User Response: Check the environment variable in the options file and use a valid environment variable. Retry the operation.

Explanation: Incorrect syntax is specified in the options file. Make sure that the variable is enclosed in curly braces.

System Action: ITSM attempts to continue the current operation.

User Response: Check the syntax of environment variable in the options file. Correct it and retry the operation.

Explanation: Environment variable expanded to a string which is too long. Make sure that the string is no more than 1023 characters long.

System Action: ITSM attempts to continue the current operation.

User Response: Check the length of environment string and break it up into smaller strings using multiple environment variables.

Explanation: Trying to restore or retrieve to a destination that cannot be reached. The specified file space name or drive letter is not valid, does not exist, or you are specifying a local share name that cannot be resolved.

System Action: Processing stopped.

User Response: Retry the command and specify a different destination.

Explanation: The selected path is not a local device and therefore is not a valid object for image operations.

System Action: The requested logical volume operation is not performed.

User Response: Choose another object.

Explanation: The filename you specified is not a valid name for a file or it is a directory.

System Action: Restore processing stopped.

User Response: Specify a correct filename for image restore.

Explanation: Only single-byte characters are allowed in an include/exclude list; you cannot use a double-byte character set (DBCS).

System Action: Processing stopped.

User Response: Remove the double-byte characters from the include/exclude list and retry the operation.

Explanation: You entered an invalid password.

System Action: ITSM cannot connect to the server without the correct password.

User Response: Enter the password, or ask your system administrator for the correct password.

Explanation: You cannot connect directly to the Storage Agent.

System Action: Processing stopped.

User Response: To perform Lanfree operations using the Storage Agent, specify the ENABLELANFREE option in your options file, and restart the process.

Explanation: The existing filespace name using the volume label has been renamed to the UNC format naming convention.

System Action: Processing continues.

User Response: None.

Explanation: Unable to rename the existing filespace name using the volume label to the UNC format naming convention.

System Action: Processing stopped.

User Response: None.

Explanation: Trying to rename the existing filespace name using the volume label to the UNC format naming convention but the drive letters do not match. Leave the existing filespace alone and create a new filespace.

System Action: Processing continues.

User Response: None.

Explanation: For backup: Trying to backup share/network, which either does not exist or does not have the correct privilege to access the share. For restore : Trying to restore to a share/network path that cannot be resolved. The directory path does not exist.

System Action: Processing stopped.

User Response: Retry the command and specify a destination, or restore the directory tree first before trying to restore the share point.

Explanation: Trying to rename the existing filespace name using the volume label to the UNC format naming convention but both filespaces exists. Leave the existing filespace alone and backup to the new filespace.

System Action: Processing continues.

User Response: None.

Explanation: Trying to restore to destination that cannot be reached. Either the drive letter is not valid, or you are specifying a local share name that cannot be resolved.

System Action: Processing stopped.

User Response: Retry the command and specify a different destination.

Explanation: You selected more than one inactive version of the same image object (logical volume). The system has no way to decide which you want to restore.

System Action: The requested logical volume restore is not performed.

User Response: Retry the operation, selecting an active version or only one inactive version of the volume you wish to restore.

Explanation: You entered a file system name that does not correspond to a mounted file system for this system. It is possible the file system name is misspelled, or simply that the file system is not currently mounted.

System Action: The requested logical volume operation is not performed.

User Response: Retry the operation, using name of a mounted file system.

Explanation: You entered a logical device name that is mapped to a mounted file system. This volume must only be referenced by its file system name.

System Action: The requested logical volume operation is not performed.

User Response: Retry the operation, using the file system name.

Explanation: You selected more than one image object (logical volume) to be restored. You also specified a destination. The system cannot place more than one image into a single destination volume. When more than one object is selected, each must be restored to its original location.

System Action: The requested logical volume restore is not performed.

User Response: Retry the operation, selecting one object to be restored to the given destination, or retry the operation without entering the destination.

Explanation: The path specified is not a valid file-system or logical volume name.

System Action: The requested logical volume operation is not performed.

User Response: Retry the operation, using a valid path.

Explanation: An error occurred in the image utility internals.

System Action: The requested logical volume operation is not performed.

User Response: Contact your ITSM administrator.

Explanation: The current system has a mix of installed components.

System Action: The requested logical volume operation is not performed.

User Response: Re-install all ITSM components

Explanation: The file system was successfully restored, but the attempt to re-mount it failed.

System Action: The file system is left unmounted.

User Response: Use the mount command to mount the file system. On AIX, run fsck if requested by the operating system.

Explanation: An error occurred during a system call, check the error log for more information.

System Action: The requested logical volume operation is not performed.

User Response: Check error log.

Explanation: The selected path is not a local device and therefore is not a valid object for image operations

System Action: The requested logical volume operation is not performed.

User Response: Choose another object.

Explanation: An error occurred while reading data from the device. Windows Only: This could be due to bad sectors on the drive.

System Action: The requested logical volume operation is not performed.

User Response: Retry the operation, then check the error log for more information. Windows Only: Please run chkdsk /r and retry the operation. If the problem persists, a possible workaround is to back up the entire drive using a regular (non-image) backup. Please ensure that all your data is backed up. Then format the drive using a full format (without the /q quick format option). Then restore the data and retry the image backup operation.

Explanation: An error occurred while writing data to the device.

System Action: The requested logical volume operation is not performed.

User Response: Re-try the operation, check error log for more information.

Explanation: You entered an invalid domain-name.

System Action: Processing stopped.

User Response: Enter a valid drive or file system name (domain).

Explanation: The specified drive-name in the domain list does not have a volume label.

System Action: Processing stopped.

User Response: Use the system format utility to place a unique volume label on all drives on which you intend to run ITSM.

Explanation: The number defining the correspondence between drive letter or file (domain name) and volume label is not known to the server.

System Action: Processing stopped.

User Response: Report the program error to your service representative.

Explanation: An abort signal to stop an operation was received.

System Action: Processing stopped.

User Response: Continue with normal operations.

Explanation: IBM Tivoli Storage Manager has encountered a condition where it can not allocate any more memory. Possible reasons include:

The system is low on memory.

The process in which the program runs has exceeded the maximum memory that it is allowed to allocate.

Some other error condition occurred that caused the program to think it is out of memory.

System Action: Processing stopped.

User Response: Stop any unnecessary programs that are running and retry the operation. Reducing the scope of queries and the amount of data returned can also solve the problem. If the error reoccurs, contact your support representative, and be sure to provide the entire text of this message along with detailed information about how you got this message.

Explanation: You specified an incorrect directory path.

System Action: Processing stopped.

User Response: Correct the syntax specified and retry the operation.

Explanation: An unknown and unexpected error-code occurred within the client program. This is a programming failure and the client program ends.

System Action: Processing stopped.

User Response: Retry the operation. If the problem continues, see your administrator.

Explanation: You did not enter a file specification as prompted.

System Action: ITSM did not continue with the requested operation.

User Response: Enter a file specification to continue.

Explanation: You entered a file specification or search string that contains incorrect characters or contains wildcard characters in the drive specification or file system name.

System Action: Processing stopped.

User Response: Enter a correct file specification as described in the appropriate Using the Backup-Archive Client book for the particular operating system.

Explanation: You entered a destination file-name specification that contains incorrect characters or has wildcard characters in the specification.

System Action: Processing stopped.

User Response: Enter a correct file specification as described in the appropriate Using the Backup-Archive Client book for the particular operating system.

Explanation: You tried to retrieve files when no files for the specified drive or file system (filespace-name) were previously archived.

System Action: Processing stopped.

User Response: Ensure that the correct drive or file system was specified and that files are archived for you to retrieve.

Explanation: You tried to restore files when no files for the specified drive or file system (filespace-name) were previously backed up.

System Action: Processing stopped.

User Response: Ensure that the correct drive or file system was specified and that files are backed up for you to restore.

Explanation: Not enough memory was available for the operation.

System Action: Processing stopped.

User Response: Retry the operation or restart the system with fewer programs in memory.

Explanation: The file being processed for backup, archive or migrate no longer exists on the client. Another process deleted the file before it could be backed up, archived or migrated by ITSM.

System Action: File skipped.

User Response: None.

Explanation: Access to the specified file or directory is denied. You tried to read from or write to a file and you do not have access permission for either the file or the directory.

System Action: Processing stopped.

User Response: Ensure that you specified the correct file or directory name, correct the permissions, or specify a new location.

Explanation: The specified file space (domain) is incorrect or does not exist on the machine.

System Action: Processing stopped.

User Response: Retry the operation specifying an existing domain (drive letter or file system name).

Explanation: The path name specified plus the path name in the restored file name combine to create a name whose length exceeds the system maximum.

System Action: Processing stopped.

User Response: Specify a destination path that, when combined, is less than the system maximum.

Explanation: ITSM tried to create a directory path-name, but is unable to because a file exists that has the same name as a directory.

System Action: Processing stopped.

User Response: Remove the file that has the same name as the directory. Refer to the given failing path, and either remove or move the file that caused this problem and restart the restore/retrieve operation.

Explanation: An unexpected communications error occurred during an object query to the server.

System Action: Processing stopped.

User Response: Verify that communications are active between the client and server machines. Server outages, processor outages, and communication controller outages can cause this error.

Explanation: You entered a search pattern or file name that cannot be found in the server database.

System Action: Processing stopped.

User Response: Ensure that your search pattern is correct, or specify a new search string.

Explanation: The server to which you are connected, does not support point in time values.

System Action: Processing stopped.

User Response: Enter the command without specifying the point in time option.

Explanation: The server to which you are connected does not support Query Node command.

System Action: Processing stopped.

User Response: Use a TSM Server that supports Query Node command.

Explanation: Either no Active Policy Set data was found on the server or a fromnode option contained a nodename not found on the server.

System Action: Processing stopped.

User Response: See your system administrator.

Explanation: The Help facility cannot read the help text file.

System Action: Processing stopped.

User Response: Make sure the DSM_DIR environment variable points to the correct directory containing the current level of ITSM program files.

Explanation: The program used all available storage.

System Action: Processing stopped.

User Response: Free any unnecessary programs (TSRs) that are running, and retry the operation. Reducing the scope of queries and the amount of data returned can also solve the problem.

Explanation: You tried to give access to a file, which is not stored on the server.

System Action: Processing stopped.

User Response: Ensure that the correct filename is specified.

Explanation: You tried to give access to a file, which is not stored on the server.

System Action: Processing stopped.

User Response: Ensure that the correct filename is specified.

Explanation: The user is not authorized to decrypt the file; the user cannot restore the file. Only a TSM Authorized user or a root user can decrypt and restore the file.

System Action: The file is not restored.

User Response: Contact your system administrator to restore the file.

Explanation: This command processing routine received more operands than it can use. Query can contain only one file specification. Restore and Retrieve can contain two file specifications. Archive, Delete, and Selective can contain a maximum of 20 file specifications.

System Action: Processing stopped.

User Response: Reduce the number of arguments and retry the operation. For UNIX-based systems, ensure that you do not omit the quotes around pattern matching characters.

Explanation: You entered an invalid management class.

System Action: ITSM is unable to do the requested operation.

User Response: Retry the operation using a valid management class.

Explanation: The management class for this file does not have an archive copy group specified. This file will not be archived.

System Action: Processing stopped.

User Response: Add a valid archive copy group to the management class, and then retry the operation.

Explanation: The management class for this file does not have a backup copy group specified. This file will not be backed up.

System Action: Processing stopped.

User Response: Add a valid backup copy group to the management class, and then retry the operation.

Explanation: This message is issued for TSM Authorized Users and root users when ENCRYPTKEY SAVE and PASSWORDACCESS PROMPT options are set. Please note that these are the default values. These values do not allow encryption.

System Action: The file is not encrypted.

User Response: To save encryption keys, you must change configuration values. Add PASSWORDACCESS GENERATE to your system option file.

Explanation: You specified an incorrect ITSM option option.

System Action: Processing stopped.

User Response: Specify a correct ITSM option as defined in the appropriate Using the Backup-Archive Client book for the particular operating system.

Explanation: The option option was specified for a command or subcommand (function) that cannot make use of that option.

System Action: Processing stopped.

User Response: See the appropriate Using the Backup-Archive Client book for your operating system for correct use of the named option.

Explanation: The user is not authorized to decrypt the file; the user cannot restore the file. Only a TSM Authorized user or a root user can decrypt and restore the file.

System Action: The file is not restored.

User Response: Contact your system administrator to restore the file.

Explanation: The Help facility cannot find the help file file-name.

System Action: Processing stopped.

User Response: Ensure that the DSM_DIR environment variable points to the correct directory containing the current level of ITSM program files.

Explanation: The Help facility cannot read the help text file, or the file is corrupted.

System Action: Processing stopped.

User Response: Make sure the DSM_DIR environment variable points to the correct directory containing the current level of ITSM program files, and that the files are intact.

Explanation: The snapshot cache location must point to a local volume that is formatted. It can not be on the same volume which is being backed up; the default cache location is on the system drive.

System Action: The client does not execute the snapshot backup operation.

User Response: Specify a different snapshot cache location using the SNAPSHOTCACHELOCATION option.

Explanation: The server is waiting for the requested media to become available before the operation can continue.

System Action: ITSM waits for requested data.

User Response: None.

Explanation: You tried to back up or migrate a file (file-name) that was specified to be excluded from backup.

System Action: ITSM did not back up or migrate the file.

User Response: Specify the file using the Include option and retry the operation.

Explanation: Unable to read commands entered from keyboard. ITSM cannot process your intended command.

System Action: Processing stopped.

User Response: Ensure that you are entering a correct command.

Explanation: During a restore, PICK and LATEST options cannot be used together.

System Action: Processing stopped.

User Response: Try again using either the PICK or the LATEST option.

Explanation: The number that represents a file space was incorrect while you were using the PICK option.

System Action: ITSM waits for your specification.

User Response: Enter a correct file space number.

Explanation: Indicates that file space deletion has started on the specified filespace-name.

System Action: None.

User Response: None.

Explanation: Deletion of the specified filespace-name failed.

System Action: Processing stopped.

User Response: Try again. If the problem continues, see your system administrator to delete the file space for you.

Explanation: ITSM successfully deleted the specified filespace-name.

System Action: None.

User Response: None.

Explanation: The specified filespace-name does not exist on the server. Your system administrator deleted the file space or another client using your client's node name might have deleted it.

System Action: None.

User Response: None.

Explanation: Execution of the HELP command requires space for both the user prompts and at least one line of the HELP directory.

System Action: The help directory is not displayed, and the help command cannot complete.

User Response: Increase the size of your display window to allow more rows of text to be displayed.

Explanation: The quotes specified in the pattern are not the same and do not make a set.

System Action: Processing stopped.

User Response: Correct the pattern using matching quotes in the syntax.

Explanation: During a delete filespace operation, you specified a file space to which your node does not have permission to delete archived data and/or backed up data.

System Action: Delete processing fails.

User Response: See your system administrator.

Explanation: Your node is not allowed by the server to delete archived files.

System Action: ITSM did not delete the archived files.

User Response: See your system administrator.

Explanation: An invalid management class was assigned to directories.

System Action: Processing stopped.

User Response: Have your service representative check the error log.

Explanation: The management class used for directories does not have a backup copy group.

System Action: Processing stopped.

User Response: Have your service representative check the error log.

Explanation: The selected drive does not have a label.

System Action: ITSM is unable to do the requested operation without a drive or label entered.

User Response: If the drive is a floppy drive, place a disk with a volume label in it and retry the operation. If the disk is a hard drive, ensure the drive has a volume label, and retry the operation.

Explanation: The selected drive has a duplicate volume label. Because ITSM uses the volume label to keep track of backup/archive information, it cannot back up or archive files from a drive with a duplicate volume label.

System Action: ITSM cannot select the drive.

User Response: If the volume needs to be available to the system, exit ITSM, and assign a volume label to the drive. Restart ITSM and retry the operation.

Explanation: You are trying to define authorization for the specified node, which already has authorization defined.

System Action: ITSM did not redefine authorization for the specified node.

User Response: Update the authorization, or delete the old rule and define a new one, or use the current authorization.

Explanation: ITSM cannot process the command because a UNIX shell expands a wildcard expression, for example, asterisk (*) or question mark (?), that has no quotes.

System Action: Command dependent.

User Response: Enclose the wildcard expression in quotes and enter the command.

Explanation: The specified drive-name was found to be invalid; the drive probably has not been defined.

System Action: ITSM skips the invalid drive and continues to the next drive.

User Response: Check the invalid drive.

Explanation: The drive-name1 was found to be a substitute (SUBST) of another drive-name2. It is not available for backup/archive.

System Action: ITSM skips the SUBST drive and continues to the next drive.

User Response: None.

Explanation: The file cannot be backed up because the client is not the file owner.

System Action: ITSM skips the file.

User Response: None.

Explanation: An incorrect number was entered for the Index.

System Action: Processing stopped.

User Response: Correct the Index entry and retry the operation.

Explanation: You entered an incomplete command-name.

System Action: Processing stopped.

User Response: Enter the correct syntax of the command and continue.

Explanation: Post restore processing failed due to an internal system error.

System Action: Please see error log for more details.

User Response: Please see your system administrator for assistance.

Explanation: None.

System Action: Processing stopped.

User Response: Enter the SET ACCESS command using the correct syntax.

Explanation: You entered an incorrect command-name.

System Action: None.

User Response: Enter the correct command.

Explanation: The DIRSONLY and FILESONLY options cannot be used together.

System Action: Processing stopped.

User Response: Try again using either the DIRSONLY or the FILESONLY option.

Explanation: None.

System Action: Processing stopped.

User Response: Because password authentication is turned off on the server, you do not need to update the password.

Explanation: Too many levels of macro nesting are encountered.

System Action: The macro is ignored and an error is returned.

User Response: Reduce the level of macro nesting.

Explanation: A macro command has been entered that specifies the macro file name shown. However, that file cannot be opened for reading.

System Action: The macro is ignored and an error is returned.

User Response: Enter the command with the proper macro name.

Explanation: File is temporarily unavailable.

System Action: File skipped.

User Response: Check and see if file is locked by other process. If not, retry the command.

Explanation: The specified command-name was successfully completed.

System Action: ITSM completed the command.

User Response: Continue with normal operations.

Explanation: An incremental backup was started, but no domain was selected.

System Action: Processing stopped.

User Response: Choose a domain and restart the incremental backup.

Explanation: The local system account does not have a profile. Therefore you cannot restore its profile.

System Action: Processing stops.

User Response: Log on to the user whose profile you want to restore.

Explanation: The drive-name1 is not a cluster disk. Backup/archive is not allowed when the CLUSTERNODE option is set to YES.

System Action: Processing stops.

User Response: Set CLUSTERNODE option to NO, then backup/archive the drive. Otherwise, you cannot backup/archive the drive.

Explanation: The filespace is not a cluster disk. Backup/archive is not allowed when the CLUSTERNODE option is set to YES.

System Action: Processing stops.

User Response: Set CLUSTERNODE option to NO, then backup/archive the drive. Otherwise, you cannot backup/archive the drive.

Explanation: The drive-name1 is a cluster disk. Backup/archive is not allowed when the CLUSTERNODE option is set to NO.

System Action: Processing stops.

User Response: Set CLUSTERNODE option to YES, then backup/archive the drive. Otherwise, you cannot backup/archive the drive.

Explanation: The filespace is a cluster disk. Backup/archive is not allowed when the CLUSTERNODE option is set to NO.

System Action: Processing stops.

User Response: Set CLUSTERNODE option to YES, then backup/archive the drive. Otherwise, you cannot backup/archive the drive.

Explanation: When ITSM is running as a cluster node, the nodename cannot be the local machine name.

System Action: Processing stops.

User Response: Change the nodename either to the cluster name or to any other name, and restart ITSM.

Explanation: When running as a cluster node, registry cannot be backed up or restored.

System Action: Processing continues.

User Response: None.

Explanation: When running as a cluster node, event logs cannot be backed up or restored.

System Action: Processing continues.

User Response: None.

Explanation: The specified file is being used by another process. You tried to read from or write to a file that is currently being used by another process.

System Action: Processing stopped.

User Response: Ensure that you specified the correct file or directory name, correct the permissions, or specify a new location.

Explanation: The system call to mount the file system failed.

System Action: The file system remains unmounted.

User Response: Use the mount command to mount the file system. On AIX, run fsck if requested by the operating system.

Explanation: The system call to unmount the file system failed.

System Action: The logical volume operation is not performed.

User Response: Make sure the device or file system is not being accessed, then retry the operation.

Explanation: The named file system is not currently mounted. It must be mounted for ITSM to perform an image backup.

System Action: The logical volume operation is not performed.

User Response: Mount the file system.

Explanation: The space allocation for the selected destination is smaller than the source.

System Action: The restore operation is not performed.

User Response: Choose a different, bigger destination or increase the size of the destination file space.

Explanation: The source and destination file system types do not match.

System Action: The requested logical volume operation is not performed.

User Response: Choose a destination that has the same file system type as the source.

Explanation: Creation of the image object failed for one of the following reasons:

• The image command was executed by a non-root user
• The image plugin library was not found.

User Response: Retry the operation after correcting the cause for failure.

System Action: The requested logical volume function is not performed.

Explanation: The image item for which a table of contents was requested is either a RAW logical volume or it was backed up without the -TOC option.

System Action: No table of contents is displayed.

User Response: Select another image object for TOC display.

Explanation: You entered a number not shown in the list of images. It is either less than one or greater than the highest item number displayed.

System Action: ITSM waits for you to enter a valid selection.

User Response: Enter a number from the list or 'Q' to quit.

Explanation: A path must be specified for this operation to execute successfully.

System Action: Processing stops.

User Response: Specify a valid path and execute the command again.

Explanation: An error occurred using named pipe communication with the journal service.

System Action: Processing stops.

User Response: Attempt to restart the service and retry the backup. If the journal service is not running, a non-journaled backup will proceed.

Explanation: An unknown error occurred while processing a system object. The error information captured indicates the reason for the failure. This information can be used to diagnose the problem.

System Action: ITSM ended the current operation.

User Response: Contact your system administrator for more information.

Explanation: The command subcommand command is not supported for the client running on this operating system on this computer.

User Response: None.

System Action: The command is not processed.

Explanation: The ITSM server that the ITSM client has opened a session with is not capable of server-free data movement, either because it is not supported by the server's level or platform, or because the appropriate license is not installed on the server.

System Action: The operation is retried using LAN-free (if available) or LAN-based data movement.

User Response: Remove the ENABLESERVERFREE option from the system option file.

Explanation: Due to the nature of HSM, image backup is not allowed on managed filesystems.

System Action: The requested logical volume operation is not performed.

User Response: None.

Explanation: The DIRSONLY and V2ARCHIVE options cannot be used together.

System Action: Processing stopped.

User Response: Try again using either the DIRSONLY or the V2ARCHIVE option.

Explanation: Log 'linkname' cannot be a symbolic link.

System Action: The symbolic link 'linkname' is deleted, the log is recreated, and processing stops.

User Response: Check the location of the new file. To specify the location of log files, refer to the user's manual for the 'errorlogname' option, the 'schedlogname' option, and the 'DSM_LOG' environmental variable.

Explanation: Log 'linkname' cannot be a symbolic link.

System Action: Processing stops.

User Response: Delete the symbolic link 'linkname'.

Explanation: Error log 'linkname' cannot be a symbolic link.

System Action: The symbolic link 'linkname' is deleted, the error log is recreated, and processing stops.

User Response: Check the location of the new error log. To specify the location of the error logs, refer to the user's manual for the 'errorlogname' option and 'DSM_LOG' environmental variable.

Explanation: Trace file 'linkname' cannot be a symbolic link.

System Action: The symbolic link 'linkname' is deleted, the trace file is recreated, and processing stops.

User Response: Specify the trace file location with the 'tracefile' option.

Explanation: Schedule log 'linkname' cannot be a symbolic link.

System Action: The symbolic link 'linkname' is deleted, the schedule log is recreated, and processing stops.

User Response: Check the location of the new schedule log. To specify the location of the schedule log, refer to the user's manual for the 'schedlogname' option.

Explanation: During the image snapshot backup ITSM encountered an error while opening or reading the old-blocks index file.

System Action: Processing stopped.

User Response: Contact your ITSM administrator.

Explanation: During the image snapshot backup ITSM encountered an error while opening or reading the old-blocks data file.

System Action: Processing stopped.

User Response: Contact your ITSM administrator.

Explanation: The image snapshot backup was not able to complete because while creating the snapshot ITSM exceeded the snapshot cache size allowed via the SNAPSHOTCACHESize option.

System Action: Processing stopped.

User Response: Increase the SNAPSHOTCACHESize value for this volume and retry the operation.

Explanation: The SNAPSHOTCACHELocation option value entered for this volume is not valid. The value for this option must be an existing, full directory path.

System Action: Processing stopped.

User Response: Please enter a valid SNAPSHOTCACHELocation value and retry the operation.

Explanation: The command specified by the PRESNAPSHOTCMD option must complete successfully in order to execute the image snapshot backup. If the command completed with a return code of 0 (zero), it is considered to have completed successfully. If the command completed with any other return code, it is considered to have failed. If the command failed then the image snapshot backup is not executed.

System Action: The client does not execute the image snapshot backup operation.

User Response: Identify and repair the problem that caused the command to fail. If a non-zero return code is normal for this command, then consider wrapping the command in a script that always exits with a return code of zero.

Explanation: If the command specified by the POSTSNAPSHOTCMD option completed with a non-zero return code, then the image snapshot backup operation will continue, but with a warning-level result. Note that the result of the POSTSNAPSHOTCMD command will not supercede a higher result from the image snapshot backup command. For example, if the image snapshot backup command completed with a return code of 12, the image snapshot backup will be considered to have completed with a return code of 12, regardless of the outcome of the POSTSNAPSHOTCMD command.

System Action: The image snapshot backup continues, but with a warning return code of at least 8.

User Response: Identify and repair the problem that caused the command to fail. If a non-zero return code is normal for this command, then consider wrapping the command in a script that always exits with a return code of zero.

Explanation: ITSM tried to create a directory path, but is unable to because a file exists that has the same name as a directory.

System Action: Processing stopped.

User Response: Remove the file that has the same name as the directory. Refer to the last restore/retrieve operation and check all directories along the path.

Explanation: An error occurred during backup of the table of contents. Check the error log for more information.

System Action: The requested logical volume operation is not performed.

User Response: Check error log.

Explanation: An error occurred while deactivating the table of contents object.

System Action: Image backup was successful. But deactivating the TOC object from the previous backup failed.

User Response: Check error log.

Explanation: An error occurred while restoring the image. Check log file for more information.

System Action: Restore stops. The file system is not mounted back.

User Response: Check error log.

Explanation: An error occurred while backing up the image. Check log file for more information.

System Action: Backup stopped. The file system is not mounted back.

User Response: Check error log.

Explanation: TOC backup of a raw device is not supported. But the raw device is backed up.

System Action: Raw device is backed up with no TOC object.

User Response: NONE.

Explanation: The user is trying to query the TOC of a file system. TOC backup for that file system has not been previously done.

System Action: Query stopped.

User Response: Backup the file system again with -TOC option.

Explanation: Arguments list for ITSM program should not exceed maximum length characters.

System Action: The command is not processed.

User Response: Correct the command and retry the operation.

Explanation: You entered a number not shown in the list of processes. It is either less than one or greater than the highest item number displayed.

System Action: ITSM waits for you to enter a valid selection.

User Response: Enter a number from the list or 'Q' to quit.

Explanation: On Linux platform, snapshot image backup is only possible for logical volumes created by the Linux logical volume manager (LVM). The default image backup type is snapshot. Backing up a partition with snapshot image backup automatically leads to a static image backup. In this case this warning appears. To aviod this message please specify static image backup or dynamic image backup.

System Action: Snapshot image backup will failover to static image backup

User Response: None.

Explanation: On Linux platform, the snapshot is created in the same volume group like the logical volume on which it is made. In this volume group there must be enough free space for the snapshot. It is possible to change the size of the snapshot by using a different value for snapshotcachesize.

System Action: None.

User Response: Decrease the value for snapshotcachesize

Explanation: The snapshot cache location is on the same volume that is being backed up, but this is not allowed; The default cache location is on the system drive.

System Action: The client does not execute the image snapshot backup operation.

User Response: Specify a different snapshot cache location using the SNAPSHOTCACHELOCATION option.

Explanation: The system options file for the server that you are attempting to connect to contains a user entry, a group entry, or both a user and group entry. Your user ID, or group ID, was not found in any of the entries. You are currently not authorized to run ITSM to this server.

System Action: ITSM initialization fails and the program ends.

User Response: See the ITSM administrator for your system, and ask to be added to the user or group list for this server.

Explanation: The system options file does not contain the SERVERNAME option.

System Action: ITSM initialization fails and the program ends.

User Response: See the ITSM administrator for your system, and make sure that the system options file contains the server name.

Explanation: The TCPSERVERADDRESS for this server is not defined in the server name stanza in the system options file.

System Action: ITSM initialization fails and the program ends.

User Response: See the ITSM administrator for your system, and make sure that the server to which you are trying to connect, has a valid TCPSERVERADDRESS defined in the system options file.

Explanation: The NODENAME defined in the options file cannot be the same as the system HostName.

System Action: Initialization fails and the program ends.

User Response: See your system administrator or the root user.

Explanation: The server ran out of resources. A lack of storage or a condition does not allow any new activity.

System Action: ITSM canceled the current operation.

User Response: Retry the operation at a later time. If the problem continues, see your system administrator to isolate what resource is unavailable.

Explanation: The current transaction between the server and the client stopped. A server, client, or communication failure cannot be recovered.

System Action: ITSM canceled the current operation.

User Response: Retry the operation. If the problem continues, see your system administrator to isolate the problem.

Explanation: The disk space allocated for the client owner is full.

System Action: Processing stopped.

User Response: Free up disk space and retry the restore or retrieve operation.

Explanation: A file that was flagged as compressed was not compressed, and the system failed.

System Action: Processing stopped.

User Response: See your system administrator to report this problem. This error is a system failure.

Explanation: You are trying to restore a file that was backed up and compressed on another client workstation that had more memory than your client workstation. You cannot restore this file. When the file is restored, it is expanded and your workstation does not have enough memory.

System Action: ITSM canceled the operation.

User Response: Obtain a machine with more memory and retry the operation.

Explanation: Not enough memory is available to do data compression or expansion. For a restore or retrieve, the file cannot be recalled from the server until more storage is made available. For a backup or archive, try running without compression if storage cannot be made available.

System Action: Processing stopped.

User Response: Free up extra storage for the operation to continue, or run the backup or archive process without compression enabled.

Explanation: The file or directory being restored or retrieved from the server cannot be written to because the destination is write locked. Another operation might have the file open and will not allow it to be updated.

System Action: File skipped.

User Response: Either determine which operation has the file write locked, or restore the file to another name or location.

Explanation: No more files can be restored or retrieved because the destination disk is full.

System Action: Processing stopped.

User Response: Free up disk space, or restore or retrieve the file to another disk.

Explanation: The specified file (object-name) cannot be sent to the server.

System Action: File skipped.

User Response: Retry the operation. If the problem continues, see your system administrator to isolate the problem through use of the server console.

Explanation: Because the file space has been the subject of at least one progressive incremental backup, the MODE=INCREMENTAL option (incremental by image date) cannot be used with the backup image command.

System Action: File system skipped.

User Response: If an image backup of the named file space is desired, retry the command without the MODE=INCREMENTAL option. To prevent this behavior in the future, delete the file space from the server and do only BACKUP IMAGE -mode=selective and BACKUP IMAGE -mode=incremental from that point on.

Explanation: An NFS file system becomes stale.

System Action: File system skipped.

User Response: Check the NFS mounted filesystem.

Explanation: All file handles for your system are currently in use. No more are available.

System Action: Processing stopped.

User Response: Either free some file handles by ending other processes, or modify your system setup to allow for more files to be open at the same time.

Explanation: The file being restored or retrieved exists.

System Action: File is replaced or skipped depending on client options.

User Response: None.

Explanation: An internal system error occurred. A file operation failed because an invalid file handle was passed.

System Action: Processing stopped.

User Response: Report the problem to your system administrator, and then retry the operation.

Explanation: A communications protocol error occurred. The communication subsystem is not properly defined or is itself in error.

System Action: ITSM ended the current operation.

User Response: Verify that the communication processes are operating properly, and then retry the operation.

Explanation: An unknown error occurred. This might be a low-level system or communication error that ITSM cannot handle or recover from.

System Action: Processing stopped.

User Response: Retry the operation. If the problem continues, determine where the problem exists. See your system administrator for further help.

Explanation: An unexpected error occurred. This might be a low-level system or communication error that ITSM cannot handle or recover from.

System Action: Processing stopped.

User Response: Retry the operation. If the problem continues, determine where the problem exists. See your system administrator for further help.

Explanation: This is a server problem.

System Action: Processing stopped.

User Response: Have your service representative check the error log.

Explanation: Server problem. Invalid policy binding.

System Action: Processing stopped.

User Response: Have your service representative check the error log.

Explanation: The current file cannot be opened to write to because it is currently being run by another operation.

System Action: File skipped.

User Response: Stop the operation that is running the file and retry the operation, or restore or retrieve the file to a different name or directory.

Explanation: While trying to resolve the file name, too many symbolic links were found.

System Action: File skipped.

User Response: Ensure that you do not have a looping symbolic link for the file.

Explanation: The file name specified is too long to be handled by ITSM.

System Action: File is skipped.

User Response: See the appropriate Using the Backup-Archive Client book for the particular operating system, for the file names that are handled by ITSM.

Explanation: File system cannot be accessed because it is locked by the system.

System Action: ITSM cannot complete the operation.

User Response: See your system administrator.

Explanation: ITSM tried to restore or retrieve a file, but it had an unknown format.

System Action: File skipped.

User Response: See your system administrator.

Explanation: Command-line arguments may not exceed maximum length characters.

System Action: The command is not processed.

User Response: Correct the command and retry the operation.

Explanation: Restore request has been sent to the server. The wait time depends on how many files you are restoring.

System Action: ITSM waits for files to restore from the server.

User Response: None.

Explanation: Currently, there is an active restore for the same source file specification. Another restore of the same source file specification cannot be started.

System Action: The requested restore fails.

User Response: Start another restore with a different source file specification.

Explanation: The restart restore token has expired. The server cannot restart the restore from where it last ended.

System Action: Processing stopped; waiting for user intervention.

User Response: Retry the request without restart or abort the request.

Explanation: The file system/drive was not ready for access.

System Action: Processing stopped.

User Response: Ensure that the drive is available to ITSM, and then retry the operation.

Explanation: The drive was not available for access. A directory exists that does not have either a '.' or '..' entry.

System Action: Processing stopped.

User Response: Ensure that the drive is operational, and then retry the operation. If unsuccessful, have your service representative check the error log.

Explanation: An error was found while reading from or writing to the file.

System Action: File or file system is skipped.

User Response: Check your system to ensure that it is operating properly. For OS/2, run CHKDSK /F for the failing drive which can be found in dsmerror.log.

Explanation: An error was found while writing to the file.

System Action: File skipped.

User Response: Check your system to ensure that it is operating properly.

Explanation: A file being restored or retrieved exceeds system set limits for this user.

System Action: File skipped.

User Response: Ensure that the system limits are set properly.

Explanation: The directory path for files being restored or retrieved cannot be created.

System Action: File skipped.

User Response: Ensure that you have the proper authorization to create the directory for file being restored or retrieved. Make sure that you have write access.

Explanation: Clean-up failed due to an internal system error.

System Action: Please see error log for more details.

User Response: Please see your system administrator for assistance.

Explanation: ITSM was not able to take a snapshot of the specified volume. Please refer to the error log for more information on the cause of failure.

System Action: Processing stopped.

User Response: Contact your ITSM administrator.

Explanation: During the image snapshot backup ITSM encountered an error while performing the specified task.

System Action: Processing stopped.

User Response: Contact your ITSM administrator.

Explanation: The file is being recalled by another process or has been recalled.

System Action: File skipped.

User Response: None

Explanation: The description option on the archive command may not specify a null string.

System Action: Processing continues, and the description option is ignored.

User Response: None. Specify at least one character in the description

Explanation: The password is not updated because of one of the following reasons:

• You entered an incorrect current password or
• You entered a new password that does not fulfill the password length requirements set on the server.

System Action: The password is not updated on server.

User Response: Enter another password.

Explanation: You tried to do a selective backup and have specified a policy set that does not contain a backup management information (the copy group).

System Action: ITSM did not backup the file.

User Response: Create a management class that has a backup copy group, bind the file to that management class in your include-exclude list, and retry the operation. If unsuccessful, see your system administrator for more information.

Explanation: You tried to archive a file or group of files and have specified a policy set that does not contain an archive management information (the copy group).

System Action: ITSM did not archive the file.

User Response: Create a management class that has an archive copy group, assign the file to the management class, either through your include-exclude list or with the ARCHMC option, and retry the operation. If unsuccessful, see your system administrator for more information.

Explanation: The getmnt system call returned an error indication. Error was encountered trying to determine what the mounted file systems are.

System Action: Processing stopped. Cannot recover.

User Response: There is a bad file system or mount point on your system. Look at file systems and mounts, and correct any errors. If unsuccessful, see your system administrator for more information.

Explanation: An error was encountered trying to determine what the mounted file systems are.

System Action: Processing stopped. Cannot recover.

User Response: There is a bad filesystem or mount point on your system. Look at file systems and mounts, and correct any errors. If you used to have an FSM (HSM) file system but then removed HSM from it, make sure that there is no FSM mount for that filesystem; if it is still there then unmount it. If unsuccessful, see your system administrator for more information.

Explanation: The management class for this file does not allow migration

System Action: File is skipped.

User Response: Either have the ITSM administrator change the Space Management Technique within the management class to a value other than NONE or change the include/exclude list to specify a management class with the appropriate Space Management Technique value.

Explanation: File has been migrated. If files that are hard linked together are migrated then files subsequent to the first one encountered get this.

System Action: File is skipped.

User Response: None.

Explanation: You tried to back up or migrate a file that is implicitly excluded.

System Action: ITSM will not back up or migrate an implicitly excluded file.

User Response: None.

Explanation: Because ENABLESERVERFREE had been specified, and an attempted server-free data movement fell back to non-server-free, the ITSM client is forcing compression off. This is to enable future server-free restore of the object backed up, when the problems preventing a server-free backup from occurring have been resolved.

System Action: The operation continues without compression.

User Response: Either Remove the ENABLESERVERFREE option from the system option file, or set COMPRESSION off in the option file.

Explanation: ITSM cannot find the Windows Socket support file (WINSOCK.DLL) in the current search path. This message only applies when using TCP/IP communications.

System Action: Connection to server fails.

User Response: Shut down Windows and place the directory where this file resides in the DOS path statement.

Explanation: During the image snapshot backup ITSM was not able to communicate with the logical volume snapshot agent (LVSA).

System Action: Processing stopped.

User Response: Please verify that the LVSA is correctly installed on your system. If the problem persists please contact your ITSM administrator.

Explanation: To perform an off-line image backup or an image restore ITSM requires exclusive use of the volume.

System Action: Processing stopped.

User Response: Please verify that no other application is accessing the volume. If this volume is being accessed by applications that can not be shutdown during backup then perform an online image backup (snapshot with LVSA) instead. During restore of an image ITSM must have exclusive use of the volume.

Explanation: Error loading the Windows socket support file into memory. This error only applies when using TCP/IP communications.

System Action: Connection to server fails.

User Response: Because this error is caused by insufficient memory, shut down running applications and retry. If the problem persists, see your system administrator.

Explanation: Error loading one or more functions from the Windows socket support file.

System Action: Connection to server fails.

User Response: Since this might possibly be caused by insufficient memory, shut down running applications and retry. If the problem persists, see your system administrator.

Explanation: You specified a Windows user account which did not have the security right to run as a service

System Action: ITSM granted the "log on as a service" right to the account you specified.

User Response: No action required.

Explanation: You specified a Windows user account which did not have the security right to run as a service. ITSM encountered a problem attempting to grant this right automatically.

System Action: The "log on as a service" right is not granted to the account specified.

User Response: Insure the account from which you are configuring the service has authority to grant rights and retry the request. Alternatively run the Windows policy editor from an administrative account to grant the "log on as a service" right to the account that is associated with the service you are configuring.

Explanation: A virtual mount point that is a file system is invalid and should be deleted.

System Action: The virtual mount point is ignored.

User Response: Delete the virtual mount point.

Explanation: Virtual mount points cannot be used in a file system handled by automounter. If virtual mount points reside in a file system that is processed from an automounter, the backed up files underneath the virtual mount points will be expired when the file system is unmounted.

System Action: The virtual mount point is ignored.

User Response: Delete the virtual mount point.

Explanation: User issued a NAS related command and NASNodename option is missing.

System Action: Operation aborted.

User Response: Use -nasnodename option with the command or place nasnodename option in the option file.

Explanation: The system call to lock the volume failed.

System Action: Processing stopped.

User Response: Please verify that no other application is accessing the volume. If this volume is being accessed by applications that can not be shutdown during backup then perform an online image backup (snapshot with LVSA) instead. During restore of an image ITSM must have exclusive use of the volume.

Explanation: ITSM does not support image operations on this platform.

System Action: Processing stopped.

User Response: Contact your ITSM administrator.

Explanation: Some bad sectors within the specified range were detected on the volume during image operation.

System Action: Processing continues.

User Response: Make sure the volume data is not corrupt by using system tools like chkdsk (Windows) or fsck (UNIX).

Explanation: A subfile component was not received by the client during the restore process.

System Action: Processing stopped.

User Response: Please check error log for more information.

Explanation: The server detected a system error and notified the clients.

System Action: Processing stopped.

User Response: See your system administrator for further information on server activity.

Explanation: No objects on the server match the query operation being performed. If this object is part of a backupset generated on a node, and the node name is changed on the server, any backup set objects that were generated prior to the name change will not match the new node name.

System Action: Processing stopped.

User Response: Ensure the names are properly entered. If the object is part of a backupset generated prior to a node name change, ensure that the node name is the same as the node for which the backup set was generated.

Explanation: The client system ended the operation with the server and ended the current transaction.

System Action: Processing stopped.

User Response: Restart the session.

Explanation: ITSM did not find an active object flagged for expiration on the server. The object is marked as expired by another ITSM operation.

System Action: None.

User Response: None.

Explanation: ITSM tried to do a restore or retrieve on an object that has no data associated with it.

System Action: ITSM ended the current operation.

User Response: See your system administrator to verify the problem. If the problem continues, see your system administrator.

Explanation: You entered an incorrect password (verifier).

System Action: Processing stopped.

User Response: Retry the session with the correct password.

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.

Explanation: Archive expiration date is too low, the date must be greater than today's date.

System Action: ITSM canceled the current operation.

User Response: Retry archiving the file with an expiration date that is higher than today's date.

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: ITSM waits for offline storage media to become available and then continues.

User Response: None.

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.

Explanation: The server does not have any space available to store the object.

System Action: ITSM 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.
• For ITSM client, set COMPRESSALWAYS=NO and COMPRESSIon=YES in the options file (DSM.OPT), then the file will be resent uncompressed if it grows during compression.
• For API Applications, consult the application's documentation for recommendations regarding compression.
• 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.

Explanation: Server media mount not possible. The server timed out waiting for a mount of an offline volume.

System Action: File skipped.

User Response: Retry later when server volumes can be mounted. Ensure that the MAXNUMMP (maximum number of mount points) defined on the server for this node is greater than 0.

Explanation: The total amount of data for a backup or archive operation exceeds the estimated size originally sent to the server for allocating data storage space. This happens when many files are growing by large amounts while the backup or archive operation is in session.

System Action: Processing stopped.

User Response: Retry the operation. If the problem continues, check what other processes are running on the client machine that are generating large amounts of data. Disable those operations while the backup or archive operation is taking place.

Explanation: The file data is currently unavailable on the server. A retrieve or restore operation was attempted. Possible causes are:

• Data was corrupted at the server
• Server found a read error
• File is temporarily involved in a reclaim operation at the server
• Server requested a tape volume that was marked unavailable.

System Action: Processing stopped.

User Response: Retry the operation. If the problem continues, see your system administrator to determine the problem from the server console or the activity log. Check whether any requests were made for a tape volume that was unavailable. A tape volume may be marked unavailable if prior read errors were encountered or the volume is checked out of the tape library.

Explanation: Unexpected Retry request. The server found an error while writing data to the server's data storage.

System Action: Client retries the operation.

User Response: None.

Explanation: The server ran out of recovery log space.

System Action: ITSM ended the current operation.

User Response: This error is a temporary problem. Retry later or see your system administrator.

Explanation: The server ran out of database space.

System Action: ITSM ended the current operation.

User Response: See your system administrator.

Explanation: The server ran out of memory.

System Action: ITSM ended the current operation.

User Response: This is a temporary problem. Retry later or see your system administrator.

Explanation: This operation cannot be completed because the file space could not be renamed.

System Action: ITSM ended the current operation.

User Response: Contact system administrator for more information.

Explanation: The specified file space does not exist on the server. Your system administrator deleted the file space or another client using your client's node name deleted it.

System Action: ITSM canceled the current operation.

User Response: Check the file space name to see if it is correct, and retry the operation.

Explanation: Open registration failed because a node is defined in the server with the same name.

System Action: ITSM canceled the current operation.

User Response: Retry with another node name.

Explanation: Open registration failed because a default policy domain does not exist for you to place your node.

System Action: ITSM canceled the current operation.

User Response: See your system administrator.

Explanation: Open registration failed because the specified node name contains invalid characters.

System Action: ITSM canceled the current operation.

User Response: Retry with another node name that does not have any invalid characters.

Explanation: The client received an unexpected Wait For Space message from the server.

System Action: ITSM ended the current operation.

User Response: See your system administrator.

Explanation: IBM Tivoli Storage Manager was not able to take a snapshot of the specified volume.

System Action: Snapshot processing stopped.

User Response: Contact your IBM Tivoli Storage Manager administrator.

Explanation: An error occurred while generating the delta file. The delta file cannot be created.

System Action: Full backup is taken of the file, and a new version of the reference file is stored in the client cache.

User Response: If the problem recurs, report the program error to your service representative.

Explanation: The server does not have space available to store the object.

System Action: ITSM ended the current operation.

User Response: Report to your system administrator that a storage pool on the server is full.

Explanation: This operation can not be completed because a restartable restore session is pending. The operation is not allowed because the restartable session and the current operation affect the same file space.

System Action: ITSM ended the current operation.

User Response: Issue a query restore to see the conflict. Issue the cancel restore command to delete any unneeded restartable restore sessions.

Explanation: User must be a ITSM authorized user to perform this action. User is not password authorized and this action requires authorization.

System Action: Processing stopped.

User Response: User must be root user, or user must be the owner of the executable and the set effective user id bit is set to 'on' ('s' bit).

Explanation: IBM Tivoli Storage Manager applications can only be used by a System Administrator.

System Action: IBM Tivoli Storage Manager will quit.

User Response: Run the Mac OS X version of IBM Tivoli Storage Manager. You will be prompted for a System Administrator name and password.

Explanation: The snapshot image backup used block list is taken before and after the start of the snapshot for informational purposes.

System Action: Processing continues.

User Response: None.

Explanation: You are trying to restore a volume mount point to a non-empty directory which is not allowed. Volume mount point is not restored.

System Action: Processing continues.

User Response: None.

Explanation: An error occurred while importing the RSM database files. The database will not be updated. Reboot the machine and then restore RSM again.

System Action: Processing continues.

User Response: Ask your system administrator to check the error log.

Explanation: RSM database files have been restored from the server and imported. The RSM service must be restarted for the updates to become effective.

System Action: Processing continues.

User Response: None.

Explanation: RSM database files have been restored from the server and imported. ITSM is about to stop then restart the RSM service.

System Action: Processing continues.

User Response: None.

Explanation: RSM database files have been restored from the server and imported. ITSM has restarted the RSM service on the user's behalf.

System Action: Processing continues.

User Response: None.

Explanation: RSM database files have been restored from the ITSM server and imported. ITSM has tried to restart the RSM service on the user's behalf but has run into a problem.

System Action: Processing stopped.

User Response: Restart the RSM service manually.

Explanation: An error occurred while exporting the RSM database files. The database will not be backed up.

System Action: Processing stopped.

User Response: Ask your system administrator to check the error log.

Explanation: The client cache is currently locked by another process.

System Action: Processing stopped.

User Response: Report the program error to your service representative.

Explanation: Key entered does not match the key used for the backed up file.

System Action: Processing stopped.

User Response: Recollect the key used for backup.

Explanation: When jobs are run in the background, the client cannot prompt for the key.

System Action: Processing stopped.

User Response: Run the Job in the foreground.

Explanation: The specified file (object-name) does not have a match on the server.

System Action: File skipped.

User Response: Backup the file and retry the operation. If the problem continues, see your system administrator to isolate the problem through use of the server console.

Explanation: ITSM was not able to take a snapshot of the specified volume. The SNAPSHOTCACHELocation points to a location which does not contain the space necessary to manage the snapshot. This could be due to an unexpected amount of disk activity which is generating more changes than can be contained in the available space at this particular point in time, or the SNAPSHOTCACHELocation needs to be changed because the specified location is not large enough to handle the usual amount of changes to the volume. Another reason for this failure can be that the specified SNAPSHOTCACHESize is not set to a large enough value to handle the usual amount of changes to the volume during snapshot image backup.

System Action: Processing stopped.

User Response: If the problem persists please increase the SNAPSHOTCACHESize and/or change the value of the SNAPSHOTCACHELocation.

Explanation: ITSM was not able to take a snapshot of the specified volume. The percent of space allotted via the SNAPSHOTCACHESize option was not enough to perform this snapshot image backup. This could be due to an unexpected amount of disk activity which is generating more changes than can be contained in the allotted space at this particular point in time. Another reason for this failure can be that the specified SNAPSHOTCACHESize is not set to a large enough value to handle the usual amount of changes to the volume during snapshot image backup.

System Action: Processing stopped.

User Response: If the problem persists please increase the SNAPSHOTCACHESize and/or change the value of the SNAPSHOTCACHELocation.

Explanation: ITSM was not able to take a snapshot of the specified volume. The Logical Volume Snapshot Agent was not able to satisfy the SNAPSHOTFSIDLEWait and SNAPSHOTFSIDLERetries options before starting the snapshot of the specified volume.

System Action: Processing stopped.

User Response: If the problem persists please modify the SNAPSHOTFSIDLEWait and SNAPSHOTFSIDLERetries options to better fit the normal disk write activity of the volume being backed up.

Explanation: ITSM was not able to take a snapshot of the specified volume due to an unexpected error.

System Action: Processing stopped.

User Response: If the problem persists please contact your ITSM administrator.

Explanation: Another IBM Tivoli Storage Manager process is already performing a snapshot of this volume.

System Action: The operation is stopped.

User Response: Please wait until the other IBM Tivoli Storage Manager process finishes with the volume and then retry the operation.

Explanation: ITSM has all available sessions in use and cannot accept a new one at this time.

System Action: ITSM canceled the current operation.

User Response: Retry the operation. If the problem continues, see your system administrator to increase the number of concurrently active sessions to the server.

Explanation: Your ITSM password has expired.

System Action: ITSM canceled the current operation. You are not allowed to connect to the server until the password is updated.

User Response: Update your password.

Explanation: The node name you entered is not known by the server, or you are attempting to access a file migrated to a different node.

System Action: ITSM canceled the current operation. You are not allowed to connect to the server until your node name is registered with the server. If attempting to access a migrated file, your nodename must be the same node which migrated the file.

User Response: Ensure that you entered your ITSM node name correctly. If yes, see your system administrator. Verify that the server is using closed registration and that your node name is registered with the server.

Explanation: Another process using this node name is active with the server.

System Action: ITSM cannot connect to the server. ITSM canceled the current operation.

User Response: If you are running a UNIX-based system, ensure that another process is not active with ITSM under the same name. Also, ensure that your node name is unique to the server so that it cannot be used by another person. See your system administrator to identify the owner of that node name.

Explanation: The server is in a disabled state and cannot be accessed for normal activity.

System Action: ITSM canceled the current operation.

User Response: Retry the operation after the server returns to an enabled state. If the problem continues, see your system administrator.

Explanation: No authorization. Registration is required by your system administrator. The server is not configured to allow open registration.

System Action: Session not started.

User Response: You must obtain a ITSM node and password from your system administrator.

Explanation: The server version and your client version do not match. The client code is downlevel.

System Action: ITSM canceled the current operation.

User Response: See your system administrator to see what version of ITSM to run for your location.

Explanation: The server version and your client version do not match. The server code is downlevel.

System Action: ITSM canceled the current operation.

User Response: See your system administrator to see what version of ITSM to run for your location.

Explanation: The node name you specified is in use on the server.

System Action: Session was not started.

User Response: The server is probably performing a task that prevents your node from establishing a session. Retry later or check with your system administrator.

Explanation: The size of the file after compressesion is greater than the size of the file before compressed.

System Action: Even though the size of the file increased, the file is compressed.

User Response: None.

Explanation: The node name you specified is currently locked on the server.

System Action: Session was not started.

User Response: Check with your system administrator to find out why your node name is locked.

Explanation: Adding a new enrollment will exceed the product license count for ITSM.

System Action: Execution of the client enrollment or connection request ends.

User Response: See your system administrator.

Explanation: The server does not have enough memory to allow your client to establish a connection with the server.

System Action: Session was not started.

User Response: Retry later or see your system administrator.

Explanation: The server ran out of recovery log space.

System Action: Session was not started.

User Response: This error is a temporary problem. Retry later or see your system administrator.

Explanation: The server ran out of database space.

System Action: Session was not started.

User Response: See your system administrator.

Explanation: The client cannot establish a connection to the server because of an internal server error.

System Action: Session was not started.

User Response: See your system administrator immediately.

Explanation: The client can not establish a connection to the server because of a unicode enabling mismatch between server and client.

System Action: Session was not started.

User Response: See your system administrator immediately.

Explanation: The server is not licensed for the requesting client type.

System Action: Execution of the client enrollment or connection request ends.

User Response: See your system administrator.

Explanation: The server administrator canceled the current client session.

System Action: Execution of the client connection request ends.

User Response: See your system administrator.

Explanation: The user ID entered cannot access this ITSM client.

System Action: The ITSM operation ends.

User Response: Grant authority to this user ID on the ITSM server so that it can access this ITSM client.

Explanation: An error occurred while reconstructing this file from its subfile components.

System Action: Processing stopped.

User Response: Please check error log for more information.

Explanation: The user has probably coded the node option incorrectly. For instance, the node that is registered to the ITSM server might be a type of NAS, but the node is actually a non-NAS client.

System Action: The ITSM operation ends.

User Response: Ensure that the node name is correct in the client options file. Make sure to use a node of type NAS only with the nasnodename option.

Explanation: The command specified by the PRESNAPSHOTCMD option must complete successfully in order to perform the snapshot backup/archive operation. If the command completed with a return code of 0 (zero), it has completed successfully. If the command completed with any other return code, it has failed. If the command failed, then the backup is still performed, but without the benefit of the snapshot technology.

System Action: The client executes backup/archive operation, but without using a snapshot.

User Response: Identify and repair the problem that caused the command to fail. If a non-zero return code is normal for this command, then consider wrapping the command in a script that always exits with a return code of zero.

Explanation: If the command specified by the POSTSNAPSHOTCMD option completed with a non-zero return code, then the snapshot operation will continue, but with a warning-level result. Note that the result of the POSTSNAPSHOTCMD command will not supercede a higher result from the backup/archive command. For example, if the backup command completed with a return code of 12, the backup will be considered to have completed with a return code of 12, regardless of the outcome of the POSTSNAPSHOTCMD command.

System Action: The backup/archive operation continues, but with a warning return code of at least 8.

User Response: Identify and repair the problem that caused the command to fail. If a non-zero return code is normal for this command, then consider wrapping the command in a script that always exits with a return code of zero.

Explanation: IBM Tivoli Storage Manager was not able to take a snapshot of the specified volume. Please refer to the error log for more information on the cause of failure.

System Action: Snapshot processing stopped.

User Response: Contact your IBM Tivoli Storage Manager administrator.

Explanation: IBM Tivoli Storage Manager was not able to take a snapshot of the specified volume. Please refer to the error log for more information on the cause of failure. The operation will continue without snapshot support.

System Action: Snapshot processing stopped.

User Response: Contact your IBM Tivoli Storage Manager administrator.

Explanation: IBM Tivoli Storage Manager was not able to take a snapshot of the specified volume. Please refer to the error log for more information on the cause of failure. The operation will continue without snapshot support.

System Action: Snapshot processing stopped.

User Response: Contact your IBM Tivoli Storage Manager administrator.

Explanation: IBM Tivoli Storage Manager was not able to take a snapshot of the specified volume. The SNAPSHOTCACHELocation points to a location which does not contain the space necessary to manage the snapshot. Reasons for failure include:

• An unexpected amount of disk activity which is generating more changes than can be contained in the available space at this particular point in time.
• The SNAPSHOTCACHELocation is not large enough to handle the usual amount of changes to the volume.
• The specified SNAPSHOTCACHESize is not set to a large enough value to handle the usual amount of changes to the volume during snapshot backup or archive operation.

System Action: Processing stopped.

User Response: If the problem persists, increase the SNAPSHOTCACHESize or change the value of the SNAPSHOTCACHELocation.