ibm tivoli storage manager: client messages and ...€¦ · this edition applies to version 7, r...

IBM Tivoli Storage ManagerVersion 7.1.3

Client Messages and ApplicationProgramming Interface Return Codes

IBM

Note:Before you use this information and the product it supports, read the information in “Notices” on page 333.

Fourth edition (September 2015)

This edition applies to version 7, release 1, modification 3 of IBM Tivoli Storage Manager (product numbers5608-E01, 5608-E02, 5608-E03, 5608-E07) and to all subsequent releases and modifications until otherwise indicatedin new editions.

© Copyright IBM Corporation 1993, 2015.US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corp.

Contents

About this publication . . . . . . .. vWho should read this guide . . . . . . . .. vPublications . . . . . . . . . . . . .. v

Chapter 1. Introduction to messages .. 1Tivoli Storage Manager server and client messagesformat . . . . . . . . . . . . . . .. 1Interpreting return code messages . . . . . .. 2

Example one for QUERY EVENT command . .. 3Example two for DEFINE VOLUME command .. 3

Chapter 2. ANS 0000-9999 messages .. 5ANS messages list . . . . . . . . . . .. 5

Chapter 3. API return codes . . . .. 295API return code format . . . . . . . . .. 295API return codes . . . . . . . . . . .. 295

Appendix. Accessibility features forthe Tivoli Storage Manager productfamily. . . . . . . . . . . . . .. 331

Notices . . . . . . . . . . . . .. 333

Glossary . . . . . . . . . . . .. 337

© Copyright IBM Corp. 1993, 2015 iii

iv IBM Tivoli Storage Manager: Client Messages and Application Programming Interface Return Codes

About this publication

IBM® Tivoli® Storage Manager is an enterprise-wide storage managementapplication for the network. It provides automated storage management services tomulti-vendor workstations, personal computers, and local area network (LAN) fileservers.

This publication contains explanations and suggested actions for messages issuedby the Tivoli Storage Manager client components:v Administrative clientv Backup-Archive clientv Tivoli Storage Manager for Space Management (HSM client for IBM AIX® and

Linux systems).v Application programming interface (API)

Who should read this guideThe target audience for this publication is system administrators who service theIBM Tivoli Storage Manager components. In this publication, it is assumed thatyou have a working knowledge of the Tivoli Storage Manager backup-archiveclient.

PublicationsThe Tivoli Storage Manager product family includes IBM Tivoli StorageFlashCopy® Manager, IBM Tivoli Storage Manager for Space Management, IBMTivoli Storage Manager for Databases, and several other storage managementproducts from IBM.

To view IBM product documentation, see http://www.ibm.com/support/knowledgecenter.

© Copyright IBM Corp. 1993, 2015 v

http://www.ibm.com/support/knowledgecenter

http://www.ibm.com/support/knowledgecenter

vi IBM Tivoli Storage Manager: Client Messages and Application Programming Interface Return Codes

Chapter 1. Introduction to messages

Messages, error codes, and return codes are issued by the IBM Tivoli StorageManager server and clients.

Messages and codes can appear on the server console, the administrative client, anoperator terminal, the administrative graphical user interface, the backup-archiveclient, or the HSM (Hierarchical Storage Management) client.

Tivoli Storage Manager provides an activity log to help the administrator trackserver activity and monitor the system. The activity log contains messagesgenerated by the server, and is stored in the database. The server automaticallydeletes messages from the activity log after they have passed the specifiedretention period. Any messages sent to the server console are stored in the activitylog. Examples of the types of messages stored in the activity log include:v When client sessions start or endv When migration starts or endsv When backed up files are expired from server storagev Any output generated from background processes

Some messages have no explanations and are not published. The client can sendstatistics to the server providing information about a backup or restore. Thesestatistics are informational messages that can be enabled or disabled to the variousevent logging receivers. These messages are not published.Related information:

Using the activity log (https://www.ibm.com/support/knowledgecenter/SSGSG7_7.1.1/com.ibm.itsm.srv.doc/t_activ_log_using.html

Tivoli Storage Manager server and client messages formatTivoli Storage Manager server and client messages consist of the followingelements:v A three-letter prefix. Messages have different prefixes to help you identify the

Tivoli Storage Manager component that issues the message. Typically, allmessages for a component have the same prefix. Sometimes a component issuesmessages with two or three different prefixes.For example, backup-archive clients issue messages with ANS prefix.Backup-archive client events that are logged to server have ANE prefix. Servercommon and server platform-specific messages have ANR prefix.

v A numeric message identifier.v A one-letter severity code. The following codes indicate the severity of the action

that generated the message. The severity codes and their meanings are asfollows:

Code Severity MeaningS Severe The product or a product function cannot continue. User

response is required.E Error An error is encountered during processing. Processing might

stop. User response might be required.

© Copyright IBM Corp. 1993, 2015 1

https://www.ibm.com/support/knowledgecenter/SSGSG7_7.1.1/com.ibm.itsm.srv.doc/t_activ_log_using.html

https://www.ibm.com/support/knowledgecenter/SSGSG7_7.1.1/com.ibm.itsm.srv.doc/t_activ_log_using.html

Code Severity MeaningW Warning Processing continues, but problems might occur later as a result

of the warning.I Information Processing continues. User response is not necessary.

v Message text that is displayed on screen and written to message logs.v Explanation, System Action, and User Response texts. These texts elaborate on

the message text, and are available in the product's messages publications and inthe command line help.

The following image presents a typical Tivoli Storage Manager server message.

The callouts identify each element of the message.

Server installation complete.

ANR 0992 I

Message PrefixMessage NumberMessage Type*

Message Text

Explanation

System Action

User Response

Explanation: The server installation procedurehas completed successfully. The server is nowavailable for normal operation.

System Action: Server completes installationprocessing.

User Response: None.

I = InformationE = ErrorS = Severe ErrorW = WarningK = Kernel message that originates from thehierarchical storage management (HSM) client

*

Message variables in the message text appear in italics.

Interpreting return code messagesMany different commands can generate the same return code. The followingexamples are illustrations of two different commands issued that result in the samereturn code; therefore, you must read the descriptive message for the command.

In these examples, two different commands yield the same return code, but theyalso return descriptive messages that are unique to each command. The twocommands are q event standard dddd and def vol cstg05 primary. Both yield ageneric message with return code:ANS5102I: Return Code 11.

But the first command also yields a descriptive message:ANR2034I: QUERY EVENT: No match found for this query.

And the second command also yields a unique, descriptive message:ANRxxxx: DEFINE VOLUME: Storage pool CSTG05 is not defined.

2 IBM Tivoli Storage Manager: Client Messages and Application Programming Interface Return Codes

Example one for QUERY EVENT command

Example two for DEFINE VOLUME command

Chapter 1. Introduction to messages 3

Chapter 2. ANS 0000-9999 messages

ANS messages with message numbers in the range 0000-9999 are issued by thefollowing IBM Tivoli Storage Manager clients:v Administrative clientsv Application programming interface clientsv Backup–archive clientsv Tivoli Storage Manager for Space Management (HSM) clients

ANS messages listIBM Tivoli Storage Manager V7.1.3 client messages are listed in ascending numericorder. The complete message is documented, including message ID, message text,explanation, system action, and user response.

ANS0101E Unable to open English messagerepository file name.

Explanation: The default English message repositoryfile cannot be opened. Either the file access permissionsprevent reading the file or the file is not present in theexpected location.

System action: TSM is unable to complete therequested operation. Processing is terminated.

User response: Make sure the file in your DSM_DIR isset up properly. If the problem continues, see yoursystem administrator for further help.

ANS0102W Unable to open the message repositoryfile name. The American Englishrepository will be used instead.

Explanation: The default message repository file forthe current locale cannot be opened. Either the fileaccess permissions prevent reading the file, the file isnot present in the expected location, or the languagespecified in the option file is not supported on thisworkstation.

System action: TSM continues processing using theEnglish language message repository.

User response: Make sure the file in your DSM_DIR isset up properly. If the problem continues, see yoursystem administrator for further help.

ANS0103E Error trying to read header record frommessage repository file name.

Explanation: The message repository file headerrecord cannot be obtained.

System action: TSM is unable to complete therequested operation.

User response: Make sure the file has not been altered

from the installation. If the problem continues, see yoursystem administrator for further help.

ANS0105E Error trying to read index for messagenumber from repository file name.

Explanation: The message text for the specifiedmessage number cannot be read.


User response: Make sure the file has not been alteredfrom the installation. If the problem continues, see yoursystem administrator for further help.

ANS0106E Message index not found for messagenumber.

Explanation: The message repository file does notcontain the message text for the message number.


User response: Make sure the DSM_DIR is set upproperly and it does not point to an old copy. If theproblem continues, see your system administrator forfurther help.

ANS0107E Error trying to read header for messagenumber from repository file name.

Explanation: The message header information cannotbe obtained for the message number in the messagefile.


User response: Make sure the file has not been alteredfrom the installation. If the problem continues, see your


system administrator for further help.

ANS0108E Error trying to read text for messagenumber from repository file name.

Explanation: The message text cannot be obtained forthe message number in the message file.


User response: Make sure the file has not been alteredfrom the installation. If the problem continues, see yoursystem administrator for further help.

ANS0109E Insufficient memory for allocation ofmessage structure.

Explanation: There is not enough memory in yoursystem to allocate the storage needed for the messagetext.


User response: Stop TSM and restart TSM. Then retrythe operation. If unsuccessful, close all unneededapplications and retry the operation.

ANS0110E Unable to open error log file file namefor output.

Explanation: The error log cannot be opened foroutput.

System action: TSM is unable to complete therequested operation. File permissions may be set suchthat writing is not allowed.

User response: Stop and restart TSM. Then retry theoperation. If unsuccessful, make sure the file is notbeing locked by another application and that filepermissions allow write access.

ANS0113E Message repository file name has aninvalid control record.

Explanation: The message repository file contains anincorrect control information.


User response: Make sure the message file was notaltered from the installation. Check DSM_DIR to makesure it is set up properly.

ANS0118E Unable to open schedule log file 'filename' for output.

Explanation: The schedule log file cannot be openedfor output.


User response: Stop TSM and restart TSM. Then retrythe operation. If unsuccessful, make sure the file hasnot been locked by another application.

ANS0119E Error trying to read response string formessage number from repository filename.

Explanation: The response string information for themessage number cannot be obtained from the messagerepository file. It is possible the message repository hasbeen corrupted.


User response: Make sure the message file was notaltered from the installation. Check DSM_DIR to makesure it is set up properly.

ANS0120E Message number number contains aninvalid multibyte sequence for thecurrent locale.

Explanation: An illegal multibyte sequence for thecurrent locale was found in the message. Either themessage repository has been corrupted or is coded in alanguage other than that of the current locale.


User response: If the message repository is notcorrupted, process the operation in the supportedlocale.

ANS0121W Unable to open the iconv converter forthe message repository file name. TheAmerican English repository will beused instead.

Explanation: The iconv converter for the defaultmessage repository for the current locale cannot beopened. The iconv converter used to convert fromUTF-8 to the current locale is not installed on this workstation.

System action: TSM continues processing using theEnglish language message repository.

User response: Make sure the required iconvconverter is installed properly. If the problemcontinues, see your system administrator for furtherhelp.

ANS0201E Invalid parameter was found.

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

System action: The system returns to the callingprocedure.

ANS0108E • ANS0201E


User response: Ask your service representative tocheck the error log.

ANS0202E Not authorized to restore the othernode's data.

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


User response: Get authorization from the other node.

ANS0203E The objName field has no leadingdirectory separator.

Explanation: The objName field does not have aleading directory separator.


User response: Correct the value for the objName.

ANS0204E Wildcards are not allowed in theobjName directory path.

Explanation: Wildcards are not allowed in theobjName directory path.



ANS0205E Unable to open error log file.

Explanation: The system is unable to open the errorlog file.


User response: Verify the DSMI_LOG value andaccess permission. On the AS/400 platform, verify thevalue specified for ERRORLOGNAME in the APIoptions file.

ANS0206E The log file cannot be written to.

Explanation: There was an error writing to the logfile.


User response: Verify the DSMI_LOG value andaccess permission. on the AS/400 platform, verify thevalue specified for ERRORLOGNAME in the APIoptions file.

ANS0207E The log file name was not specified.




ANS0208E The TCP/IP WINSOCK.DLL file cannotbe found.

Explanation: The TCP/IP WINSOCK.DLL file cannotbe found.

System action: Processing stopped.

User response: Verify your TCP/IP installation.

ANS0209E An error occurred while loading alibrary.

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



ANS0210E The TCP/IP load function failed.

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



ANS0211E The object name pointer is NULL.

Explanation: There is no value provided for the objectname pointer.


User response: Provide an address for thedsmObjName structure.

ANS0212E The data block pointer is NULL.

Explanation: There is no value provided for the datablock pointer.


User response: Provide an address for the DataBlkstructure.


Chapter 2. ANS 0000-9999 messages 7

ANS0213E The object attribute pointer is NULL.

Explanation: There is no value provided for the objectattribute pointer.


User response: Provide an address for the ObjAttrstructure.

ANS0214E There is no server session information.

Explanation: The server did not respond with thesession information.


User response: Verify the server status.

ANS0215E There is no server policy information.

Explanation: The server did not respond with thepolicy information.


User response: Verify the server policy definitions.

ANS0216E The dataBlk bufferLen value is zero.

Explanation: The value for the dataBlk bufferLen iszero.


User response: Provide a non-zero value for thebufferLen.

ANS0217E The dataBlk bufferPtr is NULL.

Explanation: There is no value provided for thedataBlk bufferPtr.


User response: Provide an address for the bufferPtr.

ANS0218E The objType is invalid.

Explanation: The value for the objType is invalid.


User response: The value for dsmObjName.objTypemust be:

DSM_OBJ_FILE or DSM_OBJ_DIRECTORY forBackup, or

DSM_OBJ_FILE for Archive.

ANS0219E The dsmEndTxn vote is invalid.

Explanation: The dsmEndTxn vote is invalid.


User response: The vote must beDSM_VOTE_COMMIT or DSM_VOTE_ABORT.

ANS0220E An invalid option was found duringoption parsing.

Explanation: An invalid option was found.


User response: Verify the options in dsm.opt, dsm.sys,and the options string. Check the error log for moredetails about the error. on the AS/400 platform, verifythe options in *LIB/QOPTTSM(APIOPT).

ANS0221E There was an error in the TSM APIinternals.

Explanation: The system encountered an error in theAPI internals.


User response: Shut down the process and retry theoperation. Verify that any previous dsmInit calls werecleaned up and terminated by a dsmTerminate call. Ifthe problem continues, contact your systemadministrator or service representative.

ANS0222E The repository type is invalid.

Explanation: The repository type is invalid.


User response: For dsmDeleteFS the repository mustbe one of the following:

v DSM_ARCHIVE_REP

v DSM_BACKUP_REP

v DSM_REPOS_ALL.

ANS0223E Filespace name should start with thedirectory delimiter.

Explanation: The filespace name is invalid.


User response: Filespace name should start with thedirectory delimiter.



ANS0224E The object name is either an emptystring or has no leading delimiter.

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


User response: Verify the format of the dsmObjNamefull path.

ANS0225E Low level qualifier of the object nameshould start with the directory delimiter.

Explanation: The low level qualifier for the objectname is invalid.


User response: Start the low level qualifier of theobject name with the directory delimiter.

ANS0226E The object owner is invalid.

Explanation: The object owner must be either the rootuser, or the object owner must be the same as thesession owner.


User response: Verify the session owner and objectowner.

ANS0227E The dsmBindMC sendType is invalid.

Explanation: The dsmBindMC sendType is invalid.


User response: The sendType must be one of thefollowing:

stBackup

stArchive

stBackupMountWait

stArchiveMountWait

ANS0228E The dsmSendObj sendType is invalid.

Explanation: The dsmSendObj sendType is invalid.



stBackup

stArchive

stBackupMountWait

stArchiveMountWait

ANS0229E The dsmDeleteObj delType is invalid.

Explanation: The dsmDeleteObj delType is invalid.


User response: The delType must be dtBackup ordtArchive.

ANS0230E The query Backup objState is invalid.

Explanation: The query Backup objState is invalid.


User response: The qryBackupData.objState must beone of the following:

DSM_ACTIVE

DSM_INACTIVE

DSM_ANY_MATCH

ANS0231E The management class name was notfound.

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


User response: Verify the management class name.

ANS0232E The drive letter is not an alphabeticcharacter.

Explanation: The drive letter is not an alphabeticcharacter. This return code is valid on MicrosoftWindows only.


User response: Verify that the drive designation is analphabetic character. The referenced field isdsmDosFSAttrib.driveLetter.

ANS0233E The Register Filespace name is NULL.

Explanation: There is no value provided for theRegister Filespace name.


User response: Provide a filespace name ondsmRegisterFS.



ANS0234E The new password value is NULL orblank.

Explanation: There is no value provided for newpassword.


User response: Provide a new password ondsmChangePW.

ANS0235E The old password value is NULL orblank.

Explanation: There is no value provided for oldpassword.


User response: Provide an old password ondsmChangePW.

ANS0236E On dsmInit, the owner is not allowed toestablish a session whenPASSWORDACCESS=generate.

Explanation: PASSWORDACCESS=GENERATEestablishes a session with the current login user as theowner. The application should set clientOwnerNamePto NULL when PASSWORDACCESS=GENERATE is ineffect.

System action: The system returns to the callingprocedure. Whether the application can continueprocessing depends on how the application handles theerror.

User response: This message applies to applicationsthat utilize the TSM API, and is intended primarily forthe vendor of the application for which the message isissued. Depending on the application, this could be aconfiguration issue.

Consult the documentation for the application andverify that the application is configured correctly. If theproblem persists, contact the application vendor forfurther assistance.

ANS0237E On dsmInit, the node is not allowedwhen PASSWORDACCESS=generate.

Explanation: PASSWORDACCESS=generateestablishes a session with the current hostname as thenode.


User response: When usingPASSWORDACCESS=generate, set clientNodeNameP toNULL.

ANS0238E The sequence of calls is invalid.

Explanation: Then API requires function calls to bemade in a specific sequence. The function calls werenot made in the expected sequence. The error can betriggered by the following issues:

v An error in the network.

v A bug in the TSM API.

v A bug in the TSM server.

v A bug in the application (IBM or third party) thatuses the TSM API.


User response: An end user can respond in thefollowing ways:

v Check the network for errors.

v Look for clues in the TSM server activity log file,TSM client side dsierror.log log file, and log files thatare specific to the problem application.

v Search the IBM support pages for APARs that matchthe problem. The TSM Manager support site is atTivoli Storage Manager Support Portal(http://www.ibm.com/support/entry/portal/product/tivoli/tivoli_storage_manager)

v If the API application is developed by a third party(not IBM), search that third party's support pages forknown issues that match the problem.

If none of the above actions resolve the problem, reportthe problem to the vendor of the application that usesthe TSM API.

A developer of an application that uses the TSM APImust investigate the reason for the problem, includingreviewing the TSM API state diagram. The TSM APIstate diagram is in the product documentation at TivoliStorage Manager product documentation(http://www.ibm.com/support/knowledgecenter/SSGSG7)

ANS0239E On dsmSendObj, wildcards are notallowed for the objName.

Explanation: On dsmSendObj, wildcards are notallowed for the objName.


User response: Provide a fs, hl, and ll on thedsmObjName.

ANS0240E The filespace to delete/set access cannotbe found.

Explanation: The filespace to delete cannot be found.




http://www.ibm.com/support/entry/portal/product/tivoli/tivoli_storage_manager



http://www.ibm.com/support/knowledgecenter/SSGSG7




User response: Verify the filespace name.

ANS0241E On dsmSendObj, dsmDeleteObj, ordsmUpdateFS the filespace is notregistered.

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



ANS0242W On dsmRegisterFS the filespace isalready registered.

Explanation: On dsmRegisterFS the filespace isalready registered.



ANS0243E On dsmBeginGetData the objID isNULL.

Explanation: On dsmBeginGetData, the objID isNULL.


User response: Verify the following:

The dsmGetList is not NULL.

Each objID is not NULL.

The dsmGetList numObjId is not zero.

ANS0244E On dsmInit the caller's API version isdifferent than the TSM library version.

Explanation: On dsmInit the caller's API version has ahigher value than the TSM library version.


User response: Install the latest TSM API library andtrusted agent module.

ANS0245E The caller's structure version is differentthan the TSM library version.

Explanation: The caller's structure version is differentthan the TSM library version.


User response: Ensure that the stVersion field is setwith the value in the header file. Recompile theapplication with the latest header files.

ANS0246E Issue dsmEndTxn and then begin a newtransaction session.

Explanation: This transaction must be ended and anew one must be started due to one of the followingreasons:

The destination changed.

The byte limit is exceeded

The maximum number of objects is exceeded.


User response: Issue dsmEndTxn and start a newtransaction session.

ANS0247E The backup or archive object isexcluded from processing.

Explanation: The backup or archive object is excludedfrom processing.


User response: Verify the objName and Exclude lists.

ANS0248E The backup object does not have a copygroup.

Explanation: The backup object does not have a copygroup.


User response: Verify server policy definitions.

ANS0249E The archive object does not have a copygroup.

Explanation: The archive object does not have a copygroup.



ANS0250E Memory used by the TSM API has beencorrupted.

Explanation: Memory used by the TSM API has beencorrupted.


User response: Retry the operation. If the problemcontinues, contact your system administrator or servicerepresentative.



ANS0251E The sendObj Archive description is toolong.

Explanation: The sendObj Archive description is toolong.


User response: The sndArchiveData.descr string mustbe less than or equal to DSM_MAX_DESCR_LENGTH.

ANS0252E The sendObj ObjAttr.objInfo is toolong.

Explanation: The sendObj ObjAttr.objInfo is too long.


User response: The objInfo field must be less than orequal to DSM_MAX_OBJINFO_LENGTH.

ANS0253E The sendObj dsmObjName.hl is toolong.

Explanation: The sendObj dsmObjName.hl is too long.


User response: The hl field must be less than or equalto DSM_MAX_HL_LENGTH.

ANS0254E The password, or encryptionPasswordstring provided is too long.

Explanation: The value provided for password orencryptionPassword is too long.


User response: The password or encrypionPasswordfield must be less thanDSM_MAX_VERIFIER_LENGTH.

ANS0255E The sendObj dsmObjName.fs is toolong.

Explanation: The sendObj dsmObjName.fs is too long.


User response: The fs field must be less than or equalto DSM_MAX_FS_LENGTH.

ANS0256E The sendObj dsmObjName.ll is toolong.

Explanation: The sendObj dsmObjName.ll is too long.


User response: The ll field must be less than or equalto DSM_MAX_LL_LENGTH.

ANS0257E On RegisterFS or UpdateFS the fsAttr'sfsInfo is too long.

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


User response: The fsInfo field must be less than orequal to DSM_MAX_FSINFO_LENGTH.

ANS0258I On dsmGetNextQObj or dsmGetDatathere is more available data.

Explanation: On dsmGetNextQObj or dsmGetDatathere is more available data.


User response: Call the function again.

ANS0259E The dataBlk buffer is too small for thequery response.

Explanation: The dataBlk buffer is too small for thequery response.


User response: On dsmGetNextQObj ensure that thedataBlk buffer is at least as big as the query responsestructure.

ANS0260E An invalid option keyword was foundduring option parsing.

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


User response: Correct the spelling of the optionkeywords. Verify that the dsmInit configuration fileonly has a subset of the dsm.sys options. Check theerror log for more details about the error.

ANS0261E The configuration file specified ondsmInit cannot be opened.

Explanation: The configuration file specified ondsmInit cannot be opened.


User response: Verify the file name.



ANS0262E The Include/Exclude definition file wasnot found.

Explanation: The Include/Exclude definition file wasnot found.


User response: Verify the file name on the Inclexcloption.

ANS0263E Either the dsm.sys file was not found, orthe Inclexcl file specified in dsm.syswas not found.

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


User response: The dsm.sys file must be in thedirectory referenced by the environment variableDSMI_DIR. Verify the file name on the Inclexcl optionin the dsm.sys file.

ANS0264E Only a UNIX root user can executedsmChangePW or dsmDeleteFS.

Explanation: Only a UNIX root user can executedsmChangePW or dsmDeleteFS.


User response: Run this program as a root user.

ANS0265E You must issue dsmBindMC beforedsmSendObj.

Explanation: You must issue dsmBindMC beforedsmSendObj.


User response: Modify your program.

ANS0266I The dsmEndTxn vote is ABORT, socheck the reason field.

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


User response: Check the reason field for the codewhich explains why the transaction has been aborted.

ANS0267E Invalid command line option/value:'option'

Explanation: The option is not valid on this commandline.

System action: Processing stops

User response: Verify that the option and value arenot misspelled and are valid with the currentcommand.

ANS0268E Server problem: Destination notdefined.

Explanation: Server problem: Destination not defined.


User response: Have your service representative checkthe error log.

ANS0270S The data buffer overflowed.

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


User response: Retry the operation. If the problemcontinues, contact your system administrator.

ANS0271E No more files can be restored orretrieved since the destination directoryis full.

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


User response: Free up disk space, or restore orretrieve the file to another disk.

ANS0272I The operation is finished.

Explanation: The operation is finished.


User response: Proceed with next function call.

ANS0273E The trusted agent execution/ownerpermissions are invalid.

Explanation: The trusted agent execution/ownerpermissions are invalid.


User response: Have your system administrator checkthe installation instructions for the client to ensure thatthe trusted agent permissions are set correctly.



ANS0274S Process killed.

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



ANS0275S Trusted agent would block theoperation.

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



ANS0276S The area for the include/exclude patternis too small.

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



ANS0277S There is no closing bracket in thepattern.

Explanation: There is no closing bracket in thepattern. This is a programming failure and the clientprogram ends.



ANS0278S The transaction will be aborted.

Explanation: The server encountered an error and willabort the transaction.

System action: The transaction will be aborted. Thereason code is passed on the dsmEndTxn call.

User response: Issue the dsmEndTxn with a vote ofDSM_VOTE_COMMIT and examine the reason code.

ANS0279I A file was skipped during a restoreoperation because the file is off line andthe application has chosen not to waitfor a tape mount.

Explanation: A file was skipped during a restoreoperation because the file is off line and the applicationhas chosen not to wait for a tape mount.

System action: File skipped.

User response: Verify the application sets themountWait value correctly on dsmBeginGetData.

ANS0280E Unable to find Trusted Agent module.

Explanation: TSM was unable to find the TSM TrustedAgent module in the specified directory. The name ofthe TSM Trusted Agent module is dsmtca.

System action: TSM ends.

User response: Make sure the Trusted Agent moduleis in the directory specified by DSMI_DIR.

ANS0282E Password file is not available.

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


User response: The root user must set and store a newpassword.

ANS0283E High level qualifier of the object nameshould start with the directory delimiter.

Explanation: The high level qualifier for the objectname is invalid.


User response: High level qualifier of the object nameshould start with the directory delimiter.

ANS0284E The number of objects ondsmBeginGetData exceedsDSM_MAX_GET_OBJ |DSM_MAX_PARTIAL_GET_OBJ.

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


User response: Check the number of objects beforecalling dsmBeginGetData. If it is greater thanDSM_MAX_GET_OBJ |DSM_MAX_PARTIAL_GET_OBJ, then issue multipleGet call sequences.

ANS0285E The update action is invalid.

Explanation: The dsmUpdateFS or dsmUpdateObjaction is invalid.


User response: Correct the action value. Valid values

ANS0274S • ANS0285E


are defined in dsmapitd.h and documented in ourUsing the API book.

ANS0286E The key file is missing.

Explanation: The key file for Tivoli Data Protectionapplication client for Oracle cannot be found.


User response: Ensure that you have ordered theTivoli Data Protection application client which containsTDP for Oracle, and install the key file.

ANS0287E The key file content is invalid.

Explanation: The key file content for Tivoli DataProtection application client for Oracle is invalid.


User response: Ensure that you have ordered theTivoli Data Protection application client which containsthe TDP for Oracle, and install the key file.

ANS0296I Encryption key passwords are not thesame.Please try again...

Explanation: TSM found that the encryption keypasswords do not match.

System action: You are prompted for the encryptionkey password.

User response: Enter the correct encryption keypassword.

ANS0297E Error opening specified file.

Explanation: The specified file could not be located oropened.

System action: Attempts to open file failed.

User response: Make sure the file exists.

ANS0298E Session Rejected: The specified user idis currently locked

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

System action: Session was not started.

User response: Check with your system administratorto find out why your user id is locked.

ANS0299E Scheduler cannot be started manuallybecause the value ofMANAGEDSERVICES option isSCHEDULE.

Explanation: if MANAGEDSERVICES SCHEDULE isindicated in the option file, the TSM scheduler cannotbe started in the traditional manner.

System action: Scheduler stopped.

User response: If you are not going to use dsmcad tomanage the schedule anymore, stop dsmcad andremove MANAGEDSERVICES option from the optionfile.

ANS0302I Successfully done.

Explanation: The operation successfully completed.

System action: None.

User response: None.

ANS0304E The password is too short.

Explanation: The new password does not haveenough characters.

System action: The password is not updated on theserver.

User response: Choose a different password. Contactyour TSM administrator to lean the passwordrequirements.

ANS0305E It is too soon after the previous updateto change the password.

Explanation: The password cannot be changed sincenot enough time has elapsed since the last passwordupdate.


User response: Try to change your password againlater.

ANS0306E The password was previously used.

Explanation: The new password that you entered waspreviously used.


User response: Choose a different password.

ANS0307E The password does not meet therequirements.

Explanation: The new password that you entered doesnot meet the requirements, such as the number ofspecial characters or digits.




User response: Choose a different password. Contactyour TSM administrator to learn the passwordrequirements.

ANS0308E Remote operation failed to start onobj-name. Status: status reason: reason

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

System action: TSM ended the current operation.

User response: Contact your system administrator formore information.

ANS0309E Remote operation failed to start onobj-name. Status: status

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

System action: IBM Tivoli Storage Manager ended thecurrent operation.


ANS0311E The tsmBuffHandle is invalid, or thevalue of dataPtr is invalid.

Explanation: An invalid value for a handle or dataPtrhas been passed into the API.


User response: There is a problem with the callingapplication. Verify the values of the tsmBuffHandle anddataptr passed to the API.

ANS0312E The number of bytes copied into thetsmBuffer is larger than the allowedvalue.

Explanation: An invalid number of bytes was copiedto a tsmBuffer.


User response: There is a problem with the callingapplication. Verify the number of bytes copied into thetsmBuffer.

ANS0313E dsmTerminate cannot finish because theapplication is holding on to 1 or moretsmBuffers.

Explanation: An application is trying to terminate asession, but is still holding some tsmBuffers.


User response: The application must return all buffersfor this session by calling tsmReleaseBuffer, and thenissue dsmTerminate.

ANS0314E An internal error occurred in thetsmBuffer array.

Explanation: An internal API buffer array erroroccurred.


User response: Try the operation again. If the problemcontinues, contact your system administrator or servicerepresentative.

ANS0315E Unable to open message text file.

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


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

ANS0316E Unable to use message text file.

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


User response: Install the message text file again.

ANS0317E Unable to use message text file.

Explanation: The system is unable to use the messagetxt file (dscenu.txt or dsmclientV3.cat for AIX) becauseof an invalid control record. On the AS/400 platformthis file is QANSAPI/QAANSENU(TXT).



ANS0318E Invalid value for DATEFORMATspecified.

Explanation: An invalid value is specified forDATEFORMAT.




User response: Specify a valid value.

ANS0319E Invalid value for TIMEFORMATspecified.

Explanation: An invalid value is specified forTIMEFORMAT.



ANS0320E Invalid value for NUMBERFORMATspecified.

Explanation: An invalid value is specified forNUMBERFORMAT.



ANS0321E msg parameter for dsmRCMsg is aNULL pointer.

Explanation: The message parameter for dsmRCMsgis a NULL pointer.


User response: Allocate enough space for the messageparameter.

ANS0322E no text available for this return code.

Explanation: The dsmRC parameter for dsmRCMsg isan unsupported return code.



ANS0323E partialObjOffset value for partial objectretrieve is invalid.

Explanation: The partialObjOffset value for partialobject retrieve is invalid.



ANS0324E partialObjLength value for partial objectretrieve is invalid.

Explanation: partialObjLength value for partial objectretrieve is invalid.



ANS0325E Partial Object Retrieve is not supportedon this server.

Explanation: The TSM server specified by the userdoes not support partial object retrieve.


User response: Specify a TSM server which supportsthe partial object retrieve function.

ANS0326E This node has exceeded its maximumnumber of mount points.

Explanation: Either no tape or sequential disk mountpoints are permitted for this operation, or themaximum number of mount points allowed are alreadyin use. The operation can not be completed. The TSMadministrator defines the maximum number of mountpoints with the MAXNUMMP property of your nodedefinition.

System action: The object is skipped

User response: If you are performing any other TSMoperations that might be using mount points, wait untilthose operations are complete, then try the failedoperation again. Otherwise contact your TSMadministrator for further assistance

ANS0327E A duplicate object was found, operationcannot complete.

Explanation: A duplicate object was found, operationcannot complete.

System action: The requested operation failed.

User response: Try the operation with a different filespecification.

ANS0328E The specified objects failed the mergetest.

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


User response: See documentation for the merge testparameters.

ANS0330E The dsmSetAccess access Type isinvalid.

Explanation: The dsmSetAccess accessType is invalid.




User response: The accessType must be one of thefollowing:

atBackup

atArchive

ANS0331E No files have been previously backedup for this filename/filespace.

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


User response: Ensure that the correct drive or filesystem was specified and that files are backed up foryou to set access.

ANS0332E No files have been previously archivedfor this filename/filespace.

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


User response: Ensure that the correct drive or filesystem was specified and that files are archived for youto set access.

ANS0333E Unknown Remote Mover type

Explanation: The specified Remote Mover type isunknown.



ANS0334E An Operation for the requested nodeand filespace is already in progress.

Explanation: A request has been made to use a datamover to perform an operation for the indicated nodeand filespace. Since an operation for this node andfilespace is already in progress, the new operationcannot be performed.


User response: Retry the operation at a later time.

ANS0335E System resource in use

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



ANS0336E Server plugin communication error

Explanation: Communication between a server pluginmodule and a NAS filer failed.



ANS0337E Server plugin detected unsupportedNAS filer operating system.

Explanation: A plugin module detected that a NASfiler is running an unsupported operating system oroperating system level.



ANS0338E An invalid operation was attempted ona node

Explanation: The operation is not valid.



ANS0339E The specified target storage pool is notdefined.

Explanation: The storage pool is not defined.



ANS0340E A target storage pool does not have thecorrect data format for the given nodetype.

Explanation: none



ANS0341E No associated data mover is defined forthe given node.

Explanation: none





ANS0342E The CRC received from the Server doesnot match the CRC calculated by theclient.

Explanation: The server sent a CRC for a buffer. Theclient calculated a CRC for the same buffer. These didnot match. The mismatch indicates a communicationfailure.

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

User response: Check the trace log for additionalinformation and retry the operation. If the problempersists, contact your system administrator.

ANS0343E An invalid operation was attempted ona group leader or group member.

Explanation: An invalid operation was attempted on alogical group.

System action: The current operation stops.

User response: Retry a valid operation.

ANS0344E Cannot Send data with a zero bytesizeEstimate.

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


User response: Set size estimate greater than 0 indsmSendObj.

ANS0345E Remote disk not defined.

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


User response: Define the proper remote disk.

ANS0346E Input destination does not matchexpected destination.

Explanation: Input destination does not matchexpected destination.


User response: Retry operation with properdestination.

ANS0347E Data mover is not available.

Explanation: Data mover is not available.


User response: Retry operation with a proper Datamover.

ANS0348E Operation failed because the copycontinue option was set to NO.

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


User response: This abort code indicates that a storeoperation, like backup or archive failed because thecopy continue option was set to NO. The sysadmin willneed to resolve the problem on the server end.

ANS0349E Transaction failed because of a problemduring a store operation.

Explanation: Transaction failed because of a problemduring a store operation. This error is typical when thenext storage pool has a different copy storage pool listand we switch to this pool in the middle of atransaction.

System action: Transaction is aborted.

User response: Resend objects in separate transactions.

ANS0350E The current client configuration doesnot comply with the value of theDATAWRITEPATH orDATAREADPATH server option for thisnode.

Explanation: The values of the DATAWRITEPATHand DATAREADPATH server options specify where theclient is allowed to send data, and where data is readfrom. The values for the specified node name shouldcorrespond with the client configuration. For example,you will get this error message if DATAWRITEPATHcontains a LAN value and the client is configured touse LAN-free protocol, or vice versa.


User response: Check the client, server, and storageagent logs to determine why the client was not able tosend data LAN-free. Make sure the client configurationand server options are compatible.

ANS0351E The node or user does not have properauthority to perform this operation

Explanation: The node or user does not have properauthority to perform this operation.

System action: The transaction is ended.

User response: Check the authority for the specifiedobject.



ANS0352E The operation is not permitted due toserver licenses values.

Explanation: The node or user is trying to perform anoperation that either exceeds license values, or is notlicensed.

System action: The session is rejected or thetransaction is cancelled, ending the current operation.

User response: See your system administrator.

ANS0353E When using useTsmBuffers, dataBlkmust be NULL in calls to dsmSendObjand dsmGetObj.

Explanation: The value for dataBlk must be NULLwhen using useTsmBuffers.


User response: There is a problem with the callingapplication. Contact your application provider

ANS0354E Encryption is not allowed when usinguseTsmBuffers.

Explanation: useTsmBuffers does not supportencryption.


User response: Try the operation again, without usinguseTsmBuffers, or disable encryption for this operation.

ANS0355E This object cannot be restored/retrievedusing useTsmBuffers, because it iscompressed.

Explanation: useTsmBuffers does not supportcompression.


User response: Try the operation again, without usinguseTsmBuffers.

ANS0356E This object cannot be restored/retrievedusing useTsmBuffers, because it isencrypted.




ANS0357E When using useTsmBuffers, arestore/retrieve with partial objectrestore is not allowed.

Explanation: useTsmBuffers does not support partialobject restore.


User response: Make sure the calling application iseither using Partial object restore or useTsmBuffers.

ANS0358E No encryption key was found. If youare using -encryptkey=prompt makesure there is a value in theencryptionPasswordP field and thatbEncryptKeyEnabled is set to true.

Explanation: There was no encryption key found inthe password file, or no key was provided by theapplication.


User response: If you are using -encryptkey=prompt,make sure there is a value in encryptionPasswordP andthat bEncryptKeyEnabled is set to true.

ANS0359E Conflicting encryption key options havebeen specified.

Explanation: When using the ENABLEENCRYPTKEYoption, the parameter bEncryptKeyEnabled for the TSMAPI dsmInitExIn_t and tsmInitExIn_t structures cannotbe set to bTrue.


User response: Either remove theENABLEENCRYPTKEY option from the options file, orset the parameter bEncryptKeyEnabled to bFalse in theprogram using the TSM API.

ANS0360E The CAD cannot start because the valueof the MANAGEDSERVICES option isNONE.

Explanation: The CAD will not start ifMANAGEDSERVICES NONE is set in the option file.The CAD is designed to manage the web client or TSMschedules. By specifying NONE, the CAD will notmanage any services.

System action: The CAD will stop processing.

User response: Specify either WEBCLIENT orSCHEDULER for the MANAGEDSERVICES option inthe option file then restart the CAD.



ANS0361I DIAG:

Explanation: The message text is provided fordiagnostic purposes and is meant to provideinformation to IBM support in problem determination.



ANS0362E There are insufficient Windows systemresources to process this command.

Explanation: This problem can occur during backupof a shared directory. The most likely reason is the'IRPStackSize' setting on the computer that hosts theshared directory is too small.

System action: The file is skipped.

User response: Check the Windows event viewer forevent ID 2011 on the computer that hosts the shareddirectory. This event indicates that the configurationparameter IRPStackSize is too small. IRPStackSize is asetting of type DWORD located in Windows registrykey HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\LanmanServer\Parameters.If the IRPStackSize value is less than 20, orIRPStackSize is not specified, then set the value to 20,restart the system, and try the operation again. Thedefault IRPStackSize value is 15. Attention: Consultwith your Windows system administrator beforemaking changes to the Windows registry or theproblem persists after changing the IRPStackSize valueto 20.

ANS0400E License file could not be opened.

Explanation: The license file was not found, or couldnot be opened because of permissions or the file iscorrupted.


User response: Check permissions on file. See if thelicense file is in the correct place.

ANS0401E Read failure on the license file.

Explanation: The license file was not found, or couldnot be opened because of permissions, or the file iscorrupted.



ANS0402E Write failure on the license file.



User response: Check permissions on file. See iflicense file is in the correct place.

ANS0403E Data in the license file is not in a validformat.

Explanation: The license file is not valid.


User response: User needs to obtain a new license.

ANS0404E The checksum in the license file doesnot match the licenseregistration string.

Explanation: The registration string is not valid.



ANS0405E This is an expired try and buy license.




ANS0410E Oracle passed invalid mode

Explanation: Invalid mode passed by Oracle.


User response: Contact your system administrator.

ANS0411E Oracle passed null file name

Explanation: Null filename passed by Oracle.



ANS0412E Wrong data block size

Explanation: Wrong Block Size



ANS0361I • ANS0412E


ANS0413E Object exists

Explanation: Backup or Restore Object already exists.


User response: If backing up an object, be sure togenerate a unique object name.

ANS0414E Not same Oracle handle

Explanation: The handle passed from Oracle is not thesame handle that TSM passed back.



ANS0415E End of file reached

Explanation: End of file reached.


User response: None

ANS0416E Wrong Read State

Explanation: The operation must be in READ state.


User response: Contact your service representative.

ANS0417E Runtime API version is outdated

Explanation: Runtime API is lower than compile timeAPI.


User response: Use the WHAT command to find outthe compile time API level. Obtain the same or higherlevel of API library.

ANS0418E Wrong write state

Explanation: The operation must be in WRITE state.



ANS0419E Invalid flag passed

Explanation: Invalid flag passed from Oracle.



ANS0420W Warning! Restoring inactive system stateobjects is not recommended.Do you wish to continue?

Explanation: Restoring inactive system state objectsmay cause system instability. Examples of possibleproblems include:

v Applications that were installed after the time thesystem state was backed up cannot function properlyafter restoring the inactive system state

v Critical operating system updates installed after theinactive system state backup was made can nolonger be available, or may not function correctly.

Restoring inactive system state objects is notrecommended unless you are certain that this is whatyou need to do.

System action: If user responds with yes, the clientwill restore the object. If user responds with no, theclient will cancel the operation.

User response: Reply to the prompt. If you areunsure, reply no, and consult your systemadministrator or operating system vendor beforeproceeding further.

ANS0421W Unable to synchronize the nodepassword with the user id passwordprovided.

Explanation: The node password was not updateddue to the reason described in the error messagepreceding this one.

System action: The node password is not updated onthe server. Next time you run the client you will beprompted for the password again.

User response: See the preceding error message.

ANS0422W The selected journal location is anetwork drive and might not beaccessible from the journal service.Select a location on a local drive.

Explanation: It is not recommended to use a networkdevice as the location where journal databases arestored. Placing journal databases on a network devicecan prevent the journal service from running.

System action: Processing continues.

User response: Choose a local drive where journaldatabases will be stored.

ANS0423E Directory 'filespace namepath-namefile-name'cannot be created. Path does not exist.

Explanation: The operating system returned a "pathnot found" status when IBM Tivoli Storage Managerattempted to create the directory needed for AutomatedSystem Recovery (ASR). One possible reason is that a



multi disk system is restored to a single disk system.


User response: Please verify that you are restoring toidentical hardware and try again.

ANS0990W Options file 'file-name' could not befound. Default option values will beused.

Explanation: Common reasons for this warninginclude:

v The default options file does not exist, and

v You did not specify the -OPTFILE option whenstarting the TSM client, and

v the environment variable DSM_CONFIG was not set.

System action: TSM client assumes default values forall client options and continues processing, using thedefault server name and associated options found inthe dsm.sys file.

User response: If the default system action isacceptable, you can eliminate this message by creatingan empty dsm.opt file in the installation directory.

If you have a client user options file (dsm.opt), eitherplace it in the installation directory or set theDSM_CONFIG environment variable to thefully-qualified path and file name of your options file.

Review the information on configuring TSM in theTSM client manual specific to your operating system. Ifthe problem persists, ask your TSM administrator forfurther assistance.

ANS0991I TSM scheduler is listening for serverrequests on port port number

Explanation: This message indicates the port numberon which the clients is listens for server requests. If theport number in the message differs from the defaultvalue or what you specified with the TCPCLIENTPORToption, it is because the port was in use by a differentprocess.


User response: Normally no further action is required.If you require TSM to use a specific port number, youneed to configure your system or applications so thenumber is avaible. Restart the TSM client and confirmit uses the desired port.

ANS0992E The destination filespace or drive letteris unavailable. For more details pleasesee dsmerror.log.

Explanation: The system is trying to restore or retrieveto a destination that cannot be reached. The specifiedfilespace name or drive letter is not valid, or does notexist, or you are specifying a local share name thatcannot be resolved.

System action: Objects which are part of this filespaceare not processed.

User response: Try the command again, and specify adifferent destination for the object that was notprocessed.

ANS0993E The source specification "source" hasinvalid format.

Explanation: The file system must be enclosed incurly braces and wildcards cannot be used except atthe lower level.

System action: The command processing isterminated.

User response: Correct the specification and try thecommand again.

ANS0994E Invalid string 'string' for virtual filespace name or group name specification.

Explanation: You entered a virtual file space name ora group name specification that contains wildcardcharacters.


User response: Enter a correct virtual file space nameand a group name and try again. Use the pick optionto display a list of groups from which you can selectone group.

ANS0995E Volume 'volume-name' could not belocked.

Explanation: The system call to lock the volumefailed.


User response: Please verify that no other applicationis accessing the volume. During restore of an imageTSM must have exclusive use of the volume.

ANS1000E An unsupported communicationsmethod was specified.

Explanation: None.

System action: processing stops.

User response: Specify a communications interfacethat is supported by the TSM client on your operatingsystem. See the TSM client manual for your operatingsystem for further information on configuring TSMclient communications.

ANS1001E Volume being backed up was not asystem volume. Skipped.

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

ANS0990W • ANS1001E


System action: Volume was not backed up.

User response: Use All option or use image backupcommand to backup this volume.

ANS1002I MOS image is being created. It maytake a while.

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

System action: TSM is gathering necessaryinformation.


ANS1004W Node has exceeded max tape mountsallowed. Operation for 'filespace-name'will be tried again later.

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

System action: The operation will be retried.

User response: Increase the number of allowed tapemounts for this node on the server to avoid thissituation again.

ANS1005I TCP/IP read error on socket = socket-id,errno = error-code, reason : 'error-reason'.

Explanation: An attempt to receive data using TCP/IPconnection failed. If reason : 'Connection reset by peer',it is possible that the server control connection timedout. This can occur if the file transfer time is greaterthan 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 filetransfer time, you can ignore this message. The clientwill reconnect with the server automatically, finishtransferring the data, and send statistics. You can alsoconsider increasing the IDLETIMEOUT value in theserver options file.

ANS1006I TCP/IP write error on socket = socket-id,errno = error-code, reason : error-reason

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

System action: Connection to server fails.

User response: Retry the operation. If the problempersists, contact your system administrator.

ANS1007E Sending of object 'object-nameobject-nameobject-name' failed. There is nobackup copy group.

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

copy group, or an INCLUDE statement is attempting tobind the file to a management class that does not havea backup copy group.

System action: TSM did not back up the file.

User response: Run DSMC QUERY MGMTCLASS-DETAIL to view information about availablemanagement classes.

v If the file is being bound to the default managementclass, make sure the management class has a backupcopy group.

v If the file is being bound to a management classspecified in an INCLUDE statement, make sure thatthe management class has a backup copy group.

v If you have more than one TSM server, make sureyou are connecting to the correct server.

v If you are unable to find a suitable managementclass, contact your TSM administrator for furtherassistance.

ANS1008E Sending of object 'object-nameobject-nameobject-name' failed: No Archive CopyGroup

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



ANS1009W An error occurred processing theoperating system include/excludestatements.The error was detected whileprocessing: subsystemname.

Explanation: The client encountered an error whileobtaining the automatic include/exclude statementsfrom the operating system. Possible reasons for thiserror include:

v The specified registry key cannot be opened forreading

v The entry under this key has incorrect data

System action: Processing continues without the fulllist of operating system include/exclude statements.

User response: Ensure that you have access to thespecified registry key and that entries are a MULTISZvalues that contain:

v Individual files

v Directories

v Wild card entries

v Environment variables

v /s switch (the /s switch is used on directory and/orwild card entries and signifies that all subdirectoriesof this directory should be excluded)

ANS1002I • ANS1009W


If the cause of this message can not be determined orresolved, contact IBM technical support for furtherassistance.

ANS1010E Error processing 'filespace-name':Unsupported file system operation.

Explanation: The file system does not support anoperation required to process the file or directory.

System action: The file or directory is skipped.Depending on the specific error encountered,processing on Solaris clients might stop.

User response: Verify that the file system is supportedby the TSM client. If a restore or retrieve failed, retrythe operation to another location. If the problempersists, look for other indications of system problems.It may be necessary to run the operating system utilitythat checks and repairs file system inconsistencies. Ifthe problem still cannot be resolved, contact your TSMadministrator for further assistance.

ANS1015E The session is rejected. The server doesnot allow a signon of a client that is notarchive-retention protection enabled.

Explanation: The client cannot establish a connectionto the server because the server is enabled forarchive-retention protection enabled and the client isnot.

System action: The session is not started.


ANS1016I No eligible files matching 'pathname'were found.

Explanation: The backup or archive operationcompleted, but no files were processed. Possiblereasons for this include:

The directory that was backed up or archivedcontains no files

The files are excluded from backup or archive

System action: None

User response: Check the path you entered.

ANS1017E Session rejected: TCP/IP connectionfailure.

Explanation: An attempt to connect to the serverusing TCP/IP communications failed. This can be aresult of incorrect TCP/IP option settings in your clientoptions file. This error can also occur if the LANconnection went down or if your system administratorcanceled a backup operation.

System action: Session rejected. Processing stopped.

User response: Retry the operation, or wait until theserver comes back up and retry the operation. If the

problem continues, see your system administrator forfurther help.

ANS1018E Port port number is already in use

Explanation: The port specified by theTCPCLIENTPORT option is in use by a differentprocess.


User response: Contact the server administrator to setup a different port for server-initiated connections.Update the TCPCLIENTPORT with this new portnumber.

ANS1019E The volume could not be opened.

Explanation: An error occurred when TSM tried toopen the volume for a backup or restore operation.

System action: The requested operation does not run.

User response: Examine the client error log foradditional messages related to this error. Verify that thevolume is available, and is not locked by anotherprocess. Try the operation again. If the problempersists, contact IBM technical support for furtherassistance.

ANS1020E System object backup failed.

Explanation: An error occurred while backing upWindows system object files. The backup did notcomplete.


User response: Ask your system administrator tocheck the error log. Restart the Windows serviceassociated with the system object indicated in the errorlog, and retry the backup operation

ANS1021E System object restore failed.

Explanation: An error occurred while restoringWindows system object files. The restore did notcomplete.


User response: Ask your system administrator tocheck the error log. Restart the machine, and thenrestore the system object indicated in the error logagain.

ANS1022E Cancel failed for node: node-namefilesystem: fs-name operation: op-typeerror: error

Explanation: The request to cancel a remote operationhas failed. The node, filespace, operation and reason forthe failure are shown.

System action: TSM operation not cancelled.




ANS1023E Session rejected: Node type mismatch

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

System action: TSM canceled the current operation.

User response: If you need a new node name, seeyour system administrator to assign a new one to you.Generally, you have a unique node name for eachmachine and operating system pair that requires accessto the server.

ANS1024E Failed to update backup attributes onserver for 'backup type' backup for'filespace namepath-namefile-name', object id'object-id:object-id' return code 'return code'.

Explanation: TSM failed to update attributes for thenamed backup object on the server. The server may notreflect correct state of the backup.


User response: Check preceding error messages inerror log for more information. Retry the operation. Ifproblem continues, contact your TSM administrator.

ANS1025E Session rejected: Authentication failure

Explanation: Authentication failure. You entered anincorrect password.


User response: Enter your correct password. If youcannot remember the correct password, see yoursystem administrator to have a new one assigned foryour node name.

ANS1026E The session is rejected: There was acommunications protocol error.

Explanation: An unexpected network message wasreceived by the client. This could be caused by networkproblems or a programming error.


User response: Verify that your communication pathis functioning properly and try the operation again. Ifthe problem persists, contact your TSM administratorfor further assistance.

ANS1028S An internal program error occurred.

Explanation: TSM encountered an unexpectedcondition and can not continue the operation. Thismight be a programming error.


User response: Try the operation again. If the problempersists, contact your TSM administrator or IBMtechnical support for further assistance.

ANS1029E Communication with the TSM server islost.

Explanation: This message is issued after the sessionwith the TSM server is unexpectedly lost. The clienterror log might contain additional informationregarding this problem.


User response:

v Restart the TSM client and retry the operation.

v If the problem persists, review the client error log forother messages that might be related to this problem.

v Verify that network connectivity exists between theTSM client machine and the TSM server machine.

v Contact your TSM administrator for furtherassistance. The TSM administrator can review theTSM server activity log for additional informationabout the problem.

ANS1030E The operating system refused a TSMrequest for memory allocation.

Explanation: TSM requires access to memory in orderto store information as processing proceeds. In thiscase, more memory was requested than the operatingsystem would allocate. Possible reasons include:

The system is low on memory.

The process in which the program runs hasexceeded the maximum memory that it is allowedto allocate.

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

System action: TSM cannot complete the requestedoperation.

User response: Close all unneeded applications andtry the operation again. If the operation still fails, trydividing the task into several smaller units. Forexample, if a file specification contains several highlevel directories, run the TSM task serially for eachdirectory. If the TSM task is an incremental backup, usethe option "-memoryefficientbackup=yes".

For UNIX systems that support resource limits, checkto see b if the memory resource limit is too low byentering the following command: ulimit -a

Based on the resulting data, you can ask the UNIXsystem root user to increase resource limits so that itwill override the current default. The UNIX system rootuser has the authority to increase resource limits.



ANS1031E The attempt to establish a TCP/IPconnection timed out before theconnection was made.

Explanation: The Object of the connection attemptfailed to respond within the the allotted wait time. Inthe case of the B/A client, this message is preceded indsmerror.log by message ANS5216E that gives detailsof the connection that failed. The condition may betemporary.


User response:


v Check the client options file and verify thatTCPSERVERADDRESS and TCPPORT specify thecorrect TCP/IP address and port number for yourTSM server.


v If the problem persists, see your TSM administratorfor further assistance.

ANS1032E An attempt to establish a TCP/IPconnection was rejected by the host

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


User response: The server was not fully initialized, isnot currently running, was not enabled for TCP/IPcommunications, or an incorrect TCP/IP port numberwas specified. If the problem continues, see yoursystem administrator.

ANS1033E An invalid TCP/IP address wasspecified.

Explanation: The TCP/IP address specified by theTSM client's TCPSERVERADDRESS setting could notbe found on the network. Common reasons for thiserror include:

v The TCPSERVERADDRESS client option specifies thewrong TCP/IP address for the TSM server".

v The machine that hosts the TSM server is not on thenetwork.

v A network problem is preventing the TSM clientfrom reaching the machine that hosts the TSM server.


User response: Verify that the TCPSERVERADDRESSand TCPPORT settings have the correct values for yourTSM server. Use your operating system's "ping" (orsimilar) utility to ensure that your machine can locatethe machine that hosts the TSM server across thenetwork. Try the operating again. If the problempersists, ask your TSM administrator for furtherassistance.

ANS1034E The specified TCP/IP host name isunreachable

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


User response: Check your options file for the correctTCPSERVERADDRESS statement. See youradministrator for the correct name of the server.

ANS1035S Options file 'file-name' could not befound, or it cannot be read.

Explanation: Common reasons for this error include:

v The default options file does not exist.

v You specified the -OPTFILE option when starting theIBM Tivoli Storage Manager client, but the optionsfile you provided does not exist.

v The DSM_CONFIG (or DSMI_CONFIG if you areusing the IBM Tivoli Storage Manager API)environment variable specifies an options file thatdoes not exist.

v You specified the -OPTFILE option when starting theIBM Tivoli Storage Manager client, but the optionsfile that you provided is not in the standard fileencoding of the system. For example, on Windowsthe expected file encoding is ANSI.

v You specified the -OPTFILE option when starting theIBM Tivoli Storage Manager client, but the optionsfile that you provided does not have appropriateread permissions for the user that is running theoperation.

System action: IBM Tivoli Storage Manager clientprocessing stops.

User response: Make sure that the options file youwant to use exists, it has the read rights set for the userthat is running the operation, and it is in the standardfile encoding of the system. For example, on Windowsthe expected file encoding is ANSI. Review theconfiguration information in the IBM Tivoli StorageManager client manual specific to your operatingsystem. If the problem persists, ask your IBM TivoliStorage Manager administrator for further assistance.

ANS1036S The option 'option' or the value suppliedfor it is not valid. It was found inoptions file 'file-name'at line number: numberThe complete entry: 'entry'

Explanation: The specified option or option value isnot valid. The option can be in the TSM options file ora parameter on a command. For options that include adate or time specification, the format of the date ortime might not match the formats specified by theDATEFORMAT or TIMEFORMAT options.

System action: Processing stops.

ANS1031E • ANS1036S


User response: Correct the option name or value. Foroptions that specify dates or times, ensure that thespecified date or time matches the DATEFORMAT andTIMEFORMAT settings. If -DATEFORMAT or-TIMEFORMAT are specified on the command line,they must precede the option that specifies the date ortime. For example, use -DATEFORMAT=3-FROMDATE=yyyy-mm-dd, instead of-FROMDATE=yyyy-mm-dd -DATEFORMAT=3.

ANS1037S Invalid keyword specified

Explanation: TSM found an incorrect keyword in theoptions file.


User response: Correct the options file with validentries.

ANS1038S Invalid option specified.

Explanation: An incorrect option was specified toTSM.


User response: Correct the options used for runningTSM.

ANS1039S The include or exclude pattern cannotbe parsed.

Explanation: The pattern is formatted incorrectly or istoo complex for TSM to interpret.


User response: Verify that the include or excludepattern is specified correctly. If the pattern is correct,then contact IBM technical support for furtherassistance.

ANS1040S Include/Exclude pattern is missing aclosing bracket

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


User response: Correct the syntax for the pattern.

ANS1041S Include/Exclude pattern must start witha directory delimiter

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



ANS1042S A beginning or ending directorydelimiter is missing from theInclude/Exclude pattern.

Explanation:

1. The include/exclude pattern has a '...' without abeginning or ending directory delimiter.

2. For Windows, the drive seperator is notimmediately followed by a directory delimiter.



ANS1043S Quotes are not matched

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


User response: Correct the pattern by using matchingquotes in the syntax.

ANS1047E The destination file system isunavailable. The following object wasskipped:File space:'filespace-name'Pathname:'path-name' Filename:'file-name'

Explanation: The client is trying to restore or retrievethe specified object to a destination that is not valid,does not exist, or cannot be reached.

System action: The object is not restored or retrieved.Processing continues with the next object.

User response: Try the command again using adifferent destination.

ANS1048E Device 'volname' is not local

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

System action: The requested logical volumeoperation is not performed.

User response: Choose another object.

ANS1049E 'filename' is not a valid destination filefor image restore

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

System action: Restore processing stopped.

User response: Specify a correct filename for imagerestore.



ANS1050E Before performing the VSS InstantRestore TSM cannot lock the volume'volume-name'.

Explanation: The volume cannot be locked becauseanother application is accessing the file systems on thevolume.


User response: Stop or suspend the applications thathave handles open on the volume. For a file systemrestore, close applications that are accessing the filesystems that are used for the VSS Instant Restore.

If you cannot close the applications that are accessingthe file system, unmount the file system. After theunmount process is complete, mount the file systemand perform the VSS Instant Restore.

For more information, see the TSM error log fileDSMERROR.LOG.

ANS1051I Invalid password

Explanation: You entered an invalid password.

System action: TSM cannot connect to the serverwithout the correct password.

User response: Enter the password, or ask yoursystem administrator for the correct password.

ANS1052E Direct connection to the Storage Agentis not allowed.

Explanation: You cannot connect directly to theStorage Agent.


User response: To perform Lanfree operations usingthe Storage Agent, specify the ENABLELANFREEoption in your options file, and restart the process.

ANS1053I Existing file space filespace-name hasbeen renamed to filespace-name

Explanation: If the file space is for Windows systemstate, this message is issued when the TSMbackup-archive client detects multiple system state filespaces where the names differ only in case. Theexistence of multiple system state file spaces can occurif, at some earlier time, your TSM administratorrenamed the system state file space to the same namebut with a different case or the computer's name waschanged from all upper case characters to lower case ormixed case characters.If the file space name represents a drive volume label,then this file space was created by an older TSMbackup-archive client.

System action: If the file space is for Windows systemstate, TSM will back up system state to the file spacecontaining the most recent backup. The older file space

is renamed as specified in this message. Subsequentsystem state backups will continue to back up systemstate to the same (most recently used) file space.If the file space name represents a drive volume label,TSM renames the file space to the corresponding UNCname and continues to back up the drive to thisrenamed file space.

User response: No further action is necessary.However, if the file space is for Windows system state,then at some future time when you have determinedyou no longer need the older renamed system state filespace, you can ask your TSM administrator to deletethe older file space from TSM storage.

ANS1054E Existing filespace filespace-name cannotbe renamed to new filespacefilespace-name. TSM return code = retcode.

Explanation: The client was unable to migrate a filespace name from the volume label naming conventionto the UNC naming convention.


User response: Check the client error log and the TSMserver activity log for any other messages that mighthelp identify the problem. If the problem cannot beresolved, contact IBM technical support for additionalassistance.

ANS1055I Trying to rename existing filespacefilespace-name to new filespacefilespace-name,but drive letters do not match,old=drive-letter, new=drive-letter. Ignorethe old filespace and backup to the newfilespace.

Explanation: Trying to rename the existing filespacename using the volume label to the UNC formatnaming convention but the drive letters do not match.Leave the existing filespace alone and create a newfilespace.



ANS1056E Share/network path share cannot beresolved. Path does not exist.

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


User response: Retry the command and specify adestination, or restore the directory tree first beforetrying to restore the share point.



ANS1057I File space filespace-name cannot berenamed to new file space filespace-name,because the new file space alreadyexists.

Explanation: The client was unable to migrate a filespace name from the volume label naming conventionto the UNC naming convention because the new filespace already exists on the TSM server.

System action: The operation proceeds using the newfile space. The old file space is ignored.

User response: No action is necessary, but if the datain the old file space is no longer needed, it can bedeleted from the TSM server.

ANS1058E The restore destination cannot bereached.

Explanation: Either the destination file system isinvalid or it cannot be reached.


User response: Try the command again using adifferent destination.

ANS1059E Two inactive objects with the sameimage name were selected. Processterminates

Explanation: You selected more than one inactiveversion of the same image object (logical volume). Thesystem has no way to decide which you want torestore.

System action: The requested logical volume restore isnot performed.

User response: Retry the operation, selecting an activeversion or only one inactive version of the volume youwish to restore.

ANS1060E The specified path is not a mountedfilesystem

Explanation: You entered a file system name that doesnot correspond to a mounted file system for thissystem. It is possible the file system name ismisspelled, or simply that the file system is notcurrently mounted.


User response: Retry the operation, using name of amounted file system.

ANS1061E The specified device corresponds to amounted file system; you must specifythe file system by name.

Explanation: You entered a logical device name that ismapped to a mounted file system. This volume mustonly be referenced by its file system name.


User response: Try the operation again, using the filesystem name instead of the device name.

ANS1062E Only a single image may be selectedwhen a destination is entered.

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

System action: The requested logical volume restore isnot performed.

User response: Retry the operation, selecting oneobject to be restored to the given destination, or retrythe operation without entering the destination.

ANS1063E The specified path is not a valid filesystem or logical volume name.

Explanation: None.

System action: The logical volume operation is notperformed.

User response: Try the operation again using a validpath.

ANS1064E An unexpected error occurred whileprocessing the image operation.

Explanation: None.


User response: Examine the client error log for anyadditional messages that may have been issued beforeor after this message. Correct any problems, if possible.If the cause of this message can not be determined orresolved, contact IBM technical support for furtherassistance.

ANS1065E Library version of the image utility doesnot match that of the TSM API

Explanation: The current system has a mix of installedcomponents.




User response: Re-install all TSM components

ANS1066E The restore operation completedsuccessfully, but the file system couldnot be remounted.

Explanation: None.

System action: The file system is left unmounted.

User response: Use the mount command to mount thefile system. On AIX, run fsck if requested by theoperating system.

ANS1067E A call to a system function returned anunexpected error.

Explanation: If you are performing a JFS2 snapshotbased operation, it is possible that the snapshot was notlarge enough to contain all the changes made to thefilesystem after the snapshot was created. This couldcause the snapshot to become invalid therebypreventing TSM client from reading the snapshot.


User response: Examine the client error log foradditional messages related to this error. Try theoperation again. If the problem persists, contact IBMtechnical support for further assistance.

If you are performing a JFS2 snapshot based operation,please use the default snapshotcachesize of 100% andensure that the volume group has sufficient disk spaceto allocate snapshots at least as large as the file systemand retry the operation.

ANS1068E Device is not local

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



ANS1069E An error occurred while reading datafrom the device

Explanation: An error occurred while reading datafrom the device. Windows Only: This could be due tobad sectors on the drive.


User response: Retry the operation, then check theerror log for more information. Windows Only: Pleaserun chkdsk /r and retry the operation. If the problempersists, a possible workaround is to back up the entiredrive using a regular (non-image) backup. Pleaseensure that all your data is backed up. Then format thedrive using a full format (without the /q quick format

option). Then restore the data and retry the imagebackup operation.

ANS1070E Write error

Explanation: An error occurred while writing data tothe device.


User response: Re-try the operation, check error logfor more information.

ANS1071E Invalid domain name entered:'domain-name'

Explanation: You entered an invalid domain name.Verify whether the domain name is a file system andthe file system is mounted. A directory cannot bespecified in the domain option, unless it is a virtualmount point.

System action: Processing continues if there are otherfile systems in the domain option to back up.

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

ANS1072E Unable to continue operation; Drive'drive-name' has no volume label.

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


User response: Use the system format utility to placea unique volume label on all drives on which youintend to run TSM.

ANS1073E The file space for domain 'domain-name'could not be found on the TSM server.

Explanation: The specified file space was expected tobe found on the server, but it no longer exists. It ispossible that a command was issued to delete the filespace from the server while the current operation wasin progress.

System action: TSM processing stops.

User response: Try the operation again. If the problemrecurs, check the error log for any other messages thatmight indicate a reason for the failure. Try to correctany indicated problems, then try the operation again. Ifthe problem persists, contact IBM technical support forfurther assistance.



ANS1074W The operation was stopped by the user.

Explanation: The operation was stopped at the requestof the user. This usually occurs when the 'Q' key ispressed two times.



ANS1075E file name(line number)The operatingsystem refused a IBM Tivoli StorageManager request for memory allocation.

Explanation: IBM Tivoli Storage Manager requiresaccess to memory in order to store information asprocessing proceeds. In this case, more memory wasrequested than the operating system would allocate.Possible reasons include:


The process in which the program runs hasexceeded the maximum allocated memory.

Some other error condition occurred. No memory isavailable.

System action: IBM Tivoli Storage Manager cannotcomplete the requested operation.

User response: Close all unneeded applications andtry the operation again. If the operation still fails, trydividing the task into several smaller units. Forexample, if a file specification contains severalhigh-level directories, run the IBM Tivoli StorageManager task serially for each directory. If the IBMTivoli Storage Manager task is an incremental backup,use the option "-memoryefficientbackup=yes".

For UNIX systems that support resource limits, you cancheck if the memory resource limit is too low byentering the following command: ulimit -a

Based on the resulting data, you can ask the UNIXsystem root user to increase the resource limit abovethe current default limit. The UNIX system root userhas the authority to increase resource limits.

ANS1076E The specified directory path 'pathname'could not be found.

Explanation: An invalid or unreachable directory pathwas specified.


User response: Try the operation again using a validdirectory path.

ANS1078S Unknown system error error-codeoccurred.

Explanation: An error unknown to TSM error-codeoccurred within the client program.

System action: The client stops.

User response: Check the error log for any othermessages that might indicate a reason for the failure.Try to correct any indicated problems, then try theoperation again. If the problem persists, contact IBMtechnical support for further assistance.

ANS1079E No file specification entered

Explanation: You did not enter a file specification asprompted.

System action: TSM did not continue with therequested operation.

User response: Enter a file specification to continue.

ANS1081E Invalid search file specification 'string'entered.

Explanation: You entered a file specification or searchstring that contains incorrect characters or containswildcard characters in the drive specification or filesystem name.


User response: Enter a correct file specification asdescribed in the appropriate Using the Backup-ArchiveClient book for the particular operating system.

ANS1082E Invalid destination file specification'file-name' entered

Explanation: You entered a destination file-namespecification that contains incorrect characters or haswildcard characters in the specification.


User response: Enter a correct file specification asdescribed in the appropriate Using the Backup-ArchiveClient book for the particular operating system.

ANS1083E No files have previously been archivedfor 'filespace-name'

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


User response: Ensure that the correct drive or filesystem was specified and that files are archived for youto retrieve.

ANS1084E No files have previously been backedup for 'filespace-name' or the specified filespace is invalid for the current operatingsystem.

Explanation: You cannot restore files. Either the filespace or drive is invalid, or no backup copies exist.




User response: Specify a valid drive or file space.Verify that backup copies exist.

ANS1086E File not found during Backup, Archiveor Migrate processing

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



ANS1087E Access to the specified file or directoryis denied

Explanation: Access to the specified file or directory isdenied. You tried to read from or write to a file andyou do not have access permission for either the file orthe directory.


User response: Ensure that you specified the correctfile or directory name, correct the permissions, orspecify a new location.

ANS1088E File space 'filespace-name' does not exist

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


User response: Retry the operation specifying anexisting domain (drive letter or file system name).

ANS1089E Destination directory path lengthexceeds system maximum

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


User response: Specify a destination path that, whencombined, is less than the system maximum.

ANS1090E The LVM1 device is no longersupported by this client.

Explanation: The selected path refers to a volumedevice managed by LVM version 1. LVM 1 is no longersupported by this version of client and therefore is nota valid object for image operations.


User response: Use earlier versions of the client thatsupport LVM1 to perform the logical volume operation.Alternatively, you can upgrade to LVM2 and migrate

the volume to LVM2. LVM2 is supported by this clientfor logical volume operations.

ANS1091E Communications error with serverduring object query

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


User response: Verify that communications are activebetween the client and server machines. Server outages,processor outages, and communication controlleroutages can cause this error.

ANS1092W No files matching search criteria werefound

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


User response: Ensure that your search pattern iscorrect, or specify a new search string.

ANS1093E Your TSM server does not supportpoint-in-time processing.

Explanation: The client has requested a point-in-timequery or restore operation, but the TSM server towhich the client is connected does not supportpoint-in-time operations.


User response: Make sure that you are connected tothe correct TSM server. If you are connected to thecorrect server, then try the command again withoutspecifying any point-in-time options.

ANS1094E An error occured trying to connect to therestore location on the virtual machine.Verify that the restore location exists onthe virtual machine and that youraccount has access to it.

Explanation: During restore processing, the systemcreates a share to access the restore location on thevirtual machine. In this situation, the system wasunable to create a share. This error typically occurs ifthe restore location does not exist or the user accountdoes not have access to the location.

System action: The system was unable to create ashare.

User response: Verify that the restore location existson the virtual machine and that your account hasaccess to it.



ANS1096S Either the node does not exist on theserver or there is no active policy set forthe node.

Explanation: This error occurs when you try to accessanother node's data. Either the node is not registeredwith the TSM server, or there is no active policy set forthe node.


User response: Verify that the node whose data youare trying to access is registered with the TSM server. Ifyou have more than one TSM server, make sure youare connecting to the correct server, then try theoperation again. If the problem persists, contact yourTSM administrator for further assistance.

ANS1097E The client help text cannot be read fromthe help file.

Explanation: The help file was opened successfullyand its table of contents are available, but there is aproblem reading the text from the help file.


User response: If the DSM_DIR environment variableis set, verify that it points to the directory containingthe current level of TSM program files, then try theoperation again. If the problem recurs, re-install theTSM client software. If the problem persists, IBMtechnical support for further assistance.

ANS1098E Process terminated; Program memoryexhausted.

Explanation: The program used all available storage.


User response: Free any unnecessary programs (TSRs)that are running, and retry the operation. Reducing thescope of queries and the amount of data returned canalso solve the problem.

ANS1099E File 'filename' not previously archived

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


User response: Ensure that the correct filename isspecified.

ANS1100E File 'filename' not previously backed up

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


User response: Ensure that the correct filename isspecified.

ANS1101E User is not authorized to encryptfile-space namedirectory_pathfile_name.

Explanation: The user is not authorized to encrypt thefile. Normally, only a IBM Tivoli Storage Managerauthorized user or a root user can use IBM TivoliStorage Manager encryption. However, a certaincombination of PASSWORDACCESS andENCRYPTKEY options may allow encryptionoperations by a non-authorized user.

System action: The file is not backed up or restored.

User response: Log in as a root or IBM Tivoli StorageManager authorized user and try the operation again.See IBM Tivoli Storage Manager Backup-Archive ClientInstallation and User's Guide for the correct usage ofthe ENCRYPTKEY option.

ANS1102E An excessive number of command linearguments are passed to the program.

Explanation: This command processing routinereceived more operands than it can use. The rules are:

v Query can contain only one file specification.

v Restore and Retrieve can contain two filespecifications.

v Archive, Incremental, and Selective can contain amaximum of 20 file specifications. To bypass the20-operand limit, use the -REMOVEOPERANDLIMIToption on the failing archive, incremental, orselective command.

Note: The TSM Client operates much more efficiently ifit expands wild cards internally, rather than acceptingthe expanded list from the shell.


User response: Reduce the number of arguments andretry the operation. For UNIX-based systems, ensurethat you have surrounded the specification containingpattern matching characters with quotes. As analternative, use the -REMOVEOPERANDLIMIT optionon the failing archive, incremental, or selectivecommand.

ANS1103E Invalid management class entered

Explanation: You entered an invalid managementclass.

System action: TSM is unable to do the requestedoperation.

User response: Retry the operation using a validmanagement class.



ANS1104E The management class for this file doesnot have a valid archive copy group.This file will not be archived.

Explanation: The management class for this file doesnot have an archive copy group specified. This file willnot be archived.


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

ANS1105E The management class for this file doesnot have a valid backup copy group.This file will not be backed up.

Explanation: The management class for this file doesnot have a backup copy group specified. This file willnot be backed up.


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

ANS1106E ENCRYPTKEY SAVE not configuredcorrectly. Encryption not used.

Explanation: This message is issued for TSMAuthorized Users and root users when ENCRYPTKEYSAVE and PASSWORDACCESS PROMPT options areset. Please note that these are the default values. Thesevalues do not allow encryption.

System action: The file is not encrypted.

User response: To save encryption keys, you mustchange configuration values. Add PASSWORDACCESSGENERATE to your system option file.

ANS1107E Invalid option/value: 'option'

Explanation: You specified an incorrect TSM option oroption value.

System action: For the command line client:Processing stops.

For the native GUI client: There is a small set ofoptions critical to the initialization of the client. If anerror is found in one of these, this message is presentedand the client terminates without further processing.

User response: Specify a correct TSM option asdefined in the appropriate Using the Backup-ArchiveClient book for the particular operating system.

ANS1108E Invalid option (option) for the functioncommand

Explanation: There are two possible reasons for thismessage:

v The option option was specified for a command orsubcommand (function) that cannot make use of thatoption.

v The option appears on the initial command line andis not valid there.


User response: See the Backup-Archive ClientInstallation and User's Guide for correct use of thenamed option.

ANS1110E The client help file file-name could notbe opened.

Explanation: This usually occurs when the help filefile-name cannot be found.


User response: If the DSM_DIR environment variableis set, verify that it points to the directory containingthe current level of TSM program files, then try theoperation again. If the problem recurs, re-install theTSM client software. If the problem persists, IBMtechnical support for further assistance.

ANS1113E The snapshot cache location is not valid.

Explanation: The snapshot cache location must pointto a local volume that is formatted with NTFS. Thedefault cache location is on the same volume where thesnapshot is being performed. The operation willcontinue without snapshot support.

System action: The client does not execute thesnapshot backup operation.

User response: Specify a different snapshot cachelocation using the SNAPSHOTCACHELOCATIONoption.

ANS1114I Waiting for mount of offline media.

Explanation: The server is waiting for the requestedmedia to become available before the operation cancontinue.

System action: TSM waits for requested data.


ANS1115W File 'file-namefile-namefile-name' excludedby Include/Exclude list

Explanation: You can not back up, archive, or migratefiles that are excluded.

System action: TSM does not process the file.

User response: If the file is intentionally excluded,then this message can be ignored. Otherwise modifythe include/exclude list, restart the client, and try theoperation again. Contact your TSM administrator forfurther assistance.

ANS1104E • ANS1115W


ANS1116E The process is running in anon-interactive mode, but requires userinput.

Explanation: This process requires keyboard input,but non-interactive processes are unable to read inputfrom keyboard.


User response: Perform the following actions toresolve this error:

v Run the product in interactive mode.

v Ensure your password is set correctly.

ANS1117E The PICK and LATEST options are notvalid together

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


User response: Try again using either the PICK or theLATEST option.

ANS1118I Invalid file space number entered.Try again.

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

System action: TSM waits for your specification.

User response: Enter a correct file space number.

ANS1119I Initiating the removal of 'filespace-name'file space.

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



ANS1120E Removal of file space 'filespace-name'failed

Explanation: An attempt was made to delete afilespace (either NAS or normal) and it wasunsuccessful.

v Your client registration may not be authorized todelete filspaces on the server. Look for messageANS1126E.

v The named filespace does not exist on the server.Look for message ANS1122W.

v Other causes which will be made known in messagesfollowing this one


User response: Take action as recommended by othermessages that accompanies this one. If so indicated, try

to remove the file space again. If the problemcontinues, your TSM administrator has the authority todelete the file space for you.

ANS1121I A request for removal of file space'filespace-name' has been successfully sentto the server.

Explanation: TSM has requested deletion of thespecified filespace-name. The deletion process may nothave actually been completed when this message isdisplayed. To verify successful deletion, consult theserver logs.

It is possible for errors to occur on the server duringthe deletion process, or the file space might containarchive objects in deletion-hold status. In either case,the file space will not be deleted.



ANS1122W File space 'filespace-name' does not existon the server. The file space mighthave been deleted by another clientusing your client's node name oran administrator.

Explanation: The specified filespace-name does not existon the server. Your system administrator deleted thefile space or another client using your client’s nodename might have deleted it.



ANS1123E The vertical screen dimension is toosmall to display theHelp directory. Increase your windowheight.

Explanation: Execution of the HELP commandrequires space for both the user prompts and at leastone 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 displaywindow to allow more rows of text to be displayed.

ANS1125E Unmatched Quotes: 'string'



User response: Correct the pattern using matchingquotes in the syntax.



ANS1126E The file space cannot be deleted becausethis node does not have permission todelete archived or backed up data.

Explanation: You cannot delete the file space dataunless your TSM administrator has authorized yournode to do so. Authorization permits you to deletebackup data, archive data, or both.

System action: Delete processing fails.

User response: Use the DSMC QUERY SESSIONcommand to verify your authorization. Ask your TSMadministrator to provide the necessary authorization orto delete the file space for you.

ANS1127E Your node does not have permission todelete archived files.

Explanation: You cannot delete archived files unlessyour TSM administrator has authorized your node todo so.

System action: TSM does not delete the archived files.

User response: Use the DSMC QUERY SESSIONcommand to verify your authorization. Ask your TSMadministrator to provide the necessary authorization.

ANS1128S The management class assigned todirectories does not exist.

Explanation: The management class named on theDIRMC option does not exist in your assigned policyset on the server. The error log contains an entryshowing the invalid management class name.


User response: Remove the current DIRMC optionfrom the client options file, then run DSMC QUERYMGMTCLASS -DETAIL to view information aboutavailable management classes. Make sure themanagement class you select has a backup copy group.If you have more than one TSM server, make sure youare connecting to the correct server. If you are unable tofind a suitable management class, contact your TSMadministrator for further assistance.

ANS1129S There is no backup copy group in themanagement class used for directories.

Explanation: The DIRMC option names amanagement class that contains no backup copy group.


User response: Remove the current DIRMC optionfrom the client options file, then run DSMC QUERYMGMTCLASS -DETAIL to view information aboutavailable management classes. Make sure themanagement class you select has a backup copy group.If you have more than one TSM server, make sure youare connecting to the correct server. If you are unable to

find a suitable management class, contact your TSMadministrator for further assistance.

ANS1130E The drive has no label. The operationcannot continue.

Explanation: Backup or archive of removable mediarequires that the media have a volume label. Anattempt was made to back up or archive data on aremovable volume that has no label.


User response: Create a volume label on theremovable media, then try the operation again.

ANS1131E A duplicate volume label exists. Theoperation cannot continue.

Explanation: For removable media, TSM uses thevolume label as the file space name. To prevent datafrom different volumes being stored in the same filespace on the TSM server, backup or archive ofremovable media volumes having duplicate volumelabels is not allowed.


User response: Change the volume labels on theremovable media volumes so that there are noduplicate labels. Then restart TSM and try theoperation again.

ANS1132E 'Access rule' Access Rule already definedfor node 'node'.Old rule must be deleted before newone can be defined.

Explanation: You are trying to define authorization forthe specified node, which already has authorizationdefined.

System action: TSM did not redefine authorization forthe specified node.

User response: Update the authorization, or delete theold rule and define a new one, or use the currentauthorization.

ANS1133W An expression might contain a wildcardnot enclosed in quotes.

Explanation: The command cannot be processedbecause a UNIX shell expands a wildcard expression,such as an asterisk (*) or a question mark (?), that hasno quotes.

If the expression contains no wildcard characters andyou wish to place more than the stated limit ofoperands on the Archive, Selective, or Incrementalcommand, add the -REMOVEOPERANDLIMIT optionto the command, and try it again.

System action: Command dependent.



User response: Enclose the wildcard expression inquotes, or add the -REMOVEOPERANDLIMIT optionand enter the command again.

ANS1134E Drive drive-name is an invalid drivespecification

Explanation: The specified drive name is not valid;the drive probably has not been defined.

System action: TSM skips the invalid drive andcontinues to the next drive.

User response: Check the invalid drive.

ANS1135E Drive drive-name1 is a virtual drive ofdrive-name2. It cannot be backed up orarchived.

Explanation: One drive is a substitute (SUBST) of theother drive. The SUBST drive cannot be backed up orarchived.

System action: The SUBST drive is skipped.Processing continues with the next drive.

User response: Do not specify any file specificationsfor a drive that is a substitute of another drive. Removeany explicit substitute drives from the DOMAINstatement or use the -<drive:> notation to remove asubstitute drive if ALL-LOCAL is specified.

ANS1136E Not file owner

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

System action: TSM skips the file.


ANS1137W Invalid Index 'number' skipped.

Explanation: An incorrect number was entered for theIndex.


User response: Correct the Index entry and retry theoperation.

ANS1138E The 'command-name' command must befollowed by a subcommand

Explanation: You entered an incompletecommand-name.


User response: Enter the correct syntax of thecommand and continue.

ANS1139W 'object-nameobject-nameobject-name' wasrestored as 'temp-name'. A reboot isrequired to complete the restore.

Explanation: The file being restored was in use byanother application, so it could not be immediatelyreplaced. The file will be replaced during the nextreboot of the operating system. It is important to notethat until the reboot occurs, the system or itsapplications might be unstable. The degree ofinstability depends on the criticality of the file to theoperating system or applications.

System action: TSM restored the file with a temporaryname, and instructed the operating system to replacethe original file with the restored file during the nextboot of the operating system.

User response: Reboot the machine as soon aspossible after the TSM restore operation ends.

ANS1140E Invalid format for Set Access command.

Explanation: The SET ACCESS command must haveat least three operands, the first of which must beeither BACKUP or ARCHIVE. A validly formed filespecification must follow.

System action: Processing stopped, the command isnot executed.

User response: Use the HELP SET ACCESS commandfor complete details of usage, then enter the SETACCESS command using the correct syntax.

ANS1141W Unknown command - command-name

Explanation: You entered an incorrect command-name.


User response: Enter the correct command.

ANS1143E The DIRSONLY and FILESONLYoptions are not valid together

Explanation: The DIRSONLY and FILESONLY optionscannot be used together.


User response: Try again using either the DIRSONLYor the FILESONLY option.

ANS1144W Password authentication not active onserver

Explanation: None.


User response: Because password authentication isturned off on the server, you do not need to update thepassword.



ANS1145E The maximum macro nesting level hasbeen exceeded. Macros may be nestedup to 10 levels.

Explanation: TSM allows macros to invoke othermacros, for example, macro 'A' invokes macro 'B'which, in turn, invokes macro 'C'. This is nesting to 3levels. The limit is 10 levels (the inital macro plus ninelevels of calls within macros currently executng). Thereis no limit to the number of different macro calls thatmay be made within a macro as long as the calls arenot nested.

System action: The macro is ignored and an error isreturned.

User response: Reduce the level of macro nesting.

ANS1146E Macro file 'file spec' cannot be opened.

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


User response: Enter the command with the propermacro name.

ANS1147E File is temporarily unavailable.

Explanation: File is temporarily unavailable.


User response: Check and see if file is locked by otherprocess. If not, retry the command.

ANS1148I 'Command-name' command successfullycompleted

Explanation: The specified command-name wassuccessfully completed.

System action: TSM completed the command.

User response: Continue with normal operations.

ANS1149E No domain is available for incrementalbackup. The domain may be empty orall file systems in the domain areexcluded.

Explanation: An incremental backup was started, butno domain was selected. Possible reasons for thismessage include:

v An attempt was made to back up a file system that isexcluded with the EXCLUDE.FS option.

v The DOMAIN is empty. That is, a DOMAINstatement excludes one or more file systems, but noDOMAIN statements include any file systems.

v DOMAIN ALL-LOCAL is in effect but the systemhas no local file systems.


User response: Verify that the DOMAIN statementsare properly configured and try the backup again.DOMAIN statements can be in client option files(dsm.opt, dsm.sys), client option sets, scheduledefinitions, and scripted TSM commands. Correctiveactions include:

v Make sure the DOMAIN option settings specify thefile systems you want to back up.

v If a file system that should be backed up is excludedby an EXCLUDE.FS statement, remove theEXCLUDE.FS statement.

v If a file system that should not be backed up is listedin a DOMAIN statement, remove the file systemfrom the DOMAIN statement.

v Make sure the DOMAIN is not empty. That is, if anyDOMAIN statements exclude file systems frombackup, make sure the DOMAIN statements includethe file systems that should be backed up.

ANS1150E Unable to restore current user profilebecause you are running asa local system account.

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


User response: Log on to the user whose profile youwant to restore.

ANS1151E 'drive-name1' is not a cluster disk.

Explanation: The indicated file system is not a clusterdisk. Because the CLUSTERNODE option is set to YES,the file system cannot be backed up or archived.


User response: If the CLUSTERNODE option isincorrectly set to YES, then change the option to NOand try the operation again. Otherwise see the clientmanual for further information about configuring theTSM client to run in a cluster environment.

ANS1152W The kernel level is below the requiredlevel for LVM support. No LVMvolumes will be available for imageoperations.

Explanation: The LVM support for image operationsrequires kernel level to be minimum at 2.6. LVMvolumes will not be recognized by the TSM client.

System action: All subsequent logical volumeoperations on LVM volumes will fail.

User response: Use earlier versions of the client thatsupport LVM1 to perform the logical volumeoperations. Alternatively, you can upgrade the kernel to



the required level to fully utilize logical volumeoperations on LVM2.

ANS1153E 'drive-name1' is a cluster disk.

Explanation: The indicated file system is a clusterdisk. Because the CLUSTERNODE option is set to NO,the file system cannot be backed up or archived.


User response: If the CLUSTERNODE option isincorrectly set to NO, then change the option to YESand try the operation again. Otherwise see the clientmanual for further information about configuring theTSM client to run in a cluster environment.

ANS1154E Object name 'filespacenamepath-namefile-name' contains aninvalid multibyte sequence for thecurrent locale.

Explanation: An illegal multibyte sequence for thecurrent locale was found in the object name. Either thepath or file name has been corrupted or is coded in alanguage other than that of the current locale.

System action: Object skipped.

User response: If the file name and path are notcorrupted, process the file in the locale for which it isvalid.

ANS1155E No domain is available for imagebackup.

Explanation: An image backup was started, but nodomain was specified.


User response: Choose a domain and restart theimage backup. Set the image domain using thedomain.image option in your dsm.opt file, eithermanually, or by using the GUI preferences editor.

ANS1156E NODENAME cannot be the localmachine name when CLUSTERNODE isset to YES

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


User response: Change the node name either to thecluster name or to any other name, and restart TSM.

ANS1157E The registry cannot be backed up orrestored when the client is running as acluster node.

Explanation: When the CLUSTERNODE option is setto YES, the registry cannot be backed up or restored.

System action: The registry is not backed up orrestored.


ANS1158E The event logs cannot be backed up orrestored when the client is running as acluster node.

Explanation: When the CLUSTERNODE option is setto YES, the event logs cannot be backed up or restored.

System action: The event logs are not backed up orrestored.


ANS1159E The specified file is being used byanother process

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



ANS1162E Filesystem could not be mounted

Explanation: The system call to mount the file systemfailed.

System action: The file system remains unmounted.

User response: Use the mount command to mount thefile system. On AIX, run fsck if requested by theoperating system.

ANS1163E Filesystem could not be unmounted.

Explanation: The system call to unmount the filesystem failed.


User response: Make sure the device or file system isnot being accessed, then retry the operation.



ANS1164E Filesystem is not mounted

Explanation: The named file system is not currentlymounted. It must be mounted for TSM to perform animage backup.


User response: Mount the file system.

ANS1165E Destination is smaller than source

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

System action: The restore operation is not performed.

User response: Choose a different, bigger destinationor increase the size of the destination file space.

ANS1166E Source and destination are not the samefile system type.

Explanation: The source and destination file systemtypes do not match.


User response: Choose a destination that has the samefile system type as the source.

ANS1168E ERROR: could not create image object.

Explanation: Creation of the image object failed forone of the following reasons:

v The image command was executed by a non-rootuser

v The image plugin library was not found.

System action: The requested logical volume functionis not performed.

User response: Retry the operation after correcting thecause for failure.

ANS1169W There is no table of contents forimage-name.

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

System action: No table of contents is displayed.

User response: Select another image object for TOCdisplay.

ANS1170I Invalid selection number entered.Try again.

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

System action: TSM waits for you to enter a validselection.

User response: Enter a number from the list or 'Q' toquit.

ANS1177E Must specify a path for this operation.

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


User response: Specify a valid path and execute thecommand again.

ANS1181E There was a communication failure withthe journal service.

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


User response: Restart the journal service, then try theoperation again. If the problem persists, contact IBMtechnical support for further assistance.

ANS1183E An unknown error occurred whileprocessing system object 'sys-obj-name':MS API function 'func-name' failed witherror error (error)

Explanation: An unknown error occurred whileprocessing a system object. The error informationcaptured indicates the reason for the failure. Thisinformation can be used to diagnose the problem.



ANS1184W The command subcommand command isnot supported on this client.

Explanation: The command subcommand command isnot supported for the client running on this operatingsystem on this computer.

System action: The command is not processed.


ANS1185E The help search argument you supplied"string" is either too long or containsunmatched quotes.

Explanation: Valid arguments are the names of thingslike section numbers, command names, option namesand message numbers. All of these search argumentsare short and none requires quoting.

System action: The help request is not executed andyou are given another chance to enter a valid



argument, display the table of contents, or exit help.

User response: Respond to the subsequent prompt asdirected.

ANS1186I The help file contains no message helpsection. Requests for message help willall result in topic not found.Enter a section number, option name,command name,or a command and subcommand.Otherwise press enter or 't' to displaythe table of contents or 'q' to exit help:

Explanation: The named file does not have the propercontent to support the help command for messages.The initial scan of the help file found no messagessection.

System action: The help command pauses and allowsyou to make another selection.

User response: During installation of TSM a properhelp file was created. Your system administrator canassist you with retrieving the original help file toreplace the named invalid file.

ANS1187E The named helpfile "filename" hasinvalid content.

Explanation: The named file does not have the propercontent to support the help command. One or moresections could not be identified.

System action: The help command is terminated.

User response: During installation of TSM a properhelp file was created. Your system administrator canassist you with retrieving the original help file toreplace the named invalid file.

ANS1188E The selected filesystem is managed byHSM, and therefore is not a valid objectfor image operations

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



ANS1189E The DIRSONLY and V2ARCHIVEoptions are not valid together

Explanation: The DIRSONLY and V2ARCHIVEoptions cannot be used together.


User response: Try again using either the DIRSONLYor the V2ARCHIVE option.

ANS1190E Symbolic link 'linkname' to 'target' wassuccessfully deleted.

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. Tospecify the location of log files, refer to the user'smanual for the 'errorlogname' option, the'schedlogname' option, and the 'DSM_LOG'environmental variable.

ANS1191E Unable to delete symbolic link 'link'.

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


User response: Delete the symbolic link 'linkname'.

ANS1192E Specifying the error log 'link' as asymbolic link is not allowed.

Explanation: Error log 'linkname' cannot be a symboliclink.

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

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

ANS1193E Specifying the trace file 'link' as asymbolic link is not allowed.

Explanation: For reasons of security and systemintegrity, the trace file 'linkname' cannot be a symboliclink.

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

User response: Use the TRACEFILE option to specifythe actual trace file location without the use ofsymbolic links.

ANS1199E The PRESNAPSHOTCMD commandfailed. The image snapshot backup willnot be executed.

Explanation: The command specified by thePRESNAPSHOTCMD option must completesuccessfully in order to execute the image snapshotbackup. If the command completed with a return codeof 0 (zero), it is considered to have completedsuccessfully. If the command completed with any otherreturn code, it is considered to have failed. If thecommand failed then the image snapshot backup is notexecuted.



System action: The client does not execute the imagesnapshot backup operation.

User response: Identify and repair the problem thatcaused the command to fail. If a non-zero return codeis normal for this command, then consider wrappingthe command in a script that always exits with a returncode of zero.

ANS1200W The POSTSNAPSHOTCMD commandcompleted with a non-zero return code.

Explanation: If the command specified by thePOSTSNAPSHOTCMD option completed with anon-zero return code, then the image snapshot backupoperation will continue, but with a warning-levelresult. Note that the result of thePOSTSNAPSHOTCMD command will not supercede ahigher result from the image snapshot backupcommand. For example, if the image snapshot backupcommand completed with a return code of 12, theimage snapshot backup will be considered to havecompleted with a return code of 12, regardless of theoutcome of the POSTSNAPSHOTCMD command.

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


ANS1201E TSM cannot build a directory pathbecause a file exists with the same nameasthe directory.

Explanation: None


User response: Remove or rename the file that has thesame name as the directory. Alternatively, you canrestore the directory to a different location.

ANS1202E TOC backup for the image failed. Checklog files.

Explanation: An error occurred during backup of thetable of contents. Check the error log for moreinformation.


User response: Check error log.

ANS1203E Table of Contents not available forselected backup set. Please contactserver administrator.

Explanation: There is no TOC for selected backup set

System action: Expansion of selected backup set willnot be possible. Will only be able to restore the wholebackup set.

User response: Please contact server administrator toregenerate TOC for backup set before backup set can beexpanded.

ANS1204E This client is not supported by the TSMexpress server

Explanation: This client is not supported by the TSMexpress server. This can occur if:

1. the client is configured as an TSM express clientusing the CLIENTVIEW option

2. the client is trying to connect to an TSM expressserver.


User response: Log in using a supported TSM expressclient.

ANS1205E This is not a supported TSM expressplatform

Explanation: This is not a supported TSM expressplatform.


User response: Log in using a supported TSM expressclient.

ANS1206E TOC backup of a raw device is notsupported. But the raw device is backedup.

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

System action: Raw device is backed up with no TOCobject.

User response: NONE.

ANS1207E No TOC has been previously backed upfor this file system.

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

System action: Query stopped.

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



ANS1209E The option_name option is not supportedwith the command_name command usingthe -FILELIST option.

Explanation: The specified option is not supportedwith the specified command when the -FILELISToption is also specified.


User response: >Do not specify the offending optionwhen the -FILELIST option is specified with thiscommand.

ANS1212I Invalid Process number entered.Try again.

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



ANS1213W Snapshot image backup is not possiblefor device device-name.starting static image backup.

Explanation: On Linux platforms, snapshot imagebackup is only possible for logical volumes created bythe Linux logical volume manager (LVM). Since thedefault image backup type is snapshot, backing up apartition which is not created using LVM automaticallyleads to a static image backup.

System action: Snapshot image backup will failover tostatic image backup

User response: To avoid this message, use theimagetype option to specify static or dynamic imagebackup.

ANS1214E The logical volume group does not haveenough free space to contain the volumesnapshot.

Explanation: The snapshot is created in the volumegroup that contains the logical volume being backedup. There is insufficient free space in the volume groupto contain the snapshot.

System action: The operation ends.

User response: Decrease the SNAPSHOTCACHESIZEvalue or make additional space available in the logicalvolume group. Then try the operation again.

ANS1215E On volumes that are RAW or formattedFAT32 the snapshot cache locationcannot be located on the same volumethat is being backed up.

Explanation: When the snapshot cache location islocated on the same volume that is being backed up thevolume must be formatted with NTFS. The defaultcache location is on the same volume where thesnapshot is being performed.

System action: The client does not execute the imagesnapshot backup operation.


ANS1216E Not authorized to run TSM. See theadministrator for your system.

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

System action: TSM initialization fails and theprogram ends.

User response: See the TSM administrator for yoursystem, and ask to be added to the user or group listfor this server.

ANS1217E Server name not found in SystemOptions File

Explanation: The system options file does not containthe SERVERNAME option.


User response: See the TSM administrator for yoursystem, and make sure that the system options filecontains the server name.

ANS1218E TCPSERVERADDRESS not defined forthis server in the System Options File

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


User response: See the TSM administrator for yoursystem, and make sure that the server to which you aretrying to connect, has a valid TCPSERVERADDRESSdefined in the system options file.



ANS1219E A virtual node name must not equaleither a node name or the system hostname.

Explanation: A VIRTUALNODENAME option wasentered with a name the same as either a NODENAMEoption or the system host name.

System action: Initialization fails and the programends.

User response: If the virtual node name entered wasthe same as the host name, remove the virtual nodename option. If it was the same as the node nameoption, you can remove either one, depending upon theintended usage. Node name is used to assign analternate name to your system. Virtual node name isused to access another system's server data.

ANS1220E The TSM server is out of resources.

Explanation: A lack of a storage resource or amaximum value condition does not allow any newactivity.


User response: Try the operation again at a later time.If the problem continues, contact your TSMadministrator to isolate what resource is unavailable.The TSM administrator can check the TSM serveractivity log for messages that might explain theproblem.

ANS1221E Transaction aborted

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


User response: Retry the operation. If the problemcontinues, see your system administrator to isolate theproblem.

ANS1222E Disk space limit for this process reached

Explanation: The disk space allocated for the clientowner is full.


User response: Free up disk space and retry therestore or retrieve operation.

ANS1223E File is not compressed; System failure.

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


User response: See your system administrator toreport this problem. This error is a system failure.

ANS1224E File compressed on a different clientmachine that has more memory

Explanation: You are trying to restore a file that wasbacked up and compressed on another clientworkstation that had more memory than your clientworkstation. You cannot restore this file. When the fileis restored, it is expanded and your workstation doesnot have enough memory.

System action: TSM canceled the operation.

User response: Obtain a machine with more memoryand retry the operation.

ANS1225E Insufficient memory for filecompression/expansion

Explanation: Not enough memory is available to dodata compression or expansion. For a restore orretrieve, the file cannot be recalled from the server untilmore storage is made available. For a backup orarchive, try running without compression if storagecannot be made available.


User response: Free up extra storage for the operationto continue, or run the backup or archive processwithout compression enabled.

ANS1226E Destination file or directory is writelocked

Explanation: The file or directory being restored orretrieved from the server cannot be written to becausethe destination is write locked. Another operationmight have the file open and will not allow it to beupdated.


User response: Either determine which operation hasthe file write locked, or restore the file to another nameor location.

ANS1227E Processing stopped; Disk full condition

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



ANS1228E Sending of object 'object-nameobject-nameobject-name' failed.

Explanation: The specified file (object-name) cannot besent to the server. This message is accompanied by atleast one other message that has more specificinformation about why the file could not be processed.




User response: Check previous messages pertaining tothis file that indicate the reason for the failure. Whereapplicable, correct the conditions that prevented the filefrom being sent to the server. The specific correctiveactions will depend on the reason for the failure.

ANS1229E MODE=INCREMENTAL is not valid onfile-space. Image backup not processed.

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

System action: File system skipped.

User response: If an image backup of the named filespace is desired, retry the command without theMODE=INCREMENTAL option. To prevent thisbehavior in the future, delete the file space from theserver and do only BACKUP IMAGE -mode=selectiveand BACKUP IMAGE -mode=incremental from thatpoint on.

ANS1230E Stale NFS File Handle

Explanation: An NFS file system becomes stale.


User response: Check the NFS mounted filesystem.

ANS1231E No file handles available

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


User response: Either free some file handles by endingother processes, or modify your system setup to allowfor more files to be open at the same time.

ANS1232E The file exists and cannot beoverwritten.

Explanation: The file being restored or retrieved existsand cannot be overwritten due to lack of authority oraccess permissions.


User response: Verify that you have sufficient accesspermissions to overwrite the file, then try the operationagain. If the problem persists, contact your systemadministrator or TSM administrator for furtherassistance.

ANS1233E An invalid file handle was passed;system error.

Explanation: An internal system error occurred: A fileoperation failed because of an invalid file handle.


User response: Try the operation again. If the failurepersists, obtain a service trace that captures theproblem and contact IBM technical support foradditional assistance. Your TSM administrator can helpyou configure the trace.

ANS1234E Protocol violation

Explanation: A communications protocol erroroccurred. The communication subsystem is notproperly defined or is itself in error.


User response: Verify that the communicationprocesses are operating properly, and then retry theoperation.

ANS1235E An unknown system error has occurredfrom which TSM cannot recover.

Explanation: An unknown error occurred. This mightbe a low-level system or communication error fromwhich TSM cannot recover.


User response: Try the operation again. If the problempersists, review the TSM error log for any relatedmessages. Obtain a service trace that captures theproblem and contact IBM technical support foradditional assistance. Your TSM administrator can helpyou configure the trace.

ANS1236E An unexpected error occurred.

Explanation: This is usually caused by a low-levelsystem error or communication error from which TSMcannot recover.


User response: Examine the client error log for anyadditional messages that might be related to thisproblem. Try the operation again. If the problempersists, contact TSM technical support for furtherassistance.

ANS1237E A problem has occurred on the TSMserver.

Explanation: The TSM client error log and the TSMserver activity log might contain additional informationabout this error.




User response: Try the operation again. If the problempersists, examine the TSM client error log and TSMserver activity log for additional information about thiserror. If the problem cannot be resolved, then obtain aSERVICE trace that captures the problem and contactIBM technical support for additional assistance. YourTSM administrator can help you configure the trace.

ANS1238S A policy management problem hasoccurred on the TSM server.

Explanation: The TSM client error log and TSM serveractivity log may contain additional information aboutthis error.

System action: Processing is stops.


ANS1241E File is in use; Write permission denied.

Explanation: The current file cannot be opened towrite to because it is currently being run by anotheroperation.


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

ANS1242E Too many symbolic links were detectedwhile resolving name

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


User response: Ensure that you do not have a loopingsymbolic link for the file.

ANS1243E The file name is too long and can not beprocessed by TSM

Explanation: The size limit for file names may vary byoperating system. The most common limit is 256characters. The file name being processed exceeds thelimit supported by TSM on this system.


User response: Enter HELP FILE SPEC or see theclient manual for the operating system on which youare receiving this error. The "File specification syntax"section of the manual explains file name lengthssupported by TSM.

ANS1244E File system is locked by system

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

System action: TSM cannot complete the operation.


ANS1245E The file has an unknown format.

Explanation: TSM tried to restore or retrieve a file, butit had an unknown format.


User response: The file was either backed up byanother application, or the data is invalid. If the filebelongs to this system, try the operation again. If theproblem persists, contact IBM technical support forfurther assistance.

ANS1246E A command-line argument exceeded themaximum length (maximum length) for asingle token.

Explanation: Command-line arguments may notexceed maximum length characters.


User response: Correct the command and retry theoperation.

ANS1247I Waiting for files from the server...

Explanation: Restore request has been sent to theserver. The wait time depends on how many files youare restoring.

System action: TSM waits for files to restore from theserver.


ANS1248E An active restore for the same sourcefile specification exists.Unable to continue with this request.

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

System action: The requested restore fails.

User response: Start another restore with a differentsource file specification.

ANS1249W Server cannot restart the last restorerequest.Do you want to restore without restartor abort the request?

Explanation: The restart restore token has expired.

ANS1238S • ANS1249W


The server cannot restart the restore from where it lastended.

System action: Processing stopped; waiting for userintervention.

User response: Retry the request without restart orabort the request.

ANS1251E File system/drive not ready

Explanation: The file system/drive was not ready foraccess.


User response: Ensure that the drive is available toTSM, and then retry the operation.

ANS1252W The server that you are connected todoes not support this function.

Explanation: You attempted to run a backup-archiveclient operation when connected to the virtual server.Backup-archive client operations are not supportedwhen connected to the virtual server.

System action: The operation fails.

User response: Connect to a valid server beforeattempting this function.

ANS1253E File input/output error

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

System action: File or file system is skipped.

User response: Check your system to ensure that it isoperating properly. For OS/2, run CHKDSK /F for thefailing drive which can be found in dsmerror.log.

ANS1254E File write error

Explanation: An error was found while writing to thefile.


User response: Check your system to ensure that it isoperating properly.

ANS1255E File exceeds system/user file limits

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


User response: Ensure that the system limits are setproperly.

ANS1256E Cannot make file/directory

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


User response: Ensure that you have the properauthorization to create the directory for file beingrestored or retrieved. Make sure that you have writeaccess.

ANS1257E An error occurred while preparing thesystem object for restore.

Explanation: This message is typically issued whenthe client is unable to delete the ADSM.SYS stagingdirectory in preparation for restoring the system object.

System action: The system object is not restored.

User response: Check the error log for any othermessages that might indicate a reason for the failure,correct any indicated problems, then try the operationagain. If the problem occurs again, manually delete theADSM.SYS directory, then try the operation again. Ifthe problem cannot be resolved, contact IBM technicalsupport for further assistance.

ANS1258E The image snapshot operation failed.

Explanation: TSM was not able to take a snapshot ofthe specified volume.



ANS1259E The image snapshot operation failed.Diagnostic text: diag_text.

Explanation: An error was encountered during imagebackup snapshot processing. The diagnostic text canvary, depending on the error.


User response: Examine the client error log foradditional messages that might indicate the reason forthe problem. Take any corrective action suggested bythe messages, then try the operation again. If theproblem persists, contact IBM technical support forfurther assistance.

ANS1260E File is being recalled or has beenrecalled.

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




User response: None

ANS1261W The archive description you specified isthe empty string.TSM will use the default description(Archive Date: current date).

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

System action: Processing continues, and thedescription option is ignored.

User response: None. Specify at least one character inthe description

ANS1262E The password is not updated. Either aninvalid current password was suppliedor the new password does not fulfill theserver password requirements.

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

v You entered an incorrect current password or

v You entered a new password that does not fulfill thepassword length requirements. The lengthrequirements are set on the server.


User response: Enter another password.

ANS1263E The active policy set does not containany backup copy groups. The backupoperation can not continue.

Explanation: In order to back up files, the policy setmust contain at last one backup copy group.

System action: TSM did not backup the file.

User response: The TSM administrator needs toupdate or define at least one management class in yourpolicy set that contains a backup copy group, or elseassign you to a different policy domain that contains atleast one backup copy group. Contact your TSMadministrator for further assistance.

ANS1264E The active policy set does not containany archive copy group. The archiveoperation cannot continue.

Explanation: In order to archive files, the policy setmust contain at least one archive copy group.

System action: TSM did not archive the file.

User response: The TSM administrator needs toupdate or define at least one management class in yourpolicy set that contains an archive copy group, or elseassign you to a different policy domain that contains atleast one archive copy group. Contact your TSMadministrator for further assistance.

ANS1265E Encountered bad mount or filesystem,processing stopped.

Explanation: The getmnt system call returned an errorindication. Error was encountered trying to determinewhat the mounted file systems are.

System action: Processing stopped. Cannot recover.

User response: There is a bad file system or mountpoint on your system. Look at file systems and mounts,and correct any errors. If unsuccessful, see your systemadministrator for more information.

ANS1266E Encountered bad mount or filesystem,processing stopped.

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

System action: Processing stopped. Cannot recover.

User response: Please, see your system administratorfor more information.

ANS1267E The management class for file file-namedoes not allow migration. This file willnot be migrated.

Explanation: The management class for this file doesnot allow migration

System action: File is skipped.

User response: Either have the TSM administratorchange the Space Management Technique within themanagement class to a value other than NONE orchange the include/exclude list to specify amanagement class with the appropriate SpaceManagement Technique value.

ANS1268E This file has been migrated.

Explanation: The error can result from migrating a filewith hard links. After a file with hard links is migrated,attempts to migrate the alias files yield an error.


User response: If this error is not a result of a hardlinked file migration, then this error might be due tothe previous cancelled migration or recall operation. Inthis case, restart the dsmrecalld daemon and try theoperation again.

ANS1269I File is implicitly excluded.

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

System action: TSM will not back up or migrate animplicitly excluded file.


ANS1261W • ANS1269I


ANS1270E Running this command requires a validNetApp Snapshot Differential c-modelicense file.

Explanation: A NetApp Snapshot Differential c-modelicense file either does not exist or is not valid.


User response: Contact IBM support.

ANS1271E The compressed file is corrupted andcannot be expanded correctly.

Explanation: The compressed file cannot be expandedcorrectly due to one of the following reasons:

There is a problem on the tape.

There is a communications problem.

The compressed file was corrupted on the TSMServer.


User response: 1) The compressed file is corruptedbecause there is a problem on the tape. To know if thisis the problem, please issue the following command onthe TSM Server: audit volume <volume_name> fix=noIf there is any problem reported, you could move thedata from that volume to a new one (see commandMOVE DATA) and try again the restore. 2) There arecommunications problems between the TSM Server andthe TSM Client and the results is that the file iscorrupted during the transmission. If you use a gigabitEthernet adapter on the Server please upgrade the carddriver (AIX platform) or add provided by SUNsuggested changes to some system network optionswhich have resolved this problem (SUN platform). 3)Please verify with your network support if during therestore there are no any problems between the TSMClient/Server that is originating the file corruption.

ANS1272W Adaptive subfile backup has beenconfigured on the client but the serverdoesn't allow this type of backup.Adaptive subfile backup will not beused for this operation.

Explanation: Adaptive subfile backup forced off bythe server.


User response: Set up the server to allow clients toback up subfiles.

ANS1274E Error Loading WINSOCK.DLL

Explanation: Error loading the Windows socketsupport file into memory. This error only applies whenusing TCP/IP communications.


User response: Because this error is caused by

insufficient memory, shut down running applicationsand retry. If the problem persists, see your systemadministrator.

ANS1275E Error Loading Function(s) fromWINSOCK.DLL

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


User response: Since this might possibly be caused byinsufficient memory, shut down running applicationsand retry. If the problem persists, see your systemadministrator.

ANS1278W Virtual mount point 'filespace-name' is afile system. It will be backed up as afile system.

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

System action: The virtual mount point is ignored.

User response: Delete the virtual mount point.

ANS1279W Virtual mount point 'filespace-name'cannot be used in a file system handledby automounter and is ignored.

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

System action: The virtual mount point is ignored.

User response: Delete the virtual mount point.

ANS1286E -nasnodename option required for thisoperation.

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

System action: Operation aborted.

User response: Use -nasnodename option with thecommand or place nasnodename option in the optionfile.

ANS1287E Volume could not be locked.

Explanation: The system call to lock the volumefailed.


User response: Please verify that no other applicationis accessing the volume. If this volume is beingaccessed by applications that can not be shutdown



during backup then perform an online image backup(snapshot) instead. During restore of an image TSMmust have exclusive use of the volume.

ANS1288E The (-TYPE) option is required with theSET EVENT command.

Explanation: There is no default value for the -TYPEoption. It must be explicitly entered with the command.

System action: The current command ends.

User response: Enter the SET EVENT command againwith the TYPE option and a value of HOLD, RELEASE,or ACTIVATERETENTION.

ANS1289W Bad areas on 'volume' between sectorshi:lo and hi:lo

Explanation: Some bad sectors within the specifiedrange were detected on the volume during imageoperation.


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

ANS1300E File 'file_name' cannot be reconstructedbecause a necessary component was notrestored.

Explanation: The subfile backup technique was usedto back up this file. During the restore, a portion of thefile was not be obtained from the server.

System action: The file indicated in the message is notrestored. Restore for all other files continues.

User response: Try to restore the file again byselecting the file for restore from the user interface. Youcan also check the client error log and the serveractivity log for any messages related to the fileindicated in the message.

ANS1301E This operation cannot continue due toan error on the TSM server. See yourTSM server administrator for assistance.

Explanation: The TSM server encountered an errorcondition that prevents the TSM client operation fromcontinuing. Your TSM server administrator can reviewthe TSM server activity log for more details about theerror.


User response: Contact your TSM server administratorfor assistance. The administrator can review the TSMserver activity log for further information about theconditions that lead to this error.

ANS1302E No objects on server match query

Explanation: No objects on the server match the queryoperation being performed. If this object is part of abackupset generated on a node, and the node name ischanged on the server, any backup set objects that weregenerated prior to the name change will not match thenew node name.


User response: Ensure the names are properlyentered. If the object is part of a backupset generatedprior to a node name change, ensure that the nodename is the same as the node for which the backup setwas generated.

ANS1303E Client ended transaction

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


User response: Restart the session.

ANS1304W An active backup version could not befound.

Explanation: An attempt was made to expire anobject, but the TSM server was unable to find an activebackup version of the object. This message is precededby message ANS1228E which specifies the object name.For instance, this message could be issued if twoseparate client processes are backing up the same filesystem at the same time. If one of the processes expiresa file, then the TSM server will make that file inactive.If the second process subsequently attempts to expirethat same file, the TSM server will not find an activeversion of the file, so the second process will issue thismessage for that file.

System action: The object is not expired. Processingcontinues with the next object.

User response:

v Review the console output, schedule log, or error logand locate the ANS1228E message that immediatelyprecedes this message. ANS1228E will identify theobject that could not be expired.

v Examine the conditions under which the problemoccurred and assess whether those conditions explainthe occurrence of this message. For example, thismessage could appear if multiple instances of theclient were attempting to back up the file systemconcurrently.

v If the reason this message occurred can not bedetermined and the message occurs when theoperation is tried again, then contact IBM support forfurther assistance. Also try searching for this messagenumber on http://www.ibm.com for possiblesolutions.



ANS1305E The TSM server has no data for theobject.

Explanation: TSM tried to do a restore or retrieve onan object that has no data associated with it. If acorrective action is possible, it is with the TSM server.

System action: TSM ends the current operation.

User response: Ask the TSM administrator to checkthe TSM activity log for any messages related to thiserror that might help identify the problem.

ANS1306E You entered an incorrect password.

Explanation: You entered an incorrect currentpassword or you entered a new password that does notfulfill the password length requirements set on theserver.


User response: Retry the session with the correctpassword. If this fails or you have forgotten yourpassword, ask the TSM administrator to assign a newpassword.

ANS1307E Node in use

Explanation: The node you are running on is in useby another operation on the server. This might be fromanother client or from some activity on the server.


User response: Retry the operation, or see yoursystem administrator to see what other operations arerunning for your node.

ANS1308E Expiration date must be greater thantoday's date

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


User response: Retry archiving the file with anexpiration date that is higher than today’s date.

ANS1309I The requested data is offline.

Explanation: For the restore or retrieve operation, oneor more of the requested files must be recalled fromoffline storage media (generally tape). The wait timedepends on your site’s offline storage managementpolicies.

System action: TSM waits for offline storage media tobecome available and then continues.


ANS1310E Object too large for server limits

Explanation: The object is too large. The configurationof the server does not have any data storage space thataccepts the object.


User response: See your system administrator todetermine the maximum file (object) size for whichyour site’s server is configured.

ANS1311E Server out of data storage space

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


User response: You can take any of the followingactions:

v Request the system administrator to add space to thestorage pool.

v For TSM client, set COMPRESSALWAYS=NO andCOMPRESSIon=YES in the options file (DSM.OPT),then the file will be resent uncompressed if it growsduring compression.

v For API Applications, consult the application'sdocumentation for recommendations regardingcompression.

v Turn off disk caching in the disk storage pool, andissue MOVE DATA commands to each disk poolvolume to clear out the cached bitfiles.

ANS1312E Server media mount not possible

Explanation: Server media mount not possible. Theserver timed out waiting for a mount of an offlinevolume.


User response: Retry later when server volumes canbe mounted. Ensure that the MAXNUMMP (maximumnumber of mount points) defined on the server for thisnode is greater than 0.

ANS1313E Size estimate exceeded

Explanation: The total amount of data for a backup orarchive operation exceeds the estimated size originallysent to the server for allocating data storage space. Thishappens when many files are growing by largeamounts while the backup or archive operation is insession.


User response: Retry the operation. If the problemcontinues, check what other processes are running onthe client machine that are generating large amounts ofdata. Disable those operations while the backup orarchive operation is taking place.



ANS1314E File data currently unavailable on server

Explanation: The file data is currently unavailable onthe server. A retrieve or restore operation wasattempted. Possible causes are:

v Data was corrupted at the server

v Server found a read error

v File is temporarily involved in a reclaim operation atthe server

v Server requested a tape volume that was markedunavailable.


User response: Retry the operation. If the problemcontinues, see your system administrator to determinethe problem from the server console or the activity log.Check whether any requests were made for a tapevolume that was unavailable. A tape volume may bemarked unavailable if prior read errors wereencountered or the volume is checked out of the tapelibrary.

ANS1315W Unexpected retry request. The TSMserver found an error while writing thedata.

Explanation: None.

System action: If the current operation supportsanother attempt, the client tries the operation again.Otherwise, processing stops.


ANS1316E The server does not have enoughrecovery log space tocontinue the current operation

Explanation: The server ran out of recovery log space.


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

ANS1317E The server does not have enoughdatabase space to continuethe current operation

Explanation: The server ran out of database space.



ANS1318E The server does not have enoughmemory to continue the currentoperation.

Explanation: The server ran out of memory.


User response: This is a temporary problem. Retrylater or see your system administrator.

ANS1319E An error occurred on the IBM TivoliStorage Manager server while trying torename file space file_space_name

Explanation: None.

System action: Because the file space cannot berenamed, the operation stops.

User response: Check the client error log and the IBMTivoli Storage Manager server activity log for any othermessages that might help identify the problem. If theproblem cannot be resolved, contact IBM technicalsupport for additional assistance.

ANS1320E The specified file space does not existon the server. Thefile space might have been deleted byanother client or anadministrator.

Explanation: The specified file space does not exist onthe server. Your system administrator deleted the filespace or another client using your client’s node namedeleted it.


User response: Check the file space name to see if it iscorrect, and retry the operation.

ANS1321S Open Registration failed because thespecified node name is defined in theserver

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


User response: Retry with another node name.

ANS1322S Open Registration failed because nodefault domain exists

Explanation: Open registration failed because adefault policy domain does not exist for you to placeyour node.



ANS1323S Open Registration failed because aninvalid node name was specified

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


User response: Retry with another node name that



does not have any invalid characters.

ANS1326S The TSM server does not currently havespace in the storage pool for this file.This may be a temporary condition.

Explanation: This message is typically issued whenthe storage pool in which the data is being placed doesnot have sufficient space to store the data, but thespace will be available soon. For example, a storagepool migration might free up sufficient space to storethe data.


User response: Try the operation at a later time. If thisfails, contact the TSM administrator and request morestorage pool space.

ANS1327W The snapshot operation for 'volname'failed with error code: retcode.

Explanation: A snapshot could not be taken of thespecified volume.

System action: Snapshot processing stopped.

User response: Check the client error log for any othermessages that might help identify the problem. If theproblem cannot be resolved, contact IBM technicalsupport for additional assistance.

ANS1328W An error occurred generating delta filefor 'file-name'. The return code is retcode.

Explanation: An error occurred that prevented thecreation of the delta file. Possible reasons for this errorinclude:

v The base file cannot be opened for reading

v The file being backed up cannot be opened forreading

v The delta file cannot be opened for writing

v The file being backed up has grown to a size largerthan 2 GB

v A memory file mapping of the file cannot be created

System action: A full backup of the file is made, and anew version of the reference file is stored in the subfilecache.

User response: If the message indicates return code4504, check the delta subfile cache directory for anyresidual delta files. The delta subfile cache directory isspecified by the client option SUBFILECACHEPATH.Search the directory for files named \".dXXXXXXXX\"where \"XXXXXXXX"\ is an eight-digit number. Ifthere are no backup operations in progress, thereshould not be any files in the SUBFILECACHEPATHwith this name. If there are no backup operations inprogress and these files exist, they can safely beremoved.If you continue to receive this message but there are no

residual delta files in the subfile cache directory andthe file has not grown to a size larger than 2 GB, thencontact IBM technical support for further assistance.

ANS1329S Server out of data storage space

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


User response: Report to your system administratorthat a storage pool on the server is full.

ANS1330S This node currently has a pendingrestartable restore session.The requested operation cannotcomplete until this session eithercompletes or is canceled.

Explanation: This operation can not be completedbecause a restartable restore session is pending. Theoperation is not allowed because the restartable sessionand the current operation affect the same file space.


User response: Issue a query restore to see theconflict. Issue the cancel restore command to delete anyunneeded restartable restore sessions.

ANS1331E Only a TSM authorized user canperform this Action.

Explanation: User must be a TSM authorized user toperform this action. User is not password authorizedand this action requires authorization.


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

ANS1332E Run the '... for Administrators' versionof the application.

Explanation: The user must be root or a systemadministrator and use the provided authorization toolsto start IBM Tivoli Storage Manager

System action: IBM Tivoli Storage Managerterminates.

User response: The user must login as the root user orbe a system administrator and use one of the followingauthorization tools to start IBM Tivoli Storage Manager:

v "TSM Backup for Administrators"

v "TSM Scheduler for Administrators"

v "TSM Scheduler Daemon for Administrators"



ANS1334W Volume mount point 'filespacenamepath-namedir-name' was not restoredbecause the target directory is notempty.

Explanation: Volume mount points can only berestored if the target directory does not already exist, orif the target directory exists but is empty. If the targetdirectory exists and is not empty, or already is ajunction point, then the volume mount point cannot berestored. On Windows Vista, it is normal to see thesewarnings during system drive restore as there aremany junction points that point to the'%systemroot%\Users' folder.

System action: The volume mount point is notrestored. Processing continues with the next object.

User response: Correct the conflict with thenon-empty directory, then try the operation again. Thisis especially important when this message is issued fora volume mount point that resides in the SYSVOL,since an incomplete SYSVOL restore can result insystem stability problems. See the reference informationfor the RESTORE command in the client manual foradditional information about restoring volume mountpoints.

ANS1335E The RSM database files could not berestored.

Explanation: None.

System action: The RSM database is not restored.Otherwise, processing continues.

User response: Check the client error log for any othermessages that might help identify the problem. Rebootthe system, then try the RSM restore operation again. Ifthe problem cannot be resolved, contact IBM technicalsupport for further assistance.

ANS1336I RSM service must be restarted forchanges to become effective.

Explanation: RSM database files have been restoredfrom the server and imported. The RSM service mustbe restarted for the updates to become effective.



ANS1337I Restarting the RSM service...

Explanation: RSM database files have been restoredfrom the server and imported. TSM is about to stopthen restart the RSM service.



ANS1338I Restart of the RSM service is completed.

Explanation: RSM database files have been restoredfrom the server and imported. TSM has restarted theRSM service on the user's behalf.



ANS1339E Restart of the RSM service failed.Restart the RSM service manually.

Explanation: RSM database files have been restoredfrom the TSM server and imported. TSM has tried torestart the RSM service on the user's behalf but has runinto a problem.


User response: Restart the RSM service manually.

ANS1340E An error occurred while backing up theRSM database.

Explanation: An error occurred while backing up theRSM database files. The database will not be backedup.


User response: Check the client error log for any othermessages that might help identify the problem. Try theoperation again. If the problem persists, contact IBMtechnical support for further assistance.

ANS1341E An invalid character appears in theoperand: operand.

Explanation: The operand contains a character that isnot valid in the current locale and code page. It cannotbe translated to its internal wide-character format.


User response: Change the locale of the workstationto match the language in which the operand isrecorded, and try the command again.

ANS1342E Client cache is locked; unable tocontinue with operation.

Explanation: The client cache is currently locked byanother process.


User response: Report the program error to yourservice representative.



ANS1343E The option 'specified-option' can only beentered when 'other-option' has beenentered.

Explanation: The command failed because thespecified option (specified-option) option was entered,but the other option (other-option) was not.

System action: The command is terminated.

User response: Run the command without thespecified option. Alternatively, run the command withthe other option added.

ANS1344E Job is running in the background.Cannot prompt for the Key.

Explanation: When jobs are run in the background,the client cannot prompt for the key.


User response: Run the Job in the foreground.

ANS1345E No objects on the server match'object-nameobject-nameobject-name'

Explanation: The specified file does not have a matchon the server.


User response: Back up the file and try the operationagain. If the problem continues, see your systemadministrator to isolate the problem through use of theserver console.

ANS1346E The image snapshot operation failed.The SNAPSHOTCACHELocation doesnot contain enough space for thissnapshot image backup.

Explanation: TSM was not able to take a snapshot ofthe specified volume. The SNAPSHOTCACHELocationpoints to a location which does not contain the spacenecessary to manage the snapshot. This could be due toan unexpected amount of disk activity which isgenerating more changes than can be contained in theavailable space at this particular point in time, or theSNAPSHOTCACHELocation needs to be changedbecause the specified location is not large enough tohandle the usual amount of changes to the volume.Another reason for this failure can be that the specifiedSNAPSHOTCACHESize is not set to a large enoughvalue to handle the usual amount of changes to thevolume during snapshot image backup.


User response: If the problem persists please increasethe SNAPSHOTCACHESize and/or change the valueof the SNAPSHOTCACHELocation.

ANS1347E The image snapshot operation failed.The percent of space to use, specifiedvia the SNAPSHOTCACHESize, hasbeen exceeded.

Explanation: TSM was not able to take a snapshot ofthe specified volume. The percent of space allotted viathe SNAPSHOTCACHESize option was not enough toperform this snapshot image backup. This could be dueto an unexpected amount of disk activity which isgenerating more changes than can be contained in theallotted space at this particular point in time. Anotherreason for this failure can be that the specifiedSNAPSHOTCACHESize is not set to a large enoughvalue to handle the usual amount of changes to thevolume during snapshot image backup.


User response: If the problem persists please increasethe SNAPSHOTCACHESize or, for Windows, changethe value of the SNAPSHOTCACHELocation.

ANS1348E Unable to satisfy theSNAPSHOTFSIDLEWait andSNAPSHOTFSIDLERetries options dueto volume write activity.

Explanation: TSM was not able to take a snapshot ofthe specified volume. The Logical Volume SnapshotAgent was not able to satisfy theSNAPSHOTFSIDLEWait and SNAPSHOTFSIDLERetriesoptions before starting the snapshot of the specifiedvolume.


User response: If the problem persists please modifythe SNAPSHOTFSIDLEWait andSNAPSHOTFSIDLERetries options to better fit thenormal disk write activity of the volume being backedup.

ANS1349E An error occurred during LogicalVolume Snapshot Agent snapshotprocessing.

Explanation: An unrecoverable error occurred duringsnapshot processing. This can be caused by a variety oferrors, so the error and system event logs should bechecked for additional messages.


User response: Check the client error log and thesystem event log for any other messages that mighthelp identify the problem. Try the operation again. Ifthe problem persists, contact IBM technical support forfurther assistance.



ANS1350E The logical volume snapshot agent(LVSA) is currently busy performing asnapshot on this same volume.

Explanation: Another IBM Tivoli Storage Managerprocess is already performing a snapshot of thisvolume.

System action: The operation is stopped.

User response: Please wait until the other IBM TivoliStorage Manager process finishes with the volume andthen retry the operation.

ANS1351E Session rejected: All server sessions arecurrently in use

Explanation: TSM has all available sessions in use andcannot accept a new one at this time.


User response: Retry the operation. If the problemcontinues, see your system administrator to increase thenumber of concurrently active sessions to the server.

ANS1352E The session is rejected. Your passwordhas expired.

Explanation: The password for TSM user ID hasexpired. It can be either TSM node name password oradministrative user ID password or both.

System action: TSM canceled the current operation.You are not allowed to connect to the server until thepassword is updated.

User response: Update your password. It may requireupdating the node name password or the corespondentadministrative ID password or both. You may use theSET PASSWORD command, or have the TSMadministrator update your node and/or youradministrative ID.

ANS1353E Session rejected: Unknown or incorrectuser ID entered

Explanation: The user ID, which is either TSM nodename or administrative user ID, is not known by theserver. Possible reasons for this include:

Your node name is not registered with the TSMserver

The node name is correct but does not have acorresponding administrative ID with the samename and client owner authority

you are attempting to access a file that wasmigrated to a different node.

System action: TSM cancelled the current operation.

User response: Verify that the server is using closedregistration and that your node name is registered withthe server. Ensure that you entered your TSM user IDcorrectly. Check that your TSM node name has a

matching admin ID with client owner authority for thenode. If it does not, your TSM administrator needs tocreate it. If attempting to access a migrated file, yournode name must be the same node which migrated thefile.

ANS1354E Session rejected: Duplicate ID entered

Explanation: Another process using this node name isactive with the server.

System action: TSM cannot connect to the server. TSMcanceled the current operation.

User response: If you are running a UNIX-basedsystem, ensure that another process is not active withTSM under the same name. Also, ensure that yournode name is unique to the server so that it cannot beused by another person. See your system administratorto identify the owner of that node name.

ANS1355E Session rejected: Server disabled.

Explanation: The server is in a disabled state andcannot be accessed for normal activity.


User response: On the TSM server, run the ENABLESESSIONS administrative command. Try the operationagain after the server returns to an enabled state. If theproblem continues, see your system administrator.

ANS1356E The server is not configured to allowopen registration

Explanation: No authorization. Registration isrequired by your system administrator. The server isnot configured to allow open registration.

System action: Session not started.

User response: You must obtain a TSM node andpassword from your system administrator.

ANS1357S Session rejected: Downlevel client codeversion

Explanation: The server version and your clientversion do not match. The client code is downlevel.


User response: See your system administrator to seewhat version of TSM to run for your location.

ANS1358S Session rejected: Downlevel server codeversion

Explanation: The server version and your clientversion do not match. The server code is downlevel.


User response: See your system administrator to see



what version of TSM to run for your location.

ANS1359E Session Rejected: The specified nodename is currently in use

Explanation: The node name you specified is in useon the server.


User response: The server is probably performing atask that prevents your node from establishing asession. Retry later or check with your systemadministrator.

ANS1360I Compressed Data Grew

Explanation: The size of the file after compression isgreater than the size of the file before compressed.

System action: Even though the size of the fileincreased, the file is compressed.


ANS1361E Session Rejected: The specified nodename is currently locked.

Explanation: The node name you specified is currentlylocked on the server.


User response: Check with your system administratorto find out why your node name is locked.

ANS1362S SLM LICENSE EXCEEDED: The clientlicenses for TSM are exceeded.See your system administrator.

Explanation: Adding a new enrollment will exceed theproduct license count for TSM.

System action: Execution of the client enrollment orconnection request ends.


ANS1363E Session Rejected: The server does nothave enough memory toallow a connection to be established.

Explanation: The server does not have enoughmemory to allow your client to establish a connectionwith the server.


User response: Retry later or see your systemadministrator.

ANS1364E Session Rejected: The server does nothave enough recovery logspace to allow a connection to beestablished.




ANS1365E Session Rejected: The server does nothave enough databasespace to allow a connection to beestablished.




ANS1366E The session is rejected. The TSM serverhas an internal error.

Explanation: The client cannot establish a connectionto the TSM server because of an internal server error.

System action: The session was not started.

User response: Notify your TSM administrator of thiserror.

ANS1367E The client is unable to sign on to theTSM server because the server does notallow sign-on of Unicode clients.

Explanation: The client is not allowed to connect tothe TSM server.

System action: The session does not start.

User response: Contact your TSM administrator forassistance in configuring a working TSM client for yourenvironment.

ANS1368S Session Rejected: The server is notlicensed for this platform type.See your system administrator.

Explanation: The server is not licensed for therequesting client type.



ANS1369E Session Rejected: The session wascanceled by the server administrator.

Explanation: The server administrator canceled thecurrent client session.



System action: Execution of the client connectionrequest ends.


ANS1370E The user ID entered does not have thecorrect level of authority to access theclient machine.

Explanation: The user ID entered cannot access thisTSM client.

System action: The TSM operation ends.

User response: Grant authority to this user ID on theTSM server so that it can access this TSM client.

ANS1371E File '' cannot be reconstructed fromsubfile components.

Explanation: An error occurred while reconstructingthis file from its subfile components.

System action: The file indicated in the message is notrestored. Restore for all other files continues.

User response: Try to restore the file again byselecting the file for restore from the user interface. Youcan also check the client error log and the serveractivity log for any messages related to the fileindicated in the message.

ANS1372E An inconsistency was detected betweenthe client node andthe node that is registered to the TSMserver.

Explanation: The user has probably coded the nodeoption incorrectly. For instance, the node that isregistered to the TSM server might be a type of NAS,but the node is actually a non-NAS client.


User response: Ensure that the node name is correctin the client options file. Make sure to use a node oftype NAS only with the nasnodename option.

ANS1373W The PRESNAPSHOTCMD command forvolume filespace completed with anon-zero return code.

Explanation: The command specified by thePRESNAPSHOTCMD option must completesuccessfully in order to perform the snapshotbackup/archive operation. If the command completedwith a return code of 0 (zero), it has completedsuccessfully. If the command completed with any otherreturn code, it has failed. If the command failed, thenthe backup is still performed, but without the benefit ofthe snapshot technology.

System action: The client executes the backup/archiveoperation, but without using a snapshot.

User response: Identify and fix the problem thatcaused the command to fail. If a non-zero return codeis normal for this command, then consider wrappingthe command in a script that always exits with a returncode of zero.

ANS1374W The POSTSNAPSHOTCMD commandfor volume filespace completed with anon-zero return code.

Explanation: The command specified by thePOSTSNAPSHOTCMD option completed with anon-zero return code. The snapshot-based backupoperation yields a return code of at least 8.

System action: The snapshot-based backup operationcontinues.

User response: Identify and resolve the problem thatcaused the post-snapshot command to fail. If anon-zero return code is normal for this command, thenconsider wrapping the post-snapshot command in ascript that always exits with a return code of zero.

ANS1375W File FilesystemPathFileName skipped byuser

Explanation: You requested that this file be skippedduring the current operation.

System action: The file is skipped during the currentoperation


ANS1376E Error processing 'filespacenamepath-namefile-name'; end-to-enddigest validation failed.

Explanation: Cryptographic digest of the restored orretrieved data did not match the digest generatedduring the backup or archive operation. Possible causesare a transmission error, data corruption, or a hashcollision.


User response: Try the restore operation again. If theproblem persists, contact IBM technical support foradditional assistance.

ANS1377W The client was unable to obtain asnapshot of 'volname'. The operation willcontinue without snapshot support.

Explanation: TSM client was unable to create asnapshot of the volume due to some reason. Instead offailing the operation, TSM client will perform anon-snapshot based backup.

System action: Snapshot processing stops.

User response: Check the client error log for any othermessages that might help identify the problem. Try the



operation again. If the problem persists, contact IBMtechnical support for further assistance.

ANS1378E The snapshot operation failed. TheSNAPSHOTCACHELocation does notcontain enough space for this snapshotoperation.

Explanation: IBM Tivoli Storage Manager was not ableto take a snapshot of the specified volume. TheSNAPSHOTCACHELocation points to a location whichdoes not contain the space necessary to manage thesnapshot. Reasons for failure include:

v An unexpected amount of disk activity which isgenerating more changes than can be contained inthe available space at this particular point in time.

v The SNAPSHOTCACHELocation is not large enoughto handle the usual amount of changes to thevolume.

v The specified SNAPSHOTCACHESize is not set to alarge enough value to handle the usual amount ofchanges to the volume during snapshot backup orarchive operation.


User response: If the problem persists, increase theSNAPSHOTCACHESize or change the value of theSNAPSHOTCACHELocation.

ANS1379E The snapshot operation failed. Thepercent of space to use for theSNAPSHOTCACHELocation, specifiedvia the SNAPSHOTCACHESize, hasbeen exceeded.

Explanation: IBM Tivoli Storage Manager was not ableto take a snapshot of the specified volume. The percentof space allotted via the SNAPSHOTCACHESize optionwas not enough to perform this snapshotbackup/archive operation. Reasons for failure include:

v The SNAPSHOTCACHELocation is not large enoughto handle the usual amount of changes to thevolume.

v The specified SNAPSHOTCACHESize is not set to alarge enough value to handle the usual amount ofchanges to the volume during snapshot backup orarchive operation.


User response: If the problem persists, increase theSNAPSHOTCACHESize or change the value of theSNAPSHOTCACHELocation.

ANS1380W The snapshot operation failed. Thefilesystem write activity prevented theLogical Volume Snapshot Agent fromsatisfying the SNAPSHOTFSIDLEWaitand SNAPSHOTFSIDLERetries options.

Explanation: IBM Tivoli Storage Manager was not ableto take a snapshot of the specified volume. The LogicalVolume Snapshot Agent was not able to satisfy theSNAPSHOTFSIDLEWait and SNAPSHOTFSIDLERetriesoptions before starting the snapshot of the specifiedvolume.


User response: If the problem persists, modify theSNAPSHOTFSIDLEWait and SNAPSHOTFSIDLERetriesoptions to better fit the normal disk write activity ofthe volume being backed up.

ANS1381W On volumes that are RAW or formattedFAT32 the snapshot cache locationcannot be located on the same volumethat is being backed up.

Explanation: When the snapshot cache location islocated on the same volume that is being backed up thevolume must be formatted with NTFS. The defaultcache location is on the same volume where thesnapshot is being performed. The operation willcontinue without snapshot support.

System action: The client does not execute thesnapshot operation.

User response: Specify a different snapshot cachelocation, using the SNAPSHOTCACHELOCATIONoption.

ANS1382E Server does not allow client-initiatedconnections for this node.

Explanation: The node is not allowed to initiateconnections due to the configuration parameters forthis node on the server. Server is able to initiateconnections to the client scheduler running inprompted mode.

System action: The IBM Tivoli Storage Manageroperation ends.

User response: Contact your systems administrator toenable client-initiated sessions for your node or updatethe SESSIONINITIATION option and run the clientscheduler.

ANS1383E Wrong server port.

Explanation: You were trying to open abackup/archive client session on the server port set upfor administrative sessions only.


User response: Contact your systems administratorand/or use the correct values for TCP port and TCPAdmin Port.



ANS1384E An object in the transaction has beenbound to an invalid management class.

Explanation: One of the objects in the transaction isbound to a management class that is not part of thisnode's policy, or the management class type is notsupported for this client level.

System action: The current operation ends.

User response: Make sure all objects are bound to avalid management class, or upgrade the client to theproper level.

ANS1385E This server does not support backupoperations.

Explanation: This server only supports archiveoperations, backup is not allowed.


User response: Use only archive operations with thisserver.

ANS1386E Deleting this object: "fshlll" is notallowed.

Explanation: The object is either under a hold andcannot be deleted, or it is on a retention-protectionenabled server and has not expired.

System action: The object is skipped and processingcontinues.

User response: Check the status of the object througha query to see if it is held, or when it expires.

ANS1387E The number of objects in thistransaction exceed TXNGROUPMAXvalues.

Explanation: There are too many objects in thistransaction.


User response: Try the operation again with fewerobjects in the transaction, or increase theTXNGROUPMAX value on the server.

ANS1388E fshlll is already under hold.

Explanation: The specified object is already underhold, and it cannot be placed under a new hold.

System action: This object is skipped and processingcontinues.

User response: Issue a query to see the status of theobjects, and try the operation again, without the objectthat is already held.

ANS1389W Invalid option (option) for the scheduledfunction command

Explanation: There are two possible reasons for thismessage:

v The option option was specified for a scheduledcommand or subcommand (function) that cannotmake use of that option.

v The option appears on a scheduled command but isvalid only on the client scheduler initial commandline, not on commands in a schedule from the server.

System action: The option is ignored.

User response: See the Backup-Archive ClientInstallation and User's Guide for correct use of thenamed option. The system administrator shouldremove the invalid option from the schedule definitionon the server.

ANS1395E The destination filespace or drive letteris unavailable. The following object wasnot processed:Filespace:'filespace-name'

Explanation: The system is trying to restore or retrieveto a destination that cannot be reached. The specifiedfilespace name or drive letter is not valid, or does notexist, or you are specifying a local share name thatcannot be resolved.

System action: Objects which are part of this filespaceare not processed.

User response: Try the command again, and specify adifferent destination for the object that was notprocessed.

ANS1396E Access to the specified log or trace file(filename) is denied.

Explanation: Access to the specified file is denied. Youspecified a log or trace file name that cannot be writtenby the current user.



ANS1397W The snapshot cannot be taken becausethe SNAPSHOTCACHELocation doesnot have enough space for this snapshotoperation.

Explanation: IBM Tivoli Storage Manager was not ableto take a snapshot of the specified volume. TheSNAPSHOTCACHELocation points to a location whichdoes not contain the space necessary to create thesnapshot; the disk is probably full. The operationcontinues without snapshot support.




User response: Change the value of theSNAPSHOTCACHELocation, or clean the disk to whichthe SNAPSHOTCACHELocation points.

ANS1398E Initialization functions cannot open oneof the Tivoli Storage Manager logs or arelated file: log-name. errno = errno-value,reason

Explanation: The file "log-name" could not be openedduring initialization. The system set the error codeerrno-value. If the reason given is "access denied," thecurrent user does not have permission to write to thelog in the directory specified. It is also possible that nospace is available at the given log location.

On Unix systems, the log must not be in the rootdirectory. Attempts to do so will result in an "accessdenied" error.

System action: Processing terminates.

User response: Set the DSM_LOG (or DSMI_LOG)environment variable to a directory into which thecurrent user can write. You may also use theERRORLOGNAME option to specify a file to which thecurrent user has write permission.

ANS1399W The logical volume snapshot agent(LVSA) is currently busy performing asnapshot on this same volume.

Explanation: IBM Tivoli Storage Manager was not ableto take a snapshot of the specified volume becauseanother process is already performing a snapshot ofthis volume. The operation continues without snapshotsupport.


User response: Wait until the other IBM Tivoli StorageManager process finishes with the volume and then trythe operation again.

ANS1400W The snapshot cache location is not valid.

Explanation: The snapshot cache location must pointto a local volume that is formatted with NTFS. Thedefault cache location is on the same volume where thesnapshot is being performed. The operation willcontinue without snapshot support.



ANS1401W The snapshot virtual volume is notaccessible.

Explanation: The logical volume snapshot agent(LVSA) cannot access the virtual volume duringOFS-enabled backup/archive operation because IBMTivoli Storage Manager was probably started viaterminal services. The operation continues withoutsnapshot support.


User response: Do not use terminal services for thesnapshot. Try the operation again on the local machine.

ANS1402W The snapshot is not supported on aremote, removable, or SAN drive.

Explanation: IBM Tivoli Storage Manager was not ableto take a snapshot of the specified volume becauseopen file support is only supported on local fixedvolumes, including volume mountpoints. The operationcontinues without snapshot support.


User response: To take advantage of the open filesupport, you may try the operation again on the localmachine.

ANS1403E Error loading a required filename DLL

Explanation: An error occurred while loading adynamic link library. The DLL load failed.


User response: Verify that your system software is upto date and that all DLLs required by the TSM clientare present.

ANS1404E Error loading one or more functionsfrom a required filename DLL

Explanation: An error occurred while loading afunction from a dynamic link library. The DLL loadfailed.


User response: Verify that your system software is upto date.

ANS1405I 'service-name' service needs to berestarted.

Explanation: The service must be restarted for therestored changes to take effect.

System action: Changes are not effected.

User response: Restart the service.

ANS1398E • ANS1405I


ANS1406I Performing operation usingpoint-in-time copy of the filesystem:'volname'.

Explanation: IBM Tivoli Storage Manager is taking asnapshot of the specified volume during the backup orarchive operation. This allows the IBM Tivoli StorageManager to access locked or in-use files.

System action: Operation proceeds.


ANS1407I Performing operation usingpoint-in-time copy of the filesystem.

Explanation: IBM Tivoli Storage Manager is taking asnapshot of the specified volume during the backup orarchive operation. This allows the IBM Tivoli StorageManager to access locked or in-use files.

System action: Operation proceeds.


ANS1408W Previous changes have not beencommited.The machine must be restarted beforethe snapshot can be taken

Explanation: IBM Tivoli Storage Manager was not ableto take a snapshot of the specified volume because aprevious operation required the machine to be restartedfor the changes to take effect, but the machine has notbeen restarted. The operation will continue withoutsnapshot support.


User response: Restart the machine and then try theoperation again.

ANS1410E Unable to access the network path.

Explanation: The network path cannot be accesseddue to a possible network problem.

System action: The client terminates.

User response: Ensure that the network is up and thepath can be accessed using a system command, andretry the operation.

ANS1411E A communication session was dropped.

Explanation: A communication session was droppeddue to a possible network problem.


User response: Ensure that the network is up andretry the operation.

ANS1412E Directory or file has bad EA data orinconsistent data.

Explanation: Directory or file has bad EA data orinconsistent data.


User response: Check failing directory or file for badEA data. Copy the directory to a new location and retrythe operation.

ANS1413W File 'filespace namepath-namefile-name' isnot recognized by the system as a diskfile and cannot be processed. The file isskipped.

Explanation: The client is unable to process file typesthat are not 'disk', such as 'character' and 'pipe'. Thismessage is typically, but not always, issued for filenames that are normally reserved for the operatingsystem. In the Windows environment, reserved namesinclude AUX, CON, NUL, PRN, COMx or LPTx, where'x' is any digit from 1 to 9 (for example, COM1, LPT3,etc.).


User response: Either delete the file if you do notneed it, or else use an EXCLUDE statement in the clientoptions to prevent the client from trying to process thefile. In the Windows environment, normal deletecommands will most likely not work. You will need toprefix the file name with the characters '\\.\'. Forexample, "del c:\mydir\lpt4" will not work, but "del\\.\c:\mydir\lpt4" will work.

ANS1414W Don't have sufficient authority to deleteopen group on server.

Explanation: An open image group exists on the TSMserver and cannot be deleted due to missing backupdelete rights for this node.


User response: Ask your TSM administrator to grantbackup delete rights for your node.

ANS1417W Protected system state file 'filename' isbacked upto the drive file space, not system statefile space.

Explanation: Files protected by Microsoft WindowsFile Protection (WFP) or Microsoft Windows ResourceProtection (WRP) are part of the Microsoft VolumeShadowCopy Services (VSS) System Writer which ispart of the system state. These files are normallybacked up as part of the system state, not the filesystem on which the files reside.A problem in the operating system environmentprevented the protected file named in the message textfrom being enumerated as a system state file and thus



backed up as part of the system state.The conditions that lead to this message are notnormal. In order to ensure that the file is protected, it isbacked up as part of the file system on which it resides.

System action: The file is backed up as part of the filesystem on which it resides.

User response: It is possible to restore the systemusing the file system and system state backups.However the conditions that prevent the system statefiles from being correctly enumerated should beaddressed.On Microsoft Windows 2008 and Microsoft Windows2008 R2 you can use the DiskShadow utilitysub-command LIST WRITERS DETAILED to enumeratethe system state files. On other versions of MicrosoftWindows you can use the vshadow utility with the-wm2 option to enumerate the system state files. Verifythat the file indicated in this message is not listed.Note: vshadow is a utility that you can obtain fromMicrosoft.After confirming that the files are not enumerated,contact your operating system technical support forhelp to diagnose and resolve the issue that prevents thefile from being correctly enumerated as part of thesystem state.

ANS1420E Volume map document (tsmvolmap.txt)not found.

Explanation: An error occurred while performing VSSAutomated System Recovery (ASR). Checkdsmerror.log for more information.


User response: Ask your system administrator tocheck the error log.

ANS1421E The image object 'object-type' was notfound on server.

Explanation: The specified image object of typeobject-type could not be located on the server. Theoperation cannot complete without this object.


User response: Examine the client error log foradditional messages that might indicate the reason forthe problem. Take any corrective action suggested bythe messages, then try the operation again. If theproblem persists, contact IBM technical support forfurther assistance.

ANS1423W 'filesystem' is a virtual mount point.Migration is not supported on virtualmount points.

Explanation: Tivoli Storage Manager HSM does notsupport virtual mount points within managed filesystems. Files in the virtual mount point folder can notbe migrated.

System action: Tivoli Storage Manager attempts tocontinue the current operation.

User response: Do not use virtual mount pointswithin file systems that are managed by HSM. Useinclude/exclude rules instead.

ANS1424W Retrying failed image operation forvolume filespace-name.

Explanation: The transaction for image operation forvolume filespace-name failed due to reason described byearlier message(s).

System action: The requested image operation will beretried again.


ANS1425E The image operation for volumefilespace-name cannot be retried becauseof a severe error.

Explanation: None.

System action: The image operation fails for theindicated volume.


ANS1426E An error occurred creating the Registrybackup directory structure

Explanation: The TSM client uses an intermediatedirectory structure on the client machine as part of theWindows Registry backup process. The client wasunable to create this intermediate directory structure, sothe Windows Registry could not be backed up.This problem can occur if you do not have sufficientprivileges to perform the backup operations, if theclient is unable to allocate more memory from thesystem, or if a component within the directorystructure already exists as a file.

System action: The Windows Registry is not backedup.

User response: Check the client error log for any othermessages that might have been logged when thismessage was written, and take the corrective action (ifany) suggested by those messages. Make sure thataccount under which the operation runs has sufficientprivileges. Ensure that the system has sufficientmemory to run TSM. Remove the ADSM.SYS directoryfrom the root of your system drive, then try theoperation again. If the problem persists, contact IBMsupport for further assistance.



ANS1427I Registry Backup function completedsuccessfully.

Explanation: Registry backup was successful.



ANS1428E Backup of the registry failed.

Explanation: None.

System action: The registry is not backed up.


ANS1429I Registry Restore function completedsuccessfully.

Explanation: Registry Restore was successful.



ANS1430W The machine must be rebooted for thechanges to take effect.

Explanation: The TSM restore operation made changesthat will not be in effect until the machine is rebooted.It is important to note that until the reboot occurs, thesystem or its applications might be unstable.

System action: None

User response: Reboot the machine as soon aspossible after the TSM restore operation ends.

ANS1431E Restore of the registry failed.

Explanation: None.

System action: The registry is not restored.


ANS1432E Keyword Expected after keyword'keyword'.

Explanation: A registry command was incorrectlyentered.

System action: Registry function is not invoked.

User response: Refer to the command reference forthis command.

ANS1433E Extraneous argument 'input' afterkeyword 'keyword'


System action: Registry function not invoked.


ANS1434E Invalid argument 'input' after keyword'keyword'


System action: Registry function not invoked.


ANS1435E An error occurred saving a registry key.

Explanation: None.

System action: The registry is not backed up.


ANS1436E An error occurred replacing a registrykey.

Explanation: None.

System action: The registry key is restored from theserver, but cannot be activated in the registry. Thecurrent registry key remains active.


ANS1437I Event Log Backup function completedsuccessfully.

Explanation: Event Log backup was successful.



ANS1438E Backup of the event logs failed.

Explanation: None.

System action: The event logs are not backed up.




ANS1439I Event Log Restore function completedsuccessfully.

Explanation: Event Log Restore was successful.



ANS1440E Restore of the event logs failed.

Explanation: None.

System action: The event logs are not restored.


ANS1441E Keyword Expected after keyword'keyword'.

Explanation: A event log command was incorrectlyentered.

System action: Event Log function is not invoked.


ANS1442E Extraneous argument 'input' afterkeyword 'keyword'


System action: Event Log function not invoked.


ANS1443E Invalid argument 'input' after keyword'keyword'


System action: Event Log function not invoked.


ANS1444E An error occurred creating the Event Logbackup directory structure

Explanation: The TSM client uses an intermediatedirectory structure on the client machine as part of theWindows Event Log backup process. The client wasunable to create this intermediate directory structure, sothe Windows Event Logs could not be backed up.This problem can occur if you do not have sufficientprivileges to perform the backup operations, if theclient is unable to allocate more memory from thesystem, or if a component within the directory

structure already exists as a file.

System action: The Windows Event Logs are notbacked up.

User response: Check the client error log for any othermessages that might have been logged when thismessage was written, and take the corrective action (ifany) suggested by those messages. Make sure thataccount under which the operation runs has sufficientprivileges. Ensure that the system has sufficientmemory to run TSM. Remove the ADSM.SYS directoryfrom the root of your system drive, then try theoperation again. If the problem persists, contact IBMsupport for further assistance.

ANS1445E ERROR: could not create NAS imageobject.

Explanation: Creation of the NAS image object failedfor one of following reasons:

v An unauthorized user invoked the NAS command

v NAS operations are not supported on the currentplatform

v Cannot find the NAS plugin library.

System action: The requested NAS operation is notperformed.

User response: Retry the operation after correcting thecause for failure.

ANS1446E VSS ASR backup document(ASRBackupDoc.xml) not found.

Explanation: An error occurred while performing VSSAutomated System Recovery (ASR). Checkdsmerror.log for more information. Possible causes forthe error are the following:

v You are trying to recover a machine running a legacyoperating system such as windows XP or windows2003. VSS ASR Restore is not supported for legacyoperating systems.

v You are trying to run ASR recovery from a backupcreated by a client earlier than version 6.2.2. Suchbackups do not have ASRBackupDoc.xml file.



ANS1448E The command command is not supportedby the current server.

Explanation: The server to which the client isconnected does not support the command.

1. If the command is "set event," the server does notsupport event-based policy. This command requiresthat the server supports event-based policy. Thatsupport is available only at TSM Server levels 5.2.2and above.



2. If the message displays any other command, theserver is configured to support archive retentionprotection and cannot process operations that arenot associated with that facility.

System action: The command is skipped and otherprocessing continues.

User response: Log in to an appropriate server andrun the command again.

ANS1449W A non-critical, unexpected error wasencountered.Deletion of a snapshot(Set/Volume)failed. Probable cause, snapshot doesnot exists anymore. ContinuingProcess...TSM snapShot ID : snapshot-idTSM function name : function-nameTSM function : function-descTSM return code : TSM-rcTSM file : file-name (line-number)

Explanation: None.


User response: Contact the TSM administrator withthe information provided in this message.

ANS1450W The -FILENAME option was specifiedwithout a file name. Output will bewritten to filename.

Explanation: The -FILENAME option was specified,but the file name was omitted.

System action: The output is written to the defaultfile.

User response: Reissue the command and specify avalid file name, or use the information that was writtento the default file.

ANS1453W The IMAGEGAPSIZE option is notsupported for non-NTFS file systems.The entire volume will be backed up.

Explanation: None.

System action: The entire volume is backed up.

User response: Refer to the client manual foradditional information regarding the IMAGEGAPSIZEoption.

ANS1454W Used blocks information could not beobtained for name. The entire volumewill be backed up.

Explanation: None.


User response: Check the client error log for any other

messages that might help identify the problem. Try theoperation again. If the problem persists, contact IBMtechnical support for further assistance.

ANS1458I OBF file for volume name is too smallfor server-free data transfer.

Explanation: The OBF file for volume is very small toinitiate a server-free data transfer. Hence this file willnot be transferred via a server-free data path.



ANS1459E VSS Automated System Recovery (ASR)failed.

Explanation: An error occurred while performing VSSAutomated System Recovery (ASR). Checkdsmerror.log for more information.



ANS1461E Error processing 'filespacenamepath-namefile-name': unsupportedencryption type.

Explanation: The files you are trying to restore orretrieve have been backed up or archived by a laterversion of the TSM client. The file encryption method isnot supported by the current client.


User response: Restore or retrieve the file with themost recent version of the TSM client.

ANS1462E Unsupported encryption type




ANS1463E Unexpected error in cryptographylibrary.

Explanation: There was an unexpected error in thecryptography library. See the error log for moreinformation.


User response: Check the error log for ANS1467E todetermine the cause of failure. Verify you TSM client isinstalled properly. If needed, reinstall client and/or



API. If the problem still exists, contact TSM technicalsupport.

ANS1464S Cannot load ICC encryption library.

Explanation: TSM is using cryptography library whichis installed automatically with the client and is beingloaded at runtime. The client cannot proceed if thelibrary is not loaded.

System action: Client exits.

User response: Check the error log for ANS1467E todetermine the cause of failure. Verify you TSM client isinstalled properly. If needed, reinstall client and/orAPI. If the problem still exists, contact TSM technicalsupport.

ANS1465E Conflicting options ERRORLOGMAXand ERRORLOGRETENTION werespecified.

Explanation: Values were specified for both theERRORLOGMAX and the ERRORLOGRETENTIONoptions. These options are mutually exclusive.


User response: Specify a nonzero value forERRORLOGMAX if you wish to have the TSM errorlog wrap when it reaches the specified maximumvalue. Use ERRORLOGRETENTION if you wish youhave the error log limited in size on a time-basedschedule.

ANS1466E Conflicting options SCHEDLOGMAXand SCHEDLOGRETENTION werespecified.

Explanation: Values were specified for both theSCHEDLOGMAX and the SCHEDLOGRETENTIONoptions. These options are mutually exclusive.


User response: Specify a nonzero value forSCHEDLOGMAX if you wish to have the TSMscheduler log wrap when it reaches the specifiedmaximum value. Use SCHEDLOGRETENTION if youwish you have the scheduler log limited in size on atime-based schedule.

ANS1467E ICC routine icc-routine returned: majRC= majRC, minRC = minRC, desc = 'desc'.

Explanation: There was an error within an ICCcryptography library. This message reports return codesand problem description which can be used by TSMtechnical support personnel to determine the cause ofthe error.

System action: Client exits.

User response: Verify you TSM client is installed

properly. If needed, reinstall client and/or API. If theproblem still exists, contact TSM technical support.

ANS1468E Backing up Automated System Recovery(ASR) files failed. No files will bebacked up.

Explanation: An error occurred while backing up thefiles needed for Automated System Recovery (ASR). Nofiles were backed up.


User response: Ask your system administrator tocheck the error log. Verify that the Windows accountfrom which you are running this command hasadministrator authority and try the command again.

ANS1469E Error processing 'filespacenamepath-namefile-name'; invalidencryption key.

Explanation: The key you entered does not match thekey that was used to encrypt the file during backup.The file can not be restored unless the matching key isentered.


User response: Try the restore operation again andprovide the correct key.

ANS1470E Unable to load GPFS functions neededfor ACL and extended attributessupport: skip path_name

Explanation: The GPFS functions that handle theGPFS ACL and extended attributes were not loaded.

System action: The object is skipped. Processingcontinues with the next object.

User response: Ensure that the GPFS software isinstalled on the system and try the operation again. OnLinux, iensure that there has been an appropriatesymbolic link created in /usr/lib/ directory for theGPFS libgpfs.so shared library.

ANS1471E ASR system information file creationfailed. ASR backup is unsuccessful.

Explanation: An error occurred while creating thesystem information file (asr.sif) needed for AutomatedSystem Recovery (ASR). The ASR backup isunsuccessful.


User response: Ask your system administrator tocheck the error log. Verify that the Windows accountfrom which you are running this command hasadministrator authority and that you have access to thesystem object staging directory <system drive>:\adsm.sys. Try the command again.



ANS1472E Could not add entry to the ASR systeminformation file. ASR backup isunsuccessful.

Explanation: An error occurred while adding an entryto the system information file (asr.sif) needed forAutomated System Recovery (ASR). The ASR backup isunsuccessful.


User response: Ask your system administrator tocheck the error log. Verify that the Windows accountfrom which you are running this command hasadministrator authority and try the command again.

ANS1473E Session rejected: TCP/IP connectionfailure for Shared Memory

Explanation: An attempt to connect to the local serverusing the Shared Memory protocol has failed duringinitial TCP/IP communications. This error can occur ifthe server is not listening on the correct port, or if theserver is down.


User response: Retry the operation, or wait until theserver comes back up and retry the operation. If theproblem continues, see your system administrator forfurther help.

ANS1474E An error occurred using the SharedMemory protocol

Explanation: An error has occurred while reading orwriting data through the Shared Memorycommunications protocol.


User response: Check the trace log for additionalinformation and retry the operation. If the problemcontinues, see your system administrator for furtherhelp.

ANS1475E Insufficient authority to connect to theshared memory region

Explanation: The user issuing the command does nothave authority to connect to the shared memorysegment. When the shared memory segment is createdby the server, it will be owned by the effective uid ofthe server process (dsmserv). Only processes runningunder this uid or root will be allowed to connect to thesegment (and thus to the server).

System action: The session is rejected and processingstops.

User response: Run the command under the uid ofthe processing running dsmserv, if possible. Otherwisecontact your system administrator for further help.

ANS1476E CLUSTERNODE is set to YES but theCluster Information Daemon is notstarted.

Explanation: The HACMP Cluster InformationDaemon must be started in order to specify theCLUSTERNODE option.

System action: Processing ends.

User response: Start the HACMP Cluster InformationDameon.

ANS1477E CLUSTERNODE is set to YES but thecluster load library is not valid.

Explanation: The load library that the operatingsystem provides to obtain the cluster name is not valid.A possible cause is an out-of-date load library whichdoes not contain the proper routines this productexpects.


User response: Ensure that the latest cluster softwareis installed on the system.

ANS1478E CLUSTERNODE is set to YES but thecluster software is not availableon this system.

Explanation: The load library that the operatingsystems provides to obtain the cluster name is notavailable on this system.


User response: Ensure that the cluster software isinstalled on the system.

ANS1479E CLUSTERNODE is set to YES but thismachine is not a member of acluster.

Explanation: This machine is not a member of acluster node. Possible causes are that the cluster servicehas not been configured correctly, or that the cluster isin the process of initialization.


User response: Ensure that the cluster software isconfigured properly. If the cluster is in the process ofinitialization, retry the operation at a later time.

ANS1480E CLUSTERNODE is set to YES but thecluster service is not enabledon this system.

Explanation: The cluster service has not been enabledon this system.




User response: Enable the cluster service on thesystem.

ANS1481E The CLUSTERNODE option is notsupported on this system.

Explanation: This option is not supported on thissystem.


User response: Disable the CLUSTERNODE option inthe local options file.

ANS1482E An unexpected error (retcode) occurredwhile the program was trying to obtainthe cluster name from the system.

Explanation: An unknown error occurred while theprogram was trying to obtain the cluster name from thecluster service. The error code is the reason codeprovided directly from the cluster service being used inthis operating system environment.


User response: Consult the documentation for yourclustering software for an explanation of the reasoncode. Insure that your clustering service is operational,then try the TSM operation again.

ANS1483I Schedule log pruning started.

Explanation: The schedule log pruning function hasbegun.

System action: The schedule log is pruned.


ANS1484I Schedule log pruning finishedsuccessfully.

Explanation: The schedule log pruning functioncompleted with no errors.



ANS1487E An error occurred while backing up theWMI repository. The database will notbe backed up.

Explanation: The Windows event log and TSM errorlog might contain additional information related to thiserror.


User response: Examine the Windows event log andTSM error log for messages related to WMI. Ensurethat the Windows Management Instrumentation serviceis started.

ANS1489E The WMI service failed to stop. No fileswill be restored.

Explanation: An error occurred while stopping theWindows Management Instrumentation (WMI) service.The database will not be restored.


User response: Examine the Windows event log andTSM error log for messages related to WindowsManagement Instrumentation (WMI). You might needto quiesce WMI activity or reboot the machine in orderto free resources which are preventing the WMI servicefrom stopping.

ANS1490W File specification 'file-spec' ignored. Afile list has already been specified.

Explanation: A non-option argument (filespecification) was encountered after the -FILELIST hasbeen processed.

System action: The argument is ignored.

User response: You may have either a -FILELIST orexplicit file specifications on this command, but notboth.

ANS1492S Invalid virtual mountpoint filespace-name:File not found.

Explanation: The specified VIRTUALMOUNTPOINTin the system options file is invalid because it could notbe found in the file system.

System action: TSM attempts to continue the currentoperation.

User response: Check the virtual mountpoint in thesystem options file and make sure it exists in the filesystem. Retry the operation.

ANS1493S Invalid virtual mountpoint filespace-name:Access denied.

Explanation: The specified VIRTUALMOUNTPOINTin the system options file is invalid because access to itis denied.


User response: Check the VIRTUALMOUNTPOINT inthe system options file and make sure it is accessible.Retry the operation.

ANS1494S Invalid virtual mountpoint filespace-name:Symbolic link.

Explanation: The specified VIRTUALMOUNTPOINTin the system options file is invalid because it is asymbolic link and FOLLOWSYMBOLIC is not set.




User response: Set the option FOLLOWSYMBOLIC toYES in the user options file. Retry the operation.

ANS1495S Invalid virtual mountpoint filespace-name:Other error, rc = return-code.

Explanation: The specified VIRTUALMOUNTPOINTin the system options file is invalid.


User response: Make sure the virtual mountpoint is adirectory and accessible from the shell, and retry theoperation.

ANS1496W Duplicate include/exclude option 'optionfile-name' found while processing theclient options file.This might produce unexpected results.

Explanation: TSM found a duplicate statement whileprocessing the client options file, which might produceunexpected results.


User response: Verify if you obtained the desiredresults. If not, you need to correct the client options fileby removing the duplicate option statement.

ANS1497W Duplicate include/exclude option 'optionfile-name' found while processing theclient options passed by the server.This might produce unexpected results.

Explanation: TSM found a duplicate statement whileprocessing the client options by the server, which mightproduce unexpected results.


User response: Verify if you obtained the desiredresults. If not, you need to correct either the clientoptions file or the client options passed by the server.

ANS1498E The IIS services failed to stop. No fileswill be restored.

Explanation: An error occurred while stopping theInternet Information Services (IIS) services. Themetabase will not be restored.


User response: Examine the Windows event log andTSM error log for messages related to InternetInformation Services (IIS). You might need to quiesceIIS activity or reboot the machine in order to freeresources which are preventing the IIS service fromstopping.

ANS1499E Creation of table of contents failed.

Explanation: A failure occurred on the server duringcreation of the table of contents.

System action: The table of contents was not created.

User response: This abort code indicates there was aproblem creating a table of contents on the server. Thesysadmin will need to consult the activity log on theserver to determine the cause.

ANS1500E Module dsmtca not found in securedirectory.

Explanation: TSM cannot find the TrustedCommunication Agent module (dsmtca) in theappropriate directory.


User response: Log on as root user, then create a linkto dsmtca module in /usr/bin with the command: ln -s/usr/tivoli/tsm/client/ba/bin/dsmtca/usr/bin/dsmtca

ANS1501E Trusted agent execution/ownerpermissions are invalid

Explanation: The Trusted Communication Agentexecution/owner permissions are invalid.


User response: Have your system administrator checkthe installation instructions for the client to ensure thatthe Trusted Communication Agent permissions are setcorrectly. This error can be caused by installing TSM asa non-root user. For the UNIX platforms that have theinstallation program (dsm.install), you must rundsm.install while logged in as the root user.

ANS1502E Access to system function required torun has been denied

Explanation: The permissions of the TrustedCommunication Agent do not allow it to be accessedby the user of the TSM client.



ANS1503E Valid password not available for server'server-name'.The administrator for your system mustrun TSM and enter the password tostore it locally.

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


User response: The administrator for your system



must set and store a new password.

ANS1504E Error starting the TrustedCommunication Agent process.

Explanation: An error has occurred starting theTrusted Communication Agent process; specifically, thefork() function has failed.


User response: Probable system error. If the problempersists, restart the workstation.

ANS1505W Performing image backup of the entirevolume for volume name. TheIMAGEGAPSIZE option value of imagegap size is being ignored as this level ofthe operating system does not supportused block image backup. Pleaseupgrade to AIX 5.3 Maintenance Level 7or later in order to perform used blockimage backup.

Explanation: AIX 5.3 Maintenance Level 7 or later hassome necessary fixes that are required to support usedblock image backup.


User response: Please upgrade to AIX 5.3Maintenance Level 7 or later in order to perform usedblock image backup.

ANS1506E The TSM Trusted Communication Agentreceived an invalid request.

Explanation: The Trusted Communication Agent isinvoked by the TSM client and has received anunknown request argument in the call.


User response: It is possible the TrustedCommunication Agent was mistakenly invoked by aprocess other than the TSM client. If that is not thecase, then this is an internal error. If the problemrecurs, contact your IBM service representative.

ANS1507E This action requires TSM administrativeauthority on this system.

Explanation: An activity has been attempted that mustbe performed by the TSM administrator (for example,open registration, filespace delete or password update).


User response: If the activity is required, theadministrator for this system must perform it.

ANS1508E Error allocating semaphores.

Explanation: An error has occurred because thesemaphores you are attempting to allocate have becomeinsufficient.


User response: Ask your system administrator forassistance, and possibly increase the number ofsemaphores in your system.

ANS1509E Error setting semaphore value orwaiting on semaphore.

Explanation: An error has occurred while attemptingto set or wait on a semaphore.



ANS1510W The specified backupset either does notexist, or does not contain file data.

Explanation: The specified backupset either does notexist, or does not contain file data for the node namespecified. The restore backupset command is limited tobackupsets that contain file data. To restore an imagebackup from a backupset, use the restore imagecommand.


User response: If an incorrect backupset name wasspecified, try the command again with the correctbackupset name. If you are trying to restore an imagefrom a backupset, refer to the restore image commandfor the correct syntax.

ANS1511I Invalid Restore session number entered.Try again.

Explanation: You entered a number not shown in thelist of restartable restores. The number you entered iseither less than one or greater than the highest itemnumber displayed.



ANS1512E Scheduled event 'event' failed. Returncode = value.

Explanation: One or more error conditions wereencountered that prevented the schedule fromcompleting successfully. This message is preceded byother messages that indicate the specific problemsencountered during the operation.

System action: Scheduled event failed.



User response: Check the schedule and error log filesfor the messages that specify what problems wereencountered during the operation. Correct theconditions that caused those messages to be issued. Thespecific corrective actions will depend on the specificerrors encountered.

For more information about return codes, search for"client return codes" in the product information(www.ibm.com/support/knowledgecenter/SSGSG7/).

ANS1513E The object 'object_name' is skipped fromrename. Error_condition.

Explanation: IBM Tivoli Storage Manager skips thespecified object from renaming because the object withthe same long name but with different attributes existson the server.

System action: The backup operation continues. Thespecified object will expire during the next incrementalbackup.

User response: The object is skipped if one of thefollowing condition occurs:

The long name object(LN) has a more recent insertdate than the short name object(SN).

The management classes for LN and SN do notmatch.

The copy groups for LN and SN do not match.

LN and SN have different owners.

The creation date for LN and SN do not match.

The short name attribute for LN does not matchSN.

If you are unable to determine what is wrong, reportthe problem to your service representative.

ANS1514W Encryption key passwords are not thesame.

Explanation: The key passwords are different.

System action: TSM allows you to try again.

User response: Enter the correct password.

ANS1515E Loading a table of contents failed.

Explanation: A failure occurred on the server duringloading of the table of contents.

System action: The table of contents was not loaded.

User response: This abort code indicates there was aproblem loading a table of contents on the server. Thesysadmin will need to consult the activity log on theserver to determine the cause.

ANS1519E Your node does not have permission todelete backup files

Explanation: The server does not allow your node todelete backup files.

System action: TSM did not delete the backup files.


ANS1520E Failure writing to the Tivoli StorageManager error log: errno = errno-value,

Explanation: A failure was encountered when writingto the dsmerror log or dsierror log. The system set theerror code errno-value. It is possible that no space isavailable at the given log location.


User response: Set the DSM_LOG (or DSMI_LOG)environment variable to a directory with adequatespace to write the log data.

ANS1521E Failure writing to a Tivoli StorageManager log or log-related file: file-name,errno = errno-value, reason

Explanation: A failure was encountered when writingto one of the log files or a related file named file-name.The system set the error code errno-value. reason is thesystem explanation of that error code. Among otherthings, it is possible that no space is available at thegiven log location.


User response: Set the DSM_LOG (or DSMI_LOG)environment variable to a directory with adequatespace to write the log data.

ANS1522E It is not possible to authenticate withthe client node client-node !The Space Management Agent versionagent-version running on client-nodedoes not match with the SpaceManagement Consoleversion console-version you are running !

Explanation: The version of the Space ManagementConsole does not match with the version of the SpaceManagement Agent running on the client nodemachine. To avoid incompatibleness it is necessary torun the console and the agent with the same version.

System action: The Space Management Console exits.

User response: Use Space Management Console withthe same version like the Space Management Agentrunning on the HSM node you want to manage.



ANS1523E An error occurred while connecting toTSA/SMDR service.

Explanation: An error was encountered during a callto the TSA/SMDR service. This message usuallyfollows previous messages that contain more specificinformation about the problem.


User response: Refer to previous messages indsmerror.log for further information. If those messagesare not helpful in identifying the cause of the problem,see your system administrator for further assistance.

ANS1528I TSM is converting the log-file fromcontinuous (pruning) mode to wrappingmode. This process may take severalminutes.

Explanation: The log-file was previously in continuousmode where the only size control was through the useof ERRORLOGRETENTION orSCHEDLOGRETENTION option. This is the firstoccasion where ERRORLOGMAX or SCHEDLOGMAXis specified for this log, so its format must be changedand old data saved.

System action: Transition processing continues.


ANS1529I TSM is converting the log-file fromwrapping mode to continuous (pruning)mode. This process may take severalminutes.

Explanation: The log-file was previously in wrappingmode where the size control was through the use of theERRORLOGMAX or SCHEDLOGMAX option. This isthe first occasion where ERRORLOGMAX orSCHEDLOGMAX is not specified for this log, so itsformat must be changed and old data saved.



ANS1530I count log records processed.

Explanation: This is just a progress report to let youknow the process is still ongoing.



ANS1532E Proxy Rejected: Proxy authority has notbeen granted to this node.

Explanation: The node has not been granted proxyauthority to access the node named by theASNODENAME option. The TSM administrator mustfirst grant proxy authority.


User response: The TSM server administrator mustgrant proxy authority for this node. See theadministrator command "Grant Proxynode".

ANS1533E Proxy Rejected: The node name youspecified in the ASNODENAME optionis locked.

Explanation: The TSM administrator has locked thenode you specified as the ASNODENAME option.


User response: The TSM server administrator mustunlock the node before you can access it. Try theoperation later, or check with your TSM administrator.

ANS1534E Proxy Rejected: The TSM server has runout of memory.

Explanation: There is not enough memory available toallow this operation to continue.


User response: Try the operation again. If the problemcontinues, see your system administrator to increase theamount of memory of the server.

ANS1535E Proxy Rejected: ASNODENAME andNODENAME are identical.

Explanation: TSM does not allow the ASNODENAMEand NODENAME option values to be the same.


User response: Use the ASNODENAME option onlyto access another node. It is not necessary to setASNODENAME option to access your own node.Remove ASNODENAME from your option file unlessyou are actually trying to access a node that you havebeen granted authority to access with theadministrative command "Grant Proxynode".

ANS1536E Proxy Rejected: The server has aninternal error.

Explanation: The client cannot proxy to the nodenamed by the ASNODENAME option because of aninternal server error.


User response: See your system administratorimmediately.

ANS1537E The ASNODENAME option is not validwith the FROMNODE option.

Explanation: None.




User response: Remove the ASNODENAME optionfrom the options file or do not use the FROMNODEoption.

ANS1538E The operation that is being attemptedcannot be invoked using theASNODENAME option.

Explanation: None.


User response: Remove the ASNODENAME optionand retry the operation.

ANS1539E The ASNODENAME option cannot beused with the CLUSTERNODE option.

Explanation: None.



ANS1540E Incremental backups using snapshotdifference is not supported on thisversion of the NetApp file server.

Explanation: Incremental backup using Snapshotdifference requires Data ONTAP V7.3 or later. To backup unicode file names, upgrade to Data ONTAP V7.3.3or later or V8.1 or later.


User response: Upgrade the file server to a supportedlevel of Data ONTAP, then retry the operation.

ANS1544E An error in WAS processing hasoccurred.

Explanation: None.

System action: None

User response: Run the following command to see thenodes that can be backed up:dsmc query was -wastype=localMake sure the results are correct for your environment,then try the operation again. If the problem persists,contact TSM technical support for further assistance.

ANS1546W TSM failed to lock the WebSphereconfiguration repository.

Explanation: None.

System action: The lock of the WebSphereconfiguration repository fails.

User response: Ensure that the WebSphere server isrunning. If the server is already running, ensure thatthe repository is unlocked. Ensure that you are backingup the correct node. To see a list of available nodes that

can be backed up, enter: 'dsmc q was -wastype=local'.

ANS1547W TSM failed to unlock the WebSphereConfiguration Repository.

Explanation: None.

System action: The unlock of the WebSphereConfiguration Repository fails.

User response: Make sure that the WebSphere serveris running. If the repository is locked, then unlock itand try the operation again. Ensure that the correctnode is being backed up. To see a list of availablenodes that can be backed up, run: 'dsmc q was-wastype=local'.

ANS1548E A supported version of WebSphere isnot installed on this machine.

Explanation: A supported version of WebSphere is notinstalled on this machine. The only version ofWebSphere that is supported is 5.0.x.

System action: None

User response: Install WebSphere 5.0 on the machine.

ANS1549E No application server instances werefound. Unable to perform backup.

Explanation: The application server is not installed onthis machine.

System action: Backup is not performed.

User response: Install the application server.

ANS1550E No network deployment managerinstances were found to back up.

Explanation: Deployment manager is not installed onthis machine.

System action: Back up is not performed.

User response: Install the network deploymentmanager.

ANS1552W A user name and a password have notbeen provided to Data Protection forWebSphere.

Explanation: The dsmc set WASPassword commandhas not been run to provide the user name and thepassword for Data Protection for WebSphere. DataProtection for WebSphere needs the user name andpassword to be able to run when WebSphere security isturned on.

System action: Data Protection for WebSphere cannotrun.

User response: Run the dsmc set WASPassword



command to set the WebSphere security user name andpassword.

ANS1553W The user name and password that havebeen provided to Data Protection forWebSphere are invalid.

Explanation: None.

System action: Data Protection for WebSphere cannotrun.

User response: Run the dsmc set WASPasswordcommand to set the WebSphere security user name andpassword.

ANS1555E The WebSphere Application Server(WAS) plug-in level must be at 5.2.1 orgreater to set the WebSphere user andpassword.

Explanation: You must have the backup-archive clientand the WAS plug-in at a level of 5.2.1 or higher to beable to connect to WebSphere when security is enabled.

System action: WebSphere does not set the user andpassword.

User response: Upgrade the WAS plug-in to 5.2.1 orgreater.

ANS1556E Setting the WAS user and passwordfailed.

Explanation: Password validation for the WAS userand password failed.

System action: WAS password validation fails.

User response: Rerun the set WASPassword commandwith the correct values for user and password.

ANS1557W The WAS Server was not running, andthe password file was saved withoutvalidation.

Explanation: If the WAS server is down, then it is notpossible to connect to the server and validate theuser-entered password. The password has still beensaved, but no validation has been performed.

System action: The set WAS password command didnot validate the password. The password has still beensaved, but no validation has been performed. Thepassword may be incorrect.

User response: There are two options:

v Try a backup. If the backup performs a failover, andthere is a incorrect password message in the errorlog, then the password that was entered is incorrect.

v Start the WAS server and rerun the set passwordcommand. Since the server is now up, validation willbe performed as normal and the user notified if agood/bad password was entered.

ANS1560W The WebSphere server is not running.

Explanation: The WebSphere server is not running.The WAS server is running for backup operations.

System action: The WebSphere server is not running.

User response: Start the WAS server and run thebackup again.

ANS1562E WAS Restore failed during EARExpansion.

Explanation: EAR Expansion is performed for aWebSphere Application server after the files have beenrestored.

System action: WAS restore fails.

User response: Run the restore again.

ANS1563W The itsm.was.properties file does notexist.

Explanation: The itsm.was.properties file is used tostore the WebSphere security user name and password.


User response: Run the dsmc set waspasswordcommand to create this file.

ANS1565E No WebSphere EARExpander wasfound. Copy the EARExpander toolfrom the base WebSphere bin directoryto the instance bin directory, then runthe restore operation again.

Explanation: The EAR files are expanded for aninstance of an Application server and the EARExpandertool does not exist in the instance bin directory.

System action: No WebSphere EARExpander found.

User response: Copy the WAS EARExpander toolfrom the base install's bin directory to the bin directoryof the instance. Then run the WAS restore operationagain, after the EARExpander tool has been copied.

ANS1566E The version of WebSphere on themachine does not match the version ofWebSphere that was backed up. Theseversions must match for a WAS restoreoperation.

Explanation: The version of WebSphere on themachine does not match the version of WebSphere thatwas backed up. These versions must match for a WASrestore operation.

System action: The WAS restore operation fails.

User response: Install the correct version ofWebSphere on the machine before performing therestore operation.



ANS1567I A 5.2.2 or higher client is restoring databacked up from a 5.2.0 client. Noversion check can be performed beforethe restore.

Explanation: WebSphere's version information was notstored as part of the backup for 5.2.0. So, a 5.2.2 clientcannot ensure that the version of WAS that is beingrestored is the same version of WAS that is on themachine. A version of WAS that is restored may beincompatible with the version of WAS on the machineand can cause errors in WAS.

System action: No version check is performed.

User response: Make sure that the version of WASthat is being restored is the same as the version of WASthat is installed on the machine.

ANS1568E The CAD attempted to register it'stcpport and tcpip address without usingthe TCPCADADDRESS option.

Explanation: The CAD sent the port and addressinformation to the server, however, there was aproblem registering the information with the server.The problem occurred because no default value for thetcpip address was provided. The server was unable todetermine a default value for the tcpip address becausethe communication method was not tcpip.

System action: The server cannot register theinformation for the CAD. CAD processing willcontinue, but some functions of the CAD may not beworking properly.

User response: Use TCPCADADDRESS in the clientoption file to indicate the proper TCP/IP address forthis CAD.

ANS1569E The CAD attempted to register it'stcpport and tcpip address but theTCP/IP address resolved to the loopbackaddress and was rejected by the server.

Explanation: The CAD sent the port and addressinformation to the server, however, there was aproblem registering the information with the server.The problem occurred because the server detected thatthe address provided resolved to the loopback address.

System action: The server did not register theinformation for the CAD. CAD processing willcontinue, but some functions of the CAD may not beworking properly.

User response: Use TCPCADADDRESS in the clientoption file to indicate the proper TCP/IP address forthis CAD. Loopback address is not valid.

ANS1570E Registering this instance of the Cadwith the server failed. Cad processcontinues.

Explanation: The CAD failed to register addressinformation to the server, due to an error. There shouldbe a message immediately preceding this message thatwould indicate the problem more precisely.

System action: The server did not register theinformation for the CAD. CAD processing willcontinue, but some functions of the CAD may not beworking properly.

User response: Look at messages immediatelypreceding this message to help determine what erroroccurred.

ANS1571E The time-option option cannot be usedwithout specifying the date-option option

Explanation: If the to/from/pit time options isspecified then the corresponding to/from/pit dateMUST also be specified.


User response: Either remove the to/from/pit timeoption or add the corresponding to/from/pit dateoption.

ANS1572E An unexpected error was received fromthe server query, RC=re tcode.

Explanation: An unexpected error was received by theclient. This could be caused by network problems or aprogramming error.



ANS1573E FROMDATE and TODATE cannot beused with PITDATE.

Explanation: The PITDATE option specifies differentand conflicting date selection criteria from theFROMDATE and TODATE options. Therefore theseoptions cannot be combined.


User response: Determine whether you require thefunctionality of PITDATE or FROMDATE andTODATE, then try the operation again. If you want torestore files as of a certain date and time, use PITDATEand PITTIME. If you want to restore files from a givenrange of dates, use FROMDATE, TODATE,FROMTIME, and TOTIME. Refer to the TSM clientmanual for your operating system for additionalinformation about these options.



ANS1574E Journal Query Failed.

Explanation: The journal daemon was unable toprocess the requested journal query.

System action: Journal backup processing isinterrupted.

User response: Retry the backup, check the journaldaemon errorlog for the cause of the failure. Backup ofother file systems in the domain will continue.

ANS1575E Journal Daemon Communications Error.

Explanation: An error occurred communicating withthe journal daemon.

System action: Journal backup processing isinterrupted.

User response: Retry the backup, check the journaldaemon and client errorlogs for the cause of the failure.

ANS1576W Space Management Agent versionmismatch.The Space Management Agent(hsmagent) version agent-versionrunning on 'client-node' client node doesnot match with theSpace Management Console (GUI)version console-version you are running!To avoid compatibility problems, pleaseuse the same version for theSpace Management Console and theSpace Management Agent.Do you want to proceed?

Explanation: The version of the Space ManagementConsole does not match with the version of the SpaceManagement Agent running on the client nodemachine. To avoid compatibility problems, please usethe same version for the Space Management Console(GUI) and the Space Management Agent (hsmagent).

System action: Prompt the user to exit or continue.

User response: Use Space Management Console (GUI)with the same version like the Space ManagementAgent (hsmagent) running on the HSM node you wantto manage.

ANS1577I The Windows console event handlerreceived a 'event' console event.

Explanation: A console event was received by one ofthe IBM Tivoli Storage Manager processes or programs.The following events can be received:

v Ctrl-C - This indicates either the user entered thectrl-c sequence or that one of the Windows serviceswas stopped.



ANS1578E The specified path 'path' is not valid forbackup or archive.

Explanation: The specified path is a special file systemor part of a special file system. Special file systemscontain dynamic information generated by theoperating system and should not be backed up orarchived. Refer to the TSM client manual for acomplete list of special file systems for your operatingsystem.

System action: Processing continues if there are otherfile systems to back up.

User response: Do not specify special file systems forbackup or archive.

ANS1579E GSKit function func-name failed witherror-code: session

Explanation: A GSKit function has failed with thespecified error code.

System action: Processing stopped

User response: Make sure you have configured thekey database for SSL communication as described inthe documentation. If the problem persists, contact TSMcustomer support.

ANS1580W An Include.Fs statement withperformance algorithm set already existsfor the drive specified. Do you want toreplace the statement?

Explanation: The user tried to create a duplicateInclude.Fs entry on a drive that already has aperformance algorithm associated with it. This isapplicable to the Preference Editor on the MFC GUI

System action: The user can replace the statementwith the new one or they can cancel out of thisoperation

User response: The user is prompted to replace thestatement with the new one or they can say No tocancel out of this operation.

ANS1581W 'object-name' was restored as 'temp-name'.A reboot is required to complete therestore.

Explanation: This is a system file restored and couldnot be immediately replaced. The file will be replacedduring the next reboot of the operating system. It isimportant to note that until the reboot occurs, thechanges will not be in effect.

System action: TSM restored the file with a temporaryname, and instructed the operating system to replacethe original file with the restored file during the nextboot of the operating system.

User response: Reboot the machine as soon as



possible after the TSM restore operation ends.

ANS1583E The Hardware Utility plug-in modulewas not found or could not be loaded.

Explanation: Processing stops.


User response: Run "dsmc show plugins" at the TSMcommand-line client prompt to see the availableplug-ins on the system and verify the path which isbeing used to load the plug-ins. If the plugin path isavailable and the Hardware Utility plug-in,libPiHDW.a, is present, ensure that the LIBPATHvariable is set to the Hardware product's library path,for example, LIBPTH=/usr/opt/db2_08_01/lib.

ANS1584E Error loading system library'libdevmapper.so' required for imageoperations for LVM2 volumes.

Explanation: The system library libdevmapper.sorequired for LVM2 image operations could not beloaded. This error can occur when the library does notexist on the system, or the library is an earlier levelthan is required. This error also occurs when the librarycan not be opened by the TSM clienti process.

System action: The image operations for LVM2volumes are not available.

User response: Check the installed packages and thelibrary versions on the system. If correct versions areinstalled, check for access related issues. If the systemdoes not have these libraries installed, contact yourLinux OS distributer. Also, refer to Technote 1452629:https://www.ibm.com/support/docview.wss?uid=swg21452629

ANS1587W Unable to read extended attributes forobject object-full-name due to errno:errno-value, reason: errno-explanation

Explanation: The extended attributes of the objectcould not be read. The system set the error codeerrno-value and the reason errno-explanation. If thereason errno-explanation is either "access denied" or"permission denied", the current user does not havepermission to read the extended attributes of the object.


User response: The error is expected if the operationtries to read extended attributes of an object that youdo not own or do not have access to. If the reasonindicates an input/output error, perform the file systemconsistency check procedure and try the operationagain. If the problem persists, contact IBM technicalsupport for further assistance.

ANS1588W I/O error reading file attribute: attr-namefor: file-name. errno = errno-value,

Explanation: The attribute attr-name of the filefile-name could not be retrieved. The system set theerror code errno-value. If the reason given is "accessdenied," the current user does not have permission toread the file attributes.

System action: Processing continues without backingup the specified file attribute.

User response: Correct the condition causing thephysical error.

ANS1589W Unable to write extended attributes forobject-full-name due to errno: errno-value,reason: errno-explanation

Explanation: The extended attributes of the objectcould not be written. The system set the error codeerrno-value and the reason errno-explanation. If thereason is either "access denied" or "permission denied",the current user does not have permission to write theextended attributes of the object.

System action: Processing continues without restoringthe extended attributes.

User response: The error is expected if the operationtries to write extended attributes to an object that youdo not own or do not have access to. If the reasonindicates an input/output error, perform the file systemconsistency check procedure and retry the operation. Ifthe problem persists, contact IBM technical support forfurther assistance.

ANS1590W I/O error writing file attribute: attr-namefor: file-name. errno = errno-value,

Explanation: The attribute attr-name of the filefile-name could not be set. The system set the error codeerrno-value. If the reason given is "access denied," thecurrent user does not have permission to set the fileattributes.

System action: Processing continues without restoringthe specified file attribute.

User response: Correct the condition causing thephysical error.

ANS1592E Failed to initialize SSL protocol.

Explanation: TSM was unable to initialize SSLprotocol.


User response: Check for GSKit related messages inthe error log. Make sure you have configured the keydatabase for SSL communication as described in thedocumentation. If the problem persists, contact TSMcustomer support.



ANS1593E Cannot open the key database.

Explanation: TSM was unable to open the keyfile thatis expected to contain the server certificate for SSLcommunications.


User response: Make sure you have configured thekey database for SSL communication as described inthe documentation. If the problem persists, contact TSMcustomer support.

ANS1594E The key database password is incorrector unavailable.

Explanation: The client was unable to open thecertificate key database using the stored password, orthe stored password could not be read.


User response: Make sure that you configure the keydatabase for SSL communication as described in theClient Installation and User's Guide. Also make surethat the stash file, dsmcert.sth, is readable by thecurrent user.

ANS1595E Bad server certificate.

Explanation: TSM was unable to open SSL connectionto server because of a bad certificate. This error usuallyoccurs when the server certificate cannot be verified bythe client.


User response: Make sure you have configured thekey database for SSL communication as described inthe documentation. Make sure to import the correctcertificate from the TSM server you are trying toconnect to.

ANS1596E SSL protocol is not supported.

Explanation: SSL protocol is not supported on thisplatform.


User response: Refer to TSM documentation for thelist of supported platforms.

ANS1597E The -pick and -deltype=all options arenot valid together.

Explanation: -deltype=all is used to delete an entiredirectory tree. You cannot use -pick to select individualobjects from the tree. -pick is valid only with-deltype=active or -deltype=inactive.


User response: Try the operation again with a validcombination of options.

If you want to delete an entire tree, use -deltype=all,but do not use -pick.If you want to select which backup versions to delete,specify -deltype=active or -deltype=inactive, and usethe -pick option. Also use -subdir=yes if you want thefile selection to include files in subdirectories of the filespecification.See the client manual or command line help foradditional information.

ANS1598E -deltype=all is not valid for this filespecification.

Explanation: -deltype=all is used to delete an entiredirectory tree. You must specify a fully wildcarddirectory when using -deltype=all.


User response: Try the operation again with a validcombination of options.If you want to delete all backup versions of an entiredirectory tree, use -deltype=all and a fully wildcardedfile specification.If you want to delete backup versions of partiallyqualified file names, use -deltype=inactive or-deltype=active. Also use -subdir=yes if you want todelete backup versions in subdirectories of the filespecification.See the client manual or command line help foradditional information.

ANS1599E Cannot load SSL runtime library.

Explanation: TSM failed to dynamically load SSLruntime library necessary for SSL protocol


User response: Make sure TSM client is properlyinstalled. Try to reinstall the client software. If theproblem persists, contact TSM customer support.

ANS1600E Unable to load the Data Protection forLotus Domino library.

Explanation: The Datt Protection for Lotus Dominolibrary could not be loaded.


User response: Ensure that Domino plugin is properlyconfigured and check the error log on the clientmachine for more information.

ANS1601E The Domino plugin operation failedbecause of an internal error.

Explanation: A Domino plugin internal error hasoccurred.


User response: Check the error log on the client



machine for more information.

ANS1602E The Domino plugin operation failedbecause the preferences file was notfound.

Explanation: The Data Protection for Lotus Dominopreference file could not be found.


User response: The Data Protection for Lotus forDomino configuration file (default name domdsm.cfg)could not be found. Check the error log on the clientmachine for more information.

ANS1603E The Domino plugin operation failedbecause of an internal TCP/IP error.

Explanation: A TCP/IP error has occurred.


User response: Check the error log on the clientmachine for more information.

ANS1604E The Domino plugin operation failedtrying to start the dsmdomp addressspace.

Explanation: The dsmdomp address space could notbe started. This is probably an installation error.


User response: Ensure that the lotus/bin directory hasa symbolic link to the tools directory for dsmdomp andthe lotus/notes directory has a symbolic link to thedsmdomp executable. If the problem persists, contactyour System Administrator for further assistance.

ANS1605E The Domino plugin operation failedwhile initializing communications withthe dsmdomp address space.

Explanation: The Domino plugin communicationinitialization failed.


User response: The dsmdomp address space failedduring its initialization. This is likely to be aninstallation error. Ensure that the lotus/bin directoryhas a symbolic link to the tools directory for dsmdompand the lotus/notes directory has a symbolic link to thedsmdomp executable. If the problem persists, contactyour System Administrator for further assistance.

ANS1606E The Domino plugin operation failedwhile starting up the dsmdomp addressspace.

Explanation: The dsmdomp address space could notbe started.

System action: The TDP for Domino processing stops.

User response: The dsmdomp address space failedduring its initialization. This is likely to be aninstallation error. Ensure that the lotus/bin directoryhas a symbolic link to the tools directory for dsmdompand the lotus/notes directory has a symbolic link to thedsmdomp executable. Examine the file/tmp/dsmdomp* for more information. If the problempersists, contact your System Administrator for furtherassistance.

ANS1607E A plugin found in the plugins library isnot supported by the current level of theTSM client.

Explanation: The plugin is not loaded, and processingcontinues.

System action: The plugin is not loaded, andprocessing continues.

User response: This probably is an installation error.Ensure that the plugins directory contains valid pluginlibraries, and that the correct level of the TSM clienthas been installed. If the problem persists, contact yourSystem Administrator for further assistance.

ANS1608E Domino plugin operation failed withthe following message:messsage

Explanation: A Domino plugin operation erroroccurred.


User response: Correct the error that caused theoperation to fail.

ANS1609E Domino plugin process failed. Thefollowing messages are associated withthe error.messsage.

Explanation: A Domino plugin operation erroroccurred.


User response: Correct the error that caused theoperation to fail.

ANS1611E A plugin operation failed because of aninternal error.

Explanation: A plugin internal error has occurred.

System action: The plugin operation stops.

User response: If the error persists, run with tracingenabled and contact your System Administrator andIBM for further assistance.



ANS1612E The Domino plugin operation failedbecause of a TSM API error.

Explanation: An TSM API error occurred .


User response: Check error log on the client machinefor more information.

ANS1613E >Could not load the TSM API.

Explanation: The TSM API could not be loaded.


User response: Check error log on the client machinefor more information.

ANS1614E The Domino plugin 'Try and Buy'license has expired.

Explanation: The 'Try and Buy' license that wasdetected has expired.


User response: This product is no longer valid for use.A valid license must be obtained before running theproduct.

ANS1615E The Domino plugin operation faileddue to a license error.

Explanation: Domino plugin license verification failed.


User response: Check the error log for furtherinformation.

ANS1616E The Domino plugin operation failedbecause the Lotus Domino API couldnot be loaded.

Explanation: The Lotus Domino API could not beloaded.


User response: Ensure the Lotus Domino Server isinstalled correctly.

ANS1617E The Domino plugin operation failedbecause of a Data Protection for DominoAPI error.

Explanation: A Data Protection for Domino API erroroccurred during a Domino plugin operation.


User response: For more details, view the followingTivoli Storage Manager error logs.

The API error log (dsierror.log) and the log of DataProtection for Domino activity (domdsm.log). The

default location of these logs is the Data Protection forDomino installation directory.

The backup-archive client error log (dsmerror.log), theweb client error log (dsmwebcl.log), and the log ofscheduler activite (dsmsched.log). The default locationof these logs is the backup-archive installationdirectory.

ANS1618E A Domino plugin operation is alreadyin progress. Please wait for operation tocomplete.

Explanation: A Domino plugin operation is inprogress.

System action: The Domino plugin operation stops.

User response: Please wait for the Domino pluginoperation to complete before starting a new Dominoplugin operation.

ANS1619E The IBM Tivoli Storage Managerapplication client cannot work with theversion of the Domino plugin you haveinstalled.

Explanation: The version of the Domino plugincurrently installed on the system is older than theversion used to build the IBM Tivoli Storage Managerapplication client.


User response: Install a version of the Domino pluginat or later than the level of the IBM Tivoli StorageManager application client.

ANS1621E Failed to update backup attributes onserver for local backup for 'filespacenamepath-namefile-name', object id -'object-id':'object-id' return code 'returncode'.

Explanation: TSM failed to update attributes for thenamed backup object on the server. The server may notreflect correct state of the backup.


User response: Check preceding error messages inerror log for more information. Retry the operation. Ifproblem continues, contact your TSM administrator.

ANS1622I Number of backup objects cleaned upon server: 'number' number of localsnapshot resources made available:'number'.

Explanation: While performing consistency check forserver's database and the local repository maintainedon the client system, reported inconsistencies werefound. Inconsistent backups cannot be restored,therefore TSM deletes all inconsistent backup objects



and frees the space occupied in the local repository.


User response: Check error log for further details onwhich objects on server were deleted. If numbers lookunusually high check your configuration and if itcontinues, contact your TSM administrator.

ANS1623W Backup of NSF DB2 database wasskipped. NSF DB2 databases notsupported.

Explanation: This version of DP for Domino plugindoes not support NSF DB2 databases.

System action: Backup of NSF DB2 databases isskipped.

User response: Exclude NSF DB2 databases frombackup.

ANS1624E 'value' is an invalid value for option'option' for 'command' command

Explanation: The specified option value is not valid inthis context.

System action: The operation was stopped

User response: Specify a valid value for the option.Consult documentation for valid values.

ANS1626E An unexpected error was encounteredwhen processing a TSM operation usinga hardware or snapshot function.TSM function name : function-nameTSM function : function-descTSM return code : TSM-rcTSM file : file-name (line-number)

Explanation: None.



ANS1627E SVC virtual disk v1 is not valid.

Explanation: The specified virtual disk is not found inthe list of virtual disks provided by the connected SVCcluster.

System action: Process stops.

User response: Ensure that this virtual disk exists inthe SVC.

ANS1628E The source v1 and target v2 virtual disksare in different SVC clusters.

Explanation: The SVC source and target virtual diskshave to be assigned to the same SVC cluster.


User response: Ensure that the source and targetvirtual disks are in the same SVC.

ANS1629E The source v1 and target v2 virtual disksare of different size.

Explanation: The SVC source and target virtual diskshave to be of the same size.


User response: Ensure that the source and targetvirtual disks are the same size.

ANS1630E An error was returned calling anoperation of the Common InterfaceModel(CIM).TSM function name : function-nameTSM function : function-descTSM CIM return code: 0xCIM-rcTSM file : file-name (line-number)

Explanation: An error occurred when calling a CIMoperation of the disk subsystem.


User response: Please see the section about the CIMreturn codes and their descriptions in the productpublication.

ANS1631E A memory allocation error has occurredin file filename, line number linenumber.

Explanation: Enough memory was not available tocontinue processing.


User response: Ensure that your system has sufficientreal and virtual memory. Close unnecessaryapplications.

ANS1632I 'option name' not specified, defaults to'deafult value'

Explanation: A value for the option is not spedified,default value wil be used.

System action: The operation continues using defaultvalue for the option

User response: To override the default, specify a validvalue for the option. Consult documentation for validvalues.

ANS1647E 'input spec': Invalid input specificationformat.

Explanation: The specified input for this commmandis invalid.

System action: The operation stops.



User response: Verify that the syntax specified withthe parameter is correct.

ANS1648W PREViewsize option value is greaterthan the specified stub size.

Explanation: The PREViewsize CLI option valuespecified must not be greater than the stub size for thefile.

System action: Operation stopped. File skipped.

User response: Change the value of the PREViewsizeaccordingly.

ANS1649E The option 'specified-option' isinconsistent with the option'other-option'.

Explanation: The command failed because the the twooptions cannot be used at the same time.

System action: The command is stopped.

User response: Run the command and do not specifyboth options.

ANS1650I Command: command-string

Explanation: The command string listed in themessagewas issued by the TSM Backup-Archive client.

System action: This message is for auditing purposesonly.

User response: This message is for auditing purposesonly.

ANS1651I Backed Up: fshlll

Explanation: The backup operation for the object wassuccessful.



ANS1652I Archived: fshlll

Explanation: The archive operation for the object wassuccessful.



ANS1653I Updated: fshlll

Explanation: The update operation for the object wassuccessful.



ANS1654E Failed: fshlll

Explanation: The backup, archive, restore or retrieveoperation for the object failed.


User response: This message is for auditing purposesonly. For information about the failure refer to the TSMBackup-Archive Client error log.

ANS1655I Restored: fshlll

Explanation: The restore operation for the object wassuccessful.



ANS1656I Retrieved: fshlll

Explanation: The retrieve operation for the object wassuccessful.



ANS1657I Expired: fshlll

Explanation: The active version of the object wasexpired in the TSM database.



ANS1658I Deleted: fshlll

Explanation: The object was deleted from the TSMdatabase.





ANS1659I Skipped: fshlll

Explanation: The object was skipped by the userduring backup or archive processing.



ANS1660I Excluded: fshlll

Explanation: The object was excluded from backup orarchive processing.



ANS1661I Unchanged: fshlll

Explanation: The object has not changed since the lastincremental backup was performed and does not needto be resent.



ANS1662I Agent Node: 'agent_node' Target Node:'target_node'

Explanation: Proxy nodes information.

System action: None

User response: None

ANS1663W The option fractional reserve on volumevol_name was reduced to less than 100percent.

Explanation: Network Appliance stronglyrecommends that when the fractional reserve is set toless than 100 percent you actively monitor spaceconsumption and the rate of change of data in thevolume to ensure you do not run out of space reservedfor overwrites. In that case, if you run out of overwritereserve space, writes to the active file system fail andthe host application or operating system might crash.

System action: Process continues.

User response: Ensure that you monitor the spaceconsumption. Consult Network Appliance for tools tomonitor available space in your volumes.

ANS1664E The snap restore for volume volnamewith snapshot name snapname woulddestroy later snapshots that are requiredfor other applications or for volumeclones.

Explanation: ONTAP will delete newer snapshots of avolume when a specific snapshot is used for snaprestore.


User response: Prior to a snap restore, ensure thatnewer snapshots are not used in other applications orin volume clones.

ANS1665W TSM for ACS did not find anysnapshots for volume volname on the Nseries filer.

Explanation: No snapshots were found for thisvolume on the N series filer.



ANS1666W TSM for ACS did not find anyinformation about the N series volumevolname.

Explanation: The query for information about thisvolume did not return any data.



ANS1667E The snapshot name snapname for volumevolname was not found in the snapshotlist on the N series filer.

Explanation: Snapshot identified by this name doesnot exist.



ANS1668E The 'drive-name1' is not a local disk.

Explanation: The specified file system is network diskor network share. Because the CLUSTERNODE optionis set to YES, the file system cannot be backed up orarchived.





ANS1669W The command subcommand command canonly be run in Windows WinPE mode.

Explanation: The command subcommand command isnot supported on a currently running operating system.You must reboot to Windows WinPE mode to run thiscommand.



ANS1670E The file specification is not valid.Specify a valid Network Appliance orN-Series NFS (AIX, Linux) or CIFS(Windows) volume.

Explanation: The file specification is not valid.Incremental backup using snapshot difference using the-SNAPDIFF option can only be performed on NetworkAppliance or N-Series NFS volumes on AIX and Linux,and on CIFS volumes on Windows. Do not specifyeither Network Appliance or N-Series Qtrees or a pathwithin the Network Appliance or N-Series volume.Only full volumes are supported.


User response: Retry the incremental backupoperation using the -SNAPDIFF option. Specify a validNetwork Appliance or N-Series NFS volume on AIX orLinux, or a CIFS volume on Windows.

ANS1671I The cluster database has been restored.Restarting the cluster services on allnodes. This will take a few minutes.

Explanation: After the cluster database is restored, thecluster service on the restoring node is in a pausedstate. The cluster service on other nodes wereshutdown. All services need to be restarted. If some ofthe services cannot be started automatically, restartthem manually.


User response: No action.

ANS1672I Could not take the cluster resourceresource name offline. MS rc retcode. Erroris ignored.

Explanation: Microsoft recommends taking the clusterresources offline during an authoritative clusterdatabase restore. However, the restore can still be doneif the resources cannot be taken offline. The error isignored.



ANS1673W Cluster service on node node name couldnot be started. You must manually startthe service.

Explanation: The cluster database has been restored.During the restore, the cluster service was taken offline.Tivoli Storage Manager failed to restart the clusterservice.


User response: You can manually start the service forthis node.

ANS1674I The cluster database has been restoredbut the cluster service on some nodescould not be started. Use the FailoverCluster Management tool to manuallystart the nodes.

Explanation: The cluster database has been restored.During the restore, the cluster services were takenoffline except for the node being restored. TivoliStorage Manager failed to automatically start thesecluster services. You need to start them manually. Thenodes whose services failed to start are logged in theclient error log.


User response: You can manually start the clusterservices.

ANS1675W Unable to obtain a list of cluster nodesto restart after the cluster database isrestored. The call 'cmd' returned withMS rc retcode. You must restart thecluster service on all the nodes after therestore is finished.

Explanation: Due to an error, Tivoli Storage Managercould not retrieve a list of nodes in the cluster torestart. The cluster services on these nodes need to bestarted manually. The client error log might containadditional information depending on where the failureoccured.


User response: Manually start the cluster services onall nodes.

ANS1676W You are doing an authoritative clusterdatabase restore. The process may seemto be hang before and after the file isrestored. This is because it may need tostart the cluster service if it is not upand take all the resources offline. Afterthe cluster database is restored, thecluster service will be restarted forchanges to be in effect. The clusterservice on all other nodes also havebeen shutdown. They will be restarted.

ANS1669W • ANS1676W


This may take a few minutes.

Explanation: The restore will seem to be paused attime because before the restore, Tivoli Storage Managerensures the cluster service is up on the restoring nodeand all the resources are taken offline. After the clusterdatabase is restored, the cluster service on the restoringnode is in a paused state. The cluster service on othernodes were shutdown. All services need to be retarted.If some of the services cannot be started automatically,you can try to restart them.



ANS1677W Tivoli Storage Manager failed to set thedisks for quick formatting because of anerror. See the error log for more details.The disks will be slow formatted whichwill cause a slower restore process.

Explanation: By default, Tivoli Storage Manager triesto set the QuickFormat value of theHKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ASR\RestoreSession keyto perform quick formatted on all the disks. Due to anerror, a slow format will be performed on there-creation of the disks. This process will cause aslower restore process.

System action: None

User response: None

ANS1678E ASR path 'path': not found.

Explanation: You have specified a directory that doesnot exist.


User response: Recheck all spelling and punctuation,particularly the placement of directory delimiters (forexample, "\"). Correct the syntax if it is incorrect, thenretry the operation.

ANS1679W Updating the registry to identify whichvolumes have been restored has failed.This does not affect the volumes thathave already been restored. See theerror log for more details. The error isbeing ignored and processing continues.

Explanation: After restoring the critical volumes,Tivoli Storage Manager tries to update theRestoredVolumes value of theHKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ASR\RestoreSession keyto indicate which volumes have been restored. Due toan error accessing the registry, the error is logged butprocessing continues.


User response: None

ANS1680W Function refresh incremental FlashCopycannot be accomplish because noconsistency group found for thesevolumes.

Explanation: A refresh of the incremental FlashCopycan only be done when the consistency group and thecorrespondent FlashCopy relation were establishedpreviously.



ANS1681E DSM_DIR was not set and theASRFILESPATH option was notspecified.

Explanation: The ASR files can be in put in theDSM_DIR path by default or overriden with theASRFILESPATH option. Either one is being set.


User response: Set the DSM_DIR environmentvariable or specify the ASRFILESPATH option on the"RESTORE MACHINEASR" command.

ANS1682W No FlashCopy relationships found inthe storage system.

Explanation: The copy services server (mostly a CIMObject Manager) does not have any FlashCopy relationobjects.

System action: Process may stop.

User response: This is not necessarily a message thatimplies the stop of the process.

ANS1683E The state status of the consistency groupis bad to achive a valid disk backup.

Explanation: TSM ACS function monitoring willexpect that the FlashCopy are in one of the stateIdle_Copied or Copying.

System action: Process will stop.

User response: Verify using the storage GUI the stateof the FlashCopy. If this state was generated by an useraction, try to start the copy process through the storageGUI, then re-start the TSM ACS moniotoring fuction.

ANS1684W Disk Full Error Accessing SubfileCache: exception-name

Explanation: A disk full error occurred attempting toaccess or write to the specified subfile cache file duringa subfile incremental backup. See the client error logfor more detailed information.

System action: Processing continues without subfile.




ANS1685E Incremental backup operation usingsnapshot difference is only available forN series/NetApp filer volumes, is not aNetApp volume.

Explanation: Cannot perform NAS NFS/CIFSincremental backup operation using snapshot differenceon the mounted or mapped volume because thevolume is not a N series/NetApp filer volume.


User response: Retry the incremental backupoperation by specifying an entire NAS NFS or CIFSvolume.

ANS1686I Single Instance Store link 'file-name' willbe restored or retrieved as a normal file.

Explanation: TSM restores Single Instance Store (SIS)links as normal files. If the restored version is aduplicate of of the copy in the SIS Common Store, thenthe SIS Groveler will eventually recreate the SIS link.

System action: TSM creates normal files instead of thereparse point.

User response: None

ANS1687E VSS Instant Restore operation failed.Please examine the TSM client error logfile (DSMERROR.LOG), the WindowsApplication Event Log, the WindowsSystem Event Log, and the VSSprovider log file (if applicable) for moredetails. Consult the VSS providerdocumentation for the meaning of theerror return code.

Explanation: VSS hardware provider failed whileperforming volume-level copy restore operation.


User response: Attempt to determine the source of theerror by examining the Application Client log file, theTSM client error log file (DSMERROR.LOG), theWindows Application Event Log, the Windows SystemEvent Log, and the VSS provider log file, if applicable.Additional instructions for Windows VSS operationsare located in the TSM Problem Determination Guide.Correct the problem and retry the operation. If thiserror persists, contact your service representative.

ANS1688I Sparse attributes for 'file-name' cannot bebacked up correctly because the volumefrom which the file is backed up doesnot support sparse files.

Explanation: If the volume from which a file is backedup does not support sparse files, then the allocated

ranges for the sparse file cannot be backed up. This istrue even if a file has its sparse attribute set. Oneexample where this can occur is if a sparse file iscreated on a NAS volume, but the volume is backed upover CIFS, where CIFS does not support sparse files.

System action: The sparse attribute and allocatedranges for the file are not backed up. If the file isrestored, the restored file will not be sparse.

User response: No action is required if you do notneed the sparse attribute and allocated ranges backedup.If you require backup of the file's sparse attribute andallocated ranges, then the volume from which IBMTivoli Storage Manager backs up the file must supportsparse files.

ANS1689E The registry was not updated after VSSASR restore.

Explanation: An error occurred while updating theregistry after VSS Automated System Recovery (ASR).Check dsmerror.log for more information.



ANS1690E The list of volumes passed contain pairswhich belong to different consistencygroups in the scope of one singlecluster.

Explanation: TSM ACS handles for each operationonly one consistency group per cluster at the sametime. If the set of volumes in a backup or restoreoperation contain pairs that belong to differentconsistency group inside one single cluster, then theprocess of the operation will be stopped.

System action: Process stopped.

User response: If you added volumes to theproduction database or to the target set, ensure thatthey are not in any FlashCopy relation.

ANS1691I The option 'option' that was found in theoptions file 'file-name' at the linenumber: number is not supported andwill be ignored by the client.

Explanation: The specified option is valid but notsupported on the current platform and will be ignoredby the client.


User response: You can ignore the message or removethe option from the option file.



ANS1692E The certificate is not trusted.

Explanation: The client was unable to open SSLconnection to the server because the server certificatewas not trusted.


User response: Make sure that you have configuredthe key database for SSL communication as describedin the documentation. If the TSM server is using aself-signed certificate, make sure that you import thecorrect certificate from the server you are trying toconnect to. When the server is using a certificate signedby an authority, make sure that the root certificate ofthe authority is imported into the client key database.

ANS1693E The certificate validity period isincorrect.

Explanation: The client was unable to open an SSLconnection to the server because the certificate validityperiod is incorrect.


User response: Report this to the TSM serveradministrator. The server must have the correctcertificate installed.

ANS1694E The certificate identity could not beverified.

Explanation: TSM was unable to open an SSLconnection to the server because the certificate identitycould not be verified. This happens when the certificateownership information does not match the TSMdomain name or IP address.


User response: Make sure that the server domainname or the IP address (the value of theTCPSERVERADDRESS option) is correct. If the problempersists, report it to your TSM server administrator.

ANS1695E The certificate is not valid.

Explanation: TSM was unable to open an SSLconnection to the server because of an invalidcertificate. The client was unable to determine the exactcause of the failure.


User response: Further analysis of the servercertificate, the client key database, or both, is needed.Refer to TSM documentation for more information.

ANS1696E Only root can perform this action.

Explanation: User must be root to perform this action.


User response: Log in as root and try the operationagain.

ANS1700W Database 'database' (save date=date) wassuccessfully recovered.

Explanation: The specified database (which was savedon the specified date) was successfuly recovered.

System action: The specified database was recoveredwith the last saved version.

User response: none.

ANS1704W Option 'option-name' can not be suppliedby application and is ignored.

Explanation: An API application supplied option. Theoption cannot be specified by an application. Theoption can be specified only in the dsm.sys options file.

System action: The supplied option is ignored.Processing continues.

User response: Correct the application configuration.

ANS1705E System Writers writersname do not exist.

Explanation: These writers are an essential part of theoperating system. When they are not available thebackup will complete successfully but the data forthose writers will not get backed up to the IBM TivoliStorage Manager server. This can result in the computernot booting after a restore of the system state.

System action: System state backup stopped.

User response: Verify that these writers exist using'vssadmin list writers' command. Try the operationagain. If the problem persists, contact your systemadministrator or IBM Tivoli Storage Manageradministrator for further help.

ANS1706E Error creating directory ' directory'.

Explanation: The system was unable to create thespecified directory.


User response: Verify that the system has theappropriate permissions to create this directory, andthen restart the operation.



ANS1707E Hard link 'new-file-name' could not becreated for existing file 'exist-file-name'.Microsoft Windows return code:'windows-return-code' 'windows-error-text'

Explanation: Some system state files are hard linksthat point to another file. During system state restore,IBM Tivoli Storage Manager recreates the hard links forrestored system state files. If a file with the same nameas the hard link already exists at the time of the restore,IBM Tivoli Storage Manager attempts to replace the filewith the hard link.This message is issued when IBM Tivoli StorageManager is unable to replace an existing file with ahard link. The message includes the hard link name,the system state file name to which the hard link pointsand the Microsoft Windows return code information.The return code information indicates why the filecould not be replaced.It is possible for the operating system or applications tobehave erratically if the hard link cannot be recreated.

System action: The hard link is skipped, system staterestore continues.

User response: Use the Microsoft Windows returncode information provided in the message to determinethe underlying cause of the error. Based on theunderlying cause of the error and the reason you arerestoring the system state, you can choose to eithercorrect the underlying cause and perform the restoreagain, or you can attempt to manually create the hardlink. Because this error message represents an unusualand unexpected condition, you should give carefulconsideration to the potential consequences of eitherchoice.The hard link can be created manually as follows:Rename the file that has the same name as the hardlink. Then use the Microsoft Windows utility fsutil.exeas follows:FSUTIL HARDLINK CREATE hardlinknameoriginalfilename

ANS1708E Backup operation failed. Only a rootuser can do this operation.

Explanation: Backups initiated by non-root users aredisabled by IBM Tivoli Storage Manager administrator.


User response: Request the IBM Tivoli StorageManager administrator to enable non-root backups.

ANS1712I Changed block tracking not supportedfor disk disk name; Performing FULLbackup of disk.

Explanation: Changed block tracking is not enabled orsupported for the specified disk, so a full backup of thedisk will be performed.

System action: A full backup of the disk is performed.

User response: None

ANS1713W There was a problem getting changedblock tracking information for disk diskname; Performing FULL backup of disk.

Explanation: Changed block tracking is supported forthe specified disk, but there was a problem getting thechanged block tracking information, so a full backup ofthe disk will be performed.

System action: A full backup of the disk is performed.

User response: Review the error log for messages asto why the changed block tracking information couldnot be obtained.

ANS1714I No changed extents found for disk diskname - skipping disk.

Explanation: No changed extents were found for thespecified disk, so there is nothing to backup; The diskwill be skipped.

System action: No data is backed up for the specifieddisk so no data has changed.


ANS1715E A filespace already exists for virtualmachine (VM_name), but with a differentvirtual machine UUID (VM_UUID) thanthe current virtual machine UUID(VM_UUID).

Explanation: A virtual machine with this name wasbacked up, and it has a different virtual machine UUIDthan the virtual machine that is backed up now. Thiscan occur if there are two virtual machines with thesame name that are backed up to the same TSM datacenter node name. In this case, the backup can notcontinue because the backup-archive client uses thevirtual machine name to uniquely reference the virtualmachine on the TSM server.

This can also occur if the virtual machine UUIDchanged after a previous backup operation. This is thecase after the following events:

1. Virtual machine VM_1 backed up.

2. Virtual machine VM_1 is restored with a new name:VM_2. A new UUID is assigned to VM_2.

3. Virtual machine VM_1 is deleted.

4. Virtual machine VM_2 is renamed to VM_1.

System action: The backup of this virtual machinefails. The backup process can continue with othervirtual machines.

User response: If there are two or more virtualmachines with the same name in the data centerinventory, you can complete either of the followingactions:



v Rename the virtual machines so that all names in thedata center inventory are unique.

v Backup up virtual machines with the same name todifferent TSM servers.

If the VM's UUID changed, run a BACKUP VMcommand with VMBACKUPUPDATEGUID option. TheVMBACKUPUPDATEGUID option updates the UUIDon the TSM server.

ANS1716E A VMware vStorage web service tasktimed-out.

Explanation: The TSM client timed-out waiting forVMware vCenter or ESX host to complete a requestedweb service task. Resources could be low or the systemcould be busy.


User response: Please check the VMware vCenter orESX host for errors.

ANS1717E A VMware vStorage web service taskfailed.

Explanation: A VMware vCenter or ESX host webservice task failed.


User response: Please check the VMware vCenter orESX host for errors.

ANS1729E The passed file list 'file-list' is not a validinput file list.Pass standard file list or collection filelist to the dsmrecall command.

Explanation: User has passed a invalid file list type tothe dsmrecall command


User response: pass standard file list or collection filelist to dsmrecall command.

ANS1730E The IBM Tivoli Storage Manager serverquery for ordering information failed.

Explanation: Tape optimized recall was not able toretrieve ordering information from the IBM TivoliStorage Manager server.


User response: Check the connection to the IBM TivoliStorage Manager server to see if the IBM Tivoli StorageManager server is available and you have the correctaccess rights configured.

ANS1731E Tape optimized recall for file list 'file-list'failed with rc = code.

Explanation: Tape optimized recall was not able toretrieve ordering information from the IBM TivoliStorage Manager server.


User response: Check all error messages above thismessage to get details about the problem.

ANS1732W File 'file' is from a different file system.writing file to list of unprocessed files:'file-list'.

Explanation: The dsmrecall command specifies a filesystem to process. Files from other file systems areskipped and written into a unprocessed list.

System action: File is skipped and information iswritten to a list of unprocessed files

User response: Check that all files in the input file listare from the correct file system.

ANS1733I A collection file was specified 'file-list'The ordering process is skipped.

Explanation: A collection file was passed as the inputfile list. Ordering is not necessary since it the file isalready ordered. Only the recall is started.

System action: The ordering processed is not started,only recall started.

User response: No further action needed.

ANS1734W The virtual machine 'VM-name' containsone or more independent disks.Backups are not supported in thisconfiguration. Specify the'-vmprocessvmwithindependent=yes'option to exclude these disks from thebackup.

Explanation: Independent disks are not affected bysnapshots so the IBM Tivoli Storage Manager clientdoes not support backing them up.

System action: The virtual machine is not backed up.

User response: Turn off the virtual machine andchange the disk independent mode or remove themfrom the virtual machine. Or specify the'-vmprocessvmwithindependent=yes' option to excludethese disks from the backup.

ANS1735W The virtual machine 'VM-name' containsone or more physical Raw DeviceMappings (RDMs). Backups are notsupported in this configuration. Specifythe '-vmprocessvmwithprdm=yes' optionto exclude these disks from the backup.



Explanation: Physical RDMs are not included insnapshots so the TSM client does not support backingthem up.


User response: Turn off the virtual machine andchange the RDMs to virtual mode or remove themfrom the virtual machine. Or specify the'-vmprocessvmwithprdm=yes' option to exclude thesedisks from the backup.

ANS1737E The PRESNAPSHOTCMD commandfailed.

Explanation: The command specified by thePRESNAPSHOTCMD option must completesuccessfully in order to perform the VSS snapshotbackup. If the command completed with a return codeof 0 (zero), it is considered to have completedsuccessfully. If the command completed with any otherreturn code, it is considered to have failed. If thecommand failed then the VSS snapshot backup is notperformed.

System action: The client does not perform the VSSsnapshot backup operation.

User response: Identify and repair the problem thatcaused the command to fail. If a non-zero return codeis normal for this command, consider wrapping thecommand in a script that always exits with a returncode of zero.

ANS1738W The POSTSNAPSHOTCMD commandfailed.

Explanation: If the command specified by thePOSTSNAPSHOTCMD option completed with anon-zero return code, the VSS snapshot backupoperation continues. The operation continues with awarning-level result. The result of thePOSTSNAPSHOTCMD command does not supersede ahigher result from the VSS snapshot backup command.For example, if the VSS snapshot backup commandcompleted with code 12, a lower return code from thePOSTSNAPSHOTCMD command does not alter thereturn code.

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

User response: Identify and repair the problem thatcaused the command to fail. Consider wrapping thecommand in a script that always exits with a returncode of zero.

ANS1739E Restore of a system drive is notpermitted.

Explanation: The drive to which you are restoringcontains the operating system.


User response: Try the operation again withoutspecifying a system drive.

ANS1740W Unable to read ACLs for object:file_system path name. Check dsmerror.logfor more information.

Explanation: The ACLs of the object are not read.


User response: Examine the client error log foradditional messages that might indicate the reason forthe problem. Try to follow the suggested correctiveactions (if any) and try the operation again.

ANS1741W Unable to read extended attributes forfile_system path name. Check dsmerror.logfor more information.

Explanation: The extended attributes of the object arenot read.


User response: Examine the client error log foradditional messages that might indicate the reason forthe problem. Follow the suggested corrective actions (ifany) and try the operation again.

ANS1742E Expose Snapshot failed for backup'backup-name'.

Explanation: Expose snapshot failed.


User response: See the dsmerror.log file for furtherdetails.

ANS1743E Unexpose snapshot failed for backup'backup-name'.

Explanation: Unexpose snapshot failed.



ANS1744E One or more of the snapshots(volumes)needed for the restore operation werenot found. See dsmerror.log for furtherdetails.

Explanation: One or more of the snapshots needed forrestore were not found on the system.





ANS1745I The virtual machine to restore has oneor more distributed port groups. Furtherconfiguration might be necessary toselect a port number after the restore iscomplete.

Explanation: The virtual machine was saved with oneor more NIC cards backed by distributed port groups.Due to conflicts on restore the port number(s) were notsaved.

System action: The restore continues.

User response: Edit the virtual machine settings andselect a port if needed.

ANS1746E No available LUNs were found.Confirm that the storage adapters areconfigured correctly on the host and thatthe LUNs are not mapped to anothervirtual machine.

Explanation: The virtual machine was stored with aRaw Device Mappings disk backed by a LUN. Therequired LUN is missing or still mapped to anothervirtual machine.

System action: The virtual machine cannot berestored.

User response: Confirm that the Storage Adapters areconfigured correctly on the host and that the LUNs arenot mapped to another virtual machine.

ANS1747E Encryption key password is notavailable.

Explanation: The client is not enabled for encryptedbackup/restore operations by non-authorized users orthe encryption key password is not stored by theadministrator.

System action: Objects that cannot be encrypted ordecrypted are skipped.

User response: Contact the administrator for yoursystem to configure encrypted operations fornon-authorized users.

ANS1748E The virtual machine was stored with aRaw Device Mappings disk backed by aLUN. The required LUN is missing orstill mapped to another virtual machine:LUN UUID lun.

Explanation: The virtual machine was stored with aRaw Device Mappings disk backed by a LUN. Therequired LUN is missing or still mapped to anothervirtual machine.


User response: Find the required LUN and make it

available to the virtual machine.

ANS1749W Object 'filespace-namehl-namell-name' wasbacked up with invalid file system typeattribute.

Explanation: File system type is used by the client todetermine if an object name is case sensitive or not.Wrong file system type may result in incorrect sortorder of the server tree for case sensitive file systems.Finally some unchanged files may expire and thenre-backed up during full incremental backup.


User response: It is recommended to rename thecorrespondent filespace on TSM server and do the fullincremental backup again.

ANS1750I Volume mount point 'volumemountpoint'is mounted to volume 'volume'. Usingsnapshot volume for 'volume' to backup.

Explanation: The volume mount point resolved to avolume that has been snapped. The same snapshotvolume will be used.



ANS1751E Error processing 'filespace name': The filesystem can not be accessed.

Explanation: The client is unable to access the filesystem. Two common reasons for this are the accountunder which the client is running does not have accessto the root of the file system, or the file system doesnot exist.

System action: The inaccessible file system is skipped.Processing continues with the next file system.

User response: Check the error log for additionalmessages that might yield additional information aboutthe problem that prevents access to the file system.Correct the problem, then retry the operation. If theaccount does not have access to the file system, theneither the system administrator needs to grant access,or an account that has access to the file system must beused. If the file system does not exist, then remove orcorrect the file system specification.

ANS1752E The file system can not be accessed.

Explanation: The client is unable to access the filesystem. Two common reasons for this are the accountunder which the client is running does not have accessto the root of the file system, or the file system doesnot exist.

System action: The inaccessible file system is ignored.

User response: Check the error log for additional



messages that might yield additional information aboutthe problem that prevents access to the file system.Correct the problem, then retry the operation. If theaccount does not have access to the file system, theneither the system administrator needs to grant access,or an account that has access to the file system must beused. If the file system does not exist, then remove orcorrect the file system specification.

ANS1753E File space 'filespace name' was backed upby an older client version, and cannotbe restored with this client version. Thefile space will be skipped.

Explanation: The backup set format in earlier clientversions for SYSTEM STATE and SYSTEM SERVICES isincompatible with the current client version. Those filespaces will be skipped. The restore might appear topause while the client skips past the objects in thosefile spaces. Other remaining file space data will berestored.

System action: Objects in this file space are skipped.Other remaining file space data will be restored.

User response: Restore this specific file space in thebackupset with a prior level client.

ANS1754E File space 'filespace name' cannot berestored when ASNODENAME optionis in affect. The file space will beskipped.

Explanation: System state data of another node shouldnot be restored to a different node. Those file spaceswill be skipped. The restore might appear to pausewhile the client skips past the objects in those filespaces. Other remaining file space data will be restored.

System action: Objects in this file space are skipped.Other remaining file space data will be restored.

User response: Remove ASNODENAME option beforerestoring this specific file space in the backupset or usethe node name that was used to backup system statedata to restore.

ANS1755W An error communicating with ActiveDirectory has occured. USEDIRECTORYoption will be ignored and processingwill continue.

Explanation: TSM attempted to query ActiveDirectory for TSM Server parameters but an error hasoccured. This could be caused by Active Directory orthe TSM Server's setup.

System action: TSM will ignore the USEDIRECTORYoption and continue with client processing.

User response: Make sure your computer is properlyset up to the domain with Active Directory. Also, makesure your TSM Administrator has properly configuredthe TSM Server for your node.

ANS1756W The Journal for 'backup-specification' hasbeen reset: The server filespace wasdeleted since the last backup completed.

Explanation: The client has reset the journal becausethe corresponding server filespace was deleted sincethe last backup completed.

System action: The journal is reset, the current backupwon't use the journal, and the journal won't beavailable for backup until a full incremental backupsuccessfully completes.










ANS1759W The Journal for 'backup-specification' hasbeen reset: The policy set was updatedsince the last backup completed.

Explanation: The client has reset the journal for thespecified file system because the node policy set wasupdated since the last backup completed.





ANS1760I Journal for 'backup-specification' enabledfor node 'nodename' and server'servername'

Explanation: The journal for the specified file systemis now valid and will be used by the next fullincremental backup by the specified TSM node andserver.

System action: The next full incremental backup ofthe file system will use the journal.


ANS1761I Journal for 'backup-specification' will beenabled upon successful completion ofthe backup.

Explanation: An active but invalid journal is presentfor the file system being backed up. Once the backupsuccessfully completes the journal will available for useby the next full incremental backup of the file systemwith the same TSM node and server.



ANS1763W Unable to unmount snapshot mountpoint snapshot mountpoint during cleanupof snapshot 'snapshot' of volume 'volume'.Error is 'error'.Operation will continue. Pleasemanually unmount, remove thesnapshot mount point directory anddelete the snapshot after backup iscompleted.

Explanation: During the termination phase of TSMclient operation, it was not possible to unmount thesnapshot for some reason. However, TSM operationwas completed successfully.

System action: Processing continues, and the unmounterror is ignored.

User response: Please manually cleanup the snapshotsas follows:Query the snapshot: snapshot -q -c: <source FS>.Snapshot name will be of the format: tsmxxxxxxxxxx.Check if it is mounted: df -k | grep tsmxxxxxxxxxx.Unmount the snapshot: umount -f tsmxxxxxxxxxx.Remove snapshot mount point: rmdir tsmxxxxxxxxxx.Delete the snapshot: snapshot -d /dev/tsmxxxxxxxxxx.If snapshot delete fails with "Device Busy" or someother error, unmount the snapshot source filesystem:umount -f <source FS>.Retry snapshot delete: snapshot -d/dev/tsmxxxxxxxxxx.Check if any logical volumes are remaining: ls -l/dev/tsm*.Remove any remaining logical volumes: rmlv -ftsmxxxxxxxxxx.

Remount source file system, if previously unmounted:mount <source FS>.

ANS1764W Unable to remove the snapshot mountpoint directory snapshot mountpointduring cleanup of snapshot 'snapshot' ofvolume 'volume'.Error is 'error'.Operation will continue. Pleasemanually remove the snapshot mountdirectory and delete the snapshot afterbackup is completed.

Explanation: During the termination phase of TSMclient operation, it was not possible to remove themount point directory for the snapshot for somereason. However, TSM operation was completedsuccessfully.

System action: Processing continues, and the rmdirerror is ignored.

User response: Please manually cleanup the snapshotsas follows:Query the snapshot: snapshot -q -c: <source FS>.Snapshot name will be of the format: tsmxxxxxxxxxx.Check if it is mounted: df -k | grep tsmxxxxxxxxxx.Unmount the snapshot: umount -f tsmxxxxxxxxxx.Remove snapshot mount point: rmdir tsmxxxxxxxxxx.Delete the snapshot: snapshot -d /dev/tsmxxxxxxxxxx.If snapshot delete fails with "Device Busy" or someother error, unmount the snapshot source filesystem:umount -f <source FS>.Retry snapshot delete: snapshot -d/dev/tsmxxxxxxxxxx.Check if any logical volumes are remaining: ls -l/dev/tsm*.Remove any remaining logical volumes: rmlv -ftsmxxxxxxxxxx.Remount source file system, if previously unmounted:mount <source FS>.

ANS1765W Unable to delete the snapshot duringcleanup of snapshot 'snapshot' of volume'volume'.Error is 'error'.Operation will continue. Pleasemanually delete the snapshot afterbackup is completed.

Explanation: During TSM client operation, it was notpossible to delete the snapshot for some reason.However, TSM operation was completed successfully.One of the reasons that the snapshot delete failedmaybe due to the fact that AIX JFS2 expects thesnapshot delete requests for a given filesystem to beissued in the order of oldest snapshot first, next oldestsnapshot second and so on. If there are other processesusing older snapshots for the same filesystem, it failsthe delete request. Also, TSM only deletes snapshotsthat was created by one of its processes. It will notdelete older snapshots created by other applications or



users. In this case, the user will have to manuallydelete all the older snapshots so that the next TSMcommand can complete successfully.

System action: Processing continues, and the snapshotdelete error is ignored.


ANS1766W Unable to remove the snapshot logicalvolume during cleanup of snapshot'snapshot' of volume 'volume'.Error is 'error'.Operation will continue. Pleasemanually remove the snapshot logicalvolume after backup is completed.

Explanation: During the termination phase of TSMclient operation, it was not possible to remove thesnapshot logical volume for some reason. However,TSM operation was completed successfully.

System action: Processing continues, and the snapshotlogical volume remove error is ignored.


ANS1767E Unable to create a snapshot logicalvolume using command:'cmd'.Error is 'error'.Please ensure that the volume group hassufficient free partitions to fulfill theallocation request.

Explanation: During the initialization phase of TSMclient operation, it was not possible to create a logicalvolume for the snapshot.

System action: Processing continues, and the createsnapshot logical volume error is ignored. TSMoperation will be performed without the snapshot.

User response: Please ensure that the volume grouphas sufficient free partitions to fulfill the mklvallocation reuest and retry the operation.

ANS1768E TSM was unable to find space for a newsnapshot.TSM function name : function-nameTSM function : function-descTSM return code : TSM-rcTSM file : file-name (line-number)

Explanation: None.


User response: Previous backups may still bepending. If problem persists contact the TSMadministrator with the information provided in thismessage.

ANS1769E NetApp file server 'server-name' at DataONTAP version'version.modification.submodification' is notsupported for performing incrementalbackups using snapshot difference.

Explanation: Incremental backup using Snapshotdifference requires Data ONTAP V7.3 or later. However,if you are upgrading from Data ONTAP V7.3.3 or laterto V8.0, you will lose snapshot difference support forunicode file names. Upgrade to Data ONTAP V8.1 orlater.


User response: Upgrade the file server to a supportedlevel of Data ONTAP, then retry the operation.

ANS1770E Unable to resolve address 'tcpip address'.Error = error code, 'error message'

Explanation: The system was not able to get theTCP/IP v6 address.


User response: Verify the address shown is a TCP/IPv6 address and can be resolved with ping or ping6.



ANS1771W The system state filespace 'filespace name'cannot be restored to a differentlocation.

Explanation: The system state file space cannot berestored to a different location. This file space isskipped.

System action: Objects in the system state file spaceare skipped. Other remaining file spaces are restored.The restore might appear to pause while the clientskips past the objects in this file space.

User response: Restore system state to its originallocation.

ANS1772E Error loading the snapshot plugin. Theplugin might not be installed.

Explanation: The snapshot plugin could not beloaded, possibly because the plugin is not installed.

System action: The snapshot backup is stopped.

User response: On Linux 86/86_64 platform, installthe TIVsm-BAhdw package if it is not already installed.Try the operation again. On AIX platform, install thehdw and snphdw filesets if they are not alreadyinstalled. Try the operation again.

ANS1773W The virtual machine 'VM-name' containsone or more independent disks andthese disks are excluded from the VMbackup.

Explanation: You cannot perform a shapshot ofindependent disks. Specify the option'-vmprocessvmwithindependent=yes' to skip thesedisks.

System action: The virtual machine independent diskswill not be backed up.


ANS1774W The virtual machine 'VM-name' containsone or more physical Raw DeviceMappings (RDM) disks and these disksare excluded from the VM backup.

Explanation: You cannot perform a shapshot ofphysical RDM disks. Specify the option'-vmprocessvmwithprdm=yes' to skip these disks.

System action: The virtual machine physical RDMdisks are not backed up.


ANS1780E writer-name failed to initialize andsubscribe to VSS.

Explanation: IBM Tivoli Storage Manager encounteredan error while creating writer-name under control of theWindows Volume Shadow Copy Service (VSS).Examine the IBM Tivoli Storage Manager error log andApplications Event Log for additional informationabout this error.


User response: Try the operation again. If the errorpersists, examine the IBM Tivoli Storage Manager errorlog and Windows event log for information related tothis error.

Restart the Windows Volume Shadow Copy Service(VSS), and try the operation again.

In some cases, it is necessary to restart the machine toclear the VSS error state.

ANS1782E writer-name failed to be stopped.

Explanation: IBM Tivoli Storage Manager encounteredan error while stopping writer-name. Examine the IBMTivoli Storage Manager error log and ApplicationsEvent Log for additional information about this error.


User response: Try the operation again. If the errorpersists, examine the IBM Tivoli Storage Manager errorlog and Windows event log for information related tothis error.

Restart the Windows Volume Shadow Copy Service(VSS), then try the operation again.

In some cases, it is necessary to retart the machine toclear the VSS error state.

ANS1784E Incremental by snapshot differencecannot be performed on 'volume-name' asit is a vFiler volume.

Explanation: Snapshot difference incremental backupis not supported on vFiler volumes.


User response: Perform snapshot differenceincremental backup on normal NetApp/N-Seriesvolumes only.

ANS1787I The virtual machine NIC is backed by adistributed virtual port group but it ismissing the portgroupKey attribute, TheNIC cannot be restored.

Explanation: The virtual machine NIC is missing therequired portgroupKey attribute.

System action: The virtual machine can be restoredbut the NIC cannot be restored.



User response: After the virtual machine has beenrestored a new NIC card can be added.

ANS1788I The target ESX host is missing therequired distributed virtual port group,the virtual machine NIC cannot berestored. UseVMDEFAULTDVPORTGROUP optionto set to specify new port group. Iftarget ESXi server does not have anyport groups, useVMDEFAULTNETWORK option.

Explanation: The virtual machine NIC was backed bya distributed virtual port group but the target ESX hostis missing this port group.



ANS1789I No Ddistributed virtual port group werefound on the target ESX host. Thevirtual machine NIC cannot be restored.

Explanation: The virtual machine NIC was backed bya distributed virtual port group but the target ESX hosthas no port group available.



ANS1790E Volume 'volname' cannot be backed upbecause 'nosnapdir=on' is set on thefiler.

Explanation: This message is issued when option'nosnapdir=on' is in set for the volume indicated in themessage. When this option is set, the volume snapshotsare hidden and thus cannot be backed up.

System action: The volume indicated in the messageis not backed up. Processing continues with the nextvolume.

User response: To back up the volume, change thevolume on the filer: Set option 'nosnapdir=off'. Then trythe backup operation for this volume again.If the volume is not backed up, remove it from thebackup-archive client DOMAIN setting.

ANS1794I The option 'cifs.enable_share_browsing= off' is set on the filer 'filerName'.

Explanation: This message is issued when the option'cifs.enable_share_browsing = off' is set on the NASfiler indicated in the message.


User response: Set option 'cifs.enable_share_browsing= on'. Then try the snapshot difference backupoperation again.

ANS1795I Operation will continue without usingsnapshot provider, because file system'volname' does not have writepermissions.

Explanation: The source file system for a snapshotshould be read-write as by definition a snapshot is apoint-in-time snapshot of changing file system.Snapshot creation updates the file system superblockwhich requires the file system to be read-write

System action: Processing continues without usingsnapshot provider.

User response: If the volume needs to be backed upvia snapshot provider, change its permissions toread-write.

ANS1796I The short name for 'fullpath-name' couldnot be set to original short name'file-name': Windows function 'func-name'failed with return code return-code,reason: 'error text'

Explanation: The client cannot set the short name forthe specified object. This is usually because the shortname is already in use by another object located in thesame directory. Another possible reason is that theaccount under which the client is running does nothave the SE_RESTORE_NAME privilege.

System action: The short name for the specified objectis not set. The object will retain the default short name.Otherwise processing continues.

User response: This message is informational and canbe safely ignored. If you require that the object berestored with its original short name, you will need tomove or delete the conflicting object. From anoperating system command prompt, change to thedirectory that contains the object you want to restore.Then use the \"dir /x\" command to identify theconflicting object. Also make sure that you have theSE_RESTORE_NAME privilege. If you need assistance,see your system administrator. After the conflict hasbeen resolved, try to restore the file again.

ANS1797E Function function-name received anunexpected error from the Microsoft APIMS-function-name: rc=error whileattempting to access the object'object-name'. Error occurred in filefile-name (line-number).

Explanation: An error occurred while processing theobject. The error code indicates the reason for thefailure. This information can be used to diagnose theproblem.



System action: The TSM client may or may not failthe operation, depending on the code.


ANS1798W An error occurred while accessingencrypted data of the object 'object-name',skipping object. Windows system errorcode error, reason 'error-reason'

Explanation: An error occurred while processingencrypted data of the object. The error informationcaptured indicates the reason for the failure. Thisinformation can be used to diagnose the problem.



ANS1799I The last access date for 'fullpath-name'could not be reset because the file isread-only.

Explanation: Option PRESERVELASTACCESSDATEYES is in effect, but the TSM client was unable to resetthe last access date for the specified file because thefile's "read only" attribute is enabled. The client cannotreset the last access date for "read only" files.

System action: The last access date for the specifiedfile is not reset. Otherwise processing continues.

User response: This message is informational and canbe safely ignored. You might want to turn off the "readonly" attribute for the file so that subsequent backupscan reset the last access date. Before turning off theattribute, you should verify that doing so will notimpact the integrity of the file or the applications thatuse the file. You should also make sure that turning offthe attribute will not conflict with the file managementpolicies of your organization.

ANS1800W The last access date for 'fullpath-name'could not be reset: function 'func-name'failed with return code return-code

Explanation: Option PRESERVELASTACCESSDATEYES is in effect, but the TSM client was unable to resetthe last access date for the specified file. The messageincludes the name of the function that failed and thereturn code from that function.

System action: The last access date for the specifiedfile is not reset. Otherwise processing continues.

User response: If the problem is reproducible, obtain aSERVICE trace that captures an instance of thisproblem. Run the QUERY SYSTEMINFO command andcollect the dsminfo.txt file. Contact IBM support andreport the exact text of this error message. Be sure toprovide support with the dsminfo.txt and dsmerror.logfiles and (if available) the SERVICE trace.

ANS1801E Unable to register the new ID withserver.

Explanation: The reasons of this problem can be lackof client system memory or server protocol error. TheTSM activity log might contain a corresponding errormessage with further information about the cause.

System action: The new ID is not registered with theserver.

User response: Please check your network connectionand try again after time. If the error appears again,please contact your client machine administrator.

ANS1802E Incremental backup of 'file-name'finished with failCount failure(s)

Explanation: This message is issued after completionof an incremental backup operation for the named filespecification when one or more objects in that filespecification could not be backed up.


User response: Examine the client error log foradditional messages that indicate the reasons that eachfailed object could not be backed up. Take anycorrective action as suggested by the messages.

ANS1803E Archive processing of 'file-space name'finished with failures.

Explanation: This message is issued after completionof an archive operation for the named file specificationwhen one or more objects in that file specificationcould not be archived.


User response: Examine the client error log foradditional messages that indicate the reasons that eachfailed object could not be archived. Take correctiveaction as suggested by the messages.

ANS1804E Selective Backup processing of 'file-spacename' finished with failures.

Explanation: This message is issued after completionof a selective backup operation for the named filespecification when one or more objects in that filespecification could not be backed up.


User response: Examine the client error log foradditional messages that indicate the reasons that eachfailed object could not be backed up. Take anycorrective action suggested by those messages.



ANS1805E Unable to restore symbolic link'file-name'.

Explanation: The client operating system is not able tocreate a symbolic link because the link points to afilename that is not given.


User response: Try the restore on a different operatingsystem.

ANS1806W Size exceeded the maximum file sizelimit on your systemfor 'filespace namepath-namefile-name' of'file-size'.

Explanation: You tried to restore or retrieve a file thathas exceeded the maximum file size limitation on yoursystem.

System action: TSM cannot restore or retrieve the file.

User response: Restore or retrieve this file on a systemthat supports the file size. See your systemadministrator.

ANS1807E Unable to recall file from server due toerror from recall daemon.

Explanation: Unable to recall file. The recall daemonreported an error while trying to recall a file. Look inthe recall daemon’s error log for more information. Thiscan happen if the server is down, the connection isbroken, or the file is missing on the server. It is alsopossible that the migration server in the system optionfile has been changed to a different server. The recalldaemon does not check the system option file forchanges once it has started.


User response: See if the server is up, and retry. If theproblem still exists, look in the error log. Also have theworkstation administrator run dsmreconcile against thefile system and see if the file shows up in the.SpaceMan/orphan.stubs file. If system option file hasbeen changed, stop all recall daemons and restart themaster recall daemon to pick up the changes.

ANS1808E The Logical Volume Snapshot Agent isnot at the correct level. It is possiblethat the Client was upgraded to a newerlevel but the LVSA driver was notupdated at the same time. Use the SetupWizard to configure either Online Imageor Open File support and choose Updatethe Logical Volume Snapshot Agent.

Explanation: The selected operation requires thecurrent level of the Logical Volume Snapshot Agent.Use the Setup Wizard to update the LVSA.

System action: The selected operation is notperformed.

User response: Retry the operation after updating theLogical Volume Snapshot Agent.

ANS1809W A session with the TSM server has beendisconnected. An attempt will be madeto reestablish the connection.

Explanation: This message is issued after the sessionwith the TSM server is unexpectedly lost. Somepossible reasons that this message might be issued:- There is a problem with the network.- The TSM server was shut down.- The TSM server administrator cancelled the clientsession.

System action: The client will try to reestablish aconnection with the server. If the TSM serveradministrator cancelled the session, then the attempt toreestablish the connection will fail and messageANS1369E will be issued. If the attempt to reestablishthe connection is successful, then processing willcontinue. If the attempt to reestablish the connectionfails, then the client will continue to try to reestablish aconnection according to theCOMMRESTARTDURATION andCOMMRESTARTINTERVAL client option settings.

User response: If the session was cancelled by theTSM server administrator and you do not know why,or if the client is unable to reestablish a session withthe TSM server, then contact your TSM serveradministrator for further information. Frequentoccurrences of the ANS1809W message can indicate aproblem with the network. If this message is repeatedlyfound in the dsmerror.log, investigate possiblenetworking trouble, such as a failing network interfacecard or router problem. One common problem is themedia speed of the network adaptors: If the networkadaptors are set to "auto-negotiate", try changing themto "100%% full duplex". If the problem persists, then asa temporary measure ask your TSM serveradministrator increase the COMMTIMEOUT andIDLETIMEOUT option settings on the TSM server. Thismight reduce the frequency of this message.

ANS1810I A session with the TSM server has beenreestablished.

Explanation: The session with the server has beenreestablished after a connection failure. This message isusually preceded by message ANS1809W.

System action: Processing will continue.

User response: None. This message is informationalonly.



ANS1811S TSM session could not be reestablished.

Explanation: The session with the server has beenlost. Attempts to reestablish the session wereunsuccessful. Possible causes include, but are notlimited to the following:

v The server has been halted.

v The network connection to the server is down.

v The communication program that TSM is interactingwith has encountered some problem.

System action: Processing is stopped.

User response: Check network connection to theserver. Insure that the TSM server is running. Insurethat the communication program underlying TSM isworking properly.

ANS1813E Image Backup processing of'filespace-name' finished with failures.

Explanation: The image backup operation failed. Thismessage is usually preceded by other messagesindicating the nature of the failure.

System action: The failing file space is skipped andprocessing continues.

User response: Examine the messages preceding thismessage and the TSM Client error log for more specificindications about the problem. A common cause is thata tape could not be mounted on the TSM server,perhaps due to an insufficient number of mount points.If there is a problem with the server, contact yourSystem Administrator for further assistance.

ANS1814E Unable to start the scheduled event'event-name'

Explanation: The scheduled event is no longer validon the server. Either the window has elapsed or theschedule has been deleted.

System action: The client scheduler queries the serverto obtain the next scheduled event.

User response: If the problem continues, contact yoursystem administrator to correct the problem on theserver.

ANS1815E Either the window has elapsed or theschedule has been deleted

Explanation: Scheduled event was no longer valid onthe server.

System action: The client scheduler queries the serverto obtain the next scheduled event.

User response: If the problem continues, see yoursystem administrator to correct the problem on theserver.

ANS1816E Invalid scheduling mode

Explanation: The mode entered for the scheduledevent was not correct.

System action: Event does not occur.

User response: Enter the correct scheduling mode andretry the operation.

ANS1817E Schedule function can only be run by aTSM authorized user.

Explanation: An attempt to use the schedule functionfailed because of improper authority.


User response: See the TSM authorized user forschedule function information.

ANS1818E The SCHEDULE command is notallowed in LOOP (interactive) mode.

Explanation: The SCHEDULE command may only begiven on the inital command line. Enter the HELPSCHED command for a complete description of theSCHEDULE command.

System action: The client does not execute anyscheduled events.

User response: Start the scheduler from the OSprompt. For example:dsmc scheduleWindows clients can also use the client schedulerservice. Read the client manual for information on howto use the SCHEDULE command and how to use theTSM client scheduler features.

ANS1819E The TSM server was unable to registerthe address for this node.

Explanation: This is a rare situation, and is usually anindication of a problem with the TSM server.


User response: Check the error log for any othermessages that might indicate a reason for the failure.Ask your TSM server administrator to check the TSMserver activity log for any messages that might indicatea problem on the server. Try to correct any indicatedproblems, then try the operation again. If the problempersists, contact IBM technical support for furtherassistance.

ANS1820E Command line options must bepreceded by a '-'

Explanation: An option was specified without a '–'delimiter.




User response: Enter the command again with a dashpreceding each option.

ANS1821E Unable to start POSTSCHEDULECMD/PRESCHEDULECMD 'command'

Explanation: The requested action required a newprocess to be created. Either an option or a schedule“action” that requested an operating system commandto be executed was entered.

System action: Request is ignored.

User response: Remove the request from the optionsfile or the schedule defined on the server.

ANS1822E Too many objects were selected forrestore. Please select less thanmax_objects objects

Explanation: The restore cannot be performed,because too many objects were selected.

System action: The restore is not performed.

User response: Retry the operation after reducing thenumber of objects selected.

ANS1823E The TESTFLAGS or TRACEFLAGSoption specifies unknown flag name'keyword' or the value supplied is invalidfor the named keyword.

Explanation: Either the testflag or traceflag name isincorrectly spelled, or the value supplied for that flag isnot valid.

System action: If the TESTFLAGS or TRACEFLAGSoption was specified in the client options file or on thecommand line during client initialization, the the clientprogram does not start. If the option was specifiedfrom the command line client while running in LOOP(interactive) mode, then the operation does not run.

User response: Correct the TESTFLAGS orTRACEFLAGS flag name or correct the value specifiedfor the TESTFLAG keyword shown in the message.These options are typically used at the direction of IBMtechnical support or as specified in the TSM ProblemDetermination Guide. If you are not sure which flagnames to use, review the TSM Problem DeterminationGuide for additional information or contact IBMtechnical support for further assistance.

ANS1824E Invalid trace file name (name too long).

Explanation: A TRACEFILE option in the preferencesfiles used a file name that is too long.

System action: Client program did not initialize.

User response: Change the file name used as theTRACEFILE so that it is equal to or less than 255characters in length.

ANS1827W Directories cannot be selected with thetable of contents currently loaded on theserver.

Explanation: The table of contents that is currentlyloaded on the server for this volume does not containobjects corresponding to the one and only point-in-timebackup. It contains an incomplete point in time ormultiple points in time.

System action: The directory is not selected forrestore.

User response: To be able to select an entire directoryfor restore, select "Use Latest" or "Use Point in Time"from the Point in Time dialog.

ANS1828E Screen size is too small for using thePICK option.

Explanation: You cannot use the PICK option on aworkstation that has a screen smaller than 20 charactersacross and 10 lines down.

System action: TSM did not complete the operation.

User response: Retry the operation using aworkstation that has a screen with the minimum size,or do not use the PICK option.

ANS1831E Password expired. The administrator forthis system must run TSM to update thepassword.

Explanation: The password expired.


User response: The administrator for this system mustupdate the password.

ANS1832W The option 'option' is no longersupported and will be ignored by TSMclient in this release.

Explanation: The specified option is in the process ofbeing made obsolete and will be ignored by the clientin this release. This option will be removed in the nextrelease and will no longer be valid.


User response: Remove the option from the optionfile. Also check the documentation to see if this optionhas been replaced by a newer option.

ANS1834S Unable to write to 'file-name' for storingpassword

Explanation: TSM cannot write to the specifiedfile-name.


User response: Check access permissions and disk



space. If unsuccessful, see your system administrator.

ANS1835E PASSWORDACCESS is GENERATE,but password needed for server'server-name'.Either the password is not stored locally,or it was changed at the server.

Explanation: Either the password is not stored locally,or it was changed at the server.

System action: TSM prompts you for the password ifTSM is running in the foreground.

User response: If TSM was running as a backgroundprocess, issue any TSM command from the foreground.Enter the password in answer to the prompt. Then tryyour background TSM command again.

ANS1836I Unable to process Processor Value Unithardware scan info file 'file name', errno,cause.

Explanation: The internal-use data file was notreadable.

System action: Processor Value Unit information isnot sent to the IBM Tivoli Storage Manager server.Processing continues.

User response: No response is necessary. This doesnot affect regular processing. Correct any file accesspermission issues and try the command again. If thefile exists, delete the file and try the command again.

ANS1837S File space filespace-name is ignored.Processing continues.

Explanation: The specified filespace-name in the systemoptions file is invalid.


User response: Check the file space in the systemoptions file and use a valid file space. Retry theoperation.

ANS1838E An error occurred while openinguser-specified options file 'filespace-name'.

Explanation: The specified options file could not belocated or opened.

System action: TSM attempts to open the defaultoptions file.

User response: Ensure that the specified options fileexists and is valid.

ANS1839E Cannot read password.

Explanation: An error occurred in setting up the inputfile (for example, the terminal) to be read.


User response: Check the attributes of the terminal.

ANS1852E Server could not load the table ofcontents. Status: status reason: reason

Explanation: A failure occurred when the serverattempted to load a file-level Table of contents for anNDMP volume. No file-level queries can be performedagainst the volume until the problem is solved.

System action: The table of contents is not loaded.

User response: Check the server Activity Log todetermine the cause of failure. Retry the operation aftercorrecting the problem.

ANS1853E Server could not load the Table ofContents. Status: status

Explanation: A failure occurred when the serverattempted to load a file-level Table of contents for anNDMP volume. No file-level queries can be performedagainst the volume until the problem is solved.

System action: The table of contents is not loaded.

User response: Check the server Activity Log todetermine the cause of failure. Retry the operation aftercorrecting the problem.

ANS1862W No table of contents information isavailable on the server for this volume.

Explanation: No objects for the selected volume existon the server that were backed up with table ofcontents information. Consequently no file-level queriescan be performed against the volume.

System action: none

User response: If file-level information is desired, useTOC option during backup.

ANS1865E Session rejected: Named Pipesconnection failure.

Explanation: An attempt to connect to the serverusing Named Pipes communications failed. This mighthave occurred if an incorrect NAMEDPIPENAME wasspecified in the options files or if your systemadministrator canceled a backup operation.


User response: Retry the operation, or wait until theserver comes back up and retry the operation. Ensurethat the value specified on the NAMEDPIPENAMEoption is the same as the one used by the server. If the



problem continues, contact your system administratorfor further help.

ANS1867E The server generated a CRC for verbtype CRC verb which does not match thereceived verb verb received.

Explanation: A cyclic redundancy check (CRC) failedbetween TSM client and server communication.

System action: The current object is skipped.Processing continues with the next object.

User response: This is an unusual condition, andcould indicate a communications problem between theTSM client and server. Try the operation again. If theproblem persists, contact IBM for further assistance.

ANS1871W The server CRC version is server CRCversion which does not match the clientversion client CRC version.

Explanation: This is a rare situation. The server andclient are using different versions of cyclic redundancycheck (CRC) algorithms.

System action: Processing continues without CRCchecking.

User response: Clients can be no more than oneversion downlevel from the TSM server. Make sure theclient and server are at compatible levels. Thecommand line client displays both client and serverversions when the client starts and connects to theserver. The QUERY SESSION command will alsodisplay the server version. From the GUI, use the\"Help/About\" menu item to identify the clientversion, and the \"File/Connection Information\"menu item to identify the server version. If the clientand server versions are incompatible, then the TSMserver administrator can turn off CRC checking foryour node.

ANS1873E An unknown error occurred whileprocessing system object 'sys-obj-name':utility function 'func-name' failed witherror error

Explanation: An unknown error occurred whileprocessing a system object. The error informationcaptured indicates the reason for the failure. Thisinformation can be used to diagnose the problem.



ANS1877E The parsed string is too long for TSM toprocess and has been truncated toprevent a buffer overflow.

Explanation: This is a rare condition. A very long

string would have to be entered by the user in acommand line, dsm.opt file, or filelist. This stringexceeds the maximum input string size of 1024 bytes.

System action: TSM truncated the string to themaximum possible length of 1024, then continued withthe operation. The operation may fail later due to thistruncation.

User response: Check the client error log for othermessages that might have been logged after thismessage was written, and take any corrective actionsuggested by those messages. If the problem persists,contact IBM support for further assistance.

ANS1878E An unknown error occurred whileprocessing system object 'sys-obj-name':Service 'service-name' and its dependentservices could not be stopped.

Explanation: An unknown error occurred whileprocessing a system object. The service listed in themessage and all of its dependent services could not bestopped. Processing cannot complete until the service isstopped.


User response: Manually stop the service and retrythe operation.

ANS1882E Unable to stop service 'service-name';error error

Explanation: The service could not be stopped by theprogram.


User response: Manually stop the service and retrythe operation.

ANS1891W SUBDIR is not a valid option whenusing FILELIST, SUBDIR will beignored.

Explanation: When Specifying FILELIST each entry isa single object and so SUBDIR will not apply.

System action: The option SUBDIR is ignored.

User response: You may have either a -FILELIST orSUBDIR on this command, but not both.

ANS1892W Expire command is not allowed on theTSM journaled filespace 'filespace'.

Explanation: You cannot expire files from the serveron a TSM journaled filespace.

System action: The expire command will not work onthis filespec

User response: If you want to expire this filepecremove it from the local filesystem.



ANS1895I Highest macro return code was returncode value.

Explanation: This message is issued after allcommands in a client macro have completed. Thereturn code represents the highest return code that wasissued during processing of the macro. In order ofincreasing severity, the return code meanings are:

0 - The command completed successfully

4 - One or more files were skipped

8 - One or more warning messages were issued

12 - One or more error messages (except for skippedfiles) were issued


User response: For return codes other than 0, the usermay wish to verify the results of the client operation(s)and take diagnostic and repair actions, as necessary.

ANS1898I ***** Processed count files *****

Explanation: TSM has processed the specified numberof files.



ANS1899I ***** Examined count files *****

Explanation: TSM has examined the specified numberof files.



ANS1900I Return code is return code value.

Explanation: The return code has been issued for thepreceding client command. In order of increasingseverity, the return code meanings are:





The return code indicates the highest severity messagethat was issued during execution of the clientcommand.For a scheduled event, the event will be consideredsuccessful if the return code is 0, 4, or 8. The event willbe considered to have failed if the return code is 12.


User response: For return codes other than 0, the usermay wish to verify the results of the client operationand take diagnostic and repair actions, as necessary.

ANS1901I Highest return code was return codevalue.

Explanation: This message indicates the highest returncode of all the client commands that were executed. Inorder of increasing severity, the return code meaningsare:






User response: For return codes other than 0, the usermay wish to verify the results of the client operation(s)and take diagnostic and repair actions, as necessary.

ANS1902E The PRESCHEDULECMD commandfailed. The scheduled event will not beexecuted.

Explanation: The command specified by thePRESCHEDULECMD option must completesuccessfully in order to execute the scheduled event. Ifthe command completed with a return code of 0 (zero),it is considered to have completed successfully. If thecommand completed with any other return code, it isconsidered to have failed. If the command failed thenthe scheduled event is not executed.

System action: The client does not execute thescheduled event, and the result code of the scheduledevent will be 12.

User response: Identify and repair the problem thatcaused the command to fail. If it is not necessary forthe command to complete before starting the scheduledevent, then consider using the PRENSCHEDULECMDoption, which does not require that the commandcomplete successfully. If a non-zero return code isnormal for this command, then consider wrapping thecommand in a script that always exits with a returncode of zero.

ANS1903W The POSTSCHEDULECMD commandfailed.

Explanation: If the command specified by thePOSTSCHEDULECMD option completed with anon-zero return code, then the scheduled event isconsidered to have completed successfully, but with awarning-level result. Note that the result of thePOSTSCHEDULECMD command will not supercede ahigher result from the scheduled client command. Forexample, if the scheduled client command completedwith a return code of 12, the scheduled event will beconsidered to have completed with a return code of 12,regardless of the outcome of the POSTSCHEDULECMDcommand.



System action: At a minimum, the result code of thescheduled event is 8.

User response: Identify and repair the problem thatcaused the command to fail. If it is not necessary forthe command to complete before posting the result ofthe scheduled event, then consider using thePOSTNSCHEDULECMD option. If a non-zero returncode is normal for this command, then considerwrapping the command in a script that always exitswith a return code of zero.

ANS1904E The archive description may not containany wildcard characterslike '?' or '*'.

Explanation: Descriptions for archive files must notcontain wildcard characters.


User response: Enter an archive description that doesnot contain wildcard characters.

ANS1906I Destination must be specified for thisoperation when using FROMNODE.

Explanation: You must specify a destination with aRestore/Retrieve command when using FROMNODEprocessing.


User response: Retry the Restore/Retrieve commandwith a destination specified.

For example, with the Windows backup-archive client:

restore -fromnode=cougar \\cougar\d$\projx\*d:\projx\

Or, with the UNIX and Linux backup-archive clients:

restore -fromn=node1 -fromo=ann "/home/proj/*"/home/gillis/

ANS1907E An error occurred while trying toperform an object merge operation onthe server.

Explanation: For NetWare clients: The TSM server isunable to perform a NetWare long name conversion.For Unix or Windows image backup: The group usedto store associated image components could not beclosed.


User response: For NetWare: It is possible that a morecurrent level of the TSM server can perform theconversion. Contact your TSM server administrator forassistance.For Unix or Windows: This error indicates anauthorization problem. Contact your TSM serveradministrator for assistance.If the problem still cannot be resolved, contact IBM

technical support for further assistance.

ANS1908I The scheduled command completedsuccessfully.

Explanation: The scheduled command completed withreturn code of zero, which is interpreted as success.

System action: The scheduled event is successful. Theresult code for the event is 0.


ANS1909E The scheduled command failed.

Explanation: The scheduled command completed witha non-zero return code, which is interpreted as failure.

System action: The scheduled event is failed. Theresult code for the event is 12.


ANS1912E An invalid registry hive was specified.

Explanation: The specified registry hive is invalid.



ANS1913E An invalid registry subkey wasspecified.

Explanation: The specified registry subkey is invalid.



ANS1914E The specified subkey isn't valid for thespecified hive.

Explanation: The specified registry subkey is invalidfor the specified registry hive.



ANS1915E Too many arguments specified for theBACKUP REGISTRY command.

Explanation: Too many arguments were specified forthe BACKUP REGISTRY command.





ANS1916E Too many arguments specified for theRESTORE REGISTRY command.

Explanation: Too many arguments were specified forthe RESTORE REGISTRY command.



ANS1917E Too few arguments specified for theBACKUP REGISTRY command.

Explanation: Too few arguments were specified forthe BACKUP REGISTRY command.



ANS1918E Too few arguments specified for theRESTORE REGISTRY command.

Explanation: Too few arguments were specified forthe RESTORE REGISTRY command.



ANS1919E The specified eventlog is not valid.

Explanation: The specified eventlog is not valid.



ANS1920E Too many arguments specified for theBACKUP EVENTLOG command.

Explanation: Too many arguments were specified forthe BACKUP EVENTLOG command.



ANS1921E Too many arguments specified for theRESTORE EVENTLOG command.

Explanation: Too many arguments were specified forthe RESTORE EVENTLOG command.



ANS1922E Too few arguments specified for theBACKUP EVENTLOG command.

Explanation: Too few arguments were specified forthe BACKUP EVENTLOG command.



ANS1923E Too few arguments specified for theRESTORE EVENTLOG command.

Explanation: Too few arguments were specified forthe RESTORE EVENTLOG command.



ANS1924E The specified system object is not valid.

Explanation: The specified system object is not valid.



ANS1925E The specified system object type is notvalid.

Explanation: The specified system object type is notvalid.



ANS1926E The specified system object type is onlyvalid on Windows NT.

Explanation: The specified system object type is onlyvalid on Windows NT.



ANS1928E Server-initiated sessions are notavailable in the LAN-free mode.

Explanation: Conflicting optionsSESSIONINIT=serveronly and ENABLELANFREE=yeswere specified. This combination is not allowed.


User response: Use client-initiated sessions or disableLAN-free.



ANS1929E An error occurred saving the registrykey.

Explanation: The active registry key cannot be copiedto the ADSM.SYS staging directory.

System action: The registry backup operation stops.

User response: Check the space available on theWindows boot partition to ensure there is room tocontain a copy of the Windows registry. This mightrequire several megabytes of free space. Also check theWindows permissions on the ADSM.SYS stagingdirectory and ensure that the Windows user which youare using to run TSM has full access to that directoryand its contents.

ANS1930W TSM Express client view not supportedwith a TSM Enterprise server.CLIENTVIEW option ignored.

Explanation: The TSM Express client view is onlysupported when going to a TSM Express server. Whena TSM Express client connects to a TSM Enterpriseserver, the CLIENTVIEW option is ignored, and theTSM Standard client view is displayed instead.

System action: The CLIENTVIEW option is ignoredand the TSM Enterprise client view is displayed.

User response: If you intend to use the TSMEnterprise server, then update your CLIENTVIEWoption to a value of STANDARD. Otherwise, updateyour TCPSERVERADDRESS option to point to yourTSM Express server.

ANS1931E An error saving one or more eventlogs.

Explanation: An error occurred saving one or moreeventlogs.



ANS1932E An error occurred replacing one or moreregistry keys.

Explanation: The registry key or keys being replacedare exclusively held by another process. The registrykeys were previously restored but the system was notrestarted.


User response: This error occurs because the registrykey or keys being replaced are exclusively held byanother process. This can happen if the registry keyswere previously restored but the system was notrebooted. Reboot the system and attempt the restoreoperation again.

ANS1933E Error accessing file or device 'name'.

Explanation: An error has occurred while accessingthe file or device.

System action: Backup set operation is not completed.

User response: Verify that the file or device exists andis accessible.

ANS1934E Backup set 'name' not found.

Explanation: The backup set name was not found onthe server.

System action: The backup set operation is notprocessed.

User response: Verify that the backup set name iscorrect.

ANS1935E Too many arguments specified for theBACKUP NTDS command.

Explanation: Too many arguments were specified forthe BACKUP NTDS command.



ANS1936E Not enough arguments specified for theBACKUP NTDS command.

Explanation: Not enough arguments were specifiedfor the BACKUP NTDS command.



ANS1937E No NTDS server name specified for theBACKUP NTDS command.

Explanation: No NTDS server name was specified forthe BACKUP NTDS command.


User response: Specify NTDS server name at thecommand and retry the operation.

ANS1938E NT Active Directory is not supported inthis OS level.

Explanation: NT Active Directory is not supported inthis OS level.


User response: Install Active Directory beforeperforming backup operation.



ANS1939E File Replication Service backup failed.

Explanation: IBM Tivoli Storage Manager encounteredan error while backing up files under control of theWindows 2000 File Replication Service


User response: Examine the Windows 2000 FileReplication Service Event log to insure the FileReplication Service is operating properly. Restart theservice and retry the backup operation.

ANS1940E File Replication Service restore failed.

Explanation: IBM Tivoli Storage Manager encounteredan error while restoring files under control of theWindows 2000 File Replication Service


User response: Examine the Windows 2000 FileReplication Service Event log to insure the FileReplication Service is operating properly. Restart theservice and retry the restore operation.

ANS1941E System Volume backup failed.

Explanation: IBM Tivoli Storage Manager encounteredan error while backing up files of the Windows 2000System Volume


User response: Examine the Windows 2000 FileReplication Service Event log to insure the systemvolume was successfully initialized. Restart the serviceand retry the backup operation

ANS1942E System Volume restore failed.

Explanation: IBM Tivoli Storage Manager encounteredan error while restoring files under control of theWindows 2000 File Replication Service


User response: Examine the Windows 2000 FileReplication Service Event log to insure the systemvolume was successfully initialized. Restart the serviceand retry the restore operation.

ANS1943E The operation is not supported:Downlevel server version.

Explanation: The operation cannot be performedbecause server version is downlevel.


User response: Use correct server version.

ANS1944E Error accessing file or device.

Explanation: An error has occurred while accessingthe file or device.

System action: Backup set operation is not completed.

User response: Verify that the file or device exists andis accessible.

ANS1945E The long namespace has been removedfrom the local filespace. If you wish toproceed with the backup/archiveoperation, rename your filespace on theserver.

Explanation: TSM has detected that the servernamespace is NTW:LONG, but the local volume doesnot have long name support. If you would like to backup the volume using the short names, rename thefilespace on the server. If you would like to back upusing long names, add the long namespace supportback to the volume in question.


User response: Add the long namespace support tothe volume or rename(remove) the correspondingserver filespace.

ANS1946W File exists, skipping

Explanation: The client tried to restore or retrieve thespecified file, but the file already existed in the targetrestore location and the user chose not to replace theexisting file.

System action: The file is skipped, a message islogged in dsmerror.log, and restore or retrieveprocessing continues with the next object.

User response: The file was skipped because eitherREPLACE NO was in effect, causing all existing filesand directories to be skipped, or REPLACE PROMPTwas in effect, and when prompted, the user chose toskip this file or all existing directories and files. Noadditional action is necessary if the decision to skip thefile was deliberate. Otherwise the operation can beretried using either REPLACE ALL (automaticallyreplace existing directories and files) or REPLACEPROMPT (prompt the user whether to replace the file).

ANS1947W The following directory exists and isskipped: file-space_name directory_pathdirectory_name

Explanation: The client tried to restore or retrieve thespecified directory. The directory exists in the targetrestore location and the user chose not to replace theexisting directory.

The directory can be skipped because the optionREPLACE=NO is set, which causes all existing files anddirectories to be skipped. The directory can be skipped



because option REPLACE=PROMPT is set, and the userchooses to skip this directory when prompted.

System action: The directory is skipped, a message islogged in the dsmerror.log log file, and restore orretrieve processing continues with the next object.

User response: No additional action is necessary.

To replace the files, try the operation again and setoption REPLACE=ALL. You can setREPLACE=PROMPT and when prompted, choose toreplace the directory.

ANS1948E The Microsoft volume shadow copysystem components could not bequeried.

Explanation: IBM Tivoli Storage Manager encounteredan error while querying the system writers undercontrol of the Windows volume shadow copy service.The TSM error log and Windows event log mightcontain additional information about this error.


User response: Try the operation again. If the errorpersists, review the TSM error log and Windows eventlog for information related to this error. You mightneed to restart the volume shadow copy service, thentry the operation again. It might be necessary to rebootthe machine to clear the volume shadow copy errorstate.

ANS1949E Microsoft volume shadow copysnapshot initialization failed.

Explanation: IBM Tivoli Storage Manager encounteredan error while initializing the Microsoft VolumeShadow Copy Service for backup or restore. The TSMerror log and Windows event log can containadditional information about this error.


User response: Try the operation again. If the errorpersists, review the TSM error log and Windows eventlog for information related to this error. Use theWindows command VSSADMIN LIST WRITERS todetermine the status of the Volume Shadow Copyservice. You can reboot the machine to clear the volumeshadow copy error state. If the system is a DomainController and the Active Directory service is stopped,restarting the Active Directory service will resolve theissue.

ANS1950E Backup using Microsoft volume shadowcopy failed.

Explanation: IBM Tivoli Storage Manager encounteredan error while performing a backup operation using theMicrosoft volume shadow copy service. The TSM errorlog and Windows event log might contain additionalinformation about this error.


User response: Review the TSM error log andWindows event log for information related to this error.Restart any failing system service indicated in theWindows event log. Restart the volume shadow copyService. You can use the Windows commandVSSADMIN LIST WRITERS to determine the status ofthe volume shadow copy service. It might be necessaryto reboot the machine to clear the Volume ShadowCopy error state.

ANS1951E Restore using Microsoft volume shadowcopy failed.

Explanation: IBM Tivoli Storage Manager encounteredan error while restoring with the Microsoft VolumeShadow Copy Service.


User response: Review the TSM error log andWindows event log for information related to this error.Restart any failing system service indicated in theWindows event log. Restart the volume shadow copyService. You can use the Windows commandVSSADMIN LIST WRITERS to determine the status ofthe volume shadow copy service. It might be necessaryto reboot the machine to clear the Volume ShadowCopy error state.

ANS1952E Invalid symbolic link destination'file-name' entered

Explanation: You entered a restore/retrievedestination file-name specification that is a symboliclink. To restore to symbolic link, make sure you set thefollowsymbolic option to yes. Also, check where thissymbolic link points. You can restore/retrieve to asymbolic link that points to an existing object.


User response: Enter a correct file specification.

ANS1954E Backup processing of 'file-space name'finished with failures.

Explanation: This message indicates that the filesystem backup has completed, but encountered errorsduring backup processing.


User response: Examine the client error log foradditional messages related to errors in backing up thefile system. Take any corrective action as suggested bythe messages.



ANS1956E Too few arguments specified for theBACKUP GROUP command.

Explanation: Too few arguments were specified forthe BACKUP GROUP command.



ANS1957E Showmembers and inactive aremutually exclusive parameters on aquery.

Explanation: Showmembers and inactive are mutuallyexclusive parameters on a query.


User response: Specify one of the mutually exclusiveparameters on the query

ANS1958W No base group found, attempting a fullbackup.

Explanation: A differential backup requires a previousfull backup to have been performed.

System action: Processing continues, and a fullbackup is attempted.

User response: None. Perform a full backup beforeattempting a differential backup

ANS1959I Removing previous incomplete group'name' Id:hi-lo

Explanation: A previous group backup failed withoutcleaning up the temporary groups correctly.

System action: The previous incomplete groups areremoved and processing continues.


ANS1971E The remote client agent (dsmagent)could not be started.

Explanation: The remote client agent cannot bestarted. This error message is usually preceded orfollowed by other messages.


User response: Check the error log for any othermessages that might indicate a reason for the failure.Verify that the web client is installed correctly. Try tocorrect any indicated problems, then try the operationagain. If the problem persists, contact IBM technicalsupport for further assistance.

ANS1972E The connection to the remote clientagent (dsmagent) failed. Either the portnumber could not be read, or the portnumber is invalid.

Explanation: An error occurred when trying to readthe port number. A connection to the remote clientagent cannot be made.


User response: Check the error log for any othermessages that might indicate a reason for the failure.Verify that the web client is installed correctly. Try tocorrect any indicated problems, then try the operationagain. If the problem persists, contact IBM technicalsupport for further assistance.

ANS1973I VSS writer for system object 'name' doesnot exist. Restore skipped.

Explanation: Microsoft Volume Shadow Copy Servicedoes not detect a writer for this system component.Either the component is not installed or is not running..


User response: Install or enable the affected systemservice and retry the operation.

ANS1974W Error removing previous incompletegroup Id:hi-lo

Explanation: A previous group backup failed withoutcleaning up the temporary groups correctly, and theerror still can not be cleaned up.

System action: The previous incomplete groupsremain and processing continues.


ANS1975W TSM server error reason occurred closingand renaming the group

Explanation: An error was encountered closing andrenaming the temporary group.

System action: The backup is unsuccessful.

User response: Ensure that the user has the properauthority to update the group and try the operationagain.

ANS1976E The specified system service is notvalid.

Explanation: The specified system service is not valid.





ANS1977E Dsmcad schedule invocation wasunsuccessful. This command will betried again in 10 minutes.

Explanation: Dsmcad was unable to get the validscheduler information from the dsmc schedule process.This could be due to some problems during thescheduler initialization, such as incorrect option usage.

System action: Dsmcad will try to invoke thescheduler again in 10 minutes in order to get the validinformation.

User response: Check the console and error logs todetermine what kind of error occurred during the dsmcprocess and correct the problem.

ANS1978E The TSM server is downlevel and doesnot support the requested function. Seeerror log for version information.

Explanation: The function being used requires a morecurrent TSM Server.


User response: Upgrade your TSM Server to a levelthat supports this function. See error log for versioninformation.

ANS1979E The TSM Storage Agent is downleveland does not support the requestedfunction. See error log for versioninformation.

Explanation: The function being used requires a morecurrent TSM Storage Agent.


User response: Upgrade your TSM Storage Agent to alevel that supports this function. See error log forversion information.

ANS1980E The TSM Server and TSM Storage agentare downlevel and do not support therequested function. See error log forversion information.

Explanation: The function being used requires a morecurrent TSM Server and TSM Storage agent


User response: Upgrade your TSM Server and TSMStorage agent to a level that supports this function. Seeerror log for version information.

ANS1981E Server :Version ver, Release rel, Levellev.sublStorage Agent:Version SAver, ReleaseSArel, Level SAlev.SAsubl

Explanation: This message supplies extra detail todownlevel messages.


User response: This message supplies extra detail todownlevel messages.

ANS1986E Initialization functions cannot open thetrace file specified.

Explanation: The file could not be opened duringinitialization. The specified path might be incorrect. It isalso possible that the current user does not havepermission to write to the tracefile in the directoryspecified. It is also possible that no space is available atthe tracefile location.


User response: Make sure the tracefile option pointsto a valid path and that the user has properpermissions to write to the specified file.

ANS1987E A destination file specification is notallowed with this command.

Explanation: Of all the system object restorecommands only RESTORE ASR allows the entry of adestination file specification.


User response: Re-issue the command without adestination file specification.

ANS1988W No filespaces are selected for preview.

Explanation: You requested a preview operationwithout selecting a client filespace.

System action: TSM cannot perform a previewwithout a filespace selected.

User response: Select the volumes you want topreview and retry the operation.

ANS1989E Initialization functions cannot open theError Log file specified.

Explanation: The Error Log file could not be openedduring initialization. The specified path may beincorrect. It is also possible that the current user doesnot have permission to write to the logfile in thedirectory specified. It is also possible that no space isavailable at the given logfile location.


User response: Make sure the logfile option points toa valid path and that the user has proper permissionsto write to the file specified.



ANS1990W The 'filesystem name' volume mount pointcan not be accessed. The TSM returncode is 'rc'.

Explanation: The client is unable to access volumemount point. The common reasons for this are that theaccount under which the client is running does nothave access to the volume mount point, or the volumeis mounted onto a cluster volume which is currentlynot available.

System action: The inaccessible mount point isskipped and processing continues. with the next mountpoint or volume.

User response: Check the error log for additionalmessages that might yield additional information aboutthe problem that prevents access to the volume mountpoint. Ensure that the TSM client is running under anaccount which as access to the volume mount point.Ensure that the mount point is not accessing a clusteredvolume. Please refer to Microsoft KB Article 280297 formore information about how to configure volumemount points on a clustered server.

ANS1991E An error occurred processing registrykey 'key-name', data value 'value-name'.See the client error log for additionalinformation about this error.

Explanation: An unexpected error occurred when theclient tried to read or update the Windows registry.Additional information regarding the error is usuallyplaced in the error log.

System action: The operation might not executecorrectly, depending on the error.

User response: Check the client error log for any othermessages that might have been logged when thismessage was written, and take any corrective actionsuggested by those messages. If the problem persists,contact IBM support for further assistance.

ANS1995W Objects of different types cannot bedeleted at the same time.

Explanation: Deleting objects of different types is notallowed. For example, deleting Backup Sets and regularfile objects at the same time is not possible.

System action: No processing takes place.

User response: Select objects of the same type toperform delete operation.

ANS1996W The volume mount points enumerationon 'filesystem name' volume failed.Windows system error code: error;reason: 'error-reason'.

Explanation: The client was unable to scan thespecified volume for volume mount points. The errorinformation captured indicates the reason for the

failure. A common reason is that the account underwhich the client is running does not have access to thevolume.

System action: The processing continues with the nextvolume.

User response: Ensure that the client is running underan account which has access to the volume and volumemount points. Correct the condition causing the errorand try the operation again. If the problem persists,contact your system administrator or TSMadministrator for further help.

ANS1997W No files have been previously backedup for the VSS component'component-name'.

Explanation: You tried to restore the Microsoft VolumeShadow Copy (VSS) System State component whichdoes not contain file data. This is not necessarily aproblem.


User response: Check the error log for any othermessages that occurred during backup. The logs canindicate a reason for the failure.

ANS1998W Transaction byte limit 'name' is notsupported by the server. Value reset tolimit

Explanation: The TXNBYTELIMIT is larger than theserver supports. The value will be reset to a supportedlimit.

System action: TXNBYTELIMIT is reset, andprocessing continues.

User response: Set the option to a value supported bythe server.

ANS1999E type of the operation processing of'filespace-name' stopped.

Explanation: The client has encountered a conditionwhere it can not continue processing the specified filespace. The TSM client error log or schedule log shouldcontain additional messages related to this error.


User response: Check the TSM client error log andschedule log for any additional messages related to thiserror. Take any corrective action that might besuggested by the related messages, then try theoperation again. If the problem persists, contact yourTSM administrator for further assistance.



ANS2026W Bad sectors were detected on the volume'volname'.

Explanation: Bad sectors are skipped during imagebackup/restore operations.


User response: Make sure the volume data is notcorrupt by using system tools like chkdsk (Windows)or fsck (Unix).

ANS2032I The client VM restore is skipping theunsupported Independent disk : vmdk

Explanation: The VMware vStorage APIs do notsupport snapshoting Independent disks, no backupswere created.



ANS2036W Pruning functions cannot open one ofthe Tivoli Storage Manager prune files:log-name. errno = errno-value,

Explanation: The file "log-name could not be openedduring pruning. The system set the error codeerrno-value. If the reason given is "access denied," thecurrent user does not have permission to write to thefile in the directory specified. It is also possible that nospace is available at the given file location or anotherTivoli Storage Manager process started by different userid is performing pruning at the same time.

System action: Pruning stops, processing continues.

User response: Set the DSM_LOG (or DSMI_LOG)environment variable to a directory into which thecurrent user can write.

ANS2037W Schedule log pruning failed.

Explanation: The schedule log pruning functioncompleted with errors.


User response: Check error log for possible reasons offailure.

ANS2038W Invalid option 'option-name' receivedfrom the TSM server client options set.

Explanation: The client received an invalid optionfrom the TSM server's client option set. Although mostsyntax checking for client option set options is done bythe server, there are still errors that can only bedetected by the client. These errors include:

v Option value is not correct.

v Options that have been retired by newer versions ofthe TSM client.

v Missing brackets or directory delimiters.

v Include and exclude patterns that are too complex.

System action: The option is ignored by the TSMclient.

User response: Contact the TSM server administratorto determine if the option can be removed from theclient option set.

ANS2039E Invalid destination file specification'file-name' entered

Explanation: The destination file specification mustend with directory delimiter when performing a file listrestore, or when the restore specification is for morethan one file, or when the option SUBDIR YES is ineffect.


User response: Specify a destination that ends withdirectory delimiter.

ANS2040E While attempting to communicate withthe remote client, a version checkreveals that the versions do not match.The version is remoteversion but theexpected version is localversion.

Explanation: During initialization between the localclient and the remote client, version checking revealsthat the versions do not match. This is usually theresult of an upgrade of one client module withoutupgrading other client modules that are part of productsolution.

System action: The calling procedure returns andcontrol is passed back the user.

User response: Check the versions of all TSM Clientproducts that communicate with each other and ensurethat they are all at the same version, release, and level.

ANS2041E Snapshot Differencing support is notavailable on the specified NetApp filer.

Explanation: Incremental by snapshot differencebackup cannot be performed because required supporton the specified NetApp filer is not availble. .



ANS2042W 'symboliclink':is a symbolic link to a fileor directory in another filesytem. ACLsor extended attributes might not bebacked up.

Explanation: The backup or archive operand containsa symbolic link to a file or directory in another filesystem. Processing may lead to loss of ACLs or otherextended attributes because they might not beprocessed.



System action: The file data is backed up. Processingcontinues with the next object.

User response: If you need to ensure that ACLs andother extended attributes are backed up successfully, donot use symbolic links to back up files on other filesystems of different file system types. Instead use TSMto process the other file system directly.

ANS2043I The virtual machine template 'name' hasalready been backed up.

Explanation: Virtual machine templates are skipped ifno change has occurred since the last backup.

System action: Processing skips this virtual machinetemplate.

User response: To back up this virtual machinetemplate, run an incremental forever full backupoperation.

ANS2044E The template virtual machine 'name'cannot be restored when the TivoliStorage Manager data mover node onthe vStorage Backup Server is connecteddirectly to an ESX/ESXi host.

Explanation: The VMware vStorage API do notsupport template virtaul machine operations whenconnected directly to an ESX/ESXi host.

System action: Processing stops for this templatevirtual machine

User response: Virtual machine template operationsare supported when the IBM Tivoli Storage Managerdata mover node connects directly to a ESX/ESXi host.Modify the VMCHOST to connect the TSM data moverto a vCenter Server.

ANS2045E The VMENABLETEMPLATEBACKUPSoption is not specified. The virtualmachine template 'name' can not bebacked up.

Explanation: The VMENABLETEMPLATEBACKUPStemplate option must specify YES in order for a virtualmachine template to be included in a backup operation.The default value is NO.

System action: Processing stops for this templatevirtual machine

User response: Use the option-vmenabletemplatebackups=yes and run the operationagain.

ANS2046S Error 'errtxt' (errno=errno) occurredtrying to write to audit log 'file-name'.The audit log function is disabled.

Explanation: There was an error encountered writing

to the audit log (for example, there is not enough spaceon the disk).

System action: Audit logging is disabled for the restof the operation. The return code for the operation isset to 12 to indicate that the contents of the audit logare incomplete.

User response: If this is an out of space conditioneither free up space on the volume or try to write theaudit log to a volume with more space.

ANS2047E An unexpected error was encounteredprocessing a system state/servicesrequest.TSM function name : function-nameTSM function : function-descTSM return code : TSM-rcTSM explanation : TSM-msgTSM file : file-name (line-number)

Explanation: None.

System action: Processing the system state stops.


ANS2048W Named stream of object'object-namepath-name file-name' is corrupt.

Explanation: One or more of the file's named streamsare corrupt.

System action: The named stream is notrestored/retrieved.

User response: The backup copy of the named streamis damaged. The file is restored to as great an extent aspossible, but the file should be examined to verify thatit is usable.

ANS2049W Named stream of object 'object-name' maybe corrupt.

Explanation: One or more of the file's named streamsmay be corrupt.

System action: The named stream isrestored/retrieved to as great an extent as possible.

User response: The backup copy of the named streammay be damaged. The file is restored to as great anextent as possible, but the file should be examined toverify that it is usable.

ANS2050E TSM needs to prompt for the passwordbut cannot prompt because the processis running in the background.

Explanation: If PASSWORDACCESS=PROMPT or ifthe password that is stored locally is incorrect, TSMattempts to prompt the user for the password. Theattempt to prompt the user fails because TSM is



running in the background. When a process is runningin the background, prompting is not allowed.


User response: If RUNASSERVICE=YES, do not setPASSWORDACCESS=PROMPT. UsePASSWORDACCESS=GENERATE.

ANS2051W The local snapshot repository was notfound on location.

Explanation: The specified directory for the localsnapshot location does not exist.


User response: A new local snapshot repository willbe build in the specified directory.

ANS2052E Information about the disk subsystem ismissing.

Explanation: The local snapshot repository could notbe initialized due to missing information about the disksubsystem.


User response: The application ensures that the disksubsystem is initialized properly. Check for precedingerror messages.

ANS2053E A memory allocation error has occurredin file filename, line number linenumber.

Explanation: Enough memory was not available tocontinue processing.


User response: Ensure that your system has sufficientreal and virtual memory. Close unnecessaryapplications.

ANS2054E Operating system error errno: messagetext.

Explanation: The application encountered anunexpected message error during the execution of asystem function. The respective operating system errorand message text will be displayed.


User response: Check the specific error message.

ANS2055I The local snapshot manager could notbe locked.

Explanation: The local repository is locked by anotherapplication. This process will proceed when the otherapplication unlock the local repository.



ANS2056I Waiting maximal timeout seconds untilthe lock is released by the otherapplication.

Explanation: While the local repository is locked byanother application, the program will wait a specificperiod of time to proceed. For example, in the mySAPenvironment, the wait period is 1 hour.



ANS2057E Local snapshot manager not initialized.

Explanation: The local snapshot repository was usedwithout previous initialization.


User response: The system normally ensures that thelocal repository is initialized. Check for preceding errormessages.

ANS2058E The data container with ID dcID couldnot be updated in the local repository.

Explanation: During a FlashCopy backup the targetset record in the local repository is updated with thecorrespondent properties. A failure occurred duringthat process.


User response: Check for preceding error messageslike memory allocation error or other system error.

ANS2059E Cannot find a target data container thatmatch with the source data container.

Explanation: During a snapshot type backup orhardware function, TSM tries to find a target datacontainer that match to the source data container tosatisfy the operation. A matching target data containercould not be found.


User response: See the rules for select one of multipletarget data containers. For example, this message willbe displayed if the user is trying to start a FlashCopybackup of type 'INCR' and all the target sets are beingused for the FlashCopy type 'COPY'. Make sure alsothat the target volumes are available to the backupsystem and the syntax is correct for the following setupfile parameters: 1. shark_target_volume 2.shark_copy_service_code 3. java_home_directory 4.primary_copyservices_servername 5. shark_username 6.shark_password



ANS2060W Cannot find a volume in the target datacontainer dcID to match with the sourcesrcvol.

Explanation: This warning message indicates that forthe specific source not any target volume could befound in this target data container that matches for aFlashCopy operation. If multiple target data containersare being used, the processing will continue checkingthe volumes of the next target data container.



ANS2061W The target data container with ID dcidwas not found in the local repository.

Explanation: An inquire of the data container with thespecified ID could not be satisfied because that targetset does not exists in the local repository.

System action: Processing may continue.

User response: The application that is requesting theinquire will decide whether or not the error should endthe program. Check for following messages.

ANS2062W Could not find a target data container inthe state state to fulfill the requestedcriteria.

Explanation: A data container in the specified statewas not found in the local repository to satisfy specificcriteria requested by the application.


User response: Which criteria have been passed isapplication specific. Check for following messages. Theapplication will decide whether or not that warningshould end the program.

ANS2063W The local snapshot repository alreadyexists on the directory location.

Explanation: An application tried to create the localrepository in a directory that already exists.


User response: The application will decide whether ornot that warning should end the program. Check forfollowing messages.

ANS2064I The local snapshot repository will becreated on the directory location.

Explanation: The local snapshot repository containinginformation about the state of the data containers isbeing created.



ANS2065I The local snapshot repository could notbe created on the directory location.

Explanation: A failure occurred creating the localsnapshot repository.


User response: Look for a operating system errormessage.

ANS2066E Cannot read the .fct file filename.

Explanation: The .fct file containing the target datacontainers was not found or is not accessible.


User response: Check the name, the path and theright of the file.

ANS2067E The exception CLsmException wasthrown. Reason: txt.

Explanation: An unexpected error occurred processinga function of the local snapshot repository.


User response: Check the specific reason.

ANS2068E No target LUNs were found for the datacontainer dcID in the .fct file filename.

Explanation: The program will search in the .fct filefor each specific data container a list of entries with thelabel <PREFIX>TARGET_VOLUME where the prefixdepends on the hardware type. Either you have awrong label for the target volumes of the specified datacontainer or this data container in the .fct file does nothave any target LUNs.


User response: This error can only occurred if theapplication does not have a GUI where the userprovides the input of the target data containers and theformat will automatically be checked. If so, pleasecheck the format of the .fct file.

ANS2069E Cannot read the file filename of the localsnapshot repository.

Explanation: The system keeps some informationabout the state of the data containers locally in a file.This file was not found or is not accessible.


User response: Check the name, the path and theright of the file.



ANS2070E The repository state file filename isempty or has a wrong format.

Explanation: The system keeps some informationabout the state of the data containers locally in a file.This file was found but the expected format of the datain not correct.


User response: Normally the system ensures that theformat of this file is correct. Check for preceding error.

ANS2071E The data container dcID could not beinserted in the local snapshot repository.

Explanation: The system keeps some informationabout the state of the data containers locally in a file.Inserting an entry for a new data container occurred anerror.


User response: This is an unexpected error. Check forpreceding error. If not any other error can be seen,collect the logs and traces and contact the support.

ANS2072E An unexpected error was encounteredprocessing a TSM operation using ahardware or snapshot function.TSM function name : function-nameTSM function : function-descTSM return code : TSM-rcTSM file : file-name (line-number)

Explanation: None.



ANS2073E The file filename of the local snapshotrepository could not be opened forwriting.

Explanation: The system keeps some informationabout the state of the data containers in the localsnapshot repository. Opening a file of this repositoryoccurred an error.


User response: Check the rights permission of thatfile.

ANS2074E Cannot open user input FlashCopytarget file 'fct_file'.

Explanation: The FlashCopy target file that the userprovided cannot be read.


User response: Run the client configuration utility and

provide a valid FlashCopy target user input file.

ANS2075E There is no VTOC data available for thevolume. The volume cannot be backedup.

Explanation: The volume disk label type is not VTOC.It is possible that your disk is formatted with an EFIlabel. The TSM client on Solaris currently supports onlyVTOC disk labels.

System action: The volume is not backed up.

User response: Do not attempt to backup volumesformatted with a non-VTOC disk label.

ANS2076E program-name: Space Managment can notbe added for file system 'filesystem' Thelength of the file system name exceedsthe maximum length of 'maxlength'which can be stored in a DMAPIattribute.

Explanation: The DMAPI has a limitation in the sizeof data that can be stored in a DMAPI attribute. If thelenght of the file system name exceeds this limit theTSM client can not add space management to the filesystem.

System action: Space management cannot be added tofile system.

User response: Please make sure that the length of thefile system name does not exceed the DMAPI limit.

ANS2077E program-name: Reconcile for file system'filesystem'can not be started for the selected modein a non-scout environment.Please use Two Way Orphan CheckReconcile instead.

Explanation: The TSM client reconciliation programcan not be started in orphan check or stub restoremode when the HSM system is configured to runwithout the scout daemon.

System action: Reconcile can not run in a non scoutenvironment.

User response: If you have configured a non scoutenvironment you need to use the Two Way OrphanCheck Reconcile.

ANS2078E System state backup is not allowedCLUSTERNODE is set to YES.

Explanation: When the CLUSTERNODE option is setto YES, the backup systemstate command is not valid.

System action: System state backup is stopped.

User response: If the CLUSTERNODE option isincorrectly set to YES, then change the option to NO



and try the operation again. Otherwise see thebackup-archive client manual for further informationabout configuring the client to run in a clusterenvironment.

ANS2079E Error processing 'filespacenamepath-namefile-name': error scanningsnapshot

Explanation: This message is issued when the TSMclient is unable to read data from a snapshot used forthe backup. If you are performing the MicrosoftVolume Shadowcopy Service (VSS) snapshot backupone possible cause is that the operating system deleteda VSS snapshot because the shadow copy storage couldnot grow. If you are performing the snapshot differenceincremental backup on normal NetApp/N-Seriesvolumes one possible cause is that the base snapshotwas accidentally removed from the NetApp file server.

System action: Backup processing for the file systemstops.

User response: If you were performing VSSsnapshot-based backup, examine the client error logand the Microsoft Windows system event log for anyother messages that might help identify the problem. Ifthere are no obvious reasons for the failure, try theoperation again,the problem might be caused bytemporary I/O conflicts between VSS and other systemdisk I/O activities. If you were performing snapshotdifference incremental backup, contact your TivoliStorage Manager administrator to verify that basesnapshot was not accidentally deleted.

ANS2080W The value 'option' for the option 'option'is no longer supported and will beignored by TSM client in this release.

Explanation: The specified option value is in theprocess of being made obsolete and will be ignored bythe client in this release. This option value will beremoved in the next release and will no longer bevalid.


User response: Update the option value or remove theoption from the option file. Also check thedocumentation to see if this option has been replacedby a newer option.

ANS2083W No vApps that match the inputspecification were found.

Explanation: A vApp that matches the specified inputor the VAPP value in the DOMAIN.VCD option wasnot found.

System action: The operation is stopped

User response: Make sure the the VAPP value in theDOMAIN.VCD option is correct.

ANS2084I Creating a new vApp

Explanation: The estore is attempting to create thedestination vApp.

System action: This message is for informationalpurposes only.

User response: No action is required.

ANS2085E The virtual machine is configured as afault tolerant virtual machine. As aresult, it cannot be backed up.

Explanation: vSphere does not allow for the snapshotor backup of fault tolerant virtual machines withvStorage API for Data Protection.


User response: To back up a fault tolerant virtualmachine with vStorage API for Data Protection, firstdisable fault tolerant. Then, after the backup completes,enable fault tolerant.

ANS2088E Session rejected: The client does not useunicode.

Explanation: The server cannot accept the clientsession because the client does not use unicode and thenode already contains a unicode filespace. The serverrecords whether or not the client's data is unicode, anddoes not let the node change this attribute.


User response: Logon to the server from a client witha platform that uses unicode data. For example, theoriginal platform that was used to create the existingfilespaces for this node. Alternatively, if the client nodeneeds to change to the platform that is currently beingattempted, contact the server administrator to removethe existing filespaces that contain unicode data and trythe node connection again.

ANS2089E The string string_text can not beconverted to Unicode.

Explanation: An object contains a multibyte sequencethat is invalid for the current locale.


User response: Verify that the locale is appropriate forthe objects that are processed.

ANS2090I The virtual machine folder could not befound in this path: 'name'.

Explanation: The destination target does not have theoriginal inventory path that was saved with the virtualmachine. As a result, the virtual machine is restored tothe top level of the ESX/ESXi inventory.

System action: Processing continues



User response: None

ANS2091I The virtual machine resource could notbe found in this path: 'name'.

Explanation: The destination target does not have theoriginal resource path that was saved with the virtualmachine. As a result, the virtual machine is restored tothe top level of the ESX/ESXi inventory.


User response: None

ANS2092I The restore process will override theoriginal inventory path that was savedwith this virtual machine.

Explanation: Specifying the -datacenter or -host optionwill override the original inventory path that wassaved with the virtual machine. As a result, the virtualmachine is restored to the top level of the ESX/ESXiinventory.


User response: None

ANS2093E The remote file system agent isdownlevel and does not support thisoperation.NODENAME : nodeMULTI-NODE NAME : multi-nodehostname : hostTCP/IP address : tcpaddr:tcpportversion : version.release.level..mod

Explanation: None.


User response: Upgrade the remote file system agentto a supported level.

ANS2097E Unable to establish a session with theTSM server as target node 'target' usingagent node 'agent'.

Explanation: None.


User response: Ensure that the multi-node name existson the server and that the agent node has the properauthority to target node listed.

ANS2100E Neither source volume id nor targetvolume id is in the volume list.

Explanation: None.



ANS2101E Compressed data grew.

Explanation: The size of data is growing aftercompression


User response: The application must abort thetransaction.

Please turn off compression and try to resend theobject.

ANS2102E File list processing not started

Explanation: An error occured before the file listprocessing was started.



ANS2104E An error occured after processing thefile list.

Explanation: An error occured after the file listprocessing completed.



ANS2105I File list entry not Processed: File ListEntry

Explanation: A file list operation encounted an error.This entry from the file list was not processed.



ANS2106I Connection to primary TSM serverprimary server; failed

Explanation: A communication error occured whileattempting to connect to the primary server. The nodeis configured for replication and will attempt to connectto the secondary server.


User response: Contact the TSM server administratorto verify if the primary server is available. If theprimary server is available, check the TSM error log forcommunications failures and correct any configurationissues. If the TSM server is not available, allow thenode to fail over to the secondary server as configured

ANS2091I • ANS2106I


by the primary TSM server administrator.

ANS2107I Attempting to connect to secondaryserver secondary server; at secondary server;: TCP/IP Port;

Explanation: The node is configured for replicationand will attempt to connect to the secondary server.The secondary server address and port are configuredby the primary TSM server administrator and are savedin the options file.


User response: Contact the TSM server administratorto verify if the primary server is available. If theprimary server is available, check the TSM error log forcommunications failures and correct any configurationissues. If the TSM server is not available, allow thenode to fail over to the secondary server as configuredby the primary TSM server administrator.

ANS2108I Connected to secondary server secondaryserver;.

Explanation: The node is configured for replicationand has successfully connected to the secondary server.



ANS2110I Connection to secondary server TSMsecondary server; failed

Explanation: A communications error occured whileattempting to connect to the secondary server. Thenode is configured for replication and an attempt toconnect to the secondary server was made but failed.


User response: Contact the TSM server administratorto verify if the secondary server is available. If thesecondary server is available, check the TSM error logfor communications failures and correct anyconfiguration issues.

ANS2111E The REPLSERVERNAME entry for thespecified MYREPLICATIONSERVERoption was not found.

Explanation: The MYREPLICATIONSERVER optionmust have a matching REPLSERVERNAME entry inthe options file. The REPLSERVERGUID,REPLTCPPORT, and REPLTCPSERVERADDRESS mustalso be specified. These options are normally set by theTSM server administrator and saved to the options fileduring logon to the primary server.


User response: Manually edit the options file to eithercorrect or remove the options.

ANS2112I Secondary server is configured as'read-only'. Backup and Archiveoperations are not supported when thesecondary server is in 'read-only' mode

Explanation: The TSM client has established a sessionwith a server that is configured as 'read-only'. The TSMserver is configured as a replication server and will notaccept data from this node.


User response: The TSM may be used for Restore,Retrieve and Query operations. Backup and Archivecommands will fail. The TSM server administrator canenable Backup and Archive operations for the nodewith the 'Update Node' command.

ANS2113E The Command; command is not enabledwhen connected to the secondary serverin failover mode.

Explanation: The TSM client has failed over andestablished a session with a secondary server. The TSMserver is configured as a replication server and will notaccept data from this node. Commands that store dataon the server are disabled.


User response: You can use the TSM client forRestore, Retrieve, and Query operations. Backup andArchive operations will fail.

ANS2114W IBM Tivoli Storage Manager applicationprotection did not copy the VSSManifest files from VM 'VM'.

Explanation: The VSS Manifest files are not found onthe guest machine.

System action: The VSS Manifest files cannot becopied. Verify that the VSS and SQL Writer services arerunning on the guest VM

User response: None

ANS2115I Replication server connectioninformation saved:connection information;

Explanation: This node is configured for replication.The replication server connection information has beensaved to the options file. The replication server optionsare set by the IBM Tivoli Storage ManagerAdministator, sent to the client during logon, and aresaved to the options file.





ANS2116W IBM Tivoli Storage Manager applicationprotection did not back up the VSSManifest files from VM 'VM'.

Explanation: A failure occurred while backing up thefiles that are necessary for application protection.

System action: The back up of this VM failed.

User response: Check the dsmerror.log for additionalinformation. Then try the operation again.

ANS2117E Source volume is of subtype dev-typeand destination is of subtype dev-type.Destination must be larger than source.

Explanation: Logical volumes from scalable volumegroups (subtype DS_LVZ) do not contain an LVCB.That is, the very first block contains user data.AIX LVM volumes from original volume groups(subtype LVM) contain a Logical Volume Control Block(LVCB) on the first block (512 bytes) of the volume.When restoring to a volume of subtype LVM, the firstblock must be skipped in order to preserve the existingLVCB of the destination volume. That is, the restoreoperation begins writing at the second block of thevolume.This means that given two volumes of identical size,one of subtype DS_LVZ and the other is of subtypeLVM, the latter has one less 512-byte block in which tostore user data. Thus when you restore a volume ofsubtype DS_LVZ to a volume of subtype LVM, it is notsufficient for the destination volume to be the same sizeas the source volume. Instead, the destination volumemust be at least one 512-block larger than the sourcevolume.


User response: Make sure that both source anddestination logical volumes are of the same type, orchoose a larger destination volume, or increase the sizeof the destination volume.

ANS2118I A write failure occurred whileattempting to save node replicationfailover values to the options file.

Explanation: A write failure is often a result ofinsufficient access permissions to the options file, butcould also be caused by the lack of available diskspace. The replication server connection informationcan not be saved and failover will not be possible.

System action: The operation failed.

User response: Check the local disk for possiblecauses of the write error, and check to see thatsufficient access to the options file is configured.

ANS2119I An invalid replication server addressreturn code rc value = rc-value wasreceived from the server.

Explanation: An invalid replication server addressreturn code indicates that the server was not able toaquire connection information.

System action: Possible server problem.

User response: Check the server log for moreinformation.

ANS2120W The last store operation date reported bythe server replication server; of servercommit date; UTC does not match the laststore operation date of client commit date;UTC stored by the client for thefilespace filespace;.

Explanation: The last store operation date reported onthe server does not match the date stored locally on theclient. If connected to the replication server it is likelythat the replication was done before the last storeoperation from the client to the primary server. Hence,the replication is out of date. If connected to theprimary server it is likely that the previous backup wasdone from another machine.


User response: Contact the TSM server administrator.Restoring from an out of date replica may lead to lossof data. If the primary server cannot be recovered, afull backup to the replica may be appropriate. Ifconnected to the primary server, the message can beignored.

ANS2121I The file space on replication server;started replication at server replicationstart date; The replication completedsuccessfully at server replication completedate;.

Explanation: The last server replication completedsuccessfully.



ANS2122I The file space on replication server;started replication at server replicationstart date;. The replication did notcomplete successfully. The lastsuccessful replication completed at serverreplication last successful date;.

Explanation: The last server replication did notcomplete successfully.


User response: Contact the TSM server administrator.



Restoring from an out of date replica may lead to lossof date. If the primary server cannot be recovered, afull backup to the replica may be appropriate.

ANS2123W Issue the dsmc SET PASSWORD-type=VCD 'vCloud Director hostname''userid' 'password' command to save anencrypted password.

Explanation: The VCDPW option was found either inan options file or as a command- line entry. Althoughboth methods of entry are allowed, they present asecurity risk because the password is in plain text andis not encrypted.

System action: The option is accepted and the VCDpassword is used in the current session.

User response: To save an encrypted password, issuethe following command:dsmc SET PASSWORD -type=VCD 'VirtualCenterhostname' 'userid' 'password'

ANS2124W Client node replication table is lockedby another process.

Explanation: Another process is using the client nodereplication table.Only one process may use it at a time.

System action: This process does not use the clientnode replication table.

User response: You can serialize processes using theclient node replication table. Or you can reconfigure thecurrent process to use a different table path to avoidcontention.

ANS2126E The Organization VDC node thatcontains snapshots of OrganizationVDC 'org vdc name' of organization 'orgname' was not found.

Explanation: The Organization VDC node contains thebackup data to be restored. The specified organizationand organization VDC are not mapped to thisOrganization VDC node. As a result, the restoreoperation cannot proceed.


User response: Verify that the specified organization,organization VDC, and vApp are correct.

ANS2127E The snapshot data that is required torestore 'vapp name' cannot be retrievedfrom the TSM Server.

Explanation: The required snapshot data was unableto be retrieved from the TSM Server.

System action: The operation stopped.

User response: Check the dsmerror.log file for

information about why the data was not retrieved.Then, try the operation again. If the problem persists,visit the IBM Support Portal for additional informationat http://www.ibm.com/support/entry/portal/.

ANS2128E Failed in creating a restored version ofvApp 'vapp name'.

Explanation: The operation to create a restored vAppon the vCloud failed. The data associated with thevApp snapshot might not be complete.


User response: Check the dsmerror.log file forinformation about why the operation failed. Then, trythe operation again. If the problem persists, visit theIBM Support Portal for additional information athttp://www.ibm.com/support/entry/portal/.

ANS2135E The node on the TSM server is in readonly mode.

Explanation: The server has prevented a storeoperation on the TSM server. The most likelyexplaination for this is the node has failed over to thesecondary server.


User response: Contact the TSM server administratorto verify if the primary server is available. If theprimary server is available, check the TSM error log forcommunications failures and correct any configurationissues.

ANS2136E Operation not permitted. The secondaryserver reports the primary server isavailable. Quit and restart the TSMclient and retry the command.

Explanation: The server has prevented a storeoperation on the secondary TSM server. The secondaryserver reports that the primary server is available.However, the TSM client failed over to the secondaryserver.


User response: Restart the TSM client and verify theprimary server connection is made. If the TSM client isunable to connect to the primary server, contact theTSM server administrator to verify if the primaryserver is available. If the primary server is available,check the TSM error log for communications failuresand correct any configuration issues.

ANS2138E Failed in restoring the vApp propertiesto vApp: 'vapp name'.

Explanation: The vApp properties were not restoredto the created vApp. This failure might be caused by aproblem in the backed up vApp or in its metadata.



System action: The operation completes. However, itis possible that the restored object does not contain allof the expected content.

User response: Check the backed up vApps on thevCloud. In addition, check the dsmerror.log file for anyadditional messages that might be related to thisproblem. Try the operation again. If the problempersists, visit the IBM Support Portal for additionalinformation at http://www.ibm.com/support/entry/portal/.

ANS2143E vApp verification failed. Datainconsistency was found.

Explanation: During the verification of a vApp, aninconsistency was found in the backup data.

System action: The restore operation was stopped.

User response: Examine the client error log for anyadditional messages that might be related to thisproblem and contact TSM technical support for furtherassistance.

ANS2145W Warning - updating an existing virtualmachine named 'name'. The restoreoperation continues.

Explanation: The virtual machine exists and will beupdated with the disks specified.

System action: The virtual machine will be updatedby the restore operation.

User response: No user action is necessary.

ANS2146E The target vCenter or ESX/ESXi host isno longer supported, for virtual machinebackups, by this version of IBM TivoliStorage Manager.

Explanation: The target vCenter or ESX/ESXi host isno longer supported, for virtual machine backups, bythis version of IBM Tivoli Storage Manager.

System action: Processing stops for this virtualmachine.

User response: Specify another target vCenter orESX/ESXi host that is supported by this version of IBMTivoli Storage Manager.

ANS2147E The virtual machine named 'name'already exists on the target system.

Explanation: The virtual machine cannot be restoredbecause the name already exists on the target system.

System action: Processing stops for this virtualmachine

User response: Use the -vmname option to rename thevirtual machine.

ANS2148I Virtual machine templates cannot bebacked up in incremental mode,switching to full mode.

Explanation: The backup of virtual machine templatesare only supported as full backups.

System action: Processing continues in full mode forthis template virtual machine.

User response: To back up this virtual machinetemplate use full mode.

ANS2149E The restore operation for this virtualmachine to the target ESX/ESXi host isnot supported because virtual machinehardware version is incompatible.

Explanation: The target ESX/ESXi host does notsupport the virtual hardware version of the virtualmachine. As a result, a restore of the specified virtualmachine to this host is not supported.

System action: Processing stops for this virtualmachine.

User response: Specify another virtual machine torestore or specify another target ESX/ESXi host thatsupports virtual hardware version of the virtualmachine.

ANS2150E SetHSMDISABLEAUTOMIGDAEMONSYES in the dsm.opt file to use HSMmulti-server functionality.

Explanation: Set HSMDISABLEAUTOMIGDAEMONSYES in the dsm.opt file to use HSM multi-serverfunctionality.

System action: HSM multi-server processing stops.

User response: SetHSMDISABLEAUTOMIGDAEMONS YES in dsm.opt.

ANS2155W Skipping file 'file-name'. File related to'server-name'.

Explanation: File is already coupled to another server.

System action: HSM continues with normal operation.

User response: Use the correct server to process thefile.

ANS2156E The server 'server-name' was not added tothe environment.

Explanation: The requested IBM Tivoli StorageManager server was not added to the multi-serverenvironment.There are several causes for this error:

v The file system is not managed by HSM.



v The HSM management is not active for the filesystem.

v The file system is out of space.

v The default IBM Tivoli Storage Manager server forthe file system was not yet added to the multi-serverenvironment.

v The IBM Tivoli Storage Manager server name is notvalid.


User response: Eliminate the possible causes for thisissue and retry.

ANS2157E The server 'server-name' was not removedfrom the environment.

Explanation: The requested IBM Tivoli StorageManager server was not added to the multi-serverenvironment.There are several causes for this error:

v The file system is not managed by HSM.

v The HSM management is not active for the filesystem.

v The IBM Tivoli Storage Manager server is the defaultserver for the file system and must be removed last.

v The IBM Tivoli Storage Manager server name is notvalid.


User response: Eliminate the possible causes for thisissue and retry.

ANS2158E The server 'server-name' was not added tothe environment.You must first add the default IBMTivoli Storage Manager server('default-server-name') for this file system.

Explanation: The requested IBM Tivoli StorageManager server was not added to the multi-serverenvironment.The requested IBM Tivoli Storage Manager server is notthe default server for the file system.


User response: Add the default IBM Tivoli StorageManager server first.

ANS2159I The server 'server-name' was added to theenvironment.

Explanation: The requested IBM Tivoli StorageManager server was added to the multi-serverenvironment.

System action: HSM multi-server processingcontinues.


ANS2160I The server 'server-name' was removedfrom the environment.

Explanation: The requested IBM Tivoli StorageManager server was removed from the multi-serverenvironment.



ANS2161E The server 'server-name' is not a validIBM Tivoli Storage Manager server forthis environment.

Explanation: The requested IBM Tivoli StorageManager server was not added to the multi-serverenvironment.


User response: Check the dsm.sys file for the correctIBM Tivoli Storage Manager server name.

ANS2162E HSM cannot be removed from the filesystem. The IBM Tivoli StorageManager multi-server list is not empty.

Explanation: HSM management was not removedfrom the file system.

System action: HSM processing continues.

User response: Remove all IBM Tivoli StorageManager servers from the multi-server list beforeremoving HSM.

ANS2163E The default IBM Tivoli Storage Managerserver ('server-name') for the file systemwill be removed.

Explanation: The default IBM Tivoli Storage Managerserver will be removed.The IBM Tivoli Storage Manager server list formulti-server will be empty after this step.

System action: HSM processing continues withoutmulti-server support.

User response: nothing.

ANS2165I The server 'server-name' is the defaultserver and has been removed last.

Explanation: The requested IBM Tivoli StorageManager server was removed from the multi-serverenvironment.


User response: None



ANS2166I The IBM Tivoli Storage Manager server'server-name' is not included in themulti-server environment.

Explanation: The requested IBM Tivoli StorageManager server is not part of the multi-serverenvironment.



ANS2167W Can not read SERVERNAME attribute.

Explanation: IBM Tivoli Storage Manager cannot readthe SERVERNAME attribute from file.



ANS2168W Can not write SERVERNAME attribute.

Explanation: IBM Tivoli Storage Manager cannot writeSERVERNAME attribute to file.



ANS2169E Skipping - Requested server is notincluded in multi-server environmentfor filesystem 'file-system'.

Explanation: The requested IBM Tivoli StorageManager server is not part of the multi-serverenvironment.



ANS2170W Skipping - file linked to another server.

Explanation: The file is already coupled to anotherIBM Tivoli Storage Manager server.

System action: HSM continues with normal operation.

User response: Use the correct server to process thefile.

ANS2171E The DMAPI version 'dmapi-version' is notsupported.

Explanation: The DMAPI version installed on thisnode is not supported from the given TSM client.

System action: Due to this issue the affected HSMprocess ends.

User response: Use the documentation to identify the

supported DMAPI versions. Install a supported DMAPIand retry the HSM command or process.

ANS2172E Command not supported inHSMBACKENDMODE TSMFREE.

Explanation: That command is not supported usingan external HSM backend.

System action: Exit programm

User response: Do not use the command

ANS2173E Volume 'volume name' from vFiler 'vFilername' is mounted using AIX NFSversion 4. This configuration is notsupported for snapshot differenceincremental backups.

Explanation: Snapshot difference incremental backupsare not supported for vFiler volumes mounted usingAIX NFS version 4.

System action: Snapshot difference incrementalbackup fails.

User response: This problem is documented byNetApp BURT 630200. Apply the fix for this once it isavailable from NetApp. Specify "testflagsnapdiffenablevfilernfs4" in dsm.opt file and retry thesnapshot difference incremental backup.

ANS2174E Conflicting options HSMLOGMAX andHSMLOGRETENTION were specified.

Explanation: Values were specified for both theHSMLOGMAX and the HSMLOGRETENTION options.These options are mutually exclusive.


User response: Specify a nonzero value forHSMLOGMAX if you wish to have the TSM hsm logwrap when it reaches the specified maximum value.Use HSMLOGRETENTION if you wish you have thehsm log limited in size on a time-based schedule.

ANS2175I Data from server 'server-name' should berecalled using the script'dsmMultiServerRemove.pl'.

Explanation: Migrated files must be recalled before aserver can be removed from the multiserverconfiguration.

System action: The server will not be removed.

User response: Check the documentation for detailedinformation about the 'dsmMultiServerRemove.pl'script.



ANS2176E The sample journal configuration file ''could not be copied to ''.

Explanation: The TSM Journal Engine setup wizardtried to create a new journal configuration file bycopying the sample configuration file. However thesample configuration file could not be successfullycopied.

System action: The TSM Journal Engine setup wizardstops.

User response: Manually copy the sample journalconfiguration file "config\tsmjbbd.ini.smp" to"baclient\tsmjbbd.ini", then try the TSM Journal Enginesetup wizard. The "baclient" and "config" directoriescan be found in the directory where you installed theTivoli Storage Manager Backup-Archive Client. Forexample, "C:\Program Files\Tivoli\TSM\baclient" and"C:\Program Files\Tivoli\TSM\config"

ANS2177E The vCloud vApp named 'vapp name'already exists on the target system.

Explanation: The restore vApp command does notsupport restoring a vApp with an existing name.

System action: The restore was not performed.

User response: Execute the required restore commandagain, considering that the given name for the restoredvApp is not used.

ANS2181I Option primary server; saved.

Explanation: This node is configured for replication.The primary server name option is now saved to theoptions file. The replication server options are set bythe IBM Tivoli Storage Manager Administator, sent tothe client during logon, and are saved to the optionsfile.



ANS2182I Option secondary server; saved.

Explanation: This node is configured for replication.The replication server option is now saved to theoptions file. The replication server options are set bythe IBM Tivoli Storage Manager Administator, sent tothe client during logon, and are saved to the optionsfile.



ANS2183E Organization 'Org name' not found in thevCloud Director.

Explanation: The specified Organization is notrecognized by the vCloud Director.

System action: The action requested for theorganization is canceled.

User response: Verify that an organization by thespecified name exists in the vCloud. Organizationnames are case-sensitive.

ANS2184E Organization VDC 'Org vDC name' notfound in organization 'Org name'.

Explanation: The specified organization VDC is notpart of the specified organization.

System action: The action requested for theorganization VDC is canceled.

User response: Verify that an organization VDC bythe specified name exists in the specified organization.Organization and organization VDC names arecase-sensitive.

ANS2185E Failed to log on to the vCloud Directoron 'vCD host name' with user name 'vCDuser name': Authentication failed.

Explanation: The vCloud credentials specified in theVCDUser and VCDPass options were rejected by thevCloud director.

System action: vCloud operations cannot beperformed.

User response: Update the VCDUser and VCDPassoptions with valid credentials for the vCloud Director.

ANS2186E Failed to log on to the vCloud Directoron 'vCD host name' with user name 'vCDuser name': User not found.

Explanation: The vCloud user specified by theVCDUser option does not exist on the vCloud Director.


User response: Update the the VCDUser option witha valid vCloud user name for the vCloud Director.

ANS2187E Failed to establish connection to thevCloud Director on 'vCD host name'.

Explanation: A connection cannot be established tothe vCloud Director on the host that is specified by theVCDHost and VCDPort options.


User response: Verify that the values of the VCDHOst



and VCDPort options are valid, network connectivity tothe host exists, and that the vCloud Director service isrunning.

ANS2188E The vCloud protection runtime libraryis not installed or failed to load.

Explanation: The vCloud runtime library is notinstalled or cannot be loaded.


User response: Verify that the TSM for VirtualEnvironments vCloud runtime library is installed. Ifneccessary, reinstall TSM for Virtual Environments.

ANS2189E The vCloud protection runtime librarycannot be initialized.

Explanation: The vCloud protection runtime libraryfailed to initialize. This issue might be caused by theJava runtime not being installed.


User response: Verify that Java is installed.

ANS2190E The vCloud protection runtime libraryencountered an internal error.

Explanation: An internal error had occured in thevCloud runtime library.


User response: Check the dsmerror.log file for anyadditional messages that might be related to thisproblem. Try the operation again. If the problempersists, visit the IBM Support Portal for additionalinformation at http://www.ibm.com/support/entry/portal/.

ANS2191E An error occurred creating the defaultVSS staging directory 'path'.

Explanation: The TSM client uses an VSS stagingdirectory to store files related to to VSS snapshotoperations. The TSM client was unable to create thisdirectory structure.

System action: The TSM client stopped.

User response: If the problem persists, contact IBMtechnicalsupport for further assistance.

ANS2192E Failed to read the node configurationinformation from node 'node name'.

Explanation: Node mapping information is requiredfor this vCloud operation. However, the mapping

information either does not exist or cannot be readfrom the specified node.

System action: The operation is canceled.

User response: Make sure that you are accessing thecorrect node. The node mapping information is storedin the Provider VDC node. If necessary, go to theConfiguration page and click 'Run the ConfigurationWizard' to make corrections to the node mapping.

ANS2193E The required filespace for the vApp'vapp name' backup does not exist.

Explanation: No filespace exists for the specifiedvApp backup.


User response: Make sure that the specified vApp iscorrect. Then, try the restore operation again.

ANS2194E The snapshot data is incomplete forvApp 'vapp name'.

Explanation: Inconsistent data was found in thebacked up vApp. It is not possible to restore thespecified vApp.


User response: Check the dsmerror.log file for anyadditional messages that might be related to thisproblem. If the problem persists, visit the IBM SupportPortal for additional information athttp://www.ibm.com/support/entry/portal/.

ANS2195E The number of VMs that are availablefor restore is different from expectedaccording to the vApp 'vapp name'metadata.

Explanation: Inconsistent data was found in the vAppmetadata. It is not possible to restore the specifiedvApp. More VMs have been backed up than are nowavailable for restore. This may happen due toincomplete node replication or if a file space wasdeleted.


User response: Check the dsmerror.log file for anymessages that may indicate the problem. Run a detailedquery for this vApp to verify that all VMs backupsexist. If node replication is used, ensure it is workingcorrectly. If the problem persists, visit the IBM SupportPortal for additional information athttp://www.ibm.com/support/entry/portal/. ContactTSM administrator for more information.



ANS2196W An incompatible disk configuration isdetected for the following disk: 'diskname'. The individual database restorefor the following database is notsupported:'database name'.

Explanation: One or more database files in thisoperation are located on the dynamic or GUID PartitionTable (GPT) disks. In this configuration, individualdatabase restore is not supported.

System action: Backup of the full VM continues.

User response: To restore the environment to theprevious statue, issue a full VM restore.

ANS2197E The verification test of vApp 'vapp name'indicates that VM data is incomplete inthe vApp. The vApp cannot be restored.

Explanation: Inconsistent data was found in the VMfor the specified vApp. It is not possible to restore thespecified vApp. This may happen due to incompletenode replication or if a file space was deleted.

System action: Operation continues.

User response: Check the dsmerror.log file for anyadditional messages that might be related to thisproblem. Run a detailed query for this vApp to verifythat all VMs backups exist. If node replication is used,ensure it is working correctly. If the problem persists,perform a FULL new backup of the vApp and visit theIBM Support Portal for additional information athttp://www.ibm.com/support/entry/portal/. ContactTSM administrator for more information.

ANS2198I Backup of VMware vCloud DirectorvApp 'vApp name' in Organization VDC'Org VDC name' of organization 'Orgname' completed successfully. VMs:number of VM backed up out of number ofVMs in vApp VMs backed upsuccessfully.

Explanation: The backup operation completed. Thenumber of VMs backed up and the total number ofVMs in the vApp are displayed.


User response: If the number of VMs backed up isless than the total in the vApp please check the errorlogs for more information.

ANS2200I ***** Filling Cache count files *****

Explanation: TSM the specified number of files havebeen added to the disk cache.



ANS2201I ***** Inspecting Cache count files *****

Explanation: TSM the specified number of files havebeen examined in the disk cache.



ANS2202E Disk Full Error Accessing Disk Cache.

Explanation: A disk full error occurred attempting toaccess or write to the specified disk cache file during adisk cache incremental backup. See the client error logfor more detailed information.


User response: This error can be resolved by freeingup space in the file system containing the cache file, orspecifying a different location for the cache file. Use thediskcachelocation option to specify the location of thecache file.

ANS2203E Error Accessing Disk Cache.

Explanation: An error occurred attempting to accessthe specified disk cache file during a disk cacheincremental backup. See the client error log for moredetailed information. TSM.



ANS2204E Disk cache restarted.

Explanation: The length of an object name exceededthe configured disk cache key length during a diskcache incremental backup. The backup must berestarted.. TSM.

System action: Backup is restarted with a larger keylength to accommodate the object name.

User response: None required. The name of the objectthat caused the failure can be found in the dsmerror.logfile.

ANS2206W The user must have root authority to usethe memory efficient backup disk cachemethod. The operation will continueusing memory efficient backup methodwithout disk caching.

Explanation: None.

System action: The operation continues without usingdisk caching.




ANS2213E Error while querying volume propertiesof volume volserial.Please verify that the volume specifiedin the target volumes file exists.

Explanation: None.



ANS2218I The encryption key password for nodenode name and server server name hasbeen migrated.

Explanation: The format of the TSM password file hasrecently changed. The option MIGRATEENCRYPTKEYis set and the stored encryption key password wasautomatically migrated to the new format. Thismessage confirms that the migration was successful.

System action: The encryption key password has beenmigrated.

User response: No response.

ANS2219E Cannot backup or archive files intofilespace because it is owned by a TSMAPI application.

Explanation: TSM Client cannot archive or backupfiles into a file space that is used a TSM APIapplication.


User response: Use separate node names for TSMClient and TSM API application(s).

ANS2220E The cluster disk could not be put inmaintenance mode.

Explanation: The system call to put the cluster disk inmaintenance mode failed.


User response: Try the operation again. If the problemcontinues, check the client error log for any othermessages that might have been logged when thismessage was written, and take the corrective action (ifany) suggested by those messages. Examine theWindows event log which may contain additionalinformation. See your system administrator or TSMadministrator for further help.

ANS2221W Java was not able to resolve the IPaddress of your local machinedue to network misconfigurationproblems!Please verify your network and DNSconfiguration are setup correctly.Note that on UNIX machines the

hostname must be reported correctly(the same)for IPv4 and IPv6 communicationmethods in the /etc/hosts configurationfile.TSM processing continues.

Explanation: Java was not able to get the local hostaddress due to network misconfiguration problems.


User response: Please verify your network and DNSconfiguration are setup correctly. Note that on UNIXmachines the hostname must be reported correctly (thesame) for IPv4 and IPv6 communication methods in the/etc/hosts configuration file. See your systemadministrator or TSM administrator for further help.

ANS2223W Rejected unauthenticatedserver-initiated session from peer name.

Explanation: For security, the client will not acceptserver-initiated sessions from servers that haveauthentication turned off.

System action: The client-server session is not opened,and the schedule is not executed. The schedulercontinues to wait for contact by a server that hasauthentication turned on.

User response: If the client system is supposed toaccept scheduled events from the prompting TSMserver, either ask the TSM server administrator to turnauthentication on, or do not use server-initiatedsessions.If the client system is not supposed to accept scheduledevents from the prompting server, ask the TSM serveradministrator to remove the client node name from theschedule on the prompting server.

ANS2225W User has specified 'SNAPSHOTROOT'option. snapshot provider snapshot backupis not valid in conjunction with thisoption."SNAPSHOTROOT option will takeprecedence and processing will continuewithout the use of a snapshot takeninternally by TSM.

Explanation: The (-SNAPSHOTROOT) option isincompatible with TSM snapshot providers such asLogical Volume Snapshot Agent, VSS snapshotprovider, JFS2 snapshot provider etc. which provide acomprehensive snapshot solution withot having to usethe (-SNAPSHOTROOT) option. It is stronglyrecommended that the snapshot capabilities providedby the TSM snapshot providers be used instead ofusing the (-SNAPSHOTROOT) option. Processing willcontinue without the use of the TSM snapshotproviders.

System action: Processing continues without the useof the TSM snapshot providers.



User response: See the appropriate Using theBackup-Archive Client book for your operating systemfor correct use of the named option.

ANS2227W Server option 'option-name' 'option-value'has not been applied on the client dueto the client optionSRVOPTSETENCRYPTIONDISABLED.

Explanation: The client optionSRVOPTSETENCRYPTIONDISABLED has been set toYES on the client thereby preventing the TSMadministrator from setting one of the following clientoptions - ENCRYPTKEY GENERATE,EXCLUDE.ENCRYPT, INCLUDE.ENCRYPT.

System action: The option will be ignored.

User response: None required.

ANS2228W Backup of VMware vCloud DirectorvApp 'vApp name' in Organization VDC'Org VDC name' of organization 'Orgname' completed. Some VMs were notbacked up. VMs: number of VM backed upout of number of VMs in vApp VMsbacked up successfully.

Explanation: The vApp backup operation completedsuccessfully. However, one or more VMs for thespecified vApp were not backed up. These VMs willnot be created during the restore operation.

System action: Processing continues to the next vApp.

User response: Check the log file for this vApp formore information about this message. Resolve theproblem, then try the operation again.

ANS2229E Failed to initialize the vCloud protectionenvironment. See the local client errorlog for detailed error messageinformation.

Explanation: The vCloud protection package couldnot be initialized.


User response: Make sure all options that are relatedto the vCloud environment are specified correctly.Check the dsmerror.log file for detailed information.

ANS2230E Failed to create vApp list according tospec 'vApp specification'

Explanation: The vApp list was unable to be retrievedfrom the vCloud Director.


User response: Make sure the values specified in theVCDHost, VCDUser, VCDPW, and DOMAIN.VCD

options are correct. Make sure the vCloud Director isalive.

ANS2232E Failed to retrieve the list of VMs forvApp 'vApp name' from the vCloudDirector.

Explanation: The VM information for the specifiedvApp was not retrieved from the vCloud Director. Thisfailure might be caused by the vCloud Director notbeing alive or accessible.

System action: The VMs that compose the specifiedvApp are not backed up. Processing continues to thenext vApp.

User response: Make sure that the vCloud Director isalive and accessible. Check the dsmerror.log file forspecific errors that are related to this issue.

ANS2234W Restore from virtual machine backup isnot available for item'.

Explanation: Restore from virtual machine backup isnot supported for the following items:

v Databases with files located on the dynamic disks,GUID Partition Table (GPT) disks, iSCSI disks orother Network Attached Storage devices.

v Exchange databases in dismounted state duringvirtual machine backup.

v Exchange databases in unhealthy state or withunhealthy database copies.

v Exchange databases in unknown state if TivoliStorage Manager is not able to determine databasehealth status during virtual machine backup.

System action: The backup operation of the full VMcontinues.

User response: Take one or more of the followingactions to resolve the issue:

v Mount the dismounted databases before virtualmachine backup.

v Repair databases in unhealthy states.

v Use the VMTSMVSS trace flag on data mover totrace database health status processing during virtualmachine backup operations.

ANS2236I The virtual machine 'VM-name' containsone or more disks that exceed the 2 TBmaximum size limit. These disks will beexcluded from the backup.

Explanation: The IBM Tivoli Storage Manager clientdoes not support backing up VMDKs that are greaterthan the supported limit.

System action: The virtual machine is backed up,however the disks exceeding the limit are skipped.



ANS2238E VCDHOST option must be set beforerunning this operation.

Explanation: VCDHOST option is missing.

System action: Operation cannot continue without thisoption being set.

User response: Add the option to the client optionsfile, either via the preferences editor or by manuallyediting the file, or specify the option on the commandline.

ANS2239W The annotations field contained toomany characters and had to betruncated.

Explanation: vSphere limits the size of the annotationsto 2000 characters. Some special characters, such asnew lines, get encoded as multiple characters. This canlead to exceeding the limit even though the size mayappear to be within the limit.

System action: The annotation field is truncated toless than 2000 characters so that the vSphere API willnot reject it.

User response: Take care to avoid creating largeannotations that may exceed the 2000 character limitafter special characters are encoded.

ANS2240T The basic verification of vApp 'vAppname' succeeded.

ANS2241T The extended verification of vApp 'vAppname' succeeded.

ANS2242E No nodes were found that matched theinput specification: node specification

Explanation: An invalid node specification wasentered.

System action: The operation was stopped.

User response: Check documentation how to specifynodes.

ANS2244W The virtual machine contains one ormore disks that exceed the maximumsize limit. Specify the'-VMSKIPMAXVMDKS=yes' option toexclude these disks from the backup.



User response: Specify the'-VMSKIPMAXVMDKS=yes' option to exclude thesedisks from the backup.

ANS2245E Virtual machine backups and restoresare not supported on 32 bit data movers.

Explanation: Virtual machine operations such asbackups and restores are not supported on 32 bit DataMovers.

System action: The operation is not performed.

User response: Update to a 64 bit Data Mover andretry the operation.

ANS2246W Failed to disable maintenance mode forvApp vApp name.

Explanation: The client has tried to disable themaintenance mode of this vApp. This operation failed.


User response: Check whether the vApp is still inmaintenance mode. If yes, disable it manually.

ANS2247E ASNODENAME option must bespecified when running this command.

Explanation: When running vCloud-relatedcommands, ASNODENAME option must specify theProvider vDC node.

System action: Operation cannot continue.

User response: Specify the Provider vDC node asASNODENAME to the command.

ANS2248E Failed to load or initialize the Javaruntime library.

Explanation: The Java runtime library (libjvm),required by the vCloud Protection environment, cannotbe loaded, or initialization of Java runtime environmentfailed

System action: Operation is stopped

User response: For Linux operating system, verify thata link named 'jre', referencing the 'jre' directory underyour Java installation path, exists in the backup-archiveclient installation directory. If a link does not exist,create the link (e.g. ln -s /opt/ibm/java-x86_64-70/jre/opt/tivoli/tsm/client/ba/bin/jre). Alternatively,modify LD_LIBRARY_PATH to include the path tolibjvm.so (e.g. exportLD_LIBRARY_PATH=$LD_LIBRARY_PATH:/opt/tivoli/tsm/client/ba/bin:/opt/ibm/java-x86_64-70/jre/bin/classic). For Windows operating system, verify thatthe JRE directory exists under the client installationdirectory. Reinstall the backup-archive client ifnecessary.



ANS2249W A virtual machine named 'vmname' existson this system.Do you want to replace the existingvirtual machine?

Explanation: Restoring this virtual machine will stopand delete the existing virtual machine and all of itsfiles. To protect application data, stop any applicationsthat are running, and then shut down the virtualmachine before you restore it.

System action: If the user chooses to continue, thesystem will stop and delete the existing virtual machineand all of its files.

User response: Choose whether to replace the existingvirtual machine.

ANS2250W A TSM core file or crash report wasfound: filename

Explanation: The presence of a core dump or crashreport indicates a process has abnormally terminated.

System action: The core file or crash report name isreported in the message. Processing continues.

User response: Review the error log for any othererror messages that may help diagnose the cause of thecore dump. If possible, correct any issues found. As acore dump is generally caused by a programming error,save the file noted in this message and contact IBMtechnical support.

ANS2253W The version of the message catalog,catalogversion, in use by TSM does notmatch the version of TSM, clientversion

Explanation: A check of the catalog version indicatesthe catalog and TSM are not the same version. Thismay lead to missing or incorrect messages being used.


User response: Review the installation of TSM, verifythe message catalog files match the installed version ofTSM. Re-installation of TSM may be required, or asystem reboot may be required to complete theinstalltion.

ANS2254E program-name with session id sessidaborted recall for token token. ERRNOerrno : errno-text was set. See messageexplanation.

Explanation: A recall was aborted from HSM. TheERRNO set from HSM explains why the recall wasaborted.Transient errors (The operation must be retried after theassociated problem was solved):ENOSPC : No space left on device. HSM couldn't freespace for the recall.ENOMEM : Not enough memory available to acquirethe required resocurces for the recall.

ESRCH : The internal communication between masterand distributor failed.EACCES : Most common errno. One of the failuresbelow:- The recall daemon are exiting. System cleanupongoing.- Recovery of previously failed nodes is ongoing.- File is immutable and can't be opened for write /truncate.- The HSM internal processing failed due to issues withthe DMAPI.EBUSY : HSM can't acquire exclusive rights on the file.EFAULT : The system detected an invalid address inattempting to use an argument.EINTR : The DMAPI implementation allowsinterruption and the process was interrupted.EINVAL : The requested right is not valid or thesession or token is not valid or token wasDM_NO_TOKEN.Static errors (The operation can't be fullfilled. Recall notpossible):EIO : The stub file is orphan.ENOENT : The file doesn't exist in the file system.EBADF : The file handle does not refer to an existing oraccessible object.

System action: The recall request was aborted fromthe HSM service.

User response: Transient errors:Solve problem indicated from the errno. On GPFSplatforms: Use command dsmmigfs q -d -n=all toverify HSM and GPFS are running properly.Retry the recall operation if failed file can be identified.Enable HSM Logging if failed failed file cannot beidentified and wait for new occurrence.(HSM Logging allows you to map between the tokendisplayed from the ANS message and the recalled file)Static errors:Restore the file from backup.

ANS2260E Failed to lock TSM password file.

Explanation: In multi-process environment TSM clientlocks the password file during authentication to avoidconflicts on updating password in case the currectpassword is expired.

System action: processing stops

User response: Try to use MAXRETRIESLOCK testflag to increase number of attempts to lock the file. Thedefault value is 1500.

ANS2261E TSM client failed to lock options file.

Explanation: In multi-process environment TSM clientlocks the options file during initialization to avoidconflicts on reading or adding an option.

System action: processing continue

User response: Try to decrease a number of TSMclient processes



ANS2262I The service is starting.

Explanation: The file restore service is starting.



ANS2263I The service started.

Explanation: The file restore service started.



ANS2264I The shutdown is in progress.

Explanation: The shutdown is in progress.



ANS2265I The service is shutting down.

Explanation: The file restore service is shutting down.



ANS2266I The option 'option-name' is set to thedefault value of 'default-value'.

Explanation: An error was detected with the optionvalue.

System action: The default setting is used.

User response: To use a non-default value, correct theoption value in the frConfig.props file.

ANS2267W The 'option-name' option value'invalid-value' is invalid.

Explanation: An error was detected with the optionvalue.

System action: The default setting is used.

User response: To use a non-default value, correct theoption value in the frConfig.props file. Then, restart theweb server that is hosting the file restore interface.

ANS2268W The TCP/IP port address on the mountproxy node cannot be located or isinvalid.

Explanation: The mount proxy node requires aTCP/IP port address. This address is used forcommunication by the client acceptor on the mountproxy node.

v If a local mount proxy node is used, the TCP/IP portaddress that was specified with the configurationwizard or notebook is invalid.

v If a remote mount proxy node is used, thedefault_mp_httpport option in the frConfig.props fileis either not specified or is invalid.

Communication with the client acceptor cannot start.


User response: If a local mount proxy node is used,use the Mount Proxy Node Pairs page in theconfiguration wizard or notebook to remove the mountproxy node. Then, add the mount proxy node again toresolve this issue.

If a remote mount proxy node is used, ensure that thedefault_mp_httpport option is specified in thefrConfig.props file with a valid TCP/IP port address.

ANS2269E The maximum number of backups wereloaded. If a restore is running, wait forit to complete and load the backupagain. If the backup is loaded inanother browser window, close thatbrowser.

Explanation: To mount another backup, one of themounted backups must be dismounted.


User response: Dismount one of the mounted backupsand try the operation again.

ANS2309I Single Sign On login to the vSphereServer failed in function function.API message A credential login is nowattempted.

Explanation: The Single Sign On (SSO) login to thevSphere Server failed. Possible reasons for this failureinclude the following situations:

v A time difference exists between the vSphere Serverclock and the client clock that exceeds 10 minutes.

v The SSO server accesses a non-default port. Thisissue can occur when the SSO server is installed onthe same system as the VMware vCenter.

System action: The system attempts a credential loginas a result of the SSO login failure.

User response: Check the dsmerror.log file for detailsabout why the SSO login attempt failed. Then, take anycorrective action, if needed.

ANS2310E The create snapshot task is disabled onthe virtual machine 'VM-name'. As aresult, the virtual machine cannot bebacked up.

Explanation: Virtual machines that are managed orreplicated by another application disable the createsnapshot task. The vSphere client or anotherapplication disabled the create snapshot task on this



virtual machine. As a result, this virtual machinecannot be backed up.

System action: The backup operation skips the virtualmachine with the disabled create snapshot task andcontinues processing the remaining virtual machines.


ANS2311E The create snapshot task is disabled onthe virtual machine. As a result, thevirtual machine cannot be backed up.

Explanation: Virtual machines that are managed orreplicated by another application disable the createsnapshot task. The vSphere client or anotherapplication disabled the create snapshot task on thisvirtual machine. As a result, this virtual machinecannot be backed up.

System action: The backup operation skips the virtualmachine with the disabled create snapshot task andcontinues processing the remaining virtual machines.


ANS2312E -DELTYPE=ALL is not allowed forDELETE BACKUP -OBJTYPE=VM.

Explanation: DELTYPE=ALL is not a valid optionvalue when deleting VM backup objects.

System action: The command is not executed.

User response: If you wish to delete all backups for aVM node, use the DELETE FILESPACE command.

ANS2313E -FILELIST is not allowed for DELETEBACKUP or EXPIRE when-OBJTYPE=VM.

Explanation: -filelist is not a valid option value whendeleting or expiring VM backup objects.


User response: If you wish to delete or expire allbackups for a VM node, use the DELETE FILESPACEcommand.

ANS2314E No VM backup exists for VM-Name.

Explanation: The TSM server has no record of a VMbackup for the VM name provided. The backup mighthave been deleted, or the VM name spelled incorrectly.


User response: If spelling is the problem, correct itand resubmit the command.

ANS2315E -PICK is not allowed for EXPIRE when-OBJTYPE=VM.

Explanation: -pick is not a valid option value whenexpiring VM backup objects.


User response: If you wish to expire all VM nodes,use the DELETE FILESPACE command.

ANS2316E Wildcards are not allowed in the VMname argument.

Explanation: When expiring or deleting a VM backup,the VM name must be specified exactly. The EXPIRE-OBJTYPE=VM command processes only one backupon each invocation. When -INACTIVE is present theDELETE BACKUP -OBJTYPE=VM command displaysall versions of a single VM backup in a list from whichto choose. If -INACTIVE is not present, this commandexpires the current active VM backup.


User response: Specify only one VM name withoutwild cards. It may be in upper or lower case.

ANS2317E Deletion of VM object VMname failed.Reason:

Explanation: The transaction which deletes the namedVM object failed at the server. The reason code ....?????

System action: The deletion is skipped and processingcontinues with the next selection, if any.

User response: Consult the error log for specificreasons for this failure.

ANS2318E Command with -OBJTYPE=VM requiresexactly one non-option argument

Explanation: This command accepts only a single VMname as an argument. Either no arguments wereentered or more than one appeared on the commandline.


User response: Specify only one VM name withoutwild cards. It may be in upper or lower case.

ANS2319W DELETE BACKUP -OBJTYPE=VMfinished with failures.

Explanation: One or more deletions failed.

System action: The VM backups which failed havebeen reported in previous messages. Processingcontinues with the next selection, if any.

User response: Consult the previous error messagesfor the cause of each failure.



ANS2320I DELETE BACKUP -OBJTYPE=VMfinished without failures.

Explanation: All VM backups selected for deletionwere deleted.

System action: Control returns to the command line.

User response: No action is required, this message isinformational.

ANS2321W EXPIRE with -OBJTYPE=VM finishedwith failures.

Explanation: The command did not complete, noobjects were expired.

System action: The VM expire which failed has beenreported in previous messages.

User response: Consult the previous error messagesfor the cause of the failure.

ANS2322I EXPIRE with -OBJTYPE=VM finishedwithout failures.

Explanation: The EXPIRE command executedsuccessfully.

System action: Control returns to the command line.

User response: No action is required, this message isinformational.

ANS2323E The user ID and password for VMwarevCloud Director 'vCD host name' are notset.

Explanation: The user ID and password for VMwarevCloud Director could not be read from encryptedpassword file.


User response: Issue the dsmc SET PASSWORD-type=VCD 'vCloud Director hostname' 'userid''password' command to save an encrypted password.

ANS2324W WARNING: The VMware vCloudDirector user ID <hostuserid> read fromthe password file is different from theVCDUser option value <vmcuserid>.Using stored value.

Explanation: All user IDs that are specified in theTSM.PWD file and in the VCDUSER option must bethe same.


User response: Contact the TSM administrator withthe information that is provided in this message.

ANS2325E Error Accessing Snapshot DifferentialChange Log for filer '' volume '', seeclient error log for more information.

Explanation: The Snapshot Differential Change Logneeded needed to backup the specified filer volumecould not be accessed

System action: The backup of the specified volumefails.

User response: Ensure that the client staging directorywhere change logs are located is accessible.

ANS2326W Corrupt Snapshot Differential ChangeLog detected, change log will be resetand a full progressive incremental willbe performed.

Explanation: A corrupt snapshot differential changelog for the filer volume being backed up was detected.

System action: The change log will be reset and a fullprogressive incremental with a new base snapshot willbe performed.


ANS2327I Creating Snapshot Differential ChangeLog.

Explanation: A new snapshot differential change logwas created.



ANS2328I Using Snapshot Differential ChangeLog.

Explanation: A snapshot differential change log isbeing used for the backup.



ANS2329W Down level Snapshot DifferentialChange Log detected, Change Log willbe reset and a full progressiveincremental will be performed.

Explanation: none.

System action: none.




ANS2330E Failed to unfreeze the VSS writersbecause the snapshot time exceeded the10 second timeout limitation.

Explanation: Microsoft VSS has a 10 second timeoutlimitation between freeze and thaw events for VSSwriters on a VM. When the snapshot time exceeds the10 second timeout limit, the VSS writers return to a'failed' state. This failed state occurs because the VSSprovider did not thaw the VSS writers within theallowed time.


User response: Check the event log. Ensure that thewriters on the guest VM are in 'stable' state beforetrying an application protection VM backup operationagain. A snapshot operation must be completed within10 seconds.

ANS2331W No match found on the server for theHyper-V VM name or VMList 'string'entered

Explanation: No match found on the server for theHyper-V VM name or VMList parameter entered.


User response: Specify another Hyper-V VM name orVMList parameter that exists on the server.

ANS2332E Failed to log on to the vCloud Director.Authentication failed.

Explanation: The vCloud credentials were rejected bythe vCloud Director.


User response: Update username and password forthe vCloud Director.

ANS2333E Failed to establish connection to thevCloud Director.

Explanation: A connection cannot be established tothe vCloud Director on the host that is specified by theVCDHost and VCDPort options.


User response: Verify that the values of the VCDHOstand VCDPort options are valid, network connectivity tothe host exists, and that the vCloud Director service isrunning.

ANS2334E An operation requiring the WindowsManagement Instrumentation (WMI)service has failed with the error'errorstring'. Unable to connect to theHyper-V namespace. Confirm thatHyper-V is installed on the backupnode.

Explanation: The Windows ManagementInstrumentation (WMI) namespace"root\virtualization\v2" for Hyper-V could not befound. This namespace is installed with Hyper-V. IfHyper-V is installed, Hyper-V is not in a good state.

System action: Creating a connection to the Hyper-VWMI provider.

User response: Check that Hyper-V is installed. IfHyper-V is not installed, install Hyper-V beforeattempting this operation again.

ANS2335E An operation requiring the WindowsManagement Instrumentation (WMI)service has failed with the error'errorstring'. The WMI service is in theshutting down or shutdown state.Restart the service and try again.

Explanation: The Windows ManagementInstrumentation (WMI) service has received a requestto shutdown or has been shutdown due to an externalerror. An internal operation which requires WMI hasbeen attempted and failed. The requested operation isunavailable while WMI is shutdown.

All Hyper-V operations require the WindowsManagement Instrumentation service.

System action: An internal TSM operation involvingWindows Management Instrumentation has occurred.

User response: Restart the Windows ManagementInstrumentation service.

ANS2336W TSM has detected that the followingHyper-V virtual machine"virtual_machines" has an interruptedincremental backup chain. Performing afull backup on the specified Hyper-Vvirtual machine.

Explanation: The last operation of the virtual machinewas a restore; or an unknown party has performedincremental backup operations on the listed virtualmachine. To prevent backup corruption a full backupwill be performed instead.

System action: TSM has detected that a virtualmachine has an interrupted incremental backup chains.

User response: A full backup is performed instead ofan incremental.

ANS2337E TSM was unable to take cluster resource'resourcename' offline. The currentoperation requires the resource to beoffline. Turning the cluster resource offfailed with rc=rc.

Explanation: The cluster resource was not takenoffline within the time limit or an attempt was made totake offline a failed cluster resource.




User response: Check that the cluster resource is notin a failed state. Verify that the cluster resource can betaken offline.

ANS2338W TSM has detected a request to backup avirtual machine replica. The state of thereplica 'vmreplicaname', ID='vmid' maydiffer from the original virtual machine.If the names of the original virtualmachine and the replica are identical thesame filespace will be used. The datamay become unrecoverable because thestate of the original virtual machine andthe replica may differ.

Explanation: Backups of an original virtual machineand their replica overwrite each other as their nameand ID are usually identical. Virtual machine replicasare taken in definite time intervals. Between theseintervals the data on the original and the replica maydiffer. In some occasions the difference may cause datacorruption if a backup of the original is followed by abackup of the replica.

System action: A backup request of a virtual machinereplica is being processed.

User response: Configure IBM Tivoli Storage Managerto back up only the original virtual machine or thereplica. Alternatively, one can change the name of thereplica compared to the original virtual machine; andthe replica will back up to a separate filespace.

ANS2339W The Hyper-V VM 'vmname' is in a"branch" state compared to the lastbackup. Incremental Forever -Incremental backup cannot beperformed. An Incremental Forever -Full backup will be performed instead.

Explanation: The VM state is in a "branch" comparedto the last backup. This causes a fallback to IncrementalForever - Full as backup consistency in this state is notguaranteed.

System action: An Incremental Forever - Full backupwill be performed.


ANS2340W The target virtual machine 'VM-name'exists, use the REPLACE option tooverwrite.

Explanation: The specified target VM exists and theuser specified not to allow restore to replace existingmachines.

System action: The virtual machine is not restored.

User response: Specify a different virtual machine as a

restore target or specify that existing virtual machinescan be replaced.

ANS2341E The target virtual machine 'VM-name'cannot be restored: The guid differsfrom the backup copy.

Explanation: The specified target VM exists and has adifferent guid than the virtual machine was backed upwith..


User response: Specify a different virtual machine as arestore target or delete the specified target virtualmachine.

ANS2342E The specified restore target 'VM-name' isambiguous: Multiple virtual machineswith the same name exist.

Explanation: The specifed restore target is ambiguous,multiple virtual machine with the same name exist.


User response: Specify a different virtual machine as arestore target.

ANS2343E A snapshot of Virtual machine 'vmname'cannot be taken because a physical diskattached.

Explanation: The Volume Snapshot Service (VSS) isunable to snapshot a virtual machine with a physicaldisk.

System action: The full backup of the the virtualmachine finished with failures. The next virtualmachine in the backup will be processed.

User response: Do not include this virtual machine indomain.vmfull for backup. A snapshot of this virtualmachine cannot be taken.

ANS2344E 'drive-name1' is a disk witness.

Explanation: The indicated volume is a disk witness.Because the CLUSTERNODE option is set to YES, thevolume cannot be backed up or archived.





ANS2345W The virtual machine named '' was foundto have an old snapshot ''. A commandwas sent to the vCenter to remove it.

Explanation: During the snapshot clean-up process thebackup-archive client found old snapshots on thevirtual machine. A remove snapshot command was sentto the VMware vCenter to remove the old snapshots.


User response: Confirm that the the virtual machine isfree of all snapshots before the next scheduled backup.

ANS2346E Expiration of VM object VMname failed.Reason:

Explanation: The transaction which expires the namedVM object failed at the server. The reason code ....?????

System action: The expiration is not completed.

User response: Consult the error log for specificreasons for this failure.

ANS2347E IBM Tivoli Storage Manager applicationprotection cannot be used. The correctJava Runtime Environment version hasnot been detected on machine. A JavaRuntime Environment version or higheris required to run this program. If youhave already installed this level of Javaversion on this machine, please ensurethat the correct Java executable is onyour PATH and start the program again.

Explanation: IBM Tivoli Storage Manager applicationprotection vm backup cannot be started because theJava runtime environment does not meet therequirements.


User response: Verify that the correct java executableis on your PATH or install the required version of Javaruntime environment and run the backup again.

ANS2348E Mount proxy host 'remoteversion' doesnot have a supported operating system.

Explanation: The mount proxy node needs to beconfigured on a supported operating system.

System action: The calling procedure returns andcontrol is passed back the user.

User response: Check the documentation for a list ofsupported operating systems. Configure the mountproxy node on a supported operating system.

ANS2349W The virtual machine named '' was foundto need snapshot consolidation. Acommand was sent to the VMwarevCenter to perform consolidation.

Explanation: During the virtual machine backupprocess the backup-archive client found the virtualmachine needed snapshot consolidation. A commandwas sent to the VMware vCenter to performconsolidation.


User response: Confirm that the virtual machine isclean of all snapshots and snapshot delta files beforethe next scheduled backup.

ANS2350E Virtual machine 'VM name' will not bebacked up because it contains at leastone of the following unsupportedspecial characters \ / : ; , * ? " ' < > |

Explanation: The specified virtual machine containscharacters that are not supported for virtual machinebackup and restore operations.

System action: The backup for the specified virtualmachine fails.

User response: Rename the virtual machine so that itdoes not contain any of the specified special characters.

ANS2351E Duplicate virtual machine name'vmname' was detected in the samebackup operation. Backups of a virtualmachine can not continue without aunique object name.

Explanation: The backup of the virtual machine failedbecause no unique object name is available.

System action: The backup for the specified virtualmachine fails. The next virtual machine to back up willbe processed.

User response: Rename the virtual machine so that itis unique among virtual machines for the node.

ANS2352E Validation of virtual machine 'vmname'configuration returned the followingmessage from Hyper-V:hypervmessageThis message indicated that the virtualmachine could not be restored until themessage from Hyper-V is addressed.

Explanation: When validating the virtual machinewith Hyper-V a message was returned that preventsthe virtual machine restore from continuing.

System action: Cannot continue with restore until theissue is resolved.



User response: Resolve the issue outlined by themessage.

ANS2398I The virtual machine 'VM-name' isconfigured as a VMware Site RecoveryManager placeholder virtual machine onthe recovery site. As a result, the virtualmachine will be skipped.

Explanation: VMware Site Recovery Manager createsplaceholder virtual machines that have no virtual diskdata. As a result, these virtual machines cannot bebacked up.

System action: The backup operation skips theplaceholder virtual machine and continues processingthe remaining virtual machines.

User response: None

ANS2399I The virtual machine is configured as aVMware Site Recovery Managerplaceholder virtual machine on therecovery site. As a result, the virtualmachine will be skipped.

Explanation: VMware Site Recovery Manager createsplaceholder virtual machines that have no virtual diskdata. As a result, these virtual machines cannot bebacked up.

System action: The backup operation skips theplaceholder virtual machine and continues processingthe remaining virtual machines.

User response: None

ANS2408I The virtual machine named 'VMNAME'is ready for Instant Access

Explanation: The Instant Access operation for thespecified virtual machine successfully completed.


User response: None

ANS2409E The Instant Restore type was notidentified.

Explanation: The client encountered a connectionerror when querying the Tivoli Storage Manager serverfor Instant Restore and Access information.


User response: Verify that the client is connected tothe server. Then run the operation again. Check withthe command QUERY SESSION what is the cause forthe connection issue. Also check the dsmerror.log foradditional information

ANS2410E Instant Restore information for thespecified virtual machines was notfound.

Explanation: The Tivoli Storage Manager server doesnot contain Instant Restore information for the specifiedvirtual machines. Or, the virtual machines werespecified incorrectly.


User response: Issue the QUERY VM *-VMRESTORETYPE=ALLTYPE command. Thiscommand queries all active Instant Access, Restore, andDisk sessions available on the Tivoli Storage Managerserver.

ANS2411E Instant Restore/Access of virtualmachine 'vmname' failed with rc =return-code

Explanation: An error happened during processing ofan Instant Restore or Access. See previous output whathappens exactly.


User response: Check the error log for informationabout how to resolve this error.

ANS2412E IBM Tivoli Storage Manager RecoveryAgent is not installed.

Explanation: IBM Tivoli Storage Manager RecoveryAgent is not installed.


User response: Ensure that IBM Tivoli StorageManager Recovery Agent is correctly installed andconfigured.

ANS2413E Cannot find the Recovery Agent shellcommand in the expected installationpath.Ensure that TSM for VE is correctlyinstalled and configured.

Explanation: The Recovery Agent shell command wasnot found in the expected installation path.


User response: Ensure that TSM for VE is correctlyinstalled and configured.

ANS2414E An error occurred when the hostnamefor the local machine was called.

Explanation: The system call gethostname failed.


User response: Verify that the configuration of thenetwork interface is correct.



ANS2415E An error occurred when the machineaddress information was called.

Explanation: The system call getaddrinfo failed.



ANS2416E An error occurred when the machinename information was called.

Explanation: The system call getnameinfo failed.



ANS2417E Unexpected communication method.Only TCP and TCPv6 are accepted.

Explanation: An unexpected communication methodwas detected.


User response: Verify that the communication methodfor Tivoli Storage Manager is correct. Use either TCP orTCPv6.

ANS2418E Unable to read or write to the localinstant restore data.filenameFile cannot be accessed or is damaged.

Explanation: Instant access and instant restoreoperations require read/write access on the local datamover to store data.


User response: To store the instant restore restoredata, the data mover application requires read andwrite access to the C:\Documents andSettings\AllUsers\Application Data\Tivoli\TSM\ orC:\ProgramData\Tivoli\TSM folder.Set the access rights to this directory so that your userhas the correct rights.If the file was damaged it can be helpfull to replace thecurrent version with the .bak file.

ANS2419E The datastore does not have enough freespace for the instant restore operation.

Explanation: The space on the selected datastore is notsufficient for the instant restore operation.


User response: Increase the datastore space or choosea different datastore.

ANS2420E Cannot detect storage deviceinformation.

Explanation: Storage device information cannot beretrieved.


User response: Ensure that the communication withthe ESX host is working. Also, review the log messageson the ESX host.

ANS2421E Cannot detect the iSCSI initiator on theESXi host.

Explanation: The iSCSI initiator name of the ESXi hostcannot be detected.



ANS2422E Cannot detect the iSCSI Host BusAdapter.

Explanation: The iSCSI adapter was not detected.



ANS2424E Cannot find the ESX host 'ESXHOST' inthe vCenter.

Explanation: The specified ESX host cannot be foundin the vCenter.


User response: Ensure that the specified ESX host is inthe vCenter. Ensure that the name of the ESX host iscorrect. Alternatively, specify another ESX host.

ANS2425E Cannot connect to the ESX host'ESXHOST'

Explanation: A connection to the specified ESX hostcannot be made


User response: Ensure that the specified ESX host isconnected to the vCenter and the network.Alternatively, specify another ESX host.

ANS2426E The ESX host 'ESXHOST' is not poweredon.

Explanation: The specified ESX host is not poweredon.




User response: Turn on the power to the ESX host.Alternatively, specify another ESX host.

ANS2427E The ESX host 'ESXHOST' is inmaintenance mode.

Explanation: The specified ESX host is in maintenancemode. A connection cannot be made to this host.


User response: Change the ESX host back to normalmode and try again. Alternatively, specify another ESXhost.

ANS2428E The ESX host 'ESXHOST' is notconnected.

Explanation: The specified ESX host is not connectedin the vCenter.


User response: Connect the ESX host in the vCenterand try again. Alternatively, specify another ESX host.

ANS2430E Cannot find the datacenter'DATACENTER'.

Explanation: The specified Datacenter cannot befound in the vCenter.


User response: Ensure that the specified datacenter isin the vCenter. Alternatively, specify another datacenter.

ANS2431E Cannot find the temporary datastore'TEMPDATASTORE' on the ESX host'ESXHOST'.

Explanation: The specified temporary datastore cannotbe found on the specified ESX host.


User response: Ensure that the specified datastore ison the ESX host. Alternatively, specify anotherdatastore.

ANS2432E The temporary datastore'TEMPDATASTORE' is the same as thetarget datastore 'DATASTORE'.

Explanation: The specified temporary datastore mustbe a different datastore than the one where the machineis restored to. You must specify two different datastoresfor Storage vMotion to work.


User response: Specify another datastore as atemporary datastore.

ANS2433E The '-vmtempdatastore' option must bespecified for an instant restoreoperation.

Explanation: You must specify two differentdatastores for Storage vMotion to work. Use the'-vmtempdatastore' option to specify a temporarydatastore.


User response: Specify a temporary datastore.

ANS2434E The datastore 'DATASTORE' was notfound on the host 'ESXHOST'.

Explanation: The specified datastore cannot be foundon the ESX host.


User response: Ensure that the specified datastore ison the ESX host. Alternatively, specify anotherdatastore.

ANS2435E IBM Tivoli Storage Manager RecoveryAgent detected the following failurewhileattempting to mount a snapshot of VM'VM' from disc='disk-label':FBCxxxxE-error-message

Explanation: The attempt to mount a VM disk as aniSCSI device failed.


User response: Check the Recovery Agent logs andthe FBCxxxxE error message, resolve the problem, andtry the operation again.

ANS2436E IBM Tivoli Storage Manager RecoveryAgent detected the following failurewhiletrying to dismount a snapshot of VM'VM' from target 'target':FBCxxxxE-error-message

Explanation: The snapshot for the specified VM couldnot be dismounted from the iSCSI target.


User response: Check the Recovery Agent logs andthe FBCxxxxE error message, resolve the problem, andtry the operation again.

ANS2442W The Linux mount proxy nodeinformation is not available.

Explanation: The Windows mount proxy was unableto retrieve its partner Linux mount proxy nodeinformation.



System action: A connection to the Linux mountproxy is not established.

User response: Ensure that the Linux mount proxynode is set up and the DSMCAD service is running onthe Linux mount proxy node. Then, try this operationagain.

ANS2444E Cannot find the datacenter for host'ESXHOST'.

Explanation: Unable to determine the datacenterwhere the ESX host is located.


User response: Check that the vCenter of the ESX hostis in a datacenter and that the user has the properauthority to access this information.

ANS2445E Virtual machine 'VM' is running. Youcannot delete this VM.

Explanation: You cannot delete a virtual machine thatis running.


User response: Ensure that you have the properauthority to power off virtual machines, then power offand delete the VM.

ANS2447E Failed to delete VM 'VM' from the ESXhost.

Explanation: You cannot delete the virtual machineform the ESX host.


User response: Ensure that you have the properauthority to delete virtual machines, then delete theVM.

ANS2448E Mount command failed.Command wasCOMMANDShell command returned:RESULT

Explanation: The TDP mount command was notsuccessful.


User response: Determine the problem from theinformation that was returned for the TDP mountcommand. Resolve the problem, then run the commandagain.

ANS2452E num_discovered iSCSI devices werediscovered on the ESX host, whilenum_mounted were expected.

Explanation: After the ESX host bus adapter wasscanned, the number of devices that were discovered isdifferent from the number of mounted devices.

System action: The Instant Restore or Instant Accessprocess is stopped.

User response: Verify that the Tivoli Storage Managermount is configured to use the correct ESX host IP. Toclean the environment, you must run the cleanupprocess.

ANS2453E An error occurred when the host busadapter was scanned.

Explanation: An error occurred when the ESX hostbus adapter was scanned.

System action: The Instant Restore, Instant Access, orcleanup process is stopped.

User response: Run the cleanup process after you fixany problems with the ESX host bus adapter.

ANS2454E An error occurred when the iSCSI targettarget_name was disconnected from theESX host bus adapter.

Explanation: An error occurred when a specific iSCSItarget was disconnected from the ESX host bus adapter.

System action: The cleanup operation is stopped.

User response: Run the cleanup process after you fixany problems with the ESX host bus adapter.

ANS2455I The virtual machine has been started.You can use the machine after it hasbooted, or you can connect to it andmanage its settings through the vCenterconsole.

Explanation: The virtual machine is being started.


User response: While the boot is in progress, you canconnect to the virtual machine and view or manageBIOS settings, manage the bootloader options, orperform other tasks. After the boot process completes,you can use the virtual machine and its applicationsand resources.

ANS2462E Unable to start the vMotion task forvirtual machine 'vm_name'.

Explanation: An instant restore of the specified virtualmachine was attempted but failed. The client could notstart a vMotion task to migrate the virtual machine.

System action: The Instant Restore operation stops.



User response: Examine the client dsmerror.log file tosee if a log entry indicates why the vMotion task failed.Additional information about the failure might also beavailable in the vCenter server, on the Task and Eventstab for the ESXi host that you were migrating the VMfrom. If possible, use the log and event records todetermine what caused the vMotion task to fail and fixit. Then, clean up the virtual machine (use the RestoreVM command with the -VMRESToretype=VMCLeanupoption) and restart the vMotion task. If you cannotrestart the task, suspend the virtual machine and usethe vSphere web client to start the virtual machinemigration from one host to another.

ANS2463W Instant Restore information cannot besaved on the server.

Explanation: An error occurred when Instant Restoreinformation was being saved on the server. The InstantRestore process is still running.

System action: The operation continues.

User response: The client dsmerror.log file mightcontain information to help troubleshoot the reason forthis error. Let the Instant Restore process complete onits own. You might need to run a clean up operation onthe virtual machine. Use the Restore VM command,and specify the -VMRESToretype=VMCLeanup option.

ANS2464E Unable to delete Instant Restoreinformation from the server.

Explanation: An error occurred while attempting todelete Instant Restore information from the server.

System action: The Instant Restore operationcontinues.

User response: The most likely reason for this error isthat an ANS2463W warning previously occurred, andthere is no data to delete. If you have not previouslyseen an ANS2463W message, the client dsmerror.log filemight contain information to help you troubleshoot thiserror. Clean up the virtual machine to remove oldinformation from the server. Use the Restore VMcommand, and specify the-VMRESToretype=VMCLeanup option.

ANS2465E An error occurred during a storagevMotion operation.

Explanation: A storage vMotion task failed whiletrying to migrate a running virtual machine.

System action: The Instant Restore operation stops.

User response: Examine the client dsmerror.log file tosee if a log entry indicates why the vMotion task failed.Additional information about the failure might also beavailable in the vCenter server, on the Task and Eventstab for the ESXi host that you were migrating the VMfrom. If possible, use the log and event records todetermine what caused the vMotion task to fail and fix

it. Then clean up the virtual machine (use the RestoreVM command with the -VMRESToretype=VMCLeanupoption) and restart the vMotion task. If you cannotrestart the task, suspend the virtual machine and usethe vSphere web client to start the VM migration fromone host to another.

ANS2466W If you continue you will lose all datacreated on this virtual machine.The virtual machine will also beremoved from the ESXi host.Are you sure that you want to do this?Press Y the virtual machine data andremove it from the ESXi host.Press any other key to continue withoutdeleting data or the VM.

Explanation: You are performing an operation that, ifallowed to continue, will delete all data that wascreated after this virtual machine was created.

System action: If Y is pressed, the Instant Restoreoperation is stopped, and a cleanup operation isperformed

User response: Respond to the prompt. Press Y todestroy all data and delete the virtual machine from theserver. Press any other key to continue withoutdeleting.

ANS2467W Unable to delete the snapshot that wascreated for the virtual machine named'vm_name'

Explanation: When a virtual machine is restored by aninstant restore operation, a snapshot is created to storeall data that were written to the virtual machine disks.When the restore is completed, the ESXi host deletesthe snapshot. The snapshot for the specified virtualmachine could not be deleted.


User response: Examine the vSphere log to determinewhy is it not possible to delete the snapshot andresolve the problems that prevent the deletion. Then,delete the snapshot by using the snapshot manager.

ANS2468E The necessary iSCSI targets could notbe found on the ESX host.

Explanation: An instant restore operation wasinitiated and one or more of the required iSCSI targetscould not be found on the ESXi host.


User response: Verify that the IP address that wasspecified with the -VMISCSISERVERADDRESSparameter is correct.



ANS2469E Unable to remove the iSCSI target.

Explanation: An error occurred while trying toremove an iSCSI target.


User response: Check vSphere client log file for thereason this operation failed and remove the iSCSItarget. To remove the failed iSCSI static targets go toyour ESXi host Configuration -> Storage Adapters ->Select the iSCSI Adapter -> right click on it -> ClickProperties -> Static Discovery and select the failediSCSI targets and remove them.

ANS2471E Unable to stop the vMotion Task 'task'.

Explanation: The specified vMotion task could not bestopped.

System action: The instant restore operation isstopped.

User response: Examine the vSphere log to determinewhy the migration cannot be stopped. Resolve theproblem and cancel the vMotion task. Then, use the-VMRESToretype=VMFULLCleanup option on theRestore VM command to remove any files or otherresources that were created by the instant restoreoperation.

ANS2472E Cannot detect the LUN for the attachedRDM devices for virtual machine namedvmname'.The restore operation for this virtualmachine cannot be completed.

Explanation: The LUNs for the RDM devices use bythe specified virtual machine are either missing, aremapped to an other machine, or the device name andthe LUN do not match.

System action: The restore operation is stopped.

User response: For restore operations wherevmrestoretype=instantrestore orvmrestoretype=instantaccess, verify that the iSCSIserver address and the VMkernel port binding match.Verify this information by checking the followingthings: 1. Check the Data Protection for VMwareconfiguration file TDPVMwareMounter.conf and verifythat the iSCSI server address is bound to the correctnetwork card and segment. 2. Use the vSphere client toconnect to your ESXi host. In vSphere, selectConfiguration->Storage Adapters to display a list of theiSCSI adapters. Right click the adapter that you areverifying. Then, select Properties ->NetworkConfiguration. In the VMkernel Port Bindings Detailsoutput, verify that the VMkernel Adapter is on thesame subnet that the datamover node is on.

ANS2473E Unable to create a Snapshot of thevirtual machine named 'vm_name'.

Explanation: An instant restore operation wasattempted for the specified virtual machine. Thesnapshot that is used to restore the virtual machinecould not be created.

System action: The instant restore operation stops.

User response: Examine the vCenter logs to determinewhy the snapshot could not be created and try theinstant restore operation again.

ANS2474E Unable to cleanup after an instantrestore operation for the virtual machinenamed 'vm_name', because vMotion taskis still running.

Explanation: An instant restore operation is stillrunning for the specified virtual machine.

System action: The cleanuop operation stops.

User response: Use the query command to check onthe status of the instant restore operation. Examine thevCenter to determine the status of the vMotion task. Ifyou want to stop the instant restore, cancel theoperation in the DP VMware GUI or stop the vMotiontask from the vCenter interface. Then, start the cleanupoperation again.

ANS2476E A restore location must be specified viathe TARGETPATH option whenrestoring to a different virtual machinename.

Explanation: A restore location must be specifed viathe TARGETPATH option when restoring to a differentvirtual machine name specified by the VMNAMEoption.


User response: Specify a restore location with theTARGETPATH option.

ANS2484I Virtual Machine 'vm_name' wassuccessfully restored

Explanation: The Virtual Machine was successfullyrestored.


User response: None

ANS2485E Cannot query the Tivoli StorageManager server to get instant accessinformation

Explanation: The server did not respond to the queryfor instant access information.



System action: The virtual machine cleanup operationis halted.

User response: Examine the dsmerror.log file and theTivoli Storage Manager server activity logs todetermine the cause of this error.

ANS2488E Error mounting the iSCSI device.

Explanation: An error occurred while trying to mountthe iSCSI device. Check the dsmerror.log file todetermine the cause of this error.



ANS2490E Could not turn off the VM that isnamed 'VM' .

Explanation: The specified virtual machine could notbe powered off. This prevents attempts to clean up theresources that were created to restore the virtualmachine.

System action: The restore operation was stopped.

User response: Turn off the virtual machine and thendelete it using the vSphere web client.

ANS2513I The virtual machine has no disksattached

Explanation: The virtual machine exists, but it doesnot have any disks attached. The machine can becleaned up.


User response: None

ANS2514I Disk status cannot be determined

Explanation: It is not possible to determine the statusof this disk.


User response: Examine the vSphere Client log todetermine what is wrong with the machine. If the logentries do not reveal problems with this virtualmachine, inspect the virtual machine in the vSphereClient to determine why the disk status cannot bedetermined. See the vSphere documentation foradditional guidance, if necessary.

ANS2515I No additional information is availablefor this virtual machine. The virtualmachine was deleted or it has beenrenamed

Explanation: Information about the virtual machinecannot be found on the ESXi host. The virtual machinemight have been previously deleted or renamed.


User response: Use the vSphere Client to determinewhat happened to this virtual machine. If the virtualmachine was renamed, make sure that it is runningwithout errors before you clean up the temporaryresources, by using the Restore VM command with the-VMRESToretype=VMCLEANUP option.

ANS2516E VMware storage vMotion operationfailed.Restart the storage vMotion operationmanually, by using the vSphere webclient, to finish the restore operation.Refer to the documentation to getdetails about the manual recoveryprocess.

Explanation: TSM Changes to the restored VM mightnot be permanently saved.

System action: TSM Automatic cleanup cannot beperformed for the failed vMotion operation.

User response: Examine the event logs to determinethe cause for the failure. Fix any problems and restartthe storage vMotion operation manually, by using thevSphere web clien, to finish the restore operation. Referto the vMotion documentation to get details about themanual recovery process.

ANS2517E Cannot query the Tivoli StorageManager server to get instant restoreinformation

Explanation: The server did not respond to the queryfor instant restore information.

System action: The virtual machine clean upoperation stops.

User response: Examine the dsmerror.log file and theTivoli Storage Manager server activity logs todetermine the cause of this error.

ANS2519E The disk \"diskname\" is an iSCSIdevice with an inactive path.Powering off the virtual machine willcause the ESXi server to hang. The cleanup operation has been stopped toprevent this.Use the Query VM command with the-detail option to obtain detailed statusinformation about the virtual machine.Correct the path so that the iSCSI stateis active and then try running theVMFULLCleanup operation again.

Explanation: A running virtual machine that has aninactive iSCSI device cannot be cleaned up.

System action: The virtual machine full clean up(VMRESTORType=VMFULLCLeanup) operation stops.



User response: For information about troubleshootinginactive iSCSI resources, search the VMware supportpages by using a search string like "troubleshootingiSCSI" or "inactive iSCSI".

ANS2520E The disk \"diskname\" is not a physicaldevice.An instant restore clean up was stoppedbecause vMotion could not restore allvirtual machine data..Use the Query VM command with the-detail option to obtain informationabout state of the specified disk.Use vMotion to manually migrate thevirtual machine devices and then try theclean up operation again.

Explanation: An instant restore clean up operation(-VMRESToretype=VMCLeanup) cannot completebecause vMotion could not restore all of the virtualmachine resources.

System action: The virtual machine clean upoperation stops.

User response: Use the VMware documentation todetermine how to use vMotion to migrate the virtualmachine. Then, try the clean up operation again byusing the Restore VM command with the-VMRESToretype=VMCLeanup option. If you do notwant to restore this virtual machine, use the RestoreVM command with the-VMRESTORType=VMFULLCLeanup option to removethe virtual machine and all of its resources.

ANS2521E Instant restore operations require validlicenses for both vMotion and storagevMothion.

Explanation: Instant restore works only when theESXi host has a valid license for both vMotion andstorage vMotion

System action: The instant restore operation isstopped.

User response: Obtain the necessary license fromVMware and assign the license to the ESXi host.

ANS2522W A user canceled the 'operationType'operation .

Explanation: A user canceled the restore/backupoperation .


User response: No response is required.

ANS2523E The virtual machine named vm cannotnot be restored to the sameconfiguration it had when it was backedup. IBM Tivoli Storage Manager willreconfigure the virtual machine toinclude only the most essentialconfiguration information and retry therestore operation.

Explanation: The restore operation failed to restore thevirtual machine to its original configuration. This errorcan occur if there is incompatibility between thehardware that the virtual machine was on when it wasbacked up, and the hardware on the physical hostwhere it was restored. IBM Tivoli Storage Manager willreconfigure the virtual machine to eliminate all butmost necessary configuration information (video andvirtual disks) and retry the restore operation.

System action: The restore operation continues, usingthe reconfigured virtual machine information.

User response: When the restore completes,reconfigure the restored virtual machine to yourrequirements.

ANS2524E An attempt to mount a snapshot of VM'disk' from disk 'vm' failed.The volume might be mounted fromanother operation and cannot beremounted.

Explanation: An attempt to mount a snapshot of VM'disk' from disk 'vm' failed.The volume might be mounted from another operationand cannot be remounted..

System action: The mount operation stops.

User response: Dismount the volume by running amount cleanup operation, then run the mountoperation again.

ANS2525E Unable to power on the created virtualMachine.

Explanation: The vSphere Server is unable to poweron the created virtual machine.

System action: The operation will be rolled back andstopped.

User response: Check the dsmerror.log file for moreinformation. Check the vSphere log to check what errorhappened during virtual machine power on.

ANS2526W TheVM_DONT_QUIESCE_ON_SNAPSHOTtestflag is deprecated for full VMbackups.Use theINCLUDE.VMSNAPSHOTATTEMPTS



option to attempt snapshots with"VMware Tools file system quiescingand application (VSS) quiescingdisabled".

Explanation: TheVM_DONT_QUIESCE_ON_SNAPSHOT testflagoverrides the INCLUDE.VMSNAPSHOTATTEMPTSoption. As a result, all snapshot attempts are withVMware Tools file system quiescing and application(VSS) quiescing disabled.

System action: Use theINCLUDE.VMSNAPSHOTATTEMPTS option to specifysnapshot attempts with VMware Tools file systemquiescing and application (VSS) quiescing disabled.

User response: See theINCLUDE.VMSNAPSHOTATTEMPTS documentationfor information about how to set this option.

ANS2527I The login request started.

Explanation: The user submitted a request to log in tothe file restore interface.



ANS2528I The login request was completedsuccessfully.VM-OS=os Data-Center=datacenter

Explanation: The user successfully logged into the filerestore interface.



ANS2529I The login request failed.

Explanation: An error occurred while logging into thefile restore interface.


User response: Review the log for related login andauthentication errors.

ANS2530I The log out request started.

Explanation: The user either logged out of the filerestore interface or the file restore interface timed outdue to inactivity.



ANS2531I The log out request was completedsuccessfully.

Explanation: The user was successfully logged out ofthe file restore interface.



ANS2532I The log out request failed.

Explanation: An error occurred while logging out ofthe file restore interface.

System action: Log out processing was completedwith errors.

User response: Review the log for related log outerrors.

ANS2533I The mount request started.Backup-ID=backupId

Explanation: The user selected a backup to load.



ANS2534I The mount request was completedsuccessfully.Backup-Date=backupDateMount-ID=mountId

Explanation: The backup was successfully mounted.



ANS2535I The mount request failed.Backup-Date=backupDateMount-ID=mountId

Explanation: An error occurred while mounting thebackup.

System action: Mount processing stops.

User response: Review the log for related mounterrors.

ANS2536I The dismount request started.Backup-ID=backupIdBackup-Date=backupDateMount-ID=mountId

Explanation: The user either selected another backupto load or logged out of the file restore interface.





ANS2537I The dismount request was completedsuccessfully.Backup-ID=backupIdBackup-Date=backupDateMount-ID=mountId

Explanation: The backup was successfullydismounted.



ANS2538I The dismount request failed.Backup-ID=backupIdBackup-Date=backupDateMount-ID=mountId

Explanation: An error occurred while dismounting thebackup.

System action: Dismount processing stops.

User response: Review the log for related dismounterrors.

ANS2539I The restore request started.Selection-Size=selectionSizeAlt-Destination=altDestination

Explanation: The user submitted a request to restorefiles, directories, or both from a backup.



ANS2540I The restore request was completedsuccessfully.

Explanation: The restore request was successfullysubmitted.



ANS2541I The restore request failed.

Explanation: An error occurred during the restorerequest.

System action: Restore processing stops.

User response: Review the log for related restoreerrors.

ANS2542I The final restore processing statistics areavailable.Total Objects=totalObjects TotalRestored=totalRestored TotalFailed=totalFailed Total Bytes=totalBytesCompletion Code=completionCode

Explanation: The restore processing statistics contain

completion codes that indicate the state of the restoreoperation.

v A completion code of 0 indicates that all items weresuccessfully restored.

v A completion code of 8 indicates that the restoreoperation was completed but some items were notrestored.

v A completion code of 12 indicates that the restoreoperation was unsuccessful.


User response: If the completion code is not 0, reviewthe logs for related restore errors.

ANS2600S Browser trying to establish connectionto client; received socket exception:exception-name

Explanation: The browser received the exceptionwhen trying to connect to the TSM client computer.


User response: Validate that the LAN is up and thatyou are trying to connect to the correct port number.

Check the error logs for any additional information:dsmerror.log, dsmwebcl.log, or dsmj.log. The defaultlocation of these logs is the installation directory of thebackup-archive client.

Ensure that the command line client runs withoutproblems. Test the command line client with acommand like "dsmc q sess".

ANS2601S The browser tried to connect to theclient and received unknown hostexception: exception-name

Explanation: The browser received the exceptionwhen trying to connect to the TSM client machine.


User response: Try the operation again. If it persists,determine what might be causing this kind of problem.For example, determine if your LAN went down, orverify if you are trying to connect to the correct TSMclient machine.

ANS2602S The browser tried to connect to theclient and received I/O exception:exception-name



User response: Determine what might be causing thiskind of exception. Try the operation again, and check ifthe LAN is down.

ANS2537I • ANS2602S


ANS2603S The browser tried to connect to theclient and received exception:exception-name



User response: Determine what might be causing thiskind of an exception. Determine if the LAN is down, orif the TSM Client Acceptor Daemon on the TSMmachine is up and running.

ANS2604S The Web client agent was unable toauthenticate with the server.

Explanation: The TSM Web client agent was unable toauthenticate with the TSM server.


User response: One possible solution is to run thecommand line client so that the client password can bere-entered. Another approach is to check the error logon the TSM Web client agent for any relevant messages.

ANS2605S Browser could not re-establishconnection to client; received protocolerror.

Explanation: The browser received a protocol errortrying to re-connect to the TSM client machine.


User response: Determine what might be causing thiskind of an error. Determine if the TSM browser and theTSM client code might be out of sync.

ANS2606S An invalid password was sent to theserver.

Explanation: The TSM password that was sent to theTSM server was invalid.


User response: Make sure that you have the correctpassword. Also make sure that it is valid, for exampleit is not too short.

ANS2607S Browser could not establish connectionto client.

Explanation: The TSM browser could not connect tothe TSM client machine.


User response: Determine what might be causing thiskind of a problem. Determine if the LAN is down, or ifthe TSM Client Acceptor Daemon on the TSM machineis up and running.

ANS2608S Nothing was selected so no operationwas performed.

Explanation: No object was selected in the GUI for theoperation to be performed upon.


User response: Make sure you select one or moreobjects (volume, directory or file) in the GUI beforeclicking on the operation to be performed.

ANS2609S TCP/IP communications failure betweenthe browser and the client machine.

Explanation: This error can occur due to any of thefollowing:

v The LAN connection to the TSM client machine wentdown.

v You are trying to connect to the TSM client machineusing the wrong port number.

v The Client Acceptor Daemon on the TSM clientmachine is not up and running and acceptingconnections.


User response: Retry the operation and make sure theLAN is up. Also check that the port number is correct,and that the Client Acceptor Daemon is started andrunning on the TSM client machine, and that it islistening on the correct port number.

ANS2610S TCP/IP communications failure betweenthe client and the server machine.


System action: The TSM client ends.

User response: Retry the operation and make sure theLAN is up. Make sure that both the TSM server andthe TSM client are up and running.

ANS2611S An unknown error occurred in thebrowser.

Explanation: An unknown error occurred in theapplet running in the browser.


User response: Retry the operation. If the problempersists, turn on tracing and see if the trace to thebrowser console gives the reason for the error.

ANS2603S • ANS2611S


ANS2612S An unknown error occurred in the clientPlease check the TSM Error Log for anyadditional information

Explanation: An unknown error occurred in the TSMclient.


User response: Retry the operation. If the problempersists, check the TSM Error Log for any additionalinformation.

ANS2613S A communications protocol erroroccurred between the web browser andthe client.

Explanation: None.


User response: Try the operation again. If the problemoccurs again, verify that the TSM web client is installedand configured correctly, and make sure you are usinga supported browser. Flush the browser cache. Then trythe operation again. If the problem persists, enableSERVICE traces on the web client on the target machineand the TSM Java applet, then reproduce the problem.Collect the traces and contact IBM for furtherassistance.

ANS2614S A protocol error occurred incommunications between the client andthe server.

Explanation: A protocol error happened between theTSM client and the TSM server.


User response: Retry the operation. If the problempersists, check the TSM Error Log for any additionalinformation. Verify that you are running the correctapplet with the appropriate level of the client.

ANS2615S The user ID entered does not match thenode name configured on the clientmachine.

Explanation: The user ID that was entered is not thesame as the node name on this TSM client.


User response: Verify that the node name entered isconfigured correctly on the TSM client.

ANS2616I The machine must be rebooted for thechanges to take effect

Explanation: The machine must be started for therestored registry changes to take effect.

System action: None

User response: Reboot the machine

ANS2617S The destination directory specified isinvalid.

Explanation: The user specified a destination targetdirectory for restore or retrieve which is invalid.


User response: Retry the operation specifying a validdirectory name.

ANS2619S The Client Acceptor Daemon wasunable to start the Remote Client Agent.

Explanation: The TSM Client Acceptor Daemon couldnot start the TSM Remote Client Agent.


User response: Check the error log on the TSM Webclient agent for any relevant messages. Then correct theproblem and retry.

ANS2620W The expand entire branch operation maytake a long time,and cannot be canceled once it hasstarted.Are you willing to wait for theoperation to complete?

Explanation: The expand entire branch operationcould take a long time and cannot be canceled once itis started.


User response: Answer 'Yes' to start the expand entirebranch operation. If you answer 'No', the currentoperation will be canceled.

ANS2622S An invalid ID or password submitted.

Explanation: Either the ID is not registered on theTSM server, or the password for the ID is incorrect.


User response: Verify that the ID you are using existson the TSM server to which the remote client nodeconnects. The ID must have sufficient privileges toaccess the remote client node's data. Also make surethat you have the correct password for the ID. If the IDdoes not exist or if the password is unknown, contactyour TSM administrator. If the ID does not exist, thenthe TSM administrator can use the REGISTER ADMINand GRANT AUTHORITY commands to register an IDthat can access the remote client node's data. If thepassword is unknown, the TSM administrator can usethe UPDATE ADMIN command to reset the password.



ANS2623S Web Client applet level is out of syncwith Web Client agent.

Explanation: The Web Client applet and Web Clientagents are at incompatible levels.


User response: Verify that you have the correct levelof the applet installed with the client, and that anincorrect level of the applet was not placed in theinstall directory.

ANS2624E This operation requires client ownerauthority.

Explanation: Your user ID has insufficient authority toperform this operation.

System action: Processing continues, but the user isnot allowed to do this operation.

User response: Do not perform this operation, or get ahigher authority level for your user ID in order toperform this operation.

ANS2625E Node does not support this imageoperation.

Explanation: Node does not support or is notconfigured to perform this image operation.

System action: Processing continues, but the user isnot allowed to do this operation.

User response: Verify whether this image relatedoperation is supported or configured on the targetplatform.

ANS2626E The Include-Exclude statement:ieStatementcontains invalid characters.

Explanation: The specified Include-Exclude statementhas invalid characters.

System action: TSM will not add the specifiedInclude-Exclude statement to the list.

User response: Retry the operation with anotherstatement that has valid characters.

ANS2627W The NTFS security attributes for object'full-name' could not be set. Windowssystem error code: error; reason:'error-reason'. Default NTFS securityattributes have been set.

Explanation: TSM was unable to set the NTFS securityattributes of the file. The error information capturedindicates the reason for the failure. Default NTFSsecurity attributes have been set.


User response: Check the reason field for the codewhich explains why the NTFS security attributes havenot been set. Correct the condition causing the errorand try the operation again. If the problem persists,contact your system administrator or TSMadministrator for further help.

ANS2628W Failed to create named stream of object'filespace namepath-namefile-name'.

Explanation: TSM was unable to create named stream.

System action: The named stream is notrestored/retrieved.

User response: The object is restored without namedstream, the object should be examined to verify that itis usable. Check the client error log for ANS5250E errormessage that should have been logged when thismessage was written, take the corrective action and trythe operation again. If the problem persists, contactyour system administrator or TSM administrator forfurther help.

ANS2629I Migration: The filespace will bemigrated to the Incremental Forevermodel.

Explanation: The first time an Incremental ForeverIncremental (IFIncr) backup is performed against avirtual machine that was previously backed up usingthe Periodic Full model, and the latest backup is anincremental backup, then backup chain will bemigrated to the Incremental Forever model.



ANS2666S Source and/or target volumes areduplicated. The same volume ismounted on more volume paths.

Explanation: This error can occur when a sourcevolume is mapped on more volume paths, for example,a drive letter and one or more mount point directories.Because TSM uses the volume path to keep track ofbackup information in its internal backups database, itcannot back up the same volume with a duplicatevolume path. See addition information in the error log.

System action: TSM cannot select the volume.

User response: Delete the last snapshots created asthey are not managed by TSM. Unmount the duplicatevolume path in order to have a single mount point tothe same source volume. Restart TSM and retry theoperation.



ANS2667I Scan operation was successful.

Explanation: The virtual machine was scannedsuccessfully.

System action: The scan process stops for the virtualmachine. The next virtual machine in the data centerwill be processed.

User response: None

ANS2668E Scan operation failed with anunexpected error.

Explanation: An unexpected error occurred duringguest scan operations.


User response: Check the client error log foradditional information.

ANS2669I Guest operating system platform is notsupported.

Explanation: The operating system of the virtualmachine was not supported by the scan operation.


User response: None

ANS2670I Remote directory in guest is being usedby another application.

Explanation: The scan operation was unable to copyfiles to the remote directory because the directory is inuse by another application.


User response: Ensure that the remote directory isunlocked. Then, reschedule the scan operation.

ANS2671I Virtual machine name was not found onthe VMware server.

Explanation: None


User response: None

ANS2672W Hostname could not be found for thespecified virtual machine name.

Explanation: This issue might be caused by the virtualmachine not running and not having a static IPaddress.


User response: Make sure the guest is properlyconfigured. Then, reschedule the scan operation.

ANS2673I Duplicate virtual machine name wasdetected.

Explanation: None


User response: None

ANS2674I The virtual machine is not connected toESX server.

Explanation: None


User response: None

ANS2675E Proxy Rejected: Proxy authority has notbeen granted to the specified datamover node.

Explanation: The scan of the virtual machine failed.



ANS2676W The guest operating system credentialwas not found.

Explanation: The guest scan operation requires a validoperating system credential.


User response: Ensure the guest operating systemcredential is set. Then, reschedule the scan operation.



ANS2677W The guest operating system credential isinvalid.

Explanation: The guest scan operation requires a validoperating system credential.


User response: Ensure a valid guest operating systemcredential is set. Then, reschedule the scan operation.

ANS2678I Guest machine is powered off.

Explanation: None


User response: None

ANS2679I VMware Tools on the guest machine isnot running.

Explanation: None


User response: None

ANS2680I VMware Tools version on the guestmachine is not current.

Explanation: None


User response: None

ANS2681W ESX host or vCenter version is notsupported.

Explanation: The ESX host or vCenter is a down levelversion.


User response: Refer to the product documentationfor supported ESX and vCenter versions.

ANS2682I The guest credential has insufficientpermissions.

Explanation: None


User response: None

ANS2683W Cannot communicate with the remotehost.

Explanation: This communication issue is caused bynetwork errors or by the host not responding.


User response: Ensure that the network and hostconnection are configured correctly. Then, reschedulethe scan operation.

ANS2684I The guest operation agent could not becontacted.

Explanation: None


User response: None

ANS2685I The VM is a template.

Explanation: VM templates are not supported by thescan operation.


User response: None

ANS2686E VM scan initialization error.

Explanation: The vm scan operation encountered anerror during initialization.


User response: Check the client error log and trace foradditional information.

ANS2687W The virtual machine 'VM-name' containsone or more disks that exceed themaximum size limit. Specify the'-VMSKIPMAXVMDKS=yes' option toexclude these disks from the backup.



User response: Specify the'-VMSKIPMAXVMDKS=yes' option to exclude thesedisks from the backup.



ANS2688E The restore of a Hyper-V virtualmachine that was backed up usingincremental forever backup is notallowed on a Windows 2008 or Windows2008 R2 host. The restore operation mustbe completed on a Windows 2012 orlater Hyper-V host

Explanation: A Hyper-V virtual machine that wasbacked up with the incremental forever backup typecan only be restored on a Windows 2012 or laterHyper-V host.

System action: The restore operation does not start.

User response: Try the operation again with aWindows 2012 or later Hyper-V host.

ANS2689E A Hyper-V command subcommandcommand was specified, but theHyper-V role is not enabled on the hostsystem

Explanation: The Hyper-V role must be enabled onthe host system where the Hyper-V operation occurs.The current system does not have the Hyper-V roleenabled.

System action: The operation does not start.

User response: Try the operation again from a hostthat has the Hyper-V role enabled.

ANS2690E A Hyper-V BACKUP VM commandwith mode IFFULL or IFINCR wasspecified but the Data Protection forMicrosoft Hyper-V license file does notexist or is not valid

Explanation: The Data Protection for MicrosoftHyper-V license file is required to issue Hyper-VBACKUP VM commands with mode IFFULL orIFINCR. Make sure the Data Protection for MicrosoftHyper-V file is installed.

System action: The backup does not start.

User response: Try the operation again from a hostthat has the Data Protection for Microsoft Hyper-Vlicense file installed. Or, issue the BACKUP VMcommand and specify mode FULL.

ANS2691E A Hyper-V BACKUP VM commandwith mode FULL was specified but theData Protection for Microsoft Hyper-Vlicense file exists. Mode IFFULL orIFINCR must be specified

Explanation: Hyper-V BACKUP VM commands withmode FULL are not allowed on hosts where the DataProtection for Microsoft Hyper-V license file isinstalled. Instead, issue the BACKUP VM commandusing mode IFFULL or IFINCR.

If you must issue the BACKUP VM command withmode FULL, you must uninstall the Data Protection forMicrosoft Hyper-V license file. However, uninstallingthe license file invalidates the IFINCR backup chain. Asa result, an IFFULL is performed if the Data Protectionfor Microsoft Hyper-V license file is reinstalled.

System action: The backup does not start.

User response: Try the operation again and specifymode IFFULL or IFINCR.

ANS2692E An error occurred while registering thefilespace for virtual machine (VM_name).

Explanation: An error occurred while registering thefilespace for the specified virtual machine.


User response: Check the error log for informationabout how to resolve this issue.

ANS2693E An error occurred while registering thefilespace for virtual machine (VM_name).There is a filespace with the same namethat is currently being deleted.

Explanation: An error occurred while registering thefilespace for the specified virtual machine. A filespacewith the same name is currently being deleted on theTSM server


User response: Wait for the delete filespace to finishand run the backup command again.

ANS2697E The virtual machine cannot be restoredbecause the datastore named 'datastore'does not exist or is inactive.

Explanation: The datastore referenced by virtualmachine when it was backed up does not exist or isinactive on the ESX/ESXi that you are restoring thevirtual machine to.


User response: Find the missing datastore or specifythe -datastore option on the Restore VM command tospecify an existing datastore to restore the virtualmachine files to.



ANS2698E Snapshot operation failed.

Explanation: If you are performing a VSS or LVSAsnapshot based operation, it is possible that thesnapshot was not large enough to contain all thechanges made to the file system after the snapshot wascreated. This could cause the snapshot to becomeinvalid thereby preventing the TSM client from readingthe snapshot.

System action: The requested operation stopped.

User response: Examine the client error log foradditional messages related to this error. Performcorrective actions indicated by the messages, then trythe operation again.

ANS2699W Importing VM 'vm name' failed for vApp'vapp name'.

Explanation: The import VM from vSphere to avCloud vApp operation failed.

System action: Restore processing for the vAppcontinues.

User response: Check the dsmerror.log file forinformation about why the VM was not imported.Then, try the operation again. If the problem persists,visit the IBM Support Portal for additional informationat http://www.ibm.com/support/entry/portal/.

ANS2700E Restoring VM 'vm name' of vApp 'vappname' is not possible. There is no VMbackup data.

Explanation: During the vApp restore, a VM thatexists in the restored vApp version could not berestored, because it was not successfully backed up.

System action: The restore operation will proceed,attempting to restore any available vApp backup data.

User response: Examine the client error log for anymessages that might be indicate on the reason for thespecified VM's backup failure. Contact TSM technicalsupport if further assistance is required.

ANS2701E The attempted database operation wasunsuccessful, check the TSM error logfor any additional information.

Explanation: Processing stops.

System action: Reserved.

User response: Check the TSM error log forinformation regarding failure and take further action.

ANS2704E Error: The vCenter server version is at alower level than the ESX host version,or the user ID specified by theVMCUser option does not havesufficient permission to perform theoperation.

Explanation: The vCenter returned an error indicatingthere is a problem with the license. This error can occurwhen the vCenter server version is at a lower levelthan the ESX host version. The vCenter server versionmust be at the same (or later) level as the ESX hostversion. This error can also occur when the user IDspecified by the VMCUser option does not havesufficient permission to perform the operation or thepermissions are not applied at the vCenter server level.


User response: Verify the vCenter server is at thecorrect level, and verify that the user ID specified bythe VMCUser option has sufficient permission toperform the operation.

ANS2705S No DB2 UDB partitions are available forrestore.

Explanation: No DB2 UDB partitions are available onthe TSM server for restore. This is most likely due to aprevious backup that was aborted before the backupcompleted. The DB2 UDB database and selectedpartitions cannot be restored.


User response: Issue the TSM client command QUERYDB2UDB command with the -DETAIL parameter usingthe same database, file, and date criteria to see if anydatabase partitions are available for restore.Alternatively restore the DB2 UDB database from adifferent backup.

ANS2711E The snapshot of virtual machine'VM-name' was removed during thebackup.

Explanation: The virtual machine snapshot wasremoved by another application or process during thebackup. This removal corrupts the backup and itbecomes unusable.


User response: Ensure that another application orprocess does not remove or modify the virtual machineduring the backup.

ANS2712W The virtual machine 'name' has aVMware Tools running, but VMwareTools is out of date.

Explanation: A supported version of VMware Toolsmust be installed, running and current to complete avirtual machine backup.



System action: The backup operation fails.

User response: Verify that a supported version ofVMware Tools is installed, current and running. Then,try the backup operation again.

ANS2713E The virtual machine 'VM-name' is in aninvalid connection state 'state'. As aresult, it cannot be backed up.

Explanation: To back up a virtual machine it must bein the 'connected' state to be accessed.


User response: Return the virtual machine to the'connected' state and try the backup again.

ANS2714W The management class 'mc' specified forthe 'dest' backup destination is invalid.The default management class will beused.

Explanation: None.


User response: Contact the TSM administrator to runthe configuration utility for DB2 UDB and specify avalid management class.

ANS2715E The virtual machine 'VM-name' isconfigured as a fault tolerant virtualmachine. As a result, it cannot bebacked up.

Explanation: vSphere does not allow for the snapshotor backup of fault tolerant virtual machines withvStorage API for Data Protection.


User response: To back up a fault tolerant virtualmachine with vStorage API for Data Protection, firstdisable fault tolerant. Then, after the backup completes,enable fault tolerant.

ANS2716E A background copy process is stillpending on local hardware. A restoreoperation cannot be initiated until thebackground copy process is completed.

Explanation: None.


User response: Wait until the background copyprocess completes and retry the restore operation.

ANS2717E The multi-node definition does not havepermission to delete its own backupfiles from the server.

Explanation: All DB2 UDB commands require that themulti-node definition has permission to delete its own

backup files from the server in order to properlyreconcile the local backup repository with the serverbackup repository.


User response: Have the TSM administrator updatethe multi-node definition so that it has permission todelete its own backup files from the server. Forexample, on the TSM administrative command-lineclient:. dsmadmc update node <multi-node name>backdelete=yes

ANS2718W The virtual machine 'VM-name' requiressnapshot consolidation.

Explanation: Snapshot consolidation is required whena snapshot is deleted but its associated disk is notcommitted back to the base disk. If consolidation is notcompleted, snapshot disks might grow and eventuallyfill the data store.

System action: The virtual machine backup continues.

User response: Consolidate the virtual machinesnapshots according to instructions provided in theappropriate VMware vSphere documentation.

ANS2719E A previous backup started on 'datetime',is using the resources needed for newbackup is still pending.

Explanation: A new backup can not be done untilprevious backup completes.


User response: Wait until previous backup completesbefore starting another local backup. Alternatively, usedifferent copyType value to perform a local backup.TSM local backup policy only allows one incrementaland one full background copy to be pending at anytime, before local backup resources are reused for anew backup version. A new local backup would resultin a backup with background copy in pending state.

ANS2720W Failed to execute the command'command'.

Explanation: IBM Tivoli Storage Manager Failed toexecute a command. The possible reason - thecommand interpreter cannot be found. Verify theComSpec and PATH environment variables that locatethe command interpreter. Either ComSpec or PATH isnot defined, or it is not correctly defined.

System action: The command does not run. Otherwiseprocessing will attempt to continue.

User response: Correct the ComSpec and PATHenvironment variable that locate the commandinterpreter. Contact your system administrator if youare not sure how to make this correction.



ANS2721E The virtual machine is in an invalidconnection state. As a result, it cannotbe backed up.

Explanation: One or more virtual machine backupsfailed because of an invalid connection state. A virtualmachine must be in the 'connected' state to be accessedfor backup.

System action: Processing stops for this virtualmachine

User response: Check the console output and errorlogs for information about why the connection statewas invalid. Correct any issues and try backing up thefailed virtual machines.

ANS2722E There is not enough space in the localrepository to complete this backup.

Explanation: This space available in the localrepository is not enough to perform snapshot for thisbackup operation. It could happen if there is morenumber of local versions kept by the management classthan there is space allocated in the local repository atconfiguration time or application configuration haschanged such that previously allocated space is notenough.


User response: Please validate TSM configuration byrunning the configuration wizard.

ANS2723E A value of UNDEF for theREAdstartsrecall option is not validwhen the HSMBACKENDMODE optionis set to TSM.

Explanation: A value of UNDEF for theREAdstartsrecall option is valid only when theHSMBACKENDMODE option is set to TSMFREE.

System action: The operation stops. The file isskipped.

User response: If the HSMBACKENDMODE option isset to TSM, set the REAdstartsrecall option to YES orNO.

ANS2724E The version of IBM Enterprise StorageServer is not supported.

Explanation: This product only supports IBM ESSmicrocode level 2.3 and 2.4.


User response: Ensure that ESS microcode level 2.3 or2.4 is installed.

ANS2725E IBM Tivoli Storage Manager applicationprotection could not register the TSMVSS provider on the guest VM 'VM'.

Explanation: The guest vm credentials speficied onthe datamover do not have the correct requiredWindows permissions for application protection.

System action: The application protection vm backupprocessing stops.

User response: Make sure that the credentialsspecified for the guest VM have the correct requiredWindows permissions for application protection typevm backups. The user guide outlines the correctpermissions that are required for backuping andrestoring application data for Microsoft Exchange andMicrosoft SQL Servers.

ANS2726E The putenv command failed for path =v1.

Explanation: There was not enough memory in theenvironment to successfully set the environment.


User response: Close all unneeded applications andtry the operation again. For UNIX systems that supportresource limits, check to see if the memory resourcelimit is too low by entering the following command:

ulimit -a


ANS2727E ESS Lun ID v1 is not valid.

Explanation: Length of ESS LUN id must be 8characters.


User response: Make sure the length of ESS Lun id is8.

ANS2728E The ESS jar file v1 cannot be found.

Explanation: The Enterprise Storage Sub-system CopyServices JAR file could not be located.


User response: In order to complete EnterpriseStorage Sub-system Copy Services functions the CopyServices command line functions must be available.Check the Copy Services command line is installed andyour Copy Services option setting is pointing to theinstallation directory of the command line.



ANS2729E Operating system command 'command'failed; rc=rc.

Explanation: None.


User response: Check the return code from theoperating system for more information about thefailure. Issue the failing command manually to see ifthe same failure occurs.

ANS2730E The primary and secondary copy serviceservers are down.

Explanation: None.


User response: Start at least one of the ESS copyservice servers. If copy server is already running, checkthe value of java home specified during configurationto make sure it is a valid path name of the directorywhere JRE is installed on master backup node. Useconfiguration wizard to update java home value for theconfiguration.

ANS2731E Cannot open the ESS command outputfile v1 for writing.

Explanation: Can't open this file for writing.


User response: Make sure you have enough space onyour system and write permission to the file.

ANS2732E The ESS LUN 'Serial number string' arealready in use.

Explanation: One or more LUNs specified in themessage are in use by other flashcopy operation.Therefore this flashcopy operation can not continue.


User response: Release ESS LUN in order to reusethem.

ANS2733E An operation requiring the WindowsManagement Instrumentation (WMI)service has failed with the error'errorstring'. TSM has been denied accessto a WMI system due to insufficientprivileges.

Explanation: Windows denied access to a WindowsManagement Instrumentation (WMI) resource, object,or operation. This program has insufficient permissionsto perform the requested operation.

System action: Performing an operation requiring theWindows Management Instrumentation service.

User response: Raise the permissions assigned to TSMand retry the operation.

ANS2734E An operation requiring the WindowsManagement Instrumentation (WMI)service has failed with the error'errorstring'. The application interfacedoes not exist.

Explanation: This error occurred because WindowsManagement Instrumentation (WMI) classes were notregistered or have become unregistered. WMI classesare registered with Windows features.

System action: Initialization of a WindowsManagement Instrumentation object failed.

User response: Register the Windows ManagementInstrumentation classes of the appropriate Windowsfeature.

ANS2736E An unexpected response was receivedfrom a remote TSM file system agent.verb : verbremote host : hostreturn code : rcreason code : rsmsg. string : msg-string

Explanation: None.



ANS2737W No disks from VM are mounted becauseall disks were excluded during thebackup.

Explanation: No disks from VM can be mountedbecause all disks were excluded during backup or theVM did not contain any disks.


User response: If files from the affected file systems orvolumes must be recovered, ensure that at least onedisk is included in the backup.

ANS2740E The vApp restore operation failed.

Explanation: The vApp restore operation failed. Checkthe error log for details on why the operation failed.


User response: Review the console output and errorlogs for the details on the problem. Fix any issues andrestart the operation.



ANS2744I TESTFLAG DB2 enabled with the valueof 'value'.

Explanation: None.

System action: This message is informational.


ANS2745E An assigned virtual disk to Hyper-VVirtual Machine 'virtualmachinename'cannot be found.

Explanation: The IBM Tivoli Storage Manager clientdetected that a Virtual Machine has assigned a diskthat is unreachable. The disk may have been moved ordeleted. A snapshot cannot be taken while the diskcannot be found.

System action: The IBM Tivoli Storage Manager couldnot find a virtual disk at the assigned path.

User response: Check that the virtual disk has notbeen moved or deleted and update the virtual machineconfiguration to match any changes to the file system.

ANS2746E An assigned virtual disk to Hyper-Vvirtual machine 'virtualmachinename' is aVHD or invalid format. Only virtualdisks in VHDX format can be backedup.

Explanation: The IBM Tivoli Storage Manager clientdetected that a virtual machine has assigned a disk thatis in the VHD format or is in an unrecognisable orunsupported format. If the disk is in VHDX format itmay be corrupted.

System action: The IBM Tivoli Storage Manager founda virtual disk in VHD or unrecognisable format whilepreparing for a backup of a virtual machine.

User response: If the virtual disk is in VHD formatthere are several options: Remove the VHD from thevirtual machine, convert the virtual disk from VHDformat to VHDX format, or adjust DOMAIN.VMFULLto skip the virtual machine from backup. If the disk isin VHDX format, check that the disk has not beencorrupted.

ANS2747E An assigned AVHDX virtual disk toHyper-V virtual machine'virtualmachinename' cannot find theparent disk. Snapshots can be takenonly if the parent can be found.

Explanation: The AVHDX format specifies an internalfield that points to a parent AVHDX or VHDX file. Ifthe parent cannot be found the disk is invalid and asnapshot will fail.

System action: TSM discovered an AVHDX attachedto a virtual machine and attempted to find the parentAVHDX or VHDX file.

User response: Check that the parent AVHDX orVHDX file still exists and has not been moved ordeleted. Return the parent AVHDX and/or VHDX file.

ANS2748E An assigned virtual disk to Hyper-Vvirtual machine 'virtualmachinename'exceeds the maximum capacity limit.The IBM Tivoli Storage Manager clientcannot backup virtual machines withdisks that exceed the limit of twoterabytes.

Explanation: The IBM Tivoli Storage Manager clientdetected that a Virtual Machine has assigned a diskwhose capacity exceeds two terabytes. Virtual disksthat exceed 2 terabytes are currently not supported byincremental forever backups.

System action: The IBM Tivoli Storage Manager founda virtual disk whose capacity exceeds two terabytes ona virtual machine scheduled for back up.

User response: There are several options available:Remove the disk from the virtual machine, shrink thedisk to under two terabytes, copy the data to virtualdisk with a capacity under two terabytes. Even thoughincremental backup is not available, the always fullbackup type is compatible with disks over twoterabytes.

ANS2749E See Microsoft Technote KB2771882. Anassigned virtual disk to Hyper-V VirtualMachine 'virtualmachinename' containsfiles that are on a Cluster SharedVolume and local volumes. A snapshotof a Virtual Machine in thisconfiguration cannot be taken.

Explanation: The IBM Tivoli Storage Manager clientdetected that a Virtual Machine has files involved inthe snapshot on both local volumes and Cluster SharedVolumes. Attempting to snapshot a virtual machine inthis configuration always results in failure. This error isdocumented in Microsoft Technote KB2771882.

System action: The IBM Tivoli Storage Manager clientdiscovered the virtual machine has files on localvolumes and cluster shared volumes prior to taking asnapshot.

User response: Check that all of the disks and theconfiguration files are all on local volumes or clustershared volumes. If necessary, perform a storagemigration to move the disks and/or configuration files.

ANS2750E The Hyper-V Virtual Machine'virtualmachinename' is currentlyundergoing one of the followingoperations:* Creating Local Snapshot* Applying Local Snapshot* Deleting Local Snapshot



* Exporting Virtual Machine* Migrating Virtual Machine* Volume Snapshot Service (VSS)Snapshot* Restore* Merging Differencing DisksThe above operations prevent a Hyper-VVSS snapshot from taking place. Waitfor the operation to finish or cancel toperform a backup.

Explanation: Some virtual machine management tasksinterfere with a virtual machine VSS snapshot. One ofthese operations was detected during a back uprequest.

System action: The IBM Tivoli Storage Manager clientdiscovered the virtual machine is currently undergoingan operation that will prevent a Volume SnapshotService snapshot from occuring.

User response: Cancel or wait for the current virtualmachine management task to finish and then retry theback up.

ANS2753I Establishing inter-client communicationwith node node(s).

Explanation: None.



ANS2785I Gathering current DB2 configuration for'type' restore.

Explanation: None.



ANS2790E Error Accessing Storage Virtual Machine'svm_name' on NetApp Filer 'filer_name'.

Explanation: The specified Storage Virtual Machinecould not be accessed on the specified filer. Make surethat the storage virtual machine exists and is runningon the specified filer and that the storage virtualmachine has been correctly associated with the filerwith the SET NETAPPSVM command.


User response: Make sure that the storage virtualmachine is running on the specified filer and that theassociation between the filer and the storage virtualmachine has been defined correctly with the dsmc setnetappsvm command.

ANS2798E Unable to start a session from clientnode 'nodename' multi-node 'multi-node'to client at address 'ip-address:ip-port'.The TSM return code is rc.

Explanation: None.



ANS2799E An error was encountered during asession with another client.check the TSM error log for anyadditional information

Explanation: This message is reserved for DB2 UDB.

System action: Reserved.

User response: This message is reserved for DB2 UDB.

ANS2800W No TSM processes were found.

Explanation: The QUERY PIDS command was unableto identify any known TSM processes running on thesystem. If the -FILTER option was used, no processesmatching the filter specification were found.


User response: If you need to use dsmtrace to enableor disable tracing for a running client process, makesure that the client is already running. If you used the-FILTER option, try the command again with a differentfilter specification. You can use -FILTER=* to display allprocesses running on the system.

ANS2801E The dsmtrace utility was unable toconnect to the specified process.

Explanation: This message typically occurs when thespecified process ID is not active.


User response: If you need to use dsmtrace to enableor disable tracing for a running client process, makesure that the client is already running. Use thedsmtrace QUERY PIDS command to identify runningclient processes, then try the command again.

ANS2802I Tracing has been disabled.

Explanation: None.





ANS2803E Tracing could not be disabled.

Explanation: A problem occurred while trying todisable tracing for the specified process. This messageis usually accompanied by other, more specificmessages immediately preceding or following thismessage.

System action: No changes are made to the tracestatus of the specified process.

User response: Review the messages that immediatelyprecede or follow this message for further informationabout this error.

ANS2804W Tracing is already enabled.-TRACEFILE, -TRACEMAX, and-TRACESEGSIZE are ignored.

Explanation: When tracing is already enabled for aclient process, only the -TRACEFLAGS option has anyeffect.

System action: The -TRACEFLAGS options are set onthe client process. -TRACEFILE, -TRACEMAX, and-TRACESEGSIZE are ignored.

User response: If you need to modify the-TRACEFILE, -TRACEMAX, or -TRACESEGSIZEsettings, you must first use the dsmtrace DISABLEcommand to disable tracing for the client process. Thenrun the dsmtrace ENABLE command to configure thedesired trace settings. If it is not necessary to modifythese settings, then this message may be ignored.

ANS2805I Tracing has been enabled.

Explanation: None.



ANS2806E Tracing could not be enabled.

Explanation: A problem occurred while trying toenable tracing for the specified process. This message isusually accompanied by other, more specific messagesimmediately preceding or following this message.

System action: No changes are made to the tracestatus of the specified process.

User response: Review the messages that immediatelyprecede or follow this message for further informationabout this error.

ANS2807E An incorrect number of parameters wasspecified for the command-namecommand.

Explanation: The specified command was invokedwith too few or too many parameters.


User response: Try the command again with thecorrect number of parameters. Run \"dsmtrace help\"for additional information on dsmtrace commandsyntax.

ANS2808W Incremental by snapshot differencebackup did not locate the registeredbase snapshot 'regbase-name' onNetApp/N-Series filer volume'volume-name'. Snapshot 'olderbase-name' isused as the base snapshot.

Explanation: Incremental by snapshot differencebackup did not locate the specified registered basesnapshot on the specified NetApp/N-Series filervolume. The most recent existing snapshot which isolder than the registered base snapshot is used as thecurrent base snapshot.



ANS2809E The backupid 'backupid:' in the input filedoes not match the vmname 'vmname:'being restored.

Explanation: There is a discrepency between thebackupid and vmname specified in the input file


User response: Confirm that the backupid specifiedmatches the vmname you are attempting to restore byre-running the inquire_detail command and make anynecessary corrections before attempting the restoreagain.

ANS2810E The TSM for Virtual EnvironmentsInput File 'input file:' appears to beempty.

Explanation: While processing the Input File no itemswere found to operate on.

System action: The operation cannot continue with anempty list.

User response: Confirm that the input file is notempty and has valid input. If the file is not empty itmay be that an error occurred while reading the file,please check the error log for any errors found duringthe reading of the file. If errors are found make thenecessary corrections before attempting the operationagain.

ANS2811E The TSM for Virtual Environmentscould not find a suitable datamoveragent for the DataCenter Node'datacenter nodename'.

Explanation: While processing Proxy relationships



with the DataCenter Node specified, no appropriatedatamover matches detected

System action: The operation cannot continue withouta valid datamover.

User response: Work with your TSM Administrator toensure that your DataCenter Nodes have granted proxyauthority to your DataMover Nodes.

ANS2812E The TSM for Virtual Environmentscould not find Datamover node named'datamover nodename' on the TSM Server.

Explanation: While processing Proxy relationshipswith the DataCenter node and DataMover nodespecified, no appropriate Datamover node namematches detected.

System action: The operation cannot continue withouta valid Datamover Node name.

User response: Make sure the Datamover node namespecified is a valid TSM node name and that the nodehas the proper proxy relationships established.

ANS2813E The TSM Server returned an emptynetwork address or port number for'datamover nodename'.

Explanation: While querying the TSM Server for theDatamover network address and port number, theServer returned zero for one of the values.

System action: The operation cannot continue withouta valid Datamover network address and port number.

User response: This is usually the result of aDatamover Node not being started. Log on to theDatamover host and start or restart the DSMCADservice and retry the TSM for Virtual Environmentscommand again. If the problem persists, work withyour TSM Server Administrator to inspect the TSMServer activity log to identify the issue.

ANS2814E TSM for Virtual Environments detectedan error while parsing the Input File'input file'. The 'specifier' appears to beempty or invalid.

Explanation: While parsing the Input File an erroroccurred.

System action: The operation cannot continue withoutvalid virtual machine specifications.

User response: This is usually the result of an emptyvirtual machine name or other identifier. Please checkthat the syntax of the Input File is correct for all entriesand that virtual machine names are not empty andretry the operation.

ANS2815E TSM for Virtual Environments detectedan error while parsing 'read in line' fromthe Input File 'input file'.


System action: The operation cannot continue withoutvalid specifications in the Input File.

User response: This may be the result of an emptyvirtual machine name or other identifier. Please checkthat the syntax of the Input File is correct for all entriesand that virtual machine names are not empty andretry the operation.

ANS2816E TSM for Virtual Environments detectedthat the TSM Server IP address was notspecified.

Explanation: While parsing the command line options,an empty Server address was detected.

System action: The operation cannot continue withouta valid network address for the TSM Server.

User response: This may be a result of the VMCLIprofile having an empty VE_TSM_SERVER_NAMEentry. Please check that the VMCLI profile is configuredcorrectly specifying the TSM Server address.

ANS2817E TSM for Virtual Environments detectedthat the vCenter Command-Lineinterface node name was not specified.

Explanation: While parsing the command line options,an empty vCenter Command-Line interface node namewas detected.

System action: The operation cannot continue withouta valid vCenter Command-Line interface node name.

User response: This may be a result of the VMCLIprofile having an empty VE__TSMCLI_NODE_NAMEentry. Please check that the VMCLI profile is configuredcorrectly specifying the vCenter Command-lineinterface node name.

ANS2818E TSM for Virtual Environments detectedthat the TSM Server port was notspecified.

Explanation: While parsing the command line options,an empty TSM Server port was detected.

System action: The operation cannot continue withouta valid TSM Server port.

User response: This may be a result of the VMCLIprofile having an empty VE_TSM_SERVER_PORTentry. Please check that the VMCLI profile is configuredcorrectly specifying the TSM Server port.



ANS2820E An interrupt has occurred. The currentoperation will end and theclient will shut down.

Explanation: This message is issued when the processis interrupted by a break signal such as CTRL-BREAKor CTRL-C.

System action: The TSM operation and process areended immediately.

User response: Restart the operation if desired.

ANS2821E The function is not supported on theplatform.

Explanation: The specified function isn't supported onthe specified platform.


User response: Please retry the specified function on asupported platform.

ANS2824E TSM for Virtual Environments detectedthat the node name representing thevCenter is not specified.

Explanation: While parsing the command line options,an empty vCenter node name was detected.

System action: The operation cannot continue withouta valid vCenter node name.

User response: This may be a result of the VMCLIprofile having an empty VE_VCENTER_NODE_NAMEentry. Please check that the VMCLI profile is configuredcorrectly specifying the vCenter node name.

ANS2825E TSM for Virtual Environments detectedthat the node name representing theDatacenter is not specified.

Explanation: While parsing the command line options,an empty datacenter node name was detected.

System action: The operation cannot continue withouta valid datacenter node name.

User response: This is a result of the -d DataCenterNode Name not being passed in to the Command-line.Re-try the operation making sure to pass the -dDatacenter Node Name to the command-line call.

ANS2826E TSM for Virtual Environments detectedthat the node name representing thevCenter Datamover is not specified.

Explanation: While parsing the command line options,an empty Datamover node name was detected.

System action: The operation cannot continue withouta valid Datamover node name.

User response: This is a result of the -o Datamover

Node Name not being passed in to the Command-line.Re-try the operation making sure to pass the -oDatamover Node Name to the command-line call.

ANS2827E TSM for Virtual Environments detectedthat the input file is not specified.

Explanation: While parsing the command line options,an empty or non-existing input file name was detected.

System action: The operation cannot continue withouta valid input file name.

User response: This is a result of the -I Inputfile namenot being passed in to the Command-line. Re-try theoperation making sure to pass the -I input file name tothe command-line call.

ANS2828E Image operations are not supported forthe specified file system.

Explanation: Image backup and restore are notsupported for the specified file system.

System action: The requested image operation is notperformed.


ANS2829E Image operations are not supported forGPFS.

Explanation: Image backup and restore are notsupported for GPFS volumes.

System action: The requested image operation is notperformed.


ANS2830E An incorrect number of parameters wasspecified.

Explanation: The specified command was invokedwith too few or too many parameters.


User response: Try the command again with thecorrect number of parameters.

ANS2831E Incremental by snapshot differencecannot be performed on 'volume-name' asit is of type 'type' and is not aNetApp/N-Series 'fsType' volume.

Explanation: The volume specified cannot be used forperforming NetApp/N-Series snapshot differenceincremental operation. The volume does not correspondto the NFS mount point or the CIFS shared drive for aNetwork Appliance or N-Series NAS volume. Onepossible reason for this failure is that snapshotdifference incremental backups can only be performedagainst NetApp/N-Series NFS volumes on AIX/Linux



platforms, or CIFS volumes on Windows platforms.

Another possible reason for this failure is that the qtreesecurity style for the volume was incorrectly selected. Ifthe CIFS volume is mapped on Windows, ensure thatthe security style is set to NTFS. If the volume ismounted as NFS, ensure that the security style is set toUNIX.


User response: Try the command again with aNetApp/N-Series NFS or CIFS volume with the correctsecurity style.

ANS2832E Incremental by snapshot differencefailed for filespace name. See the error logfor details.

Explanation: Failed to perform NAS NFS/CIFSIncremental by snapshot difference operation.


User response: Take appropriate action based on theinformation in the error log. If the problem persistsplease contact your IBM Tivoli Storage Manageradministrator.

ANS2834E You have to be a root user in order toperform incremental backup usingsnapshot difference.

Explanation: Failed to perform NAS NFS/CIFSincremental backup operation using snapshot differenceas the user was non root.


User response: Please retry the operation as root user.

ANS2835E Incremental backup using snapshotdifference is not supported on thisplatform.

Explanation: NetApp NFS/CIFS incremental backupoperation using snapshot difference is only supportedon AIX, Linux and Windows platforms.


User response: Retry the incremental operationwithout the snapdiff option.

ANS2836E Incremental backup operation usingsnapshot difference is only available forfull volumes.is a partial volume or qtree.

Explanation: Cannot perform NAS NFS/CIFSincremental backup operation using snapshot differenceon the mounted or mapped volume due to one of thefollowing reasons: 1) The volume is actually a qtree. 2)The volume is not a full volume, it is not mounted ormapped to the root of the volume.


User response: Retry the incremental backupoperation by specifying an entire NAS NFS or CIFSvolume.

ANS2837E Unable to access the required storedNetApp filer credentials (user id andpassword) for filer ''.Make sure the SET PASSWORD-TYPE=FILER command was specifiedcorrectly to store the credentials.

Explanation: The user id and password for thespecified NetApp Filer have been either not configuredor have been specified incorrectly.


User response: Use the 'set password -type=filer'command to define the user id and password for thespecified NetApp Filer and retry the snapshotdifferential backup operation.

ANS2838W The file path 'filename' exceeds HSMmaximaum path length.

Explanation: A file that you tried to migrate has apath name that is too long.

System action: File skipped from migration.

User response: Place files into a shorter path to makethem available for migration.

ANS2839E Failed with ONTAPI error 'error_code'while connecting to NetApp Filer'filer_name' using user id 'id_name'. Youmight have provided credentialsincorrectly for this Filer.

Explanation: The user ID and password have beenconfigured incorrectly for the specified Filer.

If you are using the snapdiffhttps option, ensure thatyou are not specifying vFiler volumes as vFiler doesnot support the HTTPS transport type.


User response: Make sure that the credentials youhave specified for the Filer are the correct ones. Use thedsmc set password command to specify the correctcredentials for your Filer and try the command again.

ANS2840E Incremental backup using snapshotdifference is not supported for DataONTAP file server version'version.modification.submodification'.Upgrade the file server 'file-server-name'to Data ONTAP version '7.3' or later inorder to perform incremental backupoperations using snapshot difference.



Explanation: The file server specified is not at theData ONTAP version that supports snapshot differenceAPI.


User response: Upgrade the file server to DataONTAP version 7.3 or later and retry the operation.

ANS2841E Incremental by snapshot difference isonly supported on AIX 64 bit and Linux86 bit clients.

Explanation: Incremental backup using snapshotdifference feature is only available on IBM TivoliStorage Manager AIX 64 bit and Linux 86 clients.


User response: Try the command again with an IBMTivoli Storage Manager AIX 64 bit or Linux 86 client.

ANS2842E TSM for Virtual Environments detectedan error with the createsnap: keyword.createsnap:yes is specified while alsospecifying vmsnapname:VMWareSnapshot Name.

Explanation: While parsing the Input File forFlashCopy Manager for VMWare offload backup, anerror condition was detected with VM Ware snapshothandling. Specifying a VMWare Snapshot name whilespecifying createsnap:yes is not allowed.

System action: The operation cannot continue withoutspecifying the correct createsnap: and vmsnapname:combination.

User response: This is a result of the -I Inputfilecontaining conflicting input for createsnap: andvmsnapname: keywords. If you intend to have TSM forVirtual Environments use a VMWare Snapshot createdby FlashCopy Manager then specify createsnap:no witha valid VMWare Snapshot for the vmsnapname:keyword.

ANS2849E Incremental backup operation usingsnapshot difference failed because asnapshot matching 'snapshot name' couldnot be located on volume NAS volume.

Explanation: A snapshot name or pattern specified bythe BASESNAPSHOTNAME orDIFFSNAPSHOTNAME option could not be located onthe volume being backed up.


User response: Rety the operation and specify asnapshot with the BASESNAPSHOTNAME orDIFFSNAPSHOTNAME which exists on the specifiedvolume.

ANS2850E Error Creating Snapshot: Volume NASvolume is a snapmirror destinationvolume.

Explanation: An attempt was made to create asnapshot on a read only snapmirror destinationvolume.


User response: Rety the operation using theUSEEXISTINGBASE and DIFFSNAPSHOT=latestoptions.

ANS2851E Snapshot Processing Error: .

Explanation: An error occurred due to the reasonspecified in the message


User response: Ensure that the specified volume isonline and allows write access.

ANS2852W Registered Base Snapshot '' no longerexists on volume .

Explanation: The specified base snapshot registered bythe previous backup no longer exists on the specifiedvolume.


User response: The client will attempt to use anexisting snapshot older than the missing registeredsnapshot as the base for the current backup.

ANS2853E Unable to establish base snapshot onvolume .

Explanation: A base snapshot could not be created orselected on the specified volume.


User response: See other error messages to determinewhy the base could be established.

ANS2854E Unable to establish diff snapshot onvolume .

Explanation: A diff snapshot could not be created orselected on the specified volume.


User response: See other error messages to determinewhy the diff could be established.

ANS2855W TSM for Virtual Environments detectedan error while parsing the Input File'input file'. The 'specifier' should not bespecified when using 'specifier'. Optionwill be ignored.




System action: The operation will continue ignoringthis parameter.

User response: This is usually the result of anidentifier used with the wrong option. Please check thatthe options in the Input File matches the requestedoperation and retry the operation.

ANS2856E TSM for Virtual Environments detectedthat the node name representing thevCloud is not specified.

Explanation: A node name that represents the vCloudis not specified in the VMCLI profile.

System action: The operation cannot continue withouta valid vCloud node name.

User response: Specify the vCloud node name in theVE_VCENTER_NODE_NAME parameter in the VMCLIprofile. Then, try the operation again.

ANS2857E TSM for Virtual Environments detectedwhile parsing 'read in line' from theinput file 'input file' that option 'specifier'is required for 'operation' operation.

Explanation: A required option or identifier is missingfrom the input file.


User response: This may be the result of a missingoption or identifier. Verify that the syntax of thecommand and the syntax of the values in the input fileare correct. Then, try the operation again.

ANS2858E Failed to get the list of available VMsfor backup

Explanation: Failed to get the entire list of VMs inorder to choose ones that needed to be backed up.


User response: Verify that configuration parametersfor connection to vCenter.

ANS2859E Failed to locate the Organization VDCnode that is used to store the backed updata.

Explanation: The Organization VDC node that storesthe backed up vApp data was not located. This nodemust be mapped to the Provider VDC node. This issuemight be caused by invalid mapping between theProvider VDC node and the Organization VDC node.


User response: Go to the Configuration page and click'Run the Configuration Wizard' to verify that mapping

information for the Provider VDC node is valid.

ANS2860E The PRESNAPSHOTCMD commandfailed. The snapshot differential backupwill not be executed.

Explanation: The command specified by thePRESNAPSHOTCMD option must completesuccessfully in order to execute the snapshotdifferential backup. If the command completed with areturn code of 0 (zero), it is considered to havecompleted successfully. If the command completed withany other return code, it is considered to have failed. Ifthe command failed then the snapshot differentialbackup is not executed.

System action: The client does not execute thesnapshot differential backup operation.


ANS2861W The POSTSNAPSHOTCMD commandfailed.

Explanation: If the command specified by thePOSTSNAPSHOTCMD option completed with anon-zero return code, the snapshot differential backupoperation continues. The operation continues with awarning-level result. The result of thePOSTSNAPSHOTCMD command does not supersede ahigher result from the snapshot differential backupcommand. For example, if the snapshot differentialbackup command completed with code 12, a lowerreturn code from the POSTSNAPSHOTCMD commanddoes not alter the return code.

System action: The snapshot differential backupcontinues, but with a warning return code of at least 8.

User response: Identify and repair the problem thatcaused the command to fail. Consider wrapping thecommand in a script that always exits with a returncode of zero.

ANS2862E No entry found for the specified StorageVirtual Machine.

Explanation: The SVM does not exist in the registry orpassword file.

System action: No operation is performed.

User response: The user should register the SVMusing the Set NetAppSVM command.



ANS2863E The backup-archive client failed to loadthe vCloud protection runtime library.

Explanation: vCloud protection runtime library is notloaded by the backup-archive client.


User response: Verify that the vCloud runtime libraryexist in the 'plugins' folder under the client installationfolder.

ANS2864E A Hyper-V operation was attempted, butthe Hyper-V role was not detected onthe host system.

Explanation: The Hyper-V role must be enabled onthe host system where the Hyper-V operation occurs.The current host system either does not have theHyper-V role enabled or does not support Hyper-V.

System action: The operation does not start.

User response: If the host system supports Hyper-Vthen enable the Hyper-V role. Otherwise, try theoperation again from a host system that supportsHyper-V and has the Hyper-V role enabled.

If you want to process VMware virtual machines, go tothe IBM Tivoli Storage Manager window, and click Edit> Client Preferences > VM Backup. Click VMWare FullVM or VMWare File Level. Then, click OK.

ANS2865E An error occurred creating or accessing avirtual disk for virtual machine'VM-name'.

Explanation: An error occurred creating or accessing avirtual disk while restoring a virtual machine.


User response: See the client error log for moredetailed information about the error.

ANS2866E An error occurred creating virtualmachine 'VM-name'.

Explanation: An error occurred creating the virtualmachine during the restore operation.



ANS2867E An error occurred querying virtualmachine 'VM-name'.

Explanation: An error occurred querying the virtualmachine during the restore operation.



ANS2868E An error occurred removing virtualmachine 'VM-name'.

Explanation: An error occurred removing the virtualmachine during the restore operation.



ANS2869E A virtual machine on the hypervisor hasa different name but the same ID asvirtual machine to restore 'VM-name'has. Restore not allowed.

Explanation: A virtual machine with a different nameand the same ID than the virtual machine beingrestored exists on the hypervisor.


User response: Choose a different virtual machine torestore to or delete the existing virtuual machine.

ANS2870W An incremental backup of virtualmachine 'vmname' was requested, but thevirtual machine lacks an existingrecovery snapshot. A full backup will betaken to prevent data loss.

Explanation: Removal of the recovery snapshot of avirtual machine does not reset the last successfulbackup time maintained internally. The lack of a resetcreates an inconsistency between the backup time andthe hard disk configuration of the virtual machine. Afull backup fixes the ambiguity and prevent data loss.

System action: An inconsistency in the virtualmachine configuration was detected.

User response: Avoid deleting the recovery snapshotbetween back up operations.

ANS2872E TSM was unable to restore a virtualdisk user metadata entry of virtualmachine 'vmname' to disk 'diskpath'.

Explanation: An attempt to restore a user metadataentry of a disk failed. The user metadata of the diskmay inaccessible or unreachable.

System action: A restore of a virtual disk.

User response: Check the user privileges includeaccess to virtual disk writes or move the disk to anaccessible location.

ANS2873I Virtual machine 'vmname' wassuccessfully restored. If this virtualmachine was restored to a cluster,ensure that the cluster settings enablethe restored virtual machine to operatein high availability mode. High



availability settings, and the preferredset of hypervisor nodes that can operatein high availability mode, might not beset automatically.

Explanation: The specified virtual machine has beenrestored, but the restore process does not alterMicrosoft Failover Clustering High Availability settings.If you restored a virtual machine that you previouslydeleted, or if you restored a virtual machine to a newname and location, the restored virtual machine mightnot be enabled as a high availability resource. Enablehigh availability for this virtual machine by usingMicrosoft Failover Cluster Manager, System CenterVirtual Machine Manager, or by using PowerShellcmdlets.


User response: Use Microsoft Failover ClusterManager, System Center VM manager, or PowerShell toconfigure the cluster to allow this virtual machine toperform in a high availability configuration.

ANS2876E Unable to access the required storedNetApp Management Filer credentials(user id and password) for filer ''associated with storage virtual machine'' .Make sure the SET PASSWORD-TYPE=FILER command was specifiedcorrectly to store the credentials.

Explanation: The user id and password for thespecified NetApp management filer associated with thespecified storage virtual machine have been either notconfigured or have been specified incorrectly.

A storage virtual machine is associated withmanagement filer using the SET NETAPPSVMcommand. Credentials for a management filer arestored with the SET PASSWORD -TYPE=FILERcommand.


User response: Use the 'set password -type=filer'command to define the user id and password for thespecified NetApp Management Filer. Use the 'setnetappsvm' command to associated a storage virtualmachine with a management filer. Ensure that both ofthese commands were specified correctly and retry thesnapshot differential backup operation.

ANS2888E Backup VM Full VM Incremental isunable to run.A valid TSM for Virtual Environmentslicense file (license-file) cannot be located.

Explanation: The license file was not found, or cannotbe opened because of permissions, or the file iscorrupted.



ANS2889I The vApp 'vapp name' was successfullyrestored under the name 'new vapp name'

Explanation: The restore operation was succesful inrestoring the vApp into the specified name.



ANS2891W The vApp 'vapp name' was successfullyrestored. However, failed vms num out ofexisting vms num VMs were not restored.

Explanation: Although the vApp restore operation onthe vCloud completed successfully, one or more VMswere not restored.

System action: The operation completed successfully.However, some VMs were not restored.

User response: Check the dsmerror.log file forinformation about why the VMs were not restored.Then, try the operation again. If the problem persists,visit the IBM Support Portal for additional informationat http://www.ibm.com/support/entry/portal/.

ANS2900E TSM for Virtual Environments detectedthat the scan domain was not specified.

Explanation: While parsing the command line options,no scan domain was detected. This error occurredbecause the -domain option was not specified.

System action: The operation cannot continue withouta valid scan domain.

User response: Run the operation again and specifythe -domain option.

ANS2901E TSM for Virtual Environments detectedthat the domain user was not specified.

Explanation: While parsing the command line options,no domain user was detected. This error occurredbecause the -user option was not specified.

System action: The operation cannot continue withouta valid domain user.

User response: Run the operation again and specifythe -user option.



ANS2902E Save domain password failed infunction func-name with return codereturn-code.

Explanation: An unexpected write access erroroccurred when the function tried to save the domainpassword. Write access does not exist to either theregistry or to the TSM for Virtual Environments onLinux installation folder where the password file issaved.


User response: Grant write access to either theregistry or to the TSM for Virtual Environments onLinux installation folder and try the operation again.

ANS2903E Read domain password failed infunction func-name with return codereturn-code.

Explanation: An unexpected error occurred when thefunction tried to read the domain password.


User response: On Windows, verify that the passwordexists in the registry. On Linux, verify that thepassword exists in the password file. Try the operationagain.

ANS2998I The option 'option' that was found in theinclude/exclude file 'file-name' at the linenumber: number is not supported andwill be ignored by the client.

Explanation: The specified option is valid but notsupported on the current platform and will be ignoredby the client.


User response: You can ignore the message or removethe option from the include/exclude file.

ANS3000I communication-type communicationsavailable on port port-number.

Explanation: The specified communications areavailable on the specified port number.



ANS3001W The default locale, English (UnitedStates), is used because the selectedlocale "locale" is not supported. Thesupported locales are as follows:supportedLocales

Explanation: The locale on the user's system orbrowser is not supported.

System action: The system defaults to the English(United States) locale.

User response: Use the default locale or switch to oneof the supported locales.

ANS3002I Session started for user userid(communication-method address).

Explanation: A session was started for the specifieduser.



ANS3003I The new password is case sensitive.

Explanation: Your account has been updated to usecase sensitive password.

System action: None

User response: Make sure to remember the newpassword as you enter it, including character casing.For more details, contact your TSM administrator.

ANS3004E Session for user userid terminated -invalid password entered.

Explanation: A session was terminated for thespecified user because an invalid password wasentered.

System action: The session with the specified user isterminated.

User response: Re-start the remote client and enter thecorrect password for the specified user.

ANS3005I Session for user userid terminated - idlefor idle-minutes minutes.

Explanation: A session was terminated for thespecified user because there was no activity on thesession for the specified number of minutes.

System action: The session with the specified user isterminated.

User response: Re-start the remote client to begin anew session.

ANS3006I Processing request for the TSM WebClient (ip-address).

Explanation: A request for the Web Client is beingprocessed.





ANS3007I TSM client-name terminating - idle foridle-minutes minutes.

Explanation: The specified client is terminatingbecause it has been idle for the specified time. It will beautomatically started when it is needed.

System action: The client program stops.


ANS3008E Too many symbolic links were detectedwhile resolving name 'file_name'




ANS3009E The Logical Volume Snapshot Agentplugin library was not found.

Explanation: The Logical Volume Snapshot Agent(LVSA) plugin library should have been installed whenthe client was installed, but it cannot be found.


User response: Try the operation again. If the problemrecurs, re-install the TSM client software. If the problempersists, contact IBM technical support for furtherassistance.

ANS3010E The snapshot wizard operation failed.

Explanation: The snapshot wizard operation failedwith a non-zero return code. Check the error log foradditional information.


User response: Review the error log for any errormessages, and then retry the operation after correctingthe cause for failure.

ANS3011E Previous changes have not beencommited.The machine must be rebooted beforethis operation can be performed

Explanation: A previous operation required themachine to be rebooted for the changes to take effect,but the machine has not been rebooted. The machinemust be rebooted before this selected operation can beperformed.


User response: Reboot the machine and then retry theoperation.

ANS3012E The Logical Volume Snapshot Agent isnot installed. Use the Setup Wizard toconfigure either Online Image or OpenFile support and choose the LogicalVolume Snapshot Agent as the snapshotprovider.

Explanation: The selected operation requires theLogical Volume Snapshot Agent, but it is not installed.Use the Setup Wizard to install the LVSA.


User response: Retry the operation after installing theLogical Volume Snapshot Agent.

ANS3013E The specified snapshot provider is notsupported on this version of theoperating system.

Explanation: The specified snapshot provider is notsupported on the version of the operating system youare currently running. If another snapshot provider isavailable, select it and retry the operation.


User response: If another snapshot provider isavailable, select it and retry the operation.

ANS3014E Expose snapshot failed for backupdocument 'xml-backup-doc-file'.

Explanation: Expose snapshot failed.



ANS3100E Unable to get the iSCSI initiator name.The Windows error is (error)

Explanation: The iSCSI initiator name is notconfigured on the system.


User response: See the appropriate MicrosoftDocumentation about how to configure the iSCSIinitiator name.

ANS3101E The mount operation for virtualmachine 'vmname' failed with rc =return-code. For more details, check theRecovery Agent logs.

Explanation: An error occurred during the mountoperation. See the output from the previous operation



to identify the cause of the error.


User response: Review the recovery agent logs forinformation about how to resolve this issue.

ANS3102I 'VMNAME' mounted successfully and isready

Explanation: The mount operation for the specifiedvirtual machine completed successfully. As a result, thevirtual machine is ready for a file restore operation.


User response: None

ANS3103E Unable to load the dynamic link library(iscsidsc.dll). The Windows error is(error)

Explanation: The iSCSI dynamic link library(iscsidsc.dll) cannot be found on the system.


User response: See the appropriate MicrosoftDocumentation about how to install the dynamic linklibrary (iscsidsc.dll).

ANS3104E A target was not found on the iSCSIportalThe missing target is 'target'

Explanation: The iSCSI portal is unable to discover allof the targets that were created by the IBM TivoliStorage Manager Recovery Agent command-lineinterface.


User response: See the appropriate MicrosoftDocumentation about how to correct this iSCSI portalissue. Search http://technet.microsoft.com/en-US/windowsserver for iSCSI troubleshooting information.

ANS3105E Unable to connect all targets on theiSCSI PortalThe target that is not connected is'target'. Windows error is (error)

Explanation: The iSCSI portal is unable to connect alldiscovered targets that were created by the IBM TivoliStorage Manager Recovery Agent command-lineinterface.


User response: See the appropriate MicrosoftDocumentation about how to correct this iSCSI portalissue. Search http://technet.microsoft.com/en-US/windowsserver for iSCSI troubleshooting information.

ANS3106E Windows Configuration Manager isunable to scan for new hardware.Windows error is (error)

Explanation: The new iSCSI disk connection cannot bedetected by the Windows Configuration Manager.


User response: See the appropriate MicrosoftDocumentation about how to correct this hardwarescan issue.

ANS3107E The attempt to retrieve information fordisk 'disk' failed with Windows error(error).

Explanation: A Windows API call failed to retrieve thedisk information.


User response: See the appropriate MicrosoftDocumentation for information about how to resolvethis Windows API call issue.

ANS3108W The disk with label='label' is notmounted because it was excludedduring the backup (Reason: 'reason').

Explanation: The disk cannot be mounted because itwas excluded during backup. It is not possible torecover files from any of the file systems or volumesthat use this disk.


User response: If files from the affected file systems orvolumes must be recovered, ensure that the disk isincluded in the backup.

ANS3109E The mount cannot be retrieved becausethe following mount ID cannot befound: mountID

Explanation: An error occurred while retrieving themount with the mount ID that is specified.



ANS3110E Unable to communicate with Windowsdevice 'device'. The Windows error is(error)

Explanation: A Windows API call failed to open aWindows device.





ANS3111E Unable to mount the same dynamicdisks mutliple times.The disk 'disk' signature is the same asthe disk signature of another disk thatis online.

Explanation: It is not possible to attach a second diskto the system with the same disk signature.


User response: The other disk with the identical disksignature must be dismounted before you can attemptthe operation again.

ANS3112E Windows Virtual Disk Service is notable to detect all new devices.

Explanation: The Virtual Disk Service VDS is unableto access all iSCSI targets. Some targets are missing ornot working.

System action: The operation will be rolled back andstopped.

User response: Determine why the data mover cannotaccess some iSCSI targets. Determine that the TSMserver is working correctly. Determine that the iSCSIservice is running. Search the Windows event log forproblems with the missing devices.

ANS3113E The virtual machine 'name' has at leastone mirror or RAID5 volume. Mirrorand RAID5 support is disabled!

Explanation: During the mount operation it wasdetected that the virtual machine has a mirror orRAID5 volumes. The support for such volumes werediabled by the Administrator.


User response: Contact the Administrator for moreinformation.

ANS3114E The attempt to retrieve information forvolume 'volume' failed with Windowserror (error).

Explanation: A Windows API call failed to retrieve thevolume information.



ANS3115E The attempt to bring disk 'disk' onlinefailed with Windows error (error).

Explanation: A Windows API call failed to bring thedisk online.



ANS3116E The attempt to create directory 'dir'failed with Windows error (error).

Explanation: A Windows API call failed to create thedirectory.



ANS3117E The mount volume attempt at directory'dir' failed with Windows error (error).

Explanation: A Windows API call failed to mount thespecified volume.



ANS3118E Unable to determine the operatingsystem type of the VM to be restored.

Explanation: The operating system type of the VM tobe restored cannot be determined. This issue can occurwhen the restore parameter -VMOSType is notspecified or it specifies an incorrect operating systemtype.


User response: Use the -VMOSType parameter tospecify the correct operating system type of the VM tobe restored.

ANS3119W Operating system type "name1" isdetected but operating system type"OSname" is specified.

Explanation: The operating system type of thedetected VM does not match the type specified withthe restore parameter -VMOSType. Inconsistentoperating system types might negatively impact themount operation. The operation will continue using"OSname" as the operating system type.


User response: If the mount operation fails, try theoperation again and use automatic detection or specifythe correct operating system.



ANS3122E The Microsoft iSCSI Initiator Serviceencountered an error. The Windowserror is (error).

Explanation: The Microsoft iSCSI Initiator Serviceencountered an error during an iSCSI operation. Thiserror caused the operation to stop.


User response: See the Microsoft iSCSI InitiatorService error message to determine the cause of theerror. If necessary, see the appropriate MicrosoftDocumentation for information about how to resolvethis iSCSI Initiator error.

ANS3123E Unable to read or write the local VMfile restore data.filenameFile cannot be accessed or is damaged.

Explanation: For VM file restore operations, data mustbe stored on the local data mover in a directory thatthe user running the restore can access. The data filemight also be damaged.


User response: To store the VM file restore data, thedata mover application requires read and write accessto the C:\Documents and Settings\AllUsers\Application Data\Tivoli\TSM\ or C:\ProgramData\Tivoli\TSM folder.Set the access rights to this directory so that your userhas the correct rights.If the file was damaged it can be helpful to replace thecurrent version with the .bak file.

ANS3124E The user session cannot be retrievedbecause the following context ID cannotbe found: contextID

Explanation: An error occurred while retrieving thecurrent user session with the context ID that isspecified. The error might be caused by a session thattimed out.


User response: If the session timed out, log in again.

ANS3125E The local data for file restore mountwith the ID: id and virtual machinename 'name' cannot be found!

Explanation: The local data set for the specifiedmount ID or virtual machine name cannot be found.


User response: Use the query "dsmc q vm <name>-vmrestoretype=mount" command to get the correctmount ID and virtual machine name for the cleanup.

ANS3126E The node name of the Linux mountproxy partner could not be found.

Explanation: An error occurred while querying theIBM Tivoli Storage Manager server for Linux mountproxy partner; the node could not be found.Communications with the Linux mount proxy partneris required to perform Linux VM file restore operations.


User response: Check the Linux mount proxy partnernode configuration and ensure that the node iscorrectly configured and running.

ANS3127E The IP address or port of the Linuxmount proxy partner could not befound.

Explanation: An error occurred while querying theIBM Tivoli Storage Manager server for the Linux mountproxy partner. The IP address or port of that partnercould not be found; the address and port are requiredto process file restores for Linux VMs.


User response: Check the node configuration andensure that the Linux mount proxy partner is correctlyconfigured and running. Verify that the Client AcceptorDaemon on the Linux mount proxy partner is runningand able to connect to the IBM Tivoli Storage Managerserver.

ANS3128E The node name of the Windows mountproxy does not comply with TSMnaming conventions.

Explanation: An error occurred while querying theIBM Tivoli Storage Manager server for Linux mountproxy partner. The name of the Windows mount proxydoes not comply the naming convention. A correctname is required for processing of Linux VMs.


User response: Check the node configuration andensure that the mount proxy name is correct. Use theweb based configuration wizard to set up theconfiguration.

ANS3129I The mount cleanup of VM 'VMNAME'completed.

Explanation: The mount cleanup operation for thespecified virtual machine completed.


User response: None



ANS3130E The mount cleanup operation for virtualmachine 'vmname' failed with rc =return-code

Explanation: An error occurred during the mountcleanup operation. See the output from the previousoperations to identify the cause of the error.


User response: Check the dsmerror.log file forinformation about how to resolve this issue.

ANS3131E The operation to disconnect the iSCSItargets from the Windows data moverfailed.

Explanation: An error occurred during the mountcleanup operation while disconnecting the iSCSItargets. See the output from the previous operations toidentify the cause of the error.


User response: Open the Windows iSCSI Initiator Tooland disconnect the targets and remove the target portal.The tool can be found in "Administrative Tools" ->"iSCSI Initiator"

ANS3132E The Windows iSCSI Service is unable toget a list of all currently runningsessions. The Windows error is (error)

Explanation: The iSCSI Service could not get a list ofall connected targets and the corresponding sessions.


User response: See the Microsoft documentation forinformation to correct this iSCSI issue. Searchhttp://technet.microsoft.com/en-US/windowsserverfor iSCSI troubleshooting information.

ANS3133E The target 'target' could not bedisconnected by the iSCSI portal. TheWindows error is (error)

Explanation: The iSCSI portal is unable to disconnectall the connected targets that were created by therecovery agent command-line interface.


User response: See the Microsoft documentation forinformation to correct this iSCSI portal issue. Searchhttp://technet.microsoft.com/en-US/windowsserverfor iSCSI troubleshooting information.

ANS3134E The Windows iSCSI Service is unable toget list of all currently available portals.The Windows error is (error)

Explanation: The iSCSI Service has a problem gettinga list of all available portals.



ANS3135E The removal of iSCSI Portal 'target'failed with a Windows error of (error)

Explanation: The iSCSI Service cannot remove theiSCSI Portal.



ANS3136E The mount ID was not specified in thecleanup operation.

Explanation: The -MOUNTID parameter must bespecified to perform a 'mountcleanup' operation.


User response: Use the query "dsmc q vm <name>-vmrestoretype=mount" command to get the correctmount ID for the cleanup

ANS3137W 'VMNAME' mount completed witherrors.

Explanation: The mount operation for the specifiedvirtual machine completed with errors. Only a subsetof the virtual machine's disks are ready for a file restoreoperation.

System action: The VM disks that failed werereported in previous messages.

User response: Review the previous error messagesfor the cause of each failure.

ANS3138E The unmount of the volumes failedduring the cleanup operation of mountID mountid

Explanation: An error occurred during the mountcleanup operation while unmounting the volumes.


User response: See the output from the previousoperations to identify the cause of the error.

ANS3139E The attempt to unmount the disk failedwith Windows error (error).

Explanation: The Windows API call failed to unmountthe disks.




User response: See the Microsoft documentation forinformation to correct this issue; search thedocumentation for this Windows error.

ANS3140E The connection to the following iSCSItargets failed: 'target_list'.

Explanation: The iscsiadm command-line interfacewas not able to connect to the specified iSCSI targets,from the Linux mount proxy machine.


User response: If the target is already connected onthe Linux mount proxy machine, log out from thetarget, for example: iscsiadm -m node -T targetname--logout Also, verify that the iSCSI server address iscorrectly specified.

ANS3141W Mounting the following devices failed:'device_list'.

Explanation: It was not possible to mount thespecified devices on the Linux mount proxy machine.

System action: The operation continues to mount theother devices.

User response: Perform a cleanup, or try to manuallyunmount the devices on the Linux mount proxymachine.

ANS3142E The Windows Virtual Disk Serviceencountered an error. The Windowserror is (error)

Explanation: The Windows Virtual Disk Service is notworking correctly.


User response: See the Microsoft documentation forinformation to correct this issue. Searchhttp://technet.microsoft.com/en-US/windowsserverfor Virtual Disk Service troubleshooting information.

ANS3143W The ISCSI service is not running. Itsstate is 'state'.

Explanation: The ISCSI Service is not running.

System action: The service maybe suspended,however operations cannot continue.

User response: Start the ISCSI service.

ANS3144W The ISCSI service is not running. Filerestore mount operations will not work.

Explanation: The ISCSI Service is not running. Thisservice is required on the Windows and Linux mountproxy for file restore mount operations. Full VM instantaccess and instant restore are not affected.

System action: Mount operations for file restorecannot continue.

User response: Start the ISCSI service if you want toperform a file restore operation. For VM instant accessand instant restore, no action is required.

ANS3145E A Windows API call has failed.

Explanation: A Windows API call has failed.

System action: Operations cannot continue.

User response: See the dsmerror.log for moreinformation.

ANS3146E The cleanup operation to unmount thevolume volume failed. The mounted filesystem is busy.

Explanation: An error occurred during the mountcleanup operation while unmounting the volumes onthe Linux mount proxy machine.


User response: Ensure the file system is not in useand then try the cleanup operation again, or manuallyunmount the volume on the host.

ANS3147W The iSCSI Target 'iscsi_target'wasdisconnected successfully, but theattempt to delete the target failed.

Explanation: It was not possible to delete the objectafter the target was disconnected.


User response: Try to manually delete the object onthe Linux machine. For example: iscsiadm -m node -Ttargetname -o delete

ANS3148W The iSCSI Target 'iscsi_target' wasalready connected.

Explanation: The target was already connected on theLinux mount proxy machine. This error can occur if acleanup was not perfomed, or if the cleanup was onlypartially successful.


User response: The Linux mount proxy machine triedto reuse the already connected targets. If the volumesare not correctly mounted, manually disconnect thetargets on the Linux mount proxy machine. Forexample: iscsiadm -m node -T targetname --logout;iscsadm -m node -T targetname -o delete



ANS3149E The iSCSI target 'target' failed todisconnect from the Linux machine.The message from the iscsiadmcommand-line interface is:message_output

Explanation: The iscsiadm command-line interfacewas unable to disconnect the specified iSCSI targetfrom the Linux machine.


User response: See if the target is alreadydisconnected on the Linux machine, or try to manuallydisconnect it. For example, iscsadm -m node -Ttargetname --logout Verify that the iSCSI server addressis correctly specified.

ANS3150W The block device 'block_device' of type'device_type' failed to mount. The systemmessage is:'system_message'

Explanation: It was not possible to mount one ormore devices on the Linux machine.

System action: The operation continues to mount theother devices.

User response: Perform a cleanup, or try to manuallyunmount the devices on the Linux machine.

ANS3151E The initiator.iscsi file does not exist orcannot be opened.

Explanation: The file does not exist or cannot beopened.


User response: The ISCSI service may not be installed.

ANS3152E The initiator.iscsi file does not have avalid initiator id entry.

Explanation: No ISCSI Initiator ID exists.


User response: The ISCSI servoce may not beinstalled.

ANS3153E The mount cleanup completed witherror for mount ID 'mountid' of virtualmachine 'VMNAME'; Error log 'errlog' isavailable on 'machinename'.

Explanation: An error occurred during the mountcleanup operation while unmounting the volumes. Themounted file systems may be busy. See the error log toidentify the cause of the error.


User response: Ensure the file systems are not in use

and the cleanup or manually unmount the volumes onthe host.

ANS3154E The ISCSI service is not installed.

Explanation: The ISCSI Service is not installed.


User response: Install the ISCSI service for yourplatform.

ANS3155I The Windows data mover is 'name' (ip)

Explanation: The DNS name and the IP of theWindows data mover.


User response: This information can be used todetermine if hostname and IP of the Windows datamover are correctly resolved. The information can helpif the iSCSI connection is not working as expected.

ANS3156I The iSCSI server address used is 'ip'

Explanation: This message returns the IP address ofthe iSCSI server.


User response: This information can be used todetermine if the IP address of the iSCSI server addressis correctly resolved. The information might help youtroubleshoot problems if the iSCSI connection is notworking as expected.

ANS3157I The Linux data mover is 'name' (ip)

Explanation: The DNS name and the IP address of theLinux data mover.


User response: This information can be used todetermine if hostname and IP of the Linux data moverare correctly resolved. The information might help youtroubleshoot problems if the iSCSI connection is notworking as expected.

ANS3158W The attempt to create the Windowsshare failed with Windows error (error).The share is not created.

Explanation: The creation of the Windows share failedwith the given user/group name.

System action: The Windows share is not created. Theoperation continues.

User response: One common reason for failures is thatthe specified user/group does not exist. Ensure that theWindows user or group name exists and is accessibleon the Windows data mover. If this is a domain user orgroup, the Windows data mover has to be part of that



domain. If this does not resolve the problem, see theappropriate Microsoft Documentation for informationabout this error code.

ANS3159E The attempt to remove the WindowsShare failed with Windows error (error).

Explanation: A Windows API call failed to remove theWindows Share.



ANS3160W The attempt to export Linux file systemfailed with error: NFS service is notrunning.

Explanation: exportfs command failed to make thedirectory on the Linux mount proxy available for NFSclients to mount.

System action: The operation continues withoutcreating the NFS export.

User response: Resolve the error on the Linux mountproxy. Manually export the directory.

ANS3161E The attempt to unexport Linux filesystem failed with error: NFS service isnot running.

Explanation: exportfs command failed to unexport thedirectory on the Linux mount proxy.


User response: Resolve the error on the Linux mountproxy. Manually unexport the directory.

ANS3162I The Mount cleanup of VM 'VMNAME'with mount id 'Id' and snapshot date'date time' completed.

Explanation: The mount cleanup operation for thespecified virtual machine completed.


User response: None

ANS3163W The Linux Operating System is not atthe minimum level. Mount operationsmay not complete successfully.

Explanation: The Linux Operating System is not at theminimum level.

System action: Mount operations may not completesuccessfully.

User response: Upgrade the Linux operating systemto at least the minimum level.

ANS3164W The minimum level for 'os' is 'level'.Your current level is 'actual'.

Explanation: The Linux Operating System is not at theminimum level.


User response: Upgrade the Linux operating systemto at least the minimum level.

ANS3165W A Package installed on the LinuxOperating System is not at theminimum level. Mount operations maynot complete successfully.

Explanation: A Package installed on the LinuxOperating System is not at the minimum level.


User response: Upgrade the package to at least theminimum level.

ANS3166W The minimum level for package 'package'is 'level'.Your current level is 'actual'.

Explanation: A Package installed on the LinuxOperating System is not at the minimum level.


User response: Upgrade the package to at least theminimum level.

ANS3167E IBM Tivoli Storage Manager RecoveryAgent service is not installed.

Explanation: IBM Tivoli Storage Manager RecoveryAgent service is not installed.


User response: Ensure that IBM Tivoli StorageManager Recovery Agent is correctly installed andconfigured.

ANS3168E IBM Tivoli Storage Manager RecoveryAgent service is not running.

Explanation: IBM Tivoli Storage Manager RecoveryAgent service is not running.


User response: Start IBM Tivoli Storage ManagerRecovery Agent service. The Recovery Agent can bestarted using "net start RecoveryAgent" or byreferencing TSM Recovery Agent in services.msc.



ANS3169E The mount proxy's operating systemmust be Windows Server 2008 or neweroperating system.

Explanation: The Windows operating system is not atthe minimum level.


User response: Upgrade the Windows mount proxy toa supported operating system.

ANS3170W The attempt to export Linux file systemfailed with error: exportfs commandfailed.

Explanation: exportfs command failed to make thedirectory on the Linux mount proxy available for NFSclients to mount.

System action: The operation continues withoutcreating the NFS export.

User response: Resolve the error on the Linux mountproxy. Manually export the directory.

ANS3171E The attempt to unexport Linux filesystem failed with error: exportfscommand failed.

Explanation: exportfs command failed to unexport thedirectory on the Linux mount proxy.


User response: Resolve the error on the Linux mountproxy. Manually unexport the directory.

ANS3172T Restoring virtual machine 'source' to newVM with name 'destination'.

Explanation: The specified virtual machine will berestored as a new vm with a new name.

System action: None


ANS3173E The Linux devices failed to mountcorrectly.

Explanation: The Linux devices failed to mountcorrectly.

System action: Mount operations did not notcomplete successfully.

User response: Verify that the Linux mount proxyserver can communicate with the TSM server.

ANS3174E The virtual machine mount failed.

Explanation: An error occurred during the mountoperation.


User response: Check the command-line output forthe messages that specify what problems wereencountered during the operation.

ANS3175E The VM mount cleanup failed.

Explanation: An error occurred during the mountcleanup operation.


User response: Check the command-line output forthe messages that specify what problems wereencountered during the operation.

ANS3176W Unable to locate the Windows user orgroup named 'name'. The share is notcreated.

Explanation: TSM was unable to map the specifieduser or group name to a Windows security identifier.

System action: The Windows share is not created. Theoperation continues.

User response: One common reason for this messageis that the specified user or group does not exist.Ensure that the Windows user or group name existsand is accessible on the Windows data mover. If this isa domain user or group, the Windows data mover hasto be part of that domain.

This message can also indicate that the Windows datamover is not able to access the active directory domainserver. Ensure that network problems are notpreventing the Windows data mover fromcommunicating with the active directory domain server.

ANS3177E No iSCSI target was connected. Checkyour iSCSI options for backup-archiveclient.

Explanation: No iSCSI target was found or connectedon the Linux mount proxy machine.

System action: The operation is rolled back.

User response: Check that iSCSI is setup correctly onyour Windows as well as your Linux mount proxy. Onecommon reason for a failure is that theVMISCSIServeraddress option is not specified or is setincorrectly in the options file of the Windows datamover.



ANS3178E Volume 'volume' of type 'file_system_type'has not been unmounted. Systemmessage:'system_message'

Explanation: An error occurred during the mountcleanup operation while unmounting the volumes onthe Linux mount proxy machine.


User response: Ensure the file system is not in useand then try the cleanup operation again, or manuallyunmount the volume on the Linux mount proxy.

ANS3179W Another folder share with the samename 'name' already exists.

Explanation: TSM was unable to create a folder sharewith the specified name because a share with thatname already exists.

System action: The folder share is not created. Theoperation continues and the VM disks are mounted forfile restore on the mount proxy.

User response: Use operating system commands tocreate the share of the folder with a unique name anddelete it before running the dismount operation.

ANS3180W The parameter 'name' contains charactersthat are not allowed and have beenremoved.Resulting value is 'new'

Explanation: Some characters cannot be used on multiplatform environments. To solve compatibly problemsonly a limited set of characters are allowed on thisspecific parameter.

Parameter "-MOUNTPoint" is restricted at[a-z][A-Z][0-9][:][/][\][_]

Parameter "-MOUNTTag" is restricted at[a-z][A-Z][0-9][_]

Parameter "-EXPORTParameter" is restricted onWindows at [a-z][A-Z][0-9][ ][-][_][\][@]

Parameter "-EXPORTParameter" is restricted on Linuxat [a-z][A-Z][0-9][.][:]

System action: The operation continues with modifiedparameter.

User response: None

ANS3181E The registry keyHKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\partmgr\Parameters\CrPolicy is set to an othervalue than 3.

Explanation: If the registry keyHKEY_LOCAL_MACHINE\SYSTEM\

CurrentControlSet\Services\partmgr\Parameters\CrPolicy is set to an other value than 3 it can be thatthe machine hangs during a mount operation. Changethe value to 3 and reboot the machine.


User response: The registry keyHKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\partmgr\Parameters\CrPolicy is not documented by Microsoft. Sometimesthis key is set to a value other than 3 what can lead toproblems with the mount operation. Set the value to 3and reboot the machine.

ANS3182E The mount cleanup operation timed outwaiting minutes minutes for responsefrom Linux Mount Proxy.

Explanation: The Windows Mount Proxy didn'treceive any response from Linux Mount Proxy withinthe given timeout. The Linux Mount Proxy is possiblein hanging state.


User response: Check the status of Linux MountProxy machine and mount proxy trace file for moredetails. In the case of a complete system hang onumount, a reboot followed by manual mount cleanupof the Linux mount proxy machine may be required.

ANS3183W A duplicate device UUID has beenfound during mount operation. Thedevice "deviceNameVM" of the target VMhas the same UUID of the device"deviceNameMP" of the mount proxymachine. The device "deviceNameVM"has been excluded from the list ofvolumes to be mounted on the mountproxy.

Explanation: The target VM has a duplicate deviceUUID with the mount proxy.

System action: The device of the target VM is skippedand not mounted. The operation continues.

User response: This problem can occur if the targetVM was cloned from the same template as the mountproxy. Check the block devices of the target VM byusing the 'blkid' command and make sure that noduplicate UUIDs are present with the mount proxymachines. If a duplicate device belongs to the targetVM and it is used, then assign to it a new UUID,otherwise remove such device.

ANS3184W A duplicate device UUID has beenfound during the LVM activation phaseof mount operation. The 'vgimportclone'command was not able to generate anew UUID for the LVM device"LVMdeviceName" resulting in a



duplicated UUID with the device"LVMdeviceName2" of the mount proxymachine. The device "LVMdeviceName3"has been excluded from the list ofvolumes to be mounted on the mountproxy.

Explanation: The 'vgimportclone' command was notable to generate a new UUID for this LVM device,resulting in a duplicated UUID.

System action: The device of the target VM is skippedand not mounted. The operation continues.

User response: This problem has been observed onsome Linux distributions where the 'vgimportclone'command was not able to generate a new UUID. It canalso happen if the target VM was cloned from sametemplate as the mount proxy. To resolve this problem,check the block devices of the target VM by using the'blkid' command and make sure that no duplicateUUIDs are present with the mount proxy machines. If aduplicate device belongs to the target VM and it isused, then assign to it a new UUID, otherwise removesuch device.

ANS3401W The entity name is invalid.

Explanation: A volume with this name could not befound or is not suitable for server-free operations.


User response: Specify the correct name.

ANS3402W name: A system call func failed with coderc.

Explanation: An error occurred while obtaininginformation from the operating system. The volumeinformation could not be obtained.

System action: Processing can continue if theinformation being obtained is not critical for theoperation or if it is expected behaviour in the context ofthe operation being performed.


ANS3403W Volume name cannot be opened forreading. System error code is err.

Explanation: The named volume could not be opened.Examples of why this can occur include, but are notlimited to: the device is not a valid system device, thedevice is locked by another application, or the userdoes not have correct or permissions. The operatingsystem error code shown in the message indicates thespecific reason for the failure.


User response: Use your operating system's tools toobtain the description of the error code. Also check theerror log for any other messages that might indicate areason for the failure. Try to correct any indicatedproblems, then try the operation again. If the problempersists, contact IBM technical support for furtherassistance.

ANS3404W An error occured reading volume name.

Explanation: The named volume could not be read.Examples of why this can occur include, but are notlimited to: the data being read is outside the validrange of the volume, or the device is locked by anotherapplication. The operating system error code shown inthe message indicates the specific reason for the failure.

System action: If server-free data movement is used,processing continues using non-server-free datamovement. Otherwise processing stops.


ANS3405W File system fs on volume name isunknown.

Explanation: The file system on the volume is notsupported for the operation being performed.

System action: If server-free data movement is used,processing continues using non-server-free datamovement. Otherwise processing stops.


ANS3407W name is not local.

Explanation: The drive or filesystem is not local and isnot suitable for image backup.


User response: Specify a volume that is local.

ANS3408E System call 'umount' failed for volume'volume' with errno='error'. Please takesuitable action based on errno and retrythe operation.

Explanation: Umount failed for the specified volumewith the indicated errno. Please take suitable actionbased on errno and retry the operation.




User response: Check errno for umount failure andtake corrective action before retrying the operation.

ANS3409W An error occurred writing to volumename.

Explanation: TSM could not write to the namedvolume. Examples of why this can occur include, butare not limited to: the data being written is outside thevalid range of the volume, or the device is locked byanother application. The operating system error codeshown in the message indicates the specific reason forthe failure.



ANS3410E The operating system refused a TSMrequest for memory allocation.

Explanation: TSM requires access to memory in orderto store information as processing proceeds. In thiscase, more memory was requested than the operatingsystem would allocate. Possible reasons include:


The process in which the program runs hasexceeded the maximum memory that it is allowedto allocate.

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


User response: Close all unneeded applications andtry the operation again. If the operation still fails, trydividing the task into serveral smaller units. Forexample, if a file specification contains several highlevel directories, run the TSM task serially for eachdirectory. If the TSM task is an incremental backup, usethe option "-memoryefficientbackup=yes".

For UNIX systems that support resource limits, checkto see b if the memory resource limit is too low byentering the following command: ulimit -a


ANS3411E Invalid arguments were passed tofunction name.

Explanation: The named function did not receivecorrect arguments to proceed. Please check error log foradditional errors following this one for furtherexplanation.


User response: Retry the operation. If problem persistscontant your TSM administrator.

ANS3412I DiskMapper does not support name forentity name.

Explanation: The requested function is notimplemented in DiskMapper at this time. Please reportthis error to your TSM administrator.


User response: Contact your TSM administrator.

ANS3413I DiskMapper object 'name' type 'name' isnot valid.

Explanation: The named object is not valid on theoriginating client system.


User response: Retry the operation. If the problempersists, review the client error log for other messagesthat might be related to this problem. Contact yourTSM administrator for additional help.

ANS3414I Disk 'name' is not part of any containerdefined on the system.

Explanation: None.

System action: None. This is informational message.


ANS3415W At least one of the disk containing datafor 'name' has bad blocks.

Explanation: One or more physical disks containingdata blocks of the above object has bad blocks and therequested operation can not continue.

System action: The system may find a work-around tocomplete the requested operation, pleasecheck consolelog and error log for additional information oncorrective actions taken or suggested user action.

User response: Depending on the operation TSM maysuggest an alternate way to complete the operation.Check your error log, sched log, or console log foradditional information.



ANS3416E The volume 'name' is currently in use byother process.

Explanation: The operation requires exclusive accessto the volume. The most likely cause of this failure isthat other process on the system has the volumeopened.


User response: Check applications running on yoursystem to ensure that volume is not opened by any ifthe process and then retry the operation.

ANS3417W name: A system call func failed with coderc - strerror

Explanation: An error occurred while obtaininginformation from the operating system. The volumeinformation could not be obtained.

System action: Processing can continue if theinformation being obtained is not critical for theoperation or if it is expected behaviour in the context ofthe operation being performed.


ANS3418W Memory allocation request for imagebackup operation was refused by theoperating system.

Explanation: TSM requires access to memory in orderto store information about used blocks of a file system.In this case, more memory was requested than theoperating system would allocate.

System action: If imagegapsize is too small for adedicated filesystem and TSM faces out-of-memorycondition then TSM automatically switches to fullvolume backup. Operation continues withimagegapsize = 0.

User response: Some recommendations to avoid theout-of-memory condition:

check to see if the memory resource limit is too lowby entering the following command: ulimit -aThen you can ask the UNIX system root user toincrease memory limit.

increase the value of the imagegapsize option. Thebigger imagegapsize is used, the less memory isneeded for image backup, but more unused data issent to server. And vice versa: the smallerimagegapsize is used, the more memory is neededfor backup, but less unused data is sent to server.The outcome also depends much on how data isspread on the volume.

ANS14000E Error processing 'filespace-name': filespace does not exist.

Explanation: The specified file space (domain) isincorrect or does not exist on the workstation. If themessage results from the BACKUP IMAGE commandwith the -MODE=INCREMENTAL option, it means thatyou have entered the name of a raw logical volume.The MODE=INCREMENTAL option is not valid forraw logical volumes.


User response: Try the operation again, specifying anexisting domain (drive letter or file system name). Ifthe message resulted from improper use of theMODE=INCREMENTAL option, try the commandagain, omitting that option.

ANS14001E The file space for domain 'filespace-name'could not be found on the TSM server.




ANS14002E Error processing 'filespace-name': volumelabel does not exist

Explanation: The selected drive does not have a label.

System action: TSM is unable to do the requestedoperation without a drive or label entered.

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

ANS14003E Error processing 'filespace-name':duplicate volume label encountered

Explanation: The selected drive has a duplicatevolume label. Because TSM uses the volume label tokeep track of backup/archive information, it cannotback up or archive files from a drive with a duplicatevolume label.

System action: TSM cannot select the drive.

User response: If the volume needs to be available tothe system, exit TSM, and assign a volume label to thedrive. Restart TSM and retry the operation.



ANS14004E Error processing 'filespacenamepath-namefile-name': destination fileor directory is write locked




ANS14005E Error processing 'filespacenamepath-namefile-name': file not found

Explanation: The file being processed for backup,archive or migrate no longer exists on the client.Another process deletes the file before it can be backedup, archived or migrated by TSM.



ANS14006E Error processing 'filespacenamepath-namefile-name': directory pathnot found

Explanation: The operating system returned a "pathnot found" status when IBM Tivoli Storage Managerattempted to access the directory. You either havespecified a directory that does not exist, as shown inthe message (path-name), or the directory beingprocessed no longer exists on the client because anotherprocess deleted it before it could be backed up orarchived by IBM Tivoli Storage Manager.

System action: The directory is skipped, processingcontinues

User response: Recheck all spelling and punctuation,particularly the placement of directory delimiters (forexample, "\"). Correct the syntax if it is incorrect, thenretry the operation. Ensure that the path is specifiedcorrectly and that the directory actually exists. Retrythe command with the corrected path and directoryname. If you cannot correct the directory name, use theExclude option to exclude the directory from theoperation.

ANS14007E Error processing 'filespacenamepath-namefile-name': access to theobject is denied




ANS14008E Error processing 'filespacenamepath-namefile-name': file istemporarily unavailable

Explanation: File is temporarily unavailable.


User response: Check and see if file is locked by otherprocess. If not, retry the command.

ANS14009E Error processing 'filespacenamepath-namefile-name': disk fullcondition


System action: The client prompts you for action:

v Retry this object

v Skip this object

v Abort the action

User response: Select the appropriate action for thisobject. Create some free space on the destination diskbefore you retry the operation. Another option is torestore or retrieve the file to another disk.

ANS14010E Error processing 'filespacenamepath-namefile-name': stale NFS handle

Explanation: An NFS file system becomes stale.


User response: Verify that the NFS file system ismounted. If the problem persists, unmount andremount the file system, then try the operation again.

ANS14011E Error processing 'filespacenamepath-namefile-name': no file handlesavailable




ANS14012E 'filespace namepath-namefile-name' alreadyexists. It will be skipped.

Explanation: The client tried to restore or retrieve thespecified file, but the file already existed in the targetrestore location and the user chose not to replace theexisting file.

ANS14004E • ANS14012E


System action: The file is skipped, a message islogged in dsmerror.log, and restore or retrieveprocessing continues with the next object.

User response: The file was skipped because eitherREPLACE NO was in effect, causing all existing filesand directories to be skipped, or REPLACE PROMPTwas in effect, and when prompted, the user chose toskip this file or all existing directories and files. Noadditional action is necessary if the decision to skip thefile was deliberate. Otherwise the operation can beretried using either REPLACE ALL REPLACEPROMPT.

ANS14013E Error processing 'filespacenamepath-namefile-name': invalid filehandle

Explanation: An internal system error occurred. A fileoperation failed because an invalid file handle waspassed.


User response: Report the problem to your systemadministrator, and then retry the operation.

ANS14014E Error processing 'filespacenamepath-namefile-name': unknown systemerror (error-code) encountered. Programending.

Explanation: An unrecognized and unexpectederror-code occurred within the client program. This is aprogramming failure and the client program ends.


User response: Try the operation again. If the problemcontinues, report the error to your TSM administrator.

ANS14015E Error processing 'filespacenamepath-namefile-name': unexpected TSMerror (error-code) encountered

Explanation: An unexpected error occurred. Thismight be a low-level system or communication errorthat TSM cannot handle or recover from.


User response: Try the operation again. If the problemcontinues, look for other indications of systemproblems to determine where the problem exists. Mostsystems have error or event logs which may containadditional information. See your system administratoror TSM administrator for further help.

ANS14016E Error processing 'filespacenamepath-namefile-name': file is beingexecuted; write permission denied

Explanation: The current file cannot be opened to

write to because it is currently being run by anotheroperation.



ANS14017E Error processing 'filespacenamepath-namefile-name': too manysymbolic links were detected whileresolving name




ANS14018E Error processing 'filespacenamepath-namefile-name': file name toolong

Explanation: The file name specified is too long to behandled by TSM.

System action: File is skipped.

User response: See the appropriate Using theBackup-Archive Client book for the particular operatingsystem, for the file names that are handled by TSM.

ANS14019E Error processing 'filespacenamepath-namefile-name': file system islocked by system




ANS14020E The data format for object 'filespacenamepath-namefile-name' is unknown. Theunknown format usually occurs whenthe file was backed up or archived by alater version of IBM Tivoli StorageManager.

Explanation: When a file is backed up or archived,IBM Tivoli Storage Manager includes some additionalinformation about the file. This message is issued ifIBM Tivoli Storage Manager cannot recognize theinformation during a restore or retrieve operation. Themost likely cause is that the file was backed up orarchived with a newer version of IBM Tivoli StorageManager. If the file was backed up from acase-preserving but not case-sensitive file system, thefile name might be displayed with incorrect casing. The

ANS14013E • ANS14020E


incorrect casing does not otherwise affect processingsince the file is skipped.

System action: The file is not restored or retrieved.Processing continues with the next file.

User response: Try the restore or retrieve operationagain with a current version of the IBM Tivoli StorageManager client software. If the problem persists, contactIBM technical support for further assistance.

ANS14021E Error processing 'filespacenamepath-namefile-name': file system notready




ANS14022E Error processing 'filespacenamepath-namefile-name': file system isinvalid.

Explanation: The drive was not available for access.


User response: Ensure that the drive is operational,and then try the operation again. If this is unsuccessful,check the error log.

ANS14023E Error processing 'filespacenamepath-namefile-name': file input/outputerror




ANS14024E Error processing 'filespacenamepath-namefile-name': file write error




ANS14025E Error processing 'filespacenamepath-namefile-name': file exceeds useror system file limit

Explanation: A file being backed up/restored orarchived/retrieved exceeds system set limits for this

user. Shown below are the filesize limits correspondingto various platforms.

AIX 68,589,453,312 (64GB)

HP-UX 1,099,511,627,775 (1TB-1)

Linux 2,147,483,647 (2GB)

Mac pre-OS92,147,482,624 (2GB-1K)

Mac OS918,446,744,073,709,551,616 (16EB)

NetWare4,294,963,200 (4GB -4KB)

NUMA-Q DYNIX/ptx4.5 1,095,216,660,480 (1TB-4GB)

OS/390 4,294,967,295 (4GB)

SGI 18,446,744,073,709,551,615 (16EB-1)

Solaris 2.6 or higher 1,099,511,627,775 (1TB-1)

Tru64 UNIX1,099,511,627,776 (1TB)

UnixWare2,147,483,647 (2GB)

Windows ME (FAT32)4,294,967,295 (4GB)

Windows NT/2000 (NTFS)17,592,185,978,880 (16TB-64K)



ANS14026W Error processing 'filespacenamepath-namefile-name': size of 'file-size'exceeded the maximum file size limit onyour system

Explanation: You tried to restore or retrieve a file thathas exceeded the maximum file size limitation on yoursystem.


User response: Restore or retrieve this file on a systemthat supports the file size. See your systemadministrator.

ANS14027S Error processing 'filespacenamepath-namefile-name': internal programmessage 'value' encountered

Explanation: An unexpected catastrophic programfailure occurred, indicated by value.


User response: Retry the operation. If the problem

ANS14021E • ANS14027S


continues, see your system administrator or servicerepresentative.

ANS14028E Error processing 'filespacenamepath-namefile-name': cannot createfile/directory entry



User response: Ensure that you have the properauthorization to create the directory for file beingrestored or retrieved.

ANS14029E Error processing 'filespacenamepath-namefile-name': unable to builda directory path; a file exists with thesame name as a directory

Explanation: TSM tried to create a directory path, butis unable to because a file exists that has the samename as a directory.


User response: Remove the file that has the samename as the directory. Refer to the last restore/retrieveoperation and check all directories along the path.

ANS14030E Error processing 'filespacenamepath-namefile-name': disk space limitfor this process reached




ANS14031E Error processing'file_space_namepath_namefile_name'. Nameexceeds an internal TSM limit.

Explanation: During a file operation, TSMencountered a filename where at least one componentof the file name (file_space_name, path_name ordirectory_name or file_name) exceeded an internal TSMmaximum. The internal TSM limits should not beconfused with the operating system limits forfile_space_name, path_name or directory_name,file_name.

Shown below are the TSM internal file name limits forvarious platforms.

AIX HP-UX SolarisFile_space_name 1024Path_name or directory_name 1023File_name 256

Linux

File_space_name 1024Path_name or directory_name 768File_name 256

Windows XP/2000/2003File_space_name 1024Path_name or directory_name 248File_name 248


User response: Reduce the size of the filename so thatit is smaller that the TSM internal limits.

ANS14032E Error processing 'filespacenamepath-namefile-name': file is notcompressed.




ANS14033E Error processing 'filespacenamepath-namefile-name': file compressedon a different client machine that hasmore memory




ANS14034E Error processing 'filespacenamepath-namefile-name': unknown systemerror

Explanation: An unknown error occurred. This mightbe a low-level system or communication error that TSMcannot handle or recover from.


User response: Retry the operation. If the problemcontinues, determine where the problem exists. Seeyour system administrator for further help.

ANS14035W File 'filespace namepath-namefile-name'currently unavailable on server.

Explanation: You tried to restore or retrieve a file thatis currently not available from the TSM server.

System action: TSM Cannot restore or retrieve the file.

User response: Try to restore or retrieve after the file

ANS14028E • ANS14035W


was made available on the server. See your systemadministrator.

ANS14036E An error occurred saving the registrykey.

Explanation: The active registry key cannot be copiedto the ADSM.SYS staging directory.

System action: Registry backup operation terminates.

User response: Check the space available on theWindows boot partition to ensure there enough spaceto contain a copy of the Windows registry. This mightrequire several megabytes of free space. Also check theWindows permissions on the ADSM.SYS stagingdirectory and ensure that the Windows user underwhich you are running TSM has full access to thatdirectory and its contents.

ANS14037E Object 'file-namefile-namefile-name'changed during processing. Objectskipped.

Explanation: The specified file-name was skippedduring backup, archive, or migrate because it waschanging during the attempt to process it.

System action: TSM skipped the object.

User response: If you want the file backed up,archived, or migrated, retry the operation. If it fails,determine why the object is being changed. For moreinformation on backing up, archiving, or migratingchanging objects, see your system administrator.

ANS14038E An error occurred processing file system'filespace name'.

Explanation: File system 'filespace name' is corrupted orcontains one or more corrupted directories and cannotbe processed.

System action: File system is skipped.

User response: Check your system to ensure that it isoperating properly. For the Windows environment, runCHKDSK utility for the failing drive. More informationabout corrupted directories can be found indsmerror.log.

ANS14039E Error processing 'filespacenamepath-namefile-name': compressed fileis corrupted and cannot be expanded.






User response: 1) The compressed file is corruptedbecause there is a problem on the tape. To know if thisis the problem, please issue the following command onthe TSM Server: audit volume <volume_name> fix=noIf there is any problem reported, you could move thedata from that volume to a new one (see commandMOVE DATA) and try again the restore. 2) There arecommunications problems between the TSM Server andthe TSM Client and the results is that the file iscorrupted during the transmission. If you use a gigabitethernet adapter on the Server please upgrade the carddriver (AIX platform) or add provided by SUNsuggested changes to some system network optionswhich have resolved this problem (SUN platform). 3)Please verify with your network support if during therestore there are no any problems between the TSMClient/Server that is originating the file corruption.

ANS14040E Error processing 'filespacenamepath-namefile-name': file systemfilespace name has exceeded its spacemanagement quota.

Explanation: TSM detects that the file system hasexceeded its quota. No more data can be migrated outof this file system.

System action: TSM will not migrate files from thisfile system.

User response: Recall some files, or ask the systemadministrator to increase the quota for this file system.

ANS14041E A Windows Server 2008 or 2008 R2VMware guest cannot be restored with anon-Windows data mover.

Explanation: A Windows data mover must run certaincommands to complete the restore of the ActiveDirectory. Non-Windows data movers do not have thenecessary tools to complete this operation. WindowsVMware guests that are at Windows Server 2012 orhigher are not affected by this restriction.


User response: Use a Windows data mover tocomplete this action.

ANS14042E Object name 'filespacenamepath-namefile-name' contains one ormore unrecognized characters and is notvalid.

Explanation: The file name, directory name, orvolume label syntax is incorrect.


User response: Check the disk for errors.

ANS14036E • ANS14042E


ANS14044E Error processing 'filespace-namepath-namefile-name': Case-sensitive nameconflict exists.

Explanation: While processing the specified file on theworkstation, another file name was encountered with asimilar name which only differed in case. TheBackup-Archive client does not allow names whichdiffer only in case on this platform and cannotguarantee the integrity of the file, so the file is skipped.

System action: This object will be skipped.

User response: Rename the file in question to aunique name.

ANS14045E Error processing 'filespace-namepath-namefile-name': Case-sensitive nameconflict exists. The directory tree will beskipped.

Explanation: While processing the specified file on theworkstation, another object name was encountered witha similar name which only differed in case. TheBackup-Archive client does not allow names whichdiffer only in case on this platform and cannotguarantee the integrity of the file, so the directory andall of the objects contained within it are skipped.


User response: Rename the file in question to aunique name.

ANS14046E There is an error processing'filespace-namepath-namefile-name': theobject is corrupted and unreadable.

Explanation: You tried to read from or write to a fileor directory that is corrupted. The corrupted file isskipped. If this is a directory, the objects contained inthe directory and its subdirectories are skipped.


User response: Check your system to ensure that thefilespace is not corrupted by using system tools likechkdsk (Windows) or fsck (UNIX).

ANS14047E There is a read error on'file-namefile-namefile-name'. The file isskipped.

Explanation: The specified file-name was skippedduring backup archive because the file could not beread.

If you are performing a JFS2 snapshot based operation,it is possible that the snapshot was not large enough tocontain all the changes made to the filesystem after thesnapshot was created. This could cause the snapshot tobecome invalid thereby preventing TSM client fromreading the snapshot.

System action: TSM skipped the file.


If you are performing a JFS2 snapshot based operation,please use the default snapshotcachesize of 100% andensure that the volume group has sufficient disk spaceto allocate snapshots at least as large as the file systemand retry the operation.

ANS14048W LAN-Free connection failed.

Explanation: ENABLELANFREE option is set to YESfor this session, but an attempt to establish LAN-Freeconnection failed.

System action: The TSM client will failover to nonLAN-Free support.

User response: Review the TSM error.log forLAN-Free failures. Check your LAN-Free setup andverify that all components are working properly.

ANS14049I Established LAN-Free connection.

Explanation: ENABLELANFREE option is set to YESfor this session and the TSM client successfullyestablished LAN-Free connection with server, after theLAN-Free connection was broken.

System action: The TSM client will communicate withthe server via LAN-Free.

User response: Review the TSM error.log forLAN-Free errors. Check your LAN-Free setup andverify that all components are working properly.

ANS14050W Scheduled action 'schedule-action' did notexecute for schedule 'schedule-name' asthe TSM administrator has beendisabled from executing the scheduledaction on the client.

Explanation: One or more of the client options -schedcmddisabled, srvprepostscheddisabled,srvprepostsnapdisabled, restretrscheddisabled, havebeen set to YES on the client thereby preventing theTSM administrator from executing one of the followingscheduled actions on the client - preschedule,postschedule, presnapshot, postsnapshot or scheduledoperating system commands, restore or retrieveoperations.

System action: The scheduled operation will not beexecuted and a message will be logged to TSM Serverindicating this.

User response: None required.

ANS14044E • ANS14050W


ANS14051E Error processing 'filespacenamepath-namefile-name': The decryptionoption is in effect, but the user IDunder which back-up or archive is beingrun is not authorized to decrypt thisencrypted-file-system (EFS) file.

Explanation: The file being processed is encrypted byan encrypted file system (EFS). The option is specifiedto back-up or archive the file in decrypted form. Theuser ID under which the back-up or archive is beingrun does not have decryption rights for this file.


User response: There are three possible ways to makedecryption work:

v Re-encrypt the file under the encryption key of agroup to which both the owner and theback-up/archive user IDs belong

v Add the back-up/archive user ID to the list of usersauthorized to decrypt this file

v Run the back-up or archive under the owner's userID, if possible

ANS14052E Error processing 'filespacenamepath-namefile-name':Encrypted-file-system (EFS) file cannotbe restored, because file system doesnot support restore from the raw-EFSback-up data, or possibly because therestore function does not have writeaccess to the directory.

Explanation: The file being processed is encrypted byan encrypted file system (EFS). The file was backed upin the raw encrypted format. Either the targetfilesystem does not support the encrypted format, orrestore does not have write access to the directory towhich the file is to be restored.

System action: The restore is terminated.

User response:

v The file cannot be restored to this location if the filesystem is not the AIX Enhanced Journaled FileSystem (JFS2)

v If the file is JFS2 but EFS is not enabled, then EFSmust be enabled before the file can be restored

v If the user ID under which restore is being run doesnot have write permission for the directory, thepermissions must be changed or the restore must berun under a different user ID

ANS14053E Error processing 'filespace path filename':The file cannot be restored because thefile system or operating system does notsupport the Encrypting File System(EFS) data.

Explanation: The specified object was backed-up as

raw Encrypting File System (EFS) data. The client istrying to restore or retrieve the object to a destinationthat does not support the EFS data. The location mightnot support the EFS data for one of the followingreasons:

v The operating system does not provide the support,or is a release that does not include the support

v EFS support has not been activated on the operatingsystem

v The target file system does not support the EFS data

System action: The object is not restored or retrieved.Processing continues with the next object.

User response: If this file must be restored, restore itto an AIX operating system environment supportingEFS data.

ANS14054E Error processing 'filespacenamepath-namefile-name': The encryptionkey is not loaded.

Explanation: The file being processed is encrypted byan encrypted file system (EFS). The option is specifiedto backup or archive the file in decrypted form. Theencryption key, required to decrypt the file, is notloaded in the kernel keyring.


User response: There are three situations in which thisproblem can occur:

v You just performed initial activation of EFS on theAIX system, and have not logged out. AIX does loadthe keys for the session running at the time of initialactivation. Solution: Logout and login again.

v The login password has been changed recently, andyou normally run with the EFS password the sameas the login password. AIX does not automaticallychange the EFS password when you change the loginpassword. Solution: Issue 'efskeymgr -n' to set theEFS password to be the same as the login password.

v You need to run the decrypting backup when theEFS password is different from the login password.Solution: Issue 'efskeymgr -o ksh' to launch a newshell with the keys loaded. AIX will prompt you forthe EFS password as you launch the shell. Run thebackup from the new shell.

ANS14055E Cannot update file space 'filespace-name':the file space version on the TSM serveris not compatible with this client

Explanation: The file space on the TSM server is notcompatible with this client. This is caused byperforming a backup or archive operation with a clientand then using a down-level client and attempting abackup or archive operation targeting the same filespace.This problem occurs specifically after a Windows orAIX client V6.1 or higher performs a backup or archive

ANS14051E • ANS14055E


operation and then a subsequent backup or archiveoperation is attempted with a client V5.5 or lower.


User response: Use the correct level of the client.

ANS14056E Object 'object-name' returned by the IBMTivoli Storage Manager server has ahigh-level name that exceeds themaximum length of 6000 characters. Thefile or directory cannot be processed.

Explanation: The IBM Tivoli Storage Manager serverreturned information about a backup or archive versionwith a high level name that exceeds 6000 characters.The high-level name is the directory path that containsthe object (file or directory).

This message is displayed when all of the followingconditions are true:

v The object was backed up or archived by a version6.1 or lower IBM Tivoli Storage Manager client.

v The object was backed up or archived to a version5.5 or lower IBM Tivoli Storage Manager server.

v IBM Tivoli Storage Manager client version 6.2 orhigher is attempting to perform an operation thatcauses the IBM Tivoli Storage Manager server toreturn information about this object to the client.Note: During incremental backup, the server returnsinformation to the client about active backupversions which is used to determine which files havechanged.

Beginning with IBM Tivoli Storage Manager serverversion 6.1, the maximum high level name length wasreduced from 8192 characters to 6000 characters.Objects with high level names that exceed 6000characters are not supported for backup or archive.Beginning with IBM Tivoli Storage Managerbackup-archive client version 6.2, the maximum highlevel name length was similarly reduced.

System action: The file or directory specified in themessage is skipped. Processing will continue with thenext object.

User response: Contact your IBM Tivoli StorageManager server administrator for further assistance.

ANS14058I A write failure occurred whileattempting to save node replicationfailover values to the options file.

Explanation: A write failure is often a result ofinsufficient access permissions to the options file, butcould also be caused by the lack of available diskspace. The replication server connection informationcan not be saved and failover will not be possible.

System action: The operation failed.

User response: Check the local disk for possible

causes of the write error, and check to see thatsufficient access to the options file is configured.

ANS14059I The option USEREPLICATIONFailoveris set to NO. The node will not fail overto the secondary server

Explanation: This option will prevent the node fromconnecting to the replication server in the event of afailure of the primary server.

System action: The configuration set by the TSMadministrator will be saved to the options file. Theclient will not connect to the primary server andprocessing stops.


ANS14061I Connected to secondary server secondaryserver; in fail over mode. Home server is:home server;

Explanation: The node is configured for replicationand has successfully connected to the secondary server.This message is to notify the server administrator that anode has connected to the secondary server in fail overmode.



ANS14063W IBM Tivoli Storage Manager applicationprotection cannot copy the applicationmetafile 'App-Metadata-File-Name' fromthe following VM: 'VM-Name'.Individual database restore from thisbackup is not supported.

Explanation: The application metafile was not foundon the guest machine.

System action: The operation completes. However, theapplication metafile was not copied.

User response: Make sure that the application VSSwriters are running on this guest machine, and theapplication database is in the state to allow the backup.Then try the operation again.

ANS14064I Restoring vCloud Director vApp 'vappname' from Organization VDC 'org vdcname' from organization 'org name'Target vApp name is 'restored vapp name'Restore VAPP command started. Totalnumber of vApps to process: vapps numto restore

Explanation: The restore vApp operation completed.



ANS14056E • ANS14064I


ANS14065E Proxy rejected: data mover node 'dmnode' has not been granted proxyauthority for target node 'target_node',associated with Organization vDC'OVDC name' of Organization 'Org Name'.

Explanation: The operation requires that a proxyaccess for the data center node is granted to the datamover node.

System action: Operation is canceled for the specifiedvApp.

User response: Run configuration wizard orconfiguration editor to configure proper nodesrelashionship.

ANS14066W Snapshot operation attempt x of y forthe guest virtual machine 'VM' failedusing "sType" snapshot.Reattempting snapshot with "sType2"snapshot.

Explanation: The snapshot operation has failed. Asnapshot retry operation has been scheduled.

System action: Retrying snapshot.

User response: Check the error log for any othermessages that might indicate a reason for the failure.Correct any problems and try the operation again.

ANS14067E Snapshot operation attempt x of y forthe guest virtual machine 'VM' failedusing "sType" snapshot.Backup failed.

Explanation: All snapshot retry attempts of the guestvirtual machine failed.


User response: Check the error log for any messagesthat indicate a reason for the failure. Correct anyproblems and try the operation again. If the problempersists, search the Tivoli Storage Manager Supportweb site (http://www.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.html) forknown solutions.

ANS14068I Restored virtual machine 'VM' wasbacked up using a "VMware Tools withfile system quiescing and applicationquiescing disabled" snapshot.This is equivalent to a "crash-consistent"backup.

Explanation: The restored virtual machine was backedup using a "VMware Tools with file system quiescingand application quiescing disabled" snapshot.Application Protection feature is not available.

System action: Restore of the VM continues.

User response: None

ANS14069E The Windows domain credentialscannot be found. Use the DataProtection for VMware vSphere GUIconfiguration editor to set the Windowsdomain credentials.

Explanation: The required Windows domainadministrator credentials were not set.


User response: Set the Windows domainadministrator credentials in the Data Protection forVMware vSphere GUI configuration editor.

ANS14070E Windows domain credentials areincorrect. Verify the credentials and usedsmc SET PASSWORD -type=DOMAIN'domain\userid' 'password' to updatethe username and password.

Explanation: The supplied credentials are incorrect.The system failed to authenticate to the Windowsdomain using these credentials.


User response: Use dsmc SET PASSWORD-type=DOMAIN 'domain\userid' 'password' to updatethe username and password. And then retry theoperation.

ANS14071E 'VM-Name' cannot be restored because itwas backed up with a newer version ofthe client.

Explanation: The client version that attempted torestore the virtual machine is earlier than the clientversion that backed up the virtual machine. The virtualmachine cannot be restored with an earlier clientversion.

System action: The virtual machine is not restored.Processing continues with the next virtual machine.

User response: Upgrade the client to a version that iscompatible with the client version that backed up thevirtual machine.

ANS14077E File 'filespace namepath-namefile-name' isencrypted by Microsoft EFS andcontains at least one sparse data stream.The operating system does not supportrestore for this file so it is not backedup or restored.

Explanation: An error in the Microsoft Windows APIprevents successful restore of files that meet thefollowing conditions:

v The file is encrypted by Microsoft Encrypting FileSystem (EFS) at the time it was backed up

ANS14065E • ANS14077E


v The file includes at least one data stream (alternate"named" stream or unnamed stream) that is sparse

v The operating system is any edition of Microsoft XP,Microsoft Windows Server 2003, or MicrosoftWindows Server 2003 R2

Because the file cannot be restored, IBM Tivoli StorageManager does not back it up. The problem isdocumented by Microsoft at http://support.microsoft.com/kb/2525290.

System action: The file is not backed up or restored.Processing continues with the next object or ends ifthere are no further objects.

User response: If this message is issued during abackup operation, you can do the following:

v Disable EFS encryption for the file so that it can bebacked up.

v If a backup copy of the file is not necessary, you canexclude it from backup.

ANS14081E Error processing 'filespace-name': filespace type is not supported.

Explanation: The specified file space type is notcurrently supported by TSM on this platform.

System action: The unsupported file system isskipped. Processing continues with the next file system.

User response: Refer to the documentation forinformation on what file space types are supported.

ANS14083I New node password has beengenerated.

Explanation: The client logged in using administrativeid rather than node name. New random node passwordhas been generated and recorded.



ANS14084E Error processing 'filespace-namepath-namefile-name': cannot get file status.

Explanation: While processing the file, the lstat() callset EOVERFLOW error code.

System action: This file will be skipped.

User response: The file is skipped. Processingcontinues with the next file.

ANS14085I Assigned 'number' objects from previoussystemstate backup to the newsystemstate backup.

Explanation: Objects in the previous System Statebackup have not changed and were assigned to thenew System State backup.



ANS14086W Failed to assign unchanged objects fromprevious systemstate backup to the newsystemstate backup. Objects will bebacked up.

Explanation: Objects in the previous System Statebackup have not changed and should be assigned tothe new systemstate backup. Due to error assignoperation failed and objects will be backed up.


User response: Retry the operation. If the problempersists, contact TSM technical support.

ANS14087E An attempt to load data for the wizardfailed.For more information, please see the logfile.

Explanation: An attempt to load data for the wizardfailed as the remote agent is probably unavailable.


User response: Check the log for reason for thefailure.

ANS14089W File server file-server-name has beenupgraded to Data ONTAP version'version.modifcation.submodification'.Perform a full incremental backup byspecifying optioncreatenewbase=migrate as soon aspossible.

Explanation: The file server has been upgraded to aversion that supports unicode file names forincremental backup using snapshot difference. Performa full incremental in order to backup any files withunicode names that may have been skipped by theprevious version of the IBM Tivoli Storage Managerclient.


User response: Perform a full incremental byspecifying the command line optioncreatenewbase=migrate with the snapdiff option assoon as possible.

ANS14090I File server file-server-name has beenupgraded to Data ONTAP version'version.modifcation.submodification'.Perform a full incremental backup byspecifying optioncreatenewbase=migrate as soon aspossible.

Explanation: The file server has been upgraded to a

ANS14081E • ANS14090I


version that supports unicode file names forincremental backup using snapshot difference. Performa full incremental in order to backup any files withunicode names that may have been skipped by theprevious version of the IBM Tivoli Storage Managerclient.


User response: Perform a full incremental backup byspecifying the command line optioncreatenewbase=migrate with the snapdiff option assoon as possible.

ANS14092E Data mover platform is not supportedfor instant access/restore operations.

Explanation: The instant access/restore operationfailed.

System action: The instant access/restore operationfailed. The reason for the failure is unsupportedplatform.

User response: The instant access/restore operationshould be performed from a supported data moverplatform.

ANS14099E The system volume cannot beidentified. Therefore the system statecannot be backed up.

Explanation: The system volume contains thehardware-specific system state files that are needed tostart Windows, such as Ntldr, Boot.ini, Ntdetect.com orBootmgr. If the system volume cannot be identified,then these files cannot be backed up. Therefore it is notpossible to back up the system state.

System action: Systemstate backup stops.

User response: Try the operation again. If the problempersists, obtain a service trace that captures theproblem and contact IBM technical support foradditional assistance. Your TSM administrator can helpyou configure the trace.

ANS14137E Error processing 'filespacenamepath-namefile-name': exceededmaximum number of links allowed

Explanation: Link cannot be restored or retrievedbecause the destination file system has exceededmaximum number of links allowed.


v Skip this object

v Abort the action

User response: Select the appropriate action for thisobject. Restore or retrieve the link to another filesystem.

ANS14148E Full VM backup of Virtual Machine'vmname' failed with RC rc

Explanation: The Full VM backup of virtual machinefailed.

System action: The full backup of the virtual machinefinished with failures. The next virtual machine in thevmlist will be processed. The reason for the failure iswritten to the local client error log.

User response: Check the local client error log forreason for the failure.

ANS14150E Incremental backup of Virtual Machine'vmname' failed with RC rc

Explanation: The incremental backup of virtualmachine volumes failed.

System action: The backup of the virtual machinefinished with failures. The next virtual machine in thevmlist will be processed. The reason for the failure iswritten to the local client error log.


ANS14151E Failure mounting Virtual Machine'vmname'. RC=rc

Explanation: The VMware failed to mount virtualmachine disk.

System action: The backup of the virtual machine cannot continue. The next virtual machine in the vmlistwill be processed. Refer to dsmerror.log for detailederror message for the reason for the failure.

User response: Refer to dsmerror.log for detailed errormessage.

ANS14152E Failure initializing VMware virtualmachine environment. RC=rc. Refer toIBM Tivoli Storage Manager error logfor detailed error messages.

Explanation: Failure initializing VMware virtualmachine environment. Refer to IBM Tivoli StorageManager error log for detailed error messages.

System action: The backup can not continue.

User response: Refer to IBM Tivoli Storage Managererror log for detailed messages.

ANS14153E Hostname could not be found forVirtual Machine 'vmname'

Explanation: The backup of virtual machine failed.


ANS14092E • ANS14153E



ANS14154E Possible cause Virtual Machine is notrunning and does not have a static IPaddress.




ANS14155E Virtual Machine 'vmname' could not befound on VMware server.




ANS14156E File level VM backup of virtual machine'vmname' not supported.File level VM backup not support onnon Windows platform guest OS.Platform type: 'platform'.



User response: Back up the virtual machine using theVMBACKUPType=FULLvm option.

ANS14159E Backup of Virtual Machine 'vmname'failed. rc=rc.




ANS14160E Proxy Rejected: Proxy authority has notbeen granted to Agent Node: 'agent_node'for Target Node: 'target_node'.


System action: The backup of the virtual machinefinished with failures. The next virtual machine in thevmlist will be processed. The reason for the failure isthe node has not been granted proxy authority toaccess the node named by the backup proxy node. TheTSM administrator must first grant proxy authority.


ANS14161E Duplicate virtual machine name'vmname' was detected in the samebackup operation. Backup of virtualmachine 'vmfullname' can not continuewithout a unique object name.



User response: Choose a unique name for the virtualmachine.

ANS14162E The virtual machine'virtual-machine-name' has not beenpreviously backed up.

Explanation: The specified virtual machine has notbeen previously backed up, so can not be specified forrestore.

System action: The specified virtual machine isskipped, and the next virtual machine in the restore listis processed.

User response: Verify the virtual machine name to berestored, and re-try the operation.

ANS14163I Encryption is currently enabled, but thevirtual machine backup for'virtual-machine-name' will not beencrypted.

Explanation: Virtual Machine files are not encryptedwhen backed up to the TSM server.

System action: The virtual machine files are notencrypted during the backup processing.

User response: No user action is necessary.

ANS14154E • ANS14163I


ANS14164W Compression is currently enabled, butthe virtual machine backup for'virtual-machine-name' is not compressedbecause client-side deduplication is notbeing used.

Explanation: Compression can only be used withvirtual machine CTL and Data files when the files arestored in a storage pool that is enabled for client-sidededuplication. This message is issued when the client isconfigured for compression and virtual machine CTL orData files are directed to a storage pool that is notenabled for client-side deduplication.

System action: Backup continues, and data is notcompressed.

User response: If you intend to compress virtualmachine CTL and Data files, then update your TivoliStorage Manager configuration so that both types offiles are directed to storage pools that are enabled forclient-side deduplication. If you intend to compressvirtual machine Data files but not CTL files, thenupdate your Tivoli Storage Manager configuration sothat the Data files are directed to a storage pool that isenabled for client-side deduplication. Set theVMSKIPCTLCOMPRESSION to YES in your clientoptions file. If you do not intend to use compression,then set COMPRESSION NO in your client options file.

ANS14165E Creating a Virtual Machine, but thehostname 'virtual-machine-name' was notfound.

Explanation: The Virtual Machine being creating musthave a valid hostname to be created.

System action: Check the virtual machine hostnamespecified for correctness.

User response: Correct the virtual machine hostnamespecified and retry the restore.

ANS14166E Creating a Virtual Machine, but thedatacenter 'virtual-machine-name' was notfound. The name may be incorrect ormay be located in a VMware folder andrequire the folder name such asvmfolder/dcname.

Explanation: The Virtual Machine being created musthave a valid datacenter to be created.


User response: Check the virtual machine datacenterspecified for correctness. If the datacenter is containedin a folder then the full datacenter name, complete withthe folder path, must be specified, such asvmfolder/dcname.

ANS14167E Creating a Virtual Machine, but thedatastore 'virtual-machine-name' was notfound.

Explanation: The Virtual Machine being creating musthave a valid datastore to be created.

System action: Check the virtual machine datastorespecified for correctness.

User response: Correct the virtual machine datastorespecified and retry the restore.

ANS14168E VMware has reported an error via theirSOAP interface. On the Detailed StatusReport panel, view the last errormessage reported. Also check the errorlog for more information about theproblem that occurred.

Explanation: The command to VMware failed tocomplete. The error returned is displayed on theRestore or Backup summary panel under the Last ErrorMessage section.

System action: An error occurred, and the operationfailed.

User response: Check the reported error and correctthe problem. Usually the reason for the error is auser-supplied value which is not valid for theoperation.

ANS14169E A write failure occurred on the localdisk proxy used to temporarily store thevirtual machine virtual diskinformation. The write failure can becaused by the lack of available diskspace on the drive used to store thisinformation. The VMBACKDIR optioncan be used to assign a different disklocation for this purpose. Check thedrive being used and ensure that thereis enough space available for thisoperation.

Explanation: There was a write error from the localdisk used to store the virtual machine virtual diskinformation. Usually the write error is due to lack ofdisk space, lack of write permissions, or some similarproblem with the local disk. The VMBACKDIR optioncan be used to assign a different disk location if thelocal drive does not have enough free space for theoperation.

System action: A disk write error occurred, and theoperation failed.

User response: Check the local disk for possiblecauses of the write error, and use the VMBACKDIRoption to assign another disk if needed.

ANS14164W • ANS14169E


ANS14170E Can not create a Virtual Machine onVMware release 'release-version-target'which was backed up from VMwarerelease 'release-version-source'.

Explanation: The Virtual Machine being created wasbacked up from a version of VMware which is notcompatible with the target VMware release versionbeing used for the restore.


User response: Restore the Virtual Machine to aVMware system which is compatible with the levelfrom which the Virtual Machine was backed up.

ANS14171E Backup of virtual machine 'vmname'failed. VM could not be contactedbecause of 'vmfullname' connection state.


System action: The backup of the virtual machinefinished with failures. The next virtual machine in listwill be processed.

User response: Correct the connection state fromVMware vCenter and assign VM to an ESX Server.

ANS14174E Full VM backup of VMware VirtualMachine 'vmname' failed with RC=rcmode=full_or_incr, target nodename='target_node_name', data movernode name='data_mover_node_name'




ANS14177E Full VM restore of VMware VirtualMachine 'vmname' failed with RC=rctarget node name='target_node_name',data mover nodename='data_mover_node_name'

Explanation: The Full VM restore of the virtualmachine failed.

System action: The full restore of the the virtualmachine finished with failures. The next virtualmachine in the vmlist will be processed. The reason forthe failure is written to the local client error log.


ANS14178W Compression is currently enabled, butthe virtual machine control files for'virtual-machine-name' will not becompressed because client-sidededuplication is not being used for themanagement class default or specifiedby the -vmctlmc option for'vm-ctl-mgmt-class-name'.

Explanation: Virtual machine control files are notcompressed because data is stored in a storage poolthat is not enabled for client-side data deduplication.The virtual machine control files are not compressedduring the backup processing unless data is stored in astorage pool that is enabled for client-datadeduplication.

System action: Backup continues, and control file datais not compressed.

User response: Ensure that the storage pool is enabledfor client-side data deduplication: run "q stg <poolname> f=d" and verify that the value of "DeduplicateData?" is "yes". Ensure that client-side datadeduplication is enabled on the server. To enableclient-side data deduplication, use theDEDUPLICATION parameter on the REGISTER NODEor UPDATE NODE server command. Set the value ofthe parameter to CLIENTORSERVER. The value of theDEDUPLICATION option on the client must be set toYES. You can set the DEDUPLICATION option in theclient options file, in the preference editor of the TivoliStorage Manager client GUI, or in the client option seton the Tivoli Storage Manager server. Use the DEFINECLIENTOPT command to set the DEDUPLICATIONoption in a client option set. To prevent the client fromoverriding the value in the client option set, specifyFORCE=YES. Ensure that the deduplication parameterfor the node is "ClientOrServer": The value of theDEDUPLICATION option on the client must be set toYES.

ANS14179I IBM Tivoli Storage Manager applicationprotection did not truncate the MicrosoftSQL Server logs on VM 'VM'.

Explanation: The SQL server logs were not truncatedbecause the following option was specified for thisvirtual machine: INCLUDE.VMTSMVSS vnameOPTIONS=KEEPSQLLOG

System action: The operation completes.

User response: Remove the OPTIONS=KEEPSQLLOGoption to enable truncation of the SQL logs when abackup completes.

ANS14187W CPU and Memory Resource Allocationconfiguration settings cannot be restoredwhen the IBM Tivoli Storage Managerdata mover node is connected directly toa Virtual Center managed ESX/ESXi

ANS14170E • ANS14187W


host. These settings have been skipped.

Explanation: The VMware vStorage APIs do notsupport the restore of CPU and Memory ResourceAllocation configuration settings when connecteddirectly to an ESX/ESXi host that is managed by aVirtual Center.

System action: CPU and Memory Resource Allocationconfiguration settings are skipped. Processingcontinues.

User response: Virtual machine CPU and MemoryResource Allocation configuration settings will berestored when the IBM Tivoli Storage Manager datamover node connects directly to a vCenter Server.Modify the VMCHOST to connect the TSM data moverto a vCenter Server.

ANS14191E Restore VM operation failed using 'san'transport mode. In some cases switchingfrom SAN to network-based VMrestores can be successful.

Explanation: Restore VM operations that fail usingSAN transport mode can often be successful over aLAN path. If a restore vm operation fails using the'SAN' transport mode, set the client optionVMVSTORTRANSPORT to "nbd:nbdssl" and try therestore vm operation again.

System action: Restore VM operation failed using 'san'transport mode. Restore may be successful using'nbd:nbdssl' transport modes.

User response: Restore VM operation failed using'san' transport mode. In some cases network-based VMrestores can be successful when using 'nbd' or 'nbdssl'transport modes. The VMVSTORTRANSPORT optioncan used to restrict the TSM client to use only thespecified transport modes.

ANS14193E vApp 'vApp name' cannot be processedbecause data mover 'dm node' cannotconnect to the target node 'target_node'.

Explanation: The operation requires that a proxyaccess for the data center node is granted to the datamover node.

System action: Operation is canceled for the specifiedvApp.

User response: Look for errors in error log and correctany problems. Run configuration wizard orconfiguration editor to ensure proper nodesconfiguration.

ANS14194E Encryption is currently enabled, but isnot supported for incremental foreverbackups of virtual machines(-MODE=IFFULL or-MODE=IFINCREMENTAL) .

Explanation: Client encryption of virtual machineincremental forever backups (-mode=IFFULL or-mode=IFINCREMENTAL) is not supported. In orderto avoid the unintentional storage of unencrypted dataon the server, the backup operation stops.

System action: The virtual machine backup stops.

User response: Remove the encryption options for thisoperation and run it again. You can use Secure SocketsLayer (SSL) encryption to encrypt the data over thenetwork. If the backup data must be encrypted in TSMstorage pools, use an alternative backup method suchas full and incremental backups (-mode=FULL and-mode=INCREMENTAL), or in-guest backups.

ANS14195E The target node for Organization VDC'OrgVDC name' in Organization 'Orgname' was not found. As a result, vApp'vApp name' cannot be backed up.

Explanation: Either the TSM node for the specifiedorganization VDC was not found on the TSM server, orinformation about the Organization VDC node was notfound in the Provider VDC node.

System action: Back up of the specified vApp stops.Processing continues to the next vApp.

User response: Go to the Configuration page and click'Run the Configuration Wizard' to verify that allrequired TSM nodes are registered on the TSM server.If required, register a new data mover node. Make surethat the organization VDC belongs to the providerVDC that this data mover node protects.

ANS14199W File 'file name' is not backed up as partof the system state because cluster disk'volume name' is not accessible.

Explanation: The indicated file or directory wasreturned by VSS as part of the backup file list of thewriter. However, the cluster disk where the file islocated is not accessible. The reasons for this problemcan be that the cluster disk is offline or belongs toanother node.

System action: The file is not backed up. Processingcontinues.

User response: This problem is documented inMicrosoft knowledge base topic 980794http://support.microsoft.com/default.aspx?scid=kb;EN-US;980794. The topic includes a hotfix. With the hotfix,you can specify a registry key that contains a list of oneor more files to be excluded from VSS enumeration.IBM Tivoli Storage Manager does not back up files thatare not enumerated by VSS. If the volume is broughtonline to the node performing the system state backup,then it cannot be backed up. You must remove thevolume from the registry key and restart the systembefore you can back up the volume.If you do not want to implement the hotfix for this

ANS14191E • ANS14199W


problem, IBM Tivoli Storage Manager continues toissue this message.

ANS14202E The Deployment Manager failed toinstall language pack: language packname. The Microsoft Installer error codewas error code.

Explanation: The previous language pack has beenuninstalled, and the installation of the new languagepack failed.


User response: For more information about Windowsinstaller error messages, go to the Microsoft DeveloperNetwork (MSDN) technical library athttp://msdn.microsoft.com/en-us/library and searchon "Windows Installer Error Messages".

Check the install log on the client computer.

ANS14251W writername file 'filename': not found.

Explanation: The indicated VSS writer file or directorywas returned by VSS as part of the backup file list ofthe writer. However, the object does not exist on thedisk..

System action: Processing stops ifSKIPMISSINGSYSWFILES option is set to NO.Processing continues if SKIPMISSINGSYSWFILESoption is set to YES.

User response: Verify that this file can be skippedduring system state backup.

ANS14254E The deployment manager detected anHSM client on the workstation that itneeds to deploy the Backup-Archiveclient to.

Explanation: An attempt was made to deploy theBackup-Archive client to a workstation that already hasthe HSM client installed. The Backup-Archive clientcannot be deployed to a workstation that has the HSMclient.


User response: Uninstall the HSM client andreschedule the Backup-Archive client deployment.

ANS14255E There is not enough memory for thedeployment manager to create thesystem information object

Explanation: The system information object could notbe created because there is not enough available RAMto temporarily write the data into.


User response: Close all unneeded applications on the

client workstation and reschedule the deployment.

ANS14256E The DSMI_DIR environment variable isnot defined.

Explanation: The deployment manager cannot initiatea connection to the server because the DSMI_DIRenvironment variable is not set. This error can occur ifthe deployment manager is started without using theclient scheduler.


User response: Read the available documentation todetermine how to use the client scheduler to create aclient deployment task.

ANS14257E The deployment manager cannot parseinformation in file: file name.

Explanation: The deployment manager could notparse or extract the required information from thespecified file.


User response: Check the error log file on the clientworkstation.

ANS14258E The deployment manager received theWindows "OpenSCManager failed" errormessage.

Explanation: The deployment manager could notconnect to the Windows service control manager tostart the client scheduler. In general, this error occursbecause the user who is initiating the task does nothave sufficient authority.


User response: Ensure that the user who starts theclient scheduler has administrative privileges.

ANS14259E The client scheduler is not started as aroot user.

Explanation: The client scheduler requires root userprivileges to upgrade the client code.


User response: Log in as root and start the clientscheduler.

ANS14260E The installation file system is notwriteable.

Explanation: The deployment manager cannot writeto the installation file system.


User response: Check the installation file systempermissions. It is possible that the current client node

ANS14202E • ANS14260E


runs in a virtualized environment using the client codeinstalled in a shared storage of the physicalenvironment. Reschedule the client deployment withthe client node in the physical environment.

ANS14261E The deployment manager cannotupgrade the Backup-Archive Client.

Explanation: The Backup-Archive Client cannot beupgraded because either the current location is not thedefault installation location or the DSM_DIR,DSMI_DIR, DSM_CONFIG and DSMI_CONFIGenvironment variables are defined with a relative pathand not an absolute path.


User response: Check the installation directory of thecurrent Backup-Archive Client. If the Backup-ArchiveClient is not installed in the default location, manuallyupgrade the Backup-Archive Client. If the DSM_DIR,DSMI_DIR, DSM_CONFIG and DSMI_CONFIGenvironment variables are defined with a relative path,define them with an absolute path and try the clientdeployment again.

ANS14262E The preview of the client installationfailed.

Explanation: The deployment manager did notuninstall the current client. The client code isunchanged.


User response: Check the deployment manager logand trace files on the client workstation for specificissues identified during the preview. Reschedule adeployment after any issues are resolved.

ANS14263E The deployment manager failed touninstall the backup-archive client.

Explanation: The deployment manager received anerror while uninstalling the current client.


User response: Check the deployment manager logand trace files on the client workstation for moredetails on the error. You might have to manuallyuninstall the client.

ANS14264E The deployment manager failed toinstall the backup-archive client.

Explanation: The current client was uninstalled andthe deployment manager received an error whileinstalling the new client code.


User response: Check the deployment manager logand trace files on the client workstation for more

details on the error. Manully install the new client afterthe issue is resolved.

ANS14265I Client deployment options are notspecified in the scheduler command orfrom client services.

Explanation: The default client options file will beused. The deployment manager might not report thecorrect server and node information when reportingstatus.


User response: Avoid initiating the client deploymentdirectly from the command-line, instead, always startthe client scheduler as a Windows service.

ANS14266I The deployment manager failed toinstall non-English language pack(s).

Explanation: The previous packages were uninstalled,and the installation of one or more new language packswere not successful.


User response: Check the deployment trace file on theclient workstation for specific language packinformation.

ANS14267I The deployment manager failed toinstall the hardware plugin package.

Explanation: The previous package was uninstalled.The installation of the new hardware plugin packagefailed.


User response: Check the deployment trace file on theclient workstation.

ANS14268I The deployment manager failed toinstall the journal-based backuppackage.

Explanation: The previous journal-based backuppackage was uninstalled. The new journal basedbackup package installation failed.


User response: Check the deployment trace file on theclient workstation.

ANS14269W The deployment manager is stoppingthe scheduler and/or CAD processes.

Explanation: Before deploying the new client, thedeployment manager must stop the scheduler andCAD processes. After the deployment, the processesmust be restarted.


ANS14261E • ANS14269W


User response: The client scheduler is interruptedduring the deployment.

ANS14270I The deployment manager and the newclient installation packages weredownloaded to directory: file name.

Explanation: The download directory containseverything required to complete the new clientdeployment. Deployment log and trace files can befound in the log/ sub-directory.


User response: Obtain log and trace files from thedownload directory for problem determination. Thefiles are found within the log/ sub-directory.

ANS14271E The deployment package is missing oneor more required installation imagefiles.

Explanation: The client deployment package mightnot have been imported correctly to the server. It ispossible that the deployment package is not retrievedcompletely to the client computer, due to a lack of diskspace.


User response: Ensure that client packages areavailable on the server and there is sufficient disk spaceon the client computer. Check the backup-archive clienterror log file for more detailed error messages.

ANS14272E The processor type of the package:package processor type does not match thecurrent client: system processor type..

Explanation: The processor type supported by theclient package that you want to deploy does not matchthe processor type of the workstation that you aretrying to deploy the client to. It is not always possiblefor the deployment manager to connect to the serverand report the error.


User response: Verify that you are using the correctclient package for the processor architecture of thecomputer that you want to upgrade. Then restart thedeployment.

ANS14273E The deployment manager detected ajournal based backup (JBB) client on theworkstation where it needs to deploythe Backup-Archive Client.

Explanation: An attempt was made to deploy theBackup-Archive Client to a workstation that alreadyhas the JBB client installed. On some platforms, theBackup-Archive Client cannot be deployed to a

workstation that has the JBB client installed.


User response: Uninstall the JBB client and reschedulethe Backup-Archive Client deployment.

ANS14274E The deployment manager cannot stopthe scheduler or the CAD processes.

Explanation: The deployment manager tried to shutdown the Backup-Archive Client scheduler or CADprocesses but the Backup-Archive Client might be busywith other tasks.


User response: Reschedule the Backup-Archive Clientdeployment.

ANS14275E The deployment manager cannot restartthe scheduler or the CAD processes.

Explanation: Before exiting, the deployment managercould not restart the Backup-Archive Client scheduleror CAD processes. The deployment manager stoppedthe processes prior to the client upgrade.


User response: Log on to the Backup-Archive Clientworkstation and check the error log file. If you have setenvironment variables make sure they are not definedusing relative path.

ANS14276E The deployment manager cannot obtaininformation about the scheduler or theCAD processes.

Explanation: The deployment manager needs processinformation in order to stop and restart theBackup-Archive Client scheduler or CAD processes.


User response: Log on to the Backup-Archive Clientworkstation and check the error log file and thedeployment manager error log file.

ANS14277E The target operating system versiontarget operating system does not meet theminimum required version minimumrequired version

Explanation: The operating system version is earlierthan the version required by the automatic deploymentpackage.

System action: The deployment is canceled.

User response: Ensure that the TSM version beingdeployed is supported by the target operating system.

ANS14270I • ANS14277E


ANS14278E The deployment manager cannot obtaininformation about the Logical VolumeSnapshot Agent (LVSA).

Explanation: The deployment manager needs todetermine whether an LVSA is installed on the clientworkstation.


User response: Log on to the Backup-Archive Clientworkstation and check the error log file and thedeployment manager error log file.

ANS14280E Automatic client deployment is notallowed on the client workstation.

Explanation: One or more of the running clientservices include AUTODEPLOY = NO in the optionfile.


User response: Change the AUTODEPLOY option onthe client and reschedule the client deployment.

ANS14281E The update manager cannot remove theTIVsmCapi package from non-globalzone(s): zone name.

Explanation: APAR IC57433 prevents the removal ofthe TIVsmCapi package on Solaris on a sparse-root,non-global zone if uninstalling is done from the globalzone.


User response: Manually uninstall the Tivoli StorageManager client directly from the non-global zones andreschedule the deployment.

ANS14282E Sparse-root non-global zone(s) werefound with Tivoli Storage ManagerBackup-Archive Client that wasinstalled from the non-global zone: zonenames.

Explanation: One or more non-global zones aresharing the /usr file system with the global zone. TheTivoli Storage Manager Backup-Archive Client isinstalled in the global zone with the -G parameter andalso installed manually in the non-global zone(s). Youcannot update the Tivoli Storage ManagerBackup-Archive Client in the global zone because itwill update the version of GSKit that is shared with thesparse-root non-global zones that are not part of theautomatic deployment.


User response: Manually upgrade the Backup-ArchiveClient or install it from the global zone without usingthe -G parameter. This ensures that you have the sameversion between the global zone and the sparse-root

non-global zones, and you can then deploy the clientautomatically on all such zones.

ANS14283E There is not enough disk space on pathto uncompress GSKit packages.Required space: req_space bytes;available space: avail_space bytes.

Explanation: The deployment manager determinedthat there is not enough free disk space to uncompressGSKit packages.


User response: Free up the required amount of diskspace and reschedule the automatic client deployment.

ANS14284E The deployment is cancelled because anautomatic client deployment task wasscheduled for a sparse-root, non-globalzone that shares the /usr file systemwith the global zone.

Explanation: The automatic client deployment taskthat was attempted is not supported and will becancelled.


User response: Install the Backup-Archive Client fromthe global zone or manually upgrade theBackup-Archive Client.

ANS14285E The update restore operation to anexisting virtual machine 'VmName'failed. The virtual machine is not inpower off state.

Explanation: The update restore operation to anexisting virtual machine is not supported for a runningmachine and will be aborted.

System action: Restore aborted.

User response: Turn off the virtual machine andre-run the update restore command.

ANS14290E Only one virtual machine can beselected for restore.

Explanation: Restoring multiple virtual machines isnot allowed. Only one virtual machine can be selectedfor restore.

System action: No processing occurs.

User response: Select only one virtual machine forrestore.

ANS14278E • ANS14290E


ANS14291E Virtual Machine could not be found onVMware server.




ANS14292E No virtual machine found.

Explanation: No virtual machine found with name orspecified in domain option.


User response: Specify a correct VM name or domainoption.

ANS14293E Backup of VMware vApp 'vApp name' inOrganization VDC 'Org VDC name' oforganization 'Org name' failed.

Explanation: The vApp backup operation failed. Thiserror message is a summary message and does notcontain detailed information.

System action: The configuration information andVMs for the specified vApps are not backed up.Processing continues to the next vApp.

User response: Check the previous messages in thedsmerror.log file for more details about this vApp .

ANS14301I IBM Tivoli Storage Manager detectedMicrosoft Active Directory DomainController on virtual machine 'VM'.

Explanation: The virtual machine contains MicrosoftActive Directory Domain Controller.

System action: IBM Tivoli Storage Manager savedadditional information about this virtual machine.

User response: None

ANS14302W IBM Tivoli Storage Manager failed todetect if Microsoft Active DirectoryDomain Controller on virtual machine'VM'.

Explanation: There was an error while checking if thevirtual machine contains Microsoft Active DirectoryDomain Controller.

System action: IBM Tivoli Storage Manager continuesbacking up this virtual machine.

User response: Check IBM Tivoli Storage Managererror log for additional information.

ANS14303E The vCloud Director vApp 'vapp-name'has not been previously backed up.

Explanation: The specified vCloud Director vApp hasnot been previously backed up, so can not be specifiedfor restore.

System action: The specified vCloud Director vApp isskipped, and the next vApp in the restore list isprocessed.

User response: Verify the vCloud Director vApp nameto be restored, and re-try the operation.

ANS14304I IBM Tivoli Storage Manager could notdetect the TSM for VE license. ActiveDirectory Domain Controller will not beprotected on VM 'VM'.

Explanation: The virtual machine contains MicrosoftActive Directory Domain Controller, but a TSM for VElicense is not detected. The Domain Controller will notbe protected.

System action: Install TSM for VE 7.1 or later toprotect Active Directory.

User response: None

ANS14305W Backup of VMware vApp 'vApp name' inOrganization VDC 'Org VDC name' oforganization 'Org name' completed. SomeVMs were not backed up.mode: 'Incremental Forever - full_or_incr'target node name: 'target_node_name'data mover node name:'data_mover_node_name'VMs backup status: number of VM backedup out of number of VMs in vApp VMsbacked up successfully.

Explanation: The vApp backup operation completedsuccessfully. However, one or more VMs for thespecified vApp were not backed up. These VMs willnot be created during the restore operation.

System action: Processing continues to the next vApp.

User response: Check the dsmerror.log file for thisvApp for more information about this message. Resolvethe problem, then try the operation again.

ANS14308E Full VM backup of 'hypervisor' VirtualMachine 'vmname' failed with RC=rcmode=full_or_incr, target nodename='target_node_name', data movernode name='data_mover_node_name'


System action: The full backup of the virtual machinefinished with failures. The next virtual machine in thevmlist will be processed. The reason for the failure is

ANS14291E • ANS14308E


written to the local client error log.


ANS14311E Full VM restore of 'hypervisor' VirtualMachine 'vmname' failed with RC=rctarget node name='target_node_name',data mover nodename='data_mover_node_name'

Explanation: The Full VM restore of the virtualmachine failed.

System action: The full restore of the the virtualmachine finished with failures. The next virtualmachine in the vmlist will be processed. The reason forthe failure is written to the local client error log.


ANS14446E A file restore mount operation forhypervisor type Virtual Machine 'vmname'failed. The data center node name is'data center node name', the mount proxynode name is 'mount proxy node name'.

Explanation: The file restore mount operation of thevirtual machine failed.

System action: The mount of the virtual machinefinished with failures.

User response: Review the local client error log forthe reason for the failure.

ANS14449E A cleanup of the file restore mount ofhypervisor type Virtual Machine 'vmname'failed. The data center node name is'data center node name', the mount proxynode name is 'mount proxy node name'.

Explanation: The cleanup of file restore mountoperation of the virtual machine failed.

System action: The cleanup of mount of the virtualmachine finished with failures.

User response: Review the local client error log forthe reason for the failure.

ANS14450E The mount proxy platform is notsupported for file restore mountoperations.

Explanation: The file restore mount operation failed.The mount proxy platform is unsupported or the IBMTivoli Storage Manager Recovery Agent is not correctlyinstalled and configured.

System action: The file restore mount operation failed.

User response: Ensure that the IBM Tivoli StorageManager Recovery Agent is installed and configured

correctly and run the file restore mount operation froma supported mount proxy platform.

ANS14451E The Windows iSCSI service is notavailable.

Explanation: The Windows iSCSI service is notavailable on the mount proxy machine. It is either notstarted or is not installed or configured correctly.

System action: Processing stops. The file restoremount operation fails.

User response: Ensure that the iSCSI service is up andrunning on the mount proxy machine.

ANS14900W Schedule 'schedule-name' has opened anew session with the server.

Explanation: A scheduled event endsbecause of aconnection failure. The scheduled event had to berestarted outside its normal startup window tocontinue the operation.

System action: The scheduled event is completedusing more than one session.

User response: None required. If this is a recurrentcondition, you may want to check for networkproblems.

ANS14901E The following object contains one ormore unmatched quotation marks andcannot be processed: 'filespace pathfilename'.

Explanation: The file name in the file list containsunmatched quotes. If a line in the file list begins with asingle or double quotation mark this quotation mark isconsidered to be an opening quotation mark. Thecorresponding closing quotation mark of the same typemust be at the end of the line. If there is no closingquotation mark or the closing quotation mark has beenencountered in the middle of the line, it is an invalidinput.

System action: The object is skipped.

User response: Correct the specification of the object.

ANS14904E Instant access of VMware VirtualMachine 'vmname' failed. target nodename='target_node_name', data movernode name='data_mover_node_name'

Explanation: The instant access of the virtual machinefailed.

System action: The instant access of the the virtualmachine finished with failures. The reason for thefailure is written to the local client error log.


ANS14311E • ANS14904E


ANS14907E Instant restore of VMware VirtualMachine 'vmname' failed. target nodename='target_node_name', data movernode name='data_mover_node_name'

Explanation: The instant restore of the virtual machinefailed.

System action: The instant restore of the the virtualmachine finished with failures. The reason for thefailure is written to the local client error log.


ANS14910E Cleanup of VMware Virtual Machine'vmname' failed. target nodename='target_node_name', data movernode name='data_mover_node_name'

Explanation: The cleanup of the virtual machinefailed.

System action: The cleanup of the the virtual machinefinished with failures. The reason for the failure iswritten to the local client error log.


ANS14915I Object increased in size duringcompression: filespace pathfilename

Explanation: The file increased in size duringcompression.

System action: Processing contiues.


ANS14942E The file specification 'string' is invalid.

Explanation: The operating system indicated that thefile specification is invalid. One possible reason is thatthe file specification contains unrecognized characters.Another possible cause is incorrect use of quotationmarks in the file specification.


User response: Enter a correct file specification asdescribed in the Using the Backup-Archive Client bookfor the particular operating system. Ensure that the filespecification contains valid characters. Verify correctuse of quotation marks for specifications that containblanks spaces. If multiple file specifications are used,make sure that any use of quotation marks does notcause the file specifications to be treated as a single filespecification.

ANS14946W Warning: virtual machine: 'vm-name'disk: 'disk-name' excluded by user, wasnot found.

Explanation: The specified virtual disk does not existon the virtual machine.


User response: Use the "dsmc backup vm ..."command with the -preview option to display a listingof the disk labels which exist on the virtual machine.Since the disk was specified to be excluded from thebackup, the backup will continue. However it ispossible that a disk will included in the backup whichwas not desired, check the spelling of the disk label,and correct the disk label if an undesired disk is nowincluded in the backup operation.

ANS14947E Error: virtual machine: 'vm-name' disk:'disk-name' included by user, was notfound.

Explanation: The specified virtual disk does not existon the virtual machine.


User response: Use the "dsmc backup vm ..."command with the -preview option to display a listingof the disk labels which exist on the virtual machine.Check the spelling of the disk label and correct the disklabel and then retry the 'backup vm' operation.

ANS14948E A specified virtual disk was not foundon the virtual machine.

Explanation: You must specify a virtual disk labelname which exists on the virtual machine.


User response: For a backup operation, use the "dsmcbackup vm ..." command with the -preview option todisplay a listing of the disk labels which exist on thevirtual machine. For a restore operation, use the "dsmcquery vm ..." command with the -detail option todisplay a listing of the disk labels which exist on thevirtual machine backup. Check the spelling of the disklabel and correct the disk label and then retry theoperation.

ANS14972W File server file-server-name has beenupgraded to Data ONTAP version'version.modifcation.submodification'. Thisversion does not support unicode filenames for snapshot differenceincremental backup. Upgrade to aversion that supports unicode file namesas soon as possible.

Explanation: The file server has been upgraded from aversion that supports unicode file names forincremental backup using snapshot difference to a

ANS14907E • ANS14972W


version that does not. If you have upgraded from DataONTAP version 7.3.3 (or later) to 8.0, you lose theability to back up files with unicode file names whenperforming snapshot difference incremental backup.

System action: Processing continues. However, fileswith unicode names are not backed up.

User response: Upgrade to a version that supportsunicode file names as soon as possible. If you haveupgraded from Data ONTAP version 7.3.3 (or later) to8.0, upgrade to 8.1 (or later). If it is not possible toupgrade at this time, you can suppress this warningmessage by renaming the file space on the IBM TivoliStorage Manager server and performing a snapshotdifference incremental backup.

ANS14973E An error occurred accessing NTFSsecurity information for file 'filespacenamepath-namefile-name'

Explanation: An access denied error occurred whileattempting to access NTFS security info rmation.


User response: See your system administrator orbypass the failing check by using SkipNTSecu rityoption.

ANS14974E Error processing 'filespacenamepath-namefile-name': a required NTprivilege is not held.

Explanation: The user account running TSM does notpossess a required NT user right/pr ivilege forperforming the current operation.


User response: Your system administrator has theauthority to grant the needed privilege.

ANS14987E Error processing 'filespacenamepath-namefile-name': the object is inuse by another process



User response: Ensure that the file is not locked byanother process. If the file is not locked, retry thecommand.

ANS14988W File 'filespace namepath-namefile-name' iscurrently unavailable on server and hasbeen skipped.

Explanation: You tried to restore or retrieve a file thatis currently not available from the TSM server. This ismost likely a temporary condition.


User response: Try to restore or retrieve the file againafter the file becomes available on the server. If theproblem persists, see your TSM administrator forassistance.

ANS14989E Error processing 'filespacenamepath-namefile-name': the directory isin use by another process. All objects inthe directory and any of itssubdirectories are skipped.

Explanation: The specified directory is being used byanother process. You tried to read from or write to adirectory that is currently being used by anotherprocess. The objects contained in the directory and itssubdirectories are not backed up.

System action: Processing stopped for that directory.If other files and directories were also specified in thisbackup, they are processed

User response: Ensure that you specified the correctdirectory name, correct the permissions, or specify anew location.If the directory name is correct, retry thebackup when no process has exclusive use of thedirectory.

ANS14991I Application Type Application Message IdApplication Message

Explanation: This is a message sent by the applicationyou are currently running with TSM.

System action: TSM logs the application message.

User response: Refer to the documentation for theapplication that you are using.

ANS14992W Application Type Application Message IdApplication Message




ANS14993E Application Type Application Message IdApplication Message




ANS14973E • ANS14993E


ANS14994S Application Type Application Message IdApplication Message




ANS14997E Error processing 'filespacenamepath-namefile-name': file system quotareached condition - no space left.

Explanation: No more files can be restored orretrieved because the quota of the destination filesystem has been reached.


v Retry this object

v Skip this object

v Abort the action

User response: Select the appropriate action for thisobject. Create some free space or increase the quota onthe destination file system before you retry theoperation. Another option is to restore or retrieve thefile to another file system.

ANS14998E Link information for file 'filename' couldnot be obtained: access to the object isdenied.

Explanation: Access to the specified file link is denied.You tried to read information for file link and you donot have access permission for this object.

System action: Processing of System State stops.

User response: Try the operation again. If the problempersists, contact IBM technical support for additionalassistance.

ANS14999I The following message was too long tolog to the server: 'shortened message withmessage number'

Explanation: The message text and inserts are toolarge to send to the server in the available internalbuffer.

System action: The message number message is writtento the local client error log, then shortened and sent tothe server as a part of this message. The message isreduced in length by substituting '...' in the middle ofthe original message.

User response: The message referred to has beenshortened, but describes the error that occurred. See thedocumentation for that message for more information.

ANS5003S The management class assigned todirectories does not exist.




ANS5004S There is no backup copy group in themanagement class used for directories.See the error log.




ANS5005E Table of contents information is notavailable for the selected images.

Explanation: An error occurred when the server triedto load a table of contents. Requested image or table ofcontents may have expired or been deleted on theserver.


User response: Start a new restore window to getcurrent information.

ANS5006W The policy set does not contain anybackup copy groups. TSM is unable tocontinue the backup.

Explanation: You tried to back up the files using apolicy set that contained no backup managementinformation.

System action: TSM did not back up the files.

User response: See your TSM administrator forassistance in associating your node with a policy set

ANS14994S • ANS5006W


containing a management class that has a backup copygroup. Then try the operation again.

ANS5007W The policy set does not contain anyarchive copy groups. TSM is unable tocontinue the archive.

Explanation: You tried to archive the files using apolicy set that contains no archive managementinformation.

System action: TSM did not archive the files.

User response: See your TSM administrator forassistance in associating your node with a policy setcontaining a management class that has an archivecopy group. Then try the operation again.

ANS5008W Incorrect password entered

Explanation: You entered a password that wasincorrect.

System action: TSM cannot connect to the serverwithout the correct password.

User response: Reenter the password, or ask yoursystem administrator for the current password.

ANS5009W New password entries are not the same

Explanation: During the change password, updatepassword, or open registration dialog, the two entriesfor the new password were not the same.

System action: The password was not changed on theserver.

User response: Backspace over both of the newpasswords and reenter them, ensuring that they match.

ANS5011I Backup stopped by user

Explanation: You requested to stop the backupoperation.

System action: Backup stopped.


ANS5012E Server out of backup data storage space

Explanation: The server ran out of space in its backupdata storage.

System action: TSM cannot complete the requestedbackup operation. Any files displayed on the lower halfof the backup activity panel were successfully backedup.


ANS5013E Not enough memory for backupoperation

Explanation: TSM cannot allocate memory for thespecified backup operation.


User response: Close all unneeded applications andretry the operation. Reducing the scope of queries andthe amount of data returned might also help, or seeyour system administrator.

ANS5014I Backup completed

Explanation: The backup was completed.

System action: TSM backed up the files.


ANS5015I Restore stopped by user

Explanation: You requested to stop the restoreoperation.

Attention: If you were restoring files with “overwrite”option specified, the file you restored last can bedamaged (partially overwritten).

System action: Restore stopped.


ANS5016E Not enough memory for restoreoperation

Explanation: TSM cannot allocate memory for therequested restore operation.

System action: TSM cannot complete the requestedrestore operation.

User response: Close all unneeded applications andretry the operation. Reducing the scope of queries andthe amount of data returned can also help, or see yoursystem administrator.

ANS5017I Restore completed

Explanation: A restore was completed.

System action: TSM restored the files.


ANS5018E Not enough memory for archiveoperation

Explanation: TSM cannot allocate memory for therequested archive operation.

System action: TSM cannot complete the archiveoperation.




ANS5019I Archive stopped by user

Explanation: You requested to stop the archiveoperation.

System action: Archive stopped.


ANS5020E The TSM server is out of archive datastorage space.

Explanation: The server ran out of space in its archivedata storage.

System action: TSM cannot complete the requestedarchive operation.

User response: Report the problem to your TSMsystem administrator, who can allocate more resourcesto archive storage.

ANS5021I Archive completed

Explanation: An archive was completed.

System action: TSM archived the files.


ANS5022I Retrieve stopped by user

Explanation: You requested to stop the retrieveoperation.

Attention: If you were retrieving files with“overwrite” option specified, the file you retrieved lastcan be damaged (partially overwritten).

System action: Retrieve stopped.


ANS5023E Not enough memory for retrieveoperation

Explanation: TSM cannot allocate memory for thespecified retrieve operation.

System action: TSM cannot complete the requestedretrieve operation.


ANS5024I Retrieve completed

Explanation: A retrieve was completed.

System action: TSM retrieved the files.


ANS5025E The node name contains invalidcharacters.

Explanation: The specified node name has invalidcharacters.


User response: Retry with another node name thathas valid characters.

ANS5026W MatchAllChar and MatchOneCharoptions MUST precede Include/Excludeoptions

Explanation: The MatchAllChar and MatchOneCharoptions must precede any include-exclude options.

System action: The TSM client ends the currentapplication.

User response: Move the MatchAllChar andMarchOneChar options before any include-excludeoptions.

ANS5027W Objects of different types cannot bebacked up at the same time.

Explanation: Backing up objects of different types atthe same time is not allowed in certain scenarios. Forexample, backing up Hyper-V and VMware virtualmachines at the same time is not possible.


User response: Select objects of the same type toperform backup operation.

ANS5028I Successful completion




ANS5029E This operation cannot continue due toan error on the TSM server. See yourTSM server administrator for assistance.

Explanation: The TSM server encountered an errorcondition that prevents the TSM client operation fromcontinuing. Your TSM server administrator can reviewthe TSM server activity log for more details about theerror.

System action: The processing stopped.




ANS5030E No objects on server match query

Explanation: No objects on the server match the queryoperation being performed.


User response: Ensure the names are properlyentered.

ANS5031E Client aborted transaction




ANS5032W Active object not found

Explanation: An attempt was made to expire anobject, but the server was unable to find an activebackup version of the object. This message is precededby message ANS1228E which specifies the object name.For instance, this message could be issued if twoseparate client processes are backing up the same filesystem at the same time. If one of the processes expiresa file, then the server will make that file inactive. If thesecond process subsequently attempts to expire thatsame file, the server will not find an active version ofthe file, so the second process will issue this messagefor that file.

System action: The object is not expired. Processingcontinues with the next object..

User response: Review the console output, schedulelog, or error log and locate the ANS1228E message thatimmediately precedes this message. ANS1228E willidentify the object that could not be expired. Examinethe conditions under which the problem occurred andassess whether those conditions explain the occurrenceof this message. For example, this message couldappear if multiple instances of the client wereattempting to back up the file system concurrently. Ifthe reason this message occurred can not bedetermined and the message occurs when the operationis tried again, then contact support for furtherassistance. Also try searching for this message numberon http://www.ibm.com for possible solutions.

ANS5033E Server has no data for the object.

Explanation: Server tried to do a restore or retrieve onan object that has no data associated with it. If acorrective action is possible, it is with the server.

System action: Server ends the current operation.

User response: Ask the administrator to check theactivity log for any messages related to this error thatmight help identify the problem.

ANS5034E You entered an incorrect password.


System action: The processing stops.

User response: Retry the session with the correctpassword. If this fails or you have forgotten yourpassword, ask the administrator to assign a newpassword.

ANS5035E Node is in use.




ANS5036E Expiration date must be greater thantoday's date

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

System action: The current operation is canceled.

User response: Retry archiving the file with anexpiration date that is higher than today's date.

ANS5037W The requested data is offline

Explanation: For the restore or retrieve operation, oneor more of the requested files must be recalled fromoffline storage media (generally tape). The wait timedepends on your site's offline storage managementpolicies.

System action: CLient waits for offline storage mediato become available and then continues.


ANS5038E Object too large for server limits.



User response: See your system administrator todetermine the maximum file (object) size for whichyour site's server is configured.



ANS5039E Server out of data storage space.


System action: Ended the current operation.


v For client, set COMPRESSALWAYS=NO andCOMPRESSIon=YES in the options file (DSM.OPT),then the file will be resent uncompressed if it growsduring compression.


v The system administrator can also turn off diskcaching in the disk storage pool, and issue MOVEDATA commands to each disk pool volume to clearout the cached bitfiles.

ANS5040E Server media mount not possible.



User response: Retry later when server volumes canbe mounted. Ensure that the MAXNUMMP (maximumnumber of mount points) defined on the server for thisnode is greater than 0.

ANS5041E Size estimate exceeded.




ANS5042E File data is currently unavailable on theTSM server

Explanation: The TSM client was trying to restore orretrieve data that is currently unavailable on the TSMserver. Possible causes are:

v Data is corrupted at the TSM server

v The TSM server encountered a read error


v The TSM requested a tape volume that isunavailable. Typical reasons for a volume to be

unavailable: a disk volume is offline, the volume ismarked unavailable due to an I/O error, or a tapevolume is checked out of the tape library.


User response: Try the operation again at a later time.If the problem continues, contact your TSM serveradministrator for further assistance. The administratorcan review the TSM server activity log for messagesrelated to the problem.

ANS5043W Unexpected retry request. The serverfound an error while writing the data.

Explanation: None.

System action: The client retries the operation.


ANS5044E Session rejected: All server sessions arecurrently in use.

Explanation: Server has all available sessions in useand cannot accept a new one at this time.

System action: Server canceled the current operation.

User response: Retry the operation.If the problemcontinues, see your system administrator to increase thenumber of concurrently active sessions to the server.

ANS5045E The session is rejected. Your passwordhas expired.

Explanation: Your password has expired.

System action: Server canceled the current operation.You are not allowed to connect to the server until thepassword is updated.

User response: Update your password. You may usethe SET PASSWORD command, or have theadministrator update your node.

ANS5046E Session rejected: Unknown or incorrectnode ID entered

Explanation: The node name you entered is notknown by the server, or you are attempting to access afile migrated to a different node.

System action: The current operation is canceled. Youare not allowed to connect to the server until yournode name is registered with the server. If attemptingto access a migrated file, your node name must be thesame node which migrated the file.

User response: Ensure that you entered your nodename correctly. If yes, see your system administrator.Verify that the server is using closed registration andthat your node name is registered with the server.



ANS5047E Session rejected: Duplicate ID entered.Node already logged onto server


System action: Cannot connect to the server. Canceledthe current operation.

User response: Ensure that your node name is uniqueto the server so that it cannot be used by anotherperson. See your system administrator to identify theowner of that node name.

ANS5048E Please choose a filespace.The filespaceto delete/set access cannot be found.




ANS5049E Session rejected: The server is disabled


System action: Canceled the current operation.

User response: Retry the operation after the serverreturns to an enabled state. If the problem continues,see your system administrator.

ANS5050E The server is not configured to allowopen registration.



User response: You must obtain a node and passwordfrom your system administrator.

ANS5051S Session rejected: the client code isdown-level



User response: See your system administrator to seewhat version to run for your location.

ANS5052E Session rejected: Downlevel server codeversion.



User response: See your system administrator to seewhat version to run for your location.

ANS5053W The operation was stopped by the user.




ANS5054E The operating system refused a requestfor memory allocation.

Explanation: The client requires access to memory inorder to store information as processing proceeds. Inthis case, more memory was requested than theoperating system would allocate. Possible reasonsinclude:

v The system is low on memory.

v The process in which the program runs has exceededthe maximum allocated memory.

v Some other error condition occurred. No memory isavailable.

System action: Client cannot complete the requestedoperation.

User response: Close all unneeded applications andtry the operation again. If the operation still fails, trydividing the task into several smaller units. Forexample, if a file specification contains severalhigh-level directories, run the task serially for eachdirectory. If the task is an incremental backup, use theoption "-memoryefficientbackup=yes".

ANS5055E File not found during Backup, Archiveor Migrate processing. No filespecification entered.

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



ANS5056E The specified directory path could notbe found.






ANS5057E Access to the specified file or directoryis denied.




ANS5058E No file handles available




ANS5059E The file exists and cannot beoverwritten.



User response: Verify that you have sufficient accesspermissions to overwrite the file, then try the operationagain. If the problem persists, contact your systemadministrator or administrator for further assistance.

ANS5060E Invalid parameter passed.




ANS5061E An invalid file handle passed.Report how you got this system error.

Explanation: An internal system error occurred. A fileoperation failed because of an invalid file handle.


User response: Try the operation again. If the failurepersists, obtain a service trace that captures theproblem and contact technical support for additionalassistance. Your administrator can help you configurethe trace.

ANS5062E Disk full

Explanation: Operation has stopped because thedestination disk is full.


User response: Free up disk space and retry theoperation

ANS5083E Drive specification contains wildcardcharacter.

Explanation: Drive name shouldn't contain wildcardcharacter.

System action: Wildcarded objects skipped.

User response: Use valid drive specification.

ANS5091S The TSM server does not currently havespace in the storage pool for this file.This might be a temporary condition.

Explanation: This message is typically issued whenthe storage pool in which the data is being placed doesnot have sufficient to store the data, but that the spacewill be available soon. For example, a storage poolmigration may free up sufficient space to store the data.


User response: This is possibly a temporary condition.Try the operation again at a later time. If the errorpersists, contact your TSM administrator, who canexamine server console and error logs to locate thecause of the problem.

ANS5092S Server out of data storage space.

Explanation: The server does not have any more spaceavailable to store the object.



ANS5093S SLM_LICENSE_EXCEEDED: The clientlicenses for TSM are exceeded. See yourTSM administrator.

Explanation: Adding a new enrollment will exceed theproduct license count for this TSM server.

System action: The client enrollment or connectionrequest ends.

User response: See your TSM administrator to deleteunused enrollments or negotiate an increase in thenumber of allowed licenses for your server.



ANS5094E Session Rejected. Sufficient servermemory is not available.




ANS5122E The specified filespace does not exist onthe server. The filespace might havebeen deleted by another client or anadministrator.

Explanation: The specified filespace does not exist onthe server. Your administrator might have alreadydeleted the filespace or another client using yourclient's node name might have deleted it.


User response: The filespace you selected does notexist any more. See your TSM administrator for help infinding how the filespace was deleted.

ANS5123S Open registration failed because thespecified node name is already definedin the server.

Explanation: Open registration failed because a nodeis defined on the server with the same name.



ANS5124S Open registration failed because there isno default domain.

Explanation: Open registration failed because adefault policy domain does not exist in which to placeyour node. A default policy domain is required to fullysupport open node registration.

System action: TSM cancels the current operation.

User response: See your TSM administrator forassistance in registering your node.

ANS5125S Open registration failed because aninvalid node name was specified.

Explanation: Open registration failed because thespecified node name has invalid characters.


User response: Retry with another node name thatdoes not have any invalid characters.

ANS5126S Filespaces with duplicate names are notsupported. Please unmount theduplicate filespace.

Explanation: The selected filespace has a duplicatevolume label. Because TSM uses the volume label tokeep track of backup/archive information, it cannotback up or archive files from a filespace with aduplicate volume label.

System action: TSM cannot select the volume.

User response: If the filespace needs to be available tothe system, exit TSM, and assign a volume label to thefilespace. Restart TSM and retry the operation.Otherwise, unmount the duplicate filespace.

ANS5127I TSM has detected an incomplete setup!The system options file 'dsm.sys' wasnot found, while the client options file'file-path' exists!The wizard will guide you through theconfiguration process of the initial basicTSM client options files replacing yourcurrent option file. Would you like tocontinue?

Explanation: TSM has detected an incomplete setup.The system options file, dsm.sys, was not found.Additionally, a user options file, dsm.opt, was found.To complete the configuration the configuration wizardwill create dsm.sys and replace dsm.opt with minimalsettings.

System action: TSM may stop

User response: If the current version of dsm.opt isneeded, rename the file and restart TSM. If the currentversion is not needed, select yes and allow TSM toreplace the file.

ANS5128E The management class for this file didnot have a backup copy group.

Explanation: For backup operations, a file may onlybe bound to a management class that has a backupcopy group.


User response: See your TSM system administratorfor assistance in finding a management class with therequired copy group. The administrator may alsodefine such a management class for you.

ANS5129E The management class for this file didnot have an archive copy groupspecified.

Explanation: For archive operations, a file may onlybe bound to a management class that has an archivecopy group.

System action: TSM did not archive the file.



User response: See your TSM system administratorfor assistance in finding a management class with therequired copy group. The administrator may alsodefine such a management class for you.

ANS5130W No filespaces selected for deletion

Explanation: You requested a deletion operationwithout selecting a client domain.

System action: TSM cannot perform a deletionwithout a domain selected.

User response: Select the volumes you want to deleteand retry the operation.

ANS5132I Filespace deletion canceled by user

Explanation: You requested to cancel the filespacedeletion operation.

System action: The filespace deletion operationstopped.


ANS5133I Filespace 'filespace' was deleted

Explanation: The specified filespace was successfullydeleted.

System action: TSM deleted the filespace.


ANS5134E Unable to delete the filespace becausethis node does not have permission todelete archived data and/or backed updata.

Explanation: You tried to delete a filespace that youdo not have permission to access.


User response: Ensure that you specify the correctfilespace, or specify a filespace you have access to.

ANS5135I Archive delete stopped by user

Explanation: You requested to stop the archive deleteoperation.

System action: Archive delete stopped.


ANS5138I Archive delete completed

Explanation: An archive delete was completed.

System action: TSM deleted the archived files.


ANS5139E Your node does not have permission todelete archived files.

Explanation: Your node is registered at the serverwith the ARCHDELETE option set to 'no'. Thereforeyour node is not allowed by the server to deletearchived files.

System action: TSM did not delete the archived files.

User response: See your TSM system administrator.The administrator has authority to delete archived files,and can also grant that authority to your node.

ANS5145W Server cannot restart the last restorerequest. Do you want to restore withoutrestart?

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


User response: Retry the request without restart orabort the request.

ANS5146W You cannot perform this operation whileaccessing data for another node. Do youwish to switch back to accessing yourown node?

Explanation: The user cannot perform the selectedoperation while accessing another users data.


User response: Answer "Yes" to switch back toaccessing the server as the original node.

ANS5148W The server needs to do a one-timeconversion of your archive data beforeyou can continue. This operation maytake a long time, and cannot be canceledonce it has started. Are you willing towait for the conversion to complete?

Explanation: The server must do a conversion of thearchive data before continuing. The conversion couldtake a long time, and cannot be canceled once it isstarted.


User response: Answer “Yes” to start the archive dataconversion. If you answer “No”, the current operationwill be canceled.



ANS5150E An active restore for the same sourcefile specification exists. Unable tocontinue with this request.

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

System action: The requested restore fails.

User response: Start another restore with a differentsource file specification.

ANS5151S This node currently has a pendingrestartable restore session. Therequested operation cannot completeuntil this session either completes or iscanceled.

Explanation: This operation can not be completedbecause a restartable restore session is pending. Theoperation is not allowed because the restartable sessionand the current operation affect the same file space.


User response: Issue the Query Restore command toview a list of your restartable restore sessions in theserver database. Issue the Cancel Restore command tocancel any unneeded restartable restore sessions.

ANS5152S Session Rejected: The server is notlicensed for this platform type. See yourTSM administrator.

Explanation: The server license governs the types ofclient that can connect to it. The license for this serverdoes not include the requesting client type.

System action: The client enrollment or connectionrequest ends.

User response: See your TSM administrator who mustupgrade the server license to accept your client type.

ANS5153E Session Rejected: The server does notallow a signon as a Unicode enabledclient.

Explanation: The client cannot establish a connectionto the server because of a unicode enabling mismatchbetween server and client.



ANS5154I File is implicitly excluded

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

System action: TSM will not back up or migrate animplicitly excluded file.


ANS5155E The valid password is not available. TheTSM administrator for your systemmust run TSM and enter the passwordto store it locally.

Explanation: The file containing the stored passwordfor the specified server is unavailable.


User response: The TSM administrator for yoursystem must set and store a new password.

ANS5158S Filespace deletion is in progress. Tryagain later.

Explanation: The filespace is in the process of beingdeleted.


User response: Try the operation again later. If thefilespace was being deleted, it could take awhile for itto complete. If the problem continues, report theproblem to your system administrator.

ANS5164E Backup or archive of drives withduplicate volume labels is not allowed.

Explanation: You tried to back up or archive a drivethat has a duplicate volume label. Because TSM usesthe volume label to keep track of backup or archiveinformation, it cannot back up or archive files from adrive with a duplicate volume label.

System action: TSM cannot select the drive for backupor archive operations.

User response: If the volume needs to be available tothe system, exit TSM and assign a unique volume labelto the drive. Restart TSM and try the operation again.

ANS5165E Drive has no volume label.Backup/Archive not allowed.

Explanation: You tried to backup or archive a drivethat has no volume label.

System action: TSM rejected the selected drive.

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

ANS5166E An error occurred while removinginclude-exclude statement 'statement'.Please try again.

Explanation: There was a problem with removing theinclude-exclude statement. Make sure that your



include-exclude statement is valid.

System action: No include-exclude statement wasremoved. Waiting for user action.

User response: Retry your operation. If you see thiserror message again, contact your system administrator

ANS5176W The requested virtual machine operationcannot be performed because a virtualmachine backup or restore operation isalready in progress. Please retry theoperation after the first operationcompletes.

Explanation: A virtual machine operation is already inprogress, so the requested virtual machine operationcannot be performed until the first operation complets.


User response: Wait for the first virtual machineoperation to complete, and then restart the currentrequest.

ANS5177E Client-side deduplication andserver-initiated sessions are mutuallyexclusive.

Explanation: Conflicting optionsSESSIONINIT=serveronly and DEDUPLICATION=yeswere specified. This combination is not allowed.


User response: Use client-initiated sessions or disableclient-side deduplication

ANS5178E Restart of the RSM service failed.Restart the RSM service manually.

Explanation: RSM database files have been restoredfrom the TSM server and imported. TSM has tried torestart the RSM service on the user's behalf but has runinto a problem.


User response: Restart the RSM service manually.

ANS5179E TSM is unable to continue. Exitingprogram.

Explanation: TSM ran into a problem and is unable tocontinue. This error message is usually preceded byother error messages. Resolve those errors and tryagain.

System action: Program terminates.

User response: Fix the problem(s) that preceded thismessage and then restart TSM.

ANS5181E Invalid selection; A specific backup setmust be selected.

Explanation: A selection was made that might resultin multiple backup sets being restored at the sametime, but restoring multiple backup sets at the sametime is not supported.

System action: The backup set restore was notperformed.

User response: Select a specific backup set to berestored.

ANS5182E Multiple backup sets can not berestored at the same time.

Explanation: Multiple backup sets were selected to berestored, but restoring multiple backup sets at the sametime is not supported.

System action: The backup set restore was notperformed.

User response: Select a specific backup set to berestored.

ANS5183W Objects of different types cannot berestored at the same time.

Explanation: Restoring objects of different types is notallowed. For example, restoring Backup Sets andregular file objects at the same time is not possible.


User response: Select objects of the same type toperform restore operation.

ANS5184E Illegal Operation On Following Object:object

Explanation: Requested operation cannot beperformed on this object.


User response: Try another operation on this object, ortry the same operation on another object.

ANS5186E Server is downlevel, System Servicesand System State backup disabled forthis session.

Explanation: The operation cannot be performedbecause server version is downlevel.

System action: System Service and System Statebackup is disabled for this session.

User response: Must use level 5.2.0 or higher server.



ANS5187E Unable to set SHAREAS extendedattribute for file:'pathname'Return code: 'returncode' 'strerror'Reason code: 'reasoncode'

Explanation: You must be the file owner or havesuperuser authority.

System action: File processed without settingattribute.

User response: The attribute must be set manually.

ANS5191E NT Active Directory is not online.Offline backup is not supported.

Explanation: NT Active Directory is not online whenperforming a backup operation. Offline backup is notsupported.


User response: Reboot computer and turn on ActiveDirectory, and try the operation again.

ANS5192E NT Active Directory is online. Onlinerestore is not supported.

Explanation: NT Active Directory is online whenperforming a restore operation. Online restore is notsupported.


User response: Reboot computer and enter ActiveDirectory repair mode, then try the operation again.

ANS5193E Certificate Services is not online.Offline backup is not supported.

Explanation: Certificate Services is not online whenperforming a backup operation. Offline backup is notsupported.


User response: Start Certificate Services and try theoperation again.

ANS5194E Certificate Services is online. Onlinerestore is not supported.

Explanation: Certificate Services is online whenperforming a restore operation. Online restore is notsupported.


User response: Stop Certificate Services and try theoperation again.

ANS5196W Invalid encryption key passwordentered.

Explanation: The encryption key password supplieddoes not meet the TSM requirements. This key can beup to 63 bytes in length and include the followingcharacters: A-Z Any letter, A through Z, uppercase orlowercase 0-9 Any number, 0 through 9 + Plus . Period_ Underscore - Hyphen & Ampersand

System action: TSM allows you to try again.


ANS5201E The specified function is notimplemented

Explanation: The specified function is notimplemented.



ANS5202I One or more system objects wereexcluded from processing by entries inthe include-exclude list.

Explanation: One or more system objects wereexcluded from processing by entries in theinclude-exclude list and the client did not process them.

System action: Excluded objects skipped.


ANS5204W Only one backup set may be selectedfor restore.

Explanation: Restoring multiple backup sets is notallowed. Only one backup set may be selected andrestored.


User response: Only one backup set may be selectedfor restore.

ANS5208E An invalid date or time was entered.

Explanation: An invalid date or time value wasentered. Either the syntax of the value was not correct,or an actual value (for example, “45” for month) wasinvalid.


User response: Identify and correct the invalid date ortime value. Refer to the user’s guide of thecorresponding platform for the correct date syntax.



ANS5209E System Volume backup failed.

Explanation: IBM Tivoli Storage Manager encounteredan error while backing up files of the Windows 2000System Volume


User response: Examine the Windows 2000 FileReplication Service Event log to insure the systemvolume was successfully initialized. Restart the serviceand retry the backup operation

ANS5210E System Volume restore failed.

Explanation: IBM Tivoli Storage Manager encounteredan error while restoring files of the Windows 2000System Volume


User response: Examine the Windows 2000 FileReplication Service Event log to insure the systemvolume was successfully initialized. Restart the serviceand retry the restore operation.

ANS5211E The cluster service is offline. The clusterservice must be online to perform anauthoritative cluster database restoreoperation.

Explanation: The cluster service must be online torestore the cluster database. Tivoli Storage Managertried to start the service and failed. It is possible that anauthoritative restore cannot be done.


User response: Start the cluster service and retry theoperation.

ANS5212E An error occurred while trying torename file space.

Explanation: This operation can not be completedbecause the file space could not be renamed.


User response: Contact system administrator for moreinformation.

ANS5215E function-type is not allowed on object'object'.Object is not sent to the server.

Explanation: The operation could not be performedon this object. For example, if this is an imageoperation, the selected path is a file or a directory andtherefore is not a valid object for image operations.

System action: This object is skipped.

User response: Verify that the object named is of atype supported by the command. For example, if a

filespace name is required but a directory name wasgiven, change the name so it includes only the filespacename.

ANS5216E Could not establish a TCP/IP connectionwith address 'tcp-addr:tcp-port'. TheTCP/IP error is 'tcp-err-string' (errno =errno).

Explanation: A TCP/IP connection was attemptedwith a server or agent program and failed.


User response: Ensure that the target TCP/IP addressand port number is correct. Check to ensure that a TSMserver or agent has been started at the target TCP/IPaddress and is configured to listen at the port listed inthe message.

ANS5217E Your node does not have permission todelete backed up files.

Explanation: You cannot delete backed up files unlessyour TSM administrator has authorized your node todo so.

System action: TSM does not delete the backed upfiles.

User response: Use the DSMC QUERY SESSIONcommand to verify your authorization. Ask your TSMadministrator to provide the necessary authorization.

ANS5219W Objects of different groups cannot berestored at the same time.

Explanation: Restoring objects of different groups isnot allowed.


User response: Select objects of the same group toperform restore operation.

ANS5222E The archive description exceeds 254characters.

Explanation: TSM places a maximum length of 254characters on the archive description.


User response: Issue the command again and specifya shorter valid archive description.

ANS5224W Error error code encountered whilereverting to the restored snapshot.

Explanation: After the virtual machine disks arerestored, the virtual machine is reverted to the restoredstate. The specified error was encountered whileperforming this revert operation.




User response: Try powering on the restored virtualmachine. If it fails to start, re-try the restore process.

ANS5225W Error error code encountered whileremoving the restored snapshot.

Explanation: After the virtual machine disks arerestored, the virtual machine is reverted to the restoredstate, and the snapshot is removed. The specified errorwas encountered while removing the snapshot.


User response: Try powering on the restored virtualmachine. If it fails to start, re-try the restore process.

ANS5226E The virtual machine backup operationfailed.

Explanation: The virtual machine backup operationfailed. Check the error log for details on why theoperation failed.



ANS5227E TSM detected an error where both asnapshot name was specified, and arequest to create a snapshot werespecified.

Explanation: Either a snapshot name should bespecified, or a request for TSM to create the snapshotshould be specified, but not both.


User response: This is an internal error and should bereported to your service representative.

ANS5228E A backup VM operation failed becauseVMMAXPARALLEL was reduced to 1and the client still cannot obtain aserver mount point.

Explanation: During a parallel backup operation,concurrent backup sessions required additional servermount points to perform the backups in parallel. Theclient attempted to obtain the additional mount points,but the client requests exceeded the number of mountpoints (MAXNUMMP) defined for the node. In aneffort to make the backup occur, the client reduced theVMMAXPARALLEL option to 1, but was still unable toobtain a mount point. The backup operation wasstopped.

System action: The backup operation was stopped

User response: Check the console or schedule log foradditional information. Retry the operation at a latertime. Ensure VMMAXPARALLEL is set to a value less

than or equal to MAXNUMMP.

ANS5229E The Snapshot is already mounted forbackup 'backup-name'.

Explanation: The Snapshot is currently mounted onthe local machine or a remote machine. No mountoperation on the snapshot will be allowed until it hasbeen unmounted.



ANS5230E The Snapshot is already imported to thelocal system for backup 'backup-name'.

Explanation: The Snapshot is currently imported onthe local machine. This maybe becasue the Snapshot isin use or it was not created with the Import VSSsnapshots only when needed feature enabled.


User response: Remote Mount operation not allowedon snapshots that are currenlty imported.

ANS5231E VMDK size reported by VMwarevSphere API is different than actual sizeof vmdk file. Reissue the restorecommand with the testflag-VMRESTORE_INCVMDKSIZE.

Explanation: VMDK size reported by VMwarevSphere API for virtual machine configuration isdifferent than actual size of vmdk file. This can be theresult of running a storage alignment tool on vmdkfiles before backup.


User response: Reissue the restore command with thetestflag -VMRESTORE_INCVMDKSIZE.

ANS5232I The virtual machine backup operationwas skipped.

Explanation: The virtual machine backup operationwas skipped. Check the error log for details on why theoperation was skipped.

System action: Processing of the virtual machine isskipped

User response: Review the console output and errorlogs for the details.

ANS5233E The directory cannot be found in thespecified backup. The top-leveldirectory is displayed.




System action: The top-level directory is displayedinstead.

User response: Select a valid directory and change thebackup again.

ANS5234E The system cannot connect to the virtualmachine or the machine is powered off.If the problem persists, contact youradministrator.

Explanation: The virtual machine is powered off orthe Windows domain administrator credentials is notcorrect.


User response: Ensure that the virtual machine ispowered on. Use dsmc SET PASSWORD -type=DOMAIN’domain\userid’ ’password’ to update the Windowsdomain credentials. Then, try the operation again.

ANS5235E The virtual machine cannot be reachedor a firewall is blocking the connectionto the machine.

Explanation: The file restore interface cannot reach thevirtual machine or a firewall is blocking the connection.


User response: Ensure that the virtual machine ispowered on. If the virtual machine is powered on,review the firewall rules to ensure that the correct portsare opened. Also ensure that the virtual machine hostname and TCP/IP address are resolving in the DNSserver and there are no network issues.

ANS5236E You do not have permission to restorethe file to the destination folder.

Explanation: The user does not have permission torestore files to the selected destination.


User response: Ensure that the user has properpermissions to restore files to selected location.

ANS5237E File Restore is not set up correctly or thevirtual machine cannot be reached.Contact your administrator forassistance.

Explanation: The user is unable to log in to the filerestore interface due to one of the following reasons:

v The configuration of File Restore is incorrect becausethe Windows domain credentials do not have thecorrect permissions.

v The virtual machine is powered off or a firewall isblocking the connection.

v A network issue.


User response: The administrator can take thefollowing actions to correct the problem:

v Ensure that the Windows domain credentialsprovided in the configurations notebook has thecorrect permissions to connect to the virtual machine.

v Ensure that the virtual machine is powered on andany firewall has been updated to allow connectionsfrom the mount proxy machine.

v Ensure that the mount proxy machine is able toconnect to the virtual machine manually to ensurethere is no networking issue.

ANS5245W TCPWINDOWSIZE optionCur isspecified, but exceeds the maximumvalue allowed by TSM.TCPWINDOWSIZE optionNew will beused instead.

Explanation: Refer to product manual for moreinformation about the TCPWINDOWSIZE option.

System action: The operation continues with themaximum value allowed by TSM.

User response: Set TCP window size to a value in theallowable range.

ANS5246W TCPWINDOWSIZE optionCur isspecified, but exceeds the maximumvalue allowed by the operating system.TCPWINDOWSIZE optionNew will beused instead.

Explanation: The specified value is within the rangeallowed by TSM, but the operating system restricts thevalue to something less.

System action: The operation continues with themaximum value allowed by the operating system.

User response: Set TCP window size to a valueallowed by the operating system.

ANS5247E The configuration for File Restore is notcomplete. Contact your administrator forassistance.

Explanation: The user is unable to log in to the filerestore interface because the Windows domaincredentials are missing.


User response: The administrator must provide theWindows domain administrator credentials in the FileRestore page of the configuration notebook in the DataProtection for VMware vSphere GUI.



ANS5249E The virtual machine restore operationfailed.

Explanation: The virtual machine restore operationfailed. Check the error log for details on why theoperation failed.



ANS5250E An unexpected error was encountered.TSM function name : function-nameTSM function : function-descTSM return code : TSM-rcTSM file : file-name (line-number)

Explanation: None.



ANS5251E The snapshot provider is not availablefor this operation.

Explanation: TSM was not able to take a snapshotbecause the snapshot provider is not available.


User response: If you are attempting an operationusing the Microsoft Volume Shadow Copy service makesure that Volume Shadow Copy service is installed onthe system and also ensure that the TSM snapshotplugin "pivss.dll" is present.

ANS5252E TSM attempted to execute a systemcommand which failed.command : commandrc : rc

Explanation: TSM needed to execute a systemcommand in conjunction with a snapshot operation.



ANS5253W The system could not create VolumeShadow Copy Services staging directory'dir'.

Explanation: The system was unable to create auser-specified location for the Volume Shadow CopyServices staging area. The default staging area on thesystem drive will be used instead.


User response: Check the option to specify the staging

area for Volume Shadow Copy Services operations andspecify a valid location.

ANS5254E The Volume Shadow Copy Servicessnapshot plugin 'pivss.dll' was notfound.

Explanation: The system cannot find the VSS snapshotplugin 'pivss.dll' in any of the plugin locations.


User response: Check the TSM installation to ensurethe plugin was installed correctly.

ANS5255E Unable to copy local file 'local-file' toremote location 'remote-file'.

Explanation: An attempt to transfer a file to a remotesystem failed..


User response: Ensure that the directory path on theremote system exists and that the TSM application hasthe proper authority to write to that location.

ANS5257E The volume 'volume' does not supportthe requested VSS operation.

Explanation: The volume does not support therequested VSS operation. Some reasons for this errorinclude the following conditions:

v For off-load backup requests, a hardware providercannot be found

v For off-load backup requests, the provider does notsupport transportable media

v For local backup requests, the provider does notsupport persistent snapshots

v For backup requests of Hyper-V virtual machinesthat are located on the volume with a Cluster SharedVolume File System and theVSSUSESYSTEMPROVIDER option is set to YES


User response: Try the backup again, and use asupported backup destination. If you are backing upHyper-V VMs and the VSSUSESYSTEMPROVIDERoption is set to YES, try the operation again, with theVSSUSESYSTEMPROVIDER option set to NO.

ANS5258E Microsoft volume shadow copysnapshot initialization failed.

Explanation: IBM Tivoli Storage Manager encounteredan error while initializing the Microsoft VolumeShadow Copy Service for backup or restore. The IBMTivoli Storage Manager error log and Windows eventlog can contain additional information about this error.

System action: IBM Tivoli Storage Manager stops theoperation.



User response: Try the operation again. If the errorpersists, review the IBM Tivoli Storage Manager errorlog and Windows event log for information related tothis error. Use the Windows command VSSADMINLIST WRITERS to determine the status of the VolumeShadow Copy service. Reboot the machine to clear thevolume shadow copy error state. If the system is aDomain Controller and the Active Directory service isstopped, restart the Active Directory service.

ANS5259W Failed to update volume 'volume' forread-write access used for 'volume'.

Explanation: Changing the volume to read-writeaccess requires exclusive access to the volume. If thevolume is opened by any application, this operationwill fail.


User response: Close all the applications using thevolumes and use operating system's interface to mountfailed volume for read-write access.

ANS5260W Restore object 'volume' has volume eithersource 'volume' or target 'volume' volumethat has already been selected forrestore from a different snapshotvolumes. It will be restore usingfile-level copy.

Explanation: This error can occur when multipleobjects are selected for snapshot restore and have dataoverlapping on the volumes and were selected forrestore from different backup versions. Snapshot restorecan only be performed from one local backup.

System action: The restore object identified in themessage will be restored using the file-level copy aftersnapshot restore is completed.

User response: Retry the restore of identified objectseparately for faster restore using snapshot.

ANS5261W An attempt to create a snapshot hasfailed.Another attempt will be made to createthe snapshot in number seconds.

Explanation: An attempt to create a snapshot hasfailed with a retryable error. The program will wait fora short time and retry the operation.


User response: Check the IBM Tivoli Storage Managererror logs for additional information.

ANS5262I Snapshot restore will failover tofile-level copy from snapshot volume.

Explanation: Snapshot restore is not possible due toan error at this time. TSMwill automatically fails over

to other restore method to complete the restoreoperation.


User response: Check TSM error log for moreinformation from messages preceding this one toidentify the error condition.

ANS5263E Snapshot module for 'snapshot provider'failed with error 'error msg'.

Explanation: The snapshot module for identifiedsnapshot provider failed to perform the operation andreturned with the identified error.

System action: Restore may automatically failover toalternate restore method 'file-level copy from snapshotvolume' if possible. Otherwise, processing stops.

User response: Check TSM error log for moreinformation from messages preceding this one. Usesnapshot provider interface to identify and correct theproblem.

ANS5264W No snapshot plugin found for 'snapshotprovider' snapshot provider.

Explanation: The snapshot restore requires a pluginfor the specified snapshot provider type. The pluginmust be installed under TSM directory.

System action: Restore will failover to alternaterestore method of 'file-level copy from snapshotvolume'.

User response: Contact your TSM administrator toobtain and install the required plugin module.

ANS5265W Snapshot restore has already beeninitialized using 'snapshot provider'provider module. Another module for'snapshot provider' provider can not beloaded at the same time for restore of'object name'.

Explanation: This error occurs when restoringmultiple LOCAL backup objects that were createdusing different snapshot providers. Snapshot restorecan only be done using one snapshot interface.

System action: Restore will failover to file-level copyrestore from snapshot volume.

User response: If snapshot restore is desired for theobject identified in the message, restore it using aseparate command.

ANS5266E File-level copy restore of 'object name'failed.

Explanation: Data files could not be copied from thelocal backup to their destination, causing restore to fail.

System action: Processing continues to another object,



if multiple objects are selected for restore.

User response: Check TSM error log for moreinformation from messages preceding this one.

ANS5267E Disk Mapper module failed for theoperation.

Explanation: An underlying TSM operation has failedto perform the operation due to system error.


User response: Check TSM error log for moreinformation from messages preceding this one toidentify cause of the failure. Contact TSM administratorfor more information.

ANS5268W The Microsoft Volume Shadow CopyServices writer 'name' current state (state)is not valid for the current operation.

Explanation: None.

System action: The system will retry the operationautomatically after thirty seconds up to three times toallow the writer to return to the proper state. If afterthree attempts the writer is still in the incorrect state,the operation will fail.

User response: Determine if there are other VolumeShadow Copy Services operations that are occurringconcurrently with the current operation.

ANS5269E The Microsoft Volume Shadow CopyServices writer 'name' current state (state)is not valid for the current operation orcannot be determined. The last errorreported is 'error'.

Explanation: None.


User response: Check the Microsoft event log todetermine if there are any problems with the writer.

ANS5270E A VSS restore request with timestamp'time1' conflicts with a restore requestwith timestamp 'time2'

Explanation: A VSS restore request was issued whichrequires restoring multiple components which reside inVSS backup documents with different backuptimestamps. For example, a user backs up Exchangestorage group STG1 on Monday and Exchange storagegroup STG2 on Tuesday. On Wednesday, the user triesto restore STG1 and STG2.


User response: Resubmit the restore request asseparate requests for each component. For example, ifyou receive this error trying to restore Exchangestorage groups STG1 and STG2, resubmit a restore

request for storage group STG1 and a separate restorerequest for storage group STG2.

ANS5271E A Microsoft Volume Shadow CopyServices writer is in an invalid statebefore snapshot initialization.

Explanation: None.


User response: See the IBM Tivoli Storage Managererror logs for additional information.

One of the VSS writers is in an invalid or unexpectedstate. Try the command "vssadmin list writers" andcheck the state of VSS writers. Writers must be inSTABLE state before IBM Tivoli Storage Manager cancontinue with VSS operations. Some of the writers canrecover automatically from minor errors. In most cases,restarting a writer solves the problem. The easiest wayto restart writers is to restart the operating system. It ispossible to restart the specific service that implements aVSS writer, but it is difficult to determine which serviceto restart.

ANS5272E A Microsoft Volume Shadow CopyServices writer is in an invalid stateafter snapshot initialization.

Explanation: None.


User response: See the TSM error log for additionalinformation.

ANS5273E A Microsoft Volume Shadow CopyServices writer is in an invalid stateafter taking a snapshot.

Explanation: None.



ANS5274E A Microsoft Volume Shadow CopyServices writer is in an invalid stateafter backup completion.

Explanation: None.



ANS5275E A Microsoft Volume Shadow CopyServices writer is in an invalid statebefore restore initialization.

Explanation: None.





ANS5276E A Microsoft Volume Shadow CopyServices writer is in an invalid stateafter preparing for a restore operation.

Explanation: None.



ANS5277E A Microsoft Volume Shadow CopyServices writer is in an invalid stateafter restore termination.

Explanation: None.



ANS5279E Error processing 'filename': file notfound.

Explanation: The file being processed for backup,archive, or migrate, no longer exists on the client.Another process deleted the file before it was backedup, archived, or migrated by IBM Tivoli StorageManager.



ANS5280E Object enumeration from a file set orfile list failed.

Explanation: For more information, see the IBM TivoliStorage Manager client error log. This message isalways accompanied by error log message ANS5279E ifthe object was not found or by ANS5250E for othercauses, for example, access was denied. These messagesidentify the object in question.


User response: See the user response based on othermessages in the client error log.

ANS5281E A remote backup failure has occurred.remote node name : noderemote address : addressmulti-node name : multi-nodeerror message : msg return code : rc

Explanation: For more information, see the IBM TivoliStorage Manager client error log on the remote system.



ANS5282E A remote backup failure has occurred.

Explanation: For more information, see the IBM TivoliStorage Manager client error log.



ANS5283E The operation was unsuccessful.

Explanation: None.



ANS5284I TSM has detected an incomplete setup!The client options file 'dsm.opt' was notfound, while the system options file'file-path' exists!The wizard will guide you through theconfiguration process of the initial basicTSM client options files replacing yourcurrent option file. Would you like tocontinue?

Explanation: TSM has detected an incomplete setup.The user options file, dsm.opt, was not found.Additionally, a system options file, dsm.sys, was found.To complete the configuration the configuration wizardwill create dsm.opt and replace dsm.sys with minimalsettings.

System action: TSM may stop

User response: If the current version of dsm.sys isneeded, rename the file and restart TSM. If the currentversion is not needed, select yes and allow TSM toreplace the file.

ANS5285E The Microsoft Volume Shadow CopyServices (VSS) backup XML documentis not valid for restore. For moreinformation, see the TSM client errorlog.

Explanation: Microsoft has released a Volume ShadowCopy Services (VSS) update in the following operatingsystem versions:

v Windows 2003 update rollup package KB940349

v Windows Vista Service Pack 1

This new VSS fix packages causes VSS to generates.xml control files in a format which is not compatiblewith the earlier versions of VSS. This error can occurwhen a system state restore is being performed from abase operating system level which does not have the



VSS fixes applied and the system state backup fileswere created by an operating system level that didhave the VSS fixes applied.


User response: The restore procedure for Windowssystem state requires that the operating system versionand service pack level used to initiate the restore be atthe same operating system and service pack level usedto create the system state backup. In addition note thefollowing:

v On Windows 2003 systems you must also apply theVSS rollup package KB940349 prior to performingthe Ssystem state restore.

v On Windows Vista you must apply the same servicepack that was installed at the time of backup prior toperforming the system state restore.

ANS5286I The VSS Instant Restore operation wassuccessful but some existing VSSsnapshots have been deleted by the VSSprovider.

Explanation: A successful VSS Instant Restoreoperation was performed for snapshot volumes thatwere in a dependent relationship. In order for therestore process to succeed, it was necessary to removethe snapshot volumes causing the dependency. Thosesnapshot volumes typically represent newer snapshotbackups. This forced TSM to remove the backups thatincluded the deleted snapshots. This situation is typicalwhen using SAN Volume Controller (SVC)space-efficient volumes that have multiple snapshots.



ANS5287W VSS restore operation will be performedusing VSS Fast Restore because the XIVVSS Hardware Provider is at level 2.2.2.

Explanation: XIV VSS Hardware Provider 2.2.2 hasissues with VSS Instant Restore. Please update the XIVVSS Hardware Provider to version 2.2.3, or later.


User response: Update XIV VSS Hardware Provider toversion 2.2.3, or later.

ANS5288W Test flag DISCARDZEROFILEDATAenabled. Discarding data for zero lengthobject file-name

Explanation: During the restore of a zero length file ordirectory, data was decompressed. This data could beExtended Attributes, Alternate Streams, or ACL data.By default this data is restored. Because theDISCARDZEROFILEDATA test flag is set the data isdiscarded.

System action: The data is discarded and processingcontinues

User response: Note the file or directory name in thismessage and determine if the discarded data needs tobe reset through some other means.

ANS5296I The virtual machine 'vm-name' containsone or more virtual disks that are oftype Thick Eager Zero. Creating disks ofthis type can take a long time. Thisrestore operation might time out beforethe disks are ready.

Explanation: Restoring a VM that has Thick EagerZero virtual disks can take a long time to completebecause the disks are zero-filled to obscure anyprevious content. The time that is required to provisiona Thick Eager Zero disk depends on processing loadson the VMware resources (vCenter and datastores).

System action: None

User response: Reattempt the restore operation at atime when the processing load is light on thedatacenter and vCenter resources

ANS5298E A Flashcopy background copy is inprogress between source volume: andtarget volume: .

Explanation: A Flashcopy background copy from aprevious operation is not complete for the given sourceand target volumes.

System action: Command will fail.

User response: Please wait until the background copyis complete and retry the command.

ANS5299E A Flashcopy association exists betweensource volume: and a different targetvolume: .

Explanation: A Flashcopy association exists betweenthe source volume and a target other than thedesignated target volume.

System action: Restore command will fail.

User response: Please withdraw the Flashcopyassociation between the source volume and the targetvolume and retry the restore command.

ANS5300E Error detected in specified file list 'filelist name' during processing of line linenumber:found an invalid external object ID / inodenumber / inode generation number / restoreorder number / alias entry: 'invalid entry'.Invalid line: 'invalid entry'

Explanation: File list parsing failed because of aninvalid entry.



System action: The operation aborted because of anfile list error.

User response: Correct the invalid file list entry andrestart the operation.

ANS5301E Error detected in specified file list 'filelist name' during processing of line linenumber:found an invalid ordering of externalobject IDs.ext. object ID of previous file: previousexternal object IDext. object ID of current file: currentexternal object ID

Explanation: File list parsing failed because of aninvalid ordering of the external object IDs.

System action: The operation aborted because of anfile list error.

User response: Correct the invalid file list orderingand restart the operation.

ANS5302E File list stream error to file 'file list name'detected during processing of line linenumber.

Explanation: File list processing failed because of anstream error.

System action: The operation aborted because of anfile list stream error.

User response: Check the specified file list and restartthe operation.

ANS5303I ***** date Processed count TSM serverand count file list objects *****

Explanation: TSM has processed the specified numberof TSM server and file list objects.



ANS5304E program-name: synchronous file deletionfailed for external object ID: externalobject ID.

Explanation: The HSM client could not delete anobject on the TSM Server.

System action: The current file is skipped forsynchronous file deletion and the process will continue.

User response: Check the TSM server log file.

ANS5307E The session is rejected. The server doesnot allow a signon of a client that is notenabled for space-managementretention-protection.

Explanation: The client cannot establish a connectionto the server because the server is enabled forspace-management retention-protection and the client isnot.



ANS5821E Cannot connect to Active Directory.

Explanation: TSM could not connect to ActiveDirectory. The Active Directory is either not running oryou don't have enough permissions to use it.


User response: Make sure your system is set up asActive Directory controller and the the service is active.Make sure you are logged in as a user with sufficientrights to administer the Active Directory.

ANS5822E No Active Directory objects matchquery.

Explanation: A search has been performed in ActiveDirectory; however, no objects matching the query werefound.


User response: Make sure you specify a validdistinguished name of Active Directory object or acontainer, or a valid wildcarded name, and that youhave sufficient rights to administer the Active Directory.

ANS5823W Object exists, skipping

Explanation: The client tried to restore the specifiedobject, but the object already existed in the targetrestore location and the user chose not to replace theexisting object.

System action: The object is skipped, a message islogged in dsmerror.log, and restore processingcontinues with the next object.

User response: The object was skipped because eitherREPLACE NO was in effect, causing all existing objectsto be skipped, or REPLACE PROMPT was in effect,and when prompted, the user chose to skip this object.No additional action is necessary if the decision to skipthe object was deliberate. Otherwise the operation canbe retried using either REPLACE ALL (automaticallyreplace existing object) or REPLACE PROMPT (promptthe user whether to replace the object).



ANS5824E Invalid Active Directory searchspecification.

Explanation: The search specification for ActiveDirectory objects is not valid.


User response: Refer to the documentation forsupported Active Directory syntax.

ANS5825E Reanimate 'tombstone-name' to'distinguished-name' failed. See the errorlog for more details.

Explanation: An attempt to reanimate ActiveDirectory tombstone object has been performed, but anerror occurred.

System action: Processing continues to process allother tombstone objects per user's request.


ANS5826E Restoring to a read-only domaincontroller is not allowed.

Explanation: An attempt to restore to a read-onlydomain controller.



ANS5827E A backup copy of the Active Directorydatabase was not found.

Explanation: An attempt to restore Active Directoryobjects from a database that was not backed up.


User response: Verify the Active Directory was backedup with system state.

ANS5828E A system state file space was not foundon the server. Active Directory functionscan not be executed.

Explanation: An attempt to restore the ActiveDirectory database from a system state backup thatdoes not exist.


User response: Verify that system state was backed upor back up the system state then retry the command.

ANS5829E A system state backup on the specifieddate was not found. Active Directoryfunctions can not be executed.

Explanation: An attempt to restore the ActiveDirectory database from a system state backup thatdoes not exist.


User response: Verify that system state was backed upon the specified date or specify a new date.

ANS5830E Restore of object 'tombstone-name' is notallowed by Active Directory.

Explanation: Object of certain types cannot berestored. This is a system limitation.

System action: Processing continues to process allother objects per user's request.


ANS5831E Restore for this object is not allowed byActive Directory.

Explanation: Object of certain types cannot be restord.This is a system limitation.



ANS5832E Reanimate tombstone object failed. Seethe error log for more details.

Explanation: An attempt to reanimate ActiveDirectory tombstone object has been performed, but anerror occurred.



ANS5833E This system is a Domain Controller butthe Active Directory service is stopped.You can not perform the operationunless the Active Directory service isrunning.

Explanation: The Active Directory service must berunning when you back up or restore the system stateor operate on Active Directory objects. When the ActiveDirectory service is running, it can be in online state orin offline state. When you query or restore ActiveDirectory objects, or back up the system state, theActive Directory service must be online. When yourestore the system state, the Active Directory servicemust be offline (but not stopped).


User response: If you are querying or a restoring theActive Directory objects or backing up the system state,put the Active Directory service in online state bystarting the Active Directory service. If you arerestoring the system state, put the Active Directoryservice in offline state by rebooting to the ActiveDirectory Restore Mode. When the Active Directoryservice is in the appropriate state, retry the operation.



ANS5834E Unexpected LDAP error occurred. Seethe error log for more details.

Explanation: An unexpected error occurred duringActive Directory tombstone reanimation.


User response: Check the error log for detailedinformation on the LDAP error.

ANS5835E An LDAP operation returned return code:'error string'

Explanation: An unexpected error occurred duringActive Directory tombstone reanimation.



ANS5836W One or more attributes were notrestored. See the error log.

Explanation: During processing of an Active Directoryobject, one or more object attributes could not berestored.

System action: Processing continues to process allother Active Directory objects per user's request.

User response: Check the error log for detailedinformation on which attribute(s) could not be restored.

ANS5837W 'object name': attribute 'attribute name'could not be restored.

Explanation: The listed attribute could not be restoredduring processing on the Active Directory object.

System action: Processing continues to process allother Active Directory objects per user's request.


ANS5838E The utility dsamain.exe does not existon the system. You cannot perform theoperation unless Tivoli Storage Managercan launch this utility.

Explanation: You attempted to launch dsamain.exe,but the utility does not exist.


User response: Verify that the dsamain.exe utilityexists in the Windows system32 directory. When youcan run the utility independently of Tivoli StorageManager, retry the operation.

ANS5839E The Active Directory object specificationis not allowed.

Explanation: You attempted to restore the domainobject (starting with "DC="), or you attempted torestore all objects ("name=*"), or you did not specifyanything.


User response: Modify the specification then retry theoperation.

ANS5840E The current user is not a member of theAdministrators group, and cannotperform this function.

Explanation: You must be a member of theAdministrators group to perform the Active Directoryobjects function.


User response: Log on with a user who is a memberof the Administrators group or add this user to theAdministrators group then retry the operation.

ANS5841E Active Directory database could not beopened.

Explanation: An error occurred while opening therestored Active Directory database.


User response: Make sure ntdsutil.exe utility islocated in the same directory with TSM clientexecutables. If it doesn't exist, reinstall the client. Verifythat the dsamain.exe utility exists in the Windowssystem32 directory. When you can run the utilityindependently of Tivoli Storage Manager, retry theoperation. If the problem persists, contact the support.

ANS5842E 'tombstone-name': object class violation.

Explanation: Object class error violation occurredduring tombstone reanimation. This can happen if theActive Directory schema was modified and is no longercompatible with the tombstone.


User response: Recreate the failing object manually orrestore it from a backup.

ANS5843E Object class violation.

Explanation: Object class error violation occurredduring tombstone reanimation. This can happen if theActive Directory schema was modified and is no longercompatible with the tombstone.




User response: Recreate the failing object manually orrestore it from a backup.

ANS5844E Unable to update password.

Explanation: An error occurred during the passwordupdate attempt.


User response: Try to update the password again.

ANS5845E Unable to update password because themaximum number of update attemptshas been exceeded.

Explanation: This message is issued after making 3unsuccessful attempts to update the password. Theoriginal password for the node was entered incorrectly;the new password does not meet the length or validcharacter requirements for our passwords; or there wasa mismatch between the first and second times the newpassword was entered.

System action: The password is not updated.

User response:

v Make sure the original password is entered correctly.Contact your TSM administrator for furtherassistance if you do not know the original password.

v Make sure the new password meets the passwordlength and character requirements.

v You will be prompted to enter the new passwordtwo times, so make sure it is entered correctly bothtimes.

ANS5876I SET EVENT Activate Retentioncompleted

Explanation: The Data Retention ACTIVATEtransaction has completed.

System action: TSM activated the objects that wereselected.


ANS5877I SET EVENT Hold completed

Explanation: The Data Retention HOLD transactionhas completed.

System action: TSM held the objects that wereselected.


ANS5878I SET EVENT Release completed

Explanation: The Data Retention RELEASE transactionhas completed.

System action: TSM released the objects that wereselected.


ANS6586E Recovery Agent operation failed.

Explanation: The Recovery Agent operation on aVMVSS snapshot failed.


User response: Check the Recovery Agent logs anderror messages, resolve the problem, and try theoperation again.

ANS6587W VMVSS backup failed to back up theExchange mailbox history from virtualmachine 'VM-Name'.

Explanation: An error occurred when a data movertried to back up the Exchange mailbox history from avirtual machine. The current version of Data Protectionfor Exchange might not support uploading mailboxhistory at the same time as a virtual machine backup.The error code indicates the reason for the failure.

System action: Processing continues without backingup the mailbox history information.

User response: Try to back up mailbox history onguest vm by using Data Protection for Exchangecommand 'tdpexcc.exe backup * full/UpdateMailboxInfoOnly'. Upgrade Data Protection forExchange if the current product level does not supportmailbox history backup command. Use traceflagsVMTSMVSS in data mover dsm.opt file to furtherdiagnose the problem.

ANS7421W The archive attribute for file filenamecannot be reset. The return code fromWindows API functionSetFileAttributes() is rc.

Explanation: The client was unable to reset thearchive attribute for the file indicated in the message.This error is due to an error received from theWindows API function SetFileAttributes().


User response: Try the operation again. If the problempersists, it may be indicative of a problem with the file.Contact your system administrator or TSMadministrator for further assistance.

ANS7422E Unsupported action 'action' in schedule'schedule name'.

Explanation: The scheduled action is unknown to thecurrent version of the IBM Tivoli Storage Managerclient and cannot be performed by means of aschedule. The most likely cause is that the scheduledaction requires a later version of the backup-archive



client.The unsupported action is displayed as a numberbecause the text description is not available. Scheduledactions and their corresponding action number can befound by searching for this message on the IBM TivoliStorage Manager support site.

System action: The scheduled action is not performedor queried.

User response: Search the IBM Tivoli Storage Managersupport site for this message to find information aboutscheduled actions, their corresponding action numbersand the client version at which the action is supported.Then upgrade your IBM Tivoli Storage Manager clientto a version that supports running this action as ascheduled event. Until the client is upgraded, you canrun the action manually if your version of the clientsupports it.

ANS7423E Use Set Access backup <vmname>-TYPE=VM for VMware backup filespaces. Use of the long form fs-name isnot allowed.

Explanation: You have chosen to set access using thelong-form VM file space name. This name format is notplatform independent and requires special processing.Use the -TYPE=VM option and supply only the VMname.

System action: The set access command is notprocessed.

User response: Enter the set access command usingthe -TYPE=VM option and the short form of the VMfile space name which is simply the VM name.

ANS7500W Object 'object-name' could not be boundto management class 'mgmt-specified'specified in an 'option' statement.

Explanation: The management class specified in aninclude statement was not valid. If the includestatement is an "INCLUDE.SIZE" statement thewarning message will be issued if an appropriatecopygroup is defined for the management class. Forexample, this warning will be issued on a backupoperation if no backup copygroup is defined for themanagement class or this message will be issued on anarchive operation if no archive copygroup is definedfor the management class.

System action: The management class on the includestatement is ignored and processing continues.

User response: Contact the TSM administrator tocorrect the appropriate copygroup definition on theTSM Server.

ANS7501E An invalid host address was received.Host address is too long.

Explanation: An invalid host parameter was found inthe HTTP Request. The parameter is too long. Themaximum length for a host address is 64 characters.

System action: TSM returns HTTP error code 400 BadRequest.

User response: Use a host machine with avalid/shorter host address.

ANS7502E An invalid filename was received.Filename is too long.

Explanation: A filename passed to the dsmcad serviceis too long and thus invalid.

System action: TSM returns HTTP error code 400 BadRequest.

User response: Retry connecting to dsmcad but use avalid/shorter filename.

ANS7507W The node name entry is invalid. Pleasetry again.

Explanation: An invalid entry is entered on the NodeName field.

System action: TSM prompts you to enter a validnode name.

User response: Enter a valid node name or see yoursystem administrator for the correct syntax.

ANS7510E A NAS node cannot be used for thisoperation.

Explanation: NAS nodes cannot be used foroperations like Access Another Node.

System action: TSM prompts you to enter a validnode name.

User response: Enter a valid, non-NAS, TSM nodename.

ANS7524E SSL is required.

Explanation: SSL is required to protect the clientpassword during authentication.


User response: Enable SSL communication or setSSLREQUIRED to NO.

ANS7525E SSL is required by server.

Explanation: SSL is required to protect the clientpassword during authentication.




User response: Enable SSL communication or contactyour TSM server administrator.

ANS7526E The SNAPSHOTROOT option is notvalid with either of thefollowing options: -GROUPNAME and-VIRTUALFSNAME.

Explanation: The SNAPSHOTROOT option isincompatible with the -GROUPNAME and-VIRTUALFSNAME options and cannot be used witheither one of those options.


User response: For information about backup-archiveclient processing options, see IBM Tivoli StorageManager Backup-archive Clients Installation and User'sGuide.

ANS7527E The (-SNAPSHOTROOT) option is notvalid in conjunction with num-specs filespecifications.

Explanation: The (-SNAPSHOTROOT) option must beused in conjunction with only one file specification. Itcannot be used with zero file specification (e.g., anINCREMENTAL command with no file specifications)or with more than one file specification.



ANS7529E The specified SNAPSHOTROOT'obj-name' is not valid for the BACKUPIMAGE command.

Explanation: When you use the (-SNAPSHOTROOT)option with the BACKUP IMAGE command,SNAPSHOTROOT must specify the device name of thelogical volume containing the snapshot for the backup.An example is /dev/fslv01 (on Unix) or\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy1 (on Windows).

With BACKUP IMAGE, SNAPSHOTROOT cannot beused unless SNAPSHOTPROVIDERIMAGE has one ofthe following values in effect:

v VSS

v JFS2


User response: For the correct use of the(-SNAPSHOTROOT) option, see the appropriateBackup-Archive Client Installation and User's Guide bookfor your operating system.

ANS7531E The (-SNAPSHOTROOT) option isinvalid when processing the NetWareNDS or Server Specific Information.

Explanation: The (-SNAPSHOTROOT) option is onlyintended with NetWare file server volumes and is notcompatible with processing the NDS or Server SpecificInformation on NetWare.



ANS7533E The specified file system 'obj-name' doesnot exist or is not local.

Explanation: When you use the (-SNAPSHOTROOT)option, the target and source file systems must be valid,local file systems. The file systems cannot be non-local,such as a remote NetWare drive, a remote Windowsdrive, or an NFS mount. The (-SNAPSHOTROOT)option is valid for local operations only.


User response: For the correct use of the(-SNAPSHOTROOT) option, see the appropriateBackup-Archive Client Installation and User's Guide bookfor your operating system.

ANS7534W Initialization functions cannot open/dev/tty special file. errno = errno-value,error message

Explanation: Special file /dev/tty, required bycommand line internal editor could not be openedduring initialization. The system set the error codeerrno-value.

System action: Processing continues as if EDITORoption was set to NO.

User response: Check your terminal settings.

ANS7535W Command line internal editor can notbe initialized.

Explanation: EDITOR option is set to YES in theoptions file, but command line internal editor can notbe started.

System action: Processing continues as if EDITORoption was set to NO

User response: Check previous messages to determinethe reason why the internal editor could not be started.



ANS7543E Error: Scout is not available for objectquery. Either scout is not running or theinitial file system scan has not finished.

Explanation: The scout daemon must be running forthe reconcile process to do a query for all migratedfiles. If the scout daemon is not running or the initialfile system scan has not finished you cannot run thereconcile tool in orphan check mode.


User response: Ensure that the scout daemon isrunning. If the scout daemon is not running, restart itand retry the command. If the scout daemon isrunning, wait until it finishes the initial file systemscan. You can check the current status of the scoutdaemon by using the dsmscoutd scanplan command.

ANS7544E ICC routine icc-routine failed with thefollowing error: "error-string".

Explanation: There was an error within ICCcryptography library while processing the data. Forexample, this problem can occur when encrypted clientdata is corrupted, so the restore operation cannotcorrectly decrypt it. This message reports an error codeand problem description which can be used by TSMtechnical support personnel to determine the cause ofthe failure.


User response: Ensure TSM software is installedcorrectly. If needed, reinstall the software. Make sureyou use the correct encryption key password for thedata. Make sure there are no TSM server or networkproblems that may affect the transfer of data. If theproblem still exists, contact TSM technical support.

ANS7545E Unexpected error while encrypting thedata.

Explanation: There was an error while encrypting thedata. See the error log for more information.

System action: The object is not backed up.

User response: Ensure TSM software is installedcorrectly. If needed, reinstall the software. Retry theoperation. If the problem still exists, contact TSMtechnical support.

ANS7546E Unexpected error while decrypting thedata.

Explanation: There was an error while decrypting thedata. See the error log for more information. This canhappen if the encrypted data has been corrupted whilein storage, during the network transfer, or both.

System action: The object is not restored.

User response: Ensure TSM software is installed

correctly. If needed, reinstall the software. Make surethere are no TSM server or network problems that mayaffect the transfer of data. Retry the operation. If theproblem still exists, contact TSM technical support.

ANS7547E Unexpected error while digesting thedata.

Explanation: There was an error while digesting thedata. See the error log for more information.


User response: Ensure TSM software is installedcorrectly. If needed, reinstall the software. Retry theoperation. If the problem still exists, contact TSMtechnical support.

ANS7550E The absolute option requires using theCreateNewBase=yes option whenperforming a snapshot differentialbackup.

Explanation: The absolute option specified does nothave any effect when performing a snapshotdifferential backup.


User response: Try to use the CreateNewBase=yesoption when performing a snapshot differential backup.

ANS7552I timestamp ***** Processed count files*****

Explanation: IBM Tivoli Storage Manager hasprocessed the specified number of files.



ANS7553W Disabled demand migration (ENOSPC)on file system file-system-name because ofhigh threshold, low threshold, andpmpercentage settings.

Explanation: The settings of high threshold = 100, lowthreshold = 100, and pmpercentage = 0 are reserved todisable demand migration and automigration. Used forGPFS driven migration.



ANS7554E provider option is required ifHSMBACKENDMODE is set toTSMFREE.

Explanation: You need to specify provider option forevery operation with dsmmigrate.




User response: Specify the provider option value forthe operation.

ANS7557E invalid provider.

Explanation: You need to specify a valid provider forevery operation with dsmmigrate.


User response: Specify a valid provider option valuefor the operation.

ANS7558E target option is required ifHSMBACKENDMODE is set toTSMFREE.

Explanation: You need to specify target option forevery operation with dsmmigrate.


User response: Specify the target option value for theoperation.

ANS7559E The absolute option requires specifyingthe NoJournal option when performinga Journal Based Backup for backing upfs .

Explanation: The absolute option specified does nothave any effect when performing journal basedbackups.

System action: Incremental backup is performed.

User response: Verify that the file spaces specified arenot associated with journal based backup. If the-nojournal option is also specified, then this messagewill not appear.

ANS7566E Unable to load external library: reason

Explanation: There is no valid library in hsm/bindirectory.


User response: Copy a valid external library tohsm/bin directory.

ANS7567E program-name:External recall failed!Reason:

Explanation: There is no valid library in hsm/bindirectory.


User response: Copy a valid external library tohsm/bin directory.

ANS7641I The user does not have administrativecredentials to perform a full systemstate backup.

Explanation: The user account used to perform systemstate backup including ASR Writer data must be amember of the Administrators group.

System action: System state backup skips ASR Writerdata.

User response: Log on with a user who is a memberof the Administrators group or add this user to theAdministrators group. Then try the system statebackup again.

ANS7642E An error occurred creating the registrydirectory structure.

Explanation: An error occurred while creating thedirectory structure to save or replace a registry key.

System action: Registry function fails.

User response: Ensure that the user account that isrunning the backup of the registry has the properauthority. If the user account has the proper authority,you might need to restart the machine. There might beoperations that are pending which have a file or files inthe registry directory structure locked.

ANS7643E The deployment manager detected thatthe client is being upgraded to anincorrect architecture - from 32 bit to 64bit or from 64 bit to 32 bit.

Explanation: When upgrading clients to releases lowerthan 6.3, deployment manager allows upgrades to likearchitecture only.


User response: Uninstall the client and install theBackup-Archive client at the correct bitness level.

ANS7650E The user does not have sufficientprivileges to execute IBM Tivoli StorageManager.

Explanation: The user account used to execute IBMTivoli Storage Manager must have the "Back up filesand directories" and the "Restore files and directories"security settings assigned.


User response: Assign the "Back up files anddirectories" and the "Restore files and directories"security settings to the account using the WindowsLocal Security Settings tool or use a different user-id toexecute IBM Tivoli Storage Manager.



ANS7660E An error occurred replacing one or moreregistry keys.

Explanation: The registry key or keys being replacedare exclusively held by another process. The registrykeys were previously restored but the system was notrestarted.


User response: Restart the system and try the restoreoperation again.

ANS7709E Restore operation failed. Not all fileswere restored.

Explanation: Restore operation failed due to an error.

System action: Operation completed.

User response: Check the error log for more details.

ANS7899E The client referenced a deduplicatedextent that does not exist on the TSMserver

Explanation: The deduplicated extent has beendeleted from the server during the backup or archiveoperation. If you are using deduplication cache, itmight be out of synch with the TSM server.


User response: Retry the operation. If the problempersists, turn off deduplication and retry the operation.

ANS7900W Deduplication cache has been resetbecause it is not synchronized with theTSM server

Explanation: The deduplication cache containsdeduplicated extent entries that do not exist on theTSM server. This occurs when the extents are deletedfrom the TSM server after they were recorded in thededuplication cache.

System action: The deduplication cache is reset, andall cache entries are removed. The processing continues.

User response: None

ANS7901W Client deduplication and option-name aremutually exclusive.

Explanation: The following features cannot be usedwith deduplication: lan-free, subfile, NAS,useTsmBuffers.

System action: Client deduplication is disabled.

User response: Review the configuration. Do notconfigure deduplication with the lan-free, subfile, NAS,or useTsmBuffers features.

ANS7902I Client deduplication cache is full. Cacheis reset.

Explanation: The number of entries cached in theclient deduplication cache has exceeded the configuredsize for the cache.

System action: The deduplication feature is designedso that this happens periodically.The cache is reset to no entries.

User response: You can reconfigure the clientdeduplication cache size to a larger value to reduce thefrequency of resets.

ANS7903W Client deduplication cache is locked byanother process.

Explanation: Another process is using the clientdeduplication cache.Only one process may use it at a time.

System action: This process does not use the clientdeduplication cache.The server deduplication is not changed.

User response: You can serialize processes using theclient deduplication cache. Or you can reconfigure thecurrent process to use a different cache path to avoidcontention.

ANS7904E Client deduplication and lan-free orsubfile backup are mutually exclusive.

Explanation: Client deduplication and lan-free orsubfile are mutually exclusive.

System action: Client deduplication is disabled.

User response: Review the configuration. Do notconfigure deduplication with the lan-free or subfilefeature.

ANS7906W The current storage pool either ran outof space or the current object exceededthe maxsize configuration parameter forthe storage pool, data will be stored intothe next pool - deduplication isdisabled.

Explanation: The current storage pool on the TSMserver is either out of space or the current objectexceeded the maxsize configuration parameter for thestorage pool . Data will be stored in the next storagepool. Deduplication is disabled and the transaction isbeing resent.

System action: Deduplication is disabled to allow thebackup to complete.

User response: Contact your system administrator toadd volumes to the current storage pool.



ANS7907W Connection to repository repos-namefailed. Retrying with repos2-name.

Explanation: Unable to connect to the Fastback DRHub repository. Retry using Fastback server repository.

System action: Retry operation.

User response: Specify a vaild repository.

ANS7908E Unable to mount FastBack snapshotpolicy 'Policy' client 'Client' volume'Volume'. Reason: reason

Explanation: TSM Mount failed.

System action: TSM cannot continue processing.

User response: Check the Recovery Agent logs forinformation about why the mount operation failed tocomplete.

ANS7912E FastBackMount or FastBackShell is notinstalled.

Explanation: Failure initializing FastBack environment.FastBackShell or FastBackMount are not installed or arenot located in the FastBack install directory.

System action: The FastBack operation cannotcontinue.

User response: Reinstall the software. TheFastBackShell and FastBackMount must be installed onthe dedicated proxy computer.

ANS7913E The given branch was not found in theDR Hub repository.

Explanation: The parameter to the required fbbranchoption is incorrect.

System action: The operation cannot continue.

User response: Correct the parameter given for thefbbranch option.

ANS7914E Incremental backup of FastBack client'vmname' failed with RC rc

Explanation: The archive or incremental backup ofFastBack client volumes failed.

System action: The archive or backup of FastBackclient finished with failures. The next FastBack clientwill be processed. The reason for the failure is writtento the local client error log.


ANS7915E Failure mounting FastBack client'vmname' with FastBack command. RC=rc

Explanation: The FastBackMount command failed tomount a FastBack volume.

System action: The archive or backup of the FastBackvolume can not continue. The next Volume in in linewill be processed. The output of the FastBackMountcommand will show the reason for the failure.

User response: Check the local client error log for thereason for the failure. Issue a FastBack command forthe FastBack volume to determine the reason for thefailure. Refer to the documentation for that message formore information.

ANS7916E Failure initializing FastBackenvironment.RC=rc

Explanation: Failure initializing FastBack environment.Can not find FastBackShell.exe command. TheFastBackShell or FastBackMount is not installed orFastBackShell.exe command is not located in theFastBack install directory.

System action: The backup can not continue. Theoutput of the FastBack command will show the reasonfor the failure.

User response: Issue a FastBack command todetermine the reason for the failure. Refer to thedocumentation for that message for more information.The FastBackShell and FastBackMount must beinstalled on the backup proxy computer.

ANS7917E No FastBack snapshots found for inputpolicy, client and volume combination.

Explanation: Failure processing fbClientName option.

System action: The backup cannot continue.

User response: Check for errors in the FBClientNameoption value. Refer to the documentation for theFBClientName option for more information.

ANS7918E Failure locating mounted volumes forFastBack client 'vmname' volumes. Failedwith RC=rc

Explanation: FastBack client volumes can not befound. Volume mount points are not available on thebackup proxy computer.

System action: The backup of the FastBack client cannot continue. The next FastBack client in the list will beprocessed. The output of the FastBackMount commandwill show the reason for the failure.

User response: Issue a fastbackshell mount addcommand for the FastBack client volume to determinethe reason for the failure. Refer to the documentationfor that message for more information.



ANS7919E Password for Host host could not beread from encrypted password file.

Explanation: Use dsmc SET PASSWORD-type=FastBack 'FastBack hostname' 'userid' 'password'to save encrypted password

System action: The backup cannot continue.

User response: Use dsmc SET PASSWORD-type=FastBack 'FastBack hostname' 'userid' 'password'to save encrypted password

ANS7936E objType objName not found in dump.

Explanation: TSM server could not find the object thatis specified in the FastBack Dump command..

System action: TSM skips the current object.

User response: Ensure that there is at least onesnapshot for this FastBack volume, client, and policy.Ensure that a correct object is specified as input.

ANS7937E No objType found in dump for inputobjType1 objType2.

Explanation: TSM server found no clients for thespecified policy. TSM server found no volumes for thespecified FastBack client.

System action: TSM skips the current object.

User response: Ensure that there is at least onesnapshot for this FastBack volume, client, and policy.Ensure that a correct object is specified as input.

ANS7938E Unable to dismount FastBack volume'volName'. RC = rc

Explanation: TSM Dismount failed.

System action:

User response:

ANS7939E Invalid FastBack volume specification.

Explanation: You must enter at least one FastBackclient with the "-fbclientname=" option before enteringa FastBack volume name.

System action:

User response: When entering a FastBack volumename, enter at least one FastBack client name using the"-fbclientname=" option.

ANS7940W SUBDIR NO is not valid in this context.SUBDIR will be forced to YES forFastBack commands.

Explanation: When using FastBack, SUBDIR is forcedto YES to ensure that the whole volume is processed.

System action: SUBDIR is forced to YES.

User response: To avoid this message, do not useSUBDIR NO with the command.

ANS7941E FastBack invalid repository name ordomain not set in password file entryfor hostname.

Explanation: TSM The FastBack repository name isinvalid or the domain has not been set in the passwordfile when specifying the REP form of the repository.

System action: TSM

User response: Issue the command dsmc set passwordserver userid:domain password -type=fastback.

ANS7942E Maximum number of FastBack objNameobjects exceeded.

Explanation: TSM The maximum number of FastBackobjects shown in the message has been exceeded.

System action: TSM

User response: Re-run the command with no morethan the maximum number of objects specified.

ANS7943E The combination of objName andobjName is invalid.

Explanation: TSM The combination of optionsspecified is invalid.

System action: TSM

User response: Re-run the command with acompatible set of options.

ANS7944W The number of FastBack clientsspecified client is greater than thenumber of FastBack clients found client.

Explanation: TSM One or more of the FastBack clientsspecified was not found. Look for message ANS7936Especifying the client name.

System action: TSM

User response: Correct the names of the clientsspecified.

ANS7945W The number of FastBack policiesspecified policy is greater than thenumber of FastBack policies foundpolicy.

Explanation: TSM One or more of the FastBackpolicies specified was not found. Look for messageANS7936E specifying the policy name.

System action: TSM

User response: Correct the names of the policiesspecified.



ANS7946E FastBack shell command timeout.SSHKeys may not be configured for nopassword.

Explanation: TSM The FastBack shell commandtimeout. SSH may not be configured properly.

System action: TSM

User response: Correct SSH configuration.

ANS7947E The root user .ssh directory was notfound. SSH is not configured properly.

Explanation: TSM SSH is not configured properly forthe root user.

System action: TSM


ANS7948E The public key for the FastBack serverwas not found. SSH public keys areconfigured properly.

Explanation: TSM The SSH public keys are notconfigured properly for the root user.

System action: TSM


ANS7949E The connection to FastBack serverfailed.

Explanation: TSM The connection to FastBack serverfailed.

System action: TSM

User response: Insure that the FastBack server on thetarget machine is runing properly.

ANS7950E The FastBack server is not installed onthe target machine.

Explanation: TSM The FastBack server is not installedon the target machine.

System action: TSM

User response: Install the FastBack server on thetarget machine or specify a different target machiner.

ANS7951E The FastBackShell on the target machinereturned with the message errormsg .

Explanation: TSM An error occurred with thecommand issued to the FastBackShell on the targetmachine.

System action: TSM

User response: Correct the options specified on thecommandr.

ANS7952E The package package required forFastBack support is not installed.

Explanation: TSM The required package is notinstalled.

System action: TSM

User response: Install and configure the requiredpackage.

ANS7953E The FastBack shell scripts returned anunexpected error error.

Explanation: TSM The FastBack shell scripts returnedan unexpected error.

System action: TSM

User response: Correct the error.

ANS7954E The SSH connection failed. The SSHdaemon may not be started orconfigured on the target machine

Explanation: TSM Ensure that the SSH daemon isconfigured correctly.

System action: TSM


ANS7955E The cygdrive-prefix is set incorrectly.

Explanation: TSM Ensure that cygdrive-prefix is set to/ in the ssh cygwin environment. The command mount-s --change-cygdrive-prefix / can be use to set the driveprefix correctly.

System action: TSM


ANS7956E Unable to execute cygwin shellcommands. The cygwin environmentmay be incorrectly

Explanation: TSM Use ssh to connect to the cygwinshell and ensure that the cygwin environment andcygdrive are configured correctly.

System action: TSM


ANS7957E Unable discover the FastBackShelllocation in the registry

Explanation: TSM Check that the FastBackShell wasinstalled on the Windows FastBack server machine.

System action: TSM




ANS8000I Server command: 'command'.

Explanation: The specified command is being sent tothe server. This message is displayed when thecommand is generated from a macro or when the clientis running in batch mode.

System action: The command is sent to the server forprocessing.


ANS8001I Return code return code value.

Explanation: The error code shown has been returnedfrom the preceding server command. This message ispreceded by a server message explaining the reason forthe error code.



ANS8002I Highest return code was return codevalue.

Explanation: At exit from the client, the highest returncode encountered during the session is displayed.

System action: This value is used as the program exitcode.


ANS8003I Process number process ID started.

Explanation: As a result of the preceding servercommand, the process whose ID is shown starts toexecute the command. The process can be monitoredusing the QUERY PROCESS command.



ANS8004W Your password will expire withindaysRemaining day(s).

Explanation: The password for this id is about toexpire.

System action: Logging on to the TSM Server will notbe prevented, however, the id will be locked out once itexpires.

User response: Change the password or contact yourTSM administrator to get the password updated.

ANS8005E Java Applet failed to load. Please ensurethat the Java Java version Plugin has beeninstalled for this browser.

Explanation: Java Plugin is missing from browser.Since plugin is not present, applet is not able to load.

System action: Applet unable to load and messagedisplayed.

User response: Install appropriate plugin for browserin order to use web client.

ANS8006E Unable to generate an acceptablepassword.

Explanation: An error occurred during a passwordupdate attempt using a generated password.



ANS8007E The user is not authorized to performLDAP authentication.

Explanation: Your node uses LDAP authentication.Your PASSWORDACCESS option is set to GENERATEbut the current user cannot access the stored passwordto perform authentication.

System action: The operation is stopped.

User response: Run TSM client as root user or setPASSWORDACCESS to PROMPT.

ANS8008W Redirection inside macro whose outputis redirected is ignored.

Explanation: An output redirection symbol has beenencountered inside a macro. However, the output of themacro itself (or a higher level macro) is already beingredirected.

System action: The redirection request is ignored.


ANS8010E An attempt to backup or archive a filehas exceed the maximum number ofretries.

Explanation: After five unsuccessful attempts tobackup or archive a file, the client will no longerattempt to send the file to the server.


User response: Check the console or schedule log foradditional information. Retry the operation at a latertime.

ANS8011W Rejected server-initiated session withLDAP authentication from peer name.

Explanation: For security, the client will not acceptserver-initiated sessions from servers that use LDAPauthentication.

System action: The client-server session is not opened,and the schedule is not executed. The scheduler



continues to wait for contact by a server that usesLOCAL authentication.

User response: If the client system is supposed toaccept scheduled events from the prompting TSMserver, either ask the TSM server administrator toconfigure your node to use LOCAL authentication, ordo not use server-initiated sessions.If the client system is not supposed to accept scheduledevents from the prompting server, ask the TSM serveradministrator to remove the client node name from theschedule on the prompting server.

ANS8012E Option processing storage exhausted.

Explanation: During processing of the client optionsfile, the client runs out of memory.

System action: The client session is ended.

User response: Make more memory available andrestart the administrative client.

ANS8013I Invalid encryption key password


System action: User is prompted for encryption keypassword.


ANS8014E Insufficient information to connect tohost.

Explanation: The client options file or command line,or both, do not contain enough communicationsinformation to successfully connect to the serversystem. For example, with TCP/IP both the TCPPortnumber and TCPServer address are required to make aconnection.

System action: The administrative client session isended.

User response: Determine what information is neededto establish a connection for your communicationsmethod and then specify all that information in yourclient options file or on the administrative clientcommand line.

ANS8015E File 'file spec', error code error code fromoptions processing.

Explanation: An unknown error code is returned fromthe routine that processes the client options file.


User response: Attempt to determine the error and

correct it. If the problem persists, contact your servicerepresentative.

ANS8016E Command line parameter parameternumber: 'parameter' is too long.

Explanation: The specified command line parameterexceeds the maximum length for a command lineparameter.


User response: Reissue the command with a shorterparameter.

ANS8017E Command line parameter parameternumber: 'parameter' is not valid.

Explanation: The command line parameter shown isnot a valid administrative client parameter.


User response: Reissue the command with validparameters.

ANS8018E Administrative command not valid inConsole mode.

Explanation: The Console Mode option has beenspecified but the client encounters what appears to be aserver command on the command line.


User response: Reissue the command with no servercommand.

ANS8019E Id and password must be supplied inBatch mode.

Explanation: A server command has been encounteredon the command line, but no administrator ID orpassword, or both, are specified.


User response: Reissue the command and include the-ID and -PASSWORD parameters on the command line.

ANS8020E Unable to open file 'file spec' for output.

Explanation: The file name specified in the -OUTFILEoption cannot be opened.

System action: The -OUTFILE parameter is ignored.

User response: Allow processing to continue or exitthe session and correct the file name.



ANS8021E Exiting Batch mode session due tooutput file error.

Explanation: The file specified in the -OUTFILEparameter cannot be opened for a session running inBatch mode.


User response: Reissue the command with a validoutput file name or make space available for the outputfile.

ANS8022E Output will be written only to stdout.

Explanation: The file specified in the -OUTFILEparameter cannot be opened, so output is written onlyto the standard output stream.

System action: Output that would have been writtento the output file is written to the standard outputstream.

User response: Allow processing to continue or exitthe session and correct the file name.

ANS8023E Unable to establish session with server.

Explanation: The administrative client cannot start asession with the requested server. This message ispreceded by another message that explains the reasonfor the error.


User response: Attempt to correct the error. If theproblem persists, contact your service representative.

ANS8024E End of macro after continued commandline.

Explanation: A macro containing a continuation linehas been executed, but no more lines are found in themacro file.

System action: The continued command is ignored,and an error return code is set for the macro.

User response: Correct the macro in error.

ANS8025E I/O Error reading command input.

Explanation: The client is unable to read an inputcommand from the terminal.


User response: Correct the problem on the terminaland retry the administrative session.

ANS8026E Input line longer than maximum of maxlength characters. Use continuation.

Explanation: An input command line is longer thanthe maximum input line length allowed.

System action: The input command is ignored.

User response: Reissue the command with severallines using continuation characters.

ANS8027E Unterminated comment in command.

Explanation: An input command contains an openingcomment mark but no closing comment mark.


User response: Reissue the command with matchingcomment marks.

ANS8028E Command longer than maximum of maxlength characters.

Explanation: An input command longer than themaximum command length allowed has been entered.


User response: Reissue the command with fewercharacters. This could mean replacing series ofrepeating blanks with a single blank.

ANS8029E Macro processing terminated.

Explanation: An error occurs during processing of amacro because the -ITEMCOMMIT option is notspecified on the command line. Processing of thismacro and any higher level macro is terminated.

System action: All current macro processing ends.

User response: Specify the -ITEMCOMMIT option onthe command line to ensure that the server commitseach command in the macro individually.

ANS8030E Substituted command longer thanmaximum of max length characters.

Explanation: After variable substitution, an inputcommand is longer than the maximum commandlength allowed.


User response: Reissue the command with fewercharacters. This may require replacing a series ofrepeating blanks with a single blank.

ANS8031E Missing name of macro to execute.

Explanation: A macro command is encountered thatdoes not contain a macro name.

System action: The command is ignored.



User response: Reissue the macro command with amacro file name.

ANS8032E Could not allocate storage to processmacro 'file spec'.

Explanation: The client cannot allocate enoughmemory to process the macro shown.


User response: Make more memory available to theclient and retry the macro command.

ANS8033E LDAP authentication is not supportedby Web client.

Explanation: The id you entered uses LDAPauthentication. LDAP authentication is not supportedby Web client.

System action: Login is unsuccessful.

User response: Use an id with LOCAL authentication.

ANS8034E Your administrator ID is not recognizedby this server.

Explanation: The administrator ID entered is notknown to the requested server.

System action: The administrative session terminates.

User response: Ensure that you are using a registeredadministrative ID for the server to which you areconnecting.

ANS8036E Administrative command not valid inMount mode.

Explanation: The Mount Mode option has beenspecified but the client encounters what appears to be aserver command on the command line.


User response: Reissue the command with no servercommand.

ANS8037E Missing name for redirection file.

Explanation: A command is entered that contains anoutput redirection symbol but no output file name.

System action: The command is ignored and an erroris returned.

User response: Reissue the command with an outputfile name.

ANS8038E Unable to open file 'file spec' forredirection.

Explanation: A command has been entered thatspecifies an output redirection file, but the file cannotbe opened.

System action: The command is ignored and an erroris returned.

User response: Reissue the command with a validoutput file name or make space available for the outputfile.

ANS8041E The server connection has been lost andcannot be re-established.

Explanation: During an administrative session, theclient discovers that the connection with the server hasbeen severed; an attempt to reestablish the connectionfails.


User response: Determine the cause of the failure;then try to restart the session at a later time. If theproblem persists, contact your service representative.

ANS8045E Communications error.

Explanation: An unexpected communications erroroccurs during an administrative session.



ANS8046E The client connection with the serverhas ended due to an unexpected error.

Explanation: The TSM error log might contain othermessages related to this error.

System action: The client session ends.

User response: Check the communication linkbetween the client and server to ensure that it isoperational. Examine the client error log for additionalmessages related to this error.

ANS8047E The client connection with the serverhas ended due to a communicationsbuffer overflow.



User response: Try the operation again. Check thecommunication link between the client and server toensure that it is operational. Examine the client error



log for additional messages related to this error.

ANS8048W Warning! Performing image restore ofthe Linux file system 'src' to an alternatedestination 'dest' is not recommended asthis may result in duplicate UUIDsleading to failed mounts after asuccessful restore.

Explanation: Performing an image restore of a Linuxfile system to an alternate destination may result induplicate UUID leading to failed mounts after asuccessful restore. On Linux, some file systems useUUID to identify themselves. If you took an imagebackup of such volume and restored it to a differentlocation, you will have two volumes with the sameUUID. If you use UUID to define your file systems in/etc/fstab, be aware that TSM may be unable to mountthe restored file system correctly. To avoid suchsituation, restore the image to its original location.


User response: If it is not possible or not desirable toavoid performing an image restore to an alternatedestination, change the UUID of either the original orrestored volume. Refer to your Linux documentationfor instructions on how to do this. You may also needto edit your /etc/fstab manually to allow the original,the restored or both volumes to mount.

ANS8049E A connection with the server cannot beestablished due to a communicationstime-out.



User response: Check the communication linkbetween the client and server to ensure that it isoperational. Examine the client error log for additionalmessages related to this error.

ANS8050E The TSM server is not acceptingadministrative sessions on the clientport.You must use the port numberdesignated for administrative sessions.

Explanation: The TSM server is configured to notallow administrative sessions on the client TCP/IPport. A different port number has been designated foruse by administrative sessions.

System action: The administrative session is notestablished.

User response: Use the TCPADMINPORT clientoption to specify the TCP/IP port number that the TSMserver uses for administrative sessions. See your TSMserver administrator if you do not know the correctport number.

ANS8052E Unable to decrypt file 'filespacenamepath-namefile-name'....Please try to restore this fileindividually

Explanation: File could not be decrypted and restored.

System action: File is not restored.

User response: Restore the file separately.

ANS8053E The network cannot be accessed.



User response: Check the communication linkbetween the client and server to ensure it isoperational. Examine the client error log for additionalmessages related to this error. Try the operation again.

ANS8054E No memory available to service request.

Explanation: Sufficient server memory is not available.


User response: Retry the administrative session. If theproblem persists, contact your service representative.

ANS8055E The server has insufficient resources toperform the operation.

Explanation: The server ran out of resources. A lack ofstorage or other problem condition does not allow anynew activity. The server activity log might containadditional information about this problem.


User response: The TSM administrator shouldexamine the TSM server activity log to determine thesource of the resource constraints. Try the operationagain when the server is under less load.

ANS8056E Your administrator ID is locked.

Explanation: The administrative ID entered has beenlocked by a system administrator and cannot be used.


User response: Contact your system administrator tounlock your ID.

ANS8057E The requested language files are notavailable.

Explanation: The NLS repository for the languagespecified is not available.


User response: Use a different language or obtain a



copy of the NLS repository for the language desired.

ANS8058E The specified path is a Linux Btrfssubvolume and is not valid for imagebackup.

Explanation: Linux Btrfs subvolumes are notsupported for image backup.

System action: The image backup operation is notperformed.

User response: Try the operation again using a validLinux Btrfs file system.

ANS8059E The TCP/IP functions have not beenlinked into this module.

Explanation: The ADSM TSO administrative clientcannot find the TCP/IP functions required to supportTCP/IP communications.

System action: The connection to the server fails.

User response: The TCP/IP functions must beincluded in the DSMADMC/ANSADM module. Referto the Program Directory for this product forinstructions on how to include the TCP/IP functions inthe DSMADMC/ANSADM module.

ANS8060E Error validating file 'VHDX file name'

Explanation: TSM cannot locate the file or the fileformat is not valid.

System action: The backup operation does not start.

User response: Try the operation again. If the problemcontinues, check the error log file for information abouthow to resolve this issue.

ANS8061E Session Rejected: The server does notallow a signonas a Unicode enabled administrativeclient

Explanation: The administrative client is unable toestablish a connection to the server because of aunicode enabling mismatch between server and client.


User response: Register a new administrator from adifferent administrative client or the server console, andsignon with the new administrator ID.

ANS8062E Client-to-Client communication is notallowed to take place when TSM Serverauthentication is turned off.

Explanation: Client-to-Client communication requiresTSM Authentication to be enabled.


User response: Turn TSM Server authentication onusing the Set AUthentication ON command.

ANS8063E The remote TSM Client Acceptorassociated with Node 'name' could notauthenticate with the TSM Server.

Explanation: Some TSM Client operations require theBackup/Archive Client to contact Clients on remotemachines. The remote machine in question cannotauthenticate with the TSM Server.


User response: On the remote machine, create a newTSM password for the Client Acceptor or verify thatthe current password is still valid before retrying theoperation.

ANS8064E Communication timeout. Reissue thecommand.

Explanation: The connection to the server is endedbecause of a communication timeout from the server.

System action: The server does not process thecommand.

User response: Reissue the command. If necessary,increase the values of IDLETIMEOUT andCOMMTIMEOUT options in the server options file.

ANS8103W A command was not successful.command : commandTSM function name : function-nameerror output : error-outputreturn code : return codeTSM file : file-name (line-number)

Explanation: TSM client called an external programthat failed.

System action: Depending on the circumstances, thefailure may or may not prevent further processing.

User response: See addition information in the errorlog. Use the information provided in this message fortroubleshooting or when talking with TSM support.

ANS8104W Cannot determine EFS status of the filesystem 'file-system name', errno='errnornumber', processing data normally.

Explanation: IBM Tivoli Storage Manager cannotdetermine EFS status on the specified filesystem. NoEFS specific processing will take place for files on thisfilesystem. If EFS is indeed enabled on the filesystem,all accessaible files will be backedup in cleartext.

System action: The filesystem will be processed as aregular filesystem.

User response: Contact your system administrator to



determine the cause of the error reported in themessage.

ANS8105W Unable to remove snapshot for volume'filespace-name'.

Explanation: TSM client was unable to remove thesnapshot used for image backup.


User response: See additional information in the errorlog. Use lvdisplay command to view the activesnapshots and lvremove command to remove thesnapshot manually.

ANS8106E Support for multiple IBM Tivoli StorageManager servers is enabled on thisnode.The server name must be specified forthis command.

Explanation: When a node is enabled to supportmultiple IBM Tivoli Storage Manager servers, thecommand must specify a valid IBM Tivoli StorageManager server name.


User response: Specify a valid server name for thiscommand.

ANS8201E Windows Hyper-V incremental backupsrequire Windows 2012 or later.

Explanation: TSM can only perform incrementalbackups of Windows Hyper-V on Windows operatingsystems of Windows Server 2012 and later. Incrementalbackups may not be performed on previous versions ofWindows.

System action: The incremental backup will not occur.

User response: To access incremental backups forWindows Hyper-V upgrade the operating system toWindows Server 2012 or later. Alternatively, PeriodicFull - Full backups are available for previous versionsof Windows.

ANS8503I No matching option found for pattern:'pattern'.

Explanation: You specified a pattern which does notmatch the name of any supported option.

System action: This message is the only response toyour query.

User response: Specify a different pattern or omit thepattern to display all options.

ANS8563E Recall mode has an invalid value:invalidValue.

Explanation: The recall mode you try to enable on thesystem is not existing.


User response: Check the value of the recall option.

ANS8565W ProgramName: list of recall IDs not foundin queue. These recalls are alreadyfinished:

Explanation: The program is not able to find the recallIDs and is not able to delete these processes.


User response: Check that recall IDs exist and arecorrect.

ANS8776E The IBM Tivoli Enterprise SpaceManagement Console cannot be started.Java Runtime Environment versionversion by companyhas been detected on machine.A Java Runtime Environment version orhigher is required to run this program.If you have already installed Java versionon this machine,please ensure that the correct Javaexecutable is on your PATH, otherwiseyou can download it from 'webAddress'and start the program again.

Explanation: IBM Tivoli Enterprise Space ManagementConsole cannot be started because the Java runtimeenvironment does not meet the requirements.

System action: A confirmation dialog is displayed foryou to close the application, or to open a browser witha link to the Web site where you can download thecorrect version of Java.

User response: Verify that the correct java executableis on your PATH or install the required version of Javaruntime environment and start the program again.

ANS8777E The IBM Tivoli Enterprise SpaceManagement Console cannot be started.An error occurred trying to load Tivolilook and feel.Verify that the product is correctlyinstalled.

Explanation: IBM Tivoli Enterprise Space ManagementConsole cannot be started because the library thatdefines the Tivoli look and feel cannot be found.

System action: The IBM Tivoli Enterprise SpaceManagement Console shuts down.

User response: Verify that the product is correctly



installed. If IBM Tivoli Enterprise Space ManagementConsole still cannot be started, contact your systemadministrator for further assistance.

ANS8778E A browser program cannot be found orcannot be started.An error occurred executing thecommand.commandVerify that a browser is installed andworks correctly on your local machine.

Explanation: A browser program cannot be found, soit is not possible to access the IBM Tivoli Web site andonline documentation.

System action: TSM continues to process userrequests.

User response: For the Windows platform, the defaultsystem browser is used. Verify that a browser isinstalled on your machine.

ANS8779E A browser program cannot be found orcannot be started.One of the following browsers isrequired: browser-listVerify that one of these browsers isinstalled and works correctly on yourlocal machine.

Explanation: A browser program cannot be found, soit is not possible to access the IBM Tivoli Web site andonline documentation.


User response: For UNIX platforms, a list ofsupported browsers is provided in the README.Install the required browser to access the IBM TivoliWeb sites and online documentation.

ANS8780E A browser program cannot be found orcannot be started.Check the 'file-name' file on your localmachine for more information.

Explanation: A browser program cannot be found, soit is not possible to access the Web site or onlinedocumentation.


User response: Install a browser to access the Web siteor online documentation.

ANS8781E The system could not log on to TSMclient nodenode-name on machine-name.Make sure your data and password arecorrect

and that caps lock key is not on.The Space Management Agent must berunning at the specifiedport on the machine to which you areattempting to log on to.

Explanation: The system was not able to connect tothe specified client node.


User response: Verify that:

v the information provided to connect is correct

v the machine is reachable in the network

v HSM is installed on the specified machine and aSpace Management Agent is running at the specifiedport.

ANS8782E An error occurred while loading filesystem information on 'fs-name'.Verify that the Space Management agentis running on the client node machine.Check also the local-log-file file in theinstallation directory of your localmachineand the $DSM_DIR/error-file file onmachine if present.If this does not identify the cause of theproblem, contact your systemadministratorand/or TSM technical support forfurther assistance.

Explanation: An error occurred while loading filesystem information on the selected client node

System action: Disconnects the client node.

User response: Verify that the Space Managementagent is running on the client node machine. Checkalso the dsmsm.log file in the installation directory ofyour local machine and the $DSM_DIR/dsmerror.logfile on the client node machine if present. If this doesnot identify the cause of the problem, contact yoursystem administrator and/or TSM technical support forfurther assistance.

ANS8783E An error occurred loading file systemproperties of fsName required to showspace usage graphical information.Verify that the Space Management agentis running on the client node machine.Check also the local-log-file file in theinstallation directory of your localmachineand the $DSM_DIR/error-file file onmachine if present.If this does not identify the cause of theproblem, contact your systemadministrator



and/or TSM technical support forfurther assistance.

Explanation: An error occurred while loading filesystem properties on the selected client node.

System action: Continue to process other file systemproperties.

User response: Verify that the Space Managementagent is running on the client node machine. Checkalso the dsmsm.log file in the installation directory ofyour local machine and the $DSM_DIR/dsmerror.logfile on the client node machine. If this does not identifythe cause of the problem, then see your systemadministrator for further assistance.

ANS8784E An error occurred initializing the clientnodes table.Your local configuration file 'config-file'might be corrupted.Remove it from your installationdirectory and start the program again.Check also the log-file file on your localmachine for more information.

Explanation: The client nodes table cannot beinitialized.

System action: The IBM Tivoli Enterprise SpaceManagement Console shuts down.

User response: It is possible that your local settingsfile 'dsmsm.cfg' is corrupted. Try to remove it fromyour installation directory and start the program again.Check the dsmsm.log file in the installation directory ofyour local machine and the $DSM_DIR/dsmerror.logfile on the client node machine if present. If this doesnot identify the cause of the problem, contact yoursystem administrator and/or TSM technical support forfurther assistance.

ANS8785E An error occurred disconnecting thesystem from the client node 'node-name'.The Client node is being disconnectedwithout deleting internal HsmSystemobjects.Verify that the Space Management agentis running on the client node machine.Check also the local-log-file file in theinstallation directory of your localmachineand the $DSM_DIR/error-file file onmachine if present.If this does not identify the cause of theproblem, contact your systemadministratorand/or TSM technical support forfurther assistance.

Explanation: An error occurred disconnecting thesystem from the client node. It was not possible todelete internal HsmSystem objects.

System action: The client node disconnected withoutdeleting HsmSystem objects.

User response: Verify that the Space Managementagent is running on the client node machine. Check thedsmsm.log file in the installation directory of your localmachine and the $DSM_DIR/dsmerror.log file on theclient node machine if present. If this does not identifythe cause of the problem, contact your systemadministrator and/or TSM technical support for furtherassistance.

ANS8786E An error occurred loading file systeminformation from the selected clientnode.Verify that the Space Management agentis running on the client node machine.Check also the local-log-file file in theinstallation directory of your localmachineand the $DSM_DIR/error-file file in theclient node machine if present.If this does not identify the cause of theproblem, contact your systemadministratorand/or TSM technical support forfurther assistance.

Explanation: An error occurred loading file systeminformation from the selected client node.

System action: File System information is not loaded


ANS8787E An error occurred loading file systeminformation from nodename client node.The client node is being disconnected.Verify that the Space Management agentis running on the client node machine.Check also the local-log-file file in theinstallation directory of your localmachineand the $DSM_DIR/error-file file onmachine if present.If this does not identify the cause of theproblem, contact your systemadministratorand/or TSM technical support forfurther assistance.

Explanation: An error occurred loading file systeminformation from the selected client node.

System action: The client node is disconnected




ANS8788E An error occurred starting manuallythreshold migration on file-system.Verify that the Space Management agentis running on the client node machine.Check also the local-log-file file in theinstallation directory of your localmachineand the $DSM_DIR/error-file file onmachine if present.If this does not identify the cause of theproblem, contact your systemadministratorand/or TSM technical support forfurther assistance.

Explanation: An error occurred starting the manuallythreshold migration on the selected client node.

System action: Threshold migration is not startedmanually.

User response: Check the dsmsm.log file in theinstallation directory of your local machine and the$DSM_DIR/dsmerror.log file on the client nodemachine if present. If this does not identify the cause ofthe problem, contact your system administrator and/orTSM technical support for further assistance.

ANS8789E An error occurred trying to deactivate allmanaged file systems of client-node.Check also the local-log-file file in theinstallation directory of your localmachineand the $DSM_DIR/error-file file onmachine if present.If this does not identify the cause of theproblem, contact your systemadministratorand/or TSM technical support forfurther assistance.

Explanation: An error occurred trying to deactivate allmanaged file systems of the selected client node.

System action: File systems are not deactivated.


ANS8790E An error occurred trying to reactivate allmanaged file systems of client-node.Check also the local-log-file file in theinstallation directory of your localmachineand the $DSM_DIR/error-file file onmachine if present.If this does not identify the cause of theproblem, contact your systemadministratorand/or TSM technical support forfurther assistance.

Explanation: An error occurred trying to reactivate allmanaged file systems of the selected client node.

System action: File systems are not reactivated.


ANS8791E An error occurred trying to add spacemanagement to fs-name file system.Verify that the Space Management agentis running on the client node machine.Check also the local-log-file file in theinstallation directory of your localmachineand the $DSM_DIR/error-file file onmachine if present.If this does not identify the cause of theproblem, contact your systemadministratorand/or TSM technical support forfurther assistance.

Explanation: An error occurred trying to add spacemanagement to the selected file system.

System action: Space management is not added to theselected file system.


ANS8792E An error occurred trying to removespace management from file-system filesystem.Verify that the Space Management agentis running on the client node machine.Check also the local-log-file file in theinstallation directory of your localmachineand the $DSM_DIR/error-file file on



machine if present.If this does not identify the cause of theproblem, contact your systemadministratorand/or TSM technical support forfurther assistance.

Explanation: An error occurred trying to removespace management from the selected file system.

System action: Space management is not removedfrom the selected file system.


ANS8793E An error occurred trying to deactivatefile-system file system.Verify that the Space Management agentis running on the client node machine.Check also the local-log-file file in theinstallation directory of your localmachineand the $DSM_DIR/error-file file onmachine if present.If this does not identify the cause of theproblem, contact your systemadministratorand/or TSM technical support forfurther assistance.

Explanation: An error occurred trying to deactivatethe selected file system.

System action: The selected file system is notdeactivated.


ANS8794E An error occurred trying to reactivatefile-system file system.Verify that the Space Management agentis running on the client node machine.Check also the local-log-file file in theinstallation directory of your localmachineand the $DSM_DIR/error-file file onmachine if present.If this does not identify the cause of theproblem, contact your systemadministratorand/or TSM technical support forfurther assistance.

Explanation: An error occurred trying to reactivate theselected file system.

System action: The selected file system is notreactivated.


ANS8795E An error occurred trying to save yoursettings to config-fileconfiguration file on your localmachine.Check the log-file file in the installationdirectory ofyour local machine for moreinformation.

Explanation: An error occurred trying to save yoursettings to dsmsm.cfg configuration file on your localmachine.

System action: Customized GUI settings are not savedto the local machine


ANS8809E The LD_LIBRARY_PATH is either notset or is set incorrectly. Ensure that theLD_LIBRARY_PATH environmentvariable contains the installationdirectory path name.

Explanation: The LD_LIBRARY_PATH must be setand it must contain the installation directory path.

System action: The VMware backup or restoreoperation fails.

User response: Set the LD_LIBRARY_PATH andensure that it contains the Backup/Archive clientinstallation directory.

ANS8810E The LD_LIBRARY_PATH is either notset or is set incorrectly. Ensure that theLD_LIBRARY_PATH environmentvariable contains the installationdirectory.

Explanation: The LD_LIBRARY_PATH must be setand it must contain the installation directory path.




User response: Set the LD_LIBRARY_PATH andensure that it contains the Backup/Archive clientinstallation directory.

ANS8811E VMware operations can not be runwhen the hardware plugin productTIVsm-BAhdw is installed and loaded.Please either uninstall the hardwareproduct TIVsm-BAhdw, or set theoption DONTLOAD PIHDW in theoptions file to prevent the hardwareplugin from being loaded.

Explanation: VMware operations are incompatiblewith the hardware plugin product libraries.


User response: Uninstall the hardware productproduct TIVsm-BAhdw, or set the option DONTLOADPIHDW to prevent the hardware plugin from beingloaded.

ANS8818E An error occurred trying to apply yourchanges.Your changes have not been applied tothe system.Contact your system administrator.

Explanation: An error occurred trying to apply yourchanges.

System action: User changes are not applied.


ANS8819E The following trace flag(s) are not valid:trace-flag-list.Correct them before continuing.

Explanation: One or more of the trace flags are notvalid.

System action: Prompts the user to correct the traceflags.

User response: Correct the wrong trace flags.

ANS8820E The HSM System Object was not foundon the Space Management agent.The error occurred when callingfunction: function-name.The last operation was not processedcorrectly.

Explanation: The Space Management agent wasunable to process a HSM System function, because theHSM System object was not found.

System action: The last operation is skipped.

User response: Reconnect to the Space Management

agent. If this does not solve the problem restart theSpace Management agent.

ANS8821E Unable to create requested HSM objecton Space Management agent.The last operation was not processedcorrectly.The problem is caused from a memoryproblem. Try to free memoryon the system where the SpaceManagement agent is running.Or restart the Space Management agent.

Explanation: Space Management agent was not able tocreate a requested HSM object because not enough freespace was found on the system.

System action: Last operation is skipped.

User response: Try to free more memory on thesystem where the Space Management agent is running,or restart the Space Management agent.

ANS8822E HSM File System Object was not foundon Space Management agent.The error occurred when callingfunction: function-nameThe last operation was not processedcorrectly.

Explanation: Space Management agent was not able toprocess a HSM File System function, because no HSMFile System object was found.


User response: Reconnect to the Space Managementagent. If this does not solve the problem restart theSpace Management agent.

ANS8823E A Protocol error occurred incommunication with the SpaceManagement agentThis error occurs when a session withthe Space Management agent was lost,ornetwork error caused synchronizationproblem between the SpaceManagement consoleand the agent.

Explanation: Space Management console and SpaceManagement agent has different session andtransaction key in the communication header.


User response: Restart Space Management consoleand Space Management agent.



ANS8824E A internal error occurred in the SpaceManagement agent.The error occurred in function :function-name

Explanation: Not defined exception caused a internalerror in the Space Management agent.


User response: Restart Space Management agent. Ifthis does not solve the problem contact TSM technicalsupport.

ANS8825E The Space Management API was unableto locate option objectThe error occurred in function :function-name

Explanation: Not defined exception caused thisinternal error in the Space Management API.


User response: Contact TSM technical support.

ANS8826E The Space Management API was unableto query a HSM device.This error occurs because the HSMkernel extension was not loadedcorrectly

Explanation: Because of a wrong configuration HSMwas not able the load the kernel extension. This causesto fail the query for global activation of the HSMsystem.

System action: Query for global HSM activation isskipped.

User response: Check the configuration of the HSMsystem. If you can not find any problem in theconfiguration contact TSM technical support.

ANS8827E The Space Management API was unableto locate global control block.The error occurred in function :function-name

Explanation: Not defined exception caused thisinternal error in the Space Management API.

System action: Load connection settings function isskipped.

User response: Contact TSM technical support.

ANS8828E The Space Management API lost thesession with the server.This problem is caused by a connectionfailure with the server.Check to see if your Space ManagementClient machine has a network

connectionto the TSM server.

Explanation: This error occurs when the SpaceManagement API has connection problems with theTSM server.

System action: Session with server gets lost andserver operation is skipped.

User response: Check the network connection withTSM server machine. See the error log file foradditional information why the session gets lost.Restart the Space Management Agent if the connectionre-established automatically.

ANS8829E The Space Management API was unableto initialize the HSM system.The error is caused from a problem toinitialize a DMAPI session.

Explanation: This error is caused from a problem toinitialize a DMAPI session.

System action: The HSM system cannot be initializedand the Space Management Console is ended.

User response: Try to restart Space ManagementAgent. If this does not solve the problem, see the errorlog for additional information and contact TSMtechnical support.

ANS8830W Different server name stanzas(HSM-stanza and BA-stanza) forfile-system-name file system for spacemanagement and backup-archive.

Explanation: The server name stanzas you specifiedfor the space management (HSM) client and thebackup-archive (BA) client are different. The inlinebackup and stub restore features will be unavailable forthe file system.


User response: If you want to allow inline backup andstub restore for the file system, the MIGRATESERVERand DEFAULTSERVER options must specify the sameSERVERNAME stanza in dsm.sys. You may also chooseto supply a server stanza name using theSERVERNAME option in dsm.opt or on the commandline. In either case the stanza name must match thestanza specified in the MIGRATESERVER option.

ANS8831E The Space Management API could notfind file system : function-nameAn incorrect file system name waspassed to the Space Management API.Ensurethat the file system that was selected inthe file system list is still valid.Refresh the file system view in theSpace Management Console by pressingF5 on your



keyboard or select 'Refresh` under theView menu.

Explanation: The Space Management API could notfind the file system that was specified in the SpaceManagement Console. A reason could be that the filesystem was unmounted and is not longer existing onthe system.

System action: Getting file system information for thespecified file system name is skipped.

User response: Update the file system list in the SpaceManagement Console by pressing F5 on your keyboardor selecting 'Refresh' in the View menu.

ANS8832E The Space Management API could notretrieve TSM policy settings from theserver.

Explanation: The Space Management API tried to getTSM policy settings from the server and failed for aunknown reason.

System action: Getting TSM policy settings fails andpolicy information fields are not filled up in the SpaceManagement Console.

User response: See the error log file for additionalinformation.

ANS8833E The Space Management API could notretrieve TSM policy settings fromthe already loaded list.

Explanation: The Space Management API tried to getTSM policy settings from the management list andfailed for a unknown reason.

System action: Getting TSM policy settings fails andpolicy information fields are not filled up in the SpaceManagement Console.


ANS8834E The Space Management API was unableto get file system information forfile system : filesystem-name.

Explanation: The Space Management API could notretrieve the file system information for a selected filesystem.

System action: Getting file system information failsand information are not displayed in the SpaceManagement Console.


ANS8835E The Space Management API was unableto get file system status forfile system : filesystem-name.System call to get file system statusreturned with error.

Explanation: The Space Management API could notretrieve the file system status for a selected file system.The error is caused from a failed system call on the filesystem.

System action: Getting file system status fails andinformation are not displayed in the SpaceManagement Console.


ANS8836E An object creation error occurred in theSpace Management APIThe error occurred in function :function-name.The problem is caused from a memoryproblem. Try to free memoryon the system where the SpaceManagement agent is running.Or restart the Space Management agent.

Explanation: Caused from a out of memory problemthe Space Management API could not create arequested object.

System action: The requested function fails andcannot retrieve information to the Space ManagementConsole.

User response: Free more memory on the systemwhere the Space Management agent is running, orrestart the Space Management agent.

ANS8837E The Space Management API was unableto get configuration datafrom managed file system :filesystem-name.The problem is caused from a errorwhen reading dsmmigfs table entry.

Explanation: The Space Management API readsinformation from dsmmigfs table to get HSM managedfiles system configuration. This error occurs when theAPI is unable to read an entry from this table.

System action: Getting HSM managed file systemconfiguration fails and information is not displayed inthe Space Management Console.

User response: See the error log for additionalinformation on errors occurring when reading entriesfrom the dsmmigfs table.



ANS8838E The Space Management API can not setHSM managed file systemconfiguration for file system :filesystem-name.The configuration cannot be set becausethis file system is NOT HSM managed.Check to see if the managed file systemthat was selected in the file system listis still HSM managed.Refresh the file system view in theSpace Management Console by pressingF5 on yourkeyboard or select 'Refresh` under theView menu.

Explanation: The file system that you selected fromthe file system list in the Space Management console isnot longer HSM managed and no configuration can betset for it. A reason could be that the file system wasunmanaged from a other user.

System action: Setting HSM managed file systemconfiguration fails.


ANS8839E A wrong stub file size was passed to theSpace Management API forfile system : filesystem-name.The stub file size that was entered inthe file system properties dialog is notsupportedby this file system. Correct the stub filesize value in the file system propertiesdialogof the Space Management Console.

Explanation: The Stub file size that you has specifiedis not supported by this file system.

System action: Wrong stub file size is not applied tothe file system.

User response: Correct the stub file size in the filesystem properties dialog of the Space ManagementConsole.

ANS8840E The maximum number of candidatesthat was specified forfile system : filesystem-name is out ofrange.The maximum number of candidatesvalue that was entered in the file systemproperties dialog is out of range.Correct the maximum number ofcandidates value in the file systemproperties dialogof the Space Management Console.

Explanation: The maximum number of candidates

value that was specified is out of range for this filesystem.

System action: Wrong maximum number ofcandidates value is not applied to the file system.

User response: Correct the maximum number ofcandidates value in the file system properties dialog ofthe Space Management Console.

ANS8841E The server name that was specified forthe file system :optfile-name is not valid.Correct the server name value in theclient node properties dialogof the Space Management Console.

Explanation: The server name that was specified isnot valid.

System action: Wrong server name value is notapplied to the system options file.

User response: Correct the server name value in theclient node properties dialog of the Space ManagementConsole.

ANS8842E The Space Management API was notable to modify system options file :optfile-name because of insufficientprivilege.Use root user to change HSM managedfile system configuration.

Explanation: User has no rights to modify systemoptions file.

System action: Changes are not applied to the systemoptions file.

User response: Run as root user to change HSMmanaged file system configuration.

ANS8843E No correct include/exclude settings arefound in system options file :optfile-name.Correct the include/exclude list in thesystem options file.

Explanation: The include/exclude settings in thesystem options file are not correct.


User response: Correct the include/exclude list in thesystem options file.

ANS8844E A incorrect preferred node or servername was specified in the HSMconfiguration forfilesystem-name.Correct the preferred node and servername value in the HSM configuration.



Explanation: The Space Management API could notchange preferred node settings because a wrong valuewas specified


User response: Correct the preferred node and serversettings in Space Management Configuration.

ANS8845E A incorrect owner node or server namewas specified in the HSM configurationforfilesystem-name.Correct the owner node and server namevalue in the HSM configuration.

Explanation: The Space Management API could notchange owner node settings because a wrong value wasspecified


User response: Correct the owner node and serversettings in Space Management Configuration.

ANS8846E The Space Management API was notable to update the HSM managedfile system : filesystem-name.

Explanation: The Space Management API could notapply configuration changes to the HSM managed filesystem.

System action: Changes are not applied to HSMmanaged file system.

User response: See error log file for additionalinformation why the update of the file system fails.

ANS8847E The Space Management API was notable to obtain a lock on SDR file forfile system : filesystem-name.

Explanation: The Space Management API could notlock the SDR file for the file system.

System action: Changes are not applied to HSMmanaged file system.

User response: See the error log file for additionalinformation on why the lock on the SDR file fails.

ANS8848E The Space Management API could notopen file system status file to retrievemanaged file system statistics for :filesystem-name.Reason could be insufficientpermissions or that the file does notexist. The managed file system statisticsare not retrieved from the HSM system.

Explanation: The Space Management API could not

retrieve managed file system information from filesystem status file. The error occurred when the APItries to open the file for reading.

System action: Managed file system statistics are notretrieved and information is not displayed in the SpaceManagement Console.

User response: See the error log file for additionalinformation on why opening the file system status filefails.

ANS8849E The Space Management API was notable to load HSM managedfile system statistics for : filesystem-name.Check to see if the managed file systemthat was selected in the file system listis still HSM managed.Refresh the file system view in theSpace Management Console by pressingF5 on yourkeyboard or select 'Refresh` under theView menu.

Explanation: The Space Management API could notload managed file system statistics from selected filesystem. The reason could be that the file system is notlonger HSM managed.

System action: Managed file system statistics are notretrieved and information is not displayed in the SpaceManagement Console.


ANS8850E The Space Management API was notable to add HSM tofile system : filesystem-name.This error occurs because selected filesystem is not mounted.You must mount the file system beforeyou can add HSM.

Explanation: The Space Management API could notadd HSM to a file system, because it is not mounted.

System action: The add HSM operation fails and HSMis not added to the selected file system.

User response: Mount the selected file system beforeadding HSM.

ANS8851E The Space Management API was notable to add HSM tofile system : filesystem-name.This error occurs because selected filesystem is not supported to add HSM.

Explanation: The Space Management API could notadd HSM to a unsupported file system.

System action: The add HSM operation fails and HSM



is not added to the selected file system.

User response: Select a supported file system to addHSM.

ANS8852E The Space Management API was notable to add HSM tofile system : filesystem-name.This error occurs because selected filesystem is already HSM managed.

Explanation: The Space Management API attempt tomanage a already HSM managed file system.

System action: The add HSM operation fails and theselected file system stays HSM managed.

User response: Select a not managed file system toadd HSM.

ANS8853E The Space Management API was notable to add HSM tofile system : filesystem-name.

Explanation: The Space Management API attempt tomanage file system and fails for a unknown reason.

System action: The add HSM operation fails and HSMis not added to the selected file system.

User response: Retry the add HSM operation. If thisdoes not solve the problem, see the error log file foradditional information and contact TSM technicalsupport.

ANS8854E The Space Management API was notable to remove HSM fromfile system : filesystem-name.The error occurs when the SpaceManagement API tries to lock the SDRfile and fails.

Explanation: The Space Management API attempt tounmanage (remove) file system and fails for aunknown reason.

System action: The remove HSM operation fails andHSM is not removed from the selected file system.

User response: Try the remove HSM operation again.If this does not solve the problem, see the error log filefor additional information and contact TSM technicalsupport.

ANS8855E The Space Management API was notable to start automaticmigration on the file system :filesystem-name.

Explanation: The Space Management API tries to startautomatic migration on a file system and fails for aunknown reason.

System action: The automatic migration is not startedfor the file system.

User response: See the error log file for additionalinformation and contact TSM technical support.

ANS8856E The Space Management API was notable to start reconciliationprocess on the file system :filesystem-name.

Explanation: The Space Management API tries to startreconciliation process on a file system and fails for aunknown reason.

System action: The reconciliation process is notstarted for the file system.

User response: See the error log file for additionalinformation, and contact TSM technical support.

ANS8857E The Space Management API was notable to start scoutprocess on the file system :filesystem-name.

Explanation: The Space Management API tries to startscout process on a file system and fails for a unknownreason.

System action: The scout process is not started for thefile system.

User response: See the error log file for additionalinformation, and contact TSM technical support.

ANS8858E The Space Management API was notable to migratethe file : file-name.The error occurred in function :function-name.

Explanation: The Space Management API tries tomigrate a file and fails in the displayed API function.

System action: The selected file is not migrated to theserver.


ANS8859E The Space Management API was notable to recallthe file : file-name.The error occurred in function :function-name.

Explanation: The Space Management API tries torecall a file and fails in the displayed API function.

System action: The selected file is not recalled fromthe server.




ANS8939E An unexpected error occurred trying tofilter the directory tree.rc=return-code

Explanation: The filter was not applied to thedirectory tree.

System action: The directory tree is not filtered.

User response: Contact your system administrator forfurther assistance.

ANS8945E An unexpected error occurred analyzingthe directory tree.The list of files matching your searchcriteria is not completed.rc=return-code

Explanation: It was not possible to search all itemsmatching the search criteria on the directory tree due toan unexpected error.

System action: The search results table shows only theitems found until the error is occurred.

User response: Contact your system administrator forfurther assistance.

ANS8946E RPC call failed.

Explanation: Unable to connect receiver recalldaemon.


User response: System is not operating correctly orrecall daemons are not started.

ANS9005W program name: invalid 'parameter name'value: value (must be in [minimumvalue..maximum value]).

Explanation: The program found an invalid parameterin the space management configuration of a filesystem.

System action: The paramter value was rejected.

User response: In case you tried to set the specifiedvalue manually, choose a value from the specifiedrange instead. If the value is read from a file system'sspace management configuration file (located at[fs]/.SpaceMan/hsmfsconfig.xml), edit the fileaccordingly. The name of the filesystem can bedetermined from a subsequent error message.

ANS9007W program name: invalid 'parameter name'value: value (must be in [minimumvalue..maximum value]).

Explanation: The program found an invalid parameterin the space management configuration of a filesystem.

System action: The paramter value was rejected.

User response: In case you tried to set the specified

value manually, choose a value from the specifiedrange instead. If the value is read from a file system'sspace management configuration file (located at[fs]/.SpaceMan/hsmfsconfig.xml), edit the fileaccordingly. The name of the filesystem can bedetermined from a subsequent error message.

ANS9008W Compression is enabled. Recall modefor file file-name cannot be set to partial.

Explanation: TSM can only set file attributes to auncompressed migrated file. This file has beenmigrated with compression enabled.

System action: TSM does not set the file attributes.

User response: Recall the file to state resident disablecompression and migrate the file again. Retry theoperation.

ANS9009E program name: found invalid spacemanagement configuration for'filesystem'.

Explanation: The program found an invalid spacemanagement configuration for the given filesystem.

System action: The space management configurationwas rejected for the given filesystem . When updatingan existing configuration, invalid configurations to setare ignored. When a persistent configuration file isinvalid, the filesystem will appear to not have spacemanagement enabled.

User response: In case you tried to update spacemanagement for this filesystem manually, enter a validconfiguration instead. In case the persistentconfiguration file is invalid, edit the file accordingly;alternatively, you can add space management explicitly(which will remove / overwrite the existingconfiguration). The reason for the configuration can bedetermined from a preceding error message. Thefilesystem's space management configuration file islocated at 'filesystem'/.SpaceMan/hsmfsconfig.xml.

ANS9010E program name: could not parse spacemanagement configuration file'configuration file' for filesystem.

Explanation: The space management configuration filefor the given filesystem is present but its contentappears to have invalid format.

System action: The configuration was rejected. Thefilesystem will appear to not have space managementenabled.

User response: Check the given space managementconfiguration file; it is supposed to contain awell-formed XML document with a root elementnamed 'HsmFsConfig'. To create a new configurationfile, you can simply add space management to thisfilesystem.



ANS9011E program name: could not write spacemanagement configuration file'configuration file' for filesystem.

Explanation: IBM Tivoli Storage Manager could notwrite and save the space management configuration filefor the given filesystem.

System action: IBM Tivoli Storage Manager did notsave the space management configuration information.If you tried to add space management for thisfilesystem, it was not added. If you tried to update thespace managment configuration, it was probably notupdated. If an existing configuration file in old formatwas read successfully, but could not be converted toXML format, space management will be active for thisfilesystem with the configuration from the old file.

User response: Determine if there is any reason whythe given file cannot be written.

ANS9012E error-program: Command must be run byroot user.

Explanation: TSM requires that a root user performthis operation.

System action: TSM terminates the operation.

User response: Change to root user, and then retry theoperation.

ANS9016E Cannot get space management migrationstatus for path.

Explanation: An error occurred while trying to get thespace management migration status. Either thepermissions for the status file are not set correctly, orthe status file is damaged.


User response: The root user should check thepermissions of the status file, or contact the servicerepresentative.

ANS9017W error-program: Minimum number ofrecall daemons min-dsmrecalld cannot begreaterthan maximum number of recalldaemons max-dsmrecalld;defaulting to minimum min-dsmrecalldand maximum max-dsmrecalld.

Explanation: A minimum number of recall daemonshas been entered that is greater than the maximumnumber of recall daemons.

System action: TSM uses defaults instead of thevalues specified in the client system options file(dsm.sys).

User response: Correct the MINRECALLDAEMONSand MAXRECALLDAEMONS options in the client

system options file and retry the operation.

ANS9020E A session could not be established witha TSM server or client agent. The TSMreturn code is tsm-error;.

Explanation: An issue prevented the client frommaking a connection with the TSM server. Additionaldetail is not available to include with this message.However, additional messages are likely to be reportedin the TSM error log.


User response: Check the TSM error log for additionalmessages. Refer to those messages to determine how toresolve any reported issues. If the tsm-error is -50, thereis a communication failure. Typical causes of this errorinclude misconfiguration of the server TCP/IP addressor port. Verify the TSM configuration and that theclient system network is connected. Verify that afirewall does not prevent access to the TSM server.Finally, verify that the TSM server is running andaccepting connections on the expected port.

ANS9021E error-program Unknown recall daemon(pid process-ID) terminated abnormally,status: status.

Explanation: A recall daemon stops abnormally.


User response: Try the operation again. If the problempersists, send the core file to IBM technical support foranalysis.

ANS9022E error-program Recall daemon (pidprocess-ID) ended abnormally, status:status.

Explanation: A recall daemon stopped abnormally.

System action: The operation does not complete.

User response: Try the operation again. If the problempersists, send the core file to IBM technical support foranalysis.

ANS9024E Starting with this release all candidateprocessing is doneinternally by the TSM monitor daemon.Thus -c is no longer a validoption for dsmreconcile.

Explanation: The command line options -c and-Candidates are no longer valid for dsmreconcile as allcandidates processing is now performed bydsmmonitord.

System action: TSM detected an invalid option.dsmreconcile is exiting.

User response: Don't use options -c and -Candidates



with dsmreconcile anymore.

ANS9025E The Data Protection for WebSphereplug-in version and the backup-archiveclient version do not match. Pleaseupgrade your Data Protection forWebSphere plug-in.

Explanation: The release and version of the DataProtection for WebSphere plug-in is downlevel from therelease and version of the Backup-Archive Client.

System action: None

User response: Upgrade Data Protection forWebSphere to the proper release and version.

ANS9028E program name: could not acquire lock forfilesystem.

Explanation: Prior to modifying a space managementconfiguration file, it is required to lock the file in orderto avoid concurrent access. If acquiring the lock fails,there was a concurrent access.

System action: The action was cancelled.

User response: Retry the same request or determinethe process holding the lock.

ANS9029E The WebSphere server is running, butthe server must be shut down for arestore operation. Shut down theWebSphere server and try the restoreoperation again.

Explanation: The WebSphere server must be broughtdown to perform a restore.

System action: The restore operation fails.

User response: Shut down the WebSphere server andtry the restore operation again.

ANS9030W Cannot set conflicting attributes to filefile-name.

Explanation: TSM cannot set the file attributesbecause the requested attributes are in conflict with oneanother.


User response: Retry this operation with attributesthat do not conflict with each other.

ANS9031W File file-name is not a migrated file.

Explanation: TSM can only set file attributes to amigrated file. This file has not been migrated.


User response: Migrate this file, and then retry theoperation.

ANS9032W File file-name is not in an HSM managedfile system.

Explanation: TSM detects that the file is not in anHSM managed file system, and therefore, it cannotperform the operation requested.


User response: Add space management to the filesystem, migrate the file, and then retry the operation.

ANS9034E The restore operation did not complete,due to a change in the originalWebSphere environment.

Explanation: The data must be restored to the sameenvironment that it was backed up from. This includesitems such as cell name, node name, and the locationwhere WebSphere is installed.

System action: The restore operation does notcomplete.

User response: Perform the restore procedure in theDP for WebSphere book.

ANS9036W program-name: migrated file(s) aremissing on server for number stub file(s).Look in 'file-spec' for file names.

Explanation: TSM cannot find the migrated file(s) onthe server.

System action: TSM continues.

User response: Look in the path mentioned in themessage for the file name. Also ensure that you areworking with the correct server for this file.

ANS9054E The plug-in was not found.

Explanation: None.

System action: None

User response: Run "dsmc show plugins" at thecommand prompt to see the available plug-ins on thesystem.

ANS9057W error-program: cannot get spaceinformation for file-system: error.

Explanation: TSM cannot get the space informationfor the file system.


User response: Verify that space management hasbeen added to the file system.



ANS9059E error-program: process cannot detach tobecome a daemon.

Explanation: TSM process cannot detach itself tobecome a daemon.

System action: TSM cannot start the daemon asrequested. TSM stops.

User response: Retry the operation.

ANS9060W error-program: cannot get and increaselimit of open files.

Explanation: TSM either cannot get the limit of thenumber of open files, or cannot increase the limit of thenumber of open files.

System action: TSM cannot increase the number ofopen files, and was not able to complete the operation.

User response: Free some file space by ending someprocesses or removing some files, and retry theoperation.

ANS9062E File 'filename' has changed during thebackup.

Explanation: A file changed during the backup. Checkthe dsmerror.log file for a list of files that havechanged.

System action: The backup fails.

User response: Try the backup again.

ANS9063E error-program: file system file-system is outof inodes.

Explanation: TSM cannot get space for the file systembecause the file system is out of inodes.

System action: TSM cannot get space via migration.

User response: Remove some files to make moreinodes available and retry.

ANS9064E error-program: Cannot fork a newprocess: error.

Explanation: TSM cannot fork a new process that isneeded. If the operating system errno is EAGAIN, thenthe limit on the total number of processes running onthe system or by a single user has been exceeded, orthe system does not have the resources necessary tocreate another process. If the errno is ENOMEM, thenthere is not enough memory to create the process.


User response: Depending on the error code (errno),either allocate additional virtual memory (swap space)or increase the operating system process limit. Thenrestart the HSM daemons or reboot the system.

ANS9065E File 'filename' or file 'filename2' has beenadded or removed during the backup.

Explanation: A file was added or removed during thebackup.



ANS9067W error-program: error updatingdsmmigfstab file for file-system.

Explanation: TSM found an error in updating thedsmmigfstab file for this file system.

System action: TSM does not update the dsmmigfstabfile.

User response: See the preceding error message andcorrect the error if possible. Then, retry the operation. Ifproblem persists, contact your system administrator.

ANS9068I program-name: dsmmigfstab file updatedfor file system file-system.

Explanation: TSM successfully updated thedsmmigfstab file for the file system.


User response: Continue with normal operation.

ANS9069I program-name: all file systems arereactivated to previous states.

Explanation: TSM has reactivated all file systemsmanaged by HSM to their previous states before theglobal deactivation.



ANS9070I program-name: space management is nowdeactivated for all HSM file systems.

Explanation: TSM has deactivated space managementfor all file systems listed in the dsmmigfstab file.



ANS9071W program-name: error reactivating spacemanagement for all HSM file systems.

Explanation: TSM found an error in trying toreactivate space management.

System action: TSM does not reactivate spacemanagement for HSM file systems.

User response: Make sure space management isinstalled correctly and retry the operation.



ANS9072W error-program: error deactivating spacemanagement for all FSM file systems.

Explanation: TSM found an error in trying todeactivate space management.

System action: TSM does not deactivate spacemanagement for FSM file systems.


ANS9073W program-name: error deactivating spacemanagement for file system file-system.

Explanation: TSM found an error in trying todeactivate the file system.

System action: TSM does not deactivate spacemanagement for the file system.


ANS9074I program-name: space managementfunctions have been locally deactivatedfor file system file-system.

Explanation: TSM has locally deactivated spacemanagement functions like migration, recall andreconciliation for the file system.



ANS9075W program-name: error reactivating spacemanagement for file system file-system.

Explanation: TSM found an error in trying toreactivate space management for the file system.

System action: TSM does not reactivate spacemanagement for the file system.

User response: Verify that the specified file system ismounted and that HSM is enabled for this file system.Then try the operation again. If the problem persists,contact IBM technical support for additional assistance.Provide the /etc/filesystems (or equivalent file) and theoutput from the mount and dsmdf commands.

ANS9076I program-name: space managementfunctions have been locally reactivatedfor file system file-system.

Explanation: TSM has locally reactivated spacemanagement functions like migration, recall andreconciliation for the file system. Please, note howeverthat the space management might still be globallydeactivated.



ANS9077I program-name: removed spacemanagement from file system file-system.

Explanation: TSM removed space management. Thefile system is now a native file system.



ANS9078W Space management is not removed fromfile system file-system.

Explanation: TSM was not able to remove spacemanagement from this file system. Possible causes:

Kernel extension is downlevel.

Program is downlevel.

Insufficient disk space.


User response: Refer to the immediately precedingerror message and retry the operation.

ANS9079W program-name: no migrated filesmatching search criteria found.

Explanation: TSM did not find any migrated filesmatching the search criteria.


User response: Retry the operation with a differentsearch criteria.

ANS9080E program-name: not enough space in filesystem or storage pool to recall allmigrated files.

Explanation: TSM detects there is not enough space inthe file system to hold all the migrated files if all arerecalled. If you are using GPFS storage pools, each poolneeds to have enough space to recall it's files.

System action: TSM does not attempt to recall all themigrated files.

User response: Make room in the file system byincreasing the file system size or removing some files.Retry the operation.

ANS9081W program-name: orphaned stub file(s)detected in file system file-system.

Explanation: TSM detected one or more orphanedstub files. Either the migration server was changed inthe client system options file after the file wasmigrated, or the migration server database is damaged.

System action: TSM does not attempt to remove spacemanagement from the file system.



User response: Determine the cause of orphaned stubfiles. Switch to the correct migration server and recallthe migrated files. Retry the operation.

ANS9082W program-name: error encountered whilereconciling file system file-system.

Explanation: TSM encountered an error performingreconciliation on the file system.


User response: Refer to other messages displayed ormessages in the log to correct the problem. Then retrythe operation.

ANS9083W program-name: cannot deactivate spacemanagement on file system file-system.

Explanation: TSM cannot deactivate spacemanagement on the file system.


User response: Correct the error if possible and retrythe operation.

ANS9084E program-name: file-system is not managedor not locally managed by spacemanagement.

Explanation: There is no entry for the file system inthe dsmmigfstab file or the file system is managed byanother node.

System action: TSM will not perform spacemanagement functions on this file system.

User response: Add space management to the filesystem, if appropriate, and then retry the operation. Ifthe file system is not locally managed, retry theoperation on the node managing the file system.

ANS9085E program-name: file system file-system isnot managed by space management.

Explanation: There is no entry for the file system inthe dsmmigfstab file.

System action: TSM will not perform spacemanagement functions on this file system.

User response: Add space management to the filesystem, if appropriate, and then retry the operation.

ANS9086E program-name: A DMAPI error occuredadding space management to file systemfile-system, It is possible DMAPI isdisabled on this file system. The systemset the error code: errno = errno-value

Explanation: TSM encountered an error and cannotadd space management to the file system.

System action: TSM Space management cannot beadded to file system.

User response: Verify that DMAPI is enabled for thisfile system and retry the operation.

ANS9087I Space management is successfullyadded to file system file-system.

Explanation: TSM has added space management tothe file system, and will now monitor its space usage.You can also perform other space managementoperations on this file system.



ANS9088W program-name: space management isalready active for file system filesystem.

Explanation: This message is issued when trying toadd space management to a filesystem with spacemanagement already activated. It is not possible to addspace management for a filesystem that already hasspace management activated.


User response: In case you wanted to update thefilesystem's space management configuration instead,use the appropriate update command.

ANS9089E The group backup validation failed.One or more files were added, removed,or changed during the backup.

Explanation: One or more files have been added,removed, or changed from the time WebSphere wasqueried to the time that all the data was sent to theTSM server. Check the dsmerror.log file for a list offiles that were added, removed, or changed.



ANS9090E program-name: file-system is not a validfile system name.

Explanation: TSM received an invalid file systemname. The file system is not mounted, or is notmounted correctly.


User response: Correct the file system name, and retrythe operation.

ANS9091E The WebSphere backup validationfailed. One or more files were added,removed, or changed during the backup.

Explanation: One or more files have been added,removed, or changed from the time WebSphere was



queried to the time that all the data was sent to theTSM server. Check the dsmerror.log file for a list offiles that were added, removed, or changed.


User response: Try the backup again. Do not installnew WebSphere applications or change the WebSphereconfiguration while in the backup window.

ANS9092W AES 128-bit Encryption is not beingused.

Explanation: AES 128-bit encryption is not being used.DES 56-bit encryption is being used instead.

System action: DES 56-bit Encryption is used insteadof AES 128-bit encryption.

User response: If the user wants to use AESencryption, then the user must install the IBM JRE inorder to enable AES encryption for the web client.

ANS9093W program-name: cannot update migrationcandidates list file-name.

Explanation: TSM cannot update the migrationcandidates list because not enough memory is availableto create a temporary file.


User response: Make some memory available byending some processes, and then retry the operation.

ANS9094W program-name: no candidates found infile system file-system.

Explanation: TSM found no files eligible for migrationin the file system after running dsmreconcile.



ANS9098E program-name: space management doesnot support file system file-system.

Explanation: TSM space management does notsupport this type of file system. Space managementsupports only true local file systems (e.g. JFS on AIX).Space management does not support other types of filesystems (AFS, NFS, etc).

System action: Processing of the file system stopped.


ANS9099E program-name: space management is notactive for file system file-system.

Explanation: TSM found the file system did not havespace management activated.

System action: Processing of that file system stopped.

User response: Reactivate space management for thefile system.

ANS9100E Unable to open file 'filename' for output.

Explanation: The file name specified cannot beopened.

System action: Make sure that user has access to writeto specified file, or use different file name.

User response: Output will not be saved. Pleasespecify different file or check permissions on chose file.

ANS9101E Migrated files matching 'file-name' couldnot be found.

Explanation: File name for search pattern can not befound in the TSM server database as a migrated file.

System action: No query result.

User response: Verify that the search patter is correct.

ANS9117E Virtual machine 'VM name' will not bebacked up because it contains at leastone of the following unsupportedspecial characters special characters

Explanation: The specified virtual machine containscharacters that are not supported for virtual machinebackup and restore operations.


User response: Rename the virtual machine so that itdoes not contain any of the specified special characters.

ANS9121I Activate completed.

Explanation: A Domino activate databases operationwas completed.

System action: TSM activated the databases.


ANS9126E program-name: cannot determine whetherspace management is active or inactivefor file-system due to error: error.

Explanation: The program 'program-name' indicatedin the message text was unable to obtain statistics forfile system 'file-system'. Therefore the program cannotdetermine whether space management is activated,deactivated, or globally deactivated on that file system.The message text includes a description of the Unixerrno error that occurred while trying to get the state ofspace management.

System action: TSM stops the operation.

User response: Verify that the file system is mountedand accessible. Using the appropriate tools for that file



system, check whether there are any I/O or otherintegrity errors on that file system. Then try theoperation again. If the operation fails, then a systemreboot might clear the error condition. If, after takingthese actions the problem persists, contact IBMtechnical support for assistance.

ANS9128I Inactivate logs completed.

Explanation: A Domino inactivate log operation wascompleted.

System action: TSM inactivated the log.


ANS9133E program name: space management alreadyactive for filesystem.

Explanation: This message is issued when trying toadd space management to a filesystem with spacemanagement already activated.


User response: Check the filesystem's spacemanagement configuration and consider updating it incase it does not match your needs. It is not possible toadd space management for a filesystem that alreadyhas space management activated.

ANS9134E program name: space management notactive for filesystem.

Explanation: The program requested the spacemanagement configuration for a file system wherespace management is not active.


User response: In case you entered the filesystemspecification, check for correct spelling. It is notpossible to perform space management actions on afilesystem with space management not activated.

ANS9135E program name: space management forfilesystem not controlled by the localnode.

Explanation: The program requested the spacemanagement configuration for a file system wherespace management is active, but not controlled by thelocal node. In cluster environments, some spacemanagement actions are allowed from the owner nodeonly.


User response: Determine the controller node for thisfilesystem and retry.

ANS9136E program name: could not removeconfiguration file for filesystem.

Explanation: During removal of space managementfor the given filesystem, this configuration file couldnot be removed.

System action: Space management could not bedeactivated for this filesystem.

User response: Determine the reason why the filecould not be removed and retry.

ANS9137I File: file-name is not premigrated.

Explanation: File must be premigrated to migrate it.

System action: The file was skipped.

User response: The migration of premigrated filesrequires that the file is in premigration state.

ANS9140E The migration options premigration andstub cannot be combined.

Explanation: The migration option premigration andstub are mutual exclusive. Both options end in differentresults for the same file.

System action: Command ends without changes to thefile.

User response: Use the migration optionspremigration and stub in different instances of thecommand.

ANS9145E Virtual machine will not be backed upbecause it has an empty name.

Explanation: The specified virtual machine name isempty. This is not supported for virtual machinebackup and restore operations.


User response: Rename the virtual machine so that itsname contains supported characters.

ANS9146E An RPC error has happened inprog-name executable! RPC error code:rpcStat-value, reason: rpcStat-explanation

Explanation: TSM executable got an RPC error andwas unable to continue the current operation.

System action: Processing of the current operation isstopped.

User response: Make sure that the appropriate RPCservices are up and running on your system. Forexample: - on Linux, run 'service portmap status' or'service rpcbind status' or 'systemctl status rpcbind'command depending on the Linux distribution in use; -on AIX, run 'lssrc -s portmap' command. If the RPC



error reason is "Program not registered", then youshould restart the HSM daemons via 'dsmmigfs restart'command.

ANS9147E program-name: cannot read file-spec: error.

Explanation: TSM cannot read this file.

System action: TSM cannot fully complete therequested operation.

User response: An error occurred reading an HSMmanaged file system status file. Verify that the filesystem is mounted and enabled for HSM and isactually managed by HSM and then try the operationagain. If the problem persists, contact IBM technicalsupport for further assistance. Provide the output fromthe mount, dsmdf and ls -l [file system name]commands.

ANS9148E program-name: cannot find mount pointfor file system file-system.

Explanation: TSM cannot find file system mountpoint.


User response: The specified file system is notcurrently mounted. Mount the file system and try theoperation again.

ANS9150I Archive log completed.

Explanation: A Domino archive log operation wascompleted.

System action: TSM archived the log.


ANS9151E An unexpected program error wasencountered .TSM function name : function-nameTSM function : function-descTSM return code : TSM-rcTSM file : file-name (line-number)

Explanation: None.


User response: Check error log for more information.Contact the TSM administrator with the informationprovided in this message.

ANS9152E program-name: cannot deactivate spacemanagement for whole system: error.

Explanation: Space management cannot bedeactivated for the whole machine.

System action: TSM cannot deactivate spacemanagement support.

User response: The HSM global status is inaccessible,possibly due to concurrent access. Try the operationagain. If the problem continues, examine the output ofthe shell command ps -aef as well as the contents of/etc/adsm/SpaceMan/config/dmiFSGlobalState.pid. Ifa pid is stored in this file and it does correspond to arunning process, remove the dmiFSGlobalState.pid fileand retry the operation. If the problem persists, rebootthe system and repeat the appropriate analysis for yourfile system type.

ANS9153E program-name: cannot reactivate spacemanagement for whole system: error.

Explanation: Space management cannot be reactivatedfor the whole machine.

System action: TSM cannot reactivate spacemanagement support.

User response: The HSM global status is inaccessible,possibly due to concurrent access. Try the operationagain. If the problem continues, examine the output ofthe shell command ps -aef as well as the contents of/etc/adsm/SpaceMan/config/dmiFSGlobalState.pid. Ifa pid is stored in this file and it does correspond to arunning process, remove the dmiFSGlobalState.pid fileand retry the operation. If the problem persists, rebootthe system and repeat the appropriate analysis for yourfile system type.

ANS9154E program-name: cannot deactivate spacemanagement for file system file-system:error.

Explanation: Space management cannot bedeactivated for the file system.

System action: TSM unable to deactivate spacemanagement support for the file system.

User response: The HSM file system status isinaccessible, possibly due to concurrent access. Try theoperation again. If the problem continues verify thatthe file system is mounted and that HSM is enabled onthe file system with the Unix shell commands mountand dsmdf. If the problem persists, reboot the systemand try the operation again.

ANS9155E program-name: cannot reactivate spacemanagement for file system file-system:error.

Explanation: Space management cannot be reactivatedfor the file system.

System action: TSM cannot reactivate spacemanagement support to the file system.

User response: The HSM file system status isinaccessible, possibly due to concurrent access. Try theoperation again. If the problem continues, verify thatthe file system is mounted and that HSM is enabled onthe file system with the Unix shell commands mount



and dsmdf. If the problem persists, reboot the systemand try the operation again.

ANS9156I Rollforward completed.

Explanation: A Domino DB2 rollforward operationwas completed.

System action: TSM rollforward the Domino DB2database log.


ANS9157W Please enter a valid filespace location

Explanation: This message will be seen when you runthe Pref editor from MFC GUI. This means that userhas not entered a required field which is filespacelocation path.

System action: TSM Enter required field

User response: Operation will not proceed till userenters required field

ANS9159E program-name: unable to create temporaryfile.

Explanation: TSM cannot create a temporary file.

System action: TSM cannot complete its operation.

User response: Check with the Unix mount shellcommand that /tmp and /etc exist as separate filesystems on your system. Use the df command to checkwhether they are full. Create additional space bydeleting files or increasing the file system size.

ANS9160E program-name: cannot write to temporaryfile or status filefile-spec: error.

Explanation: TSM cannot complete writing to thetemporary file.


User response: The Unix error code may provideguidance as to why the write failed. Use the Unixmount and df shell commands to verify that theassociated file system is mounted and has spaceavailable. If this message resulted from a shellcommand, mount the file system and create additionalspace if necessary, then retry the operation. If themessage did not result from a shell command, restartthe daemons. If the problem persists, reboot the system.

ANS9161E Invalid backupset file or device nameentered.

Explanation: The backupset file or device namespecified does not contain a valid backupset.


User response: Specify a file name or device thatcontains a valid backupset and retry the operation.

ANS9162W Object: 'dir-name' is skipped for recall: Itis a directory.

Explanation: The object is a directory. Spacemanagement does not recall directories.

System action: IBM Tivoli Storage Manager does notrecall this object because it is a directory.


ANS9163W program-name: Could not acquire therecall daemon session id.

Explanation: Could not set up the event dispositionfor the file system, because the recall daemon sessioncould not be acquired. It seems the recall daemon is notrunning. Recall requests will not be handled, whichmeans the TSM client for space management can't reactto recall requests for this file system.

System action: TSM could not set up the recall eventhandling. The recall event handling is not enabled forthis filesystem.

User response: Start or restart the recall daemon.

ANS9164W program-name: Could not acquire themonitor daemon session id.

Explanation: Could not set up the event dispositionfor the file system, because the monitor daemon sessioncould not be acquired. It seems the monitor daemon isnot running. Thus the thresholds for file system usagewill not be monitored and the NOSPACE event will notbe handled, which means the file system may run outof space.

System action: TSM could not set up the NOSPACEevent handling. The NOSPACE event handling is notenabled for this filesystem.

User response: Start or restart the monitor daemon.

ANS9165E program-name cannot open directorydirectory-spec due to the following error:error.

Explanation: The directory indicated in the messagetext cannot be opened. The message text includes adescription of the error that occurred.

System action: The requested operation is notcompleted.

User response: Try to correct the error condition thatis indicated in the message text, then try the operationagain. If the problem persists, contact IBM technicalsupport for further assistance.



ANS9166I A 'backup type' backup version backupdate 'datetime' is not consistent with localrepository and has been deleted fromthe server (object name='filespacenamepath-namefile-name', ID ='object-id:object-id').

Explanation: The specified backup instance of thenamed object is not valid with local repository contents.This could happen if local repository is modified or gotcorrupted on the client system. This backup can not berestored, therefore it will be deleted on the server.

System action: The specified backup object will bedeleted on the server. Processing will continue.


ANS9167W The client cache for adaptive subfilebackup is corrupt and cannot be used.

Explanation: The adaptive subfile cache has becomecorrupt. While the backup client can detect thecorruption, the reason for the corruption cannot bedetermined.

System action: The TSM client will proceed withstandard selective or incremental backup. The cachewill be rebuilt so that subsequent backups will use theadaptive subfile technique.

User response: If the problem persists, contact IBMtechnical support for assistance. Be prepared to providethe client error log, which will contain additionalmessages that might be useful for support to helpidentify the problem.

ANS9169E program-name: cannot create directorydirectory-spec, reason.

Explanation: TSM cannot create this directory.

System action: TSM does not create this directory.

User response: Verify that this directory does notalready exist, and that its parent directory has properpermissions.

ANS9170E program-name: file-system is not amounted local file system.

Explanation: TSM did not find that this file system isproperly mounted.

System action: TSM ignores the file system.

User response: Verify that this file system is local andmounted and activated properly.

ANS9171E An error internal to TSM has occurred.The following string is too long: error.

Explanation: None.

System action: The requested operation does notcomplete.

User response: A system reboot might clear up theproblem, after which the operation should be triedagain. If the problem persists, contact IBM technicalsupport for further assistance.

ANS9172I Backup system component '' is excludedfrom processing.

Explanation: You tried to back up the systemcomponent that was specified to be excluded frombackup.

System action: IBM Tivoli Storage Manager did notback up the system component.

User response: Verify the input keyword or the writername via the command line client and the Exclude lists.

ANS9173I Backup system component '' doesn'texist.

Explanation: You tried to back up the systemcomponent that is not installed or is not started.

System action: IBM Tivoli Storage Manager did notback up the system component.

User response: Verify the input keyword or the writername by using the GUI interface to expand the "SystemState" or "System Services" node.

ANS9174I A backup delete completed.

Explanation: A Backup delete was completed.

System action: TSM deleted backup files.

ANS9176I Backup delete is stopped by the user.

Explanation: You requested the backup deleteoperation be stopped.

System action: Archive delete stopped.


ANS9177W All data events for remote recallsrunning on node: 'cluster node ID',hostname: 'cluster node hostname' aregoing to be aborted.

Explanation: The remote node is not responding, soall DMAPI data events which are currently beingprocessed on this remote node should be aborted. Thiswarning is likely caused by an RPC communicationissue between the local node and the specified remotenode.



System action: The dsmrecalld distributor process isgoing to abort all data events (if any) which arecurrently being processed on the specified remote node.

User response: Ensure that the network and hostconnection are configured correctly. Then, retry therecall operation.

ANS9178E program-name cannot open file file-specdue to the following error: error.

Explanation: The program indicated in the messagetext was unable to open the specified file. The messagetext also includes a description of the error thatoccurred when it tried to open the file.


User response: Verify that the file system on whichthe file resides is mounted, then try the operationagain. A system reboot might clear up the problem. Ifthe problem persists, contact IBM technical support forfurther assistance.

ANS9179W The operation completed successfully.However, some error occurred oncreation of the required vApps list.

Explanation: One or more of the items included in thevApps specification were not found. This can be causedby a change in the vCD organizations configuration ora user mistake in the provided vApp spec.

System action: The operation completes successfully

User response: Check the local client error log for areason for the failure and check the commandspecification. Correct any issues and execute thecommand again.

ANS9180W An entry in the password file could notbe decrypted.

Explanation: The password failed decryptionvalidation.

System action: The password in the password file willbe ignored. You will be prompted for the password,unless the process is running in the background, suchas in scheduling mode.

User response: Enter the password when prompted.

ANS9182W Your customized client nodes listalready contains this node.Would you like to update it?

Explanation: The list of client nodes contains alreadythe specified client node. You cannot have two clientnodes with the same client node name in the samemachine.

System action: Updates or does not update the client

node, depending on the user response.

User response: Select "yes" to update the client node.Select "no" to cancel this operation.

ANS9183W Removing Space Management from'file-system' file systemmeans that all migrated data will berecalled from TSM Server 'server-name'Make sure that enough free space ispresent on this file system for therecalled data.Do you want to remove SpaceManagement from 'client-node' now?

Explanation: Removing Space Management from theselected file system means that all migrated data willbe recalled from the server.

System action: Prompts the user to confirm whenremoving Space Management from the selected filesystem.

User response: Make sure that enough free space ispresent on this file system for the recalled data.

ANS9184E program-name cannot allocate memorydue to the following error: error.

Explanation: A memory allocation error occurred. Themessage text includes a description of the error thatoccurred.


User response: Try the operation again. If the problemoccurs in an HSM daemon, restart the daemon, then trythe operation again. If the problem continues to occur,use your operating system's administrative tools tocheck virtual memory (swap space) on your system,and increase it if necessary. Check whether anapplication is consuming available virtual memory. Asystem reboot might also clear up the problem. If theproblem persists, contact IBM technical support forfurther assistance.

ANS9185W Master scout daemon is not running!

Explanation: A list of candidates files eligible formigration cannot be built because the master scoutdaemon is not running on the selected client node.

System action: Files are not automatically migrated tothe TSM server.

User response: Restart the master scout daemonmanually using the "dsmscoutd" command from acommand shell on the machine where SpaceManagement Agent is running.



ANS9186E program-name: cannot open mounted filesystem file-system: error.

Explanation: TSM cannot open mounted file system.

System action: TSM ignores the file system.

User response: Verify that this file system is mountedand activated properly.

ANS9187W Monitor daemon is not running!

Explanation: Files cannot be automatically migrated tothe TSM server or recalled from TSM server becausethe monitor daemon is not running on the selectedclient node.

System action: Files are not automatically migrated orrecalled from the TSM server.

User response: Restart the monitor daemon manuallyusing the "dsmmonitord" command from a commandshell on the machine where Space Management Agentis running.

ANS9201W LAN-free path failed.

Explanation: A LAN-free connection could not bemade.

System action: The system will connect to the serverwithout using the LAN-free path.

User response: Verify your LAN-free setup.

ANS9203E ENABLELANFREE can not be usedwhen HSM is installed.

Explanation: The TSM Client has detected that HSMis installed on the system. LAN-free is not a validoption when HSM is installed.

v This error occurs on AIX when this file is found:/usr/tivoli/tsm/client/hsm/bin/dsmrecalld

v This error occurs on Solaris when this file is found:/opt/tivoli/tsm/client/hsm/bin/dsmrecalld

System action: An invalid option is detected andprocessing stops.

User response: Remove the ENABLELANFREE optionfrom the system option file. ENABLELANFREE canonly be used when HSM is not installed.

ANS9206W User quota is reached!

Explanation: The maximum amount of data that canbe migrated and premigrated from this file system tothe TSM Server is reached.

System action: Files cannot be migrated to TSMserver.

User response: Use the File System Properties dialogto specify a different quota value.

ANS9220W Recall daemon is not running!

Explanation: Files cannot be recalled from TSM serverbecause the recall daemon is not running on theselected client node.

System action: Files are not recalled from the TSMserver.

User response: Restart the recall daemon manuallyusing the "dsmrecalld" command by a command shellon the machine where Space Management Agent isrunning.

ANS9227E Internal error loading the status:error-message

Explanation: An exception has been detected loadingthe status of space management activities.

System action: The status of the related activity is notloaded. The process continues to load the status at thenext refresh interval.


ANS9230E Communication error detected in themigration phase of this process!

Explanation: An unexpected error is occurred due toserver communication error in migration phase.



ANS9231E Processing error detected in themigration phase of this process!

Explanation: An unexpected error is occurred due tosome processing communication error.

System action: TSM will not migrate or premigratefiles from this file system.




ANS9233E Processing error detected in thepremigration phase of this process!

Explanation: An unexpected error is occurred due tosome processing communication error in thepremigration phase.

System action: TSM will not premigrate files from thisfile system.


ANS9236E Error detected performing reconciliationon this file system!

Explanation: An error is occurred performingreconciliation on the selected file system.

System action: TSM will not reconcile this file systemwith TSM server.


ANS9240W Could not acquire the serial number ofdisk 'disk-name' at LUN LUN-id.

Explanation: TSM was not able to determine the serialnumber of the specified disk. The disk may not supportSCSI inquiries of the Vital Product Data on page 0x80.

System action: Server-free data movement will not bepossible for data residing on the specified disk.


ANS9249E File 'file-namefile-namefile-name' accessedduring migration. File skipped.

Explanation: The specified file-name was not migratedbecause the file was accessed by another process duringthe attempt to migrate it.

System action: TSM left the file resident.

User response: If you want the file migrated, stop theprocess which is accessing the file and retry themigration.

ANS9250I File system 'file-system' reconciliationcompleted.

Explanation: TSM has finished reconciling the filesystem.



ANS9251E ProgramName: Cannot parsecommand-line options correctly.

Explanation: An internal program error occurredtrying to parse the command-line arguments.

System action: The program is not able to process therequest.

User response: Use the -h or -help option to see whatoptions are allowed on the command-line, then retrythe request.

ANS9252I Value of environment variable: envVar.

Explanation: None.



ANS9255I An empty status file will be generated.

Explanation: The HSM status file is missing or can notbe opened. An empty status file will be created.

System action: File data migration will continue towork normally.

User response: Please run dsmreconcile to create acomplete status file.

ANS9256E File 'file-namefile-namefile-name' iscurrently opened by another process.

Explanation: The file is locked by a migration or recalloperation. A file can be the object of only one recallprocess or one recall operation at a time.


User response: If this error is not a result of a parallelfile migration or recall operation, then this error mightbe due to the previous cancelled migration or recalloperation. In this case, restart the dsmrecalld daemonand try the operation again.

ANS9263W You cannot restore both active andinactive versions of System State.

Explanation: Restoring an active copy and inactivecopy of System State is not allowed.


User response: Select either the active copy or theinactive copy to perform restore operation.



ANS9264E Incremental backup of Virtual Machine'vmname' failed with RC rc

Explanation: The incremental backup of virtualmachine volumes failed.



ANS9265E Failure mounting Virtual Machine'vmname' with vcbMounter command.RC=rc

Explanation: The VMware vcbmount command failedto mount virtual machine disk.

System action: The backup of the virtual machine cannot continue. The next virtual machine in the vmlistwill be processed. The output of the vcbMountercommand will show the reason for the failure.

User response: Issue a vcbMounter command for thevirtual machine to determine the reason for the failure.Refer to the documentation for that message for moreinformation.

ANS9266E Failure initializing virtual machineenvironment. Can not findvcbMounter.exe command. RC=rc

Explanation: Failure initializing virtual machineenvironment. Can not find vcbMounter.exe command.The VMware Consolidated Backup Framework notinstalled or vcbMounter.exe command is not located incurrent PATH environment variable.

System action: The backup can not continue. Theoutput of the vcbMounter command will show thereason for the failure.

User response: Issue a vcbMounter command for thevirtual machine to determine the reason for the failure.Refer to the documentation for that message for moreinformation. The VMware Consolidated BackupFramework must be installed on the Backup Proxymachine. The installed location and the vcbMounter.exemust be located in the PATH environment variable. Thedefault location is C:\Program Files\VMware\VMwareConsolidated Backup Framework.

ANS9267E program-name: File system file-system hasexceeded its quota.

Explanation: TSM detects that the file system hasexceeded its quota. No more data can be migrated outof this file system.


User response: Recall some files, or ask the systemadministrator to increase the quota for this file system.

ANS9278E Failure processing vmList option. RC=rc

Explanation: Failure processing vmList option.


User response: Check for errors in the vmList optionvalue. Refer to the documentation for the vmList optionfor more information.

ANS9279E Failure locating Virtual Machine'vmname' volumes. Failed with RC=rc

Explanation: Virtual machine volumes can not found.Volume mount points are not available on BackupProxy machine.

System action: The backup of the virtual machine cannot continue. The next virtual machine in the vmlistwill be processed. The output of the vcbMountercommand will show the reason for the failure.

User response: Issue a vcbMounter command for thevirtual machine to determine the reason for the failure.Refer to the documentation for that message for moreinformation.

ANS9280E 'vmname' option must be set whenrunning this operation.

Explanation: A required option for the command ismissing.

System action: The operation can not continue.

User response: Set the missing option using thePreference Editor or the command line.

ANS9287E Invalid or unsupported device.

Explanation: The logical volume device is eitherinvalid or unsupported.Refer to the documentation for device type support forimage backup.


User response: For image backup source or imagerestore destination, specify a device of one of thesupported types.

ANS9288W File: file-name of logical sizefile-logical-size and allocated sizefile-allocated-size is too small to qualifyfor migration.

Explanation: To be eligible for migration, a file mustsatisfy all of the following size criteria:- The file logical size is larger than the value of thestubsize option.



- The space that a file occupies (the allocated size) is atleast as great as the value of the minmigfilesize option.

System action: IBM Tivoli Storage Manager does notmigrate this file because migration does not freeadditional space.

User response: Verify that the settings of the stubsizeoption and the minmigfilesize option are appropriatefor your migration requirements.

ANS9289W Object: 'dir-name' is skipped formigration: It is a directory.

Explanation: The object is a directory. Spacemanagement does not migrate directories.

System action: IBM Tivoli Storage Manager does notmigrate this object because it is a directory.


ANS9290W File: file-name is skipped for migration:The file type is either unknown orunsupported.

Explanation: The file either cannot be read, is not aregular file, or its type is unknown to the HSM client.The HSM client migrates only regular files and doesnot migrate directories, symbolic links, and special files.

System action: IBM Tivoli Storage Manager does notmigrate this file.


ANS9291E program-name: A conflicting spacemanagement program is alreadyrunning in the file-system file system.Re-run this program later in this filesystem.

Explanation: TSM detected another program runningin the file system that cannot run at the same time asthe program your tried to initiate. The followingprograms cannot run at the same time for a file system:

dsmreconcile

dsmautomig

dsmmigfs remove.

Also, dsmmigfs remove cannot run while a migrationprocess is running in the file system.

System action: TSM will not run the program at thistime.

User response: Try running the program later.

ANS9292E program-name: Cannot access lock filelock-file/lock-filelock-file: error

Explanation: TSM cannot access a lock file due to anerror. The lock file provides serialization of certain

programs to prevent conflicting processes from runningat the same time.

System action: TSM will not run the program at thistime.

User response: Check the permissions on thedirectories leading up to the lock file and also thepermissions on the program executable.

ANS9293E TSM space management cannot accessERRORPROG error-program:error

Explanation: TSM encountered an error trying toaccess the program specified with the ERRORPROGoption in your client system options file (dsm.sys). Thismessage will appear only the first time this erroroccurs.

System action: TSM cannot send a severe errormessage to the specified error message program.

User response: Check to make sure the program existsand that it accepts standard input when run. It isusually best if ERRORPROG specifies the fullyqualified file name of the program.

ANS9294I No files matching 'file-name' were found.

Explanation: You entered a search pattern or file namethat cannot be found in the local file system.


User response: Ensure that your search pattern iscorrect, or specify a new search string.

ANS9296W Performing image backup of the entirevolume for volume name. TheIMAGEGAPSIZE option and used blockimage backup is not supported fornon-JFS2 file systems on AIX.

Explanation: None.


User response: Refer to the client manual foradditional information regarding the IMAGEGAPSIZEoption and used block image backup.

ANS9297W File file-name is skipped for migration:No backup copy found.

Explanation: A management class is assigned to thefile with the attribute MIGREQUIRESBKUP set to YES.This option requires that there exists a current backupcopy of the file before migration. However, there is nobackup copy found on the migration server. This file isnot migrated. Note: IBM Tivoli Storage Manager checksonly the migration server for a backup copy. If themigration server and backup server are differentservers, IBM Tivoli Storage Manager does not find abackup copy of the file.




User response: Back up this file on the migrationserver, or assign a management class to this file thatdoes not require a current backup copy. Try theoperation again.

ANS9298W File file-name is skipped for migration:Backup copy found is not current.

Explanation: A management class is assigned to thefile with the attribute MIGREQUIRESBKUP set to YES.This option requires that there exists a current backupcopy of the file before migration. However, the backupcopy found on the migration server is an old version.This file is not migrated. Note: IBM Tivoli StorageManager checks only the migration server for a backupcopy. If the migration server and backup server aredifferent servers, there must be a valid backup copy ofthe file on the migration server.


User response: Back up the current file on themigration server, or assign a management class to thisfile that does not require a current backup copy. Retrythe operation.

ANS9299I Cannot get the number of migrated filesfor file system file-system.

Explanation: Failed to get the number of migratedfiles on the file system. The number is stored in thestatus file for the file system.

System action: If you are removing spacemanagement from the file system, processing stops.Space management is not removed.

User response: Run reconciliation to reconcile the filesystem. Retry operation.

ANS9300I Migrated files found in file systemfile-system.Check for any error encountered duringrecall.

Explanation: Remove space management failedbecause there are migrated files in the file system. TSMwas unable to recall any files, or some of the migratedfiles may have failed during a recall operation.

System action: TSM remove processing stops.

User response: Check for error messages that occurredduring the recall process, correct any problems, andretry the remove process.

ANS9301E Full VM backup of Virtual Machine'vmname' failed with RC rc




ANS9302E The Restore VM command does notsupport VMBACKUPTYPE=FILE data.VM File level restore must be run frominside the virtual machine or with the'asnodename' option.

Explanation: The Restore VM function not supportedfor file level data.

System action: The system does not process yourrequested action.

User response: Virtual machine File level restore mustbe run from inside the virtual machine or with theasnodename option. To process a full virtual machinerestore, issue the command withVMBACKUPTYPE=FULLVM.

ANS9303E Full VM restore of Virtual Machine'vmname' failed with RC rc

Explanation: The Full VM restore of virtual machinefailed.

System action: The full restore of the virtual machinefinished with failures. The next virtual machine in thevmlist will be processed. The reason for the failure iswritten to the local client error log.


ANS9304E VMware Converter tool not installed onsystem.

Explanation: VMware Converter tool install could notbe detected on system.

System action: The full virtual machine image fileshave been restored successfully at the specifiedlocation.

User response: No further action is necessary. The fullvirtual machine images files can be used by varioustools. VMware Converter tool can be installed onsystem.

ANS9305E An invalid Hyper-V VM name 'string'was entered.

Explanation: You entered a Hyper-V VM name thatcontains incorrect characters or contains wildcardcharacters.


User response: Enter a correct Hyper-V VM name.



ANS9306E An invalid Hyper-V VM list 'string' wasentered.

Explanation: You entered a Hyper-V VM list thatcontains incorrect characters or contains wildcardcharacters.


User response: Enter a correct Hyper-V VM list.

ANS9307E No Hyper-V VM name or VMListentered

Explanation: No Hyper-V VM name or VMListparameter was specified.


User response: Specify a correct Hyper-V VM name orVMList parameter.

ANS9308E No match found for the Hyper-V VMname or VMList 'string' entered

Explanation: No match found for the Hyper-V VMname or VMList parameter entered.


User response: Specify a correct Hyper-V VM name orVMList parameter.

ANS9309E Pick option specified but also a valuefor the Hyper-V VM name or VMList'string' entered

Explanation: You cannot specify the -pick option andalso include a Hyper-V VM name or VMList parameter.


User response: Specify the -pick option without aHyper-V VM name or VMList parameter.

ANS9311E No Hyper-V VMs exist on the TSMserver

Explanation: No filespaces representing a Hyper-VVirtual Machine currently exist on the TSM server.


User response: You must successfully backup aHyper-V Virtual Machine before using this command.

ANS9312S program-name: Cannot changeowner/group on file: file-name: error

Explanation: TSM cannot change the ownership orgroup, or both for the specified file. This change isnecessary for space management to run properly.

System action: TSM cannot continue processing.

User response: Ensure that directory permissions

allow the file owner or group to be changed. Reissuethe command.

ANS9313E program-name: The TMP directory is full.

Explanation: The TMP directory from the operatingsystem is full.

System action: TSM stops.

User response: Delete some files in the TMP directoryand retry the operation.

ANS9316T File system 'file-system' undeletecompleted.

Explanation: TSM has finished undeleting the filesystem.



ANS9331W VMware vCenter or ESX Server useridand password for VMC Host <host>VMC Userid <userid> could not be readfrom encrypted pwd file.

Explanation: VMware vCenter or ESX Server useridand password could not be read from encryptedpassword file.


User response: Use dsmc SET PASSWORD -type=VM'vCenter hostname' 'userid' 'password' to saveencrypted password.

ANS9332E VMware vCenter or ESX Server useridand password not set. Use dsmc SETPASSWORD -type=VM 'vCenterhostname' 'userid' 'password' to saveencrypted password.

Explanation: VMware vCenter or ESX Server useridand password could not be read from encryptedpassword file.


User response: Use dsmc SET PASSWORD -type=VM'vCenter hostname' 'userid' 'password' to saveencrypted password.

ANS9333E Unable to re-create 'file-name' as a stubfile due to Unix-system-call() failure;errno: error; reason: 'error-reason'.

Explanation: TSM was unable to re-create thespecified file as a stub due to an error.

System action: The processing continues with the nextfile.

User response: Please, look into the dsmerror.log for



further error details. If the affected file path doesn'texist, restore it from your backup (if any) or re-create itmanually, then re-try the operation. Make sure that thespecified file system is TSM space managed, writableand in consistent state.

ANS9334E Wrong alias 'alias-name' received fromthe server.

Explanation: TSM could not build a valid pathnamefor a migrated file due to the invalid alias receivedfrom the server.

System action: The processing continues with the nextfile.

User response: If possible, perform either an orphancheck reconcile or an inline incremental backup of theinitial file, so that the alias is updated on the server.Then, retry the operation. Otherwise, contact TSMsupport for further investigation and problemresolution.

ANS9347W Warning:'domain-keyword' specified onDomain will be ignored whenconnecting to VMware ESX/ESXi host.Connect to VMware vCenter to processthis domain.

Explanation: None.

System action: Domain keyword is ignored.

User response: Connect to VMware vCenter toprocess this domain.

ANS9350E Backup operation failed due to volumemixture.Please refer to explanation section foradditional information.

Explanation: IBM Tivoli Storage Manager failed tocreate the backup because of the mixture of volumeswas detected. Some volumes selected meet therequirements for importing snapshots only whenneeded and some do not. This situation occurs when abackup operation is requested and the "Import VSSsnapshots Only When Needed" feature is enabled andnot all the volumes involved in the backup operationare managed by a VSS Hardware Provider thatsupports transportable snapshots. Additionally thesituation can also occur in a clustered environmentduring a backup operation, when not all the volumesinvolved in the backup operation are managed by aVSS Hardware Provider that supports transportablesnapshots.


User response: Try the operation again by splitting thebackup operation. Ensure that all the volumes involvedin the backup operation are either managed by aHardware Provider that supports transportablesnapshots or that all the volumes involved in the

operation do not support transportable snapshots.Additionally you may also turn off the "Import VSSsnapshots Only When Needed" feature to allow thebackup to allow the mixure.

ANS9351E Data was not available on server andwas skipped.

Explanation: The data to be restored is not availableon the server, so it will not be restored.

System action: The data is skipped, and the restoreprocessing continues with the next object to be restored.


ANS9352E SAN or HOTADD was chosen as thetransport for at least one of the disks inthe operation, but the SAN policy is notOnlineAll for this datamover. SAN orHOTADD cannot be used unless theSAN policy is OnlineAll.

Explanation: SAN or HOTADD was chosen as thetransport because either the default transport settingwas used, or it was specified in theVMVSTORTRANSPORT option. In order to use SAN orHOTADD as the transport mode, the SAN policy mustbe set to OnlineAll.


User response: Set the SAN policy to OnlineAll, or setVMVSTORTRANSPORT to something other than SANor HOTADD, such as NBD. Then try the restoreoperation again.

ANS9354E The node or owner name 'node' specifiedin the SET ACCESS command exceedsthe maximum allowed length (64).

Explanation: An invalid node or owner name hasbeen entered in the SET ACCESS command.


User response: Enter the SET ACCESS commandusing the correct node or owner name.

ANS9355E VMware vStorage VI Web Service APIreported error message: vstor-api-msg

Explanation: The VMware vStorage VI Web ServiceAPI reported an error with the specified message text.


User response: Check the dsmerror log file foradditional information, and contact the IBM TivoliStorage Manager administrator with the informationprovided in this message.



ANS9356E A VMware vStorage API error wasreported.

Explanation: A VMware vStorage API was reported.See other messages displayed and logged for additionalinformation about the problem.



ANS9359W program-name: file-system: high thresholdhigh-threshold exceeds recommendedmaximum max-threshold maximumpercentage.

Explanation: System performance can be impacted.There can be delays from waiting for demandmigration.


User response: Set the migration high threshold lowerthan the file system capacity.

ANS9360W program-name: file-system: configuredlow-threshold low threshold is below therecommended minimum floor-percent lowthreshold.

Explanation: TSM low threshold is not recommendedto be less than teh minimum space required by this filesystem and may result in endless attempts to findmigration candidates. Usage of the file system may behigher than the recommended minimum of lowthreshold on GPFS and Veritas because these types offile system allocate some space for metadata.


User response: Set the migration low threshold higherthan the recommended-minimum size of the filesystem.

ANS9361W program-name: file-system: the configuredpre-mig premigration is greater than thedifference between the configuredlow-threshold low threshold and therecommended-minimum size of the filesystem Min_size.

Explanation: TSM premigration percentage below thelow threshold may not leave sufficient space for the filesystem, and can result in endless attempts to findmigration candidates. Usage of the file system may behigher than the recommended minimum of lowthreshold on GPFS and Veritas because these types offile system allocate some space for metadata.


User response: Lower the premigration setting.

ANS9362W program-name: file-system: MAXFILESmax-files is less than used inodes usedinodes in the file system. MAXFILESwill be set to the minimum possiblevalue.

Explanation: TSM The specified maxfiles value isbelow the number of files already existing in the filesystem. The value will be ignored, and CFI will defaultto the minimum possible size according to the numberof currently used inodes.


User response: Increase the value of maxfiles.

ANS9363W program-name: file-system: MAXFILESmax-files is more than files total availableinodes in the file system. MAXFILESwill be set to the maximum possiblevalue.

Explanation: TSM The specified maxfiles value isabove the number of available inodes in the file system.The value will be ignored, and CFI will default to themaximum size that corresponds to the number ofavailable inodes.


User response: Decrease the value of maxfiles.

ANS9364E Failure initializing virtual machineenvironment. Refer to dsmerror.log fordetailed error messages.

Explanation: Failure initializing virtual machineenvironment. Refer to dsmerror.log for detailed errormessages.


User response: Refer to dsmerror.log for detailed errormessage.

ANS9365E VMware vStorage API error for virtualmachine 'VM-name'.TSM function name : function-nameTSM file : file-name (line-number)API return code : TSM-rcAPI error message : function-desc

Explanation: None.





ANS9368W WARNING: VMware Host Userid<hostuserid> read from pwd file differentthan VMCUSER option value<vmcuserid>. Using VMCUSER optionvalue.

Explanation: None.



ANS9369W WARNING: VMware VirtualCenter orESX Server User Password for VMCHost <host> VMC Userid <userid> set inoptions file.

Explanation: None.



ANS9370W Use Preferences Editor or dsmc SETPASSWORD -type=VM 'VirtualCenterhostname' 'userid' 'password' to saveencrypted password.

Explanation: The VMCPW option was found either inan option file or on the command line. While thismethod of entry is allowed, it presents a security riskbecause the password is in plain text and notencrypted.

System action: The option is accepted and the VMCpassword is used in the current session.

User response: To save the encrypted password, usethe Preferences Editor VM Backup panel or thecommand:dsmc SET PASSWORD -type=VM 'VirtualCenterhostname' 'userid' 'password'

ANS9371I program-name: file-system: The specifiedMAXFILES value is 0. The CFI size willbe calculated automatically now.

Explanation: TSM The specified maxfiles value is 0,which means that the CFI size is managedautomatically now.



ANS9372E Unable to create the virtual machine tobe restored due to an invalid host name,datacenter name, or datastore name.

Explanation: IBM Tivoli Storage Manager was unableto create the virtual machine to be restored because aninvalid host name, datacenter name, or datastore name

was specified. Check the dsmerror log file forinformation on the specific reason for the failure.



ANS9373E VMware vStorage API environmentcould not be found.Install the VMware VDDK and copyVMware runtime libraries from theVDDK bin directory to TSM baclientdirectory.

Explanation: Failure initializing virtual machineenvironment.


User response: Make sure the VMware VDDK isinstalled and copy VMware runtime libraries fromVDDK bin directory to TSM baclient directory.

ANS9374E VMware vStorage virtual storage driverservice is not running or could not befound.Make sure VMware'vstor2-mntapi20-shared.sys' service isinstalled and running. Install theVMware vStorage API runtime files.

Explanation: Failure initializing VMware vStorage APIenvironment.


User response: Make sure the VMware'vstor2-mntapi20-shared.sys' service is installed andrunning. Install the VMware vStorage API runtimefiles.

ANS9376E The Backup VM command domainkeyword 'domain-keyword' was specified,but this domain does not contain anyvirtual machines. This error can alsooccur if the value for the VMHOSTparameter is not specified as an IPaddress or as a fully qualified domainname.

Explanation: The command cannot complete becausethe virtual machine could not be found.


User response: Try the operation again. Ensure thatthe value for the VMHOST parameter is specified as anIP address or as a fully qualified domain name. Thehost name that you specify must match the host nameas it is displayed in the vCenter server in the Host andClusters view. This could be the fully qualified host



name (FQDN), the shortened domain name, or the hostIP address.

ANS9377E No virtual machine is specified on thestring command or the virtual machinedomain list could not be processed.

Explanation: No virtual machine found with name orspecified in domain option.


User response: Specify a correct VM name or domainoption.

ANS9378E Unexpected error while fingeprintingthe data

Explanation: There was an error while fingerprintingthe data. See the error log for more information.


User response: Retry the operation. Retry theoperation without client-side deduplication. If theproblem persists, contact TSM technical support.

ANS9379E Unexpected error while deduplicatingthe data

Explanation: There was an error while deduplicatingthe data. See the error log for more information.


User response: Retry the operation. Retry theoperation without client-side deduplication. If theproblem persists, contact TSM technical support.

ANS9380E The virtual machine that was specifiedon the string command could not befound.

Explanation: The command cannot complete becausethe virtual machine could not be found.


User response: Try the operation again. Specify acorrect VM name or DOMAIN option. This error canalso be caused by incorrect settings for the VMHOST,VMHOSTCLUSTER, VMFOLDER or VMDATASTOREoptions. The VMHOST option value must be specifiedas an IP address or as a server name that is in fullyqualified domain name (FQDN) format. The host namethat you specify must match the host name as it isdisplayed in the vCenter server in the Host andClusters view. This could be the fully qualified hostname (FQDN), the shortened domain name, or the hostIP address.

ANS9381I The value set for vmlist option will bemigrated to the new domain option.

Explanation: New option has been set.



ANS9383E Required files for VMware vStoragevirtual machine backup could not befound.Run the TSM install selecting thevmwaretools feature or install theVMware VDDK.

Explanation: Failure initializing virtual machineenvironment.


User response: Run the TSM install selecting thevmwaretools feature. VMware.

ANS9384W Unable to get VMware Changed BlockTracking(CBT) data for virtual machine'virtual machine name'. Full VM backupcontinues, and includes both used andunused areas of the disk.

Explanation: IBM Tivoli Storage Manager was unableto obtain Changed Block Tracking(CBT) data for thespecified virtual machine. The backup continues, butinstead of backing up just the used blocks (in the fullVM backup case), or just the changed blocks (in theincremental VM backup case), the entire virtualmachine is backed up. This backup includes both theused and unused blocks of the disk.

System action: The backup continues.

User response: See the error log dsmerror.log forinformation about why the changed block data is notobtained.

ANS9385W Error returned from VMware vStorageAPI for virtual machine 'VM-name' invSphere API function__ns2__QueryChangedDiskAreas.RC=API return code, Detail message: APImessage

Explanation: None.

System action: CBT processing stops.




ANS9386W Changed block tracking is notsupported for virtual machine 'virtualmachine name'. A FULL backup of thedisk will be performed and will includeboth used and unused areas of the disk.

Explanation: IBM Tivoli Storage Manager was unableto obtain Changed Block Tracking(CBT) data for thespecified virtual machine because changed blocktracking is not supported. RDM disks in physicalmode, virtual disks attached to shared virtual SCSI bus,and VMs with hardware version 6 or earlier are notsupported. The backup continues, but instead ofbacking up just the used blocks (in the full VM backupcase), or just the changed blocks (in the incrementalVM backup case), the entire virtual machine is backedup. This backup includes both the used and unusedblocks of the disk.

System action: The backup continues.

User response: See the error log dsmerror.log forinformation about why the changed block data is notobtained.

ANS9387W An incremental backup for virtualmachine 'virtual machine name' is notpossible because changed blockinformation cannot be obtained. A fullVM backup is attempted instead.

Explanation: Changed block information is required toperform an incremental backup, but the informationcould not be obtained from the virtual machine. Theinformation can be missing if two nodes back up thesame virtual machine. One node runs a dailyincremental backup, and the other node runs a weeklyfull backup. After the weekly full backup runs, the nextdaily backup cannot obtain changed block information,so a full backup is run instead of an incrementalbackup. Subsequent daily backups will be incrementaluntil the next weekly full backup.

System action: The backup continues as a full backupinstead of an incremental backup.

User response: Search the IBM Tivoli Storage Managersupport site Tivoli Storage Manager Support Portal(http://www.ibm.com/support/entry/portal/product/tivoli/tivoli_storage_manager) for this message number,for other possible causes of this error.

ANS9388E The management class 'management classname' specified for the 'option name'option is invalid, or does not have abackup copy group.

Explanation: The management class name for thespecified option does not exist, or it exists but does nothave a valid backup copy group.


User response: Verify that the specified management

class name is valid, and that it contains a valid backupcopy group.

ANS9389W The DEDUP backup attempt wasunsuccessful for virtual machine 'virtualmachine name'. Retry #retry attempt numberwith DEDUP disabled.

Explanation: The attempt to backup the virtualmachine with DEDUP enabled was unsuccessful.Instead of failing the backup right away, an attempt isbeing made to backup the virtual machine withDEDUP disabled.

System action: Processing continues with DEDUPdisabled.

User response: Check the log files for messages as towhy DEDUP failed. If future attempts to backup usingDEDUP fail, contact your system administator.

ANS9390W The DEDUP backup attempt wasunsuccessful for virtual machine 'virtualmachine name'. Retry #retry attempt numberwith DEDUP still enabled.

Explanation: The attempt to backup the virtualmachine with DEDUP enabled was unsuccessful.Instead of failing the backup right away, an attempt isbeing made to retry the backup of the virtual machinewith DEDUP still enabled.

System action: Processing continues with DEDUP stillenabled.

User response: Check the log files for messages as towhy DEDUP failed. If future attempts to backup usingDEDUP fail, contact your system administator.

ANS9391W Linux guest OS with EFI Boot enabledis not fully supported by TSM VMwarebackup. Manual steps may be requiredfollowing restore to enable the virtualmachine to power on correctly.

Explanation: A restored Linux guest OS with EFI bootenabled may not successfully start. Manual steps arerequired to successfully boot the guest OS.

System action: Restore processing continues.

User response: Following guest OS restore: removeand reattach the guest Linux boot disk, select GuestBoot Option to enter EFI setup configuration on nextboot, power on the guest, enter EFI Boot Maintenance,add Boot Device, select unnamed volume, give it alabel, save and commit changes, continue with boot.

ANS9392W No backupset name entered.

Explanation: You must provide a backupset for thisoperation.







User response: Specify a valid backupset name.

ANS9393W Incorrect backupset name entered.

Explanation: The backupset name provided wasinvalid. Wildcards are not allowed.


User response: Specify a valid backupset name.

ANS9394W No backupset file or device nameentered.

Explanation: You must provide a backupset file ordevice name for this operation.


User response: Specify a valid backupset file or devicename.

ANS9395E The filespace has been migrated to theincremental forever model;MODE=FULL and MODE=INCR are notvalid.

Explanation: You must run only incremental foreverbackup types (IFINCR or IFFULL) if the filespace hasbeen migrated to the incremental forever type.


User response: Specify either MODE=IFFULL orMODE=IFINCR.

ANS9396W Virtual machine 'VM' is not running.IBM Tivoli Storage ManagerApplication Protection will not be usedwhile backing up this VM.

Explanation: IBM Tivoli Storage Manager ApplicationProtection can only protect VMs that are running.

System action: IBM Tivoli Storage ManagerApplication Protection uses the VMWare tools toprovide application consistency.

User response: Turn on the virtual machine or excludeit from TSM application protection by removing theINCLUDE.VMTSMVSS option for this virtual machine.If you want logs to be truncated useINCLUDE.VMTSMVSS to protect this machine.

ANS9397W TSM application protection cannotprotect this machine. Virtual machine'VM' does not have operating system orapplications supported by TSMapplication protection.

Explanation: The application protection can be usedonly for virtual machines that have operating systemsor applications that are supported by IBM TivoliStorage Manager application protection. Refer to the

product documentation for the list of supportedoperating systems and applications.

System action: IBM Tivoli Storage Manager will usethe VMware Tools to provide application consistency.

User response: Exclude the virtual machine fromapplication protection by removing theINCLUDE.VMTSMVSS option for this virtual machine.

ANS9398E IBM Tivoli Storage Manager applicationprotection failed to initialize on virtualmachine 'VM'. See the error log for moredetails.

Explanation: TSM application protection encounteredan error during initialization.


User response: See the TSM error log for more details.Correct the error(s) and try the operation again.

ANS9399W program-name: lock file access error foroperation value on path value value witherrno text value.

Explanation: A lock file operation has failed.

System action: TSM logs the condition and continuesprocessing, or exits if directory not found.

User response: Correct the configuration.

ANS9401E program-name: Cannot kill recall daemon.

Explanation: TSM A request for killing the recalldaemon failed. This may occur during node failover.


User response: Continue with normal operation unlessfurther errors occur.

ANS9402E program-name: Cannot notify process nameto recover HSM operations on a failingnode.

Explanation: In order to assume the functionality of afailing partner node, the dsmwatchd daemon mustnotify the local daemons.


User response: Communication cannot be establishedwith the HSM daemon specified in this message. Checkwhether the target daemon is running. Start or restartthe target daemon as appropriate. If the problempersists, restart the GPFS cluster.



ANS9404E Error creating the specified VirtualMachine. See log files for moreinformation.

Explanation: An error was encountered creating theVirtual Machine. Look in the dsmerror.log foradditional information on why the Virtual Machinecould not be created.


User response: Check the dsmerror.log for morespecific messages on why the virtual machine could notbe created.

ANS9405I program-name: The takeover of filesystemfile system started.

Explanation: The local activation of the specified filesystem started successfully.

System action: TSM on the local node will try toactivate the file system that is space managed onanother node.


ANS9410W VMware Tools are either not runnningor out-of-date on virtual machine 'VM'.IBM Tivoli Storage Manager applicationprotection cannot be used.

Explanation: IBM Tivoli Storage Manager applicationprotection requires that VMware tools are installed andrunning with an up-to-date version on the virtualmachine.

System action: TSM will not provide applicationconsistency. Application logs are not truncated.

User response: Install and/or upgrade and/or startVMware Tools on the virtual machine or exclude itfrom the application protection by removing theINCLUDE.VMTSMVSS option for this virtual machine.

ANS9411E VSS provider registration failed.Command 'command' failed withWindows RC=return code

Explanation: IBM Tivoli Storage Manager was unableto register the VSS provider on the virtual machine.


User response: Restart the virtual machine and try theoperation again.

ANS9412E program-name: Failover is disabled on thelocal machine. Aborting failover ...

Explanation: TSM Failover operations were disabledeither by the system or the user.


User response: Check failover policy if necessary.

ANS9415E Failed to copy 'source' to 'destination' withVMware RC=rc on virtual machine 'guestVM name'.

Explanation: IBM Tivoli Storage Manager was unableto copy a file to the virtual machine.


User response: Verify that the source file exists andthe destination is accessible. Restart the virtual machineand try the operation again.

ANS9416E Cannot create the directory 'source' onthe virtual machine with WindowsRC=rc

Explanation: IBM Tivoli Storage Manager client wasunable to create the specified directory on the virtualmachine. It is possible that the directory exists and islocked by a process.


User response: Verify the the specified directory doesnot exist on the virtual machine. Restart the virtualmachine and try the operation again.

ANS9417E IBM Tivoli Storage Manager applicationprotection could not freeze the VSSwriters on the virtual machine named'VM'. See the TSM error log for moredetails.

Explanation: IBM Tivoli Storage Manager applicationprotection encountered an error while freezing the VSSwriters.


User response: Use the 'vssadmin list writers'command to determine if any VSS writers detect errorson he virtual machine. Restart the VM. Retry theoperation. If the retry fails, see the error log for detailsabout the errors.

ANS9422I program-name: The rollback of filesystemfile system started.

Explanation: The local activation of the specified filesystem started successfully.

System action: TSM on the local node will try toactivate the file system that is space managed onanother node.




ANS9428E program-name: The takeover of filesystemfile system failed to start.

Explanation: The local activation of the specified filesystem failed to start. Please, note that only file systemswhich are space managed on another node within thesame cluster can be taken over. Additionally, the filesystem must be mounted locally.

System action: TSM will not take over the file system.

User response: Make sure the file system is mountedlocally and managed with the TSM client for spacemanagement on another node within the same clusterand retry the operation.

ANS9431E IBM Tivoli Storage Manager applicationprotection failed to thaw VSS writers onvirtual machine 'VM'. See the TSM errorlog for more details.

Explanation: IBM Tivoli Storage Manager applicationprotection encountered an error while thawing VSSwriters.


User response: See the error log for more details.Verify that all VSS writers are not reporitng errors byrunning command 'vssadmin list writers'. Restart thevirtual machine and try the operation again. If the retryfails, see the error log for details about the errors.

ANS9432W IBM Tivoli Storage Manager applicationprotection failed to truncate applicationlogs on virtual machine 'VM'.

Explanation: IBM Tivoli Storage Manager applicationprotection encountered an error while completing VSSbackup operation. The applications were successfullyquiesced, but their logs were not truncated.

System action: Application logs are not truncated.

User response: See the TSM error log for more details.Verify that all VSS writers are not reporting errors byrunning command 'vssadmin list writers'. Restart thevirtual machine and try the operation again. If the retryfails, see the error log for details about the errors. Onthe guest VM, verify that a mounted volume is notonline. Use the Recovery Agent to dismount andremove any existing mount directories. Then, try thebackup operation again.

ANS9433E program-name: dm_send_msg failed witherrno Errno.

Explanation: Unable to execute DMApi call.

System action: Aborting operation.

User response: Check consistency of the GPFSdaemon.

ANS9443E program-name: The operation cannot beexecuted in a deactivated failoverenvironment.

Explanation: The operation relies on an active failoverenvironment.

System action: Aborting operation.

User response: Run dsmmigfs enableFailover on thelocal node and repeat the operation.

ANS9450W program-name: No eligible filesystem fortakeover.

Explanation: None of the locally mounted GPFSfilesystems matches with the remotely managedfilesystems of the failure node.

System action: Aborting takeover operation.

User response: Check that the filesystems of theremote failure node get managed elsewhere within thenode set.

ANS9451E program-name: GPFS or the SP switch isdown locally. Aborting takeoveractivities ...

Explanation: TSM GPFS is not functional locally.


User response: Check switch and VSD status. Thelocal system must be unfenced.

ANS9452E program-name: The DMApi is notfunctional locally. Aborting takeoveractivities ...

Explanation: The operation stopped because theDMApi interface is not accessible.


User response: Check GPFS status.

ANS9453E program-name: Could not determine theGPFS storage pool id for file 'file-path'.Reason: reason

Explanation: The processed file does not exist or islocated on a file system without storage pool support.

System action: The requested operation stops.

User response: Please check the input parameters andif DMAPI is enabled on the file system.

ANS9457E program-name: Could not determine thestorage pools of file system 'file-system'.Reason: reason

Explanation: The specified file system is not a GPFSfile system or has an old GPFS version.




User response: Please update to a supported versionof GPFS.

ANS9459E Using the specified MAXCANDIDATESparameter would produce anout-of-spacecondition in the parent filesystem of/etc/adsm/SpaceMan/candidatesPool.Based onthe current free space situation themaximum value for theMAXCANDIDATES parameter is value.

Explanation: TSM The automigration candidate poolsfor the selected filesystem require MAXCANDIDATES/10 KB plus a safety buffer of 5 MB of memory under/etc/adsm/SpaceMan/candidatesPool, which exceedsthe available space.

System action: TSM Abort operation.

User response: Increase the filesystem size or choose asmaller value for the MAXCANDIDATES parameter.You may also create a dedicated filesystem withsufficient space for the migration pools under/etc/adsm/SpaceMan/candidatesPool. Kill thedsmscout processes after performing this option.

ANS9462E Failover functionality is not supportedwith this HSM release.

Explanation: The TSM user ran dsmmigfs with thefailover flag on an unsupported platform.

System action: TSM ends the operation.


ANS9469E Warning! Unable to write a completemigration candidate list due to lowspace in the parent filesystem of name.

Explanation: TSM Low space in filesystem whichstores the migration candidates files.

System action: TSM The executable writes a partialmigration candidates list.

User response: Increase the filesystem size or create adedicated filesystem with sufficient size under thegiven path.

ANS9474E program-name: Lost my session witherrno: errno . Trying to recover.

Explanation: The DMAPI session is not valid.

System action: Trying to recover session.

User response: Check the failure node. You mighthave to recover the local GPFS daemon.

ANS9475W IBM Tivoli Storage Manager applicationprotection failed to cleanup after a VSSbackup on virtual machine VM.

Explanation: IBM Tivoli Storage Manager applicationprotection encountered an error while cleaning up aftera VSS backup operation.

System action: None

User response: See the TSM error log for more details.Restart the virtual machine and try the operation again.If the problem persists, contact IBM technical supportfor further assistance.

ANS9476I program-name: Recovered my DM sessionsid.

Explanation: DMAPI session is recovered.



ANS9480E program-name: The rollback of filesystemfile system failed to start.

Explanation: The local activation of the specified filesystem failed to start. Please, note that a rollback canonly be performed after the space management of thefile system was moved from the local node to anothernode during failover. Additionally, the file system mustbe mounted locally.

System action: TSM will not roll back the file system.

User response: Make sure the file system is mountedlocally and managed with the TSM client for spacemanagement on another node within the same clusterand retry the operation.

ANS9487W program-name: cannot query the right onsession session for file handle = filehandletoken = token. Reason : error

Explanation: TSM space management cannot querythe right on a file.

System action: Processing of the file is interrupted.


ANS9488E Java Runtime Environment (JRE) wasnot found. File VM does not exist.

Explanation: JRE was not found in the TSMinstallation directory.


User response: Re-install the product or install arequired version of JRE and try again. If JRE is alreadyinstalled on your machine, then make sure the PATHenvironment variable contains path to javaw.exe.



ANS9489E Java Runtime Environment (JRE) wasnot found.

Explanation: JRE was not found.


User response: If you have already installed JRE,please verify that the \"java\" executable is set in thesystem PATH, otherwise install the required JREversion.

ANS9490E Cannot find httpagent.jar in the TSMclient installation directory.

Explanation: The required file was not found.


User response: Re-install the product or install arequired version of JRE and try again.

ANS9491E The password credentials for virtualmachine 'guest VM name' could not befound. Use dsmc SET PASSWORD-type=VMGUEST 'VM guest name''userid' 'password' to save encryptedpassword.

Explanation: The required password was not found.


User response: Use dsmc SET PASSWORD-type=VMGUEST 'VM guest name' 'userid' 'password'to save encrypted password. And then retry the'backup vm' operation.

ANS9492E Destination size is not equal to source

Explanation: The space allocation for the selecteddestination is not the same as the source.


User response: Choose a different destination which isequal in size to the source.

ANS9493E The credentials found for virtualmachine 'guest VM name' are incorrect.Verify the credentials and use dsmc SETPASSWORD -type=VMGUEST 'VMguest name' 'userid' 'password' toupdate the username and password.

Explanation: The supplied credentials are incorrect.Failed to authenticate to guest VM using thesecredentials.


User response: Use dsmc SET PASSWORD-type=VMGUEST 'VM guest name' 'userid' 'password'to update the username and password. And then retrythe 'backup vm' operation.

ANS9494E Command 'command' completed withRC=return code on virtual machine 'guestVM name'.

Explanation: A remote command either timed out orfailed.


User response: Increase the value of VMTIMEOUToption and try the operation again.

ANS9495E Failed to login to virtual machine 'guestVM name' because the VMware Tools arenot running in the guest machine.Verify that the VMware tools arerunning and that no other program hasaccess or is making any changes to thisVM.

Explanation: Failed to login to virtual machinebecause the VMware Tools are not running in the guestmachine.


User response: Make sure that the VMware tools arerunning and that no other program has access or ismaking changes to this VM. And then retry the 'backupvm' operation.

ANS9496E Unable to lock virtual machine VM forapplication protection.

Explanation: The virtual machine is being backed upby another process. Only one process is allowed to useTSM application protection during a backup of avirtual machine at a time.


User response: There is already another virtualmachine backup in process via another datamover.Please wait for the other virtual machine backup tocomplete and re-try the operation. Or there was a crashor CTRL+C during the previous virutal machinebackup. Please wait 10 minutes and re-try theoperation.

ANS9497W Virtual machine 'VM' resides on an ESXServer or vCenter that is not supportedby TSM application protection. IBMTivoli Storage Manager applicationprotection will not be used.

Explanation: Refer to the product documentation forthe list of supported ESX and vCenter versions.


User response: Exclude the virtual machine fromapplication protection by removing theINCLUDE.VMTSMVSS option for this virtual machine.



ANS9498W A valid IBM Tivoli Storage Manager forVirtual Environments license file(license-file) cannot be located. IBMTivoli Storage Manager applicationprotection will not be used.

Explanation: The license file was not found, or cannotbe opened because of permissions, or the file iscorrupted.



ANS9499W VMware tools on virtual machine 'VM'need to be updated. IBM Tivoli StorageManager application protection will notbe used.

Explanation: IBM Tivoli Storage Manager applicationprotection requires that VMware Tools are up to date.


User response: Update VMware Tools on the virtualmachine

ANS9500W program-name: cannot disposition themount event. Reason: error

Explanation: The system wide mount event could notbe dispositioned. Mount events will not be received bythis daemon.


User response: Try to resolve the problem and restartthe recall daemon. If the problem cannot be resolvedimmediately, kill and restart the recall daemon after anTSM space management supported file system has beenadded using dsmmigfs or after a file system has beenmounted using the mount command.

ANS9501W program-name: cannot set eventdisposition on session session for filesystem mountdirtoken = token. Reason : error

Explanation: Events could not be dispositioned on thefile system. No events will be received for thisfilesystem. HSM is not enabled for this file system.


User response: The file system must be one of thesupported native file systems in order for the TSMspace management to support it. Verify that the mountoptions the file system are correct. Correct the problemand remount the file system.

ANS9502W program-name: cannot remove eventdisposition on session session for filesystem mountdirtoken = token. Reason : error

Explanation: Event dispositions could not be removedfrom the file system.


User response: Verify that the file system is mountedand that dmapi is enabled on that file system. If theproblem persists, unmount and remount the filesystem, then try the operation again. If the problem stillpersists, reboot the system.

ANS9503I program-name: events have been set anddispositioned on session session for filesystem filesystem-name

Explanation: Setting events and dispositioning theseon a DM session enables the file system for TSM spacemanagement support.



ANS9504W program-name: The file systemfilesystem-name is not mounted or ismounted with wrong options.

Explanation: Either the file system is not mounted orit has been mounted with incorrect options.


User response: Mount the file system or remount itwith corrected mount options.

ANS9505E program-name: cannot initialize theDMAPI interface. Reason: error

Explanation: TSM client failed to performimplementation-defined initialization of the DMAPIinterface.

System action: The dm_init_service() function failed.

User response: If you are running TSM as a non-rootuser and you have TSM space management clientinstalled, please, make sure that the dsmrootd daemonis up and running, then retry the operation. If youdon't have TSM space management client installed,retry the operation under the root user authority.

ANS9506E program-name: The provided filespaceargument 'argument' has an invalidformat.

Explanation: Occurs if you are on a GPFS file systemand the file system parameter was not in the correctformat.




User response: See the dsmautomig documentationfor the correct syntax.

ANS9507E program-name: cannot request the righton session session for file handlefilehandletoken = token. Reason : error

Explanation: TSM space management cannot requestthe required right on a file.



ANS9508W program-name: cannot release the right onsession session for file handle = filehandletoken = token. Reason : error

Explanation: TSM space management cannot releasethe right on a file.



ANS9509W program-name: received an unexpectedevent of type event-type on sessionsession.

Explanation: TSM space management daemonreceived an unexpected event. This event has not beendispositioned.

System action: TSM ignores event and continues.


ANS9510E program-name: cannot get event messagesfrom session session, expected maxmessage-length = msglen, returnedmessage-length = return-length. Reason :error

Explanation: TSM space management encountered anerror while trying to receive a message on a DMsession.



ANS9511E program-name: cannot read DM attributeson session session forfile: name = name handle = handletoken = token. Reason : error

Explanation: TSM space management cannot read theDM attributes of a DM object, usually a file. If the filename is not available, it will be displayed as an emptystring or as <NA>.



ANS9512E program-name: cannot set DM attributeson session session forfile handle = filehandle token = token.Reason : error

Explanation: TSM space management cannot set DMattributes for a DM object, usually a file.



ANS9513E program-name: cannot remove DMattributes on session session forfile handle = filehandle token = token.Reason : error

Explanation: TSM space management cannot removeDM attributes for a DM object, usually a file.



ANS9514E program-name: cannot create a file handlefrom path. Reason: error

Explanation: TSM space management cannot create afile handle from the given file.



ANS9515E program-name: cannot set the migrationinformation. Reason: error

Explanation: TSM space management cannot set themigration information of a file, because spacemanagement cannot create a file handle from the fileand/or from the file system.



ANS9516E program-name: cannot create an userevent message on session session.Reason: error

Explanation: TSM space management cannot create anuser event message, needed to reference rights on a fileto be processed.



ANS9518E program-name: cannot respond to anevent message on session session usingtoken tokenReason : error

Explanation: An event message could not beresponded to (returned to the system).



System action: TSM space management continues.

User response: If a user process is unexpectedlyblocked and cannot be killed, see your systemadministrator.

ANS9519W program-name: cannot set eventlist for afile system on session sessiontoken = token fs-handle = fs-handle.Reason : error

Explanation: An eventlist could not be set on a filesystem. None of the events will be generated by thesystem on this file system.


User response: Try the operation again. If the problempersists, verify that the file system is mounted withdmapi enabled. If the problem still persists, reboot thesystem.

ANS9520E program-name: cannot set a managedregion on session sessionfor file handle = filehandle token = token.Reason : error

Explanation: A managed region could not be set on afile. No events will be generated for this file.



ANS9521E program-name: cannot get the fileattributes on session sessionfor file handle = handle token = token.Reason : error

Explanation: TSM space management cannot read theattributes of a file.



ANS9522E program-name: can not create a filesystem handle from path. Reason: error

Explanation: TSM can not create a file system handlefrom the file system name. If Reason is Operation notpermitted, the dmapi functionality may be disabled forthe file system.

System action: Processing of the file system isinterrupted.

User response: If Reason is Operation not permitted,enable dmapi functionality for the file system and retry.

ANS9523E program-name: is unable to verify thestub size for the file on session sessionfile handle = filehandle token = token.Reason : error

Explanation: A correct stub size could not bedetermined by the system.

System action: TSM stops migration of the file.

User response: Try the operation again. If the problempersists, verify that the file system is mounted withdmapi enabled. If the problem still persists, restart thesystem.

ANS9524W program-name: adjusted stubsize to anallowed value on session sessionfile handle = filehandle token = tokenold stubsize = old-size new stubsize =new-size

Explanation: The predefined stubsize for the fileshould be corrected to accommodate to the boundaryand rounding constraints imposed by the DMAPIimplementation. TSM space management can alsochange the stubsize during migration if the predefinedstubsize value is larger than the logical file size.



ANS9525E program-name: is unable to create a stubfile on session sessionfor file handle = handle token = token.Reason : error

Explanation: An error occurred while creating a stubfile.



ANS9526E program-name: cannot open the state filefilename for writing. Reason: error

Explanation: The global or file system state file couldnot be opened.

System action: TSM stops processing.


ANS9527E program-name: cannot write to the statefile filename. Reason: error

Explanation: TSM space management could not writeto the state file.





ANS9528W program-name: cannot read from the statefile filename.. The file is corrupted and will berecreated.

Explanation: TSM space management could not readfrom the state file.



ANS9529W program-name: cannot obtain the handleof a file system state file

Explanation: TSM space management could not findthe handle of a file system state file that is stored in theglobal state file. This can occur if either spacemanagement is querying a file system that has no HSMsupport added, or the file system state file is corrupted,or the global state file is corrupted.

System action: TSM continues or stops processing,depending on the situation.


ANS9530W program-name: cannot remove an entryfor file-system from the global state file.

Explanation: The entry for the file system in thedmiFSGlobalState file cannot be removed. Possiblereasons:

v There is not enough memory to create temporary filename for temporary file system table.

v There is not enough free space or inodes to createtemporary file system table

v The real or temporary file system table files cannotbe opened.

System action: TSM does not remove the entry fromthe global state file.


ANS9531E program-name: cannot create a DMsession: old session = oldsessionsession info = session-info. Reason : error

Explanation: TSM space management could not createa DM session.


User response: Try the operation again. If the problempersists restart the system.

ANS9532W program-name: cannot destroy the sessionsession. Reason: error

Explanation: TSM space management could notdestroy a DM session.



ANS9533W program-name: failed getting all sessions.Reason: error

Explanation: TSM space management could not get allDM sessions on the system.



ANS9534W program-name: cannot query a session.Reason: error

Explanation: TSM space management could not querya DM session on the system.



ANS9535E program-name: a file handle could not becreated from the file descriptorfile-descriptor.Reason: error

Explanation: TSM space management could not createa file handle.





ANS9536E program-name: cannot query an eventmessage on session session. Reason: error

Explanation: TSM space management cannot query anevent message, needed to determine whether nfs call.



ANS9537E program-name: Invalid storage pool'storagepool' for file system 'filesystem'.

Explanation: No storage pool with that name exists onthe specified file system.


User response: Please make sure the storage poolexists on the specified file system.

ANS9538W program-name: request request for DM fileattributes not recognized

Explanation: An unknown request type has beenencountered that cannot be handled.



ANS9539E program-name: cannot create a file systemhandle from thefile handle = filehandle. Reason : error

Explanation: A file system handle could not becreated from a file handle.



ANS9542E program-name: the file attributes couldnot be set on session sessionfor file handle = filehandle token = tokenflag = flagReason : error

Explanation: TSM space management could notupdate file attributes.



ANS9543W program-name: The TSM client needsblocks-num1 free file system blocks to beable to handle the nospace condition onfile system filesystem-name, errno:error-num, reason: error-str. Currentlyblocks-num2 blocks with a block size ofblock-size bytes are available.

Explanation: Either the TSM client is not able to getstatus information for the file system or there isinsufficient space in the file system. The messagereports zero blocks if the file system status informationis not available.


User response: If there is insufficient space in the filesystem, free the required space or increase the filesystem capacity. If this is due to an input output error,perform an appropriate file system check (e.g. fsck).Then try the operation again.

ANS9545E program-name: cannot get a lock forlockdirlockfile to continue processing.

Explanation: TSM space management could not obtaina lock for a file.


User response: Try the operation again. If problempersists, restart HSM. If problem still persists, restartthe system.

ANS9546E IBM Tivoli Storage Manager cannotperform instant restore becauseMicrosoft Active Directory DomainController was detected on virtualmachine.

Explanation: The virtual machine contains MicrosoftActive Directory Domain Controller. It cannot berecovered using instant restore.


User response: Use a regular restore to recover thevirtaul machine.

ANS9548W Cannot complete remote file access forinode:'inode number', alias:'file name'.

Explanation: TSM space management cannot completethe remote file access. The file may be migrated to anTSM migration server that could be temporarilyunavailable. The file may be an orphan stub.

System action: TSM terminates the current operation.

User response: Check to see whether the server hasbeen disabled by the system administrator, then retrythe operation. To check whether the file is an orphanstub or not, run dsmreconcile for the affected filesystem. Note: the file alias may be displayed as'unavailable' if the connection to server is unavailableor 'orphan' if the appropriate file copy cannot belocated on a particular migration server.



ANS9550W File recall has been discontinued.

Explanation: Recall stops because the file beingrecalled would cause the file system to run out ofspace.

System action: TSM terminates the current operation.

User response: Increase the file system space, orremove unneeded files, or wait until spacemanagement has migrated files off the file system bydemand or threshold migration, or manually migratefiles. Then retry the operation.

ANS9552E program-name: cannot add spacemanagement to file-system; path includesnon-local file system.

Explanation: An attempt was made to add spacemanagement to a file system whose path containsnon-local elements.


User response: File system must be entirely local.

ANS9554E program-name: command for file systemmountdirReason : error

Explanation: An attempt to enable or disable xdsmapi functionality on the file system failed. If the attemptwas to enable HSM, then HSM is not enabled for thisfile system.


User response: The file system must be of type JFS2 inorder for the TSM Space Management to successfullyset the managed attribute. Verify that the file system isof the correct type.

ANS9555E Guest name VM does not match anyvirtual machines.

Explanation: TSM application protection requires theguest name to match a virtual machine.


User response: Check the guest name and make sureit is spelled correctly.

ANS9556E Number of CTL files on disk (number ofCTLs on disk) do not match the expectedvalue (number of CTLs in cache).

Explanation: The number of CTLs files counted inVCM lib cache should be equal to that in the localdisks.

System action: Processing is aborted.


ANS9576E Not enough space in filesystem to createmeta data file!At least space space required!

Explanation: A disk full error occurred attempting tocreate the metadata file. Please migrate some files infilesystem to free at least space kb.



ANS9577E An exception "msg"!Unable to use meta file!

Explanation: An internal error occurred. The dsmscoutis unable to use the meta data file!



ANS9578E An unknown error occurred!

Explanation: An internal error has occurred. Thedsmscout is unable to use the meta data file! The filehas been deleted. A new meta data file will be created.



ANS9590E The SOAP error information: messagefailed, reason: message

Explanation: The detailed SOAP error message iscreated from gSOAP communication module and doesnot exist in the chosen language!


User response: Verify your system and retry theoperation.

ANS9591E A SOAP UDP connection error hashappened!

Explanation: The SOAP communication system hadan UDP error. Please see errorlog file for more detailedinformation!

System action: TSM aborts the operation.


ANS9592E A SOAP TCP connection error hashappened!

Explanation: The SOAP communication system hadan TCP error. Please see errorlog file for more detailedinformation!





ANS9593E A SOAP HTTP communication error hashappened!

Explanation: The SOAP communication system hadan HTTP error. Please see errorlog file for moredetailed information!



ANS9594E An internal SOAP error has happend!

Explanation: The SOAP communication system hadan internal error. Please see errorlog file for moredetailed information!



ANS9595E The SOAP communication system is outof memory!

Explanation: The SOAP communication system hadan memory error. Please see errorlog file for moredetailed information!



ANS9596E The SOAP communication endedunexpected!

Explanation: The SOAP communication system hadan EOF error. Please see errorlog file for more detailedinformation!



ANS9613E program-name: Stub size of stubsize bytesis not supported on filesystem.

Explanation: The given stub size value not a multipleof the file system block size and cannot be supported.

System action: The program aborts the operation.

User response: Use a correct stub size.

ANS9616E program-name: cannot get migrationinformation for migrated-file-alias onfile-system-name

Explanation: TSM space management cannot accessthe specified file system object using the systemDMAPI functions. This condition might occur ifDMAPI support is not enabled for the file system, or ifthere is an inconsistency in the file system. Thismessage is typically preceded by other messages thathave more specific information about the error.


Processing continues with the next file.

User response: Review dsmerror.log for precedingmessages that might have more specific informationabout the error. Verify that the file system is consistentand mounted with DMAPI support enabled. Then retrythe operation. If the problem persists, contact IBMtechnical support for further assistance.

ANS9645W The vApps backup operation completed.However, one or more vApp backupsfailed.

Explanation: There were successfull vApp backupsbut there were backup failures as well. The operation isconsidered successfull.

System action: The backup operation completedsuccessfully.

User response: Check the console output and errorlogs for information about why the backups failed.Correct any issues and try backing up the failed vAppsagain.

ANS9669W program-name: file-system CFI is out ofrange.

Explanation: TSM CFI is out of range on the specifiedfile system. The scout daemon could not insert a newfile entry into the CFI during the file system scan. As aresult, it may not provide enough candidates for thenext automigration.


User response: Please, reconsider the MAXFILESoption setting for the file system. The CFI size shouldlikely be increased via 'dsmmigfs update /fs-MAXFiles=n' command.

ANS9674W One or more of the required vAppscould not be retreived.

Explanation: Not all of the vApps that were requiredby the given specification could be retreived. This canbe caused by a change in the vCD vApps definition ora user mistake in the provided vApp spec.

System action: The operation will proceed, as thereare still existing items to operate on.

User response: Check the provided vAppsspecification to make sure the specification matches theexisting configuration. Correct any issues and try theoperation again.

ANS9733E File: File-name excluded by theInclude/Exclude list

Explanation: You tried to back up the named file-namethat was specified to be excluded from backup.




User response: Specify the file using the Includeoption and retry the operation.

ANS9778E Error(s) were detected in options file: ''Do you want TSM to comment out theline with errors and continue?

Explanation: Invalid options or option values wereencountered while reading the options file.

System action: This message is displayed. Furtheraction depends on your response.

User response: Click "Yes" to allow TSM to turn theinvalid line into comments. If you click "No", you willexit immediately.

ANS9779E Unable to open options file '' forwriting.

Explanation: An error occurred while TSM tried toopen options file for writing to update it.

System action: Program exits.

User response: Check file and directory accesspermissions or correct invalid entries in your optionsfile manually.

ANS9782S The selected backupset was generatedby a newer version of the backup server,and the new backupset version is notsupported by this client; The backupsetdata cannot be restored by this versionof the client.

Explanation: The backupset you are attempting torestore was generated by a newer server that has adifferent level of functionality. The client you are usingdoes not recognize this newer format so it cannotrestore the data from the backupset.


User response: Restore the backupset with a clientthat is at the same or higher level as the server thatwas used to generate the backupset.

ANS9806W The file system type is not supported.

Explanation: The file system is not a type supportedby space management.

System action: TSM cannot add space management tothe file system.

User response: There is a mismatch between the HSMclient and the file system type specified. If the filesystem type is consistent with the intent, install anHSM client that supports it, then try the operationagain. Only one HSM client can be installed at a time.

ANS9807W The specified backupset file does notcontain a backupset of type "file" for thespecified nodename.

Explanation: Local backupset support is limited tobackupsets that contain file data; Image backupsets arenot supported locally. The specified backupset does notcontain a backupset with file data for the node namespecified.


User response: Specify a different backupset file torestore file data from a backupset. To restore an imagefrom a backupset, access the backupset from a TSMserver.

ANS9827W Error accessing the Recall daemon lockfile: file name.

Explanation: There is a problem accessing the recalldaemon lock file.

System action: TSM cannot determine whether therecall daemon is running. Because the recall daemon isneeded to perform file recalls, the recall fails.

User response: Check with the system administrator.The recall process needs read access to the/etc/adsm/SpaceMan/dsmrecalld.pid file.

ANS9828W File: file-name is skipped for migration:The file is either AFM uncached ordirty.

Explanation: If using GPFS Active file management,the file could either be uncached or dirty.Uncached (no file data available in cache. Access wouldcause replication from home)Dirty (changed file data in cache. No valid replicationin home)

System action: The file is skipped from processing.

User response: Uncached (fetch the file from home tocache and rerun the processing)Dirty (replicate the file from cache to home and rerunthe processing)

ANS9829W Recall daemon is not running.

Explanation: An TSM recall daemon is not running.

System action: TSM recall fails.

User response: Ask the system administrator to start arecall daemon by issuing the dsmrecalld command.

ANS9842E The watch daemon is not runningproperly.

Explanation: An TSM watch daemon is either notrunning, has no dmapi session, or is not connected togroup services.



System action: The TSM action fails.

User response: Ask the system administrator to checkGPFS and the group services and to restart a watchdaemon by issuing the dsmwatchd command.

ANS9845E Space management action ends.

Explanation: TSM The requested space managementoperation is ended because the watch daemon is notworking properly.

System action: TSM is unable to complete theoperation.

User response: Look for previous messages.

ANS9849W Local backupset cannot be expanded;Only full backupset restore is supportedlocally.

Explanation: Local backupsets cannot be expanded toshow volumes, directories, and files. Only fullbackupset restore is supported from local backupsets.


User response: To restore specific volumes, directories,and files from a backupset, restore the backupset fromthe TSM server.

ANS9850E Tape read error; Max Blocksize isblocksize. Attempted to read blocksizeblocksize. Run dsmmaxsg to update scsidriver max blocksize allowed and retryoperation.

Explanation: An attempt to read from tape at thespecified blocksize failed; Tha maximum blocksizeallowed for the scsi driver is shown.


User response: If the maximum blocksize is less thanthe blocksize used by the operation, run the dsmmaxsgutility to update the maximum blocksize allowed forthe scsi driver, and then retry the operation. If themaximum blocksize is greater than or equal to theblocksize used, then verify that the tape installed andoperating correctly and retry the operation.

ANS9857W The restored HSM for Windows stubfile may be an orphan: stub file name

Explanation: The restored stub file may not beaccessible in the HSM client archive and thus itpossibly cannot be recalled.

System action: Stub file is restored.

User response: Check if the stub file can be accessed.

ANS9858E The backup-archive operation did notrun. The backup-archive operationinvolves stub files that were migratedwith the HSM for Windows client. Theinstalled HSM for Windows clientversion version. release. level isincompatible with installedbackup-archive client version version.release. level.

Explanation: The backup-archive client uses the HSMfor Windows client for backup-archive operations thatinvolve migrated files. The HSM for Windows clientand the backup-archive client must be at the same PTFlevel.

System action: The backup-archive operation does notrun for any files. Migrated files and resident files arenot processed.

User response: Uninstall the current HSM forWindows client and install an HSM for Windows clientat the same PTF level as the backup-archive client.

ANS9890W program-name: The file system filesystemis already owned by that node.

Explanation: The file system is already owned by thatnode..



ANS9892E Unable to find snapshot(s) in the localrepository.

Explanation: The requested volume snapshot(s) werenot found in the local repository.


User response: Ensure the operation is issued with theproper nodename and/or server address. In anon-cluster environment perform the operation from adifferent host with the expected hostname. Retry theoperation.

ANS9895W Space management in file system filesystem is not active.

Explanation: You tried to select a file in a file systemfor which space management is inactive.

System action: TSM continues with normal operation.

User response: Reactivate space management for thefile system, and then proceed with selecting files.



ANS9916I VMCUSER does not have one or morerequired vSphere privileges tocreate/update/cancel Tasks in vSphererelated to this operation. The operationwill continue.

Explanation: VMCUSER does not have one or morerequired vSphere privileges to create/update/cancelTasks related to this operation. This is informationalonly and does not affect the Backup/Restore operation.

System action: A Task related to this operation maynot show up in the vSphere Client due to missingprivileges. The operation will continue.

User response: The vSphere Task provides additionalinformation about TSM initiated VM Backup/Restoreoperations including progress as well as the ability tocancel these tasks from the vSphere Client. Please referto the 'VMware vCenter Server user privilegerequirements' section of the 'IBM Tivoli StorageManager for Virtual Environments: Data Protection forVMware User's Guide.'

ANS9918E Cannot open migration candidates listfor file-system.

Explanation: TSM cannot access the migrationcandidates list for the specified file system.

System action: TSM continues normal operation.

User response: Select OK to return.

ANS9919E Failed to find the expected control filesfor vm name.

Explanation: During a verify operation, the number ofcontrol files that were found on the server do notmatch the expected amount for one or more disks.

System action: The backup operation for this VMcontinues based on the VMVERIFYIFAction option.

User response: Perform a full VM backup for thisvirtual machine or specify the VMVERIFYAction optionto force a full VM backup.

ANS9920W Forcing a full vm backup for vm name.

Explanation: During a verify operation, the number ofcontrol files that were found on the server do notmatch the expected amount for one or more disks. As aresult, a full VM backup is performed.

System action: The backup operation for this VM is afull backup instead of an incremental backup.

User response: Ensure the VERIFYIFAction option isset to the wanted value.

ANS9921E Virtual machine disk, vm name (disklabel), verification check failed (size ondisk/ ctl size).

Explanation: During a verify operation, the number ofcontrol files that were found on the server do notmatch the expected amount for this disk.

System action: The backup operation for this VMproceeds based on the VMVERIFYIFAction option.

User response: Perform a full VM backup for thisvirtual machine or specify the VMVERIFYIFActionoption to force a full VM backup.

ANS9922I VMVERIFYIFLatest is enabled for vmname (action: type).

Explanation: This VM operation verifies the controlfiles from the previous backup to ensure that allexpected files are on the server.

System action: The operation proceeds based on thevalue of the VMVERIFYIFAction option.

User response: Ensure the VERIFYIFAction option isset to the wanted value.

ANS9950W Streaming and partial recall modes cannot be set for files migrated usingexternal backend.

Explanation: Streaming or partial recall modes are notsupported for files in this mode.

System action: Operation aborted.

User response: Special recall modes are only availablefor files migrated using TSM Server as a backend.

ANS9951I File: file-name has already been migrated.

Explanation: You tried to migrate a file that is alreadymigrated. Note that you may get this message if the fileis hard linked with another, already migrated file.



ANS9958E File 'file-namefile-namefile-name has not yetreached the age for migration. Fileskipped.

Explanation: This file cannot be migrated because ithas not yet reached the age for migration.

System action: TSM will not highlight the file.




ANS9959W IBM Tivoli Storage Manager acceptorreceived a non-critical network errorerrno, TSM return code : TSM-rc.

Explanation: The communication problem happenedwhile listening for inbound connection but the IBMTivoli Storage Manager acceptor continues running.


User response: No further action is required, it can besafely ignored.

ANS9984W PFR plugin library was not found.

Explanation: PFR plugin library should have beeninstalled when the client was installed, but it cannot befound.



ANS9987W Partial recall mode is not set forfull-file-name

Explanation: Partial recall mode is not set for thespecified file.

System action: The recall is not performed for thespecified file. Processing stopped.

User response: Set the partial recall mode on the file("dsmattr -recallmode=partialrecall" command) andre-try the operation.

ANS9989W Management class mcName specified onthe INCLUDEstatement in file-name at line line-numberdoes not exist.

Explanation: Management class named on theINCLUDE statement in the file-name file does not existin your assigned policy set on the server.

System action: The object is bound to the defaultmanagement class.

User response:

v Update the INCLUDE statement so that it specifies avalid management class.

v Define the management class named on theINCLUDE statement (if it is intended to have amanagement class with that name).

v Verify that the node is in the correct policy domain(perhaps the node was accidentally put in the wrongpolicy domain, and the correct domain has themanagement class).

v Remove the INCLUDE statement if it is no longernecessary to bind the files to the management class.

ANS9990W Management class mcName specified onINCLUDE statementin client option set does not exist.

Explanation: Management class named on theINCLUDE statement in client option file does not existin your assigned policy set on the server.

System action: The object is bound to the defaultmanagement class.

User response:

v Update the INCLUDE statement so that it specifies avalid management class.

v Define the management class named on theINCLUDE statement (if it is intended to have amanagement class with that name).

v Verify that the node is in the correct policy domain(perhaps the node was accidentally put in the wrongpolicy domain, and the correct domain has themanagement class).

v Remove the INCLUDE statement if it is no longernecessary to bind the files to the management class.

ANS9992E The following options must be setbefore running this operation:VMCHOST or VMCUSER.

Explanation: VMCHOST or VMCUSER is missingfrom the options file.

System action: Operation cannot continue withoutoptions being set.

User response: Manually edit the options file or usethe preferences editor to set these options.

ANS9999E ():

Explanation: This message carries diagnostic textrelating to a client process or algorithm. Thisinformation is intended for reporting processingexceptions and other non-standard situations that occuron the TSM client. The (component), (code), and (text)will vary depending upon the cause of the messageand the client process or algorithm that issues themessage.

System action: Client processing may or may notcontinue depending upon the cause of this message.

User response: Examine error messages that may havebeen displayed before and/or after this message andcorrect any problems, if possible. If the cause of thismessage can not be determined or resolved, contactyour support representative. If you contact yoursupport representative, the entire text of this messageshould be reported.



Chapter 3. API return codes

IBM Tivoli Storage Manager V7.1.3 API return codes are listed. The format of thereturn codes is described.

API return code formatThis section explains the API (Application Programming Interface) return codeformat. For each return code, the following information is provided:v The return code number. This number corresponds to the number in the dsmrc.h

header file.v The severity code. This letter is an indication of the severity that generated the

return code. The possible severity codes and their meanings include:

S Severe error Processing cannot continue.E Error Processing cannot continue.W Warning Processing can continue, but problems might develop

later. You should be cautious.I Information Processing continues. User response is not necessary.

v The symbolic name. This name corresponds to the definition in the header file,dsmrc.h. Always use the symbolic name for a return code in your application ratherthan the return code number.

v The explanation. This field explains the circumstances under which this returncode might be generated.

v The system action. This field describes what action Tivoli Storage Manager isgoing to take in response to the return code.

v The user response. This field explains how you should respond to the systemaction.

Many of the return codes describe errors that cause processing to stop. You cansend a message to the end user that describes the problem and suggest a course ofaction. To identify different messages, use these return code values or develop yourown numbering system.

API return codesIBM Tivoli Storage Manager V7.1.3 API return codes are listed in ascendingnumeric order. The complete return code is documented.

-452 E DSM_RC_SHM_NOTAUTH Insufficientauthority to connect to the sharedmemory region

Explanation: The user issuing the command does nothave authority to connect to the shared memorysegment. When the shared memory segment is createdby the server, it will be owned by the effective uid ofthe server process (dsmserv). Only processes runningunder this uid or root will be allowed to connect to thesegment (and thus to the server).

System action: The session is rejected and processingstops.

User response: Run the command under the uid ofthe processing running dsmserv, if possible. Otherwisecontact your system administrator for further help.

-451 E DSM_RC_SHM_FAILURE An erroroccurred using the Shared Memoryprotocol

Explanation: An error has occurred while reading or


writing data through the Shared Memorycommunications protocol.


User response: Check the trace log for additionalinformation and retry the operation. If the problemcontinues, see your system administrator for furtherhelp.

-450 E DSM_RC_SHM_TCPIP_FAILURESession rejected: TCP/IP connectionfailure for Shared Memory

Explanation: An attempt to connect to the local serverusing the Shared Memory protocol has failed duringinitial TCP/IP communications. This error can occur ifthe server is not listening on the correct port, or if theserver is down.



-190 E DSM_RC_NP_ERROR Session rejected:Named Pipes connection failure.

Explanation: An attempt to connect to the serverusing Named Pipes communications failed. This mighthave occurred if an incorrect NAMEDPIPENAME wasspecified in the options files or if your systemadministrator canceled a backup operation.


User response: Retry the operation, or wait until theserver comes back up and retry the operation. Ensurethat the value specified on the NAMEDPIPENAMEoption is the same as the one used by the server. If theproblem continues, contact your system administratorfor further help.

-057 E DSM_RC_TCPIP_LOADFAILURE TheTCP/IP load function failed.

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



-056 E DSM_RC_TCPIP_DLL_ LOADFAILUREAn error occurred while loading alibrary.

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



-055 E DSM_RC_WINSOCK_MISSING TheTCP/IP WINSOCK.DLL file cannot befound.

Explanation: The TCP/IP WINSOCK.DLL file cannotbe found.



-054 E DSM_RC_NETWORK_UNREACHABLEThe specified TCP/IP host name isunreachable

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


User response: Check your options file for the correctTCPSERVERADDRESS statement. See youradministrator for the correct name of the server.

-053 E DSM_RC_BAD_HOST_NAME Aninvalid TCP/IP address was specified.

Explanation: The TCP/IP address specified by theTSM client's TCPSERVERADDRESS setting could notbe found on the network. Common reasons for thiserror include:

v The TCPSERVERADDRESS client option specifies thewrong TCP/IP address for the TSM server".

v The machine that hosts the TSM server is not on thenetwork.

v A network problem is preventing the TSM clientfrom reaching the machine that hosts the TSM server.


User response: Verify that the TCPSERVERADDRESSand TCPPORT settings have the correct values for yourTSM server. Use your operating system's "ping" (orsimilar) utility to ensure that your machine can locatethe machine that hosts the TSM server across thenetwork. Try the operating again. If the problempersists, ask your TSM administrator for furtherassistance.

-052 E DSM_RC_CONN_REFUSED An attemptto establish a TCP/IP connection wasrejected by the host

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


User response: The server was not fully initialized, isnot currently running, was not enabled for TCP/IPcommunications, or an incorrect TCP/IP port number

-450 E • -052 E


was specified. If the problem continues, see yoursystem administrator.

-051 E DSM_RC_CONN_TIMEDOUT Theattempt to establish a TCP/IP connectiontimed out before the connection wasmade.

Explanation: The Object of the connection attemptfailed to respond within the the allotted wait time. Inthe case of the B/A client, this message is preceded indsmerror.log by message ANS5216E that gives detailsof the connection that failed. The condition may betemporary.


User response:


v Check the client options file and verify thatTCPSERVERADDRESS and TCPPORT specify thecorrect TCP/IP address and port number for yourTSM server.


v If the problem persists, see your TSM administratorfor further assistance.

-050 E DSM_RC_TCPIP_FAILURE Sessionrejected: TCP/IP connection failure.




0000 I DSM_RC_OK Successfully done.




0001 E DSM_RC_ABORT_SYSTEM_ERRORThis operation cannot continue due toan error on the TSM server. See yourTSM server administrator for assistance.

Explanation: The TSM server encountered an errorcondition that prevents the TSM client operation fromcontinuing. Your TSM server administrator can review

the TSM server activity log for more details about theerror.



0002 E DSM_RC_ABORT_NO_MATCH Noobjects on server match query

Explanation: No objects on the server match the queryoperation being performed. If this object is part of abackupset generated on a node, and the node name ischanged on the server, any backup set objects that weregenerated prior to the name change will not match thenew node name.


User response: Ensure the names are properlyentered. If the object is part of a backupset generatedprior to a node name change, ensure that the nodename is the same as the node for which the backup setwas generated.

0003 E DSM_RC_ABORT_BY_CLIENT Clientended transaction




0004 W DSM_RC_ABORT_ACTIVE_NOT_FOUND An active backup version couldnot be found.

Explanation: An attempt was made to expire anobject, but the TSM server was unable to find an activebackup version of the object. This message is precededby message ANS1228E which specifies the object name.For instance, this message could be issued if twoseparate client processes are backing up the same filesystem at the same time. If one of the processes expiresa file, then the TSM server will make that file inactive.If the second process subsequently attempts to expirethat same file, the TSM server will not find an activeversion of the file, so the second process will issue thismessage for that file.

System action: The object is not expired. Processingcontinues with the next object.

User response:

v Review the console output, schedule log, or error logand locate the ANS1228E message that immediatelyprecedes this message. ANS1228E will identify theobject that could not be expired.

-051 E • 0004 W

Chapter 3. API return codes 297

v Examine the conditions under which the problemoccurred and assess whether those conditions explainthe occurrence of this message. For example, thismessage could appear if multiple instances of theclient were attempting to back up the file systemconcurrently.

v If the reason this message occurred can not bedetermined and the message occurs when theoperation is tried again, then contact IBM support forfurther assistance. Also try searching for this messagenumber on http://www.ibm.com for possiblesolutions.

0005 E DSM_RC_ABORT_NO_DATA The TSMserver has no data for the object.

Explanation: TSM tried to do a restore or retrieve onan object that has no data associated with it. If acorrective action is possible, it is with the TSM server.


User response: Ask the TSM administrator to checkthe TSM activity log for any messages related to thiserror that might help identify the problem.

0006 E DSM_RC_ABORT_BAD_VERIFIER Youentered an incorrect password.



User response: Retry the session with the correctpassword. If this fails or you have forgotten yourpassword, ask the TSM administrator to assign a newpassword.

0007 E DSM_RC_ABORT_NODE_IN_USENode in use




0008 E DSM_RC_ABORT_EXPDATE_TOO_LOW Expiration date must be greaterthan today's date

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


User response: Retry archiving the file with an

expiration date that is higher than today’s date.

0009 W DSM_RC_ABORT_DATA_OFFLINE Therequested data is offline.

Explanation: For the restore or retrieve operation, oneor more of the requested files must be recalled fromoffline storage media (generally tape). The wait timedepends on your site’s offline storage managementpolicies.

System action: TSM waits for offline storage media tobecome available and then continues.


0010 E DSM_RC_ABORT_EXCLUDED_BY_SIZE Object too large for server limits



User response: See your system administrator todetermine the maximum file (object) size for whichyour site’s server is configured.

0011 E DSM_RC_ABORT_NO_REPOSIT_SPACE Server out of data storage space





v For TSM client, set COMPRESSALWAYS=NO andCOMPRESSIon=YES in the options file (DSM.OPT),then the file will be resent uncompressed if it growsduring compression.

v For API Applications, consult the application'sdocumentation for recommendations regardingcompression.

v Turn off disk caching in the disk storage pool, andissue MOVE DATA commands to each disk poolvolume to clear out the cached bitfiles.

0012 E DSM_RC_ABORT_MOUNT_NOT_POSSIBLE Server media mount notpossible



User response: Retry later when server volumes can

0005 E • 0012 E


be mounted. Ensure that the MAXNUMMP (maximumnumber of mount points) defined on the server for thisnode is greater than 0.

0013 E DSM_RC_ABORT_SIZESTIMATE_EXCEED Size estimate exceeded




0014 E DSM_RC_ABORT_DATA_UNAVAILABLE File data currentlyunavailable on server

Explanation: The file data is currently unavailable onthe server. A retrieve or restore operation wasattempted. Possible causes are:

v Data was corrupted at the server

v Server found a read error


v Server requested a tape volume that was markedunavailable.


User response: Retry the operation. If the problemcontinues, see your system administrator to determinethe problem from the server console or the activity log.Check whether any requests were made for a tapevolume that was unavailable. A tape volume may bemarked unavailable if prior read errors wereencountered or the volume is checked out of the tapelibrary.

0015 E DSM_RC_ABORT_RETRY Unexpectedretry request. The TSM server found anerror while writing the data.

Explanation: None.

System action: If the current operation supportsanother attempt, the client tries the operation again.Otherwise, processing stops.


0016 E DSM_RC_ABORT_NO_LOG_SPACEThe server does not have enoughrecovery log space tocontinue the current operation




0017 E DSM_RC_ABORT_NO_DB_SPACE Theserver does not have enough databasespace to continuethe current operation




0018 E DSM_RC_ABORT_NO_MEMORY Theserver does not have enough memory tocontinue the current operation.

Explanation: The server ran out of memory.


User response: This is a temporary problem. Retrylater or see your system administrator.

0020 E DSM_RC_ABORT_FS_NOT_ DEFINEDThe specified file space does not existon the server. Thefile space might have been deleted byanother client or anadministrator.

Explanation: The specified file space does not exist onthe server. Your system administrator deleted the filespace or another client using your client’s node namedeleted it.


User response: Check the file space name to see if it iscorrect, and retry the operation.

0021 S DSM_RC_ABORT_NODE_ALREADY_DEFED Open Registration failedbecause the specified node name isdefined in the server

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



0013 E • 0021 S


0022 S DSM_RC_ABORT_NO_DEFAULT_DOMAIN Open Registration failedbecause no default domain exists

Explanation: Open registration failed because adefault policy domain does not exist for you to placeyour node.



0023 S DSM_RC_ABORT_INVALID_NODENAME Open Registration failedbecause an invalid node name wasspecified

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


User response: Retry with another node name thatdoes not have any invalid characters.

0024 E DSM_RC_ABORT_NO_INVALID_POL_BIND An object in the transactionhas been bound to an invalidmanagement class.

Explanation: One of the objects in the transaction isbound to a management class that is not part of thisnode's policy, or the management class type is notsupported for this client level.


User response: Make sure all objects are bound to avalid management class, or upgrade the client to theproper level.

0024 S DSM_RC_ABORT_INVALID_POL_BIND A policy management problemhas occurred on the TSM server.

Explanation: The TSM client error log and TSM serveractivity log may contain additional information aboutthis error.

System action: Processing is stops.


0025 E DSM_RC_ABORT_DEST_NOT_DEFINED Server problem: Destinationnot defined.

Explanation: Server problem: Destination not defined.


User response: Have your service representative checkthe error log.

0026 S DSM_RC_ABORT_WAIT_FOR_ SPACEThe TSM server does not currently havespace in the storage pool for this file.This may be a temporary condition.

Explanation: This message is typically issued whenthe storage pool in which the data is being placed doesnot have sufficient space to store the data, but thespace will be available soon. For example, a storagepool migration might free up sufficient space to storethe data.


User response: Try the operation at a later time. If thisfails, contact the TSM administrator and request morestorage pool space.

0027 E DSM_RC_ABORT_NOT_AUTHORIZED The file space cannot bedeleted because this node does not havepermission to delete archived or backedup data.

Explanation: You cannot delete the file space dataunless your TSM administrator has authorized yournode to do so. Authorization permits you to deletebackup data, archive data, or both.

System action: Delete processing fails.

User response: Use the DSMC QUERY SESSIONcommand to verify your authorization. Ask your TSMadministrator to provide the necessary authorization orto delete the file space for you.

0028 E DSM_RS_ABORT_RULE_ALREADY_DEFED 'Access rule' Access Rule alreadydefined for node 'node'.Old rule must be deleted before newone can be defined.

Explanation: You are trying to define authorization forthe specified node, which already has authorizationdefined.

System action: TSM did not redefine authorization forthe specified node.

User response: Update the authorization, or delete theold rule and define a new one, or use the currentauthorization.

0022 S • 0028 E


0029 S DSM_RC_ABORT_NO_STOR_SPACE_STOP Server out of data storagespace

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



0030 E DSM_RC_ABORT_LICENSE_VIOLATION The operation is notpermitted due to server licenses values.

Explanation: The node or user is trying to perform anoperation that either exceeds license values, or is notlicensed.

System action: The session is rejected or thetransaction is cancelled, ending the current operation.


0032 E DSM_RC_ABORT_DUPLICATE_OBJECT A duplicate object was found,operation cannot complete.

Explanation: A duplicate object was found, operationcannot complete.


User response: Try the operation with a different filespecification.

0033 E DSM_RC_ABORT_INVALID_ OFFSETpartialObjOffset value for partial objectretrieve is invalid.

Explanation: The partialObjOffset value for partialobject retrieve is invalid.



0034 E DSM_RC_ABORT_INVALID_ LENGTHpartialObjLength value for partial objectretrieve is invalid.

Explanation: partialObjLength value for partial objectretrieve is invalid.



0036 E DSM_RC_END_NODE_NOT_AUTHORIZED The node or user doesnot have proper authority to performthis operation

Explanation: The node or user does not have properauthority to perform this operation.

System action: The transaction is ended.

User response: Check the authority for the specifiedobject.

0041 E DSM_RC_ABORT_EXCEED_MAX_MPThis node has exceeded its maximumnumber of mount points.

Explanation: Either no tape or sequential disk mountpoints are permitted for this operation, or themaximum number of mount points allowed are alreadyin use. The operation can not be completed. The TSMadministrator defines the maximum number of mountpoints with the MAXNUMMP property of your nodedefinition.

System action: The object is skipped

User response: If you are performing any other TSMoperations that might be using mount points, wait untilthose operations are complete, then try the failedoperation again. Otherwise contact your TSMadministrator for further assistance

0045 E DSM_RC_ABORT_MERGE_ERROR Thespecified objects failed the merge test.

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


User response: See documentation for the merge testparameters.

0047 E DSM_RC_ABORT_INVALID_OPERATION An invalid operation wasattempted on a node

Explanation: The operation is not valid.



0048 E DSM_RC_ABORT_STGPOOL_UNDEFINED The specified targetstorage pool is not defined.

Explanation: The storage pool is not defined.



0029 S • 0048 E


0049 E DSM_RC_ABORT_INVALID_DATA_FORMAT A target storage pool does nothave the correct data format for thegiven node type.

Explanation: none



0050 E DSM_RC_ABORT_DATAMOVER_UNDEFINED No associated data moveris defined for the given node.

Explanation: none



0051 E DSM_RC_REJECT_NO_RESOURCESSession rejected: All server sessions arecurrently in use

Explanation: TSM has all available sessions in use andcannot accept a new one at this time.


User response: Retry the operation. If the problemcontinues, see your system administrator to increase thenumber of concurrently active sessions to the server.

0052 E DSM_RC_REJECT_VERIFIER_EXPIRED The session is rejected. Yourpassword has expired.

Explanation: The password for TSM user ID hasexpired. It can be either TSM node name password oradministrative user ID password or both.

System action: TSM canceled the current operation.You are not allowed to connect to the server until thepassword is updated.

User response: Update your password. It may requireupdating the node name password or the corespondentadministrative ID password or both. You may use theSET PASSWORD command, or have the TSMadministrator update your node and/or youradministrative ID.

0053 E DSM_RC_REJECT_ID_UNKNOWNSession rejected: Unknown or incorrectuser ID entered

Explanation: The user ID, which is either TSM nodename or administrative user ID, is not known by theserver. Possible reasons for this include:

Your node name is not registered with the TSMserver

The node name is correct but does not have acorresponding administrative ID with the samename and client owner authority

you are attempting to access a file that wasmigrated to a different node.

System action: TSM cancelled the current operation.

User response: Verify that the server is using closedregistration and that your node name is registered withthe server. Ensure that you entered your TSM user IDcorrectly. Check that your TSM node name has amatching admin ID with client owner authority for thenode. If it does not, your TSM administrator needs tocreate it. If attempting to access a migrated file, yournode name must be the same node which migrated thefile.

0054 E DSM_RC_REJECT_DUPLICATE_IDSession rejected: Duplicate ID entered


System action: TSM cannot connect to the server. TSMcanceled the current operation.

User response: If you are running a UNIX-basedsystem, ensure that another process is not active withTSM under the same name. Also, ensure that yournode name is unique to the server so that it cannot beused by another person. See your system administratorto identify the owner of that node name.

0055 E DSM_RC_REJECT_SERVER_DISABLED Session rejected: Serverdisabled.



User response: On the TSM server, run the ENABLESESSIONS administrative command. Try the operationagain after the server returns to an enabled state. If theproblem continues, see your system administrator.

0056 E DSM_RC_REJECT_CLOSED_REGISTER The server is not configuredto allow open registration



User response: You must obtain a TSM node andpassword from your system administrator.

0049 E • 0056 E


0057 S DSM_RC_REJECT_CLIENT_DOWNLEVEL Session rejected:Downlevel client code version




0058 S DSM_RC_REJECT_SERVER_DOWNLEVEL Session rejected:Downlevel server code version




0059 E DSM_RC_REJECT_ID_IN_USE SessionRejected: The specified node name iscurrently in use

Explanation: The node name you specified is in useon the server.


User response: The server is probably performing atask that prevents your node from establishing asession. Retry later or check with your systemadministrator.

0061 E DSM_RC_REJECT_ID_LOCKEDSession Rejected: The specified nodename is currently locked.

Explanation: The node name you specified is currentlylocked on the server.


User response: Check with your system administratorto find out why your node name is locked.

0062 S DSM_RC_SIGNONREJECT_LICENSE_MAX SLM LICENSEEXCEEDED: The client licenses for TSMare exceeded.See your system administrator.

Explanation: Adding a new enrollment will exceed theproduct license count for TSM.



0063 E DSM_RC_REJECT_NO_MEMORYSession Rejected: The server does nothave enough memory toallow a connection to be established.




0064 E DSM_RC_REJECT_NO_DB_SPACESession Rejected: The server does nothave enough databasespace to allow a connection to beestablished.




0065 E DSM_RC_REJECT_NO_LOG_SPACESession Rejected: The server does nothave enough recovery logspace to allow a connection to beestablished.




0066 E DSM_RC_REJECT_INTERNAL_ ERRORThe session is rejected. The TSM serverhas an internal error.

Explanation: The client cannot establish a connectionto the TSM server because of an internal server error.

System action: The session was not started.

User response: Notify your TSM administrator of thiserror.

0067 S DSM_RC_SIGNONREJECT_INVALID_CLI Session Rejected: Theserver is not licensed for this platformtype.See your system administrator.

Explanation: The server is not licensed for therequesting client type.



0057 S • 0067 S


0068 E DSM_RC_CLIENT_NOT_ARCHRETPROT The session is rejected.The server does not allow a signon of aclient that is not archive-retentionprotection enabled.

Explanation: The client cannot establish a connectionto the server because the server is enabled forarchive-retention protection enabled and the client isnot.



0069 E DSM_RC_SESSION_CANCELEDSession Rejected: The session wascanceled by the server administrator.

Explanation: The server administrator canceled thecurrent client session.

System action: Execution of the client connectionrequest ends.


0073 E DSM_RC_REJECT_INVALID_NODE_TYPE An inconsistency wasdetected between the client node andthe node that is registered to the TSMserver.

Explanation: The user has probably coded the nodeoption incorrectly. For instance, the node that isregistered to the TSM server might be a type of NAS,but the node is actually a non-NAS client.


User response: Ensure that the node name is correctin the client options file. Make sure to use a node oftype NAS only with the nasnodename option.

0074 E DSM_RC_REJECT_INVALID_SESSIONINIT Server does not allowclient-initiated connections for thisnode.

Explanation: The node is not allowed to initiateconnections due to the configuration parameters forthis node on the server. Server is able to initiateconnections to the client scheduler running inprompted mode.


User response: Contact your systems administrator toenable client-initiated sessions for your node or updatethe SESSIONINITIATION option and run the clientscheduler.

0075 E DSM_RC_REJECT_WRONG_PORTWrong server port.

Explanation: You were trying to open abackup/archive client session on the server port set upfor administrative sessions only.


User response: Contact your systems administratorand/or use the correct values for TCP port and TCPAdmin Port.

0079 E DSM_RC_CLIENT_NOT_SPMRETPROT The session is rejected.The server does not allow a signon of aclient that is not enabled forspace-management retention-protection.

Explanation: The client cannot establish a connectionto the server because the server is enabled forspace-management retention-protection and the client isnot.



0101 W DSM_RC_USER_ABORT The operationwas stopped by the user.




0102 E DSM_RC_NO_MEMORY file name(linenumber)The operating system refused aIBM Tivoli Storage Manager request formemory allocation.

Explanation: IBM Tivoli Storage Manager requiresaccess to memory in order to store information asprocessing proceeds. In this case, more memory wasrequested than the operating system would allocate.Possible reasons include:


The process in which the program runs hasexceeded the maximum allocated memory.

Some other error condition occurred. No memory isavailable.

System action: IBM Tivoli Storage Manager cannotcomplete the requested operation.

User response: Close all unneeded applications andtry the operation again. If the operation still fails, trydividing the task into several smaller units. Forexample, if a file specification contains severalhigh-level directories, run the IBM Tivoli Storage

0068 E • 0102 E


Manager task serially for each directory. If the IBMTivoli Storage Manager task is an incremental backup,use the option "-memoryefficientbackup=yes".

For UNIX systems that support resource limits, you cancheck if the memory resource limit is too low byentering the following command: ulimit -a

Based on the resulting data, you can ask the UNIXsystem root user to increase the resource limit abovethe current default limit. The UNIX system root userhas the authority to increase resource limits.

0104 E DSM_RC_FILE_NOT_FOUND File notfound during Backup, Archive orMigrate processing

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



0105 E DSM_RC_PATH_NOT_FOUND Thespecified directory path 'pathname' couldnot be found.




0106 E DSM_RC_ACCESS_DENIED Access tothe specified file or directory is denied




0106 E DSM_RC_ACCESS_DENIED Thespecified file is being used by anotherprocess




0107 E DSM_RC_NO_HANDLES No filehandles available




0108 E DSM_RC_FILE_EXISTS The file existsand cannot be overwritten.



User response: Verify that you have sufficient accesspermissions to overwrite the file, then try the operationagain. If the problem persists, contact your systemadministrator or TSM administrator for furtherassistance.

0109 E DSM_RC_INVALID_PARM Invalidparameter was found.




0110 E DSM_RC_INVALID_HANDLE Aninvalid file handle was passed; systemerror.

Explanation: An internal system error occurred: A fileoperation failed because of an invalid file handle.


User response: Try the operation again. If the failurepersists, obtain a service trace that captures theproblem and contact IBM technical support foradditional assistance. Your TSM administrator can helpyou configure the trace.

0111 E DSM_RC_DISK_FULL Processingstopped; Disk full condition




0104 E • 0111 E


0113 E DSM_RC_PROTOCOL_VIOLATIONProtocol violation

Explanation: A communications protocol erroroccurred. The communication subsystem is notproperly defined or is itself in error.


User response: Verify that the communicationprocesses are operating properly, and then retry theoperation.

0114 E DSM_RC_UNKNOWN_ERROR Anunknown system error has occurredfrom which TSM cannot recover.

Explanation: An unknown error occurred. This mightbe a low-level system or communication error fromwhich TSM cannot recover.


User response: Try the operation again. If the problempersists, review the TSM error log for any relatedmessages. Obtain a service trace that captures theproblem and contact IBM technical support foradditional assistance. Your TSM administrator can helpyou configure the trace.

0115 E DSM_RC_UNEXPECTED_ERROR Anunexpected error occurred.

Explanation: This is usually caused by a low-levelsystem error or communication error from which TSMcannot recover.


User response: Examine the client error log for anyadditional messages that might be related to thisproblem. Try the operation again. If the problempersists, contact TSM technical support for furtherassistance.

0116 E DSM_RC_FILE_BEING_EXECUTED Fileis in use; Write permission denied.

Explanation: The current file cannot be opened towrite to because it is currently being run by anotheroperation.



0117 E DSM_RC_DIR_NO_SPACE No morefiles can be restored or retrieved sincethe destination directory is full.

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



0118 E DSM_RC_LOOPED_SYM_LINK Toomany symbolic links were detectedwhile resolving name




0119 E DSM_RC_FILE_NAME_TOO_LONGThe file name is too long and can not beprocessed by TSM

Explanation: The size limit for file names may vary byoperating system. The most common limit is 256characters. The file name being processed exceeds thelimit supported by TSM on this system.


User response: Enter HELP FILE SPEC or see theclient manual for the operating system on which youare receiving this error. The "File specification syntax"section of the manual explains file name lengthssupported by TSM.

0120 E DSM_RC_FILE_SPACE_LOCKED Filesystem is locked by system




0121 I DSM_RC_FINISHED The operation isfinished.

Explanation: The operation is finished.


User response: Proceed with next function call.

0122 E DSM_RC_UNKNOWN_FORMAT Thefile has an unknown format.

Explanation: TSM tried to restore or retrieve a file, butit had an unknown format.


User response: The file was either backed up byanother application, or the data is invalid. If the filebelongs to this system, try the operation again. If the

0113 E • 0122 E


problem persists, contact IBM technical support forfurther assistance.

0123 E DSM_RC_NO_AUTHORIZATION Notauthorized to restore the other node'sdata.

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


User response: Get authorization from the other node.

0124 E DSM_RC_FILE_SPACE_NOT_ FOUNDFile space 'filespace-name' does not exist

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


User response: Retry the operation specifying anexisting domain (drive letter or file system name).

0125 E DSM_RC_TXN_ABORTED Transactionaborted

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


User response: Retry the operation. If the problemcontinues, see your system administrator to isolate theproblem.

0126 E DSM_RC_SUBDIR_AS_FILE TSMcannot build a directory path because afile exists with the same name asthe directory.

Explanation: None


User response: Remove or rename the file that has thesame name as the directory. Alternatively, you canrestore the directory to a different location.

0127 E DSM_RC_PROCESS_NO_SPACE Diskspace limit for this process reached




0128 E DSM_RC_PATH_TOO_LONGDestination directory path lengthexceeds system maximum

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


User response: Specify a destination path that, whencombined, is less than the system maximum.

0129 E DSM_RC_NOT_COMPRESSED File isnot compressed; System failure.




0130 E DSM_RC_TOO_MANY_BITS Filecompressed on a different clientmachine that has more memory




0131 S DSM_RC_SYSTEM_ERROR An internalprogram error occurred.

Explanation: TSM encountered an unexpectedcondition and can not continue the operation. Thismight be a programming error.


User response: Try the operation again. If the problempersists, contact your TSM administrator or IBMtechnical support for further assistance.

0131 E DSM_RC_COMPRESSED_DATA_CORRUPTED The compressed file iscorrupted and cannot be expandedcorrectly.





0123 E • 0131 E



User response: 1) The compressed file is corruptedbecause there is a problem on the tape. To know if thisis the problem, please issue the following command onthe TSM Server: audit volume <volume_name> fix=noIf there is any problem reported, you could move thedata from that volume to a new one (see commandMOVE DATA) and try again the restore. 2) There arecommunications problems between the TSM Server andthe TSM Client and the results is that the file iscorrupted during the transmission. If you use a gigabitEthernet adapter on the Server please upgrade the carddriver (AIX platform) or add provided by SUNsuggested changes to some system network optionswhich have resolved this problem (SUN platform). 3)Please verify with your network support if during therestore there are no any problems between the TSMClient/Server that is originating the file corruption.

0132 E DSM_RC_NO_SERVER_RESOURCESThe TSM server is out of resources.

Explanation: A lack of a storage resource or amaximum value condition does not allow any newactivity.


User response: Try the operation again at a later time.If the problem continues, contact your TSMadministrator to isolate what resource is unavailable.The TSM administrator can check the TSM serveractivity log for messages that might explain theproblem.

0133 E DSM_RC_FS_NOT_KNOWN The filespace for domain 'domain-name' could notbe found on the TSM server.




0134 E DSM_RC_NO_LEADING_DIRSEP TheobjName field has no leading directoryseparator.

Explanation: The objName field does not have aleading directory separator.



0135 E DSM_RC_WILDCARD_DIR Wildcardsare not allowed in the objNamedirectory path.

Explanation: Wildcards are not allowed in theobjName directory path.



0136 E DSM_RC_COMM_PROTOCOL_ERRORThe session is rejected: There was acommunications protocol error.

Explanation: An unexpected network message wasreceived by the client. This could be caused by networkproblems or a programming error.



0137 E DSM_RC_AUTH_FAILURE Sessionrejected: Authentication failure

Explanation: Authentication failure. You entered anincorrect password.


User response: Enter your correct password. If youcannot remember the correct password, see yoursystem administrator to have a new one assigned foryour node name.

0138 E DSM_RC_TA_NOT_VALID The trustedagent execution/owner permissions areinvalid.

Explanation: The trusted agent execution/ownerpermissions are invalid.


User response: Have your system administrator checkthe installation instructions for the client to ensure thatthe trusted agent permissions are set correctly.

0139 S DSM_RC_KILLED Process killed.

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



0132 E • 0139 S


0145 S DSM_RC_WOULD_BLOCK Trustedagent would block the operation.

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



0146 S DSM_RC_TOO_SMALL The area forthe include/exclude pattern is too small.

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



0147 S DSM_RC_UNCLOSED There is noclosing bracket in the pattern.

Explanation: There is no closing bracket in thepattern. This is a programming failure and the clientprogram ends.



0148 S DSM_RC_NO_STARTING_DELIMITER Include/Exclude patternmust start with a directory delimiter

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



0149 S DSM_RC_NEEDED_DIR_ DELIMITERA beginning or ending directorydelimiter is missing from theInclude/Exclude pattern.

Explanation:

1. The include/exclude pattern has a '...' without abeginning or ending directory delimiter.

2. For Windows, the drive seperator is notimmediately followed by a directory delimiter.



0151 S DSM_RC_BUFFER_OVERFLOW Thedata buffer overflowed.

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



0154 E DSM_RC_NO_COMPRESS_MEMORYInsufficient memory for filecompression/expansion

Explanation: Not enough memory is available to dodata compression or expansion. For a restore orretrieve, the file cannot be recalled from the server untilmore storage is made available. For a backup orarchive, try running without compression if storagecannot be made available.


User response: Free up extra storage for the operationto continue, or run the backup or archive processwithout compression enabled.

0155 T DSM_RC_COMPRESS_GREWCompressed Data Grew

Explanation: The size of the file after compression isgreater than the size of the file before compressed.

System action: Even though the size of the fileincreased, the file is compressed.


0156 E DSM_RC_INV_COMM_METHOD Anunsupported communications methodwas specified.

Explanation: None.


User response: Specify a communications interfacethat is supported by the TSM client on your operatingsystem. See the TSM client manual for your operatingsystem for further information on configuring TSMclient communications.

0157 S DSM_RC_WILL_ABORT Thetransaction will be aborted.

Explanation: The server encountered an error and willabort the transaction.

System action: The transaction will be aborted. Thereason code is passed on the dsmEndTxn call.

User response: Issue the dsmEndTxn with a vote ofDSM_VOTE_COMMIT and examine the reason code.

0145 S • 0157 S


0158 E DSM_RC_FS_WRITE_LOCKEDDestination file or directory is writelocked




0159 I DSM_RC_SKIPPED_BY_USER A filewas skipped during a restore operationbecause the file is off line and theapplication has chosen not to wait for atape mount.

Explanation: A file was skipped during a restoreoperation because the file is off line and the applicationhas chosen not to wait for a tape mount.


User response: Verify the application sets themountWait value correctly on dsmBeginGetData.

0160 E DSM_RC_TA_NOT_FOUND Unable tofind Trusted Agent module.

Explanation: TSM was unable to find the TSM TrustedAgent module in the specified directory. The name ofthe TSM Trusted Agent module is dsmtca.


User response: Make sure the Trusted Agent moduleis in the directory specified by DSMI_DIR.

0162 E DSM_RC_FS_NOT_READY Filesystem/drive not ready




0164 E DSM_RC_FIO_ERROR Fileinput/output error


System action: File or file system is skipped.


0165 E DSM_RC_WRITE_FAILURE File writeerror




0166 E DSM_RC_OVER_FILE_SIZE_ LIMITFile exceeds system/user file limits

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



0167 E DSM_RC_CANNOT_MAKE Cannotmake file/directory



User response: Ensure that you have the properauthorization to create the directory for file beingrestored or retrieved. Make sure that you have writeaccess.

0168 E DSM_RC_NO_PASS_FILE Password fileis not available.

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


User response: The root user must set and store a newpassword.

0169 E DSM_RC_VERFILE_OLDPASSWORDACCESS is GENERATE,but password needed for server'server-name'.Either the password is not stored locally,or it was changed at the server.

Explanation: Either the password is not stored locally,or it was changed at the server.

System action: TSM prompts you for the password ifTSM is running in the foreground.

User response: If TSM was running as a backgroundprocess, issue any TSM command from the foreground.Enter the password in answer to the prompt. Then tryyour background TSM command again.

0158 E • 0169 E


0173 E DSM_RC_INPUT_ERROR The processis running in a non-interactive mode,but requires user input.

Explanation: This process requires keyboard input,but non-interactive processes are unable to read inputfrom keyboard.


User response: Perform the following actions toresolve this error:

v Run the product in interactive mode.

v Ensure your password is set correctly.

0174 E DSM_RC_REJECT_PLATFORM_MISMATCH Session rejected: Nodetype mismatch

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


User response: If you need a new node name, seeyour system administrator to assign a new one to you.Generally, you have a unique node name for eachmachine and operating system pair that requires accessto the server.

0175 E DSM_RC_TL_NOT_FILE_OWNER Notfile owner

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

System action: TSM skips the file.


0177 S DSM_RC_UNMATCHED_QUOTEQuotes are not matched



User response: Correct the pattern by using matchingquotes in the syntax.

0184 E DSM_RC_TL_NOBCG The managementclass for this file does not have a validbackup copy group.This file will not be backed up.

Explanation: The management class for this file doesnot have a backup copy group specified. This file willnot be backed up.


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

0185 W DSM_RC_TL_EXCLUDED File'file-namefile-namefile-name' excluded byInclude/Exclude list

Explanation: You can not back up, archive, or migratefiles that are excluded.

System action: TSM does not process the file.

User response: If the file is intentionally excluded,then this message can be ignored. Otherwise modifythe include/exclude list, restart the client, and try theoperation again. Contact your TSM administrator forfurther assistance.

0186 E DSM_RC_TL_NOACG The managementclass for this file does not have a validarchive copy group.This file will not be archived.

Explanation: The management class for this file doesnot have an archive copy group specified. This file willnot be archived.


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

0187 E DSM_RC_PS_INVALID_ARCHMCInvalid management class entered

Explanation: You entered an invalid managementclass.

System action: TSM is unable to do the requestedoperation.

User response: Retry the operation using a validmanagement class.

0188 S DSM_RC_NO_PS_DATA Either thenode does not exist on the server orthere is no active policy set for thenode.

Explanation: This error occurs when you try to accessanother node's data. Either the node is not registeredwith the TSM server, or there is no active policy set forthe node.


User response: Verify that the node whose data youare trying to access is registered with the TSM server. Ifyou have more than one TSM server, make sure youare connecting to the correct server, then try theoperation again. If the problem persists, contact yourTSM administrator for further assistance.

0173 E • 0188 S


0189 S DSM_RC_PS_INVALID_DIRMC Themanagement class assigned todirectories does not exist.




0190 S DSM_RC_PS_NO_CG_IN_DIR_MCThere is no backup copy group in themanagement class used for directories.




0231 E DSM_RC_ABORT_MOVER_TYPEUnknown Remote Mover type

Explanation: The specified Remote Mover type isunknown.



0232 E DSM_RC_ABORT_ITEM_IN_USE AnOperation for the requested node andfilespace is already in progress.

Explanation: A request has been made to use a datamover to perform an operation for the indicated nodeand filespace. Since an operation for this node andfilespace is already in progress, the new operationcannot be performed.



0233 E DSM_RC_ABORT_LOCK_CONFLICTSystem resource in use

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



0234 E DSM_RC_ABORT_SRV_PLUGIN_COMM_ERROR Server plugincommunication error

Explanation: Communication between a server pluginmodule and a NAS filer failed.



0235 E DSM_RC_ABORT_SRV_PLUGIN_OS_ERROR Server plugin detectedunsupported NAS filer operatingsystem.

Explanation: A plugin module detected that a NASfiler is running an unsupported operating system oroperating system level.



0236E DSM_RC_ABORT_CRC_FAILED TheCRC received from the Server does notmatch the CRC calculated by the client.

Explanation: The server sent a CRC for a buffer. Theclient calculated a CRC for the same buffer. These didnot match. The mismatch indicates a communicationfailure.

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

User response: Check the trace log for additionalinformation and retry the operation. If the problempersists, contact your system administrator.

0237E DSM_RC_ABORT_INVALID_GROUP_ACTION An invalid operationwas attempted on a group leader orgroup member.

Explanation: An invalid operation was attempted on alogical group.


User response: Retry a valid operation.

0189 S • 0237E


0238E DSM_RC_ABORT_DISK_ UNDEFINEDRemote disk not defined.

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


User response: Define the proper remote disk.

0239E DSM_RC_ABORT_BAD_DESTINATION Input destination doesnot match expected destination.

Explanation: Input destination does not matchexpected destination.


User response: Retry operation with properdestination.

0240E DSM_RC_ABORT_DATAMOVER_NOT_AVAILABLE Data mover is notavailable.

Explanation: Data mover is not available.


User response: Retry operation with a proper Datamover.

0241E DSM_RC_ABORT_STGPOOL_COPY_CONT_NO Operation failed because thecopy continue option was set to NO.

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


User response: This abort code indicates that a storeoperation, like backup or archive failed because thecopy continue option was set to NO. The sysadmin willneed to resolve the problem on the server end.

0242E DSM_RC_ABORT_RETRY_SINGLE_TXN Transaction failed because of aproblem during a store operation.

Explanation: Transaction failed because of a problemduring a store operation. This error is typical when thenext storage pool has a different copy storage pool listand we switch to this pool in the middle of atransaction.

System action: Transaction is aborted.

User response: Resend objects in separate transactions.

0245 E DSM_RC_ABORT_PATH_RESTRICTED The current clientconfiguration does not comply with thevalue of the DATAWRITEPATH orDATAREADPATH server option for thisnode.

Explanation: The values of the DATAWRITEPATHand DATAREADPATH server options specify where theclient is allowed to send data, and where data is readfrom. The values for the specified node name shouldcorrespond with the client configuration. For example,you will get this error message if DATAWRITEPATHcontains a LAN value and the client is configured touse LAN-free protocol, or vice versa.


User response: Check the client, server, and storageagent logs to determine why the client was not able tosend data LAN-free. Make sure the client configurationand server options are compatible.

0247 E DSM_RC_ABORT_INSERT_NOT_ALLOWED This server does not supportbackup operations.

Explanation: This server only supports archiveoperations, backup is not allowed.


User response: Use only archive operations with thisserver.

0248 E DSM_RC_ABORT_DELETE_NOT_ALLOWED Deleting this object: "fshlll"is not allowed.

Explanation: The object is either under a hold andcannot be deleted, or it is on a retention-protectionenabled server and has not expired.

System action: The object is skipped and processingcontinues.

User response: Check the status of the object througha query to see if it is held, or when it expires.

0249 E DSM_RC_ABORT_TXN_LIMIT_EXCEEDED The number of objects inthis transaction exceedTXNGROUPMAX values.

Explanation: There are too many objects in thistransaction.


User response: Try the operation again with fewerobjects in the transaction, or increase theTXNGROUPMAX value on the server.

0238E • 0249 E


0250 E DSM_RC_ABORT_OBJECT_ALREADY_HELD fshlll is already underhold.

Explanation: One of the objects in the transaction Thespecified object is already under hold, and it cannot beplaced under a new hold.

System action: The current operation ends. This objectis skipped and processing continues.

User response: Issue a query to see the status of theobjects, and try the operation again, without the objectthat is already held.

0292 E DSM_RC_TCA_FORK_FAILED Errorstarting the Trusted CommunicationAgent process.

Explanation: An error has occurred starting theTrusted Communication Agent process; specifically, thefork() function has failed.



0295 E DSM_RC_TCA_INVALID_REQUESTThe TSM Trusted Communication Agentreceived an invalid request.

Explanation: The Trusted Communication Agent isinvoked by the TSM client and has received anunknown request argument in the call.


User response: It is possible the TrustedCommunication Agent was mistakenly invoked by aprocess other than the TSM client. If that is not thecase, then this is an internal error. If the problemrecurs, contact your IBM service representative.

0296 E DSM_RC_TCA_NOT_ROOT This actionrequires TSM administrative authorityon this system.

Explanation: An activity has been attempted that mustbe performed by the TSM administrator (for example,open registration, filespace delete or password update).


User response: If the activity is required, theadministrator for this system must perform it.

0297 E DSM_RC_TCA_SEMGET_ERROR Errorallocating semaphores.

Explanation: An error has occurred because thesemaphores you are attempting to allocate have becomeinsufficient.


User response: Ask your system administrator forassistance, and possibly increase the number ofsemaphores in your system.

0298 E DSM_RC_TCA_SEM_OP_ERROR Errorsetting semaphore value or waiting onsemaphore.

Explanation: An error has occurred while attemptingto set or wait on a semaphore.



0400 E DSM_RC_INVALID_OPT An invalidoption was found during optionparsing.

Explanation: An invalid option was found.


User response: Verify the options in dsm.opt, dsm.sys,and the options string. Check the error log for moredetails about the error. on the AS/400 platform, verifythe options in *LIB/QOPTTSM(APIOPT).

0405 E DSM_RC_NO_HOST_ADDRTCPSERVERADDRESS not defined forthis server in the System Options File

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


User response: See the TSM administrator for yoursystem, and make sure that the server to which you aretrying to connect, has a valid TCPSERVERADDRESSdefined in the system options file.

0406 S DSM_RC_NO_OPT_FILE Options file'file-name' could not be found, or itcannot be read.

Explanation: Common reasons for this error include:

v The default options file does not exist.

v You specified the -OPTFILE option when starting theIBM Tivoli Storage Manager client, but the optionsfile you provided does not exist.

v The DSM_CONFIG (or DSMI_CONFIG if you areusing the IBM Tivoli Storage Manager API)environment variable specifies an options file thatdoes not exist.

v You specified the -OPTFILE option when starting theIBM Tivoli Storage Manager client, but the optionsfile that you provided is not in the standard file

0250 E • 0406 S


encoding of the system. For example, on Windowsthe expected file encoding is ANSI.

v You specified the -OPTFILE option when starting theIBM Tivoli Storage Manager client, but the optionsfile that you provided does not have appropriateread permissions for the user that is running theoperation.

System action: IBM Tivoli Storage Manager clientprocessing stops.

User response: Make sure that the options file youwant to use exists, it has the read rights set for the userthat is running the operation, and it is in the standardfile encoding of the system. For example, on Windowsthe expected file encoding is ANSI. Review theconfiguration information in the IBM Tivoli StorageManager client manual specific to your operatingsystem. If the problem persists, ask your IBM TivoliStorage Manager administrator for further assistance.

0408 E DSM_RC_MACHINE_SAME A virtualnode name must not equal either a nodename or the system host name.

Explanation: A VIRTUALNODENAME option wasentered with a name the same as either a NODENAMEoption or the system host name.

System action: Initialization fails and the programends.

User response: If the virtual node name entered wasthe same as the host name, remove the virtual nodename option. If it was the same as the node nameoption, you can remove either one, depending upon theintended usage. Node name is used to assign analternate name to your system. Virtual node name isused to access another system's server data.

0409 E DSM_RC_INVALID_SERVER Servername not found in System Options File

Explanation: The system options file does not containthe SERVERNAME option.


User response: See the TSM administrator for yoursystem, and make sure that the system options filecontains the server name.

0410 E DSM_RC_INVALID_KEYWORD Aninvalid option keyword was foundduring option parsing.

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


User response: Correct the spelling of the optionkeywords. Verify that the dsmInit configuration fileonly has a subset of the dsm.sys options. Check theerror log for more details about the error.

0411 S DSM_RC_PATTERN_TOO_COMPLEXThe include or exclude pattern cannotbe parsed.

Explanation: The pattern is formatted incorrectly or istoo complex for TSM to interpret.


User response: Verify that the include or excludepattern is specified correctly. If the pattern is correct,then contact IBM technical support for furtherassistance.

0412 S DSM_RC_NO_CLOSING_BRACKETInclude/Exclude pattern is missing aclosing bracket

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



0426 E DSM_RC_CANNOT_OPEN_TRACEFILE Initialization functionscannot open the trace file specified.

Explanation: The file could not be opened duringinitialization. The specified path might be incorrect. It isalso possible that the current user does not havepermission to write to the tracefile in the directoryspecified. It is also possible that no space is available atthe tracefile location.


User response: Make sure the tracefile option pointsto a valid path and that the user has properpermissions to write to the specified file.

0427 E DSM_RC_CANNOT_OPEN_LOGFILEInitialization functions cannot open theError Log file specified.

Explanation: The Error Log file could not be openedduring initialization. The specified path may beincorrect. It is also possible that the current user doesnot have permission to write to the logfile in thedirectory specified. It is also possible that no space isavailable at the given logfile location.


User response: Make sure the logfile option points toa valid path and that the user has proper permissionsto write to the file specified.

0408 E • 0427 E


0600 E DSM_RC_DUP_LABEL A duplicatevolume label exists. The operationcannot continue.

Explanation: For removable media, TSM uses thevolume label as the file space name. To prevent datafrom different volumes being stored in the same filespace on the TSM server, backup or archive ofremovable media volumes having duplicate volumelabels is not allowed.


User response: Change the volume labels on theremovable media volumes so that there are noduplicate labels. Then restart TSM and try theoperation again.

0601 E DSM_RC_NO_LABEL The drive has nolabel. The operation cannot continue.

Explanation: Backup or archive of removable mediarequires that the media have a volume label. Anattempt was made to back up or archive data on aremovable volume that has no label.


User response: Create a volume label on theremovable media, then try the operation again.

0610 E DSM_RC_NLS_CANT_OPEN_TXTUnable to open message text file.

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


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

0611 E DSM_RC_NLS_CANT_READ_HDRUnable to use message text file.

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



0612 E DSM_RC_NLS_INVALID_CNTL_ RECUnable to use message text file.

Explanation: The system is unable to use the messagetxt file (dscenu.txt or dsmclientV3.cat for AIX) becauseof an invalid control record. On the AS/400 platformthis file is QANSAPI/QAANSENU(TXT).



0613 E DSM_RC_NLS_INVALID_DATE_ FMTInvalid value for DATEFORMATspecified.

Explanation: An invalid value is specified forDATEFORMAT.



0614 E DSM_RC_NLS_INVALID_TIME_ FMTInvalid value for TIMEFORMATspecified.

Explanation: An invalid value is specified forTIMEFORMAT.



0615 E DSM_RC_NLS_INVALID_NUM_FMTInvalid value for NUMBERFORMATspecified.

Explanation: An invalid value is specified forNUMBERFORMAT.



0620 E DSM_RC_LOG_CANT_BE_OPENEDUnable to open error log file.




0600 E • 0620 E


0621 E DSM_RC_LOG_ERROR_WRITING_TO_LOG The log file cannot be writtento.

Explanation: There was an error writing to the logfile.


User response: Verify the DSMI_LOG value andaccess permission. on the AS/400 platform, verify thevalue specified for ERRORLOGNAME in the APIoptions file.

0622 E DSM_RC_LOG_NOT_SPECIFIED Thelog file name was not specified.




0927 E DSM_RC_NOT_ADSM_AUTHORIZEDOnly a TSM authorized user canperform this Action.

Explanation: User must be a TSM authorized user toperform this action. User is not password authorizedand this action requires authorization.


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

961 E DSM_RC_DIRECT_STORAGE_AGENT_UNSUPPORTED Directconnection to the Storage Agent is notallowed.

Explanation: You cannot connect directly to theStorage Agent.


User response: To perform Lanfree operations usingthe Storage Agent, specify the ENABLELANFREEoption in your options file, and restart the process.

963 E DSM_RC_FS_NAMESPACE_DOWNLEVEL The long namespace hasbeen removed from the local filespace.If you wish to proceed with thebackup/archive operation, rename yourfilespace on the server.

Explanation: TSM has detected that the servernamespace is NTW:LONG, but the local volume doesnot have long name support. If you would like to backup the volume using the short names, rename thefilespace on the server. If you would like to back upusing long names, add the long namespace supportback to the volume in question.


User response: Add the long namespace support tothe volume or rename(remove) the correspondingserver filespace.

0996 E DSM_RC_SERVER_DOWNLEVEL_FUNC The TSM server is downleveland does not support the requestedfunction. See error log for versioninformation.

Explanation: The function being used requires a morecurrent TSM Server.


User response: Upgrade your TSM Server to a levelthat supports this function. See error log for versioninformation.

0997 E DSM_RC_STORAGEAGENT_DOWNLEVEL The TSM Storage Agentis downlevel and does not support therequested function. See error log forversion information.

Explanation: The function being used requires a morecurrent TSM Storage Agent.


User response: Upgrade your TSM Storage Agent to alevel that supports this function. See error log forversion information.

0998 E DSM_RC_SERVER_AND_SA_DOWNLEVEL The TSM Server andTSM Storage agent are downlevel anddo not support the requested function.See error log for version information.

Explanation: The function being used requires a morecurrent TSM Server and TSM Storage agent


User response: Upgrade your TSM Server and TSMStorage agent to a level that supports this function. Seeerror log for version information.

0621 E • 0998 E


1376 E DSM_RC_DIGEST_VALIDATION_ERROR Error processing 'filespacenamepath-namefile-name'; end-to-enddigest validation failed.

Explanation: Cryptographic digest of the restored orretrieved data did not match the digest generatedduring the backup or archive operation. Possible causesare a transmission error, data corruption, or a hashcollision.


User response: Try the restore operation again. If theproblem persists, contact IBM technical support foradditional assistance.

2000 E DSM_RC_NULL_OBJNAME The objectname pointer is NULL.

Explanation: There is no value provided for the objectname pointer.


User response: Provide an address for thedsmObjName structure.

2001 E DSM_RC_NULL_DATABLKPTR Thedata block pointer is NULL.

Explanation: There is no value provided for the datablock pointer.


User response: Provide an address for the DataBlkstructure.

2002 E DSM_RC_NULL_MSG msg parameterfor dsmRCMsg is a NULL pointer.

Explanation: The message parameter for dsmRCMsgis a NULL pointer.


User response: Allocate enough space for the messageparameter.

2004 E DSM_RC_NULL_OBJATTRPTR Theobject attribute pointer is NULL.

Explanation: There is no value provided for the objectattribute pointer.


User response: Provide an address for the ObjAttrstructure.

2006 E DSM_RC_NO_SESS_BLK There is noserver session information.

Explanation: The server did not respond with thesession information.


User response: Verify the server status.

2007 E DSM_RC_NO_POLICY_BLK There isno server policy information.

Explanation: The server did not respond with thepolicy information.


User response: Verify the server policy definitions.

2008 E DSM_RC_ZERO_BUFLEN The dataBlkbufferLen value is zero.

Explanation: The value for the dataBlk bufferLen iszero.


User response: Provide a non-zero value for thebufferLen.

2009 E DSM_RC_NULL_BUFPTR The dataBlkbufferPtr is NULL.

Explanation: There is no value provided for thedataBlk bufferPtr.


User response: Provide an address for the bufferPtr.

2010 E DSM_RC_INVALID_OBJTYPE TheobjType is invalid.

Explanation: The value for the objType is invalid.


User response: The value for dsmObjName.objTypemust be:

DSM_OBJ_FILE or DSM_OBJ_DIRECTORY forBackup, or

DSM_OBJ_FILE for Archive.

2011 E DSM_RC_INVALID_VOTE ThedsmEndTxn vote is invalid.

Explanation: The dsmEndTxn vote is invalid.

1376 E • 2011 E



User response: The vote must beDSM_VOTE_COMMIT or DSM_VOTE_ABORT.

2012 E DSM_RC_INVALID_ACTION Theupdate action is invalid.

Explanation: The dsmUpdateFS or dsmUpdateObjaction is invalid.


User response: Correct the action value. Valid valuesare defined in dsmapitd.h and documented in ourUsing the API book.

2014 E DSM_RC_INVALID_DS_HANDLEThere was an error in the TSM APIinternals.

Explanation: The system encountered an error in theAPI internals.


User response: Shut down the process and retry theoperation. Verify that any previous dsmInit calls werecleaned up and terminated by a dsmTerminate call. Ifthe problem continues, contact your systemadministrator or service representative.

2015 E DSM_RC_INVALID_REPOS Therepository type is invalid.

Explanation: The repository type is invalid.


User response: For dsmDeleteFS the repository mustbe one of the following:

v DSM_ARCHIVE_REP

v DSM_BACKUP_REP

v DSM_REPOS_ALL.

2016 E DSM_RC_INVALID_FSNAME Filespacename should start with the directorydelimiter.

Explanation: The filespace name is invalid.


User response: Filespace name should start with thedirectory delimiter.

2017 E DSM_RC_INVALID_OBJNAME Theobject name is either an empty string orhas no leading delimiter.

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


User response: Verify the format of the dsmObjNamefull path.

2018 E DSM_RC_INVALID_LLNAME Lowlevel qualifier of the object nameshould start with the directory delimiter.

Explanation: The low level qualifier for the objectname is invalid.


User response: Start the low level qualifier of theobject name with the directory delimiter.

2019 E DSM_RC_INVALID_OBJOWNER Theobject owner is invalid.

Explanation: The object owner must be either the rootuser, or the object owner must be the same as thesession owner.


User response: Verify the session owner and objectowner.

2020 E DSM_RC_INVALID_ACTYPE ThedsmBindMC sendType is invalid.

Explanation: The dsmBindMC sendType is invalid.



stBackup

stArchive

stBackupMountWait

stArchiveMountWait

2021 E DSM_RC_INVALID_RETCODE no textavailable for this return code.

Explanation: The dsmRC parameter for dsmRCMsg isan unsupported return code.



2012 E • 2021 E


2022 E DSM_RC_INVALID_SENDTYPE ThedsmSendObj sendType is invalid.

Explanation: The dsmSendObj sendType is invalid.



stBackup

stArchive

stBackupMountWait

stArchiveMountWait

2023 E DSM_RC_INVALID_PARAMETER ThedsmDeleteObj delType is invalid.

Explanation: The dsmDeleteObj delType is invalid.


User response: The delType must be dtBackup ordtArchive.

2024 E DSM_RC_INVALID_OBJSTATE Thequery Backup objState is invalid.

Explanation: The query Backup objState is invalid.


User response: The qryBackupData.objState must beone of the following:

DSM_ACTIVE

DSM_INACTIVE

DSM_ANY_MATCH

2025 E DSM_RC_INVALID_MCNAME Themanagement class name was not found.

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


User response: Verify the management class name.

2026 E DSM_RC_INVALID_DRIVE_CHAR Thedrive letter is not an alphabeticcharacter.

Explanation: The drive letter is not an alphabeticcharacter. This return code is valid on MicrosoftWindows only.


User response: Verify that the drive designation is an

alphabetic character. The referenced field isdsmDosFSAttrib.driveLetter.

2027 E DSM_RC_NULL_FSNAME The RegisterFilespace name is NULL.

Explanation: There is no value provided for theRegister Filespace name.


User response: Provide a filespace name ondsmRegisterFS.

2028 E DSM_RC_INVALID_HLNAME Highlevel qualifier of the object nameshould start with the directory delimiter.

Explanation: The high level qualifier for the objectname is invalid.


User response: High level qualifier of the object nameshould start with the directory delimiter.

2029 E DSM_RC_NUMOBJ_EXCEED Thenumber of objects on dsmBeginGetDataexceeds DSM_MAX_GET_OBJ |DSM_MAX_PARTIAL_GET_OBJ.

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


User response: Check the number of objects beforecalling dsmBeginGetData. If it is greater thanDSM_MAX_GET_OBJ |DSM_MAX_PARTIAL_GET_OBJ, then issue multipleGet call sequences.

2030 E DSM_RC_NEWPW_REQD The newpassword value is NULL or blank.

Explanation: There is no value provided for newpassword.


User response: Provide a new password ondsmChangePW.

2022 E • 2030 E


2031 E DSM_RC_OLDPW_REQD The oldpassword value is NULL or blank.

Explanation: There is no value provided for oldpassword.


User response: Provide an old password ondsmChangePW.

2032 E DSM_RC_NO_OWNER_REQD OndsmInit, the owner is not allowed toestablish a session whenPASSWORDACCESS=generate.

Explanation: PASSWORDACCESS=GENERATEestablishes a session with the current login user as theowner. The application should set clientOwnerNamePto NULL when PASSWORDACCESS=GENERATE is ineffect.

System action: The system returns to the callingprocedure. Whether the application can continueprocessing depends on how the application handles theerror.

User response: This message applies to applicationsthat utilize the TSM API, and is intended primarily forthe vendor of the application for which the message isissued. Depending on the application, this could be aconfiguration issue.

Consult the documentation for the application andverify that the application is configured correctly. If theproblem persists, contact the application vendor forfurther assistance.

2033 E DSM_RC_NO_NODE_REQD OndsmInit, the node is not allowed whenPASSWORDACCESS=generate.

Explanation: PASSWORDACCESS=generateestablishes a session with the current hostname as thenode.


User response: When usingPASSWORDACCESS=generate, set clientNodeNameP toNULL.

2034 E DSM_RC_KEY_MISSING The key fileis missing.

Explanation: The key file for Tivoli Data Protectionapplication client for Oracle cannot be found.


User response: Ensure that you have ordered theTivoli Data Protection application client which contains

TDP for Oracle, and install the key file.

2035 E DSM_RC_KEY_BAD The key filecontent is invalid.

Explanation: The key file content for Tivoli DataProtection application client for Oracle is invalid.


User response: Ensure that you have ordered theTivoli Data Protection application client which containsthe TDP for Oracle, and install the key file.

2041 E DSM_RC_BAD_CALL_SEQUENCE Thesequence of calls is invalid.

Explanation: Then API requires function calls to bemade in a specific sequence. The function calls werenot made in the expected sequence. The error can betriggered by the following issues:

v An error in the network.

v A bug in the TSM API.

v A bug in the TSM server.

v A bug in the application (IBM or third party) thatuses the TSM API.


User response: An end user can respond in thefollowing ways:

v Check the network for errors.

v Look for clues in the TSM server activity log file,TSM client side dsierror.log log file, and log files thatare specific to the problem application.

v Search the IBM support pages for APARs that matchthe problem. The TSM Manager support site is atTivoli Storage Manager Support Portal(http://www.ibm.com/support/entry/portal/product/tivoli/tivoli_storage_manager)

v If the API application is developed by a third party(not IBM), search that third party's support pages forknown issues that match the problem.

If none of the above actions resolve the problem, reportthe problem to the vendor of the application that usesthe TSM API.

A developer of an application that uses the TSM APImust investigate the reason for the problem, includingreviewing the TSM API state diagram. The TSM APIstate diagram is in the product documentation at TivoliStorage Manager product documentation(http://www.ibm.com/support/knowledgecenter/SSGSG7)

2031 E • 2041 E









2042 E DSM_RC_INVALID_TSMBUFFER ThetsmBuffHandle is invalid, or the valueof dataPtr is invalid.

Explanation: An invalid value for a handle or dataPtrhas been passed into the API.


User response: There is a problem with the callingapplication. Verify the values of the tsmBuffHandle anddataptr passed to the API.

2043 E DSM_RC_TOO_MANY_BYTES Thenumber of bytes copied into thetsmBuffer is larger than the allowedvalue.

Explanation: An invalid number of bytes was copiedto a tsmBuffer.


User response: There is a problem with the callingapplication. Verify the number of bytes copied into thetsmBuffer.

2044 E DSM_RC_MUST_RELEASE_BUFFERdsmTerminate cannot finish because theapplication is holding on to 1 or moretsmBuffers.

Explanation: An application is trying to terminate asession, but is still holding some tsmBuffers.


User response: The application must return all buffersfor this session by calling tsmReleaseBuffer, and thenissue dsmTerminate.

2045 E DSM_RC_BUFF_ARRAY_ERROR Aninternal error occurred in the tsmBufferarray.

Explanation: An internal API buffer array erroroccurred.


User response: Try the operation again. If the problemcontinues, contact your system administrator or servicerepresentative.

2046 E DSM_RC_INVALID_DATABLK Whenusing useTsmBuffers, dataBlk must beNULL in calls to dsmSendObj anddsmGetObj.

Explanation: The value for dataBlk must be NULLwhen using useTsmBuffers.


User response: There is a problem with the callingapplication. Contact your application provider

2047 E DSM_RC_ENCR_NOT_ALLOWEDEncryption is not allowed when usinguseTsmBuffers.



User response: Try the operation again, without usinguseTsmBuffers, or disable encryption for this operation.

2048 E DSM_RC_OBJ_COMPRESSED Thisobject cannot be restored/retrieved usinguseTsmBuffers, because it iscompressed.

Explanation: useTsmBuffers does not supportcompression.



2049 E DSM_RC_OBJ_ENCRYPTED This objectcannot be restored/retrieved usinguseTsmBuffers, because it is encrypted.




2050 E DSM_RC_WILDCHAR_NOTALLOWEDOn dsmSendObj, wildcards are notallowed for the objName.

Explanation: On dsmSendObj, wildcards are notallowed for the objName.


User response: Provide a fs, hl, and ll on thedsmObjName.

2042 E • 2050 E


2051 E DSM_RC_POR_NOT_ALLOWED Whenusing useTsmBuffers, a restore/retrievewith partial object restore is notallowed.

Explanation: useTsmBuffers does not support partialobject restore.


User response: Make sure the calling application iseither using Partial object restore or useTsmBuffers.

2052 E DSM_RC_NO_ENCRYPTION_KEY Noencryption key was found. If you areusing -encryptkey=prompt make surethere is a value in theencryptionPasswordP field and thatbEncryptKeyEnabled is set to true.

Explanation: There was no encryption key found inthe password file, or no key was provided by theapplication.


User response: If you are using -encryptkey=prompt,make sure there is a value in encryptionPasswordP andthat bEncryptKeyEnabled is set to true.

2053 E DSM_RC_ENCR_CONFLICTConflicting encryption key options havebeen specified.

Explanation: When using the ENABLEENCRYPTKEYoption, the parameter bEncryptKeyEnabled for the TSMAPI dsmInitExIn_t and tsmInitExIn_t structures cannotbe set to bTrue.


User response: Either remove theENABLEENCRYPTKEY option from the options file, orset the parameter bEncryptKeyEnabled to bFalse in theprogram using the TSM API.

2060 E DSM_RC_FSNAME_NOTFOUND Thefilespace to delete/set access cannot befound.




2061 E DSM_RC_FS_NOT_REGISTERED OndsmSendObj, dsmDeleteObj, ordsmUpdateFS the filespace is notregistered.

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



2062 W DSM_RC_FS_ALREADY_REGED OndsmRegisterFS the filespace is alreadyregistered.

Explanation: On dsmRegisterFS the filespace isalready registered.



2063 E DSM_RC_OBJID_NOTFOUND OndsmBeginGetData the objID is NULL.

Explanation: On dsmBeginGetData, the objID isNULL.


User response: Verify the following:

The dsmGetList is not NULL.

Each objID is not NULL.

The dsmGetList numObjId is not zero.

2064 E DSM_RC_WRONG_VERSION OndsmInit the caller's API version isdifferent than the TSM library version.

Explanation: On dsmInit the caller's API version has ahigher value than the TSM library version.


User response: Install the latest TSM API library andtrusted agent module.

2065 E DSM_RC_WRONG_VERSION_PARMThe caller's structure version is differentthan the TSM library version.

Explanation: The caller's structure version is differentthan the TSM library version.


User response: Ensure that the stVersion field is setwith the value in the header file. Recompile the

2051 E • 2065 E


application with the latest header files.

2070 E DSM_RC_NEEDTO_ENDTXN IssuedsmEndTxn and then begin a newtransaction session.

Explanation: This transaction must be ended and anew one must be started due to one of the followingreasons:

The destination changed.

The byte limit is exceeded

The maximum number of objects is exceeded.


User response: Issue dsmEndTxn and start a newtransaction session.

2080 E DSM_RC_OBJ_EXCLUDED The backupor archive object is excluded fromprocessing.

Explanation: The backup or archive object is excludedfrom processing.


User response: Verify the objName and Exclude lists.

2081 E DSM_RC_OBJ_NOBCG The backupobject does not have a copy group.

Explanation: The backup object does not have a copygroup.



2082 E DSM_RC_OBJ_NOACG The archiveobject does not have a copy group.

Explanation: The archive object does not have a copygroup.



2090 E DSM_RC_APISYSTEM_ERRORMemory used by the TSM API has beencorrupted.

Explanation: Memory used by the TSM API has beencorrupted.


User response: Retry the operation. If the problem

continues, contact your system administrator or servicerepresentative.

2100 E DSM_RC_DESC_TOOLONG ThesendObj Archive description is too long.

Explanation: The sendObj Archive description is toolong.


User response: The sndArchiveData.descr string mustbe less than or equal to DSM_MAX_DESCR_LENGTH.

2101 E DSM_RC_OBJINFO_TOOLONG ThesendObj ObjAttr.objInfo is too long.

Explanation: The sendObj ObjAttr.objInfo is too long.


User response: The objInfo field must be less than orequal to DSM_MAX_OBJINFO_LENGTH.

2102 E DSM_RC_HL_TOOLONG The sendObjdsmObjName.hl is too long.

Explanation: The sendObj dsmObjName.hl is too long.


User response: The hl field must be less than or equalto DSM_MAX_HL_LENGTH.

2103 E DSM_RC_PASSWD_TOOLONG Thepassword, or encryptionPassword stringprovided is too long.

Explanation: The value provided for password orencryptionPassword is too long.


User response: The password or encrypionPasswordfield must be less thanDSM_MAX_VERIFIER_LENGTH.

2104 E DSM_RC_FILESPACE_TOOLONG ThesendObj dsmObjName.fs is too long.

Explanation: The sendObj dsmObjName.fs is too long.


User response: The fs field must be less than or equalto DSM_MAX_FS_LENGTH.

2070 E • 2104 E


2105 E DSM_RC_LL_TOOLONG The sendObjdsmObjName.ll is too long.

Explanation: The sendObj dsmObjName.ll is too long.


User response: The ll field must be less than or equalto DSM_MAX_LL_LENGTH.

2106 E DSM_RC_FSINFO_TOOLONG OnRegisterFS or UpdateFS the fsAttr'sfsInfo is too long.

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


User response: The fsInfo field must be less than orequal to DSM_MAX_FSINFO_LENGTH.

2107 E DSM_RC_SENDDATA_WITH_ZERO_SIZE Cannot Send data with a zero bytesizeEstimate.

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


User response: Set size estimate greater than 0 indsmSendObj.

2110 E DSM_RC_INVALID_ACCESS_TYPEThe dsmSetAccess access Type isinvalid.

Explanation: The dsmSetAccess accessType is invalid.


User response: The accessType must be one of thefollowing:

atBackup

atArchive

2111 E DSM_RC_QUERY_COMM_FAILURECommunications error with serverduring object query

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



2112 E DSM_RC_NO_FILES_BACKUP No fileshave been previously backed up for thisfilename/filespace.

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


User response: Ensure that the correct drive or filesystem was specified and that files are backed up foryou to set access.

2113 E DSM_RC_NO_FILES_ARCHIVE Nofiles have been previously archived forthis filename/filespace.

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


User response: Ensure that the correct drive or filesystem was specified and that files are archived for youto set access.

2114 E DSM_RC_INVALID_SETACCESSInvalid format for Set Access command.

Explanation: The SET ACCESS command must haveat least three operands, the first of which must beeither BACKUP or ARCHIVE. A validly formed filespecification must follow.

System action: Processing stopped, the command isnot executed.

User response: Use the HELP SET ACCESS commandfor complete details of usage, then enter the SETACCESS command using the correct syntax.

2120 E DSM_RC_STRING_TOO_LONG Thefollowing message was too long to logto the server: 'shortened message withmessage number'

Explanation: The message text and inserts are toolarge to send to the server in the available internalbuffer.

System action: The message number message is writtento the local client error log, then shortened and sent tothe server as a part of this message. The message isreduced in length by substituting '...' in the middle ofthe original message.

User response: The message referred to has beenshortened, but describes the error that occurred. See thedocumentation for that message for more information.

2105 E • 2120 E


2200 I DSM_RC_MORE_DATA OndsmGetNextQObj or dsmGetData thereis more available data.

Explanation: On dsmGetNextQObj or dsmGetDatathere is more available data.


User response: Call the function again.

2210 E DSM_RC_BUFF_TOO_SMALL ThedataBlk buffer is too small for the queryresponse.

Explanation: The dataBlk buffer is too small for thequery response.


User response: On dsmGetNextQObj ensure that thedataBlk buffer is at least as big as the query responsestructure.

2228 E DSM_RC_NO_API_CONFIGFILE Theconfiguration file specified on dsmInitcannot be opened.

Explanation: The configuration file specified ondsmInit cannot be opened.


User response: Verify the file name.

2229 E DSM_RC_NO_INCLEXCL_FILE TheInclude/Exclude definition file was notfound.

Explanation: The Include/Exclude definition file wasnot found.


User response: Verify the file name on the Inclexcloption.

2230 E DSM_RC_NO_SYS_OR_INCLEXCLEither the dsm.sys file was not found, orthe Inclexcl file specified in dsm.syswas not found.

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


User response: The dsm.sys file must be in thedirectory referenced by the environment variable

DSMI_DIR. Verify the file name on the Inclexcl optionin the dsm.sys file.

2231 E DSM_RC_REJECT_NO_POR_SUPPORT Partial Object Retrieve is notsupported on this server.

Explanation: The TSM server specified by the userdoes not support partial object retrieve.


User response: Specify a TSM server which supportsthe partial object retrieve function.

2300 E DSM_RC_NEED_ROOT Only a UNIXroot user can execute dsmChangePW ordsmDeleteFS.

Explanation: Only a UNIX root user can executedsmChangePW or dsmDeleteFS.


User response: Run this program as a root user.

2301 E DSM_RC_NEEDTO_CALL_BINDMCYou must issue dsmBindMC beforedsmSendObj.

Explanation: You must issue dsmBindMC beforedsmSendObj.


User response: Modify your program.

2302 I DSM_RC_CHECK_REASON_CODEThe dsmEndTxn vote is ABORT, socheck the reason field.

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


User response: Check the reason field for the codewhich explains why the transaction has been aborted.

2400 E DSM_RC_ALMGR_OPEN_FAIL Licensefile could not be opened.



User response: Check permissions on file. See if the

2200 I • 2400 E


license file is in the correct place.

2401 E DSM_RC_ALMGR_READ_FAIL Readfailure on the license file.

Explanation: The license file was not found, or couldnot be opened because of permissions, or the file iscorrupted.



2402 E DSM_RC_ALMGR_WRITE_FAIL Writefailure on the license file.



User response: Check permissions on file. See iflicense file is in the correct place.

2403 E DSM_RC__ALMGR_DATA_FMT Datain the license file is not in a validformat.

Explanation: The license file is not valid.



2404 E DSM_RC_ALMGR_CKSUM_BAD Thechecksum in the license file does notmatch the licenseregistration string.




2405 E DSM_RC_ALMGR_TRIAL_EXPRD Thisis an expired try and buy license.




2410 E DSM_RC_ORC_INVALID_MODEOracle passed invalid mode

Explanation: Invalid mode passed by Oracle.



2411 E DSM_RC_ORC_NULL_FILENAMEOracle passed null file name

Explanation: Null filename passed by Oracle.



2412 E DSM_RC_ORC_WRONG_BLKSIZEWrong data block size

Explanation: Wrong Block Size



2413 E DSM_RC_ORC_OBJ_EXISTS Objectexists

Explanation: Backup or Restore Object already exists.


User response: If backing up an object, be sure togenerate a unique object name.

2414 E DSM_RC_ORC_NOTSAME_HANDLENot same Oracle handle

Explanation: The handle passed from Oracle is not thesame handle that TSM passed back.



2415 E DSM_RC_ORC_END_OF_FILE End offile reached

Explanation: End of file reached.


User response: None

2401 E • 2415 E


2416 E DSM_RC_ORC_WRONG_RDSTATEWrong Read State

Explanation: The operation must be in READ state.



2417 E DSM_RC_ORC_LOWER_APIVERRuntime API version is outdated

Explanation: Runtime API is lower than compile timeAPI.


User response: Use the WHAT command to find outthe compile time API level. Obtain the same or higherlevel of API library.

2418 E DSM_RC_ORC_WRONG_WRTSTATEWrong write state

Explanation: The operation must be in WRITE state.



2419 E DSM_RC_ORC_INVALID_FLAGInvalid flag passed

Explanation: Invalid flag passed from Oracle.



4580 E DSM_RC_ENC_WRONG_KEY Errorprocessing 'filespace namepath-namefile-name'; invalid encryption key.



User response: Try the restore operation again andprovide the correct key.

4582 E DSM_RC_ENC_NOT_AUTHORIZEDUser is not authorized to encryptfile-space namedirectory_pathfile_name.

Explanation: The user is not authorized to encrypt thefile. Normally, only a IBM Tivoli Storage Managerauthorized user or a root user can use IBM TivoliStorage Manager encryption. However, a certain

combination of PASSWORDACCESS andENCRYPTKEY options may allow encryptionoperations by a non-authorized user.

System action: The file is not backed up or restored.

User response: Log in as a root or IBM Tivoli StorageManager authorized user and try the operation again.See IBM Tivoli Storage Manager Backup-Archive ClientInstallation and User's Guide for the correct usage ofthe ENCRYPTKEY option.

4584 E DSM_RC_ENC_TYPE_UNKOWN Errorprocessing 'filespace namepath-namefile-name': unsupported encryption type.




4600 E DSM_RC_CLUSTER_INFO_LIBRARY_NOT_LOADEDCLUSTERNODE is set to YES but theCluster Information Daemon is notstarted.

Explanation: The HACMP Cluster InformationDaemon must be started in order to specify theCLUSTERNODE option.


User response: Start the HACMP Cluster InformationDameon.

4601 E DSM_RC_CLUSTER_LIBRARY_INVALID CLUSTERNODE is set to YESbut the cluster load library is not valid.

Explanation: The load library that the operatingsystem provides to obtain the cluster name is not valid.A possible cause is an out-of-date load library whichdoes not contain the proper routines this productexpects.


User response: Ensure that the latest cluster softwareis installed on the system.

4602 E DSM_RC_CLUSTER_LIBRARY_NOT_LOADED CLUSTERNODE is setto YES but the cluster software is notavailableon this system.

Explanation: The load library that the operating

2416 E • 4602 E


systems provides to obtain the cluster name is notavailable on this system.


User response: Ensure that the cluster software isinstalled on the system.

4603 E DSM_RC_CLUSTER_NOT_MEMBER_OF_CLUSTER CLUSTERNODE is set toYES but this machine is not a memberof acluster.

Explanation: This machine is not a member of acluster node. Possible causes are that the cluster servicehas not been configured correctly, or that the cluster isin the process of initialization.


User response: Ensure that the cluster software isconfigured properly. If the cluster is in the process ofinitialization, retry the operation at a later time.

4604 E DSM_RC_CLUSTER_NOT_ENABLEDCLUSTERNODE is set to YES but thecluster service is not enabledon this system.

Explanation: The cluster service has not been enabledon this system.


User response: Enable the cluster service on thesystem.

4605 E DSM_RC_CLUSTER_NOT_SUPPORTED The CLUSTERNODEoption is not supported on this system.

Explanation: This option is not supported on thissystem.


User response: Disable the CLUSTERNODE option inthe local options file.

4606 E DSM_RC_CLUSTER_UNKNOWN_ERROR An unexpected error (retcode)occurred while the program was tryingto obtain the cluster name from thesystem.

Explanation: An unknown error occurred while theprogram was trying to obtain the cluster name from thecluster service. The error code is the reason codeprovided directly from the cluster service being used inthis operating system environment.


User response: Consult the documentation for your

clustering software for an explanation of the reasoncode. Insure that your clustering service is operational,then try the TSM operation again.

5702 E DSM_RC_PROXY_REJECT_NO_RESOURCES Proxy Rejected: The TSMserver has run out of memory.

Explanation: There is not enough memory available toallow this operation to continue.


User response: Try the operation again. If the problemcontinues, see your system administrator to increase theamount of memory of the server.

5705 E DSM_RC_PROXY_REJECT_DUPLICATE_ID Proxy Rejected:ASNODENAME and NODENAME areidentical.

Explanation: TSM does not allow the ASNODENAMEand NODENAME option values to be the same.


User response: Use the ASNODENAME option onlyto access another node. It is not necessary to setASNODENAME option to access your own node.Remove ASNODENAME from your option file unlessyou are actually trying to access a node that you havebeen granted authority to access with theadministrative command "Grant Proxynode".

5710 E DSM_RC_PROXY_REJECT_ID_IN_ USEProxy Rejected: The node name youspecified in the ASNODENAME optionis locked.

Explanation: The TSM administrator has locked thenode you specified as the ASNODENAME option.


User response: The TSM server administrator mustunlock the node before you can access it. Try theoperation later, or check with your TSM administrator.

5717 E DSM_RC_PROXY_REJECT_INTERNAL_ERROR Proxy Rejected:The server has an internal error.

Explanation: The client cannot proxy to the nodenamed by the ASNODENAME option because of aninternal server error.



4603 E • 5717 E


5722 E DSM_RC_PROXY_REJECT_NOT_AUTHORIZED Proxy Rejected: Proxyauthority has not been granted to thisnode.

Explanation: The node has not been granted proxyauthority to access the node named by theASNODENAME option. The TSM administrator mustfirst grant proxy authority.



5746 E DSM_RC_PROXY_INVALID_FROMNODE The ASNODENAMEoption is not valid with theFROMNODE option.

Explanation: None.


User response: Remove the ASNODENAME optionfrom the options file or do not use the FROMNODEoption.

5748 E DSM_RC_PROXY_INVALID_ CLUSTERThe ASNODENAME option cannot beused with the CLUSTERNODE option.

Explanation: None.



5749 E DSM_RC_PROXY_INVALID_FUNCTION The operation that is beingattempted cannot be invoked using theASNODENAME option.

Explanation: None.



5801 E DSM_RC_CRYPTO_ICC_ERRORUnexpected error in cryptographylibrary.

Explanation: There was an unexpected error in thecryptography library. See the error log for moreinformation.


User response: Check the error log for ANS1467E todetermine the cause of failure. Verify you TSM client isinstalled properly. If needed, reinstall client and/or

API. If the problem still exists, contact TSM technicalsupport.

5722 E • 5801 E


Appendix. Accessibility features for the Tivoli StorageManager product family

Accessibility features help users who have a disability, such as restricted mobilityor limited vision to use information technology products successfully.

Accessibility features

The IBM Tivoli Storage Manager family of products includes the followingaccessibility features:v Keyboard-only operation using standard operating-system conventionsv Interfaces that support assistive technology such as screen readers

The command-line interfaces of all products in the product family are accessible.

Tivoli Storage Manager Operations Center provides the following additionalaccessibility features when you use it with a Mozilla Firefox browser on aMicrosoft Windows system:v Screen magnifiers and content zoomingv High contrast mode

The Operations Center and the Tivoli Storage Manager server can be installed inconsole mode, which is accessible.

The Operations Center help system is enabled for accessibility. For moreinformation, click the question mark icon on the help system menu bar.

Vendor software

The Tivoli Storage Manager product family includes certain vendor software that isnot covered under the IBM license agreement. IBM makes no representation aboutthe accessibility features of these products. Contact the vendor for the accessibilityinformation about its products.

IBM and accessibility

See the IBM Human Ability and Accessibility Center (http://www.ibm.com/able)for information about the commitment that IBM has to accessibility.


http://www.ibm.com/able

http://www.ibm.com/able

Notices

This information was developed for products and services offered in the U.S.A.

IBM may not offer the products, services, or features discussed in this document inother countries. Consult your local IBM representative for information on theproducts and services currently available in your area. Any reference to an IBMproduct, program, or service is not intended to state or imply that only that IBMproduct, program, or service may be used. Any functionally equivalent product,program, or service that does not infringe any IBM intellectual property right maybe used instead. However, it is the user's responsibility to evaluate and verify theoperation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matterdescribed in this document. The furnishing of this document does not grant youany license to these patents. You can send license inquiries, in writing, to:

IBM Director of LicensingIBM CorporationNorth Castle Drive, MD-NC119Armonk, NY 10504-1785United States of America

For license inquiries regarding double-byte character set (DBCS) information,contact the IBM Intellectual Property Department in your country or sendinquiries, in writing, to:

Intellectual Property LicensingLegal and Intellectual Property LawIBM Japan Ltd.19-21, Nihonbashi-Hakozakicho, Chuo-kuTokyo 103-8510, Japan

The following paragraph does not apply to the United Kingdom or any othercountry where such provisions are inconsistent with local law:INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THISPUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHEREXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESSFOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express orimplied warranties in certain transactions, therefore, this statement may not applyto you.

This information could include technical inaccuracies or typographical errors.Changes are periodically made to the information herein; these changes will beincorporated in new editions of the publication. IBM may make improvementsand/or changes in the product(s) and/or the program(s) described in thispublication at any time without notice.

Any references in this information to non-IBM websites are provided forconvenience only and do not in any manner serve as an endorsement of thosewebsites. The materials at those websites are not part of the materials for this IBMproduct and use of those websites is at your own risk.


IBM may use or distribute any of the information you supply in any way itbelieves appropriate without incurring any obligation to you.

Licensees of this program who want to have information about it for the purposeof enabling: (i) the exchange of information between independently createdprograms and other programs (including this one) and (ii) the mutual use of theinformation which has been exchanged, should contact:

IBM Corporation2Z4A/10111400 Burnet RoadAustin, TX 78758US

Such information may be available, subject to appropriate terms and conditions,including in some cases, payment of a fee.

The licensed program described in this document and all licensed materialavailable for it are provided by IBM under terms of the IBM Customer Agreement,IBM International Program License Agreement or any equivalent agreementbetween us.

Any performance data contained herein was determined in a controlledenvironment. Therefore, the results obtained in other operating environments mayvary significantly. Some measurements may have been made on development-levelsystems and there is no guarantee that these measurements will be the same ongenerally available systems. Furthermore, some measurements may have beenestimated through extrapolation. Actual results may vary. Users of this documentshould verify the applicable data for their specific environment.

Information concerning non-IBM products was obtained from the suppliers ofthose products, their published announcements or other publicly available sources.IBM has not tested those products and cannot confirm the accuracy ofperformance, compatibility or any other claims related to non-IBM products.Questions on the capabilities of non-IBM products should be addressed to thesuppliers of those products.

This information contains examples of data and reports used in daily businessoperations. To illustrate them as completely as possible, the examples include thenames of individuals, companies, brands, and products. All of these names arefictitious and any similarity to the names and addresses used by an actual businessenterprise is entirely coincidental.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, whichillustrate programming techniques on various operating platforms. You may copy,modify, and distribute these sample programs in any form without payment toIBM, for the purposes of developing, using, marketing or distributing applicationprograms conforming to the application programming interface for the operatingplatform for which the sample programs are written. These examples have notbeen thoroughly tested under all conditions. IBM, therefore, cannot guarantee orimply reliability, serviceability, or function of these programs. The sampleprograms are provided "AS IS", without warranty of any kind. IBM shall not beliable for any damages arising out of your use of the sample programs.


Each copy or any portion of these sample programs or any derivative work, mustinclude a copyright notice as follows:Portions of this code are derived from IBM® Corp. Sample Programs.

© Copyright IBM® Corp. _enter the year or years_. All rights reserved.

Trademarks

IBM, the IBM logo, and ibm.com® are trademarks or registered trademarks ofInternational Business Machines Corp., registered in many jurisdictions worldwide.Other product and service names might be trademarks of IBM or other companies.A current list of IBM trademarks is available on the Web at "Copyright andtrademark information" at www.ibm.com/legal/copytrade.shtml.

Adobe is a registered trademark of Adobe Systems Incorporated in the UnitedStates, and/or other countries.

Linear Tape-Open, LTO, and Ultrium are trademarks of HP, IBM Corp. andQuantum in the U.S. and other countries.

Intel and Itanium are trademarks or registered trademarks of Intel Corporation orits subsidiaries in the United States and other countries.

Linux is a registered trademark of Linus Torvalds in the United States, othercountries, or both.

Microsoft, Windows, and Windows NT are trademarks of Microsoft Corporation inthe United States, other countries, or both.

Java™ and all Java-based trademarks and logos are trademarks or registeredtrademarks of Oracle and/or its affiliates.

UNIX is a registered trademark of The Open Group in the United States and othercountries.

Terms and conditions for product documentation

Permissions for the use of these publications are granted subject to the followingterms and conditions.

ApplicabilityThese terms and conditions are in addition to any terms of use for the IBMwebsite.

Personal useYou may reproduce these publications for your personal, noncommercialuse provided that all proprietary notices are preserved. You may notdistribute, display or make derivative work of these publications, or anyportion thereof, without the express consent of IBM.

Commercial useYou may reproduce, distribute and display these publications solely withinyour enterprise provided that all proprietary notices are preserved. Youmay not make derivative works of these publications, or reproduce,distribute or display these publications or any portion thereof outside yourenterprise, without the express consent of IBM.

Rights Except as expressly granted in this permission, no other permissions,

Notices 335

http://www.ibm.com/legal/copytrade.shtml

licenses or rights are granted, either express or implied, to the publicationsor any information, data, software or other intellectual property containedtherein.

IBM reserves the right to withdraw the permissions granted hereinwhenever, in its discretion, the use of the publications is detrimental to itsinterest or, as determined by IBM, the above instructions are not beingproperly followed.

You may not download, export or re-export this information except in fullcompliance with all applicable laws and regulations, including all UnitedStates export laws and regulations.

IBM MAKES NO GUARANTEE ABOUT THE CONTENT OF THESEPUBLICATIONS. THE PUBLICATIONS ARE PROVIDED "AS-IS" ANDWITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED ORIMPLIED, INCLUDING BUT NOT LIMITED TO IMPLIED WARRANTIESOF MERCHANTABILITY, NON-INFRINGEMENT, AND FITNESS FOR APARTICULAR PURPOSE.

Privacy policy considerations

IBM Software products, including software as a service solutions, (“SoftwareOfferings”) may use cookies or other technologies to collect product usageinformation, to help improve the end user experience, to tailor interactions withthe end user, or for other purposes. In many cases no personally identifiableinformation is collected by the Software Offerings. Some of our Software Offeringscan help enable you to collect personally identifiable information. If this SoftwareOffering uses cookies to collect personally identifiable information, specificinformation about this offering’s use of cookies is set forth below.

This Software Offering does not use cookies or other technologies to collectpersonally identifiable information.

If the configurations deployed for this Software Offering provide you as customerthe ability to collect personally identifiable information from end users via cookiesand other technologies, you should seek your own legal advice about any lawsapplicable to such data collection, including any requirements for notice andconsent.

For more information about the use of various technologies, including cookies, forthese purposes, see IBM’s Privacy Policy at http://www.ibm.com/privacy andIBM’s Online Privacy Statement at http://www.ibm.com/privacy/details in thesection entitled “Cookies, Web Beacons and Other Technologies,” and the “IBMSoftware Products and Software-as-a-Service Privacy Statement” athttp://www.ibm.com/software/info/product-privacy.


http://www.ibm.com/privacy

http://www.ibm.com/privacy/details

http://www.ibm.com/software/info/product-privacy

Glossary

A glossary is available with terms and definitions for the IBM Tivoli Storage Manager family of products.

See Tivoli Storage Manager glossary (http://www.ibm.com/support/knowledgecenter/SSGSG7_7.1.3/tsm/glossary.html).

To view glossaries for other IBM products, see http://www.ibm.com/software/globalization/terminology/.


http://www.ibm.com/support/knowledgecenter/SSGSG7_7.1.3/tsm/glossary.html

http://www.ibm.com/support/knowledgecenter/SSGSG7_7.1.3/tsm/glossary.html

http://www.ibm.com/software/globalization/terminology/

http://www.ibm.com/software/globalization/terminology/

IBM®

Product Number: 5608-E015608-E025608-E035608-E075608-E12

Printed in USA