# # Distributed Storage Manager # # OCO Source Materials # # (C) Copyright IBM Corporation 1990, 2021 # # # Symbolic Message ID and Message Definitions # # This file was generated by a program. # ------> DO NOT MODIFY MANUALLY <------ # # 0200 VMBACKUP_WITH_NEWER_VERSION=ANS0200E The virtual machine '{0}' was backed up with a later version of the backup-archive client. VMBACKUP_WITH_NEWER_VERSION_EXPLANATION=The virtual machine was backed up with a later version of the backup-archive client. The objects of the virtual machine backup that were retrieved cannnot be correctly displayed. VMBACKUP_WITH_NEWER_VERSION_SYSACT=The backup information for the virtual machine will not be displayed. VMBACKUP_WITH_NEWER_VERSION_URESP=Query the virtual machine on a later version of the backup-archive client to view backup details. If a query of all virtual machines does not display virtual machines that were backed up at the same client version, issue the Query VM command for individual virtual machines. # 0211 API_ObjName_Null=ANS0211E The object name pointer is NULL. API_ObjName_Null_EXPLANATION=There is no value provided for the object name pointer. API_ObjName_Null_SYSACT=The system returns to the calling procedure. API_ObjName_Null_URESP=Provide an address for the dsmObjName structure. # 0212 API_DataBlk_Null=ANS0212E The data block pointer is NULL. API_DataBlk_Null_EXPLANATION=There is no value provided for the data block pointer. API_DataBlk_Null_SYSACT=The system returns to the calling procedure. API_DataBlk_Null_URESP=Provide an address for the DataBlk structure. # 0213 API_ObjAttr_Null=ANS0213E The object attribute pointer is NULL. API_ObjAttr_Null_EXPLANATION=There is no value provided for the object attribute pointer. API_ObjAttr_Null_SYSACT=The system returns to the calling procedure. API_ObjAttr_Null_URESP=Provide an address for the ObjAttr structure. # 0214 API_No_Session_Info=ANS0214E There is no server session information. API_No_Session_Info_EXPLANATION=The server did not respond with the session information. API_No_Session_Info_SYSACT=The system returns to the calling procedure. API_No_Session_Info_URESP=Verify the server status. # 0215 API_No_Policy_Info=ANS0215E There is no server policy information. API_No_Policy_Info_EXPLANATION=The server did not respond with the policy information. API_No_Policy_Info_SYSACT=The system returns to the calling procedure. API_No_Policy_Info_URESP=Verify the server policy definitions. # 0216 API_Zero_BufferLen=ANS0216E The dataBlk bufferLen value is zero. API_Zero_BufferLen_EXPLANATION=The value for the dataBlk bufferLen is zero. API_Zero_BufferLen_SYSACT=The system returns to the calling procedure. API_Zero_BufferLen_URESP=Provide a non-zero value for the bufferLen. # 0217 API_BufferPtr_Null=ANS0217E The dataBlk bufferPtr is NULL. API_BufferPtr_Null_EXPLANATION=There is no value provided for the dataBlk bufferPtr. API_BufferPtr_Null_SYSACT=The system returns to the calling procedure. API_BufferPtr_Null_URESP=Provide an address for the bufferPtr. # 0218 API_Invalid_ObjType=ANS0218E The objType is invalid. API_Invalid_ObjType_EXPLANATION=The value for the objType is invalid. API_Invalid_ObjType_SYSACT=The system returns to the calling procedure. API_Invalid_ObjType_URESP=The value for dsmObjName.objType must be: DSM_OBJ_FILE or DSM_OBJ_DIRECTORY for Backup, or DSM_OBJ_FILE for Archive. # 0219 API_Invalid_Vote=ANS0219E The dsmEndTxn vote is invalid. API_Invalid_Vote_EXPLANATION=The dsmEndTxn vote is invalid. API_Invalid_Vote_SYSACT=The system returns to the calling procedure. API_Invalid_Vote_URESP=The vote must be DSM_VOTE_COMMIT or DSM_VOTE_ABORT. # 0221 API_Internal_Error=ANS0221E There was an error in the IBM Spectrum Protect API internals. API_Internal_Error_EXPLANATION=The system encountered an error in the API internals. API_Internal_Error_SYSACT=The system returns to the calling procedure. API_Internal_Error_URESP=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. # 0222 API_Invalid_Repository=ANS0222E The repository type is invalid. API_Invalid_Repository_EXPLANATION=The repository type is invalid. API_Invalid_Repository_SYSACT=The system returns to the calling procedure. API_Invalid_Repository_URESP=For dsmDeleteFS the repository must be one of the following: # 0223 API_Invalid_Filespace_Name=ANS0223E Filespace name should start with the directory delimiter. API_Invalid_Filespace_Name_EXPLANATION=The filespace name is invalid. API_Invalid_Filespace_Name_SYSACT=The system returns to the calling procedure. API_Invalid_Filespace_Name_URESP=Filespace name should start with the directory delimiter. # 0224 API_Invalid_ObjName=ANS0224E The object name is either an empty string or has no leading delimiter. API_Invalid_ObjName_EXPLANATION=The object name is invalid because of an empty string or there is no leading delimiter. API_Invalid_ObjName_SYSACT=The system returns to the calling procedure. API_Invalid_ObjName_URESP=Verify the format of the dsmObjName full path. # 0225 API_Invalid_Lowlevel_Qualifier=ANS0225E Low level qualifier of the object name should start with the directory delimiter. API_Invalid_Lowlevel_Qualifier_EXPLANATION=The low level qualifier for the object name is invalid. API_Invalid_Lowlevel_Qualifier_SYSACT=The system returns to the calling procedure. API_Invalid_Lowlevel_Qualifier_URESP=Start the low level qualifier of the object name with the directory delimiter. # 0226 API_Invalid_ObjOwner=ANS0226E The object owner is invalid. API_Invalid_ObjOwner_EXPLANATION=The object owner must be either the root user, or the object owner must be the same as the session owner. API_Invalid_ObjOwner_SYSACT=The system returns to the calling procedure. API_Invalid_ObjOwner_URESP=Verify the session owner and object owner. # 0227 API_Invalid_Bind_Type=ANS0227E The dsmBindMC sendType is invalid. API_Invalid_Bind_Type_EXPLANATION=The dsmBindMC sendType is invalid. API_Invalid_Bind_Type_SYSACT=The system returns to the calling procedure. API_Invalid_Bind_Type_URESP=The sendType must be one of the following: stBackup stArchive stBackupMountWait stArchiveMountWait # 0228 API_Invalid_SendType=ANS0228E The dsmSendObj sendType is invalid. API_Invalid_SendType_EXPLANATION=The dsmSendObj sendType is invalid. API_Invalid_SendType_SYSACT=The system returns to the calling procedure. API_Invalid_SendType_URESP=The sendType must be one of the following: stBackup stArchive stBackupMountWait stArchiveMountWait # 0229 API_Invalid_DelType=ANS0229E The dsmDeleteObj delType is invalid. API_Invalid_DelType_EXPLANATION=The dsmDeleteObj delType is invalid. API_Invalid_DelType_SYSACT=The system returns to the calling procedure. API_Invalid_DelType_URESP=The delType must be dtBackup or dtArchive. # 0230 API_Invalid_ObjState=ANS0230E The query Backup objState is invalid. API_Invalid_ObjState_EXPLANATION=The query Backup objState is invalid. API_Invalid_ObjState_SYSACT=The system returns to the calling procedure. API_Invalid_ObjState_URESP=The qryBackupData.objState must be one of the following: DSM_ACTIVE DSM_INACTIVE DSM_ANY_MATCH # 0231 API_Mgmt_Class_Not_Found=ANS0231E The management class name was not found. API_Mgmt_Class_Not_Found_EXPLANATION=A query or send operation is unable to find the management class name. API_Mgmt_Class_Not_Found_SYSACT=The system returns to the calling procedure. API_Mgmt_Class_Not_Found_URESP=Verify the management class name. # 0232 API_Invalid_Drive=ANS0232E The drive letter is not an alphabetic character. API_Invalid_Drive_EXPLANATION=The drive letter is not an alphabetic character. This return code is valid on Microsoft Windows only. API_Invalid_Drive_SYSACT=The system returns to the calling procedure. API_Invalid_Drive_URESP=Verify that the drive designation is an alphabetic character. The referenced field is dsmDosFSAttrib.driveLetter. # 0233 API_Filespace_Name_NULL=ANS0233E The Register Filespace name is NULL. API_Filespace_Name_NULL_EXPLANATION=There is no value provided for the Register Filespace name. API_Filespace_Name_NULL_SYSACT=The system returns to the calling procedure. API_Filespace_Name_NULL_URESP=Provide a filespace name on dsmRegisterFS. # 0234 API_New_Password_Req=ANS0234E The new password value is NULL or blank. API_New_Password_Req_EXPLANATION=There is no value provided for new password. API_New_Password_Req_SYSACT=The system returns to the calling procedure. API_New_Password_Req_URESP=Provide a new password on dsmChangePW. # 0235 API_Old_Password_Req=ANS0235E The old password value is NULL or blank. API_Old_Password_Req_EXPLANATION=There is no value provided for old password. API_Old_Password_Req_SYSACT=The system returns to the calling procedure. API_Old_Password_Req_URESP=Provide an old password on dsmChangePW. # 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=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 API_Owner_Not_Allowed_SYSACT=The system returns to the calling procedure. Whether the application can continue processing depends on how the application handles the error. API_Owner_Not_Allowed_URESP=This message applies to applications that utilize the IBM Spectrum Protect 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. # 0237 API_Node_Not_Allowed=ANS0237E On dsmInit, the node is not allowed when PASSWORDACCESS=generate. API_Node_Not_Allowed_EXPLANATION=PASSWORDACCESS=generate establishes a session with the current hostname as the node. API_Node_Not_Allowed_SYSACT=The system returns to the calling procedure. API_Node_Not_Allowed_URESP=When using PASSWORDACCESS=generate, set clientNodeNameP to NULL. # 0238 API_Invalid_Call_Sequence=ANS0238E The sequence of calls is invalid. API_Invalid_Call_Sequence_EXPLANATION=Then API requires function calls to be made in a specific sequence. The function calls were not made in the expected sequence. The error can be triggered by the following issues: API_Invalid_Call_Sequence_SYSACT=The system returns to the calling procedure. API_Invalid_Call_Sequence_URESP=An end user can respond in the following ways: # 0239 API_Wildcard_Not_Allowed=ANS0239E On dsmSendObj, wildcards are not allowed for the objName. API_Wildcard_Not_Allowed_EXPLANATION=On dsmSendObj, wildcards are not allowed for the objName. API_Wildcard_Not_Allowed_SYSACT=The system returns to the calling procedure. API_Wildcard_Not_Allowed_URESP=Provide a fs, hl, and ll on the dsmObjName. # 0240 API_Filespace_Not_Found=ANS0240E The filespace to delete/set access cannot be found. API_Filespace_Not_Found_EXPLANATION=The filespace to delete cannot be found. API_Filespace_Not_Found_SYSACT=The system returns to the calling procedure. API_Filespace_Not_Found_URESP=Verify the filespace name. # 0241 API_Filespace_Not_Registered=ANS0241E On dsmSendObj, dsmDeleteObj, or dsmUpdateFS the filespace is not registered. API_Filespace_Not_Registered_EXPLANATION=On dsmSendObj, dsmDeleteObj, or dsmUpdateFS, the filespace is not registered. API_Filespace_Not_Registered_SYSACT=The system returns to the calling procedure. API_Filespace_Not_Registered_URESP=Verify the filespace name. # 0242 API_FS_Already_Registered=ANS0242W On dsmRegisterFS the filespace is already registered. API_FS_Already_Registered_EXPLANATION=On dsmRegisterFS the filespace is already registered. API_FS_Already_Registered_SYSACT=The system returns to the calling procedure. API_FS_Already_Registered_URESP=Verify the filespace name. # 0243 API_No_ObjID=ANS0243E On dsmBeginGetData the objID is NULL. API_No_ObjID_EXPLANATION=On dsmBeginGetData, the objID is NULL. API_No_ObjID_SYSACT=The system returns to the calling procedure. API_No_ObjID_URESP=Verify the following: The dsmGetList is not NULL. Each objID is not NULL. The dsmGetList numObjId is not zero. # 0244 API_Wrong_Version=ANS0244E On dsmInit, the caller API version is different than the IBM Spectrum Protect library version. API_Wrong_Version_EXPLANATION=On dsmInit, the caller API version is later than the IBM Spectrum Protect library version. API_Wrong_Version_SYSACT=The system returns to the calling procedure. API_Wrong_Version_URESP=Install the latest IBM Spectrum Protect API library. # 0245 API_Wrong_Version_Parm=ANS0245E The caller's structure version is different than the IBM Spectrum Protect library version. API_Wrong_Version_Parm_EXPLANATION=The caller's structure version is different than the IBM Spectrum Protect library version. API_Wrong_Version_Parm_SYSACT=The system returns to the calling procedure. API_Wrong_Version_Parm_URESP=Ensure that the stVersion field is set with the value in the header file. Recompile the application with the latest header files. # 0246 API_Need_To_Call_EndTxn=ANS0246E Issue dsmEndTxn and then begin a new transaction session. API_Need_To_Call_EndTxn_EXPLANATION=This transaction must be ended and a new one must be started due to one of the following reasons: The destination changed. The byte limit is exceeded The maximum number of objects is exceeded. API_Need_To_Call_EndTxn_SYSACT=The system returns to the calling procedure. API_Need_To_Call_EndTxn_URESP=Issue dsmEndTxn and start a new transaction session. # 0247 API_Obj_Excluded=ANS0247E The backup or archive object is excluded from processing. API_Obj_Excluded_EXPLANATION=The backup or archive object is excluded from processing. API_Obj_Excluded_SYSACT=The system returns to the calling procedure. API_Obj_Excluded_URESP=Verify the objName and Exclude lists. # 0248 API_No_Backup_CG=ANS0248E The backup object does not have a copy group. API_No_Backup_CG_EXPLANATION=The backup object does not have a copy group. API_No_Backup_CG_SYSACT=The system returns to the calling procedure. API_No_Backup_CG_URESP=Verify server policy definitions. # 0249 API_No_Archive_CG=ANS0249E The archive object does not have a copy group. API_No_Archive_CG_EXPLANATION=The archive object does not have a copy group. API_No_Archive_CG_SYSACT=The system returns to the calling procedure. API_No_Archive_CG_URESP=Verify server policy definitions. # 0250 API_Internal_Mem_Error=ANS0250E Memory used by the IBM Spectrum Protect API has been corrupted. API_Internal_Mem_Error_EXPLANATION=Memory used by the IBM Spectrum Protect API has been corrupted. API_Internal_Mem_Error_SYSACT=The system returns to the calling procedure. API_Internal_Mem_Error_URESP=Retry the operation. If the problem continues, contact your system administrator or service representative. # 0251 API_Descr_Too_Long=ANS0251E The sendObj Archive description is too long. API_Descr_Too_Long_EXPLANATION=The sendObj Archive description is too long. API_Descr_Too_Long_SYSACT=The system returns to the calling procedure. API_Descr_Too_Long_URESP=The sndArchiveData.descr string must be less than or equal to DSM_MAX_DESCR_LENGTH. # 0252 API_ObjInfo_Too_Long=ANS0252E The sendObj ObjAttr.objInfo is too long. API_ObjInfo_Too_Long_EXPLANATION=The sendObj ObjAttr.objInfo is too long. API_ObjInfo_Too_Long_SYSACT=The system returns to the calling procedure. API_ObjInfo_Too_Long_URESP=The objInfo field must be less than or equal to DSM_MAX_OBJINFO_LENGTH. # 0253 API_HL_Too_Long=ANS0253E The sendObj dsmObjName.hl is too long. API_HL_Too_Long_EXPLANATION=The sendObj dsmObjName.hl is too long. API_HL_Too_Long_SYSACT=The system returns to the calling procedure. API_HL_Too_Long_URESP=The hl field must be less than or equal to DSM_MAX_HL_LENGTH. # 0254 API_Password_Too_Long=ANS0254E The password, or encryptionPassword string provided is too long. API_Password_Too_Long_EXPLANATION=The value provided for password or encryptionPassword is too long. API_Password_Too_Long_SYSACT=The system returns to the calling procedure. API_Password_Too_Long_URESP=The password or encrypionPassword field must be less than DSM_MAX_VERIFIER_LENGTH. # 0255 API_FS_Too_Long=ANS0255E The sendObj dsmObjName.fs is too long. API_FS_Too_Long_EXPLANATION=The sendObj dsmObjName.fs is too long. API_FS_Too_Long_SYSACT=The system returns to the calling procedure. API_FS_Too_Long_URESP=The fs field must be less than or equal to DSM_MAX_FS_LENGTH. # 0256 API_LL_Too_Long=ANS0256E The sendObj dsmObjName.ll is too long. API_LL_Too_Long_EXPLANATION=The sendObj dsmObjName.ll is too long. API_LL_Too_Long_SYSACT=The system returns to the calling procedure. API_LL_Too_Long_URESP=The ll field must be less than or equal to DSM_MAX_LL_LENGTH. # 0257 API_FSInfo_Too_Long=ANS0257E On RegisterFS or UpdateFS the fsAttr's fsInfo is too long. API_FSInfo_Too_Long_EXPLANATION=On RegisterFS or UpdateFS the fsAttr's fsInfo is too long. API_FSInfo_Too_Long_SYSACT=The system returns to the calling procedure. API_FSInfo_Too_Long_URESP=The fsInfo field must be less than or equal to DSM_MAX_FSINFO_LENGTH. # 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=The dataBlk buffer is too small for the query response. API_Buff_Too_Small_SYSACT=The system returns to the calling procedure. API_Buff_Too_Small_URESP=On dsmGetNextQObj ensure that the dataBlk buffer is at least as big as the query response structure. # 0261 API_No_Config_File=ANS0261E The configuration file specified on dsmInit cannot be opened. API_No_Config_File_EXPLANATION=The configuration file specified on dsmInit cannot be opened. API_No_Config_File_SYSACT=The system returns to the calling procedure. API_No_Config_File_URESP=Verify the file name. # 0262 API_No_InclExcl_File=ANS0262E The Include/Exclude definition file was not found.\n API_No_InclExcl_File_EXPLANATION=The Include/Exclude definition file was not found. API_No_InclExcl_File_SYSACT=The system returns to the calling procedure. API_No_InclExcl_File_URESP=Verify the file name on the Inclexcl option. # 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=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_SYSACT=The system returns to the calling procedure. API_No_Sys_Or_InclExcl_File_URESP=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. # 0264 API_Only_Root=ANS0264E Only a UNIX root user can execute dsmChangePW or dsmDeleteFS. API_Only_Root_EXPLANATION=Only a UNIX root user can execute dsmChangePW or dsmDeleteFS. API_Only_Root_SYSACT=The system returns to the calling procedure. API_Only_Root_URESP=Run this program as a root user. # 0265 API_Issue_BindMC=ANS0265E You must issue dsmBindMC before dsmSendObj. API_Issue_BindMC_EXPLANATION=You must issue dsmBindMC before dsmSendObj. API_Issue_BindMC_SYSACT=The system returns to the calling procedure. API_Issue_BindMC_URESP=Modify your program. # 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=The high level qualifier for the object name is invalid. API_Invalid_Highlevel_Qualifier_SYSACT=The system returns to the calling procedure. API_Invalid_Highlevel_Qualifier_URESP=High level qualifier of the object name should start with the directory delimiter. # 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=The number of objects (numObjId) specified on the dsmBeginGetData call exceeds DSM_MAX_GET_OBJ | DSM_MAX_PARTIAL_GET_OBJ. API_Numobj_Exceed_SYSACT=The system returns to the calling procedure. API_Numobj_Exceed_URESP=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. # 0285 API_Invalid_Action=ANS0285E The update action is invalid. API_Invalid_Action_EXPLANATION=The dsmUpdateFS or dsmUpdateObj action is invalid. API_Invalid_Action_SYSACT=The system returns to the calling procedure. API_Invalid_Action_URESP=Correct the action value. Valid values are defined in dsmapitd.h and documented in our Using the API book. # 0286 API_Key_Missing=ANS0286E The key file is missing. API_Key_Missing_EXPLANATION=The key file for Data Protection for Oracle cannot be found. API_Key_Missing_SYSACT=The system returns to the calling procedure. API_Key_Missing_URESP=Ensure that you have ordered the Data Protection for Oracle, and install the key file. # 0287 API_Key_Bad=ANS0287E The key file content is invalid. API_Key_Bad_EXPLANATION=The key file content for Data Protection for Oracle is invalid. API_Key_Bad_SYSACT=The system returns to the calling procedure. API_Key_Bad_URESP=Ensure that you have ordered the Data Protection for Oracle, and install the key file. # 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=The user id you specified is currently locked on the server. SESS_Reject_User_Id_Locked_SYSACT=Session was not started. SESS_Reject_User_Id_Locked_URESP=Check with your system administrator to find out why your user id is locked. # 0300 GUI_NAS_OBJECT=Nas Object # 0304 COM_Password_Too_Short=ANS0304E The password is too short.\n COM_Password_Too_Short_EXPLANATION=The new password does not have enough characters. COM_Password_Too_Short_SYSACT=The password is not updated on the server. COM_Password_Too_Short_URESP=Choose a different password. Contact your IBM Spectrum Protect administrator to lean the password requirements. # 0305 COM_Password_Too_Young=ANS0305E It is too soon after the previous update to change the password.\n COM_Password_Too_Young_EXPLANATION=The password cannot be changed since not enough time has elapsed since the last password update. COM_Password_Too_Young_SYSACT=The password is not updated on the server. COM_Password_Too_Young_URESP=Try to change your password again later. # 0306 COM_Password_In_History=ANS0306E The password was previously used.\n COM_Password_In_History_EXPLANATION=The new password that you entered was previously used. COM_Password_In_History_SYSACT=The password is not updated on the server. COM_Password_In_History_URESP=Choose a different password. # 0307 COM_Password_Not_Complex=ANS0307E The password does not meet the requirements.\n COM_Password_Not_Complex_EXPLANATION=The new password that you entered does not meet the requirements, such as the number of special characters or digits. COM_Password_Not_Complex_SYSACT=The password is not updated on the server. COM_Password_Not_Complex_URESP=Choose a different password. Contact your IBM Spectrum Protect administrator to learn the password requirements. # 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=The request to start a remote operation has failed for the indicated node and file space. The status and the reason for the failure are shown. GUI_REMOTE_OP_FAILED_TO_START_STATUS_REASON_SYSACT=Processing ends. GUI_REMOTE_OP_FAILED_TO_START_STATUS_REASON_URESP=Contact your system administrator for more information. # 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=The request to start a remote operation has failed for the indicated node and file space. The status of the failure is shown. GUI_REMOTE_OP_FAILED_TO_START_STATUS_SYSACT=Current operation has ended. GUI_REMOTE_OP_FAILED_TO_START_STATUS_URESP=Contact your system administrator for more information. # 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=An invalid value for a handle or dataPtr has been passed into the API. API_Invalid_Tsmbuffer_SYSACT=The system returns to the calling procedure. API_Invalid_Tsmbuffer_URESP=There is a problem with the calling application. Verify the values of the tsmBuffHandle and dataptr passed to the API. # 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=An invalid number of bytes was copied to a tsmBuffer. API_Too_many_Bytes_SYSACT=The system returns to the calling procedure. API_Too_many_Bytes_URESP=There is a problem with the calling application. Verify the number of bytes copied into the tsmBuffer. # 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=An application is trying to terminate a session, but is still holding some tsmBuffers. API_Must_Release_Buffer_SYSACT=The system returns to the calling procedure. API_Must_Release_Buffer_URESP=The application must return all buffers for this session by calling tsmReleaseBuffer, and then issue dsmTerminate. # 0314 API_Buff_Array_Error=ANS0314E An internal error occurred in the tsmBuffer array. API_Buff_Array_Error_EXPLANATION=An internal API buffer array error occurred. API_Buff_Array_Error_SYSACT=The system returns to the calling procedure. API_Buff_Array_Error_URESP=Try the operation again. If the problem continues, contact your system administrator or service representative. # 0321 API_Null_Msg=ANS0321E msg parameter for dsmRCMsg is a NULL pointer. API_Null_Msg_EXPLANATION=The message parameter for dsmRCMsg is a NULL pointer. API_Null_Msg_SYSACT=The system returns to the calling procedure. API_Null_Msg_URESP=Allocate enough space for the message parameter. # 0322 API_Invalid_Retcode=ANS0322E no text available for this return code. API_Invalid_Retcode_EXPLANATION=The dsmRC parameter for dsmRCMsg is an unsupported return code. API_Invalid_Retcode_SYSACT=The system returns to the calling procedure. API_Invalid_Retcode_URESP=Specify a valid value. # 0323 API_Invalid_Offset=ANS0323E partialObjOffset value for partial object retrieve is invalid. API_Invalid_Offset_EXPLANATION=The partialObjOffset value for partial object retrieve is invalid. API_Invalid_Offset_SYSACT=The system returns to the calling procedure. API_Invalid_Offset_URESP=Specify a valid value. # 0324 API_Invalid_Length=ANS0324E partialObjLength value for partial object retrieve is invalid. API_Invalid_Length_EXPLANATION=partialObjLength value for partial object retrieve is invalid. API_Invalid_Length_SYSACT=The system returns to the calling procedure. API_Invalid_Length_URESP=Specify a valid value. # 0325 API_POR_Not_Supported=ANS0325E Partial Object Retrieve is not supported on this server. API_POR_Not_Supported_EXPLANATION=The IBM Spectrum Protect server specified by the user does not support partial object retrieve. API_POR_Not_Supported_SYSACT=The system returns to the calling procedure. API_POR_Not_Supported_URESP=Specify a IBM Spectrum Protect server which supports the partial object retrieve function. # 0326 API_Exceed_Max_MP=ANS0326E This node has exceeded its maximum number of mount points. API_Exceed_Max_MP_EXPLANATION=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 IBM Spectrum Protect administrator defines the maximum number of mount points with the MAXNUMMP property of your node definition. API_Exceed_Max_MP_SYSACT=The object is skipped API_Exceed_Max_MP_URESP=If you are performing any other operations that might be using mount points, wait until those operations are complete, then try the failed operation again. Otherwise contact your IBM Spectrum Protect administrator for further assistance # 0327 API_Duplicate_Object=ANS0327E A duplicate object was found, operation cannot complete. API_Duplicate_Object_EXPLANATION=A duplicate object was found, operation cannot complete. API_Duplicate_Object_SYSACT=The requested operation failed. API_Duplicate_Object_URESP=Try the operation with a different file specification. # 0329 GUI_MB_MOVED=MB Moved # 0330 API_Invalid_Access_Type=ANS0330E The dsmSetAccess access Type is invalid. API_Invalid_Access_Type_EXPLANATION=The dsmSetAccess accessType is invalid. API_Invalid_Access_Type_SYSACT=The system returns to the calling procedure. API_Invalid_Access_Type_URESP=The accessType must be one of the following: atBackup atArchive # 0331 API_No_Files_Backed_Up=ANS0331E No files have been previously backed up for this filename/filespace. API_No_Files_Backed_Up_EXPLANATION=You tried to set access to files when no files for the specified filename, drive or file system were previously backed up. API_No_Files_Backed_Up_SYSACT=Processing stopped. API_No_Files_Backed_Up_URESP=Ensure that the correct drive or file system was specified and that files are backed up for you to set access. # 0332 API_No_Files_Archived=ANS0332E No files have been previously archived for this filename/filespace. API_No_Files_Archived_EXPLANATION=You tried to set access to files when no files for the specified filename, drive or file system were previously archived. API_No_Files_Archived_SYSACT=Processing stopped. API_No_Files_Archived_URESP=Ensure that the correct drive or file system was specified and that files are archived for you to set access. # 0333 CLI_Abort_Mover_Type=ANS0333E Unknown Remote Mover type CLI_Abort_Mover_Type_EXPLANATION=The specified Remote Mover type is unknown. CLI_Abort_Mover_Type_SYSACT=Current operation has ended. CLI_Abort_Mover_Type_URESP=Contact your system administrator for more information. # 0334 CLI_Abort_Item_In_Use=ANS0334E An Operation for the requested node and file space is already in progress. CLI_Abort_Item_In_Use_EXPLANATION=A request has been made to use a data mover to perform an operation for the indicated node and file space. Since an operation for this node and file space is already in progress, the new operation cannot be performed. CLI_Abort_Item_In_Use_SYSACT=Current operation has ended. CLI_Abort_Item_In_Use_URESP=Retry the operation at a later time. # 0335 CLI_Abort_Lock_Conflict=ANS0335E System resource in use CLI_Abort_Lock_Conflict_EXPLANATION=A required resource is in use by another command or process. CLI_Abort_Lock_Conflict_SYSACT=Current operation has ended. CLI_Abort_Lock_Conflict_URESP=Retry the operation at a later time. # 0336 CLI_Abort_Srv_Plugin_Comm_Error=ANS0336E Server plugin communication error CLI_Abort_Srv_Plugin_Comm_Error_EXPLANATION=Communication between a server plugin module and a NAS filer failed. CLI_Abort_Srv_Plugin_Comm_Error_SYSACT=Current operation has ended. CLI_Abort_Srv_Plugin_Comm_Error_URESP=Contact your system administrator for more information. # 0337 CLI_Abort_Srv_Plugin_Os_Error=ANS0337E Server plugin detected unsupported NAS filer operating system. CLI_Abort_Srv_Plugin_Os_Error_EXPLANATION=A plugin module detected that a NAS filer is running an unsupported operating system or operating system level. CLI_Abort_Srv_Plugin_Os_Error_SYSACT=Current operation has ended. CLI_Abort_Srv_Plugin_Os_Error_URESP=Contact your system administrator for more information. # 0338 CLI_Abort_Invalid_Operation=ANS0338E An invalid operation was attempted on a node CLI_Abort_Invalid_Operation_EXPLANATION=The operation is not valid. CLI_Abort_Invalid_Operation_SYSACT=Current operation has ended. CLI_Abort_Invalid_Operation_URESP=Contact your system administrator for more information. # 0339 CLI_Abort_Stgpool_Undefined=ANS0339E The specified target storage pool is not defined. CLI_Abort_Stgpool_Undefined_EXPLANATION=The storage pool is not defined. CLI_Abort_Stgpool_Undefined_SYSACT=Current operation has ended. CLI_Abort_Stgpool_Undefined_URESP=Contact your system administrator for more information. # 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=none CLI_Abort_Invalid_Data_Format_SYSACT=Current operation has ended. CLI_Abort_Invalid_Data_Format_URESP=Contact your system administrator for more information. # 0341 CLI_Abort_Datamover_Undefined=ANS0341E No associated data mover is defined for the given node.\n CLI_Abort_Datamover_Undefined_EXPLANATION=none CLI_Abort_Datamover_Undefined_SYSACT=Current operation has ended. CLI_Abort_Datamover_Undefined_URESP=Contact your system administrator for more information. # 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=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. CLI_Abort_Crc_Failed_SYSACT=In some cases, the client can indicate the failure to the server and retry the operation. CLI_Abort_Crc_Failed_URESP=Check the trace log for additional information and retry the operation. If the problem persists, contact your system administrator. # 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=An invalid operation was attempted on a logical group. CLI_Abort_Invalid_Group_Action_SYSACT=The current operation stops. CLI_Abort_Invalid_Group_Action_URESP=Retry a valid operation. # 0344 API_Senddata_With_Zero_Size=ANS0344E Cannot Send data with a zero byte sizeEstimate. API_Senddata_With_Zero_Size_EXPLANATION=You cannot send data for an object with size estimate = 0. API_Senddata_With_Zero_Size_SYSACT=The system returns to the calling procedure. API_Senddata_With_Zero_Size_URESP=Set size estimate greater than 0 in dsmSendObj. # 0345 CLI_Abort_Disk_Undefined=ANS0345E Remote disk not defined. CLI_Abort_Disk_Undefined_EXPLANATION=An operation was attempted on a remote disk that is not defined. CLI_Abort_Disk_Undefined_SYSACT=The current operation stops. CLI_Abort_Disk_Undefined_URESP=Define the proper remote disk. # 0346 CLI_Abort_Bad_Destination=ANS0346E Input destination does not match expected destination. CLI_Abort_Bad_Destination_EXPLANATION=Input destination does not match expected destination. CLI_Abort_Bad_Destination_SYSACT=The current operation stops. CLI_Abort_Bad_Destination_URESP=Retry operation with proper destination. # 0347 CLI_Abort_Datamover_Not_Available=ANS0347E Data mover is not available. CLI_Abort_Datamover_Not_Available_EXPLANATION=Data mover is not available. CLI_Abort_Datamover_Not_Available_SYSACT=The current operation stops. CLI_Abort_Datamover_Not_Available_URESP=Retry operation with a proper Data mover. # 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=Operation failed because the copy continue option was set to NO. CLI_Abort_Stgpool_Copy_Cont_No_SYSACT=The current operation stops. CLI_Abort_Stgpool_Copy_Cont_No_URESP=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. # 0349 CLI_Abort_Retry_Single_Txn=ANS0349E Transaction failed because of a problem during a store operation. CLI_Abort_Retry_Single_Txn_EXPLANATION=Transaction failed because of a problem during a store operation. This error is typical when the next storage pool has a different copy storage pool list and we switch to this pool in the middle of a transaction. CLI_Abort_Retry_Single_Txn_SYSACT=Transaction is aborted. CLI_Abort_Retry_Single_Txn_URESP=Resend objects in separate transactions. # 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=The node or user does not have proper authority to perform this operation. CLI_Abort_Node_Not_Authorized_SYSACT=The transaction is ended. CLI_Abort_Node_Not_Authorized_URESP=Check the authority for the specified object. # 0352 CLI_Abort_License_Violation=ANS0352E The operation is not permitted due to server licenses values.\n CLI_Abort_License_Violation_EXPLANATION=The node or user is trying to perform an operation that either exceeds license values, or is not licensed. CLI_Abort_License_Violation_SYSACT=The session is rejected or the transaction is cancelled, ending the current operation. CLI_Abort_License_Violation_URESP=See your system administrator. # 0353 API_Invalid_DataBlk=ANS0353E When using useTsmBuffers, dataBlk must be NULL in calls to dsmSendObj and dsmGetObj. API_Invalid_DataBlk_EXPLANATION=The value for dataBlk must be NULL when using useTsmBuffers. API_Invalid_DataBlk_SYSACT=The system returns to the calling procedure. API_Invalid_DataBlk_URESP=There is a problem with the calling application. Contact your application provider # 0354 API_Encr_Not_Allowed=ANS0354E Encryption is not allowed when using useTsmBuffers. API_Encr_Not_Allowed_EXPLANATION=useTsmBuffers does not support encryption. API_Encr_Not_Allowed_SYSACT=The system returns to the calling procedure. API_Encr_Not_Allowed_URESP=Try the operation again, without using useTsmBuffers, or disable encryption for this operation. # 0355 API_Obj_Compressed=ANS0355E This object cannot be restored/retrieved using useTsmBuffers, because it is compressed. API_Obj_Compressed_EXPLANATION=useTsmBuffers does not support compression. API_Obj_Compressed_SYSACT=The system returns to the calling procedure. API_Obj_Compressed_URESP=Try the operation again, without using useTsmBuffers. # 0356 API_Obj_Encrypted=ANS0356E This object cannot be restored/retrieved using useTsmBuffers, because it is encrypted. API_Obj_Encrypted_EXPLANATION=useTsmBuffers does not support encryption. API_Obj_Encrypted_SYSACT=The system returns to the calling procedure. API_Obj_Encrypted_URESP=Try the operation again, without using useTsmBuffers. # 0357 API_POR_Not_Allowed=ANS0357E When using useTsmBuffers, a restore/retrieve with partial object restore is not allowed. API_POR_Not_Allowed_EXPLANATION=useTsmBuffers does not support partial object restore. API_POR_Not_Allowed_SYSACT=The system returns to the calling procedure. API_POR_Not_Allowed_URESP=Make sure the calling application is either using Partial object restore or useTsmBuffers. # 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=There was no encryption key found in the password file, or no key was provided by the application. API_No_Encryption_Key_SYSACT=The system returns to the calling procedure. API_No_Encryption_Key_URESP=If you are using -encryptkey=prompt, make sure there is a value in encryptionPasswordP and that bEncryptKeyEnabled is set to true. # 0359 API_Encr_Conflict=ANS0359E Conflicting encryption key options have been specified. API_Encr_Conflict_EXPLANATION=When using the ENABLEENCRYPTKEY option, the parameter bEncryptKeyEnabled for the IBM Spectrum Protect API dsmInitExIn_t and tsmInitExIn_t structures cannot be set to bTrue. API_Encr_Conflict_SYSACT=The system returns to the calling procedure. API_Encr_Conflict_URESP=Either remove the ENABLEENCRYPTKEY option from the options file, or set the parameter bEncryptKeyEnabled to bFalse in the program using the IBM Spectrum Protect API. # 0361 CLI_Generic_Diag_LogMsg=ANS0361I DIAG: # 0362 CLI_No_Server_Memory=ANS0362E There are insufficient Windows system resources to process this command. CLI_No_Server_Memory_EXPLANATION=This problem can occur during backup of a shared directory. The most likely reason is the 'IRPStackSize' setting on the computer that hosts the shared directory is too small. CLI_No_Server_Memory_SYSACT=The file is skipped. CLI_No_Server_Memory_URESP=Check the Windows event viewer for event ID 2011 on the computer that hosts the shared directory. This event indicates that the configuration parameter IRPStackSize is too small. IRPStackSize is a setting of type DWORD located in Windows registry key HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\services\\LanmanServer\\Parameters. If the IRPStackSize value is less than 20, or IRPStackSize is not specified, then set the value to 20, restart the system, and try the operation again. The default IRPStackSize value is 15. Attention: Consult with your Windows system administrator before making changes to the Windows registry or the problem persists after changing the IRPStackSize value to 20. # 0373 CLI_VM_SAN_POLICY_CHANGED=ANS0373I The SAN Policy of the system is set to '{0}'.\n # 0374 BAREST_CAD_NOT_RUNNING=ANS0374E The CAD service is not running on the local node.\n BAREST_CAD_NOT_RUNNING_EXPLANATION=The CAD service is not running. BAREST_CAD_NOT_RUNNING_SYSACT=The operation cannot continue without a connection to the CAD service. BAREST_CAD_NOT_RUNNING_URESP=Make sure that the CAD service is running and configured correctly. # 0375 BAREST_FILESPACE_LENGTH=ANS0375E The fileSpace parameter is either not defined or too long.\n BAREST_FILESPACE_LENGTH_EXPLANATION=The fileSpace parameter cannot be empty and cannot be longer than 1024 characters. BAREST_FILESPACE_LENGTH_SYSACT=The operation cannot continue. BAREST_FILESPACE_LENGTH_URESP=Make sure that the fileSpace parameter is used correctly. # 0376 BAREST_CODEPAGE_INVALID=ANS0376E The value for the codePage parameter is incorrect.\n BAREST_CODEPAGE_INVALID_EXPLANATION=The codePage parameter can only be "MBCS" or "UCS2". BAREST_CODEPAGE_INVALID_SYSACT=The operation cannot continue. BAREST_CODEPAGE_INVALID_URESP=Make sure that the codePage parameter is used correctly. # 0377 BAREST_PATH_TO_LONG=ANS0377E The value for the path parameter is incorrect.\n BAREST_PATH_TO_LONG_EXPLANATION=The path parameter cannot be longer than 6000 characters. BAREST_PATH_TO_LONG_SYSACT=The operation cannot continue. BAREST_PATH_TO_LONG_URESP=Make sure that the path parameter is used correctly. # 0378 BAREST_INVALID_NAME=ANS0378E The value for the name parameter is incorrect.\n BAREST_INVALID_NAME_EXPLANATION=The name parameter cannot be longer than 512 characters and cannot start with the directory delimiter. BAREST_INVALID_NAME_SYSACT=The operation cannot continue. BAREST_INVALID_NAME_URESP=Make sure that the name parameter is used correctly. # 0379 BAREST_INVALID_STATUS=ANS0379E The value for the status parameter is incorrect.\n BAREST_INVALID_STATUS_EXPLANATION=The status parameter can only be "ALL", "ACTIVE" or "INACTIVE". BAREST_INVALID_STATUS_SYSACT=The operation cannot continue. BAREST_INVALID_STATUS_URESP=Make sure that the status parameter is used correctly. # 0380 BAREST_INVALID_TYPE=ANS0380E The value for the type parameter is incorrect.\n BAREST_INVALID_TYPE_EXPLANATION=The type parameter can only be "FILE" or "DIR". BAREST_INVALID_TYPE_SYSACT=The operation cannot continue. BAREST_INVALID_TYPE_URESP=Make sure that the type parameter is used correctly. # 0381 BAREST_INVALID_DATETIME=ANS0381E The value for either the startDateTime or endDateTime parameter is incorrect.\n BAREST_INVALID_DATETIME_EXPLANATION=The startDateTime and endDateTime parameters can only be a valid JSON date time format. BAREST_INVALID_DATETIME_SYSACT=The operation cannot continue. BAREST_INVALID_DATETIME_URESP=Make sure that the startDateTime and endDateTime parameters are used correctly. # 0382 BAREST_INVALID_JSON=ANS0382E The rest call JSON data is missing values.\n BAREST_INVALID_JSON_EXPLANATION=The JSON data for the rest call are incorrect and cannot be processed. BAREST_INVALID_JSON_SYSACT=The operation cannot continue. BAREST_INVALID_JSON_URESP=Make sure that the JSON for the rest call is correct and has all needed values. # 0400 API_Almgr_Open_Fail=ANS0400E License file could not be opened. API_Almgr_Open_Fail_EXPLANATION=The license file was not found, or could not be opened because of permissions or the file is corrupted. API_Almgr_Open_Fail_SYSACT=The system returns to the calling procedure. API_Almgr_Open_Fail_URESP=Check permissions on file. See if the license file is in the correct place. # 0401 API_Almgr_Read_Fail=ANS0401E Read failure on the license file. API_Almgr_Read_Fail_EXPLANATION=The license file was not found, or could not be opened because of permissions, or the file is corrupted. API_Almgr_Read_Fail_SYSACT=The system returns to the calling procedure. API_Almgr_Read_Fail_URESP=Check permissions on file. See if the license file is in the correct place. # 0402 API_Almgr_Write_Fail=ANS0402E Write failure on the license file. API_Almgr_Write_Fail_EXPLANATION=The license file was not found, or could not be opened because of permissions or the file is corrupted. API_Almgr_Write_Fail_SYSACT=The system returns to the calling procedure. API_Almgr_Write_Fail_URESP=Check permissions on file. See if license file is in the correct place. # 0403 API_Almgr_Data_Fmt=ANS0403E Data in the license file is not in a valid format. API_Almgr_Data_Fmt_EXPLANATION=The license file is not valid. API_Almgr_Data_Fmt_SYSACT=The system returns to the calling procedure. API_Almgr_Data_Fmt_URESP=User needs to obtain a new license. # 0404 API_Almgr_Cksum_bad=ANS0404E The checksum in the license file does not match the licenseregistration string. API_Almgr_Cksum_bad_EXPLANATION=The registration string is not valid. API_Almgr_Cksum_bad_SYSACT=The system returns to the calling procedure. API_Almgr_Cksum_bad_URESP=User needs to obtain a new license. # 0405 API_Almgr_Trial_exprd=ANS0405E This is an expired try and buy license. API_Almgr_Trial_exprd_EXPLANATION=The registration string is not valid. API_Almgr_Trial_exprd_SYSACT=The system returns to the calling procedure. API_Almgr_Trial_exprd_URESP=User needs to obtain a new license. # 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=Restoring inactive system state objects may cause system instability. Examples of possible problems include: \nRestoring inactive system state objects is not recommended unless you are certain that this is what you need to do. DSI_INACTIVE_SYSSTATE_Warning_SYSACT=If user responds with yes, the client will restore the object. If user responds with no, the client will cancel the operation. DSI_INACTIVE_SYSSTATE_Warning_URESP=Reply to the prompt. If you are unsure, reply no, and consult your system administrator or operating system vendor before proceeding further. # 0421 COM_Password_Not_Synchronized=ANS0421W Unable to synchronize the node password with the user id password provided.\n COM_Password_Not_Synchronized_EXPLANATION=The node password was not updated due to the reason described in the error message preceding this one. COM_Password_Not_Synchronized_SYSACT=The node password is not updated on the server. Next time you run the client you will be prompted for the password again. COM_Password_Not_Synchronized_URESP=See the preceding error message. # 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=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. DSI_JOURNALWIZ_DBPATHNETWORK_SYSACT=Processing continues. DSI_JOURNALWIZ_DBPATHNETWORK_URESP=Choose a local drive where journal databases will be stored. # 0423 CLI_Cannot_Create_Directory=ANS0423E Directory '{0}{1}{2}' cannot be created. Path does not exist.\n CLI_Cannot_Create_Directory_EXPLANATION=The operating system returned a "path not found" status when IBM Spectrum Protect attempted to create the directory needed for Automated System Recovery (ASR). One possible reason is that a multi disk system is restored to a single disk system. CLI_Cannot_Create_Directory_SYSACT=Processing stopped. CLI_Cannot_Create_Directory_URESP=Please verify that you are restoring to identical hardware and try again. # 0992 CLI_Invalid_DestFilespace=ANS0992E The destination filespace or drive letter is unavailable. For more details please see dsmerror.log. CLI_Invalid_DestFilespace_EXPLANATION=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. CLI_Invalid_DestFilespace_SYSACT=Objects which are part of this filespace are not processed. CLI_Invalid_DestFilespace_URESP=Try the command again, and specify a different destination for the object that was not processed. # 0995 Img_Volume_Lock_Failure_Ex=ANS0995E Volume '{0}' could not be locked.\n Img_Volume_Lock_Failure_Ex_EXPLANATION=The system call to lock the volume failed. Img_Volume_Lock_Failure_Ex_SYSACT=Processing stopped. Img_Volume_Lock_Failure_Ex_URESP=Please verify that no other application is accessing the volume. During restore of an image IBM Spectrum Protect must have exclusive use of the volume. # 1001 Img_NOT_SYSDrive_Skip=ANS1001E Volume being backed up was not a system volume. Skipped.\n Img_NOT_SYSDrive_Skip_EXPLANATION=User specified to back up system volume only. This volume was not backed up since this volume is not a system volume. Img_NOT_SYSDrive_Skip_SYSACT=Volume was not backed up. Img_NOT_SYSDrive_Skip_URESP=Use All option or use image backup command to backup this volume. # 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=The client encountered an error while obtaining the automatic include/exclude statements from the operating system. Possible reasons for this error include: CLI_OPERATING_SYSTEM_EXCLUDE_ERROR_SYSACT=Processing continues without the full list of operating system include/exclude statements. CLI_OPERATING_SYSTEM_EXCLUDE_ERROR_URESP=Ensure that you have access to the specified registry key and that entries are a MULTISZ values that contain: If the cause of this message can not be determined or resolved, contact IBM technical support for further assistance. # 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=The client cannot establish a connection to the server because the server is enabled for archive-retention protection enabled and the client is not. SESS_Reject_Client_Not_Archretprot_SYSACT=The session is not started. SESS_Reject_Client_Not_Archretprot_URESP=See your system administrator. # 1019 Img_Open_Failure=ANS1019E The volume could not be opened.\n Img_Open_Failure_EXPLANATION=An error occurred when IBM Spectrum Protect tried to open the volume for a backup or restore operation. Img_Open_Failure_SYSACT=The requested operation does not run. Img_Open_Failure_URESP=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. # 1022 GUI_CancelFailed=ANS1022E Cancel failed for node: {0} filesystem: {1} operation: {2} error: {3} GUI_CancelFailed_EXPLANATION=The request to cancel a remote operation has failed. The node, file space, operation and reason for the failure are shown. GUI_CancelFailed_SYSACT=Operation not cancelled. GUI_CancelFailed_URESP=Contact your system administrator for more information. # 1023 SESS_Reject_Nodetype_Mismatch=ANS1023E Session rejected: Node type mismatch\n SESS_Reject_Nodetype_Mismatch_EXPLANATION=Your node name is associated with a different type of operating system and cannot be used on this system. SESS_Reject_Nodetype_Mismatch_SYSACT=Current operation has been cancelled. SESS_Reject_Nodetype_Mismatch_URESP=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. # 1026 SESS_Protocol_Error=ANS1026E The session is rejected: There was a communications protocol error.\n SESS_Protocol_Error_EXPLANATION=An unexpected network message was received by the client. This could be caused by network problems or a programming error. SESS_Protocol_Error_SYSACT=The current operation has been cancelled. SESS_Protocol_Error_URESP=Verify that your communication path is functioning properly and try the operation again. If the problem persists, contact your IBM Spectrum Protect administrator for further assistance. # 1027 GUI_NodeCannotBeSelected=This node cannot be selected. # 1029 SESS_Communications_Severed=ANS1029E Communication with the IBM Spectrum Protect server is lost.\n SESS_Communications_Severed_EXPLANATION=This message is issued after the session with the IBM Spectrum Protect server is unexpectedly lost. The client error log might contain additional information regarding this problem. SESS_Communications_Severed_SYSACT=processing stops. SESS_Communications_Severed_URESP= # 1030 SESS_Memory_Exhausted=ANS1030E The operating system refused a request for memory allocation. SESS_Memory_Exhausted_EXPLANATION=Access to memory is required in order to store information as processing proceeds. In this case, more memory was requested than the operating system would allocate. Possible reasons include: The system is low on memory. The process in which the program runs has exceeded the maximum memory that it is allowed to allocate. Some other error condition occurred that caused the program to think it is out of memory. SESS_Memory_Exhausted_SYSACT=Requested operation cannot be completed. SESS_Memory_Exhausted_URESP=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 IBM Spectrum Protect task serially for each directory. If the IBM Spectrum Protect task is an incremental backup, use the option "-memoryefficientbackup=yes". # 1035 COM_OptFileNotFound=ANS1035S Options file '{0}' could not be found, or it cannot be read. \n COM_OptFileNotFound_EXPLANATION=Common reasons for this error include: COM_OptFileNotFound_SYSACT=IBM Spectrum Protect client processing stops. COM_OptFileNotFound_URESP=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 Spectrum Protect client manual specific to your operating system. If the problem persists, ask your IBM Spectrum Protect administrator for further assistance. # 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=The specified option or option value is not valid. 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. COM_Options_Emsg_SYSACT=Processing stops. COM_Options_Emsg_URESP=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. # 1037 COM_Invalid_Keyword=ANS1037S Invalid keyword specified\n COM_Invalid_Keyword_EXPLANATION=An incorrect keyword was found in the options file. COM_Invalid_Keyword_SYSACT=Processing stopped. COM_Invalid_Keyword_URESP=Correct the options file with valid entries. # 1038 COM_Invalid_Option=ANS1038S Invalid option specified.\n COM_Invalid_Option_EXPLANATION=An incorrect option was specified to IBM Spectrum Protect. COM_Invalid_Option_SYSACT=Processing stopped. COM_Invalid_Option_URESP=Correct the options used for running IBM Spectrum Protect. # 1039 COM_Patt_Too_Complex=ANS1039S The include or exclude pattern cannot be parsed.\n COM_Patt_Too_Complex_EXPLANATION=The pattern is formatted incorrectly or is too complex to be interpreted. COM_Patt_Too_Complex_SYSACT=Processing stopped. COM_Patt_Too_Complex_URESP=Verify that the include or exclude pattern is specified correctly. If the pattern is correct, then contact IBM technical support for further assistance. # 1040 COM_Patt_Missing_Bracket=ANS1040S Include/Exclude pattern is missing a closing bracket\n COM_Patt_Missing_Bracket_EXPLANATION=The include or exclude pattern is incorrectly constructed. The closing bracket is missing. COM_Patt_Missing_Bracket_SYSACT=Processing stopped. COM_Patt_Missing_Bracket_URESP=Correct the syntax for the pattern. # 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=
  1. The include/exclude pattern has a '...' without a beginning or ending directory delimiter.
  2. For Windows, the drive seperator is not immediately followed by a directory delimiter.
COM_Patt_Missing_Delim_SYSACT=Processing stopped. COM_Patt_Missing_Delim_URESP=Correct the syntax for the pattern. # 1043 COM_Unmatched_Quotes=ANS1043S Quotes are not matched\n COM_Unmatched_Quotes_EXPLANATION=The quotes specified in the pattern are not the same and do not make a set. COM_Unmatched_Quotes_SYSACT=Processing stopped. COM_Unmatched_Quotes_URESP=Correct the pattern by using matching quotes in the syntax. # 1048 Img_Device_Not_Local_Cl=ANS1048E Device '{0}' is not local\n Img_Device_Not_Local_Cl_EXPLANATION=The selected path is not a local device and therefore is not a valid object for image operations.\n Img_Device_Not_Local_Cl_SYSACT=The requested logical volume operation is not performed. Img_Device_Not_Local_Cl_URESP=Choose another object. # 1052 CLI_Direct_Storage_Agent_Unsupported=ANS1052E Direct connection to the Storage Agent is not allowed.\n CLI_Direct_Storage_Agent_Unsupported_EXPLANATION=You cannot connect directly to the Storage Agent. CLI_Direct_Storage_Agent_Unsupported_SYSACT=Processing stopped. CLI_Direct_Storage_Agent_Unsupported_URESP=To perform Lanfree operations using the Storage Agent, specify the ENABLELANFREE option in your options file, and restart the process. # 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=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. CLI_Sharename_Path_Not_Found_SYSACT=Processing stopped. CLI_Sharename_Path_Not_Found_URESP=Retry the command and specify a destination, or restore the directory tree first before trying to restore the share point. # 1058 CLI_Invalid_Restore_Destination=ANS1058E The restore destination cannot be reached.\n CLI_Invalid_Restore_Destination_EXPLANATION=Either the destination file system is invalid or it cannot be reached. CLI_Invalid_Restore_Destination_SYSACT=Processing stopped. CLI_Invalid_Restore_Destination_URESP=Try the command again using a different destination. # 1060 Fs_Not_A_Mount_Point=ANS1060E The specified path is not a mounted filesystem\n Fs_Not_A_Mount_Point_EXPLANATION=You entered a file system name that does not correspond to a mounted file system for this system. It is possible the file system name is misspelled, or simply that the file system is not currently mounted. Fs_Not_A_Mount_Point_SYSACT=The requested logical volume operation is not performed. Fs_Not_A_Mount_Point_URESP=Retry the operation, using name of a mounted file system. # 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=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. Dev_Is_Fs_SYSACT=The requested logical volume operation is not performed. Dev_Is_Fs_URESP=Try the operation again, using the file system name instead of the device name. # 1063 Img_Invalid_Drive=ANS1063E The specified path is not a valid file system or logical volume name.\n Img_Invalid_Drive_EXPLANATION=None. Img_Invalid_Drive_SYSACT=The logical volume operation is not performed. Img_Invalid_Drive_URESP=Try the operation again using a valid path. # 1064 Img_Internal_Err=ANS1064E An unexpected error occurred while processing the image operation. Img_Internal_Err_EXPLANATION=None. Img_Internal_Err_SYSACT=The requested operation does not run. Img_Internal_Err_URESP=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. # 1065 Img_Caller_Pilib_High=ANS1065E Library version of the image utility does not match that of the IBM Spectrum Protect API\n Img_Caller_Pilib_High_EXPLANATION=The current system has a mix of installed components. Img_Caller_Pilib_High_SYSACT=The requested logical volume operation is not performed. Img_Caller_Pilib_High_URESP=Re-install all IBM Spectrum Protect components # 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=None. Img_Rest_Ok_Mount_Fail_SYSACT=The file system is left unmounted. Img_Rest_Ok_Mount_Fail_URESP=Use the mount command to mount the file system. On AIX, run fsck if requested by the operating system. # 1067 Img_Os_Syscall_Err=ANS1067E A call to a system function returned an unexpected error. Img_Os_Syscall_Err_EXPLANATION=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 IBM Spectrum Protect client from reading the snapshot. Img_Os_Syscall_Err_SYSACT=The requested operation does not run. Img_Os_Syscall_Err_URESP=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. # 1068 Img_Device_Not_Local=ANS1068E The device is not local.\n Img_Device_Not_Local_EXPLANATION=The selected path is not a valid object for image operations. The selected path is either a remote device or a partition that resides on a multipath device.\n Img_Device_Not_Local_SYSACT=The requested logical volume operation is not performed. Img_Device_Not_Local_URESP=Choose another object. # 1069 Img_Read_Failure=ANS1069E An error occurred while reading data from the device\n Img_Read_Failure_EXPLANATION=An error occurred while reading data from the device. Windows Only: This could be due to bad sectors on the drive. Img_Read_Failure_SYSACT=The requested logical volume operation is not performed. Img_Read_Failure_URESP=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. # 1070 Img_Write_Failure=ANS1070E Write error\n Img_Write_Failure_EXPLANATION=An error occurred while writing data to the device. Img_Write_Failure_SYSACT=The requested logical volume operation is not performed. Img_Write_Failure_URESP=Re-try the operation, check error log for more information. # 1071 CLI_Inv_Domain=ANS1071E Invalid domain name entered: '{0}'\n CLI_Inv_Domain_EXPLANATION=You entered an invalid domain name. Verify 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. CLI_Inv_Domain_SYSACT=Processing continues if there are other file systems in the domain option to back up. CLI_Inv_Domain_URESP=Enter a valid drive or file system name (domain). # 1072 CLI_No_Volume_Label=ANS1072E Unable to continue operation; Drive '{0}' has no volume label.\n CLI_No_Volume_Label_EXPLANATION=The specified drive-name in the domain list does not have a volume label. CLI_No_Volume_Label_SYSACT=Processing stopped. CLI_No_Volume_Label_URESP=Use the system format utility to place a unique volume label on all drives on which you intend to run IBM Spectrum Protect. # 1077 GUI_LastImageBackup=Last Image Backup # 1080 GUI_NAS=NAS # 1085 VMBACKUP_VDDK_INVALID_SNAPSHOT_CONFIG=ANS1085E The VMware vStorage API reported an invalid snapshot configuration.\n VMBACKUP_VDDK_INVALID_SNAPSHOT_CONFIG_EXPLANATION=A VMware vStorage API error occurred due to an invalid snapshot configuration. VMBACKUP_VDDK_INVALID_SNAPSHOT_CONFIG_SYSACT=A VMware vStorage API error occurred, and the virtual machine backup failed. VMBACKUP_VDDK_INVALID_SNAPSHOT_CONFIG_URESP=Check the VMware logs for possible causes of the error, and retry the operation. # 1091 CLI_Comm_Error_During_Query=ANS1091E Communications error with server during object query\n CLI_Comm_Error_During_Query_EXPLANATION=An unexpected communications error occurred during an object query to the server. CLI_Comm_Error_During_Query_SYSACT=Processing stopped. CLI_Comm_Error_During_Query_URESP=Verify that communications are active between the client and server machines. Server outages, processor outages, and communication controller outages can cause this error. # 1092 CLI_No_Match_Found=ANS1092W No files matching search criteria were found\n CLI_No_Match_Found_EXPLANATION=You entered a search pattern or file name that cannot be found in the server database. CLI_No_Match_Found_SYSACT=Processing stopped. CLI_No_Match_Found_URESP=Ensure that your search pattern is correct, or specify a new search string. # 1094 VM_CREATE_SHARE_UNKNOWN_ERROR=ANS1094E An error occured trying to connect to the restore location on the virtual machine. Verify that the restore location exists on the virtual machine and that your account has access to it. VM_CREATE_SHARE_UNKNOWN_ERROR_EXPLANATION=During restore processing, the system creates a share to access the restore location on the virtual machine.\u00a0In this situation, the system was unable to create a share. This error typically occurs if the restore location does not exist or the user account does not have access to the location. VM_CREATE_SHARE_UNKNOWN_ERROR_SYSACT=The system was unable to create a share. VM_CREATE_SHARE_UNKNOWN_ERROR_URESP=Verify that the restore location exists on the virtual machine and that your account has access to it. # 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=This error occurs when you try to access another node's data. Either the node is not registered with the IBM Spectrum Protect server, or there is no active policy set for the node. CLI_NO_PS_Data_Found_SYSACT=Processing stops. CLI_NO_PS_Data_Found_URESP=Verify that the node whose data you are trying to access is registered with the IBM Spectrum Protect server. If you have more than one IBM Spectrum Protect server, make sure you are connecting to the correct server, then try the operation again. If the problem persists, contact your IBM Spectrum Protect administrator for further assistance. # 1101 CLI_Encrypt_Not_Authorized=ANS1101E User is not authorized to encrypt {0}{1}{2}.\n CLI_Encrypt_Not_Authorized_EXPLANATION=The user is not authorized to encrypt the file. Normally, only a IBM Spectrum Protect authorized user or a root user can use IBM Spectrum Protect encryption. However, a certain combination of PASSWORDACCESS and ENCRYPTKEY options may allow encryption operations by a non-authorized user. CLI_Encrypt_Not_Authorized_SYSACT=The file is not backed up or restored. CLI_Encrypt_Not_Authorized_URESP=Log in as a root or IBM Spectrum Protect authorized user and try the operation again. See IBM Spectrum Protect Backup-Archive Client Installation and User's Guide for the correct usage of the ENCRYPTKEY option. # 1103 CLI_Invalid_Management_Class=ANS1103E Invalid management class entered\n CLI_Invalid_Management_Class_EXPLANATION=You entered an invalid management class. CLI_Invalid_Management_Class_SYSACT=Requested operation is not possible. CLI_Invalid_Management_Class_URESP=Retry the operation using a valid management class. # 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=The management class for this file does not have a backup copy group specified. This file will not be backed up. CLI_MC_No_Back_CG_SYSACT=Processing stopped. CLI_MC_No_Back_CG_URESP=Add a valid backup copy group to the management class, and then retry the operation. # 1111 CLI_Invalid_Local_Management_Class=ANS1111E The requested operation is not possible using the management class that was entered.\n CLI_Invalid_Local_Management_Class_EXPLANATION=The management class is not valid because the Data Version Exists value is greater than 30. For local backups on a VVOL datastore, this value must be 1 - 30. CLI_Invalid_Local_Management_Class_SYSACT=Processing stopped. CLI_Invalid_Local_Management_Class_URESP=Retry the operation using a valid management class. # 1113 Img_Snapshot_Cache_Location_Invalid=ANS1113E The snapshot cache location is not valid.\n Img_Snapshot_Cache_Location_Invalid_EXPLANATION=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. Img_Snapshot_Cache_Location_Invalid_SYSACT=The client does not execute the snapshot backup operation. Img_Snapshot_Cache_Location_Invalid_URESP=Specify a different snapshot cache location using the SNAPSHOTCACHELOCATION option. # 1115 CLI_MC_Excluded=ANS1115W File '{0}{1}{2}' excluded by Include/Exclude list\n CLI_MC_Excluded_EXPLANATION=You can not back up, archive, or migrate files that are excluded. CLI_MC_Excluded_SYSACT=The file can not be processed. CLI_MC_Excluded_URESP=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 IBM Spectrum Protect administrator for further assistance. # 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=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. CLI_No_Label_SYSACT=The requested operation does not run. CLI_No_Label_URESP=Create a volume label on the removable media, then try the operation again. # 1134 CLI_Invalid_Drive_Spec=ANS1134E Drive {0} is an invalid drive specification\n CLI_Invalid_Drive_Spec_EXPLANATION=The specified drive name is not valid; the drive probably has not been defined. CLI_Invalid_Drive_Spec_SYSACT=Process skips the invalid drive and continues to the next drive. CLI_Invalid_Drive_Spec_URESP=Check the invalid drive. # 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=One drive is a substitute (SUBST) of the other drive. The SUBST drive cannot be backed up or archived. CLI_SUBST_Drive_SYSACT=The SUBST drive is skipped. Processing continues with the next drive. CLI_SUBST_Drive_URESP=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 - notation to remove a substitute drive if ALL-LOCAL is specified. # 1140 CLI_Invalid_SetAccess=ANS1140E Invalid format for Set Access command.\n CLI_Invalid_SetAccess_EXPLANATION=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. CLI_Invalid_SetAccess_SYSACT=Processing stopped, the command is not executed. CLI_Invalid_SetAccess_URESP=Use the HELP SET ACCESS command for complete details of usage, then enter the SET ACCESS command using the correct syntax. # 1147 CLI_File_Unavailable=ANS1147E File is temporarily unavailable.\n CLI_File_Unavailable_EXPLANATION=File is temporarily unavailable. CLI_File_Unavailable_SYSACT=File skipped. CLI_File_Unavailable_URESP=Check and see if file is locked by other process. If not, retry the command. # 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=An incremental backup was started, but no domain was selected. Possible reasons for this message include: CLI_NoFileSpaces_SYSACT=processing stops. CLI_NoFileSpaces_URESP=Verify that the DOMAIN statements are properly configured and try the backup again. DOMAIN statements can be in client option files (dsm.opt, dsm.sys), client option sets, schedule definitions, and scripted IBM Spectrum Protect commands. Corrective actions include: # 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=The local system account does not have a profile. Therefore you cannot restore its profile. CLI_NTRunning_as_Local_System_Account_SYSACT=Processing stops. CLI_NTRunning_as_Local_System_Account_URESP=Log on to the user whose profile you want to restore. # 1151 CLI_NOT_CLUSTER_Disk1=ANS1151E '{0}' is not a cluster disk.\n CLI_NOT_CLUSTER_Disk1_EXPLANATION=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. CLI_NOT_CLUSTER_Disk1_SYSACT=Processing stops. CLI_NOT_CLUSTER_Disk1_URESP=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 client to run in a cluster environment. # 1152 VMBACKUP_VDDK_FAILED_TO_QUIESCE_VM=ANS1152E The VMware vStorage API reported a failure to quiesce the virtual machine.\n VMBACKUP_VDDK_FAILED_TO_QUIESCE_VM_EXPLANATION=A VDDK error occurred while quiescing the virtual machine. VMBACKUP_VDDK_FAILED_TO_QUIESCE_VM_SYSACT=A VMware vStorage API error occurred, and the virtual machine backup failed. VMBACKUP_VDDK_FAILED_TO_QUIESCE_VM_URESP=This error can occur if there is a lot of activity on the virtual machine at the time the snapshot is occurring. Try setting the INCLUDE.VMSNAPSHOTATTEMPTS option to resolve this issue. Also, check the VMware logs for possible causes of the error, and try the operation again. # 1153 CLI_CLUSTER_Disk1=ANS1153E '{0}' is a cluster disk.\n CLI_CLUSTER_Disk1_EXPLANATION=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. CLI_CLUSTER_Disk1_SYSACT=Processing stops. CLI_CLUSTER_Disk1_URESP=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 client to run in a cluster environment. # 1155 CLI_NoImageDomain=ANS1155E No domain is available for image backup.\n CLI_NoImageDomain_EXPLANATION=An image backup was started, but no domain was specified. CLI_NoImageDomain_SYSACT=Processing stopped. CLI_NoImageDomain_URESP=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. # 1156 COM_Invalid_Nodename=ANS1156E NODENAME cannot be the local machine name when CLUSTERNODE is set to YES\n COM_Invalid_Nodename_EXPLANATION=When IBM Spectrum Protect is running as a cluster node, the node name cannot be the local machine name. COM_Invalid_Nodename_SYSACT=Processing stops. COM_Invalid_Nodename_URESP=Change the node name either to the cluster name or to any other name, and restart IBM Spectrum Protect. # 1162 Img_Mount_Failure=ANS1162E Filesystem could not be mounted\n Img_Mount_Failure_EXPLANATION=The system call to mount the file system failed. Img_Mount_Failure_SYSACT=The file system remains unmounted. Img_Mount_Failure_URESP=Use the mount command to mount the file system. On AIX, run fsck if requested by the operating system. # 1163 Img_Umount_Failure=ANS1163E Filesystem could not be unmounted.\n Img_Umount_Failure_EXPLANATION=The system call to unmount the file system failed. Img_Umount_Failure_SYSACT=The logical volume operation is not performed. Img_Umount_Failure_URESP=Make sure the device or file system is not being accessed, then retry the operation. # 1164 Img_Fs_Not_Mounted=ANS1164E Filesystem is not mounted\n Img_Fs_Not_Mounted_EXPLANATION=The named file system is not currently mounted. It must be mounted for IBM Spectrum Protect to perform an image backup. Img_Fs_Not_Mounted_SYSACT=The logical volume operation is not performed. Img_Fs_Not_Mounted_URESP=Mount the file system. # 1165 Img_Lv_Too_Small=ANS1165E Destination is smaller than source\n Img_Lv_Too_Small_EXPLANATION=The space allocation for the selected destination is smaller than the source. Img_Lv_Too_Small_SYSACT=The restore operation is not performed. Img_Lv_Too_Small_URESP=Choose a different, bigger destination or increase the size of the destination file space. # 1166 Img_Wrong_Fstype=ANS1166E Source and destination are not the same file system type.\n Img_Wrong_Fstype_EXPLANATION=The source and destination file system types do not match. Img_Wrong_Fstype_SYSACT=The requested logical volume operation is not performed. Img_Wrong_Fstype_URESP=Choose a destination that has the same file system type as the source. # 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=An error occurred using named pipe communication with the journal service. JOURNAL_NP_ERROR_SYSACT=Processing stops. JOURNAL_NP_ERROR_URESP=Restart the journal service, then try the operation again. If the problem persists, contact IBM technical support for further assistance. # 1194 VMBACKUP_VDDK_ANOTHER_TASK_IN_PROGRESS=ANS1194E The VMware vStorage API reported another task was in progress for the virtual machine.\n VMBACKUP_VDDK_ANOTHER_TASK_IN_PROGRESS_EXPLANATION=A VMware vStorage API error occurred due to another task in progress for the virtual machine. VMBACKUP_VDDK_ANOTHER_TASK_IN_PROGRESS_SYSACT=A VMware vStorage API error occurred, and the virtual machine backup failed. VMBACKUP_VDDK_ANOTHER_TASK_IN_PROGRESS_URESP=Wait for the other task to complete and try the operation again. # 1195 DSI_NTSecurity_AccessDenied=An error occurred accessing NTFS security information\n # 1196 DSI_NTPrivilege_NotHeld=A required NT privilege is not held\n # 1197 VMBACKUP_VDDK_READ_ERROR_GENERAL=ANS1197E A VMware Virtual Disk Kit (VDDK) API read failure occurred while reading data for backup.\n VMBACKUP_VDDK_READ_ERROR_GENERAL_EXPLANATION=There was a VMware Virtual Disk Kit (VDDK) API read error while reading data to backup. VMBACKUP_VDDK_READ_ERROR_GENERAL_SYSACT=A VMware Virtual Disk Kit (VDDK) API read error occurred, and the virtual machine backup failed. VMBACKUP_VDDK_READ_ERROR_GENERAL_URESP=Check the VMware logs for possible causes of the read error, and try the operation again. # 1198 VMBACKUP_VDDK_READ_ERROR_NO_MEMORY=ANS1198E The VMware Virtual Disk Kit (VDDK) API reported an out-of-memory condition while reading data for backup.\n VMBACKUP_VDDK_READ_ERROR_NO_MEMORY_EXPLANATION=A VMware Virtual Disk Kit (VDDK) API read error occurred due to out-of-memory condition while reading data to backup. VMBACKUP_VDDK_READ_ERROR_NO_MEMORY_SYSACT=A VMware Virtual Disk Kit (VDDK) API read error occurred. The virtual machine backup failed. VMBACKUP_VDDK_READ_ERROR_NO_MEMORY_URESP=Check the VMware logs for possible causes of the read error, and try the operation again. # 1199 Img_Snapshot_PreCmd_Failed=ANS1199E The PRESNAPSHOTCMD command failed. The image snapshot backup will not be executed.\n Img_Snapshot_PreCmd_Failed_EXPLANATION=The command specified by the PRESNAPSHOTCMD option must complete successfully in order to execute the image snapshot backup. If the command completed with a return code of 0 (zero), it is considered to have completed successfully. If the command completed with any other return code, it is considered to have failed. If the command failed then the image snapshot backup is not executed. Img_Snapshot_PreCmd_Failed_SYSACT=The client does not execute the image snapshot backup operation. Img_Snapshot_PreCmd_Failed_URESP=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. # 1200 Img_Snapshot_PostCmd_Failed=ANS1200W The POSTSNAPSHOTCMD command completed with a non-zero return code.\n Img_Snapshot_PostCmd_Failed_EXPLANATION=If the command specified by the POSTSNAPSHOTCMD option completed with a non-zero return code, then the image snapshot backup operation will continue, but with a warning-level result. Note that the result of the POSTSNAPSHOTCMD command will not supercede a higher result from the image snapshot backup command. For example, if the image snapshot backup command completed with a return code of 12, the image snapshot backup will be considered to have completed with a return code of 12, regardless of the outcome of the POSTSNAPSHOTCMD command. Img_Snapshot_PostCmd_Failed_SYSACT=The image snapshot backup continues, but with a warning return code of at least 8. Img_Snapshot_PostCmd_Failed_URESP=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. # 1202 Img_Toc_Send_Fail=ANS1202E TOC backup for the image failed. Check log files.\n Img_Toc_Send_Fail_EXPLANATION=An error occurred during backup of the table of contents. Check the error log for more information. Img_Toc_Send_Fail_SYSACT=The requested logical volume operation is not performed. Img_Toc_Send_Fail_URESP=Check error log. # 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=There is no TOC for selected backup set DSJ_EXPRESS_BSET_LOADTOC_ERROR_SYSACT=Expansion of selected backup set will not be possible. Will only be able to restore the whole backup set. DSJ_EXPRESS_BSET_LOADTOC_ERROR_URESP=Please contact server administrator to regenerate TOC for backup set before backup set can be expanded. # 1204 Express_Client_Not_Supported=ANS1204E This client is not supported by the IBM Spectrum Protect express server\n Express_Client_Not_Supported_EXPLANATION=This client is not supported by the IBM Spectrum Protect express server. This can occur if:
  1. the client is configured as an IBM Spectrum Protect express client using the CLIENTVIEW option
  2. the client is trying to connect to an IBM Spectrum Protect express server.
Express_Client_Not_Supported_SYSACT=Processing stops. Express_Client_Not_Supported_URESP=Log in using a supported IBM Spectrum Protect express client. # 1205 Express_Platform_Not_Supported=ANS1205E This is not a supported IBM Spectrum Protect express platform\n Express_Platform_Not_Supported_EXPLANATION=This is not a supported IBM Spectrum Protect express platform. Express_Platform_Not_Supported_SYSACT=Processing stops. Express_Platform_Not_Supported_URESP=Log in using a supported IBM Spectrum Protect express client. # 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=TOC backup of a raw device is not supported. But the raw device is backed up. Img_Raw_Ok_Toc_Notsupp_SYSACT=Raw device is backed up with no TOC object. Img_Raw_Ok_Toc_Notsupp_URESP=NONE. # 1207 Img_No_Tocbkup_Found=ANS1207E No TOC has been previously backed up for this file system. Img_No_Tocbkup_Found_EXPLANATION=The user is trying to query the TOC of a file system. TOC backup for that file system has not been previously done. Img_No_Tocbkup_Found_SYSACT=Query stopped. Img_No_Tocbkup_Found_URESP=Backup the file system again with -TOC option. # 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=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. Img_Snapshot_Too_Large_SYSACT=The operation ends. Img_Snapshot_Too_Large_URESP=Decrease the SNAPSHOTCACHESIZE value or make additional space available in the logical volume group. Then try the operation again. # 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=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. Img_Snapshot_Cache_Location_Conflict_SYSACT=The client does not execute the image snapshot backup operation. Img_Snapshot_Cache_Location_Conflict_URESP=Specify a different snapshot cache location using the SNAPSHOTCACHELOCATION option. # 1216 CLI_Abort_No_Auth=ANS1216E Not authorized to run IBM Spectrum Protect. See the administrator for your system.\n CLI_Abort_No_Auth_EXPLANATION=The system options file for the server that you are attempting to connect to contains a user entry, a group entry, or both a user and group entry. Your user ID, or group ID, was not found in any of the entries. You are currently not authorized to run IBM Spectrum Protect to this server. CLI_Abort_No_Auth_SYSACT=IBM Spectrum Protect initialization fails and the program ends. CLI_Abort_No_Auth_URESP=See the IBM Spectrum Protect administrator for your system, and ask to be added to the user or group list for this server. # 1217 CLI_Abort_No_Server=ANS1217E Server name not found in System Options File\n CLI_Abort_No_Server_EXPLANATION=The system options file does not contain the SERVERNAME option. CLI_Abort_No_Server_SYSACT=IBM Spectrum Protect initialization fails and the program ends. CLI_Abort_No_Server_URESP=See the IBM Spectrum Protect administrator for your system, and make sure that the system options file contains the server name. # 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=The TCPSERVERADDRESS for this server is not defined in the server name stanza in the system options file. CLI_Abort_No_Host_Addr_SYSACT=IBM Spectrum Protect initialization fails and the program ends. CLI_Abort_No_Host_Addr_URESP=See the IBM Spectrum Protect 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. # 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=A VIRTUALNODENAME option was entered with a name the same as either a NODENAME option or the system host name. CLI_Abort_Machine_Same_SYSACT=Initialization fails and the program ends. CLI_Abort_Machine_Same_URESP=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. # 1229 Img_Invalid_Incr=ANS1229E MODE=INCREMENTAL is not valid on {0}. Image backup not processed.\n Img_Invalid_Incr_EXPLANATION=Because the file space has been the subject of at least one progressive incremental backup, the MODE=INCREMENTAL option (incremental by image date) cannot be used with the backup image command. Img_Invalid_Incr_SYSACT=File system skipped. Img_Invalid_Incr_URESP=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. # 1230 CLI_Stale_File=ANS1230E Stale NFS File Handle\n CLI_Stale_File_EXPLANATION=An NFS file system becomes stale. CLI_Stale_File_SYSACT=File system skipped. CLI_Stale_File_URESP=Check the NFS mounted filesystem. # 1237 CLI_Serv_Prob_See_Error_Log=ANS1237E A problem has occurred on the IBM Spectrum Protect server. CLI_Serv_Prob_See_Error_Log_EXPLANATION=The client error log and the IBM Spectrum Protect server activity log might contain additional information about this error. CLI_Serv_Prob_See_Error_Log_SYSACT=Processing stops. CLI_Serv_Prob_See_Error_Log_URESP=Try the operation again. If the problem persists, examine the client error log and IBM Spectrum Protect 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 IBM Spectrum Protect administrator can help you configure the trace. # 1238 CLI_Int_Error_See_Error_Log=ANS1238S A policy management problem has occurred on the IBM Spectrum Protect server.\n CLI_Int_Error_See_Error_Log_EXPLANATION=The client error log and IBM Spectrum Protect server activity log may contain additional information about this error. CLI_Int_Error_See_Error_Log_SYSACT=Processing is stops. CLI_Int_Error_See_Error_Log_URESP=Try the operation again. If the problem persists, examine the client error log and IBM Spectrum Protect 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 IBM Spectrum Protect administrator can help you configure the trace. # 1252 Invalid_Server_Msg=ANS1252W The server that you are connected to does not support this function.\n Invalid_Server_Msg_EXPLANATION=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. Invalid_Server_Msg_SYSACT=The operation fails. Invalid_Server_Msg_URESP=Connect to a valid server before attempting this function. # 1256 CLI_Cannot_Make=ANS1256E Cannot make file/directory\n CLI_Cannot_Make_EXPLANATION=The directory path for files being restored or retrieved cannot be created. CLI_Cannot_Make_SYSACT=File skipped. CLI_Cannot_Make_URESP=Ensure that you have the proper authorization to create the directory for file being restored or retrieved. Make sure that you have write access. # 1258 Img_Snapshot_Failed=ANS1258E The image snapshot operation failed.\n Img_Snapshot_Failed_EXPLANATION=The process was not able to take a snapshot of the specified volume. Img_Snapshot_Failed_SYSACT=Processing stopped. Img_Snapshot_Failed_URESP=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. # 1260 CLI_SM_Already_Recalled=ANS1260E File is being recalled or has been recalled.\n CLI_SM_Already_Recalled_EXPLANATION=The file is being recalled by another process or has been recalled. CLI_SM_Already_Recalled_SYSACT=File skipped. CLI_SM_Already_Recalled_URESP=None # 1265 CLI_Getmnt_Failed=ANS1265E Encountered bad mount or filesystem, processing stopped.\n CLI_Getmnt_Failed_EXPLANATION=The getmnt system call returned an error indication. Error was encountered trying to determine what the mounted file systems are. CLI_Getmnt_Failed_SYSACT=Processing stopped. Cannot recover. CLI_Getmnt_Failed_URESP=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. # 1266 CLI_Mounts_Failed=ANS1266E Encountered bad mount or filesystem, processing stopped.\n CLI_Mounts_Failed_EXPLANATION=An error was encountered trying to determine what the mounted file systems are. CLI_Mounts_Failed_SYSACT=Processing stopped. Cannot recover. CLI_Mounts_Failed_URESP=Please, see your system administrator for more information. # 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=The management class for this file does not allow migration CLI_MC_SM_Tech_None_SYSACT=File is skipped. CLI_MC_SM_Tech_None_URESP=Either have the IBM Spectrum Protect 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. # 1268 CLI_SM_Already_Migrated=ANS1268E This file has been migrated.\n CLI_SM_Already_Migrated_EXPLANATION=The error can result from migrating a file with hard links. After a file with hard links is migrated, attempts to migrate the alias files yield an error. CLI_SM_Already_Migrated_SYSACT=The file is skipped. CLI_SM_Already_Migrated_URESP=If this error is not a result of a hard linked file migration, then this error might be due to the previous cancelled migration or recall operation. In this case, restart the dsmrecalld daemon and try the operation again. # 1270 CLI_Snapdiff_Invalid_License=ANS1270E Running this command requires a valid NetApp Snapshot Differential c-mode license file.\n CLI_Snapdiff_Invalid_License_EXPLANATION=A NetApp Snapshot Differential c-mode license file either does not exist or is not valid. CLI_Snapdiff_Invalid_License_SYSACT=Processing stops. CLI_Snapdiff_Invalid_License_URESP=Contact IBM support. # 1273 CLI_Hotfix_Not_Installed=ANS1273I Microsoft Windows hotfix '{0}' is not installed.\n # 1277 VMBACKUP_VDDK_FILE_NOT_FOUND=ANS1277E The VMware vStorage API reported that a file was not found for the virtual machine.\n VMBACKUP_VDDK_FILE_NOT_FOUND_EXPLANATION=A VMware vStorage API error occurred due to a file not found on the virtual machine. VMBACKUP_VDDK_FILE_NOT_FOUND_SYSACT=A VMware vStorage API error occurred, and the virtual machine backup failed. VMBACKUP_VDDK_FILE_NOT_FOUND_URESP=Check the VMware logs for possible causes of the error, and try the operation again. # 1287 Img_Volume_Lock_Failure=ANS1287E Volume could not be locked.\n Img_Volume_Lock_Failure_EXPLANATION=The system call to lock the volume failed. Img_Volume_Lock_Failure_SYSACT=Processing stopped. Img_Volume_Lock_Failure_URESP=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) instead. During restore of an image IBM Spectrum Protect must have exclusive use of the volume. # 1299 CLI_Unable_To_Generate_Encryption_Key=ANS1299E Unable to generate an encryption key for storing password\n CLI_Unable_To_Generate_Encryption_Key_EXPLANATION=You tried to start an operation that led to storing password on the IBM Spectrum Protect client side but the client was unable to generate an encryption key very likely due to a configured FIPS-enabled operating system environment. CLI_Unable_To_Generate_Encryption_Key_SYSACT=Processing stops. CLI_Unable_To_Generate_Encryption_Key_URESP=The IBM Spectrum Protect client doesn't support the Federal Information Processing Standard (FIPS) enabled operating system environmnet for locally stored passwords. See your system administrator for assistance in reconfiguring the FIPS-enabled operating system environment. For more details on FIPS support, see the following techdoc: http://www-01.ibm.com/support/docview.wss?uid=swg22007756 # 1327 Snapshot_Failed_With_Error=ANS1327W The snapshot operation for '{0}' failed with error code: {1}.\n Snapshot_Failed_With_Error_EXPLANATION=A snapshot could not be taken of the specified volume. Snapshot_Failed_With_Error_SYSACT=Snapshot processing stopped. Snapshot_Failed_With_Error_URESP=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. # 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=An error occurred that prevented the creation of the delta file. Possible reasons for this error include: DSM_DELTAFILE_GENERATES_ERROR_SYSACT=A full backup of the file is made, and a new version of the reference file is stored in the subfile cache. DSM_DELTAFILE_GENERATES_ERROR_URESP=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. # 1342 CLI_Client_Cache_Locked=ANS1342E Client cache is locked; unable to continue with operation. CLI_Client_Cache_Locked_EXPLANATION=The client cache is currently locked by another process. CLI_Client_Cache_Locked_SYSACT=Processing stopped. CLI_Client_Cache_Locked_URESP=Report the program error to your service representative. # 1344 CLI_Client_Back_Ground_Process=ANS1344E Job is running in the background. Cannot prompt for the Key. CLI_Client_Back_Ground_Process_EXPLANATION=When jobs are run in the background, the client cannot prompt for the key. CLI_Client_Back_Ground_Process_SYSACT=Processing stopped. CLI_Client_Back_Ground_Process_URESP=Run the Job in the foreground. # 1345 CLI_Restore_Abort_No_Match=ANS1345E No objects on the server match '{0}{1}{2}'\n CLI_Restore_Abort_No_Match_EXPLANATION=The specified file does not have a match on the server. CLI_Restore_Abort_No_Match_SYSACT=The file is skipped. CLI_Restore_Abort_No_Match_URESP=Back up the file and try the operation again. If the problem continues, see your system administrator to isolate the problem through use of the server console. # 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=IBM Spectrum Protect 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. Img_Snapshot_CacheLocation_Full_SYSACT=Processing stopped. Img_Snapshot_CacheLocation_Full_URESP=If the problem persists please increase the SNAPSHOTCACHESize and/or change the value of the SNAPSHOTCACHELocation. # 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=IBM Spectrum Protect 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. Img_Snapshot_CacheLocation_Percent_Exceeded_SYSACT=Processing stopped. Img_Snapshot_CacheLocation_Percent_Exceeded_URESP=If the problem persists please increase the SNAPSHOTCACHESize or, for Windows, change the value of the SNAPSHOTCACHELocation. # 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=IBM Spectrum Protect 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. Img_Snapshot_Too_Many_FS_Writes_SYSACT=Processing stopped. Img_Snapshot_Too_Many_FS_Writes_URESP=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. # 1349 LVSA_Snapshot_Driver_Error=ANS1349E An error occurred during Logical Volume Snapshot Agent snapshot processing.\n LVSA_Snapshot_Driver_Error_EXPLANATION=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. LVSA_Snapshot_Driver_Error_SYSACT=Processing stopped. LVSA_Snapshot_Driver_Error_URESP=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. # 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=Another IBM Spectrum Protect process is already performing a snapshot of this volume. LVSA_Driver_Busy_With_Same_Volume_SYSACT=The operation is stopped. LVSA_Driver_Busy_With_Same_Volume_URESP=Please wait until the other IBM Spectrum Protect process finishes with the volume and then retry the operation. # 1353 SESS_Reject_Id_Unknown=ANS1353E Session rejected: User ID is incorrect, does not have admin authority, or is not known by the server\n SESS_Reject_Id_Unknown_EXPLANATION=The user ID, which is either IBM Spectrum Protect node name or administrative user ID, is not known by the server. Possible reasons for this include: Your node name is not registered with the IBM Spectrum Protect server The node name is correct but does not have a corresponding administrative ID with the same name and client owner authority you are attempting to access a file that was migrated to a different node. SESS_Reject_Id_Unknown_SYSACT=Current operation has been cancelled. SESS_Reject_Id_Unknown_URESP=Do the following checks: Check that your IBM Spectrum Protect user ID is entered correctly. Check the administrative ID associated with your IBM Spectrum Protect node and verify that the IBM Spectrum Protect node name has a matching administrative ID with client owner authority for the node. If it does not, your IBM Spectrum Protect administrator needs to create it. Check that the server is using closed registration and that your node name is registered with the server. If attempting to access a migrated file, your node name must be the same node that migrated the file. # 1361 SESS_Reject_Id_Locked=ANS1361E Session Rejected: The specified node name is currently locked.\n SESS_Reject_Id_Locked_EXPLANATION=The node name you specified is currently locked on the server. SESS_Reject_Id_Locked_SYSACT=Session was not started. SESS_Reject_Id_Locked_URESP=Check with your system administrator to find out why your node name is locked. # 1366 SESS_Reject_Internal_Error=ANS1366E The session is rejected. The IBM Spectrum Protect server has an internal error.\n SESS_Reject_Internal_Error_EXPLANATION=The client cannot establish a connection to the IBM Spectrum Protect server because of an internal server error. SESS_Reject_Internal_Error_SYSACT=The session was not started. SESS_Reject_Internal_Error_URESP=Notify your IBM Spectrum Protect administrator of this error. # 1369 SESS_Reject_Session_Canceled=ANS1369E Session Rejected: The session was canceled by the server administrator.\n SESS_Reject_Session_Canceled_EXPLANATION=The server administrator canceled the current client session. SESS_Reject_Session_Canceled_SYSACT=Execution of the client connection request ends. SESS_Reject_Session_Canceled_URESP=See your system administrator. # 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=The user ID entered cannot access this IBM Spectrum Protect client. SESS_Reject_Id_Not_Authorized_SYSACT=Operation ends. SESS_Reject_Id_Not_Authorized_URESP=Grant authority to this user ID on the IBM Spectrum Protect server so that it can access this IBM Spectrum Protect client. # 1372 SESS_Reject_Invalid_Node_Type=ANS1372E An inconsistency was detected between the client node and\nthe node that is registered to the IBM Spectrum Protect server. SESS_Reject_Invalid_Node_Type_EXPLANATION=The user has probably coded the node option incorrectly. For instance, the node that is registered to the IBM Spectrum Protect server might be a type of NAS, but the node is actually a non-NAS client. SESS_Reject_Invalid_Node_Type_SYSACT=Operation ends. SESS_Reject_Invalid_Node_Type_URESP=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. # 1373 Snapshot_PreCmd_Failed=ANS1373W The PRESNAPSHOTCMD command for volume {0} completed with a non-zero return code.\n Snapshot_PreCmd_Failed_EXPLANATION=The command specified by the PRESNAPSHOTCMD option must complete successfully in order to perform the snapshot backup/archive operation. If the command completed with a return code of 0 (zero), it has completed successfully. If the command completed with any other return code, it has failed. If the command failed, then the backup is still performed, but without the benefit of the snapshot technology. Snapshot_PreCmd_Failed_SYSACT=The client executes the backup/archive operation, but without using a snapshot. Snapshot_PreCmd_Failed_URESP=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. # 1374 Snapshot_PostCmd_Failed=ANS1374W The POSTSNAPSHOTCMD command for volume {0} completed with a non-zero return code.\n Snapshot_PostCmd_Failed_EXPLANATION=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. Snapshot_PostCmd_Failed_SYSACT=The snapshot-based backup operation continues. Snapshot_PostCmd_Failed_URESP=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. # 1376 CLI_Digest_Validation_Error=ANS1376E Error processing '{0}{1}{2}'; end-to-end digest validation failed.\n CLI_Digest_Validation_Error_EXPLANATION=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. CLI_Digest_Validation_Error_SYSACT=Processing stops CLI_Digest_Validation_Error_URESP=Try the restore operation again. If the problem persists, contact IBM technical support for additional assistance. # 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=IBM Spectrum Protect client was unable to create a snapshot of the volume due to some reason. Instead of failing the operation, IBM Spectrum Protect client will perform a non-snapshot based backup. Snapshot_Failed_Continue_Vol_No_Snap_SYSACT=Snapshot processing stops. Snapshot_Failed_Continue_Vol_No_Snap_URESP=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. # 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=IBM Spectrum Protect 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: Snapshot_CacheLocation_Full_SYSACT=Processing stopped. Snapshot_CacheLocation_Full_URESP=If the problem persists, increase the SNAPSHOTCACHESize or change the value of the SNAPSHOTCACHELocation. # 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=IBM Spectrum Protect 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: Snapshot_CacheLocation_Percent_Exceeded_SYSACT=Processing stopped. Snapshot_CacheLocation_Percent_Exceeded_URESP=If the problem persists, increase the SNAPSHOTCACHESize or change the value of the SNAPSHOTCACHELocation. # 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=IBM Spectrum Protect 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. Snapshot_Too_Many_FS_Writes_SYSACT=Snapshot processing stops. Snapshot_Too_Many_FS_Writes_URESP=If the problem persists, modify the SNAPSHOTFSIDLEWait and SNAPSHOTFSIDLERetries options to better fit the normal disk write activity of the volume being backed up. # 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=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. Snapshot_Cache_Location_Conflict_SYSACT=The client does not execute the snapshot operation. Snapshot_Cache_Location_Conflict_URESP=Specify a different snapshot cache location, using the SNAPSHOTCACHELOCATION option. # 1382 SESS_Reject_Invalid_SessionInit=ANS1382E Server does not allow client-initiated connections for this node. SESS_Reject_Invalid_SessionInit_EXPLANATION=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. SESS_Reject_Invalid_SessionInit_SYSACT=The IBM Spectrum Protect operation ends. SESS_Reject_Invalid_SessionInit_URESP=Contact your systems administrator to enable client-initiated sessions for your node or update the SESSIONINITIATION option and run the client scheduler. # 1383 SESS_Reject_Wrong_Port=ANS1383E Wrong server port. SESS_Reject_Wrong_Port_EXPLANATION=You were trying to open a backup/archive client session on the server port set up for administrative sessions only. SESS_Reject_Wrong_Port_SYSACT=The IBM Spectrum Protect operation ends. SESS_Reject_Wrong_Port_URESP=Contact your systems administrator and/or use the correct values for TCP port and TCP Admin Port. # 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=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. CLI_Abort_Invalid_Pol_Bind_SYSACT=The current operation ends. CLI_Abort_Invalid_Pol_Bind_URESP=Make sure all objects are bound to a valid management class, or upgrade the client to the proper level. # 1385 CLI_Abort_Insert_Not_Allowed=ANS1385E This server does not support backup operations.\n CLI_Abort_Insert_Not_Allowed_EXPLANATION=This server only supports archive operations, backup is not allowed. CLI_Abort_Insert_Not_Allowed_SYSACT=The current operation ends. CLI_Abort_Insert_Not_Allowed_URESP=Use only archive operations with this server. # 1386 CLI_Abort_Delete_Not_Allowed=ANS1386E Deleting this object: "{0}{1}{2}" is not allowed.\n CLI_Abort_Delete_Not_Allowed_EXPLANATION=The object is either under a hold and cannot be deleted, or it is on a retention-protection enabled server and has not expired. CLI_Abort_Delete_Not_Allowed_SYSACT=The object is skipped and processing continues. CLI_Abort_Delete_Not_Allowed_URESP=Check the status of the object through a query to see if it is held, or when it expires. # 1387 CLI_Abort_Txn_Limit_Exceeded=ANS1387E The number of objects in this transaction exceed TXNGROUPMAX values.\n CLI_Abort_Txn_Limit_Exceeded_EXPLANATION=There are too many objects in this transaction. CLI_Abort_Txn_Limit_Exceeded_SYSACT=The current operation ends. CLI_Abort_Txn_Limit_Exceeded_URESP=Try the operation again with fewer objects in the transaction, or increase the TXNGROUPMAX value on the server. # 1388 CLI_Abort_Object_Aready_Held=ANS1388E {0}{1}{2} is already under hold.\n CLI_Abort_Object_Aready_Held_EXPLANATION=The specified object CLI_Abort_Object_Aready_Held_SYSACT=This object is skipped and processing continues. CLI_Abort_Object_Aready_Held_URESP=Issue a query to see the status of the objects, and try the operation again, without the object that is already held. # 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=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. CLI_Invalid_Destination_Filespace_SYSACT=Objects which are part of this filespace are not processed. CLI_Invalid_Destination_Filespace_URESP=Try the command again, and specify a different destination for the object that was not processed. # 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=IBM Spectrum Protect 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. Snapshot_Unable_Create_CacheFiles_SYSACT=The client does not execute the snapshot operation. Snapshot_Unable_Create_CacheFiles_URESP=Change the value of the SNAPSHOTCACHELocation, or clean the disk to which the SNAPSHOTCACHELocation points. # 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=IBM Spectrum Protect 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. OFS_LVSA_Driver_Busy_With_Same_Volume_SYSACT=Snapshot processing stops. OFS_LVSA_Driver_Busy_With_Same_Volume_URESP=Wait until the other IBM Spectrum Protect process finishes with the volume and then try the operation again. # 1400 OFS_Snapshot_Cache_Location_Invalid=ANS1400W The snapshot cache location is not valid.\n OFS_Snapshot_Cache_Location_Invalid_EXPLANATION=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. OFS_Snapshot_Cache_Location_Invalid_SYSACT=Snapshot processing stops. OFS_Snapshot_Cache_Location_Invalid_URESP=Specify a different snapshot cache location using the SNAPSHOTCACHELOCATION option. # 1401 OFS_Snapshot_Virtual_Vol_Inaccessible=ANS1401W The snapshot virtual volume is not accessible.\n OFS_Snapshot_Virtual_Vol_Inaccessible_EXPLANATION=The logical volume snapshot agent (LVSA) cannot access the virtual volume during OFS-enabled backup/archive operation because IBM Spectrum Protect was probably started via terminal services. The operation continues without snapshot support. OFS_Snapshot_Virtual_Vol_Inaccessible_SYSACT=Snapshot processing stops. OFS_Snapshot_Virtual_Vol_Inaccessible_URESP=Do not use terminal services for the snapshot. Try the operation again on the local machine. # 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=IBM Spectrum Protect 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. OFS_Snapshot_Notsupported_On_Vol_SYSACT=The client does not execute the snapshot operation. OFS_Snapshot_Notsupported_On_Vol_URESP=To take advantage of the open file support, you may try the operation again on the local machine. # 1403 SESS_DLL_LoadFailure=ANS1403E Error loading a required {0} DLL\n SESS_DLL_LoadFailure_EXPLANATION=An error occurred while loading a dynamic link library. The DLL load failed. SESS_DLL_LoadFailure_SYSACT=Processing stopped. SESS_DLL_LoadFailure_URESP=Verify that your system software is up to date and that all DLLs required by the IBM Spectrum Protect client are present. # 1404 SESS_DLL_Function_LoadFailure=ANS1404E Error loading one or more functions from a required {0} DLL\n SESS_DLL_Function_LoadFailure_EXPLANATION=An error occurred while loading a function from a dynamic link library. The DLL load failed. SESS_DLL_Function_LoadFailure_SYSACT=Processing stopped. SESS_DLL_Function_LoadFailure_URESP=Verify that your system software is up to date. # 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=IBM Spectrum Protect 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. CLI_OFS_Reboot_Required_Before_Continuing_SYSACT=The client does not execute the snapshot operation. CLI_OFS_Reboot_Required_Before_Continuing_URESP=Restart the machine and then try the operation again. # 1409 VMBACKUP_INCLUDE_RESETCBT=ANS1409I A full backup for the {0} virtual machine will be performed because an include.resetcbt option was specified for the virtual machine.\n # 1410 CLI_BAD_NETPATH=ANS1410E Unable to access the network path.\n CLI_BAD_NETPATH_EXPLANATION=The network path cannot be accessed due to a possible network problem. CLI_BAD_NETPATH_SYSACT=The client terminates. CLI_BAD_NETPATH_URESP=Ensure that the network is up and the path can be accessed using a system command, and retry the operation. # 1411 CLI_SESS_DROP=ANS1411E A communication session was dropped.\n CLI_SESS_DROP_EXPLANATION=A communication session was dropped due to a possible network problem. CLI_SESS_DROP_SYSACT=The client terminates. CLI_SESS_DROP_URESP=Ensure that the network is up and retry the operation. # 1412 CLI_BAD_EADATA=ANS1412E Directory or file has bad EA data or inconsistent data.\n CLI_BAD_EADATA_EXPLANATION=Directory or file has bad EA data or inconsistent data. CLI_BAD_EADATA_SYSACT=The client terminates. CLI_BAD_EADATA_URESP=Check failing directory or file for bad EA data. Copy the directory to a new location and retry the operation. # 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}']. # 1418 MSG_AUTH_PASSWORD_EXPIRED=ANS1418E Authentication error. The Admin and/or Node password for {0} has expired.\n MSG_AUTH_PASSWORD_EXPIRED_EXPLANATION=Session authentication failed with the server because either the admin or node password for the node has expired. MSG_AUTH_PASSWORD_EXPIRED_SYSACT=Processing of the current operation is stopped. MSG_AUTH_PASSWORD_EXPIRED_URESP=Update your admin and/or node password for the node identified. # 1448 CLI_Invalid_Command_For_Server=ANS1448E The {0} command is not supported by the current server.\n CLI_Invalid_Command_For_Server_EXPLANATION=The server to which the client is connected does not support the command.
  1. If the command is "set event," the server does not support event-based policy. This command requires that the server supports event-based policy. That support is available only at IBM Spectrum Protect Server levels 5.2.2 and above.
  2. If the message displays any other command, the server is configured to support archive retention protection and cannot process operations that are not associated with that facility.
CLI_Invalid_Command_For_Server_SYSACT=The command is skipped and other processing continues. CLI_Invalid_Command_For_Server_URESP=Log in to an appropriate server and run the command again. # 1451 MoreInfo_Msg=More Information # 1452 LessInfo_Msg=Less Information # 1455 VMNAME_OPTION_VALUE_INVALID_FOR_RESTORE=ANS1455E The value of the -vmname option '{0}' would result in the restoration of multiple virtual machines with the same name. Use the keywords '*',