#
# Distributed Storage Manager
#
# OCO Source Materials
#
# (C) Copyright IBM Corporation 1990, 2013
#
#
# Symbolic Message ID and Message Definitions
#
# This file was generated by a program.
# ------> DO NOT MODIFY MANUALLY <------
#
# 0211
API_ObjName_Null=ANS0211E The object name pointer is NULL.
API_ObjName_Null_EXPLANATION=<p>There is no value provided for the object name pointer.</p>
API_ObjName_Null_SYSACT=<p>The system returns to the calling procedure.</p>
API_ObjName_Null_URESP=<p>Provide an address for the dsmObjName structure.</p>
# 0212
API_DataBlk_Null=ANS0212E The data block pointer is NULL.
API_DataBlk_Null_EXPLANATION=<p>There is no value provided for the data block pointer.</p>
API_DataBlk_Null_SYSACT=<p>The system returns to the calling procedure.</p>
API_DataBlk_Null_URESP=<p>Provide an address for the DataBlk structure.</p>
# 0213
API_ObjAttr_Null=ANS0213E The object attribute pointer is NULL.
API_ObjAttr_Null_EXPLANATION=<p>There is no value provided for the object attribute pointer.</p>
API_ObjAttr_Null_SYSACT=<p>The system returns to the calling procedure.</p>
API_ObjAttr_Null_URESP=<p>Provide an address for the ObjAttr structure.</p>
# 0214
API_No_Session_Info=ANS0214E There is no server session information.
API_No_Session_Info_EXPLANATION=<p>The server did not respond with the session information.</p>
API_No_Session_Info_SYSACT=<p>The system returns to the calling procedure.</p>
API_No_Session_Info_URESP=<p>Verify the server status.</p>
# 0215
API_No_Policy_Info=ANS0215E There is no server policy information.
API_No_Policy_Info_EXPLANATION=<p>The server did not respond with the policy information.</p>
API_No_Policy_Info_SYSACT=<p>The system returns to the calling procedure.</p>
API_No_Policy_Info_URESP=<p>Verify the server policy definitions.</p>
# 0216
API_Zero_BufferLen=ANS0216E The dataBlk bufferLen value is zero.
API_Zero_BufferLen_EXPLANATION=<p>The value for the dataBlk bufferLen is zero.</p>
API_Zero_BufferLen_SYSACT=<p>The system returns to the calling procedure.</p>
API_Zero_BufferLen_URESP=<p>Provide a non-zero value for the bufferLen.</p>
# 0217
API_BufferPtr_Null=ANS0217E The dataBlk bufferPtr is NULL.
API_BufferPtr_Null_EXPLANATION=<p>There is no value provided for the dataBlk bufferPtr.</p>
API_BufferPtr_Null_SYSACT=<p>The system returns to the calling procedure.</p>
API_BufferPtr_Null_URESP=<p>Provide an address for the bufferPtr.</p>
# 0218
API_Invalid_ObjType=ANS0218E The objType is invalid.
API_Invalid_ObjType_EXPLANATION=<p>The value for the objType is invalid.</p>
API_Invalid_ObjType_SYSACT=<p>The system returns to the calling procedure.</p>
API_Invalid_ObjType_URESP=<p>The value for dsmObjName.objType must be: <ul style="simple"> <li>DSM_OBJ_FILE or DSM_OBJ_DIRECTORY for Backup, or</li> <li>DSM_OBJ_FILE for Archive.</li> </ul></p>
# 0219
API_Invalid_Vote=ANS0219E The dsmEndTxn vote is invalid.
API_Invalid_Vote_EXPLANATION=<p>The dsmEndTxn vote is invalid.</p>
API_Invalid_Vote_SYSACT=<p>The system returns to the calling procedure.</p>
API_Invalid_Vote_URESP=<p>The vote must be DSM_VOTE_COMMIT or DSM_VOTE_ABORT.</p>
# 0221
API_Internal_Error=ANS0221E There was an error in the TSM API internals.
API_Internal_Error_EXPLANATION=<p>The system encountered an error in the API internals.</p>
API_Internal_Error_SYSACT=<p>The system returns to the calling procedure.</p>
API_Internal_Error_URESP=<p>Shut down the process and retry the operation. Verify that any previous dsmInit calls were cleaned up and terminated by a dsmTerminate call. If the problem continues, contact your system administrator or service representative. </p>
# 0222
API_Invalid_Repository=ANS0222E The repository type is invalid.
API_Invalid_Repository_EXPLANATION=<p>The repository type is invalid.</p>
API_Invalid_Repository_SYSACT=<p>The system returns to the calling procedure.</p>
API_Invalid_Repository_URESP=<p>For dsmDeleteFS the repository must be one of the following: <ul> <li>DSM_ARCHIVE_REP</li> <li>DSM_BACKUP_REP</li> <li>DSM_REPOS_ALL.</li> </ul></p>
# 0223
API_Invalid_Filespace_Name=ANS0223E Filespace name should start with the directory delimiter.
API_Invalid_Filespace_Name_EXPLANATION=<p>The filespace name is invalid.</p>
API_Invalid_Filespace_Name_SYSACT=<p>The system returns to the calling procedure.</p>
API_Invalid_Filespace_Name_URESP=<p>Filespace name should start with the directory delimiter.</p>
# 0224
API_Invalid_ObjName=ANS0224E The object name is either an empty string or has no leading delimiter.
API_Invalid_ObjName_EXPLANATION=<p>The object name is invalid because of an empty string or there is no leading delimiter.</p>
API_Invalid_ObjName_SYSACT=<p>The system returns to the calling procedure.</p>
API_Invalid_ObjName_URESP=<p>Verify the format of the dsmObjName full path.</p>
# 0225
API_Invalid_Lowlevel_Qualifier=ANS0225E Low level qualifier of the object name should start with the directory delimiter.
API_Invalid_Lowlevel_Qualifier_EXPLANATION=<p>The low level qualifier for the object name is invalid.</p>
API_Invalid_Lowlevel_Qualifier_SYSACT=<p>The system returns to the calling procedure.</p>
API_Invalid_Lowlevel_Qualifier_URESP=<p>Start the low level qualifier of the object name with the directory delimiter. </p>
# 0226
API_Invalid_ObjOwner=ANS0226E The object owner is invalid.
API_Invalid_ObjOwner_EXPLANATION=<p>The object owner must be either the root user, or the object owner must be the same as the session owner.</p>
API_Invalid_ObjOwner_SYSACT=<p>The system returns to the calling procedure.</p>
API_Invalid_ObjOwner_URESP=<p>Verify the session owner and object owner.</p>
# 0227
API_Invalid_Bind_Type=ANS0227E The dsmBindMC sendType is invalid.
API_Invalid_Bind_Type_EXPLANATION=<p>The dsmBindMC sendType is invalid.</p>
API_Invalid_Bind_Type_SYSACT=<p>The system returns to the calling procedure.</p>
API_Invalid_Bind_Type_URESP=<p>The sendType must be one of the following: <ul style="simple"> <li>stBackup</li> <li>stArchive</li> <li>stBackupMountWait</li> <li>stArchiveMountWait</li> </ul></p>
# 0228
API_Invalid_SendType=ANS0228E The dsmSendObj sendType is invalid.
API_Invalid_SendType_EXPLANATION=<p>The dsmSendObj sendType is invalid.</p>
API_Invalid_SendType_SYSACT=<p>The system returns to the calling procedure.</p>
API_Invalid_SendType_URESP=<p>The sendType must be one of the following: <ul style="simple"> <li>stBackup</li> <li>stArchive</li> <li>stBackupMountWait</li> <li>stArchiveMountWait</li> </ul></p>
# 0229
API_Invalid_DelType=ANS0229E The dsmDeleteObj delType is invalid.
API_Invalid_DelType_EXPLANATION=<p>The dsmDeleteObj delType is invalid.</p>
API_Invalid_DelType_SYSACT=<p>The system returns to the calling procedure.</p>
API_Invalid_DelType_URESP=<p>The delType must be dtBackup or dtArchive.</p>
# 0230
API_Invalid_ObjState=ANS0230E The query Backup objState is invalid.
API_Invalid_ObjState_EXPLANATION=<p>The query Backup objState is invalid.</p>
API_Invalid_ObjState_SYSACT=<p>The system returns to the calling procedure.</p>
API_Invalid_ObjState_URESP=<p>The qryBackupData.objState must be one of the following: <ul style="simple"> <li>DSM_ACTIVE</li> <li>DSM_INACTIVE</li> <li>DSM_ANY_MATCH</li> </ul></p>
# 0231
API_Mgmt_Class_Not_Found=ANS0231E The management class name was not found.
API_Mgmt_Class_Not_Found_EXPLANATION=<p>A query or send operation is unable to find the management class name. </p>
API_Mgmt_Class_Not_Found_SYSACT=<p>The system returns to the calling procedure.</p>
API_Mgmt_Class_Not_Found_URESP=<p>Verify the management class name.</p>
# 0232
API_Invalid_Drive=ANS0232E The drive letter is not an alphabetic character.
API_Invalid_Drive_EXPLANATION=<p>The drive letter is not an alphabetic character. This return code is valid on Microsoft Windows only.</p>
API_Invalid_Drive_SYSACT=<p>The system returns to the calling procedure.</p>
API_Invalid_Drive_URESP=<p>Verify that the drive designation is an alphabetic character. The referenced field is dsmDosFSAttrib.driveLetter.</p>
# 0233
API_Filespace_Name_NULL=ANS0233E The Register Filespace name is NULL.
API_Filespace_Name_NULL_EXPLANATION=<p>There is no value provided for the Register Filespace name.</p>
API_Filespace_Name_NULL_SYSACT=<p>The system returns to the calling procedure.</p>
API_Filespace_Name_NULL_URESP=<p>Provide a filespace name on dsmRegisterFS.</p>
# 0234
API_New_Password_Req=ANS0234E The new password value is NULL or blank.
API_New_Password_Req_EXPLANATION=<p>There is no value provided for new password.</p>
API_New_Password_Req_SYSACT=<p>The system returns to the calling procedure.</p>
API_New_Password_Req_URESP=<p>Provide a new password on dsmChangePW.</p>
# 0235
API_Old_Password_Req=ANS0235E The old password value is NULL or blank.
API_Old_Password_Req_EXPLANATION=<p>There is no value provided for old password.</p>
API_Old_Password_Req_SYSACT=<p>The system returns to the calling procedure.</p>
API_Old_Password_Req_URESP=<p>Provide an old password on dsmChangePW.</p>
# 0236
API_Owner_Not_Allowed=ANS0236E On dsmInit, the owner is not allowed to establish a session when PASSWORDACCESS=generate.
API_Owner_Not_Allowed_EXPLANATION=<p> PASSWORDACCESS=GENERATE establishes a session with the current login user as the owner. The application should set clientOwnerNameP to NULL when PASSWORDACCESS=GENERATE is in effect. \n\n</p>
API_Owner_Not_Allowed_SYSACT=<p>The system returns to the calling procedure. Whether the application can continue processing depends on how the application handles the error.</p>
API_Owner_Not_Allowed_URESP=<p>This message applies to applications that utilize the TSM API, and is intended primarily for the vendor of the application for which the message is issued. Depending on the application, this could be a configuration issue. </p> <p>Consult the documentation for the application and verify that the application is configured correctly. If the problem persists, contact the application vendor for further assistance.</p>
# 0237
API_Node_Not_Allowed=ANS0237E On dsmInit, the node is not allowed when PASSWORDACCESS=generate.
API_Node_Not_Allowed_EXPLANATION=<p>PASSWORDACCESS=generate establishes a session with the current hostname as the node.</p>
API_Node_Not_Allowed_SYSACT=<p>The system returns to the calling procedure.</p>
API_Node_Not_Allowed_URESP=<p>When using PASSWORDACCESS=generate, set clientNodeNameP to NULL.</p>
# 0238
API_Invalid_Call_Sequence=ANS0238E The sequence of calls is invalid.
API_Invalid_Call_Sequence_EXPLANATION=<p>The sequence of calls is invalid.</p>
API_Invalid_Call_Sequence_SYSACT=<p>The system returns to the calling procedure.</p>
API_Invalid_Call_Sequence_URESP=<p>Verify the transaction call sequence.</p>
# 0239
API_Wildcard_Not_Allowed=ANS0239E On dsmSendObj, wildcards are not allowed for the objName.
API_Wildcard_Not_Allowed_EXPLANATION=<p>On dsmSendObj, wildcards are not allowed for the objName.</p>
API_Wildcard_Not_Allowed_SYSACT=<p>The system returns to the calling procedure.</p>
API_Wildcard_Not_Allowed_URESP=<p>Provide a fs, hl, and ll on the dsmObjName.</p>
# 0240
API_Filespace_Not_Found=ANS0240E The filespace to delete/set access cannot be found.
API_Filespace_Not_Found_EXPLANATION=<p>The filespace to delete cannot be found.</p>
API_Filespace_Not_Found_SYSACT=<p>The system returns to the calling procedure.</p>
API_Filespace_Not_Found_URESP=<p>Verify the filespace name.</p>
# 0241
API_Filespace_Not_Registered=ANS0241E On dsmSendObj, dsmDeleteObj, or dsmUpdateFS the filespace is not registered.
API_Filespace_Not_Registered_EXPLANATION=<p>On dsmSendObj, dsmDeleteObj, or dsmUpdateFS, the filespace is not registered. </p>
API_Filespace_Not_Registered_SYSACT=<p>The system returns to the calling procedure.</p>
API_Filespace_Not_Registered_URESP=<p>Verify the filespace name.</p>
# 0242
API_FS_Already_Registered=ANS0242W On dsmRegisterFS the filespace is already registered.
API_FS_Already_Registered_EXPLANATION=<p>On dsmRegisterFS the filespace is already registered.</p>
API_FS_Already_Registered_SYSACT=<p>The system returns to the calling procedure.</p>
API_FS_Already_Registered_URESP=<p>Verify the filespace name.</p>
# 0243
API_No_ObjID=ANS0243E On dsmBeginGetData the objID is NULL.
API_No_ObjID_EXPLANATION=<p>On dsmBeginGetData, the objID is NULL.</p>
API_No_ObjID_SYSACT=<p>The system returns to the calling procedure.</p>
API_No_ObjID_URESP=<p>Verify the following: <ul style="simple"> <li>The dsmGetList is not NULL.</li> <li>Each objID is not NULL.</li> <li>The dsmGetList numObjId is not zero.</li> </ul></p>
# 0244
API_Wrong_Version=ANS0244E On dsmInit the caller's API version is different than the TSM library version.
API_Wrong_Version_EXPLANATION=<p>On dsmInit the caller's API version has a higher value than the TSM library version.</p>
API_Wrong_Version_SYSACT=<p>The system returns to the calling procedure.</p>
API_Wrong_Version_URESP=<p>Install the latest TSM API library and trusted agent module.</p>
# 0245
API_Wrong_Version_Parm=ANS0245E The caller's structure version is different than the TSM library version.
API_Wrong_Version_Parm_EXPLANATION=<p>The caller's structure version is different than the TSM library version. </p>
API_Wrong_Version_Parm_SYSACT=<p>The system returns to the calling procedure.</p>
API_Wrong_Version_Parm_URESP=<p>Ensure that the stVersion field is set with the value in the header file. Recompile the application with the latest header files.</p>
# 0246
API_Need_To_Call_EndTxn=ANS0246E Issue dsmEndTxn and then begin a new transaction session.
API_Need_To_Call_EndTxn_EXPLANATION=<p>This transaction must be ended and a new one must be started due to one of the following reasons: <ul style="simple"> <li>The destination changed.</li> <li>The byte limit is exceeded</li> <li>The maximum number of objects is exceeded.</li> </ul></p>
API_Need_To_Call_EndTxn_SYSACT=<p>The system returns to the calling procedure.</p>
API_Need_To_Call_EndTxn_URESP=<p>Issue dsmEndTxn and start a new transaction session.</p>
# 0247
API_Obj_Excluded=ANS0247E The backup or archive object is excluded from processing.
API_Obj_Excluded_EXPLANATION=<p>The backup or archive object is excluded from processing.</p>
API_Obj_Excluded_SYSACT=<p>The system returns to the calling procedure.</p>
API_Obj_Excluded_URESP=<p>Verify the objName and Exclude lists.</p>
# 0248
API_No_Backup_CG=ANS0248E The backup object does not have a copy group.
API_No_Backup_CG_EXPLANATION=<p>The backup object does not have a copy group.</p>
API_No_Backup_CG_SYSACT=<p>The system returns to the calling procedure.</p>
API_No_Backup_CG_URESP=<p>Verify server policy definitions.</p>
# 0249
API_No_Archive_CG=ANS0249E The archive object does not have a copy group.
API_No_Archive_CG_EXPLANATION=<p>The archive object does not have a copy group.</p>
API_No_Archive_CG_SYSACT=<p>The system returns to the calling procedure.</p>
API_No_Archive_CG_URESP=<p>Verify server policy definitions.</p>
# 0250
API_Internal_Mem_Error=ANS0250E Memory used by the TSM API has been corrupted.
API_Internal_Mem_Error_EXPLANATION=<p>Memory used by the TSM API has been corrupted.</p>
API_Internal_Mem_Error_SYSACT=<p>The system returns to the calling procedure.</p>
API_Internal_Mem_Error_URESP=<p>Retry the operation. If the problem continues, contact your system administrator or service representative.</p>
# 0251
API_Descr_Too_Long=ANS0251E The sendObj Archive description is too long.
API_Descr_Too_Long_EXPLANATION=<p>The sendObj Archive description is too long.</p>
API_Descr_Too_Long_SYSACT=<p>The system returns to the calling procedure.</p>
API_Descr_Too_Long_URESP=<p>The sndArchiveData.descr string must be less than or equal to DSM_MAX_DESCR_LENGTH. </p>
# 0252
API_ObjInfo_Too_Long=ANS0252E The sendObj ObjAttr.objInfo is too long.
API_ObjInfo_Too_Long_EXPLANATION=<p>The sendObj ObjAttr.objInfo is too long.</p>
API_ObjInfo_Too_Long_SYSACT=<p>The system returns to the calling procedure.</p>
API_ObjInfo_Too_Long_URESP=<p>The objInfo field must be less than or equal to DSM_MAX_OBJINFO_LENGTH. </p>
# 0253
API_HL_Too_Long=ANS0253E The sendObj dsmObjName.hl is too long.
API_HL_Too_Long_EXPLANATION=<p>The sendObj dsmObjName.hl is too long.</p>
API_HL_Too_Long_SYSACT=<p>The system returns to the calling procedure.</p>
API_HL_Too_Long_URESP=<p>The hl field must be less than or equal to DSM_MAX_HL_LENGTH.</p>
# 0254
API_Password_Too_Long=ANS0254E The password, or encryptionPassword string provided is too long.
API_Password_Too_Long_EXPLANATION=<p>The value provided for password or encryptionPassword is too long.</p>
API_Password_Too_Long_SYSACT=<p>The system returns to the calling procedure.</p>
API_Password_Too_Long_URESP=<p>The password or encrypionPassword field must be less than DSM_MAX_VERIFIER_LENGTH. </p>
# 0255
API_FS_Too_Long=ANS0255E The sendObj dsmObjName.fs is too long.
API_FS_Too_Long_EXPLANATION=<p>The sendObj dsmObjName.fs is too long.</p>
API_FS_Too_Long_SYSACT=<p>The system returns to the calling procedure.</p>
API_FS_Too_Long_URESP=<p>The fs field must be less than or equal to DSM_MAX_FS_LENGTH.</p>
# 0256
API_LL_Too_Long=ANS0256E The sendObj dsmObjName.ll is too long.
API_LL_Too_Long_EXPLANATION=<p>The sendObj dsmObjName.ll is too long.</p>
API_LL_Too_Long_SYSACT=<p>The system returns to the calling procedure.</p>
API_LL_Too_Long_URESP=<p>The ll field must be less than or equal to DSM_MAX_LL_LENGTH.</p>
# 0257
API_FSInfo_Too_Long=ANS0257E On RegisterFS or UpdateFS the fsAttr's fsInfo is too long.
API_FSInfo_Too_Long_EXPLANATION=<p>On RegisterFS or UpdateFS the fsAttr's fsInfo is too long.</p>
API_FSInfo_Too_Long_SYSACT=<p>The system returns to the calling procedure.</p>
API_FSInfo_Too_Long_URESP=<p>The fsInfo field must be less than or equal to DSM_MAX_FSINFO_LENGTH.</p>
# 0258
API_More_Data=ANS0258I On dsmGetNextQObj or dsmGetData there is more available data.
# 0259
API_Buff_Too_Small=ANS0259E The dataBlk buffer is too small for the query response.
API_Buff_Too_Small_EXPLANATION=<p>The dataBlk buffer is too small for the query response.</p>
API_Buff_Too_Small_SYSACT=<p>The system returns to the calling procedure.</p>
API_Buff_Too_Small_URESP=<p>On dsmGetNextQObj ensure that the dataBlk buffer is at least as big as the query response structure.</p>
# 0261
API_No_Config_File=ANS0261E The configuration file specified on dsmInit cannot be opened.
API_No_Config_File_EXPLANATION=<p>The configuration file specified on dsmInit cannot be opened.</p>
API_No_Config_File_SYSACT=<p>The system returns to the calling procedure.</p>
API_No_Config_File_URESP=<p>Verify the file name.</p>
# 0262
API_No_InclExcl_File=ANS0262E The Include/Exclude definition file was not found.\n
API_No_InclExcl_File_EXPLANATION=<p>The Include/Exclude definition file was not found.</p>
API_No_InclExcl_File_SYSACT=<p>The system returns to the calling procedure.</p>
API_No_InclExcl_File_URESP=<p>Verify the file name on the Inclexcl option.</p>
# 0263
API_No_Sys_Or_InclExcl_File=ANS0263E Either the dsm.sys file was not found, or the Inclexcl file specified in dsm.sys was not found.
API_No_Sys_Or_InclExcl_File_EXPLANATION=<p>Either the dsm.sys file was not found, or the Inclexcl file specified in dsm.sys was not found.</p>
API_No_Sys_Or_InclExcl_File_SYSACT=<p>The system returns to the calling procedure.</p>
API_No_Sys_Or_InclExcl_File_URESP=<p>The dsm.sys file must be in the directory referenced by the environment variable DSMI_DIR. Verify the file name on the Inclexcl option in the dsm.sys file.</p>
# 0264
API_Only_Root=ANS0264E Only a UNIX root user can execute dsmChangePW or dsmDeleteFS.
API_Only_Root_EXPLANATION=<p>Only a UNIX root user can execute dsmChangePW or dsmDeleteFS.</p>
API_Only_Root_SYSACT=<p>The system returns to the calling procedure.</p>
API_Only_Root_URESP=<p>Run this program as a root user.</p>
# 0265
API_Issue_BindMC=ANS0265E You must issue dsmBindMC before dsmSendObj.
API_Issue_BindMC_EXPLANATION=<p>You must issue dsmBindMC before dsmSendObj.</p>
API_Issue_BindMC_SYSACT=<p>The system returns to the calling procedure.</p>
API_Issue_BindMC_URESP=<p>Modify your program.</p>
# 0266
API_Check_Reason_Code=ANS0266I The dsmEndTxn vote is ABORT, so check the reason field.
# 0283
API_Invalid_Highlevel_Qualifier=ANS0283E High level qualifier of the object name should start with the directory delimiter.
API_Invalid_Highlevel_Qualifier_EXPLANATION=<p>The high level qualifier for the object name is invalid.</p>
API_Invalid_Highlevel_Qualifier_SYSACT=<p>The system returns to the calling procedure.</p>
API_Invalid_Highlevel_Qualifier_URESP=<p>High level qualifier of the object name should start with the directory delimiter.</p>
# 0284
API_Numobj_Exceed=ANS0284E The number of objects on dsmBeginGetData exceeds DSM_MAX_GET_OBJ | DSM_MAX_PARTIAL_GET_OBJ.
API_Numobj_Exceed_EXPLANATION=<p>The number of objects (numObjId) specified on the dsmBeginGetData call exceeds DSM_MAX_GET_OBJ | DSM_MAX_PARTIAL_GET_OBJ.</p>
API_Numobj_Exceed_SYSACT=<p>The system returns to the calling procedure.</p>
API_Numobj_Exceed_URESP=<p>Check the number of objects before calling dsmBeginGetData. If it is greater than DSM_MAX_GET_OBJ | DSM_MAX_PARTIAL_GET_OBJ, then issue multiple Get call sequences.</p>
# 0285
API_Invalid_Action=ANS0285E The update action is invalid.
API_Invalid_Action_EXPLANATION=<p>The dsmUpdateFS or dsmUpdateObj action is invalid.</p>
API_Invalid_Action_SYSACT=<p>The system returns to the calling procedure.</p>
API_Invalid_Action_URESP=<p>Correct the action value. Valid values are defined in dsmapitd.h and documented in our Using the API book.</p>
# 0286
API_Key_Missing=ANS0286E The key file is missing.
API_Key_Missing_EXPLANATION=<p>The key file for TDPAPP; application client for Oracle cannot be found.</p>
API_Key_Missing_SYSACT=<p>The system returns to the calling procedure.</p>
API_Key_Missing_URESP=<p>Ensure that you have ordered the TDPAPP; application client which contains TDP for Oracle, and install the key file.</p>
# 0287
API_Key_Bad=ANS0287E The key file content is invalid.
API_Key_Bad_EXPLANATION=<p>The key file content for TDPAPP; application client for Oracle is invalid.</p>
API_Key_Bad_SYSACT=<p>The system returns to the calling procedure.</p>
API_Key_Bad_URESP=<p>Ensure that you have ordered the TDPAPP; application client which contains the TDP for Oracle, and install the key file.</p>
# 0288
DSI_RUNNING=running
# 0289
DSI_COMPLETED=completed
# 0290
DSI_CANCELLED=cancelled
# 0291
DSI_CANCEL_PENDING=cancel pending
# 0292
DSI_FAILED=failed
# 0293
DSI_PROC_NOT_FOUND=process not found
# 0294
DSI_INT_SERVER_ERROR=internal server error
# 0298
SESS_Reject_User_Id_Locked=ANS0298E Session Rejected: The specified user id is currently locked\n
SESS_Reject_User_Id_Locked_EXPLANATION=<p>The user id you specified is currently locked on the server.</p>
SESS_Reject_User_Id_Locked_SYSACT=<p>Session was not started.</p>
SESS_Reject_User_Id_Locked_URESP=<p>Check with your system administrator to find out why your user id is locked. </p>
# 0300
GUI_NAS_OBJECT=Nas Object
# 0304
COM_Password_Too_Short=ANS0304E The password is too short.\n
COM_Password_Too_Short_EXPLANATION=<p>The new password does not have enough characters.</p>
COM_Password_Too_Short_SYSACT=<p>The password is not updated on the server.</p>
COM_Password_Too_Short_URESP=<p>Choose a different password. Contact your TSM administrator to lean the password requirements.</p>
# 0305
COM_Password_Too_Young=ANS0305E It is too soon after the previous update to change the password.\n
COM_Password_Too_Young_EXPLANATION=<p>The password cannot be changed since not enough time has elapsed since the last password update.</p>
COM_Password_Too_Young_SYSACT=<p>The password is not updated on the server.</p>
COM_Password_Too_Young_URESP=<p>Try to change your password again later.</p>
# 0306
COM_Password_In_History=ANS0306E The password was previously used.\n
COM_Password_In_History_EXPLANATION=<p>The new password that you entered was previously used.</p>
COM_Password_In_History_SYSACT=<p>The password is not updated on the server.</p>
COM_Password_In_History_URESP=<p>Choose a different password.</p>
# 0307
COM_Password_Not_Complex=ANS0307E The password does not meet the requirements.\n
COM_Password_Not_Complex_EXPLANATION=<p>The new password that you entered does not meet the requirements, such as the number of special characters or digits.</p>
COM_Password_Not_Complex_SYSACT=<p>The password is not updated on the server.</p>
COM_Password_Not_Complex_URESP=<p>Choose a different password. Contact your TSM administrator to learn the password requirements.</p>
# 0308
GUI_REMOTE_OP_FAILED_TO_START_STATUS_REASON=ANS0308E Remote operation failed to start on {0}. Status: {1} reason: {2}
GUI_REMOTE_OP_FAILED_TO_START_STATUS_REASON_EXPLANATION=<p>The request to start a remote operation has failed for the indicated node and filespace. The status and the reason for the failure are shown.</p>
GUI_REMOTE_OP_FAILED_TO_START_STATUS_REASON_SYSACT=<p>TSM ended the current operation.</p>
GUI_REMOTE_OP_FAILED_TO_START_STATUS_REASON_URESP=<p>Contact your system administrator for more information.</p>
# 0309
GUI_REMOTE_OP_FAILED_TO_START_STATUS=ANS0309E Remote operation failed to start on {0}. Status: {1}
GUI_REMOTE_OP_FAILED_TO_START_STATUS_EXPLANATION=<p>The request to start a remote operation has failed for the indicated node and filespace. The status of the failure is shown.</p>
GUI_REMOTE_OP_FAILED_TO_START_STATUS_SYSACT=<p>IBM Tivoli Storage Manager ended the current operation.</p>
GUI_REMOTE_OP_FAILED_TO_START_STATUS_URESP=<p>Contact your system administrator for more information.</p>
# 0310
CLI_TOC_MEDIA_WAIT=Media wait for table of contents.\n
# 0311
API_Invalid_Tsmbuffer=ANS0311E The tsmBuffHandle is invalid, or the value of dataPtr is invalid.
API_Invalid_Tsmbuffer_EXPLANATION=<p>An invalid value for a handle or dataPtr has been passed into the API.</p>
API_Invalid_Tsmbuffer_SYSACT=<p>The system returns to the calling procedure.</p>
API_Invalid_Tsmbuffer_URESP=<p>There is a problem with the calling application. Verify the values of the tsmBuffHandle and dataptr passed to the API.</p>
# 0312
API_Too_many_Bytes=ANS0312E The number of bytes copied into the tsmBuffer is larger than the allowed value.
API_Too_many_Bytes_EXPLANATION=<p>An invalid number of bytes was copied to a tsmBuffer.</p>
API_Too_many_Bytes_SYSACT=<p>The system returns to the calling procedure.</p>
API_Too_many_Bytes_URESP=<p>There is a problem with the calling application. Verify the number of bytes copied into the tsmBuffer.</p>
# 0313
API_Must_Release_Buffer=ANS0313E dsmTerminate cannot finish because the application is holding on to 1 or more tsmBuffers.
API_Must_Release_Buffer_EXPLANATION=<p>An application is trying to terminate a session, but is still holding some tsmBuffers.</p>
API_Must_Release_Buffer_SYSACT=<p>The system returns to the calling procedure.</p>
API_Must_Release_Buffer_URESP=<p>The application must return all buffers for this session by calling tsmReleaseBuffer, and then issue dsmTerminate.</p>
# 0314
API_Buff_Array_Error=ANS0314E An internal error occurred in the tsmBuffer array.
API_Buff_Array_Error_EXPLANATION=<p>An internal API buffer array error occurred.</p>
API_Buff_Array_Error_SYSACT=<p>The system returns to the calling procedure.</p>
API_Buff_Array_Error_URESP=<p>Try the operation again. If the problem continues, contact your system administrator or service representative.</p>
# 0321
API_Null_Msg=ANS0321E msg parameter for dsmRCMsg is a NULL pointer.
API_Null_Msg_EXPLANATION=<p>The message parameter for dsmRCMsg is a NULL pointer.</p>
API_Null_Msg_SYSACT=<p>The system returns to the calling procedure.</p>
API_Null_Msg_URESP=<p>Allocate enough space for the message parameter.</p>
# 0322
API_Invalid_Retcode=ANS0322E no text available for this return code.
API_Invalid_Retcode_EXPLANATION=<p>The dsmRC parameter for dsmRCMsg is an unsupported return code.</p>
API_Invalid_Retcode_SYSACT=<p>The system returns to the calling procedure.</p>
API_Invalid_Retcode_URESP=<p>Specify a valid value.</p>
# 0323
API_Invalid_Offset=ANS0323E partialObjOffset value for partial object retrieve is invalid.
API_Invalid_Offset_EXPLANATION=<p>The partialObjOffset value for partial object retrieve is invalid.</p>
API_Invalid_Offset_SYSACT=<p>The system returns to the calling procedure.</p>
API_Invalid_Offset_URESP=<p>Specify a valid value.</p>
# 0324
API_Invalid_Length=ANS0324E partialObjLength value for partial object retrieve is invalid.
API_Invalid_Length_EXPLANATION=<p>partialObjLength value for partial object retrieve is invalid.</p>
API_Invalid_Length_SYSACT=<p>The system returns to the calling procedure.</p>
API_Invalid_Length_URESP=<p>Specify a valid value.</p>
# 0325
API_POR_Not_Supported=ANS0325E Partial Object Retrieve is not supported on this server.
API_POR_Not_Supported_EXPLANATION=<p>The TSM server specified by the user does not support partial object retrieve. </p>
API_POR_Not_Supported_SYSACT=<p>The system returns to the calling procedure.</p>
API_POR_Not_Supported_URESP=<p>Specify a TSM server which supports the partial object retrieve function. </p>
# 0326
API_Exceed_Max_MP=ANS0326E This node has exceeded its maximum number of mount points.
API_Exceed_Max_MP_EXPLANATION=<p>Either no tape or sequential disk mount points are permitted for this operation, or the maximum number of mount points allowed are already in use. The operation can not be completed. The TSM administrator defines the maximum number of mount points with the MAXNUMMP property of your node definition.</p>
API_Exceed_Max_MP_SYSACT=<p>The object is skipped</p>
API_Exceed_Max_MP_URESP=<p>If you are performing any other TSM operations that might be using mount points, wait until those operations are complete, then try the failed operation again. Otherwise contact your TSM administrator for further assistance</p>
# 0327
API_Duplicate_Object=ANS0327E A duplicate object was found, operation cannot complete.
API_Duplicate_Object_EXPLANATION=<p>A duplicate object was found, operation cannot complete. </p>
API_Duplicate_Object_SYSACT=<p>The requested operation failed.</p>
API_Duplicate_Object_URESP=<p>Try the operation with a different file specification.</p>
# 0329
GUI_MB_MOVED=MB Moved
# 0330
API_Invalid_Access_Type=ANS0330E The dsmSetAccess access Type is invalid.
API_Invalid_Access_Type_EXPLANATION=<p>The dsmSetAccess accessType is invalid.</p>
API_Invalid_Access_Type_SYSACT=<p>The system returns to the calling procedure.</p>
API_Invalid_Access_Type_URESP=<p>The accessType must be one of the following: <ul style="simple"> <li>atBackup</li> <li>atArchive</li> </ul></p>
# 0331
API_No_Files_Backed_Up=ANS0331E No files have been previously backed up for this filename/filespace.
API_No_Files_Backed_Up_EXPLANATION=<p>You tried to set access to files when no files for the specified filename, drive or file system were previously backed up.</p>
API_No_Files_Backed_Up_SYSACT=<p>Processing stopped.</p>
API_No_Files_Backed_Up_URESP=<p>Ensure that the correct drive or file system was specified and that files are backed up for you to set access.</p>
# 0332
API_No_Files_Archived=ANS0332E No files have been previously archived for this filename/filespace.
API_No_Files_Archived_EXPLANATION=<p>You tried to set access to files when no files for the specified filename, drive or file system were previously archived.</p>
API_No_Files_Archived_SYSACT=<p>Processing stopped.</p>
API_No_Files_Archived_URESP=<p>Ensure that the correct drive or file system was specified and that files are archived for you to set access.</p>
# 0333
CLI_Abort_Mover_Type=ANS0333E Unknown Remote Mover type
CLI_Abort_Mover_Type_EXPLANATION=<p>The specified Remote Mover type is unknown.</p>
CLI_Abort_Mover_Type_SYSACT=<p>TSM ended the current operation.</p>
CLI_Abort_Mover_Type_URESP=<p>Contact your system administrator for more information.</p>
# 0334
CLI_Abort_Item_In_Use=ANS0334E An Operation for the requested node and filespace is already in progress.
CLI_Abort_Item_In_Use_EXPLANATION=<p>A request has been made to use a data mover to perform an operation for the indicated node and filespace. Since an operation for this node and filespace is already in progress, the new operation cannot be performed. </p>
CLI_Abort_Item_In_Use_SYSACT=<p>TSM ended the current operation.</p>
CLI_Abort_Item_In_Use_URESP=<p>Retry the operation at a later time.</p>
# 0335
CLI_Abort_Lock_Conflict=ANS0335E System resource in use
CLI_Abort_Lock_Conflict_EXPLANATION=<p>A required resource is in use by another command or process. </p>
CLI_Abort_Lock_Conflict_SYSACT=<p>TSM ended the current operation.</p>
CLI_Abort_Lock_Conflict_URESP=<p>Retry the operation at a later time.</p>
# 0336
CLI_Abort_Srv_Plugin_Comm_Error=ANS0336E Server plugin communication error
CLI_Abort_Srv_Plugin_Comm_Error_EXPLANATION=<p>Communication between a server plugin module and a NAS filer failed. </p>
CLI_Abort_Srv_Plugin_Comm_Error_SYSACT=<p>TSM ended the current operation.</p>
CLI_Abort_Srv_Plugin_Comm_Error_URESP=<p>Contact your system administrator for more information.</p>
# 0337
CLI_Abort_Srv_Plugin_Os_Error=ANS0337E Server plugin detected unsupported NAS filer operating system.
CLI_Abort_Srv_Plugin_Os_Error_EXPLANATION=<p>A plugin module detected that a NAS filer is running an unsupported operating system or operating system level. </p>
CLI_Abort_Srv_Plugin_Os_Error_SYSACT=<p>TSM ended the current operation.</p>
CLI_Abort_Srv_Plugin_Os_Error_URESP=<p>Contact your system administrator for more information.</p>
# 0338
CLI_Abort_Invalid_Operation=ANS0338E An invalid operation was attempted on a node
CLI_Abort_Invalid_Operation_EXPLANATION=<p>The operation is not valid.</p>
CLI_Abort_Invalid_Operation_SYSACT=<p>TSM ended the current operation.</p>
CLI_Abort_Invalid_Operation_URESP=<p>Contact your system administrator for more information.</p>
# 0339
CLI_Abort_Stgpool_Undefined=ANS0339E The specified target storage pool is not defined.
CLI_Abort_Stgpool_Undefined_EXPLANATION=<p>The storage pool is not defined.</p>
CLI_Abort_Stgpool_Undefined_SYSACT=<p>TSM ended the current operation.</p>
CLI_Abort_Stgpool_Undefined_URESP=<p>Contact your system administrator for more information.</p>
# 0340
CLI_Abort_Invalid_Data_Format=ANS0340E A target storage pool does not have the correct data format for the given node type.
CLI_Abort_Invalid_Data_Format_EXPLANATION=<p>none</p>
CLI_Abort_Invalid_Data_Format_SYSACT=<p>TSM ended the current operation.</p>
CLI_Abort_Invalid_Data_Format_URESP=<p>Contact your system administrator for more information.</p>
# 0341
CLI_Abort_Datamover_Undefined=ANS0341E No associated data mover is defined for the given node.\n
CLI_Abort_Datamover_Undefined_EXPLANATION=<p>none</p>
CLI_Abort_Datamover_Undefined_SYSACT=<p>TSM ended the current operation.</p>
CLI_Abort_Datamover_Undefined_URESP=<p>Contact your system administrator for more information.</p>
# 0342
CLI_Abort_Crc_Failed=ANS0342E The CRC received from the Server does not match the CRC calculated by the client.
CLI_Abort_Crc_Failed_EXPLANATION=<p>The server sent a CRC for a buffer. The client calculated a CRC for the same buffer. These did not match. The mismatch indicates a communication failure. </p>
CLI_Abort_Crc_Failed_SYSACT=<p>In some cases, the client can indicate the failure to the server and retry the operation.</p>
CLI_Abort_Crc_Failed_URESP=<p>Check the trace log for additional information and retry the operation. If the problem persists, contact your system administrator.</p>
# 0343
CLI_Abort_Invalid_Group_Action=ANS0343E An invalid operation was attempted on a group leader or group member.
CLI_Abort_Invalid_Group_Action_EXPLANATION=<p>An invalid operation was attempted on a logical group.</p>
CLI_Abort_Invalid_Group_Action_SYSACT=<p>The current operation stops.</p>
CLI_Abort_Invalid_Group_Action_URESP=<p>Retry a valid operation.</p>
# 0344
API_Senddata_With_Zero_Size=ANS0344E Cannot Send data with a zero byte sizeEstimate.
API_Senddata_With_Zero_Size_EXPLANATION=<p>You cannot send data for an object with size estimate = 0.</p>
API_Senddata_With_Zero_Size_SYSACT=<p>The system returns to the calling procedure.</p>
API_Senddata_With_Zero_Size_URESP=<p>Set size estimate greater than 0 in dsmSendObj.</p>
# 0345
CLI_Abort_Disk_Undefined=ANS0345E Remote disk not defined.
CLI_Abort_Disk_Undefined_EXPLANATION=<p>An operation was attempted on a remote disk that is not defined.</p>
CLI_Abort_Disk_Undefined_SYSACT=<p>The current operation stops.</p>
CLI_Abort_Disk_Undefined_URESP=<p>Define the proper remote disk.</p>
# 0346
CLI_Abort_Bad_Destination=ANS0346E Input destination does not match expected destination.
CLI_Abort_Bad_Destination_EXPLANATION=<p>Input destination does not match expected destination.</p>
CLI_Abort_Bad_Destination_SYSACT=<p>The current operation stops.</p>
CLI_Abort_Bad_Destination_URESP=<p>Retry operation with proper destination.</p>
# 0347
CLI_Abort_Datamover_Not_Available=ANS0347E Data mover is not available.
CLI_Abort_Datamover_Not_Available_EXPLANATION=<p>Data mover is not available.</p>
CLI_Abort_Datamover_Not_Available_SYSACT=<p>The current operation stops.</p>
CLI_Abort_Datamover_Not_Available_URESP=<p>Retry operation with a proper Data mover.</p>
# 0348
CLI_Abort_Stgpool_Copy_Cont_No=ANS0348E Operation failed because the copy continue option was set to NO.
CLI_Abort_Stgpool_Copy_Cont_No_EXPLANATION=<p>Operation failed because the copy continue option was set to NO.</p>
CLI_Abort_Stgpool_Copy_Cont_No_SYSACT=<p>The current operation stops.</p>
CLI_Abort_Stgpool_Copy_Cont_No_URESP=<p> This abort code indicates that a store operation, like backup or archive failed because the copy continue option was set to NO. The sysadmin will need to resolve the problem on the server end. </p>
# 0349
CLI_Abort_Retry_Single_Txn=ANS0349E Transaction failed because of a problem during a store operation.
CLI_Abort_Retry_Single_Txn_EXPLANATION=<p>Transaction failed because of a problem during a store operation. This error is typical when the next storage pool has a different copy storage pool list and we switch to this pool in the middle of a transaction. </p>
CLI_Abort_Retry_Single_Txn_SYSACT=<p>Transaction is aborted.</p>
CLI_Abort_Retry_Single_Txn_URESP=<p> Resend objects in separate transactions. </p>
# 0351
CLI_Abort_Node_Not_Authorized=ANS0351E The node or user does not have proper authority to perform this operation\n
CLI_Abort_Node_Not_Authorized_EXPLANATION=<p>The node or user does not have proper authority to perform this operation. </p>
CLI_Abort_Node_Not_Authorized_SYSACT=<p>The transaction is ended.</p>
CLI_Abort_Node_Not_Authorized_URESP=<p>Check the authority for the specified object.</p>
# 0352
CLI_Abort_License_Violation=ANS0352E The operation is not permitted due to server licenses values.\n
CLI_Abort_License_Violation_EXPLANATION=<p>The node or user is trying to perform an operation that either exceeds license values, or is not licensed.</p>
CLI_Abort_License_Violation_SYSACT=<p>The session is rejected or the transaction is cancelled, ending the current operation.</p>
CLI_Abort_License_Violation_URESP=<p>See your system administrator.</p>
# 0353
API_Invalid_DataBlk=ANS0353E When using useTsmBuffers, dataBlk must be NULL in calls to dsmSendObj and dsmGetObj.
API_Invalid_DataBlk_EXPLANATION=<p>The value for dataBlk must be NULL when using useTsmBuffers.</p>
API_Invalid_DataBlk_SYSACT=<p>The system returns to the calling procedure.</p>
API_Invalid_DataBlk_URESP=<p>There is a problem with the calling application. Contact your application provider</p>
# 0354
API_Encr_Not_Allowed=ANS0354E Encryption is not allowed when using useTsmBuffers.
API_Encr_Not_Allowed_EXPLANATION=<p>useTsmBuffers does not support encryption.</p>
API_Encr_Not_Allowed_SYSACT=<p>The system returns to the calling procedure.</p>
API_Encr_Not_Allowed_URESP=<p>Try the operation again, without using useTsmBuffers, or disable encryption for this operation.</p>
# 0355
API_Obj_Compressed=ANS0355E This object cannot be restored/retrieved using useTsmBuffers, because it is compressed.
API_Obj_Compressed_EXPLANATION=<p>useTsmBuffers does not support compression.</p>
API_Obj_Compressed_SYSACT=<p>The system returns to the calling procedure.</p>
API_Obj_Compressed_URESP=<p>Try the operation again, without using useTsmBuffers.</p>
# 0356
API_Obj_Encrypted=ANS0356E This object cannot be restored/retrieved using useTsmBuffers, because it is encrypted.
API_Obj_Encrypted_EXPLANATION=<p>useTsmBuffers does not support encryption.</p>
API_Obj_Encrypted_SYSACT=<p>The system returns to the calling procedure.</p>
API_Obj_Encrypted_URESP=<p>Try the operation again, without using useTsmBuffers.</p>
# 0357
API_POR_Not_Allowed=ANS0357E When using useTsmBuffers, a restore/retrieve with partial object restore is not allowed.
API_POR_Not_Allowed_EXPLANATION=<p>useTsmBuffers does not support partial object restore.</p>
API_POR_Not_Allowed_SYSACT=<p>The system returns to the calling procedure.</p>
API_POR_Not_Allowed_URESP=<p>Make sure the calling application is either using Partial object restore or useTsmBuffers.</p>
# 0358
API_No_Encryption_Key=ANS0358E No encryption key was found. If you are using -encryptkey=prompt make sure there is a value in the encryptionPasswordP field and that bEncryptKeyEnabled is set to true.
API_No_Encryption_Key_EXPLANATION=<p>There was no encryption key found in the password file, or no key was provided by the application.</p>
API_No_Encryption_Key_SYSACT=<p>The system returns to the calling procedure.</p>
API_No_Encryption_Key_URESP=<p>If you are using -encryptkey=prompt, make sure there is a value in encryptionPasswordP and that bEncryptKeyEnabled is set to true.</p>
# 0359
API_Encr_Conflict=ANS0359E Conflicting encryption key options have been specified.
API_Encr_Conflict_EXPLANATION=<p>When using the ENABLEENCRYPTKEY option, the parameter bEncryptKeyEnabled for the TSM API dsmInitExIn_t and tsmInitExIn_t structures cannot be set to bTrue.</p>
API_Encr_Conflict_SYSACT=<p>The system returns to the calling procedure.</p>
API_Encr_Conflict_URESP=<p>Either remove the ENABLEENCRYPTKEY option from the options file, or set the parameter bEncryptKeyEnabled to bFalse in the program using the TSM API.</p>
# 0361
CLI_Generic_Diag_LogMsg=ANS0361I DIAG: 
# 0400
API_Almgr_Open_Fail=ANS0400E License file could not be opened.
API_Almgr_Open_Fail_EXPLANATION=<p>The license file was not found, or could not be opened because of permissions or the file is corrupted.</p>
API_Almgr_Open_Fail_SYSACT=<p>The system returns to the calling procedure.</p>
API_Almgr_Open_Fail_URESP=<p>Check permissions on file. See if the license file is in the correct place. </p>
# 0401
API_Almgr_Read_Fail=ANS0401E Read failure on the license file.
API_Almgr_Read_Fail_EXPLANATION=<p>The license file was not found, or could not be opened because of permissions, or the file is corrupted.</p>
API_Almgr_Read_Fail_SYSACT=<p>The system returns to the calling procedure.</p>
API_Almgr_Read_Fail_URESP=<p>Check permissions on file. See if the license file is in the correct place. </p>
# 0402
API_Almgr_Write_Fail=ANS0402E Write failure on the license file.
API_Almgr_Write_Fail_EXPLANATION=<p>The license file was not found, or could not be opened because of permissions or the file is corrupted.</p>
API_Almgr_Write_Fail_SYSACT=<p>The system returns to the calling procedure.</p>
API_Almgr_Write_Fail_URESP=<p>Check permissions on file. See if license file is in the correct place. </p>
# 0403
API_Almgr_Data_Fmt=ANS0403E Data in the license file is not in a valid format.
API_Almgr_Data_Fmt_EXPLANATION=<p>The license file is not valid.</p>
API_Almgr_Data_Fmt_SYSACT=<p>The system returns to the calling procedure.</p>
API_Almgr_Data_Fmt_URESP=<p>User needs to obtain a new license.</p>
# 0404
API_Almgr_Cksum_bad=ANS0404E The checksum in the license file does not match the licenseregistration string.
API_Almgr_Cksum_bad_EXPLANATION=<p>The registration string is not valid.</p>
API_Almgr_Cksum_bad_SYSACT=<p>The system returns to the calling procedure.</p>
API_Almgr_Cksum_bad_URESP=<p>User needs to obtain a new license.</p>
# 0405
API_Almgr_Trial_exprd=ANS0405E This is an expired try and buy license.
API_Almgr_Trial_exprd_EXPLANATION=<p>The registration string is not valid.</p>
API_Almgr_Trial_exprd_SYSACT=<p>The system returns to the calling procedure.</p>
API_Almgr_Trial_exprd_URESP=<p>User needs to obtain a new license.</p>
# 0406
GUI_PCT_SIGN=%
# 0407
GUI_SHOW_IN_TASK_WINDOW=Show in Task Window
# 0408
GUI_REFRESH_BUTTON=Refresh
# 0409
GUI_DISMISSED=Window Dismissed. Process will continue.
# 0420
DSI_INACTIVE_SYSSTATE_Warning=ANS0420W Warning! Restoring inactive system state objects is not recommended. \n\nDo you wish to continue? \n
DSI_INACTIVE_SYSSTATE_Warning_EXPLANATION=<p>Restoring inactive system state objects may cause system instability. Examples of possible problems include:<ul> <li>Applications that were installed after the time the system state was backed up cannot function properly after restoring the inactive system state</li> <li>Critical operating system updates installed after the inactive system state backup was made can no longer be available, or may not function correctly. </li> </ul>\nRestoring inactive system state objects is not recommended unless you are certain that this is what you need to do.</p>
DSI_INACTIVE_SYSSTATE_Warning_SYSACT=<p>If user responds with yes, the client will restore the object. If user responds with no, the client will cancel the operation.</p>
DSI_INACTIVE_SYSSTATE_Warning_URESP=<p>Reply to the prompt. If you are unsure, reply no, and consult your system administrator or operating system vendor before proceeding further.</p>
# 0421
COM_Password_Not_Synchronized=ANS0421W Unable to synchronize the node password with the user id password provided.\n
COM_Password_Not_Synchronized_EXPLANATION=<p>The node password was not updated due to the reason described in the error message preceding this one.</p>
COM_Password_Not_Synchronized_SYSACT=<p>The node password is not updated on the server. Next time you run the client you will be prompted for the password again.</p>
COM_Password_Not_Synchronized_URESP=<p>See the preceding error message.</p>
# 0422
DSI_JOURNALWIZ_DBPATHNETWORK=ANS0422W The selected journal location is a network drive and might not be accessible from the journal service. Select a location on a local drive.
DSI_JOURNALWIZ_DBPATHNETWORK_EXPLANATION=<p> It is not recommended to use a network device as the location where journal databases are stored. Placing journal databases on a network device can prevent the journal service from running. </p>
DSI_JOURNALWIZ_DBPATHNETWORK_SYSACT=<p>Processing continues.</p>
DSI_JOURNALWIZ_DBPATHNETWORK_URESP=<p> Choose a local drive where journal databases will be stored. </p>
# 0992
CLI_Invalid_DestFilespace=ANS0992E The destination filespace or drive letter is unavailable. For more details please see dsmerror.log.
CLI_Invalid_DestFilespace_EXPLANATION=<p>The system is trying to restore or retrieve to a destination that cannot be reached. The specified filespace name or drive letter is not valid, or does not exist, or you are specifying a local share name that cannot be resolved. </p>
CLI_Invalid_DestFilespace_SYSACT=<p>Objects which are part of this filespace are not processed.</p>
CLI_Invalid_DestFilespace_URESP=<p>Try the command again, and specify a different destination for the object that was not processed. </p>
# 0995
Img_Volume_Lock_Failure_Ex=ANS0995E Volume '{0}' could not be locked.\n
Img_Volume_Lock_Failure_Ex_EXPLANATION=<p> The system call to lock the volume failed. </p>
Img_Volume_Lock_Failure_Ex_SYSACT=<p> Processing stopped. </p>
Img_Volume_Lock_Failure_Ex_URESP=<p> Please verify that no other application is accessing the volume. During restore of an image TSM must have exclusive use of the volume. </p>
# 1001
Img_NOT_SYSDrive_Skip=ANS1001E Volume being backed up was not a system volume. Skipped. \n
Img_NOT_SYSDrive_Skip_EXPLANATION=<p> User specified to back up system volume only. This volume was not backed up since this volume is not a system volume. </p>
Img_NOT_SYSDrive_Skip_SYSACT=<p> Volume was not backed up. </p>
Img_NOT_SYSDrive_Skip_URESP=<p> Use All option or use image backup command to backup this volume. </p>
# 1009
CLI_OPERATING_SYSTEM_EXCLUDE_ERROR=ANS1009W An error occurred processing the operating system include/exclude statements.\nThe error was detected while processing: {0}.\n
CLI_OPERATING_SYSTEM_EXCLUDE_ERROR_EXPLANATION=<p>The client encountered an error while obtaining the automatic include/exclude statements from the operating system. Possible reasons for this error include: <ul> <li>The specified registry key cannot be opened for reading</li> <li>The entry under this key has incorrect data</li> </ul></p>
CLI_OPERATING_SYSTEM_EXCLUDE_ERROR_SYSACT=<p>Processing continues without the full list of operating system include/exclude statements.</p>
CLI_OPERATING_SYSTEM_EXCLUDE_ERROR_URESP=<p>Ensure that you have access to the specified registry key and that entries are a MULTISZ values that contain: <ul> <li>Individual files</li> <li>Directories</li> <li>Wild card entries</li> <li>Environment variables</li> <li>/s switch (the /s switch is used on directory and/or wild card entries and signifies that all subdirectories of this directory should be excluded)</li> </ul> If the cause of this message can not be determined or resolved, contact IBM technical support for further assistance. </p>
# 1011
Img_Use_Snapshot_Image_Backup=Using {0} snapshot image backup for {1}.\n
# 1012
Img_Use_Static_Image_Backup=Using static image backup for volume '{0}'\n
# 1013
Img_Use_Dynamic_Image_Backup=Using dynamic image backup for volume '{0}'\n
# 1014
DSI_RC_UnsupportedFSOperation=Unsupported file system operation.
# 1015
SESS_Reject_Client_Not_Archretprot=ANS1015E The session is rejected. The server does not allow a signon of a client that is not archive-retention protection enabled.\n
SESS_Reject_Client_Not_Archretprot_EXPLANATION=<p>The client cannot establish a connection to the server because the server is enabled for archive-retention protection enabled and the client is not.</p>
SESS_Reject_Client_Not_Archretprot_SYSACT=<p>The session is not started.</p>
SESS_Reject_Client_Not_Archretprot_URESP=<p>See your system administrator.</p>
# 1019
Img_Open_Failure=ANS1019E The volume could not be opened.\n
Img_Open_Failure_EXPLANATION=<p> An error occurred when TSM tried to open the volume for a backup or restore operation. </p>
Img_Open_Failure_SYSACT=<p> The requested operation does not run. </p>
Img_Open_Failure_URESP=<p> Examine the client error log for additional messages related to this error. Verify that the volume is available, and is not locked by another process. Try the operation again. If the problem persists, contact IBM technical support for further assistance. </p>
# 1022
GUI_CancelFailed=ANS1022E Cancel failed for node: {0} filesystem: {1} operation: {2} error: {3}
GUI_CancelFailed_EXPLANATION=<p>The request to cancel a remote operation has failed. The node, filespace, operation and reason for the failure are shown.</p>
GUI_CancelFailed_SYSACT=<p>TSM operation not cancelled.</p>
GUI_CancelFailed_URESP=<p>Contact your system administrator for more information.</p>
# 1023
SESS_Reject_Nodetype_Mismatch=ANS1023E Session rejected: Node type mismatch\n
SESS_Reject_Nodetype_Mismatch_EXPLANATION=<p> Your node name is associated with a different type of operating system (such as OS/2 or AIX) and cannot be used on this system. </p>
SESS_Reject_Nodetype_Mismatch_SYSACT=<p> TSM canceled the current operation. </p>
SESS_Reject_Nodetype_Mismatch_URESP=<p> If you need a new node name, see your system administrator to assign a new one to you. Generally, you have a unique node name for each machine and operating system pair that requires access to the server. </p>
# 1027
GUI_NodeCannotBeSelected=This node cannot be selected.
# 1029
SESS_Communications_Severed=ANS1029E Communication with the TSM server is lost.\n
SESS_Communications_Severed_EXPLANATION=<p>This message is issued after the session with the TSM server is unexpectedly lost. The client error log might contain additional information regarding this problem.</p>
SESS_Communications_Severed_SYSACT=<p>processing stops.</p>
SESS_Communications_Severed_URESP=<p> <ul> <li>Restart the TSM client and retry the operation.</li> <li>If the problem persists, review the client error log for other messages that might be related to this problem.</li> <li>Verify that network connectivity exists between the TSM client machine and the TSM server machine.</li> <li>Contact your TSM administrator for further assistance. The TSM administrator can review the TSM server activity log for additional information about the problem.</li> </ul> </p>
# 1030
SESS_Memory_Exhausted=ANS1030E The operating system refused a TSM request for memory allocation.
SESS_Memory_Exhausted_EXPLANATION=<p> TSM requires access to memory in order to store information as processing proceeds. In this case, more memory was requested than the operating system would allocate. Possible reasons include: <ul style="simple bkm:(compact simple) ipf:(compact simple)"> <li>The system is low on memory.</li> <li>The process in which the program runs has exceeded the maximum memory that it is allowed to allocate.</li> <li>Some other error condition occurred that caused the program to think it is out of memory.</li> </ul></p>
SESS_Memory_Exhausted_SYSACT=<p>TSM cannot complete the requested operation.</p>
SESS_Memory_Exhausted_URESP=<p>Close all unneeded applications and try the operation again. If the operation still fails, try dividing the task into several smaller units. For example, if a file specification contains several high level directories, run the TSM task serially for each directory. If the TSM task is an incremental backup, use the option "-memoryefficientbackup=yes".</p> <p>For UNIX systems that support resource limits, check to see b if the memory resource limit is too low by entering the following command: <xph> ulimit -a </xph></p> <p> Based on the resulting data, you can ask the UNIX system root user to increase resource limits so that it will override the current default. The UNIX system root user has the authority to increase resource limits. </p>
# 1035
COM_OptFileNotFound=ANS1035S Options file '{0}' could not be found, or it cannot be read. \n
COM_OptFileNotFound_EXPLANATION=<p>Common reasons for this error include:<ul> <li>The default options file does not exist.</li> <li>You specified the -OPTFILE option when starting the IBM Tivoli Storage Manager client, but the options file you provided does not exist.</li> <li>The DSM_CONFIG (or DSMI_CONFIG if you are using the IBM Tivoli Storage Manager API) environment variable specifies an options file that does not exist.</li> <li>You specified the -OPTFILE option when starting the IBM Tivoli Storage Manager client, but the options file that you provided is not in the standard file encoding of the system. For example, on Windows the expected file encoding is ANSI.</li> <li>You specified the -OPTFILE option when starting the IBM Tivoli Storage Manager client, but the options file that you provided does not have appropriate read permissions for the user that is running the operation.</li> </ul> </p>
COM_OptFileNotFound_SYSACT=<p> IBM Tivoli Storage Manager client processing stops. </p>
COM_OptFileNotFound_URESP=<p> Make sure that the options file you want to use exists, it has the read rights set for the user that is running the operation, and it is in the standard file encoding of the system. For example, on Windows the expected file encoding is ANSI. Review the configuration information in the IBM Tivoli Storage Manager client manual specific to your operating system. If the problem persists, ask your IBM Tivoli Storage Manager administrator for further assistance. </p>
# 1036
COM_Options_Emsg=ANS1036S The option '{0}' or the value supplied for it is not valid. It was found in options file '{1}'\n\t at line number: {2}\n\t The complete entry: '{3}'\n\n
COM_Options_Emsg_EXPLANATION=<p> The specified <mv>option</mv> in the TSM options file (<mv>file-name</mv>) or the command line, is in error. Either the option itself or its value are invalid. For options that include a date or time specification, the format of the date or time might not match the formats specified by the DATEFORMAT or TIMEFORMAT options. </p>
COM_Options_Emsg_SYSACT=<p> Processing stopped. </p>
COM_Options_Emsg_URESP=<p> Correct the option name or value. For options that specify dates or times, ensure that the specified date or time matches the DATEFORMAT and TIMEFORMAT settings. If -DATEFORMAT or -TIMEFORMAT are specified on the command line, they must precede the option that specifies the date or time. For example, use -DATEFORMAT=3 -FROMDATE=yyyy-mm-dd, instead of -FROMDATE=yyyy-mm-dd -DATEFORMAT=3. </p>
# 1037
COM_Invalid_Keyword=ANS1037S Invalid keyword specified\n
COM_Invalid_Keyword_EXPLANATION=<p> TSM found an incorrect keyword in the options file. </p>
COM_Invalid_Keyword_SYSACT=<p> Processing stopped. </p>
COM_Invalid_Keyword_URESP=<p> Correct the options file with valid entries. </p>
# 1038
COM_Invalid_Option=ANS1038S Invalid option specified\n
COM_Invalid_Option_EXPLANATION=<p> An incorrect option was specified to TSM. </p>
COM_Invalid_Option_SYSACT=<p> Processing stopped. </p>
COM_Invalid_Option_URESP=<p> Correct the options used for running TSM. </p>
# 1039
COM_Patt_Too_Complex=ANS1039S The include or exclude pattern cannot be parsed.\n
COM_Patt_Too_Complex_EXPLANATION=<p> The pattern is formatted incorrectly or is too complex for TSM to interpret. </p>
COM_Patt_Too_Complex_SYSACT=<p> Processing stopped. </p>
COM_Patt_Too_Complex_URESP=<p> Verify that the include or exclude pattern is specified correctly. If the pattern is correct, then contact IBM technical support for further assistance. </p>
# 1040
COM_Patt_Missing_Bracket=ANS1040S Include/Exclude pattern is missing a closing bracket\n
COM_Patt_Missing_Bracket_EXPLANATION=<p> The include or exclude pattern is incorrectly constructed. The closing bracket is missing. </p>
COM_Patt_Missing_Bracket_SYSACT=<p> Processing stopped. </p>
COM_Patt_Missing_Bracket_URESP=<p> Correct the syntax for the pattern. </p>
# 1042
COM_Patt_Missing_Delim=ANS1042S A beginning or ending directory delimiter is missing from the Include/Exclude pattern.\n
COM_Patt_Missing_Delim_EXPLANATION=<p> <ol> <li>The include/exclude pattern has a '...' without a beginning or ending directory delimiter.</li> <li>For Windows, the drive seperator is not immediately followed by a directory delimiter.</li></ol> </p>
COM_Patt_Missing_Delim_SYSACT=<p> Processing stopped. </p>
COM_Patt_Missing_Delim_URESP=<p> Correct the syntax for the pattern. </p>
# 1043
COM_Unmatched_Quotes=ANS1043S Quotes are not matched\n
COM_Unmatched_Quotes_EXPLANATION=<p> The quotes specified in the pattern are not the same and do not make a set. </p>
COM_Unmatched_Quotes_SYSACT=<p> Processing stopped. </p>
COM_Unmatched_Quotes_URESP=<p> Correct the pattern by using matching quotes in the syntax. </p>
# 1048
Img_Device_Not_Local_Cl=ANS1048E Device '{0}' is not local\n
Img_Device_Not_Local_Cl_EXPLANATION=<p>The selected path is not a local device and therefore is not a valid object for image operations.\n</p>
Img_Device_Not_Local_Cl_SYSACT=<p>The requested logical volume operation is not performed.</p>
Img_Device_Not_Local_Cl_URESP=<p>Choose another object.</p>
# 1052
CLI_Direct_Storage_Agent_Unsupported=ANS1052E Direct connection to the Storage Agent is not allowed.\n
CLI_Direct_Storage_Agent_Unsupported_EXPLANATION=<p>You cannot connect directly to the Storage Agent.</p>
CLI_Direct_Storage_Agent_Unsupported_SYSACT=<p>Processing stopped.</p>
CLI_Direct_Storage_Agent_Unsupported_URESP=<p>To perform Lanfree operations using the Storage Agent, specify the ENABLELANFREE option in your options file, and restart the process.</p>
# 1056
CLI_Sharename_Path_Not_Found=ANS1056E Share/network path {0} cannot be resolved. Path does not exist.\n
CLI_Sharename_Path_Not_Found_EXPLANATION=<p> For backup: Trying to backup share/network, which either does not exist or does not have the correct privilege to access the share. For restore : Trying to restore to a share/network path that cannot be resolved. The directory path does not exist. </p>
CLI_Sharename_Path_Not_Found_SYSACT=<p>Processing stopped.</p>
CLI_Sharename_Path_Not_Found_URESP=<p> Retry the command and specify a destination, or restore the directory tree first before trying to restore the share point. </p>
# 1058
CLI_Invalid_Restore_Destination=ANS1058E The restore destination cannot be reached.\n
CLI_Invalid_Restore_Destination_EXPLANATION=<p> Either the destination file system is invalid or it cannot be reached. </p>
CLI_Invalid_Restore_Destination_SYSACT=<p>Processing stopped.</p>
CLI_Invalid_Restore_Destination_URESP=<p>Try the command again using a different destination.</p>
# 1060
Fs_Not_A_Mount_Point=ANS1060E The specified path is not a mounted filesystem\n
Fs_Not_A_Mount_Point_EXPLANATION=<p>You entered a file system name that does not correspond to a mounted file system for this system. It is possible the file system name is misspelled, or simply that the file system is not currently mounted.</p>
Fs_Not_A_Mount_Point_SYSACT=<p>The requested logical volume operation is not performed.</p>
Fs_Not_A_Mount_Point_URESP=<p>Retry the operation, using name of a mounted file system.</p>
# 1061
Dev_Is_Fs=ANS1061E The specified device corresponds to a mounted file system; you must specify the file system by name.\n
Dev_Is_Fs_EXPLANATION=<p>You entered a logical device name that is mapped to a mounted file system. This volume must only be referenced by its file system name.</p>
Dev_Is_Fs_SYSACT=<p>The requested logical volume operation is not performed.</p>
Dev_Is_Fs_URESP=<p>Try the operation again, using the file system name instead of the device name.</p>
# 1063
Img_Invalid_Drive=ANS1063E The specified path is not a valid file system or logical volume name.\n
Img_Invalid_Drive_EXPLANATION=<p> None. </p>
Img_Invalid_Drive_SYSACT=<p> The logical volume operation is not performed. </p>
Img_Invalid_Drive_URESP=<p> Try the operation again using a valid path. </p>
# 1064
Img_Internal_Err=ANS1064E An unexpected error occurred while processing the image operation.
Img_Internal_Err_EXPLANATION=<p> None. </p>
Img_Internal_Err_SYSACT=<p> The requested operation does not run. </p>
Img_Internal_Err_URESP=<p> Examine the client error log for any additional messages that may have been issued before or after this message. Correct any problems, if possible. If the cause of this message can not be determined or resolved, contact IBM technical support for further assistance. </p>
# 1065
Img_Caller_Pilib_High=ANS1065E Library version of the image utility does not match that of the TSM API\n
Img_Caller_Pilib_High_EXPLANATION=<p> The current system has a mix of installed components. </p>
Img_Caller_Pilib_High_SYSACT=<p> The requested logical volume operation is not performed. </p>
Img_Caller_Pilib_High_URESP=<p> Re-install all TSM components </p>
# 1066
Img_Rest_Ok_Mount_Fail=ANS1066E The restore operation completed successfully, but the file system could not be remounted.
Img_Rest_Ok_Mount_Fail_EXPLANATION=<p> None. </p>
Img_Rest_Ok_Mount_Fail_SYSACT=<p> The file system is left unmounted. </p>
Img_Rest_Ok_Mount_Fail_URESP=<p> Use the mount command to mount the file system. On AIX, run fsck if requested by the operating system. </p>
# 1067
Img_Os_Syscall_Err=ANS1067E A call to a system function returned an unexpected error.
Img_Os_Syscall_Err_EXPLANATION=<p> If you are performing a JFS2 snapshot based operation, it is possible that the snapshot was not large enough to contain all the changes made to the filesystem after the snapshot was created. This could cause the snapshot to become invalid thereby preventing TSM client from reading the snapshot. </p>
Img_Os_Syscall_Err_SYSACT=<p> The requested operation does not run. </p>
Img_Os_Syscall_Err_URESP=<p> Examine the client error log for additional messages related to this error. Try the operation again. If the problem persists, contact IBM technical support for further assistance. </p> <p> If you are performing a JFS2 snapshot based operation, please use the default snapshotcachesize of 100% and ensure that the volume group has sufficient disk space to allocate snapshots at least as large as the file system and retry the operation. </p>
# 1068
Img_Device_Not_Local=ANS1068E Device is not local \n
Img_Device_Not_Local_EXPLANATION=<p> The selected path is not a local device and therefore is not a valid object for image operations\n</p>
Img_Device_Not_Local_SYSACT=<p> The requested logical volume operation is not performed. </p>
Img_Device_Not_Local_URESP=<p> Choose another object. </p>
# 1069
Img_Read_Failure=ANS1069E An error occurred while reading data from the device\n
Img_Read_Failure_EXPLANATION=<p>An error occurred while reading data from the device. Windows Only: This could be due to bad sectors on the drive.</p>
Img_Read_Failure_SYSACT=<p>The requested logical volume operation is not performed.</p>
Img_Read_Failure_URESP=<p>Retry the operation, then check the error log for more information. Windows Only: Please run chkdsk /r and retry the operation. If the problem persists, a possible workaround is to back up the entire drive using a regular (non-image) backup. Please ensure that all your data is backed up. Then format the drive using a full format (without the /q quick format option). Then restore the data and retry the image backup operation.</p>
# 1070
Img_Write_Failure=ANS1070E Write error \n
Img_Write_Failure_EXPLANATION=<p> An error occurred while writing data to the device. </p>
Img_Write_Failure_SYSACT=<p> The requested logical volume operation is not performed. </p>
Img_Write_Failure_URESP=<p> Re-try the operation, check error log for more information. </p>
# 1071
CLI_Inv_Domain=ANS1071E Invalid domain name entered: '{0}'\n
CLI_Inv_Domain_EXPLANATION=<p> You entered an invalid domain <mv>domain-name.</mv> Check whether the domain name is a file system and the file system is mounted. A directory cannot be specified in the domain option, unless it is a virtual mount point. </p>
CLI_Inv_Domain_SYSACT=<p> Processing continues if there are other file systems in the domain option to back up. </p>
CLI_Inv_Domain_URESP=<p> Enter a valid drive or file system name (domain). </p>
# 1072
CLI_No_Volume_Label=ANS1072E Unable to continue operation; Drive '{0}' has no volume label.\n
CLI_No_Volume_Label_EXPLANATION=<p> The specified <mv>drive-name</mv> in the domain list does not have a volume label. </p>
CLI_No_Volume_Label_SYSACT=<p> Processing stopped. </p>
CLI_No_Volume_Label_URESP=<p> Use the system format utility to place a unique volume label on all drives on which you intend to run TSM. </p>
# 1077
GUI_LastImageBackup=Last Image Backup
# 1080
GUI_NAS=NAS
# 1091
CLI_Comm_Error_During_Query=ANS1091E Communications error with server during object query\n
CLI_Comm_Error_During_Query_EXPLANATION=<p>An unexpected communications error occurred during an object query to the server.</p>
CLI_Comm_Error_During_Query_SYSACT=<p>Processing stopped.</p>
CLI_Comm_Error_During_Query_URESP=<p>Verify that communications are active between the client and server machines. Server outages, processor outages, and communication controller outages can cause this error.</p>
# 1092
CLI_No_Match_Found=ANS1092W No files matching search criteria were found\n
CLI_No_Match_Found_EXPLANATION=<p> You entered a search pattern or file name that cannot be found in the server database. </p>
CLI_No_Match_Found_SYSACT=<p> Processing stopped. </p>
CLI_No_Match_Found_URESP=<p> Ensure that your search pattern is correct, or specify a new search string. </p>
# 1096
CLI_NO_PS_Data_Found=ANS1096S Either the node does not exist on the server or there is no active policy set for the node.\n
CLI_NO_PS_Data_Found_EXPLANATION=<p> This error occurs when you try to access another node's data. Either the node is not registered with the TSM server, or there is no active policy set for the node. </p>
CLI_NO_PS_Data_Found_SYSACT=<p> Processing stops. </p>
CLI_NO_PS_Data_Found_URESP=<p> Verify that the node whose data you are trying to access is registered with the TSM server. If you have more than one TSM server, make sure you are connecting to the correct server, then try the operation again. If the problem persists, contact your TSM administrator for further assistance. </p>
# 1101
CLI_Encrypt_Not_Authorized=ANS1101E User is not authorized to encrypt {0}{1}{2}.\n
CLI_Encrypt_Not_Authorized_EXPLANATION=<p> The user is not authorized to encrypt the file. Normally, only a IBM Tivoli Storage Manager authorized user or a root user can use IBM Tivoli Storage Manager encryption. However, a certain combination of PASSWORDACCESS and ENCRYPTKEY options may allow encryption operations by a non-authorized user. </p>
CLI_Encrypt_Not_Authorized_SYSACT=<p>The file is not backed up or restored.</p>
CLI_Encrypt_Not_Authorized_URESP=<p>Log in as a root or IBM Tivoli Storage Manager authorized user and try the operation again. See IBM Tivoli Storage Manager Backup-Archive Client Installation and User's Guide for the correct usage of the ENCRYPTKEY option.</p> 
# 1103
CLI_Invalid_Management_Class=ANS1103E Invalid management class entered\n
CLI_Invalid_Management_Class_EXPLANATION=<p> You entered an invalid management class. </p>
CLI_Invalid_Management_Class_SYSACT=<p> TSM is unable to do the requested operation. </p>
CLI_Invalid_Management_Class_URESP=<p> Retry the operation using a valid management class. </p>
# 1105
CLI_MC_No_Back_CG=ANS1105E The management class for this file does not have a valid backup copy group.\nThis file will not be backed up.\n
CLI_MC_No_Back_CG_EXPLANATION=<p>The management class for this file does not have a backup copy group specified. This file will not be backed up.</p>
CLI_MC_No_Back_CG_SYSACT=<p>Processing stopped.</p>
CLI_MC_No_Back_CG_URESP=<p>Add a valid backup copy group to the management class, and then retry the operation.</p>
# 1113
Img_Snapshot_Cache_Location_Invalid=ANS1113E The snapshot cache location is not valid.\n
Img_Snapshot_Cache_Location_Invalid_EXPLANATION=<p>The snapshot cache location must point to a local volume that is formatted with NTFS. The default cache location is on the same volume where the snapshot is being performed. The operation will continue without snapshot support. </p>
Img_Snapshot_Cache_Location_Invalid_SYSACT=<p>The client does not execute the snapshot backup operation.</p>
Img_Snapshot_Cache_Location_Invalid_URESP=<p>Specify a different snapshot cache location using the SNAPSHOTCACHELOCATION option.</p>
# 1115
CLI_MC_Excluded=ANS1115W File '{0}{1}{2}' excluded by Include/Exclude list\n
CLI_MC_Excluded_EXPLANATION=<p>You can not back up, archive, or migrate files that are excluded.</p>
CLI_MC_Excluded_SYSACT=<p>TSM does not process the file.</p>
CLI_MC_Excluded_URESP=<p> If the file is intentionally excluded, then this message can be ignored. Otherwise modify the include/exclude list, restart the client, and try the operation again. Contact your TSM administrator for further assistance.</p>
# 1124
DSI_PswdChangeNotAllowed=Password cannot be changed via this application when authentication is OFF on the server. Please try again when authentication is ON.
# 1130
CLI_No_Label=ANS1130E The drive has no label. The operation cannot continue.
CLI_No_Label_EXPLANATION=<p> Backup or archive of removable media requires that the media have a volume label. An attempt was made to back up or archive data on a removable volume that has no label. </p>
CLI_No_Label_SYSACT=<p> The requested operation does not run. </p>
CLI_No_Label_URESP=<p> Create a volume label on the removable media, then try the operation again. </p>
# 1134
CLI_Invalid_Drive_Spec=ANS1134E Drive {0} is an invalid drive specification\n
CLI_Invalid_Drive_Spec_EXPLANATION=<p> The specified <mv>drive-name</mv> was found to be invalid; the drive probably has not been defined. </p>
CLI_Invalid_Drive_Spec_SYSACT=<p> TSM skips the invalid drive and continues to the next drive. </p>
CLI_Invalid_Drive_Spec_URESP=<p> Check the invalid drive. </p>
# 1135
CLI_SUBST_Drive=ANS1135E Drive {0} is a virtual drive of {1}. It cannot be backed up or archived.\n
CLI_SUBST_Drive_EXPLANATION=<p> Drive <mv>drive-name1</mv> was found to be a substitute (SUBST) of drive <mv>drive-name2</mv>. The SUBST drive cannot be backed up or archived. </p>
CLI_SUBST_Drive_SYSACT=<p> The SUBST drive is skipped. Processing continues with the next drive. </p>
CLI_SUBST_Drive_URESP=<p> Do not specify any file specifications for a drive that is a substitute of another drive. Remove any explicit substitute drives from the DOMAIN statement or use the -<drive:> notation to remove a substitute drive if ALL-LOCAL is specified. </p>
# 1140
CLI_Invalid_SetAccess=ANS1140E Invalid format for Set Access command.\n
CLI_Invalid_SetAccess_EXPLANATION=<p>The SET ACCESS command must have at least three operands, the first of which must be either BACKUP or ARCHIVE. A validly formed file specification must follow.</p>
CLI_Invalid_SetAccess_SYSACT=<p>Processing stopped, the command is not executed.</p>
CLI_Invalid_SetAccess_URESP=<p>Use the HELP SET ACCESS command for complete details of usage, then enter the SET ACCESS command using the correct syntax.</p>
# 1147
CLI_File_Unavailable=ANS1147E File is temporarily unavailable.\n
CLI_File_Unavailable_EXPLANATION=<p> File is temporarily unavailable. </p>
CLI_File_Unavailable_SYSACT=<p> File skipped. </p>
CLI_File_Unavailable_URESP=<p> Check and see if file is locked by other process. If not, retry the command. </p>
# 1149
CLI_NoFileSpaces=ANS1149E No domain is available for incremental backup. The domain may be empty or all file systems in the domain are excluded.\n
CLI_NoFileSpaces_EXPLANATION=<p>An incremental backup was started, but no domain was selected. There are two possible reasons for this message: <ul> <li> The client is a diskless workstation for which no local file systems exist.</li> <li>An attempt was made to back up a file system that is excluded with the EXCLUDE.FS option.</li> </ul> </p>
CLI_NoFileSpaces_SYSACT=<p>processing stops.</p>
CLI_NoFileSpaces_URESP=<p>Choose a domain and restart the incremental backup. Make sure that the DOMAIN statement specifies the file systems you wish to back up. Prevent this message by not trying to back up the file system that is excluded with EXCLUDE.FS. If this file system should be backed up, then remove the EXCLUDE.FS option.</p>
# 1150
CLI_NTRunning_as_Local_System_Account=ANS1150E Unable to restore current user profile because you are running as\na local system account.\n
CLI_NTRunning_as_Local_System_Account_EXPLANATION=<p>The local system account does not have a profile. Therefore you cannot restore its profile.</p>
CLI_NTRunning_as_Local_System_Account_SYSACT=<p>Processing stops.</p>
CLI_NTRunning_as_Local_System_Account_URESP=<p>Log on to the user whose profile you want to restore.</p>
# 1151
CLI_NOT_CLUSTER_Disk1=ANS1151E '{0}' is not a cluster disk.\n
CLI_NOT_CLUSTER_Disk1_EXPLANATION=<p> The indicated file system is not a cluster disk. Because the CLUSTERNODE option is set to YES, the file system cannot be backed up or archived. </p>
CLI_NOT_CLUSTER_Disk1_SYSACT=<p>Processing stops.</p>
CLI_NOT_CLUSTER_Disk1_URESP=<p> If the CLUSTERNODE option is incorrectly set to YES, then change the option to NO and try the operation again. Otherwise see the client manual for further information about configuring the TSM client to run in a cluster environment. </p>
# 1153
CLI_CLUSTER_Disk1=ANS1153E '{0}' is a cluster disk.\n
CLI_CLUSTER_Disk1_EXPLANATION=<p> The indicated file system is a cluster disk. Because the CLUSTERNODE option is set to NO, the file system cannot be backed up or archived. </p>
CLI_CLUSTER_Disk1_SYSACT=<p>Processing stops.</p>
CLI_CLUSTER_Disk1_URESP=<p> If the CLUSTERNODE option is incorrectly set to NO, then change the option to YES and try the operation again. Otherwise see the client manual for further information about configuring the TSM client to run in a cluster environment. </p>
# 1155
CLI_NoImageDomain=ANS1155E No domain is available for image backup.\n
CLI_NoImageDomain_EXPLANATION=<p>An image backup was started, but no domain was specified.</p>
CLI_NoImageDomain_SYSACT=<p>Processing stopped.</p>
CLI_NoImageDomain_URESP=<p>Choose a domain and restart the image backup. Set the image domain using the domain.image option in your dsm.opt file, either manually, or by using the GUI preferences editor.</p>
# 1156
COM_Invalid_Nodename=ANS1156E NODENAME cannot be the local machine name when CLUSTERNODE is set to YES\n
COM_Invalid_Nodename_EXPLANATION=<p>When TSM is running as a cluster node, the node name cannot be the local machine name.</p>
COM_Invalid_Nodename_SYSACT=<p>Processing stops.</p>
COM_Invalid_Nodename_URESP=<p>Change the node name either to the cluster name or to any other name, and restart TSM.</p>
# 1162
Img_Mount_Failure=ANS1162E Filesystem could not be mounted \n
Img_Mount_Failure_EXPLANATION=<p> The system call to mount the file system failed. </p>
Img_Mount_Failure_SYSACT=<p> The file system remains unmounted. </p>
Img_Mount_Failure_URESP=<p> Use the mount command to mount the file system. On AIX, run fsck if requested by the operating system. </p>
# 1163
Img_Umount_Failure=ANS1163E Filesystem could not be unmounted.\n
Img_Umount_Failure_EXPLANATION=<p> The system call to unmount the file system failed. </p>
Img_Umount_Failure_SYSACT=<p> The logical volume operation is not performed. </p>
Img_Umount_Failure_URESP=<p> Make sure the device or file system is not being accessed, then retry the operation. </p>
# 1164
Img_Fs_Not_Mounted=ANS1164E Filesystem is not mounted \n
Img_Fs_Not_Mounted_EXPLANATION=<p> The named file system is not currently mounted. It must be mounted for TSM to perform an image backup. </p>
Img_Fs_Not_Mounted_SYSACT=<p> The logical volume operation is not performed. </p>
Img_Fs_Not_Mounted_URESP=<p> Mount the file system. </p>
# 1165
Img_Lv_Too_Small=ANS1165E Destination is smaller than source \n
Img_Lv_Too_Small_EXPLANATION=<p> The space allocation for the selected destination is smaller than the source. </p>
Img_Lv_Too_Small_SYSACT=<p> The restore operation is not performed. </p>
Img_Lv_Too_Small_URESP=<p> Choose a different, bigger destination or increase the size of the destination file space. </p>
# 1166
Img_Wrong_Fstype=ANS1166E Source and destination are not the same file system type.\n
Img_Wrong_Fstype_EXPLANATION=<p> The source and destination file system types do not match. </p>
Img_Wrong_Fstype_SYSACT=<p> The requested logical volume operation is not performed. </p>
Img_Wrong_Fstype_URESP=<p> Choose a destination that has the same file system type as the source. </p>
# 1180
CLI_Use_Journal=Using journal for '{0}'\n
# 1181
JOURNAL_NP_ERROR=ANS1181E There was a communication failure with the journal service.\n
JOURNAL_NP_ERROR_EXPLANATION=<p> An error occurred using named pipe communication with the journal service. </p>
JOURNAL_NP_ERROR_SYSACT=<p>Processing stops.</p>
JOURNAL_NP_ERROR_URESP=<p> Restart the journal service, then try the operation again. If the problem persists, contact IBM technical support for further assistance. </p>
# 1195
DSI_NTSecurity_AccessDenied=An error occurred accessing NTFS security information\n
# 1196
DSI_NTPrivilege_NotHeld=A required NT privilege is not held\n
# 1199
Img_Snapshot_PreCmd_Failed=ANS1199E The PRESNAPSHOTCMD command failed. The image snapshot backup will not be executed.\n
Img_Snapshot_PreCmd_Failed_EXPLANATION=<p>The command specified by the PRESNAPSHOTCMD option must complete successfully in order to execute the image snapshot backup. If the command completed with a return code of 0 (zero), it is considered to have completed successfully. If the command completed with any other return code, it is considered to have failed. If the command failed then the image snapshot backup is not executed.</p>
Img_Snapshot_PreCmd_Failed_SYSACT=<p>The client does not execute the image snapshot backup operation.</p>
Img_Snapshot_PreCmd_Failed_URESP=<p>Identify and repair the problem that caused the command to fail. If a non-zero return code is normal for this command, then consider wrapping the command in a script that always exits with a return code of zero.</p>
# 1200
Img_Snapshot_PostCmd_Failed=ANS1200W The POSTSNAPSHOTCMD command completed with a non-zero return code.\n
Img_Snapshot_PostCmd_Failed_EXPLANATION=<p>If the command specified by the POSTSNAPSHOTCMD option completed with a non-zero return code, then the image snapshot backup operation will continue, but with a warning-level result. Note that the result of the POSTSNAPSHOTCMD command will not supercede a higher result from the image snapshot backup command. For example, if the image snapshot backup command completed with a return code of 12, the image snapshot backup will be considered to have completed with a return code of 12, regardless of the outcome of the POSTSNAPSHOTCMD command.</p>
Img_Snapshot_PostCmd_Failed_SYSACT=<p>The image snapshot backup continues, but with a warning return code of at least 8.</p>
Img_Snapshot_PostCmd_Failed_URESP=<p>Identify and repair the problem that caused the command to fail. If a non-zero return code is normal for this command, then consider wrapping the command in a script that always exits with a return code of zero.</p>
# 1202
Img_Toc_Send_Fail=ANS1202E TOC backup for the image failed. Check log files. \n
Img_Toc_Send_Fail_EXPLANATION=<p> An error occurred during backup of the table of contents. Check the error log for more information. </p>
Img_Toc_Send_Fail_SYSACT=<p> The requested logical volume operation is not performed. </p>
Img_Toc_Send_Fail_URESP=<p> Check error log. </p>
# 1203
DSJ_EXPRESS_BSET_LOADTOC_ERROR=ANS1203E Table of Contents not available for selected backup set. Please contact server administrator.
DSJ_EXPRESS_BSET_LOADTOC_ERROR_EXPLANATION=<p>There is no TOC for selected backup set</p>
DSJ_EXPRESS_BSET_LOADTOC_ERROR_SYSACT=<p> Expansion of selected backup set will not be possible. Will only be able to restore the whole backup set. </p>
DSJ_EXPRESS_BSET_LOADTOC_ERROR_URESP=<p> Please contact server administrator to regenerate TOC for backup set before backup set can be expanded. </p>
# 1204
Express_Client_Not_Supported=ANS1204E This client is not supported by the TSM express server\n
Express_Client_Not_Supported_EXPLANATION=<p>This client is not supported by the TSM express server. This can occur if: <ol> <li>the client is configured as an TSM express client using the CLIENTVIEW option</li> <li>the client is trying to connect to an TSM express server.</li> </ol></p>
Express_Client_Not_Supported_SYSACT=<p>Processing stops.</p>
Express_Client_Not_Supported_URESP=<p>Log in using a supported TSM express client. </p>
# 1205
Express_Platform_Not_Supported=ANS1205E This is not a supported TSM express platform\n
Express_Platform_Not_Supported_EXPLANATION=<p>This is not a supported TSM express platform.</p>
Express_Platform_Not_Supported_SYSACT=<p>Processing stops.</p>
Express_Platform_Not_Supported_URESP=<p>Log in using a supported TSM express client. </p>
# 1206
Img_Raw_Ok_Toc_Notsupp=ANS1206E TOC backup of a raw device is not supported. But the raw device is backed up. \n
Img_Raw_Ok_Toc_Notsupp_EXPLANATION=<p> TOC backup of a raw device is not supported. But the raw device is backed up. </p>
Img_Raw_Ok_Toc_Notsupp_SYSACT=<p> Raw device is backed up with no TOC object. </p>
Img_Raw_Ok_Toc_Notsupp_URESP=<p> NONE. </p>
# 1207
Img_No_Tocbkup_Found=ANS1207E No TOC has been previously backed up for this file system.
Img_No_Tocbkup_Found_EXPLANATION=<p> The user is trying to query the TOC of a file system. TOC backup for that file system has not been previously done. </p>
Img_No_Tocbkup_Found_SYSACT=<p> Query stopped. </p>
Img_No_Tocbkup_Found_URESP=<p> Backup the file system again with -TOC option. </p>
# 1208
GUI_Rest_Nas_Confirm=You are about to restore a file system to a destination that might already contain data. The final contents of this destination after the restore is completed will be dependent on the NAS appliance. Are you sure you want to replace File System/Volume: '{0}'?
# 1214
Img_Snapshot_Too_Large=ANS1214E The logical volume group does not have enough free space to contain the volume snapshot.
Img_Snapshot_Too_Large_EXPLANATION=<p> The snapshot is created in the volume group that contains the logical volume being backed up. There is insufficient free space in the volume group to contain the snapshot. </p>
Img_Snapshot_Too_Large_SYSACT=<p>The operation ends.</p>
Img_Snapshot_Too_Large_URESP=<p> Decrease the SNAPSHOTCACHESIZE value or make additional space available in the logical volume group. Then try the operation again. </p>
# 1215
Img_Snapshot_Cache_Location_Conflict=ANS1215E On volumes that are RAW or formatted FAT32 the snapshot cache location cannot be located on the same volume that is being backed up.\n
Img_Snapshot_Cache_Location_Conflict_EXPLANATION=<p>When the snapshot cache location is located on the same volume that is being backed up the volume must be formatted with NTFS. The default cache location is on the same volume where the snapshot is being performed. </p>
Img_Snapshot_Cache_Location_Conflict_SYSACT=<p>The client does not execute the image snapshot backup operation.</p>
Img_Snapshot_Cache_Location_Conflict_URESP=<p>Specify a different snapshot cache location using the SNAPSHOTCACHELOCATION option.</p>
# 1216
CLI_Abort_No_Auth=ANS1216E Not authorized to run TSM. See the administrator for your system.\n
CLI_Abort_No_Auth_EXPLANATION=<p> The system options file for the server that you are attempting to connect to contains a user entry, a group entry, or both a user and group entry. Your user ID, or group ID, was not found in any of the entries. You are currently not authorized to run TSM to this server. </p>
CLI_Abort_No_Auth_SYSACT=<p> TSM initialization fails and the program ends. </p>
CLI_Abort_No_Auth_URESP=<p> See the TSM administrator for your system, and ask to be added to the user or group list for this server. </p>
# 1217
CLI_Abort_No_Server=ANS1217E Server name not found in System Options File\n
CLI_Abort_No_Server_EXPLANATION=<p> The system options file does not contain the SERVERNAME option. </p>
CLI_Abort_No_Server_SYSACT=<p> TSM initialization fails and the program ends. </p>
CLI_Abort_No_Server_URESP=<p> See the TSM administrator for your system, and make sure that the system options file contains the server name. </p>
# 1218
CLI_Abort_No_Host_Addr=ANS1218E TCPSERVERADDRESS not defined for this server in the System Options File\n
CLI_Abort_No_Host_Addr_EXPLANATION=<p> The TCPSERVERADDRESS for this server is not defined in the server name stanza in the system options file. </p>
CLI_Abort_No_Host_Addr_SYSACT=<p> TSM initialization fails and the program ends. </p>
CLI_Abort_No_Host_Addr_URESP=<p> See the TSM administrator for your system, and make sure that the server to which you are trying to connect, has a valid TCPSERVERADDRESS defined in the system options file. </p>
# 1219
CLI_Abort_Machine_Same=ANS1219E A virtual node name must not equal either a node name or the system host name.\n
CLI_Abort_Machine_Same_EXPLANATION=<p> A VIRTUALNODENAME option was entered with a name the same as either a NODENAME option or the system host name. </p>
CLI_Abort_Machine_Same_SYSACT=<p> Initialization fails and the program ends. </p>
CLI_Abort_Machine_Same_URESP=<p> If the virtual node name entered was the same as the host name, remove the virtual node name option. If it was the same as the node name option, you can remove either one, depending upon the intended usage. Node name is used to assign an alternate name to your system. Virtual node name is used to access another system's server data. </p>
# 1229
Img_Invalid_Incr=ANS1229E MODE=INCREMENTAL is not valid on {0}. Image backup not processed.\n
Img_Invalid_Incr_EXPLANATION=<p>Because the file space has been the subject of at least one progressive incremental backup, the MODE=INCREMENTAL option (incremental by image date) cannot be used with the backup image command.</p>
Img_Invalid_Incr_SYSACT=<p>File system skipped.</p>
Img_Invalid_Incr_URESP=<p>If an image backup of the named file space is desired, retry the command without the MODE=INCREMENTAL option. To prevent this behavior in the future, delete the file space from the server and do only BACKUP IMAGE -mode=selective and BACKUP IMAGE -mode=incremental from that point on.</p>
# 1230
CLI_Stale_File=ANS1230E Stale NFS File Handle\n
CLI_Stale_File_EXPLANATION=<p> An NFS file system becomes stale. </p>
CLI_Stale_File_SYSACT=<p> File system skipped. </p>
CLI_Stale_File_URESP=<p> Check the NFS mounted filesystem. </p>
# 1237
CLI_Serv_Prob_See_Error_Log=ANS1237E A problem has occurred on the TSM server.
CLI_Serv_Prob_See_Error_Log_EXPLANATION=<p> The TSM client error log and the TSM server activity log might contain additional information about this error. </p>
CLI_Serv_Prob_See_Error_Log_SYSACT=<p> Processing stops. </p>
CLI_Serv_Prob_See_Error_Log_URESP=<p> Try the operation again. If the problem persists, examine the TSM client error log and TSM server activity log for additional information about this error. If the problem cannot be resolved, then obtain a SERVICE trace that captures the problem and contact IBM technical support for additional assistance. Your TSM administrator can help you configure the trace. </p>
# 1238
CLI_Int_Error_See_Error_Log=ANS1238S A policy management problem has occurred on the TSM server.\n
CLI_Int_Error_See_Error_Log_EXPLANATION=<p> The TSM client error log and TSM server activity log may contain additional information about this error. </p>
CLI_Int_Error_See_Error_Log_SYSACT=<p> Processing is stops. </p>
CLI_Int_Error_See_Error_Log_URESP=<p> Try the operation again. If the problem persists, examine the TSM client error log and TSM server activity log for additional information about this error. If the problem cannot be resolved, then obtain a SERVICE trace that captures the problem and contact IBM technical support for additional assistance. Your TSM administrator can help you configure the trace. </p>
# 1252
Invalid_Server_Msg=ANS1252W The server that you are connected to does not support this function.\n
Invalid_Server_Msg_EXPLANATION=<p>You attempted to run a backup-archive client operation when connected to the virtual server. Backup-archive client operations are not supported when connected to the virtual server.</p>
Invalid_Server_Msg_SYSACT=<p>The operation fails.</p>
Invalid_Server_Msg_URESP=<p>Connect to a valid server before attempting this function.</p>
# 1256
CLI_Cannot_Make=ANS1256E Cannot make file/directory\n
CLI_Cannot_Make_EXPLANATION=<p> The directory path for files being restored or retrieved cannot be created. </p>
CLI_Cannot_Make_SYSACT=<p> File skipped. </p>
CLI_Cannot_Make_URESP=<p> Ensure that you have the proper authorization to create the directory for file being restored or retrieved. Make sure that you have write access. </p>
# 1258
Img_Snapshot_Failed=ANS1258E The image snapshot operation failed.\n
Img_Snapshot_Failed_EXPLANATION=<p> TSM was not able to take a snapshot of the specified volume. </p>
Img_Snapshot_Failed_SYSACT=<p> Processing stopped. </p>
Img_Snapshot_Failed_URESP=<p> Check the error log for any other messages that might indicate a reason for the failure. Try to correct any indicated problems, then try the operation again. If the problem persists, contact IBM technical support for further assistance. </p>
# 1260
CLI_SM_Already_Recalled=ANS1260E File is being recalled or has been recalled.\n
CLI_SM_Already_Recalled_EXPLANATION=<p>The file is being recalled by another process or has been recalled.</p>
CLI_SM_Already_Recalled_SYSACT=<p>File skipped.</p>
CLI_SM_Already_Recalled_URESP=<p>None</p>
# 1265
CLI_Getmnt_Failed=ANS1265E Encountered bad mount or filesystem, processing stopped.\n
CLI_Getmnt_Failed_EXPLANATION=<p> The getmnt system call returned an error indication. Error was encountered trying to determine what the mounted file systems are. </p>
CLI_Getmnt_Failed_SYSACT=<p> Processing stopped. Cannot recover. </p>
CLI_Getmnt_Failed_URESP=<p> There is a bad file system or mount point on your system. Look at file systems and mounts, and correct any errors. If unsuccessful, see your system administrator for more information. </p>
# 1266
CLI_Mounts_Failed=ANS1266E Encountered bad mount or filesystem, processing stopped.\n
CLI_Mounts_Failed_EXPLANATION=<p> An error was encountered trying to determine what the mounted file systems are. </p>
CLI_Mounts_Failed_SYSACT=<p> Processing stopped. Cannot recover. </p>
CLI_Mounts_Failed_URESP=<p> Please, see your system administrator for more information. </p>
# 1267
CLI_MC_SM_Tech_None=ANS1267E The management class for file {0}\ndoes not allow migration. This file will not be migrated.\n
CLI_MC_SM_Tech_None_EXPLANATION=<p> The management class for this file does not allow migration </p>
CLI_MC_SM_Tech_None_SYSACT=<p> File is skipped. </p>
CLI_MC_SM_Tech_None_URESP=<p> Either have the TSM administrator change the Space Management Technique within the management class to a value other than NONE or change the include/exclude list to specify a management class with the appropriate Space Management Technique value. </p>
# 1268
CLI_SM_Already_Migrated=ANS1268E This file has been migrated.\n
CLI_SM_Already_Migrated_EXPLANATION=<p> The file has been migrated already. For instance, if some files that are hard linked together are migrated, then the files subsequent to the first one encountered get this error. However, there might be other reasons for this error - for details, see the user response section.</p>
CLI_SM_Already_Migrated_SYSACT=<p>File is skipped.</p>
CLI_SM_Already_Migrated_URESP=<p> If this error is not a result of a hard linked file migration, then this error may be due to the previous aborted migration or recall operation. In this case, try to restart the dsmrecalld and retry the operation.</p>
# 1287
Img_Volume_Lock_Failure=ANS1287E Volume could not be locked.\n
Img_Volume_Lock_Failure_EXPLANATION=<p> The system call to lock the volume failed. </p>
Img_Volume_Lock_Failure_SYSACT=<p> Processing stopped. </p>
Img_Volume_Lock_Failure_URESP=<p> Please verify that no other application is accessing the volume. If this volume is being accessed by applications that can not be shutdown during backup then perform an online image backup (snapshot with LVSA) instead. During restore of an image TSM must have exclusive use of the volume. </p>
# 1327
Snapshot_Failed_With_Error=ANS1327W The snapshot operation for '{0}' failed with error code: {1}.\n
Snapshot_Failed_With_Error_EXPLANATION=<p> A snapshot could not be taken of the specified volume. </p>
Snapshot_Failed_With_Error_SYSACT=<p>Snapshot processing stopped.</p>
Snapshot_Failed_With_Error_URESP=<p> Check the client error log for any other messages that might help identify the problem. If the problem cannot be resolved, contact IBM technical support for additional assistance. </p>
# 1328
DSM_DELTAFILE_GENERATES_ERROR=ANS1328W An error occurred generating delta file for '{0}'. The return code is {1}.\n
DSM_DELTAFILE_GENERATES_ERROR_EXPLANATION=<p> An error occurred that prevented the creation of the delta file. Possible reasons for this error include: <ul> <li>The base file cannot be opened for reading</li> <li>The file being backed up cannot be opened for reading</li> <li>The delta file cannot be opened for writing</li> <li>The file being backed up has grown to a size larger than 2 GB</li> <li>A memory file mapping of the file cannot be created</li> </ul> </p>
DSM_DELTAFILE_GENERATES_ERROR_SYSACT=<p> A full backup of the file is made, and a new version of the reference file is stored in the subfile cache. </p>
DSM_DELTAFILE_GENERATES_ERROR_URESP=<p> If the message indicates return code 4504, check the delta subfile cache directory for any residual delta files. The delta subfile cache directory is specified by the client option SUBFILECACHEPATH. Search the directory for files named \".dXXXXXXXX\" where \"XXXXXXXX"\\ is an eight-digit number. If there are no backup operations in progress, there should not be any files in the SUBFILECACHEPATH with this name. If there are no backup operations in progress and these files exist, they can safely be removed.\n\nIf you continue to receive this message but there are no residual delta files in the subfile cache directory and the file has not grown to a size larger than 2 GB, then contact IBM technical support for further assistance. </p>
# 1342
CLI_Client_Cache_Locked=ANS1342E Client cache is locked; unable to continue with operation.
CLI_Client_Cache_Locked_EXPLANATION=<p>The client cache is currently locked by another process. </p>
CLI_Client_Cache_Locked_SYSACT=<p>Processing stopped.</p>
CLI_Client_Cache_Locked_URESP=<p>Report the program error to your service representative.</p>
# 1344
CLI_Client_Back_Ground_Process=ANS1344E Job is running in the background. Cannot prompt for the Key.
CLI_Client_Back_Ground_Process_EXPLANATION=<p>When jobs are run in the background, the client cannot prompt for the key. </p>
CLI_Client_Back_Ground_Process_SYSACT=<p>Processing stopped.</p>
CLI_Client_Back_Ground_Process_URESP=<p>Run the Job in the foreground.</p>
# 1345
CLI_Restore_Abort_No_Match=ANS1345E No objects on server match '{0}{1}{2}'\n
CLI_Restore_Abort_No_Match_EXPLANATION=<p>The specified file (<mv>object-name</mv>) does not have a match on the server. </p>
CLI_Restore_Abort_No_Match_SYSACT=<p>File skipped.</p>
CLI_Restore_Abort_No_Match_URESP=<p>Backup the file and retry the operation. If the problem continues, see your system administrator to isolate the problem through use of the server console.</p>
# 1346
Img_Snapshot_CacheLocation_Full=ANS1346E The image snapshot operation failed. The SNAPSHOTCACHELocation does not contain enough space for this snapshot image backup.\n
Img_Snapshot_CacheLocation_Full_EXPLANATION=<p>TSM was not able to take a snapshot of the specified volume. The SNAPSHOTCACHELocation points to a location which does not contain the space necessary to manage the snapshot. This could be due to an unexpected amount of disk activity which is generating more changes than can be contained in the available space at this particular point in time, or the SNAPSHOTCACHELocation needs to be changed because the specified location is not large enough to handle the usual amount of changes to the volume. Another reason for this failure can be that the specified SNAPSHOTCACHESize is not set to a large enough value to handle the usual amount of changes to the volume during snapshot image backup. </p>
Img_Snapshot_CacheLocation_Full_SYSACT=<p> Processing stopped. </p>
Img_Snapshot_CacheLocation_Full_URESP=<p> If the problem persists please increase the SNAPSHOTCACHESize and/or change the value of the SNAPSHOTCACHELocation. </p>
# 1347
Img_Snapshot_CacheLocation_Percent_Exceeded=ANS1347E The image snapshot operation failed. The percent of space to use, specified via the SNAPSHOTCACHESize, has been exceeded.\n
Img_Snapshot_CacheLocation_Percent_Exceeded_EXPLANATION=<p>TSM was not able to take a snapshot of the specified volume. The percent of space allotted via the SNAPSHOTCACHESize option was not enough to perform this snapshot image backup. This could be due to an unexpected amount of disk activity which is generating more changes than can be contained in the allotted space at this particular point in time. Another reason for this failure can be that the specified SNAPSHOTCACHESize is not set to a large enough value to handle the usual amount of changes to the volume during snapshot image backup. </p>
Img_Snapshot_CacheLocation_Percent_Exceeded_SYSACT=<p> Processing stopped. </p>
Img_Snapshot_CacheLocation_Percent_Exceeded_URESP=<p> If the problem persists please increase the SNAPSHOTCACHESize or, for Windows, change the value of the SNAPSHOTCACHELocation. </p>
# 1348
Img_Snapshot_Too_Many_FS_Writes=ANS1348E Unable to satisfy the SNAPSHOTFSIDLEWait and SNAPSHOTFSIDLERetries options due to volume write activity.\n
Img_Snapshot_Too_Many_FS_Writes_EXPLANATION=<p>TSM was not able to take a snapshot of the specified volume. The Logical Volume Snapshot Agent was not able to satisfy the SNAPSHOTFSIDLEWait and SNAPSHOTFSIDLERetries options before starting the snapshot of the specified volume. </p>
Img_Snapshot_Too_Many_FS_Writes_SYSACT=<p> Processing stopped. </p>
Img_Snapshot_Too_Many_FS_Writes_URESP=<p> If the problem persists please modify the SNAPSHOTFSIDLEWait and SNAPSHOTFSIDLERetries options to better fit the normal disk write activity of the volume being backed up. </p>
# 1349
LVSA_Snapshot_Driver_Error=ANS1349E An error occurred during Logical Volume Snapshot Agent snapshot processing.\n
LVSA_Snapshot_Driver_Error_EXPLANATION=<p> An unrecoverable error occurred during snapshot processing. This can be caused by a variety of errors, so the error and system event logs should be checked for additional messages. </p>
LVSA_Snapshot_Driver_Error_SYSACT=<p> Processing stopped. </p>
LVSA_Snapshot_Driver_Error_URESP=<p> Check the client error log and the system event log for any other messages that might help identify the problem. Try the operation again. If the problem persists, contact IBM technical support for further assistance. </p>
# 1350
LVSA_Driver_Busy_With_Same_Volume=ANS1350E The logical volume snapshot agent (LVSA) is currently busy performing a snapshot on this same volume.\n
LVSA_Driver_Busy_With_Same_Volume_EXPLANATION=<p>Another IBM Tivoli Storage Manager process is already performing a snapshot of this volume. </p>
LVSA_Driver_Busy_With_Same_Volume_SYSACT=<p>The operation is stopped.</p>
LVSA_Driver_Busy_With_Same_Volume_URESP=<p>Please wait until the other IBM Tivoli Storage Manager process finishes with the volume and then retry the operation.</p>
# 1353
SESS_Reject_Id_Unknown=ANS1353E Session rejected: Unknown or incorrect user ID entered\n
SESS_Reject_Id_Unknown_EXPLANATION=<p> The user ID, which is either TSM node name or administrative user ID, is not known by the server. Possible reasons for this include: <ul style="simple"> <li>Your node name is not registered with the TSM server</li> <li> The node name is correct but does not have a corresponding administrative ID with the same name and client owner authority </li> <li>you are attempting to access a file that was migrated to a different node.</li> </ul> </p>
SESS_Reject_Id_Unknown_SYSACT=<p> TSM cancelled the current operation. </p>
SESS_Reject_Id_Unknown_URESP=<p> Verify that the server is using closed registration and that your node name is registered with the server. Ensure that you entered your TSM user ID correctly. Check that your TSM node name has a matching admin ID with client owner authority for the node. If it does not, your TSM administrator needs to create it. If attempting to access a migrated file, your node name must be the same node which migrated the file. </p>
# 1361
SESS_Reject_Id_Locked=ANS1361E Session Rejected: The specified node name is currently locked\n
SESS_Reject_Id_Locked_EXPLANATION=<p> The node name you specified is currently locked on the server. </p>
SESS_Reject_Id_Locked_SYSACT=<p> Session was not started. </p>
SESS_Reject_Id_Locked_URESP=<p> Check with your system administrator to find out why your node name is locked. </p>
# 1366
SESS_Reject_Internal_Error=ANS1366E The session is rejected. The TSM server has an internal error.\n
SESS_Reject_Internal_Error_EXPLANATION=<p> The client cannot establish a connection to the TSM server because of an internal server error. </p>
SESS_Reject_Internal_Error_SYSACT=<p> The session was not started. </p>
SESS_Reject_Internal_Error_URESP=<p> Notify your TSM administrator of this error. </p>
# 1369
SESS_Reject_Session_Canceled=ANS1369E Session Rejected: The session was canceled by the server administrator.\n
SESS_Reject_Session_Canceled_EXPLANATION=<p> The server administrator canceled the current client session. </p>
SESS_Reject_Session_Canceled_SYSACT=<p> Execution of the client connection request ends. </p>
SESS_Reject_Session_Canceled_URESP=<p> See your system administrator. </p>
# 1370
SESS_Reject_Id_Not_Authorized=ANS1370E The user ID entered does not have the correct level of authority to access the client machine.
SESS_Reject_Id_Not_Authorized_EXPLANATION=<p> The user ID entered cannot access this TSM client. </p>
SESS_Reject_Id_Not_Authorized_SYSACT=<p> The TSM operation ends. </p>
SESS_Reject_Id_Not_Authorized_URESP=<p> Grant authority to this user ID on the TSM server so that it can access this TSM client. </p>
# 1372
SESS_Reject_Invalid_Node_Type=ANS1372E An inconsistency was detected between the client node and \nthe node that is registered to the TSM server.
SESS_Reject_Invalid_Node_Type_EXPLANATION=<p>The user has probably coded the node option incorrectly. For instance, the node that is registered to the TSM server might be a type of NAS, but the node is actually a non-NAS client.</p>
SESS_Reject_Invalid_Node_Type_SYSACT=<p>The TSM operation ends.</p>
SESS_Reject_Invalid_Node_Type_URESP=<p>Ensure that the node name is correct in the client options file. Make sure to use a node of type NAS only with the nasnodename option.</p>
# 1373
Snapshot_PreCmd_Failed=ANS1373W The PRESNAPSHOTCMD command for volume {0} completed with a non-zero return code.\n
Snapshot_PreCmd_Failed_EXPLANATION=<p>The command specified by the PRESNAPSHOTCMD option must complete successfully in order to perform the snapshot backup/archive operation. If the command completed with a return code of 0 (zero), it has completed successfully. If the command completed with any other return code, it has failed. If the command failed, then the backup is still performed, but without the benefit of the snapshot technology.</p>
Snapshot_PreCmd_Failed_SYSACT=<p>The client executes the backup/archive operation, but without using a snapshot. </p>
Snapshot_PreCmd_Failed_URESP=<p>Identify and fix the problem that caused the command to fail. If a non-zero return code is normal for this command, then consider wrapping the command in a script that always exits with a return code of zero.</p>
# 1374
Snapshot_PostCmd_Failed=ANS1374W The POSTSNAPSHOTCMD command for volume {0} completed with a non-zero return code.\n
Snapshot_PostCmd_Failed_EXPLANATION=<p>The command specified by the POSTSNAPSHOTCMD option completed with a non-zero return code. The snapshot-based backup operation yields a return code of at least 8. </p>
Snapshot_PostCmd_Failed_SYSACT=<p>The snapshot-based backup operation continues.</p>
Snapshot_PostCmd_Failed_URESP=<p>Identify and resolve the problem that caused the post-snapshot command to fail. If a non-zero return code is normal for this command, then consider wrapping the post-snapshot command in a script that always exits with a return code of zero.</p>
# 1376
CLI_Digest_Validation_Error=ANS1376E Error processing '{0}{1}{2}'; end-to-end digest validation failed.\n
CLI_Digest_Validation_Error_EXPLANATION=<p> Cryptographic digest of the restored or retrieved data did not match the digest generated during the backup or archive operation. Possible causes are a transmission error, data corruption, or a hash collision. </p>
CLI_Digest_Validation_Error_SYSACT=<p>Processing stops</p>
CLI_Digest_Validation_Error_URESP=<p> Try the restore operation again. If the problem persists, contact IBM technical support for additional assistance. </p>
# 1377
Snapshot_Failed_Continue_Vol_No_Snap=ANS1377W The client was unable to obtain a snapshot of '{0}'. The operation will continue without snapshot support.\n
Snapshot_Failed_Continue_Vol_No_Snap_EXPLANATION=<p>TSM client was unable to create a snapshot of the volume due to some reason. Instead of failing the operation, TSM client will perform a non-snapshot based backup.</p>
Snapshot_Failed_Continue_Vol_No_Snap_SYSACT=<p>Snapshot processing stops.</p>
Snapshot_Failed_Continue_Vol_No_Snap_URESP=<p> Check the client error log for any other messages that might help identify the problem. Try the operation again. If the problem persists, contact IBM technical support for further assistance. </p>
# 1378
Snapshot_CacheLocation_Full=ANS1378E The snapshot operation failed. The SNAPSHOTCACHELocation does not contain enough space for this snapshot operation.\n
Snapshot_CacheLocation_Full_EXPLANATION=<p>IBM Tivoli Storage Manager was not able to take a snapshot of the specified volume. The SNAPSHOTCACHELocation points to a location which does not contain the space necessary to manage the snapshot. Reasons for failure include:<ul> <li>An unexpected amount of disk activity which is generating more changes than can be contained in the available space at this particular point in time. </li> <li>The SNAPSHOTCACHELocation is not large enough to handle the usual amount of changes to the volume.</li> <li>The specified SNAPSHOTCACHESize is not set to a large enough value to handle the usual amount of changes to the volume during snapshot backup or archive operation.</li> </ul></p>
Snapshot_CacheLocation_Full_SYSACT=<p>Processing stopped.</p>
Snapshot_CacheLocation_Full_URESP=<p>If the problem persists, increase the SNAPSHOTCACHESize or change the value of the SNAPSHOTCACHELocation.</p>
# 1379
Snapshot_CacheLocation_Percent_Exceeded=ANS1379E The snapshot operation failed. The percent of space to use for the SNAPSHOTCACHELocation, specified via the SNAPSHOTCACHESize, has been exceeded.\n
Snapshot_CacheLocation_Percent_Exceeded_EXPLANATION=<p>IBM Tivoli Storage Manager was not able to take a snapshot of the specified volume. The percent of space allotted via the SNAPSHOTCACHESize option was not enough to perform this snapshot backup/archive operation. Reasons for failure include:<ul> <li>The SNAPSHOTCACHELocation is not large enough to handle the usual amount of changes to the volume.</li> <li>The specified SNAPSHOTCACHESize is not set to a large enough value to handle the usual amount of changes to the volume during snapshot backup or archive operation.</li> </ul></p>
Snapshot_CacheLocation_Percent_Exceeded_SYSACT=<p>Processing stopped.</p>
Snapshot_CacheLocation_Percent_Exceeded_URESP=<p>If the problem persists, increase the SNAPSHOTCACHESize or change the value of the SNAPSHOTCACHELocation.</p>
# 1380
Snapshot_Too_Many_FS_Writes=ANS1380W The snapshot operation failed. The filesystem write activity prevented the Logical Volume Snapshot Agent from satisfying the SNAPSHOTFSIDLEWait and SNAPSHOTFSIDLERetries options.\n
Snapshot_Too_Many_FS_Writes_EXPLANATION=<p>IBM Tivoli Storage Manager was not able to take a snapshot of the specified volume. The Logical Volume Snapshot Agent was not able to satisfy the SNAPSHOTFSIDLEWait and SNAPSHOTFSIDLERetries options before starting the snapshot of the specified volume.</p>
Snapshot_Too_Many_FS_Writes_SYSACT=<p>Snapshot processing stops.</p>
Snapshot_Too_Many_FS_Writes_URESP=<p>If the problem persists, modify the SNAPSHOTFSIDLEWait and SNAPSHOTFSIDLERetries options to better fit the normal disk write activity of the volume being backed up.</p>
# 1381
Snapshot_Cache_Location_Conflict=ANS1381W On volumes that are RAW or formatted FAT32 the snapshot cache location cannot be located on the same volume that is being backed up.\n
Snapshot_Cache_Location_Conflict_EXPLANATION=<p>When the snapshot cache location is located on the same volume that is being backed up the volume must be formatted with NTFS. The default cache location is on the same volume where the snapshot is being performed. The operation will continue without snapshot support. </p>
Snapshot_Cache_Location_Conflict_SYSACT=<p>The client does not execute the snapshot operation.</p>
Snapshot_Cache_Location_Conflict_URESP=<p>Specify a different snapshot cache location, using the SNAPSHOTCACHELOCATION option.</p>
# 1382
SESS_Reject_Invalid_SessionInit=ANS1382E Server does not allow client-initiated connections for this node.
SESS_Reject_Invalid_SessionInit_EXPLANATION=<p> The node is not allowed to initiate connections due to the configuration parameters for this node on the server. Server is able to initiate connections to the client scheduler running in prompted mode. </p>
SESS_Reject_Invalid_SessionInit_SYSACT=<p>The IBM Tivoli Storage Manager operation ends.</p>
SESS_Reject_Invalid_SessionInit_URESP=<p> Contact your systems administrator to enable client-initiated sessions for your node or update the SESSIONINITIATION option and run the client scheduler. </p>
# 1383
SESS_Reject_Wrong_Port=ANS1383E Wrong server port.
SESS_Reject_Wrong_Port_EXPLANATION=<p> You were trying to open a backup/archive client session on the server port set up for administrative sessions only. </p>
SESS_Reject_Wrong_Port_SYSACT=<p>The IBM Tivoli Storage Manager operation ends.</p>
SESS_Reject_Wrong_Port_URESP=<p> Contact your systems administrator and/or use the correct values for TCP port and TCP Admin Port. </p>
# 1384
CLI_Abort_Invalid_Pol_Bind=ANS1384E An object in the transaction has been bound to an invalid management class.\n
CLI_Abort_Invalid_Pol_Bind_EXPLANATION=<p>One of the objects in the transaction is bound to a management class that is not part of this node's policy, or the management class type is not supported for this client level.</p>
CLI_Abort_Invalid_Pol_Bind_SYSACT=<p>The current operation ends.</p>
CLI_Abort_Invalid_Pol_Bind_URESP=<p>Make sure all objects are bound to a valid management class, or upgrade the client to the proper level.</p>
# 1385
CLI_Abort_Insert_Not_Allowed=ANS1385E This server does not support backup operations.\n
CLI_Abort_Insert_Not_Allowed_EXPLANATION=<p>This server only supports archive operations, backup is not allowed.</p>
CLI_Abort_Insert_Not_Allowed_SYSACT=<p>Current operation ends.</p>
CLI_Abort_Insert_Not_Allowed_URESP=<p>Use only archive operations with this server.</p>
# 1386
CLI_Abort_Delete_Not_Allowed=ANS1386E Deleting this object: "{0}{1}{2}" is not allowed.\n
CLI_Abort_Delete_Not_Allowed_EXPLANATION=<p>The object is either under a hold and cannot be deleted, or it is on a retention-protection enabled server and has not expired.</p>
CLI_Abort_Delete_Not_Allowed_SYSACT=<p>The object is skipped and processing continues.</p>
CLI_Abort_Delete_Not_Allowed_URESP=<p>Check the status of the object through a query to see if it is held, or when it expires.</p>
# 1387
CLI_Abort_Txn_Limit_Exceeded=ANS1387E The number of objects in this transaction exceed TXNGROUPMAX values.\n
CLI_Abort_Txn_Limit_Exceeded_EXPLANATION=<p>There are too many objects in this transaction.</p>
CLI_Abort_Txn_Limit_Exceeded_SYSACT=<p>Current operation ends.</p>
CLI_Abort_Txn_Limit_Exceeded_URESP=<p>Try the operation again with fewer objects in the transaction, or increase the TXNGROUPMAX value on the server.</p>
# 1388
CLI_Abort_Object_Aready_Held=ANS1388E {0}{1}{2} is already under hold.\n
CLI_Abort_Object_Aready_Held_EXPLANATION=<p><ph props="api">One of the objects in the transaction</ph> <ph props="msg">The specified object</ph> is already under hold, and it cannot be placed under a new hold.</p>
CLI_Abort_Object_Aready_Held_SYSACT=<p><ph props="api">Current operation ends.</ph> <ph props="msg">This object is skipped and processing continues.</ph></p>
CLI_Abort_Object_Aready_Held_URESP=<p>Issue a query to see the status of the objects, and try the operation again, without the object that is already held.</p>
# 1395
CLI_Invalid_Destination_Filespace=ANS1395E The destination filespace or drive letter is unavailable. The following object was not processed: \nFilespace:'{0}' \n
CLI_Invalid_Destination_Filespace_EXPLANATION=<p>The system is trying to restore or retrieve to a destination that cannot be reached. The specified filespace name or drive letter is not valid, or does not exist, or you are specifying a local share name that cannot be resolved. </p>
CLI_Invalid_Destination_Filespace_SYSACT=<p>Objects which are part of this filespace are not processed.</p>
CLI_Invalid_Destination_Filespace_URESP=<p>Try the command again, and specify a different destination for the object that was not processed. </p>
# 1397
Snapshot_Unable_Create_CacheFiles=ANS1397W The snapshot cannot be taken because the SNAPSHOTCACHELocation does not have enough space for this snapshot operation.\n
Snapshot_Unable_Create_CacheFiles_EXPLANATION=<p>IBM Tivoli Storage Manager was not able to take a snapshot of the specified volume. The SNAPSHOTCACHELocation points to a location which does not contain the space necessary to create the snapshot; the disk is probably full. The operation continues without snapshot support. </p>
Snapshot_Unable_Create_CacheFiles_SYSACT=<p>The client does not execute the snapshot operation.</p>
Snapshot_Unable_Create_CacheFiles_URESP=<p>Change the value of the SNAPSHOTCACHELocation, or clean the disk to which the SNAPSHOTCACHELocation points.</p>
# 1399
OFS_LVSA_Driver_Busy_With_Same_Volume=ANS1399W The logical volume snapshot agent (LVSA) is currently busy performing a snapshot on this same volume.\n
OFS_LVSA_Driver_Busy_With_Same_Volume_EXPLANATION=<p>IBM Tivoli Storage Manager was not able to take a snapshot of the specified volume because another process is already performing a snapshot of this volume. The operation continues without snapshot support. </p>
OFS_LVSA_Driver_Busy_With_Same_Volume_SYSACT=<p>Snapshot processing stops.</p>
OFS_LVSA_Driver_Busy_With_Same_Volume_URESP=<p>Wait until the other IBM Tivoli Storage Manager process finishes with the volume and then try the operation again.</p>
# 1400
OFS_Snapshot_Cache_Location_Invalid=ANS1400W The snapshot cache location is not valid.\n
OFS_Snapshot_Cache_Location_Invalid_EXPLANATION=<p>The snapshot cache location must point to a local volume that is formatted with NTFS. The default cache location is on the same volume where the snapshot is being performed. The operation will continue without snapshot support. </p>
OFS_Snapshot_Cache_Location_Invalid_SYSACT=<p>Snapshot processing stops.</p>
OFS_Snapshot_Cache_Location_Invalid_URESP=<p>Specify a different snapshot cache location using the SNAPSHOTCACHELOCATION option.</p>
# 1401
OFS_Snapshot_Virtual_Vol_Inaccessible=ANS1401W The snapshot virtual volume is not accessible.\n
OFS_Snapshot_Virtual_Vol_Inaccessible_EXPLANATION=<p>The logical volume snapshot agent (LVSA) cannot access the virtual volume during OFS-enabled backup/archive operation because IBM Tivoli Storage Manager was probably started via terminal services. The operation continues without snapshot support. </p>
OFS_Snapshot_Virtual_Vol_Inaccessible_SYSACT=<p>Snapshot processing stops.</p>
OFS_Snapshot_Virtual_Vol_Inaccessible_URESP=<p>Do not use terminal services for the snapshot. Try the operation again on the local machine. </p>
# 1402
OFS_Snapshot_Notsupported_On_Vol=ANS1402W The snapshot is not supported on a remote, removable, or SAN drive.\n
OFS_Snapshot_Notsupported_On_Vol_EXPLANATION=<p>IBM Tivoli Storage Manager was not able to take a snapshot of the specified volume because open file support is only supported on local fixed volumes, including volume mountpoints. The operation continues without snapshot support. </p>
OFS_Snapshot_Notsupported_On_Vol_SYSACT=<p>The client does not execute the snapshot operation.</p>
OFS_Snapshot_Notsupported_On_Vol_URESP=<p>To take advantage of the open file support, you may try the operation again on the local machine.</p>
# 1403
SESS_DLL_LoadFailure=ANS1403E Error loading a required {0} DLL\n
SESS_DLL_LoadFailure_EXPLANATION=<p>An error occurred while loading a dynamic link library. The DLL load failed. </p>
SESS_DLL_LoadFailure_SYSACT=<p>Processing stopped.</p>
SESS_DLL_LoadFailure_URESP=<p>Verify that your system software is up to date and that all DLLs required by the TSM client are present.</p>
# 1404
SESS_DLL_Function_LoadFailure=ANS1404E Error loading one or more functions from a required {0} DLL\n
SESS_DLL_Function_LoadFailure_EXPLANATION=<p>An error occurred while loading a function from a dynamic link library. The DLL load failed. </p>
SESS_DLL_Function_LoadFailure_SYSACT=<p>Processing stopped.</p>
SESS_DLL_Function_LoadFailure_URESP=<p>Verify that your system software is up to date.</p>
# 1406
Snapshot_Used_For_Vol_Name=ANS1406I Performing operation using point-in-time copy of the filesystem: '{0}'.\n
# 1407
Snapshot_Used_For_Vol=ANS1407I Performing operation using point-in-time copy of the filesystem.\n
# 1408
CLI_OFS_Reboot_Required_Before_Continuing=ANS1408W Previous changes have not been commited.\n The machine must be restarted before the snapshot can be taken
CLI_OFS_Reboot_Required_Before_Continuing_EXPLANATION=<p>IBM Tivoli Storage Manager was not able to take a snapshot of the specified volume because a previous operation required the machine to be restarted for the changes to take effect, but the machine has not been restarted. The operation will continue without snapshot support. </p>
CLI_OFS_Reboot_Required_Before_Continuing_SYSACT=<p>The client does not execute the snapshot operation.</p>
CLI_OFS_Reboot_Required_Before_Continuing_URESP=<p>Restart the machine and then try the operation again.</p>
# 1410
CLI_BAD_NETPATH=ANS1410E Unable to access the network path.\n
CLI_BAD_NETPATH_EXPLANATION=<p> The network path cannot be accessed due to a possible network problem. </p>
CLI_BAD_NETPATH_SYSACT=<p> The client terminates. </p>
CLI_BAD_NETPATH_URESP=<p> Ensure that the network is up and the path can be accessed using a system command, and retry the operation. </p>
# 1411
CLI_SESS_DROP=ANS1411E A communication session was dropped.\n
CLI_SESS_DROP_EXPLANATION=<p> A communication session was dropped due to a possible network problem. </p>
CLI_SESS_DROP_SYSACT=<p> The client terminates. </p>
CLI_SESS_DROP_URESP=<p> Ensure that the network is up and retry the operation. </p>
# 1412
CLI_BAD_EADATA=ANS1412E Directory or file has bad EA data or inconsistent data.\n
CLI_BAD_EADATA_EXPLANATION=<p> Directory or file has bad EA data or inconsistent data. </p>
CLI_BAD_EADATA_SYSACT=<p> The client terminates. </p>
CLI_BAD_EADATA_URESP=<p> Check failing directory or file for bad EA data. Copy the directory to a new location and retry the operation. </p>
# 1415
CLI_VSS_ASR_PreRestore_Wait=Waiting for pre-restore to complete ['{0}'].
# 1416
CLI_VSS_ASR_PostRestore_Wait=Waiting for post-restore to complete ['{0}'].
# 1448
CLI_Invalid_Command_For_Server=ANS1448E The {0} command is not supported by the current server.\n
CLI_Invalid_Command_For_Server_EXPLANATION=<p>The server to which the client is connected does not support the <mv>command</mv>. <ol> <li>If the command is "set event," the server does not support event-based policy. This command requires that the server support event-based policy. That support is available only at TSM Server levels 5.2.2 and above.</li> <li>If the message displays any other command, the server is configured to support archive retention protection and cannot process operations not associated with that facility.</li> </ol></p>
CLI_Invalid_Command_For_Server_SYSACT=<p>The command is skipped and other processing continues.</p>
CLI_Invalid_Command_For_Server_URESP=<p>Log in to an appropriate server and retry the command.</p>
# 1451
MoreInfo_Msg=More Information
# 1452
LessInfo_Msg=Less Information
# 1461
CLI_Encryption_Type_Unknown=ANS1461E Error processing '{0}{1}{2}': unsupported encryption type.\n
CLI_Encryption_Type_Unknown_EXPLANATION=<p>The files you are trying to restore or retrieve have been backed up or archived by a later version of the TSM client. The file encryption method is not supported by the current client.</p>
CLI_Encryption_Type_Unknown_SYSACT=<p>Object skipped.</p>
CLI_Encryption_Type_Unknown_URESP=<p>Restore or retrieve the file with the most recent version of the TSM client.</p>
# 1462
DSI_Encryption_Type_Unknown=ANS1462E Unsupported encryption type
DSI_Encryption_Type_Unknown_EXPLANATION=<p>The files you are trying to restore or retrieve have been backed up or archived by a later version of the TSM client. The file encryption method is not supported by the current client.</p>
DSI_Encryption_Type_Unknown_SYSACT=<p>Object skipped.</p>
DSI_Encryption_Type_Unknown_URESP=<p>Restore or retrieve the file with the most recent version of the TSM client.</p>
# 1463
Crypto_ICC_Error=ANS1463E Unexpected error in cryptography library.\n
Crypto_ICC_Error_EXPLANATION=<p>There was an unexpected error in the cryptography library. See the error log for more information. </p>
Crypto_ICC_Error_SYSACT=<p>processing stops.</p>
Crypto_ICC_Error_URESP=<p>Check the error log for ANS1467E to determine the cause of failure. Verify you TSM client is installed properly. If needed, reinstall client and/or API. If the problem still exists, contact TSM technical support. </p>
# 1464
Crypto_ICC_Cannot_Load=ANS1464S Cannot load ICC encryption library.\n
Crypto_ICC_Cannot_Load_EXPLANATION=<p>TSM is using cryptography library which is installed automatically with the client and is being loaded at runtime. The client cannot proceed if the library is not loaded. </p>
Crypto_ICC_Cannot_Load_SYSACT=<p>Client exits.</p>
Crypto_ICC_Cannot_Load_URESP=<p>Check the error log for ANS1467E to determine the cause of failure. Verify you TSM client is installed properly. If needed, reinstall client and/or API. If the problem still exists, contact TSM technical support. </p>
# 1465
CLI_ErrorLog_Conflict=ANS1465E Conflicting options ERRORLOGMAX and ERRORLOGRETENTION were specified.\n
CLI_ErrorLog_Conflict_EXPLANATION=<p>Values were specified for both the ERRORLOGMAX and the ERRORLOGRETENTION options. These options are mutually exclusive. </p>
CLI_ErrorLog_Conflict_SYSACT=<p>Processing stops.</p>
CLI_ErrorLog_Conflict_URESP=<p>Specify a nonzero value for ERRORLOGMAX if you wish to have the TSM error log wrap when it reaches the specified maximum value. Use ERRORLOGRETENTION if you wish you have the error log limited in size on a time-based schedule. </p>
# 1466
CLI_SchedLog_Conflict=ANS1466E Conflicting options SCHEDLOGMAX and SCHEDLOGRETENTION were specified.\n
CLI_SchedLog_Conflict_EXPLANATION=<p>Values were specified for both the SCHEDLOGMAX and the SCHEDLOGRETENTION options. These options are mutually exclusive. </p>
CLI_SchedLog_Conflict_SYSACT=<p>Processing stops.</p>
CLI_SchedLog_Conflict_URESP=<p>Specify a nonzero value for SCHEDLOGMAX if you wish to have the TSM scheduler log wrap when it reaches the specified maximum value. Use SCHEDLOGRETENTION if you wish you have the scheduler log limited in size on a time-based schedule. </p>
# 1469
CLI_Client_Wrong_Key_Pass_To_Restore=ANS1469E Error processing '{0}{1}{2}'; invalid encryption key.\n
CLI_Client_Wrong_Key_Pass_To_Restore_EXPLANATION=<p>The key you entered does not match the key that was used to encrypt the file during backup. The file can not be restored unless the matching key is entered.</p>
CLI_Client_Wrong_Key_Pass_To_Restore_SYSACT=<p>processing stops.</p>
CLI_Client_Wrong_Key_Pass_To_Restore_URESP=<p> Try the restore operation again and provide the correct key.</p>
# 1473
SESS_SHM_TCPIP_Failure=ANS1473E Session rejected: TCP/IP connection failure for Shared Memory\n
SESS_SHM_TCPIP_Failure_EXPLANATION=<p> An attempt to connect to the local server using the Shared Memory protocol has failed during initial TCP/IP communications. This error can occur if the server is not listening on the correct port, or if the server is down. </p>
SESS_SHM_TCPIP_Failure_SYSACT=<p> Session rejected. Processing stopped. </p>
SESS_SHM_TCPIP_Failure_URESP=<p> Retry the operation, or wait until the server comes back up and retry the operation. If the problem continues, see your system administrator for further help. </p>
# 1474
SESS_SHM_Failure=ANS1474E An error occurred using the Shared Memory protocol\n
SESS_SHM_Failure_EXPLANATION=<p> An error has occurred while reading or writing data through the Shared Memory communications protocol. </p>
SESS_SHM_Failure_SYSACT=<p> TSM cannot complete the requested operation. </p>
SESS_SHM_Failure_URESP=<p> Check the trace log for additional information and retry the operation. If the problem continues, see your system administrator for further help. </p>
# 1475
SESS_SHM_Not_Auth=ANS1475E Insufficient authority to connect to the shared memory region\n
SESS_SHM_Not_Auth_EXPLANATION=<p> The user issuing the command does not have authority to connect to the shared memory segment. When the shared memory segment is created by the server, it will be owned by the effective uid of the server process (dsmserv). Only processes running under this uid or root will be allowed to connect to the segment (and thus to the server). </p>
SESS_SHM_Not_Auth_SYSACT=<p> The session is rejected and processing stops. </p>
SESS_SHM_Not_Auth_URESP=<p> Run the command under the uid of the processing running dsmserv, if possible. Otherwise contact your system administrator for further help. </p>
# 1485
DSI_Restoring_VMP_To_Non_Empty_Dir=Volume mount point was not restored because the target directory is not empty.\n
# 1499
CLI_Abort_Toc_Creation_Fail=ANS1499E Creation of table of contents failed.\n
CLI_Abort_Toc_Creation_Fail_EXPLANATION=<p>A failure occurred on the server during creation of the table of contents. </p>
CLI_Abort_Toc_Creation_Fail_SYSACT=<p>The table of contents was not created.</p>
CLI_Abort_Toc_Creation_Fail_URESP=<p>This abort code indicates there was a problem creating a table of contents on the server. The sysadmin will need to consult the activity log on the server to determine the cause.</p>
# 1500
COM_TCA_Not_Found=ANS1500E Module dsmtca not found in secure directory.\n
COM_TCA_Not_Found_EXPLANATION=<p> TSM cannot find the Trusted Communication Agent module (dsmtca) in the appropriate directory. </p>
COM_TCA_Not_Found_SYSACT=<p> TSM ends. </p>
COM_TCA_Not_Found_URESP=<p> Log on as root user, then create a link to dsmtca module in /usr/bin with the command: ln -s /usr/tivoli/tsm/client/ba/bin/dsmtca /usr/bin/dsmtca </p>
# 1501
COM_TCA_Not_Valid=ANS1501E Trusted agent execution/owner permissions are invalid\n
COM_TCA_Not_Valid_EXPLANATION=<p> The Trusted Communication Agent execution/owner permissions are invalid. </p>
COM_TCA_Not_Valid_SYSACT=<p> TSM ends. </p>
COM_TCA_Not_Valid_URESP=<p> Have your system administrator check the installation instructions for the client to ensure that the Trusted Communication Agent permissions are set correctly. This error can be caused by installing TSM as a non-root user. For the UNIX platforms that have the installation program (dsm.install), you must run dsm.install while logged in as the root user. </p>
# 1502
COM_TCA_Access_Denied=ANS1502E Access to system function required to run has been denied\n
COM_TCA_Access_Denied_EXPLANATION=<p> The permissions of the Trusted Communication Agent do not allow it to be accessed by the user of the TSM client. </p>
COM_TCA_Access_Denied_SYSACT=<p> TSM ends. </p>
COM_TCA_Access_Denied_URESP=<p> See your system administrator. </p>
# 1504
COM_TCA_Fork_Failed=ANS1504E Error starting the Trusted Communication Agent process.\n
COM_TCA_Fork_Failed_EXPLANATION=<p> An error has occurred starting the Trusted Communication Agent process; specifically, the fork() function has failed. </p>
COM_TCA_Fork_Failed_SYSACT=<p> TSM ends. </p>
COM_TCA_Fork_Failed_URESP=<p> Probable system error. If the problem persists, restart the workstation. </p>
# 1506
COM_TCA_Invalid_Request=ANS1506E The TSM Trusted Communication Agent received an invalid request.\n
COM_TCA_Invalid_Request_EXPLANATION=<p> The Trusted Communication Agent is invoked by the TSM client and has received an unknown request argument in the call. </p>
COM_TCA_Invalid_Request_SYSACT=<p> TSM ends. </p>
COM_TCA_Invalid_Request_URESP=<p>It is possible the Trusted Communication Agent was mistakenly invoked by a process other than the TSM client. If that is not the case, then this is an internal error. If the problem recurs, contact your IBM service representative. </p>
# 1507
COM_Not_Adsm_Admin=ANS1507E This action requires TSM administrative authority on this system.\n
COM_Not_Adsm_Admin_EXPLANATION=<p> An activity has been attempted that must be performed by the TSM administrator (for example, open registration, filespace delete or password update). </p>
COM_Not_Adsm_Admin_SYSACT=<p> TSM ends. </p>
COM_Not_Adsm_Admin_URESP=<p> If the activity is required, the administrator for this system must perform it. </p>
# 1508
COM_TCA_SemGet_Error=ANS1508E Error allocating semaphores.\n
COM_TCA_SemGet_Error_EXPLANATION=<p>An error has occurred because the semaphores you are attempting to allocate have become insufficient.</p>
COM_TCA_SemGet_Error_SYSACT=<p>Processing ends.</p>
COM_TCA_SemGet_Error_URESP=<p>Ask your system administrator for assistance, and possibly increase the number of semaphores in your system. </p>
# 1509
COM_TCA_Sem_Operation_Error=ANS1509E Error setting semaphore value or waiting on semaphore.\n
COM_TCA_Sem_Operation_Error_EXPLANATION=<p> An error has occurred while attempting to set or wait on a semaphore. </p>
COM_TCA_Sem_Operation_Error_SYSACT=<p> Processing ends. </p>
COM_TCA_Sem_Operation_Error_URESP=<p> Probable system error. If the problem persists, restart the workstation. </p>
# 1514
DSI_ENCRYPTION_NOTMATCH=ANS1514W Encryption key passwords are not the same.
DSI_ENCRYPTION_NOTMATCH_EXPLANATION=<p>The key passwords are different.</p>
DSI_ENCRYPTION_NOTMATCH_SYSACT=<p>TSM allows you to try again.</p>
DSI_ENCRYPTION_NOTMATCH_URESP=<p>Enter the correct password.</p>
# 1515
CLI_Abort_Toc_Load_Fail=ANS1515E Loading a table of contents failed.\n
CLI_Abort_Toc_Load_Fail_EXPLANATION=<p>A failure occurred on the server during loading of the table of contents. </p>
CLI_Abort_Toc_Load_Fail_SYSACT=<p>The table of contents was not loaded.</p>
CLI_Abort_Toc_Load_Fail_URESP=<p>This abort code indicates there was a problem loading a table of contents on the server. The sysadmin will need to consult the activity log on the server to determine the cause.</p>
# 1522
DSI_SM_ERROR_AGENT_VERSION=ANS1522E It is not possible to authenticate with the client node {0} ! \n\nThe Space Management Agent version {1} running on {2} \ndoes not match with the Space Management Console \nversion {3} you are running ! 
DSI_SM_ERROR_AGENT_VERSION_EXPLANATION=<p>The version of the Space Management Console does not match with the version of the Space Management Agent running on the client node machine. To avoid incompatibleness it is necessary to run the console and the agent with the same version. </p>
DSI_SM_ERROR_AGENT_VERSION_SYSACT=<p>The Space Management Console exits.</p>
DSI_SM_ERROR_AGENT_VERSION_URESP=<p>Use Space Management Console with the same version like the Space Management Agent running on the HSM node you want to manage.</p>
# 1524
CLI_Query_Journal=Querying Journal for '{0}'\n
# 1525
CLI_JBB_InProgress=Another Journal Based Backup is currently in progress for '{0}'\n
# 1526
CLI_JBB_WaitToComplete=Waiting for other Journal Based Backup to complete\n
# 1527
CLI_Process_Journal=Processing {0} Journal entries for '{1}'\n
# 1531
DSI_BackDelChoice_All=Delete All Objects
# 1532
Proxy_Reject_Id_Not_Authorized=ANS1532E Proxy Rejected: Proxy authority has not been granted to this node.
Proxy_Reject_Id_Not_Authorized_EXPLANATION=<p> The node has not been granted proxy authority to access the node named by the ASNODENAME option. The TSM administrator must first grant proxy authority. </p>
Proxy_Reject_Id_Not_Authorized_SYSACT=<p> The TSM operation ends. </p>
Proxy_Reject_Id_Not_Authorized_URESP=<p> The TSM server administrator must grant proxy authority for this node. See the administrator command "Grant Proxynode". </p>
# 1533
Proxy_Reject_Id_In_Use=ANS1533E Proxy Rejected: The node name you specified in the ASNODENAME option is locked.
Proxy_Reject_Id_In_Use_EXPLANATION=<p> The TSM administrator has locked the node you specified as the ASNODENAME option. </p>
Proxy_Reject_Id_In_Use_SYSACT=<p> The TSM operation ends. </p>
Proxy_Reject_Id_In_Use_URESP=<p> The TSM server administrator must unlock the node before you can access it. Try the operation later, or check with your TSM administrator. </p>
# 1534
Proxy_Reject_No_Resources=ANS1534E Proxy Rejected: The TSM server has run out of memory.
Proxy_Reject_No_Resources_EXPLANATION=<p> There is not enough memory available to allow this operation to continue. </p>
Proxy_Reject_No_Resources_SYSACT=<p> TSM canceled the current operation. </p>
Proxy_Reject_No_Resources_URESP=<p> Try the operation again. If the problem continues, see your system administrator to increase the amount of memory of the server. </p>
# 1535
Proxy_Reject_Duplicate_Id=ANS1535E Proxy Rejected: ASNODENAME and NODENAME are identical.
Proxy_Reject_Duplicate_Id_EXPLANATION=<p> TSM does not allow the ASNODENAME and NODENAME option values to be the same. </p>
Proxy_Reject_Duplicate_Id_SYSACT=<p> TSM canceled the current operation. </p>
Proxy_Reject_Duplicate_Id_URESP=<p> Use the ASNODENAME option only to access another node. It is not necessary to set ASNODENAME option to access your own node. Remove ASNODENAME from your option file unless you are actually trying to access a node that you have been granted authority to access with the administrative command "Grant Proxynode". </p>
# 1536
Proxy_Reject_Internal_Error=ANS1536E Proxy Rejected: The server has an internal error.
Proxy_Reject_Internal_Error_EXPLANATION=<p> The client cannot proxy to the node named by the ASNODENAME option because of an internal server error. </p>
Proxy_Reject_Internal_Error_SYSACT=<p> TSM canceled the current operation. </p>
Proxy_Reject_Internal_Error_URESP=<p> See your system administrator immediately. </p>
# 1537
Asnode_Invalid_Option=ANS1537E The ASNODENAME option is not valid with the FROMNODE option.\n
Asnode_Invalid_Option_EXPLANATION=<p>None. </p>
Asnode_Invalid_Option_SYSACT=<p>Processing stops. </p>
Asnode_Invalid_Option_URESP=<p>Remove the ASNODENAME option from the options file or do not use the FROMNODE option. </p>
# 1538
Asnode_Invalid_Function=ANS1538E The operation that is being attempted cannot be invoked using the ASNODENAME option.
Asnode_Invalid_Function_EXPLANATION=<p>None. </p>
Asnode_Invalid_Function_SYSACT=<p>Processing stops. </p>
Asnode_Invalid_Function_URESP=<p>Remove the ASNODENAME option and retry the operation. </p>
# 1539
Asnode_Cluster_Invalid_Option=ANS1539E The ASNODENAME option cannot be used with the CLUSTERNODE option.
Asnode_Cluster_Invalid_Option_EXPLANATION=<p>None. </p>
Asnode_Cluster_Invalid_Option_SYSACT=<p>Processing stops. </p>
Asnode_Cluster_Invalid_Option_URESP=<p>Remove the ASNODENAME option and retry the operation. </p>
# 1540
SnapDiff_Filer_Not_Supported=ANS1540E Incremental backups using snapshot difference is not supported on this version of the NetApp file server. \n
SnapDiff_Filer_Not_Supported_EXPLANATION=<p> Incremental backup using Snapshot difference requires Data ONTAP V7.3 or later. To back up unicode file names, upgrade to Data ONTAP V7.3.3 or later or V8.1 or later. </p>
SnapDiff_Filer_Not_Supported_SYSACT=<p> Processing stops. </p>
SnapDiff_Filer_Not_Supported_URESP=<p> Upgrade the file server to a supported level of Data ONTAP, then retry the operation. </p>
# 1544
Was_FS_BADERROR=ANS1544E An error in WAS processing has occurred.\n
Was_FS_BADERROR_EXPLANATION=<p>None.</p>
Was_FS_BADERROR_SYSACT=<p> None </p>
Was_FS_BADERROR_URESP=<p> Run the following command to see the nodes that can be backed up: \ndsmc query was -wastype=local \nMake sure the results are correct for your environment, then try the operation again. If the problem persists, contact TSM technical support for further assistance. </p>
# 1545
Was_FINISHED=WAS Processing has successfully completed.\n
# 1546
Was_LOCK_FAILED=ANS1546W TSM failed to lock the WebSphere configuration repository.
Was_LOCK_FAILED_EXPLANATION=<p>None.</p>
Was_LOCK_FAILED_SYSACT=<p>The lock of the WebSphere configuration repository fails.</p>
Was_LOCK_FAILED_URESP=<p>Ensure that the WebSphere server is running. If the server is already running, ensure that the repository is unlocked. Ensure that you are backing up the correct node. To see a list of available nodes that can be backed up, enter: 'dsmc q was -wastype=local'.</p>
# 1547
Was_UNLOCK_FAILED=ANS1547W TSM failed to unlock the WebSphere Configuration Repository.
Was_UNLOCK_FAILED_EXPLANATION=<p>None.</p>
Was_UNLOCK_FAILED_SYSACT=<p>The unlock of the WebSphere Configuration Repository fails.</p>
Was_UNLOCK_FAILED_URESP=<p>Make sure that the WebSphere server is running. If the repository is locked, then unlock it and try the operation again. Ensure that the correct node is being backed up. To see a list of available nodes that can be backed up, run: 'dsmc q was -wastype=local'.</p>
# 1548
Was_NOT_INSTALLED=ANS1548E A supported version of WebSphere is not installed on this machine.\n
Was_NOT_INSTALLED_EXPLANATION=<p> A supported version of WebSphere is not installed on this machine. The only version of WebSphere that is supported is 5.0.x. </p>
Was_NOT_INSTALLED_SYSACT=<p> None </p>
Was_NOT_INSTALLED_URESP=<p> Install WebSphere 5.0 on the machine. </p>
# 1549
DSI_NOAPPINST=ANS1549E No application server instances were found. Unable to perform backup.
DSI_NOAPPINST_EXPLANATION=<p> The application server is not installed on this machine. </p>
DSI_NOAPPINST_SYSACT=<p> Backup is not performed. </p>
DSI_NOAPPINST_URESP=<p> Install the application server. </p>
# 1550
DSI_NONDINST=ANS1550E No network deployment manager instances were found to back up.
DSI_NONDINST_EXPLANATION=<p> Deployment manager is not installed on this machine. </p>
DSI_NONDINST_SYSACT=<p> Back up is not performed. </p>
DSI_NONDINST_URESP=<p> Install the network deployment manager. </p>
# 1552
Was_NO_SECURITY_PROPS=ANS1552W A user name and a password have not been provided to Data Protection for WebSphere.\n
Was_NO_SECURITY_PROPS_EXPLANATION=<p>The dsmc set WASPassword command has not been run to provide the user name and the password for Data Protection for WebSphere. Data Protection for WebSphere needs the user name and password to be able to run when WebSphere security is turned on.</p>
Was_NO_SECURITY_PROPS_SYSACT=<p>Data Protection for WebSphere cannot run.</p>
Was_NO_SECURITY_PROPS_URESP=<p>Run the dsmc set WASPassword command to set the WebSphere security user name and password.</p>
# 1553
Was_INVALID_SECURITY_PROPS=ANS1553W The user name and password that have been provided to Data Protection for WebSphere are invalid.\n
Was_INVALID_SECURITY_PROPS_EXPLANATION=<p>None.</p>
Was_INVALID_SECURITY_PROPS_SYSACT=<p>Data Protection for WebSphere cannot run.</p>
Was_INVALID_SECURITY_PROPS_URESP=<p>Run the dsmc set WASPassword command to set the WebSphere security user name and password.</p>
# 1555
Was_NO_PASSWORD_FUNC=ANS1555E The WebSphere Application Server (WAS) plug-in level must be at 5.2.1 or greater to set the WebSphere user and password.\n
Was_NO_PASSWORD_FUNC_EXPLANATION=<p>You must have the backup-archive client and the WAS plug-in at a level of 5.2.1 or higher to be able to connect to WebSphere when security is enabled.</p>
Was_NO_PASSWORD_FUNC_SYSACT=<p>WebSphere does not set the user and password.</p>
Was_NO_PASSWORD_FUNC_URESP=<p>Upgrade the WAS plug-in to 5.2.1 or greater.</p>
# 1556
Was_SET_PWD_FAILED=ANS1556E Setting the WAS user and password failed.\n
Was_SET_PWD_FAILED_EXPLANATION=<p>Password validation for the WAS user and password failed.</p>
Was_SET_PWD_FAILED_SYSACT=<p>WAS password validation fails.</p>
Was_SET_PWD_FAILED_URESP=<p>Rerun the set WASPassword command with the correct values for user and password.</p>
# 1557
Was_PWD_NOT_VALIDATED=ANS1557W The WAS Server was not running, and the password file was saved without validation.\n
Was_PWD_NOT_VALIDATED_EXPLANATION=<p>If the WAS server is down, then it is not possible to connect to the server and validate the user-entered password. The password has still been saved, but no validation has been performed. </p>
Was_PWD_NOT_VALIDATED_SYSACT=<p>The set WAS password command did not validate the password. The password has still been saved, but no validation has been performed. The password may be incorrect. </p>
Was_PWD_NOT_VALIDATED_URESP=<p>There are two options: <ul> <li>Try a backup. If the backup performs a failover, and there is a incorrect password message in the error log, then the password that was entered is incorrect. </li> <li>Start the WAS server and rerun the set password command. Since the server is now up, validation will be performed as normal and the user notified if a good/bad password was entered. </li></ul></p>
# 1559
Was_SET_PASSWORD_OK=Set WAS password completed successfully.\n
# 1560
Was_SERVER_DOWN=ANS1560W The WebSphere server is not running.\n
Was_SERVER_DOWN_EXPLANATION=<p>The WebSphere server is not running. The WAS server is running for backup operations. </p>
Was_SERVER_DOWN_SYSACT=<p>The WebSphere server is not running.</p>
Was_SERVER_DOWN_URESP=<p>Start the WAS server and run the backup again.</p>
# 1561
Was_LOADING_JRE=Loading the Java Runtime Environment, please wait.\n
# 1562
Was_EAR_EXPANSION_FAILED=ANS1562E WAS Restore failed during EAR Expansion.\n
Was_EAR_EXPANSION_FAILED_EXPLANATION=<p>EAR Expansion is performed for a WebSphere Application server after the files have been restored.</p>
Was_EAR_EXPANSION_FAILED_SYSACT=<p>WAS restore fails.</p>
Was_EAR_EXPANSION_FAILED_URESP=<p>Run the restore again.</p>
# 1563
Was_NO_PROP_FILE=ANS1563W The itsm.was.properties file does not exist.\n
Was_NO_PROP_FILE_EXPLANATION=<p>The itsm.was.properties file is used to store the WebSphere security user name and password.</p>
Was_NO_PROP_FILE_SYSACT=<p>None.</p>
Was_NO_PROP_FILE_URESP=<p>Run the dsmc set waspassword command to create this file.</p>
# 1564
Was_WAIT_FOR_EAR=Running the WebSphere EAR expansion, please wait.\n
# 1565
Was_NO_EAR_EXPANDER=ANS1565E No WebSphere EARExpander was found. Copy the EARExpander tool from the base WebSphere bin directory to the instance bin directory, then run the restore operation again.\n
Was_NO_EAR_EXPANDER_EXPLANATION=<p>The EAR files are expanded for an instance of an Application server and the EARExpander tool does not exist in the instance bin directory.</p>
Was_NO_EAR_EXPANDER_SYSACT=<p>No WebSphere EARExpander found.</p>
Was_NO_EAR_EXPANDER_URESP=<p>Copy the WAS EARExpander tool from the base install's bin directory to the bin directory of the instance. Then run the WAS restore operation again, after the EARExpander tool has been copied.</p>
# 1566
Was_REST_VER_MISMATCH=ANS1566E The version of WebSphere on the machine does not match the version of WebSphere that was backed up. These versions must match for a WAS restore operation.\n
Was_REST_VER_MISMATCH_EXPLANATION=<p>The version of WebSphere on the machine does not match the version of WebSphere that was backed up. These versions must match for a WAS restore operation.</p>
Was_REST_VER_MISMATCH_SYSACT=<p>The WAS restore operation fails.</p>
Was_REST_VER_MISMATCH_URESP=<p>Install the correct version of WebSphere on the machine before performing the restore operation.</p>
# 1567
Was_NO_VER_CHECK=ANS1567I A 5.2.2 or higher client is restoring data backed up from a 5.2.0 client. No version check can be performed before the restore.\n
# 1574
CLI_JOURNAL_QUERY_ERROR=ANS1574E Journal Query Failed.\n
CLI_JOURNAL_QUERY_ERROR_EXPLANATION=<p>The journal daemon was unable to process the requested journal query. </p>
CLI_JOURNAL_QUERY_ERROR_SYSACT=<p>Journal backup processing is interrupted.</p>
CLI_JOURNAL_QUERY_ERROR_URESP=<p>Retry the backup, check the journal daemon errorlog for the cause of the failure. Backup of other file systems in the domain will continue. </p>
# 1575
CLI_JOURNAL_COMM_ERROR=ANS1575E Journal Daemon Communications Error.\n
CLI_JOURNAL_COMM_ERROR_EXPLANATION=<p>An error occurred communicating with the journal daemon. </p>
CLI_JOURNAL_COMM_ERROR_SYSACT=<p>Journal backup processing is interrupted.</p>
CLI_JOURNAL_COMM_ERROR_URESP=<p>Retry the backup, check the journal daemon and client errorlogs for the cause of the failure. </p>
# 1576
DSI_SM_WARNING_AGENT_VERSION=ANS1576W Space Management Agent version mismatch. \n\nThe Space Management Agent (hsmagent) version {0} \nrunning on '{1}' client node does not match with the \nSpace Management Console (GUI) version {2} you are running! \n\nTo avoid compatibility problems, please use the same version for the \nSpace Management Console and the Space Management Agent. \n\nDo you want to proceed?\n
DSI_SM_WARNING_AGENT_VERSION_EXPLANATION=<p>The version of the Space Management Console does not match with the version of the Space Management Agent running on the client node machine. To avoid compatibility problems, please use the same version for the Space Management Console (GUI) and the Space Management Agent (hsmagent).</p>
DSI_SM_WARNING_AGENT_VERSION_SYSACT=<p>Prompt the user to exit or continue.</p>
DSI_SM_WARNING_AGENT_VERSION_URESP=<p>Use Space Management Console (GUI) with the same version like the Space Management Agent (hsmagent) running on the HSM node you want to manage.</p>
# 1578
CLI_Special_FS=ANS1578E The specified path '{0}' is not valid for backup or archive. \n
CLI_Special_FS_EXPLANATION=<p> The specified path is a special file system or part of a special file system. Special file systems contain dynamic information generated by the operating system and should not be backed up or archived. Refer to the TSM client manual for a complete list of special file systems for your operating system. </p>
CLI_Special_FS_SYSACT=<p> Processing continues if there are other file systems to back up. </p>
CLI_Special_FS_URESP=<p> Do not specify special file systems for backup or archive. </p>
# 1580
DSI_PREFP_DUPLICATEFS_REPLACE=ANS1580W An Include.Fs statement with performance algorithm set already exists for the drive specified. Do you want to replace the statement?
DSI_PREFP_DUPLICATEFS_REPLACE_EXPLANATION=<p> The user tried to create a duplicate Include.Fs entry on a drive that already has a performance algorithm associated with it. This is applicable to the Preference Editor on the MFC GUI </p>
DSI_PREFP_DUPLICATEFS_REPLACE_SYSACT=<p> The user can replace the statement with the new one or they can cancel out of this operation </p>
DSI_PREFP_DUPLICATEFS_REPLACE_URESP=<p> The user is prompted to replace the statement with the new one or they can say No to cancel out of this operation. </p>
# 1582
DSI_PREFEP_SELECTFS=Filespace List
# 1585
DSI_DPREFP_FSALGO_LABEL=Select a filespace and algorithm
# 1586
DSI_DPREFP_SELECTFS_GROUP=Select Filesystem
# 1591
DSJ_OBJINFO_NAMESPACE_LONGUTF8=Long UTF-8
# 1592
SSL_Initialization_Failure=ANS1592E Failed to initialize SSL protocol.\n
SSL_Initialization_Failure_EXPLANATION=<p>TSM was unable to initialize SSL protocol.</p>
SSL_Initialization_Failure_SYSACT=<p>Processing stopped</p>
SSL_Initialization_Failure_URESP=<p>Check for GSKit related messages in the error log. Make sure you have configured the key database for SSL communication as described in the documentation. If the problem persists, contact TSM customer support.</p>
# 1593
SSL_Keyfile_Open_Failed=ANS1593E Cannot open the key database.\n
SSL_Keyfile_Open_Failed_EXPLANATION=<p>TSM was unable to open the keyfile that is expected to contain the server certificate for SSL communications.</p>
SSL_Keyfile_Open_Failed_SYSACT=<p>Processing stopped</p>
SSL_Keyfile_Open_Failed_URESP=<p>Make sure you have configured the key database for SSL communication as described in the documentation. If the problem persists, contact TSM customer support.</p>
# 1594
SSL_Keyfile_Bad_Password=ANS1594E Wrong key database password.\n
SSL_Keyfile_Bad_Password_EXPLANATION=<p>The key database that contains the server certificate has been set up with the wrong password.</p>
SSL_Keyfile_Bad_Password_SYSACT=<p>Processing stopped</p>
SSL_Keyfile_Bad_Password_URESP=<p>Make sure you have configured the key database for SSL communication as described in the documentation.</p>
# 1595
SSL_Bad_Certificate=ANS1595E Bad server certificate.\n
SSL_Bad_Certificate_EXPLANATION=<p>TSM was unable to open SSL connection to server because of a bad certificate. This error usually occurs when the server certificate cannot be verified by the client.</p>
SSL_Bad_Certificate_SYSACT=<p>Processing stopped</p>
SSL_Bad_Certificate_URESP=<p>Make sure you have configured the key database for SSL communication as described in the documentation. Make sure to import the correct certificate from the TSM server you are trying to connect to.</p>
# 1596
SSL_Not_Supported=ANS1596E SSL protocol is not supported.\n
SSL_Not_Supported_EXPLANATION=<p>SSL protocol is not supported on this platform.</p>
SSL_Not_Supported_SYSACT=<p>Processing stopped</p>
SSL_Not_Supported_URESP=<p>Refer to TSM documentation for the list of supported platforms.</p>
# 1599
SSL_Cannot_Load_Library=ANS1599E Cannot load SSL runtime library.\n
SSL_Cannot_Load_Library_EXPLANATION=<p>TSM failed to dynamically load SSL runtime library necessary for SSL protocol</p>
SSL_Cannot_Load_Library_SYSACT=<p>Processing stopped</p>
SSL_Cannot_Load_Library_URESP=<p>Make sure TSM client is properly installed. Try to reinstall the client software. If the problem persists, contact TSM customer support.</p>
# 1600
Dom_Unable_to_load_library=ANS1600E Unable to load the Data Protection for Lotus Domino library.\n
Dom_Unable_to_load_library_EXPLANATION=<p>The Datt Protection for Lotus Domino library could not be loaded.</p>
Dom_Unable_to_load_library_SYSACT=<p>Processing ends.</p>
Dom_Unable_to_load_library_URESP=<p>Ensure that Domino plugin is properly configured and check the error log on the client machine for more information.</p>
# 1601
Dom_PI_internal_error=ANS1601E The Domino plugin operation failed because of an internal error.\n
Dom_PI_internal_error_EXPLANATION=<p>A Domino plugin internal error has occurred.</p>
Dom_PI_internal_error_SYSACT=<p>Processing ends.</p>
Dom_PI_internal_error_URESP=<p>Check the error log on the client machine for more information.</p>
# 1602
Dom_Cfg_File_not_found=ANS1602E The Domino plugin operation failed because the preferences file was not found.\n
Dom_Cfg_File_not_found_EXPLANATION=<p>The Data Protection for Lotus Domino preference file could not be found.</p>
Dom_Cfg_File_not_found_SYSACT=<p>Processing ends.</p>
Dom_Cfg_File_not_found_URESP=<p>The Data Protection for Lotus for Domino configuration file (default name domdsm.cfg) could not be found. Check the error log on the client machine for more information.</p>
# 1603
Dom_TCP_error=ANS1603E The Domino plugin operation failed because of an internal TCP/IP error.\n
Dom_TCP_error_EXPLANATION=<p>A TCP/IP error has occurred.</p>
Dom_TCP_error_SYSACT=<p>Processing ends.</p>
Dom_TCP_error_URESP=<p>Check the error log on the client machine for more information.</p>
# 1604
Dom_Fork_error=ANS1604E The Domino plugin operation failed trying to start the dsmdomp address space.\n
Dom_Fork_error_EXPLANATION=<p> The dsmdomp address space could not be started. This is probably an installation error. </p>
Dom_Fork_error_SYSACT=<p>Processing ends.</p>
Dom_Fork_error_URESP=<p>Ensure that the lotus/bin directory has a symbolic link to the tools directory for dsmdomp and the lotus/notes directory has a symbolic link to the dsmdomp executable. If the problem persists, contact your System Administrator for further assistance.</p>
# 1605
Dom_Child_error=ANS1605E The Domino plugin operation failed while initializing communications with the dsmdomp address space.\n
Dom_Child_error_EXPLANATION=<p>The Domino plugin communication initialization failed.</p>
Dom_Child_error_SYSACT=<p>Processing ends.</p>
Dom_Child_error_URESP=<p>The dsmdomp address space failed during its initialization. This is likely to be an installation error. Ensure that the lotus/bin directory has a symbolic link to the tools directory for dsmdomp and the lotus/notes directory has a symbolic link to the dsmdomp executable. If the problem persists, contact your System Administrator for further assistance.</p>
# 1606
Dom_Child_startup_error=ANS1606E The Domino plugin operation failed while starting up the dsmdomp address space.\n
Dom_Child_startup_error_EXPLANATION=<p>The dsmdomp address space could not be started.</p>
Dom_Child_startup_error_SYSACT=<p>The TDP for Domino processing stops.</p>
Dom_Child_startup_error_URESP=<p>The dsmdomp address space failed during its initialization. This is likely to be an installation error. Ensure that the lotus/bin directory has a symbolic link to the tools directory for dsmdomp and the lotus/notes directory has a symbolic link to the dsmdomp executable. Examine the file /tmp/dsmdomp* for more information. If the problem persists, contact your System Administrator for further assistance.</p>
# 1607
PI_NotSupported=ANS1607E A plugin found in the plugins library is not supported by the current level of the TSM client.\n
PI_NotSupported_EXPLANATION=<p>The plugin is not loaded, and processing continues.</p>
PI_NotSupported_SYSACT=<p>The plugin is not loaded, and processing continues.</p>
PI_NotSupported_URESP=<p>This probably is an installation error. Ensure that the plugins directory contains valid plugin libraries, and that the correct level of the TSM client has been installed. If the problem persists, contact your System Administrator for further assistance.</p>
# 1611
PI_InternalError=ANS1611E A plugin operation failed because of an internal error.\n
PI_InternalError_EXPLANATION=<p>A plugin internal error has occurred.</p>
PI_InternalError_SYSACT=<p>The plugin operation stops.</p>
PI_InternalError_URESP=<p>If the error persists, run with tracing enabled and contact your System Administrator and IBM for further assistance.</p>
# 1612
Dom_ADSM_API_Error=ANS1612E The Domino plugin operation failed because of a TSM API error.\n
Dom_ADSM_API_Error_EXPLANATION=<p>An TSM API error occurred .</p>
Dom_ADSM_API_Error_SYSACT=<p>Processing ends.</p>
Dom_ADSM_API_Error_URESP=<p>Check error log on the client machine for more information.</p>
# 1613
Dom_Could_Not_Load_ADSM_DLL=ANS1613E >Could not load the TSM API.\n
Dom_Could_Not_Load_ADSM_DLL_EXPLANATION=<p>The TSM API could not be loaded.</p>
Dom_Could_Not_Load_ADSM_DLL_SYSACT=<p>Processing ends.</p>
Dom_Could_Not_Load_ADSM_DLL_URESP=<p>Check error log on the client machine for more information.</p>
# 1614
Dom_Almgr_Trial_Expired=ANS1614E The Domino plugin 'Try and Buy' license has expired.\n
Dom_Almgr_Trial_Expired_EXPLANATION=<p>The 'Try and Buy' license that was detected has expired.</p>
Dom_Almgr_Trial_Expired_SYSACT=<p>Processing ends.</p>
Dom_Almgr_Trial_Expired_URESP=<p>This product is no longer valid for use. A valid license must be obtained before running the product.</p>
# 1615
Dom_License_Error=ANS1615E The Domino plugin operation failed due to a license error.\n
Dom_License_Error_EXPLANATION=<p>Domino plugin license verification failed.</p>
Dom_License_Error_SYSACT=<p>Processing ends.</p>
Dom_License_Error_URESP=<p>Check the error log for further information.</p>
# 1616
Dom_Could_Not_Load_Notes_DLL=ANS1616E The Domino plugin operation failed because the Lotus Domino API could not be loaded.\n
Dom_Could_Not_Load_Notes_DLL_EXPLANATION=<p>The Lotus Domino API could not be loaded.</p>
Dom_Could_Not_Load_Notes_DLL_SYSACT=<p>Processing ends.</p>
Dom_Could_Not_Load_Notes_DLL_URESP=<p>Ensure the Lotus Domino Server is installed correctly.</p>
# 1617
Dom_TDP_API_Error=ANS1617E The Domino plugin operation failed because of a Data Protection for Domino API error.\n
Dom_TDP_API_Error_EXPLANATION=<p>A Data Protection for Domino API error occurred during a Domino plugin operation.</p> 
Dom_TDP_API_Error_SYSACT=<p>Processing ends.</p> 
Dom_TDP_API_Error_URESP=<p>For more details, view the following Tivoli Storage Manager error logs.</p> <p> The API error log (dsierror.log) and the log of Data Protection for Domino activity (domdsm.log). The default location of these logs is the Data Protection for Domino installation directory. </p> <p> The backup-archive client error log (dsmerror.log), the web client error log (dsmwebcl.log), and the log of scheduler activite (dsmsched.log). The default location of these logs is the backup-archive installation directory. </p> 
# 1618
Dom_Operation_In_Progress=ANS1618E A Domino plugin operation is already in progress. Please wait for operation to complete.\n
Dom_Operation_In_Progress_EXPLANATION=<p>A Domino plugin operation is in progress.</p>
Dom_Operation_In_Progress_SYSACT=<p>The Domino plugin operation stops.</p>
Dom_Operation_In_Progress_URESP=<p>Please wait for the Domino plugin operation to complete before starting a new Domino plugin operation.</p>
# 1619
Dom_Low_Struct_Level=ANS1619E The IBM Tivoli Storage Manager application client cannot work with the version of the Domino plugin you have installed.\n
Dom_Low_Struct_Level_EXPLANATION=<p>The version of the Domino plugin currently installed on the system is older than the version used to build the IBM Tivoli Storage Manager application client.</p>
Dom_Low_Struct_Level_SYSACT=<p>Processing ends.</p>
Dom_Low_Struct_Level_URESP=<p>Install a version of the Domino plugin at or later than the level of the IBM Tivoli Storage Manager application client.</p>
# 1623
Dom_NSFDB2_Skipped=ANS1623W Backup of NSF DB2 database was skipped. NSF DB2 databases not supported.\n
Dom_NSFDB2_Skipped_EXPLANATION=<p> This version of DP for Domino plugin does not support NSF DB2 databases.</p>
Dom_NSFDB2_Skipped_SYSACT=<p>Backup of NSF DB2 databases is skipped.</p>
Dom_NSFDB2_Skipped_URESP=<p>Exclude NSF DB2 databases from backup.</p>
# 1649
CLI_InconsistentOptions=ANS1649E The option '{0}' is inconsistent with the option '{1}'.\n
CLI_InconsistentOptions_EXPLANATION=<p> The command failed because the specified option (<mv>specified-option</mv>) can not be specified in combination with the option (<mv>other-option</mv>), which is also specified. </p>
CLI_InconsistentOptions_SYSACT=<p>The command is terminated.</p>
CLI_InconsistentOptions_URESP=<p> Run the command without the specified option. Alternatively, run the command without the other option. </p>
# 1662
SESS_Proxy_Nodes_Info=ANS1662I Agent Node: '{0}' Target Node: '{1}'
# 1668
CLI_NOT_LOCAL_CLUSTER_Disk=ANS1668E The '{0}' is not a local disk.\n
CLI_NOT_LOCAL_CLUSTER_Disk_EXPLANATION=<p> The specified file system is network disk or network share. Because the CLUSTERNODE option is set to YES, the file system cannot be backed up or archived. </p>
CLI_NOT_LOCAL_CLUSTER_Disk_SYSACT=<p>Processing stops.</p>
CLI_NOT_LOCAL_CLUSTER_Disk_URESP=<p> If the CLUSTERNODE option is incorrectly set to YES, then change the option to NO and try the operation again. Otherwise see the client manual for further information about configuring the TSM client to run in a cluster environment. </p>
# 1671
CLI_Cluster_Restarting_All_Nodes=ANS1671I The cluster database has been restored. Restarting the cluster services on all nodes. This will take a few minutes.\n
# 1672
CLI_Cluster_Take_Resource_Offline_Failed=ANS1672I Could not take the cluster resource {0} offline. MS rc {1}. Error is ignored.\n
# 1673
CLI_Cluster_Start_Service_Failed=ANS1673W Cluster service on node {0} could not be started. You must manually start the service.\n
CLI_Cluster_Start_Service_Failed_EXPLANATION=<p> The cluster database has been restored. During the restore, the cluster service was taken offline. Tivoli Storage Manager failed to restart the cluster service. </p>
CLI_Cluster_Start_Service_Failed_SYSACT=<p>Processing continues.</p>
CLI_Cluster_Start_Service_Failed_URESP=<p> You can manually start the service for this node. </p>
# 1674
CLI_Cluster_Restart_Services_Manually=ANS1674I The cluster database has been restored but the cluster service on some nodes could not be started. Use the Failover Cluster Management tool to manually start the nodes.\n
# 1675
CLI_Cluster_Services_Must_Start_Manually=ANS1675W Unable to obtain a list of cluster nodes to restart after the cluster database is restored. The call '{0}' returned with MS rc {1}. You must restart the cluster service on all the nodes after the restore is finished.\n
CLI_Cluster_Services_Must_Start_Manually_EXPLANATION=<p> Due to an error, Tivoli Storage Manager could not retrieve a list of nodes in the cluster to restart. The cluster services on these nodes need to be started manually. The client error log might contain additional information depending on where the failure occured. </p>
CLI_Cluster_Services_Must_Start_Manually_SYSACT=<p>Processing continues.</p>
CLI_Cluster_Services_Must_Start_Manually_URESP=<p> Manually start the cluster services on all nodes. </p>
# 1676
CLI_Cluster_Authoritative_Restore_Warning=ANS1676W You are doing an authoritative cluster database restore. The process may seem to be hang before and after the file is restored. This is because it may need to start the cluster service if it is not up and take all the resources offline. After the cluster database is restored, the cluster service will be restarted for changes to be in effect. The cluster service on all other nodes also have been shutdown. They will be restarted. This may take a few minutes.\n
CLI_Cluster_Authoritative_Restore_Warning_EXPLANATION=<p> The restore will seem to be paused at time because before the restore, Tivoli Storage Manager ensures the cluster service is up on the restoring node and all the resources are taken offline. After the cluster database is restored, the cluster service on the restoring node is in a paused state. The cluster service on other nodes were shutdown. All services need to be retarted. If some of the services cannot be started automatically, you can try to restart them. </p>
CLI_Cluster_Authoritative_Restore_Warning_SYSACT=<p>Processing continues.</p>
CLI_Cluster_Authoritative_Restore_Warning_URESP=<p> No action. </p>
# 1684
SubfileCache_DiskFull_Error=ANS1684W Disk Full Error Accessing Subfile Cache: {0}\n
SubfileCache_DiskFull_Error_EXPLANATION=<p> A disk full error occurred attempting to access or write to the specified subfile cache file during a subfile incremental backup. See the client error log for more detailed information. TSM. </p>
SubfileCache_DiskFull_Error_SYSACT=<p> Processing continues without subfile. </p>
SubfileCache_DiskFull_Error_URESP=<p> None. </p>
# 1685
SnapDiff_Not_Netapp_Fs=ANS1685E Incremental backup operation using snapshot difference is only available for N series/NetApp filer volumes, {0} is not a NetApp volume.
SnapDiff_Not_Netapp_Fs_EXPLANATION=<p> Cannot perform NAS NFS/CIFS incremental backup operation using snapshot difference on the mounted or mapped volume because the volume is not a N series/NetApp filer volume. </p>
SnapDiff_Not_Netapp_Fs_SYSACT=<p> Processing stops. </p>
SnapDiff_Not_Netapp_Fs_URESP=<p> Retry the incremental backup operation by specifying an entire NAS NFS or CIFS volume. </p>
# 1686
CLI_SIS_Limitation=ANS1686I Single Instance Store link '{0}' will be restored or retrieved as a normal file.\n
# 1692
SSL_Cert_Not_Trusted=ANS1692E The certificate is not trusted.\n
SSL_Cert_Not_Trusted_EXPLANATION=<p>The client was unable to open SSL connection to the server because the server certificate was not trusted.</p>
SSL_Cert_Not_Trusted_SYSACT=<p>Processing stopped</p>
SSL_Cert_Not_Trusted_URESP=<p>Make sure that you have configured the key database for SSL communication as described in the documentation. If the TSM server is using a self-signed certificate, make sure that you import the correct certificate from the server you are trying to connect to. When the server is using a certificate signed by an authority, make sure that the root certificate of the authority is imported into the client key database.</p>
# 1693
SSL_Cert_Validity_Incorrect=ANS1693E The certificate validity period is incorrect.\n
SSL_Cert_Validity_Incorrect_EXPLANATION=<p>The client was unable to open an SSL connection to the server because the certificate validity period is incorrect.</p>
SSL_Cert_Validity_Incorrect_SYSACT=<p>Processing stopped</p>
SSL_Cert_Validity_Incorrect_URESP=<p>Report this to the TSM server administrator. The server must have the correct certificate installed.</p>
# 1694
SSL_Cert_Identity_Wrong=ANS1694E The certificate identity could not be verified.\n
SSL_Cert_Identity_Wrong_EXPLANATION=<p>TSM was unable to open an SSL connection to the server because the certificate identity could not be verified. This happens when the certificate ownership information does not match the TSM domain name or IP address.</p>
SSL_Cert_Identity_Wrong_SYSACT=<p>Processing stopped</p>
SSL_Cert_Identity_Wrong_URESP=<p>Make sure that the server domain name or the IP address (the value of the TCPSERVERADDRESS option) is correct. If the problem persists, report it to your TSM server administrator.</p>
# 1695
SSL_Cert_Invalid=ANS1695E The certificate is not valid.\n
SSL_Cert_Invalid_EXPLANATION=<p>TSM was unable to open an SSL connection to the server because of an invalid certificate. The client was unable to determine the exact cause of the failure.</p>
SSL_Cert_Invalid_SYSACT=<p>Processing stopped</p>
SSL_Cert_Invalid_URESP=<p>Further analysis of the server certificate, the client key database, or both, is needed. Refer to TSM documentation for more information.</p>
# 1697
DSI_Auto_Client_Deploy_Label=Automatic Client Deployment
# 1698
DSI_Auto_Deploy_Label=Automatically deploy the client from the server
# 1699
DSI_Auto_Reboot_Label=Allow automatic system restart
# 1701
DSI_PREFERG_AUTODEPLOY_YES_FDA_DESC=Yes
# 1702
DSI_PREFERG_AUTODEPLOY_YES_NOREBOOT_FDA_DESC=Yes, if no reboot is required
# 1703
DSI_PREFERG_AUTODEPLOY_NO_FDA_DESC=No
# 1708
CLI_Abort_Not_Root=ANS1708E Backup operation failed. Only a root user can do this operation.\n
CLI_Abort_Not_Root_EXPLANATION=<p> Backups initiated by non-root users are disabled by IBM Tivoli Storage Manager administrator. </p>
CLI_Abort_Not_Root_SYSACT=<p>The operation stops.</p>
CLI_Abort_Not_Root_URESP=<p> Request the IBM Tivoli Storage Manager administrator to enable non-root backups. </p>
# 1711
VM_Incr_Selected_No_Full_Backup_Exists=ANS1711W Incremental backup selected for '{0}', but a Full backup has not yet been performed. Performing a Full backup instead.\n
VM_Incr_Selected_No_Full_Backup_Exists_EXPLANATION=<p>An incremental backup of the specified virtual machine was selected, but no full backup of that virtual machine exists; A full backup must exist before an incremental backup can be performed.</p>
VM_Incr_Selected_No_Full_Backup_Exists_SYSACT=<p>A full backup of the virtual machine is performed instead of an incremental backup.</p>
VM_Incr_Selected_No_Full_Backup_Exists_URESP=<p>None</p>
# 1712
VM_CBT_Not_Supported_Performing_Full=ANS1712I Changed block tracking not supported for disk {0}; Performing FULL backup of disk.\n
# 1713
VM_Failure_Getting_CBT_Info_Performing_Full=ANS1713W There was a problem getting changed block tracking information for disk {0}; Performing FULL backup of disk.\n
VM_Failure_Getting_CBT_Info_Performing_Full_EXPLANATION=<p>Changed block tracking is supported for the specified disk, but there was a problem getting the changed block tracking information, so a full backup of the disk will be performed.</p>
VM_Failure_Getting_CBT_Info_Performing_Full_SYSACT=<p>A full backup of the disk is performed.</p>
VM_Failure_Getting_CBT_Info_Performing_Full_URESP=<p>Review the error log for messages as to why the changed block tracking information could not be obtained.</p>
# 1714
VM_No_Changed_Extents_Found_Skipping_Disk=ANS1714I No changed extents found for disk {0} - skipping disk.\n
# 1715
VM_Filespace_Exists_Different_VM_Uuid=ANS1715E A filespace already exists for VM ({0}), but with a different VM uuid ({1}) than the current one ({2}).\n
VM_Filespace_Exists_Different_VM_Uuid_EXPLANATION=<p>No changed extents were found for the specified disk, so there is nothing to backup; The disk will be skipped.</p>
VM_Filespace_Exists_Different_VM_Uuid_SYSACT=<p>No data is backed up for the specified disk so no data has changed.</p>
VM_Filespace_Exists_Different_VM_Uuid_URESP=<p>None.</p>
# 1734
VMBACKUP_VSTORAGE_INDEPENDENT_ONLINE=ANS1734W The virtual machine '{0}' contains one or more independent disks. Backups are not supported in this configuration. Specify the '-vmprocessvmwithindependent=yes' option to exclude these disks from the backup.\n
VMBACKUP_VSTORAGE_INDEPENDENT_ONLINE_EXPLANATION=<p>Independent disks are not affected by snapshots so the IBM Tivoli Storage Manager client does not support backing them up.</p>
VMBACKUP_VSTORAGE_INDEPENDENT_ONLINE_SYSACT=<p>The virtual machine is not backed up.</p>
VMBACKUP_VSTORAGE_INDEPENDENT_ONLINE_URESP=<p>Power off the virtual machine and change the disk independent mode or remove them from the virtual machine. Or specify the '-vmprocessvmwithindependent=yes' option to exclude these disks from the backup.</p>
# 1735
VMBACKUP_VSTORAGE_PHYRDM_ONLINE=ANS1735W The virtual machine '{0}' contains one or more physical Raw Device Mappings (RDMs). Backups are not supported in this configuration. Specify the '-vmprocessvmwithprdm=yes' option to exclude these disks from the backup.\n
VMBACKUP_VSTORAGE_PHYRDM_ONLINE_EXPLANATION=<p>Physical RDMs are not included in snapshots so the TSM client does not support backing them up.</p>
VMBACKUP_VSTORAGE_PHYRDM_ONLINE_SYSACT=<p>The virtual machine is not backed up.</p>
VMBACKUP_VSTORAGE_PHYRDM_ONLINE_URESP=<p>Power off the virtual machine and change the RDMs to virtual mode or remove them from the virtual machine. Or specify the '-vmprocessvmwithprdm=yes' option to exclude these disks from the backup.</p>
# 1740
CLI_Unable_To_Get_ACLS=ANS1740W Unable to read ACLs for object: {0}{1}{2}. Check dsmerror.log for more information.\n
CLI_Unable_To_Get_ACLS_EXPLANATION=<p>The ACLs of the object are not read.</p>
CLI_Unable_To_Get_ACLS_SYSACT=<p>The object is skipped. Processing continues with the next object.</p>
CLI_Unable_To_Get_ACLS_URESP=<p> Examine the client error log for additional messages that might indicate the reason for the problem. Try to follow the suggested corrective actions (if any) and try the operation again. </p>
# 1741
CLI_Unable_To_Get_XATTRS=ANS1741W Unable to read extended attributes for {0}{1}{2}. Check dsmerror.log for more information.\n
CLI_Unable_To_Get_XATTRS_EXPLANATION=<p>The extended attributes of the object are not read.</p>
CLI_Unable_To_Get_XATTRS_SYSACT=<p>The object is skipped. Processing continues with the next object.</p>
CLI_Unable_To_Get_XATTRS_URESP=<p> Examine the client error log for additional messages that might indicate the reason for the problem. Follow the suggested corrective actions (if any) and try the operation again. </p>
# 1750
Use_Existing_Snap_Volume=ANS1750I Volume mount point '{0}' is mounted to volume '{1}'. Using snapshot volume for '{2}' to backup.\n
# 1751
CLI_FS_Inaccessible=ANS1751E Error processing '{0}': The file system can not be accessed.
CLI_FS_Inaccessible_EXPLANATION=<p> The client is unable to access the file system. Two common reasons for this are the account under which the client is running does not have access to the root of the file system, or the file system does not exist. </p>
CLI_FS_Inaccessible_SYSACT=<p> The inaccessible file system is skipped. Processing continues with the next file system. </p>
CLI_FS_Inaccessible_URESP=<p> Check the error log for additional messages that might yield additional information about the problem that prevents access to the file system. Correct the problem, then retry the operation. If the account does not have access to the file system, then either the system administrator needs to grant access, or an account that has access to the file system must be used. If the file system does not exist, then remove or correct the file system specification. </p>
# 1752
CLI_Generic_FS_Inaccessible=ANS1752E The file system can not be accessed.
CLI_Generic_FS_Inaccessible_EXPLANATION=<p> The client is unable to access the file system. Two common reasons for this are the account under which the client is running does not have access to the root of the file system, or the file system does not exist. </p>
CLI_Generic_FS_Inaccessible_SYSACT=<p> The inaccessible file system is ignored. </p>
CLI_Generic_FS_Inaccessible_URESP=<p> Check the error log for additional messages that might yield additional information about the problem that prevents access to the file system. Correct the problem, then retry the operation. If the account does not have access to the file system, then either the system administrator needs to grant access, or an account that has access to the file system must be used. If the file system does not exist, then remove or correct the file system specification. </p>
# 1753
CLI_BackupSet_Not_Supported_FSType=ANS1753E File space '{0}' was backed up by an older client version, and cannot be restored with this client version. The file space will be skipped.
CLI_BackupSet_Not_Supported_FSType_EXPLANATION=<p> The backup set format in earlier client versions for SYSTEM STATE and SYSTEM SERVICES is incompatible with the current client version. Those file spaces will be skipped. The restore might appear to pause while the client skips past the objects in those file spaces. Other remaining file space data will be restored. </p>
CLI_BackupSet_Not_Supported_FSType_SYSACT=<p> Objects in this file space are skipped. Other remaining file space data will be restored. </p>
CLI_BackupSet_Not_Supported_FSType_URESP=<p> Restore this specific file space in the backupset with a prior level client. </p>
# 1754
Proxy_Skip_SystemState_FS=ANS1754E File space '{0}' cannot be restored when ASNODENAME option is in affect. The file space will be skipped.
Proxy_Skip_SystemState_FS_EXPLANATION=<p> System state data of another node should not be restored to a different node. Those file spaces will be skipped. The restore might appear to pause while the client skips past the objects in those file spaces. Other remaining file space data will be restored. </p>
Proxy_Skip_SystemState_FS_SYSACT=<p> Objects in this file space are skipped. Other remaining file space data will be restored. </p>
Proxy_Skip_SystemState_FS_URESP=<p> Remove ASNODENAME option before restoring this specific file space in the backupset or use the node name that was used to backup system state data to restore. </p>
# 1755
DSI_USEDIROVERRIDE_FAILED=ANS1755W An error communicating with Active Directory has occured. USEDIRECTORY option will be ignored and processing will continue.
DSI_USEDIROVERRIDE_FAILED_EXPLANATION=<p>TSM attempted to query Active Directory for TSM Server parameters but an error has occured. This could be caused by Active Directory or the TSM Server's setup.</p>
DSI_USEDIROVERRIDE_FAILED_SYSACT=<p>TSM will ignore the USEDIRECTORY option and continue with client processing.</p>
DSI_USEDIROVERRIDE_FAILED_URESP=<p>Make sure your computer is properly set up to the domain with Active Directory. Also, make sure your TSM Administrator has properly configured the TSM Server for your node.</p>
# 1756
CLI_Journal_No_FS=ANS1756W The Journal for '{0}' has been reset: The server filespace was deleted since the last backup completed.\n
CLI_Journal_No_FS_EXPLANATION=<p> The client has reset the journal because the corresponding server filespace was deleted since the last backup completed. </p>
CLI_Journal_No_FS_SYSACT=<p> The journal is reset, the current backup won't use the journal, and the journal won't be available for backup until a full incremental backup successfully completes. </p>
CLI_Journal_No_FS_URESP=<p> None. </p>
# 1757
CLI_Journal_Incr_Date=ANS1757W The Journal for '{0}' has been reset: The server filespace was deleted since the last backup completed.\n
CLI_Journal_Incr_Date_EXPLANATION=<p> The client has reset the journal because the corresponding server filespace was deleted since the last backup completed. </p>
CLI_Journal_Incr_Date_SYSACT=<p> The journal is reset, the current backup won't use the journal, and the journal won't be available for backup until a full incremental backup successfully completes. </p>
CLI_Journal_Incr_Date_URESP=<p> None. </p>
# 1758
CLI_Journal_Del_Date=ANS1758W The Journal for '{0}' has been reset: The server filespace was deleted since the last backup completed.\n
CLI_Journal_Del_Date_EXPLANATION=<p> The client has reset the journal because the corresponding server filespace was deleted since the last backup completed. </p>
CLI_Journal_Del_Date_SYSACT=<p> The journal is reset, the current backup won't use the journal, and the journal won't be available for backup until a full incremental backup successfully completes. </p>
CLI_Journal_Del_Date_URESP=<p> None. </p>
# 1759
CLI_Journal_Pol_Date=ANS1759W The Journal for '{0}' has been reset: The policy set was updated since the last backup completed.\n
CLI_Journal_Pol_Date_EXPLANATION=<p> The client has reset the journal for the specified file system because the node policy set was updated since the last backup completed. </p>
CLI_Journal_Pol_Date_SYSACT=<p> The journal is reset, the current backup won't use the journal, and the journal won't be available for backup until a full incremental backup successfully completes. </p>
CLI_Journal_Pol_Date_URESP=<p> None. </p>
# 1760
CLI_Journal_Validated=ANS1760I Journal for '{0}' enabled for node '{1}' and server '{2}'\n
# 1761
CLI_Journal_Initial_Backup=ANS1761I Journal for '{0}' will be enabled upon successful completion of the backup.\n\n
# 1762
DSI_PREFP_SELECTFS_FROMLIST=Please select a Filespace from the List to update.
# 1769
SnapDiff_Ontap_Version_Not_Supported=ANS1769E NetApp file server '{0}' at Data ONTAP version '{1}.{2}.{3}' is not supported for performing incremental backups using snapshot difference.\n
SnapDiff_Ontap_Version_Not_Supported_EXPLANATION=<p> Incremental backup using Snapshot difference requires Data ONTAP V7.3 or later. However, if you are upgrading from Data ONTAP V7.3.3 or later to V8.0, you will lose snapshot difference support for unicode file names. Upgrade to Data ONTAP V8.1 or later. </p>
SnapDiff_Ontap_Version_Not_Supported_SYSACT=<p> Processing stops. </p>
SnapDiff_Ontap_Version_Not_Supported_URESP=<p> Upgrade the file server to a supported level of Data ONTAP, then retry the operation. </p>
# 1771
CLI_Skip_SystemState_FS=ANS1771W The system state filespace '{0}' cannot be restored to a different location.\n
CLI_Skip_SystemState_FS_EXPLANATION=<p>The system state file space cannot be restored to a different location. This file space is skipped. </p>
CLI_Skip_SystemState_FS_SYSACT=<p>Objects in the system state file space are skipped. Other remaining file spaces are restored. The restore might appear to pause while the client skips past the objects in this file space. </p>
CLI_Skip_SystemState_FS_URESP=<p>Restore system state to its original location.</p>
# 1784
SnapDiff_vFiler_Not_Supported=ANS1784E Incremental by snapshot difference cannot be performed on '{0}' as it is a vFiler volume.\n
SnapDiff_vFiler_Not_Supported_EXPLANATION=<p> Snapshot difference incremental backup is not supported on vFiler volumes. </p>
SnapDiff_vFiler_Not_Supported_SYSACT=<p> Processing stops. </p>
SnapDiff_vFiler_Not_Supported_URESP=<p> Perform snapshot difference incremental backup on normal NetApp/N-Series volumes only. </p>
# 1807
CLI_SM_Unable_To_Recall=ANS1807E Unable to recall file from server due to error from recall daemon.\n
CLI_SM_Unable_To_Recall_EXPLANATION=<p>Unable to recall file. The recall daemon reported an error while trying to recall a file. Look in the recall daemon's error log for more information. This can happen if the server is down, the connection is broken, or the file is missing on the server. It is also possible that the migration server in the system option file has been changed to a different server. The recall daemon does not check the system option file for changes once it has started. </p>
CLI_SM_Unable_To_Recall_SYSACT=<p>File skipped.</p>
CLI_SM_Unable_To_Recall_URESP=<p>See if the server is up, and retry. If the problem still exists, look in the error log. Also have the workstation administrator run dsmreconcile against the file system and see if the file shows up in the .SpaceMan/orphan.stubs file. If system option file has been changed, stop all recall daemons and restart the master recall daemon to pick up the changes.</p>
# 1808
DSI_Lvsa_Incorrect_Version=ANS1808E The Logical Volume Snapshot Agent is not at the correct level. It is possible that the Client was upgraded to a newer level but the LVSA driver was not updated at the same time. Use the Setup Wizard to configure either Online Image or Open File support and choose Update the Logical Volume Snapshot Agent.
DSI_Lvsa_Incorrect_Version_EXPLANATION=<p>The selected operation requires the current level of the Logical Volume Snapshot Agent. Use the Setup Wizard to update the LVSA. </p>
DSI_Lvsa_Incorrect_Version_SYSACT=<p>The selected operation is not performed.</p>
DSI_Lvsa_Incorrect_Version_URESP=<p>Retry the operation after updating the Logical Volume Snapshot Agent.</p>
# 1822
DSI_MaxRestObjsExceeded=ANS1822E Too many objects were selected for restore. Please select less than {0} objects
DSI_MaxRestObjsExceeded_EXPLANATION=<p>The restore cannot be performed, because too many objects were selected. </p>
DSI_MaxRestObjsExceeded_SYSACT=<p>The restore is not performed.</p>
DSI_MaxRestObjsExceeded_URESP=<p>Retry the operation after reducing the number of objects selected.</p>
# 1823
COM_Inv_Trace_Keyword=ANS1823E The TESTFLAGS or TRACEFLAGS option specifies unknown flag name '{0}' or the value supplied is invalid for the named keyword.\n
COM_Inv_Trace_Keyword_EXPLANATION=<p> Either the testflag or traceflag name is incorrectly spelled, or the value supplied for that flag is not valid. </p>
COM_Inv_Trace_Keyword_SYSACT=<p> If the TESTFLAGS or TRACEFLAGS option was specified in the client options file or on the command line during client initialization, the the client program does not start. If the option was specified from the command line client while running in LOOP (interactive) mode, then the operation does not run. </p>
COM_Inv_Trace_Keyword_URESP=<p> Correct the TESTFLAGS or TRACEFLAGS flag name or correct the value specified for the TESTFLAG keyword shown in the message. These options are typically used at the direction of IBM technical support or as specified in the TSM Problem Determination Guide. If you are not sure which flag names to use, review the TSM Problem Determination Guide for additional information or contact IBM technical support for further assistance. </p>
# 1825
DSI_CREATE_NEW_FILE_PROMPT=File '{0}' could not be found. Do you want to create it?
# 1827
DSI_CannotSelectNdmpDir=ANS1827W Directories cannot be selected with the table of contents currently loaded on the server.
DSI_CannotSelectNdmpDir_EXPLANATION=<p>The table of contents that is currently loaded on the server for this volume does not contain objects corresponding to the one and only point-in-time backup. It contains an incomplete point in time or multiple points in time. </p>
DSI_CannotSelectNdmpDir_SYSACT=<p>The directory is not selected for restore.</p>
DSI_CannotSelectNdmpDir_URESP=<p>To be able to select an entire directory for restore, select "Use Latest" or "Use Point in Time" from the Point in Time dialog.</p>
# 1838
COM_OptFile_Open_Failure=ANS1838E Error opening user specified options file '{0}' .\n
COM_OptFile_Open_Failure_EXPLANATION=<p> The specified <mv>options file-name</mv> could not be located or opened. </p>
COM_OptFile_Open_Failure_SYSACT=<p> TSM attempts to open default option file. </p>
COM_OptFile_Open_Failure_URESP=<p> Make sure specified option file exists and is valid. </p>
# 1848
DSI_LoadTocTitle=Load Table of Contents
# 1849
DSI_BACKUP_DATE=Backup Date
# 1850
DSI_LoadTocCancelPrompt=Do you want to cancel loading the table of contents?
# 1851
DSI_ServerLoadingToc=The server is loading a table of contents. Please wait.
# 1852
DSI_TocLoadAbort=ANS1852E Server could not load the table of contents. Status: {0} reason: {1}
DSI_TocLoadAbort_EXPLANATION=<p>A failure occurred when the server attempted to load a file-level Table of contents for an NDMP volume. No file-level queries can be performed against the volume until the problem is solved.</p>
DSI_TocLoadAbort_SYSACT=<p>The table of contents is not loaded.</p>
DSI_TocLoadAbort_URESP=<p>Check the server Activity Log to determine the cause of failure. Retry the operation after correcting the problem.</p>
# 1853
DSI_TocLoadFail=ANS1853E Server could not load the Table of Contents. Status: {0}
DSI_TocLoadFail_EXPLANATION=<p>A failure occurred when the server attempted to load a file-level Table of contents for an NDMP volume. No file-level queries can be performed against the volume until the problem is solved.</p>
DSI_TocLoadFail_SYSACT=<p>The table of contents is not loaded.</p>
DSI_TocLoadFail_URESP=<p>Check the server Activity Log to determine the cause of failure. Retry the operation after correcting the problem.</p>
# 1854
DSI_UsePointInTime=Use Point in Time Date
# 1855
DSI_UseLatestDate=Use Latest Date
# 1856
DSI_SelectImages=Select Images
# 1857
DSI_UseSelectedImages=Use Selected Images
# 1858
DSI_NdmpSelectImagesTitle=Select Images for {0}/{1}
# 1859
DSI_SelectBackupImagesDescription=Choose from available backup images to display files.\n\nNote: Differential images contain all files added or modified since the preceding full backup image. The resulting tree will contain all versions of files in selected images.
# 1860
DSI_Clear=Clear
# 1861
DSI_NasSelectiveRestore=Nas Selective Restore
# 1862
DSI_NoTocInfo=ANS1862W No table of contents information is available on the server for this volume.
DSI_NoTocInfo_EXPLANATION=<p>No objects for the selected volume exist on the server that were backed up with table of contents information. Consequently no file-level queries can be performed against the volume.</p>
DSI_NoTocInfo_SYSACT=<p>none</p>
DSI_NoTocInfo_URESP=<p>If file-level information is desired, use TOC option during backup.</p>
# 1863
DSI_NdmpPitTitle=Set Point in Time for {0}/{1}.
# 1864
DSI_SelectABackupDateDescription=Select a backup date or backed-up images to be used for files.\n\nNote: Changing the date or images will cancel any current file selections, and cause the table of contents to be reloaded on the server.
# 1865
SESS_NP_ERROR=ANS1865E Session rejected: Named Pipes connection failure.\n
SESS_NP_ERROR_EXPLANATION=<p> An attempt to connect to the server using Named Pipes communications failed. This might have occurred if an incorrect NAMEDPIPENAME was specified in the options files or if your system administrator canceled a backup operation. </p>
SESS_NP_ERROR_SYSACT=<p> Processing stopped. </p>
SESS_NP_ERROR_URESP=<p> Retry the operation, or wait until the server comes back up and retry the operation. Ensure that the value specified on the NAMEDPIPENAME option is the same as the one used by the server. If the problem continues, contact your system administrator for further help. </p>
# 1866
DSI_Transferred={0} transferred
# 1868
DSI_SelectExpiringFull= (The corresponding full image is expiring, so will not be displayed in the list.)
# 1904
CLI_Archive_Descr_Invalid=ANS1904E The archive description may not contain any wildcard characters \nlike '?' or '*'.\n
CLI_Archive_Descr_Invalid_EXPLANATION=<p> Descriptions for archive files must not contain wildcard characters. </p>
CLI_Archive_Descr_Invalid_SYSACT=<p> Processing stopped. </p>
CLI_Archive_Descr_Invalid_URESP=<p> Enter an archive description that does not contain wildcard characters. </p>
# 1927
DSI_SelectFullPrompt=Do you want to also select the full image corresponding to this differential image?
# 1930
ExpressClient_To_EnterpriseServer_Warning=ANS1930W TSM Express client view not supported with a TSM Enterprise server. CLIENTVIEW option ignored.
ExpressClient_To_EnterpriseServer_Warning_EXPLANATION=<p>The TSM Express client view is only supported when going to a TSM Express server. When a TSM Express client connects to a TSM Enterprise server, the CLIENTVIEW option is ignored, and the TSM Standard client view is displayed instead.</p>
ExpressClient_To_EnterpriseServer_Warning_SYSACT=<p>The CLIENTVIEW option is ignored and the TSM Enterprise client view is displayed.</p>
ExpressClient_To_EnterpriseServer_Warning_URESP=<p>If you intend to use the TSM Enterprise server, then update your CLIENTVIEW option to a value of STANDARD. Otherwise, update your TCPSERVERADDRESS option to point to your TSM Express server. </p>
# 1933
DSC_RC_OBJECTSET_LOCAL_ACCESS_ERROR=ANS1933E Error accessing file or device '{0}'.\n
DSC_RC_OBJECTSET_LOCAL_ACCESS_ERROR_EXPLANATION=<p> An error has occurred while accessing the file or device. </p>
DSC_RC_OBJECTSET_LOCAL_ACCESS_ERROR_SYSACT=<p> Backup set operation is not completed. </p>
DSC_RC_OBJECTSET_LOCAL_ACCESS_ERROR_URESP=<p> Verify that the file or device exists and is accessible. </p>
# 1946
CLI_File_Exists_Skipping=ANS1946W File {0}{1}{2} exists, skipping\n
CLI_File_Exists_Skipping_EXPLANATION=<p>The client tried to restore or retrieve the specified file, but the file already existed in the target restore location and the user chose not to replace the existing file.</p>
CLI_File_Exists_Skipping_SYSACT=<p>The file is skipped, a message is logged in dsmerror.log, and restore or retrieve processing continues with the next object.</p>
CLI_File_Exists_Skipping_URESP=<p>The file was skipped because either REPLACE NO was in effect, causing all existing files and directories to be skipped, or REPLACE PROMPT was in effect, and when prompted, the user chose to skip this file or all existing directories and files. No additional action is necessary if the decision to skip the file was deliberate. Otherwise the operation can be retried using either REPLACE ALL (automatically replace existing directories and files) or REPLACE PROMPT (prompt the user whether to replace the file).</p>
# 1947
CLI_Dir_Exists_Skipping=ANS1947W The following directory exists and is skipped: {0}{1}{2}\n
CLI_Dir_Exists_Skipping_EXPLANATION=<p> The client tried to restore or retrieve the specified directory. The directory exists in the target restore location and the user chose not to replace the existing directory. </p> <p>The directory can be skipped because the option REPLACE=NO is set, which causes all existing files and directories to be skipped. The directory can be skipped because option REPLACE=PROMPT is set, and the user chooses to skip this directory when prompted. </p>
CLI_Dir_Exists_Skipping_SYSACT=<p>The directory is skipped, a message is logged in the dsmerror.log log file, and restore or retrieve processing continues with the next object.</p>
CLI_Dir_Exists_Skipping_URESP=<p>No additional action is necessary.</p> <p>To replace the files, try the operation again and set option REPLACE=ALL. You can set REPLACE=PROMPT and when prompted, choose to replace the directory.</p>
# 1948
CLI_VSS_Query_SystemWriters_Failed=ANS1948E The Microsoft volume shadow copy system components could not be queried.\n
CLI_VSS_Query_SystemWriters_Failed_EXPLANATION=<p>IBM Tivoli Storage Manager encountered an error while querying the system writers under control of the Windows volume shadow copy service. The TSM error log and Windows event log might contain additional information about this error.</p>
CLI_VSS_Query_SystemWriters_Failed_SYSACT=<p>Processing stops.</p>
CLI_VSS_Query_SystemWriters_Failed_URESP=<p>Try the operation again. If the error persists, review the TSM error log and Windows event log for information related to this error. You might need to restart the volume shadow copy service, then try the operation again. It might be necessary to reboot the machine to clear the volume shadow copy error state. </p>
# 1949
CLI_VSS_Initialize_For_Snapshot_Failed=ANS1949E Microsoft volume shadow copy snapshot initialization failed.\n
CLI_VSS_Initialize_For_Snapshot_Failed_EXPLANATION=<p> IBM Tivoli Storage Manager encountered an error while initializing the Microsoft Volume Shadow Copy Service for backup or restore. The TSM error log and Windows event log can contain additional information about this error. </p>
CLI_VSS_Initialize_For_Snapshot_Failed_SYSACT=<p>processing stops.</p>
CLI_VSS_Initialize_For_Snapshot_Failed_URESP=<p> Try the operation again. If the error persists, review the TSM error log and Windows event log for information related to this error. Use the Windows command VSSADMIN LIST WRITERS to determine the status of the Volume Shadow Copy service. You can reboot the machine to clear the volume shadow copy error state. If the system is a Domain Controller and the Active Directory service is stopped, restarting the Active Directory service will resolve the issue. </p>
# 1950
CLI_VSS_Backup_Failed=ANS1950E Backup using Microsoft volume shadow copy failed.\n
CLI_VSS_Backup_Failed_EXPLANATION=<p>IBM Tivoli Storage Manager encountered an error while performing a backup operation using the Microsoft volume shadow copy service. The TSM error log and Windows event log might contain additional information about this error. </p>
CLI_VSS_Backup_Failed_SYSACT=<p>processing stops.</p>
CLI_VSS_Backup_Failed_URESP=<p> Review the TSM error log and Windows event log for information related to this error. Restart any failing system service indicated in the Windows event log. Restart the volume shadow copy Service. You can use the Windows command VSSADMIN LIST WRITERS to determine the status of the volume shadow copy service. It might be necessary to reboot the machine to clear the Volume Shadow Copy error state. </p>
# 1951
CLI_VSS_Restore_Failed=ANS1951E Restore using Microsoft volume shadow copy failed.\n
CLI_VSS_Restore_Failed_EXPLANATION=<p>IBM Tivoli Storage Manager encountered an error while restoring with the Microsoft Volume Shadow Copy Service.</p>
CLI_VSS_Restore_Failed_SYSACT=<p>processing stops.</p>
CLI_VSS_Restore_Failed_URESP=<p>Review the TSM error log and Windows event log for information related to this error. Restart any failing system service indicated in the Windows event log. Restart the volume shadow copy Service. You can use the Windows command VSSADMIN LIST WRITERS to determine the status of the volume shadow copy service. It might be necessary to reboot the machine to clear the Volume Shadow Copy error state.</p>
# 1965
DSJ_JAVA_DIAGNOSTIC_TITLE=Java GUI Diagnostic
# 1966
DSJ_JAVA_DIAGNOSTIC_NODE=Note: The changes to the settings in this dialog are in effect only for this invocation of the application.
# 1967
DSJ_JAVA_DIAGNOSTIC_TRACE=Java GUI Trace
# 1968
DSJ_JAVA_DIAGNOSTIC_ENABLE_TRACEFLAGS=Enable traceflags
# 1969
DSJ_JAVA_DIAGNOSTIC_ENTER_TRACEFLAGS=Enter traceflags:
# 1970
DSJ_JAVA_DIAGNOSTIC_ENTER_TRACEFILE=Enter tracefile name:
# 1971
DSJ_AGENT_NOT_START_EXCEPTION=ANS1971E The remote client agent (dsmagent) could not be started.
DSJ_AGENT_NOT_START_EXCEPTION_EXPLANATION=<p> The remote client agent cannot be started. This error message is usually preceded or followed by other messages. </p>
DSJ_AGENT_NOT_START_EXCEPTION_SYSACT=<p> Processing is stopped. </p>
DSJ_AGENT_NOT_START_EXCEPTION_URESP=<p> Check the error log for any other messages that might indicate a reason for the failure. Verify that the web client is installed correctly. Try to correct any indicated problems, then try the operation again. If the problem persists, contact IBM technical support for further assistance. </p>
# 1972
DSJ_AGENT_PORTNUM_NOT_READ=ANS1972E The connection to the remote client agent (dsmagent) failed. Either the port number could not be read, or the port number is invalid.
DSJ_AGENT_PORTNUM_NOT_READ_EXPLANATION=<p> An error occurred when trying to read the port number. A connection to the remote client agent cannot be made. </p>
DSJ_AGENT_PORTNUM_NOT_READ_SYSACT=<p> Processing stopped. </p>
DSJ_AGENT_PORTNUM_NOT_READ_URESP=<p> Check the error log for any other messages that might indicate a reason for the failure. Verify that the web client is installed correctly. Try to correct any indicated problems, then try the operation again. If the problem persists, contact IBM technical support for further assistance. </p>
# 1973
CLI_VSS_Restore_Sysobj_Skip=ANS1973I VSS writer for system object '{0}' does not exist. Restore skipped.\n
# 1978
CLI_Server_DownLevel_func=ANS1978E The TSM server is downlevel and does not support the requested function. See error log for version information.
CLI_Server_DownLevel_func_EXPLANATION=<p>The function being used requires a more current TSM Server. </p>
CLI_Server_DownLevel_func_SYSACT=<p>The operation fails.</p>
CLI_Server_DownLevel_func_URESP=<p>Upgrade your TSM Server to a level that supports this function. See error log for version information.</p>
# 1979
CLI_StorageAgent_DownLevel=ANS1979E The TSM Storage Agent is downlevel and does not support the requested function. See error log for version information.
CLI_StorageAgent_DownLevel_EXPLANATION=<p>The function being used requires a more current TSM Storage Agent. </p>
CLI_StorageAgent_DownLevel_SYSACT=<p>The operation fails.</p>
CLI_StorageAgent_DownLevel_URESP=<p>Upgrade your TSM Storage Agent to a level that supports this function. See error log for version information.</p>
# 1980
CLI_Server_And_StorageAgent_DownLevel=ANS1980E The TSM Server and TSM Storage agent are downlevel and do not support the requested function. See error log for version information.
CLI_Server_And_StorageAgent_DownLevel_EXPLANATION=<p>The function being used requires a more current TSM Server and TSM Storage agent </p>
CLI_Server_And_StorageAgent_DownLevel_SYSACT=<p>The operation fails.</p>
CLI_Server_And_StorageAgent_DownLevel_URESP=<p>Upgrade your TSM Server and TSM Storage agent to a level that supports this function. See error log for version information.</p>
# 1981
CLI_Server_And_StorageAgent_VRLM=ANS1981E Server :Version {0}, Release {1}, Level {2}.{3}\nStorage Agent:Version {4}, Release {5}, Level {6}.{7}
CLI_Server_And_StorageAgent_VRLM_EXPLANATION=<p>This message supplies extra detail to downlevel messages. </p>
CLI_Server_And_StorageAgent_VRLM_SYSACT=<p>The operation fails.</p>
CLI_Server_And_StorageAgent_VRLM_URESP=<p>This message supplies extra detail to downlevel messages.</p>
# 1985
DSI_CONN_SA_INFORMATION=Storage Agent Information
# 1986
TRACEFILE_Cannot_Open=ANS1986E Initialization functions cannot open the trace file specified.\n
TRACEFILE_Cannot_Open_EXPLANATION=<p>The file "<mv>tracefile-name</mv> could not be opened during initialization. The specified path may be incorrect. It is also possible that the current user does not have permission to write to the tracefile in the directory specified. It is also possible that no space is available at the given tracefile location.</p>
TRACEFILE_Cannot_Open_SYSACT=<p>Processing terminates.</p>
TRACEFILE_Cannot_Open_URESP=<p>Make sure the tracefile option points to a valid path and that the user has proper permissions to write to the file specified.</p>
# 1988
DSI_Preview_NoFileSys=ANS1988W No filespaces are selected for preview.
DSI_Preview_NoFileSys_EXPLANATION=<p>You requested a preview operation without selecting a client filespace.</p>
DSI_Preview_NoFileSys_SYSACT=<p>TSM cannot perform a preview without a filespace selected.</p>
DSI_Preview_NoFileSys_URESP=<p>Select the volumes you want to preview and retry the operation.</p>
# 1989
LOGFILE_Cannot_Open=ANS1989E Initialization functions cannot open the Error Log file specified.\n
LOGFILE_Cannot_Open_EXPLANATION=<p>The Error Log file could not be opened during initialization. The specified path may be incorrect. It is also possible that the current user does not have permission to write to the logfile in the directory specified. It is also possible that no space is available at the given logfile location.</p>
LOGFILE_Cannot_Open_SYSACT=<p>Processing terminates.</p>
LOGFILE_Cannot_Open_URESP=<p>Make sure the logfile option points to a valid path and that the user has proper permissions to write to the file specified.</p>
# 1990
CLI_MP_INACCESSIBLE=ANS1990W The '{0}' volume mount point can not be accessed. The TSM return code is '{1}'.\n
CLI_MP_INACCESSIBLE_EXPLANATION=<p> The client is unable to access volume mount point. The common reasons for this are that the account under which the client is running does not have access to the volume mount point, or the volume is mounted onto a cluster volume which is currently not available. </p>
CLI_MP_INACCESSIBLE_SYSACT=<p> The inaccessible mount point is skipped and processing continues. with the next mount point or volume. </p>
CLI_MP_INACCESSIBLE_URESP=<p> Check the error log for additional messages that might yield additional information about the problem that prevents access to the volume mount point. Ensure that the TSM client is running under an account which as access to the volume mount point. Ensure that the mount point is not accessing a clustered volume. Please refer to Microsoft KB Article 280297 for more information about how to configure volume mount points on a clustered server. </p>
# 1992
DSI_PREFERS_SCHED_CMD=Scheduled Operating System commands
# 1993
DSI_PREFERS_SCHED_RESTRETR=Scheduled Restore/Retrieve operations
# 1995
DSI_DELETE_ONE_OBJECT_TYPE=ANS1995W Objects of different types cannot be deleted at the same time.
DSI_DELETE_ONE_OBJECT_TYPE_EXPLANATION=<p>Deleting objects of different types is not allowed. For example, deleting Backup Sets and regular file objects at the same time is not possible.</p>
DSI_DELETE_ONE_OBJECT_TYPE_SYSACT=<p>No processing takes place.</p>
DSI_DELETE_ONE_OBJECT_TYPE_URESP=<p>Select objects of the same type to perform delete operation. </p>
# 1996
CLI_MP_ENUMERATING_FAILED=ANS1996W The volume mount points enumeration on '{0}' volume failed. Windows system error code: {1}; reason: '{2}'.\n
CLI_MP_ENUMERATING_FAILED_EXPLANATION=<p> The client was unable to scan the specified volume for volume mount points. The error information captured indicates the reason for the failure. A common reason is that the account under which the client is running does not have access to the volume. </p>
CLI_MP_ENUMERATING_FAILED_SYSACT=<p> The processing continues with the next volume. </p>
CLI_MP_ENUMERATING_FAILED_URESP=<p> Ensure that the client is running under an account which has access to the volume and volume mount points. Correct the condition causing the error and try the operation again. If the problem persists, contact your system administrator or TSM administrator for further help. </p>
# 2029
dsmEvent_Restore_Complete_No_Failures=Restore complete with no reported failures.\n
# 2030
dsmEvent_Restore_Complete_With_Failures=Restore complete with failures.\n
# 2038
COM_Invalid_Cloptset_Option=ANS2038W Invalid option '{0}' received from the TSM server client options set.\n
COM_Invalid_Cloptset_Option_EXPLANATION=<p> The client received an invalid option from the TSM server's client option set. Although most syntax checking for client option set options is done by the server, there are still errors that can only be detected by the client. These errors include: <ul> <li>Option value is not correct.</li> <li>Options that have been retired by newer versions of the TSM client.</li> <li>Missing brackets or directory delimiters.</li> <li>Include and exclude patterns that are too complex.</li> </ul> </p>
COM_Invalid_Cloptset_Option_SYSACT=<p> The option is ignored by the TSM client. </p>
COM_Invalid_Cloptset_Option_URESP=<p> Contact the TSM server administrator to determine if the option can be removed from the client option set. </p>
# 2040
IC_Version_Mismatch_generic=ANS2040E While attempting to communicate with the remote client, a version check reveals that the versions do not match.
IC_Version_Mismatch_generic_EXPLANATION=<p>During initialization between the local client and the remote client, version checking reveals that the versions do not match. This is usually the result of an upgrade of one client module without upgrading other client modules that are part of product solution.</p>
IC_Version_Mismatch_generic_SYSACT=<p>The calling procedure returns and control is passed back the user.</p>
IC_Version_Mismatch_generic_URESP=<p>Check the versions of all TSM Client products that communicate with each other and ensure that they are all at the same version, release, and level.</p>
# 2041
SnapDiff_Api_NotAvailable=ANS2041E Snapshot Differencing support is not available on the specified NetApp filer.\n
SnapDiff_Api_NotAvailable_EXPLANATION=<p>Incremental by snapshot difference backup cannot be performed because required support on the specified NetApp filer is not availble. .</p>
SnapDiff_Api_NotAvailable_SYSACT=<p>Processing terminates.</p>
SnapDiff_Api_NotAvailable_URESP=<p>None.</p>
# 2044
VSTORAGE_SKIPPING_TEMPLATE_RESTORE=ANS2044E The template virtual machine '{0}' cannot be restored when the Tivoli Storage Manager data mover node on the vStorage Backup Server is connected directly to an ESX/ESXi host.\n
VSTORAGE_SKIPPING_TEMPLATE_RESTORE_EXPLANATION=<p>The VMware vStorage API do not support template virtaul machine operations when connected directly to an ESX/ESXi host.</p>
VSTORAGE_SKIPPING_TEMPLATE_RESTORE_SYSACT=<p>Processing stops for this template virtual machine</p>
VSTORAGE_SKIPPING_TEMPLATE_RESTORE_URESP=<p>Virtual machine template operations are supported when the IBM Tivoli Storage Manager data mover node connects directly to a ESX/ESXi host. Modify the VMCHOST to connect the TSM data mover to a vCenter Server.</p>
# 2045
VSTORAGE_SKIPPING_TEMPLATE=ANS2045E The VMENABLETEMPLATEBACKUPS option is not specified. The virtual machine template '{0}' can not be backed up.\n
VSTORAGE_SKIPPING_TEMPLATE_EXPLANATION=<p>The VMENABLETEMPLATEBACKUPS template option must specify YES in order for a virtual machine template to be included in a backup operation. The default value is NO.</p>
VSTORAGE_SKIPPING_TEMPLATE_SYSACT=<p>Processing stops for this template virtual machine</p>
VSTORAGE_SKIPPING_TEMPLATE_URESP=<p>Use the option -vmenabletemplatebackups=yes and run the operation again.</p>
# 2074
LSM_Cannot_Open_Input_FCT=ANS2074E Cannot open user input FlashCopy target file '{0}'.\n
LSM_Cannot_Open_Input_FCT_EXPLANATION=<p>The FlashCopy target file that the user provided cannot be read. </p>
LSM_Cannot_Open_Input_FCT_SYSACT=<p>The operation fails.</p>
LSM_Cannot_Open_Input_FCT_URESP=<p>Run the client configuration utility and provide a valid FlashCopy target user input file.</p>
# 2079
CLI_VSS_Snapshot_File_Not_Found=ANS2079E Error processing '{0}{1}{2}': error scanning snapshot
CLI_VSS_Snapshot_File_Not_Found_EXPLANATION=<p> This message is issued when the TSM client is unable to read data from a snapshot used for the backup. If you are performing the Microsoft Volume Shadowcopy Service (VSS) snapshot backup one possible cause is that the operating system deleted a VSS snapshot because the shadow copy storage could not grow. If you are performing the snapshot difference incremental backup on normal NetApp/N-Series volumes one possible cause is that the base snapshot was accidentally removed from the NetApp file server. </p>
CLI_VSS_Snapshot_File_Not_Found_SYSACT=<p>Backup processing for the file system stops.</p>
CLI_VSS_Snapshot_File_Not_Found_URESP=<p> If you were performing VSS snapshot-based backup, examine the client error log and the Microsoft Windows system event log for any other messages that might help identify the problem. If there are no obvious reasons for the failure, try the operation again,the problem might be caused by temporary I/O conflicts between VSS and other system disk I/O activities. If you were performing snapshot difference incremental backup, contact your Tivoli Storage Manager administrator to verify that base snapshot was not accidentally deleted. </p>
# 2090
VSTORAGE_FAILED_VMFOLDER_PATH=ANS2090I The virtual machine folder could not be found in this path: '{0}'.\n
# 2091
VSTORAGE_FAILED_RESOURCE_PATH=ANS2091I The virtual machine resource could not be found in this path: '{0}'.\n
# 2092
VSTORAGE_OVERRIDE_INVENTORY_PATH=ANS2092I The restore process will override the original inventory path that was saved with this virtual machine. \n
# 2093
CLI_FSAgent_Downlevel=ANS2093E The remote file system agent is downlevel and does not support this operation.\n NODENAME : {0} \n MULTI-NODE NAME : {1} \n hostname : {2} \n TCP/IP address : {3}:{4} \n version : {5}.{6}.{7}.{8}\n
CLI_FSAgent_Downlevel_EXPLANATION=<p>None. </p>
CLI_FSAgent_Downlevel_SYSACT=<p>The operation fails.</p>
CLI_FSAgent_Downlevel_URESP=<p>Upgrade the remote file system agent to a supported level.</p>
# 2145
VSTORAGE_VM_EXISTING_NAME=ANS2145W Warning - updating an existing virtual machine named '{0}'. The restore operation continues.\n
VSTORAGE_VM_EXISTING_NAME_EXPLANATION=<p>The virtual machine exists and will be updated with the disks specified.</p>
VSTORAGE_VM_EXISTING_NAME_SYSACT=<p>The virtual machine will be updated by the restore operation.</p>
VSTORAGE_VM_EXISTING_NAME_URESP=<p>No user action is necessary.</p>
# 2146
VSTORAGE_UNSUPPORTED_HOST_BACKUP=ANS2146E The target vCenter or ESX/ESXi host is no longer supported, for virtual machine backups, by this version of IBM Tivoli Storage Manager.\n
VSTORAGE_UNSUPPORTED_HOST_BACKUP_EXPLANATION=<p>The target vCenter or ESX/ESXi host is no longer supported, for virtual machine backups, by this version of IBM Tivoli Storage Manager.</p>
VSTORAGE_UNSUPPORTED_HOST_BACKUP_SYSACT=<p>Processing stops for this virtual machine.</p>
VSTORAGE_UNSUPPORTED_HOST_BACKUP_URESP=<p>Specify another target vCenter or ESX/ESXi host that is supported by this version of IBM Tivoli Storage Manager.</p>
# 2147
VSTORAGE_VM_WITH_DUPLICATE_NAME=ANS2147E The virtual machine named '{0}' already exists on the target system.\n
VSTORAGE_VM_WITH_DUPLICATE_NAME_EXPLANATION=<p>The virtual machine cannot be restored because the name already exists on the target system.</p>
VSTORAGE_VM_WITH_DUPLICATE_NAME_SYSACT=<p>Processing stops for this virtual machine</p>
VSTORAGE_VM_WITH_DUPLICATE_NAME_URESP=<p>Use the -vmname option to rename the virtual machine.</p>
# 2149
VSTORAGE_SKIPPING_DOWNLEVEL_RESTORE=ANS2149E The restore operation for this virtual machine to the target ESX/ESXi host is not supported because virtual machine hardware version is incompatible.\n
VSTORAGE_SKIPPING_DOWNLEVEL_RESTORE_EXPLANATION=<p>The target ESX/ESXi host does not support the virtual hardware version of the virtual machine. As a result, a restore of the specified virtual machine to this host is not supported.</p>
VSTORAGE_SKIPPING_DOWNLEVEL_RESTORE_SYSACT=<p>Processing stops for this virtual machine.</p>
VSTORAGE_SKIPPING_DOWNLEVEL_RESTORE_URESP=<p>Specify another virtual machine to restore or specify another target ESX/ESXi host that supports virtual hardware version of the virtual machine.</p>
# 2173
AIX_Vfiler_NFS4_SnapDiff_Not_Supported=ANS2173E Volume '{0}' from vFiler '{1}' is mounted using AIX NFS version 4. This configuration is not supported for snapshot difference incremental backups.\n
AIX_Vfiler_NFS4_SnapDiff_Not_Supported_EXPLANATION=<p> Snapshot difference incremental backups are not supported for vFiler volumes mounted using AIX NFS version 4. </p>
AIX_Vfiler_NFS4_SnapDiff_Not_Supported_SYSACT=<p>Snapshot difference incremental backup fails. </p>
AIX_Vfiler_NFS4_SnapDiff_Not_Supported_URESP=<p>This problem is documented by NetApp BURT 630200. Apply the fix for this once it is available from NetApp. Specify "testflag snapdiffenablevfilernfs4" in dsm.opt file and retry the snapshot difference incremental backup. </p>
# 2174
CLI_HsmLog_Conflict=ANS2174E Conflicting options HSMLOGMAX and HSMLOGRETENTION were specified.\n
CLI_HsmLog_Conflict_EXPLANATION=<p>Values were specified for both the HSMLOGMAX and the HSMLOGRETENTION options. These options are mutually exclusive. </p>
CLI_HsmLog_Conflict_SYSACT=<p>Processing stops.</p>
CLI_HsmLog_Conflict_URESP=<p>Specify a nonzero value for HSMLOGMAX if you wish to have the TSM hsm log wrap when it reaches the specified maximum value. Use HSMLOGRETENTION if you wish you have the hsm log limited in size on a time-based schedule. </p>
# 2201
CLI_ExaminingInDiskCache=ANS2201I ***** Inspecting Cache {0} files *****\n
# 2202
DiskCache_DiskFull_Error=ANS2202E Disk Full Error Accessing Disk Cache.
DiskCache_DiskFull_Error_EXPLANATION=<p>A disk full error occurred attempting to access or write to the specified disk cache file during a disk cache incremental backup. See the client error log for more detailed information.</p>
DiskCache_DiskFull_Error_SYSACT=<p>Processing stops.</p>
DiskCache_DiskFull_Error_URESP=<p>This error can be resolved by freeing up space in the file system containing the cache file, or specifying a different location for the cache file. Use the diskcachelocation option to specify the location of the cache file.</p>
# 2203
DiskCache_Access_Error=ANS2203E Error Accessing Disk Cache.
DiskCache_Access_Error_EXPLANATION=<p>An error occurred attempting to access the specified disk cache file during a disk cache incremental backup. See the client error log for more detailed information. TSM.</p>
DiskCache_Access_Error_SYSACT=<p>Processing stops.</p>
DiskCache_Access_Error_URESP=<p>None.</p>
# 2204
DiskCache_NameLength_Exceeds_Key=ANS2204E Disk cache restarted.
DiskCache_NameLength_Exceeds_Key_EXPLANATION=<p>The length of an object name exceeded the configured disk cache key length during a disk cache incremental backup. The backup must be restarted.. TSM.</p>
DiskCache_NameLength_Exceeds_Key_SYSACT=<p>Backup is restarted with a larger key length to accommodate the object name.</p>
DiskCache_NameLength_Exceeds_Key_URESP=<p>None required. The name of the object that caused the failure can be found in the dsmerror.log file. </p>
# 2205
CLI_Using_DiskCache=Using disk caching for backup of filespace {0}\n
# 2206
DiskCache_User_Must_Be_Root=ANS2206W The user must have root authority to use the memory efficient backup disk cache method. The operation will continue using memory efficient backup method without disk caching.\n
DiskCache_User_Must_Be_Root_EXPLANATION=<p> None. </p>
DiskCache_User_Must_Be_Root_SYSACT=<p>The operation continues without using disk caching.</p>
DiskCache_User_Must_Be_Root_URESP=<p> None. </p>
# 2207
CLI_ACTIVE_STATUS_CACHE_FILL=Filling Cache: {0}
# 2208
CLI_ACTIVE_STATUS_EXPIRE_WALK=Inspecting Cache: {0}
# 2209
DSI_PREFERR_PERFORMANCE_TUNING_PREFERENCES=Performance Tuning Preferences
# 2210
DSI_PREFERR_PERFORMANCE_TUNING_SAVING=Saving performance tuning preferences to IBM Tivoli Storage Manager configuration files...
# 2211
DSI_PREFERR_PERFORMANCE_TUNING_SAVED=Your performance tuning preferences setting has been saved.
# 2212
DSI_PREFERR_PERFORMANCE_TUNING=Performance Tuning
# 2214
DSI_PREFERR_MEMORY_RESIDENT=Use memory-resident method
# 2215
DSI_PREFERR_MEMORY_SAVING_INCR=Use memory saving method
# 2216
DSI_PREFERR_MEMORY_DISKCACHE=Use disk cache method
# 2217
DSI_PREFERR_MEMORY_METHOD=Memory Usage Algorithm to be used during backup
# 2220
Img_Vol_Set_Maint_Mode_Failure=ANS2220E The cluster disk could not be put in maintenance mode.\n
Img_Vol_Set_Maint_Mode_Failure_EXPLANATION=<p> The system call to put the cluster disk in maintenance mode failed. </p>
Img_Vol_Set_Maint_Mode_Failure_SYSACT=<p> Processing stopped. </p>
Img_Vol_Set_Maint_Mode_Failure_URESP=<p> Try the operation again. If the problem continues, check the client error log for any other messages that might have been logged when this message was written, and take the corrective action (if any) suggested by those messages. Examine the Windows event log which may contain additional information. See your system administrator or TSM administrator for further help. </p>
# 2221
DSI_HOST_ADDRESS_CONFIGURATION=ANS2221W Java was not able to resolve the IP address of your local machine \ndue to network misconfiguration problems! \n\nPlease verify your network and DNS configuration are setup correctly. \nNote that on UNIX machines the hostname must be reported correctly (the same) \nfor IPv4 and IPv6 communication methods in the /etc/hosts configuration file. \n\nTSM processing continues. \n
DSI_HOST_ADDRESS_CONFIGURATION_EXPLANATION=<p> Java was not able to get the local host address due to network misconfiguration problems. </p>
DSI_HOST_ADDRESS_CONFIGURATION_SYSACT=<p> Processing continues. </p>
DSI_HOST_ADDRESS_CONFIGURATION_URESP=<p> Please verify your network and DNS configuration are setup correctly. Note that on UNIX machines the hostname must be reported correctly (the same) for IPv4 and IPv6 communication methods in the /etc/hosts configuration file. See your system administrator or TSM administrator for further help. </p>
# 2222
DSI_PREFERR_APPLY_ALL_FILESPACES=Apply algorithm to all the filespaces
# 2224
DSI_PREFERR_APPLY_ONE_FILESPACE=Select individual filespaces
# 2600
DSJ_CONNECT_SOCKETEXCEPTION=ANS2600S  Browser trying to establish connection to client; received socket exception: {0} 
DSJ_CONNECT_SOCKETEXCEPTION_EXPLANATION=<p> The browser received the exception <mv>exception-name</mv> trying to connect to the TSM client computer. </p> 
DSJ_CONNECT_SOCKETEXCEPTION_SYSACT=<p> The TSM operation ends. </p> 
DSJ_CONNECT_SOCKETEXCEPTION_URESP=<p> Validate that the LAN is up and that you are trying to connect to the correct port number. </p> <p> Check error logs for any additional information: dsmerror.log, dsmwebcl.log, or dsmj.log. The default location of these logs is the installation directory of the backup-archive client. </p> <p> Ensure that the command line client runs without problems. Test the command line client with a command like "dsmc q sess". </p> 
# 2601
DSJ_CONNECT_UNKNOWNHOSTEXCEPTION=ANS2601S Browser trying to establish connection to client; received unknown host exception: {0}
DSJ_CONNECT_UNKNOWNHOSTEXCEPTION_EXPLANATION=<p> The browser received the exception <mv>exception-name</mv> trying to connect to the TSM client machine. </p>
DSJ_CONNECT_UNKNOWNHOSTEXCEPTION_SYSACT=<p> The TSM operation ends. </p>
DSJ_CONNECT_UNKNOWNHOSTEXCEPTION_URESP=<p> Retry the operation. If it persists, determine what might be causing this kind of a problem. Determine if your LAN went down. Determine if you are trying to connect to the correct TSM client machine. </p>
# 2602
DSJ_CONNECT_IOEXCEPTION=ANS2602S Browser trying to establish connection to client; received IO exception: {0}
DSJ_CONNECT_IOEXCEPTION_EXPLANATION=<p> The browser received the exception <mv>exception-name</mv> trying to connect to the TSM client machine. </p>
DSJ_CONNECT_IOEXCEPTION_SYSACT=<p> The TSM operation ends. </p>
DSJ_CONNECT_IOEXCEPTION_URESP=<p> Determine what might be causing this kind of an exception. Retry the problem, and check if the LAN is down. </p>
# 2603
DSJ_CONNECT_EXCEPTION=ANS2603S Browser trying to establish connection to client; received exception: {0}
DSJ_CONNECT_EXCEPTION_EXPLANATION=<p> The browser received the exception <mv>exception-name</mv> trying to connect to the TSM client machine. </p>
DSJ_CONNECT_EXCEPTION_SYSACT=<p> The TSM operation ends. </p>
DSJ_CONNECT_EXCEPTION_URESP=<p> Determine what might be causing this kind of an exception. Determine if the LAN may be down, or if the TSM Client Acceptor Daemon on the TSM machine is up and running. </p>
# 2604
DSJ_AGENT_AUTH_FAILED=ANS2604S The Web client agent was unable to authenticate with the server.
DSJ_AGENT_AUTH_FAILED_EXPLANATION=<p> The TSM Web client agent was unable to authenticate with the TSM server. </p>
DSJ_AGENT_AUTH_FAILED_SYSACT=<p> The TSM operation ends. </p>
DSJ_AGENT_AUTH_FAILED_URESP=<p> One possible solution is to run the command line client so that the client password can be re-entered. Another approach is to check the error log on the TSM Web client agent for any relevant messages. </p>
# 2605
DSJ_CHECKSESS_PROTOCOL_ERROR=ANS2605S Browser could not re-establish connection to client; received protocol error.
DSJ_CHECKSESS_PROTOCOL_ERROR_EXPLANATION=<p> The browser received a protocol error trying to re-connect to the TSM client machine. </p>
DSJ_CHECKSESS_PROTOCOL_ERROR_SYSACT=<p> The TSM operation ends. </p>
DSJ_CHECKSESS_PROTOCOL_ERROR_URESP=<p> Determine what might be causing this kind of an error. Determine if the TSM browser and the TSM client code might be out of sync. </p>
# 2606
DSJ_ABORT_BAD_VERIFIER=ANS2606S An invalid password was sent to the server.
DSJ_ABORT_BAD_VERIFIER_EXPLANATION=<p> The TSM password that was sent to the TSM server was invalid. </p>
DSJ_ABORT_BAD_VERIFIER_SYSACT=<p> The TSM operation ends. </p>
DSJ_ABORT_BAD_VERIFIER_URESP=<p> Make sure that you have the correct password. Also make sure that it is valid, for example it is not too short. </p>
# 2607
DSJ_CONNECT_FAILURE=ANS2607S Browser could not establish connection to client.
DSJ_CONNECT_FAILURE_EXPLANATION=<p> The TSM browser could not connect to the TSM client machine. </p>
DSJ_CONNECT_FAILURE_SYSACT=<p> The TSM operation ends. </p>
DSJ_CONNECT_FAILURE_URESP=<p> Determine what might be causing this kind of a problem. Determine if the LAN is down, or if the TSM Client Acceptor Daemon on the TSM machine is up and running. </p>
# 2608
DSJ_NONE_SELECTED=ANS2608S Nothing was selected so no operation was performed.
DSJ_NONE_SELECTED_EXPLANATION=<p> No object was selected in the GUI for the operation to be performed upon. </p>
DSJ_NONE_SELECTED_SYSACT=<p> The TSM operation ends. </p>
DSJ_NONE_SELECTED_URESP=<p> Make sure you select one or more objects (volume, directory or file) in the GUI before clicking on the operation to be performed. </p>
# 2609
DSJ_TCPIP_BROWSER_FAILURE=ANS2609S TCP/IP communications failure between the browser and the client machine.
DSJ_TCPIP_BROWSER_FAILURE_EXPLANATION=<p> This error can occur due to any of the following: <ul> <li>The LAN connection to the TSM client machine went down. </li><li>You are trying to connect to the TSM client machine using the wrong port number. </li><li>The Client Acceptor Daemon on the TSM client machine is not up and running and accepting connections. </li></ul> </p>
DSJ_TCPIP_BROWSER_FAILURE_SYSACT=<p> The TSM operation ends. </p>
DSJ_TCPIP_BROWSER_FAILURE_URESP=<p> Retry the operation and make sure the LAN is up. Also check that the port number is correct, and that the Client Acceptor Daemon is started and running on the TSM client machine, and that it is listening on the correct port number. </p>
# 2610
DSJ_TCPIP_CLIENT_FAILURE=ANS2610S TCP/IP communications failure between the client and the server machine.
DSJ_TCPIP_CLIENT_FAILURE_EXPLANATION=<p> An attempt to connect to the server using TCP/IP communications failed. This can be a result of incorrect TCP/IP option settings in your client options file. This error can also occur if the LAN connection went down or if your system administrator canceled a backup operation. </p>
DSJ_TCPIP_CLIENT_FAILURE_SYSACT=<p> The TSM client ends. </p>
DSJ_TCPIP_CLIENT_FAILURE_URESP=<p> Retry the operation and make sure the LAN is up. Make sure that both the TSM server and the TSM client are up and running. </p>
# 2611
DSJ_UNKNOWN_BROWSER_ERROR=ANS2611S An unknown error occurred in the browser.
DSJ_UNKNOWN_BROWSER_ERROR_EXPLANATION=<p> An unknown error occurred in the applet running in the browser. </p>
DSJ_UNKNOWN_BROWSER_ERROR_SYSACT=<p> The TSM operation ends. </p>
DSJ_UNKNOWN_BROWSER_ERROR_URESP=<p> Retry the operation. If the problem persists, turn on tracing and see if the trace to the browser console gives the reason for the error. </p>
# 2612
DSJ_UNKNOWN_CLIENT_ERROR=ANS2612S An unknown error occurred in the client\nPlease check the TSM Error Log for any additional information
DSJ_UNKNOWN_CLIENT_ERROR_EXPLANATION=<p> An unknown error occurred in the TSM client. </p>
DSJ_UNKNOWN_CLIENT_ERROR_SYSACT=<p> The TSM client ends. </p>
DSJ_UNKNOWN_CLIENT_ERROR_URESP=<p> Retry the operation. If the problem persists, check the TSM Error Log for any additional information. </p>
# 2613
DSJ_COMM_BROWSER_PROTOCOL_ERROR=ANS2613S A communications protocol error occurred between the web browser and the client.
DSJ_COMM_BROWSER_PROTOCOL_ERROR_EXPLANATION=<p> None. </p>
DSJ_COMM_BROWSER_PROTOCOL_ERROR_SYSACT=<p> The operation ends. </p>
DSJ_COMM_BROWSER_PROTOCOL_ERROR_URESP=<p> Try the operation again. If the problem occurs again, verify that the TSM web client is installed and configured correctly, and make sure you are using a supported browser. Flush the browser cache. Then try the operation again. If the problem persists, enable SERVICE traces on the web client on the target machine and the TSM Java applet, then reproduce the problem. Collect the traces and contact IBM for further assistance. </p>
# 2614
DSJ_COMM_CLIENT_PROTOCOL_ERROR=ANS2614S A protocol error occurred in communications between the client and the server.
DSJ_COMM_CLIENT_PROTOCOL_ERROR_EXPLANATION=<p> A protocol error happened between the TSM client and the TSM server. </p>
DSJ_COMM_CLIENT_PROTOCOL_ERROR_SYSACT=<p> The TSM client ends. </p>
DSJ_COMM_CLIENT_PROTOCOL_ERROR_URESP=<p> Retry the operation. If the problem persists, check the TSM Error Log for any additional information. Verify that you are running the correct applet with the appropriate level of the client. </p>
# 2615
DSJ_INCORRECT_NODENAME=ANS2615S The user ID entered does not match the node name configured on the client machine.
DSJ_INCORRECT_NODENAME_EXPLANATION=<p> The user ID that was entered is not the same as the node name on this TSM client. </p>
DSJ_INCORRECT_NODENAME_SYSACT=<p> The TSM operation ends. </p>
DSJ_INCORRECT_NODENAME_URESP=<p> Verify that the node name entered is configured correctly on the TSM client. </p>
# 2616
DSJ_Reboot_Machine=ANS2616I The machine must be rebooted for the changes to take effect
# 2617
DSJ_INVALID_DESTINATION_DIRECTORY=ANS2617S The destination directory specified is invalid.
DSJ_INVALID_DESTINATION_DIRECTORY_EXPLANATION=<p> The user specified a destination target directory for restore or retrieve which is invalid. </p>
DSJ_INVALID_DESTINATION_DIRECTORY_SYSACT=<p> The TSM operation ends. </p>
DSJ_INVALID_DESTINATION_DIRECTORY_URESP=<p> Retry the operation specifying a valid directory name. </p>
# 2619
DSJ_ERROR_STARTING_AGENT=ANS2619S The Client Acceptor Daemon was unable to start the Remote Client Agent.
DSJ_ERROR_STARTING_AGENT_EXPLANATION=<p> The TSM Client Acceptor Daemon could not start the TSM Remote Client Agent. </p>
DSJ_ERROR_STARTING_AGENT_SYSACT=<p> The TSM operation ends. </p>
DSJ_ERROR_STARTING_AGENT_URESP=<p> Check the error log on the TSM Web client agent for any relevant messages. Then correct the problem and retry. </p>
# 2620
DSJ_Expand_Entire_Warning=ANS2620W The expand entire branch operation may take a long time, \nand cannot be canceled once it has started.\n\nAre you willing to wait for the operation to complete?
DSJ_Expand_Entire_Warning_EXPLANATION=<p> The expand entire branch operation could take a long time and cannot be canceled once it is started. </p>
DSJ_Expand_Entire_Warning_SYSACT=<p> Processing stopped; waiting for user intervention. </p>
DSJ_Expand_Entire_Warning_URESP=<p> Answer 'Yes' to start the expand entire branch operation. If you answer 'No', the current operation will be canceled. </p>
# 2622
DSJ_ID_OR_PW_UNKNOWN=ANS2622S An invalid ID or password submitted.
DSJ_ID_OR_PW_UNKNOWN_EXPLANATION=<p> Either the ID is not registered on the TSM server, or the password for the ID is incorrect. </p>
DSJ_ID_OR_PW_UNKNOWN_SYSACT=<p> The TSM operation ends. </p>
DSJ_ID_OR_PW_UNKNOWN_URESP=<p> Verify that the ID you are using exists on the TSM server to which the remote client node connects. The ID must have sufficient privileges to access the remote client node's data. Also make sure that you have the correct password for the ID. If the ID does not exist or if the password is unknown, contact your TSM administrator. If the ID does not exist, then the TSM administrator can use the REGISTER ADMIN and GRANT AUTHORITY commands to register an ID that can access the remote client node's data. If the password is unknown, the TSM administrator can use the UPDATE ADMIN command to reset the password. </p>
# 2623
DSJ_APPLET_AGENT_OUT_OF_SYNC=ANS2623S Web Client applet level is out of sync with Web Client agent.
DSJ_APPLET_AGENT_OUT_OF_SYNC_EXPLANATION=<p>The Web Client applet and Web Client agents are at incompatible levels.</p>
DSJ_APPLET_AGENT_OUT_OF_SYNC_SYSACT=<p>The TSM operation ends.</p>
DSJ_APPLET_AGENT_OUT_OF_SYNC_URESP=<p>Verify that you have the correct level of the applet installed with the client, and that an incorrect level of the applet was not placed in the install directory.</p>
# 2624
DSJ_OPERATION_REQUIRES_CLIENT_OWNER=ANS2624E This operation requires client owner authority.
DSJ_OPERATION_REQUIRES_CLIENT_OWNER_EXPLANATION=<p>Your user ID has insufficient authority to perform this operation.</p>
DSJ_OPERATION_REQUIRES_CLIENT_OWNER_SYSACT=<p>Processing continues, but the user is not allowed to do this operation. </p>
DSJ_OPERATION_REQUIRES_CLIENT_OWNER_URESP=<p>Do not perform this operation, or get a higher authority level for your user ID in order to perform this operation. </p>
# 2625
DSJ_IMAGE_OPERATION_NOT_SUPPORTED=ANS2625E Node does not support this image operation.
DSJ_IMAGE_OPERATION_NOT_SUPPORTED_EXPLANATION=<p>Node does not support or is not configured to perform this image operation.</p>
DSJ_IMAGE_OPERATION_NOT_SUPPORTED_SYSACT=<p>Processing continues, but the user is not allowed to do this operation. </p>
DSJ_IMAGE_OPERATION_NOT_SUPPORTED_URESP=<p>Verify whether this image related operation is supported or configured on the target platform. </p>
# 2626
DSI_InvCharsIn_Statement=ANS2626E The Include-Exclude statement:\n {0} \ncontains invalid characters.
DSI_InvCharsIn_Statement_EXPLANATION=<p>The specified Include-Exclude statement has invalid characters.</p>
DSI_InvCharsIn_Statement_SYSACT=<p>TSM will not add the specified Include-Exclude statement to the list.</p>
DSI_InvCharsIn_Statement_URESP=<p>Retry the operation with another statement that has valid characters.</p>
# 2697
VSTORAGE_VM_MISSING_DATASTORE=ANS2697E The virtual machine cannot be restored because the datastore named '{0}' does not exist or is inactive.\n
VSTORAGE_VM_MISSING_DATASTORE_EXPLANATION=<p>The datastore referenced by virtual machine when it was backed up does not exist or is inactive on the ESX/ESXi that you are restoring the virtual machine to.</p>
VSTORAGE_VM_MISSING_DATASTORE_SYSACT=<p>The virtual machine cannot be restored.</p>
VSTORAGE_VM_MISSING_DATASTORE_URESP=<p>Find the missing datastore or specify the -datastore option on the Restore VM command to specify an existing datastore to restore the virtual machine files to.</p>
# 2808
SnapDiff_Using_OlderBaseSnapshot=ANS2808W Incremental by snapshot difference backup did not locate the registered base snapshot '{0}' on NetApp/N-Series filer volume '{1}'. Snapshot '{2}' is used as the base snapshot.\n
SnapDiff_Using_OlderBaseSnapshot_EXPLANATION=<p>Incremental by snapshot difference backup did not locate the specified registered base snapshot on the specified NetApp/N-Series filer volume. The most recent existing snapshot which is older than the registered base snapshot is used as the current base snapshot.</p>
SnapDiff_Using_OlderBaseSnapshot_SYSACT=<p>Processing continues.</p>
SnapDiff_Using_OlderBaseSnapshot_URESP=<p>None.</p>
# 2819
DSI_CLUSTERCW_DRIVE_NOT_FROM_DOMAINLIST=The specified drive is invalid. Specify a valid drive from the selected domain list.
# 2828
Img_FS_Not_Supported=ANS2828E Image operations are not supported for the specified file system.\n
Img_FS_Not_Supported_EXPLANATION=<p> Image backup and restore are not supported for the specified file system.\n</p>
Img_FS_Not_Supported_SYSACT=<p> The requested image operation is not performed. </p>
Img_FS_Not_Supported_URESP=<p> Choose another object. </p>
# 2829
Img_GPFS_Not_Supported=ANS2829E Image operations are not supported for GPFS.\n
Img_GPFS_Not_Supported_EXPLANATION=<p> Image backup and restore are not supported for GPFS volumes.\n</p>
Img_GPFS_Not_Supported_SYSACT=<p> The requested image operation is not performed. </p>
Img_GPFS_Not_Supported_URESP=<p> Choose another object. </p>
# 2831
SnapDiff_Not_Supported=ANS2831E Incremental by snapshot difference cannot be performed on '{0}' as it is of type '{1}' and is not a NetApp/N-Series '{2}' volume.\n
SnapDiff_Not_Supported_EXPLANATION=<p> The volume specified cannot be used for performing NetApp/N-Series snapshot difference incremental operation. The volume does not correspond to the NFS mount point or the CIFS shared drive for a Network Appliance or N-Series NAS volume. One possible reason for this failure is that snapshot difference incremental backups can only be performed against NetApp/N-Series NFS volumes on AIX/Linux platforms, or CIFS volumes on Windows platforms.</p> <p>Another possible reason for this failure is that the qtree security style for the volume was incorrectly selected. If the CIFS volume is mapped on Windows, ensure that the security style is set to NTFS. If the volume is mounted as NFS, ensure that the security style is set to UNIX.</p>
SnapDiff_Not_Supported_SYSACT=<p>Processing stops.</p>
SnapDiff_Not_Supported_URESP=<p> Try the command again with a NetApp/N-Series NFS or CIFS volume with the correct security style. </p>
# 2835
SnapDiff_Operation_Failed_Not_Supported=ANS2835E Incremental backup using snapshot difference is not supported on this platform.\n
SnapDiff_Operation_Failed_Not_Supported_EXPLANATION=<p> NetApp NFS/CIFS incremental backup operation using snapshot difference is only supported on AIX, Linux and Windows platforms. </p>
SnapDiff_Operation_Failed_Not_Supported_SYSACT=<p> Processing stops. </p>
SnapDiff_Operation_Failed_Not_Supported_URESP=<p> Retry the incremental operation without the snapdiff option. </p>
# 2836
SnapDiff_Not_Supported_For_Qtrees=ANS2836E Incremental backup operation using snapshot difference is only available for full volumes.\n{0} is a partial volume or qtree.\n
SnapDiff_Not_Supported_For_Qtrees_EXPLANATION=<p> Cannot perform NAS NFS/CIFS incremental backup operation using snapshot difference on the mounted or mapped volume due to one of the following reasons: 1) The volume is actually a qtree. 2) The volume is not a full volume, it is not mounted or mapped to the root of the volume. </p>
SnapDiff_Not_Supported_For_Qtrees_SYSACT=<p> Processing stops. </p>
SnapDiff_Not_Supported_For_Qtrees_URESP=<p> Retry the incremental backup operation by specifying an entire NAS NFS or CIFS volume. </p>
# 2837
SnapDiff_No_Password_Found=ANS2837E Failed to perform incremental backup operation using snapshot difference as the user id and password for NAS Filer '{0}' have not been configured correctly.\n
SnapDiff_No_Password_Found_EXPLANATION=<p> The user id and password for the specified NAS Filer have been either not configured or have been specified incorrectly. </p>
SnapDiff_No_Password_Found_SYSACT=<p> Processing stops. </p>
SnapDiff_No_Password_Found_URESP=<p> Use the 'set password -type=filer' command to define the user id and password for the specified NAS Filer and retry the incremental backup operation. </p>
# 2839
Snap_Authetication_Failure=ANS2839E Failed with ONTAPI error '{0}' while connecting to NetApp Filer '{1}' using user id '{2}'. You might have provided credentials incorrectly for this Filer.\n
Snap_Authetication_Failure_EXPLANATION=<p> The user ID and password have been configured incorrectly for the specified Filer. </p>
Snap_Authetication_Failure_SYSACT=<p> Processing stops. </p>
Snap_Authetication_Failure_URESP=<p> Make sure that the credentials you have specified for the Filer are the correct ones. Use the dsmc set password command to specify the correct credentials for your Filer and try the command again. </p>
# 2840
SnapDiff_Not_Supported_For_Filer_Version=ANS2840E Incremental backup using snapshot difference is not supported for Data ONTAP file server version '{0}.{1}.{2}'. Upgrade the file server '{3}' to Data ONTAP version '7.3' or later in order to perform incremental backup operations using snapshot difference.\n
SnapDiff_Not_Supported_For_Filer_Version_EXPLANATION=<p> The file server specified is not at the Data ONTAP version that supports snapshot difference API. </p>
SnapDiff_Not_Supported_For_Filer_Version_SYSACT=<p> Processing stops. </p>
SnapDiff_Not_Supported_For_Filer_Version_URESP=<p> Upgrade the file server to Data ONTAP version 7.3 or later and retry the operation. </p>
# 2841
SnapDiff_Not_Supported_For_OS_Platform=ANS2841E Incremental by snapshot difference is only supported on AIX 64 bit and Linux 86 bit clients. \n
SnapDiff_Not_Supported_For_OS_Platform_EXPLANATION=<p> Incremental backup using snapshot difference feature is only available on IBM Tivoli Storage Manager AIX 64 bit and Linux 86 clients. </p>
SnapDiff_Not_Supported_For_OS_Platform_SYSACT=<p>Processing stops.</p>
SnapDiff_Not_Supported_For_OS_Platform_URESP=<p> Try the command again with an IBM Tivoli Storage Manager AIX 64 bit or Linux 86 client. </p>
# 2849
SnapDiff_Matching_Snapshot_NotFound=ANS2849E Incremental backup operation using snapshot difference failed because a snapshot matching '{0}' could not be located on volume {1}.\n
SnapDiff_Matching_Snapshot_NotFound_EXPLANATION=<p> A snapshot name or pattern specified by the BASESNAPSHOTNAME or DIFFSNAPSHOTNAME option could not be located on the volume being backed up. </p>
SnapDiff_Matching_Snapshot_NotFound_SYSACT=<p> Processing stops. </p>
SnapDiff_Matching_Snapshot_NotFound_URESP=<p> Rety the operation and specify a snapshot with the BASESNAPSHOTNAME or DIFFSNAPSHOTNAME which exists on the specified volume. </p>
# 2850
SnapDiff_Snapmirror_Destination_Volume=ANS2850E Error Creating Snapshot: Volume {0} is a snapmirror destination volume.\n
SnapDiff_Snapmirror_Destination_Volume_EXPLANATION=<p> An attempt was made to create a snapshot on a read only snapmirror destination volume. </p>
SnapDiff_Snapmirror_Destination_Volume_SYSACT=<p> Processing stops. </p>
SnapDiff_Snapmirror_Destination_Volume_URESP=<p> Rety the operation using the USEEXISTINGBASE and DIFFSNAPSHOT=latest options. </p>
# 2851
SnapDiff_Failed=ANS2851E Snapshot Processing Error: {0}.\n
SnapDiff_Failed_EXPLANATION=<p> An error occurred due to the reason specified in the message </p>
SnapDiff_Failed_SYSACT=<p> Processing stops. </p>
SnapDiff_Failed_URESP=<p> Ensure that the specified volume is online and allows write access. </p>
# 2852
SnapDiff_RegisteredBase_NotFound=ANS2852W Registered Base Snapshot '{0}' no longer exists on volume {1} .\n
SnapDiff_RegisteredBase_NotFound_EXPLANATION=<p> The specified base snapshot registered by the previous backup no longer exists on the specified volume. </p>
SnapDiff_RegisteredBase_NotFound_SYSACT=<p> Processing continues. </p>
SnapDiff_RegisteredBase_NotFound_URESP=<p> The client will attempt to use an existing snapshot older than the missing registered snapshot as the base for the current backup. </p>
# 2853
SnapDiff_UnableToEstablishBase=ANS2853E Unable to establish base snapshot on volume {0}.\n
SnapDiff_UnableToEstablishBase_EXPLANATION=<p> A base snapshot could not be created or selected on the specified volume. </p>
SnapDiff_UnableToEstablishBase_SYSACT=<p> Processing stops. </p>
SnapDiff_UnableToEstablishBase_URESP=<p> See other error messages to determine why the base could be established. </p>
# 2854
SnapDiff_UnableToEstablishDiff=ANS2854E Unable to establish diff snapshot on volume {0}.\n
SnapDiff_UnableToEstablishDiff_EXPLANATION=<p> A diff snapshot could not be created or selected on the specified volume. </p>
SnapDiff_UnableToEstablishDiff_SYSACT=<p> Processing stops. </p>
SnapDiff_UnableToEstablishDiff_URESP=<p> See other error messages to determine why the diff could be established. </p>
# 2888
Missing_License_File=ANS2888E Backup VM Full VM Incremental is unable to run.\nA valid TSM for Virtual Environments license file ({0}) cannot be located. \n
Missing_License_File_EXPLANATION=<p>The license file was not found, or cannot be opened because of permissions, or the file is corrupted.</p>
Missing_License_File_SYSACT=<p>The system returns to the calling procedure.</p>
Missing_License_File_URESP=<p>Check permissions on file. See if the license file is in the correct place.</p>
# 2999
DSI_CLUSTER_PROTECTION_CONFIRM_AND_APPLY_DESC=You have completed the configurations of the Cluster Protection. Click on the 'Apply' button to confirm your configuration.
# 3003
COM_New_Password_Case_Sensitive=ANS3003I The new password is case sensitive.\n
# 3010
DSI_Snapshot_Wizard_Failed=ANS3010E The snapshot wizard operation failed.
DSI_Snapshot_Wizard_Failed_EXPLANATION=<p>The snapshot wizard operation failed with a non-zero return code. Check the error log for additional information. </p>
DSI_Snapshot_Wizard_Failed_SYSACT=<p>The selected operation is not performed.</p>
DSI_Snapshot_Wizard_Failed_URESP=<p>Review the error log for any error messages, and then retry the operation after correcting the cause for failure.</p>
# 3011
CLI_Reboot_Required_Before_Continuing=ANS3011E Previous changes have not been commited.\n The machine must be rebooted before this operation can be performed
CLI_Reboot_Required_Before_Continuing_EXPLANATION=<p>A previous operation required the machine to be rebooted for the changes to take effect, but the machine has not been rebooted. The machine must be rebooted before this selected operation can be performed. </p>
CLI_Reboot_Required_Before_Continuing_SYSACT=<p>The selected operation is not performed.</p>
CLI_Reboot_Required_Before_Continuing_URESP=<p>Reboot the machine and then retry the operation.</p>
# 3012
DSI_Lvsa_Not_Installed=ANS3012E The Logical Volume Snapshot Agent is not installed. Use the Setup Wizard to configure either Online Image or Open File support and choose the Logical Volume Snapshot Agent as the snapshot provider.
DSI_Lvsa_Not_Installed_EXPLANATION=<p>The selected operation requires the Logical Volume Snapshot Agent, but it is not installed. Use the Setup Wizard to install the LVSA. </p>
DSI_Lvsa_Not_Installed_SYSACT=<p>The selected operation is not performed.</p>
DSI_Lvsa_Not_Installed_URESP=<p>Retry the operation after installing the Logical Volume Snapshot Agent.</p>
# 3013
DSI_Snapshot_Provider_Not_Valid_OS=ANS3013E The specified snapshot provider is not supported on this version of the operating system. 
DSI_Snapshot_Provider_Not_Valid_OS_EXPLANATION=<p>The specified snapshot provider is not supported on the version of the operating system you are currently running. If another snapshot provider is available, select it and retry the operation. </p>
DSI_Snapshot_Provider_Not_Valid_OS_SYSACT=<p>The selected operation is not performed.</p>
DSI_Snapshot_Provider_Not_Valid_OS_URESP=<p>If another snapshot provider is available, select it and retry the operation.</p>
# 4000
DSI_PREFER_PREFERENCES_EDITOR=Preferences Editor
# 4001
DSI_PREFERG_GENERAL_PREFERENCES=General Preferences
# 4002
DSI_PREFERB_BACKUP_PREFERENCES=Backup Preferences
# 4003
DSI_PREFERR_RESTORE_PREFERENCES=Restore Preferences
# 4004
DSI_PREFERW_CLIENT_PREFERENCES=Web Client Preferences
# 4005
DSI_PREFERD_DIAGNOSTIC_PREFERENCES=Diagnostic Preferences
# 4006
DSI_PREFERIS_SNAPSHOT_PREFERENCES=Image Snapshot Preferences
# 4007
DSI_PREFERI_INCLUDE_EXCLUDE_PREFERENCES=Include Exclude Preferences
# 4008
DSI_PREFERC_GEN_COMMUNICATION_PREF=Communication Preferences
# 4009
DSI_PREFERS_SCHEDULE_PREF=Scheduler Preferences
# 4010
DSI_PREFERM_COMMANDLINE_PREF=Command Line Interface Preferences
# 4011
DSI_PREFERR_MISCELLANEOUS=Miscellaneous
# 4012
DSI_PREFERG_BYTE_PER_TRANSFER_FORMAT=Transaction Buffer Size Format
# 4013
DSI_PREFERG_ERROR_LOG_RETENTION_FORMAT=Retention Format
# 4016
DSI_PREFERG_GENERAL_SAVING=Saving general preferences to IBM Tivoli Storage Manager configuration files...
# 4017
DSI_PREFERG_GENERAL_SAVED=Your general preferences setting has been saved.
# 4018
DSI_PREFERG_BYTES_PER_TRANS_FORMAT=Transaction Buffer Size Format
# 4019
DSI_PREFERG_ERROR_LOG_KEEP_ENTRIES_FORMAT=Keep Entries Format
# 4022
DSI_PREFERG_CHOOSE_ERROR_LOG_FILE_NAME=Choose the Error Log file name
# 4023
DSI_PREFERB_VIRTUAL_MOUNT_ADD=Add button
# 4024
DSI_PREFERB_VIRTUAL_MOUNT_REMOVE=Remove button
# 4025
DSI_PREFERB_BACKUP_SAVING=Saving backup preferences to IBM Tivoli Storage Manager configuration files...
# 4026
DSI_PREFERB_BACKUP_SAVED=Your backup preferences setting has been saved.
# 4028
DSI_PREFERB_CHOOSE_VIRTUAL_MOUNT=Choose a Virtual Mount Point
# 4029
DSI_PREFERI_STATEMENT_LIST=Statement List
# 4030
DSI_PREFERI_INCLEXCL_SAVING=Saving Include/Exclude preferences to IBM Tivoli Storage Manager configuration files...
# 4031
DSI_PREFERI_INCLEXCL_SAVED=Your Include/Exclude preferences setting has been saved.
# 4032
DSI_PREFERR_RESTORE_SAVING=Saving restore preferences to IBM Tivoli Storage Manager configuration files...
# 4033
DSI_PREFERR_RESTORE_SAVED=Your restore preferences setting has been saved.
# 4035
DSI_PREFERW_PORTS=Ports
# 4037
DSI_PREFERD_CHOOSE_TRACE_FILE_NAME=Choose the Trace File
# 4042
DSI_PREFERIS_CHACE_SETTINGS=Cache Settings
# 4043
DSI_PREFERC_GEN_COMMSETTINGS=Communication Settings
# 4044
DSI_PREFERC_TCPIP_ADMIN_PORT=Admin Port
# 4045
DSI_PREFERS_SESSION_INIT=Session Initiation
# 4046
DSI_PREFERS_SESSION_CLIENT=Client
# 4047
DSI_PREFERS_SESSION_SERVER=Server Only
# 4048
DSI_PREFERS_RETRY_SETTINGS=Retry Settings
# 4049
DSI_PREFERS_PREVENT_ANY_PRESCHEDULE_CMD=Prevent any preschedule commands
# 4050
DSI_PREFERS_PREVENT_ANY_POSTSCHEDULE_CMD=Prevent any postschedule commands
# 4051
DSI_PREFERA_AUTHORIZATION_PREF=Authorization Preferences
# 4052
DSI_PREFERA_SERVICES=Authorization for TSM services
# 4053
DSI_PREFERA_SERVICES_ALL=All groups and users can request TSM services
# 4055
DSI_PREFERC_NLS_FORMAT=Format Settings
# 4056
DSI_PREFERH_HSM_PREF=HSM Preferences
# 4057
DSI_PREFERH_NUMBER_RECALL_DAEMONS=Number of Recall Daemons
# 4058
DSI_GENERIC_MINIMUM=Minimum
# 4059
DSI_GENERIC_MAXIMUM=Maximum
# 4060
DSI_PREFERH_MAX_NUMBER_PROC=Number of Maximum Processes
# 4064
DSI_PREFERH_HSM_PERIOD=Period Settings
# 4065
DSI_PREFERH_HSM_MAX_MIN=Processes/Daemons Settings
# 4066
DSI_PREFERD_DIAGNOSTIC_SAVING=Saving diagnostic preferences to IBM Tivoli Storage Manager configuration files...
# 4067
DSI_PREFERD_DIAGNOSTIC_SAVED=Your diagnostic preferences setting has been saved.
# 4084
DSI_PREFER_GENERAL_LOADING=Loading General Preferences from IBM Tivoli Storage Manager configuration files...
# 4085
DSI_PREFER_GENERAL_LOADED=General Preferences has been loaded from IBM Tivoli Storage Manager configuration files.
# 4086
DSI_PREFER_BACKUP_LOADING=Loading Backup Preferences from IBM Tivoli Storage Manager configuration files...
# 4087
DSI_PREFER_BACKUP_LOADED=Backup Preferences has been loaded from IBM Tivoli Storage Manager configuration files.
# 4088
DSI_PREFER_RESTORE_LOADING=Loading Restore Preferences from IBM Tivoli Storage Manager configuration files...
# 4089
DSI_PREFER_RESTOREP_LOADED=Restore Preferences has been loaded from IBM Tivoli Storage Manager configuration files.
# 4090
DSI_PREFER_INCLUDE_EXCLUDE_LOADING=Loading Include-Exclude Preferences from IBM Tivoli Storage Manager configuration files...
# 4091
DSI_PREFER_INCLUDE_EXCLUDE_LOADED=Include-Exclude Preferences has been loaded from IBM Tivoli Storage Manager configuration files.
# 4092
DSI_PREFER_IMAGE_SNAPSHOT_LOADING=Loading Image Snapshot Preferences from IBM Tivoli Storage Manager configuration files...
# 4093
DSI_PREFER_IMAGE_SNAPSHOT_LOADED=Image Snapshot Preferences has been loaded from IBM Tivoli Storage Manager configuration files.
# 4094
DSI_PREFER_SCHEDULER_LOADING=Loading Scheduler Preferences from IBM Tivoli Storage Manager configuration files...
# 4095
DSI_PREFER_SCHEDULER_LOADED=Scheduler Preferences has been loaded from IBM Tivoli Storage Manager configuration files.
# 4096
DSI_PREFER_REGIONAL_SETTING_LOADING=Loading Regional Setting Preferences from IBM Tivoli Storage Manager configuration files...
# 4097
DSI_PREFER_REGIONAL_SETTING_LOADED=Regional Setting Preferences has been loaded from IBM Tivoli Storage Manager configuration files.
# 4098
DSI_PREFER_COMMUNICATION_LOADING=Loading Communication Preferences from IBM Tivoli Storage Manager configuration files...
# 4099
DSI_PREFER_COMMUNICATION_LOADED=Communication Preferences has been loaded from IBM Tivoli Storage Manager configuration files.
# 4100
DSI_PREFER_AUTHORIZATION_LOADING=Loading Authorization Preferences from IBM Tivoli Storage Manager configuration files...
# 4101
DSI_PREFER_AUTHORIZATION_LOADED=Authorization Preferences has been loaded from IBM Tivoli Storage Manager configuration files.
# 4102
DSI_PREFER_WEB_CLIENT_LOADING=Loading Web Client Preferences from IBM Tivoli Storage Manager configuration files...
# 4103
DSI_PREFER_WEB_CLIENT_LOADED=Web Client Preferences has been loaded from IBM Tivoli Storage Manager configuration files.
# 4104
DSI_PREFER_HSM_LOADING=Loading HSM Preferences from IBM Tivoli Storage Manager configuration files...
# 4105
DSI_PREFER_HSM_LOADED=HSM Preferences has been loaded from IBM Tivoli Storage Manager configuration files.
# 4106
DSI_PREFER_COMMAND_LINE_LOADING=Loading Command Line Preferences from IBM Tivoli Storage Manager configuration files...
# 4107
DSI_PREFER_COMMAND_LINE_LOADED=Command Line Preferences has been loaded from IBM Tivoli Storage Manager configuration files.
# 4108
DSI_PREFER_DIAGNOSTIC_LOADING=Loading Diagnostic Preferences from IBM Tivoli Storage Manager configuration files...
# 4109
DSI_PREFER_DIAGNOSTIC_LOADED=Diagnostic Preferences has been loaded from IBM Tivoli Storage Manager configuration files.
# 4110
DSI_PREFERM_DISPLAY_ON_SCREEN=Display on Screen
# 4111
DSI_GENERIC_ADD_DOTDOTDOT=Add...
# 4113
DSI_PREFER_WARNING=Warning
# 4114
DSI_PREFER_ERROR_INDICATOR=\nFields marked with a red indicator are not correctly entered.\n\nPlease correct them before applying the changes.
# 4115
DSI_PREFER_OPTIONS_SAVED=The changes you have made require you to close the \n{0} dialog before they can take effect.\n\nClick OK to continue.
# 4116
DSI_PREFER_RESET_TOOLTIP=Returns the values of changed setting choices to their last applied state.
# 4117
DSI_PREFER_CANCEL_TOOLTIP=Resets all changes made since the last Apply and closes the editor.
# 4118
DSI_PREFER_APPLY_TOOLTIP=Applies the changes made to the selected objects, without closing the editor.
# 4119
DSI_PREFER_OK_TOOLTIP=Applies the changes made to the selected objects and closes the editor.
# 4120
DSI_PREFER_SBAR_NO_CHANGES=No changes have been found on this preferences setting.
# 4121
DSI_PREFER_SBAR_OPTIONS_SAVED=Your preferences settings have been saved.
# 4122
DSI_PREFER_SBAR_CLOSING=Closing Preferences Editor...
# 4123
DSI_PREFER_SBAR_RELOADING=Reloading preferences from the agent...
# 4124
DSI_PREFER_SBAR_RELOADED=Preferences settings have been reloaded.
# 4125
DSI_PREFER_SBAR_NO_RELOAD_NECESSARY=It is not necessary to reload the preferences because no changes have been applied from the previous state.
# 4126
DSI_PREFER_SBAR_WARNING_DEFAULT=Warning: The '{0}' option will be set to the default value.
# 4127
DSI_PREFER_SBAR_ERROR_BETWEEN=Error: The '{0}' option must be in the range from {1} to {2}.
# 4128
DSI_PREFER_SBAR_NOT_LENGTH_MORE=Error: The length of '{0}' option can not be more than {1} characters.
# 4129
DSI_PREFER_SETTING_LOADED=The '{0}' settings have been loaded.
# 4130
DSI_PREFERCW_CREATE_OPTIONS_FILE_FDA=Select this option if you do not already have a TSM client options file. TSM will create an options file for you based on your specifications in this wizard.
# 4131
DSI_PREFER_LOADING_SETTING=Loading '{0}' settings...
# 4132
DSI_PREFERCW_UPDATE_OPTIONS_FILE_FDA=Select this option if you want to change the basic TSM options in your client options file
# 4133
DSI_PREFERCW_IMPORT_OPTIONS_FILE=Import from an existing options file for use
# 4134
DSI_PREFERCW_IMPORT_OPTIONS_FILE_FDA=Select this option if you want to use an existing client options file from an older client. TSM will import the values from your existing options file for you to edit in this wizard.
# 4135
DSI_PREFERCW_OPTIONS_FILE_NAME_LOCATION=Option File Name and Location
# 4136
DSI_PREFERCW_CHOOSE_OPTIONS_FILE_NAME_LOCATION=Choose the Option file name location
# 4137
DSI_PREFERCW_OPTIONS_FILE_NAME_LOCATION_FDA=Use the Option File Name and Location wizard panel to specify the name of the client options file to use.
# 4138
DSI_PREFERCW_ASK_OPTIONS_FILE_NAME=Specify the options file that TSM should use
# 4139
DSI_PREFERCW_ASK_OPTIONS_FILE_NAME_FDA=Specify the fully-qualified name of the client options file. The client options file is usually named dsm.opt
# 4140
DSI_PREFER_SAVING_SETTING=Saving '{0}' settings...
# 4141
DSI_PREFERCW_OPTIONS_FILE_NAME_BROWSE_FDA=Click this button if you want to open a file selection window and select the options file you want to use.
# 4142
DSI_PREFERCW_OPTIONS_FILE=Specify the options file that should be used
# 4143
DSI_PREFERCW_ASK_TSM_SERVER_NAME=TSM Server Name
# 4144
DSI_PREFERCW_ASK_TSM_SERVER_NAME_FDA=Use the TSM Server Name wizard panel to specify the name you want to use to identify a TSM server, and to begin a stanza containing parameters for that server.
# 4145
DSI_PREFER_SETTING_SAVED=Your '{0}' settings have been saved.
# 4146
DSI_PREFERCW_TSM_SERVER_NAME_FDA=In your client options file (dsm.opt), the TSM server name specifies which server, of those named in the client system options file (dsm.sys), to contact for services.
# 4147
DSI_PREFERCW_TSM_SERVER=Which TSM server do you want to access?
# 4148
DSI_PREFERCW_TSM_CLIENT_SERVER_COMMUNICATIONS=TSM Client/Server Communications
# 4149
DSI_PREFERCW_TSM_CLIENT_SERVER_COMMUNICATIONS_FDA=Use the TSM Client/Server Communications wizard panel to specify the communication method to use to communicate with the TSM server.
# 4150
DSI_PREFERCW_ASK_COMMUNICATIONS_METHOD=Which communication method do you want the TSM Client to use when communicating with the TSM Server?
# 4152
DSI_PREFERCW_COMMUNICATIONS_METHOD_FDA=Select TCP/IP for Transmission Control Protocol/Internet Protocol or Shared Memory when the TSM server and the TSM client are on the same workstation
# 4153
DSI_PREFERCW_ASK_COMMUNICATIONS_PARAMS=What Shared Memory parameters are the server using?
# 4154
DSI_PREFERCW_ASK_COMMUNICATION_PARAMETERS=Communication Parameters
# 4155
DSI_PREFERCW_ASK_COMMUNICATION_PARAMETERS_FDA=Use the TCP/IP Communication Parameters window to specify the parameters to use to communicate with the TSM server.
# 4156
DSI_PREFERCW_TSM_AUTHENTICATION=TSM Authentication
# 4157
DSI_PREFERCW_TSM_AUTHENTICATION_FDA=Use the Authentication wizard panel to specify the authentication options to use when the TSM client connects with the TSM server.
# 4159
DSI_PREFERCW_OPTION_FILE_TASK=Options File Task
# 4160
DSI_PREFERCW_OPTION_FILE_TASK_FDA=Select a task from the Options File Task wizard panel and click to the Next button.
# 4161
DSI_PREFERCW_TCP_IP_ADDRESS_AND_PORT=What is the TCP/IP address and port of the TSM server?
# 4162
DSI_PREFERCW_ASK_TSM_NODE_NAME=What is the TSM node name to use?
# 4163
DSI_PREFERCW_COMPLETING_WIZARD=Completing the TSM Client Configuration Wizard
# 4164
DSI_PREFERCW_COMPLETING_WIZARD_FDA=Use the Completing the TSM Client Configuration Wizard panel to apply your configuration settings.
# 4165
DSI_PREFERCW_WIZARD_COMPLETED=You have completed the client configuration.\nClick Finish to apply this configuration.
# 4166
DSI_PREFERCW_OPTION_REQUIRED=\nSpecify a value for this option before continuing.
# 4167
DSI_PREFERCW_OPTION_INVALID=\nAn invalid option has been specified. \nPlease correct it before continuing.
# 4168
DSI_PREFERCW_OPTION_REQUIRED_BETWEEN=\nPlease specify a value between {0} and {1}
# 4169
DSI_PREFERW_WEB_CAD_PORT=Web CAD Port
# 4170
DSI_PREFERW_WEB_AGENT_PORT=Web Agent Port
# 4171
DSI_PREFERW_PRIVILEGES=Privileges
# 4172
DSI_PREFERR_MAKE_SPARSE_FILE=Restore or retrieve file to sparse file
# 4173
DSI_PREFERH_NUM_MIG_THRESHOLD_PROC=Number of Processes for Automatic Threshold Migration
# 4174
DSI_PREFERH_NUM_RECONCILE_PROC=Number of Processes for Reconciliation
# 4175
DSI_CLUSTERCW_OPTIONS_FILE_NAME_LOCATION=Cluster Option File name and location
# 4176
DSI_CLUSTERCW_OPTION_FILE_NAME=Cluster Option File
# 4177
DSI_CLUSTERCW_SCHEDULER_WIZARD_COMPLETE=Scheduler Wizard Complete.
# 4178
DSI_CLUSTERCW_SCHEDULER_OPT_FILE_NAME=\nSpecify the options file that the Cluster Protection scheduler should use. \nNote: If file exists in specified location, file will be overwritten.
# 4179
DSI_CLUSTERCW_CLUSTER_GROUP_NA=Cluster Group: Not Available
# 4181
DSI_CLUSTERCW_CREATE_STARTED=Cluster configuration has started...
# 4182
DSI_CLUSTERCW_CREATE_COMPLETED=Cluster configuration has completed successfully...
# 4183
DSI_CLUSTERCW_CREATE_ERROR=Cluster configuration could not be completed.
# 4184
DSI_CLUSTERCW_REMOVE_STARTED=Cluster configuration is being removed...
# 4185
DSI_CLUSTERCW_REMOVE_COMPLETED=Cluster configuration has been removed successfully...
# 4186
DSI_CLUSTERCW_REMOVE_ERROR=Cluster configuration could not be removed.
# 4187
DSI_CLUSTERCW_GEN_SERVICE_CREATE=Done with creating generic service resource...
# 4188
DSI_CLUSTERCW_GEN_SERVICE_REMOVE=Done with removing generic service resource...
# 4189
DSI_CLUSTERCW_CLUSTER_GROUP=Cluster Group: 
# 4190
DSI_CLUSTERCW_OPT_FILE_NAME=Cluster Opt File Name
# 4191
DSI_CLUSTERCW_FILENAME_STF_DESC=Type the fully-qualified name of the client options file. The client options file is usually named dsm.opt.
# 4192
DSI_CLUSTERCW_OPT_FILE_A_DIRECTORY=The Cluster Options File name can not be a directory
# 4193
DSI_CLUSTERCW_DIR_NOT_FOUND=The specified path is invalid. Specify a valid directory and a filename
# 5003
DSI_PS_Invalid_DirMC=ANS5003S The management class assigned to directories does not exist.
DSI_PS_Invalid_DirMC_EXPLANATION=<p>The management class named on the DIRMC option does not exist in your assigned policy set on the server. The error log contains an entry showing the invalid management class name.</p>
DSI_PS_Invalid_DirMC_SYSACT=<p>processing stops.</p>
DSI_PS_Invalid_DirMC_URESP=<p>Remove the current DIRMC option from the client options file, then run DSMC QUERY MGMTCLASS -DETAIL to view information about available management classes. Make sure the management class you select has a backup copy group. If you have more than one TSM server, make sure you are connecting to the correct server. If you are unable to find a suitable management class, contact your TSM administrator for further assistance.</p>
# 5004
DSI_PS_No_CG_In_DirMC=ANS5004S There is no backup copy group in the management class used for directories. See the error log.
DSI_PS_No_CG_In_DirMC_EXPLANATION=<p>The DIRMC option names a management class that contains no backup copy group.</p>
DSI_PS_No_CG_In_DirMC_SYSACT=<p>processing stops.</p>
DSI_PS_No_CG_In_DirMC_URESP=<p>Remove the current DIRMC option from the client options file, then run DSMC QUERY MGMTCLASS -DETAIL to view information about available management classes. Make sure the management class you select has a backup copy group. If you have more than one TSM server, make sure you are connecting to the correct server. If you are unable to find a suitable management class, contact your TSM administrator for further assistance.</p>
# 5005
DSI_MissingToc=ANS5005E Table of contents information is not available for the selected images.
DSI_MissingToc_EXPLANATION=<p>An error occurred when the server tried to load a table of contents. Requested image or table of contents may have expired or been deleted on the server.</p>
DSI_MissingToc_SYSACT=<p>Processing stopped.</p>
DSI_MissingToc_URESP=<p>Start a new restore window to get current information.</p>
# 5006
DSI_No_Back_Copy_Groups=ANS5006W The policy set does not contain any backup copy groups. TSM is unable to continue the backup.
DSI_No_Back_Copy_Groups_EXPLANATION=<p>You tried to back up the files using a policy set that contained no backup management information.</p>
DSI_No_Back_Copy_Groups_SYSACT=<p>TSM did not back up the files.</p>
DSI_No_Back_Copy_Groups_URESP=<p>See your TSM administrator for assistance in associating your node with a policy set containing a management class that has a backup copy group. Then try the operation again. </p>
# 5007
DSI_No_Arch_Copy_Groups=ANS5007W The policy set does not contain any archive copy groups. TSM is unable to continue the archive.
DSI_No_Arch_Copy_Groups_EXPLANATION=<p>You tried to archive the files using a policy set that contains no archive management information.</p>
DSI_No_Arch_Copy_Groups_SYSACT=<p>TSM did not archive the files.</p>
DSI_No_Arch_Copy_Groups_URESP=<p>See your TSM administrator for assistance in associating your node with a policy set containing a management class that has an archive copy group. Then try the operation again. </p>
# 5008
DSI_Pw_Incorrect=ANS5008W Incorrect password entered
DSI_Pw_Incorrect_EXPLANATION=<p>You entered a password that was incorrect.</p>
DSI_Pw_Incorrect_SYSACT=<p>TSM cannot connect to the server without the correct password.</p>
DSI_Pw_Incorrect_URESP=<p>Reenter the password, or ask your system administrator for the current password.</p>
# 5009
DSI_Pw_DontMatch=ANS5009W New password entries are not the same
DSI_Pw_DontMatch_EXPLANATION=<p>During the change password, update password, or open registration dialog, the two entries for the new password were not the same.</p>
DSI_Pw_DontMatch_SYSACT=<p>The password was not changed on the server.</p>
DSI_Pw_DontMatch_URESP=<p>Backspace over both of the new passwords and reenter them, ensuring that they match.</p>
# 5010
DSI_RC_FileNameCasingConflict=File name case conflict
# 5011
DSI_Ba_Stopped=ANS5011I Backup stopped by user
# 5012
DSI_Ba_NoSpace=ANS5012E Server out of backup data storage space
DSI_Ba_NoSpace_EXPLANATION=<p>The server ran out of space in its backup data storage.</p>
DSI_Ba_NoSpace_SYSACT=<p>TSM cannot complete the requested backup operation. Any files displayed on the lower half of the backup activity panel were successfully backed up. </p>
DSI_Ba_NoSpace_URESP=<p>See your system administrator.</p>
# 5013
DSI_Ba_NoMem=ANS5013E Not enough memory for backup operation
DSI_Ba_NoMem_EXPLANATION=<p>TSM cannot allocate memory for the specified backup operation.</p>
DSI_Ba_NoMem_SYSACT=<p>TSM cannot complete the requested operation.</p>
DSI_Ba_NoMem_URESP=<p>Close all unneeded applications and retry the operation. Reducing the scope of queries and the amount of data returned might also help, or see your system administrator.</p>
# 5014
DSI_Ba_Complete=ANS5014I Backup completed
# 5015
DSI_Rs_Stopped=ANS5015I Restore stopped by user
# 5016
DSI_Rs_NoMem=ANS5016E Not enough memory for restore operation
DSI_Rs_NoMem_EXPLANATION=<p>TSM cannot allocate memory for the requested restore operation.</p>
DSI_Rs_NoMem_SYSACT=<p>TSM cannot complete the requested restore operation.</p>
DSI_Rs_NoMem_URESP=<p>Close all unneeded applications and retry the operation. Reducing the scope of queries and the amount of data returned can also help, or see your system administrator.</p>
# 5017
DSI_Rs_Complete=ANS5017I Restore completed
# 5018
DSI_Ar_NoMem=ANS5018E Not enough memory for archive operation
DSI_Ar_NoMem_EXPLANATION=<p>TSM cannot allocate memory for the requested archive operation.</p>
DSI_Ar_NoMem_SYSACT=<p>TSM cannot complete the archive operation.</p>
DSI_Ar_NoMem_URESP=<p>Close all unneeded applications and retry the operation. Reducing the scope of queries and the amount of data returned might also help, or see your system administrator.</p>
# 5019
DSI_Ar_Stopped=ANS5019I Archive stopped by user
# 5020
DSI_Ar_NoSpace=ANS5020E The TSM server is out of archive data storage space.
DSI_Ar_NoSpace_EXPLANATION=<p>The server ran out of space in its archive data storage.</p>
DSI_Ar_NoSpace_SYSACT=<p>TSM cannot complete the requested archive operation.</p>
DSI_Ar_NoSpace_URESP=<p>Report the problem to your TSM system administrator, who can allocate more resources to archive storage.</p>
# 5021
DSI_Ar_Complete=ANS5021I Archive completed
# 5022
DSI_Rt_Stopped=ANS5022I Retrieve stopped by user
# 5023
DSI_Rt_NoMem=ANS5023E Not enough memory for retrieve operation
DSI_Rt_NoMem_EXPLANATION=<p>TSM cannot allocate memory for the specified retrieve operation.</p>
DSI_Rt_NoMem_SYSACT=<p>TSM cannot complete the requested retrieve operation.</p>
DSI_Rt_NoMem_URESP=<p>Close all unneeded applications and retry the operation. Reducing the scope of queries and the amount of data returned might also help, or see your system administrator.</p>
# 5024
DSI_Rt_Complete=ANS5024I Retrieve completed
# 5025
DSI_InvCharsIn_NodeName=ANS5025E The node name contains invalid characters.
DSI_InvCharsIn_NodeName_EXPLANATION=<p>The specified node name has invalid characters.</p>
DSI_InvCharsIn_NodeName_SYSACT=<p>TSM canceled the current operation.</p>
DSI_InvCharsIn_NodeName_URESP=<p>Retry with another node name that has valid characters.</p>
# 5026
DSI_WildsAfter_InclExcl=ANS5026W MatchAllChar and MatchOneChar options MUST precede Include/Exclude options
DSI_WildsAfter_InclExcl_EXPLANATION=<p>The MatchAllChar and MatchOneChar options must precede any include-exclude options.</p>
DSI_WildsAfter_InclExcl_SYSACT=<p>The TSM client ends the current application.</p>
DSI_WildsAfter_InclExcl_URESP=<p>Move the MatchAllChar and MarchOneChar options before any include-exclude options.</p>
# 5028
DSI_RC_Successful=Successful completion
# 5029
DSI_RC_AbortSystemError=Server detected system error
# 5030
DSI_RC_AbortNoMatch=No objects on server match query
# 5031
DSI_RC_AbortByClient=Client aborted transaction
# 5032
DSI_RC_AbortActiveNotFound=Active object not found
# 5033
DSI_RC_AbortNoData=No data on server
# 5035
DSI_RC_AbortNodeInUse=Node in use
# 5036
DSI_RC_AbortExpdateTooLow=Expiration date too low
# 5037
DSI_RC_AbortDataOffline=Data offline
# 5038
DSI_RC_AbortExcludedBySize=Object too large for server limits
# 5039
DSI_RC_AbortNoStorSpaceSkip=Server out of data storage space
# 5040
DSI_RC_AbortMountNotPossibl=Server media mount not possible
# 5041
DSI_RC_AbortSizeEstimateExc=Size estimate exceeded
# 5042
DSI_RC_AbortDataUnavailable=Data unavailable to server
# 5043
DSI_RC_AbortRetry=Retry
# 5044
DSI_RC_RejectNoResources=All server sessions are currently in use
# 5045
DSI_RC_RejectVerifierExpired=Password expired
# 5047
DSI_RC_RejectDuplicateId=Node already logged onto server
# 5048
DSI_RC_ChooseFS=Please choose a filespace.
# 5049
DSI_RC_RejectServerDisabled=The server is disabled
# 5050
DSI_RC_RejectClosedRegistrat=The server is not configured to allow open registration
# 5051
DSI_RC_RejectClientDownlevel=The client code is down-level
# 5052
DSI_RC_RejectServerDownlevel=The server code is down-level
# 5053
DSI_RC_UserAbort=Operation stopped by user
# 5054
DSI_RC_NoMemory=Not enough memory for operation
# 5055
DSI_RC_FileNotFound=File not found
# 5056
DSI_RC_PathNotFound=Path not found
# 5057
DSI_RC_AccessDenied=Access denied
# 5058
DSI_RC_NoHandles=No file handles available
# 5059
DSI_RC_FileExists=File already exists
# 5060
DSI_RC_InvalidParm=Invalid parameter passed
# 5061
DSI_RC_InvalidHandle=Invalid file handle passed\nReport how you got this
# 5062
DSI_RC_DiskFull=ANS5062E Disk full
DSI_RC_DiskFull_EXPLANATION=<p>Operation has stopped because the destination disk is full.</p>
DSI_RC_DiskFull_SYSACT=<p>Processing stopped.</p>
DSI_RC_DiskFull_URESP=<p>Free up disk space and retry the operation</p>
# 5063
DSI_RC_ProtocolViolation=Protocol violation\nReport how you got this
# 5064
DSI_RC_UnknownError=Unknown system error. Please check the TSM Error Log for any additional information
# 5065
DSI_RC_UnexpectedError=Unexpected error. Please check the TSM Error Log for any additional information
# 5066
DSI_RC_FileBeingExecuted=File is being executed, write permission denied
# 5067
DSI_RC_DirNoSpace=Directory can not be expanded
# 5068
DSI_RC_FileNameTooLong=File name too long
# 5069
DSI_RC_FileSpaceLocked=Filespace is locked by system
# 5070
DSI_RC_Finished=Processing complete
# 5071
DSI_RC_UnknownFormat=Unknown data format
# 5072
DSI_RC_NoAuthorization=Request denied; no authorization in place
# 5073
DSI_RC_FileSpaceNotFound=Filespace not found
# 5074
DSI_RC_TxnAborted=Transaction aborted
# 5075
DSI_RC_SubdirAsFile=Directory name exists as file
# 5076
DSI_RC_ProcessNoSpace=Disk space limit for this process reached
# 5077
DSI_RC_PathTooLong=Path name too long
# 5078
DSI_RC_NotCompressed=File thought to be compressed was not\nReport how you got this
# 5079
DSI_RC_TooManyBits=File compressed on a different client machine with more memory available
# 5080
DSI_RC_SystemError=Internal system error\n. Please check the TSM Error Log for any additional information.
# 5081
DSI_RC_NoServerResources=All server sessions are currently in use
# 5082
DSI_RC_FSNotKnown=Filespace not known to server
# 5083
DSI_RC_WildcardDir=ANS5083E Drive specification contains wildcard character.\n
DSI_RC_WildcardDir_EXPLANATION=<p>Drive name shouldn't contain wildcard character.</p>
DSI_RC_WildcardDir_SYSACT=<p>Wildcarded objects skipped.</p>
DSI_RC_WildcardDir_URESP=<p>Use valid drive specification.</p>
# 5085
DSI_RC_AuthFailure=Authentication failure
# 5086
DSI_RC_Continue=Continue processing\nReport how you got this
# 5087
DSI_RC_Overwrite=Overwrite file\nReport how you got this
# 5088
DSI_RC_NoOverwrite=Do not overwrite file\nReport how you got this
# 5089
DSI_RC_Retry=Retry operation\nReport how you got this
# 5090
DSI_RC_Skip=Skip current operation\nReport how you got this
# 5091
DSI_RC_AbortWaitForSpace=ANS5091S The TSM server does not currently have space in the storage pool for this file. This might be a temporary condition.
DSI_RC_AbortWaitForSpace_EXPLANATION=<p>This message is typically issued when the storage pool in which the data is being placed does not have sufficient to store the data, but that the space will be available soon. For example, a storage pool migration may free up sufficient space to store the data.</p>
DSI_RC_AbortWaitForSpace_SYSACT=<p>TSM ends the current operation.</p>
DSI_RC_AbortWaitForSpace_URESP=<p>This is possibly a temporary condition. Try the operation again at a later time. If the error persists, contact your TSM administrator, who can examine server console and error logs to locate the cause of the problem.</p>
# 5092
DSI_RC_AbortNoStorSpaceStop=ANS5092S Server out of data storage space.
DSI_RC_AbortNoStorSpaceStop_EXPLANATION=<p>The server does not have any more space available to store the object. </p>
DSI_RC_AbortNoStorSpaceStop_SYSACT=<p>TSM ended the current operation.</p>
DSI_RC_AbortNoStorSpaceStop_URESP=<p>Report to your system administrator that a storage pool on the server is full.</p>
# 5093
DSI_RC_Reject_License_Max=ANS5093S SLM_LICENSE_EXCEEDED: The client licenses for TSM are exceeded. See your TSM administrator.
DSI_RC_Reject_License_Max_EXPLANATION=<p>Adding a new enrollment will exceed the product license count for this TSM server.</p>
DSI_RC_Reject_License_Max_SYSACT=<p>The client enrollment or connection request ends.</p>
DSI_RC_Reject_License_Max_URESP=<p>See your TSM administrator to delete unused enrollments or negotiate an increase in the number of allowed licenses for your server.</p>
# 5094
DSI_RC_RejectServNoMemory=ANS5094E Session Rejected. Sufficient server memory is not available.
DSI_RC_RejectServNoMemory_EXPLANATION=<p>The server does not have enough memory to allow your client to establish a connection with the server.</p>
DSI_RC_RejectServNoMemory_SYSACT=<p>Session was not started.</p>
DSI_RC_RejectServNoMemory_URESP=<p>Retry later or see your system administrator.</p>
# 5095
DSI_RC_UnknownFileDataType=Structured file data type is unknown
# 5096
DSI_RC_BufferOverflow=Data buffer overflow
# 5097
DSI_RC_ReadFailure=Error reading file
# 5098
DSI_RC_FileChanging=File changing during operation
# 5099
DSI_RC_NoCompressMemory=Compress/Expand out of memory
# 5100
DSI_RC_CompressGrew=Compression grew
# 5102
DSI_RC_ConnTimedout=TCP/IP connection attempt timed out
# 5103
DSI_RC_ConnRefused=TCP/IP connection refused by host
# 5104
DSI_RC_BadHostName=TCP/IP invalid host name
# 5105
DSI_RC_NetworkUnreachable=TCP/IP host unreachable
# 5106
DSI_RC_SessTerminated=Communication session terminated
# 5107
DSI_RC_WriteFailure=Error writing file
# 5108
DSI_RC_OverFileSizeLimit=File over user or system size limit
# 5109
DSI_RC_RejectIDInUse=Client ID is already in use
# 5110
DSI_RC_FIOError=File input/output error
# 5111
DSI_RC_InvCommMethod=Invalid communications method
# 5112
DSI_RC_WillAbort=Transaction will be aborted\nReport how you got this
# 5113
DSI_RC_FSWriteLocked=Filespace is write protected
# 5115
DSI_RC_FSNotReady=Filespace not ready
# 5116
DSI_RC_FSIsBad=Filespace is invalid
# 5117
DSI_RC_Abort_No_Log_Space=The server does not have enough recovery log space to continue the current activity.
# 5118
DSI_RC_Abort_No_DB_Space=The server does not have enough database space to continue the current activity.
# 5119
DSI_RC_Reject_No_Log_Space=Session Rejected: The server does not have enough recovery log space to allow a connection to be established.
# 5120
DSI_RC_Reject_No_DB_Space=Session Rejected: The server does not have enough database space to allow a connection to be established.
# 5121
DSI_RC_AbortNoServMemory=The server does not have enough memory to continue current activity.
# 5122
DSI_RC_AbortFSNotDefined=ANS5122E The specified filespace does not exist on the server. The filespace might have been deleted by another client or an administrator.
DSI_RC_AbortFSNotDefined_EXPLANATION=<p>The specified filespace does not exist on the server. Your administrator might have already deleted the filespace or another client using your client's node name might have deleted it.</p>
DSI_RC_AbortFSNotDefined_SYSACT=<p>TSM ends the current operation.</p>
DSI_RC_AbortFSNotDefined_URESP=<p>The filespace you selected does not exist any more. See your TSM administrator for help in finding how the filespace was deleted.</p>
# 5123
DSI_RC_AbortNodeAlreadyDef=ANS5123S Open registration failed because the specified node name is already defined in the server.
DSI_RC_AbortNodeAlreadyDef_EXPLANATION=<p>Open registration failed because a node is defined on the server with the same name.</p>
DSI_RC_AbortNodeAlreadyDef_SYSACT=<p>TSM canceled the current operation.</p>
DSI_RC_AbortNodeAlreadyDef_URESP=<p>Retry with another node name.</p>
# 5124
DSI_RC_AbortNoDefaultDomain=ANS5124S Open registration failed because there is no default domain.
DSI_RC_AbortNoDefaultDomain_EXPLANATION=<p>Open registration failed because a default policy domain does not exist in which to place your node. A default policy domain is required to fully support open node registration.</p>
DSI_RC_AbortNoDefaultDomain_SYSACT=<p>TSM cancels the current operation.</p>
DSI_RC_AbortNoDefaultDomain_URESP=<p>See your TSM administrator for assistance in registering your node.</p>
# 5125
DSI_RC_AbortInvalidNodename=ANS5125S Open registration failed because an invalid node name was specified.
DSI_RC_AbortInvalidNodename_EXPLANATION=<p>Open registration failed because the specified node name has invalid characters. </p>
DSI_RC_AbortInvalidNodename_SYSACT=<p>TSM canceled the current operation.</p>
DSI_RC_AbortInvalidNodename_URESP=<p>Retry with another node name that does not have any invalid characters. </p>
# 5126
DSI_Duplicate_Volname=ANS5126S Filespaces with duplicate names are not supported. Please unmount the duplicate filespace.
DSI_Duplicate_Volname_EXPLANATION=<p>The selected filespace has a duplicate volume label. Because TSM uses the volume label to keep track of backup/archive information, it cannot back up or archive files from a filespace with a duplicate volume label.</p>
DSI_Duplicate_Volname_SYSACT=<p>TSM cannot select the volume.</p>
DSI_Duplicate_Volname_URESP=<p>If the filespace needs to be available to the system, exit TSM, and assign a volume label to the filespace. Restart TSM and retry the operation. Otherwise, unmount the duplicate filespace.</p>
# 5127
DSI_Replace_Dsm_Opt_File=ANS5127I TSM has detected an incomplete setup! \n\nThe system options file 'dsm.sys' was not found, while the client options file '{0}' exists! \n\nThe wizard will guide you through the configuration process of the initial basic TSM client options files replacing your current option file. Would you like to continue?
# 5128
DSI_MC_FailBackCG=ANS5128E The management class for this file did not have a backup copy group.
DSI_MC_FailBackCG_EXPLANATION=<p>For backup operations, a file may only be bound to a management class that has a backup copy group.</p>
DSI_MC_FailBackCG_SYSACT=<p>TSM did not back up the file.</p>
DSI_MC_FailBackCG_URESP=<p>See your TSM system administrator for assistance in finding a management class with the required copy group. The administrator may also define such a management class for you.</p>
# 5129
DSI_MC_FailArchCG=ANS5129E The management class for this file did not have an archive copy group specified.
DSI_MC_FailArchCG_EXPLANATION=<p>For archive operations, a file may only be bound to a management class that has an archive copy group.</p>
DSI_MC_FailArchCG_SYSACT=<p>TSM did not archive the file.</p>
DSI_MC_FailArchCG_URESP=<p>See your TSM system administrator for assistance in finding a management class with the required copy group. The administrator may also define such a management class for you.</p>
# 5130
DSI_FsDel_NoFileSys=ANS5130W No filespaces selected for deletion
DSI_FsDel_NoFileSys_EXPLANATION=<p>You requested a deletion operation without selecting a client domain.</p>
DSI_FsDel_NoFileSys_SYSACT=<p>TSM cannot perform a deletion without a domain selected.</p>
DSI_FsDel_NoFileSys_URESP=<p>Select the volumes you want to delete and retry the operation.</p>
# 5131
DSI_File_Skipped_By_User=File '{0}{1}{2}' skipped by user
# 5132
DSI_FsDel_Cancelled=ANS5132I Filespace deletion canceled by user
# 5133
DSI_FsDel_Complete=ANS5133I Filespace '{0}' was deleted
# 5134
DSI_FsDel_NoPermToDelFS=ANS5134E Unable to delete the filespace because this node does not have permission to delete archived data and/or backed up data.
DSI_FsDel_NoPermToDelFS_EXPLANATION=<p>You tried to delete a filespace that you do not have permission to access. </p>
DSI_FsDel_NoPermToDelFS_SYSACT=<p>TSM canceled the operation.</p>
DSI_FsDel_NoPermToDelFS_URESP=<p>Ensure that you specify the correct filespace, or specify a filespace you have access to.</p>
# 5135
DSI_ArDel_Stopped=ANS5135I Archive delete stopped by user
# 5137
DSI_NoObjToRestore=No objects to restore.
# 5138
DSI_ArDel_Complete=ANS5138I Archive delete completed
# 5139
DSI_ArchDel_NoPerm=ANS5139E Your node does not have permission to delete archived files.
DSI_ArchDel_NoPerm_EXPLANATION=<p>Your node is registered at the server with the ARCHDELETE option set to 'no'. Therefore your node is not allowed by the server to delete archived files.</p>
DSI_ArchDel_NoPerm_SYSACT=<p>TSM did not delete the archived files.</p>
DSI_ArchDel_NoPerm_URESP=<p>See your TSM system administrator. The administrator has authority to delete archived files, and can also grant that authority to your node.</p>
# 5140
DSI_ArDel_Question=You are about to delete the selected files from the archive data storage. Do you wish to continue?
# 5142
DSI_FSDELETE_Question=ALL the data on the server for filespace '{0}' will be deleted! ALL DATA will be UNRECOVERABLE for this filespace. Do you still wish to delete this filespace?
# 5143
DSI_PWUpdated=Password successfully changed
# 5144
DSI_PW_Invalid=New password cannot be blank.
# 5145
DSI_Restart_Not_Possible=ANS5145W Server cannot restart the last restore request. Do you want to restore without restart?
DSI_Restart_Not_Possible_EXPLANATION=<p>The restart restore token has expired. The server cannot restart the restore from where it last ended.</p>
DSI_Restart_Not_Possible_SYSACT=<p>Processing stopped; waiting for user intervention.</p>
DSI_Restart_Not_Possible_URESP=<p>Retry the request without restart or abort the request.</p>
# 5146
DSI_Accessing_Another_User=ANS5146W You cannot perform this operation while accessing data for another node. Do you wish to switch back to accessing your own node?
DSI_Accessing_Another_User_EXPLANATION=<p>The user cannot perform the selected operation while accessing another users data.</p>
DSI_Accessing_Another_User_SYSACT=<p>Processing stopped; waiting for user intervention.</p>
DSI_Accessing_Another_User_URESP=<p>Answer "Yes" to switch back to accessing the server as the original node. </p>
# 5147
DSI_No_Restart_Restores=There are no restore sessions available that can be restarted.
# 5148
DSI_Archive_Conversion=ANS5148W The server needs to do a one-time conversion of your archive data before you can continue. This operation may take a long time, and cannot be canceled once it has started. Are you willing to wait for the conversion to complete?
DSI_Archive_Conversion_EXPLANATION=<p>The server must do a conversion of the archive data before continuing. The conversion could take a long time, and cannot be canceled once it is started. </p>
DSI_Archive_Conversion_SYSACT=<p>Processing stopped; waiting for user intervention.</p>
DSI_Archive_Conversion_URESP=<p>Answer <q>Yes</q> to start the archive data conversion. If you answer <q> No</q>, the current operation will be canceled.</p>
# 5149
DSI_PNEW_Invalid=The length of new password should be in the range of 1 to 63.
# 5150
DSI_Duplicate_Restore=ANS5150E An active restore for the same source file specification exists. Unable to continue with this request.
DSI_Duplicate_Restore_EXPLANATION=<p>Currently, there is an active restore for the same source file specification. Another restore of the same source file specification cannot be started. </p>
DSI_Duplicate_Restore_SYSACT=<p>The requested restore fails.</p>
DSI_Duplicate_Restore_URESP=<p>Start another restore with a different source file specification.</p>
# 5151
DSI_Abort_Restore_In_Progress=ANS5151S This node currently has a pending restartable restore session. The requested operation cannot complete until this session either completes or is canceled.
DSI_Abort_Restore_In_Progress_EXPLANATION=<p>This operation can not be completed because a restartable restore session is pending. The operation is not allowed because the restartable session and the current operation affect the same file space.</p>
DSI_Abort_Restore_In_Progress_SYSACT=<p>TSM ended the current operation.</p>
DSI_Abort_Restore_In_Progress_URESP=<p>Issue the Query Restore command to view a list of your restartable restore sessions in the server database. Issue the Cancel Restore command to cancel any unneeded restartable restore sessions.</p>
# 5152
DSI_RC_Reject_Inv_Client_Type=ANS5152S Session Rejected: The server is not licensed for this platform type. See your TSM administrator.
DSI_RC_Reject_Inv_Client_Type_EXPLANATION=<p>The server license governs the types of client that can connect to it. The license for this server does not include the requesting client type.</p>
DSI_RC_Reject_Inv_Client_Type_SYSACT=<p>The client enrollment or connection request ends.</p>
DSI_RC_Reject_Inv_Client_Type_URESP=<p>See your TSM administrator who must upgrade the server license to accept your client type.</p>
# 5153
DSI_RC_Reject_UnicodeNotAllowed=ANS5153E Session Rejected: The server does not allow a signon as a Unicode enabled client.
DSI_RC_Reject_UnicodeNotAllowed_EXPLANATION=<p>The client cannot establish a connection to the server because of a unicode enabling mismatch between server and client.</p>
DSI_RC_Reject_UnicodeNotAllowed_SYSACT=<p>Session was not started.</p>
DSI_RC_Reject_UnicodeNotAllowed_URESP=<p>See your system administrator immediately.</p>
# 5154
DSI_MC_Excluded_Implicit=ANS5154I File is implicitly excluded
# 5155
DSI_TCA_No_Pswd_File=ANS5155E Valid password not available. The TSM administrator for your system must run TSM and enter the password to store it locally.
DSI_TCA_No_Pswd_File_EXPLANATION=<p>The file containing the stored password for the specified server <mv>server-name </mv> is unavailable.</p>
DSI_TCA_No_Pswd_File_SYSACT=<p>TSM ends.</p>
DSI_TCA_No_Pswd_File_URESP=<p>The TSM administrator for your system must set and store a new password. </p>
# 5156
DSI_Lose_Selection_Criteria=Changing criteria will cause the current selections to be lost
# 5158
DSI_FilespaceDelete_InProgress=ANS5158S Filespace deletion is in progress. Try again later.
DSI_FilespaceDelete_InProgress_EXPLANATION=<p>The filespace is in the process of being deleted.</p>
DSI_FilespaceDelete_InProgress_SYSACT=<p>TSM cannot complete the requested operation.</p>
DSI_FilespaceDelete_InProgress_URESP=<p>Try the operation again later. If the filespace was being deleted, it could take awhile for it to complete. If the problem continues, report the problem to your system administrator.</p>
# 5159
DSI_RC_LoopedSymLink=Too many symbolic links
# 5160
DSI_OBJINFO_TOC=Table of Contents:
# 5161
DSI_NAS_DIFF_IMAGE=NAS Differential Image
# 5162
DSI_NAS_FULL_IMAGE=NAS Full Image
# 5163
DSI_RC_NotFileOwner=Not File Owner
# 5164
DSI_DuplicateVolume=ANS5164E Backup or archive of drives with duplicate volume labels is not allowed.
DSI_DuplicateVolume_EXPLANATION=<p>You tried to back up or archive a drive that has a duplicate volume label. Because TSM uses the volume label to keep track of backup or archive information, it cannot back up or archive files from a drive with a duplicate volume label.</p>
DSI_DuplicateVolume_SYSACT=<p>TSM cannot select the drive for backup or archive operations.</p>
DSI_DuplicateVolume_URESP=<p>If the volume needs to be available to the system, exit TSM and assign a unique volume label to the drive. Restart TSM and try the operation again. </p>
# 5165
DSI_DriveHasNoLabel=ANS5165E Drive has no volume label. Backup/Archive not allowed.
DSI_DriveHasNoLabel_EXPLANATION=<p>You tried to backup or archive a drive that has no volume label.</p>
DSI_DriveHasNoLabel_SYSACT=<p>TSM rejected the selected drive.</p>
DSI_DriveHasNoLabel_URESP=<p>If the drive is a floppy drive, place a disk with a volume label in it and retry the operation. If the disk is a hard drive, ensure the drive has a volume label, and retry the operation.</p>
# 5166
IE_UNABLE_TO_REMOVE_STMT=ANS5166E An error occurred while removing include-exclude statement '{0}'. Please try again.
IE_UNABLE_TO_REMOVE_STMT_EXPLANATION=<p>There was a problem with removing the include-exclude statement. Make sure that your include-exclude statement is valid.</p>
IE_UNABLE_TO_REMOVE_STMT_SYSACT=<p>No include-exclude statement was removed. Waiting for user action.</p>
IE_UNABLE_TO_REMOVE_STMT_URESP=<p> Retry your operation. If you see this error message again, contact your system administrator</p>
# 5170
DSI_SCHWIZ_TITLE=TSM Scheduler Wizard
# 5175
DSI_RC_SocketFile=Socket File: Skipped
# 5176
VMBACKUP_VM_Operation_Already_In_Progress=ANS5176W The requested virtual machine operation cannot be performed because a virtual machine backup or restore operation is already in progress. Please retry the operation after the first operation completes.\n
VMBACKUP_VM_Operation_Already_In_Progress_EXPLANATION=<p>A virtual machine operation is already in progress, so the requested virtual machine operation cannot be performed until the first operation complets.</p>
VMBACKUP_VM_Operation_Already_In_Progress_SYSACT=<p>Processing stops</p>
VMBACKUP_VM_Operation_Already_In_Progress_URESP=<p>Wait for the first virtual machine operation to complete, and then restart the current request.</p>
# 5178
DSI_Restart_Rsm_Service_Failed=ANS5178E Restart of the RSM service failed. Restart the RSM service manually.\n
DSI_Restart_Rsm_Service_Failed_EXPLANATION=<p>RSM database files have been restored from the TSM server and imported. TSM has tried to restart the RSM service on the user's behalf but has run into a problem.</p>
DSI_Restart_Rsm_Service_Failed_SYSACT=<p>Processing stopped.</p>
DSI_Restart_Rsm_Service_Failed_URESP=<p>Restart the RSM service manually.</p>
# 5179
DSI_UNABLE_TO_START_DSM=ANS5179E TSM is unable to continue. Exiting program.
DSI_UNABLE_TO_START_DSM_EXPLANATION=<p>TSM ran into a problem and is unable to continue. This error message is usually preceded by other error messages. Resolve those errors and try again.</p>
DSI_UNABLE_TO_START_DSM_SYSACT=<p>Program terminates.</p>
DSI_UNABLE_TO_START_DSM_URESP=<p>Fix the problem(s) that preceded this message and then restart TSM.</p>
# 5180
DSI_RC_InvalidFileName=Object name contains one or more unrecognized characters and is not valid.
# 5181
DSI_ObjectSet_Unsupported_Selection=ANS5181E Invalid selection; A specific backup set must be selected.
DSI_ObjectSet_Unsupported_Selection_EXPLANATION=<p> A selection was made that might result in multiple backup sets being restored at the same time, but restoring multiple backup sets at the same time is not supported. </p>
DSI_ObjectSet_Unsupported_Selection_SYSACT=<p> The backup set restore was not performed. </p>
DSI_ObjectSet_Unsupported_Selection_URESP=<p> Select a specific backup set to be restored. </p>
# 5182
DSI_ObjectSet_Multiple_Sets_Not_Supported=ANS5182E Multiple backup sets can not be restored at the same time.
DSI_ObjectSet_Multiple_Sets_Not_Supported_EXPLANATION=<p> Multiple backup sets were selected to be restored, but restoring multiple backup sets at the same time is not supported. </p>
DSI_ObjectSet_Multiple_Sets_Not_Supported_SYSACT=<p> The backup set restore was not performed. </p>
DSI_ObjectSet_Multiple_Sets_Not_Supported_URESP=<p> Select a specific backup set to be restored. </p>
# 5183
DSI_RESTORE_ONE_OBJECT_TYPE=ANS5183W Objects of different types cannot be restored at the same time.
DSI_RESTORE_ONE_OBJECT_TYPE_EXPLANATION=<p>Restoring objects of different types is not allowed. For example, restoring Backup Sets and regular file objects at the same time is not possible.</p>
DSI_RESTORE_ONE_OBJECT_TYPE_SYSACT=<p>No processing takes place.</p>
DSI_RESTORE_ONE_OBJECT_TYPE_URESP=<p>Select objects of the same type to perform restore operation. </p>
# 5184
DSI_RC_IllegalOperationOnObject=ANS5184E Illegal Operation On Following Object: {0}\n
DSI_RC_IllegalOperationOnObject_EXPLANATION=<p>Requested operation cannot be performed on this object.</p>
DSI_RC_IllegalOperationOnObject_SYSACT=<p>This object will be skipped.</p>
DSI_RC_IllegalOperationOnObject_URESP=<p>Try another operation on this object, or try the same operation on another object.</p>
# 5186
DSI_RC_VSSRejectServerDownlevel=ANS5186E Server is downlevel, System Services and System State backup disabled for this session.
DSI_RC_VSSRejectServerDownlevel_EXPLANATION=<p>The operation cannot be performed because server version is downlevel. </p>
DSI_RC_VSSRejectServerDownlevel_SYSACT=<p>System Service and System State backup is disabled for this session.</p>
DSI_RC_VSSRejectServerDownlevel_URESP=<p>Must use level 5.2.0 or higher server.</p>
# 5191
DSI_SysObj_Ntds_Backup_Offline=ANS5191E NT Active Directory is not online. Offline backup is not supported.\n
DSI_SysObj_Ntds_Backup_Offline_EXPLANATION=<p>NT Active Directory is not online when performing a backup operation. Offline backup is not supported.</p>
DSI_SysObj_Ntds_Backup_Offline_SYSACT=<p>Processing stopped.</p>
DSI_SysObj_Ntds_Backup_Offline_URESP=<p>Reboot computer and turn on Active Directory, and try the operation again.</p>
# 5192
DSI_SysObj_Ntds_Restore_Online=ANS5192E NT Active Directory is online. Online restore is not supported.\n
DSI_SysObj_Ntds_Restore_Online_EXPLANATION=<p>NT Active Directory is online when performing a restore operation. Online restore is not supported.</p>
DSI_SysObj_Ntds_Restore_Online_SYSACT=<p>Processing stopped.</p>
DSI_SysObj_Ntds_Restore_Online_URESP=<p>Reboot computer and enter Active Directory repair mode, then try the operation again.</p>
# 5193
DSI_SysObj_CertSrv_Backup_Offline=ANS5193E Certificate Services is not online. Offline backup is not supported.\n
DSI_SysObj_CertSrv_Backup_Offline_EXPLANATION=<p>Certificate Services is not online when performing a backup operation. Offline backup is not supported.</p>
DSI_SysObj_CertSrv_Backup_Offline_SYSACT=<p>Processing stopped.</p>
DSI_SysObj_CertSrv_Backup_Offline_URESP=<p>Start Certificate Services and try the operation again.</p>
# 5194
DSI_SysObj_CertSrv_Restore_Online=ANS5194E Certificate Services is online. Online restore is not supported.\n
DSI_SysObj_CertSrv_Restore_Online_EXPLANATION=<p>Certificate Services is online when performing a restore operation. Online restore is not supported.</p>
DSI_SysObj_CertSrv_Restore_Online_SYSACT=<p>Processing stopped.</p>
DSI_SysObj_CertSrv_Restore_Online_URESP=<p>Stop Certificate Services and try the operation again.</p>
# 5195
DSI_CFGWIZ_FAILED=Data was written to the options file, however there was at least one error that must be fixed before we can connect to a server.
# 5196
DSI_KeyPw_Incorrect=ANS5196W Invalid encryption key password entered.
DSI_KeyPw_Incorrect_EXPLANATION=<p> The encryption key password supplied does not meet the TSM requirements. This key can be up to 63 bytes in length and include the following characters: A-Z Any letter, A through Z, uppercase or lowercase 0-9 Any number, 0 through 9 + Plus . Period _ Underscore - Hyphen & Ampersand </p>
DSI_KeyPw_Incorrect_SYSACT=<p>TSM allows you to try again.</p>
DSI_KeyPw_Incorrect_URESP=<p>Enter the correct encryption key password.</p>
# 5204
DSI_RESTORE_ONE_BACKUPSET_TYPE=ANS5204W Only one backup set may be selected for restore.
DSI_RESTORE_ONE_BACKUPSET_TYPE_EXPLANATION=<p>Restoring multiple backup sets is not allowed. Only one backup set may be selected and restored.</p>
DSI_RESTORE_ONE_BACKUPSET_TYPE_SYSACT=<p>No processing takes place.</p>
DSI_RESTORE_ONE_BACKUPSET_TYPE_URESP=<p>Only one backup set may be selected for restore. </p>
# 5208
DSI_Invalid_Date=ANS5208E An invalid date or time was entered.
DSI_Invalid_Date_EXPLANATION=<p>An invalid date or time value was entered. Either the syntax of the value was not correct, or an actual value (for example, <q>45</q> for month) was invalid. </p>
DSI_Invalid_Date_SYSACT=<p>Processing stops.</p>
DSI_Invalid_Date_URESP=<p>Identify and correct the invalid date or time value. Refer to the user's guide of the corresponding platform for the correct date syntax.</p>
# 5209
DSI_SysObj_Sysvol_Backup_Failed=ANS5209E System Volume backup failed.\n
DSI_SysObj_Sysvol_Backup_Failed_EXPLANATION=<p>IBM Tivoli Storage Manager encountered an error while backing up files of the Windows 2000 System Volume</p>
DSI_SysObj_Sysvol_Backup_Failed_SYSACT=<p>Processing stopped.</p>
DSI_SysObj_Sysvol_Backup_Failed_URESP=<p>Examine the Windows 2000 File Replication Service Event log to insure the system volume was successfully initialized. Restart the service and retry the backup operation</p>
# 5210
DSI_SysObj_Sysvol_Restore_Failed=ANS5210E System Volume restore failed.\n
DSI_SysObj_Sysvol_Restore_Failed_EXPLANATION=<p>IBM Tivoli Storage Manager encountered an error while restoring files of the Windows 2000 System Volume</p>
DSI_SysObj_Sysvol_Restore_Failed_SYSACT=<p>Processing stopped.</p>
DSI_SysObj_Sysvol_Restore_Failed_URESP=<p>Examine the Windows 2000 File Replication Service Event log to insure the system volume was successfully initialized. Restart the service and retry the restore operation.</p>
# 5211
DSI_Cluster_Service_Offline=ANS5211E The cluster service is offline. The cluster service must be online to perform an authoritative cluster database restore operation.
DSI_Cluster_Service_Offline_EXPLANATION=<p> The cluster service must be online to restore the cluster database. Tivoli Storage Manager tried to start the service and failed. It is possible that an authoritative restore cannot be done. </p>
DSI_Cluster_Service_Offline_SYSACT=<p>Processing stops.</p>
DSI_Cluster_Service_Offline_URESP=<p>Start the cluster service and retry the operation.</p>
# 5212
DSI_Abort_Fs_Rename_Error=ANS5212E An error occurred while trying to rename file space.\n
DSI_Abort_Fs_Rename_Error_EXPLANATION=<p>This operation can not be completed because the file space could not be renamed.</p>
DSI_Abort_Fs_Rename_Error_SYSACT=<p>TSM ended the current operation.</p>
DSI_Abort_Fs_Rename_Error_URESP=<p>Contact system administrator for more information.</p>
# 5215
DSI_RC_IllegalOperation=ANS5215E {0} is not allowed on object '{1}'.\nObject is not sent to the server.\n
DSI_RC_IllegalOperation_EXPLANATION=<p>The operation could not be performed on this object. For example, if this is an image operation, the selected path is a file or a directory and therefore is not a valid object for image operations. </p>
DSI_RC_IllegalOperation_SYSACT=<p>This object is skipped.</p>
DSI_RC_IllegalOperation_URESP=<p>Verify that the object named is of a type supported by the command. For example, if a filespace name is required but a directory name was given, change the name so it includes only the filespace name.</p>
# 5216
TCPIP_connection_error=ANS5216E Could not establish a TCP/IP connection with address '{0}:{1}'. The TCP/IP error is '{2}' (errno = {3}). \n
TCPIP_connection_error_EXPLANATION=<p>A TCP/IP connection was attempted with a server or agent program and failed.</p>
TCPIP_connection_error_SYSACT=<p>Processing stops.</p>
TCPIP_connection_error_URESP=<p>Ensure that the target TCP/IP address and port number is correct. Check to ensure that a TSM server or agent has been started at the target TCP/IP address and is configured to listen at the port listed in the message.</p>
# 5217
DSI_BackDel_NoPerm=ANS5217E Your node does not have permission to delete backed up files.\n
DSI_BackDel_NoPerm_EXPLANATION=<p>You cannot delete backed up files unless your TSM administrator has authorized your node to do so.</p>
DSI_BackDel_NoPerm_SYSACT=<p>TSM does not delete the backed up files.</p>
DSI_BackDel_NoPerm_URESP=<p>Use the DSMC QUERY SESSION command to verify your authorization. Ask your TSM administrator to provide the necessary authorization.</p>
# 5218
DSI_RC_CompressedDataCorrupted=The compressed file is corrupted and cannot be expanded correctly.
# 5219
DSI_RESTORE_FROM_MULTI_GROUP=ANS5219W Objects of different groups cannot be restored at the same time.
DSI_RESTORE_FROM_MULTI_GROUP_EXPLANATION=<p>Restoring objects of different groups is not allowed.</p>
DSI_RESTORE_FROM_MULTI_GROUP_SYSACT=<p>No processing takes place.</p>
DSI_RESTORE_FROM_MULTI_GROUP_URESP=<p>Select objects of the same group to perform restore operation. </p>
# 5220
DSI_UNSUPPORTED_FILE_TYPE=The file is not recognized by the system as a disk file and cannot be processed.
# 5222
DSI_RC_DescTooLong=ANS5222E The archive description exceeds 254 characters.\n
DSI_RC_DescTooLong_EXPLANATION=<p> TSM places a maximum length of 254 characters on the archive description. </p>
DSI_RC_DescTooLong_SYSACT=<p>processing stops.</p>
DSI_RC_DescTooLong_URESP=<p>Issue the command again and specify a shorter valid archive description.</p>
# 5223
DSI_RC_FileOrDirectoryIsCorrupted=The object is corrupted
# 5226
VMBACKUP_Backup_Operation_Failed=ANS5226E The virtual machine backup operation failed.\n
VMBACKUP_Backup_Operation_Failed_EXPLANATION=<p>The virtual machine backup operation failed. Check the error log for details on why the operation failed.</p>
VMBACKUP_Backup_Operation_Failed_SYSACT=<p>Processing stops</p>
VMBACKUP_Backup_Operation_Failed_URESP=<p>Review the console output and error logs for the details on the problem. Fix any issues and restart the operation.</p>
# 5227
VMBACKUP_Invalid_Snaptype=ANS5227E TSM detected an error where both a snapshot name was specified, and a request to create a snapshot were specified.\n
VMBACKUP_Invalid_Snaptype_EXPLANATION=<p>Either a snapshot name should be specified, or a request for TSM to create the snapshot should be specified, but not both.</p>
VMBACKUP_Invalid_Snaptype_SYSACT=<p>Processing stops.</p>
VMBACKUP_Invalid_Snaptype_URESP=<p>This is an internal error and should be reported to your service representative.</p>
# 5228
CLI_VM_Exceeded_Mount_Point_After_Retry=ANS5228E A backup VM operation failed because VMMAXPARALLEL was reduced to 1 and the client still cannot obtain a server mount point.
CLI_VM_Exceeded_Mount_Point_After_Retry_EXPLANATION=<p>During a parallel backup operation, concurrent backup sessions required additional server mount points to perform the backups in parallel. The client attempted to obtain the additional mount points, but the client requests exceeded the number of mount points (MAXNUMMP) defined for the node. In an effort to make the backup occur, the client reduced the VMMAXPARALLEL option to 1, but was still unable to obtain a mount point. The backup operation was stopped. </p>
CLI_VM_Exceeded_Mount_Point_After_Retry_SYSACT=<p>The backup operation was stopped</p>
CLI_VM_Exceeded_Mount_Point_After_Retry_URESP=<p>Check the console or schedule log for additional information. Retry the operation at a later time. Ensure VMMAXPARALLEL is set to a value less than or equal to MAXNUMMP. </p>
# 5249
VMBACKUP_Restore_Operation_Failed=ANS5249E The virtual machine restore operation failed.\n
VMBACKUP_Restore_Operation_Failed_EXPLANATION=<p>The virtual machine restore operation failed. Check the error log for details on why the operation failed.</p>
VMBACKUP_Restore_Operation_Failed_SYSACT=<p>Processing stops</p>
VMBACKUP_Restore_Operation_Failed_URESP=<p>Review the console output and error logs for the details on the problem. Fix any issues and restart the operation.</p>
# 5284
DSI_Replace_Dsm_Sys_File=ANS5284I TSM has detected an incomplete setup! \n\nThe client options file 'dsm.opt' was not found, while the system options file '{0}' exists! \n\nThe wizard will guide you through the configuration process of the initial basic TSM client options files replacing your current option file. Would you like to continue?
# 5821
AD_Cant_Connect=ANS5821E Cannot connect to Active Directory. \n
AD_Cant_Connect_EXPLANATION=<p> TSM could not connect to Active Directory. The Active Directory is either not running or you don't have enough permissions to use it. </p>
AD_Cant_Connect_SYSACT=<p> Processing stops. </p>
AD_Cant_Connect_URESP=<p> Make sure your system is set up as Active Directory controller and the the service is active. Make sure you are logged in as a user with sufficient rights to administer the Active Directory. </p>
# 5822
AD_No_Objects_Found=ANS5822E No Active Directory objects match query. \n
AD_No_Objects_Found_EXPLANATION=<p> A search has been performed in Active Directory; however, no objects matching the query were found. </p>
AD_No_Objects_Found_SYSACT=<p> Processing stops. </p>
AD_No_Objects_Found_URESP=<p> Make sure you specify a valid distinguished name of Active Directory object or a container, or a valid wildcarded name, and that you have sufficient rights to administer the Active Directory. </p>
# 5823
AD_Object_Exists_Skipping=ANS5823W Object {0} exists, skipping\n
AD_Object_Exists_Skipping_EXPLANATION=<p> The client tried to restore the specified object, but the object already existed in the target restore location and the user chose not to replace the existing object. </p>
AD_Object_Exists_Skipping_SYSACT=<p> The object is skipped, a message is logged in dsmerror.log, and restore processing continues with the next object. </p>
AD_Object_Exists_Skipping_URESP=<p> The object was skipped because either REPLACE NO was in effect, causing all existing objects to 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 skip the object was deliberate. Otherwise the operation can be retried using either REPLACE ALL (automatically replace existing object) or REPLACE PROMPT (prompt the user whether to replace the object). </p>
# 5824
AD_Invalid_Search_Arg=ANS5824E Invalid Active Directory search specification.\n
AD_Invalid_Search_Arg_EXPLANATION=<p> The search specification for Active Directory objects is not valid. </p>
AD_Invalid_Search_Arg_SYSACT=<p> Processing stops. </p>
AD_Invalid_Search_Arg_URESP=<p> Refer to the documentation for supported Active Directory syntax. </p>
# 5826
AD_ReadOnly_Domain_Controller=ANS5826E Restoring to a read-only domain controller is not allowed.\n
AD_ReadOnly_Domain_Controller_EXPLANATION=<p> An attempt to restore to a read-only domain controller. </p>
AD_ReadOnly_Domain_Controller_SYSACT=<p> Processing stops. </p>
AD_ReadOnly_Domain_Controller_URESP=<p> None. </p>
# 5827
AD_Database_Was_Not_Backed_Up=ANS5827E A backup copy of the Active Directory database was not found.\n
AD_Database_Was_Not_Backed_Up_EXPLANATION=<p> An attempt to restore Active Directory objects from a database that was not backed up. </p>
AD_Database_Was_Not_Backed_Up_SYSACT=<p> Processing stops. </p>
AD_Database_Was_Not_Backed_Up_URESP=<p> Verify the Active Directory was backed up with system state. </p>
# 5831
AD_Object_Restore_Not_Allowed_GUI=ANS5831E Restore for this object is not allowed by Active Directory.\n
AD_Object_Restore_Not_Allowed_GUI_EXPLANATION=<p> Object of certain types cannot be restord. This is a system limitation. </p>
AD_Object_Restore_Not_Allowed_GUI_SYSACT=<p> Processing continues to process all other objects per user's request. </p>
AD_Object_Restore_Not_Allowed_GUI_URESP=<p> None. </p>
# 5832
AD_Object_Reanimate_Failed_GUI=ANS5832E Reanimate tombstone object failed. See the error log for more details.\n
AD_Object_Reanimate_Failed_GUI_EXPLANATION=<p> An attempt to reanimate Active Directory tombstone object has been performed, but an error occurred. </p>
AD_Object_Reanimate_Failed_GUI_SYSACT=<p> Processing continues to process all other tombstone objects per user's request. </p>
AD_Object_Reanimate_Failed_GUI_URESP=<p> None. </p>
# 5833
AD_Domain_Services_Stopped=ANS5833E This system is a Domain Controller but the Active Directory service is stopped. You can not perform the operation unless the Active Directory service is running.\n
AD_Domain_Services_Stopped_EXPLANATION=<p> The Active Directory service must be running when you back up or restore the system state or operate on Active Directory objects. When the Active Directory service is running, it can be in online state or in offline state. When you query or restore Active Directory objects, or back up the system state, the Active Directory service must be online. When you restore the system state, the Active Directory service must be offline (but not stopped). </p>
AD_Domain_Services_Stopped_SYSACT=<p>Processing stopped.</p>
AD_Domain_Services_Stopped_URESP=<p> If you are querying or a restoring the Active Directory objects or backing up the system state, put the Active Directory service in online state by starting the Active Directory service. If you are restoring the system state, put the Active Directory service in offline state by rebooting to the Active Directory Restore Mode. When the Active Directory service is in the appropriate state, retry the operation. </p>
# 5834
AD_Unexpected_LDAP_Error=ANS5834E Unexpected LDAP error occurred. See the error log for more details.\n
AD_Unexpected_LDAP_Error_EXPLANATION=<p> An unexpected error occurred during Active Directory tombstone reanimation. </p>
AD_Unexpected_LDAP_Error_SYSACT=<p> Processing continues to process all other tombstone objects per user's request. </p>
AD_Unexpected_LDAP_Error_URESP=<p> Check the error log for detailed information on the LDAP error. </p>
# 5835
AD_LDAP_Error=ANS5835E An LDAP operation returned {0}: '{1}'
AD_LDAP_Error_EXPLANATION=<p> An unexpected error occurred during Active Directory tombstone reanimation. </p>
AD_LDAP_Error_SYSACT=<p> Processing continues to process all other tombstone objects per user's request. </p>
AD_LDAP_Error_URESP=<p> None. </p>
# 5836
AD_Some_Attr_Not_Restored=ANS5836W One or more attributes were not restored. See the error log.\n
AD_Some_Attr_Not_Restored_EXPLANATION=<p> During processing of an Active Directory object, one or more object attributes could not be restored. </p>
AD_Some_Attr_Not_Restored_SYSACT=<p> Processing continues to process all other Active Directory objects per user's request. </p>
AD_Some_Attr_Not_Restored_URESP=<p> Check the error log for detailed information on which attribute(s) could not be restored. </p>
# 5837
AD_Attr_Not_Restored=ANS5837W '{0}': attribute '{1}' could not be restored.\n
AD_Attr_Not_Restored_EXPLANATION=<p> The listed attribute could not be restored during processing on the Active Directory object. </p>
AD_Attr_Not_Restored_SYSACT=<p> Processing continues to process all other Active Directory objects per user's request. </p>
AD_Attr_Not_Restored_URESP=<p> None. </p>
# 5838
AD_Cant_Launch_dsamain=ANS5838E The utility dsamain.exe does not exist on the system. You cannot perform the operation unless Tivoli Storage Manager can launch this utility.\n
AD_Cant_Launch_dsamain_EXPLANATION=<p> You attempted to launch dsamain.exe, but the utility does not exist. </p>
AD_Cant_Launch_dsamain_SYSACT=<p>Processing stopped.</p>
AD_Cant_Launch_dsamain_URESP=<p> Verify that the dsamain.exe utility exists in the Windows system32 directory. When you can run the utility independently of Tivoli Storage Manager, retry the operation. </p>
# 5841
AD_Cant_Mount_Ntds=ANS5841E Active Directory database could not be opened.\n
AD_Cant_Mount_Ntds_EXPLANATION=<p> An error occurred while opening the restored Active Directory database. </p>
AD_Cant_Mount_Ntds_SYSACT=<p>Processing stopped.</p>
AD_Cant_Mount_Ntds_URESP=<p> Make sure ntdsutil.exe utility is located in the same directory with TSM client executables. If it doesn't exist, reinstall the client. Verify that the dsamain.exe utility exists in the Windows system32 directory. When you can run the utility independently of Tivoli Storage Manager, retry the operation. If the problem persists, contact the support. </p>
# 5843
AD_Object_Class_Violation_GUI=ANS5843E Object class violation.\n
AD_Object_Class_Violation_GUI_EXPLANATION=<p> Object class error violation occurred during tombstone reanimation. This can happen if the Active Directory schema was modified and is no longer compatible with the tombstone. </p>
AD_Object_Class_Violation_GUI_SYSACT=<p>Processing continues to process all other objects per user's request.</p>
AD_Object_Class_Violation_GUI_URESP=<p> Recreate the failing object manually or restore it from a backup. </p>
# 5844
COM_Unable_To_Update_Password=ANS5844E Unable to update password.\n
COM_Unable_To_Update_Password_EXPLANATION=<p>An error occurred during the password update attempt.</p>
COM_Unable_To_Update_Password_SYSACT=<p>The password is not updated on the server.</p>
COM_Unable_To_Update_Password_URESP=<p>Try to update the password again.</p>
# 5875
DSI_RC_NO_SUBDIR=No files backed up under sub directories.
# 5876
DSJ_RETENTION_ACTIVATE_COMPLETED=ANS5876I SET EVENT Activate Retention completed
# 5877
DSJ_RETENTION_HOLD_COMPLETED=ANS5877I SET EVENT Hold completed
# 5878
DSJ_RETENTION_RELEASE_COMPLETED=ANS5878I SET EVENT Release completed
# 7507
DSW_ARULE_CHG_NODE_INVALID=ANS7507W The node name entry is invalid. Please try again.
DSW_ARULE_CHG_NODE_INVALID_EXPLANATION=<p>An invalid entry is entered on the Node Name field.</p>
DSW_ARULE_CHG_NODE_INVALID_SYSACT=<p>TSM prompts you to enter a valid node name.</p>
DSW_ARULE_CHG_NODE_INVALID_URESP=<p>Enter a valid node name or see your system administrator for the correct syntax.</p>
# 7510
DSJ_NASNODE_INVALID_OP=ANS7510E A NAS node cannot be used for this operation.
DSJ_NASNODE_INVALID_OP_EXPLANATION=<p>NAS nodes cannot be used for operations like Access Another Node.</p>
DSJ_NASNODE_INVALID_OP_SYSACT=<p>TSM prompts you to enter a valid node name.</p>
DSJ_NASNODE_INVALID_OP_URESP=<p>Enter a valid, non-NAS, TSM node name.</p>
# 7524
SSL_Required=ANS7524E SSL is required.\n
SSL_Required_EXPLANATION=<p>SSL is required to protect the client password during authentication.</p>
SSL_Required_SYSACT=<p>Processing terminates.</p>
SSL_Required_URESP=<p>Enable SSL communication or set SSLREQUIRED to NO.</p>
# 7525
SSL_Required_By_Server=ANS7525E SSL is required by server.\n
SSL_Required_By_Server_EXPLANATION=<p>SSL is required to protect the client password during authentication.</p>
SSL_Required_By_Server_SYSACT=<p>Processing terminates.</p>
SSL_Required_By_Server_URESP=<p>Enable SSL communication or contact your TSM server administrator.</p>
# 7545
Crypto_Encrypt_Error=ANS7545E Unexpected error while encrypting the data.\n
Crypto_Encrypt_Error_EXPLANATION=<p>There was an error while encrypting the data. See the error log for more information.</p>
Crypto_Encrypt_Error_SYSACT=<p>The object is not backed up.</p>
Crypto_Encrypt_Error_URESP=<p>Ensure TSM software is installed correctly. If needed, reinstall the software. Retry the operation. If the problem still exists, contact TSM technical support. </p>
# 7546
Crypto_Decrypt_Error=ANS7546E Unexpected error while decrypting the data.\n
Crypto_Decrypt_Error_EXPLANATION=<p>There was an error while decrypting the data. See the error log for more information. This can happen if the encrypted data has been corrupted while in storage, during the network transfer, or both.</p>
Crypto_Decrypt_Error_SYSACT=<p>The object is not restored.</p>
Crypto_Decrypt_Error_URESP=<p>Ensure TSM software is installed correctly. If needed, reinstall the software. Make sure there are no TSM server or network problems that may affect the transfer of data. Retry the operation. If the problem still exists, contact TSM technical support. </p>
# 7547
Crypto_Digest_Error=ANS7547E Unexpected error while digesting the data.\n
Crypto_Digest_Error_EXPLANATION=<p>There was an error while digesting the data. See the error log for more information.</p>
Crypto_Digest_Error_SYSACT=<p>The object is not backed up.</p>
Crypto_Digest_Error_URESP=<p>Ensure TSM software is installed correctly. If needed, reinstall the software. Retry the operation. If the problem still exists, contact TSM technical support. </p>
# 7642
DSW_REGBACK_ERROR_DIRCREATE=ANS7642E An error occurred creating the registry directory structure.
DSW_REGBACK_ERROR_DIRCREATE_EXPLANATION=<p>An error occurred while creating the directory structure to save or replace a registry key.</p>
DSW_REGBACK_ERROR_DIRCREATE_SYSACT=<p>Registry function fails.</p>
DSW_REGBACK_ERROR_DIRCREATE_URESP=<p>Ensure that the user account that is running the backup of the registry has the proper authority. If the user account has the proper authority, you might need to restart the machine. There might be operations that are pending which have a file or files in the registry directory structure locked.</p>
# 7660
DSW_REGREST_FAILED=ANS7660E An error occurred replacing one or more registry keys.\n
DSW_REGREST_FAILED_EXPLANATION=<p>The registry key or keys being replaced are exclusively held by another process. The registry keys were previously restored but the system was not restarted.</p>
DSW_REGREST_FAILED_SYSACT=<p>processing stops.</p>
DSW_REGREST_FAILED_URESP=<p>Restart the system and try the restore operation again.</p>
# 7665
DSW_ChooseDirectory=Select Directory
# 7702
DSW_DIRSEL_RESTDEST_TITLE=Select Restore Destination Directory
# 7703
DSW_DIRSEL_RETRDEST_TITLE=Select Retrieve Destination Directory
# 7751
DSW_OBJINFO_ATTRIB_ARCHIVE=Archive 
# 7752
DSW_OBJINFO_ATTRIB_HIDDEN=Hidden 
# 7753
DSW_OBJINFO_ATTRIB_READONLY=Read-only 
# 7754
DSW_OBJINFO_ATTRIB_SYSTEM=System 
# 7771
DSW_RESTOPTIONS_NTSECURITY_CHECK=Restore &NTFS security information
# 7772
DSW_SCHWIZ_NAMELOCNT_TITLE=TSM Scheduler name and location
# 7888
DSI_Virtual_Machine=Virtual Machine
# 7889
DSI_VM_Configuration=VM Configuration
# 7912
CLI_FBBACKUP_Not_Installed=ANS7912E FastBackMount or FastBackShell is not installed.\n
CLI_FBBACKUP_Not_Installed_EXPLANATION=<p> Failure initializing FastBack environment. FastBackShell or FastBackMount are not installed or are not located in the FastBack install directory. </p>
CLI_FBBACKUP_Not_Installed_SYSACT=<p> The FastBack operation cannot continue. </p>
CLI_FBBACKUP_Not_Installed_URESP=<p> Reinstall the software. The FastBackShell and FastBackMount must be installed on the dedicated proxy computer. </p>
# 7914
CLI_FBBACKUP_ConsoleStatus9_Incr_backup_of_FB_Failed=ANS7914E Incremental backup of FastBack client '{0}' failed with RC {1}\n
CLI_FBBACKUP_ConsoleStatus9_Incr_backup_of_FB_Failed_EXPLANATION=<p> The archive or incremental backup of FastBack client volumes failed. </p>
CLI_FBBACKUP_ConsoleStatus9_Incr_backup_of_FB_Failed_SYSACT=<p> The archive or backup of FastBack client finished with failures. The next FastBack client will be processed. The reason for the failure is written to the local client error log. </p>
CLI_FBBACKUP_ConsoleStatus9_Incr_backup_of_FB_Failed_URESP=<p> Check the local client error log for reason for the failure. </p>
# 7915
CLI_FBBACKUP_ConsoleStatus10_Mount_of_FB_Failed=ANS7915E Failure mounting FastBack client '{0}' with FastBack command. RC={1}\n
CLI_FBBACKUP_ConsoleStatus10_Mount_of_FB_Failed_EXPLANATION=<p> The FastBackMount command failed to mount a FastBack volume. </p>
CLI_FBBACKUP_ConsoleStatus10_Mount_of_FB_Failed_SYSACT=<p> The archive or backup of the FastBack volume can not continue. The next Volume in in line will be processed. The output of the FastBackMount command will show the reason for the failure. </p>
CLI_FBBACKUP_ConsoleStatus10_Mount_of_FB_Failed_URESP=<p> Check the local client error log for the reason for the failure. Issue a FastBack command for the FastBack volume to determine the reason for the failure. Refer to the documentation for that message for more information. </p>
# 7916
CLI_FBBACKUP_ConsoleStatus11_FBInit_Failed=ANS7916E Failure initializing FastBack environment.RC={0}\n
CLI_FBBACKUP_ConsoleStatus11_FBInit_Failed_EXPLANATION=<p> Failure initializing FastBack environment. Can not find FastBackShell.exe command. The FastBackShell or FastBackMount is not installed or FastBackShell.exe command is not located in the FastBack install directory. </p>
CLI_FBBACKUP_ConsoleStatus11_FBInit_Failed_SYSACT=<p> The backup can not continue. The output of the FastBack command will show the reason for the failure. </p>
CLI_FBBACKUP_ConsoleStatus11_FBInit_Failed_URESP=<p> Issue a FastBack command to determine the reason for the failure. Refer to the documentation for that message for more information. The FastBackShell and FastBackMount must be installed on the backup proxy computer. </p>
# 7917
CLI_FBBACKUP_ConsoleStatus12_FBGetClients_Failed=ANS7917E No FastBack snapshots found for input policy, client and volume combination.\n
CLI_FBBACKUP_ConsoleStatus12_FBGetClients_Failed_EXPLANATION=<p> Failure processing fbClientName option. </p>
CLI_FBBACKUP_ConsoleStatus12_FBGetClients_Failed_SYSACT=<p> The backup cannot continue. </p>
CLI_FBBACKUP_ConsoleStatus12_FBGetClients_Failed_URESP=<p> Check for errors in the FBClientName option value. Refer to the documentation for the FBClientName option for more information. </p>
# 7918
CLI_FBBACKUP_ConsoleStatus13_GetVM_Alllocal_Failed=ANS7918E Failure locating mounted volumes for FastBack client '{0}' volumes. Failed with RC={1}\n
CLI_FBBACKUP_ConsoleStatus13_GetVM_Alllocal_Failed_EXPLANATION=<p> FastBack client volumes can not be found. Volume mount points are not available on the backup proxy computer. </p>
CLI_FBBACKUP_ConsoleStatus13_GetVM_Alllocal_Failed_SYSACT=<p> The backup of the FastBack client can not continue. The next FastBack client in the list will be processed. The output of the FastBackMount command will show the reason for the failure. </p>
CLI_FBBACKUP_ConsoleStatus13_GetVM_Alllocal_Failed_URESP=<p> Issue a fastbackshell mount add command for the FastBack client volume to determine the reason for the failure. Refer to the documentation for that message for more information. </p>
# 7919
CLI_FBBACKUP_No_Password_Specified=ANS7919E Password for Host {0} could not be read from encrypted password file. \n
CLI_FBBACKUP_No_Password_Specified_EXPLANATION=<p> Use dsmc SET PASSWORD -type=FastBack 'FastBack hostname' 'userid' 'password' to save encrypted password </p>
CLI_FBBACKUP_No_Password_Specified_SYSACT=<p> The backup cannot continue. </p>
CLI_FBBACKUP_No_Password_Specified_URESP=<p> Use dsmc SET PASSWORD -type=FastBack 'FastBack hostname' 'userid' 'password' to save encrypted password </p>
# 8004
LDAP_PASSWORD_EXPIRING=ANS8004W Your password will expire within {0} day(s).\n
LDAP_PASSWORD_EXPIRING_EXPLANATION=<p>The password for this id is about to expire.</p>
LDAP_PASSWORD_EXPIRING_SYSACT=<p>Logging on to the TSM Server will not be prevented, however, the id will be locked out once it expires.</p>
LDAP_PASSWORD_EXPIRING_URESP=<p>Change the password or contact your TSM administrator to get the password updated.</p>
# 8006
COM_Generated_Password_Rejected=ANS8006E Unable to generate an acceptable password.\n
COM_Generated_Password_Rejected_EXPLANATION=<p>An error occurred during a password update attempt using a generated password.</p>
COM_Generated_Password_Rejected_SYSACT=<p>The password is not updated on the server.</p>
COM_Generated_Password_Rejected_URESP=<p>Contact your TSM administrator.</p>
# 8007
LDAP_Not_Authorized=ANS8007E The user is not authorized to perform LDAP authentication.\n
LDAP_Not_Authorized_EXPLANATION=<p>Your node uses LDAP authentication. Your PASSWORDACCESS option is set to GENERATE but the current user cannot access the stored password to perform authentication.</p>
LDAP_Not_Authorized_SYSACT=<p>The operation is stopped.</p>
LDAP_Not_Authorized_URESP=<p>Run TSM client as root user or set PASSWORDACCESS to PROMPT.</p>
# 8013
CLI_Invalid_Enc_Password=ANS8013I Invalid encryption key password \n
# 8033
LDAP_Not_Supported=ANS8033E LDAP authentiction is not supported by Web client.\n
LDAP_Not_Supported_EXPLANATION=<p>The id you entered uses LDAP authentication. LDAP authentication is not supported by Web client. </p>
LDAP_Not_Supported_SYSACT=<p>Login is unsuccessful.</p>
LDAP_Not_Supported_URESP=<p>Use an id with LOCAL authentication.</p>
# 8120
CLI_QueryStatistics=\n\nQuery Statistics \n\n Total Volumes {0}\n Number of Files {1}\n Number of Directories {2}\n Aggregate Data Size {3}\n Average File Size {4}\n Classic Restore Memory Estimate {5}\n\n
# 8776
DSI_SM_JAVA_VERSION_ERROR=ANS8776E The IBM Tivoli Enterprise Space Management Console cannot be started. \n\nJava Runtime Environment version {0} by {1} \nhas been detected on {2}.\n\nA Java Runtime Environment {3} or higher is required to run this program. \nIf you have already installed Java {4} on this machine, \nplease ensure that the correct Java executable is on your PATH, otherwise \nyou can download it from '{5}'\nand start the program again.
DSI_SM_JAVA_VERSION_ERROR_EXPLANATION=<p>IBM Tivoli Enterprise Space Management Console cannot be started because the Java runtime environment does not meet the requirements.</p>
DSI_SM_JAVA_VERSION_ERROR_SYSACT=<p>A confirmation dialog is displayed for you to close the application, or to open a browser with a link to the Web site where you can download the correct version of Java.</p>
DSI_SM_JAVA_VERSION_ERROR_URESP=<p>Verify that the correct java executable is on your PATH or install the required version of Java runtime environment and start the program again.</p>
# 8777
DSI_SM_LOOK_AND_FEEL_ERROR=ANS8777E The IBM Tivoli Enterprise Space Management Console cannot be started. \n\nAn error occurred trying to load Tivoli look and feel. \n\nVerify that the product is correctly installed.\n
DSI_SM_LOOK_AND_FEEL_ERROR_EXPLANATION=<p>IBM Tivoli Enterprise Space Management Console cannot be started because the library that defines the Tivoli look and feel cannot be found.</p>
DSI_SM_LOOK_AND_FEEL_ERROR_SYSACT=<p>The IBM Tivoli Enterprise Space Management Console shuts down.</p>
DSI_SM_LOOK_AND_FEEL_ERROR_URESP=<p>Verify that the product is correctly installed. If IBM Tivoli Enterprise Space Management Console still cannot be started, contact your system administrator for further assistance.</p>
# 8778
DSI_SM_WIN_BROWSER_ERROR=ANS8778E A browser program cannot be found or cannot be started. \n\nAn error occurred executing the command.\n{0}\n\nVerify that a browser is installed and works correctly on your local machine.
DSI_SM_WIN_BROWSER_ERROR_EXPLANATION=<p>A browser program cannot be found, so it is not possible to access the IBM Tivoli Web site and online documentation.</p>
DSI_SM_WIN_BROWSER_ERROR_SYSACT=<p>TSM continues to process user requests.</p>
DSI_SM_WIN_BROWSER_ERROR_URESP=<p>For the Windows platform, the default system browser is used. Verify that a browser is installed on your machine.</p>
# 8779
DSI_SM_UNIX_BROWSER_ERROR=ANS8779E A browser program cannot be found or cannot be started. \n\nOne of the following browsers is required: {0}\n\nVerify that one of these browsers is installed and works correctly on your local machine.
DSI_SM_UNIX_BROWSER_ERROR_EXPLANATION=<p>A browser program cannot be found, so it is not possible to access the IBM Tivoli Web site and online documentation.</p>
DSI_SM_UNIX_BROWSER_ERROR_SYSACT=<p>TSM continues to process user requests.</p>
DSI_SM_UNIX_BROWSER_ERROR_URESP=<p>For UNIX platforms, a list of supported browsers is provided in the README. Install the required browser to access the IBM Tivoli Web sites and online documentation.</p>
# 8780
DSI_SM_APPLET_BROWSER_ERROR=ANS8780E A browser program cannot be found or cannot be started. \n\nCheck the '{0}' file on your local machine for more information.
DSI_SM_APPLET_BROWSER_ERROR_EXPLANATION=<p>A browser program cannot be found, so it is not possible to access the Web site or online documentation.</p>
DSI_SM_APPLET_BROWSER_ERROR_SYSACT=<p>TSM continues to process user requests.</p>
DSI_SM_APPLET_BROWSER_ERROR_URESP=<p>Install a browser to access the Web site or online documentation.</p>
# 8781
DSI_SM_LOGON_ERROR=ANS8781E The system could not log on to TSM client node \n{0} on {1}. \n\nMake sure your data and password are correct \nand that caps lock key is not on. \nThe Space Management Agent must be running at the specified \nport on the machine to which you are attempting to log on to.
DSI_SM_LOGON_ERROR_EXPLANATION=<p>The system was not able to connect to the specified client node.</p>
DSI_SM_LOGON_ERROR_SYSACT=<p>TSM continues to process user requests.</p>
DSI_SM_LOGON_ERROR_URESP=<p>Verify that: <ul> <li>the information provided to connect is correct</li> <li>the machine is reachable in the network</li> <li>HSM is installed on the specified machine and a Space Management Agent is running at the specified port.</li> </ul> </p>
# 8782
DSI_SM_FS_LOADING_ERROR=ANS8782E An error occurred while loading file system information on '{0}'. \n\nVerify that the Space Management agent is running on the client node machine.\nCheck also the {1} file in the installation directory of your local machine \nand the $DSM_DIR/{2} file on {3} if present. \nIf this does not identify the cause of the problem, contact your system administrator \nand/or TSM technical support for further assistance. 
DSI_SM_FS_LOADING_ERROR_EXPLANATION=<p>An error occurred while loading file system information on the selected client node</p>
DSI_SM_FS_LOADING_ERROR_SYSACT=<p>Disconnects the client node.</p>
DSI_SM_FS_LOADING_ERROR_URESP=<p>Verify that the Space Management agent is running on the client node machine. Check also the dsmsm.log file in the installation directory of your local machine and the $DSM_DIR/dsmerror.log file on the client node machine if present. If this does not identify the cause of the problem, contact your system administrator and/or TSM technical support for further assistance.</p>
# 8783
DSI_SM_ERROR_LOADING_FS_PROPERTIES=ANS8783E An error occurred loading file system properties of {0} required to show space usage graphical information. \n\nVerify that the Space Management agent is running on the client node machine.\nCheck also the {1} file in the installation directory of your local machine \nand the $DSM_DIR/{2} file on {3} if present. \nIf this does not identify the cause of the problem, contact your system administrator \nand/or TSM technical support for further assistance. 
DSI_SM_ERROR_LOADING_FS_PROPERTIES_EXPLANATION=<p>An error occurred while loading file system properties on the selected client node.</p>
DSI_SM_ERROR_LOADING_FS_PROPERTIES_SYSACT=<p>Continue to process other file system properties.</p>
DSI_SM_ERROR_LOADING_FS_PROPERTIES_URESP=<p>Verify that the Space Management agent is running on the client node machine. Check also the dsmsm.log file in the installation directory of your local machine and the $DSM_DIR/dsmerror.log file on the client node machine. If this does not identify the cause of the problem, then see your system administrator for further assistance.</p>
# 8784
DSI_SM_INIT_NODE_TABLE_ERROR=ANS8784E An error occurred initializing the client nodes table. \n\nYour local configuration file '{0}' might be corrupted.\nRemove it from your installation directory and start the program again. \nCheck also the {1} file on your local machine for more information. \n
DSI_SM_INIT_NODE_TABLE_ERROR_EXPLANATION=<p>The client nodes table cannot be initialized.</p>
DSI_SM_INIT_NODE_TABLE_ERROR_SYSACT=<p>The IBM Tivoli Enterprise Space Management Console shuts down.</p>
DSI_SM_INIT_NODE_TABLE_ERROR_URESP=<p>It is possible that your local settings file 'dsmsm.cfg' is corrupted. Try to remove it from your installation directory and start the program again. Check the dsmsm.log file in the installation directory of your local machine and the $DSM_DIR/dsmerror.log file on the client node machine if present. If this does not identify the cause of the problem, contact your system administrator and/or TSM technical support for further assistance.</p>
# 8785
DSI_SM_DELETE_HSM_SYSTEM_ERROR=ANS8785E An error occurred disconnecting the system from the client node '{0}'. \n\nThe Client node is being disconnected without deleting internal HsmSystem objects. \n\nVerify that the Space Management agent is running on the client node machine.\nCheck also the {1} file in the installation directory of your local machine \nand the $DSM_DIR/{2} file on {3} if present. \nIf this does not identify the cause of the problem, contact your system administrator \nand/or TSM technical support for further assistance. 
DSI_SM_DELETE_HSM_SYSTEM_ERROR_EXPLANATION=<p>An error occurred disconnecting the system from the client node. It was not possible to delete internal HsmSystem objects.</p>
DSI_SM_DELETE_HSM_SYSTEM_ERROR_SYSACT=<p>The client node disconnected without deleting HsmSystem objects.</p>
DSI_SM_DELETE_HSM_SYSTEM_ERROR_URESP=<p>Verify that the Space Management agent is running on the client node machine. Check the dsmsm.log file in the installation directory of your local machine and the $DSM_DIR/dsmerror.log file on the client node machine if present. If this does not identify the cause of the problem, contact your system administrator and/or TSM technical support for further assistance.</p>
# 8786
DSI_SM_LOAD_FS_STATISTICS_ERROR=ANS8786E An error occurred loading file system information from the selected client node. \n\nVerify that the Space Management agent is running on the client node machine.\nCheck also the {0} file in the installation directory of your local machine \nand the $DSM_DIR/{1} file in the client node machine if present. \nIf this does not identify the cause of the problem, contact your system administrator \nand/or TSM technical support for further assistance. 
DSI_SM_LOAD_FS_STATISTICS_ERROR_EXPLANATION=<p>An error occurred loading file system information from the selected client node. </p>
DSI_SM_LOAD_FS_STATISTICS_ERROR_SYSACT=<p>File System information is not loaded</p>
DSI_SM_LOAD_FS_STATISTICS_ERROR_URESP=<p>Verify that the Space Management agent is running on the client node machine. Check the dsmsm.log file in the installation directory of your local machine and the $DSM_DIR/dsmerror.log file on the client node machine if present. If this does not identify the cause of the problem, contact your system administrator and/or TSM technical support for further assistance.</p>
# 8787
DSI_SM_ERROR_LOADING_DATA=ANS8787E An error occurred loading file system information from {0} client node. \nThe client node is being disconnected. \n\nVerify that the Space Management agent is running on the client node machine.\nCheck also the {1} file in the installation directory of your local machine \nand the $DSM_DIR/{2} file on {3} if present. \nIf this does not identify the cause of the problem, contact your system administrator \nand/or TSM technical support for further assistance. 
DSI_SM_ERROR_LOADING_DATA_EXPLANATION=<p>An error occurred loading file system information from the selected client node.</p>
DSI_SM_ERROR_LOADING_DATA_SYSACT=<p>The client node is disconnected</p>
DSI_SM_ERROR_LOADING_DATA_URESP=<p>Verify that the Space Management agent is running on the client node machine. Check the dsmsm.log file in the installation directory of your local machine and the $DSM_DIR/dsmerror.log file on the client node machine if present. If this does not identify the cause of the problem, contact your system administrator and/or TSM technical support for further assistance.</p>
# 8788
DSI_SM_ERROR_STARTING_AUTOMIGRATION_FS=ANS8788E An error occurred starting manually threshold migration on {0}. \n\nVerify that the Space Management agent is running on the client node machine.\nCheck also the {1} file in the installation directory of your local machine \nand the $DSM_DIR/{2} file on {3} if present. \nIf this does not identify the cause of the problem, contact your system administrator \nand/or TSM technical support for further assistance. 
DSI_SM_ERROR_STARTING_AUTOMIGRATION_FS_EXPLANATION=<p>An error occurred starting the manually threshold migration on the selected client node.</p>
DSI_SM_ERROR_STARTING_AUTOMIGRATION_FS_SYSACT=<p>Threshold migration is not started manually.</p>
DSI_SM_ERROR_STARTING_AUTOMIGRATION_FS_URESP=<p>Check the dsmsm.log file in the installation directory of your local machine and the $DSM_DIR/dsmerror.log file on the client node machine if present. If this does not identify the cause of the problem, contact your system administrator and/or TSM technical support for further assistance.</p>
# 8789
DSI_SM_ERROR_GLOBAL_DEACTIVATING=ANS8789E An error occurred trying to deactivate all managed file systems of {0}. \n\nCheck also the {1} file in the installation directory of your local machine \nand the $DSM_DIR/{2} file on {3} if present. \nIf this does not identify the cause of the problem, contact your system administrator \nand/or TSM technical support for further assistance. 
DSI_SM_ERROR_GLOBAL_DEACTIVATING_EXPLANATION=<p>An error occurred trying to deactivate all managed file systems of the selected client node.</p>
DSI_SM_ERROR_GLOBAL_DEACTIVATING_SYSACT=<p>File systems are not deactivated.</p>
DSI_SM_ERROR_GLOBAL_DEACTIVATING_URESP=<p>Check the dsmsm.log file in the installation directory of your local machine and the $DSM_DIR/dsmerror.log file on the client node machine if present. If this does not identify the cause of the problem, contact your system administrator and/or TSM technical support for further assistance.</p>
# 8790
DSI_SM_ERROR_GLOBAL_REACTIVATING=ANS8790E An error occurred trying to reactivate all managed file systems of {0}. \n\nCheck also the {1} file in the installation directory of your local machine \nand the $DSM_DIR/{2} file on {3} if present. \nIf this does not identify the cause of the problem, contact your system administrator \nand/or TSM technical support for further assistance. 
DSI_SM_ERROR_GLOBAL_REACTIVATING_EXPLANATION=<p>An error occurred trying to reactivate all managed file systems of the selected client node.</p>
DSI_SM_ERROR_GLOBAL_REACTIVATING_SYSACT=<p>File systems are not reactivated.</p>
DSI_SM_ERROR_GLOBAL_REACTIVATING_URESP=<p>Check the dsmsm.log file in the installation directory of your local machine and the $DSM_DIR/dsmerror.log file on the client node machine if present. If this does not identify the cause of the problem, contact your system administrator and/or TSM technical support for further assistance.</p>
# 8791
DSI_SM_ERROR_ADDING_SPACE_MAN=ANS8791E An error occurred trying to add space management to {0} file system. \n\nVerify that the Space Management agent is running on the client node machine.\nCheck also the {1} file in the installation directory of your local machine \nand the $DSM_DIR/{2} file on {3} if present. \nIf this does not identify the cause of the problem, contact your system administrator \nand/or TSM technical support for further assistance. 
DSI_SM_ERROR_ADDING_SPACE_MAN_EXPLANATION=<p>An error occurred trying to add space management to the selected file system.</p>
DSI_SM_ERROR_ADDING_SPACE_MAN_SYSACT=<p>Space management is not added to the selected file system.</p>
DSI_SM_ERROR_ADDING_SPACE_MAN_URESP=<p>Check the dsmsm.log file in the installation directory of your local machine and the $DSM_DIR/dsmerror.log file on the client node machine if present. If this does not identify the cause of the problem, contact your system administrator and/or TSM technical support for further assistance.</p>
# 8792
DSI_SM_ERROR_REMOVING_SPACE_MAN=ANS8792E An error occurred trying to remove space management from {0} file system. \n\nVerify that the Space Management agent is running on the client node machine.\nCheck also the {1} file in the installation directory of your local machine \nand the $DSM_DIR/{2} file on {3} if present. \nIf this does not identify the cause of the problem, contact your system administrator \nand/or TSM technical support for further assistance. 
DSI_SM_ERROR_REMOVING_SPACE_MAN_EXPLANATION=<p>An error occurred trying to remove space management from the selected file system.</p>
DSI_SM_ERROR_REMOVING_SPACE_MAN_SYSACT=<p>Space management is not removed from the selected file system.</p>
DSI_SM_ERROR_REMOVING_SPACE_MAN_URESP=<p>Check the dsmsm.log file in the installation directory of your local machine and the $DSM_DIR/dsmerror.log file on the client node machine if present. If this does not identify the cause of the problem, contact your system administrator and/or TSM technical support for further assistance.</p>
# 8793
DSI_SM_ERROR_DEACTIVATING_FS=ANS8793E An error occurred trying to deactivate {0} file system. \n\nVerify that the Space Management agent is running on the client node machine.\nCheck also the {1} file in the installation directory of your local machine \nand the $DSM_DIR/{2} file on {3} if present. \nIf this does not identify the cause of the problem, contact your system administrator \nand/or TSM technical support for further assistance. 
DSI_SM_ERROR_DEACTIVATING_FS_EXPLANATION=<p>An error occurred trying to deactivate the selected file system.</p>
DSI_SM_ERROR_DEACTIVATING_FS_SYSACT=<p>The selected file system is not deactivated.</p>
DSI_SM_ERROR_DEACTIVATING_FS_URESP=<p>Check the dsmsm.log file in the installation directory of your local machine and the $DSM_DIR/dsmerror.log file on the client node machine if present. If this does not identify the cause of the problem, contact your system administrator and/or TSM technical support for further assistance.</p>
# 8794
DSI_SM_ERROR_REACTIVATING_FS=ANS8794E An error occurred trying to reactivate {0} file system. \n\nVerify that the Space Management agent is running on the client node machine.\nCheck also the {1} file in the installation directory of your local machine \nand the $DSM_DIR/{2} file on {3} if present. \nIf this does not identify the cause of the problem, contact your system administrator \nand/or TSM technical support for further assistance. 
DSI_SM_ERROR_REACTIVATING_FS_EXPLANATION=<p>An error occurred trying to reactivate the selected file system.</p>
DSI_SM_ERROR_REACTIVATING_FS_SYSACT=<p>The selected file system is not reactivated.</p>
DSI_SM_ERROR_REACTIVATING_FS_URESP=<p>Check the dsmsm.log file in the installation directory of your local machine and the $DSM_DIR/dsmerror.log file on the client node machine if present. If this does not identify the cause of the problem, contact your system administrator and/or TSM technical support for further assistance.</p>
# 8795
DSI_SM_SAVE_CONFIGURATION_ERROR=ANS8795E An error occurred trying to save your settings to {0} \nconfiguration file on your local machine. \n\nCheck the {1} file in the installation directory of \nyour local machine for more information. \n
DSI_SM_SAVE_CONFIGURATION_ERROR_EXPLANATION=<p>An error occurred trying to save your settings to dsmsm.cfg configuration file on your local machine. </p>
DSI_SM_SAVE_CONFIGURATION_ERROR_SYSACT=<p>Customized GUI settings are not saved to the local machine</p>
DSI_SM_SAVE_CONFIGURATION_ERROR_URESP=<p>Check the dsmsm.log file in the installation directory of your local machine and the $DSM_DIR/dsmerror.log file on the client node machine if present. If this does not identify the cause of the problem, contact your system administrator and/or TSM technical support for further assistance.</p>
# 8800
DSW_MENU_ADSM_BACKUP_VM=Ba&ckup VM
# 8801
DSI_VM_FULL_BACKUP_TYPE=VM Full Backup Options
# 8802
DSI_VM_VSTOR_TYPE=VStorage
# 8803
DSI_VM_VCB_TYPE=VCB
# 8804
DSI_VM_MGMT_CLASS=VM Management Class
# 8805
DSI_BACKUP_VM_INCR=VMWare Full VM Incremental
# 8806
DSI_VM_DATACENTER=Datacenter:
# 8807
DSI_VM_HOST=Host:
# 8808
DSI_VM_DATASTORE=Datastore:
# 8810
DSI_LIBPATH_Not_set=ANS8810E The LD_LIBRARY_PATH is either not set or is set incorrectly. Ensure that the LD_LIBRARY_PATH environment variable contains the installation directory.\n
DSI_LIBPATH_Not_set_EXPLANATION=<p>The LD_LIBRARY_PATH must be set and it must contain the installation directory path. </p>
DSI_LIBPATH_Not_set_SYSACT=<p>The VMware backup or restore operation fails.</p>
DSI_LIBPATH_Not_set_URESP=<p>Set the LD_LIBRARY_PATH and ensure that it contains the Backup/Archive client installation directory. </p>
# 8811
HARDWARE_PLUGIN_INSTALLED=ANS8811E VMware operations can not be run when the hardware plugin product TIVsm-BAhdw is installed and loaded. Please either uninstall the hardware product TIVsm-BAhdw, or set the option DONTLOAD PIHDW in the options file to prevent the hardware plugin from being loaded.\n
HARDWARE_PLUGIN_INSTALLED_EXPLANATION=<p>VMware operations are incompatible with the hardware plugin product libraries. </p>
HARDWARE_PLUGIN_INSTALLED_SYSACT=<p>The VMware backup or restore operation fails.</p>
HARDWARE_PLUGIN_INSTALLED_URESP=<p>Uninstall the hardware product product TIVsm-BAhdw, or set the option DONTLOAD PIHDW to prevent the hardware plugin from being loaded.</p>
# 8812
DSI_BACKUP_VM_PFINCR=Periodic Full - Incremental
# 8813
DSI_BACKUP_VM_PFFULL=Periodic Full - Full
# 8814
DSI_BACKUP_VM_IFINCR=Incremental Forever - Incremental
# 8815
DSI_BACKUP_VM_IFFULL=Incremental Forever - Full
# 8818
DSI_SM_ERROR_SAVE_OPTIONS=ANS8818E An error occurred trying to apply your changes. \nYour changes have not been applied to the system.\n\nContact your system administrator.
DSI_SM_ERROR_SAVE_OPTIONS_EXPLANATION=<p>An error occurred trying to apply your changes.</p>
DSI_SM_ERROR_SAVE_OPTIONS_SYSACT=<p>User changes are not applied.</p>
DSI_SM_ERROR_SAVE_OPTIONS_URESP=<p>Contact your system administrator.</p>
# 8819
DSI_SM_INVALID_TRACE_FLAGS=ANS8819E The following trace flag(s) are not valid: {0}. \nCorrect them before continuing.
DSI_SM_INVALID_TRACE_FLAGS_EXPLANATION=<p>One or more of the trace flags are not valid.</p>
DSI_SM_INVALID_TRACE_FLAGS_SYSACT=<p>Prompts the user to correct the trace flags.</p>
DSI_SM_INVALID_TRACE_FLAGS_URESP=<p>Correct the wrong trace flags.</p>
# 8820
DSI_SMA_HSMSYSTEM_OBJECT_NOT_FOUND=ANS8820E The HSM System Object was not found on the Space Management agent. \nThe error occurred when calling function: {0}. \nThe last operation was not processed correctly.
DSI_SMA_HSMSYSTEM_OBJECT_NOT_FOUND_EXPLANATION=<p>The Space Management agent was unable to process a HSM System function, because the HSM System object was not found.</p>
DSI_SMA_HSMSYSTEM_OBJECT_NOT_FOUND_SYSACT=<p>The last operation is skipped.</p>
DSI_SMA_HSMSYSTEM_OBJECT_NOT_FOUND_URESP=<p>Reconnect to the Space Management agent. If this does not solve the problem restart the Space Management agent.</p>
# 8821
DSI_SMA_COULD_NOT_CREATE_HSM_OBJECT=ANS8821E Unable to create requested HSM object on Space Management agent. \nThe last operation was not processed correctly. \nThe problem is caused from a memory problem. Try to free memory \non the system where the Space Management agent is running. \nOr restart the Space Management agent.
DSI_SMA_COULD_NOT_CREATE_HSM_OBJECT_EXPLANATION=<p>Space Management agent was not able to create a requested HSM object because not enough free space was found on the system.</p>
DSI_SMA_COULD_NOT_CREATE_HSM_OBJECT_SYSACT=<p>Last operation is skipped.</p>
DSI_SMA_COULD_NOT_CREATE_HSM_OBJECT_URESP=<p>Try to free more memory on the system where the Space Management agent is running, or restart the Space Management agent.</p>
# 8822
DSI_SMA_HSMFILESYSTEM_OBJECT_NOT_FOUND=ANS8822E HSM File System Object was not found on Space Management agent. \nThe error occurred when calling function: {0} \nThe last operation was not processed correctly.
DSI_SMA_HSMFILESYSTEM_OBJECT_NOT_FOUND_EXPLANATION=<p>Space Management agent was not able to process a HSM File System function, because no HSM File System object was found.</p>
DSI_SMA_HSMFILESYSTEM_OBJECT_NOT_FOUND_SYSACT=<p>Last operation is skipped.</p>
DSI_SMA_HSMFILESYSTEM_OBJECT_NOT_FOUND_URESP=<p>Reconnect to the Space Management agent. If this does not solve the problem restart the Space Management agent.</p>
# 8823
DSI_SMA_PROTOCOL_ERROR=ANS8823E A Protocol error occurred in communication with the Space Management agent \nThis error occurs when a session with the Space Management agent was lost, or \nnetwork error caused synchronization problem between the Space Management console \nand the agent.
DSI_SMA_PROTOCOL_ERROR_EXPLANATION=<p>Space Management console and Space Management agent has different session and transaction key in the communication header.</p>
DSI_SMA_PROTOCOL_ERROR_SYSACT=<p>Last operation is skipped.</p>
DSI_SMA_PROTOCOL_ERROR_URESP=<p>Restart Space Management console and Space Management agent.</p>
# 8824
DSI_SMA_INTERNAL_ERROR=ANS8824E A internal error occurred in the Space Management agent. \nThe error occurred in function : {0} \n
DSI_SMA_INTERNAL_ERROR_EXPLANATION=<p>Not defined exception caused a internal error in the Space Management agent.</p>
DSI_SMA_INTERNAL_ERROR_SYSACT=<p>Last operation is skipped.</p>
DSI_SMA_INTERNAL_ERROR_URESP=<p>Restart Space Management agent. If this does not solve the problem contact TSM technical support.</p>
# 8825
DSI_SMAPI_LOCATE_OPTIONOBJECT_FAILS=ANS8825E The Space Management API was unable to locate option object \nThe error occurred in function : {0} \n
DSI_SMAPI_LOCATE_OPTIONOBJECT_FAILS_EXPLANATION=<p>Not defined exception caused this internal error in the Space Management API.</p>
DSI_SMAPI_LOCATE_OPTIONOBJECT_FAILS_SYSACT=<p>Last operation is skipped.</p>
DSI_SMAPI_LOCATE_OPTIONOBJECT_FAILS_URESP=<p>Contact TSM technical support.</p>
# 8826
DSI_SMAPI_HSMSYSTEM_ISGLOBALACTIVE_FAILS=ANS8826E The Space Management API was unable to query a HSM device. \nThis error occurs because the HSM kernel extension was not loaded correctly \n
DSI_SMAPI_HSMSYSTEM_ISGLOBALACTIVE_FAILS_EXPLANATION=<p>Because of a wrong configuration HSM was not able the load the kernel extension. This causes to fail the query for global activation of the HSM system.</p>
DSI_SMAPI_HSMSYSTEM_ISGLOBALACTIVE_FAILS_SYSACT=<p>Query for global HSM activation is skipped.</p>
DSI_SMAPI_HSMSYSTEM_ISGLOBALACTIVE_FAILS_URESP=<p>Check the configuration of the HSM system. If you can not find any problem in the configuration contact TSM technical support.</p>
# 8827
DSI_SMAPI_HSMCONNECTION_LOADCONNSET_GETGLOBALCB_ERROR=ANS8827E The Space Management API was unable to locate global control block. \nThe error occurred in function : {0} \n
DSI_SMAPI_HSMCONNECTION_LOADCONNSET_GETGLOBALCB_ERROR_EXPLANATION=<p>Not defined exception caused this internal error in the Space Management API.</p>
DSI_SMAPI_HSMCONNECTION_LOADCONNSET_GETGLOBALCB_ERROR_SYSACT=<p>Load connection settings function is skipped.</p>
DSI_SMAPI_HSMCONNECTION_LOADCONNSET_GETGLOBALCB_ERROR_URESP=<p>Contact TSM technical support.</p>
# 8828
DSI_SMAPI_CHECK_SERVER_SESSION_ERROR=ANS8828E The Space Management API lost the session with the server. \nThis problem is caused by a connection failure with the server. \nCheck to see if your Space Management Client machine has a network connection \nto the TSM server.
DSI_SMAPI_CHECK_SERVER_SESSION_ERROR_EXPLANATION=<p>This error occurs when the Space Management API has connection problems with the TSM server.</p>
DSI_SMAPI_CHECK_SERVER_SESSION_ERROR_SYSACT=<p>Session with server gets lost and server operation is skipped.</p>
DSI_SMAPI_CHECK_SERVER_SESSION_ERROR_URESP=<p>Check the network connection with TSM server machine. See the error log file for additional information why the session gets lost. Restart the Space Management Agent if the connection re-established automatically. </p>
# 8829
DSI_SMAPI_INITHSM_CREATESESS_FAILS=ANS8829E The Space Management API was unable to initialize the HSM system. \nThe error is caused from a problem to initialize a DMAPI session.
DSI_SMAPI_INITHSM_CREATESESS_FAILS_EXPLANATION=<p>This error is caused from a problem to initialize a DMAPI session.</p>
DSI_SMAPI_INITHSM_CREATESESS_FAILS_SYSACT=<p>The HSM system cannot be initialized and the Space Management Console is ended.</p>
DSI_SMAPI_INITHSM_CREATESESS_FAILS_URESP=<p>Try to restart Space Management Agent. If this does not solve the problem, see the error log for additional information and contact TSM technical support. </p>
# 8831
DSI_SMAPI_GET_FILESYSTEM_FAILS=ANS8831E The Space Management API could not find file system : {0} \nAn incorrect file system name was passed to the Space Management API. Ensure \nthat the file system that was selected in the file system list is still valid. \nRefresh the file system view in the Space Management Console by pressing F5 on your \nkeyboard or select 'Refresh` under the View menu.
DSI_SMAPI_GET_FILESYSTEM_FAILS_EXPLANATION=<p>The Space Management API could not find the file system that was specified in the Space Management Console. A reason could be that the file system was unmounted and is not longer existing on the system. </p>
DSI_SMAPI_GET_FILESYSTEM_FAILS_SYSACT=<p>Getting file system information for the specified file system name is skipped.</p>
DSI_SMAPI_GET_FILESYSTEM_FAILS_URESP=<p>Update the file system list in the Space Management Console by pressing F5 on your keyboard or selecting 'Refresh' in the View menu.</p>
# 8832
DSI_SMAPI_GET_MGMT_LIST_ERROR=ANS8832E The Space Management API could not retrieve TSM policy settings from the server. \n
DSI_SMAPI_GET_MGMT_LIST_ERROR_EXPLANATION=<p>The Space Management API tried to get TSM policy settings from the server and failed for a unknown reason.</p>
DSI_SMAPI_GET_MGMT_LIST_ERROR_SYSACT=<p>Getting TSM policy settings fails and policy information fields are not filled up in the Space Management Console.</p>
DSI_SMAPI_GET_MGMT_LIST_ERROR_URESP=<p>See the error log file for additional information.</p>
# 8833
DSI_SMAPI_GET_MGMT_INFO_ERROR=ANS8833E The Space Management API could not retrieve TSM policy settings from \nthe already loaded list.
DSI_SMAPI_GET_MGMT_INFO_ERROR_EXPLANATION=<p>The Space Management API tried to get TSM policy settings from the management list and failed for a unknown reason.</p>
DSI_SMAPI_GET_MGMT_INFO_ERROR_SYSACT=<p>Getting TSM policy settings fails and policy information fields are not filled up in the Space Management Console.</p>
DSI_SMAPI_GET_MGMT_INFO_ERROR_URESP=<p>See the error log file for additional information.</p>
# 8834
DSI_SMAPI_GET_FS_INFO_FAILS=ANS8834E The Space Management API was unable to get file system information for \nfile system : {0}. \n
DSI_SMAPI_GET_FS_INFO_FAILS_EXPLANATION=<p>The Space Management API could not retrieve the file system information for a selected file system.</p>
DSI_SMAPI_GET_FS_INFO_FAILS_SYSACT=<p>Getting file system information fails and information are not displayed in the Space Management Console.</p>
DSI_SMAPI_GET_FS_INFO_FAILS_URESP=<p>See the error log file for additional information.</p>
# 8835
DSI_SMAPI_GET_FS_STATUS_FAILS=ANS8835E The Space Management API was unable to get file system status for \nfile system : {0}. \nSystem call to get file system status returned with error.
DSI_SMAPI_GET_FS_STATUS_FAILS_EXPLANATION=<p>The Space Management API could not retrieve the file system status for a selected file system. The error is caused from a failed system call on the file system.</p>
DSI_SMAPI_GET_FS_STATUS_FAILS_SYSACT=<p>Getting file system status fails and information are not displayed in the Space Management Console.</p>
DSI_SMAPI_GET_FS_STATUS_FAILS_URESP=<p>See the error log file for additional information.</p>
# 8836
DSI_SMAPI_CREATE_OBJECT_ERROR=ANS8836E An object creation error occurred in the Space Management API \nThe error occurred in function : {0}. \nThe problem is caused from a memory problem. Try to free memory \non the system where the Space Management agent is running. \nOr restart the Space Management agent.
DSI_SMAPI_CREATE_OBJECT_ERROR_EXPLANATION=<p>Caused from a out of memory problem the Space Management API could not create a requested object. </p>
DSI_SMAPI_CREATE_OBJECT_ERROR_SYSACT=<p>The requested function fails and cannot retrieve information to the Space Management Console.</p>
DSI_SMAPI_CREATE_OBJECT_ERROR_URESP=<p>Free more memory on the system where the Space Management agent is running, or restart the Space Management agent.</p>
# 8837
DSI_SMAPI_GET_MFSCONFIG_FAILS=ANS8837E The Space Management API was unable to get configuration data \nfrom managed file system : {0}. \nThe problem is caused from a error when reading dsmmigfs table entry.
DSI_SMAPI_GET_MFSCONFIG_FAILS_EXPLANATION=<p>The Space Management API reads information from dsmmigfs table to get HSM managed files system configuration. This error occurs when the API is unable to read an entry from this table.</p>
DSI_SMAPI_GET_MFSCONFIG_FAILS_SYSACT=<p>Getting HSM managed file system configuration fails and information is not displayed in the Space Management Console.</p>
DSI_SMAPI_GET_MFSCONFIG_FAILS_URESP=<p>See the error log for additional information on errors occurring when reading entries from the dsmmigfs table.</p>
# 8838
DSI_SMAPI_FS_NOT_HSM_MANAGED=ANS8838E The Space Management API can not set HSM managed file system \nconfiguration for file system : {0}. \nThe configuration cannot be set because this file system is NOT HSM managed. Check to see if the managed file system that was selected in the file system list is still HSM managed. \nRefresh the file system view in the Space Management Console by pressing F5 on your \nkeyboard or select 'Refresh` under the View menu.
DSI_SMAPI_FS_NOT_HSM_MANAGED_EXPLANATION=<p>The file system that you selected from the file system list in the Space Management console is not longer HSM managed and no configuration can bet set for it. A reason could be that the file system was unmanaged from a other user.</p>
DSI_SMAPI_FS_NOT_HSM_MANAGED_SYSACT=<p>Setting HSM managed file system configuration fails.</p>
DSI_SMAPI_FS_NOT_HSM_MANAGED_URESP=<p>Update the file system list in the Space Management Console by pressing F5 on your keyboard or selecting 'Refresh' in the View menu.</p>
# 8839
DSI_SMAPI_STUBSIZE_NOT_SUPPORTED=ANS8839E A wrong stub file size was passed to the Space Management API for \nfile system : {0}. \nThe stub file size that was entered in the file system properties dialog is not supported \nby this file system. Correct the stub file size value in the file system properties dialog \nof the Space Management Console.
DSI_SMAPI_STUBSIZE_NOT_SUPPORTED_EXPLANATION=<p>The Stub file size that you has specified is not supported by this file system.</p>
DSI_SMAPI_STUBSIZE_NOT_SUPPORTED_SYSACT=<p>Wrong stub file size is not applied to the file system.</p>
DSI_SMAPI_STUBSIZE_NOT_SUPPORTED_URESP=<p>Correct the stub file size in the file system properties dialog of the Space Management Console.</p>
# 8840
DSI_SMAPI_MAXCANDIDATE_OUT_OF_RANGE=ANS8840E The maximum number of candidates that was specified for \nfile system : {0} is out of range. \nThe maximum number of candidates value that was entered in the file system properties dialog is out of range. \nCorrect the maximum number of candidates value in the file system properties dialog \nof the Space Management Console.
DSI_SMAPI_MAXCANDIDATE_OUT_OF_RANGE_EXPLANATION=<p>The maximum number of candidates value that was specified is out of range for this file system.</p>
DSI_SMAPI_MAXCANDIDATE_OUT_OF_RANGE_SYSACT=<p>Wrong maximum number of candidates value is not applied to the file system.</p>
DSI_SMAPI_MAXCANDIDATE_OUT_OF_RANGE_URESP=<p>Correct the maximum number of candidates value in the file system properties dialog of the Space Management Console.</p>
# 8841
DSI_SMAPI_WRONG_SERVERNAME_IN_OPTFILE=ANS8841E The server name that was specified for the file system : \n{0} is not valid. \nCorrect the server name value in the client node properties dialog \nof the Space Management Console.
DSI_SMAPI_WRONG_SERVERNAME_IN_OPTFILE_EXPLANATION=<p>The server name that was specified is not valid.</p>
DSI_SMAPI_WRONG_SERVERNAME_IN_OPTFILE_SYSACT=<p>Wrong server name value is not applied to the system options file.</p>
DSI_SMAPI_WRONG_SERVERNAME_IN_OPTFILE_URESP=<p>Correct the server name value in the client node properties dialog of the Space Management Console.</p>
# 8842
DSI_SMAPI_COULD_NOT_MODIFY_OPTFILE=ANS8842E The Space Management API was not able to modify system options file : \n{0} because of insufficient privilege. \nUse root user to change HSM managed file system configuration.
DSI_SMAPI_COULD_NOT_MODIFY_OPTFILE_EXPLANATION=<p>User has no rights to modify system options file.</p>
DSI_SMAPI_COULD_NOT_MODIFY_OPTFILE_SYSACT=<p>Changes are not applied to the system options file.</p>
DSI_SMAPI_COULD_NOT_MODIFY_OPTFILE_URESP=<p>Run as root user to change HSM managed file system configuration.</p>
# 8843
DSI_SMAPI_INCLEXCL_INCORRECT_IN_OPTFILE=ANS8843E No correct include/exclude settings are found in system options file : \n{0}. \nCorrect the include/exclude list in the system options file. \n
DSI_SMAPI_INCLEXCL_INCORRECT_IN_OPTFILE_EXPLANATION=<p>The include/exclude settings in the system options file are not correct.</p>
DSI_SMAPI_INCLEXCL_INCORRECT_IN_OPTFILE_SYSACT=<p>Changes are not applied to the system options file.</p>
DSI_SMAPI_INCLEXCL_INCORRECT_IN_OPTFILE_URESP=<p>Correct the include/exclude list in the system options file.</p>
# 8844
DSI_SMAPI_UPDATE_PREFNODE_ERROR=ANS8844E A incorrect preferred node or server name was specified in the HSM configuration for \n{0}. \nCorrect the preferred node and server name value in the HSM configuration. \n
DSI_SMAPI_UPDATE_PREFNODE_ERROR_EXPLANATION=<p>The Space Management API could not change preferred node settings because a wrong value was specified</p>
DSI_SMAPI_UPDATE_PREFNODE_ERROR_SYSACT=<p>Changes are not applied to the system options file.</p>
DSI_SMAPI_UPDATE_PREFNODE_ERROR_URESP=<p>Correct the preferred node and server settings in Space Management Configuration.</p>
# 8845
DSI_SMAPI_UPDATE_OWNERNODE_ERROR=ANS8845E A incorrect owner node or server name was specified in the HSM configuration for \n{0}. \nCorrect the owner node and server name value in the HSM configuration. \n
DSI_SMAPI_UPDATE_OWNERNODE_ERROR_EXPLANATION=<p>The Space Management API could not change owner node settings because a wrong value was specified</p>
DSI_SMAPI_UPDATE_OWNERNODE_ERROR_SYSACT=<p>Changes are not applied to the system options file.</p>
DSI_SMAPI_UPDATE_OWNERNODE_ERROR_URESP=<p>Correct the owner node and server settings in Space Management Configuration.</p>
# 8846
DSI_SMAPI_UPDATE_MANGEDFS_ERROR=ANS8846E The Space Management API was not able to update the HSM managed \nfile system : {0}. \n
DSI_SMAPI_UPDATE_MANGEDFS_ERROR_EXPLANATION=<p>The Space Management API could not apply configuration changes to the HSM managed file system.</p>
DSI_SMAPI_UPDATE_MANGEDFS_ERROR_SYSACT=<p>Changes are not applied to HSM managed file system.</p>
DSI_SMAPI_UPDATE_MANGEDFS_ERROR_URESP=<p>See error log file for additional information why the update of the file system fails.</p>
# 8847
DSI_SMAPI_UNABLE_TO_LOCK_SDR_FILE=ANS8847E The Space Management API was not able to obtain a lock on SDR file for \nfile system : {0}. \n
DSI_SMAPI_UNABLE_TO_LOCK_SDR_FILE_EXPLANATION=<p>The Space Management API could not lock the SDR file for the file system.</p>
DSI_SMAPI_UNABLE_TO_LOCK_SDR_FILE_SYSACT=<p>Changes are not applied to HSM managed file system.</p>
DSI_SMAPI_UNABLE_TO_LOCK_SDR_FILE_URESP=<p>See the error log file for additional information on why the lock on the SDR file fails.</p>
# 8848
DSI_SMAPI_OPEN_FSSTATUS_FILE_FAILS=ANS8848E The Space Management API could not open file system status file to retrieve \nmanaged file system statistics for : {0}. \nReason could be insufficient permissions or that the file does not exist. The managed file system statistics are not retrieved from the HSM system.
DSI_SMAPI_OPEN_FSSTATUS_FILE_FAILS_EXPLANATION=<p>The Space Management API could not retrieve managed file system information from file system status file. The error occurred when the API tries to open the file for reading.</p>
DSI_SMAPI_OPEN_FSSTATUS_FILE_FAILS_SYSACT=<p>Managed file system statistics are not retrieved and information is not displayed in the Space Management Console.</p>
DSI_SMAPI_OPEN_FSSTATUS_FILE_FAILS_URESP=<p>See the error log file for additional information on why opening the file system status file fails.</p>
# 8849
DSI_SMAPI_LOAD_FSSTATISTICS_FAILS=ANS8849E The Space Management API was not able to load HSM managed \nfile system statistics for : {0}. \nCheck to see if the managed file system that was selected in the file system list is still HSM managed. \nRefresh the file system view in the Space Management Console by pressing F5 on your \nkeyboard or select 'Refresh` under the View menu.
DSI_SMAPI_LOAD_FSSTATISTICS_FAILS_EXPLANATION=<p>The Space Management API could not load managed file system statistics from selected file system. The reason could be that the file system is not longer HSM managed.</p>
DSI_SMAPI_LOAD_FSSTATISTICS_FAILS_SYSACT=<p>Managed file system statistics are not retrieved and information is not displayed in the Space Management Console.</p>
DSI_SMAPI_LOAD_FSSTATISTICS_FAILS_URESP=<p>Update the file system list in the Space Management Console by pressing F5 on your keyboard or selecting 'Refresh' in the View menu.</p>
# 8850
DSI_SMAPI_ADD_HSM_FAILS_ON_MOUNT=ANS8850E The Space Management API was not able to add HSM to \nfile system : {0}. \nThis error occurs because selected file system is not mounted. \nYou must mount the file system before you can add HSM.
DSI_SMAPI_ADD_HSM_FAILS_ON_MOUNT_EXPLANATION=<p>The Space Management API could not add HSM to a file system, because it is not mounted.</p>
DSI_SMAPI_ADD_HSM_FAILS_ON_MOUNT_SYSACT=<p>The add HSM operation fails and HSM is not added to the selected file system.</p>
DSI_SMAPI_ADD_HSM_FAILS_ON_MOUNT_URESP=<p>Mount the selected file system before adding HSM.</p>
# 8851
DSI_SMAPI_ADD_HSM_FAILS_ON_UNSUPPORTED_FS=ANS8851E The Space Management API was not able to add HSM to \nfile system : {0}. \nThis error occurs because selected file system is not supported to add HSM. \n
DSI_SMAPI_ADD_HSM_FAILS_ON_UNSUPPORTED_FS_EXPLANATION=<p>The Space Management API could not add HSM to a unsupported file system.</p>
DSI_SMAPI_ADD_HSM_FAILS_ON_UNSUPPORTED_FS_SYSACT=<p>The add HSM operation fails and HSM is not added to the selected file system.</p>
DSI_SMAPI_ADD_HSM_FAILS_ON_UNSUPPORTED_FS_URESP=<p>Select a supported file system to add HSM.</p>
# 8852
DSI_SMAPI_HSM_ALREADY_ADDED=ANS8852E The Space Management API was not able to add HSM to \nfile system : {0}. \nThis error occurs because selected file system is already HSM managed. \n
DSI_SMAPI_HSM_ALREADY_ADDED_EXPLANATION=<p>The Space Management API attempt to manage a already HSM managed file system.</p>
DSI_SMAPI_HSM_ALREADY_ADDED_SYSACT=<p>The add HSM operation fails and the selected file system stays HSM managed.</p>
DSI_SMAPI_HSM_ALREADY_ADDED_URESP=<p>Select a not managed file system to add HSM.</p>
# 8853
DSI_SMAPI_ADD_HSM_FAILS=ANS8853E The Space Management API was not able to add HSM to \nfile system : {0}. \n
DSI_SMAPI_ADD_HSM_FAILS_EXPLANATION=<p>The Space Management API attempt to manage file system and fails for a unknown reason.</p>
DSI_SMAPI_ADD_HSM_FAILS_SYSACT=<p>The add HSM operation fails and HSM is not added to the selected file system.</p>
DSI_SMAPI_ADD_HSM_FAILS_URESP=<p>Retry the add HSM operation. If this does not solve the problem, see the error log file for additional information and contact TSM technical support. </p>
# 8854
DSI_SMAPI_REMOVE_HSM_FAILS=ANS8854E The Space Management API was not able to remove HSM from \nfile system : {0}. \nThe error occurs when the Space Management API tries to lock the SDR file and fails.
DSI_SMAPI_REMOVE_HSM_FAILS_EXPLANATION=<p>The Space Management API attempt to unmanage (remove) file system and fails for a unknown reason.</p>
DSI_SMAPI_REMOVE_HSM_FAILS_SYSACT=<p>The remove HSM operation fails and HSM is not removed from the selected file system.</p>
DSI_SMAPI_REMOVE_HSM_FAILS_URESP=<p>Try the remove HSM operation again. If this does not solve the problem, see the error log file for additional information and contact TSM technical support. </p>
# 8855
DSI_SMAPI_START_AUTOMIG_FAILS=ANS8855E The Space Management API was not able to start automatic \nmigration on the file system : {0}. \n
DSI_SMAPI_START_AUTOMIG_FAILS_EXPLANATION=<p>The Space Management API tries to start automatic migration on a file system and fails for a unknown reason.</p>
DSI_SMAPI_START_AUTOMIG_FAILS_SYSACT=<p>The automatic migration is not started for the file system.</p>
DSI_SMAPI_START_AUTOMIG_FAILS_URESP=<p>See the error log file for additional information and contact TSM technical support. </p>
# 8856
DSI_SMAPI_START_RECONCILE_FAILS=ANS8856E The Space Management API was not able to start reconciliation \nprocess on the file system : {0}. \n
DSI_SMAPI_START_RECONCILE_FAILS_EXPLANATION=<p>The Space Management API tries to start reconciliation process on a file system and fails for a unknown reason.</p>
DSI_SMAPI_START_RECONCILE_FAILS_SYSACT=<p>The reconciliation process is not started for the file system.</p>
DSI_SMAPI_START_RECONCILE_FAILS_URESP=<p>See the error log file for additional information, and contact TSM technical support. </p>
# 8857
DSI_SMAPI_START_SCOUT_FAILS=ANS8857E The Space Management API was not able to start scout \nprocess on the file system : {0}. \n
DSI_SMAPI_START_SCOUT_FAILS_EXPLANATION=<p>The Space Management API tries to start scout process on a file system and fails for a unknown reason.</p>
DSI_SMAPI_START_SCOUT_FAILS_SYSACT=<p>The scout process is not started for the file system.</p>
DSI_SMAPI_START_SCOUT_FAILS_URESP=<p>See the error log file for additional information, and contact TSM technical support. </p>
# 8858
DSI_SMAPI_GENERIC_MIGRATE_ERROR=ANS8858E The Space Management API was not able to migrate \nthe file : {0}. \nThe error occurred in function : {1}. \n
DSI_SMAPI_GENERIC_MIGRATE_ERROR_EXPLANATION=<p>The Space Management API tries to migrate a file and fails in the displayed API function.</p>
DSI_SMAPI_GENERIC_MIGRATE_ERROR_SYSACT=<p>The selected file is not migrated to the server.</p>
DSI_SMAPI_GENERIC_MIGRATE_ERROR_URESP=<p>See the error log file for additional information.</p>
# 8859
DSI_SMAPI_GENERIC_RECALL_ERROR=ANS8859E The Space Management API was not able to recall \nthe file : {0}. \nThe error occurred in function : {1}. \n
DSI_SMAPI_GENERIC_RECALL_ERROR_EXPLANATION=<p>The Space Management API tries to recall a file and fails in the displayed API function.</p>
DSI_SMAPI_GENERIC_RECALL_ERROR_SYSACT=<p>The selected file is not recalled from the server.</p>
DSI_SMAPI_GENERIC_RECALL_ERROR_URESP=<p>See the error log file for additional information.</p>
# 8939
DSI_FIND_TREE_NOT_FILTERED=ANS8939E An unexpected error occurred trying to filter the directory tree. \nrc={0}
DSI_FIND_TREE_NOT_FILTERED_EXPLANATION=<p>The filter was not applied to the directory tree.</p>
DSI_FIND_TREE_NOT_FILTERED_SYSACT=<p>The directory tree is not filtered.</p>
DSI_FIND_TREE_NOT_FILTERED_URESP=<p>Contact your system administrator for further assistance.</p>
# 8945
DSI_FIND_TREE_NOT_SEARCHED=ANS8945E An unexpected error occurred analyzing the directory tree. \nThe list of files matching your search criteria is not completed. \nrc={0}
DSI_FIND_TREE_NOT_SEARCHED_EXPLANATION=<p>It was not possible to search all items matching the search criteria on the directory tree due to an unexpected error.</p>
DSI_FIND_TREE_NOT_SEARCHED_SYSACT=<p>The search results table shows only the items found until the error is occurred.</p>
DSI_FIND_TREE_NOT_SEARCHED_URESP=<p>Contact your system administrator for further assistance.</p>
# 9020
Session_connection_error=ANS9020E Could not establish a session with a TSM server or client agent. The TSM return code is {0}. \n
Session_connection_error_EXPLANATION=<p>A communication error occured. The return code is provided to help diagnose the problem.</p>
Session_connection_error_SYSACT=<p>Processing stops.</p>
Session_connection_error_URESP=<p>Check the TSM error log for communications failures such as TCP/IP, shared memory, or named pipe errors.</p>
# 9025
Was_REJECT_DOWNLEVEL=ANS9025E The Data Protection for WebSphere plug-in version and the backup-archive client version do not match. Please upgrade your Data Protection for WebSphere plug-in.\n
Was_REJECT_DOWNLEVEL_EXPLANATION=<p>The release and version of the Data Protection for WebSphere plug-in is downlevel from the release and version of the Backup-Archive Client.</p>
Was_REJECT_DOWNLEVEL_SYSACT=<p>None</p>
Was_REJECT_DOWNLEVEL_URESP=<p>Upgrade Data Protection for WebSphere to the proper release and version. </p>
# 9029
Was_SERVER_UP_ON_RESTORE=ANS9029E The WebSphere server is running, but the server must be shut down for a restore operation. Shut down the WebSphere server and try the restore operation again.\n
Was_SERVER_UP_ON_RESTORE_EXPLANATION=<p>The WebSphere server must be brought down to perform a restore.</p>
Was_SERVER_UP_ON_RESTORE_SYSACT=<p>The restore operation fails.</p>
Was_SERVER_UP_ON_RESTORE_URESP=<p>Shut down the WebSphere server and try the restore operation again.</p>
# 9034
Was_RES_VALIDATION_FAILED=ANS9034E The restore operation did not complete, due to a change in the original WebSphere environment. \n
Was_RES_VALIDATION_FAILED_EXPLANATION=<p>The data must be restored to the same environment that it was backed up from. This includes items such as cell name, node name, and the location where WebSphere is installed.</p>
Was_RES_VALIDATION_FAILED_SYSACT=<p>The restore operation does not complete.</p>
Was_RES_VALIDATION_FAILED_URESP=<p>Perform the restore procedure in the <cit><bibentry><doctitle><titleblk><title>DP for WebSphere </title> </titleblk></doctitle></bibentry></cit> book. </p>
# 9054
PI_NOT_FOUND=ANS9054E The plug-in was not found.\n
PI_NOT_FOUND_EXPLANATION=<p>None.</p>
PI_NOT_FOUND_SYSACT=<p>None</p>
PI_NOT_FOUND_URESP=<p>Run "dsmc show plugins" at the command prompt to see the available plug-ins on the system.</p>
# 9089
Group_BACKUP_VALIDATION_FAILED=ANS9089E The group backup validation failed. One or more files were added, removed, or changed during the backup.\n
Group_BACKUP_VALIDATION_FAILED_EXPLANATION=<p>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 the TSM server. Check the dsmerror.log file for a list of files that were added, removed, or changed.</p>
Group_BACKUP_VALIDATION_FAILED_SYSACT=<p>The backup fails.</p>
Group_BACKUP_VALIDATION_FAILED_URESP=<p>Try the backup again. </p>
# 9091
Was_BACKUP_VALIDATION_FAILED=ANS9091E The WebSphere backup validation failed. One or more files were added, removed, or changed during the backup.\n
Was_BACKUP_VALIDATION_FAILED_EXPLANATION=<p>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 the TSM server. Check the dsmerror.log file for a list of files that were added, removed, or changed.</p>
Was_BACKUP_VALIDATION_FAILED_SYSACT=<p>The backup fails.</p>
Was_BACKUP_VALIDATION_FAILED_URESP=<p>Try the backup again. Do not install new WebSphere applications or change the WebSphere configuration while in the backup window.</p>
# 9092
DSI_ENCRYPTION_Warning=ANS9092W AES 128-bit Encryption is not being used. \n
DSI_ENCRYPTION_Warning_EXPLANATION=<p>AES 128-bit encryption is not being used. DES 56-bit encryption is being used instead.</p>
DSI_ENCRYPTION_Warning_SYSACT=<p>DES 56-bit Encryption is used instead of AES 128-bit encryption. </p>
DSI_ENCRYPTION_Warning_URESP=<p>If the user wants to use AES encryption, then the user must install the IBM JRE in order to enable AES encryption for the web client.</p>
# 9094
DSSM_SM_NoCandidates=ANS9094W {0}: no candidates found in file system {1}.\n
DSSM_SM_NoCandidates_EXPLANATION=<p>TSM found no files eligible for migration in the file system after running dsmreconcile.</p>
DSSM_SM_NoCandidates_SYSACT=<p>TSM continues.</p>
DSSM_SM_NoCandidates_URESP=<p>Continue with normal operation.</p>
# 9117
VMBACKUP_VMName_Contains_Unsupported_Chars=ANS9117E Virtual machine '{0}' will not be backed up because it contains at least one of the following unsupported special characters {1}\n
VMBACKUP_VMName_Contains_Unsupported_Chars_EXPLANATION=<p> The specified virtual machine contains characters that are not supported for virtual machine backup and restore operations. </p>
VMBACKUP_VMName_Contains_Unsupported_Chars_SYSACT=<p>The backup for the specified virtual machine fails.</p>
VMBACKUP_VMName_Contains_Unsupported_Chars_URESP=<p>Rename the virtual machine so that it does not contain any of the specified special characters.</p>
# 9121
DSI_DOM_ACTIVATE_Complete=ANS9121I Activate completed.
# 9128
DSI_DOM_INACTIVATELOG_Complete=ANS9128I Inactivate logs completed.
# 9150
DSI_DOM_ARCHIVELOG_Complete=ANS9150I Archive log completed.
# 9156
DSI_DOM_ROLLFORWARD_Complete=ANS9156I Rollforward completed.
# 9157
DSI_PREFP_NOFILESPACE_LOCATION=ANS9157W Please enter a valid filespace location
DSI_PREFP_NOFILESPACE_LOCATION_EXPLANATION=<p>This message will be seen when you run the Pref editor from MFC GUI. This means that user has not entered a required field which is filespace location path.</p>
DSI_PREFP_NOFILESPACE_LOCATION_SYSACT=<p>TSM Enter required field</p>
DSI_PREFP_NOFILESPACE_LOCATION_URESP=<p>Operation will not proceed till user enters required field</p>
# 9161
CLI_Invalid_Backupset_Source_Entered=ANS9161E Invalid backupset file or device name entered.\n
CLI_Invalid_Backupset_Source_Entered_EXPLANATION=<p> The backupset file or device name specified does not contain a valid backupset. </p>
CLI_Invalid_Backupset_Source_Entered_SYSACT=<p>Processing stopped.</p>
CLI_Invalid_Backupset_Source_Entered_URESP=<p> Specify a file name or device that contains a valid backupset and retry the operation. </p>
# 9172
CLI_SystemWriter_Excluded=ANS9172I Backup system component '{0}' is excluded from processing.\n
# 9173
CLI_SystemWriter_Not_Valid=ANS9173I Backup system component '{0}' doesn't exist.\n
# 9174
DSI_BackDel_Complete=ANS9174I A backup delete completed.
# 9176
DSI_BackDel_Stopped=ANS9176I Backup delete is stopped by the user.
# 9182
DSI_SM_WARNING_NODE_UPDATE=ANS9182W Your customized client nodes list already contains this node. \n\nWould you like to update it?
DSI_SM_WARNING_NODE_UPDATE_EXPLANATION=<p> The list of client nodes contains already the specified client node. You cannot have two client nodes with the same client node name in the same machine. </p>
DSI_SM_WARNING_NODE_UPDATE_SYSACT=<p>Updates or does not update the client node, depending on the user response.</p>
DSI_SM_WARNING_NODE_UPDATE_URESP=<p>Select "yes" to update the client node. Select "no" to cancel this operation.</p>
# 9183
DSI_SM_WARNING_FS_UNMANAGE=ANS9183W Removing Space Management from '{0}' file system \nmeans that all migrated data will be recalled from TSM Server '{1}' \nMake sure that enough free space is present on this file system for the recalled data. \n\nDo you want to remove Space Management from '{2}' now?
DSI_SM_WARNING_FS_UNMANAGE_EXPLANATION=<p>Removing Space Management from the selected file system means that all migrated data will be recalled from the server.</p>
DSI_SM_WARNING_FS_UNMANAGE_SYSACT=<p>Prompts the user to confirm when removing Space Management from the selected file system.</p>
DSI_SM_WARNING_FS_UNMANAGE_URESP=<p>Make sure that enough free space is present on this file system for the recalled data.</p>
# 9185
DSI_SM_MFS_SCOUT_DAEMON_NOT_RUNNING=ANS9185W Master scout daemon is not running!
DSI_SM_MFS_SCOUT_DAEMON_NOT_RUNNING_EXPLANATION=<p>A list of candidates files eligible for migration cannot be built because the master scout daemon is not running on the selected client node.</p>
DSI_SM_MFS_SCOUT_DAEMON_NOT_RUNNING_SYSACT=<p>Files are not automatically migrated to the TSM server. </p>
DSI_SM_MFS_SCOUT_DAEMON_NOT_RUNNING_URESP=<p>Restart the master scout daemon manually using the "dsmscoutd" command from a command shell on the machine where Space Management Agent is running.</p>
# 9187
DSI_SM_MFS_MONITOR_DAEMON_NOT_RUNNING=ANS9187W Monitor daemon is not running!
DSI_SM_MFS_MONITOR_DAEMON_NOT_RUNNING_EXPLANATION=<p>Files cannot be automatically migrated to the TSM server or recalled from TSM server because the monitor daemon is not running on the selected client node.</p>
DSI_SM_MFS_MONITOR_DAEMON_NOT_RUNNING_SYSACT=<p>Files are not automatically migrated or recalled from the TSM server.</p>
DSI_SM_MFS_MONITOR_DAEMON_NOT_RUNNING_URESP=<p>Restart the monitor daemon manually using the "dsmmonitord" command from a command shell on the machine where Space Management Agent is running.</p>
# 9201
CLI_LANFREE_FAILED=ANS9201W LAN-free path failed.\n
CLI_LANFREE_FAILED_EXPLANATION=<p>A LAN-free connection could not be made.</p>
CLI_LANFREE_FAILED_SYSACT=<p>The system will connect to the server without using the LAN-free path. </p>
CLI_LANFREE_FAILED_URESP=<p>Verify your LAN-free setup.</p>
# 9206
DSI_SM_MFS_USER_QUOTA_REACHED=ANS9206W User quota is reached!
DSI_SM_MFS_USER_QUOTA_REACHED_EXPLANATION=<p>The maximum amount of data that can be migrated and premigrated from this file system to the TSM Server is reached.</p>
DSI_SM_MFS_USER_QUOTA_REACHED_SYSACT=<p>Files cannot be migrated to TSM server. </p>
DSI_SM_MFS_USER_QUOTA_REACHED_URESP=<p>Use the File System Properties dialog to specify a different quota value.</p>
# 9220
DSI_SM_MFS_RECALL_DAEMON_NOT_RUNNING=ANS9220W Recall daemon is not running!
DSI_SM_MFS_RECALL_DAEMON_NOT_RUNNING_EXPLANATION=<p>Files cannot be recalled from TSM server because the recall daemon is not running on the selected client node.</p>
DSI_SM_MFS_RECALL_DAEMON_NOT_RUNNING_SYSACT=<p>Files are not recalled from the TSM server. </p>
DSI_SM_MFS_RECALL_DAEMON_NOT_RUNNING_URESP=<p>Restart the recall daemon manually using the "dsmrecalld" command by a command shell on the machine where Space Management Agent is running.</p>
# 9227
DSI_SM_ERROR_LOADING_STATUS=ANS9227E Internal error loading the status: {0}
DSI_SM_ERROR_LOADING_STATUS_EXPLANATION=<p>An exception has been detected loading the status of space management activities.</p>
DSI_SM_ERROR_LOADING_STATUS_SYSACT=<p>The status of the related activity is not loaded. The process continues to load the status at the next refresh interval.</p>
DSI_SM_ERROR_LOADING_STATUS_URESP=<p>Check the dsmsm.log file in the installation directory of your local machine and the $DSM_DIR/dsmerror.log file on the client node machine if present. If this does not identify the cause of the problem, contact your system administrator and/or TSM technical support for further assistance.</p>
# 9230
DSI_SM_MFS_AUTOMIG_COMM_ERROR=ANS9230E Communication error detected in the migration phase of this process!
DSI_SM_MFS_AUTOMIG_COMM_ERROR_EXPLANATION=<p>An unexpected error is occurred due to server communication error in migration phase.</p>
DSI_SM_MFS_AUTOMIG_COMM_ERROR_SYSACT=<p>TSM will not migrate files from this file system.</p>
DSI_SM_MFS_AUTOMIG_COMM_ERROR_URESP=<p>Check the dsmsm.log file in the installation directory of your local machine and the $DSM_DIR/dsmerror.log file on the client node machine if present. If this does not identify the cause of the problem, contact your system administrator and/or TSM technical support for further assistance.</p>
# 9231
DSI_SM_MFS_AUTOMIG_OTHER_ERROR=ANS9231E Processing error detected in the migration phase of this process!
DSI_SM_MFS_AUTOMIG_OTHER_ERROR_EXPLANATION=<p>An unexpected error is occurred due to some processing communication error.</p>
DSI_SM_MFS_AUTOMIG_OTHER_ERROR_SYSACT=<p>TSM will not migrate or premigrate files from this file system.</p>
DSI_SM_MFS_AUTOMIG_OTHER_ERROR_URESP=<p>Check the dsmsm.log file in the installation directory of your local machine and the $DSM_DIR/dsmerror.log file on the client node machine if present. If this does not identify the cause of the problem, contact your system administrator and/or TSM technical support for further assistance.</p>
# 9233
DSI_SM_MFS_AUTOMIG_PRE_MIG_ERROR=ANS9233E Processing error detected in the premigration phase of this process!
DSI_SM_MFS_AUTOMIG_PRE_MIG_ERROR_EXPLANATION=<p>An unexpected error is occurred due to some processing communication error in the premigration phase.</p>
DSI_SM_MFS_AUTOMIG_PRE_MIG_ERROR_SYSACT=<p>TSM will not premigrate files from this file system.</p>
DSI_SM_MFS_AUTOMIG_PRE_MIG_ERROR_URESP=<p>Check the dsmsm.log file in the installation directory of your local machine and the $DSM_DIR/dsmerror.log file on the client node machine if present. If this does not identify the cause of the problem, contact your system administrator and/or TSM technical support for further assistance.</p>
# 9236
DSI_SM_MFS_RECONCILATION_PROCESS_FAILED=ANS9236E Error detected performing reconciliation on this file system!
DSI_SM_MFS_RECONCILATION_PROCESS_FAILED_EXPLANATION=<p>An error is occurred performing reconciliation on the selected file system.</p>
DSI_SM_MFS_RECONCILATION_PROCESS_FAILED_SYSACT=<p>TSM will not reconcile this file system with TSM server.</p>
DSI_SM_MFS_RECONCILATION_PROCESS_FAILED_URESP=<p>Check the dsmsm.log file in the installation directory of your local machine and the $DSM_DIR/dsmerror.log file on the client node machine if present. If this does not identify the cause of the problem, contact your system administrator and/or TSM technical support for further assistance.</p>
# 9263
DSI_RESTORE_ACTIVE_INACTIVE_SYSSTATE=ANS9263W You cannot restore both active and inactive versions of System State.
DSI_RESTORE_ACTIVE_INACTIVE_SYSSTATE_EXPLANATION=<p>Restoring an active copy and inactive copy of System State is not allowed.</p>
DSI_RESTORE_ACTIVE_INACTIVE_SYSSTATE_SYSACT=<p>No processing takes place.</p>
DSI_RESTORE_ACTIVE_INACTIVE_SYSSTATE_URESP=<p>Select either the active copy or the inactive copy to perform restore operation. </p>
# 9264
CLI_VMBACKUP_ConsoleStatus9_Incr_backup_of_VM_Failed=ANS9264E Incremental backup of Virtual Machine '{0}' failed with RC {1}\n
CLI_VMBACKUP_ConsoleStatus9_Incr_backup_of_VM_Failed_EXPLANATION=<p> The incremental backup of virtual machine volumes failed. </p>
CLI_VMBACKUP_ConsoleStatus9_Incr_backup_of_VM_Failed_SYSACT=<p> The backup of the virtual machine finished with failures. The next virtual machine in the vmlist will be processed. The reason for the failure is written to the local client error log. </p>
CLI_VMBACKUP_ConsoleStatus9_Incr_backup_of_VM_Failed_URESP=<p> Check the local client error log for reason for the failure. </p>
# 9265
CLI_VMBACKUP_ConsoleStatus10_Mount_of_VM_Failed=ANS9265E Failure mounting Virtual Machine '{0}' with vcbMounter command. RC={1}\n
CLI_VMBACKUP_ConsoleStatus10_Mount_of_VM_Failed_EXPLANATION=<p> The VMware vcbmount command failed to mount virtual machine disk. </p>
CLI_VMBACKUP_ConsoleStatus10_Mount_of_VM_Failed_SYSACT=<p> The backup of the virtual machine can not continue. The next virtual machine in the vmlist will be processed. The output of the vcbMounter command will show the reason for the failure. </p>
CLI_VMBACKUP_ConsoleStatus10_Mount_of_VM_Failed_URESP=<p> Issue a vcbMounter command for the virtual machine to determine the reason for the failure. Refer to the documentation for that message for more information. </p>
# 9266
CLI_VMBACKUP_ConsoleStatus11_VMInit_Failed=ANS9266E Failure initializing virtual machine environment. Can not find vcbMounter.exe command. RC={0}\n
CLI_VMBACKUP_ConsoleStatus11_VMInit_Failed_EXPLANATION=<p> Failure initializing virtual machine environment. Can not find vcbMounter.exe command. The VMware Consolidated Backup Framework not installed or vcbMounter.exe command is not located in current PATH environment variable. </p>
CLI_VMBACKUP_ConsoleStatus11_VMInit_Failed_SYSACT=<p> The backup can not continue. The output of the vcbMounter command will show the reason for the failure. </p>
CLI_VMBACKUP_ConsoleStatus11_VMInit_Failed_URESP=<p> Issue a vcbMounter command for the virtual machine to determine the reason for the failure. Refer to the documentation for that message for more information. The VMware Consolidated Backup Framework must be installed on the Backup Proxy machine. The installed location and the vcbMounter.exe must be located in the PATH environment variable. The default location is C:\\Program Files\\VMware\\VMware Consolidated Backup Framework. </p>
# 9267
DSSM_SM_FileSystemExceedQuota=ANS9267E {0}: File system {1} has exceeded its quota.\n
DSSM_SM_FileSystemExceedQuota_EXPLANATION=<p>TSM detects that the file system has exceeded its quota. No more data can be migrated out of this file system.</p>
DSSM_SM_FileSystemExceedQuota_SYSACT=<p>TSM will not migrate files from this file system.</p>
DSSM_SM_FileSystemExceedQuota_URESP=<p>Recall some files, or ask the system administrator to increase the quota for this file system.</p>
# 9278
CLI_VMBACKUP_ConsoleStatus12_VMGetVMList_Failed=ANS9278E Failure processing vmList option. RC={0}\n
CLI_VMBACKUP_ConsoleStatus12_VMGetVMList_Failed_EXPLANATION=<p> Failure processing vmList option. </p>
CLI_VMBACKUP_ConsoleStatus12_VMGetVMList_Failed_SYSACT=<p> The backup can not continue. </p>
CLI_VMBACKUP_ConsoleStatus12_VMGetVMList_Failed_URESP=<p> Check for errors in the vmList option value. Refer to the documentation for the vmList option for more information. </p>
# 9279
CLI_VMBACKUP_ConsoleStatus13_GetVM_Alllocal_Failed=ANS9279E Failure locating Virtual Machine '{0}' volumes. Failed with RC={1}\n
CLI_VMBACKUP_ConsoleStatus13_GetVM_Alllocal_Failed_EXPLANATION=<p> Virtual machine volumes can not found. Volume mount points are not available on Backup Proxy machine. </p>
CLI_VMBACKUP_ConsoleStatus13_GetVM_Alllocal_Failed_SYSACT=<p> The backup of the virtual machine can not continue. The next virtual machine in the vmlist will be processed. The output of the vcbMounter command will show the reason for the failure. </p>
CLI_VMBACKUP_ConsoleStatus13_GetVM_Alllocal_Failed_URESP=<p> Issue a vcbMounter command for the virtual machine to determine the reason for the failure. Refer to the documentation for that message for more information. </p>
# 9280
CLI_VMBACKUP_Error1_Option_Missing=ANS9280E '{0}' option must be set when running this operation.\n
CLI_VMBACKUP_Error1_Option_Missing_EXPLANATION=<p> A required option for the command is missing. </p>
CLI_VMBACKUP_Error1_Option_Missing_SYSACT=<p> The operation can not continue. </p>
CLI_VMBACKUP_Error1_Option_Missing_URESP=<p> Set the missing option using the Preference Editor or the command line. </p>
# 9287
Img_Invalid_Device=ANS9287E Invalid or unsupported device.\n
Img_Invalid_Device_EXPLANATION=<p> The logical volume device is either invalid or unsupported.\nRefer to the documentation for device type support for image backup. </p>
Img_Invalid_Device_SYSACT=<p> The logical volume operation is not performed. </p>
Img_Invalid_Device_URESP=<p> For image backup source or image restore destination, specify a device of one of the supported types. </p>
# 9301
CLI_VMBACKUP_ConsoleStatus38_Fullvm_backup_Failed=ANS9301E Full VM backup of Virtual Machine '{0}' failed with RC {1}\n
CLI_VMBACKUP_ConsoleStatus38_Fullvm_backup_Failed_EXPLANATION=<p> The Full VM backup of virtual machine failed. </p>
CLI_VMBACKUP_ConsoleStatus38_Fullvm_backup_Failed_SYSACT=<p> The full backup of the virtual machine finished with failures. The next virtual machine in the vmlist will be processed. The reason for the failure is written to the local client error log. </p>
CLI_VMBACKUP_ConsoleStatus38_Fullvm_backup_Failed_URESP=<p> Check the local client error log for reason for the failure. </p>
# 9302
CLI_VMBACKUP_ConsoleStatus39_Restore_Filelevel_Not_Supported=ANS9302E The Restore VM command does not support VMBACKUPTYPE=FILE data.\nVM File level restore must be run from inside the virtual machine or with the 'asnodename' option.\n
CLI_VMBACKUP_ConsoleStatus39_Restore_Filelevel_Not_Supported_EXPLANATION=<p> The Restore VM function not supported for file level data. </p>
CLI_VMBACKUP_ConsoleStatus39_Restore_Filelevel_Not_Supported_SYSACT=<p>The system does not process your requested action.</p>
CLI_VMBACKUP_ConsoleStatus39_Restore_Filelevel_Not_Supported_URESP=<p>Virtual machine File level restore must be run from inside the virtual machine or with the asnodename option. To process a full virtual machine restore, issue the command with VMBACKUPTYPE=FULLVM.</p>
# 9303
CLI_VMBACKUP_ConsoleStatus40_Fullvm_Restore_Failed=ANS9303E Full VM restore of Virtual Machine '{0}' failed with RC {1}\n
CLI_VMBACKUP_ConsoleStatus40_Fullvm_Restore_Failed_EXPLANATION=<p> The Full VM restore of virtual machine failed. </p>
CLI_VMBACKUP_ConsoleStatus40_Fullvm_Restore_Failed_SYSACT=<p> The full restore of the virtual machine finished with failures. The next virtual machine in the vmlist will be processed. The reason for the failure is written to the local client error log. </p>
CLI_VMBACKUP_ConsoleStatus40_Fullvm_Restore_Failed_URESP=<p> Check the local client error log for reason for the failure. </p>
# 9304
CLI_VMBACKUP_ConsoleStatus41_Restore_Launching_Converter_Failed=ANS9304E VMware Converter tool not installed on system.\n
CLI_VMBACKUP_ConsoleStatus41_Restore_Launching_Converter_Failed_EXPLANATION=<p> VMware Converter tool install could not be detected on system. </p>
CLI_VMBACKUP_ConsoleStatus41_Restore_Launching_Converter_Failed_SYSACT=<p> The full virtual machine image files have been restored successfully at the specified location. </p>
CLI_VMBACKUP_ConsoleStatus41_Restore_Launching_Converter_Failed_URESP=<p> No further action is necessary. The full virtual machine images files can be used by various tools. VMware Converter tool can be installed on system. </p>
# 9305
CLI_Invalid_HyperV_VMname=ANS9305E Invalid Hyper-V VM name '{0}' entered\n
CLI_Invalid_HyperV_VMname_EXPLANATION=<p>You entered a Hyper-V VM name <mv>string</mv> that contains incorrect characters or contains wildcard characters.</p>
CLI_Invalid_HyperV_VMname_SYSACT=<p>Processing stopped.</p>
CLI_Invalid_HyperV_VMname_URESP=<p>Enter a correct Hyper-V VM name.</p>
# 9306
CLI_Invalid_HyperV_VMList=ANS9306E Invalid Hyper-V VM list '{0}' entered\n
CLI_Invalid_HyperV_VMList_EXPLANATION=<p>You entered a Hyper-V VM list <mv>string</mv> that contains incorrect characters or contains wildcard characters.</p>
CLI_Invalid_HyperV_VMList_SYSACT=<p>Processing stopped.</p>
CLI_Invalid_HyperV_VMList_URESP=<p>Enter a correct Hyper-V VM list.</p>
# 9307
CLI_No_HyperV_VMname=ANS9307E No Hyper-V VM name or VMList entered\n
CLI_No_HyperV_VMname_EXPLANATION=<p>No Hyper-V VM name or VMList parameter was specified.</p>
CLI_No_HyperV_VMname_SYSACT=<p>Processing stopped.</p>
CLI_No_HyperV_VMname_URESP=<p>Specify a correct Hyper-V VM name or VMList parameter.</p>
# 9308
CLI_No_HyperV_VMname_found=ANS9308E No match found for the Hyper-V VM name or VMList '{0}' entered\n
CLI_No_HyperV_VMname_found_EXPLANATION=<p>No match found for the Hyper-V VM name or VMList parameter entered.</p>
CLI_No_HyperV_VMname_found_SYSACT=<p>Processing stopped.</p>
CLI_No_HyperV_VMname_found_URESP=<p>Specify a correct Hyper-V VM name or VMList parameter.</p>
# 9309
CLI_HyperV_VMname_found_with_Pick=ANS9309E Pick option specified but also a value for the Hyper-V VM name or VMList '{0}' entered\n
CLI_HyperV_VMname_found_with_Pick_EXPLANATION=<p>You cannot specify the -pick option and also include a Hyper-V VM name or VMList parameter.</p>
CLI_HyperV_VMname_found_with_Pick_SYSACT=<p>Processing stopped.</p>
CLI_HyperV_VMname_found_with_Pick_URESP=<p>Specify the -pick option without a Hyper-V VM name or VMList parameter.</p>
# 9310
CLI_Rest_HyperV_Confirm=*****WARNING******\nRestoring the selected Virtual Machine(s) '{0}'\nwill stop the VM, delete all the VM files, then restore the VM with the backup.\nIt is recomended that you manually shutdown the VM before proceeding to cleanly\nstop any applications running inside the VM.\nAre you sure you want to proceed?
# 9311
CLI_No_HyperV_VMs_on_Server=ANS9311E No Hyper-V VMs exist on the TSM server\n
CLI_No_HyperV_VMs_on_Server_EXPLANATION=<p>No filespaces representing a Hyper-V Virtual Machine currently exist on the TSM server.</p>
CLI_No_HyperV_VMs_on_Server_SYSACT=<p>Processing stopped.</p>
CLI_No_HyperV_VMs_on_Server_URESP=<p>You must successfully backup a Hyper-V Virtual Machine before using this command.</p>
# 9347
VMBACKUP_Domain_keyword_host_warning=ANS9347W Warning:'{0}' specified on Domain will be ignored when connecting to VMware ESX/ESXi host. Connect to VMware vCenter to process this domain.\n
VMBACKUP_Domain_keyword_host_warning_EXPLANATION=<p>None.</p>
VMBACKUP_Domain_keyword_host_warning_SYSACT=<p>Domain keyword is ignored.</p>
VMBACKUP_Domain_keyword_host_warning_URESP=<p>Connect to VMware vCenter to process this domain.</p>
# 9350
CLI_VSS_Mixed_Transport_volumes=ANS9350E Backup operation failed due to volume mixture.\nPlease refer to explanation section for additional information.\n
CLI_VSS_Mixed_Transport_volumes_EXPLANATION=<p> IBM Tivoli Storage Manager failed to create the backup because of the mixture of volumes was detected. Some volumes selected meet the requirements for importing snapshots only when needed and some do not. This situation occurs when a backup operation is requested and the "Import VSS snapshots Only When Needed" feature is enabled and not all the volumes involved in the backup operation are managed by a VSS Hardware Provider that supports transportable snapshots. Additionally the situation can also occur in a clustered environment during a backup operation, when not all the volumes involved in the backup operation are managed by a VSS Hardware Provider that supports transportable snapshots. </p>
CLI_VSS_Mixed_Transport_volumes_SYSACT=<p>processing stops.</p>
CLI_VSS_Mixed_Transport_volumes_URESP=<p> Try the operation again by splitting the backup operation. Ensure that all the volumes involved in the backup operation are either managed by a Hardware Provider that supports transportable snapshots or that all the volumes involved in the operation do not support transportable snapshots. Additionally you may also turn off the "Import VSS snapshots Only When Needed" feature to allow the backup to allow the mixure. </p>
# 9351
DSC_RC_AbortDataUnavailableSkipped=ANS9351E Data was not available on server and was skipped.
DSC_RC_AbortDataUnavailableSkipped_EXPLANATION=<p> The data to be restored is not available on the server, so it will not be restored. </p>
DSC_RC_AbortDataUnavailableSkipped_SYSACT=<p> The data is skipped, and the restore processing continues with the next object to be restored. </p>
DSC_RC_AbortDataUnavailableSkipped_URESP=<p> Contact your TSM administrator. </p>
# 9356
vStorAPI_Error_Reported=ANS9356E A VMware vStorage API error was reported.\n
vStorAPI_Error_Reported_EXPLANATION=<p>A VMware vStorage API was reported. See other messages displayed and logged for additional information about the problem.</p>
vStorAPI_Error_Reported_SYSACT=<p>Processing stops.</p>
vStorAPI_Error_Reported_URESP=<p>Check the dsmerror log file for additional information, and contact the IBM Tivoli Storage Manager administrator with the information provided in this message.</p>
# 9364
CLI_VMBACKUP_Console_VMInit_Failed=ANS9364E Failure initializing virtual machine environment. Refer to dsmerror.log for detailed error messages.\n
CLI_VMBACKUP_Console_VMInit_Failed_EXPLANATION=<p> Failure initializing virtual machine environment. Refer to dsmerror.log for detailed error messages. </p>
CLI_VMBACKUP_Console_VMInit_Failed_SYSACT=<p> The backup can not continue. </p>
CLI_VMBACKUP_Console_VMInit_Failed_URESP=<p> Refer to dsmerror.log for detailed error message. </p>
# 9366
DSI_QUERY_LOCAL_FS_FAILED=An attempt to query local file systems failed. \n\nFor more information, please see the log file.
# 9367
DSI_NO_JBB_SUPPORTED_FS_FOUND=No file systems that can be supported by TSM Journal Engine were found. \n\nFor more information, please see the log file.
# 9373
VMBACKUP_TSM_OpenSSLStub_VDDK_NotInstall=ANS9373E VMware vStorage API environment could not be found.\nInstall the VMware VDDK and copy VMware runtime libraries from the VDDK bin directory to TSM baclient directory.\n
VMBACKUP_TSM_OpenSSLStub_VDDK_NotInstall_EXPLANATION=<p> Failure initializing virtual machine environment. </p>
VMBACKUP_TSM_OpenSSLStub_VDDK_NotInstall_SYSACT=<p> The backup can not continue. </p>
VMBACKUP_TSM_OpenSSLStub_VDDK_NotInstall_URESP=<p> Make sure the VMware VDDK is installed and copy VMware runtime libraries from VDDK bin directory to TSM baclient directory. </p>
# 9374
VMBACKUP_VDDK_Driver_Not_Loaded_VDDKInstall=ANS9374E VMware vStorage virtual storage driver service is not running or could not be found.\nMake sure VMware 'vstor2-mntapi10.sys' service is installed and running. Install the VMware VDDK.\n
VMBACKUP_VDDK_Driver_Not_Loaded_VDDKInstall_EXPLANATION=<p> Failure initializing virtual machine environment. </p>
VMBACKUP_VDDK_Driver_Not_Loaded_VDDKInstall_SYSACT=<p> The backup can not continue. </p>
VMBACKUP_VDDK_Driver_Not_Loaded_VDDKInstall_URESP=<p> Make sure the VMware 'vstor2-mntapi10.sys' service is installed and running. Install the VMware VDDK. VMware. </p>
# 9375
VMBACKUP_VDDK_Driver_Not_Loaded_TSMInstall=ANS9375E VMware vStorage virtual storage driver service is not running or could not be found.\nMake sure VMware 'vstor2-mntapi10.sys' service is installed and running. Run the TSM install selecting the vmwaretools feature or install the VMware VDDK.\n
VMBACKUP_VDDK_Driver_Not_Loaded_TSMInstall_EXPLANATION=<p> Failure initializing virtual machine environment. </p>
VMBACKUP_VDDK_Driver_Not_Loaded_TSMInstall_SYSACT=<p> The backup can not continue. </p>
VMBACKUP_VDDK_Driver_Not_Loaded_TSMInstall_URESP=<p> Make sure the VMware 'vstor2-mntapi10.sys' service is installed and running. Run the TSM install selecting the vmwaretools or install the VMware VDDK. VMware. </p>
# 9377
CLI_VMBACKUP_VMGetVMList_Failed=ANS9377E No virtual machine is specified on the {0} command or the virtual machine domain list could not be processed.\n
CLI_VMBACKUP_VMGetVMList_Failed_EXPLANATION=<p>No virtual machine found with name or specified in domain option.</p>
CLI_VMBACKUP_VMGetVMList_Failed_SYSACT=<p>Processing stops.</p>
CLI_VMBACKUP_VMGetVMList_Failed_URESP=<p>Specify a correct VM name or domain option.</p>
# 9378
Data_Fingerprint_Error=ANS9378E Unexpected error while fingeprinting the data
Data_Fingerprint_Error_EXPLANATION=<p> There was an error while fingerprinting the data. See the error log for more information. </p>
Data_Fingerprint_Error_SYSACT=<p>The object is not backed up.</p>
Data_Fingerprint_Error_URESP=<p> Retry the operation. Retry the operation without client-side deduplication. If the problem persists, contact TSM technical support. </p>
# 9379
Data_Dedup_Error=ANS9379E Unexpected error while deduplicating the data
Data_Dedup_Error_EXPLANATION=<p> There was an error while deduplicating the data. See the error log for more information. </p>
Data_Dedup_Error_SYSACT=<p>The object is not backed up.</p>
Data_Dedup_Error_URESP=<p> Retry the operation. Retry the operation without client-side deduplication. If the problem persists, contact TSM technical support. </p>
# 9380
CLI_VMBACKUP_No_VM_found=ANS9380E No virtual machine found processing {0} command.\n
CLI_VMBACKUP_No_VM_found_EXPLANATION=<p>No virtual machine found with name or specified in domain option.</p>
CLI_VMBACKUP_No_VM_found_SYSACT=<p>Processing stopped.</p>
CLI_VMBACKUP_No_VM_found_URESP=<p>Specify a correct VM name or domain option.</p>
# 9381
VMBACKUP_VMList_to_Domain=ANS9381I The value set for {0} option will be migrated to the new {1} option.\n
# 9383
VMBACKUP_VDDK_TSMInstall_comp_not_installed=ANS9383E Required files for VMware vStorage virtual machine backup could not be found.\nRun the TSM install selecting the vmwaretools feature or install the VMware VDDK.\n
VMBACKUP_VDDK_TSMInstall_comp_not_installed_EXPLANATION=<p> Failure initializing virtual machine environment. </p>
VMBACKUP_VDDK_TSMInstall_comp_not_installed_SYSACT=<p> The backup can not continue. </p>
VMBACKUP_VDDK_TSMInstall_comp_not_installed_URESP=<p> Run the TSM install selecting the vmwaretools feature. VMware. </p>
# 9384
VMBACKUP_CBT_Failed_Full_Instead_All_Data=ANS9384W Unable to get VMware Changed Block Tracking(CBT) data for virtual machine '{0}'. Full VM backup continues, and includes both used and unused areas of the disk.\n
VMBACKUP_CBT_Failed_Full_Instead_All_Data_EXPLANATION=<p>IBM Tivoli Storage Manager was unable to obtain Changed Block Tracking(CBT) data for the specified virtual machine. The backup continues, but instead of backing up just the used blocks (in the full VM backup case), or just the changed blocks (in the incremental VM backup case), the entire virtual machine is backed up. This backup includes both the used and unused blocks of the disk. </p>
VMBACKUP_CBT_Failed_Full_Instead_All_Data_SYSACT=<p>The backup continues.</p>
VMBACKUP_CBT_Failed_Full_Instead_All_Data_URESP=<p>See the error log dsmerror.log for information about why the changed block data is not obtained.</p>
# 9386
VMBACKUP_CBT_Not_Supported_Full_Instead_All_Data=ANS9386W Changed block tracking is not supported for virtual machine '{0}'. A FULL backup of the disk will be performed and will include both used and unused areas of the disk.\n
VMBACKUP_CBT_Not_Supported_Full_Instead_All_Data_EXPLANATION=<p>IBM Tivoli Storage Manager was unable to obtain Changed Block Tracking(CBT) data for the specified virtual machine because changed block tracking is not supported. RDM disks in physical mode, virtual disks attached to shared virtual SCSI bus, and VMs with hardware version 6 or earlier are not supported. The backup continues, but instead of backing up just the used blocks (in the full VM backup case), or just the changed blocks (in the incremental VM backup case), the entire virtual machine is backed up. This backup includes both the used and unused blocks of the disk. </p>
VMBACKUP_CBT_Not_Supported_Full_Instead_All_Data_SYSACT=<p>The backup continues.</p>
VMBACKUP_CBT_Not_Supported_Full_Instead_All_Data_URESP=<p>See the error log dsmerror.log for information about why the changed block data is not obtained.</p>
# 9387
VMBACKUP_Incr_Failed_Full_Instead=ANS9387W Incremental backup unsuccessful for virtual machine '{0}'. Performing Full backup instead.\n
VMBACKUP_Incr_Failed_Full_Instead_EXPLANATION=<p>IBM Tivoli Storage Manager was unable to perform an incremental backup of the specified virtual machine. The backup continues, but a full backup will be performed instead. </p>
VMBACKUP_Incr_Failed_Full_Instead_SYSACT=<p>The backup continues.</p>
VMBACKUP_Incr_Failed_Full_Instead_URESP=<p>See the error log dsmerror.log for information about why the changed block data is not obtained.</p>
# 9388
VMBACKUP_Mgmt_Class_Invalid_Or_NoBackupCG=ANS9388E The management class '{0}' specified for. the '{1}' option is invalid, or does not have a backup copy group.\n
VMBACKUP_Mgmt_Class_Invalid_Or_NoBackupCG_EXPLANATION=<p> The management class name for the specified option does not exist, or it exists but does not have a valid backup copy group. </p>
VMBACKUP_Mgmt_Class_Invalid_Or_NoBackupCG_SYSACT=<p>Processing stops.</p>
VMBACKUP_Mgmt_Class_Invalid_Or_NoBackupCG_URESP=<p>Verify that the specified management class name is valid, and that it contains a valid backup copy group.</p>
# 9389
VMBACKUP_Dedup_Unsuccessful_Retry_No_Dedup=ANS9389W The DEDUP backup attempt was unsuccessful for virtual machine '{0}'. Retry #{1} with DEDUP disabled.\n
VMBACKUP_Dedup_Unsuccessful_Retry_No_Dedup_EXPLANATION=<p> The attempt to backup the virtual machine with DEDUP enabled was unsuccessful. Instead of failing the backup right away, an attempt is being made to backup the virtual machine with DEDUP disabled. </p>
VMBACKUP_Dedup_Unsuccessful_Retry_No_Dedup_SYSACT=<p>Processing continues with DEDUP disabled.</p>
VMBACKUP_Dedup_Unsuccessful_Retry_No_Dedup_URESP=<p>Check the log files for messages as to why DEDUP failed. If future attempts to backup using DEDUP fail, contact your system administator.</p>
# 9390
VMBACKUP_Dedup_Unsuccessful_Retry_With_Dedup=ANS9390W The DEDUP backup attempt was unsuccessful for virtual machine '{0}'. Retry #{1} with DEDUP still enabled.\n
VMBACKUP_Dedup_Unsuccessful_Retry_With_Dedup_EXPLANATION=<p> The attempt to backup the virtual machine with DEDUP enabled was unsuccessful. Instead of failing the backup right away, an attempt is being made to retry the backup of the virtual machine with DEDUP still enabled. </p>
VMBACKUP_Dedup_Unsuccessful_Retry_With_Dedup_SYSACT=<p>Processing continues with DEDUP still enabled.</p>
VMBACKUP_Dedup_Unsuccessful_Retry_With_Dedup_URESP=<p>Check the log files for messages as to why DEDUP failed. If future attempts to backup using DEDUP fail, contact your system administator.</p>
# 9391
VMBACKUP_warn_efi_linux_workaround=ANS9391W Linux guest OS with EFI Boot enabled is not fully supported by TSM VMware backup. Manual steps may be required following restore to enable the virtual machine to power on correctly.\n
VMBACKUP_warn_efi_linux_workaround_EXPLANATION=<p> A restored Linux guest OS with EFI boot enabled may not successfully start. Manual steps are required to successfully boot the guest OS.</p>
VMBACKUP_warn_efi_linux_workaround_SYSACT=<p>Restore processing continues.</p>
VMBACKUP_warn_efi_linux_workaround_URESP=<p>Following guest OS restore: remove and reattach the guest Linux boot disk, select Guest Boot Option to enter EFI setup configuration on next boot, power on the guest, enter EFI Boot Maintenance, add Boot Device, select unnamed volume, give it a label, save and commit changes, continue with boot.</p>
# 9392
CLI_No_Backupset_Entered=ANS9392W No backupset name entered.\n
CLI_No_Backupset_Entered_EXPLANATION=<p>You must provide a backupset for this operation.</p>
CLI_No_Backupset_Entered_SYSACT=<p>Processing stops.</p>
CLI_No_Backupset_Entered_URESP=<p>Specify a valid backupset name.</p>
# 9393
CLI_Incorrect_Backupset_Entered=ANS9393W Incorrect backupset name entered.\n
CLI_Incorrect_Backupset_Entered_EXPLANATION=<p>The backupset name provided was invalid. Wildcards are not allowed.</p>
CLI_Incorrect_Backupset_Entered_SYSACT=<p>Processing stops.</p>
CLI_Incorrect_Backupset_Entered_URESP=<p>Specify a valid backupset name.</p>
# 9394
CLI_No_Backupset_Source_Entered=ANS9394W No backupset file or device name entered.\n
CLI_No_Backupset_Source_Entered_EXPLANATION=<p>You must provide a backupset file or device name for this operation.</p>
CLI_No_Backupset_Source_Entered_SYSACT=<p>Processing stops.</p>
CLI_No_Backupset_Source_Entered_URESP=<p>Specify a valid backupset file or device name.</p>
# 9395
CLI_VM_Old_Style_Backup_On_Top_New=ANS9395E The filespace has been migrated to the incremental forever model; MODE=FULL and MODE=INCR are not valid.\n
CLI_VM_Old_Style_Backup_On_Top_New_EXPLANATION=<p>You must run only incremental forever backup types (IFINCR or IFFULL) if the filespace has been migrated to the incremental forever type.</p>
CLI_VM_Old_Style_Backup_On_Top_New_SYSACT=<p>Processing stops.</p>
CLI_VM_Old_Style_Backup_On_Top_New_URESP=<p>Specify either MODE=IFFULL or MODE=IFINCR.</p>
# 9396
APP_VM_NOT_RUNNING=ANS9396W Virtual machine '{0}' is not running. IBM Tivoli Storage Manager can not protect VMs that are not running. IBM Tivoli Storage Manager application protection will not be used.\n
APP_VM_NOT_RUNNING_EXPLANATION=<p>IBM Tivoli Storage Manager can only protect VMs that are running.</p>
APP_VM_NOT_RUNNING_SYSACT=<p>IBM Tivoli Storage Manager uses the VMWare tools to provide application consistency.</p>
APP_VM_NOT_RUNNING_URESP=<p> Power on the virtual machine or exclude it from TSM application protection by removing the INCLUDE.VMTSMVSS option for this virtual machine. If you want logs to be truncated use INCLUDE.VMTSMVSS to protect this machine. </p>
# 9397
APP_VM_NOT_SUPPORTED=ANS9397W TSM application protection cannot protect this machine. Virtual machine '{0}' does not have operating system or applications supported by TSM application protection.
APP_VM_NOT_SUPPORTED_EXPLANATION=<p> The application protection can be used only for virtual machines that have operating systems or applications that are supported by IBM Tivoli Storage Manager application protection. Refer to the product documentation for the list of supported operating systems and applications. </p>
APP_VM_NOT_SUPPORTED_SYSACT=<p>IBM Tivoli Storage Manager will use the VMware Tools to provide application consistency.</p>
APP_VM_NOT_SUPPORTED_URESP=<p> Exclude the virtual machine from application protection by removing the INCLUDE.VMTSMVSS option for this virtual machine. </p>
# 9398
APP_VM_INIT_FAILED=ANS9398E IBM Tivoli Storage Manager application protection failed to initialize on virtual machine '{0}'. See the error log for more details.\n
APP_VM_INIT_FAILED_EXPLANATION=<p> TSM application protection encountered an error during initialization. </p>
APP_VM_INIT_FAILED_SYSACT=<p>Processing stops.</p>
APP_VM_INIT_FAILED_URESP=<p> See the TSM error log for more details. Correct the error(s) and try the operation again. </p>
# 9404
VMBACKUP_Create_VM_Failed=ANS9404E Error creating the specified Virtual Machine. See log files for more information.\n
VMBACKUP_Create_VM_Failed_EXPLANATION=<p>An error was encountered creating the Virtual Machine. Look in the dsmerror.log for additional information on why the Virtual Machine could not be created.</p>
VMBACKUP_Create_VM_Failed_SYSACT=<p>Processing stops.</p>
VMBACKUP_Create_VM_Failed_URESP=<p>Check the dsmerror.log for more specific messages on why the virtual machine could not be created.</p>
# 9410
APP_VM_VMWARE_TOOLS_NOT_RUNNING=ANS9410W VMware Tools are either not runnning or out-of-date on virtual machine '{0}'. IBM Tivoli Storage Manager application protection cannot be used.\n
APP_VM_VMWARE_TOOLS_NOT_RUNNING_EXPLANATION=<p> IBM Tivoli Storage Manager application protection requires that VMware tools are installed and running with an up-to-date version on the virtual machine. </p>
APP_VM_VMWARE_TOOLS_NOT_RUNNING_SYSACT=<p>TSM will not provide application consistency. Application logs are not truncated.</p>
APP_VM_VMWARE_TOOLS_NOT_RUNNING_URESP=<p> Install and/or upgrade and/or start VMware Tools on the virtual machine or exclude it from the application protection by removing the INCLUDE.VMTSMVSS option for this virtual machine. </p>
# 9411
APP_VM_VSS_REG_FAILURE=ANS9411E VSS provider registration failed. Command '{0}' failed with Windows RC={1}\n
APP_VM_VSS_REG_FAILURE_EXPLANATION=<p> IBM Tivoli Storage Manager was unable to register the VSS provider on the virtual machine. </p>
APP_VM_VSS_REG_FAILURE_SYSACT=<p>Processing stops.</p>
APP_VM_VSS_REG_FAILURE_URESP=<p> Restart the virtual machine and try the operation again. </p>
# 9415
APP_VM_COPY_FAILURE=ANS9415E Failed to copy '{0}' to '{1}' with VMware RC={2} on the virtual machine.\n
APP_VM_COPY_FAILURE_EXPLANATION=<p> IBM Tivoli Storage Manager was unable to copy a file to the virtual machine. </p>
APP_VM_COPY_FAILURE_SYSACT=<p>Processing stops.</p>
APP_VM_COPY_FAILURE_URESP=<p> Verify that the source file exists and the destination is accessible. Restart the virtual machine and try the operation again. </p>
# 9416
APP_VM_MKDIR_FAILURE=ANS9416E Cannot create the directory '{0}' on the virtual machine with Windows RC={1}\n
APP_VM_MKDIR_FAILURE_EXPLANATION=<p> IBM Tivoli Storage Manager client was unable to create the specified directory on the virtual machine. It is possible that the directory exists and is locked by a process. </p>
APP_VM_MKDIR_FAILURE_SYSACT=<p>Processing stops.</p>
APP_VM_MKDIR_FAILURE_URESP=<p> Verify the the specified directory does not exist on the virtual machine. Restart the virtual machine and try the operation again. </p>
# 9417
APP_VM_VSS_FREEZE_FAILED=ANS9417E IBM Tivoli Storage Manager application protection could not freeze the VSS writers on the virtual machine named '{0}'. See the TSM error log for more details.\n
APP_VM_VSS_FREEZE_FAILED_EXPLANATION=<p> IBM Tivoli Storage Manager application protection encountered an error while freezing the VSS writers. </p>
APP_VM_VSS_FREEZE_FAILED_SYSACT=<p>Processing stops</p>
APP_VM_VSS_FREEZE_FAILED_URESP=<p> Use the 'vssadmin list writers' command to determine if any VSS writers detect errors on he virtual machine. Restart the VM. Retry the operation. If the retry fails, see the error log for details about the errors. </p>
# 9431
APP_VM_VSS_THAW_FAILED=ANS9431E IBM Tivoli Storage Manager application protection failed to thaw VSS writers on virtual machine '{0}'. See the TSM error log for more details.\n
APP_VM_VSS_THAW_FAILED_EXPLANATION=<p> IBM Tivoli Storage Manager application protection encountered an error while thawing VSS writers. </p>
APP_VM_VSS_THAW_FAILED_SYSACT=<p>Processing stops</p>
APP_VM_VSS_THAW_FAILED_URESP=<p> See the error log for more details. Verify that all VSS writers are not reporitng errors by running command 'vssadmin list writers'. Restart the virtual machine and try the operation again. If the retry fails, see the error log for details about the errors. </p>
# 9432
APP_VM_VSS_COMPLETE_FAILED=ANS9432W IBM Tivoli Storage Manager application protection failed to truncate application logs on virtual machine '{0}'.\n
APP_VM_VSS_COMPLETE_FAILED_EXPLANATION=<p> IBM Tivoli Storage Manager application protection encountered an error while completing VSS backup operation. The applications were successfully quiesced, but their logs were not truncated. </p>
APP_VM_VSS_COMPLETE_FAILED_SYSACT=<p>Application logs are not truncated.</p>
APP_VM_VSS_COMPLETE_FAILED_URESP=<p> See the TSM error log for more details. Verify that all VSS writers are not reporitng errors by running command 'vssadmin list writers'. Restart the virtual machine and try the operation again. If the retry fails, see the error log for details about the errors. </p>
# 9475
APP_VM_VSS_CLEANUP_FAILED=ANS9475W IBM Tivoli Storage Manager application protection failed to cleanup after a VSS backup on virtual machine {0}.\n
APP_VM_VSS_CLEANUP_FAILED_EXPLANATION=<p> IBM Tivoli Storage Manager application protection encountered an error while cleaning up after a VSS backup operation. </p>
APP_VM_VSS_CLEANUP_FAILED_SYSACT=<p>None</p>
APP_VM_VSS_CLEANUP_FAILED_URESP=<p> See the TSM error log for more details. Restart the virtual machine and try the operation again. If the problem persists, contact IBM technical support for further assistance. </p>
# 9488
NO_JRE_FOUND_WIN=ANS9488E Java Runtime Environment (JRE) was not found. File {0} does not exist.\n
NO_JRE_FOUND_WIN_EXPLANATION=<p> JRE was not found in the TSM installation directory. </p>
NO_JRE_FOUND_WIN_SYSACT=<p>Processing stops</p>
NO_JRE_FOUND_WIN_URESP=<p> Re-install the product or install a required version of JRE and try again. If JRE is already installed on your machine, then make sure the PATH environment variable contains path to javaw.exe. </p>
# 9489
NO_JRE_FOUND_UNX=ANS9489E Java Runtime Environment (JRE) was not found.\n
NO_JRE_FOUND_UNX_EXPLANATION=<p> JRE was not found. </p>
NO_JRE_FOUND_UNX_SYSACT=<p>Processing stops</p>
NO_JRE_FOUND_UNX_URESP=<p> If you have already installed JRE, please verify that the \"java\" executable is set in the system PATH, otherwise install the required JRE version. </p>
# 9490
HTTPAGENT_JAR_NOT_FOUND=ANS9490E Cannot find httpagent.jar in the TSM client installation directory.\n
HTTPAGENT_JAR_NOT_FOUND_EXPLANATION=<p> The required file was not found. </p>
HTTPAGENT_JAR_NOT_FOUND_SYSACT=<p>Processing stops</p>
HTTPAGENT_JAR_NOT_FOUND_URESP=<p> Re-install the product or install a required version of JRE and try again. </p>
# 9491
APP_VM_PWD_NOTFOUND=ANS9491E The password credentials for virtual machine '{0}' could not be found. Use dsmc SET PASSWORD -type=VMGUEST 'VM guest name' 'userid' 'password' to save encrypted password.\n
APP_VM_PWD_NOTFOUND_EXPLANATION=<p> The required password was not found. </p>
APP_VM_PWD_NOTFOUND_SYSACT=<p>Processing stops</p>
APP_VM_PWD_NOTFOUND_URESP=<p> Use dsmc SET PASSWORD -type=VMGUEST 'VM guest name' 'userid' 'password' to save encrypted password. And then retry the 'backup vm' operation. </p>
# 9492
DSI_IMG_VSS_DEST_SIZE_NOT_EQUAL_SOURCE=ANS9492E Destination size is not equal to source \n
DSI_IMG_VSS_DEST_SIZE_NOT_EQUAL_SOURCE_EXPLANATION=<p> The space allocation for the selected destination is not the same as the source. </p>
DSI_IMG_VSS_DEST_SIZE_NOT_EQUAL_SOURCE_SYSACT=<p> The restore operation is not performed. </p>
DSI_IMG_VSS_DEST_SIZE_NOT_EQUAL_SOURCE_URESP=<p> Choose a different destination which is equal in size to the source. </p>
# 9493
APP_VM_PWD_INCORRECT=ANS9493E The credentials found for virtual machine '{0}' are incorrect. Verify the credentials and use dsmc SET PASSWORD -type=VMGUEST 'VM guest name' 'userid' 'password' to update the username and password.\n
APP_VM_PWD_INCORRECT_EXPLANATION=<p> The supplied credentials are incorrect. Failed to authenticate to guest VM using these credentials. </p>
APP_VM_PWD_INCORRECT_SYSACT=<p>Processing stops</p>
APP_VM_PWD_INCORRECT_URESP=<p> Use dsmc SET PASSWORD -type=VMGUEST 'VM guest name' 'userid' 'password' to update the username and password. And then retry the 'backup vm' operation. </p>
# 9494
APP_VM_REMOTE_OP_FAILED=ANS9494E Command '{0}' completed with RC={2} on virtual machine '{1}'.\n
APP_VM_REMOTE_OP_FAILED_EXPLANATION=<p> A remote command either timed out or failed. </p>
APP_VM_REMOTE_OP_FAILED_SYSACT=<p>Processing stops</p>
APP_VM_REMOTE_OP_FAILED_URESP=<p> Increase the value of VMTIMEOUT option and try the operation again. </p>
# 9495
APP_VM_OPERATION_NOT_ALLOWED=ANS9495E Failed to login to virtual machine '{0}' because the VMware Tools are not running in the guest machine. Verify that the VMware tools are running and that no other program has access or is making any changes to this VM.\n
APP_VM_OPERATION_NOT_ALLOWED_EXPLANATION=<p> Failed to login to virtual machine because the VMware Tools are not running in the guest machine. </p>
APP_VM_OPERATION_NOT_ALLOWED_SYSACT=<p>Processing stops</p>
APP_VM_OPERATION_NOT_ALLOWED_URESP=<p> Make sure that the VMware tools are running and that no other program has access or is making changes to this VM. And then retry the 'backup vm' operation. </p>
# 9496
APP_VM_GET_GUEST_OWNERSHIP_FAILED=ANS9496E Unable to lock virtual machine {0} for application protection.\n
APP_VM_GET_GUEST_OWNERSHIP_FAILED_EXPLANATION=<p> The virtual machine is being backed up by another process. Only one process is allowed to use TSM application protection during a backup of a virtual machine at a time. </p>
APP_VM_GET_GUEST_OWNERSHIP_FAILED_SYSACT=<p>Processing stops</p>
APP_VM_GET_GUEST_OWNERSHIP_FAILED_URESP=<p> Wait for the other virtual machine backup to complete and re-try the operation. </p>
# 9497
APP_VM_ESX_NOT_SUPPORTED=ANS9497W Virtual machine '{0}' resides on an ESX Server or vCenter that is not supported by TSM application protection. IBM Tivoli Storage Manager application protection will not be used.\n
APP_VM_ESX_NOT_SUPPORTED_EXPLANATION=<p> Refer to the product documentation for the list of supported ESX and vCenter versions. </p>
APP_VM_ESX_NOT_SUPPORTED_SYSACT=<p>IBM Tivoli Storage Manager will use the VMware Tools to provide application consistency.</p>
APP_VM_ESX_NOT_SUPPORTED_URESP=<p> Exclude the virtual machine from application protection by removing the INCLUDE.VMTSMVSS option for this virtual machine. </p>
# 9498
APP_VM_Missing_License_File=ANS9498W A valid IBM Tivoli Storage Manager for Virtual Environments license file ({0}) cannot be located. IBM Tivoli Storage Manager application protection will not be used.\n
APP_VM_Missing_License_File_EXPLANATION=<p> The license file was not found, or cannot be opened because of permissions, or the file is corrupted. </p>
APP_VM_Missing_License_File_SYSACT=<p>IBM Tivoli Storage Manager will use the VMware Tools to provide application consistency.</p>
APP_VM_Missing_License_File_URESP=<p>Check permissions on file. See if the license file is in the correct place.</p>
# 9499
APP_VM_VMWARE_TOOLS_NEED_UPDATE=ANS9499W VMware tools on virtual machine '{0}' need to be updated. IBM Tivoli Storage Manager application protection will not be used.\n
APP_VM_VMWARE_TOOLS_NEED_UPDATE_EXPLANATION=<p> IBM Tivoli Storage Manager application protection requires that VMware Tools are up to date. </p>
APP_VM_VMWARE_TOOLS_NEED_UPDATE_SYSACT=<p>IBM Tivoli Storage Manager will use the VMware Tools to provide application consistency.</p>
APP_VM_VMWARE_TOOLS_NEED_UPDATE_URESP=<p> Update VMware Tools on the virtual machine </p>
# 9646
DSSM_Not_Applicable=N/A
# 9726
DSSM_MC_NO_ARCH_CG=No Archive Copy Group
# 9732
DSSM_MC_NO_BACK_CG=No Backup Copy Group
# 9778
DSI_OPT_ERROR_REQUEST_TO_FIX=ANS9778E Error(s) were detected in options file: '{0}' Do you want TSM to comment out the line with errors and continue?\n
DSI_OPT_ERROR_REQUEST_TO_FIX_EXPLANATION=<p>Invalid options or option values were encountered while reading the options file.</p>
DSI_OPT_ERROR_REQUEST_TO_FIX_SYSACT=<p>This message is displayed. Further action depends on your response.</p>
DSI_OPT_ERROR_REQUEST_TO_FIX_URESP=<p>Click "Yes" to allow TSM to turn the invalid line into comments. If you click "No", you will exit immediately.</p>
# 9779
DSI_OPT_UNABLE_TO_WRITE=ANS9779E Unable to open options file '{0}' for writing. \n
DSI_OPT_UNABLE_TO_WRITE_EXPLANATION=<p>An error occurred while TSM tried to open options file for writing to update it.</p>
DSI_OPT_UNABLE_TO_WRITE_SYSACT=<p>Program exits.</p>
DSI_OPT_UNABLE_TO_WRITE_URESP=<p>Check file and directory access permissions or correct invalid entries in your options file manually.</p>
# 9782
CLI_Invalid_Backupset_Uplevel=ANS9782S The selected backupset was generated by a newer version of the backup server, and the new backupset version is not supported by this client; The backupset data cannot be restored by this version of the client.
CLI_Invalid_Backupset_Uplevel_EXPLANATION=<p> The backupset you are attempting to restore was generated by a newer server that has a different level of functionality. The client you are using does not recognize this newer format so it cannot restore the data from the backupset. </p>
CLI_Invalid_Backupset_Uplevel_SYSACT=<p>Processing stopped.</p>
CLI_Invalid_Backupset_Uplevel_URESP=<p> Restore the backupset with a client that is at the same or higher level as the server that was used to generate the backupset. </p>
# 9807
CLI_Local_Backupset_Requested_Not_Found=ANS9807W The specified backupset file does not contain a backupset of type "file" for the specified nodename.\n
CLI_Local_Backupset_Requested_Not_Found_EXPLANATION=<p> Local backupset support is limited to backupsets that contain file data; Image backupsets are not supported locally. The specified backupset does not contain a backupset with file data for the node name specified. </p>
CLI_Local_Backupset_Requested_Not_Found_SYSACT=<p>Processing stopped.</p>
CLI_Local_Backupset_Requested_Not_Found_URESP=<p> Specify a different backupset file to restore file data from a backupset. To restore an image from a backupset, access the backupset from a TSM server. </p>
# 9810
DSSM_ALREADY_RECALLED=File has already been recalled.
# 9849
CLI_Local_Backupset_TOC_Not_Supported=ANS9849W Local backupset cannot be expanded; Only full backupset restore is supported locally.\n
CLI_Local_Backupset_TOC_Not_Supported_EXPLANATION=<p> Local backupsets cannot be expanded to show volumes, directories, and files. Only full backupset restore is supported from local backupsets. </p>
CLI_Local_Backupset_TOC_Not_Supported_SYSACT=<p>Processing stopped.</p>
CLI_Local_Backupset_TOC_Not_Supported_URESP=<p> To restore specific volumes, directories, and files from a backupset, restore the backupset from the TSM server. </p>
# 9850
CLI_PVR_Read_Error_Blocksize_Max=ANS9850E Tape read error; Max Blocksize is {0}. Attempted to read blocksize {1}. Run dsmmaxsg to update scsi driver max blocksize allowed and retry operation.\n
CLI_PVR_Read_Error_Blocksize_Max_EXPLANATION=<p> An attempt to read from tape at the specified blocksize failed; Tha maximum blocksize allowed for the scsi driver is shown. </p>
CLI_PVR_Read_Error_Blocksize_Max_SYSACT=<p>Processing stopped.</p>
CLI_PVR_Read_Error_Blocksize_Max_URESP=<p> If the maximum blocksize is less than the blocksize used by the operation, run the dsmmaxsg utility to update the maximum blocksize allowed for the scsi driver, and then retry the operation. If the maximum blocksize is greater than or equal to the blocksize used, then verify that the tape installed and operating correctly and retry the operation. </p>
# 9851
DSI_PW_Mismatch=The passwords in the entry field and the verify field do not match. Please retry.
# 9892
LSM_UNABLE_TO_CREATE_SNAPLIST=ANS9892E Unable to find snapshot(s) in the local repository.\n
LSM_UNABLE_TO_CREATE_SNAPLIST_EXPLANATION=<p>The requested volume snapshot(s) were not found in the local repository.</p>
LSM_UNABLE_TO_CREATE_SNAPLIST_SYSACT=<p>Processing stops.</p>
LSM_UNABLE_TO_CREATE_SNAPLIST_URESP=<p>Ensure the operation is issued with the proper nodename and/or server address. In a non-cluster environment perform the operation from a different host with the expected hostname. Retry the operation.</p>
# 9895
DSSM_FS_InInactive=ANS9895W Space management in file system {0} is not active.
DSSM_FS_InInactive_EXPLANATION=<p>You tried to select a file in a file system for which space management is inactive.</p>
DSSM_FS_InInactive_SYSACT=<p>TSM continues with normal operation.</p>
DSSM_FS_InInactive_URESP=<p>Reactivate space management for the file system, and then proceed with selecting files.</p>
# 9992
DSI_RC_VM_OPTION_MISSING=ANS9992E The following options must be set before running this operation: VMCHOST, VMCPW, or VMCUSER.
DSI_RC_VM_OPTION_MISSING_EXPLANATION=<p>VMCHOST, VMCPW, or VMCUSER is missing from the options file.</p>
DSI_RC_VM_OPTION_MISSING_SYSACT=<p>Operation cannot continue without options being set.</p>
DSI_RC_VM_OPTION_MISSING_URESP=<p>Manually edit the options file or use the preferences editor to set these options.</p>
# 10000
DSI_Preview_Complete_Success=Preview has completed successfully.
# 10001
DSI_Preview_Traverse=Traverse Subdirectories
# 10002
DSI_Preview_Function=Which function do you want to preview?
# 10003
DSI_Preview_Filter=What type of option do you want to preview?
# 10004
DSI_Preview_Description=Use this window to produce a list of files and directories that will be backed up or archived according to the include-exclude list applicable to the client. This list will be stored in a file that you specify.
# 10005
DSI_Preview_Destination=Enter the name of the file where you want the results to be stored:
# 10006
DSI_Preview_Title=Preview Include-Exclude
# 10007
DSI_Preview_Location=Please select where you want to store the results
# 10008
DSW_MENU_UTILS_PREVIEW=&Preview Include-Exclude
# 10011
DSI_COMMON_EXTENSION=Extension
# 10012
DSI_COMMON_DESCRIPTION=Description
# 10015
DSI_CFGWIZ_RECOMMEND_TITLE=Recommended Include/Exclude List
# 10016
DSI_CFGWIZ_RECOMMEND_DESCRIPTION=The following is a list of TSM recommended Include/Exclude items for files which are not normally required for system recovery. Selected items will be added to your configuration file, and excluded from backups.
# 10017
DSI_CFGWIZ_COMMON_TITLE=Common File Exclusion Selection
# 10018
DSI_CFGWIZ_COMMON_DESCRIPTION=Please select from the list the file types you wish to be excluded. By default, all of these file types are included.
# 10019
DSJ_EXPRESS_VERSION_LINK=Version
# 10020
DSJ_RECENTBACKUP_TAB_TOOLTIP=The most recent backups are displayed in this Tab
# 10021
DSJ_DISKBACKUP_TAB_TOOLTIP=Backups stored on disk are displayed in this tab
# 10022
DSJ_MEDIABACKUP_TAB_TOOLTIP=Backups stored on media are displayed in this tab
# 10023
DSJ_RECENTBACKUP_TAB=Most Recent Backup
# 10024
DSJ_DISKBACKUP_TAB=Disk
# 10025
DSJ_MEDIABACKUP_TAB=Media
# 10026
DSJ_EXPRESS_RESTORE_HELP_TEXT=The directory tree shows data that has been backed up.\n\n- Select the "Most Recent Backup" tab to view your most recent Backups on disk.\n- Select the "Disk" tab to view all your backups on disk. The backup server stores data on disk for 14 days.\n- Select the "Media" tab to view your backups that are copied to media, such as tape, for longer-term storage.\n
# 10027
DSI_TCPIP_USESSL=Use Secure Socket Layer (SSL)
# 10028
DSJ_EXPHUB_BANNER_MAINTITLE=Storage Manager Express Client
# 10029
DSJ_EXPHUB_BANNER_SUBTITLE={0} is connected to the Backup server {1}
# 10030
DSJ_EXPHUB_BACKUP_TITLE=Disk Backup
# 10031
DSJ_EXPHUB_LAST_BACKUP=The last backup was on {0} when {1} new or changed files were backed up.
# 10032
DSJ_EXPHUB_BACKUP_COMPUTER=Back Up Computer
# 10033
DSJ_EXPHUB_BACKUP_EXPLANATION=Immediately backs up all new and changed files from preselected drives on your system. If you want to change drive selections, go to Settings.
# 10034
DSJ_EXPHUB_BACKUP_EXPLORETREE=Explore and Back Up Files...
# 10035
DSJ_EXPHUB_BACKUP_EXPLORETREE_EXP=Lets you choose files to back up or exclude from backup.
# 10036
DSJ_EXPHUB_BACKUP_IMAGE=Image Backup
# 10037
DSJ_EXPHUB_BACKUP_IMAGE_EXP=Immediately backs up each preselected drive into an image for disaster recovery purposes. If you want to change drive selections, go to Settings.
# 10038
DSJ_EXPHUB_VIEW_BACKUP_REPORT=View Last Backup Report...
# 10039
DSJ_EXPHUB_RESTORE_TITLE=Restore
# 10040
DSJ_EXPHUB_RESTORE_WIZARD=Restore File Wizard...
# 10041
DSJ_EXPHUB_RESTORE_WIZ_EXP=Guides you through restoring your files and directories that reside on disk or offsite media.
# 10042
DSJ_EXPHUB_SETTINGS_TITLE=Settings
# 10043
DSJ_EXPHUB_MODIFY_SETTINGS=Modify Settings...
# 10044
DSJ_EXPHUB_MODIFY_SETTINGS_EXP=View or modify global backup client properties for this computer.
# 10045
DSI_PREFERC_NLS_LANG_FORMAT=Language Settings
# 10046
DSJ_LOGIN_SIGNON_TITLE=Storage Manager Sign-On
# 10047
DSJ_LOGIN_PROMPT_ID=Enter your TSM User ID and Password
# 10048
DSJ_LOGIN_TT_USERID=Type your user ID. This is usually your computer name.
# 10049
DSJ_LOGIN_TT_LOGIN_BUTTON=Click this button to authenticate to the Backup Server
# 10050
DSJ_LOGIN_TT_CANCEL_BUTTON=Click this button to close the window
# 10051
DSJ_EXPHUB_RESTORE_IMGWIZARD=Restore Image Wizard...
# 10052
DSJ_EXPHUB_RESTORE_IMGWIZ_EXP=Guides you through restoring your entire disk from an Image backup that resides on disk or offsite media.
# 10053
DSJ_EXPHUB_RESTORE_TREE=Explore and Restore files...
# 10054
DSJ_EXPHUB_RESTORE_TREE_EXP=Explore and select your files and directories that reside on disk or offsite media for restore
# 10055
DSJ_EXPHUB_RESTORE_TREEIMG=Explore and Restore an entire disk from an image...
# 10056
DSJ_EXPHUB_RESTORE_TREEIMG_EXP=Explore and select your entire disk from an image backup that reside on disk or offsite media for restore
# 10057
DSJ_SHOWHELPAREA_MENUITEM=&Show Hints and Tips
# 10058
DSJ_BACKUP_HELPAREA_TEXT=The directory tree shows the files on your computer. You can do the following:\n\n- Select files and directories that you want to back up.\n- Highlight an item and click the Exclude icon to exclude it from current and future backups.\n- Click Backup to back up selected files.\n
# 10059
DSJ_EXPRESS_DIAGNOSTIC_HELP_TEXT=Specify the options for tracing this computer in the event of a problem.
# 10060
DSJ_EXPRESS_ERRORLOG_LINK=View Error Log
# 10061
DSI_PREFERL_LOGGING=Logging
# 10062
DSI_PREFERA_ADVANCED_PREFERENCES=Error Log
# 10063
DSJ_EXPRESS_ADVANCED_PREFERENCE_HELP_TEXT=Specify how many days to maintain error log entries before pruning the log and whether to save the pruned entries, or specify the maximum log size. You cannot update the location of the error log.
# 10064
DSI_PREFERA_ADVANCED_PREF_SCHEDLOG=Schedule Log
# 10065
DSJ_EXPRESS_ADVANCED_PREF_SCHEDLOG_TEXT=Specify how many days to maintain schedule log entries before pruning the log and whether to save the pruned entries, or specify the maximum log size. You cannot update the location of the schedule log.
# 10066
DSJ_EXPRESS_SCHEDLOG_LINK=View Schedule Log
# 10067
EXP_CW_No_Backupsets=No media copy available
# 10888
DSI_PREFERB_ADAPTIVE_SUBFILE_BACKUP_CACHEPATH=Browse for cache path
# 10889
DSI_PREFA_ENCRYPTION_TYPE_TITLE=Encryption Type
# 10890
DSI_PREFA_56BITDES=56-bit DES
# 10891
DSI_PREFA_128BITAES=128-bit AES
# 10893
CLI_CONN_SERVERONLY="Server Only"
# 10894
CLI_CONN_CLIENTORSERVER="Client Or Server"
# 10895
CLI_CONN_DEDUPLICATION=Deduplication...........: {0}\n
# 11024
DSI_NoObjToDelete=No objects to delete.
# 11040
CLI_Never=Never
# 11044
Img_Use_Online_Image_Backup=Using online image backup.\n
# 11045
Img_Use_Offline_Image_Backup=Using offline image backup.\n
# 11118
DSI_PREVIEW_PROCEED_QUESTION=Depending on the number of objects to query, this operation could take a while to complete.\n\nAre you sure you want to continue?
# 11156
EXPRESS_GUI_COMM_FAILURE_Question=Do you wish to continue for purposes of modifying your settings? \n
# 11160
CLI_Processing_Finished=\n{0} processing finished.\n
# 11168
DSI_Del_Image_Confirm=You are about to delete the selected images from the Backup data storage. Do you wish to continue?
# 11173
DSI_Rest_Image_Confirm=Restoring the selected image(s) will replace all filesystem parameters and/or data that currently resides there. Are you sure you want to proceed?
# 11174
CLI_Default_Archive_Description=Archive Date: {0}
# 11222
DSC_MONTH_JANUARY=January
# 11223
DSC_MONTH_FEBRUARY=February
# 11224
DSC_MONTH_MARCH=March
# 11225
DSC_MONTH_APRIL=April
# 11226
DSC_MONTH_MAY=May
# 11227
DSC_MONTH_JUNE=June
# 11228
DSC_MONTH_JULY=July
# 11229
DSC_MONTH_AUGUST=August
# 11308
COMMON_FilesystemNoLabel=(Drive Has No Label)
# 11309
COMMON_FilesystemNotAvailable=(Drive Not Available)
# 11310
COMMON_SubstDrive=(SUBST Alias of Drive {0}:)
# 11318
CLI_No_File_Spaces_Found=No file spaces for node '{0}' were found on the server\n
# 11321
CLI_Rest_Image_Confirm=Restoring a file system or raw logical volume will replace any data that\ncurrently resides there and all file system parameters. Are you sure you want to replace\n File System/Volume: '{0}'? 
# 11351
DSC_MONTH_SEPTEMBER=September
# 11352
DSC_MONTH_OCTOBER=October
# 11353
DSC_MONTH_NOVEMBER=November
# 11354
DSC_MONTH_DECEMBER=December
# 11355
DSC_BS_FIRSTVOL_PROMPT=Please enter the location of the first backup set volume.
# 11356
DSC_BS_NEXTVOL_PROMPT=Please enter the location of the next backup set volume.
# 11357
DSC_BS_LASTVOL_PROMPT=Please enter the location of the last backup set volume.
# 11358
DSC_BS_NUMBEREDVOL_PROMPT=Please enter the location of the backup set volume number {0}.
# 11373
CLI_CONN_YES="Yes"
# 11374
CLI_CONN_NO="No"
# 11416
GUI_NOT_CONNECTED=NOT CONNECTED
# 11429
GUI_COMM_FAILURE_Question=Do you wish to continue for purposes of local backupset restore? \n
# 11443
DSI_DOM_MACHINE_LABEL=Data Protection for Domino
# 11444
DSI_DOM_DATADIR_LABEL=Domino Data Directory
# 11445
DSI_DOM_DBRESTORE_LABEL=Databases to Restore
# 11446
DSI_DOM_DBACTIVATE_LABEL=Databases to Activate
# 11447
DSI_DOM_DBACTIVATE_OTHER_LABEL=Other Databases
# 11448
DSI_COLUMN_ATTRIBUTE=Attribute
# 11449
DSI_DOM_NoDbsToActivate=No databases to activate.
# 11450
DSI_OBJINFO_TYPE_DOM_MACHINE=Domino Node
# 11451
DSI_OBJINFO_TYPE_DOM_SERVER=Domino Server
# 11452
DSI_OBJINFO_TYPE_DOM_DATADIR=Domino Data Directory
# 11453
DSI_OBJINFO_TYPE_DOM_DIR=Domino Directory
# 11454
DSI_OBJINFO_TYPE_DOM_DB=Domino NSF Database
# 11455
DSI_OBJINFO_TYPE_DOM_LOG=Domino Transaction Log Extent
# 11456
DSI_OBJINFO_TYPE_DOM_RESTORE=Domino Restore
# 11457
DSI_OBJINFO_TYPE_DOM_RESTORELOG=Domino Transaction Log Restore
# 11458
DSI_OBJINFO_TYPE_DOM_ACTIVATE=Domino Activate
# 11459
DSI_OBJINFO_TYPE_DOM_NODE=Domino Machine
# 11460
DSI_OBJINFO_TYPE_DOM_ACTIVATE_OTHER=Domino Activate Other Databases
# 11465
DSI_ACTIVEDIR_LOCALDEL=Local Deleted Objects
# 11466
DSI_DOM_NoLogsToInactivate=No logs to inactivate.
# 11467
DSI_COLUMN_VALUE=Value
# 11468
DSI_DOM_OBJECTS_ACTIVATED=Activated:
# 11469
DSI_DOM_OBJECTS_INACTIVATED=Inactivated:
# 11470
DSI_DOM_SERVER=Server {0}
# 11471
DSI_DOM_DB_LOGGED=Logged:
# 11472
DSI_DOM_VERSION=Version:
# 11473
DSI_DOM_BUILD=Build:
# 11474
DSI_DOM_TXN_LOGGING=Logging:
# 11475
DSI_DOM_TXN_LOGGING_ARCHIVAL=Archival
# 11476
DSI_DOM_TXN_LOGGING_LINEAR=Linear
# 11477
DSI_DOM_TXN_LOGGING_CIRCULAR=Circular
# 11478
DSI_DOM_TXN_NO_LOGGING=No Logging
# 11479
DSI_PIT_USE_IT_DOM=Use a Point in Time date during restore or Domino activate
# 11480
DSI_DOM_TXN_LOGGING_ID=Logger Id:
# 11481
DSI_DOM_DB2_GROUPS_LABEL=DB2 Groups
# 11482
DSI_BackChoice_DomDb2DB=DB2 database
# 11483
DSI_BackChoice_DomDb2Group=DB2 Group
# 11484
DSI_OBJINFO_TYPE_DOM_DB2NSF=Domino DB2NSF Database
# 11485
DSI_OBJINFO_TYPE_DOM_DB2GROUP=Domino DB2 Group
# 11486
DSI_OBJINFO_TYPE_DOM_DB2CLASS=Domino DB2 Class
# 11489
DSI_PREFP_FILESPACE_LISTBOX=Modify file system statements
# 11490
DSI_TRUE=TRUE
# 11493
DSI_PREFERR_MIGSTATE=Restore as migrated file
# 11494
DSI_PREFERR_CHECK_STUB_ACCESS=Restore resident if not accessible
# 11495
DSI_PREFERB_SKIP_MIGRATED=Skip migrated files
# 11496
DSI_PREFERR_MIGRATED_FILES=Restore settings
# 11497
DSI_PREFERB_BACKUP_ARCHIVE_SETTINGS=Backup / archive settings
# 11498
DSI_PREFERH_HSM_FOR_WINDOWS=HSM for Windows
# 11499
DSI_FALSE=FALSE
# 11508
DSI_DOM_ACTIVATE_BUTTON=Activate
# 11509
DSI_DOM_ACTIVATEDB=Activate Databases on a Restore operation
# 11510
DSI_DOM_APPLYLOG=Apply Logs on an Activate operation
# 11511
DSI_DOM_ROLLFORWARD_BUTTON=Rollforward
# 11512
DSI_DOM_BACLIENT_VIEW=B/A Client
# 11513
DSI_DOM_NSF_VIEW=Domino NSF
# 11514
DSI_DOM_DB2FULL_VIEW=Domino DB2 Databases
# 11515
DSI_DOM_DB2TBSP_VIEW=Domino DB2 Groups
# 11516
DSI_DOM_INACTIVATE_DB2OBJ=Inactivate DB2 Objects
# 11517
DSI_DOM_FULLDB2_RESTORE=Databases to Restore
# 11518
DSI_DOM_DB2GROUP_RESTORE=Groups to Restore
# 11519
DSI_DOM_DB2NSF_ACTIVATE=Databases to Activate
# 11520
DSI_DOM_DB2_ROLLFORWARD=Databases to Rollforward
# 11521
DSI_DOM_DB2_VIEW=Domino DB2
# 11522
DSI_DOM_DB2REST_ALT_DB=Restore to alternate DB2 database
# 11523
DSI_DOM_DB2REST_INPLACE_DB=Inplace Restore
# 11524
DSI_DOM_DB2ACTIVATE_ORG_LOC=Activate to Original location
# 11525
DSI_DOM_DB2ACTIVATE_ALT_LOC=Activate to Following location
# 11526
DSI_DOM_DB2REST_CHANGE_ALT_DBNAME=Name of alternate DB2 database
# 11527
DSI_DOM_DB2REST_CHANGE_ALT_DBLOCATION=Location of alternate DB2 database
# 11528
DSI_DOM_DB2REST_CHANGE_ALT_DBLOG_PATH=Log path for alternate DB2 database
# 11529
DSI_DOM_DB2REST_CHANGE_DB2CONTAINER_PATH=DB2 groups container path
# 11530
DSI_DOM_DB2ACTIVATE_LOCK_DB2GRP=Lock DB2 group after activation
# 11531
DSI_DOM_DB2ACTIVATE_ISOLATE_DB2GRP=Isolate DB2 group after activation
# 11532
DSI_DOM_DB2_RESTOPT=Data Protection for Domino DB2 Restore Options
# 11533
DSI_DOM_DB2_ACTOPT=Data Protection for Domino DB2 Activate Options
# 11534
DSI_DOM_FULLBACKUP_BUTTON=Full Backup
# 11535
DSI_DOM_ROLLFORWARD_EXTOPT=Domino DB2 database rollforward options
# 11536
DSI_DOM_ROLLFORWARD_OPT=Rollforward options
# 11538
DSI_DOM_ROLLFORWARD_APPLYLOG=Apply Logs
# 11539
DSI_DOM_ROLLFORWARD_PREPARE=Prepare
# 11540
DSI_DOM__DB2_ACTDST_WINDOWS_TITLE=Activate Destination
# 11541
DSI_DOM__DB2_ACTDST_ACTIVATE_TO=Activate to
# 11542
DSI_DOM_DB2_ACTDST_TITLE=Select destination for activated objects
# 11543
DSI_DOM_DB2_ACTDST_OK=Activate
# 11544
DSI_DPREFP_MEMRESIDENT_BUTTON=Use memory-resident method
# 11545
DSI_DPREFP_MEMSAVING_BUTTON=Use memory saving method
# 11546
DSI_DPREFP_DISKCACHE_BUTTON=Use disk cache method
# 11547
DSI_DPREFP_DISKCACHE_TEXT=Disk Cache File Location:
# 11548
DSI_DPREFP_SELECT_ALGORITHM_GROUP=Select Algorithm for Filespace Incremental
# 11549
DSI_DPREFP_SELECT_FILESPACE_BUTTON=Select individual filespaces:
# 11550
DSI_PREFERB_CHECK_REPARSE_CONTENT=Check stub reparse content
# 11556
DSI_DOM_RESTLOG_LABEL=Restore Log Archive
# 11557
DSI_DOM_ARCHLOG_BUTTON=Archive Log
# 11558
DSI_DOM_INACTIVATELOG_BUTTON=Inactivate Log Archives
# 11559
DSI_DPREFP_SELECT_ALLFILESPACES_BUTTON=Apply algorithm to all the filespaces
# 11567
DSI_OS_LABEL=Operating System
# 11569
DSJ_OBJINFO_VMAppProtectType_LABEL=Application Protection Type:
# 11570
DSJ_OBJINFO_VMApps_LABEL=Application(s) Protected:
# 11571
DSI_DPREFP_SELECT_FILESPACES_GROUP=Individual Filespace Statement List
# 11572
DSI_BackChoice_Domino=Backup Domino
# 11588
Comparing_Files_On_Server=Comparing local system files with active version on the server. This may take a long time depending on the number of files...\n
# 11603
DSI_PREFERH_HSM_FOR_WINDOWS_TITLE=HSM for Windows Preferences
# 11604
DSJ_EXPRESS_GENERAL_PREFERENCE_WARN_TEXT=Use this only if the name of your computer has changed. The computer name must match the computer name stored on the backup server. If the names do not match, files on this computer will not be backed up during scheduled backups, and you will not be able to access the backup server to restore your files. Modifying this option will require you to restart the application.
# 11605
DSJ_EXPRESS_GENERAL_PREFERENCE_HELP_TEXT=Type the name of your computer to identify it to the backup server.
# 11606
DSJ_EXPRESS_BACKUP_DOMAIN_PREFERENCE_HELP_TEXT=Specify the drives to include for file level backup. New and changed files on the selected drives are backed up during scheduled backups or file level backups that you initiate from this computer. At least one drive must be specified.
# 11607
DSJ_EXPRESS_BACKUP_IMAGE_PREFERENCE_HELP_TEXT=Specify the drives and objects to include for image backup of your system. The selected items on this list are backed up during scheduled image backups or image backups of your predefined drives that you initiate from this computer. At least one drive must be specified.
# 11608
DSJ_EXPRESS_RESTORE_PREFERENCE_HELP_TEXT=Use this page to manage how backups of existing files are restored.
# 11609
DSJ_EXPRESS_COMMUNICATION_PREFERENCE_HELP_TEXT=Enter settings to use to communicate with the backup server.
# 11610
DSJ_EXPRESS_REMOTECLIENT_PREFERENCE_HELP_TEXT=Specify the TCP/IP ports to use to remotely connect to your computer. The Web CAD Port and the Web Agent Port enable you to back up this computer through a firewall. If you do not specify a value for either of these two ports, a free port number is randomly assigned to each port.
# 11611
DSJ_EXPRESS_REMOTECLIENT_PREFERENCE_TAB_TEXT=Remote Computer
# 11612
DSJ_EXPRESS_REMOTECLIENT_PREFERENCE_TITLE_TEXT=Remote Computer Preferences
# 11613
DSJ_EXPRESS_DIAGNOSTIC_PREFERENCE_HELP_TEXT=Use only at the direction of your Service Representative.
# 11615
DSJ_LAST_BACKUP_LABEL=Last Backup Report
# 11616
DSJ_LAST_BACKUP_HELP=This report shows the statistics of your most recent backup of new and changed files. The list of files that failed to be backed up is displayed. To retry a backup of the files that failed, click Explore and Back Up Files in the Tivoli Storage Manager window, select the files that failed to be backed up, and click the Backup button.
# 11617
DSJ_LAST_BACKUP_SCHEDULE=Your last backup of new and changed files using schedule {0} completed with {1} errors.\nIt took {2} minutes and {3} seconds to complete and back up {4} files.
# 11618
DSJ_LAST_BACKUP_INTERACTIVE=Your last interactive backup of new and changed files completed with {0} errors.\nIt took {1} minutes and {2} seconds to complete and back up {3} files.
# 11619
DSJ_LAST_BACKUP_TRANSFERRED=Bytes transferred: {0}
# 11621
DSI_DOM_REPLACEDB=Replace Existing Files
# 11622
DSJ_LAST_BACKUP_TABLE_FILE_COLUMN=File Name
# 11623
DSJ_LAST_BACKUP_TABLE_FILE_HELP=List of files that failed to back up
# 11624
DSJ_LAST_BACKUP_TABLE_REASON_COLUMN=Reason
# 11625
DSJ_LAST_BACKUP_AGGREGATE_RATE=Data transfer rate: {0} KB/sec
# 11626
DSJ_LAST_BACKUP_LOG=Click here to see the detailed error log.
# 11627
DSJ_LAST_BACKUP_TITLE=IBM Tivoli Storage Manager Express Client
# 11628
DSJ_LAST_BACKUP_STATS=Statistics
# 11629
DSJ_LAST_BACKUP_PERF_STATS=Performance Statistics
# 11630
DSJ_COMPUTER_NAME=Computer Name
# 11631
DSI_PREFERB_IMAGE_BACKUP=Image Backup
# 11632
DSI_PREFERB_IMAGE_BACKUPLIST=Image Backup List
# 11633
DSI_PREFERB_FILE_BACKUP=File Level Backup
# 11634
DSJ_EXPRESS_RESTORE_PREFERENCE_LABEL=Select the default action for restoring existing files:
# 11635
DSJ_EXPRESS_BACKUP_COMMON_PREFERENCE_HELP_TEXT=This option compresses files before you send them to the backup server. Compressing your files reduces data storage for backup versions of your files. It can, however, affect backup client throughput. A fast processor on a slow network connection benefits from compression, but a slow processor on a fast network connection does not.
# 11636
DSJ_EXPRESS_DIAGNOSTIC_JAVAGUI_TRACE_PREFERENCE_DIALOG=Java GUI Diagnostics
# 11637
DSJ_EXPRESS_DIAGNOSTIC_JAVAAPPLET_TRACE_PREFERENCE_DIALOG=Java Applet Diagnostics
# 11638
DSJ_EXPRESS_DIAGNOSTIC_JAVAGUI_HELP_TEXT=Enable Java GUI tracing. The changes to the Java GUI trace settings are in effect only for this invocation of the application. Use only at the direction of your Service Representative.
# 11639
DSJ_EXPRESS_DIAGNOSTIC_JAVAAPPLET_HELP_TEXT=Enable Java Applet tracing. The changes to the Java Applet trace settings are in effect only for this invocation of the applet. Use only at the direction of your Service Representative.
# 11640
DSJ_EXPRESS_HINTS_TITLE=Hints and Tips
# 11641
DSJ_EXPRESS_REST_WIZ_WELCOME=Welcome
# 11642
DSJ_EXPRESS_REST_WIZ_WELCOME_HELP=Use this wizard to restore your files or images from the backup server.
# 11643
DSJ_EXPRESS_REST_WIZ_WELCOME_CONTENT=Restoring files or images includes the following tasks:\n\n- Set a filter to display a version of your backups. This helps you target the files you want to restore. \nFor example, you can show just your most recent backups on disk, show backups that were made within a specific number of days or before a specific date, or show older backups that reside on offsite media on the backup server.\n\n- Select the files you want to restore based on the version that you selected.\n\n- Select the destination to put the restored files. You can put the files in their original locations or to alternate locations on your computer. When restoring an image backup of the operating system drive, you must select a restore destination other than the original location.\n
# 11644
DSJ_EXPRESS_VERSION_TITLE=Backup Client Version:
# 11650
DSJ_LAST_BACKUP_TABLE_REASON_HELP=Tells you why the backup failed
# 11651
DSI_VALUE_OUT_OF_RANGE='{0}' must be between {1} and {2}.
# 11652
DSI_PREFERP_CHOOSE_DCL=Choose the Disk Cache Location
# 11653
DSI_PREFERP_CHOOSE_FILESPACE=Choose Filespace
# 11655
DSI_Failed_To_Create_Stream=Failed to create named stream
# 11656
DSI_NOT_LOCAL_CLUSTER_Disk=The file space is not a local disk.
# 11661
DSJ_LAST_BACKUP_TABLE_TITLE=List of new and changed files that failed.
# 11665
DSI_Rest_HyperV_Confirm=Restoring the selected Virtual Machine '{0}' will stop the VM, delete all the VM files, then restore the VM with the backup. It is recomended that you manually shutdown the VM before proceeding to cleanly stop any applications running inside the VM. Are you sure you want to proceed?
# 12070
DSW_WIZ_CHOOSE_PATH=Browse for Directory
# 12100
DSI_VMBACKUP_Processing_Snapshot_Disk=Processing snapshot\n\tdisk: {0} ({1})\n\tCapacity: {2}\n\tData to Send: {3}\n\tTransport: {4}[sending]\n
# 12101
DSI_VMBACKUP_Backup_Config_Info=Backing up Full VM configuration information for '{0}'\n
# 12102
DSI_VMBACKUP_Restoring_Disk=Restoring disk {0} ({1}), Capacity: {2} {3}[receiving]\n
# 12103
DSI_VMBACKUP_Restoring_Full= Restoring FULL ({0}) - bytes to restore: {1}\n
# 12104
DSI_VMBACKUP_Restoring_Incr=Restoring {0} ({1}) - bytes to restore: {2}\n
# 12105
DSI_VMBACKUP_Restore_Config_Info=Restoring VM configuration information for '{0}'\n
# 12200
DSW_MENU_FILE=&File
# 12201
DSW_MENU_FILE_LOGIN=&Login
# 12202
DSW_MENU_FILE_CONNECTION_INFO=&Connection Information
# 12210
DSW_MENU_EDIT=&Edit
# 12214
DSW_MENU_EDIT_SELECT=&Select Items
# 12215
DSW_MENU_EDIT_DESELECT=&Deselect Items
# 12216
DSW_MENU_EDIT_BSLOC=&Backup Set Location
# 12217
DSW_MENU_EDIT_INCLUDE_ITEM=&Include Item(s)
# 12218
DSW_MENU_EDIT_EXCLUDE_ITEM=&Exclude Item(s)
# 12220
DSW_MENU_ADSM=&Actions
# 12221
DSW_MENU_ADSM_BACKUP=&Backup
# 12222
DSW_MENU_ADSM_RESTORE=&Restore
# 12223
DSW_MENU_ADSM_RESTART_RESTORE=Re&startable Restores...
# 12224
DSW_MENU_ADSM_ARCHIVE=&Archive Package
# 12225
DSW_MENU_ADSM_RETRIEVE=Re&trieve Package
# 12226
DSW_MENU_ADSM_BACKUP_DOMAIN=Backup &Domain
# 12230
DSW_MENU_UTILITIES=&Utilities
# 12231
DSW_MENU_UTILS_CHANGE_PASSWORD=&Change Password...
# 12232
DSW_MENU_UTILS_NODE_ACCESS_LIST=&Node Access List...
# 12233
DSW_MENU_UTILS_ANOTHER_USER=&Access Another Node...
# 12234
DSW_MENU_UTILS_VIEW_POLICY=&View Policy Information
# 12235
DSW_MENU_UTILS_DELETE_ARCHIVE=De&lete Archive Data...
# 12236
DSW_MENU_UTILS_DELETE_DATA=&Delete Filespaces...
# 12239
DSW_MENU_ADSM_RESTORE_VM=Restore &VM
# 12240
DSW_MENU_VIEW=&View
# 12245
DSW_MENU_VIEW_DISPLAY_ACTIVEINACTIVE_FILES=Display active/&inactive files
# 12246
DSW_MENU_VIEW_DISPLAY_ACTIVEFILESONLY=Display &active files only
# 12247
DSW_MENU_VIEW_FILE_DETAILS=&File details...
# 12248
DSW_MENU_VIEW_EXPAND=&Expand branch
# 12249
DSW_MENU_VIEW_EXPAND_ENTIRE=Expand entire &branch
# 12250
DSW_MENU_VIEW_COLLAPSE=&Collapse branch
# 12251
DSW_MENU_VIEW_COLLAPSE_ENTIRE=Co&llapse entire branch
# 12256
DSJ_APPLETPREF_JVMENV=Java Environment
# 12257
DSJ_APPLETPREF_VENDOR=Vendor:
# 12258
DSJ_APPLETPREF_OS=Operating System:
# 12259
DSJ_APPLETPREF_OSVER=OS Version:
# 12263
DSW_MENU_HELP_INTERNET_RESOURCES=&Internet Resources
# 12264
DSW_MENU_HELP_PROD_URL=IBM Tivoli Storage Manager &Home Page
# 12265
DSW_MENU_HELP_PROD_TECH_SUPPORT_URL=IBM Tivoli Storage Manager &Technical Support Home Page
# 12266
DSW_MENU_HELP_BRAND_URL=Tivoli Home &Page
# 12267
DSW_MENU_HELP_REDBOOKS_URL=Tivoli Redbooks &Web site
# 12268
DSW_MENU_HELP_README=IBM Tivoli Storage Manager &Readme
# 12269
DSW_MENU_HELP_BOOKS=IBM Tivoli Storage Manager &Information Center
# 12270
DSW_MENU_HELP=&Help
# 12271
DSW_MENU_HELP_TOPICS=&Help Topics
# 12275
DSW_MENU_HELP_GET_STARTED=&Getting Started...
# 12276
DSW_STATUS_INTERNET_RESOURCES=Display online links to technical support, help, and publications.
# 12277
DSW_MENU_ABOUT_ADSM=&About TSM
# 12278
DSW_MENU_UTILS_SETUPWIZARD=Setup &Wizard
# 12279
DSW_MENU_ADSM_BACKUP_DOMAIN_IMAGE=Backup Domain &Image
# 12280
DSW_MENU_UTILS_ASRDISKETTE=C&reate ASR Diskette
# 12281
DSW_CREATE_ASRDISKETTE=Specify the floppy drive that IBM Tivoli Storage Manager is used to create the ASR recovery diskette. Insert a blank floppy into the designated drive and press Finish.
# 12282
DSW_CREATE_ASRDISKETTE_TITLE=Create Automated System Recovery Diskette
# 12283
DSI_RESTORE_VM_TITLE=Restore Virtual Machine
# 12284
DSI_VIRTUALMACHINES_NODE_LABEL=Virtual Machines
# 12285
DSI_COLUMN_VM_NAME=VM
# 12286
DSI_COLUMN_VM_HOSTNAME=VM Hostname
# 12287
DSI_COLUMN_VM_HOSTSRV=Host Server
# 12288
DSI_COLUMN_VM_ID=VM Id
# 12289
DSI_COLUMN_TYPE=Type
# 12290
DSI_COLUMN_STATUS=Status
# 12291
DSI_COLUMN_CHNGTRK=Change Tracking
# 12292
DSW_CREATE_ASRDISKETTE_COMPLETE=ASR Diskette contents were successfully written to {0}
# 12294
DSW_STATUS_PROD_URL=Display the IBM Tivoli Storage Manager Web site.
# 12295
DSW_STATUS_PROD_TECH_SUPPORT_URL=Display the IBM Tivoli Storage Manager technical support Web site.
# 12296
DSW_STATUS_BRAND_URL=Display the Tivoli Web site.
# 12297
DSW_STATUS_README=Display the IBM Tivoli Storage Manager readme.
# 12298
DSW_STATUS_REDBOOKS_URL=Display the Tivoli Redbooks Web site.
# 12299
DSW_STATUS_BOOKS_URL=Display the IBM Tivoli Storage Manager publications Web site.
# 12300
DSW_MENU_UTILS_DPESSDB2=Data &Protection for ACS (DB2 UDB)
# 12301
DSW_MENU_UTILS_CFGWIZ=Configuration &Wizard(s)
# 12302
DSM_MENU_HELP_INTERNET_RESOURCES=Internet Resources
# 12303
DSM_MENU_HELP_PROD_URL=IBM Tivoli Storage Manager Home Page
# 12304
DSM_MENU_HELP_PROD_TECH_SUPPORT_URL=IBM Tivoli Storage Manager Technical Support Home Page
# 12305
DSM_MENU_HELP_BRAND_URL=Tivoli Home Page
# 12306
DSM_MENU_HELP_REDBOOKS_URL=Tivoli Redbooks Web site
# 12307
DSM_MENU_HELP_README=IBM Tivoli Storage Manager Readme
# 12308
DSM_MENU_HELP_BOOKS=IBM Tivoli Storage Manager Publications Home Page
# 12309
DSI_ESSDB2CFGWIZ_TITLE=TSM for Hardware Data Protection for ACS DB2 Configuration Wizard
# 12310
DSI_PREFER_CFGWIZ_ERROR_BETWEEN=Error: Field '{0}' must be in the range from {1} to {2}.
# 12311
DSI_PREFER_CFGWIZ_NOT_LENGTH_MORE=Error: The length of '{0}' can not be more than {1} characters.
# 12312
DSI_PREFER_CFGWIZ_REQUIRED=Error: Field '{0}' is required and must have a valid value entered.
# 12313
DSI_PREFER_CFGWIZ_CHAR_ERROR_BETWEEN=Error: Field '{0}' must be at least {1} characters long and no more than {2} characters long.
# 12314
DSI_PREFER_CFGWIZ_NOT_MORE=Error: Field '{0}' must not be greater than {1}
# 12315
DSI_PREFER_CFGWIZ_AT_LEAST=Error: Field '{0}' must not be less than {1}
# 12316
DSI_PREFER_CFGWIZ_LENGTH_AT_LEAST=Error: Field '{0}' must be at least {1} characters long
# 12317
DSI_ESSDB2_CFGWIZ_NOT_SUPPORTED=ACS DB2 Configuration Wizard is valid for AIX target clients only.
# 12318
DSI_GENERIC_CFGWIZ_COMPLETED=The Configuration Wizard Completed Successfully
# 12319
DSI_ESSDB2_NOT_DETECTED=The ACS DB2 Plugin was not detected on target system
# 12320
DSI_GENERIC_CFGWIZ_CANCEL=The Configuration Wizard has been Aborted upon User's Request
# 12321
CLI_VMBACKUP_ConsoleStatus21_Fullvm_backup_start=Starting Full VM backup of Virtual Machine '{0}'\n
# 12322
CLI_VMBACKUP_ConsoleStatus22_Fullvm_backup_Success=Successful Full VM backup of Virtual Machine '{0}'\n
# 12323
CLI_VMBACKUP_ConsoleStatus23_Restore_Final_Cmd_Complete=Restore VM command complete\n
# 12324
CLI_VMBACKUP_ConsoleStatus24_Restore_Final_Success_Count=Total number of virtual machines restored successfully: {0}\n
# 12325
CLI_VMBACKUP_ConsoleStatus25_Restore_Final_Failed_Count=Total number of virtual machine restores failed: {0}\n
# 12326
CLI_VMBACKUP_ConsoleStatus26_Fullvm_Restore_Avail_At_Loc=Restored Full VM files are now available at location:\n {0}\n
# 12327
CLI_VMBACKUP_ConsoleStatus27_Restore_Converter_Tool_Info=Virtual Infrastructure Client or VMware Converter tool can be used to redefine virtual machine to the VMware Virtual Center Inventory.\n
# 12328
CLI_VMBACKUP_ConsoleStatus28_Restore_Converter_Prompt=Would you like to launch VMware Converter now?
# 12329
CLI_VMBACKUP_ConsoleStatus29_Restore_Launching_Converter=Launching VMware Converter...\n
# 12330
CLI_VMBACKUP_ConsoleStatus30_Restore_VM_Cmd_Start=Restore VM command started. Total number of virtual machines to process: {0}\n
# 12331
CLI_VMBACKUP_ConsoleStatus31_Restore_Start=Restore of Virtual Machine '{0}' started\n\n
# 12332
CLI_VMBACKUP_ConsoleStatus32_Restore_Start2=Starting Full VM restore of Virtual Machine '{0}'\n
# 12333
CLI_VMBACKUP_ConsoleStatus33_Fullvm_Restore_Success=Successful Full VM restore of Virtual Machine '{0}'\n
# 12334
CLI_VMBACKUP_ConsoleStatus34_Restore_Success_indent= virtual machine '{0}' restored successfully\n
# 12335
CLI_VMBACKUP_ConsoleStatus35_Fullvm_Restore_Loc_indent= restore location: {0}\n
# 12336
CLI_VMBACKUP_ConsoleStatus36_Restore_Failed_indent= virtual machine '{0}' restore failed\n
# 12337
CLI_VMBACKUP_ConsoleStatus37_Fullvm_Restore_Avail_At_Loc2=Restored Full VM files are now available at location:\n {0}\fullvm\\n
# 12338
CLI_VMBACKUP_ConsoleStatus41_Fullvm_Backup_Avail_At_Loc2=Local copy of Full VM image files available at location:\n {0}\fullvm\\n
# 12339
DSI_HYPERV_VMS_NODE_LABEL=Hyper-V VMs
# 12340
DSI_ON_MSG=On
# 12341
DSI_OFF_MSG=Off
# 12342
DSI_NOT_SUPPORTED_MSG=Not Supported
# 12343
DSI_BACKUP_VM_TITLE=Backup Virtual Machine
# 12500
DSJ_LANGUAGE_ID=en_US
# 12501
DSJ_HELPBASE=wchelp
# 12502
DSJ_EXPRESS_HELPBASE=wcxhelp
# 12504
DSJ_OBJINFO_ENCRYPTION_TYPE_LABEL=Encryption Type:
# 12505
DSJ_OBJINFO_DEDUPLICATED_LABEL=Client-deduplicated:
# 12506
DSJ_OBJINFO_COMPRESSED_LABEL=Compressed:
# 12507
DSJ_OBJINFO_ATTRIB_COMPRESSED=Compressed 
# 12508
DSJ_OBJINFO_ATTRIB_ENCRYPTED=Encrypted 
# 12509
DSW_TSM_HOMEPAGE=http://www.ibm.com/software/tivoli/products/storage-mgr
# 12510
DSW_TECHSUPT_HOMEPAGE=http://www.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.html
# 12511
DSW_TIVOLI_HOMEPAGE=http://www.ibm.com/software/tivoli
# 12512
DSW_TSMPUBS_HOMEPAGE=http://pic.dhe.ibm.com/infocenter/tsminfo/v6r4/index.jsp
# 12513
DSW_REDBOOKS_HOMEPAGE=http://www.redbooks.ibm.com/portals/tivoli
# 12514
DSI_FILECHOOSER_FILESTYPE=Files of type:
# 12516
DSI_FILECHOOSER_LOOKIN=Look in:
# 12517
DSI_FILECHOOSER_LIST=List
# 12518
DSI_FILECHOOSER_NEWFOLDER=Create New Folder
# 12519
DSI_FILECHOOSER_HOME=Home
# 12550
DSI_GENERIC_CFGWIZ_CREATE_ASSIGNMENT_HELP=Please assign a value for '{0}' in the text box below:
# 12551
DSI_GENERIC_CFGWIZ_MODIFY_ASSIGNMENT_HELP=Please make a selection for '{0}' from the list below:
# 12552
DSI_GENERIC_CFGWIZ_CREATE_ASSIGNMENT=Create Assignment
# 12553
DSI_GENERIC_CFGWIZ_MODIFY_ASSIGNMENT=Modify Assignment
# 12554
DSI_GENERIC_CFGWIZ_ITEM_NOT_SELECTED=You must select an entry to perform this Action!
# 12555
DSI_GENERIC_CFGWIZ_SELECT_ONE=Select one of the Following
# 12557
DSO_OBJINFO_EASIZE=EA Buffer Size:
# 12558
DSO_OBJINFO_ACLSIZE=ACL Size:
# 12560
DSO_OBJINFO_LAST_ACCESS=Last Access Date:
# 12561
DSO_OBJINFO_LAST_CHANGED=Last Changed Date:
# 12562
DSO_OBJINFO_ALLOC_SIZE=Allocated Size:
# 12564
DSJ_REGISTRY_MACHINE_HIVE=HKEY_LOCAL_MACHINE
# 12565
DSJ_REGISTRY_USERS_HIVE=HKEY_USERS
# 12566
DSJ_APPLET_PREF_TITLE=Applet Preferences
# 12585
DSI_JOURNAL_WIZARD_DESC=This wizard will guide you through the configuration process of the Journal-based backup (JBB) Engine. \n\nThe wizard will let you set specific JBB options and install the JBB daemon service.
# 12604
DSJ_MENU_EDIT_APPLET_PREF=&Applet Preferences
# 12605
DSJ_MENU_EDIT_CLIENT_PREF=&Client Preferences
# 12606
DSJ_MENU_EDIT_JAVA_DIAGNOSTIC=&Java Diagnostic
# 12607
DSJ_MENU_FILE_JAVAGUI_EXIT=&Exit
# 12639
DSI_NO_DRIVES_AVAILABLE=No removable drives were found. Your system must have at least one removable drive for this operation.
# 12676
DSI_IE_INFILES_BORDER_ARC=Which files to include for archive?
# 12679
DSI_IE_EXFILES_BORDER_ARC=Which files to exclude from archive?
# 12700
DSJ_HUB_BACKUP_BUTTON=Backup
# 12701
DSJ_HUB_ARCHIVE_BUTTON=Archive
# 12702
DSJ_HUB_RESTORE_BUTTON=Restore
# 12703
DSJ_HUB_RETRIEVE_BUTTON=Retrieve
# 12705
DSJ_HUB_WELCOME=Welcome to IBM Tivoli Storage Manager. Click below to perform a task.
# 12706
DSJ_HUB_BACKUP_HEADER=Backup
# 12707
DSJ_HUB_BACKUP_TEXT=Backup and Restore copies of data that are frequently updated.
# 12708
DSJ_HUB_ARCHIVE_HEADER=Archive
# 12709
DSJ_HUB_ARCHIVE_TEXT=Archive and Retrieve copies of data that are preserved for a specific period of time.
# 12710
DSJ_HUB_BACKUP_BUTTON_TEXT=Copies files to server storage to prevent loss of data.
# 12711
DSJ_HUB_RESTORE_BUTTON_TEXT=Restores saved files from server storage.
# 12712
DSJ_HUB_ARCHIVE_BUTTON_TEXT=Creates an archive copy in long-term storage.
# 12713
DSJ_HUB_RETRIEVE_BUTTON_TEXT=Retrieves an archive copy from long-term storage.
# 12750
DSJ_BACKOPTIONS_NTSECURITY_CHECK=Back up NTFS security information
# 12751
DSJ_RESTOPTIONS_NTSECURITY_CHECK=Restore NTFS security information
# 12753
DSJ_ARCHDESCR_OK=OK
# 12754
DSJ_CHGPASS_USERID=User id:
# 12755
DSJ_LOGIN_USERID=User id:
# 12756
DSJ_PASSWORD_USERID=User id:
# 12757
DSJ_CONNECTION_TITLE=TSM Connection Information
# 12758
DSJ_CONN_CLIENT_USER_ID=User ID:
# 12759
DSJ_CONN_CLIENT_IP_ADDR=IP Address:
# 12760
DSJ_CONN_CLIENT_NODE_NAME=Node Name:
# 12761
DSJ_CONN_CLIENT_TYPE=Type:
# 12762
DSJ_CONN_CLIENT_VERSION=Version:
# 12763
DSJ_CONN_AUTHORITY_LEVEL=Authority Level:
# 12764
DSJ_CONN_AUTH_SYSTEM=System
# 12765
DSJ_CONN_AUTH_POLICY=Policy
# 12766
DSJ_CONN_AUTH_OWNER=Client Owner
# 12767
DSJ_CONN_AUTH_ACCESS=Client Access
# 12768
DSJ_CONN_AUTH_NONE=None
# 12800
DSJ_APPLET_PREF_NOTE=Note: The changes to the settings in this dialog are in effect only for this invocation of the applet.
# 12806
DSJ_APPLET_PREF_TRACEFLAGS=Applet Diagnostics
# 12807
DSJ_APPLET_PREF_ENABLE_TRACEFLAGS=Enable applet traceflags
# 12808
DSJ_APPLET_PREF_ENTER_TRACEFLAGS=Enter applet traceflags
# 12809
DSI_FILECHOOSER_FILEFILTER_ALL=All files (*.*)
# 12810
DSJ_APPLET_PREF_OK_BUTTON=OK
# 12811
DSJ_APPLET_PREF_CANCEL_BUTTON=Cancel
# 12813
DSJ_APPLET_PREF_TRACE_NOTE=Note: Enabling tracing may decrease the performance of the applet.
# 12896
DSI_IE_INDIRS_BORDER=Which directories to include for backup?
# 12897
DSI_IE_EXDIRS_BORDER=Which directories to exclude from backup?
# 12898
DSI_IE_INCLUDE_DIRS=Create New Include Directories Rule
# 12899
DSI_IE_EXCLUDE_DIRS=Create New Exclude Directories Rule
# 12901
DSI_IE_WRITE_PROMPT=Do you wish to write the following include-exclude statement(s) to the options file?\n\n{0}
# 12902
DSI_IE_PREVIEW=Preview the include-exclude statement
# 12903
DSI_IE_INCLUDE_FILES=Create New Include Files Rule
# 12904
DSI_BACKUPSET_FILEFILTER=Backup Set files (*.OST)
# 12905
DSI_IE_INFILES_BORDER=Which files to include for backup?
# 12906
DSI_IE_INCLUDE_SUBDIR=Include in subdirectories too
# 12907
DSI_IE_EXCLUDE_FILES=Create New Exclude Files Rule
# 12908
DSI_IE_EXCLUDE_ALLDIR=Exclude this directory everywhere
# 12909
DSI_IE_EXFILES_BORDER=Which files to exclude from backup?
# 12910
DSI_IE_EXCLUDE_SUBDIR=Exclude in subdirectories too
# 12913
DSJ_EDIT_SELECT=Select highlighted files
# 12914
DSJ_EDIT_DESELECT=Deselect highlighted files
# 12915
DSI_IE_ONE_FILE=Just this file:
# 12916
DSI_IE_FILES_EXT=All files of this extension:
# 12917
DSI_IE_MATCHING_FILES=All files matching pattern
# 12918
DSI_IE_ENTER_PATTERN=Enter wildcard pattern:
# 12919
DSI_IE_DIR_BORDER=In which directories?
# 12925
DSI_IE_ONE_DIR=Just this directory:
# 12926
DSI_IE_SEL_DIR=Selected directory:
# 12927
DSI_IE_ALL_DIRS=All directories
# 12929
DSI_IE_FS_BORDER=In which file systems?
# 12930
DSI_IE_ALL_FS=All filespaces
# 12931
DSI_IE_SEL_FS=Selected filespaces
# 12932
DSJ_EDIT_INCLUDE_ITEM=Include highlighted items
# 12933
DSJ_EDIT_EXCLUDE_ITEM=Exclude highlighted items
# 12944
DSJ_VIEW_DISPLAYACTIVEINACTIVEFILES=Display both active and inactive files
# 12945
DSJ_VIEW_DISPLAYACTIVEFILESONLY=Display only the active files
# 12946
DSJ_VIEW_FILEDETAILS=View the details of the selected file
# 12964
DSJ_OBJINFO_NAMESPACE_DOS=DOS 
# 12965
DSJ_OBJINFO_NAMESPACE_MAC=Macintosh 
# 12966
DSJ_OBJINFO_NAMESPACE_NFS=NFS 
# 12967
DSJ_OBJINFO_NAMESPACE_FTAM=FTAM 
# 12968
DSJ_OBJINFO_NAMESPACE_LONG=Long 
# 12969
DSJ_OBJINFO_NAMESPACE_BINDERY=Bindery 
# 12970
DSJ_OBJINFO_NAMESPACE_ROOT=Root 
# 12971
DSJ_OBJINFO_NAMESPACE_NDS=NDS 
# 12972
DSJ_OBJINFO_NAMESPACE_SSINFO=Server Specific Info 
# 12973
DSJ_OBJINFO_NAMESPACE_SCHEMA=Schema 
# 12975
DSJ_OBJINFO_KIND_NODE=Node (OS/2) 
# 12976
DSJ_OBJINFO_NAMESPACE=Name Space: 
# 12977
DSJ_OBJINFO_SHORT_NAME=Short Name: 
# 12978
DSJ_ARCOPT_SYMLINKS=Archive the file/directory pointed to by a symbolic link
# 12979
DSJ_MENU_VIEW_TASK_LIST=&Task List
# 13004
CLI_SYSOBJ_EVENT_LOG=Event Log
# 13009
CLI_SYSOBJ_RSM_DB=RSM Database
# 13014
CLI_SYSOBJ_WMI=WMI Database
# 13016
DSI_OBJINFO_TYPE_WMIDB=WMI
# 13018
DSI_CONN_FS_WMIDB=WMI
# 13023
DSI_BACKDEL_TITLE=Backup Delete
# 13026
DSW_MENU_UTILS_DELETE_BACKUP=D&elete Backup Data...
# 13028
DSI_BackDel_Question=You are about to delete the selected files from the Backup data storage. Do you wish to continue?
# 13031
CLI_SYSOBJ_SYSTEMSTATE=System State
# 13036
CLI_SYSOBJ_SYSTEMSERVICES=System Services
# 13041
DSI_GENERIC_SELECTALL=Select All
# 13042
DSI_GENERIC_CLEARALL=Clear All
# 13043
CLI_SYSOBJ_ASR=Automated System Recovery
# 13044
CLI_SYSOBJ_GROUPLIST=VSS xml files
# 13045
CLI_SYSOBJ_BIT_SERVICE=BIT Service
# 13046
CLI_SYSOBJ_DHCP_DB=DHCP Server
# 13047
CLI_SYSOBJ_RSS_DB=Remote Storage Server
# 13048
CLI_SYSOBJ_TLS_DB=Terminal Server Licensing
# 13049
CLI_SYSOBJ_IIS_DB=IIS Server Metabase
# 13050
CLI_SYSOBJ_WINS_DB=WINS Database
# 13051
DSI_ACTIVE_TITLE_BACKDELETE=Backup Delete Report
# 13066
CLI_SYSOBJ_BOOTABLESYSTEMSTATE=Bootable System State
# 14036
dsmEvent_Save_RegistryKey_Failed=ANS14036E An error occurred saving the registry key.\n
dsmEvent_Save_RegistryKey_Failed_EXPLANATION=<p> The active registry key cannot be copied to the ADSM.SYS staging directory. </p>
dsmEvent_Save_RegistryKey_Failed_SYSACT=<p>Registry backup operation terminates.</p>
dsmEvent_Save_RegistryKey_Failed_URESP=<p> Check the space available on the Windows boot partition to ensure there enough space to contain a copy of the Windows registry. This might require several megabytes of free space. Also check the Windows permissions on the ADSM.SYS staging directory and ensure that the Windows user under which you are running TSM has full access to that directory and its contents. </p>
# 14052
dsmEvent_EFS_Cant_raw_write=ANS14052E Error processing '{0}{1}{2}': Encrypted-file-system (EFS) file cannot be restored, because file system does not support restore from the raw-EFS back-up data, or possibly because the restore function does not have write access to the directory.
dsmEvent_EFS_Cant_raw_write_EXPLANATION=<p>The file being processed is encrypted by an encrypted file system (EFS). The file was backed up in the raw encrypted format. Either the target filesystem does not support the encrypted format, or restore does not have write access to the directory to which the file is to be restored.</p>
dsmEvent_EFS_Cant_raw_write_SYSACT=<p>The restore is terminated.</p>
dsmEvent_EFS_Cant_raw_write_URESP=<p> <ul> <li>The file cannot be restored to this location if the file system is not the AIX Enhanced Journaled File System (JFS2)</li> <li>If the file is JFS2 but EFS is not enabled, then EFS must be enabled before the file can be restored</li> <li>If the user ID under which restore is being run does not have write permission for the directory, the permissions must be changed or the restore must be run under a different user ID</li> </ul> </p>
# 14077
CLI_BAD_EFS_file=ANS14077E File '{0}{1}{2}' is encrypted by Microsoft EFS and contains at least one sparse data stream. The operating system does not support restore for this file so it is not backed up or restored.\n
CLI_BAD_EFS_file_EXPLANATION=<p>An error in the Microsoft Windows API prevents successful restore of files that meet the following conditions: <ul> <li>The file is encrypted by Microsoft Encrypting File System (EFS) at the time it was backed up</li> <li>The file includes at least one data stream (alternate "named" stream or unnamed stream) that is sparse</li> <li>The operating system is any edition of Microsoft XP, Microsoft Windows Server 2003, or Microsoft Windows Server 2003 R2</li> </ul> Because the file cannot be restored, IBM Tivoli Storage Manager does not back it up. The problem is documented by Microsoft at http://support.microsoft.com/kb/2525290.</p>
CLI_BAD_EFS_file_SYSACT=<p>The file is not backed up or restored. Processing continues with the next object or ends if there are no further objects.</p>
CLI_BAD_EFS_file_URESP=<p>If this message is issued during a backup operation, you can do the following: <ul> <li>Disable EFS encryption for the file so that it can be backed up. </li> <li>If a backup copy of the file is not necessary, you can exclude it from backup.</li> </ul></p>
# 14087
DSI_WIZARD_LOAD_DATA_FAILED=An attemp to load data for the wizard failed. \nFor more information, please see the log file.
# 14088
DSI_ERROR=Error
# 14089
SnapDiff_Filer_Migration_Warning=ANS14089W File server {1} has been upgraded to Data ONTAP version '{2}.{3}.{0}'. Perform a full incremental backup by specifying option createnewbase=migrate as soon as possible.\n
SnapDiff_Filer_Migration_Warning_EXPLANATION=<p> The file server has been upgraded to a version that supports unicode file names for incremental backup using snapshot difference. Perform a full incremental in order to backup any files with unicode names that may have been skipped by the previous version of the IBM Tivoli Storage Manager client. </p>
SnapDiff_Filer_Migration_Warning_SYSACT=<p> Processing continues. </p>
SnapDiff_Filer_Migration_Warning_URESP=<p> Perform a full incremental by specifying the command line option createnewbase=migrate with the snapdiff option as soon as possible. </p>
# 14090
SnapDiff_Filer_Migration_Info=ANS14090I File server {1} has been upgraded to Data ONTAP version '{2}.{3}.{0}'. Perform a full incremental backup by specifying option createnewbase=migrate as soon as possible.\n
# 14091
dsmEvent_VM_Stat23_Fullvm_Incr_backup_start=Starting Full VM Incremental backup of Virtual Machine '{0}'\n
# 14099
dsmEvent_Fail_ToFind_SystemVolume=ANS14099E The system volume cannot be identified. Therefore the system state cannot be backed up.\n
dsmEvent_Fail_ToFind_SystemVolume_EXPLANATION=<p> The system volume contains the hardware-specific system state files that are needed to start Windows, such as Ntldr, Boot.ini, Ntdetect.com or Bootmgr. If the system volume cannot be identified, then these files cannot be backed up. Therefore it is not possible to back up the system state. </p>
dsmEvent_Fail_ToFind_SystemVolume_SYSACT=<p>Systemstate backup stops.</p>
dsmEvent_Fail_ToFind_SystemVolume_URESP=<p> Try the operation again. If the problem persists, obtain a service trace that captures the problem and contact IBM technical support for additional assistance. Your TSM administrator can help you configure the trace. </p>
# 14146
dsmEvent_VM_Stat21_Fullvm_backup_start=Starting Full VM backup of Virtual Machine '{0}'\n
# 14147
dsmEvent_VM_Stat22_Fullvm_backup_Success=Successful Full VM backup of Virtual Machine '{0}'\n
# 14148
dsmEvent_VM_Stat38_Fullvm_backup_Failed=ANS14148E Full VM backup of Virtual Machine '{0}' failed with RC {1}\n
dsmEvent_VM_Stat38_Fullvm_backup_Failed_EXPLANATION=<p> The Full VM backup of virtual machine failed. </p>
dsmEvent_VM_Stat38_Fullvm_backup_Failed_SYSACT=<p> The full backup of the virtual machine finished with failures. The next virtual machine in the vmlist will be processed. The reason for the failure is written to the local client error log. </p>
dsmEvent_VM_Stat38_Fullvm_backup_Failed_URESP=<p> Check the local client error log for reason for the failure. </p>
# 14150
dsmEvent_VM_Stat9_Incr_backup_of_VM_Failed=ANS14150E Incremental backup of Virtual Machine '{0}' failed with RC {1}\n
dsmEvent_VM_Stat9_Incr_backup_of_VM_Failed_EXPLANATION=<p> The incremental backup of virtual machine volumes failed. </p>
dsmEvent_VM_Stat9_Incr_backup_of_VM_Failed_SYSACT=<p> The backup of the virtual machine finished with failures. The next virtual machine in the vmlist will be processed. The reason for the failure is written to the local client error log. </p>
dsmEvent_VM_Stat9_Incr_backup_of_VM_Failed_URESP=<p> Check the local client error log for reason for the failure. </p>
# 14151
dsmEvent_VM_Stat10_Mount_of_VM_Failed=ANS14151E Failure mounting Virtual Machine '{0}'. RC={1}\n
dsmEvent_VM_Stat10_Mount_of_VM_Failed_EXPLANATION=<p> The VMware failed to mount virtual machine disk. </p>
dsmEvent_VM_Stat10_Mount_of_VM_Failed_SYSACT=<p> The backup of the virtual machine can not continue. The next virtual machine in the vmlist will be processed. Refer to dsmerror.log for detailed error message for the reason for the failure. </p>
dsmEvent_VM_Stat10_Mount_of_VM_Failed_URESP=<p> Refer to dsmerror.log for detailed error message. </p>
# 14152
dsmEvent_VM_Stat11_VMInit_Failed=ANS14152E Failure initializing VMware virtual machine environment. RC={0}. Refer to client dsmerror.log for detailed error messages.\n
dsmEvent_VM_Stat11_VMInit_Failed_EXPLANATION=<p> Failure initializing VMware virtual machine environment. Refer to dsmerror.log for detailed error messages. </p>
dsmEvent_VM_Stat11_VMInit_Failed_SYSACT=<p> The backup can not continue. </p>
dsmEvent_VM_Stat11_VMInit_Failed_URESP=<p> Refer to dsmerror.log for detailed error message. </p>
# 14153
dsmEvent_VM_Error_NoHost1=ANS14153E Hostname could not be found for Virtual Machine '{0}'
dsmEvent_VM_Error_NoHost1_EXPLANATION=<p> The backup of virtual machine failed. </p>
dsmEvent_VM_Error_NoHost1_SYSACT=<p> The backup of the virtual machine finished with failures. The next virtual machine in the vmlist will be processed. The reason for the failure is written to the local client error log. </p>
dsmEvent_VM_Error_NoHost1_URESP=<p> Check the local client error log for reason for the failure. </p>
# 14154
dsmEvent_VM_Error_NoHost2=ANS14154E Possible cause Virtual Machine is not running and does not have a static IP address.
dsmEvent_VM_Error_NoHost2_EXPLANATION=<p> The backup of virtual machine failed. </p>
dsmEvent_VM_Error_NoHost2_SYSACT=<p> The backup of the virtual machine finished with failures. The next virtual machine in the vmlist will be processed. The reason for the failure is written to the local client error log. </p>
dsmEvent_VM_Error_NoHost2_URESP=<p> Check the local client error log for reason for the failure. </p>
# 14155
dsmEvent_VM_Error_NotOnServer=ANS14155E Virtual Machine '{0}' could not be found on VMware server.
dsmEvent_VM_Error_NotOnServer_EXPLANATION=<p> The backup of virtual machine failed. </p>
dsmEvent_VM_Error_NotOnServer_SYSACT=<p> The backup of the virtual machine finished with failures. The next virtual machine in the vmlist will be processed. The reason for the failure is written to the local client error log. </p>
dsmEvent_VM_Error_NotOnServer_URESP=<p> Check the local client error log for reason for the failure. </p>
# 14156
dsmEvent_VM_Error_File_NonWindows_OS=ANS14156E File level VM backup of virtual machine '{0}' not supported.\nFile level VM backup not support on non Windows platform guest OS. Platform type: '{1}'.
dsmEvent_VM_Error_File_NonWindows_OS_EXPLANATION=<p> The backup of virtual machine failed. </p>
dsmEvent_VM_Error_File_NonWindows_OS_SYSACT=<p> The backup of the virtual machine finished with failures. The next virtual machine in the vmlist will be processed. The reason for the failure is written to the local client error log. </p>
dsmEvent_VM_Error_File_NonWindows_OS_URESP=<p> Backup using Full VM support. </p>
# 14159
dsmEvent_VM_Error_Other=ANS14159E Backup of Virtual Machine '{0}' failed. rc={1}.
dsmEvent_VM_Error_Other_EXPLANATION=<p> The backup of virtual machine failed. </p>
dsmEvent_VM_Error_Other_SYSACT=<p> The backup of the virtual machine finished with failures. The next virtual machine in the vmlist will be processed. The reason for the failure is written to the local client error log. </p>
dsmEvent_VM_Error_Other_URESP=<p> Check the local client error log for reason for the failure. </p>
# 14160
dsmEvent_Proxy_Reject_Id_Not_Authorized=ANS14160E Proxy Rejected: Proxy authority has not been granted to Agent Node: '{0}' for Target Node: '{1}'.
dsmEvent_Proxy_Reject_Id_Not_Authorized_EXPLANATION=<p> The backup of virtual machine failed. </p>
dsmEvent_Proxy_Reject_Id_Not_Authorized_SYSACT=<p> The backup of the virtual machine finished with failures. The next virtual machine in the vmlist will be processed. The reason for the failure is the node has not been granted proxy authority to access the node named by the backup proxy node. The TSM administrator must first grant proxy authority. </p>
dsmEvent_Proxy_Reject_Id_Not_Authorized_URESP=<p> The TSM server administrator must grant proxy authority for this node. See the administrator command "Grant Proxynode". </p>
# 14161
dsmEvent_VM_Error_Duplicate_Hostname=ANS14161E Duplicate virtual machine name '{0}' was detected in the same backup operation. Backup of virtual machine '{1}' can not continue without a unique object name.
dsmEvent_VM_Error_Duplicate_Hostname_EXPLANATION=<p> The backup of virtual machine failed. </p>
dsmEvent_VM_Error_Duplicate_Hostname_SYSACT=<p> The backup of the virtual machine finished with failures. The next virtual machine in the vmlist will be processed. The reason for the failure is written to the local client error log. </p>
dsmEvent_VM_Error_Duplicate_Hostname_URESP=<p> Choose a unique name for the virtual machine. </p>
# 14162
dsmEvent_VM_No_Backup_Exists=ANS14162E The virtual machine '{0}' has not been previously backed up.\n
dsmEvent_VM_No_Backup_Exists_EXPLANATION=<p>The specified virtual machine has not been previously backed up, so can not be specified for restore.</p>
dsmEvent_VM_No_Backup_Exists_SYSACT=<p>The specified virtual machine is skipped, and the next virtual machine in the restore list is processed.</p>
dsmEvent_VM_No_Backup_Exists_URESP=<p>Verify the virtual machine name to be restored, and re-try the operation.</p>
# 14163
dsmEvent_VM_No_Encryption_Performed=ANS14163I Encryption is currently enabled, but the virtual machine backup for '{0}' will not be encrypted.\n
# 14164
dsmEvent_VM_No_Compression_Performed=ANS14164W Compression is currently enabled, but the virtual machine backup for '{0}' is not compressed because client-side deduplication is not being used.\n
dsmEvent_VM_No_Compression_Performed_EXPLANATION=<p>Virtual machine files are not compressed because data is stored in a storage pool that is not enabled for client-side data deduplication.\nThe virtual machine files are not compressed during the backup processing unless data is stored in a storage pool that is enabled for client-data deduplication. </p>
dsmEvent_VM_No_Compression_Performed_SYSACT=<p>Backup continues, and data is not compressed.</p>
dsmEvent_VM_No_Compression_Performed_URESP=<p>Ensure that the storage pool is enabled for client-side data deduplication: Ensure that the deduplication parameter for the node is "ClientOrServer" and that deduplication is set for the client.</p>
# 14165
dsmEvent_VM_No_HostName_Found=ANS14165E Creating a Virtual Machine, but the hostname '{0}' was not found.\n
dsmEvent_VM_No_HostName_Found_EXPLANATION=<p>The Virtual Machine being creating must have a valid hostname to be created.</p>
dsmEvent_VM_No_HostName_Found_SYSACT=<p>Check the virtual machine hostname specified for correctness.</p>
dsmEvent_VM_No_HostName_Found_URESP=<p>Correct the virtual machine hostname specified and retry the restore.</p>
# 14166
dsmEvent_VM_No_DataCenter_Found=ANS14166E Creating a Virtual Machine, but the datacenter '{0}' was not found. The name may be incorrect or may be located in a VMware folder and require the folder name such as vmfolder/dcname.\n
dsmEvent_VM_No_DataCenter_Found_EXPLANATION=<p>The Virtual Machine being created must have a valid datacenter to be created.</p>
dsmEvent_VM_No_DataCenter_Found_SYSACT=<p>Processing stops.</p>
dsmEvent_VM_No_DataCenter_Found_URESP=<p>Check the virtual machine datacenter specified for correctness. If the datacenter is contained in a folder then the full datacenter name, complete with the folder path, must be specified, such as vmfolder/dcname.</p>
# 14167
dsmEvent_VM_No_DataStore_Found=ANS14167E Creating a Virtual Machine, but the datastore '{0}' was not found.\n
dsmEvent_VM_No_DataStore_Found_EXPLANATION=<p>The Virtual Machine being creating must have a valid datastore to be created.</p>
dsmEvent_VM_No_DataStore_Found_SYSACT=<p>Check the virtual machine datastore specified for correctness.</p>
dsmEvent_VM_No_DataStore_Found_URESP=<p>Correct the virtual machine datastore specified and retry the restore.</p>
# 14168
dsmEvent_VM_SOAP_Error=ANS14168E VMware has reported an error via their SOAP interface. On the Detailed Status Report panel, view the last error message reported. Also check the error log for more information about the problem that occurred.\n
dsmEvent_VM_SOAP_Error_EXPLANATION=<p>The command to VMware failed to complete. The error returned is displayed on the Restore or Backup summary panel under the Last Error Message section. </p>
dsmEvent_VM_SOAP_Error_SYSACT=<p>An error occurred, and the operation failed.</p>
dsmEvent_VM_SOAP_Error_URESP=<p>Check the reported error and correct the problem. Usually the reason for the error is a user&hyphen;supplied value which is not valid for the operation.</p>
# 14169
dsmEvent_VM_Write_Failure=ANS14169E A write failure occurred on the local disk proxy used to temporarily store the virtual machine virtual disk information. The write failure can be caused by the lack of available disk space on the drive used to store this information. The VMBACKDIR option can be used to assign a different disk location for this purpose. Check the drive being used and ensure that there is enough space available for this operation.\n
dsmEvent_VM_Write_Failure_EXPLANATION=<p>There was a write error from the local disk used to store the virtual machine virtual disk information. Usually the write error is due to lack of disk space, lack of write permissions, or some similar problem with the local disk. The VMBACKDIR option can be used to assign a different disk location if the local drive does not have enough free space for the operation.</p>
dsmEvent_VM_Write_Failure_SYSACT=<p>A disk write error occurred, and the operation failed.</p>
dsmEvent_VM_Write_Failure_URESP=<p>Check the local disk for possible causes of the write error, and use the VMBACKDIR option to assign another disk if needed.</p>
# 14170
dsmEvent_VM_InCompatible_Server=ANS14170E Can not create a Virtual Machine on VMware release '{0}' which was backed up from VMware release '{1}'.\n
dsmEvent_VM_InCompatible_Server_EXPLANATION=<p>The Virtual Machine being created was backed up from a version of VMware which is not compatible with the target VMware release version being used for the restore.</p>
dsmEvent_VM_InCompatible_Server_SYSACT=<p>Processing stops.</p>
dsmEvent_VM_InCompatible_Server_URESP=<p>Restore the Virtual Machine to a VMware system which is compatible with the level from which the Virtual Machine was backed up.</p>
# 14171
dsmEvent_VM_Error_Conn_Orphand=ANS14171E Backup of virtual machine '{0}' failed. VM could not be contacted because of '{1}' connection state.
dsmEvent_VM_Error_Conn_Orphand_EXPLANATION=<p> The backup of virtual machine failed. </p>
dsmEvent_VM_Error_Conn_Orphand_SYSACT=<p> The backup of the virtual machine finished with failures. The next virtual machine in list will be processed. </p>
dsmEvent_VM_Error_Conn_Orphand_URESP=<p> Correct the connection state from VMware vCenter and assign VM to an ESX Server. </p>
# 14172
dsmEvent_VM_Stat121_Fullvm_backup_start=Starting Full VM backup of VMware Virtual Machine '{0}'\n\tmode: '{1}'\n\ttarget node name: '{2}'\n\tdata mover node name: '{3}'\n\tapplication protection type: '{4}'\n\tapplication(s) protected: '{5}'\n
# 14173
dsmEvent_VM_Stat122_Fullvm_backup_Success=Successful Full VM backup of VMware Virtual Machine '{0}'\n\tmode: '{1}'\n\ttarget node name: '{2}'\n\tdata mover node name: '{3}'\n
# 14174
dsmEvent_VM_Stat138_Fullvm_backup_Failed=ANS14174E Full VM backup of VMware Virtual Machine '{0}' failed with RC={1} mode={2}, target node name='{3}', data mover node name='{4}'\n
dsmEvent_VM_Stat138_Fullvm_backup_Failed_EXPLANATION=<p> The Full VM backup of virtual machine failed. </p>
dsmEvent_VM_Stat138_Fullvm_backup_Failed_SYSACT=<p> The full backup of the virtual machine finished with failures. The next virtual machine in the vmlist will be processed. The reason for the failure is written to the local client error log. </p>
dsmEvent_VM_Stat138_Fullvm_backup_Failed_URESP=<p> Check the local client error log for reason for the failure. </p>
# 14175
dsmEvent_VM_Stat221_Fullvm_restore_start=Starting Full VM restore of VMware Virtual Machine '{0}' target node name='{1}', data mover node name='{2}'\n
# 14176
dsmEvent_VM_Stat222_Fullvm_restore_Success=Successful Full VM restore of VMware Virtual Machine '{0}' target node name='{1}', data mover node name='{2}'\n
# 14177
dsmEvent_VM_Stat238_Fullvm_restore_Failed=ANS14177E Full VM restore of VMware Virtual Machine '{0}' failed with RC={1} target node name='{2}', data mover node name='{3}'\n
dsmEvent_VM_Stat238_Fullvm_restore_Failed_EXPLANATION=<p> The Full VM restore of the virtual machine failed. </p>
dsmEvent_VM_Stat238_Fullvm_restore_Failed_SYSACT=<p> The full restore of the the virtual machine finished with failures. The next virtual machine in the vmlist will be processed. The reason for the failure is written to the local client error log. </p>
dsmEvent_VM_Stat238_Fullvm_restore_Failed_URESP=<p> Check the local client error log for reason for the failure. </p>
# 14178
dsmEvent_VM_No_Compression_Performed_For_Ctl=ANS14178W Compression is currently enabled, but the virtual machine control files for '{0}' will not be compressed because client-side deduplication is not being used for the management class default or specified by the -vmctlmc option for '{1}'.\n
dsmEvent_VM_No_Compression_Performed_For_Ctl_EXPLANATION=<p>Virtual machine control files are not compressed because data is stored in a storage pool that is not enabled for client-side data deduplication.\nThe virtual machine control files are not compressed during the backup processing unless data is stored in a storage pool that is enabled for client-data deduplication. </p>
dsmEvent_VM_No_Compression_Performed_For_Ctl_SYSACT=<p>Backup continues, and control file data is not compressed.</p>
dsmEvent_VM_No_Compression_Performed_For_Ctl_URESP=<p>Ensure that the storage pool is enabled for client-side data deduplication: run "q stg <pool name> f=d" and verify that the value of "Deduplicate Data?" is "yes". Ensure that client-side data deduplication is enabled on the server. To enable client-side data deduplication, use the DEDUPLICATION parameter on the REGISTER NODE or UPDATE NODE server command. Set the value of the parameter to CLIENTORSERVER. The value of the DEDUPLICATION option on the client must be set to YES. You can set the DEDUPLICATION option in the client options file, in the preference editor of the Tivoli Storage Manager client GUI, or in the client option set on the Tivoli Storage Manager server. Use the DEFINE CLIENTOPT command to set the DEDUPLICATION option in a client option set. To prevent the client from overriding the value in the client option set, specify FORCE=YES. Ensure that the deduplication parameter for the node is "ClientOrServer": The value of the DEDUPLICATION option on the client must be set to YES.</p>
# 14187
VSTORAGE_SKIPPING_RES_ALLOC_RESTORE=ANS14187W CPU and Memory Resource Allocation configuration settings cannot be restored when the IBM Tivoli Storage Manager data mover node is connected directly to a Virtual Center managed ESX/ESXi host. These settings have been skipped.\n
VSTORAGE_SKIPPING_RES_ALLOC_RESTORE_EXPLANATION=<p> The VMware vStorage APIs do not support the restore of CPU and Memory Resource Allocation configuration settings when connected directly to an ESX/ESXi host that is managed by a Virtual Center. </p>
VSTORAGE_SKIPPING_RES_ALLOC_RESTORE_SYSACT=<p>CPU and Memory Resource Allocation configuration settings are skipped. Processing continues.</p>
VSTORAGE_SKIPPING_RES_ALLOC_RESTORE_URESP=<p> Virtual machine CPU and Memory Resource Allocation configuration settings will be restored when the IBM Tivoli Storage Manager data mover node connects directly to a vCenter Server. Modify the VMCHOST to connect the TSM data mover to a vCenter Server. </p>
# 14191
VSTORAGE_SUGGEST_NBD_ON_SAN_REST_FAILURE=ANS14191E Restore VM operation failed using 'san' transport mode. In some cases switching from SAN to network-based VM restores can be successful.\n
VSTORAGE_SUGGEST_NBD_ON_SAN_REST_FAILURE_EXPLANATION=<p> Restore VM operations that fail using SAN transport mode can often be successful over a LAN path. If a restore vm operation fails using the 'SAN' transport mode, set the client option VMVSTORTRANSPORT to "nbd:nbdssl" and try the restore vm operation again. </p>
VSTORAGE_SUGGEST_NBD_ON_SAN_REST_FAILURE_SYSACT=<p>Restore VM operation failed using 'san' transport mode. Restore may be successful using 'nbd:nbdssl' transport modes.</p>
VSTORAGE_SUGGEST_NBD_ON_SAN_REST_FAILURE_URESP=<p> Restore VM operation failed using 'san' transport mode. In some cases network-based VM restores can be successful when using 'nbd' or 'nbdssl' transport modes. The VMVSTORTRANSPORT option can used to restrict the TSM client to use only the specified transport modes. </p>
# 14199
CLI_Sys_File_Inaccessible=ANS14199W File '{0}' is not backed up as part of the system state because cluster disk '{1}' is not accessible.
CLI_Sys_File_Inaccessible_EXPLANATION=<p>The indicated file or directory was returned by VSS as part of the backup file list of the writer. However, the cluster disk where the file is located is not accessible. The reasons for this problem can be that the cluster disk is offline or belongs to another node.</p>
CLI_Sys_File_Inaccessible_SYSACT=<p>The file is not backed up. Processing continues.</p>
CLI_Sys_File_Inaccessible_URESP=<p>This problem is documented in Microsoft knowledge base topic 980794 http://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 one or more files to be excluded from VSS enumeration. IBM Tivoli Storage Manager does not back up files that are not enumerated by VSS. If the volume is brought online to the node performing the system state backup, then it cannot be backed up. You must remove the volume from the registry key and restart the system before you can back up the volume.\nIf you do not want to implement the hotfix for this problem, IBM Tivoli Storage Manager continues to issue this message.</p>
# 14290
VMRESTORE_Can_Select_Only_One_VM=ANS14290E Only one virtual machine can be selected for restore.\n
VMRESTORE_Can_Select_Only_One_VM_EXPLANATION=<p>Restoring multiple virtual machines is not allowed. Only one virtual machine can be selected for restore.</p>
VMRESTORE_Can_Select_Only_One_VM_SYSACT=<p>No processing occurs.</p>
VMRESTORE_Can_Select_Only_One_VM_URESP=<p>Select only one virtual machine for restore.</p>
# 14291
dsmEvent_VM_Error_NotFoundOnServer=ANS14291E Virtual Machine could not be found on VMware server.
dsmEvent_VM_Error_NotFoundOnServer_EXPLANATION=<p> The backup of virtual machine failed. </p>
dsmEvent_VM_Error_NotFoundOnServer_SYSACT=<p> The backup of the virtual machine finished with failures. The next virtual machine in the vmlist will be processed. The reason for the failure is written to the local client error log. </p>
dsmEvent_VM_Error_NotFoundOnServer_URESP=<p> Check the local client error log for reason for the failure. </p>
# 14292
CLI_VMBACKUP_No_Virtual_Machine_found=ANS14292E No virtual machine found.\n
CLI_VMBACKUP_No_Virtual_Machine_found_EXPLANATION=<p>No virtual machine found with name or specified in domain option.</p>
CLI_VMBACKUP_No_Virtual_Machine_found_SYSACT=<p>Processing stopped.</p>
CLI_VMBACKUP_No_Virtual_Machine_found_URESP=<p>Specify a correct VM name or domain option.</p>
# 14946
VM_BACKUP_EXCLUDE_VMDK_NOT_FOUND=ANS14946W Warning: virtual machine: '{0}' disk: '{1}' excluded by user, was not found.\n
VM_BACKUP_EXCLUDE_VMDK_NOT_FOUND_EXPLANATION=<p> The specified virtual disk does not exist on the virtual machine. </p>
VM_BACKUP_EXCLUDE_VMDK_NOT_FOUND_SYSACT=<p>Processing continues.</p>
VM_BACKUP_EXCLUDE_VMDK_NOT_FOUND_URESP=<p> Use the "dsmc backup vm ..." command with the -preview option to display a listing of the disk labels which exist on the virtual machine. Since the disk was specified to be excluded from the backup, the backup will continue. However it is possible that a disk will included in the backup which was not desired, check the spelling of the disk label, and correct the disk label if an undesired disk is now included in the backup operation. </p>
# 14947
VM_BACKUP_INCLUDE_VMDK_NOT_FOUND=ANS14947E Error: virtual machine: '{0}' disk: '{1}' included by user, was not found.\n
VM_BACKUP_INCLUDE_VMDK_NOT_FOUND_EXPLANATION=<p> The specified virtual disk does not exist on the virtual machine. </p>
VM_BACKUP_INCLUDE_VMDK_NOT_FOUND_SYSACT=<p>Processing stops.</p>
VM_BACKUP_INCLUDE_VMDK_NOT_FOUND_URESP=<p> Use the "dsmc backup vm ..." command with the -preview option to display a listing of the disk labels which exist on the virtual machine. Check the spelling of the disk label and correct the disk label and then retry the 'backup vm' operation. </p>
# 14948
dsmEvent_VMDK_Not_Found=ANS14948E A specified virtual disk was not found on the virtual machine.\n
dsmEvent_VMDK_Not_Found_EXPLANATION=<p>You must specify a virtual disk label name which exists on the virtual machine.</p>
dsmEvent_VMDK_Not_Found_SYSACT=<p>Processing stops.</p>
dsmEvent_VMDK_Not_Found_URESP=<p> For a backup operation, use the "dsmc backup vm ..." command with the -preview option to display a listing of the disk labels which exist on the virtual machine. For a restore operation, use the "dsmc query vm ..." command with the -detail option to display a listing of the disk labels which exist on the virtual machine backup. Check the spelling of the disk label and correct the disk label and then retry the operation. </p>
# 14972
SnapDiff_Filer_Non_Unicode_Level_Warning=ANS14972W File server {1} has been upgraded to Data ONTAP version '{2}.{3}.{0}'. This version does not support unicode file names for snapshot difference incremental backup. Upgrade to a version that supports unicode file names as soon as possible.\n
SnapDiff_Filer_Non_Unicode_Level_Warning_EXPLANATION=<p> The file server has been upgraded from a version that supports unicode file names for incremental backup using snapshot difference to a version that does not. If you have upgraded from Data ONTAP version 7.3.3 (or later) to 8.0, you lose the ability to back up files with unicode file names when performing snapshot difference incremental backup. </p>
SnapDiff_Filer_Non_Unicode_Level_Warning_SYSACT=<p> Processing continues. However, files with unicode names are not backed up. </p>
SnapDiff_Filer_Non_Unicode_Level_Warning_URESP=<p> Upgrade to a version that supports unicode file names as soon as possible. If you have upgraded from Data ONTAP version 7.3.3 (or later) to 8.0, upgrade to 8.1 (or later). If it is not possible to upgrade at this time, you can suppress this warning message by renaming the file space on the IBM Tivoli Storage Manager server and performing a snapshot difference incremental backup. </p>
# 14978
DSI_DEDUPLICATION_REDUCTION_RATIO=Deduplication Reduction:
# 14979
DSI_TOTAL_DATA_REDUCTION_RATIO=Total Data Reduction:
# 14980
DSI_TOTAL_INSPECTED_BYTES=Total Bytes Inspected:
# 14983
DSI_TOTAL_DEDUPLICATED_FILES=Files Deduplicated:
# 14999
dsmEvent_Message_Too_Long=ANS14999I The following message was too long to log to the server: '{0}' \n
# 15001
DSI_BackChoice_Org_Incr=Incremental
# 15003
DSI_ACCUSER_DEFAULTNODE=Default Node Name:
# 15004
DSI_BackChoice_Incr=Incremental (complete)
# 15005
DSI_BackChoice_PartIncr=Incremental (date only)
# 15006
DSI_BackChoice_Selective=Always backup
# 15007
DSI_ACTIVITY=Activity
# 15008
DSI_ArchiveMCMenuItem={0}: {1} Days
# 15009
DSI_BackChoice_Image=Image backup
# 15010
DSI_ARCHIVE_ARCHIVE=Archive
# 15012
DSI_CLASS=Class
# 15013
DSI_ARCHIVE_DESCRIPTION=Description:
# 15014
DSI_ARCHIVE_TITEL=Archive
# 15015
DSI_NODE_NAME=Node Name
# 15020
DSI_ButtonStop=Stop
# 15025
DSI_ADMIN_ID=Admin ID
# 15026
DSI_CONN_SERVER_INFORMATION=Server Information
# 15028
DSI_DATE_STARTED=Date Started
# 15029
DSI_BackChoice_ImageIncr=Incremental image (date only)
# 15033
DSI_RESTART_REPLACE_ALL=All
# 15040
DSI_RESTART_TITLE=Select a Restore Operation to Restart
# 15041
DSI_RESTART_EXPLAIN=You may continue an interrupted restore operation by selecting a restore from the list below.
# 15042
DSI_RESTART_CANCEL=Cancel
# 15043
DSI_RESTART_RESTART=Restart
# 15044
DSI_RESTART_WINDOW_TITLE=Restart restore
# 15045
DSI_RESTART_DELETE=Delete
# 15046
DSI_RESTART_COLHDR_SOURCE=Source
# 15048
DSI_RESTART_COLHDR_STARTDATE=Start Date
# 15051
DSI_ACCUSER_TITLE=Enter Node to Access
# 15053
DSI_ACCUSER_NODE=Node Name:
# 15054
DSI_ACCUSER_USER=User Name:
# 15056
DSI_ACCUSER_MYSELF=Default
# 15057
DSI_ACCUSER_SET=Set
# 15061
DSI_CONN_FS_REGISTRY=Registry
# 15062
DSI_CONN_FS_EVENTLOG=Event Log
# 15063
DSI_CONN_FS_IMAGE=Image
# 15064
DSI_CONN_FS_PORTABLEMEDIA=Backup Sets
# 15065
DSI_CONN_FS_SYSTEMOBJECT=System Object
# 15066
DSI_CONN_FS_ACTIVEDIR=Active Directory
# 15067
DSI_CONN_FS_RSM=RSM
# 15068
DSI_CONN_FS_CLUSTERDB=Cluster DB
# 15069
DSI_CONN_FS_RAW=RAW
# 15070
DSI_CONN_FS_FILELEVEL=File Level
# 15071
DSI_OBJINFO_TYPE_VOLUME_RAW=Raw Logical Volume
# 15072
DSI_OBJINFO_TYPE_REGISTRY=Registry
# 15073
DSI_OBJINFO_TYPE_EVENTLOG=Event Log
# 15075
DSI_OBJINFO_TYPE_PORTABLEMEDIA=Backup Sets
# 15076
DSI_OBJINFO_TYPE_SYSTEMOBJECT=System Object
# 15077
DSI_OBJINFO_TYPE_ACTIVEDIR=Active Directory
# 15078
DSI_OBJINFO_TYPE_RSM=RSM
# 15079
DSI_OBJINFO_TYPE_CLUSTERDB=Cluster DB
# 15081
DSI_CONN_FS_PORTABLEBACKUPSETS_LOCAL=Local
# 15082
DSI_CONN_FS_PORTABLEBACKUPSETS_REMOTE=Server
# 15083
DSI_OBJINFO_TYPE_PORTABLEBACKUPSETSLOCAL=Backup Sets From Local
# 15084
DSI_OBJINFO_TYPE_PORTABLEBACKUPSETSREMOTE=Backup Sets From Server
# 15085
DSI_OBJINFO_TYPE_PORTABLEBACKUPSET=Backup Set
# 15086
DSI_WHAT_IMAGE_TO_RESTORE=What to restore for image
# 15087
DSI_IMAGE_PLUS_INCREMENTAL=Image plus incremental directories and files
# 15088
DSI_DELETE_INACTIVE_IMAGE=Delete inactive files from local
# 15089
DSI_RESTORE_IMAGE_ONLY=Image only
# 15090
DSI_BACKUP_IMAGE_TOC=Backup image with TOC (table of contents)
# 15092
DSI_CONN_FS_SYSVOL=System Volume
# 15093
DSI_OBJINFO_TYPE_SYSVOL=System Volume
# 15096
DSI_CONN_FS_COMPLUSDB=COM+ DB
# 15097
DSI_OBJINFO_TYPE_COMPLUSDB=COM+ DB
# 15098
DSI_STATUS=Status
# 15099
DSI_CONN_FS_CERTSRV=Certificate Server
# 15100
DSI_ABOUT_ADSM_TITEL=About TSM
# 15101
DSI_COLUMN_NAME=Name
# 15102
DSI_COLUMN_SIZE=Size
# 15103
DSI_COLUMN_MODIFIED=Modified
# 15104
DSI_COLUMN_CREATED=Created
# 15105
DSI_COLUMN_MANAGEMENT=Mgmt Class
# 15106
DSI_COLUMN_DIRECTORY=Directory
# 15107
DSI_COLUMN_BACKEDUP=Backed Up
# 15108
DSI_COLUMN_ARCHIVED=Archived
# 15109
DSI_COLUMN_ACCESSED=Accessed
# 15110
DSI_CONN_SERVER_NAME=Name:
# 15111
DSI_CONN_SERVER_TYPE=Type:
# 15112
DSI_CONN_SERVER_VERSION=Version:
# 15113
DSI_CONN_DEL_BACKUP=Delete Backup Files:
# 15114
DSI_CONN_DEL_ARCHIVE=Delete Archive Files:
# 15115
DSI_CONN_ACCESS_DATE=Last Access Date:
# 15117
DSI_CONN_ACCESS_NODE=Accessing As Node:
# 15118
DSI_CONN_USER_NAME=User Name:
# 15119
DSI_CONN_ACCESS_USER=Accessing As User:
# 15121
DSI_CONN_WINDOW_TITLE=Connection Information
# 15122
DSI_CONN_OK=OK
# 15124
DSI_CONN_SELECT=No file matching the current filter specification is selected.
# 15125
DSI_ACTIVITIES_SELECTED=TSM activities selected
# 15126
DSI_CONN_BE_PATIENT=Server doing conversion of archive data. Please be patient.
# 15127
DSI_CONN_FS_LOCAL=Local
# 15128
DSI_CONN_FS_REMOVABLE=Removable
# 15129
DSI_CONN_FS_NETWORK=Network
# 15130
DSI_POLICY_WINDOW_TITLE=Policy Information
# 15131
DSI_POLICY_TITLE=Display Policy Information
# 15133
DSI_NO_ACTIVITIES=There are no TSM activities to monitor.
# 15134
DSI_POLICY_DOMAIN=Domain:
# 15135
DSI_POLICY_ACTIVE_POLICY=Active Policy Set:
# 15136
DSI_POLICY_ACTIVATION_DATE=Activation Date:
# 15137
DSI_POLICY_DEFAULT_MGM_CLASS=Default Mgmt Class:
# 15138
DSI_POLICY_MGM_CLASS=Management Class:
# 15141
DSI_PIT_WINDOW_TITLE=Point in Time Restore
# 15142
DSI_PIT_TITLE=Enter a 'Point in Time' date
# 15143
DSI_PIT_NOTE=NOTE: Enabling or disabling Point in Time restore will cause all selections to be lost.
# 15144
DSI_PIT_USE_IT=Use a Point in Time date during restore
# 15145
DSI_PIT_CANCEL=Cancel
# 15146
DSI_PIT_OK=OK
# 15147
DSI_PIT_DAY=Day
# 15148
DSI_PIT_MONTH=Month
# 15149
DSI_PIT_YEAR=Year
# 15150
DSI_PIT_HOUR=Hour
# 15151
DSI_PIT_MINUTE=Minute
# 15154
DSI_NODES=Nodes
# 15155
DSI_OPTIONS_BUTTON=Options
# 15157
DSI_ACTIVE_TITLE_NASBACKUP=NAS Backup Report
# 15158
DSI_ACTIVE_TITLE_NASRESTORE=NAS Restore Report
# 15161
DSI_ACTIVE_ELAPSED_TIME=Elapsed Time:
# 15162
DSI_DISMISS_BUTTON=Dismiss
# 15163
DSI_ACTIVE_TRANSFER_RATE=Network (KB/s):
# 15164
DSI_ACTIVE_BYTES_TRANSFERRED=Bytes Transferred:
# 15165
DSI_ACTIVE_COMPRESSIO_RATIO=Compressed By:
# 15166
DSI_ACTIVE_OBJECTS_INSPECTED=Inspected:
# 15167
DSI_ACTIVE_OBJECTS_BACKED=Backed Up:
# 15168
DSI_ACTIVE_OBJECTS_FAILED=Failed:
# 15169
DSI_ACTIVE_OBJECTS_MARKED=Marked Inactive:
# 15170
DSI_ACTIVE_TITLE=Backup Report
# 15171
DSI_ACTIVE_VIEW=View
# 15172
DSI_ACTIVE_LASTERRMSG=Last Error Message
# 15173
DSI_ACTIVE_AGGR_TRASNFER_RATE=Aggregate(KB/s):
# 15174
DSI_ACTIVE_STATUS=Status:
# 15175
DSI_ACTIVE_OBJECTS_UPDATED=Updated:
# 15176
DSI_ACTIVE_OBJECTS_REBOUND=Rebound:
# 15177
DSI_NASDIFF_NASDIFF=NAS Differential Backup
# 15181
DSI_ACTIVE_STATUS_WAITING=Waiting for media...
# 15194
DSI_ACTIVE_OBJECTS_ARCHIVED=Archived:
# 15195
DSI_ACTIVE_TITLE_ARCHIVE=Archive Report
# 15196
DSI_ACTIVE_OBJECTS_DELETED=Deleted:
# 15197
DSI_ACTIVE_TITLE_ARCHDELETE=Archive Delete Report
# 15199
DSI_NASFULL_NASFULL=NAS Full Backup
# 15204
DSI_MENU_CLOSE_WINDOW=&Close
# 15211
DSI_MENU_FILE_DETAILS=&File details...
# 15218
DSI_MENU_HELP=Help
# 15219
DSI_REPORT_BUTTON=Report
# 15221
DSI_EXPAND_BUTTON=Expand
# 15238
DSI_MENU_SELECT_FILE=&Select Items
# 15239
DSI_MENU_DESELECT_FILE=&Deselect Items
# 15251
DSI_Stat_Bytes_LanFree=LanFree Data Bytes:
# 15252
DSI_SCHWIZ_COPY_FILES=Copy Files
# 15253
DSI_PREFERS_CLIENT_SESSINIT=Client
# 15254
DSI_PREFERC_ADMIN_PORT=Admin Port
# 15255
DSI_AS_NODE_NAME=As Node Name
# 15256
DSI_MENU_HELP_ABOUT=&About TSM
# 15258
DSI_COLLAPSE_BUTTON=Collapse
# 15265
DSI_CONN_SERVER_INFO=Server Information
# 15266
DSI_CONN_CLIENT_INFO=Remote Client Information
# 15267
DSI_CONN_AUTH_INFO=Authorization Information
# 15270
DSI_ARCOPT_OK=OK
# 15271
DSI_ARCOPT_CANCEL=Cancel
# 15272
DSI_ARCOPT_OVERRIDE=Override include/exlude list
# 15273
DSI_ARCOPT_DELETE_AFTER=Delete files after Archive
# 15274
DSI_ARCOPT_MANAGEMENT_CLASS=Management Class
# 15275
DSI_ARCOPT_COMPRESS_GROW=Continue compressing if object grows
# 15276
DSI_ARCOPT_COMPRESS=Compress objects
# 15277
DSI_ARCOPT_TITEL=Archive Options
# 15278
DSI_ARCOPT_HEADER=Override Archive Options
# 15280
DSI_NASBACKUP_NASBACKUP=NAS Backup
# 15281
DSI_NASRESTORE_NASRESTORE=NAS Restore
# 15282
DSI_BACKUP_BACKUP=Backup
# 15284
DSI_OBJINO_EXCLUDED_CHECKBOX=Excluded
# 15285
DSI_OBJINFO_IESOURCE=Source:
# 15286
DSI_OBJINFO_IEPATTERN=Pattern:
# 15287
DSI_BACKUP_TITEL=Backup
# 15289
DSI_ADVANCED_LABEL=Advanced
# 15290
DSI_BACKOPT_OK=OK
# 15291
DSI_BACKOPT_CANCEL=Cancel
# 15292
DSI_BACKOPT_TITEL=Backup Options
# 15293
DSI_BACKOPT_COMPRESS=Compress objects
# 15294
DSI_BACKOPT_COMPRESS_GROW=Continue compressing if object grows
# 15295
DSI_BACKOPT_EFFICIENT=Use less memory (slower)
# 15296
DSI_BACKOPT_HEADER=Override Backup Options
# 15299
DSI_PREFERCW_WIZARD_COMPLETED_NOTE=NOTE: The IBM Tivoli Storage Manager configuration files will be updated only after a session is created (e.g. Backup, Restore, Connection Information, etc.).\nIf the Java GUI is closed before a session is made, the changes will be lost.
# 15300
DSI_CHGPASS_OK=Change
# 15301
DSI_CHGPASS_CANCEL=Cancel
# 15302
DSI_CHGPASS_TITEL=Change Password
# 15303
DSI_CHGPASS_PASSWORD_EXPIRED=Your TSM password has expired
# 15305
DSI_CHGPASS_CURRENT=Current password:
# 15306
DSI_CHGPASS_NEW=New password:
# 15307
DSI_CHGPASS_VERIFY_NEW=Verify password:
# 15308
DSI_RC_Diff_Rebuild=Unable to reconstruct file from subfile components
# 15309
DSI_RC_Diff_Missing_Component=Unable to reconstruct file: necessary component was not restored
# 15311
DSI_HUBSMALL_LARGE=&Large
# 15312
DSI_BackDelChoice_Active=Delete Active Objects
# 15313
DSI_BackDelChoice_Inactive=Delete Inactive Objects
# 15314
DSI_ACTIVE_SUBFILE_RATIO=Subfile Reduction:
# 15315
DSI_ACTIVE_OBJECTS_SUBFILE=Subfile:
# 15317
DSI_POLICY_SERVER_NAME=Server:
# 15318
DSI_RESTORE_OPTIONS_ADVANCED=Advanced Restore Options
# 15319
DSI_RESTORE_OPTIONS_DISABLENQR=Disable No Query Restore method
# 15320
DSI_OPERATION_INTERRUPTED_MSG=The operation has been interrupted! \n\nPlease click on the 'Back' button to modify your configuration, or click on the 'Apply' button to try it again.
# 15321
DSI_HUB_SMALL=&Small
# 15322
DSI_HUB_TITEL=IBM Tivoli Storage Manager
# 15338
DSI_SCHWIZ_REPLACE_FILES=Replace Files
# 15339
DSI_OBJECTS_ASSIGNED=Inspected:
# 15340
DSI_LOGIN_WINDOW_TITEL=TSM Login
# 15341
DSI_LOGIN_TITEL=Login into a TSM server
# 15344
DSI_LOGIN_PASSWORD=Password:
# 15345
DSI_LOGIN_CANCEL=Cancel
# 15346
DSI_LOGIN_LOGIN=Login
# 15347
DSI_OBJINFO_OWNER=Owner:
# 15348
DSI_WIZARD_ONLINE_IMAGE_TITLE_DESC=Use this wizard to configure the backup-archive client for online image backup operations. \n\nYou can select a snapshot provider to create snapshots of your volumes. The snapshots are used as the source for online image backups.
# 15349
DSI_WIZARD_OPEN_FILE_SUPPORT_TITLE_DESC=Use this wizard to configure the backup-archive client for open file support backup and archive operations. \n\nYou can select a snapshot provider to create snapshots of your volumes. The snapshots are used as the source for snapshot based file backup and archive operations.
# 15350
DSI_PASSWORD_TITEL=Enter Password
# 15351
DSI_PASSWORD_LOGIN=Login
# 15352
DSI_PASSWORD_CANCEL=Cancel
# 15353
DSI_PASSWORD_ENTER_PASSWORD=Please enter your password
# 15355
DSI_OBJINFO_CREATOR=Creator:
# 15356
DSI_OBJINFO_LOCKED=Locked:
# 15357
DSI_OBJINFO_WHERE=Where:
# 15358
DSI_OBJINFO_KIND=Kind:
# 15359
DSI_OBJINFO_TYPE_DESCRIPTION=Archive Package
# 15360
DSI_OBJINFO_TITEL=Information
# 15361
DSI_OBJINFO_WINDOW_TITEL=Information Window
# 15362
DSI_OBJINFO_NAME=Name:
# 15363
DSI_OBJINFO_TYPE=Type:
# 15364
DSI_OBJINFO_SIZE=Size:
# 15365
DSI_OBJINFO_USER_ID=User ID:
# 15366
DSI_OBJINFO_GROUP_ID=Group ID:
# 15367
DSI_OBJINFO_MODIFY_TIME=Modified:
# 15368
DSI_OBJINFO_CHANGE_TIME=Changed:
# 15369
DSI_OBJINFO_ACCESS_TIME=Accessed:
# 15370
DSI_OBJINFO_TYPE_DIRECTORY=Directory
# 15371
DSI_OBJINFO_TYPE_VOLUME=Filespace
# 15372
DSI_OBJINFO_TYPE_FILE=File
# 15374
DSI_OBJINFO_TYPE_NETWORK=Network
# 15375
DSI_OBJINFO_TYPE_REMOVABLE=Removable
# 15376
DSI_OBJINFO_TYPE_MACHINE=Machine
# 15378
DSI_OBJINFO_ATTRIBUTES=Attributes:
# 15379
DSI_OBJINFO_CREATION_DATE=Created:
# 15380
DSI_PREFERC_GEN_COMMUNICATION=Communication
# 15381
DSI_PREFERC_GEN_COMMMETHOD=Communication Method
# 15382
DSI_PREFERC_GEN_TCPIP=TCP/IP
# 15383
DSI_OBJINFO_STORED_SIZE=Stored Size:
# 15384
DSI_PREFERC_GEN_USEDIRECTORY=Use Active Directory Lookup
# 15385
DSI_PREFERC_GEN_TCPIPv6=TCP/IP v6
# 15386
DSI_JOURNAL_INSTALL_START_MSG=Trying to install JBB service...
# 15387
DSI_JOURNAL_INSTALL_END_MSG=The TSM JBB Client service has been successfully installed!
# 15388
DSI_JOURNAL_INSTALL_ERROR_MSG=The TSM JBB Client service has not been installed!
# 15389
DSI_PREFERC_GEN_PIPE=Named Pipe
# 15390
DSI_PREFERC_GEN_SHMEM=Shared Memory
# 15391
DSI_PREFERC_GEN_COMMON=Common Options
# 15392
DSI_PREFERC_GEN_DURATION=Restart Duration
# 15393
DSI_PREFERC_GEN_INTERVAL=Restart Interval
# 15394
DSI_PREFERC_GEN_LARGE_BUFFERS=Use Large Buffers
# 15395
DSI_PREFERC_GEN_PIPE_NAME=Named Pipe Name
# 15396
DSI_COLUMN_EXPIRES=Expires on
# 15397
DSI_PREFERC_GEN_SHMEM_PORT=Port
# 15398
DSI_PREFERIS_FSIDLE_RETRIES=FS Idle Retries
# 15399
DSI_PREFERIS_FSIDLE_WAIT=FS Idle Wait Max
# 15400
DSI_PREFER_TITEL=Preferences
# 15401
DSI_PREFER_HELP=Help
# 15402
DSI_PREFER_APPLY=Apply
# 15403
DSI_PREFER_CANCEL=Cancel
# 15404
DSI_PREFER_OK=OK
# 15405
DSI_PREFER_FSEL_FILTER=File-Filter
# 15406
DSI_PREFER_FSEL_DIR=Directory
# 15407
DSI_PREFER_FSEL_FILES=Files
# 15408
DSI_PREFER_FSEL_SELECT=Selected
# 15409
DSI_PREFER_FSEL_OK=OK
# 15410
DSI_PREFER_FSEL_DOFILTER=Filter
# 15411
DSI_PREFER_FSEL_CANCEL=Cancel
# 15412
DSI_PREFERG_GENERAL=General
# 15413
DSI_OBJINO_INCLUDED=Included
# 15414
DSI_PREFERG_PROMPT_TAPES=Prompt before mounting tapes
# 15415
DSI_PREFERS_ERROR_LOG_MAX=Enable error log file wrapping
# 15416
DSI_PREFERG_SELECT=Select
# 15417
DSI_PREFERS_SCHED_LOG_MAX=Enable scheduler log file wrapping
# 15418
DSI_PREFERG_BYTES_PER_TRANS=Transaction Buffer Size
# 15419
DSI_PREFERG_ERROR_PROCESSING=Error Log
# 15420
DSI_PREFERG_ERROR_FILE=Log File Name
# 15421
DSI_PREFERG_SELECT_ERROR_FILE=Select error file
# 15422
DSI_PREFERG_PRUNE_OLD=Prune old entries
# 15423
DSI_PREFERG_KEEP_ENTRIES=Prune entries older than
# 15424
DSI_PREFERG_DAYS=Days
# 15425
DSI_PREFERG_SAVE_PRUNED=Save pruned entries
# 15426
DSI_PREFERB_BACKUP=Backup
# 15427
DSI_PREFERB_COMPRESS_OBJECTS=Compress objects
# 15428
DSI_PREFERB_CONTINUE_GROW=Continue compressing if object grows
# 15429
DSI_PREFERB_MEMORY_EFFICIENT=Use memory-saving algorithm
# 15430
DSI_PREFERB_RETRY_IF_CHANGES=Number of retries if file is in use
# 15431
DSI_OBJINFO_EXPIRES_TIME=Expires on:
# 15432
DSI_PREFERR_RESTORE=Restore
# 15433
DSI_PREFERR_FILE_EXISTS=Action for files that already exist
# 15434
DSI_PREFERR_SHOW_PROMPT=Ask user before replacing
# 15435
DSI_PREFERR_LEAVE_INTACT=Leave existing files intact
# 15436
DSI_PREFERR_REPLACE_EXISTING=Replace existing files
# 15437
DSI_PREFERR_REPLACE_READONLY=Replace files even if read-only/locked
# 15438
DSI_PREFERS_SCHEDULE=Scheduler
# 15439
DSI_PREFERS_SCHEDULE_MODE=Schedule Mode
# 15440
DSI_PREFERS_POLLING=Polling
# 15441
DSI_PREFERS_PROMPTED=Prompted
# 15442
DSI_PREFERS_QUERY_SCHEDULE=Query Schedule Interval
# 15443
DSI_PREFERS_HOURS=Hours
# 15444
DSI_PREFERS_TCP_ADDRESS=Your TCP/IP address
# 15445
DSI_PREFERS_TCP_PORT=Your TCP/IP port
# 15446
DSI_PREFERS_RETRY_PERIOD=Retry period
# 15447
DSI_PREFERS_CMD_RETRIES=Maximum command retries
# 15448
DSI_PREFERI_SNAP_FSIDLE_RETRIES=FS Idle Retries
# 15449
DSI_PREFERI_SNAP_FSIDLE_WAIT=FS Idle Wait Max
# 15450
DSI_PREFERS_SCHEDULE_LOG=Schedule Log
# 15451
DSI_PREFERS_ERROR_FILE=Save errors in file:
# 15452
DSI_PREFERS_SELECT=Select
# 15453
DSI_PREFERS_SELECT_ERROR_FILE=Select Schedule Log File
# 15454
DSI_SCHWIZ_CHOOSE_LOGFILE=Choose the Log file name location
# 15455
DSI_PREFERC_TCPIP_PORT=Server Port
# 15456
DSI_PREFERC_TCPIP_BUFSIZE=Buffer Size
# 15457
DSI_PREFERC_TCPIP_SERVER_ADDR=Server Address
# 15458
DSI_PREFERC_TCPIP_WINDOW_SIZE=Window Size
# 15459
DSI_PREFERC_TCPIP_NO_DELAY=Send transaction to the server immediately
# 15460
DSI_PREFERB_RESET_LAST_ACCESS_DATE=Reset modified last access date
# 15461
DSI_PREFERB_EXCLUDE_DOMAIN=Exclude these domain(s) from backup
# 15462
DSI_PREFERB_RESET_ARCHIVE_ATTRIB=Reset archive attribute
# 15463
DSI_SnapProviderChoice_JFS2=AIX JFS2 snapshot provider
# 15464
DSI_SnapProviderChoice_LVM=LINUX LVM snapshot provider
# 15465
DSI_SnapProviderChoice_NONE=Do not use a snapshot
# 15466
DSI_PREFERB_SNAPPROVIDER_FS_TYPE=Enable snapshot based file backup/archive using: 
# 15467
DSI_PREFERB_SNAPPROVIDER_IMAGE_TYPE=Enable snapshot based online image backup using: 
# 15468
DSI_PREFERC_TCPIP_SSLREQUIRED=SSL is Required
# 15469
DSI_BackChoice_SnapDiffSel_WINDOW_TITEL=Difference Snapshot Choices
# 15470
DSI_RESTOPT_WINDOW_TITEL=Restore Options
# 15471
DSI_RESTOPT_TITEL=Modify restore and collision options
# 15472
DSI_RESTOPT_OK=OK
# 15473
DSI_RESTOPT_CANCEL=Cancel
# 15474
DSI_RESTOPT_WHAT_OBJECTS=What objects to restore
# 15475
DSI_RESTOPT_ALL_SELECTED=All selected files and directories
# 15476
DSI_RESTOPT_FILES_ONLY=Files only
# 15477
DSI_RESTOPT_DIRS_ONLY=Directories only
# 15478
DSI_RESTOPT_ACTIONS_EXIST=Action for files that already exist
# 15479
DSI_RESTOPT_REPLACE_FILES=Replace
# 15480
DSI_RESTOPT_ASK_USER=Ask user before replacing
# 15481
DSI_RESTOPT_REPLACE_RO=Replace files even if read-only/locked
# 15482
DSI_SCHWIZ_SCHNAME_UPDATE_OR_REMOVE_DESC=Please select name of service you want to update or remove.
# 15483
DSI_RETROPT_WINDOW_TITEL=Retrieve Options
# 15484
DSI_RETROPT_TITEL=Modify retrieve and collision options
# 15485
DSI_RETROPT_WHAT_OBJECTS=What objects to retrieve
# 15486
DSI_RESTOPT_ONLY_IF_NEWER=Replace only if newer
# 15487
DSI_PREFVM_NOUSERNAME_ENTERED=Error: A VM User name must be specified if a VM Password is present.
# 15488
DSI_ENABLE_LANFREE=Enable LAN-free
# 15489
DSI_SCHEDULER_REMOTE_OPTIONS=Remote Options
# 15490
DSI_RESTORE_TITEL=Restore
# 15491
DSI_RESTORE_RESTORE=Restore
# 15493
DSI_PREFERIS_GAPSIZE_KB=KB
# 15494
DSI_PREFERIS_GAPSIZE_MB=MB
# 15495
DSI_PREFERIS_GAPSIZE_GB=GB
# 15496
DSI_PREFERIS_FSIDLEWAIT_SEC=S
# 15497
DSI_RESTORE_PIT=Point In Time
# 15498
DSI_PREFERIS_FSIDLEWAIT_MILLISEC=MS
# 15500
DSI_RESTDST_WINDOW_TITEL=Restore Destination
# 15501
DSI_RESTDST_OK=Restore
# 15502
DSI_RESTDST_CANCEL=Cancel
# 15503
DSI_RESTDST_TITEL=Select destination for restored objects
# 15504
DSI_RESTDST_RESTORE_TO=Restore to
# 15505
DSI_RESTDST_ORIGINAL=Original location
# 15506
DSI_RESTDST_FOLLOWING=Following location
# 15508
DSI_RESTDST_FSEL_SELECT=Select
# 15509
DSI_RESTDST_FSEL_SELECT_DIR=Select Destination Directory
# 15513
DSI_RESTDST_FSEL_OK=OK
# 15515
DSI_RESTDST_FSEL_CANCEL=Cancel
# 15516
DSI_RESTDST_COMPLETE_PATH=Restore complete path
# 15517
DSI_RESTDST_PARTIAL_PATH=Restore partial path
# 15518
DSI_RESTDST_NOT_PRESERVE=Do not preserve directory structure
# 15520
DSI_RESTDSTR_WINDOW_TITEL=Retrieve Destination
# 15521
DSI_RESTDSTR_OK=Retrieve
# 15522
DSI_RESTDSTR_TITEL=Select destination for retrieved objects
# 15523
DSI_RESTDSTR_RESTORE_TO=Retrieve to
# 15524
DSI_RESTDSTR_COMPLETE_PATH=Retrieve complete path
# 15525
DSI_RESTDSTR_PARTIAL_PATH=Retrieve partial path
# 15527
DSI_MISC_CMD=CMD
# 15539
DSI_MISC_INVALID_LENGTH=Entry must be between {0} and {1} characters in length.
# 15540
DSI_RESTDST_NOBASE=Restore partial path without base directory
# 15541
DSI_RESTDSTR_NOBASE=Retrieve partial path without base directory
# 15547
DSI_BackChoice_ImageSnapshot=Snapshot image backup
# 15548
CLI_Rest_Image_To_File_Confirm=File '{0}' exists. Do you want to replace it?
# 15549
DSI_BackChoice_SnapDiffIncr=Incremental (snapshot difference)
# 15551
GUI_PREF_EFSDECRYPT_LABEL=Decrypt Encrypted File System (EFS) files
# 15553
DSI_PREFEI_INCLUDE_FS=Include.Fs
# 15556
DSI_RACTIVE_ELAPSED_TIME=Elapsed Time:
# 15557
DSI_SCHEDULER_LOGFILES=Log Files
# 15558
DSI_RACTIVE_TRANSFER_RATE=Network (KB/s):
# 15560
DSI_ACCEPTOR_NAME_REMOVE_DESC=The TSM acceptor is an HTTP daemon that serves the Web client Java applet to Web browsers. The program that starts the client acceptor process is called dsmcad.exe. The TSM client acceptor is installed and run as a service.
# 15561
DSI_RACTIVE_OBJECTS_INSPECTED=Inspected:
# 15562
DSI_RACTIVE_OBJECTS_RESTORED=Restored:
# 15563
DSI_RACTIVE_OBJECTS_FAILED=Failed:
# 15564
DSI_RACTIVE_TITLE=Restore Report
# 15565
DSI_RACTIVE_VIEW=View
# 15566
DSI_RACTIVE_LASTERRMSG=Last Error Message
# 15567
DSI_ACCEPTOR_SELECT_SERVICE=Select Web Client Service
# 15568
DSI_RACTIVE_AGGR_TRANSFER_RATE=Aggregate (KB/s):
# 15569
DSI_RACTIVE_STATUS=Status:
# 15570
DSI_RACTIVE_OBJECTS_RETRIEVED=Retrieved:
# 15571
DSI_RACTIVE_TITLE_RETRIEVE=Retrieve Report
# 15572
DSI_RECALL_RECALL=Recall
# 15573
DSI_MIGRATE_MIGRATE=Migrate
# 15574
DSI_RECONCILE_RECONCILE=Reconcile
# 15575
DSI_THRESHMIG_THRESHMIG=Threshold Migration
# 15576
DSI_REMOVEHSM_REMOVEHSM=Remove Space Management
# 15577
DSI_TSM_ACTIVITIES=TSM Activities
# 15578
DSI_MONITOR_TSM_ACTIVITIES=&Monitor TSM Activities
# 15579
DSI_RC_DirInUse=The directory is being used by another process
# 15580
DSI_EXISTS_TITLE=File already exists - replace?
# 15581
DSI_EXISTS_WINDOW_TITLE=File Exists
# 15582
DSI_EXISTS_NAME=Name:
# 15583
DSI_EXISTS_PATH=Location:
# 15584
DSI_EXISTS_ORIGINAL_FILE=Local File
# 15585
DSI_EXISTS_BACKUP_FILE=TSM File
# 15586
DSI_EXISTS_MODIFIED_DATE=Mod. Date:
# 15587
DSI_EXISTS_SIZE=Size:
# 15588
DSI_EXISTS_DONT_RESTORE=Do not Replace
# 15589
DSI_EXISTS_RESTORE=Replace
# 15590
DSI_EXISTS_CANCEL=Cancel
# 15591
DSI_EXISTS_APPLY_ALL=Apply action to all remaining files
# 15592
DSI_EXISTS_ACCESS_WINDOW_TITLE=Access Denied
# 15593
DSI_EXISTS_ACCESS_TITLE=File is Read-Only - force overwrite?
# 15594
DSI_EXISTS_ACCESS_SKIP=Skip
# 15595
DSI_EXISTS_ACCESS_FORCEOVERWRITE=Overwrite
# 15596
DSI_EXISTS_INUSE_WINDOW_TITLE=File In Use by Another Process
# 15597
DSI_EXISTS_INUSE_TITLE=File in use by another process-replace at reboot?
# 15598
DSI_EXISTS_INUSE_FORCEOVERWRITE=Replace at Reboot
# 15599
DSI_RC_FileInUse=The file is being used by another process
# 15610
DSI_MEDIA_WINDOW_TITLE=Media Mount
# 15611
DSI_MEDIA_TITLE=Offline Media is Required
# 15612
DSI_MEDIA_EXPLAINATION=The following object requires offline media to be mounted.
# 15613
DSI_MEDIA_OBJECT=Object:
# 15614
DSI_MEDIA_DEVICE=Device:
# 15615
DSI_MEDIA_VOLUME=Volume Label:
# 15616
DSI_MEDIA_ACTION=Select an appropriate action
# 15617
DSI_MEDIA_WAITONCE=Wait for the volume to be mounted
# 15618
DSI_MEDIA_WAITALWAYS=Always wait for a volume to be mounted
# 15619
DSI_MEDIA_SKIPOBJECT=Skip this object
# 15620
DSI_MEDIA_SKIPTAPE=Skip all objects on this volume
# 15621
DSI_MEDIA_SKIPALL=Skip all objects requiring a media to be mounted
# 15622
DSI_MEDIA_CANCELOPERATION=Cancel entire operation
# 15623
DSI_MEDIA_OK=OK
# 15624
DSI_PREFERIS_IMAGE_SNAPSHOT=Image-Snapshot
# 15625
DSI_PREFERIS_IMAGE_OPTIONS=Image Options
# 15626
DSI_PREFERIS_IMAGE_GAP_SIZE=Gap Size
# 15627
DSI_PREFERIS_SNAPSHOT_OPTIONS=Snapshot Options
# 15628
DSI_PREFERIS_CACHE_LOC=Cache Location
# 15629
DSI_DPREFB_SUB_CACHE_SIZE=Cache Size (MB)
# 15630
DSI_DPREFB_SUB_CACHE_PATH=Cache Path
# 15632
DSI_DPREFB_SUB_BACKUP=Use adaptive sub-file backup
# 15633
DSI_PREFERIS_CACHE_SIZE=Cache Size
# 15634
DSI_ENCRYPTION_VERIFY_KEY=Confirm Key password:
# 15635
DSI_ENCRYPTION_KEY=Encryption Key password:
# 15636
DSI_ENCRYPT_STATIC_TITLE=Enter File Encryption Key Password 
# 15637
DSI_SCHED_CONFIRM_AND_APPLY_DESC=You have completed the configuration of the TSM Scheduler. Click on the 'Apply' button to confirm your configuration.
# 15638
DSI_ENCRYPTION_SKIP=Skip
# 15639
DSI_ENCRYPTION_APPLY_ALL=Apply action to all remaining encrypted files
# 15640
DSI_GENERIC_TITLE=TSM
# 15641
DSI_GENERIC_OK=OK
# 15642
DSI_GENERIC_CANCEL=Cancel
# 15643
DSI_GENERIC_YES=Yes
# 15644
DSI_GENERIC_NO=No
# 15645
DSI_GENERIC_CONTINUE=Continue
# 15646
DSI_ENCRYPTION_FILENAME=File name:
# 15647
DSI_CONN_FS_MSDFS=Distributed File System
# 15648
DSI_OBJINFO_TYPE_AFSDFS=AFS/DFS File System
# 15649
DSI_PREFERIS_PREPOST_CMD=Pre/Post Snapshot Commands
# 15651
DSI_SCHED_SELECT_SERVICE=Select Scheduler Service
# 15662
DSI_ESTIMAT_UNKNOWN=N/A
# 15665
DSI_ESTIMAT_RESET=Reset
# 15667
DSI_LOCAL_ADO=Local AD Object
# 15670
DSI_OBJINFO_BACKUP_TIME=Backup Date:
# 15671
DSI_OBJINFO_ARCHIVE_TIME=Archive Date:
# 15672
DSI_OBJINFO_TYPE_VOLUME_LOCAL=Local Filespace
# 15674
DSI_OBJINFO_USAGE=Capacity (%Used):
# 15676
DSI_OBJINFO_LASTINCR_TIME=Last Incremental:
# 15677
DSI_OBJINFO_MGMTCLASS=Management Class:
# 15678
DSI_OBJINFO_USAGE_STR={0} ({1}%)
# 15679
DSI_OBJINFO_FILESPACE_TYPE=Filespace ({0})
# 15684
DSI_FIND_SEARCH=Search
# 15685
DSI_FIND_FILTER=Filter
# 15694
DSI_FIND_NAME_ANY=any name
# 15695
DSI_FIND_NAME_MASK=matches mask
# 15696
DSI_FIND_NAME_STARTS=starts with
# 15697
DSI_FIND_NAME_ENDS=ends with
# 15698
DSI_FIND_NAME_CONTAINS=contains
# 15699
DSI_FIND_NAME_IS=is
# 15700
DSI_FIND_SIZE_LARGER=larger or equal
# 15701
DSI_FIND_SIZE_EXACTLY=exactly
# 15702
DSI_FIND_SIZE_SMALLER=smaller or equal
# 15703
DSI_FIND_DATELABEL_ANY=any date
# 15705
DSI_FIND_TYPE_ALL=all files
# 15706
DSI_FIND_TYPE_REGULAR=regular files
# 15707
DSI_FIND_TYPE_SPECIAL=special files
# 15708
DSI_FIND_TITLE_BA=Find Files (Backup)
# 15709
DSI_FIND_TITLE_RS=Find Files (Restore)
# 15710
DSI_FIND_TITLE_AR=Find Files (Archive)
# 15711
DSI_FIND_TITLE_RT=Find Files (Retrieve)
# 15712
DSI_FIND_ACT_STOP=Stop
# 15713
DSI_FIND_ACT_TITLE=Searching...
# 15714
DSI_FIND_ACT_SEARCHIN=Searching in:
# 15717
DSI_FIND_INVALID_DIR=Invalid Start Path. Please select a valid directory.
# 15718
DSI_INVALID_DIR_SELECTED=The selected object is not a valid directory. Please try again.
# 15719
DSI_FIND_FILTER_WARNING=Items currently selected will not be processed if they do not match the filter specification. Continue anyway?
# 15720
DSI_IE_SELECT_INFO=If you need to exclude many files from this folder, it is recommended that you use the Include-Exclude Wizard rather than handling these files individually.\nHandling these files one at a time could take a while. Are you sure you want to continue?
# 15721
DSI_FIND_NO_MATCHES=No matches.
# 15734
DSI_FIND_DATELABEL_BETWEEN=between {0} {1} and {2} {3}
# 15743
DSI_FIND_TITLE_ARDEL=Find Files (Archive Delete)
# 15751
DSI_ABOUT_PRODUCTNAME=Storage Manager
# 15752
DSI_ABOUT_CLIENTNAME=Backup-Archive Client
# 15753
DSI_ABOUT_VERSION=Version {0}, Release {1}, Level {2}.{3} {4}
# 15754
DSI_ABOUT_LICENSEDMAT=Licensed Materials - Property of IBM.
# 15755
DSI_ABOUT_COPYRIGHT=(c) Copyright by IBM Corporation and other(s) 1990, {0}.
# 15756
DSI_ABOUT_RIGHTSRESERVED=All Rights Reserved.
# 15757
DSI_ABOUT_TRADEMARK1=See product license for details.
# 15758
DSI_FIND_TITLE_BADEL=Find Files (Backup Delete)
# 15759
DSI_ABOUT_GOVTRIGHTS=
# 15760
DSI_ABOUT_GOVTRIGHTS2=
# 15761
DSI_ABOUT_GOVTRIGHTS3=
# 15762
DSI_ABOUT_TRADEMARK2=
# 15763
DSI_ABOUT_TRADEMARK3=
# 15764
DSI_STATUSBAR_EXCLUDED_FILE=File '{0}' is excluded
# 15766
DSI_OBJINFO_FSID=fsID:
# 15767
DSI_OBJINFO_UNICODE=Unicode:
# 15768
DSI_FSRENAME_YES=Yes, rename this non-Unicode filespace.
# 15769
DSI_FSRENAME_YESALL=Yes, rename all non-Unicode filespaces in this operation.
# 15770
DSI_FSRENAME_NO=No, do not rename this non-Unicode filespace.
# 15771
DSI_FSRENAME_NOALL=No, do not rename any non-Unicode filespaces in this operation.
# 15772
DSI_FSRENAME_CANCEL_OPERATION=Cancel entire operation
# 15773
DSI_FSRENAME_EXPLANATION=There needs to be a one time rename of the existing filespace '{0}' on the server in order to backup/archive this filespace as a Unicode enabled filespace. Once this change occurs, the filespace '{1}' will be renamed to '{2}_OLD', and the client will add '{3}' again as a Unicode enabled filespace. The current operation will continue using the Unicode enabled filespace. Do you want to continue?
# 15774
DSI_FSRENAME_WINDOW_TITLE=Rename Filespace
# 15775
DSI_FSRENAME_TITLE=Select Option for Renaming Filespace
# 15776
DSI_FSRENAME_GROUPBOX=Select Rename Option
# 15777
DSI_FSRENAME_OK=OK
# 15778
DSI_PIT_SECOND=Seconds
# 15779
DSI_STATUSBAR_EXCLUDED=Directory '{0}' is excluded
# 15780
DSI_STATUSBAR_PATH_FILTERED=Displaying {0} (filtered)
# 15781
DSI_STATUSBAR_PATH=Displaying {0}
# 15782
DSI_STATUSBAR_LOADING=Loading {0} {1}
# 15783
DSI_STATUSBAR_LOADING_DONE=Ready.
# 15784
DSI_STATUSBAR_SCANNING=Scanning {0} ...
# 15785
DSI_STATUSBAR_FILTERING=Filtering {0} ...
# 15787
DSI_PREFERI_INCLUDE_IMAGE=Include.Image
# 15788
DSI_PREFERI_IMAGE_TYPE=Image Type
# 15789
DSI_PREFERI_PRE_SNAP_CMD=Presnapshot Command
# 15790
DSI_AUTHERR_DUPLICATE=This authorization rule has already been defined.
# 15791
DSI_AUTHERR_NO_FS_BA=No files from the specified filespace have been backed up yet.
# 15792
DSI_AUTHERR_NO_FS_AR=No files from the specified filespace have been archived yet.
# 15793
DSI_AUTHERR_QRY_ERROR=Communications error with server during authorization query.
# 15794
DSI_AUTHERR_NO_FILES_BA=No files backed up yet match the specified file name.
# 15795
DSI_AUTHERR_NO_FILES_AR=No files archived yet match the specified file name.
# 15796
DSI_AUTHERR_NO_NODE=Please supply the name of a node to grant access to.
# 15797
DSI_PREFERI_POST_SNAP_CMD=Postsnapshot Command
# 15798
DSI_PREFERI_SNAP_CACHE_LOC=Snapshot Cache Location
# 15806
DSI_PREFERI_SNAP_FSIDLE_WAIT_MIN=FS Idle Wait Min
# 15807
DSI_PREFERIS_FSIDLE_WAIT_MIN=FS Idle Wait Min
# 15811
DSI_STATUSBAR_FILE=File: {0}
# 15812
DSI_STATUSBAR_OBJECT=Object: {0}
# 15813
DSI_PREFERG_FSRENAME_NO=no
# 15814
DSI_PREFERG_FSRENAME_YES=yes
# 15815
DSI_PREFERG_FSRENAME_PROMPT=prompt
# 15816
DSI_PREFERG_FSRENAME_LABEL=Rename non-Unicode filespaces during backup/archive.
# 15817
DSI_PREFERI_IMAGE_GAP_SIZE=Image Gap Size
# 15818
DSI_PREFERI_IMAGE_TYPE_SNAPSHOT=Snapshot
# 15819
DSI_PREFERI_IMAGE_TYPE_DYNAMIC=Dynamic
# 15820
DSI_HELP_BUTTON=Help
# 15829
DSI_AUTHORISATION_FILESPACE=Filespace Name:
# 15830
DSI_AUTHORISATION_OK=OK
# 15831
DSI_AUTHORISATION_CANCEL=Cancel
# 15833
DSI_AUTHORISATION_NODE=Grant Access to Node:
# 15834
DSI_AUTHORISATION_PATH=Directory:
# 15835
DSI_AUTHORISATION_USER=User:
# 15836
DSI_AUTHORISATION_FILENAME=Filename:
# 15837
DSI_AUTHORISATION_TYPE=Permit Access to:
# 15838
DSI_AUTHORISATION_BACKUP=Backed up Objects
# 15839
DSI_AUTHORISATION_ARCHIVE=Archived Objects
# 15840
DSI_AUTHORISATION_ADD=Add...
# 15841
DSI_AUTHORISATION_CHANGE=Change...
# 15842
DSI_AUTHORISATION_DELETE=Delete
# 15843
DSI_AUTHORISATION_TITLE=Node Access List
# 15847
DSI_PREFERI_IMAGE_TYPE_STATIC=Static
# 15850
DSI_PREFER_ERR_WINDOW_TITLE=Option Error
# 15851
DSI_PREFER_ERR_TITLE=Error in options file
# 15852
DSI_PREFER_ERR_OPTION=Option file:
# 15853
DSI_PREFER_ERR_INVALID=Invalid entry:
# 15854
DSI_PREFER_ERR_LINENUMBER=Line number:
# 15855
DSI_PREFER_ERR_COMPLETE=Complete line:
# 15856
DSI_PREFER_ERR_REASON=Reason:
# 15857
DSI_PREFER_ERR_OK=OK
# 15858
DSI_PREFER_NOT_RUNTIME=Please restart client for new preferences to take effect.
# 15859
DSI_AUTHORISATION_FILESPACE_AND_DIRECTORY=Filespace and Directory: 
# 15860
DSI_OPENREG_WINDOW_TITLE=Open Registration
# 15861
DSI_OPENREG_TITLE=Register New Node
# 15862
DSI_OPENREG_NEW_NODE=New node name:
# 15863
DSI_OPENREG_CONTACT=Contact Information
# 15864
DSI_OPENREG_PASSWORD=Password (enter twice for verification)
# 15865
DSI_OPENREG_CANCEL=Cancel
# 15866
DSI_OPENREG_REGISTER=Register
# 15867
DSI_AUTHORISATION_ADD_TITLE=Add Access Rule
# 15868
DSI_AUTHORISATION_CHANGE_TITLE=Change Access Rule
# 15869
DSI_AUTHORISATION_SUBDIRS=Include subdirectories
# 15870
DSI_AUTHORISATION_MAIN_DIR=Include files for this directory only 
# 15871
DSI_AUTHORISATION_ACCESS=Access: 
# 15875
DSI_STATUSBAR_LOADING_DOTDOTDOT=Loading {0}...
# 15876
DSI_STATUSBAR_LOADED={0} has been loaded.
# 15877
DSI_CFGWIZ_PLUGIN_NOT_AVAILABLE=Configuration Wizard plugin is not available.
# 15878
DSI_PREFER_PLUGIN_NOT_AVAILABLE=Preferences Editor plugin is not available.
# 15879
DSI_ABOUT_COPYRIGHT_JAVA=Java and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or its affiliates.
# 15880
DSI_FSDELETE_WINDOW_TITLE=Delete Filespaces
# 15881
DSI_FSDELETE_TITLE=Delete Backup/Archive Filespaces
# 15882
DSI_FSDELETE_WARNING=WARNING: This dialog allows you to delete entire filespaces. Backup and archive data for selected filespaces will be *irretrievably* erased. You will be asked for confirmation before each selected filespace is deleted.
# 15883
DSI_FSDELETE_DELETE=Delete
# 15884
DSI_FSDELETE_CANCEL=Cancel
# 15885
DSI_RESTDST_IMAGE_WARN=When restoring an image backup of the operating system drive, you must select a restore destination other than the original location.
# 15886
DSJ_SYSSTATE_RESTORE_FIRST=If you are performing a system recovery, and you have just restored the system state or system object, you must restore the system drive next. You must restart your system after restoring the system drive. \n\nIf you are NOT performing a system recovery, you must restart your system now.
# 15887
DSJ_SYSSTATE_RESTORE_SYSDRIVE=You have selected a system state or system object for restore. When performing a system recovery, you must first restore the system state or system object, and then restore the system drive in a separate restore operation. \n\nRecommendation: Turn off Windows Automatic Updates until the restore is complete and you have restarted your system. You can turn on Automatic Updates after completing your system recovery.
# 15888
DSJ_INCOMPATIBLE_OBJECTS=Restoring {0} and {1} is not allowed in the same operation.
# 15890
DSI_ARCHDEL_WINDOW_TITLE=Archive Delete
# 15891
DSI_ARCHDEL_DELETE=Delete
# 15892
DSI_POLICY_RETAIN_INIT_CREATE=Create
# 15894
DSI_POLICY_RETAIN_INIT_EVENT=Event
# 15896
DSI_ARCHDESCR_TITLE=Select Archive Description
# 15897
DSI_ARCHDESCR_CANCEL=Cancel
# 15898
DSI_POLICY_RETAIN_INIT=Retain Initiation:
# 15899
DSI_POLICY_RETAIN_MIN=Retain Minimum:
# 15900
DSI_FAILLIST_WINDOW_TITEL=List of failed files
# 15902
DSI_FAILLIST_REASON=Reason
# 15903
DSI_FAILLIST_FILENAME=Filename
# 15904
DSI_IE_REMOVE_EXCL_DIR=In order to include this directory, TSM needs to remove this Include-Exclude statement ({0}) from your options file. Since this Include-Exclude statement contains wildcard character(s), removing this statement will include any directories that match the pattern. Do you want to include this directory anyway?
# 15910
DSI_RETRIEVE_RETRIEVE=Retrieve
# 15912
DSJ_RETENTION_INIT_STATUS=Retention Initiation:
# 15913
DSJ_RETENTION_HOLD_STATUS=Held for delete?
# 15914
DSI_RETRIEVE_TITEL=Retrieve
# 15915
DSJ_ENTIRE_MEDIA=You have selected an entire media copy for restore. All objects in the media copy, including all drives, system objects, system state and system services, will be restored. If you do not want to restore the entire media copy, you can expand the media copy to view the contents within it, and select specific items to restore.\nNote: Expanding a media copy might take a long time.
# 15916
DSJ_SYSSTATE_DESELECT=You have deselected an item within a fully-selected media copy, which causes all items within the media copy to be deselected. You must re-select the items that you want to restore. This ensures that all objects selected are of the same type.
# 15917
DSI_WEB_SERVICE_INSTALL_START_MSG=Trying to install Web service...
# 15918
DSI_WEB_SERVICE_INSTALL_END_MSG=The TSM Web Client service has been successfully installed!
# 15919
DSI_WEB_SERVICE_INSTALL_ERROR_MSG=The TSM Web Client service has not been installed!
# 15920
DSI_CONN_SSL_INFO=SSL Information:
# 15921
DSJ_RETENTION_REPORT_ACTIVATED=Objects Activated:
# 15922
DSJ_RETENTION_REPORT_HELD=Objects Held:
# 15923
DSJ_RETENTION_REPORT_RELEASED=Objects Released:
# 15925
DSI_POLICY_MC_NAME=Management Class Name:
# 15926
DSI_POLICY_MC_DESCR=Description:
# 15927
DSI_POLICY_MC_COPY_GROUP=Copy Group 
# 15928
DSI_POLICY_MC_COPY_GROUP_NAME= Copy Group Name:
# 15929
DSI_POLICY_COPY_TYPE= Copy Type:
# 15930
DSI_POLICY_COPY_FREQUENCY= Copy Frequency:
# 15931
DSI_POLICY_VER_DATA_EXST= Versions Data Exists:
# 15932
DSI_POLICY_VER_DATA_DLTD= Versions Data Deleted:
# 15933
DSI_POLICY_RET_XTRA_VERS= Retain Extra Versions:
# 15934
DSI_POLICY_RET_ONLY_VERS= Retain Only Version:
# 15935
DSI_POLICY_COPY_SER= Copy Serialization:
# 15936
DSI_POLICY_COPY_MODE= Copy Mode:
# 15937
DSI_POLICY_COPY_DEST_NAME= Copy Destination:
# 15938
DSI_POLICY_RETAIN_VERS= Retain Version:
# 15939
DSI_POLICY_CMD_COPY_FREQUENCY= Copy Frequency:
# 15940
DSI_ADO_EXISTS_TITLE=Active Directory Object exists - replace?
# 15941
DSI_POLICY_INFO_GROUP_TITLE=Information for server: {0}
# 15942
DSI_POLICY_MC_NoLimit=No Limit
# 15943
DSI_POLICY_MC_Days={0} day(s)
# 15944
DSI_POLICY_MC_Versions={0} version(s)
# 15945
DSI_POLICY_SER_Static=Static
# 15946
DSI_POLICY_SER_SharedStatic=Shared Static
# 15947
DSI_POLICY_SER_SharedDymanic=Shared Dynamic
# 15948
DSI_POLICY_SER_Dynamic=Dynamic
# 15949
DSI_POLICY_MODE_Modified=Modified
# 15950
DSI_POLICY_MODE_Absolute=Absolute
# 15951
DSI_POLICY_COPY_Backup=Backup
# 15952
DSI_POLICY_COPY_Archive=Archive
# 15953
DSI_JOURNAL_UPDATE_START_MSG=Trying to update JBB service...
# 15954
DSI_JOURNAL_UPDATE_END_MSG=The TSM JBB Client service has been successfully updated!
# 15955
DSI_JOURNAL_UPDATE_ERROR_MSG=The TSM JBB Client service has not been updated!
# 15956
DSJ_RETENTION_SETEVENT_BUTTON=&Set Event
# 15957
DSI_PREFERC_NLS_BPORTUGESE=Portuguese (Brazil)
# 15958
DSI_PREFERC_NLS_KOREAN=Korean
# 15959
DSI_PREFERC_NLS_TCHINESE=Chinese (Taiwan)
# 15960
DSI_PREFERIS_PRESNAP_PREVENT=Prevent the following Presnapshot command from executing:
# 15961
DSI_PREFERIS_POSTSNAP_PREVENT=Prevent the following Postsnapshot command from executing:
# 15962
DSJ_RETENTION_INIT_UNKNOWN=Unknown
# 15963
DSJ_RETENTION_INIT_STARTED=Started
# 15964
DSJ_RETENTION_INIT_PENDING=Pending
# 15965
DSJ_RETENTION_INITIATION_COLUMN=Initiation
# 15966
DSJ_RETENTION_ACTIVATE_EVENT=Activate Retention
# 15967
DSJ_RETENTION_HOLD_EVENT=Hold
# 15968
DSJ_RETENTION_RELEASE_EVENT=Release
# 15969
DSJ_RETENTION_SEL_TYPE=Select Event type:
# 15970
DSJ_RETENTION_EVENTS_TITLE=Data Retention Events
# 15971
DSJ_RETENTION_EVENTS_MENUITEM=Set Data R&etention Events
# 15972
DSI_PREFERC_NLS_NLS=Regional Settings
# 15973
DSI_PREFERC_NLS_LANGUAGE=Language
# 15974
DSI_PREFERC_NLS_AMENG=English (United States)
# 15975
DSI_PREFERC_NLS_GERMAN=German (Germany)
# 15976
DSI_PREFERC_NLS_FRENCH=French (France)
# 15977
DSI_PREFERC_NLS_SPANISH=Spanish (Spain)
# 15978
DSI_PREFERC_NLS_ITALLIAN=Italian (Italy)
# 15979
DSJ_RETENTION_CONN_INFO=Archive Retention:
# 15980
DSI_PREFERC_NLS_JAPAN=Japanese
# 15981
DSI_PREFERC_NLS_SCHINESE=Chinese (PRC)
# 15982
DSI_PREFERC_NLS_DATE=Date Format
# 15983
DSI_PREFERC_NLS_DATE1=mm/dd/yyyy
# 15984
DSI_PREFERC_NLS_DATE2=dd-mm-yyyy
# 15985
DSI_PREFERC_NLS_DATE3=yyyy-mm-dd
# 15986
DSI_PREFERC_NLS_DATE4=dd.mm.yyyy
# 15987
DSI_PREFERC_NLS_DATE5=yyyy.mm.dd
# 15988
DSI_PREFERC_NLS_TIME=Time Format
# 15989
DSI_PREFERC_NLS_TIME1=hh:mm:ss
# 15990
DSI_PREFERC_NLS_TIME2=hh,mm,ss
# 15991
DSI_PREFERC_NLS_TIME3=hh.mm.ss
# 15992
DSI_PREFERC_NLS_TIME4=hh:mm:ss A/P
# 15993
DSI_PREFERC_NLS_NUMBER=Number Format
# 15994
DSI_PREFERC_NLS_NUMBER1=123,456.000
# 15995
DSI_PREFERC_NLS_NUMBER2=123,456,000
# 15996
DSI_PREFERC_NLS_NUMBER3=123 456,000
# 15997
DSI_PREFERC_NLS_NUMBER4=123 456.000
# 15998
DSI_PREFERC_NLS_NUMBER5=123.456,000
# 15999
DSI_PREFERC_NLS_NUMBER6=123'456,000
# 16000
DSI_DOM_ACTIVATE=Activate
# 16001
DSI_DOM_ROLLFORWARD=Rollforward
# 16002
DSI_DOM_INACTIVATE=Inactivate
# 16003
DSI_DOM_ACTIVATE_TITLE=Activate Report
# 16004
DSI_DOM_ROLLFORWARD_TITLE=Rollforward Report
# 16005
DSI_DOM_INACTIVATE_TITLE=Inactivate Report
# 16006
DSI_DOM_OBJECTS_ROLLFORWARD=Rollforward:
# 16007
DSI_DOM_ROLLFORWARD_Question=Restore completed successfully. Would you like to Rollforward the DB2 database now?
# 16008
DSI_VIEW_SELECTION=View:
# 16009
DSI_DOM_CHANGE_LABEL=Change:
# 16010
CLI_VIEWS_UPGRADE_PROMPT_LABEL=The Tivoli Storage Manager Backup Server has been upgraded from Express to Enterprise\n\nTo upgrade the client to Enterprise now, click Yes, then select the Standard client view from the Preferences Editor.\nTo upgrade at a later time, click Modify Settings from the main window and select the Standard client view.\n\nDo you want to upgrade now?\n
# 16011
DSI_CLIENT_GUI_RESTART=You must restart the Backup Archive Client GUI for your changes to take effect
# 16012
DSI_SCHWIZ_COMPLETED_MSG=Scheduler Wizard has completed successfully!
# 16013
DSI_SCHEDULER_TITLE_DESC=This wizard will guide you through the configuration process of the TSM Client Scheduler. \n\nThe client scheduler communicates with the server and performs scheduled tasks automatically. You can install more than one client scheduler.
# 16014
DSI_CFGWIZ_DEFAULT_SCHEDULER_NAME=TSM Client Scheduler
# 16015
DSI_POLICY_LANFREE_DEST= Lan Free Destination:
# 16016
DSI_POLICY_DEDUPLICATE_DATA= Deduplicate Data:
# 16017
DSI_CFGWIZ_SCHEDULER_NAME=TSM Scheduler Name
# 16018
DSI_PREFERC_NLS_DATE6=yyyy/mm/dd
# 16019
DSI_PREFERC_NLS_DATE7=dd/mm/yyyy
# 16020
DSI_PREFERC_NLS_TIME5=A/P hh:mm:ss
# 16021
DSI_TOTAL_PREDEDUP_BYTES=Total bytes before deduplication: 
# 16022
DSI_GENERIC_DEFAULT=Default
# 16023
DSI_TOTAL_POSTDEDUP_BYTES=Total bytes after deduplication: 
# 16211
DSI_CFGWIZ_COMMON_TITLE_ID=File Exclusion
# 16217
DSI_CFGWIZ_WEB_CLIENT_ACCEPTOR_UPDATE_DESC=Select the Web client service you wish to update.
# 16218
DSI_CFGWIZ_WEB_CLIENT_ACCEPTOR_REMOVE_DESC=Select the Web client service you wish to remove.
# 16219
DSI_CFGWIZ_WEB_CLIENT_ACCEPTOR_DUPLICATE_DESC=A service with the same name is already installed! \n\nPlease choose a different name for the Web client acceptor service.
# 16220
DSI_CFGWIZ_WEB_CLIENT_AUTHENTICATION_FDA_DESC=What is the TSM node name and the TSM password for this node to use?
# 16221
DSI_CFGWIZ_PASSWORD=TSM Password
# 16222
DSI_CFGWIZ_WEB_CLIENT_CONTACT_TSM_SERVER=Contact the TSM Server to validate password
# 16223
DSI_CFGWIZ_WEB_CLIENT_CONTACT_TSM_SERVER_ID=Contact TSM Server
# 16226
DSI_SCHWIZ_SCHNAME_ID=Scheduler Name
# 16227
DSI_CFGWIZ_SERVICE_LOGIN_OPTIONS_DESC=Which account should the service use when logging onto Windows?
# 16230
DSI_CFGWIZ_WEB_CLIENT_PASSWORD_ERROR=A valid password is required! \nPlease note that a valid password is required even if the validate check box is not selected, otherwise the service can be installed but cannot be started.
# 16231
DSI_CFGWIZ_CLUSTER_CHECKBOX=Help me protect my cluster
# 16232
DSI_WIZARD_CLUSTER_SUPPORT_DESC=Select this checkbox to set up Cluster Protection. You can go through the wizard more than once and configure each of the cluster groups.
# 16233
DSI_WIZARD_CLUSTER=Cluster protection
# 16234
DSI_WIZARD_CLUSTER_TASK=Cluster Protection Wizard
# 16235
DSI_WIZARD_CLUSTER_TASK_DESC=This wizard will guide you through the configuration process of the Cluster Protection.
# 16236
DSI_WIZARD_CLUSTER_NAME=Cluster name
# 16237
DSI_WIZARD_CLUSTER_SELECT_DRIVES=Select drives
# 16238
DSI_WIZARD_CLUSTER_INSTALL=Configure a new or additional cluster group
# 16239
DSI_WIZARD_CLUSTER_UPDATE=Update a previously configured cluster group
# 16240
DSI_WIZARD_CLUSTER_REMOVE=Remove a previously configured cluster group
# 16241
DSI_WIZARD_CLUSTER_INSTALL_DESC=Select this option to configure new Cluster Protection.
# 16242
DSI_WIZARD_CLUSTER_UPDATE_DESC=Select this option to re-configure one of the existing Cluster Protections.
# 16243
DSI_WIZARD_CLUSTER_REMOVE_DESC=Select this option to remove one of the existing Cluster Protection.
# 16244
DSI_WIZARD_CLUSTER_NAME_TITLE=Cluster Group Name
# 16245
DSI_WIZARD_CLUSTER_NAME_STATIC=Which cluster group would you like to set up Cluster Protection for?
# 16246
DSI_WIZARD_CLUSTER_GROUP_NAME=Cluster Group Name
# 16247
DSI_WIZARD_CLUSTER_GROUP_NAME_DESC=Select the Cluster Group Name you would like to configure
# 16250
DSI_WIZARD_CLUSTER_SELECT_DRIVES_INFO=Select drives
# 16251
DSI_PREFERC_TCPIP_SSLREQUIRED_SERVERONLY=Server only
# 16252
VSS_Volume_Not_Found=The volume '{0}' was not found on the system. Ensure that automatic mounting of volumes is enabled on the system.\n
# 16253
DSI_CLUSTERCW_END_CONFIG=Cluster configuration has ended!
# 16254
DSI_CLUSTERCW_NODE_OWNS_NO_CLUSGROUPS=Current node does NOT own any cluster groups! Please exit the configuration and make sure the node owns a cluster group and relaunch the TSM Client.
# 16255
DSI_CLUSTERCW_NO_CLUSGROUPS_AVAILABLE=There are now cluster group available for configuration!
# 16256
DSI_CLUSTERCW_NO_CLUSGROUPS_TO_CONFIG=No cluster groups available to configure. Click "next" to finish the wizard!
# 16317
DSI_STATUSBAR_LOAD_LOCALE=Loading locale settings {0} {1}
# 16326
DSI_PREFERIS_SRV_PREPOST_SNAP_PREVENT=Prevent Administrator defined Presnapshot and Postsnapshot commands from executing
# 16365
EXP_CW_Restore_Options_Label=Select Version to Restore
# 16366
EXP_CW_Restore_Options_Help=Set a filter for displaying a version of your backups. This helps you target the files you want to restore. The backup server stores data on disk for 14 days. Copies of the data can also reside on media for longer-term storage.
# 16367
EXP_CW_Restore_Recent_Files=Files most recently backed up to disk (single version of each file)
# 16368
EXP_CW_Restore_All_Versions=Files backed up to disk within the following number of days (all versions):
# 16369
EXP_CW_Restore_PIT=Files backed up to disk prior to this point in time:
# 16370
EXP_CW_Restore_Media=Files residing on media (can include older data, but takes longer to restore):
# 16371
EXP_CW_Restore_Select_Number=Select a Number:
# 16372
EXP_CW_Restore_Select_Date=Select the date when the media copy was generated:
# 16373
EXP_CW_Restore_Action_Label=Show me:
# 16374
EXP_CW_Restore_Select_FIles_Label=Select Files
# 16375
EXP_CW_Restore_Select_Image_Label=Select Image
# 16376
EXP_CW_Restore_Select_Destination_Label=Select Destination
# 16377
EXP_CW_Restore_Tree_Files_Label=Select Directories or Files to Restore
# 16378
EXP_CW_Restore_Tree_Files_Help=Click the check boxes next to the files and directories you want to restore.
# 16379
EXP_CW_Restore_Tree_Img_Label=Select Image Backups to Restore
# 16380
EXP_CW_Restore_Tree_Img_Help=Click the check box next to an image that you want to restore. The selected image will be restored, along with any file level backups taken after the image backup. This ensures that your system will be restored to the most current state. However, if you are attempting a point in time restore, only the image will be restored.
# 16381
EXP_CW_Restore_Destination_Label=Select Options for Restore
# 16382
EXP_CW_Restore_Destination_Help=Specify the destination to put your restored data.
# 16383
EXP_CW_Restore_Recent_Image=Images most recently backed up to disk (single version of each image)
# 16384
EXP_CW_Restore_All_Versions_Image=Images backed up to disk within the following number of days (all versions):
# 16385
EXP_CW_Restore_PIT_Image=Images backed up to disk prior to this point in time:
# 16386
EXP_CW_Restore_Media_Image=Images residing on media (can include older data, but takes longer to restore):
# 16387
DSJ_EXPHUB_NO_LAST_BACKUP=No previous backup has been completed for this machine.
# 16388
DSJ_ABOUT_EXPRESS_CLIENTNAME=Backup Client
# 16389
DSJ_LOGIN_TT_PASSWORD=Type your TSM password. If you do not know the password, contact the backup administrator.
# 16390
DSI_SNAPWIZ_INSTALL_VSS_MSG=Trying to install VSS client ...
# 16391
DSI_SNAPWIZ_INSTALL_LVSA_MSG=Trying to install LVSA client ...
# 16392
DSI_SNAPWIZ_UNINSTALL_LVSA_MSG=Trying to uninstall LVSA client ...
# 16393
DSI_SNAPWIZ_DISABLE_OFS_MSG=Trying to disable open file support ...
# 16394
DSI_SNAPWIZ_DISABLE_IMAGE_MSG=Trying to disable online image support ...
# 16400
DSI_WIZARD_NEXT=Next
# 16401
DSI_WIZARD_BACK=Back
# 16402
DSI_SHOW_FDA_TOOLTIP=Show 'Help on Item' area
# 16403
DSI_HIDE_FDA_TOOLTIP=Hide 'Help on Item' area
# 16404
DSI_SHOW_HELP_ONLINE_TOOLTIP=Show Help Online
# 16405
DSI_HELP_ON_ITEM=Help on Item
# 16406
DSI_HELP_ON_ITEM_FDA_DESC=Select or move the focus over the item to see its description.
# 16407
DSI_SHOW_HELP_ON_ITEM_FDA_DESC=Click on the the 'Help on Item' button in the toolbar to hide this help.
# 16408
DSI_SETUP_WIZARD_STEP=Setup Wizard
# 16409
DSI_WIZARD_CLOSE_QUESTION=Do you want to close the Configuration Wizard now?
# 16410
DSI_WAIT_TO_COMPLETE=Please wait until the operation is completed!
# 16411
DSI_PROGRESS_PREPARING=Preparing to save your configuration ...
# 16412
DSI_PROGRESS_SAVING=Saving options file ...
# 16413
DSI_OPTIONS_COMPLETE=The TSM Options File has been successfully written!
# 16414
DSI_FINISH_TO_CLOSE=Press the 'Finish' button to close this wizard.
# 16415
DSI_CLIENT_OPTIONS_FILE_STEP=Client Options File
# 16416
DSI_CLIENT_OPTIONS_FILE_TITLE=TSM Client Options File Configuration Wizard
# 16417
DSI_CLIENT_OPTIONS_FILE_DESC=This wizard will guide you through the configuration process of the initial basic TSM Client options file. \n\nAfter you have finished the initial set up of the options file you can use the Preferences Editor to specify other client options.
# 16418
DSI_OPTION_FILE_NAME_STEP=Option File Name
# 16419
DSI_SERVER_STANZA_STEP=Server Stanza
# 16420
DSI_NO_WRITE_PERMISSION=Cannot start the GUI because the configuration files are missing and the Configuration Wizard cannot create them because of no write permission on: \n{0}
# 16421
DSI_CLIENT_NODE_NAME=Client Node Name
# 16422
DSI_COMMUNICATION_OPTIONS=Communication Options
# 16423
DSI_CONFIRM_AND_APPLY_STEP=Confirm and Apply
# 16424
DSI_CONFIRM_AND_APPLY_TITLE=Confirm and Apply your configuration
# 16425
DSI_CONFIRM_AND_APPLY_DESC=You have completed the configuration of the TSM Client Options File. Click on the 'Apply' button to confirm your configuration. The initial basic TSM Client Options File will be saved to the disk.
# 16426
DSI_TAKE_TIME_TO_COMPLETE=Please note that this operation may take a while to complete.
# 16427
DSI_COMPLETING_CONFIGURATION=Completing your configuration
# 16428
DSI_NO_TSM_SERVER_CONNECTION=A connection could not be established with the IBM Tivoli Storage Manager server that was specified. \n\nThe configuration wizard is unable to contact the IBM Tivoli Storage Manager server using the information that was specified. Verify that the machine name or the IP address is specified correctly, and verify that the IBM Tivoli Storage Manager server is running on the specified port. \n\nIf the specified information is correct and you want to continue without having a IBM Tivoli Storage Manager server connection (for example, for local backupset restore purposes), click '{0}'.
# 16429
DSI_PREFERC_GEN_PIPE_DESC=Use this field to specify the name of the named pipe to use for communication between a client and a server that reside on the same workstation. 
# 16430
DSI_VALIDATE_OPTION_ERROR=Error on \n'{0}'
# 16431
DSI_VALIDATE_OPTION_WARNING=Warning on \n'{0}'
# 16432
DSI_BROWSE_BTN_DESC=Click the 'Browse' button if you want to open a directory/file selection window and select the directory/file you want to use.
# 16433
DSI_PORT_NUMBER_NOT_VALID=The number specified is not valid! \n\nThe number must be in the range between {0} and {1}
# 16434
DSI_PREFERC_TCPIP_SERVER_ADDR_DESC=Specify the name or the TCP/IP address of the machine where the Tivoli Storage Manager server is running.
# 16435
DSI_CW_PORT_NUMBER_DESC=Type the TCP/IP port number you want use to communicate with the TSM server. \n\nThe default port number is 1500, while other valid values are in the range between 1000 and 32767.
# 16436
DSI_CW_OPTION_TO_DEFAULT_VALUE=The {0} is required! \nThe value has been reset now to its default value. \n\nSpecify a new value or click on 'Next' button to continue.
# 16437
DSI_PREFERC_GEN_TCPIP_DESC=Transmission Control Protocol/Internet Protocol (TCP/IP)
# 16438
DSI_PREFERC_GEN_TCPIPv6_DESC=Transmission Control Protocol/Internet Protocol Version 6 (TCP/IP v6)
# 16439
DSI_CW_GEN_PIPE_DESC=Named Pipes is a type of interprocess communication that permits message data streams to pass between peer processes, such as between a client and a server. Use a named pipe when the client and the Tivoli Storage Manager server or Storage Agent are on the same workstation.
# 16440
DSI_PREFERC_GEN_SHMEM_DESC=Use shared memory when the client and the Tivoli Storage Manager server or Storage Agent are on the same workstation.
# 16441
DSI_CONN_FS_ACTIVEDIR_DESC=Click this option to automatically use Windows Active Directory communication information during client initialization. This bypasses communication method parameters stored locally in your options file and directly queries the directory for the communication method to use.
# 16442
DSI_STATUSBAR_CHECK_AGENT_PORT=Checking agent portnumber {0} {1}
# 16443
DSI_STATUSBAR_START_AGENT=Starting dsmagent {0} {1}
# 16444
DSI_STATUSBAR_CREATE_SESSION=Creating new session {0} {1}
# 16445
DSI_STATUSBAR_CREATE_APP_CONTROLLER=Creating application controller {0} {1}
# 16446
DSI_STATUSBAR_CREATE_FRAME=Creating frame {0} {1}
# 16447
DSI_STATUSBAR_COMPLETE=Completed! {0} {1}
# 16448
DSI_STATUSBAR_INIT_LANG=Initializing language system {0} {1}
# 16449
DSI_STATUSBAR_SET_PARAM=Setting parameters {0} {1}
# 16450
DSI_STATUSBAR_GET_HOST=Getting host address {0} {1}
# 16451
DSI_STATUSBAR_CHECK_PASSWD=Check password {0} {1}
# 16452
DSI_STATUSBAR_CHECK_CONFIG=Check for configuration files {0} {1}
# 16453
DSI_STATUSBAR_START_WIZARD=Starting Configuration Wizards dialog {0} {1}
# 16454
DSI_STATUSBAR_SHOW_GUI=Showing the GUI {0} {1}
# 16455
DSI_STATUSBAR_INIT_HELP=Initializing help system {0} {1}
# 16456
DSI_STATUSBAR_INIT_TRACE=Initializing trace system {0} {1}
# 16457
DSI_PROGRESS_CREATE_IM=Creating the interface manager ...
# 16458
DSI_PROGRESS_CONTACT_AGENT=Contacting the agent ...
# 16459
DSI_CLIENT_NODE_NAME_DESC=Which is the TSM Client Node Name to use?
# 16460
DSI_CLIENT_NODE_NAME_LENGTH_DESC=The length of the node name can be 1 to 64 characters.
# 16461
DSI_OPTION_LENGTH_NOT_VALID=The length exceed the maximum value! \n\nThe lenght of this option must be in the range between {0} and {1}
# 16462
DSI_OPTION_FILE_NAME_DESC=Type the fully-qualified name of the client options file. The client options file is usually named dsm.opt.
# 16463
DSI_OPTION_FILE_NAME_NOT_VALID=The specified location of the options file doesn't exist! \n\nPlease make sure the path is correct. Use the browse button to get a valid path or to create a new one.
# 16464
DSI_SERVER_STANZA_TITLE=TSM Server Stanza
# 16465
DSI_SERVER_STANZA_DESC=Which TSM server stanza name do you want to use?
# 16466
DSI_SERVER_STANZA=Server Stanza
# 16467
DSI_CFGWIZ_WEB_CLIENT_DUP_AGENT_FDA_DESC=A service with the same name is already installed! \n\nPlease choose a different name for the remote client agent.
# 16468
DSI_CHOOSE_WIZARD_TITLE=Welcome to the TSM Client Configuration Wizard!
# 16469
DSI_CHOOSE_WIZARD_DESC=This wizard will guide you through the configuration process of the TSM Client. Please select below the TSM components you wish configure.
# 16470
DSI_WIZARD_OPTIONS_FILE=Client Options File
# 16471
DSI_WIZARD_OPTIONS_FILE_DESC=Select this check box to create the initial basic TSM Backup Archive client options file. After you have finished the initial set up of the options file, you can use the Preferences Editor to specify other client options.
# 16472
DSI_WIZARD_WEB_CLIENT=Web Client
# 16473
DSI_WIZARD_WEB_CLIENT_DESC=Select this check box to set up the options for the TSM Web Client that allows you to remotely use TSM on your client machine via a Web browser.
# 16474
DSI_WIZARD_SCHEDULER=Client Scheduler
# 16475
DSI_WIZARD_SCHEDULER_DESC=Select this check box to set up the options for the TSM Client Scheduler. The client scheduler communicates with the server and performs scheduled tasks automatically. You can install more than one client scheduler.
# 16476
DSI_WIZARD_JOURNAL_ENGINE=Journal Engine
# 16477
DSI_WIZARD_JOURNAL_ENGINE_DESC=Select this check box to set up the options for the TSM Journal Engine. The journal engine maintains a record of changes to client data which is utilized to increase backup throughput. You can only install one journal engine per client machine.
# 16478
DSI_WIZARD_ONLINE_IMAGE=Online Image Support
# 16479
DSI_WIZARD_ONLINE_IMAGE_DESC=Select this check box to set up the Backup Archive client for online image backup operations. It allows to perform an image backup while the volume remains available to other applications.
# 16480
DSI_WIZARD_OPEN_FILE_SUPPORT=Open File Support
# 16481
DSI_WIZARD_OPEN_FILE_SUPPORT_DESC=Select this check box to configure the TSM Backup Archive client for open file support backup and archive operations. This service enables backup or archive of files that are locked by other applications.
# 16482
DSI_PROGRESS_START_AGENT=Starting dsmagent ...
# 16483
DSI_PROGRESS_CHECK_AGENT_PORT=Checking agent portnumber ...
# 16484
DSI_PROGRESS_CREATE_SESSION=Creating new session ...
# 16485
DSI_NEXT_TO_CONTINUE=Press the 'Next' button to contine.
# 16486
DSI_SELECT_TO_CONTINUE=Please select at least one option to proceed.
# 16487
DSI_CW_SERVICE_TASK_NEW=Install a new {0}
# 16488
DSI_CW_SERVICE_TASK_UPDATE=Update a previously installed {0}
# 16489
DSI_CW_SERVICE_TASK_REMOVE=Remove a previously installed {0}
# 16490
DSI_CW_TASK=Task
# 16491
DSI_CW_CHOOSE_TASK=Choose Task
# 16492
DSI_WEBWIZ_INTRO_INSTALL_DESC=Select this option to set up the TSM Web client. This program allows you to remotely access your client machine via a Web browser or via a hyperlink connection in the Administrative Web Interface.
# 16493
DSI_WEBWIZ_INTRO_UPDATE_DESC=Select this option to reconfigure the Web client.
# 16494
DSI_WEBWIZ_INTRO_REMOVE_DESC=Select this option to remove a previously installed Web Client agent.
# 16495
DSI_CW_SCHEDULER_TASK=Scheduler Task
# 16496
DSI_SCHWIZ_TASK_INSTALL_DESC=Select this option to install and configure a new client scheduler or add an additional client scheduler. You can edit other client scheduler preferences on the Scheduler tab of the Preferences window.
# 16497
DSI_SCHWIZ_TASK_UPDATE_DESC=Select this option to re-configure an existing client scheduler.
# 16498
DSI_SCHWIZ_TASK_REMOVE_DESC=Select this option to remove an existing client scheduler.
# 16499
DSI_ACCEPTOR_NAME=TSM acceptor name
# 16500
DSI_WEB_ACCEPTOR_NAME=Web service name
# 16501
DSI_CW_WEB_PORT_DESC=Type the TCP/IP port address to use to communicate with the Web client acceptor. \n\nThe default port number is 1581, while other valid values are in the range between 1000 and 32767.
# 16502
DSI_WEB_CLIENT_TITLE=TSM Web Client Configuration Wizard
# 16503
DSI_WEB_CLIENT_TITLE_DESC=This wizard will guide you through the configuration process of the TSM Web Backup Archive Client. \n\nThe Web Client program allows you to remotely access your client machine via a Web browser or via a hyperlink connection in the Administrative Web Interface. With the Web Client you can remotely back up or archive data on your client machine to the server, and restore or retrieve data from the server to your client machine.
# 16504
DSI_ACCEPTOR_NAME_DESC=The TSM client acceptor is an HTTP daemon that serves the Web client Java applet to Web browsers. The program that starts the client acceptor process is called dsmcad.exe. The TSM client acceptor is installed and run as a service. Specify the name of a new Web Client Acceptor service to install or to select an existing Client Acceptor service to configure.
# 16505
DSI_FB_POLICY_SUMMARY=FastBack policy
# 16506
DSI_FB_CLIENT_NODE_SUMMARY=FastBack Client node
# 16507
DSI_FB_VOLUMES_SUMMARY=Volumes to protect
# 16508
DSI_FB_TSM_PROTECT_SUMMARY=Protection type
# 16509
DSI_FB_SERVER_NODE_SUMMARY=FastBack Server node
# 16510
DSI_FB_TSM_MGMT_CLASS_SUMMARY=Management class
# 16511
DSI_FB_TSM_RET_DAYS_SUMMARY=Retention days
# 16512
DSI_SCHEDULE_EVERY_SUMMARY=Schedule every
# 16513
DSI_FB_START_DAYS_SUMMARY=Schedule days
# 16514
DSI_FB_PROGRESS_UPDATING_NODE=Updating TSM client node name ...
# 16515
DSI_FB_PROGRESS_SENDING_OPTIONS=Sending wizard options to the agent ...
# 16516
DSI_FB_WIZARD_COMPLETED=The TSM Client wizard has been completed successfully!
# 16517
DSI_FB_WIZARD_SCHED_INSTRUCTION=Please review and execute the {0} administrative script files to setup the TSM Central Scheduler. \nThe script files are located in the {1} directory of the FastBack server machine's system drive.
# 16518
DSI_FB_WIZARD_NO_SCRIPTS_CREATED=The TSM agent was not able to create the required scripts!
# 16519
DSI_FB_WIZARD_ERROR_NO=The following error is occurred: {0}
# 16520
DSI_WIZARD_FASTBACK_SUPPORT=FastBack
# 16521
DSI_FB_MAIN_TASK_DESCR=This wizard will guide you through options to enable long-term storage of your TSM FastBack data to a TSM Server using the TSM Backup/Archive Client. \n\nThe wizard gathers the required information from the TSM FastBack Server repository and from your input in order to create scripts required to: \n\u0020\u0020\u0020\u2022 mount TSM FastBack volumes \n\u0020\u0020\u0020\u2022 execute backups of TSM FastBack volumes \n\u0020\u0020\u0020\u2022 dismount TSM FastBack volumes \n\u0020\u0020\u0020\u2022 setup the TSM B/A Central Scheduler \n\nTSM FastBack requirements: \n\u0020\u0020\u0020\u2022 product already configured for short-term data retention \n\u0020\u0020\u0020\u2022 repository, policy and snapshot already defined \n\u0020\u0020\u0020\u2022 at leat one snapshot taken in the TSM FastBack repository \n\u0020\u0020\u0020\u2022 {0} file in the {1} \n\u0020\u0020\u0020\u0020\u0020\u0020 directory of the FastBack server machine's system drive.
# 16522
DSI_FB_VOLUME_SELECTION_TASK=Volume Selection
# 16523
DSI_FB_PROTECTION_TYPE_TASK=Protection Type
# 16524
DSI_FB_VOLUME_PROTECTION_OPT_TASK=Protection Options
# 16525
DSI_FB_SCHEDULE_OPT_TASK=Schedule Options
# 16526
DSI_FB_CONFIRM_AND_APPLY_DESCR=You have completed your configuration! \nClick the 'Apply' button to confirm your selections.
# 16527
DSI_CFGWIZ_FASTBACK_CHECKBOX=Help me configure the client to protect FastBack client data
# 16528
DSI_WIZARD_FASTBACK_SUPPORT_DESC=Select this check box to create scripts that will enable the TSM Backup/Archive Client to transfer TSM FastBack user data to a TSM Server for long-term storage.
# 16529
DSI_FB_VOLUME_SELECTION_TASK_DESC=Select a TSM FastBack policy name, client machine name, and list of volumes for long-term storage protection by the TSM Backup/Archive Client.
# 16530
DSI_FB_POLICY=TSM FastBack policy
# 16531
DSI_FB_SELECT_POLICY=-- Select a policy --
# 16532
DSI_FB_SELECT_CLIENT=-- Select a client --
# 16533
DSI_FB_CLIENT=TSM FastBack client
# 16534
DSI_FB_VOLUMES=Volumes to protect
# 16535
DSI_FB_POLICY_DESC=Use the drop-down list to select the TSM FastBack snapshot policy.\n\nTSM FastBack policies are used to link client groups to a job schedule, to specify the number of snapshots that are to be retained, and to identify the snapshot priority.
# 16536
DSI_FB_CLIENT_DESC=Use the drop-down list to select the name of the client machine that were backed up by TSM FastBack as part of the selected policy.
# 16537
DSI_FB_VOLUMES_DESC=Select one or more volumes that were backed up on the selected client and you wish to protect for a long-term data retention.
# 16538
DSI_FB_POLICY_REQUIRED=Please select a TSM FastBack policy from the drop-down list!
# 16539
DSI_FB_CLIENT_REQUIRED=Please select from the drop-down list a client machine that were backed up by TSM FastBack!
# 16540
DSI_FB_VOLUME_REQUIRED=Please select at least one volume to protect!
# 16541
DSI_FB_POLICY_LIST_EMPTY=TSM was not able to find the list of policies from the TSM FastBack repository! \n\nPlease check that the TSM FastBack is correctly configured and that user data has been already backup to the TSM FastBack repository!
# 16542
DSI_FB_SCHEDULE_OPTIONS_TASK=Schedule options
# 16543
DSI_FB_SCHEDULE_OPTIONS_TASK_DESC=Specify the options to setup the TSM Central Scheduler.
# 16544
DSI_FB_SCHEDULE_PERIOD=Schedule Period every:
# 16545
DSI_FB_SCHEDULE_START_PERIOD=Start schedule every:
# 16546
DSI_FB_SCHEDULE_PERIOD_REQUIRED=Specifies the length of time between startup windows for this schedule. \n\nYou can specify a number from 1 to 999. The default is 1.
# 16547
DSI_FB_SCHED_START_DAYS=Start Days
# 16548
DSI_FB_SCHEDULE_UNIT=Schedule Unit
# 16549
DSI_FB_SCHEDULE_UNIT_DESC=Specifies the time units used to determine the period between startup windows for this schedule. \nThe default is WEEKS.
# 16550
DSI_FB_SCHEDULE_PERIOD_DESC=Specifies the length of time between startup windows for this schedule. \n\nYou can specify a number from 1 to 999. The default is 1.
# 16551
DSI_FB_SCHEDULE_START_DAYS=Schedule Start Days
# 16552
DSI_FB_SCHEDULE_START_DAYS_DESC=Specifies the day of the week on which the schedule start.
# 16553
DSI_FB_SCHEDULE_START_HOUR=Schedule Start Hour
# 16554
DSI_FB_SCHEDULE_START_HOUR_DESC=Specifies the hour for the beginning of the schedule.
# 16555
DSI_FB_SCHEDULE_START_MINUTES=Schedule Start Minutes
# 16556
DSI_FB_SCHEDULE_START_MINUTES_DESC=Specifies the minutes for the beginning of the schedule.
# 16557
DSI_FB_PROTECT_TYPE_TASK=Protection Type
# 16558
DSI_FB_PROTECT_TYPE_TASK_DESC=How do you want to protect the selected volumes taken from the TSM FastBack repository?
# 16559
DSI_FB_PROTECT_INCREMENTAL_DESC=Chose this protection type to backup only the changes to the TSM FastBack selected volumes since the last time it was backed up by the TSM Backup/Archive Scheduler.
# 16560
DSI_FB_PROTECT_ARCHIVE_DESC=Choose this protection type if you want to create a new full archive of the selected volumes.
# 16561
DSI_FB_PROTECT_OPTIONS_TASK=Protection Options
# 16562
DSI_FB_PROTECT_OPTIONS_TASK_DESC=What is the TSM node name that will be used to store data on the TSM Server on behalf of the TSM FastBack server?
# 16563
DSI_FB_SERVER_NODE_NAME_DESC=Type the name of the node that will be used to identify your TSM FastBack server node on the TSM server. \n\nIt is suggested to input the name of your TSM FastBack server. This is normally the machine name and also the default value.
# 16564
DSI_FB_TSM_SCRIPT_PATH=Script Path
# 16565
DSI_FB_TSM_SCHED_START=Schedule Start
# 16567
DSI_FB_TSM_SCHED_START_DESC=Would you like to start the TSM Scheduler upon completion of this wizard?
# 16568
DSI_FB_TSM_ADMIN_ID=TSM Administrative User ID
# 16569
DSI_FB_TSM_ADMIN_PWD=TSM Administrative Password
# 16570
DSI_FB_TSM_SCHED_START_YES_DESC=Select 'Yes' if you want to setup the TSM Central Scheduler, register the client nodes and create the proxy relationship upon completion of this wizard.
# 16571
DSI_FB_TSM_SCHED_START_NO_DESC=Select 'No' if you want to manually setup the TSM Central Scheduler, register the client nodes and create the proxy relationship later by running the '{1}' scripts located in the '{0}' directory of your agent machine upon completion of this wizard.
# 16572
DSI_FB_TSM_ADMIN_ID_SHORT=User ID
# 16573
DSI_FB_TSM_ADMIN_PWD_SHORT=Password
# 16574
DSI_FB_TSM_ADMIN_ID_DESC=Type the TSM Administrative user ID that is required in order to define the TSM Schedule.
# 16575
DSI_FB_TSM_ADMIN_PWD_DESC=Type the TSM Administrative Password that is required in order to define the TSM Schedule.
# 16576
DSI_FB_TSM_ADMIN_ID_REQUIRED=Please type the TSM Administrative user ID that is required in order to define the TSM Schedule. \n\nIf you don't know the TSM Administrative User ID, you can proceed by clicking on 'No' and upon completion of this wizard executing the {0} administrative script files to setup the TSM Central Scheduler.
# 16577
DSI_FB_TSM_ADMIN_PWD_REQUIRED=Please type the TSM Administrative password that is required in order to define the TSM Schedule. \n\nIf you don't know the TSM Administrative password, you can proceed by clicking on 'No' and upon completion of this wizard executing the {0} administrative script files to setup the TSM Central Scheduler.
# 16578
DSI_FB_TSM_POLICY_DOMAIN_SUMMARY=Policy Domain
# 16579
DSI_FB_SCHEDULE_EVERY=Schedule every:
# 16580
DSI_FB_SERVER_NODE_NAME=Node name for TSM FastBack server
# 16581
DSI_FB_SELECT_REP_NAME=-- Select Repository Name --
# 16582
DSI_FB_SELECT_REP_LOC=-- Select Repository Location --
# 16583
DSI_FB_CHOOSE_REPOSITORY=Choose FastBack Repository
# 16584
DSI_FB_CHOOSE_REPOSITORY_DESC=Which is the repository containing the TSM FastBack volumes to protect?
# 16585
DSI_FB_REPOSITORY_LOCATION=Repository Location
# 16586
DSI_FB_REPOSITORY_LOCATION_DESC=Please select the location of the repository that contains the volumes to protect.
# 16587
DSI_FB_REPOSITORY_LOCATION_REQ=Please select a TSM FastBack repository location from the drop-down list!
# 16588
DSI_FB_REPOSITORY_NAME=Repository Name
# 16589
DSI_FB_REPOSITORY_NAME_DESC=Please select the name of the repository that contains the volumes to protect.
# 16590
DSI_FB_REPOSITORY_NAME_REQ=Please select a TSM FastBack repository name from the drop-down list!
# 16591
DSI_CLIENT_NODE_REG_TITLE=TSM Client Node Registration
# 16592
DSI_CLIENT_NODE_REG_TITLE_DESC=Which password do you want to use to register the TSM Client node with the Tivoli Storage Manager server?
# 16593
DSI_PASSWORD_DESC=Specifies the password of the node to be registered. The maximum length of the password is 64 characters. The password is not case-sensitive and can contain any alphanumeric character, underscore (_), period (.), hyphen (-), plus (+), or ampersand (&).
# 16594
DSI_CONFIRM_PASSWORD_DESC=Type the password for the client node again.
# 16595
DSI_CLIENT_NODE=TSM Client Node
# 16596
DSI_OPENREG_CONTACT_DESC=Specifies information to identify the node being registered. This information is optional. The maximum length of the contact information is 255 characters.
# 16597
DSI_PASSWORD_REQUIRED=The password is required! \nPlease type a non empty password.
# 16598
DSI_PASSWORD_MAX_LENGTH=The maximum length of the password is 64 characters!
# 16599
DSI_CONFIRM_PASSWORD_REQUIRED=The confirm password is required! \nPlease type the password again.
# 16600
DSI_CONFIRM_PASSWORD_INVALID=The password entries are not the same.
# 16601
DSI_OPENREG_CONTACT_MAX_LENGTH=The maximum length of the contact information is 255 characters!
# 16602
DSI_FB_CLIENT_NODE_REG_TITLE=Register FastBack Client as Client Node
# 16603
DSI_FB_CLIENT_NODE_REG_DESC=Which password do you want to use to register the TSM FastBack Client as a client node with the Tivoli Storage Manager server?
# 16604
DSI_FB_CLIENT_NODE_CONTACT=TSM Client Node for FastBack Client
# 16605
DSI_FB_SERVER_NODE_REG_TITLE=Register FastBack Server as Client Node
# 16606
DSI_FB_SERVER_NODE_REG_DESC=Which password do you want to use to register the TSM FastBack Server as a client node with the Tivoli Storage Manager server?
# 16607
DSI_FB_SERVER_NODE_CONTACT=TSM Client Node for FastBack Server
# 16608
DSI_FB_REPOSITORY_SELECTION_TASK=Repository Selection
# 16609
DSI_FB_CLIENT_REGISTRATION_TASK=Client Registration
# 16610
DSI_FB_SERVER_REGISTRATION_TASK=Server Registration
# 16611
DSI_FB_BACK_TO_PROTECT_FURTHER_DATA=Press the 'Back' button if you want to protect further FastBack client data.
# 16612
DSI_FB_REPOSITORY_LIST_EMPTY=TSM was not able to detect the list of repositories from the TSM FastBack DR Server! \n\nPlease check that the TSM FastBack Server is correctly configured! 
# 16613
DSI_DPREFVM_VMBACKUP_HYPERVFULL_IMAGE_LABEL=Hyper-V Full VM
# 16614
DSI_DPREFVM_VMBACKUP_HYPERVFULL_IMAGE_FDA_DESC=Select the virtual machine to backup when you issue the backup VM command on the Hyper-V machine.
# 17017
DSI_JOURNAL_REMOVE_START_MSG=Trying to remove JBB service...
# 17018
DSI_JOURNAL_REMOVE_END_MSG=The TSM JBB Client service has been successfully removed!
# 17019
DSI_JOURNAL_REMOVE_ERROR_MSG=The TSM JBB Client service has not been removed!
# 17027
DSI_IMAGE_CONFIRM_AND_APPLY_DESC=You have completed the configuration of the TSM Online Image Support. Click on the 'Apply' button to confirm your configuration.
# 17029
DSI_OPEN_FILE_CONFIRM_AND_APPLY_DESC=You have completed the configuration of the TSM Open File Support. Click on the 'Apply' button to confirm your configuration.
# 17037
DSI_AUTHENTICATION=Authentication
# 17038
DSI_LOGIN_OPTIONS=Login Options
# 17039
DSI_SELECT_WEB_SERVICE=Select Web Service
# 17053
DSI_SCHEDULER_INSTALL_END_MSG=Scheduler was installed successfully!
# 17054
DSI_SCHEDULER_UPDATE_END_MSG=Scheduler was updated successfully!
# 17055
DSI_SCHEDULER_REMOVE_END_MSG=Scheduler was removed successfully!
# 17063
DSI_JOURNAL_CONFIRM_AND_APPLY_DESC=You have completed the configuration of the TSM Journal Engine. Click on the 'Apply' button to confirm your configuration.
# 17152
DSI_WEB_SERVICE_UPDATE_START_MSG=Trying to update Web service...
# 17153
DSI_WEB_SERVICE_UPDATE_END_MSG=The TSM Web Client service has been successfully updated!
# 17154
DSI_WEB_SERVICE_UPDATE_ERROR_MSG=The TSM Web Client service has not been updated!
# 17155
DSI_WEB_SERVICE_REMOVE_START_MSG=Trying to remove Web service...
# 17156
DSI_WEB_SERVICE_REMOVE_END_MSG=The TSM Web Client service has been successfully removed!
# 17157
DSI_WEB_SERVICE_REMOVE_ERROR_MSG=The TSM Web Client service has not been removed!
# 17161
DSI_SCHWIZ_USE_CAD_ID=Use CAD
# 17162
DSI_GENERIC_UNKNOWN=Unknown
# 17163
DSI_GENERIC_NONE=None
# 17164
DSI_CFGWIZ_CONFIRM_PASSWORD=Confirm Password
# 17165
DSI_SCHEDULER_UPDATE_START_MSG=Trying to update Scheduler client ...
# 17166
DSI_SCHEDULER_REMOVE_START_MSG=Trying to remove Scheduler client ...
# 17167
DSI_CFGWIZ_ACCOUNT_NAME=Account Name
# 17171
DSI_CFGWIZ_START_OPTION_MANUALLY_ID=Start Manually
# 17172
DSI_SCHEDULER_INSTALL_START_MSG=Trying to install Scheduler client ...
# 17173
DSI_CFGWIZ_START_OPTION_AUTOMATICALLY_ID=Start when boot
# 17174
CW_NO_ELEMENTS_SELECTED=The {0} is required to have at least one element selected \n\nSelect at least one element in the list and click on 'Next' button to continue.
# 17175
DSI_CFGWIZ_WEB_AGENT_NAME=TSM Remote Client Agent
# 17176
DSI_SCHWIZ_REMOTE_COPY_FILES=Do you wish to copy the install files from this machine to the remote machine?
# 17178
DSI_CFGWIZ_WEB_SERVICE_NAME_ID=TSM Agent Name
# 17180
DSI_CFGWIZ_WEB_CLIENT_PARAMETERS=Web Client Parameters
# 17181
DSI_SCHWIZ_REMOTE_PATH_ID=Install Directory
# 17184
DSI_CFGWIZ_START_OPTION=Start Option
# 17188
DSI_CFGWIZ_WEB_AGENT_NAME_ID=Agent Name
# 17189
DSI_CFGWIZ_WEB_CLIENT_PARAMETERS_ID=Remote Access
# 17190
DSI_CFGWIZ_CONFIRM_WEB_CLIENT=You have completed the configurations of the TSM Web Client. Click on the 'Apply' button to confirm your configuration.
# 18001
DSI_VM_MGMT_CLASS_FDA_DESC=VM Management Class Description
# 18002
DSI_DPREFVM_VMBACKUP_VMCTLMC_LABEL=VM Management Class for Control Information
# 18003
DSI_DPREFVM_VMBACKUP_VMCTLMC_LABEL_FDA_DESC=VM Management Class for Control Information Description
# 18004
DSI_DPREFVM_VMBACKUP_VMVSTORTRANSPORT_LABEL=VMware Transport
# 18005
DSI_DPREFVM_VMBACKUP_VMVSTORTRANSPORT_LABEL_FDA_DESC=VMware Transport Description
# 18006
DSI_DPREFVM_VMBACKUP_VMVSTORTRANSPORT_SAN_LABEL=SAN
# 18007
DSI_DPREFVM_VMBACKUP_VMVSTORTRANSPORT_HOTADD_LABEL=HOTADD
# 18008
DSI_DPREFVM_VMBACKUP_VMVSTORTRANSPORT_NBDSSL_LABEL=NBDSSL
# 18009
DSI_DPREFVM_VMBACKUP_VMVSTORTRANSPORT_NBD_LABEL=NBD
# 18010
DSI_DPREFVM_VMBACKUP_VMSKIPRDM_LABEL=Back up virtual machines and skip all raw device mapping (RDM) disks that use physical compatibility mode
# 18011
DSI_DPREFVM_VMBACKUP_VMSKIPRDM_LABEL_FDA_DESC=Backup virtual machines provisioned with disks that do not support snapshots. Since these types of disks do not support snapshots, the disks will be skipped during the backup operation; only disks that support snapshots will be processed.
# 18012
DSI_DPREFVM_VMBACKUP_VMSKIPINDEPENDENT_LABEL=Back up virtual machines and skip all independent disks
# 18013
DSI_DPREFVM_VMBACKUP_VMSKIPINDEPENDENT_LABEL_FDA_DESC=Backup virtual machines provisioned with disks that do not support snapshots. Since these types of disks do not support snapshots, the disks will be skipped during the backup operation; only disks that support snapshots will be processed.
# 18014
DSI_CLUSTERCW_ERROR_CONFIG=Error, the Cluster Generic Service and/or Cluster Resource could not be created!
# 18015
DSI_CLUSTERCW_CLUSTER_NODE_DOWN=Node ({0}) is currently unavailable... \n\nPlease make sure all nodes are up and running in this cluster environment and re-launch the Cluster Configuration Wizard to configure one or more cluster groups for protection.
# 18016
DSI_CLUSTERCW_ERROR_REMOVE=Error, the cluster configuration could not be removed! The associated generic service/resource could not be found.
# 18017
DSI_CLUSTERCW_AVAIL_STORAGE=Available Storage
# 18018
DSI_CLUSTERCW_REMOTE_REGISTRY_CONN=Error, could not connect to remote registry. Please make sure all nodes are up and running in this cluster environment.
# 18028
DSI_DPREFVM_VMBACKUP_VMENABLETEMPLATES_LABEL=Back up virtual machines templates
# 18051
DSI_PercentDisplay= {0}% \n 
# 18052
SNAPSHOT_Label4SnapDiffProgressDisplay=Determine snapshot difference \n
# 18053
SNAPSHOT_SnapDiffSettingConflict=You cannot perform an incremental by snapshot difference backup on a selection that is not a whole network volume. \n
# 18054
SNAPSHOT_SnapDiffTreeSelectionConflict=Snapshot difference has been chosen. Only whole network volumes can be selected. \n
# 18055
DSI_NumObjectsDisplay= {0} objects \n 
# 18502
DSI_INFO_NOT_AVAIL=Information Not Available
# 18512
DSI_SM_MACHINE_NAME_ID=Machine
# 18513
DSI_SM_MACHINE_NAME=Machine Name or IP Address
# 18514
DSI_SM_MACHINE_NAME_FDA_DESC=Type the name or the IP address of the workstation that you want to logon to. Space Management must be installed and the Space Management agent must be running on this machine.
# 18515
DSI_SM_CLIENT_NODE_NAME_ID=Client Node
# 18516
DSI_SM_CLIENT_NODE_NAME=TSM Client Node Name
# 18517
DSI_SM_CLIENT_NODE_NAME_FDA_DESC=Type the name of the TSM Client node. The TSM Client Node must be already registered and authenticated with the TSM Server.
# 18518
DSI_SM_PORT_ID=Port
# 18519
DSI_SM_PORT_NUMBER=Port Number 
# 18520
DSI_SM_PORT_NUMBER_FDA_DESC=Type the TCP/IP port number that you want use to communicate with the machine on which the Space Management agent is running.
# 18521
DSI_SM_PASSWORD_FDA_DESC=Type the password of TSM Client Node. The TSM Client Node must be already registered and authenticated with the TSM Server.
# 18522
DSI_SM_SAVE_PASSWORD=Save password locally
# 18523
DSI_SM_SAVE_PASSWORD_FDA_DESC=Check this box to save the password locally on your machine. \n\nNOTE: You need to be authenticated at minimum with one TSM Client Node in order to retrieve the password.
# 18524
DSI_SM_SSL_ID=SSL
# 18525
DSI_SM_SSL=Use SSL (Secure Socket Layer)
# 18526
DSI_SM_SSL_DESC=Check this box to use the HTTPS secure socket layer (SSL) interface to communicate with the machine on which the Space Management agent is running.
# 18527
DSI_SM_STATUS=Status
# 18528
DSI_SM_OPTIONS_BUTTON_FDA_DESC=Click this button to show more logon options.
# 18529
DSI_SM_SIGN_ON=&Sign On
# 18530
DSI_SM_SIGN_ON_TOOLTIP=Sign On to the selected Client Node
# 18531
DSI_SM_SIGN_OFF=Sign &Off
# 18532
DSI_SM_SIGN_OFF_TOOLTIP=Sign Off from the selected Client Node
# 18533
DSI_SM_CLOSE_DIALOG_TITLE=Closing Enterprise Space Management Console
# 18534
DSI_SM_CLOSE_DIALOG_TEXT=Do you want to close Enterprise Space Management Console now?
# 18535
DSI_SM_PREFER_OK_FDA_DESC=Click OK to logon to the specified TSM Client Node.
# 18536
DSI_SM_PREFER_CANCEL_FDA_DESC=Click Cancel to close this window.
# 18538
DSI_SM_WARNING_NODE_UPDATE_TITLE=Client Node update confirmation
# 18539
DSI_SM_STATUS_BAR_FS_LOADING=Loading File System information of '{0}' ...
# 18540
DSI_SM_STATUS_BAR_FS_LOADED=File System information of '{0}' loaded.
# 18541
DSI_SM_STATUS_BAR_LOCAL_SETTINGS_LOADING=Loading customized settings...
# 18542
DSI_SM_STATUS_BAR_LOCAL_SETTINGS_LOADED=Customized settings has been loaded
# 18543
DSI_SM_STATUS_BAR_LOCAL_SETTINGS_NOT_FOUND=Customized settings has not been found.
# 18544
DSI_SM_STATUS_BAR_LOCAL_SETTINGS_SAVING=Saving customized settings...
# 18545
DSI_SM_STATUS_BAR_LOCAL_SETTINGS_SAVED=Customized settings has been saved
# 18546
DSI_SM_ERROR_LOCAL_SETTINGS_NOT_SAVED=Customized settings has not been saved.
# 18547
DSI_SM_NODE_NOT_CONNECTED=Not connected
# 18548
DSI_SM_NODE_AUTHENTICATED=Authenticated
# 18549
DSI_SM_NOT_DEFINED=Not defined
# 18550
DSI_SM_FS_NAME=File System
# 18551
DSI_SM_FS_TYPE=Type
# 18552
DSI_CLUSTER_NODENAME_NOT_VALID=In a cluster environment NODENAME can not be the same as computer name
# 18553
DSI_SM_FS_STATE=State
# 18554
DSI_SM_FS_SIZE=Size
# 18555
DSI_SM_FS_FREE_SPACE=Free
# 18556
DSI_SM_FS_UTILIZATION=Utilization
# 18557
DSI_SM_FS_RESIDENT_DATA=Resident
# 18558
DSI_SM_FS_RESIDENT_FILES=Resident Files
# 18559
DSI_SM_FS_FREE_INODES=Free Inodes
# 18560
DSI_SM_MFS_SERVER_NAME=Server Name
# 18561
DSI_SM_MFS_MIGRATED_DATA=Migrated
# 18562
DSI_SM_MFS_MIGRATED_FILES=Migrated Files
# 18563
DSI_SM_MFS_PREMIGRATED_DATA=Premigrated Data
# 18564
DSI_SM_MFS_PREMIGRATED_FILES=Premigrated Files
# 18565
DSI_SM_MFS_PREMIGRATED_PERCENTUAL=Premigrated
# 18566
DSI_SM_MFS_LOW_THRESHOLD=Low Threshold
# 18567
DSI_SM_MFS_HIGH_THRESHOLD=High Threshold
# 18568
DSI_SM_MFS_QUOTA=Quota
# 18569
DSI_SM_MFS_STUB_SIZE=Stub Size (bytes)
# 18570
DSI_SM_MFS_MAX_CANDIDATES=Max Candidates
# 18573
DSI_SM_FS_NOT_MANAGEABLE=Not Manageable
# 18574
DSI_SM_FS_NOT_MANAGED=Not Managed
# 18575
DSI_SM_FS_DEACTIVATED=Deactivated
# 18576
DSI_SM_FS_ACTIVE=Active
# 18577
DSI_SM_FS_PROPERTIES=File System &Properties...
# 18578
DSI_SM_FS_PROPERTIES_TOOLTIP=Edit the properties of the selected File System
# 18579
DSI_SM_FS_AUTO_MIGRATE=Threshold M&igration
# 18580
DSI_SM_FS_AUTO_MIGRATE_TOOLTIP=Start Threshold Migration on the selected File System
# 18581
DSI_SM_FS_DEACTIVATE=Deact&ivate
# 18582
DSI_SM_FS_DEACTIVATE_TOOLTIP=Deactivate selected File System 
# 18583
DSI_SM_FS_REACTIVATE=Rea&ctivate
# 18584
DSI_SM_FS_REACTIVATE_TOOLTIP=Reactivate selected File System 
# 18585
DSI_SM_NODE_GLOBAL_DEACTIVATE=&Global Deactivate
# 18586
DSI_SM_NODE_GLOBAL_DEACTIVATE_TOOLTIP=Deactivate all managed File Systems on the selected Client Node
# 18587
DSI_SM_NODE_GLOBAL_REACTIVATE=&Global Reactivate
# 18588
DSI_SM_NODE_GLOBAL_REACTIVATE_TOOLTIP=Reactivate all managed File Systems on the selected Client Node
# 18589
DSI_SM_NODE_SPACE_USAGE=Space &Usage
# 18590
DSI_SM_SPACE_USAGE_CHART_TITLE=Space Utilization of '{0}'
# 18591
DSI_SM_NODE_SPACE_USAGE_TOOLTIP=Display graphical view of Space Utilization of the selected Client Node
# 18592
DSI_SM_NODE_PROPERTIES=Client &Node Properties...
# 18593
DSI_SM_NODE_PROPERTIES_TOOLTIP=Display the properties of the selected Client Node
# 18594
DSI_SM_NODE_ADD=A&dd
# 18595
DSI_SM_NODE_EDIT=Edi&t
# 18596
DSI_SM_NODE_REMOVE=&Remove
# 18597
DSI_SM_FILE_MENU=&File
# 18598
DSI_SM_EDIT_MENU=&Edit
# 18599
DSI_SM_VIEW_MENU=&View
# 18600
DSI_SM_ACTIONS_MENU=&Actions
# 18601
DSI_SM_WINDOW_MENU=&Window
# 18602
DSI_SM_HELP_MENU=&Help
# 18603
DSI_SM_EXIT_MENU=E&xit
# 18604
DSI_SM_SAVE_SETTINGS_MENU=&Save Settings
# 18605
DSI_SM_SAVE_SETTINGS_ON_EXIT_MENU=Save Se&ttings on Exit
# 18606
DSI_SM_IMPORT_SETTINGS_MENU=&Import Settings...
# 18607
DSI_SM_BANNER_AREA=&Banner Area
# 18608
DSI_SM_TOOLBAR=&Toolbar
# 18609
DSI_SM_REMEMBER_VIEW_SETTINGS=Re&member View Settings
# 18610
DSI_SM_RESET_VIEW_SETTINGS=Reset View Settin&gs
# 18611
DSI_SM_ABOUT_SPACE_MANAGEMENT_CONSOLE=&About Space Management...
# 18612
DSI_SM_HELP_TOPICS=Help &Topics
# 18613
DSI_SM_FS_STATE_UNKNOWN=Unknown
# 18614
DSI_SM_FS_NOT_DETERMINED=Not Determined
# 18615
DSI_SM_MY_TASKS=My Tasks
# 18616
DSI_SM_MANAGE_RESOURCES=&Manage Resources
# 18617
DSI_SM_WELCOME=Wel&come
# 18618
DSI_SM_FRAME_TITLE=IBM Tivoli Enterprise Space Management Console
# 18619
DSI_SM_BANNER_TEXT=TSM for Space Management
# 18620
DSI_SM_FS_MANAGE=&Manage
# 18621
DSI_SM_FS_MANAGE_TOOLTIP=Add Space Management
# 18622
DSI_SM_FS_UNMANAGE=&Unmanage
# 18623
DSI_SM_FS_UNMANAGE_TOOLTIP=Remove Space Management from the selected file system
# 18624
DSI_SM_FILE_SYSTEM_MENU=File S&ystem
# 18625
DSI_SM_CLIENT_NODE_MENU=&Client Node
# 18626
DSI_SM_CONTENTS_OF=Contents of '{0}'
# 18627
DSI_SM_CLIENT_NODES=Client Nodes
# 18628
DSI_PREFER_VIEW=View Details
# 18629
DSI_NODE_OPTS=Client Node Properties
# 18630
DSI_GENERAL_OPTS_CLIENT=Client Options
# 18631
DSI_GENERAL_OPTS_NLSDATADIR=NLS Data Storage Name
# 18632
DSI_GENERAL_OPTS_NLSDATADIR_FDA_DESC=Displays the path and filename of the TSM message file.
# 18633
DSI_GENERAL_OPTS_DIRFORTSM=Directory for TSM files
# 18634
DSI_GENERAL_OPTS_DIRFORTSM_FDA_DESC=Displays the directory path in which the TSM program files are installed.
# 18635
DSI_GENERAL_OPTS_ERRORPROG=Error Program Name
# 18636
DSI_GENERAL_OPTS_ERRORPROG_FDA_DESC=Displays the program to which TSM sends a message if a severe error occurs during Space Management processing.
# 18637
DSI_GENERAL_OPTS_MSGMODE=Message Mode
# 18638
DSI_GENERAL_OPTS_MSGMODE_FDA_DESC=Displays whether messages are displayed on the screen during TSM processing.
# 18639
DSI_GENERAL_OPTS_MSGMODE_QUIET=Quiet Mode
# 18640
DSI_GENERAL_OPTS_MSGMODE_QUIET_FDA_DESC=Messages are not displayed on screen.
# 18641
DSI_GENERAL_OPTS_MSGMODE_VERBOSE=Verbose Mode
# 18642
DSI_GENERAL_OPTS_MSGMODE_VERBOSE_FDA_DESC=Messages are displayed on screen.
# 18643
DSI_SERVER_OPTS=Server
# 18644
DSI_SERVER_OPTS_PREF=Server Options
# 18645
DSI_SERVER_OPTS_FDA_DESC=Use Server Options to view information on how your client node communicates with the TSM Server.
# 18646
DSI_SERVER_OPTS_TYPE=Server Type
# 18647
DSI_SERVER_OPTS_TYPE_FDA_DESC=Displays the type of operating system of the server to which your client node is connected.
# 18648
DSI_SERVER_OPTS_VERSION=Server Version.Release.Level
# 18649
DSI_SERVER_OPTS_VERSION_FDA_DESC=Displays the version of the TSM Server to which your client node is connected.
# 18650
DSI_SERVER_OPTS_LASTACCESSDATE=Last Access Date
# 18651
DSI_SERVER_OPTS_LASTACCESSDATE_FDA_DESC=Displays the date and time you last accessed the TSM Server.
# 18652
DSI_SERVER_OPTS_DELBACKFILES=Delete Backup Files
# 18653
DSI_SERVER_OPTS_DELBACKFILES_FDA_DESC=Displays whether your client node has the authority to delete data backed up using the TSM Backup-Archive Client.
# 18654
DSI_SERVER_OPTS_DELARCHFILES=Delete Archive Files
# 18655
DSI_SERVER_OPTS_DELARCHFILES_FDA_DESC=Displays whether your client node has the authority to delete data archived using the TSM Backup-Archive Client.
# 18656
DSI_POLICY_OPTS=Policy
# 18657
DSI_POLICY_OPTS_PREF=Policy Information
# 18658
DSI_POLICY_OPTS_FDA_DESC=Use Policy Information to display policy information defined for your client node.
# 18659
DSI_POLICY_OPTS_ACTIVESET=Active Policy Set
# 18660
DSI_POLICY_OPTS_ACTIVESET_FDA_DESC=Displays the policy set that is active for your policy domain. A policy set contains a group of one or more management classes.
# 18661
DSI_POLICY_OPTS_DEFMGMTCLASS=Default Management Class
# 18662
DSI_POLICY_OPTS_DEFMGMTCLASS_FDA_DESC=Displays the default management class for your active policy set. A management class contains attributes that determine how backup and archive data on the server is managed.
# 18663
DSI_POLICY_OPTS_DOMAIN=Policy Domain
# 18664
DSI_POLICY_OPTS_DOMAIN_FDA_DESC=Displays the policy domain to which your client node belongs. A policy domain contains a group of one or more policy sets.
# 18665
DSI_POLICY_OPTS_ACTIVATIONDATE=Activation Date
# 18666
DSI_POLICY_OPTS_ACTIVATIONDATE_FDA_DESC=Displays the date on which your active policy set became active.
# 18667
DSI_POLICY_OPTS_MCLIST=Management Classes
# 18668
DSI_POLICY_OPTS_MCLIST_FDA_DESC=Displays a list of management classes for which you can view details.
# 18669
DSI_POLICY_OPTS_MCPREF=Management Class Details
# 18670
DSI_POLICY_OPTS_MCPREF_FDA_DESC=Use Management Class Details to display the policy information for the selected management class.
# 18671
DSI_POLICY_OPTS_MCNAME=Management Class Name
# 18672
DSI_POLICY_OPTS_MCNAME_FDA_DESC=Displays the name of the management class.
# 18673
DSI_POLICY_OPTS_MCDESC=Description
# 18674
DSI_POLICY_OPTS_MCDESC_FDA_DESC=Displays a description of the management class.
# 18675
DSI_POLICY_OPTS_MCSMTECH=Space Management Technique
# 18676
DSI_POLICY_OPTS_MCSMTECH_FDA_DESC=Displays the type of migration that will be used to migrate files to the server.
# 18677
DSI_POLICY_OPTS_MCAUTOMIG=Auto Migrate on Non-usage
# 18678
DSI_POLICY_OPTS_MCAUTOMIG_FDA_DESC=Displays the number of days that must elapse since the file was last accessed before it is eligible for automatic migration.
# 18679
DSI_POLICY_OPTS_MCMIGREQBACK=Backup Required Before Migration
# 18680
DSI_POLICY_OPTS_MCMIGREQBACK_FDA_DESC=Displays whether a current backup version of a file must exist on the server before the file can be migrated.
# 18681
DSI_POLICY_OPTS_MCDESTINATION=Destination for Migrated Files
# 18682
DSI_POLICY_OPTS_MCDESTINATION_FDA_DESC=Displays the name of the storage pool on the server in which migrated files are stored.
# 18683
DSI_POLICY_OPTS_COPY_TYPE=Copy Group Type
# 18684
DSI_POLICY_OPTS_COPY_TYPE_FDA_DESC=Displays the type of a copy group used by the TSM Backup-Archive Client.
# 18685
DSI_POLICY_OPTS_COPY_TYPE_SELECT=Select a Copy Group Type
# 18686
DSI_POLICY_OPTS_COPY_TYPE_NONE=No Copy Group is defined
# 18687
DSI_POLICY_OPTS_COPY_BACK=Backup Copy Group Details
# 18688
DSI_POLICY_OPTS_COPY_BACK_FDA_DESC=The Backup Copy Group Details window displays the attributes for the backup copy group in a management class.
# 18689
DSI_POLICY_OPTS_COPY_NAME=Copy Group Name
# 18690
DSI_POLICY_OPTS_COPY_NAME_FDA_DESC=Displays the name of a copy group in a management class.
# 18691
DSI_POLICY_OPTS_COPY_FREQ=Copy Frequency
# 18692
DSI_POLICY_OPTS_COPY_FREQ_FDA_DESC=Displays the number of days that must elapse between successive backup or archive operations using the TSM Backup-Archive Client.
# 18693
DSI_POLICY_OPTS_COPY_VEREXISTS=Versions Data Exists
# 18694
DSI_POLICY_OPTS_COPY_VEREXISTS_FDA_DESC=Displays the maximum number of different backup versions that are retained on the server.
# 18695
DSI_POLICY_OPTS_COPY_VERDELETED=Versions Data Deleted
# 18696
DSI_POLICY_OPTS_COPY_VERDELETED_FDA_DESC=Displays the maximum number of different backup versions of files and directories that were deleted from your file system that are retained on the server. 
# 18697
DSI_POLICY_OPTS_COPY_RETEXTRA=Retain Extra Versions
# 18698
DSI_POLICY_OPTS_COPY_RETEXTRA_FDA_DESC=Displays the number of days for which all but the most recent backup version are retained on the server. The most recent version is the active version, and active versions are never deleted.
# 18699
DSI_POLICY_OPTS_COPY_RETONLY=Retain Only Versions
# 18700
DSI_POLICY_OPTS_COPY_RETONLY_FDA_DESC=Displays the number of days for which the last remaining inactive version of a file or directory is retained on the server.
# 18701
DSI_POLICY_OPTS_COPY_RETVER=Retain Version
# 18702
DSI_POLICY_OPTS_COPY_RETVER_FDA_DESC=Displays the number of days for which an archive file, archived using the TSM Backup-Archive Client, remains on the server.
# 18703
DSI_POLICY_OPTS_COPY_SERIAL=Copy Serialization
# 18704
DSI_POLICY_OPTS_COPY_SERIAL_FDA_DESC=Specifies whether a file can be in use during a backup or archive process using the TSM Backup-Archive Client, and what to do if the file is in use.
# 18705
DSI_POLICY_OPTS_COPY_DEST=Copy Destination
# 18706
DSI_POLICY_OPTS_COPY_DEST_FDA_DESC=Displays the destination where backup versions and archive copies, backed up or archived using the TSM Backup-Archive Client, reside on the server.
# 18707
DSI_POLICY_OPTS_COPY_MODE=Copy Mode
# 18708
DSI_POLICY_OPTS_COPY_MODE_FDA_DESC=Displays the value of the Mode attribute for the backup copy group or the archive copy group.
# 18709
DSI_POLICY_OPTS_COPY_MODE_MODIFIED=Modified Mode
# 18710
DSI_POLICY_OPTS_COPY_MODE_MODIFIED_FDA_DESC=Indicates that a file is considered for incremental backup only if it has changed since the last backup.
# 18711
DSI_POLICY_OPTS_COPY_MODE_ABSOLUTE=Absolute Mode
# 18712
DSI_POLICY_OPTS_COPY_MODE_ABSOLUTE_FDA_DESC=Indicates that a file is considered for incremental backup regardless of whether it has changed since the last backup.
# 18713
DSI_POLICY_OPTS_COPY_ARCH=Archive Copy Group Details
# 18714
DSI_POLICY_OPTS_COPY_ARCH_FDA_DESC=The Archive Copy Group Details window displays the attributes for the archive copy group in a management class.
# 18715
DSI_SM_FS_INFO=File System Information
# 18716
DSI_SM_FS_UTILIZATION_TITLE=Space Utilization
# 18717
DSI_SM_FS_NAME_FDA_DESC=Displays the name of the file system.
# 18718
DSI_SM_FS_TYPE_FDA_DESC=Displays the type of file system.
# 18719
DSI_SM_FS_SIZE_FDA_DESC=Displays the size of the file system.
# 18720
DSI_SM_FS_STATE_FDA_DESC=Displays the state of the file system with respect to Space Management. The state of a file system can be Active, Deactivated, Global Deactivated, or Not Managed.
# 18721
DSI_SM_MFS_SERVER_NAME_FDA_DESC=Displays the name of the server to which files are migrated.
# 18722
DSI_SM_MFS_THRESHOLD=Thresholds
# 18723
DSI_SM_MFS_THRESHOLD_FDA_DESC=Threshold migration maintains a specific level of free space on your local file system. The threshold percentages set for this file system affect when threshold migration starts and stops. A high threshold determines when threshold migration starts. A low threshold determines when file migration stops.
# 18724
DSI_SM_MFS_MIGSTART=Migration starts when space usage equals \nor exceeds {0} KB
# 18725
DSI_SM_MFS_MIGSTOP=Migration stops when space usage equals \nor less then {0} KB
# 18726
DSI_SM_MFS_HIGH_THRESHOLD_FDA_DESC=Drag the High Threshold slider to a percentage of the file system at which HSM automatically starts migrating eligible files to the TSM Server during a threshold or demand migration process.
# 18727
DSI_SM_MFS_LOW_THRESHOLD_FDA_DESC=Drag the Low Threshold slider to a percentage of the file system at which HSM automatically stops migrating eligible files to the TSM Server during a threshold or demand migration process.
# 18728
DSI_SM_MFS_MGMT=Management
# 18729
DSI_SM_MFS_MGMT_FDA_DESC=Use File System Management Properties to set the quota, stub file size, and premigration percentage for your file system.
# 18730
DSI_SM_MFS_MGMT_PREF=File System Management
# 18731
DSI_SM_MFS_MGMT_SETTINGS=Space Management Settings
# 18732
DSI_SM_MFS_STUB_SIZE_LONG=Stub File Size
# 18733
DSI_SM_MFS_STUB_SIZE_LONG_FDA_DESC=Specify the size of the stub file that replaces a migrated file. 511 bytes of the stub file are used to identify a migrated file. The remainder of the stub file contains the leader data of the migrated file.
# 18734
DSI_SM_MFS_PREMIGRATED=Premigration Percentage
# 18735
DSI_SM_MFS_PREMIGRATED_FDA_DESC=Drag the slider to set the percentage of space on a file system that can contain premigrated files that are eligible for migration.
# 18736
DSI_SM_MFS_PREMIGRATED_SIZE=The amount of data on this file system \nwhich can be premigrated is {0} KB
# 18737
DSI_PREFER_SBAR_WARNING_BLOCKSIZE=Warning: The Stub File Size option will be set to the physical block size.
# 18738
DSI_PREFER_SBAR_WARNING_BLOCKSIZE_MULT=Warning: The Stub File Size option will be set to a multiple of the physical block size.
# 18739
DSI_SM_MFS_QUOTA_FDA_DESC=Specify the total number of megabytes of data you can migrate and premigrate to the migration server from a local file system.
# 18740
DSI_SM_MFS_CANDIDATES=Candidates
# 18741
DSI_SM_MFS_CANDIDATES_PREF=File System Migration Candidates
# 18742
DSI_SM_MFS_CANDIDATES_FDA_DESC=Use Migration Candidates Properties to set attributes for files that are candidates for migration on your file system.
# 18743
DSI_SM_MFS_CANDIDATES_ATTRS=Candidates Attributes
# 18744
DSI_SM_MFS_MAX_CANDIDATES_NUM=Maximum Number of Candidates
# 18745
DSI_SM_MFS_MAX_CANDIDATES_FDA_DESC=Specify the maximum number of files that can be on the migration candidates list.
# 18746
DSI_SM_MFS_AGE_FACTOR_FDA_DESC=Specify the weight assigned to a file's age when files are prioritized for migration. File age in this case is the number of days since a file was last accessed. The Age Factor is used with the Size Factor to determine a file's priority for migration.
# 18747
DSI_SM_MFS_SIZE_FACTOR_FDA_DESC=Specify the weight given to a file's size when files are prioritized for migration. File size in this case is the size of the file in 1K blocks. The Size Factor is used with Age Factor to determine a file's priority for migration.
# 18748
DSI_SM_LOGON=Logon
# 18749
DSI_SM_LOGON_FDA_DESC=Use the Logon window to logon to the a TSM Client Node on a machine on which the Space Management agent is running.
# 18750
DSI_SM_CLIENT_NODE_EDIT=Client Node Edit
# 18751
DSI_SM_CLIENT_NODE_ADD=Client Node Add
# 18752
DSI_SM_NODE_DEACTIVATED=Global Deactivated
# 18753
DSI_SM_NODE_ADD_TOOLTIP=Add a new Client Node
# 18754
DSI_SM_NODE_EDIT_TOOLTIP=Edit the selected Client Node
# 18755
DSI_SM_NODE_REMOVE_TOOLTIP=Remove the selected Client Node
# 18756
DSI_SM_NODE_ACTIVE=Active
# 18757
DSI_SM_NODE_NOT_MANAGEABLE=Not Manageable
# 18758
DSI_SM_NODE_NOT_MANAGED=Not Managed
# 18759
DSI_SM_REFRESH_TOOLTIP=Reload data for the selected node
# 18760
DSI_SM_SAVE_SETTINGS_TOOLTIP=Save current view settings locally
# 18761
DSI_SM_IMPORT_SETTINGS_TOOLTIP=Import settings from the selected client node
# 18762
DSI_SM_SIGNOFF_AND_CLOSE_DIALOG_TEXT=Do you want to Sign Off all connected client nodes \nand close Enterprise Space Management Console now?
# 18763
DSI_SM_STATUS_BAR_NODE_SIGNED_OFF=Client node '{0}' has been signed off
# 18764
DSI_SM_DEBUG_CONSOLE=&Debug Console
# 18765
DSI_SM_DEBUG_CONSOLE_TITLE=IBM Tivoli Debug Console
# 18766
DSI_SM_FRAME_TITLE_DEBUG=IBM Tivoli Enterprise Space Management Console (Debug mode)
# 18767
DSI_SM_CLOSE=Close
# 18768
DSI_SM_SAVE_AS=Save as...
# 18769
DSI_SM_ERROR_MESSAGE= Error Message
# 18770
DSI_SM_WARNING_MESSAGE= Warning Message
# 18771
DSI_SM_DOWNLOAD_NOW=Download now...
# 18773
DSI_SM_WARNING_NODE_REMOVE=Do you want to remove '{0}' from the customized client nodes list?
# 18796
DSI_SM_LOGON_DESCRIPTION=The information below is needed to logon to a TSM Client Node on a machine on which the Space Management agent is running. \r\nClick on an item to see a description. If you do not know the information requested, contact your system administrator.
# 18800
DSI_SM_FILE_SYSTEMS=File Systems
# 18801
DSI_SM_FS_PROPERTIES_TITLE=File System Properties
# 18802
DSI_SM_GENERAL_PROPERTIES=General Properties
# 18803
DSI_SM_FILE_SYSTEM_SPACE_FORMAT=File System space
# 18804
DSI_SM_LOW_THRESHOLD_ABBREVIATION=LT
# 18805
DSI_SM_HIGH_THRESHOLD_ABBREVIATION=HT
# 18806
DSI_SM_QUOTA_ABBREVIATION=QT
# 18807
DSI_FILESIZE_BYTES_LONG=Byte
# 18808
DSI_SM_FS_SHOW_ALL=Show all file systems
# 18809
DSI_SM_FS_SHOW_MANAGED_ONLY=Show managed file systems only
# 18810
DSI_SM_FS_SHOW_MANAGEABLE_ONLY=Show manageable file systems only
# 18811
DSI_SM_REFRESH_AUTOM=Refresh automatically
# 18812
DSI_SM_REFRESH_INTERVAL=Refresh interval
# 18813
DSI_SM_GENERAL_PROPERTIES_FDA_DESC=Displays general file system information.\nIf Resident Data equals or exceeds High Threshold (HT) level, eligible files automatically begin migrating to TSM Server until Resident Data reach Low Threshold (LT) level. The Quota (QT) level determines the maximum amount of data that can be migrated and premigrated from this file system to the TSM Server.
# 18814
DSI_SM_FS_PROPERTIES_MODIFIED=Properties of '{0}' has been modified.
# 18815
DSI_SM_FS_PROPERTIES_NOT_MODIFIED=Properties of '{0}' has not been modified.
# 18816
DSI_SM_EDITING_PROPERTIES=Editing {0} dialog...
# 18821
DSI_SM_STATUS_BAR_NODE_GLOBAL_DEACTIVATING=Deactivating all managed file systems of '{0}'...
# 18822
DSI_SM_STATUS_BAR_NODE_GLOBAL_DEACTIVATED=All managed file systems of '{0}' has been deactivated
# 18823
DSI_SM_STATUS_BAR_NODE_NOT_GLOBAL_DEACTIVATED=All managed file systems of '{0}' has not been deactivated
# 18824
DSI_SM_STATUS_BAR_NODE_GLOBAL_REACTIVATING=Reactivating all managed file systems of '{0}'...
# 18825
DSI_SM_STATUS_BAR_NODE_GLOBAL_REACTIVATED=All managed file systems of '{0}' has been reactivated
# 18826
DSI_SM_STATUS_BAR_NODE_NOT_GLOBAL_REACTIVATED=All managed file systems of '{0}' has not been reactivated
# 18827
DSI_SM_STATUS_BAR_NODE_CONNECTING=Contacting host '{0}' ...
# 18828
DSI_SM_STATUS_BAR_NODE_CONNECTED=Host '{0}' connected
# 18829
DSI_SM_STATUS_BAR_NODE_NOT_CONNECTED=Host '{0}' not connected
# 18830
DSI_SM_STATUS_BAR_FS_NOT_LOADED=File System information of '{0}' are not loaded.
# 18831
DSI_SM_HELP_TOPICS_FDA_DESC=Click the help icon button to open Help Topics dialog.
# 18832
DSI_SM_STATUS_BAR_FS_UNMANAGING=Removing Space Management from '{0}' file system ...
# 18833
DSI_SM_STATUS_BAR_FS_UNMANAGED=Space Management has been removed from '{0}' file system
# 18834
DSI_SM_STATUS_BAR_FS_NOT_UNMANAGED=Space Management has not been removed from '{0}' file system
# 18835
DSI_SM_STATUS_BAR_FS_MANAGING=Adding Space Management to '{0}' file system ...
# 18836
DSI_SM_STATUS_BAR_FS_MANAGED=Space Management has been added to '{0}' file system
# 18837
DSI_SM_STATUS_BAR_FS_NOT_MANAGED=Space Management has not been added to '{0}' file system
# 18838
DSI_SM_STATUS_BAR_FS_DEACTIVATING=Deactivating Space Management from '{0}' file system ...
# 18839
DSI_SM_STATUS_BAR_FS_DEACTIVATED=Space Management has been deactivated from '{0}' file system
# 18840
DSI_SM_STATUS_BAR_FS_NOT_DEACTIVATED=Space Management has been not deactivated from '{0}' file system
# 18841
DSI_SM_STATUS_BAR_FS_REACTIVATING=Reactivating Space Management on '{0}' file system ...
# 18842
DSI_SM_STATUS_BAR_FS_REACTIVATED=Space Management has been reactivated on '{0}' file system
# 18843
DSI_SM_STATUS_BAR_FS_NOT_REACTIVATED=Space Management has been not reactivated on '{0}' file system
# 18844
DSI_SM_HELP_ONLINE=&Online Documentation...
# 18845
DSI_SM_FS_CHOOSE_COLUMNS=Ch&oose Columns...
# 18846
DSI_PREFERI_SNAP_PROVIDER_TYPE=Snapshot Provider Type
# 18847
DSI_PREFERI_SNAPPROVIDER_CHOICE_JFS2=JFS2
# 18848
DSI_PREFERI_SNAPPROVIDER_CHOICE_LVM=LINUX_LVM
# 18849
DSI_PREFERI_SNAPPROVIDER_CHOICE_NONE=None
# 18850
DSI_PREFERI_DYNAMIC_IMAGE_TYPE=Dynamic Image Backup
# 18851
DSI_PREFERI_DYNAMIC_IMAGE_NO=No
# 18888
Explanation_Msg=Explanation:
# 18889
Sysact_Msg=System Action:
# 18890
Uresp_Msg=User Response:
# 18900
DSI_FIND_SEARCH_AND_FILTER=Search and Filter
# 18901
DSW_MENU_FIND=&Find
# 18902
DSI_FIND_SEARCH_FILES=Search Files
# 18903
DSI_FIND_SEARCH_OPTIONS=Search Options
# 18904
DSI_FIND_SEL_DATE=Date
# 18905
DSI_FIND_OWNER_AND_GROUP=Owner and Group
# 18906
DSI_FIND_SEL_TYPE=Type
# 18907
DSI_FIND_FILES_NAME=File Name
# 18908
DSI_FIND_FILES_MODIFIED=Files Modified
# 18909
DSI_FIND_FILES_ACCESSED=Files Accessed
# 18910
DSI_FIND_FILES_ARCHIVED=Files Archived
# 18911
DSI_FIND_FILES_BACKED_UP=Files Backed Up
# 18912
DSI_FIND_START_PATH=Start Path
# 18913
DSI_FIND_FILES_INSPECTED=Files inspected
# 18914
DSI_FIND_MATCHES_FOUND=Matches found
# 18915
DSI_FIND_AFTER_DATE=after
# 18916
DSI_FIND_BEFORE_DATE=before
# 18917
DSI_FIND_EXACTLY_ON_DATE=exactly on
# 18918
DSI_FIND_BETWEEN_DATE=between
# 18919
DSI_FIND_AND_DATE=and
# 18920
GUI_SEARCHFILTER_CRITERIA=Search/Filter Criteria
# 18921
DSI_FIND_PREVIOUS_YEAR=Previous Year
# 18922
DSI_FIND_NEXT_YEAR=Next Year
# 18923
DSI_FIND_PREVIOUS_MONTH=Previous Month
# 18924
DSI_FIND_NEXT_MONTH=Next Month
# 18925
DSI_FIND_MONDAY_ABBREVIATION=Mon
# 18926
DSI_FIND_TUESDAY_ABBREVIATION=Tue
# 18927
DSI_FIND_WEDNESDAY_ABBREVIATION=Wed
# 18928
DSI_FIND_THURSDAY_ABBREVIATION=Thu
# 18929
DSI_FIND_FRIDAY_ABBREVIATION=Fri
# 18930
DSI_FIND_SATURDAY_ABBREVIATION=Sat
# 18931
DSI_FIND_SUNDAY_ABBREVIATION=Sun
# 18932
DSI_FIND_SEARCH_RESULTS=Search Results
# 18933
DSI_MENU_SELECT_ALL_FILES=Select &all items
# 18934
DSI_MENU_RESET_SEARCH_CRITERIA=&Reset search criteria
# 18935
DSI_FIND_COMPLETED=Search completed
# 18936
DSI_FIND_STOP_BY_USER=Search stop by user
# 18937
DSI_FIND_CLOSE=A search process is still running.\nDo you want to stop it and to close the dialog now?
# 18938
DSI_FIND_TREE_FILTERED=The tree underneath {0} \nhas been filtered with the specified filter criteria. \n\nDo you want to close the dialog now?
# 18939
GUI_SEARCHFILTER_SEARCH_TYPE=What to Search
# 18940
DSI_FIND_MATCHES_UNDERNEATH={0} matches underneath {1}
# 18941
DSI_FIND_MATCHES_INFO=Click the Search button to begin a search.
# 18942
DSI_MENU_SEARCH=&Search
# 18943
DSI_MENU_STOP=&Stop
# 18944
DSI_MENU_FILTER=&Filter
# 18945
GUI_SEARCHFILTER_ALL_OBJS=All Objects
# 18946
DSI_FIND_REMOVE_FILTER=Remove Filter
# 18947
DSW_MENU_REMOVE_FILTER=&Remove Filter
# 18948
DSI_FIND_FILTER_APPLYING=Applying filter criteria to the tree...
# 18949
DSI_FIND_FILTER_APPLIED=The specified filter criteria has been applied to the tree.
# 18950
DSI_FIND_FILTER_NOT_APPLIED=The specified filter criteria has not been applied to the tree.
# 18951
DSI_FIND_SEARCH_TOOLTIP=Search for files matching the specified search criteria
# 18952
DSI_FIND_FILTER_TOOLTIP=Apply the specified filter criteria to the tree
# 18953
DSI_FIND_STOP_TOOLTIP=Stop the search process
# 18954
DSI_FIND_CONFIRM_REMOVE_FILTER=Do you want to remove the filter underneath \n{0}
# 18955
DSI_SM_ABOUT_PRODUCT=IBM Tivoli Enterprise Space Management Console gives the administrator the ability to manage multiple machines where Hierarchical Storage Manager (HSM) is installed using the same graphical user interface. To start on managing your resources click on MyTasks/ManageResource now.\n\nIBM Tivoli is really interested in receiving your feedback and suggestion to improve this product which you can email to: {0}
# 18956
DSI_SM_MFS_VIEW_ACTIVITIES=A&ctivities...
# 18957
DSI_SM_MFS_ACTIVITIES=Activities
# 18958
DSI_SM_MFS_ACTIVITIES_TOOLTIP=Display the activities of the selected File System
# 18959
DSI_SM_MFS_ACTIVITIES_TITLE=Space Management Activities
# 18960
DSI_SM_MFS_SCOUT_ACTIVITIES_TITLE=Scout Activities
# 18961
DSI_SM_MFS_MASTER_PROCESS_ID=Master Process ID
# 18962
DSI_SM_MFS_START_TIME=Start time
# 18963
DSI_SM_MFS_UPDATE_TIME=Update time
# 18964
DSI_SM_MFS_NO_ACTIVITIES_DETECTED=No activities detected
# 18965
DSI_SM_MFS_LAST_RUNNING_PROCESS_DETAILS=Details of latest running process
# 18966
DSI_SM_MFS_PROCESS_INFO=Process Information
# 18967
DSI_SM_MFS_SCANNING_STATUS=Scanning Status
# 18968
DSI_SM_MFS_START_LOCATION=Start location
# 18969
DSI_SM_MFS_CURRENT_LOCATION=Current location
# 18970
DSI_SM_MFS_FILES_ANALYZED=Files analyzed
# 18971
DSI_SM_MFS_CANDIDATES_FOUND=Candidates found
# 18972
DSI_SM_MFS_FILES_SKIPPED=Files Skipped
# 18973
DSI_SM_MFS_FILES_EXCLUDED=Files excluded
# 18974
DSI_SM_MFS_FILES_TOO_SMALL=Files too small
# 18975
DSI_SM_MFS_SYMBOLIC_LINKS=Symbolic links
# 18976
DSI_SM_MFS_OTHER_SKIPPED_FILES=Other skipped files
# 18977
DSI_SM_MFS_ACTIVITIES_DETAILS=Details
# 18978
DSI_SM_MFS_STATUS_SEARCHING_CANDIDATES=Searching for candidates...
# 18979
DSI_SM_STATUS_REFRESHING_ACTIVITIES=Refreshing activities status...
# 18980
GUI_SEARCHFILTER_SEARCH_OBJ=Search All Objects
# 18981
DSI_SM_DIRECTORIES_ABBREVIATION=dir(s)
# 18982
GUI_SEARCHFILTER_OBJNAME=Object Name
# 18983
DSI_SM_MFS_SCOUT_ACTIVITIES_REFRESHED_ON=Scout activities refreshed on {0}
# 18984
DSI_SM_MFS_PROCESS_ID=Process ID
# 18985
DSI_SM_MFS_CANDIDATES_FOUND_OF_MAX={0} of {1} [ new: {2} ]
# 18987
DSI_SM_MFS_AUTOMIG_ACTIVITIES_TITLE=Automigration Activities
# 18988
DSI_SM_MFS_RECONCILATION_ACTIVITIES_TITLE=Reconciliation Activities
# 18989
DSI_SM_ACTIVITIES_ON=Activities on {0}
# 18990
DSI_SM_NEW_MIGRATED_FILES=Migrated {0} files to TSM server
# 18993
DSI_SM_MFS_AUTOMIG_ACTIVITIES_REFRESHED_ON=Automigration activities refreshed on {0}
# 18994
DSI_SM_MFS_RECONCILE_ACTIVITIES_REFRESHED_ON=Reconciliation activities refreshed on {0}
# 18995
DSI_SM_MFS_WORKING_MIGRATORS=Working migrators
# 18996
DSI_SM_MFS_ACTIVATED_BY=Activated by
# 18997
DSI_SM_MFS_MIGRATION_STATUS_TITLE=Migration Status
# 18999
DSI_SM_MFS_MIGRATED_SPACE=Migrated Space
# 19000
DSI_SM_MFS_CURRENT_THRESHOLD=Current threshold
# 19001
DSI_SM_MFS_LOW_HIGH_THRESHOLD=Low-High
# 19002
DSI_SM_MFS_PREMIGRATION_STATUS_TITLE=Premigration Status
# 19004
DSI_SM_MFS_PREMIGRATED_SPACE=Premigrated space
# 19005
DSI_SM_MFS_CURRENT_PREMIGRATION_LEVEL=Current premigration
# 19006
DSI_SM_MFS_MAX_PREMIGRATION_LEVEL=Max
# 19007
DSI_SM_MFS_MIGRATING_FILES_TO_SERVER=Migrating files to TSM server {0} ...
# 19008
DSI_SM_MFS_ACTIVATED_BY_HIGH_THRESHOLD_REACHED=High threshold reached
# 19009
DSI_SM_MFS_ACTIVATED_BY_NO_SPACE_CONDITION=No space condition
# 19010
DSI_SM_MFS_ACTIVATED_BY_USER=User
# 19012
DSI_SM_MFS_NEW_CANDIDATES=Fond {0} new candidates eligible for migration
# 19013
DSI_SM_ACTIVITIES_STATUS_REFRESHED_ON=Activities refreshed on {0}
# 19014
DSI_SM_MFS_RECONCILE_STATUS=Reconcile Status
# 19015
DSI_SM_MFS_PROCESSED_FILES=Processed files
# 19016
DSI_SM_MFS_ORPHANS_FILES=Orphaned stub files
# 19018
DSI_SM_MFS_FILES_EXPIRATION_STATUS=Files Expiration Status
# 19019
DSI_SM_MFS_FILES_EXPIRATION_PERIOD=Files expiration period
# 19020
DSI_SM_MFS_FILES_EXPIRED_ON_SERVER=Files expired on the server
# 19021
DSI_SM_MFS_FILES_NEWLY_MARKED=Files newly marked for expiration
# 19022
DSI_SM_MFS_FILES_PREVIOUSLY_MARKED=Files previously marked for expiration
# 19023
DSI_SM_MFS_RECONCILATION_PROCESS_STARTED=Reconciliation process started...
# 19024
DSI_SM_MFS_READING_PREMIGRATION_TABLE=Reading premigration table...
# 19025
DSI_SM_MFS_PREMIGRATION_TABLE_READ=Premigration table read
# 19026
DSI_SM_MFS_QUERY_MIGRATION_LIST=Querying migration list from TSM server...
# 19027
DSI_SM_MFS_MIGRATION_LIST_RETRIEVED=Migration list retrieved from TSM server
# 19028
DSI_SM_MFS_QUERY_BACKUP_LIST=Querying backup list...
# 19029
DSI_SM_MFS_BACKUP_LIST_RETRIEVED=Backup list retrieved
# 19030
DSI_SM_MFS_TRAVERSING_FILE_SYSTEM=Traversing file system...
# 19031
DSI_SM_MFS_UPDATING_PREMIGRATION_DB=Updating premigration database...
# 19032
DSI_SM_MFS_PREMIGRATION_DB_UPDATED=Premigration database updated
# 19033
DSI_SM_MFS_EXPIRING_FILES_ON_SERVER=Expiring files on TSM server...
# 19034
DSI_SM_MFS_RECONCILATION_PROCESS_COMPLETED=Analyzed {0} entries. Processed {1} files.
# 19035
DSI_SM_MFS_FILE_SYSTEM_TRAVERSED=File system traversed
# 19036
DSI_BackChoice_SnapDiff_Latest=Latest
# 19037
DSI_SM_MFS_LATEST_MIGRATED_FILES=Latest migrated files
# 19038
DSI_SM_MFS_LATEST_MIGRATED_DATA=Latest migrated data
# 19039
DSI_SM_MFS_LATEST_PREMIGRATED_FILES=Latest premigrated files
# 19040
DSI_SM_MFS_LATEST_PREMIGRATED_DATA=Latest premigrated data
# 19041
DSI_SM_FS_REFRESH=&Refresh
# 19042
DSI_FDA_BUTTON=FDA button
# 19043
DSI_FDA_BUTTON_FDA_DESC=Click the Field Description Area (FDA) button to display help for the selected item 
# 19044
DSI_HELP_BUTTON_FDA_DESC=Click the Help button to display contextual help for this window
# 19045
DSI_SM_PROPERTIES=&Properties...
# 19046
DSI_BackChoice_SnapDiff_LatestGrpTitle=Use the latest existing snapshot?
# 19047
DSI_SM_MFS_SCOUT_DAEMON_NOT_RUNNING_FDA_DESC=A list of candidates files eligible for migration cannot be built because \nthe master scout daemon is not running on the selected client node. \nPlease restart the master scout daemon manually using the "dsmscoutd" \ncommand on the machine where Space Management Agent is running.
# 19048
DSI_SM_MFS_SCOUT_ERROR_LOADING_STATUS_FDA_DESC=An exception has been detected loading the scout activities status.
# 19049
DSI_SM_MFS_STATUS_SEARCHING_CANDIDATES_FDA_DESC=The dsmscout daemon is now building a migration candidates list.\n\nA migration candidates list is a list of files in your file system that are eligible for automatic migration at the time the list is built.\n\nOn the "Details" section you can find more detailed information about the progress of this process.
# 19050
DSI_SM_MFS_SCOUT_NO_ACTIVITIES_FDA_DESC=No scout activities are detected at the moment.\n\nClick on "Details of latest running process" section to see detailed information about the latest run of the scout daemon.
# 19051
DSI_SM_MFS_MASTER_SCOUT_PROCESS_ID_FDA_DESC=Process ID of the master scout daemon.\nThe dsmscout daemon continuously scans your managed file system for candidates requests from the automatic migration processes, and for elapsed scan-interval hours of all your active HSM-managed file system. \nA missing process ID number means that the master scout daemon is not running.
# 19052
DSI_SM_MFS_SCOUT_PROCESS_ID_FDA_DESC=Process ID of the slave scout daemon.\nA slave scout daemon is started from the master scout daemon to scan for new candidates. After a candidates scan is completed for your file system, a new migration candidates list is created and the slave scout daemon ends. \nA missing process ID number means that the slave scout daemon is not running.
# 19053
DSI_SM_MFS_START_TIME_FDA_DESC=Time of the latest start of the process.
# 19054
DSI_SM_MFS_UPDATE_TIME_FDA_DESC=Time of the latest information update from Space Management Agent.
# 19055
DSI_SM_MFS_START_LOCATION_FDA_DESC=Start path used by the scout daemon to scan for candidates.
# 19056
DSI_SM_MFS_CURRENT_LOCATION_FDA_DESC=Current path the scout daemon is scanning for candidates.
# 19057
DSI_SM_MFS_FILES_ANALYZED_FDA_DESC=Number of files [directories] analyzed by the scout daemon.
# 19058
DSI_SM_MFS_CANDIDATES_FOUND_FDA_DESC=Number of all [new] candidates found by the scout daemon.\n\nUse the File System Properties dialog to specify the maximum number of migration candidates the scout daemon should search.
# 19059
DSI_SM_MFS_FILES_EXCLUDED_FDA_DESC=Number of excluded files found by the scout daemon.
# 19060
DSI_SM_MFS_FILES_TOO_SMALL_FDA_DESC=Number of small files found by the scout daemon. Small files (e.g. stubs) are not eligible for migration.
# 19061
DSI_SM_MFS_SYMBOLIC_LINKS_FDA_DESC=Number of symbolic links found by the scout daemon.
# 19062
DSI_SM_MFS_OTHER_SKIPPED_FILES_FDA_DESC=Number of other skipped files analyzed by the scout daemon.
# 19063
DSI_SM_MFS_ACTIVITIES_DETAILS_FDA_DESC=This section contains detailed information of current or latest running process.\n\nClick on the section title to expand or collapse the section.
# 19064
DSI_SM_MFS_PROCESS_INFO_FDA_DESC=This section contains process information of current or latest running process.\n\nClick on the section title to expand or collapse the section.
# 19065
DSI_SM_MFS_SCANNING_STATUS_FDA_DESC=This section contains information about the results of current or latest scanning process.\n\nClick on the section title to expand or collapse the section.
# 19066
DSI_SM_MFS_FILES_SKIPPED_FDA_DESC=This section contains information about the skipped files of current or latest scanning process.\n\nClick on the section title to expand or collapse the section.
# 19067
DSI_SM_MFS_ACTIVITIES_TITLE_FDA_DESC=The Space Management Activities dialog allows to monitor activities of HSM-managed file system.\n\nClick an item to see its description.
# 19068
DSI_SM_ACT_REFRESH_BUTTON_FDA_DESC=Click on Refresh button to refresh the status of all activities from the Space Management Agent.
# 19069
DSI_SM_ACT_CLOSE_BUTTON_FDA_DESC=Click on Close button to close the Space Management dialog.
# 19070
DSI_SM_ACT_OPTIONS_BUTTON_FDA_DESC=Click on Options button to show or to modify Space Management Activities options.
# 19071
DSI_SM_REFRESH_AUTOM_FDA_DESC=Select this check box to refresh the status of the Space Management Activities automatically with the specified refresh interval.
# 19072
DSI_SM_REFRESH_INTERVAL_FDA_DESC=Specify the amount of time to wait before attempting to refresh the status of the activities.
# 19073
DSI_SM_MFS_MASTER_AUTOMIG_PROCESS_ID_FDA_DESC=Process ID of the space monitor daemon.\nThe space monitor daemon checks space usage on your active HSM-managed file systems at interval that you specify. \nA missing process ID number means that the monitor daemon is not running.
# 19074
DSI_SM_MFS_AUTOMIG_PROCESS_ID_FDA_DESC=Process ID of the dsmautomig process.\nWhen space usage reaches the high threshold, or when you start the dsmautomig command manually, migration automatically sends eligible files to storage. When space usage reach the low threshold, migration stops.\nA missing process ID number means that the slave dsmautomig process is not running.
# 19075
DSI_SM_MFS_ACTIVATED_BY_FDA_DESC=Automigration process can be activated if High Level Threshold is reached, if No Space Condition is detected or manually by running the dsmautomig command.
# 19076
DSI_SM_MFS_WORKING_MIGRATORS_FDA_DESC=Number of migrators, that currently are migrating files, of the maximum migrators available.
# 19077
DSI_SM_MFS_MIGRATION_STATUS_FDA_DESC=This section contains information about the migration status of current or latest automigration process.\n\nClick on the section title to expand or collapse the section.
# 19078
DSI_SM_MFS_MIGRATED_FILES_FDA_DESC=Number of the latest migrated files to the TSM server.
# 19079
DSI_SM_MFS_MIGRATED_DATA_FDA_DESC=Latest amount of data migrated to the TSM server.
# 19080
DSI_SM_MFS_CURRENT_THRESHOLD_FDA_DESC=Space usage of the file system in percentage.
# 19081
DSI_SM_MFS_LOW_HIGH_THRESHOLD_FDA_DESC=Threshold percentages of the file system at which HSM automatically starts (High) and stops (Low) migrating eligible files to the TSM Server during a threshold or demand migration process. \n\nUse the File System Properties dialog to specify a different value.
# 19082
DSI_SM_MFS_PREMIGRATION_STATUS_FDA_DESC=This section contains information about the premigration status of current or latest automigration process.\n\nClick on the section title to expand or collapse the section.
# 19083
DSI_SM_MFS_PREMIGRATED_FILES_FDA_DESC=Number of the latest premigrated files to the TSM server.
# 19084
DSI_SM_MFS_PREMIGRATED_DATA_FDA_DESC=Latest amount of data premigrated to the TSM server.
# 19085
DSI_SM_MFS_CURRENT_PREMIGRATION_LEVEL_FDA_DESC=Amount of data premigrated to the TSM server in percentage.
# 19086
DSI_SM_MFS_MAX_PREMIGRATION_LEVEL_FDA_DESC=Maximum percentage of the file system that can be premigrated to the TSM server.\n\nUse the File System Properties dialog to specify a different value.
# 19088
DSI_SM_MFS_RECONCILE_PROCESS_ID_FDA_DESC=Process ID of the dsmreconcile process.\nA reconciliation process is used to reconcile or synchronize the file system with the TSM server.\nA missing process ID number means that the reconcile process is not running.
# 19089
DSI_SM_MFS_RECONCILATION_ACTIVITIES_TITLE_FDA_DESC=This section contains information about the reconciliation status of current or latest reconcile process.\n\nClick on the section title to expand or collapse the section.
# 19090
DSI_SM_MFS_PROCESSED_FILES_FDA_DESC=Number of files processed during file system traversal of current or latest reconcile process.
# 19091
DSI_SM_MFS_ORPHANS_FILES_FDA_DESC=Number of orphaned stub files detected during current or latest reconcile process.\n\nAn orphaned stub file is a stub file for which a corresponding migrated file in storage is not located. Possible situations in which stub files might become orphaned include the following: \n- dsm.sys points to a different server for space management services other than the one to which files were migrated.\n- Your TSM administrator uses "delete filespace" command to delete any migrated files from the file system.\n- A media failure occurs that corrupts or loses your migrated files. Storage Pool backup and recovery provides protection against media failures. You can restore a backup version of the file if you used the backup-archive client.\n
# 19092
DSI_SM_MFS_FILES_EXPIRATION_STATUS_FDA_DESC=This section contains information about the files expiration status of current or latest reconcile process.\n\nClick on the section title to expand or collapse the section.
# 19093
DSI_SM_MFS_FILES_EXPIRATION_PERIOD_FDA_DESC=Number of days that copies of migrated or premigrated files remain on the TSM server after they are modified on, or erased from, the file system. The default is seven days.
# 19094
DSI_SM_MFS_FILES_EXPIRED_ON_SERVER_FDA_DESC=Number of files expired on the TSM server due to expiration period.
# 19095
DSI_SM_MFS_FILES_NEWLY_MARKED_FDA_DESC=Number of files newly marked for expiration on the TSM server.
# 19096
DSI_SM_MFS_FILES_PREVIOUSLY_MARKED_FDA_DESC=Number of files previously marked for expiration on the TSM server.
# 19097
DSI_SM_MFS_QUOTA_LEVEL_FDA_DESC=The quota level determines the maximum amount of data that can be \nmigrated and premigrated from this file system to the TSM Server.\nYou can use the File System Properties dialog to specify a different quota level.
# 19098
DSI_SM_MFS_REC_MIGRATED_FILES_FDA_DESC=Number of the migrated files on the TSM server after reconciliation.
# 19099
DSI_SM_MFS_REC_PREMIGRATED_FILES_FDA_DESC=Number of the premigrated files on the TSM server after reconciliation.
# 19100
DSI_SM_MFS_WORKING_MIGRATORS_OF_MAXIMUM={0} of {1}
# 19101
DSI_FDA_BUTTON_TOOLTIP=Show/Hide Field Description Area (FDA)
# 19102
DSI_HELP_BUTTON_TOOLTIP=Display help
# 19103
DSI_SM_ACT_REFRESH_BUTTON_TOOLTIP=Refresh the status all activities.
# 19104
DSI_SM_ACT_CLOSE_BUTTON_TOOLTIP=Close Space Management Activities dialog
# 19105
DSI_SM_ACT_OPTIONS_BUTTON_TOOLTIP=Display/modify Space Management Activities options.
# 19106
DSI_SM_MFS_MONITOR_DAEMON_NOT_RUNNING_FDA_DESC=Files cannot be automatically migrated or recalled from TSM server because \nthe monitor daemon is not running on the selected client node.\nPlease restart the monitor daemon manually using the "dsmmonitord" \ncommand on the machine where Space Management Agent is running.
# 19107
DSI_SM_MFS_RECALL_DAEMON_NOT_RUNNING_FDA_DESC=Files cannot be recalled from TSM server because the recall daemon \nis not running on the selected client node. \nPlease restart the recall daemon manually using the "dsmrecalld" \ncommand on the machine where Space Management Agent is running.
# 19112
DSI_SM_MFS_AUTOMIG_COMM_ERROR_FDA_DESC=TSM cannot migrate files from this file system because a communication error is occurred in the migration phase.
# 19113
DSI_SM_MFS_AUTOMIG_PRE_MIG_ERROR_FDA_DESC=TSM cannot migrate files from this file system because a communication error is occurred in the premigration phase.
# 19114
DSI_SM_MFS_AUTOMIG_OTHER_ERROR_FDA_DESC=TSM cannot migrate files from this file system because a processing error is occurred in the migration phase.
# 19116
DSW_IBM_HOMEPAGE=http://www.ibm.com/software
# 19117
DSW_HSM_HOMEPAGE=http://www.ibm.com/software/tivoli/products/storage-mgr-space
# 19118
DSW_HSM_TECHSUPT_HOMEPAGE=http://www.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManagerforSpaceManagement.html
# 19119
DSW_TIVOLI_REDBOOKS_HOMEPAGE=http://www.redbooks.ibm.com/portals/Tivoli
# 19120
DSW_MENU_HELP_HSM_PROD_URL=TSM for Spa&ce Management Home Page
# 19121
DSW_MENU_HELP_HSM_PROD_TECH_SUPPORT_URL=TSM for Space &Management Technical Support Home Page
# 19122
DSW_MENU_HELP_IBM_URL=IBM H&ome Page
# 19123
DSW_MENU_HELP_TIVOLI_REDBOOKS_URL=Tivoli and IBM &Redbooks Home Page
# 19124
DSW_TIVOLI_TECHSUPT_HOMEPAGE=http://www.ibm.com/software/sysmgmt/products/support
# 19125
DSW_MENU_HELP_TIVOLI_TECH_SUPPORT_URL=Tivoli Software S&upport Home Page
# 19126
DSI_SM_HELP_TOPICS_FDA=Help Topics
# 19127
DSI_SM_CLIENT_NODE_ADD_FDA_DESC=Use the Client Node Add window to add a TSM Client Node to the Client Nodes list.
# 19128
DSI_SM_CLIENT_NODE_EDIT_FDA_DESC=Use the Client Node Edit window to modify a TSM Client Node in the Client Nodes list.
# 19129
DSI_SM_CHECK_LOG_FILES=Check the {0} file in the $DSM_LOG or installation directory on your local machine and the $DSM_DIR/{1} file on the client node machine if present.
# 19130
DSI_SM_CHECK_LOCAL_LOG_FILE=Check the {0} file in the $DSM_LOG or installation directory on your local machine if present.
# 19131
DSI_SM_CONTACT_TECHNICAL_SUPPORT=If this does not help to identify the cause of the problem, contact your system administrator and/or TSM technical support for further assistance.
# 19132
DSI_SM_TOOLBAR_LABELS=Too&lbar Labels
# 19133
DSI_SM_FS_STATUS_UPDATED=The operation requested was already performed by another process, \nbut the status in the file system table was not updated.\nFile system table information is now updated!\nFile system {0} is in {1} state.
# 19134
DSI_SM_MFS_LOCK=A conflicting Space Management process is already running in the \n{0} file system.\nPlease wait until the Space Management process is ready and try again.
# 19135
DSI_AUTHERR_INVALID_NODE_OWNER=The supplied node or user name exceeds the maximum allowed lengh (64).
# 24000
DSI_PREFERS_SCHEDULE_CMD=Schedule Command
# 24001
DSI_PREFERS_PRESCHEDULE=Preschedule Command
# 24002
DSI_PREFERS_PRESCHEDULE_PREVENT=Prevent the following Preschedule command from executing:
# 24003
DSI_PREFERS_POSTSCHEDULE=Postschedule Command
# 24004
DSI_PREFERS_POSTSCHEDULE_PREVENT=Prevent the following Postschedule command from executing:
# 24005
DSI_PREFERS_SCHEDCMD_WAIT=Wait for the command to complete
# 24006
DSI_PREFERS_COMMAND=Command
# 24007
DSI_PREFERS_FORCE=Force the client command process to continue running after account logs off
# 24008
CLI_No_File_Spaces_Found_Matching=No file spaces for node '{0}' were found on the server matching\nthe search criteria\n
# 24010
DSI_PREFERA_AUTHORIZATION=Authorization
# 24011
DSI_PREFERA_PASSWORD_ACCESS=Password Access
# 24012
DSI_PREFERA_PASSWORD_PROMPT=Password Prompt
# 24013
DSI_PREFERA_PASSWORD_GENERATE=Password Generate
# 24014
DSI_PREFERA_PASSWORD=Password
# 24015
DSI_PREFERA_PASSWORD_DIR=Location
# 24016
CLI_TOC_CREATE=A table of contents is being created.\n
# 24020
DSI_PREFERW_WEBCLIENT=Web Client
# 24021
DSI_PREFERW_HTTPPORT=HTTP Port
# 24022
DSI_PREFERW_SSLPORT=SSL Port
# 24023
DSI_PREFERW_REVOKE=Revoke remote access privilege
# 24024
DSI_PREFERM_COMMANDLINE=Command Line
# 24025
DSI_PREFERM_QUIET=Do not display process information on screen
# 24026
DSI_PREFERM_PAUSE=Pause after displaying the following number of lines
# 24027
DSI_PREFERM_DISPLAY_LINE=Number of lines to display on screen
# 24028
DSI_PREFERW_WEBPORTS=WEB Ports
# 24029
DSI_PREFERD_TRACE_ENABLE_WRAP=Enable trace file wrapping
# 24030
DSI_PREFERD_DIAGNOSTIC=Diagnostics
# 24031
DSI_PREFERD_TRACE=Trace
# 24032
DSI_PREFERD_TRACE_ENABLE=Enable Tracing
# 24033
DSI_PREFERD_TRACE_FILENAME=File Name
# 24034
DSI_PREFERD_TRACE_FLAG=Trace Flags
# 24035
DSI_BackChoice_NoJournalIncr=Incremental (without journal)
# 24037
DSI_PREFERD_TRACE_MAX1_SIZE=Maximum size (MB)
# 24038
DSI_PREFERD_TRACE_ENABLE_SPAN=Enable trace file spanning
# 24039
DSI_PREFERD_TRACE_MAX2_SIZE=Maximum size (MB) per file segment
# 24040
DSI_PREFERB_BACKUP_REG=Back up Registry during incremental backup
# 24041
DSI_PREFERB_BACKUP_AFSMOUNT=Back up only AFS mount point information
# 24042
DSI_PREFERB_BACKUP_DFSMOUNT=Back up only DFS mount point information
# 24043
DSI_PREFERB_BACKUP_SYMLINK=Back up the file/directory that a symbolic link points to
# 24044
DSI_PREFERB_ARCHIVE_SYMLINK=Archive the file/directory that a symbolic link points to
# 24045
DSI_PREFERB_VIRTUAL_MOUNT=Virtual Mount Point
# 24046
DSI_PREFERB_DOMAIN_GROUP=Domain for Backup
# 24047
DSI_PREFERB_BACKUP_TYPE=Backup Type
# 24048
DSI_PREFERB_ALL_LOCAL=Back up all local file systems
# 24049
DSI_PREFERB_ALL_LOFS=Back up all Loopback Virtual File Systems
# 24050
DSI_PREFERB_DOMAIN_LIST=Domain List
# 24051
DSI_PREFERV_DIR=Virtual Mount Directory
# 24052
DSI_PREFERV_MOUNT_POINTS=Virtual Mount Points
# 24053
DSI_PREFERD_CRASH_DUMP_DIR=Crash Dump Location
# 24054
DSI_PREFERB_DOMAIN_GROUP_DESCRIPTION=The following contains options that you can select to specify which drives to include in your client domain. By default all local files are backed up.
# 24055
DSI_PREFERI_INCLEXCL_TITLE=Include-Exclude
# 24056
DSI_PREFERB_DOMAIN_GROUP_CLUS_DESCRIPTION=The following contains options that you can select to specify which drives to include in your client domain. At least one drive needs to be selected before continuing to the next panel.
# 24057
DSI_PREFERI_DFSINCLEXCL=Use DFS include-exclude options file
# 24058
DSI_PREFERI_DEFINE=Define Include-Exclude Options
# 24059
DSI_PREFERI_CATEGORY=Category
# 24060
DSI_PREFERI_TYPE=Type
# 24061
DSI_PREFERI_FILE_OR_PATTERN=File or Pattern
# 24062
DSI_PREFERI_MODIFY=Modify Include-Exclude Options
# 24063
DSI_PREFERI_MGMTCLASS=Management Class
# 24064
DSI_PREFERI_STATEMENTS=Statements
# 24065
DSI_PREFERW_CADMODE=Managed Services Options
# 24067
DSI_PREFERW_CADMODE_SCHED=Schedule
# 24068
DSI_PREFERW_CADMODE_BOTH=Both
# 24069
DSI_PREFERC_GEN_TCPIPv6_OPT=TCP/IP v6 Options
# 24070
DSI_PREFERC_GEN_TCPIP_OPT=TCP/IP Options
# 24071
DSI_JOURNALWIZ_PATHNOTABSOLUTE=The path entered is not an absolute path. Please enter a full path.
# 24076
DSI_PREFERC_GEN_NAMEDPIPE_OPT=Named Pipe Options
# 24077
DSI_PREFERC_GEN_SHAREDMEMORY_OPT=Shared Memory Options
# 24080
DSI_PREFERH_CHECK_THRESHOLDS=Check Space Usage Interval
# 24081
DSI_PREFERH_RECONCILE_INTERVAL=File Systems Reconcile Interval
# 24086
DSI_PREFERH_MIGFILE_EXP=Keeps Migrated and Premigrated Files for
# 24087
DSI_PREFERH_OPTION_FORMAT=Option Format for Commands
# 24088
DSI_PREFERH_KERNEL_MSG=Display messages sent by the kernel
# 24089
DSI_PREFERH_RESTORE_MIGSTATE=Restore or retrieve files to stub files
# 24095
DSI_PREFERG_RETURN_TO_TREE=Return to tree window after function completed
# 24096
DSI_PREFERG_NTFS_SECURITY=Back up or restore NTFS security information
# 24097
DSI_PREFERG_SERVER_OPTIONS=Server Options
# 24098
DSI_PREFERG_SERVER_NAME=Server Name
# 24099
DSI_PREFERG_DEFAULT_SERVER=Default Server Name
# 24100
DSI_PREFERG_MIG_SERVER_NAME=Migration Server Name
# 24101
DSI_PREFER_BROWSE=Browse...
# 24102
DSI_PREFER_SELECT=Select...
# 24104
DSI_PREFER_CHANGE=Change
# 24105
DSI_PREFER_UPDATE=Update
# 24106
DSI_PREFER_REMOVE=Remove
# 24107
DSI_PREFER_MOVEUP=Move Up
# 24108
DSI_PREFER_MOVEDOWN=Move Down
# 24109
DSI_PREFER_PREVIEW=Preview...
# 24110
DSI_PREFER_DEFINE=Define...
# 24111
DSI_PREFER_MINUTES=Minutes
# 24112
DSI_PREFER_SECONDS=Seconds
# 24113
DSI_PREFER_KB=KB
# 24114
DSI_PREFER_SELECT_DIR=Select Directory
# 24117
DSI_CFGWIZ_TITLE=TSM Client Configuration Wizard
# 24119
DSI_CFGWIZ_BACHECKBOX=Help me configure the TSM Client Options File
# 24120
DSI_CFGWIZ_WEBCHECKBOX=Help me configure the TSM Web Client
# 24121
DSI_CFGWIZ_SCHEDCHECKBOX=Help me configure the TSM Client Scheduler
# 24130
DSI_PREFER_SELECT_DUMP_DIR=Specify a directory where core or dump file will be stored
# 24133
DSI_CFGWIZ_COMMO_RADIO_USEDIRECTORY=Use Active Directory to locate the TSM server
# 24158
DSI_CFGWIZ_NAMEDPIPE_INSTRUCT=Which Named Pipe options is the server using?
# 24162
DSI_SCHWIZ_TASK_INSTALL=Install a new or additional scheduler
# 24163
DSI_SCHWIZ_TASK_UPDATE=Update a previously installed scheduler
# 24164
DSI_SCHWIZ_TASK_REMOVE=Remove a previously installed scheduler
# 24194
DSI_CFGWIZ_LISTS_INCLEXCL=Include/exclude list
# 24203
DSI_WEBWIZ_INTRO_INSTALL=Install a new Web Client agent
# 24204
DSI_WEBWIZ_INTRO_UPDATE=Update a previously installed Web Client agent
# 24205
DSI_WEBWIZ_INTRO_REMOVE=Remove a previously installed Web Client agent
# 24206
DSI_WEBWIZ_PARAM_TITLE=Web Client options
# 24207
DSI_WEBWIZ_PARAM_PORT=Which port number should be used for HTTP communication with the Web Client Acceptor?
# 24208
DSI_WEBWIZ_PARAM_REVOKEACC=Do you wish to revoke remote access privileges to the Web Client?
# 24215
DSI_PREFERS_SCHED_CMD_PREVENT=Prevent Administrator defined Scheduled Operating System commands from executing
# 24221
DSI_PREFERS_SCHED_RESTRETR_PREVENT=Prevent Administrator defined Scheduled Restore/Retrieve operations from executing
# 24227
DSI_PREFERS_PREVENT_ADMIN=Prevent the following Administrator defined Commands from executing:
# 24230
DSI_PREFERS_SRV_PREPOST=Preschedule and Postschedule commands
# 24231
DSI_PREFERH_HSM_TITLE=HSM
# 24232
DSI_PREFERH_OPTION_LONG=Long
# 24233
DSI_PREFERH_OPTION_SHORT=Short
# 24234
DSI_PREFEI_INCLUDE=Include
# 24235
DSI_PREFEI_EXCLUDE=Exclude
# 24236
DSI_PREFEI_NONE=
# 24237
DSI_PREFEI_ARCHIVE=Archive
# 24238
DSI_PREFEI_BACKUP=Backup
# 24247
DSI_CFGWIZ_OPTFILETASK_STATIC_INSTRUCTION=Which task do you wish to perform?
# 24248
DSI_CFGWIZ_OPTFILETASK_CREATE=Create a new options file
# 24249
DSI_CFGWIZ_OPTFILETASK_IMPORT=Import an existing options file for use
# 24250
DSI_CFGWIZ_OPTFILETASK_UPDATE=Update my options file
# 24251
DSI_PREFERA_SEND_PASSWORD_PROG=Send password to program
# 24252
DSI_PREFERA_SEND_PASSWORD_ID=Send password to user ID
# 24253
DSI_PREFERA_SEND_PASSWORD_BROWSE=Browse
# 24254
DSI_PREFERA_USERS=Users
# 24255
DSI_PREFERA_GROUPS=Groups
# 24256
DSI_PREFERA_SELECT_USER=Select user from list
# 24257
DSI_EVENTBACK_APPLICATIONCHECK=Application Event
# 24258
DSI_EVENTBACK_SECURITYCHECK=Security Event
# 24259
DSI_EVENTBACK_SYSTEMCHECK=System Event
# 24267
DSW_REGBACK_SAMCHECK=Security Accounts Manager Database
# 24268
DSW_REGBACK_SECPOLICY=Security Policy Database
# 24269
DSW_REGBACK_SOFTCONF=Local Machine Software Configuration
# 24270
DSW_REGBACK_SYSCONF=Local Machine System Configuration
# 24271
DSW_REGBACK_DEFPROFILE=Default User Profile
# 24272
DSW_REGBACK_CURPROFILE=Current User Profile
# 24273
DSI_RESTDST_RESTORE_EVTLOG_TO=Restore Event Log to
# 24274
DSI_RESTDST_FSEL_SELECT_DIR_EVTLOG=Select Event Log Destination Directory
# 24275
DSI_BSLOC_TITLE_STATIC=Specify backup set location
# 24276
DSI_GENERIC_FILENAME_PROMPT=File name:
# 24277
DSI_INACTIVE_SYSOBJ_Warning=Warning! Restoring individual, inactive System Objects is not recommended \n\nDo you wish to continue? \n
# 24278
DSI_GENERIC_BROWSEDOTDOTDOT=Browse...
# 24279
DSI_BSLOC_FILE_SELECT_TITLE=Backup Set File Name
# 24280
DSI_PREFER_EDIT=Edit..
# 24281
DSI_SETUP_BACK=< Back
# 24282
DSI_SETUP_NEXT=Next >
# 24283
DSI_RESTART_RSM_Question=Do you want to restart RSM service now? If not, you need to restart RSM later for changes to become effective.
# 24284
DSI_ACTIVATE_REG_Question=Do you want to activate the registry key(s) after the restore?
# 24285
DSI_SETUP_FINISH=Finish
# 24286
DSI_INACTIVE_SYSSERVICE_Warning=Warning! Restoring individual, inactive System Service is not recommended \n\nDo you wish to continue? \n
# 24289
DSI_DEVICENAME_OTHER=Tape name:
# 24290
DSI_ACTIVE_PERFORMANCE=Performance
# 24291
DSI_ACTIVE_XFER_RATE=Transfer Rate
# 24292
DSI_ACTIVE_OBJECT_COUNT=Object Count
# 24293
DSI_ACTIVE_BACKUP_HEADER=Detailed Status Report
# 24294
DSI_TASK_LIST=Task List
# 24295
DSI_ARCHDEL_ARCHDEL=Archive Delete
# 24296
DSI_RACTIVE_RESTORE_HEADER=Detailed Status Report
# 24300
DSI_BACKDEL_BACKDEL=Backup Delete
# 24314
DSI_PREFERB_ALL_NFS=Back up all network file systems
# 24315
DSI_PREFERB_ALL_AUTO_LOFS=Back up all automounted Loopback Virtual File systems
# 24316
DSI_PREFERB_ALL_AUTO_NFS=Back up all automounted network file systems
# 24317
DSI_PREFERS_SRV_PREPOST_PREVENT=Prevent Administrator defined Preschedule and Postschedule commands from executing
# 24318
CLI_Rest_Image_Larger=The destination volume is larger than the source volume. This will reduce \nthe file system '{0}' size to '{1}'. \nDo you wish to continue?
# 24319
DSI_PREFEI_HSM=HSM
# 24320
DSI_Rest_Image_FBFWarning=Cannot get exclusive lock of file system '{0}'. \nFile by file restore will be used instead of image restore. \nDo you wish to continue?
# 24321
DSI_SCHWIZ_NAMELOCNT_NAME=What name would you like to give to the TSM scheduler?
# 24322
DSI_SCHWIZ_NAMELOCNT_LOCREM=Do you wish to install the scheduler on your local machine or a remote machine?
# 24323
DSI_SCHWIZ_NAMELOCNT_LOCAL=Local Machine
# 24324
DSI_SCHWIZ_NAMELOCNT_REMOTE=Remote Machine
# 24325
DSI_SCHWIZ_REMOTE_TITLE=Remote machine options
# 24326
DSI_SCHWIZ_REMOTE_MACHINE=What is the name of the remote machine on which to install the scheduler?
# 24330
DSI_SCHWIZ_REMOTE_REPLACE=Replace existing installation files on remote machine
# 24331
DSI_SCHWIZ_LOGFILES_TITLE=Log file names and locations
# 24333
DSI_SCHWIZ_FILES_LOGGING=Enable event logging
# 24334
DSI_SCHWIZ_SCHEDLOG_NAME=Specify the file names and locations of your client schedule log and error log files
# 24335
DSI_SCHWIZ_ERRLOG_NAME=Specify the client error log file that should be used
# 24337
DSI_SCHWIZ_SVCLOGIN_MANUAL=Manually when I explicitly start the service
# 24338
DSI_SCHWIZ_SVCLOGIN_AUTO=Automatically when Windows boots
# 24339
DSI_SCHWIZ_SVCLOGIN_SYSACCT=The System account
# 24340
DSI_SCHWIZ_SVCLOGIN_THISACCT=This account
# 24343
DSI_SCHWIZ_SVCLOGIN_TITLE=Service login options
# 24345
DSI_SCHWIZ_SVCLOGIN_STARTUP_TITLE=When do you want the service to start?
# 24349
DSI_SCHWIZ_NAMELOCNT_CADMODESCHED=Use the Client Acceptor daemon (CAD) to manage the scheduler
# 24354
DSI_SCHWIZ_REMOTE_PATH=Where would you like to install it on this remote machine?
# 24381
DSI_WEBWIZ_NAME_TITLE=Select the names of the Web services
# 24382
DSI_WEBWIZ_NAME_ACCEPTOR_STATIC=What name would you like to give to the TSM acceptor?
# 24383
DSI_WEBWIZ_NAME_AGENT_STATIC=What name would you like to give to the TSM agent?
# 24401
DSI_IMG_STAC_NOT_IMPLEMENTED=Image function is not implemented.
# 24402
DSI_JOURNALWIZ_NOTIFY_INSTRUCT=Select the notification filters to monitor for file system {0}
# 24403
DSI_DPREFVM_VMBACKUP_BACKUP_TYPE_LABEL=Backup Type
# 24404
DSI_IMG_STAC_LOW_RESOURCES=Image insufficient resources.
# 24407
DSI_IMG_STAC_ITEM_NOT_FOUND=Image item not found.
# 24408
DSI_IMG_STAC_ALREADY_INITIALIZED=Image: An attempt was made to initialize RDRC or one of its components more than once.
# 24409
DSI_IMG_STAC_INTERNAL=Image internal error.
# 24410
DSI_IMG_STAC_ABORTED=Image operation aborted.
# 24411
DSI_IMG_STAC_NOTIFY_SUBTREE_CHANGED=Image subtree changed.
# 24412
DSI_IMG_STAC_INCOMPATIBLE_VERSION=Image incompatible version.
# 24413
DSI_IMG_STAC_NOT_INITIALIZED=Image RDRC is not initialized.
# 24414
DSI_IMG_STAC_OBJECT_IS_USED=Image cannot uninitialize, some object(s) in use.
# 24415
DSI_ARCOPT_V2ARCHIVE=V2 Archive
# 24416
DSI_IMG_STAC_ALREADY_INSTALLED=Image component is already installed.
# 24417
DSI_IMG_STAC_NOT_INSTALLED=Image module is not installed.
# 24418
DSI_IMG_STAC_INVALID_NAME=Image component name is invalid.
# 24419
DSI_IMG_STAC_NOT_REGISTERED=Image component is not registered.
# 24420
DSI_IMG_STAC_BAD_MODULE=Image module does not contain ModuleInitialize().
# 24421
DSI_IMG_STAC_INVALID_PROPERTY=Image invalid object property.
# 24423
DSI_IMG_STAC_CS_BAD_STORAGE=Image configuration storage is bad or corrupted.
# 24424
DSI_IMG_STAC_CS_NOT_INITIALIZED=Image configuration storage is not yet initialized.
# 24425
DSI_IMG_STAC_CS_INITIALIZE_FAILED=Image configuration storage could not be initialized.
# 24426
DSI_JOURNALWIZ_DBLOCATION_INSTRUCT=Specify the location where the Journal Database files will be written for file system {0}
# 24427
DSI_IMG_STAC_CS_NO_VALUE=Image configuration storage item has no value.
# 24428
DSI_IMG_STAC_SA_NO_MORE_DATA=Image no more data in source storage adaptor stream.
# 24429
DSI_IMG_STAC_SA_GENERIC=Image storage adaptor generic error.
# 24430
DSI_IMG_STAC_CE_READ_ERROR=Image storage adaptor read error.
# 24431
DSI_IMG_STAC_CE_WRITE_ERROR=Image storage adaptor write error.
# 24432
DSI_PREFEI_EXCLUDE_RESTORE=Exclude.Restore
# 24433
DSI_PREFEI_RESTORE=Restore
# 24434
DSI_IMG_STAC_CE_SEEK_ERROR=Image storage adaptor seek error.
# 24435
DSI_IMG_STAC_CE_COPY_OPERATION_COMPLETE=Image copy operation completed.
# 24436
DSI_IMG_STAC_PM_ALREADY_REGISTERED=Image specified item already registered.
# 24437
DSI_PREFEI_EXCLUDE_COMPRESS=Exclude.Compression
# 24438
DSI_PREFEI_INCLUDE_COMPRESS=Include.Compression
# 24439
DSI_PREFEI_EXCLUDE_SUBFILE=Exclude.Subfile
# 24440
DSI_PREFEI_INCLUDE_SUBFILE=Include.Subfile
# 24441
DSI_PREFEI_INCLUDE_SYSOBJ=Include.SystemObject
# 24442
DSI_PREFERB_INCR_THRESHOLD=Threshold for non-journal incremental backup
# 24443
DSI_CFGWIZ_JOURNALCHECKBOX=Help me configure the TSM Journal Engine
# 24444
DSI_JOURNALWIZ_TASK_TITLE=TSM Journal Engine Wizard
# 24445
DSI_JOURNALWIZ_TASK_TASK=Which task do you wish to perform?
# 24446
DSI_JOURNALWIZ_TASK_INSTALL=Install a new TSM Journal Engine
# 24447
DSI_JOURNALWIZ_TASK_UPDATE=Update a previously installed TSM Journal Engine
# 24448
DSI_JOURNALWIZ_TASK_REMOVE=Remove a previously installed TSM Journal Engine
# 24449
DSI_JOURNALWIZ_FSLIST_TITLE=Journaled File Systems
# 24450
DSI_JOURNALWIZ_FSLIST_INSTRUCT=Specify the file systems to be monitored for journaling
# 24451
DSI_JOURNALWIZ_FSLIST_ALL_LOCAL=Journal all local file systems
# 24452
DSI_JOURNALWIZ_FSLIST_JFSLIST=Journaled File Systems
# 24453
DSI_JOURNALWIZ_SPECIFY_JFS=Please select one or more file systems to be monitored for journaling.
# 24454
DSI_JOURNALWIZ_PARAMS_TITLE=Journal Database Location
# 24456
DSI_JOURNALWIZ_DBSIZE_TITLE=Journal Database Maximum Size
# 24457
DSI_JOURNALWIZ_DBSIZE_INSTRUCT=Specify the maximum size of the Journal Database for file system {0}
# 24458
DSI_JOURNALWIZ_DBSIZE_NOLIMIT=Do not limit the size of the Journal Database
# 24460
DSI_JOURNALWIZ_INSTALL_SUCCESS=Journal Engine successfully installed
# 24461
DSI_JOURNALWIZ_UPDATE_SUCCESS=Journal Engine successfully updated
# 24462
DSI_JOURNALWIZ_REMOVE_SUCCESS=Journal Engine successfully removed
# 24468
DSI_JOURNALWIZ_PARAMS_JFSLOCATION2=Use this directory name on each Journal Filesystem
# 24469
DSI_JOURNALWIZ_INIFILENOTFOUND=Configuration file '{0}' not found
# 24470
DSI_JOURNALWIZ_DIRNOTFOUND=Directory '{0}' not found. Do you want to create it now?
# 24471
DSI_JOURNALWIZ_DIRERROR=Unable to create directory '{0}'. Please use a different path and try again.
# 24472
DSI_JOURNALWIZ_NOTIFY_TITLE=Journal Notification Configuration
# 24473
DSI_JOURNALWIZ_NOTIFY_GROUPBOX=Notification Filters
# 24474
DSI_JOURNALWIZ_NOTIFY_CDRCB=Delete
# 24475
DSI_JOURNALWIZ_NOTIFY_FILECB=File Size
# 24476
DSI_JOURNALWIZ_NOTIFY_ACCESSEDCB=Last Accessed Timestamp
# 24477
DSI_JOURNALWIZ_NOTIFY_MODIFIEDCB=Last Modified Timestamp
# 24478
DSI_JOURNALWIZ_NOTIFY_ATTRIBUTESCB=Attributes
# 24479
DSI_JOURNALWIZ_NOTIFY_NTFSCB=NTFS Security
# 24480
DSI_PREFEI_INCLUDE_SYSSTATE=Include.SystemState
# 24481
DSI_PREFEI_EXCLUDE_SYSTEMSERVICE=Exclude.SystemService
# 24482
DSI_JOURNALWIZ_PARAMS_PATH=Use this path for all Journal Database files
# 24486
DSI_LVSAWIZ_TASK_REMOVE=Remove the TSM Logical Volume Snapshot Agent
# 24487
DSI_SNAPWIZ_OFS_CONFIG_SUCCESS=Open file support successfully configured. \nThe machine must be rebooted for the changes to take effect.
# 24489
DSI_SNAPWIZ_IMAGE_CONFIG_SUCCESS=Online image support successfully configured. \nThe machine must be rebooted for the changes to take effect.
# 24492
DSI_CFGWIZ_OFS_CHECKBOX=Help me configure Open File Support
# 24493
DSI_SNAPWIZ_OFS_CONFIG_SUCCESS_NO_REBOOT=Open file support successfully configured.
# 24495
DSI_CFGWIZ_ONLINE_IMAGE_CHECKBOX=Help me configure 'Online' Image Support
# 24500
DSI_SNAPWIZ_IMAGE_CONFIG_SUCCESS_NO_REBOOT=Online image support successfully configured
# 24502
DSI_WIZ_WHEN_START_STATIC=Would you like to start the service upon completion of this wizard?
# 24511
DSI_PREFS_SNAP_PROVIDER_VSS=VSS
# 24512
DSI_PREFS_SNAP_PROVIDER_LVSA=LVSA
# 24516
DSI_DPREFVM_VMBACKUP_VMBACKUP_GROUP_LABEL=VM Backup Options
# 24517
DSI_DPREFVM_VMBACKUP_VMLIST_LABEL=VM List
# 24518
DSI_DPREFVM_VMBACKUP_VMCONTROL_GROUP_LABEL=VMware Virtual Center or ESX Server
# 24519
DSI_DPREFVM_VMBACKUP_VCHOST_LABEL=Host
# 24520
DSI_DPREFVM_VMBACKUP_VCUSER_LABEL=User
# 24521
DSI_DPREFVM_VMBACKUP_VCPASSWORD_LABEL=Password
# 24524
DSI_PREFERVM_VMBACKUP=VM Backup
# 24525
DSI_VM_BACKUP_PREFERENCES=Virtual Machine Backup Preferences
# 24526
DSI_DPREFVM_VMBACKUP_BACKUP_DIR_LABEL=Virtual Machine Backup Options
# 24527
DSI_DPREFVM_VMBACKUP_FULL_IMAGE_LABEL=VMWare Full VM
# 24528
DSI_DPREFVM_VMBACKUP_DS_LOC_LABEL=Temporary Staging Directory
# 24529
DSI_DPREFVM_VMBACKUP_NO_DELETE_LABEL=Save local copy of Full VM files in datastore after backup
# 24530
DSI_DPREFVM_VMBACKUP_STAGING_AREA_LABEL=VMWare Backup Staging Area
# 24531
DSI_WIZARD_ONLINE_IMAGE_TITLE=TSM Online Image Support Wizard
# 24532
DSI_WIZARD_OPEN_FILE_TITLE=TSM Open File Support Wizard
# 24533
DSI_SNAP_PROVIDER_TO_USE=Which snapshot provider do you wish to use?
# 24534
DSI_LVSA_PROVIDER=Logical Volume Snapshot Agent (LVSA)
# 24535
DSI_DISABLE_OFS=None (Disable open file support)
# 24536
DSI_DISABLE_OIS=None (Disable online image support)
# 24537
DSI_UNINSTALL_LVSA=Uninstall the Logical Volume Snapshot Agent (LVSA)?
# 24538
DSI_DPREFVM_VMBACKUP_FILE_LEVEL_LABEL=VMWare File Level
# 24539
DSI_PREFERG_STAGINGDIRECTORY=Staging Directory
# 24540
DSI_PREFERG_CHOOSE_STAGINGDIRECTORY=Choose the Staging Directory name
# 24542
DSI_VSS_PROVIDER=Volume Shadowcopy Services (VSS)
# 24886
DSI_DIR_ERROR_MSG=Encountered error while accessing directory services. rc = {0}.
# 24887
DSI_GENERIC_NOSELECTION_MSG=No item selected.
# 24891
DSI_COMMDIR_LISTCOL_SERVERNAME=Name
# 24892
DSI_COMMDIR_LISTCOL_TCPIP_ADDR=TCP/IP Address
# 24893
DSI_COMMDIR_LISTCOL_TCPIP_PORT=Port #
# 24896
DSI_COMMDIR_LISTCOL_NP_NAME=Named Pipe Name
# 24897
DSI_PREFEI_EXCLUDE_ATTRIB_SYMLINK=Exclude.Attribute.Symlink
# 24898
DSI_PREFEI_INCLUDE_ATTRIB_SYMLINK=Include.Attribute.Symlink
# 24899
DSI_PREFEI_INCLUDE_ARCHIVE=Include.Archive
# 24900
DSI_PREFEI_EXCLUDE_DIR=Exclude.Dir
# 24901
DSI_PREFEI_EXCLUDE_FILE=Exclude.File
# 24902
DSI_PREFEI_EXCLUDE_FS=Exclude.Fs
# 24903
DSI_PREFEI_INCLUDE_BACKUP=Include.Backup
# 24904
DSI_PREFEI_INCLUDE_IMAGE=Include.Image
# 24905
DSI_PREFEI_EXCLUDE_BACKUP=Exclude.Backup
# 24906
DSI_PREFEI_EXCLUDE_FILE_BACKUP=Exclude.File.Backup
# 24907
DSI_PREFEI_EXCLUDE_IMAGE=Exclude.Image
# 24908
DSI_PREFEI_INCLUDE_FILE=Include.File
# 24909
DSI_PREFEI_EXCLUDE_FILE_SPACEMGMT=Exclude.File.Spacemgmt
# 24910
DSI_PREFEI_EXCLUDE_SPACEMGMT=Exclude.Spacemgmt
# 24940
DSI_PREFEI_EXCLUDE_SYSTEMOBJECT=Exclude.SystemObject
# 24950
DSI_CONN_FS_FRS=FRS
# 24951
DSI_CONN_FS_SYSTEMFILES=System Files
# 24952
DSI_CONN_FS_DRCDIMAGE=Disaster Recovery CD Image
# 24964
DSI_PREFERA_ENCRYPTION_PROMPT=Prompt for encryption key password
# 24965
DSI_PREFERA_ENCRYPTION_SAVE=Save encryption key password locally
# 24966
DSI_PREFERA_ENCRYPTION_GROUP=Encryption Key Password
# 24967
DSI_PREFEI_EXCLUDE_ENCRYPTION=Exclude.Encryption
# 24968
DSI_PREFEI_INCLUDE_ENCRYPTION=Include.Encryption
# 24969
DSI_DPREFB_SUB_FILE_GROUP=Adaptive sub-file backup
# 24982
DSI_PREFEI_EXCLUDE_ARCHIVE=Exclude.Archive
# 24983
DSI_PREFEI_INCLEXCL_CATAGORY=Include Exclude File
# 24984
DSI_PREFEI_INCLEXCL_TYPE=INCLEXCL
# 24985
DSI_BackChoice_NasFull=Full
# 24986
DSI_BackChoice_NasDiff=Differential
# 24987
DSI_OBJINFO_TYPE_VOLUME_NAS=Network Attached Storage Filespace
# 24988
DSI_OBJINFO_TYPE_ROOT=Root Node
# 24989
DSI_OBJINFO_TYPE_NAS_MACHINE=Network Attached Storage Machine
# 24998
DSI_SHOW_ALL_SERVERS_MSG=Show all servers
# 25537
DSI_WAS_MACHINE_LABEL=WebSphere Application Server
# 25538
DSI_WAS_NDNODE_LABEL=Network Deployment Manager
# 25539
DSI_WAS_APPNODE_LABEL=Application Server
# 25540
DSI_WAS_RESTOREFILE_WARNING=WARNING! Restoring data other than at the group level can corrupt your WebSphere installation. It is strongly recommended that you restore data at the Network Deployment Manager node or Application Server node level only. Do you want to continue?
# 25559
DSI_PREFERA_ENCRYPTION_GENERATE=Generate encryption key password
# 25840
AD_Object_Restored='{0}' restored.\n
# 25841
AD_Object_Exists_Replace=Object '{0}' exists\n
# 25842
AD_Database_Query_Confirmation=You are about to query the content of the Active Directory database that was backed up to the Tivoli Storage Manager server. The database must be restored first and the process may take a long time to restore depending on the size of the database. Do you wish to proceed?\n
# 25843
AD_Database_Query_Date_Confirm=You are about to query the content of the Active Directory database that was backed up on {0} to the Tivoli Storage Manager server. The database must be restored first and the process may take a long time to restore depending on the size of the database. Do you wish to proceed?\n
# 25844
DSI_PREFER_FSIDLE_WAIT_MIN_GREATER=Error: The value for option '{0}' should be smaller then the value for option '{1}'.
# 25845
AD_Database_Opening=Opening the restored Active Directory database...\n
# 25846
DSI_PREFERVM_DOMAIN_VMBACKUP=Domain for VM Backup
# 25847
DSI_PREFERVM_DOMAIN_VMBACKUP_TYPES=Domain Backup Types
# 25848
DSI_PREFERVM_DOMAIN_VMBACKUP_OPT=VM Options
# 25849
DSI_PREFERVM_VMBACKUP_HOST_FOLDER_VM=VM host, VM host cluster, VM folder, VM datastore or VM name
# 25850
DSI_PREFERVM_VMBACKUP_INSERT=Insert
# 25851
DSI_PREFERVM_DOMAIN_VMBACKUP_FILE=Domain File Level VM
# 25852
DSI_PREFERVM_DOMAIN_VMBACKUP_FULL=Domain Full VM
# 25857
DSI_DEDUP=Deduplication
# 25858
DSI_DEDUP_PREFERENCES=Deduplication Preferences
# 25859
DSI_DEDUP_OPTIONS=Deduplication Options
# 25860
DSI_ENABLE_DEDUP=Enable Deduplication
# 25861
DSI_DEDUP_CACHE=Deduplication Cache
# 25862
DSI_ENABLE_DEDUP_CACHE=Enable Deduplication Cache
# 25863
DSI_DEDUP_CACHE_LOCATION=Deduplication Cache Location
# 25872
DSJ_OBJECT_TYPE_LABEL=Object Type
# 30000
DSI_PREFERG_GENERAL_FDA_DESC=Use this tab to set general processing options for the client.
# 30001
DSI_PREFERG_NODE_NAME_FDA_DESC=The node name is a unique name used to identify your client node to the server when you begin a client session. Type the name of your client node to identify your node to the server.
# 30002
DSI_PREFERG_ERROR_FILE_FDA_DESC=In the General Preferences tab, this field contains the name and location of the error log file. In the Scheduler Preferences tab, this field contains the name and location of the schedule log file.
# 30003
DSI_PREFERG_SERVER_NAME_FDA_DESC=This field displays the name of the Tivoli Storage Manager server with which you are in a session.
# 30004
DSI_PREFERG_DEFAULT_SERVER_FDA_DESC=This field displays the name of the default server.
# 30005
DSI_PREFERG_MIG_SERVER_NAME_FDA_DESC=Displays the name of the server to which your files are migrated during HSM operations if the HSM client is installed on your workstation.
# 30006
DSI_PREFERG_PROMPT_TAPES_FDA_DESC=Select this check box if you want the client to prompt you to choose whether to wait for a tape to mount if it is required for a backup, archive, restore, or retrieve process.
# 30007
DSI_PREFERG_RETURN_TO_TREE_FDA_DESC=Select this check box to display the tree window after a task is finished. If this check box is clear, the main Tivoli Storage Manager window appears after the end of a task.
# 30008
DSI_PREFERG_ENABLE_LANFREE_FDA_DESC=Select this check box to enable an available LAN-free path to and from a SAN-attached storage device for backup, restore, archive, and retrieve operations. When enabled, data transfer between the client and the server-defined storage device is performed over a SAN and bypasses the LAN.
# 30009
DSI_PREFERG_SAVE_PRUNED_FDA_DESC=Select this check box to save the pruned entries in a separate file. Pruned error log entries are saved in the dsmerlog.pru file. Pruned schedule log entries are saved in the dsmsched.pru file.
# 30010
DSI_PREFERG_BYTES_PER_TRANS_FDA_DESC=Specify the maximum size of each transaction exchanged between the Tivoli Storage Manager client and server.
# 30011
DSI_PREFERG_KEEP_ENTRIES_FDA_DESC=Specify how long you want to keep the log entries before they are deleted from the log.
# 30012
DSI_PREFERG_KEEP_ENTRIES_FORMAT_FDA_DESC=Specify how long you want to keep the log entries before they are deleted from the log.
# 30013
DSI_PREFERG_BYTES_PER_TRANS_FORMAT_FDA_DESC=Specify the maximum size of each transaction exchanged between the Tivoli Storage Manager client and server.
# 30014
DSI_PREFERG_ERROR_LOG_KEEP_ENTRIES_FORMAT_FDA_DESC=Specify how long you want to keep the log entries before they are deleted from the log.
# 30015
DSI_PREFERG_ERROR_LOG_BROWSE_FDA_DESC=Click this button to open a file or directory selection window. Find the directory or file you want, select it, and click OK.
# 30016
DSI_PREFERB_BACKUP_FDA_DESC=Use this tab to set backup processing options.
# 30017
DSI_PREFERB_COMPRESS_OBJECTS_FDA_DESC=Select this check box to compress objects before sending them to the server.
# 30018
DSI_PREFERB_CONTINUE_GROW_FDA_DESC=Select this check box to compress objects even if compression increases the size of the object.
# 30019
DSI_PREFERB_ARCHIVE_SYMLINK_FDA_DESC=Select this check box to archive the file or directory that a symbolic link points to. On AIX operating systems, any AIX JFS2 extended attributes of the target of the symbolic link are also archived. If you do not select this check box, only the symbolic link is archived.
# 30020
DSI_PREFERB_MEMORY_EFFICIENT_FDA_DESC=Select this option to use less memory during file system incremental backups. When selected, the client backs up data one directory at a time. This uses less memory but takes longer to complete.
# 30021
DSI_PREFERB_ALL_LOCAL_FDA_DESC=Select this check box to include all local file systems (except local removable drives such as CD-ROM or floppy drives) for the selected Backup Type.
# 30022
DSI_PREFERB_ALL_LOFS_FDA_DESC=Select this check box to include all Loopback Virtual File Systems (LVFS) in the client domain for the Backup Type that you selected. This does not include the file systems handled by an automounter daemon.
# 30023
DSI_PREFERB_ALL_AUTO_LOFS_FDA_DESC=Select this check box to include all automounted Loopback Virtual File Systems (LVFS) in the client domain for the Backup Type that you selected. The automounted loopback file systems are handled by an automounter daemon.
# 30024
DSI_PREFERB_ALL_AUTO_NFS_FDA_DESC=Select this check box to include all automounted network file systems in the client domain for the Backup Type that you selected. The automounted network file systems are handled by an automounter daemon.
# 30025
DSI_PREFERB_ALL_NFS_FDA_DESC=Select this check box to include all network file systems in the client domain for the Backup Type that you selected. This does not include the file systems that are handled by an automounter daemon.
# 30026
DSI_PREFERB_RETRY_IF_CHANGES_FDA_DESC=Specify the number of times you want to retry a back up or archive operation when an object is in use. You can click the up or down arrows to change the value.
# 30027
DSI_PREFERB_DOMAIN_LIST_FDA_DESC=Select the file systems that you want to include in your client domain for incremental backup or image backup.
# 30028
DSI_PREFERB_VIRTUAL_MOUNT_FDA_DESC=This field displays a list of virtual mount points. A virtual mount point is a specific directory within a file system that represents the starting location in which you want the client to consider files for backup.
# 30029
DSI_PREFERB_VIRTUAL_MOUNT_ADD_FDA_DESC=Click this button to add a virtual mount point. The Choose Virtual Mount Point dialog appears.
# 30030
DSI_PREFERB_VIRTUAL_MOUNT_REMOVE_FDA_DESC=Click this button to delete the selected item in the Virtual Mount Points list box.
# 30031
DSI_PREFERR_RESTORE_FDA_DESC=Use this tab to set restore processing options.
# 30032
DSI_PREFERR_FILE_EXISTS_FDA_DESC=Use this tab to set restore processing options.
# 30033
DSI_PREFERR_SHOW_PROMPT_FDA_DESC=Select this option to have the client prompt you to choose whether to replace an existing file on your computer when it restores or retrieves a file from the server.
# 30034
DSI_PREFERR_LEAVE_INTACT_FDA_DESC=Select this option to choose not to replace any existing files on your computer with files from the server.
# 30035
DSI_PREFERR_REPLACE_EXISTING_FDA_DESC=Select this option to replace existing files on your computer with the files from the server.
# 30036
DSI_PREFERI_STATEMENT_LIST_FDA_DESC=The Statement List contains statements for include-exclude processing that determines which files can be backed up and the associated management classes to use for the backup or archive.
# 30037
DSI_PREFERI_INCLEXCL_TITLE_FDA_DESC=Use this tab to specify include-exclude processing options.
# 30038
DSI_PREFERI_TYPE_FDA_DESC=Select an option type to specify the include or exclude option for the function that you selected in the Category drop-down list. The include or exclude options that are available depend on what you selected in the Category list.
# 30039
DSI_PREFERI_MGMTCLASS_FDA_DESC=Select an item from this list to assign a management class to the files or directories specified in the File or Pattern field. Applies only to include statements.
# 30040
DSI_PREFERI_FILE_OR_PATTERN_FDA_DESC=Type a file name or a pattern or click Browse to open a file selection window and select a file.
# 30041
DSI_PREFERI_MODIFY_FDA_DESC=Click this button to open the Define Include-Exclude Options window to update the options in an include or exclude statement.
# 30042
DSI_PREFERI_INCLUDE_EXCLUDE_DEFINE=Use this window to specify the options for an include-exclude statement. The options that you specify are put in an include or exclude statement that is displayed in the Statement List in the Include-Exclude Preferences window.
# 30043
DSI_PREFERS_SCHEDULE_FDA_DESC=Use the Scheduler tab to specify processing options for scheduled work.
# 30044
DSI_PREFERS_POLLING_FDA_DESC=Click Polling to specify that your client periodically asks the server for scheduled work.
# 30045
DSI_PREFERS_PROMPTED_FDA_DESC=Click this option to specify that the server contact your client when it is time to start a scheduled operation.
# 30046
DSI_PREFERS_QUERY_SCHEDULE_FDA_DESC=Set the amount of time you want the client scheduler to wait between attempts to contact the server for scheduled work.
# 30047
DSI_PREFERS_TCP_ADDRESS_FDA_DESC=Type a TCP/IP address in this field. Use this field if your client node has more than one address and you want the server to contact an address different from the address that made initial contact with the server.
# 30048
DSI_PREFERS_TCP_PORT_FDA_DESC=Type a TCP/IP port number in this field. This field specifies a TCP/IP number for the server to contact the client when the server begins the server prompted scheduled operation.
# 30049
DSI_PREFERS_RETRY_PERIOD_FDA_DESC=Type the amount of time the client scheduler waits between attempts to process a scheduled command in this field.
# 30050
DSI_PREFERS_CMD_RETRIES_FDA_DESC=Type the number of times you want your client to retry a scheduled command that fails in this field.
# 30051
DSI_PREFERS_SCHEDULE_LOG_FDA_DESC=In the General Preferences tab, this field contains the name and location of the error log file. In the Scheduler Preferences tab, this field contains the name and location of the schedule log file.
# 30052
DSI_PREFERS_SCHEDULE_CMD_FDA_DESC=Type the command that you want to run before the client starts scheduled processing. For example, you may want to quiesce a database before scheduled processing begins.
# 30053
DSI_PREFERS_PRESCHEDULE_FDA_DESC=Type the command that you want to run before the client starts scheduled processing. For example, you may want to quiesce a database before scheduled processing begins.
# 30054
DSI_PREFERS_PREVENT_ANY_PRESCHEDULE_CMD_FDA_DESC=Select this check box to disable any pre-schedule commands that you defined in your client options file.
# 30055
DSI_PREFERS_POSTSCHEDULE_FDA_DESC=Type the command that you want to run after scheduled processing is finished. For example, you may want to restart a database after scheduled processing is complete.
# 30056
DSI_PREFERS_PREVENT_ANY_POSTSCHEDULE_CMD_FDA_DESC=Select this check box to disable any post-schedule commands that you defined in your client options file.
# 30057
DSI_PREFERS_SCHEDCMD_WAIT_FDA_DESC=Select this check box to wait for the command to complete before the client continues processing. This box is active only after you enter text in the command field.
# 30058
DSI_PREFERC_GEN_COMMMETHOD_FDA_DESC=Specify the communication method your client uses to connect to the Tivoli Storage Manager server.
# 30059
DSI_PREFERC_GEN_COMMON_FDA_DESC=Specify the duration for the client to continue attempting to restart a session that was stopped due to error, such as communication failure. The client will keep trying to restart a session for this duration until it connects successfully to the server.
# 30060
DSI_PREFERC_GEN_COMMUNICATION_FDA_DESC=Specify the communication method your client uses to connect to the Tivoli Storage Manager server.
# 30061
DSI_PREFERC_GEN_DURATION_FDA_DESC=Specify the duration for the client to continue attempting to restart a session that was stopped due to error, such as communication failure. The client will keep trying to restart a session for this duration until it connects successfully to the server.
# 30062
DSI_PREFERC_GEN_INTERVAL_FDA_DESC=Specify the amount of time the client should wait before attempting to restart a session that was stopped due to error, such as communication failure.
# 30063
DSI_PREFERC_TCPIP_BUFSIZE_FDA_DESC=Specify a buffer size that you want to use for the internal TCP/IP communication buffer.
# 30064
DSI_PREFERC_TCPIP_NO_DELAY_FDA_DESC=Select this check box to allow successive, small data packets to be sent immediately across the network. The default is selected.
# 30065
DSI_PREFERC_TCPIP_PORT_FDA_DESC=Specify the TCP/IP port number that is used to communicate with the Tivoli Storage Manager server. Obtain the port number from your administrator and type it in the field.
# 30066
DSI_PREFERC_TCPIP_SERVER_ADDR_FDA_DESC=Specify the name or the TCP/IP address of the Tivoli Storage Manager server. Obtain the server address from your administrator and type it in this field.
# 30067
DSI_PREFERC_TCPIP_WINDOW_SIZE_FDA_DESC=Specify the size that you want to use for the TCP/IP sliding window for your client node. Use this field to specify the amount of data that the client receives that can be buffered at one time on a TCP/IP connection.
# 30068
DSI_PREFERC_GEN_SHAREDMEMORY_OPT_FDA_DESC=Specify a port number for the port at which the server is listening to establish a shared memory connection. Shared memory is an area of memory accessible by several processes at the same time. Use shared memory when the client and the Tivoli Storage Manager server or Storage Agent reside on the same system.
# 30069
DSI_PREFERC_GEN_SHMEM_FDA_DESC=Specify a port number for the port at which the server is listening to establish a shared memory connection. Shared memory is an area of memory accessible by several processes at the same time. Use shared memory when the client and the Tivoli Storage Manager server or Storage Agent reside on the same system.
# 30070
DSI_PREFERC_GEN_SHMEM_PORT_FDA_DESC=Specify a port number for the port at which the server is listening to establish a shared memory connection. Shared memory is an area of memory accessible by several processes at the same time. Use shared memory when the client and the Tivoli Storage Manager server or Storage Agent reside on the same system.
# 30071
DSI_PREFERC_NLS_NLS_FDA_DESC=Use this tab to set locale options for your client.
# 30072
DSI_PREFERC_NLS_DATE_FDA_DESC=Select the format you want to use for displaying dates.
# 30073
DSI_PREFERC_NLS_TIME_FDA_DESC=Select the format you want to use for displaying the system time.
# 30074
DSI_PREFERA_AUTHORIZATION_FDA_DESC=Use this tab to specify authorization options for your client.
# 30075
DSI_PREFERA_PASSWORD_ACCESS_FDA_DESC=Click this option to automatically generate a new password each time the password expires.
# 30076
DSI_PREFERA_PASSWORD_PROMPT_FDA_DESC=Select this option to prompt you for your Tivoli Storage Manager password each time a client connects to the server.
# 30077
DSI_PREFERA_PASSWORD_GENERATE_FDA_DESC=Click this option to automatically generate a new password each time the password expires.
# 30078
DSI_PREFERA_PASSWORD_DIR_FDA_DESC=Type the name of a directory in this field to specify the location in which to store an encrypted password file, or click Browse to open a selection window and specify the directory location.
# 30079
DSI_PREFERA_GROUPS_FDA_DESC=The Groups list box contains a list of groups on your workstation. Select the groups that you want to authorize to request services from the server.
# 30080
DSI_PREFERA_USERS_FDA_DESC=The Users list box contains a list of user IDs on your workstation. Select the users whom you want to authorize to request services from the server.
# 30081
DSI_PREFERA_ENCRYPTION_GROUP_FDA_DESC=Click this option if you do not want to locally save the password the client uses to generate the encryption key for encrypting and decrypting file data. Instead, you are prompted for your key with each backup and restore operation. To set the encryption key password, use the Encryption window.
# 30082
DSI_PREFERA_ENCRYPTION_PROMPT_FDA_DESC=Click this option if you do not want to locally save the password the client uses to generate the encryption key for encrypting and decrypting file data. Instead, you are prompted for your key with each backup and restore operation. To set the encryption key password, use the Encryption window.
# 30083
DSI_PREFERA_ENCRYPTION_SAVE_FDA_DESC=Click this option to save your password locally in an encrypted format for backup or restore operations. By selecting this option, you are not prompted for the password with each operation.
# 30084
DSI_PREFERW_CADMODE_FDA_DESC=Select an option from this field to specify which services you want to manage using the Client Acceptor (CAD). You can choose to manage the scheduler, the Web Client, or both the scheduler and the Web Client.
# 30085
DSI_PREFERW_CADMODE_SCHED_FDA_DESC=Select an option from this field to specify which services you want to manage using the Client Acceptor (CAD). You can choose to manage the scheduler, the Web Client, or both the scheduler and the Web Client.
# 30086
DSI_PREFERW_CADMODE_WEBCL_FDA_DESC=Select an option from this field to specify which services you want to manage using the Client Acceptor (CAD). You can choose to manage the scheduler, the Web Client, or both the scheduler and the Web Client.
# 30087
DSI_PREFERW_HTTPPORT_FDA_DESC=Type the TCP/IP port address for the Web client in this field. The HTTP Port address is used to communicate with the Web client.
# 30088
DSI_PREFERW_REVOKE_FDA_DESC=Select this check box to restrict an administrator with client access privilege from accessing a client workstation that is running the Web client.
# 30089
DSI_PREFERW_WEBCLIENT_FDA_DESC=Use this tab to specify processing options for your Tivoli Storage ManagerWeb client.
# 30090
DSI_PREFERW_WEBPORTS_FDA_DESC=Type the required Tivoli Storage Manager Client Acceptor Daemon port number. The Client Acceptor Daemon serves the backup client Java applet to a Web browser. The Web CAD Port and Web Agent Port allow you to use the Web Client through a firewall.
# 30091
DSI_PREFERM_COMMANDLINE_FDA_DESC=Use this tab to specify Tivoli Storage Manager command line client processing options.
# 30092
DSI_PREFERM_DISPLAY_LINE_FDA_DESC=Specify the number of lines of processing information to appear at one time on your Tivoli Storage Manager command line client screen.
# 30093
DSI_PREFERM_PAUSE_FDA_DESC=Select this check box to specify that the command line client pauses after displaying the number of lines you indicate in the Number of lines to display on screen field.
# 30094
DSI_PREFERM_QUIET_FDA_DESC=Select this check box to suppress process information in the Tivoli Storage Manager command line client window.
# 30095
DSI_PREFERD_DIAGNOSTIC_FDA_DESC=Use this tab to specify the type of tracing to perform in the event of a problem with your client.
# 30096
DSI_PREFERD_TRACE_FDA_DESC=Enables the tracing feature. When you select this check box, the File Name and Trace Flags fields become available.
# 30097
DSI_PREFERD_TRACE_ENABLE_FDA_DESC=Enables the tracing feature. When you select this check box, the File Name and Trace Flags fields become available.
# 30098
DSI_PREFERD_TRACE_FILENAME_FDA_DESC=Type the name of the file in which to save your trace output. You can also click the Browse button to open a file selection window to select a file.
# 30099
DSI_PREFERD_TRACE_FLAG_FDA_DESC=Type a list of trace flags. Separate the trace flags with commas or spaces. Your Service Representative will be able to tell you which trace flags to use.
# 30100
DSI_PREFERD_TRACE_FILE_NAME_BROWSE_FDA_DESC=Click this button to open a file or directory selection window. Find the directory or file you want, select it, and click OK.
# 30101
DSI_PREFERIS_IMAGE_SNAPSHOT_FDA_DESC=Use this tab to set snapshot-related backup processing options.
# 30102
DSI_PREFERH_HSM_TITLE_FDA_DESC=Use this tab to specify processing options for the Tivoli Storage Manager for Space Management (HSM) client. The settings in this tab apply only if you installed the (HSM) client.
# 30103
DSI_PREFERH_CHECK_THRESHOLDS_FDA_DESC=Specify how often the space monitor daemon in the HSM client checks space usage on your file systems. The space monitor daemon checks each file system to which you have added space management.
# 30104
DSI_PREFERH_RECONCILE_INTERVAL_FDA_DESC=Specify how often the HSM client reconciles your file systems. The HSM client reconciles each file system for which space management is active and builds a new Migration Candidates list.
# 30105
DSI_PREFERH_MAX_RECALL_DAEMONS_FDA_DESC=Specify the maximum number of HSM recall daemons you want to run at one time to perform recalls for your client.
# 30106
DSI_PREFERH_MIN_RECALL_DAEMONS_FDA_DESC=Specify the minimum number of recall daemons you want to run simultaneously to perform recalls for your client.
# 30107
DSI_PREFERH_MAX_RECONCILE_PROC_FDA_DESC=Specify the maximum number of reconciliation processes that the HSM program can start at one time.
# 30108
DSI_PREFERH_MAX_THRESHOLD_PROC_FDA_DESC=Specify the maximum number of threshold migration processes that the HSM program can start at one time.
# 30109
DSI_PREFERH_MIGFILE_EXP_FDA_DESC=Specify the amount of time for which copies of migrated or premigrated files are kept on the server after they are modified on your local file system, or deleted from your local file system.
# 30110
DSI_PREFERH_OPTION_FORMAT_FDA_DESC=Select an item from the list to specify the format to use when you specify HSM commands.
# 30111
DSI_PREFERH_KERNEL_MSG_FDA_DESC=Select this check box to specify that HSM related messages are displayed during processing.
# 30112
DSI_PREFERH_RESTORE_MIGSTATE_FDA_DESC=Select this check box to specify that Tivoli Storage Manager restores or retrieves migrated or premigrated files to stub files on the local file system during a restore or retrieve operation. The files remain migrated.
# 30113
DSI_PREFERC_NLS_NUMBER_FDA_DESC=Select the format that you want to use for displaying numbers in the client.
# 30114
DSI_PREFERS_SCHEDULE_MODE_FDA_DESC=Use the Scheduler tab to specify processing options for scheduled work.
# 30115
DSI_PREFERS_SESSION_INIT_FDA_DESC=Select an item from this list to specify whether the server or the client initiates client sessions through a firewall.
# 30116
DSI_PREFERC_TCPIP_ADMIN_PORT_FDA_DESC=Specify a port number of the server in this field. This port specifies a separate TCP/IP port number on which the server is waiting for requests for administrative client sessions, allowing secure administrative sessions within a private network. Obtain this port address from your administrator.
# 30117
DSI_PREFERD_TRACE_ENABLE_WRAP_FDA_DESC=Select this check box to allow the trace output to wrap to the beginning of the trace file when the trace file reaches the size indicated by the Maximum size field.
# 30118
DSI_PREFERD_TRACE_ENABLE_SPAN_FDA_DESC=Select this check box to allow the trace output to span multiple files. The size of each file is determined by the value specified below.
# 30119
DSI_PREFERD_TRACE_MAX1_SIZE_FDA_DESC=Specify the maximum size for the trace file. You can specify a value from 1 to 4294967295.
# 30120
DSI_PREFERD_TRACE_MAX2_SIZE_FDA_DESC=Specify the maximum size for the trace segments. You can specify a value between 0 and 1000 MB.
# 30121
DSI_PREFERB_RESET_LAST_ACCESS_DATE_FDA_DESC=Select this check box to preserve the last access dates of files that are backed up or archived to the server.
# 30122
DSI_PREFERR_MAKE_SPARSE_FILE_FDA_DESC=Select this check box to perform sparse file processing during restore or retrieve.
# 30123
DSI_PREFERIS_CACHE_SIZE_FDA_DESC=Specify an appropriate cache size for creating the snapshot for snapshot-related backup operations.
# 30124
DSI_PREFERG_PRUNE_OLD_FDA_DESC=Select this check box to automatically delete older log entries from the log.
# 30125
DSI_PREFERR_REPLACE_READONLY_FDA_DESC=Select this check box if you want to overwrite read-only or locked files when the client restores files from the server.
# 30126
DSI_PREFERI_CATEGORY_FDA_DESC=Select the type of function for which you want to generate include or exclude statements in the client options file. When you select an item in the list, the options that pertain to the selected category item are displayed in the Type list.
# 30127
DSI_PREFERCW_OPTION_FILE_TASK_FDA_DESC=Select an options file task and click Next to continue. The selections that you make in this configuration wizard are stored in a client options file.
# 30128
DSI_PREFERA_SERVICES_ALL_FDA_DESC=Select this check box to allow all groups and users on your system to request Tivoli Storage Manager services.
# 30129
DSI_PREFERG_ASNODE_NAME_FDA_DESC=Type the name of the target node to which you have been granted proxy authority to enable your client for client node proxy support.
# 30130
DSI_PREFERG_ERROR_LOG_ENABLE_WRAP_FDA_DESC=Select this check box to allow error log records to wrap to the beginning of the error log file when the error log file reaches the size indicated by the Maximum size (MB) field.
# 30131
DSI_PREFERG_MAX_LOG_SIZE_FDA_DESC=Specify the maximum size for the log file in megabytes (MB). You can specify a value from 0 to 2047.
# 30132
DSI_PREFERS_LOG_WRAP_FDA_DESC=Select this check box to allow scheduler log records to wrap to the beginning of the schedule log file when the schedule log file reaches the size indicated by the Maximum size (MB) field.
# 30133
DSI_PREFERS_MAX_LOG_SIZE_FDA_DESC=Specify the maximum size for the log file in megabytes (MB). You can specify a value from 0 to 2047.
# 30134
DSI_PREFA_ENCRYPTION_TYPE_FDA_DESC=Select a data encryption type in this field. The encryption type that you choose is used to encrypt data during backup and archive operations using the Include.Encryption option.
# 30135
DSI_PREFA_56BITDES_FDA_DESC=Select a data encryption type in this field. The encryption type that you choose is used to encrypt data during backup and archive operations using the Include.Encryption option.
# 30136
DSI_PREFA_128BITAES_FDA_DESC=Select a data encryption type in this field. The encryption type that you choose is used to encrypt data during backup and archive operations using the Include.Encryption option.
# 30137
DSI_PREFERR_PERFORMANCE_TUNING_FDA_DESC=Use this tab to specify how the backup-archive client uses memory during file system incremental backups.
# 30138
DSI_PREFERR_MEMORY_RESIDENT_FDA_DESC=Select this option to use a faster, more memory-intensive method for processing file system incremental backups.
# 30139
DSI_PREFERR_MEMORY_SAVING_INCR_FDA_DESC=Select this option to use less memory during file system incremental backups. When selected, the client backs up data one directory at a time. This uses less memory but takes longer to complete.
# 30140
DSI_PREFERR_MEMORY_DISKCACHE_FDA_DESC=Select this option to use the least amount of memory during file system incremental backups. This method requires significantly more disk space. Use this method for a filespace that has too many files for an incremental backup to complete using either the memory-resident algorithm or the memory-saving algorithm.
# 30141
DSI_PREFERR_MEMORY_METHOD_FDA_DESC=Use this tab to specify how the backup-archive client uses memory during file system incremental backups.
# 30142
DSI_PREFERR_APPLY_ALL_FILESPACES_FDA_DESC=Select this option to apply the memory algorithm to all filespaces on your computer. The memory method will be used to process incremental backups of any filespace on your computer.
# 30143
DSI_PREFERR_APPLY_ONE_FILESPACE_FDA_DESC=Select this option to apply the memory algorithm for incremental backup of an individual filespace. Click Browse to specify the filespace to which you want to apply the memory algorithm.
# 30144
DSI_PREFERP_STATEMENT_LIST_FDA_DESC=This list contains the names of individual filespaces to which you applied memory algorithms.
# 30145
DSI_PREFERS_PRESCHEDULE_PREVENT_FDA_DESC=Select this check box to disable any pre-schedule commands that you defined in your client options file.
# 30146
DSI_PREFERS_POSTSCHEDULE_PREVENT_FDA_DESC=Select this check box to disable any post-schedule commands that you defined in your client options file.
# 30147
DSI_PREFERS_SCHED_CMD_PREVENT_FDA_DESC=Select this check box to disable any operating system commands that the administrator scheduled for your node. Selecting this option can prevent an administrator from running inadvertent or potentially malicious operations on your computer.
# 30148
DSI_PREFERS_SCHED_RESTRETR_PREVENT_FDA_DESC=Select this check box to disable any restore or retrieve operations that the administrator scheduled for your node. Selecting this option can prevent an administrator from running inadvertent or potentially malicious operations on your computer.
# 30149
DSI_PREFERS_SRV_PREPOST_PREVENT_FDA_DESC=Select this check box to prevent any administrator defined pre-snapshot or post-snapshot commands from running on your client node during scheduled snapshot image (or online image) backup operations.
# 30150
DSI_PREFERB_SNAPPROVIDER_IMAGE_TYPE_FDA_DESC=Use this field to set up your backup-archive client for snapshot-based online image backup operations and to specify a snapshot provider. During this backup operation, the backup-archive client uses a snapshot of your volume as the source of the backup operation, allowing the original volume to be available to other system applications.
# 30151
DSI_PREFERB_SNAPPROVIDER_FS_TYPE_FDA_DESC=Use this field to set up your backup-archive client for snapshot based file backup or archive operations and to specify a snapshot provider.
# 30152
DSI_SnapProviderChoiceFS_NONE_FDA_DESC=Select this option if you do not want to use open file support (or snapshot based file backup) operations. The client performs a normal (non-snapshot) file backup of the files in your volumes.
# 30153
DSI_SnapProviderChoice_NONE_FDA_DESC=Select this option if you do not want to use snapshot based online image backups. The client performs an offline (static) image backup of your volumes.
# 30154
DSI_SnapProviderChoiceFS_JFS2_FDA_DESC=Select this option to use the snapshots that are created by the JFS2 file system snapshot provider.
# 30155
DSI_SnapProviderChoice_JFS2_FDA_DESC=Select this option to use the snapshots that are created by the JFS2 file system snapshot provider.
# 30156
DSI_SnapProviderChoice_LVM_FDA_DESC=Select this option to use the snapshots that are created by the Logical Volume Manager (LVM) snapshot provider. This option is available only to Linux LVM clients and only applies to snapshot image backup.
# 30157
DSI_SnapProviderChoice_VSS_FDA_DESC=Select this option to use the snapshots that are provided by the Volume Shadow Copy Service (VSS). VSS is the preferred method for creating snapshots.
# 30158
DSI_SnapProviderChoiceFS_VSS_FDA_DESC=Select this option to use the snapshots that are provided by the Volume Shadow Copy Service (VSS). VSS is the preferred method for creating snapshots.
# 30159
DSI_PREFERI_DYNAMIC_IMAGE_TYPE_FDA_DESC=Select this option to include a file system or logical volume for dynamic image backup processing, or assign a management class when used with dynamic image backup.
# 30160
DSI_PREFERI_SNAP_PROVIDER_TYPE_FDA_DESC=Select a snapshot provider to use for snapshot-related backup operations.
# 30161
DSI_PREFERA_ENCRYPTION_GENERATE_FDA_DESC=Select this option to dynamically generate an encryption key when the Tivoli Storage Manager client begins a backup or archive.
# 30162
DSI_PREFERC_TCPIP_USE_SSL_FDA_DESC=Select this check box to connect with Secure Sockets Layer (SSL), to provide industry standard, SSL-based secure communications between the backup-archive client and the Tivoli Storage Manager Server. This check box does not apply to Mac OS X clients.
# 30163
DSI_PREFERB_DECRYPT_EFS_TYPE_FDA_DESC=Use this field to control whether or not files encrypted by an AIX Encrypted File System (EFS) are read in encrypted or decrypted format.
# 30164
DSI_PREFERIS_PRESNAP_PREVENT_FDA_DESC=Select this check box to disable any pre-snapshot commands that you defined in your client options file.
# 30165
DSI_PREFERI_PRE_SNAP_CMD_FDA_DESC=Type a command or batch file to be executed prior to the start of a snapshot. This is useful if you need to quiesce an application before the snapshot provider starts a snapshot.This is useful if you need to quiesce an application before the snapshot begins.
# 30166
DSI_PREFERIS_POSTSNAP_PREVENT_FDA_DESC=Select this check box to disable any post-snapshot commands that are defined in your client options file.
# 30167
DSI_PREFERI_POST_SNAP_CMD_FDA_DESC=Type a command or batch file to be executed after the start of a snapshot. This is useful if you need to restart an application that was quiesced by the pre-snapshot command.
# 30168
DSI_PREFERIS_IMAGE_GAP_SIZE_FDA_DESC=Specify the minimum size of empty regions on a formatted volume that should be skipped during image backup.
# 30169
DSI_PREFERG_NTFS_SECURITY_FDA_DESC=Select this check box to back up security information such as file permissions. In subsequent incremental backups, the client will be able to detect and back up changed file permissions. This option is applicable only to NTFS files.
# 30170
DSI_PREFERG_AUTOFSRENAME_FDA_DESC=Use this filed drop-down list box to specify whether to rename your existing non-Unicode filespaces on the server. This option allows Unicode enabled filespaces with the original name to be created for the current operation.
# 30171
DSI_PREFERB_DFS_MOUNTPOINT_FDA_DESC=Use this option to view a Microsoft DFS junction (NTFS or FAT) as a junction or a directory.
# 30172
DSI_PREFERB_RESET_LAST_ARCHIVE_FDA_DESC=Select this check box to reset the Windows archive attribute on files that are successfully backed up to the Tivoli Storage Manager server. This option also resets the archive attribute of a file during incremental backup if there is already an active backup version on the server. This option is useful to applications, such as IBM Tivoli Storage Resource Manager, as a simple way to report on the backup status of files.
# 30173
DSI_PREFERB_INCR_THESHOLD_FDA_DESC=Specify the value for the number of directories in any journaled filespace that might contain active files that should be expired. When this threshold is reached during a full filespace journaled incremental, the client initiates an incremental backup on each such directory.
# 30174
DSI_PREFERB_USE_SUBFILE_FDA_DESC=Select this check box to send only changed portions of a file to the server during successive incremental backup operations instead of sending the entire file.
# 30175
DSI_PREFERB_CACHE_PATH_FDA_DESC=Specify the path where the client cache resides for adaptive subfile backup processing. You can select a path with the browse button.
# 30176
DSI_PREFERB_CACHE_SIZE_FDA_DESC=Specify the client cache size in megabytes for adaptive subfile backup. You can type a value in the entry field or click the up or down arrows to change the value.
# 30177
DSI_PREFERS_RUNASSERVICE_FDA_DESC=Select this check box to specify that the client command process continues to run even if the account that started the client logs off.
# 30178
DSI_PREFERVM_VMBACKUP_FDA_DESC=Use this tab to set processing options for backing up virtual machine data.
# 30179
DSI_DPREFVM_VMBACKUP_BACKUP_TYPE_FDA_DESC=Select the type of virtual machine backup to perform when you issue the backup VM command on the Tivoli Storage Manager data mover node that is installed on the vStorage backup server.
# 30180
DSI_DPREFVM_VMBACKUP_FILE_LEVEL_FDA_DESC=Select the type of virtual machine backup to perform when you issue the backup VM command on the Tivoli Storage Manager data mover node that is installed on the vStorage backup server.
# 30181
DSI_DPREFVM_VMBACKUP_FULL_IMAGE_FDA_DESC=Select the type of virtual machine backup to perform when you issue the backup VM command on the Tivoli Storage Manager data mover node that is installed on the vStorage backup server.
# 30182
DSI_DPREFVM_VMBACKUP_VCHOST_FDA_DESC=Specify the host name of the VMware Virtual Center or ESX server that contains the virtual machines that you want to back up.
# 30183
DSI_DPREFVM_VMBACKUP_VCUSER_FDA_DESC=Specify the user name of the VMware Virutal Center or ESX server that contains the virtual machines that you want to back up.
# 30184
DSI_DPREFVM_VMBACKUP_VCPASSWORD_FDA_DESC=Specify the password of the VMware Virutal Center or ESX server that contains the virtual machines that you want to back up.
# 30185
DSI_DPREFVM_VMBACKUP_DS_LOC_FDA_DESC=Specify the location to store temporary files during VMware backups.
# 30186
DSI_PREFERG_STAGING_DIR_FDA_DESC=Specify the location where the client can store any data it generates in order to perform its operations. The data is deleted by the client after an operation ends.
# 30187
DSI_SERVER_STANZA_FDA_DESC=Specify a Tivoli Storage Manager server to contact for services. You can also specify a new server to contact, and to begin a stanza containing parameters for that server. Server stanzas are stored in the client system options file (dsm.sys).
# 30188
DSI_JOURNALWIZ_FSLIST_ALL_LOCAL_FDA_DESC=Specify which file systems to monitor for journaling.
# 30189
DSI_JOURNALWIZ_FSLIST_JFSLIST_FDA_DESC=Specify which file systems to monitor for journaling.
# 30190
DSI_JOURNALWIZ_DBSIZE_TITLE_FDA_DESC=Specify the maximum size of the journal database in megabytes (MB). The Journal Database Maximum Size field can contain a value from 1 MB to 999 MB.
# 30191
DSI_JOURNALWIZ_DBSIZE_NOLIMIT_FDA_DESC=Select this option if you do not want to place a fixed limit on the size of the journal database. The maximum size is based on available disk space.
# 30192
DSI_JOURNALWIZ_NOTIFY_CDRCB_FDA_DESC=Select this check box if you want the journal service to monitor a file or directory whenever you create, delete, or rename it.
# 30193
DSI_JOURNALWIZ_NOTIFY_FILECB_FDA_DESC=Select this check box if you want the journal service to monitor file size changes. Notification is deferred until the disk write cache is flushed.
# 30194
DSI_JOURNALWIZ_NOTIFY_MODIFIEDCB_FDA_DESC=Select this check box if you want the journal service to monitor timestamp changes for a file that is modified. Notification is deferred until the disk write cache is flushed.
# 30195
DSI_JOURNALWIZ_NOTIFY_ACCESSEDCB_FDA_DESC=Select this check box if you want the journal service to monitor timestamp changes for a file that was accessed.
# 30196
DSI_JOURNALWIZ_NOTIFY_ATTRIBUTESCB_FDA_DESC=Select this check box if you want the journal service to monitor file attribute changes.
# 30197
DSI_JOURNALWIZ_NOTIFY_NTFSCB_FDA_DESC=Select this check box if you want the journal service to monitor NTFS security changes for a file.
# 30198
DSI_JOURNALWIZ_PARAMS_TITLE_FDA_DESC=Specify the directory to which the journal databases are written. You can specify the same journal directory for all journaled databases or a different journal directory for each journal database.
# 30199
DSI_JOURNALWIZ_TASK_INSTALL_FDA_DESC=Select an option to install, update, or remove a Tivoli Storage Manager Journal Engine.
# 30200
DSI_JOURNALWIZ_TASK_UPDATE_FDA_DESC=Select an option to install, update, or remove a Tivoli Storage Manager Journal Engine.
# 30201
DSI_JOURNALWIZ_TASK_REMOVE_FDA_DESC=Select an option to install, update, or remove a Tivoli Storage Manager Journal Engine.
# 30202
DSI_CFGWIZ_SELECTALL_FDA_DESC=Click this button to select all the items on the list.
# 30203
DSI_CFGWIZ_CLEARALL_FDA_DESC=Click this button to clear the selections on the list.
# 30204
DSI_CFGWIZ_COMMON_TITLE_FDA_DESC=Select one or more commonly excluded file types from the list. These types of files are potentially large files that you might not want to back up, such as multimedia files, archive files, object files, and core or dump files.
# 30205
DSI_CFGWIZ_DOMAIN_LIST_FDA_DESC=Specify which file systems to include in your client domain.
# 30206
DSI_CFGWIZ_BACKUP_TYPE_FDA_DESC=Use this field to display the client domain settings for a backup type.
# 30207
DSI_CFGWIZ_WEB_CLIENT_PASSWORD_FDA_DESC=Type the password for your node. The password can contain 1 to 63 characters, and any alphanumeric character, underscore (_), period (.), hyphen (-), plus (+), or ampersand (&).
# 30208
DSI_CFGWIZ_WEB_CLIENT_CONTACT_TSM_SERVER_FDA_DESC=Use this check box to specify whether you want the client to initiate authentication with the Tivoli Storage Manager server to validate the password that you specified.
# 30209
DSI_CFGWIZ_SYSTEM_ACCOUNT_FDA_DESC=Select this option if you want the service to log on to the local system account.
# 30210
DSI_CFGWIZ_SPECIFIC_ACCOUNT_FDA_DESC=Select this option if you want the service to log on to the local system account.
# 30211
DSI_CFGWIZ_ACCOUNT_NAME_FDA_DESC=Select this option if you want to assign a logon user account to the service, such as a local administrator account or a domain administrator account.
# 30212
DSI_CFGWIZ_PASSWORD_FDA_DESC=Type the password for the user account that you specified.
# 30213
DSI_CFGWIZ_CONFIRM_PASSWORD_FDA_DESC=Type the password for the user account again.
# 30214
DSI_CFGWIZ_START_OPTION_MANUALLY_FDA_DESC=Select this option to manually start the service from the Windows Services control panel.
# 30215
DSI_CFGWIZ_START_OPTION_AUTOMATICALLY_FDA_DESC=Select this option if you want the service to start automatically when the operating system starts.
# 30216
DSI_CFGWIZ_WEB_SERVICE_NAME_FDA_DESC=Specify the name of the remote client agent.
# 30217
DSI_CFGWIZ_WEB_CLIENT_YES_FDA_DESC=Specify whether you want to restrict an administrator with client access from accessing the Web client.
# 30218
DSI_CFGWIZ_WEB_CLIENT_NO_FDA_DESC=Specify whether you want to restrict an administrator with client access from accessing the Web client.
# 30219
DSI_CFGWIZ_START_OPTION_YES_FDA_DESC=Specify whether to start the Web client, scheduler, or journal engine service upon completion of the Web client, Scheduler, or Journal Engine wizard.
# 30220
DSI_CFGWIZ_START_OPTION_NO_FDA_DESC=Specify whether to start the Web client, scheduler, or journal engine service upon completion of the Web client, Scheduler, or Journal Engine wizard.
# 30221
DSI_SCHWIZ_SCHNAME_FDA_DESC=Type a name for the client scheduler that you are installing or adding.
# 30222
DSI_SCHWIZ_LOCAL_MACHINE_FDA_DESC=Select this option to install the client scheduler on your local computer.
# 30223
DSI_SCHWIZ_USE_CAD_FDA_DESC=Select this option to use the Client Acceptor service (CAD) to manage the client scheduler.
# 30224
DSI_SCHWIZ_LOGFILE_FDA_DESC=Type the fully qualified name of the client schedule log file. You can also click Browse to open a file selection window and select the schedule log file that you want to use.
# 30225
DSI_SCHWIZ_ERROR_LOGFILE_FDA_DESC=Type the fully qualified name of the client error log file. You can also click Browse to open a file selection window and select the client error log file that you want to use.
# 30226
DSI_SCHWIZ_FILES_LOGGING_FDA_DESC=Select this option if you want detailed events for the client scheduler to be logged in the Event Log.
# 30227
DSI_SCHWIZ_SCHNAME_UPDATE_REMOVE_FDA_DESC=Select a client scheduler to update or remove.
# 30228
DSI_CFGWIZ_VSS_FDA_DESC=Select this option to use the snapshots that are provided by the Volume Shadow Copy Service (VSS). VSS is the preferred method for creating snapshots.
# 30229
DSI_CFGWIZ_NONE_ONLINE_IMAGE_FDA_DESC=Select this option if you do not want to use snapshot based online image backups. The client performs an offline (static) image backup of your volumes.
# 30230
DSI_CFGWIZ_NONE_OPEN_FILE_FDA_DESC=Select this option if you do not want to use open file support (or snapshot based file backup) operations. The client performs a normal (non-snapshot) file backup of the files in your volumes.
# 30231
DSI_TCPIP_ADTABLE_FDA_DESC=Select a Tivoli Storage Manager server that is registered in the Active Directory that the client can communicate with using the specified communication protocol.
# 30232
DSI_NAMEDPIPE_ADTABLE_FDA_DESC=Select a Tivoli Storage Manager server that is registered in the Active Directory that the client can communicate with using the specified communication protocol.
# 30233
DSI_SHOW_ALL_SERVERS_FDA_DESC=Select this check box to list all the servers that are registered in the Active Directory.
# 30234
DSI_PREFERC_GEN_USEDIRECTORY_FDA_DESC=Select this check box to automatically use the Windows Active Directory communication information during client initialization. This bypasses the communication method parameters that are stored locally in your options file and directly queries the directory for the communication method and server with which to connect.
# 30235
DSI_PREFERVM_DOMAIN_VMBACKUP_TYPES_FDA_DESC=Select a virtual machine backup type from this list to create a domain for the backup of VMware virtual machines.
# 30236
DSI_PREFERVM_DOMAIN_VMBACKUP_VMBACKUP_FILE_FDA_DESC=When this item is selected, the virtual machines that are included in the domain for file-level virtual machine backup are displayed.
# 30237
DSI_PREFERVM_DOMAIN_VMBACKUP_VMBACKUP_FULL_FDA_DESC=When this item is selected, the virtual machines that are included in the domain for full virtual machine backup are displayed.
# 30238
DSI_PREFERVM_DOMAIN_VMBACKUP_OPT_FDA_DESC=Select an item from this list to specify the type of virtual machine object that you want to include in your VM backup domain.
# 30239
DSI_PREFERVM_VMBACKUP_HOST_FOLDER_VM_FDA_DESC=Specify a VMware host server name, host cluster name, data store name, folder name, or a list of virtual machine host names to process. What you specify depends on what you select in the VM options field.
# 30240
DSI_PREFERVM_VMBACKUP_INSERT_FDA_DESC=Click this button to insert the VM object that you specified into the list below the Domain Backup Type field.
# 30241
DSI_PREFERVM_VMBACKUP_REMOVE_FDA_DESC=Click this button to remove the highlighted item in the list below the Domain Backup Type field.
# 30242
DSI_DEDUP_FDA_DESC=Use this tab to set processing options for client-side data deduplication.
# 30243
DSI_ENABLE_DEDUP_FDA_DESC=Select this check box to enable the backup-archive client for client-side data deduplication.
# 30244
DSI_ENABLE_DEDUP_CACHE_FDA_DESC=Select this check box to use a cache during client-side data deduplication. Using a local cache can reduce network traffic between the Tivoli Storage Manager server and the client.
# 30245
DSI_DEDUP_CACHE_LOCATION_FDA_DESC=Specify the location where the data deduplication cache database is created.
# 30246
DSI_DEDUP_CACHE_MAX_FDA_DESC=Specify the maximum size (in megabytes) of the data deduplication database file. When the cache file reaches its maximum size, the cache is emptied.
# 30247
DSI_DEDUP_CACHE_LOCATION_BROWSE_DESC=Click this button to open a file or directory selection window. Find the directory or file you want, select it, and click OK.
# 30248
DSI_PREFERG_AUTODEPLOY=Select an option to specify whether the Tivoli Storage Manager server can automatically deploy the backup-archive client program to your computer during a scheduled operation.
# 30249
DSI_PREFERG_AUTODEPLOY_FDA_DESC=Select an option to specify whether the Tivoli Storage Manager server can automatically deploy the backup-archive client program to your computer during a scheduled operation.
# 30250
DSI_PREFERG_AUTODEPLOY_YES=Select an option to specify whether the Tivoli Storage Manager server can automatically deploy the backup-archive client program to your computer during a scheduled operation.
# 30251
DSI_PREFERG_AUTODEPLOY_YES_NOREBOOT=Select an option to specify whether the Tivoli Storage Manager server can automatically deploy the backup-archive client program to your computer during a scheduled operation.
# 30252
DSI_PREFERG_AUTODEPLOY_NO=Select an option to specify whether the Tivoli Storage Manager server can automatically deploy the backup-archive client program to your computer during a scheduled operation.
# 30253
DSI_DPREFVM_VMBACKUP_VMMGTCLASS_FDA_DESC=Specify a management class name to override the default management class setting for VMware full virtual machine (VM) backups.
# 30254
DSI_PREFERC_TCPIP_SSLREQUIRED_FDA_DESC=Specify whether the SSL protocol is required to protect the Tivoli Storage Manager password over the network during client authentication.
# 30255
DSI_DPREFVM_VMBACKUP_VMENABLETEMPLATES_LABEL_FDA_DESC=Select this check box to back up VMware template virtual machines when the client protects virtual machines in a vCenter server. You cannot back up VMware templates if you are connected directly to an ESXi host because template virtual machines are not accessible.
