Messages


Chapter 6. Application Program Interface (0200-0479)



ANS0200I Successfully done.

Explanation: The operation successfully completed.
System Action: None.
User Response: None.



ANS0201E Invalid parameter was found.

Explanation: The system encountered an internal program error due to an invalid parameter.
System Action: The system returns to the calling procedure.
User Response: Ask your service representative to check the error log.



ANS0202E Not authorized to restore the other node's data.

Explanation: The client is not authorized to restore the other node's data.
System Action: The system returns to the calling procedure.
User Response: Get authorization from the other node.



ANS0203E The objName field has no leading directory separator.

Explanation: The objName field does not have a leading directory separator.
System Action: The system returns to the calling procedure.
User Response: Correct the value for the objName.



ANS0204E Wildcards are not allowed in the objName directory path.

Explanation: Wildcards are not allowed in the objName directory path.
System Action: The system returns to the calling procedure.
User Response: Correct the value for the objName.



ANS0205E Unable to open error log file.

Explanation: The system is unable to open the error log file.
System Action: The system returns to the calling procedure.
User Response: Verify the DSMI_LOG value and access permission. On the AS/400 platform, verify the value specified for ERRORLOGNAME in the API options file.



ANS0206E The log file cannot be written to.

Explanation: There was an error writing to the log file.
System Action: The system returns to the calling procedure.
User Response: Verify the DSMI_LOG value and access permission. on the AS/400 platform, verify the value specified for ERRORLOGNAME in the API options file.



ANS0207E The log file name was not specified.

Explanation: The system is unable to open the error log file.
System Action: The system returns to the calling procedure.
User Response: Verify the DSMI_LOG value and access permission. On the AS/400 platform, verify the value specified for ERRORLOGNAME in the API options file.



ANS0208E The TCP/IP WINSOCK.DLL file cannot be found.

Explanation: The TCP/IP WINSOCK.DLL file cannot be found.
System Action: Processing stopped.
User Response: Verify your TCP/IP installation.



ANS0209E An error occurred while loading a library.

Explanation: An error occurred while loading a library. The TCP/IP DLL load failed.
System Action: Processing stopped.
User Response: Verify your TCP/IP installation.



ANS0210E The TCP/IP load function failed.

Explanation: An error occurred while locating a function. The TCP/IP load function failed.
System Action: Processing stopped.
User Response: Verify your TCP/IP installation.



ANS0211E The object name pointer is NULL.

Explanation: There is no value provided for the object name pointer.
System Action: The system returns to the calling procedure.
User Response: Provide an address for the dsmObjName structure.



ANS0212E The data block pointer is NULL.

Explanation: There is no value provided for the data block pointer.
System Action: The system returns to the calling procedure.
User Response: Provide an address for the DataBlk structure.



ANS0213E The object attribute pointer is NULL.

Explanation: There is no value provided for the object attribute pointer.
System Action: The system returns to the calling procedure.
User Response: Provide an address for the ObjAttr structure.



ANS0214E There is no server session information.

Explanation: The server did not respond with the session information.
System Action: The system returns to the calling procedure.
User Response: Verify the server status.



ANS0215E There is no server policy information.

Explanation: The server did not respond with the policy information.
System Action: The system returns to the calling procedure.
User Response: Verify the server policy definitions.



ANS0216E The dataBlk bufferLen value is zero.

Explanation: The value for the dataBlk bufferLen is zero.
System Action: The system returns to the calling procedure.
User Response: Provide a non-zero value for the bufferLen.



ANS0217E The dataBlk bufferPtr is NULL.

Explanation: There is no value provided for the dataBlk bufferPtr.
System Action: The system returns to the calling procedure.
User Response: Provide an address for the bufferPtr.



ANS0218E The objType is invalid.

Explanation: The value for the objType is invalid.
System Action: The system returns to the calling procedure.
User Response: The value for dsmObjName.objType must be:

DSM_OBJ_FILE or DSM_OBJ_DIRECTORY for Backup, or

DSM_OBJ_FILE for Archive.



ANS0219E The dsmEndTxn vote is invalid.

Explanation: The dsmEndTxn vote is invalid.
System Action: The system returns to the calling procedure.
User Response: The vote must be DSM_VOTE_COMMIT or DSM_VOTE_ABORT.



ANS0220E An invalid option was found during option parsing.

Explanation: An invalid option was found.
System Action: The system returns to the calling procedure.
User Response: Verify the options in dsm.opt, dsm.sys, and the options string. Check the error log for more details about the error. on the AS/400 platform, verify the options in *LIB/QOPTTSM(APIOPT).



ANS0221E There was an error in the TSM API internals.

Explanation: The system encountered an error in the API internals.
System Action: The system returns to the calling procedure.
User Response: Shut down the process and retry the operation. Verify that any previous dsmInit calls were cleaned up and terminated by a dsmTerminate call. If the problem continues, contact your system administrator or service representative.



ANS0222E The repository type is invalid.

Explanation: The repository type is invalid.
System Action: The system returns to the calling procedure.
User Response: For dsmDeleteFS the repository must be one of the following:



ANS0223E Filespace name should start with the directory delimiter.

Explanation: The filespace name is invalid.
System Action: The system returns to the calling procedure.
User Response: Filespace name should start with the directory delimiter.



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

Explanation: The object name is invalid because of an empty string or there is no leading delimiter.
System Action: The system returns to the calling procedure.
User Response: Verify the format of the dsmObjName full path.



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

Explanation: The low level qualifier for the object name is invalid.
System Action: The system returns to the calling procedure.
User Response: Start the low level qualifier of the object name with the directory delimiter.



ANS0226E The object owner is invalid.

Explanation: The object owner must be either the root user, or the object owner must be the same as the session owner.
System Action: The system returns to the calling procedure.
User Response: Verify the session owner and object owner.



ANS0227E The dsmBindMC sendType is invalid.

Explanation: The dsmBindMC sendType is invalid.
System Action: The system returns to the calling procedure.
User Response: The sendType must be one of the following:

stBackup

stArchive

stBackupMountWait

stArchiveMountWait



ANS0228E The dsmSendObj sendType is invalid.

Explanation: The dsmSendObj sendType is invalid.
System Action: The system returns to the calling procedure.
User Response: The sendType must be one of the following:

stBackup

stArchive

stBackupMountWait

stArchiveMountWait



ANS0229E The dsmDeleteObj delType is invalid.

Explanation: The dsmDeleteObj delType is invalid.
System Action: The system returns to the calling procedure.
User Response: The delType must be dtBackup or dtArchive.



ANS0230E The query Backup objState is invalid.

Explanation: The query Backup objState is invalid.
System Action: The system returns to the calling procedure.
User Response: The qryBackupData.objState must be one of the following:

DSM_ACTIVE

DSM_INACTIVE

DSM_ANY_MATCH



ANS0231E The management class name was not found.

Explanation: A query or send operation is unable to find the management class name.
System Action: The system returns to the calling procedure.
User Response: Verify the management class name.



ANS0232E The drive letter is not an alphabetic character.

Explanation: The drive letter is not an alphabetic character. This return code is valid on Microsoft Windows or OS/2.
System Action: The system returns to the calling procedure.
User Response: Verify that the drive designation is an alphabetic character. The referenced field is dsmDosFSAttrib.driveLetter.



ANS0233E The Register Filespace name is NULL.

Explanation: There is no value provided for the Register Filespace name.
System Action: The system returns to the calling procedure.
User Response: Provide a filespace name on dsmRegisterFS.



ANS0234E The new password value is NULL or blank.

Explanation: There is no value provided for new password.
System Action: The system returns to the calling procedure.
User Response: Provide a new password on dsmChangePW.



ANS0235E The old password value is NULL or blank.

Explanation: There is no value provided for old password.
System Action: The system returns to the calling procedure.
User Response: Provide an old password on dsmChangePW.



ANS0236E On dsmInit, the owner is not allowed when PASSWORDACCESS=generate.

Explanation: PASSWORDACCESS=generate establishes a session with the current login user as the owner.
System Action: The system returns to the calling procedure.
User Response: When using PASSWORDACCESS=generate, set clientOwnerNameP to NULL.



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

Explanation: PASSWORDACCESS=generate establishes a session with the current hostname as the node.
System Action: The system returns to the calling procedure.
User Response: When using PASSWORDACCESS=generate, set clientNodeP to NULL.



ANS0238E The sequence of calls is invalid.

Explanation: The sequence of calls is invalid.
System Action: The system returns to the calling procedure.
User Response: Verify the transaction call sequence.



ANS0239E On dsmSendObj, wildcards are not allowed for the objName.

Explanation: On dsmSendObj, wildcards are not allowed for the objName.
System Action: The system returns to the calling procedure.
User Response: Provide a fs, hl, and ll on the dsmObjName.



ANS0240E The filespace to delete/set access cannot be found.

Explanation: The filespace to delete cannot be found.
System Action: The system returns to the calling procedure.
User Response: Verify the filespace name.



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

Explanation: On dsmSendObj, dsmDeleteObj, or dsmUpdateFS, the filespace is not registered.
System Action: The system returns to the calling procedure.
User Response: Verify the filespace name.



ANS0242W On dsmRegisterFS the filespace is already registered.

Explanation: On dsmRegisterFS the filespace is already registered.
System Action: The system returns to the calling procedure.
User Response: Verify the filespace name.



ANS0243E On dsmBeginGetData the objID is NULL.

Explanation: On dsmBeginGetData, the objID is NULL.
System Action: The system returns to the calling procedure.
User Response: Verify the following:

The dsmGetList is not NULL.

Each objID is not NULL.

The dsmGetList numObjId is not zero.



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

Explanation: On dsmInit the caller's API version has a higher value than the TSM library version.
System Action: The system returns to the calling procedure.
User Response: Install the latest TSM API library and trusted agent module.



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

Explanation: The caller's structure version is different than the TSM library version.
System Action: The system returns to the calling procedure.
User Response: Ensure that the stVersion field is set with the value in the header file. Recompile the application with the latest header files.



ANS0246E Issue dsmEndTxn and then begin a new transaction session.

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

The destination changed.

The byte limit is exceeded

The maximum number of objects is exceeded.


System Action: The system returns to the calling procedure.
User Response: Issue dsmEndTxn and start a new transaction session.



ANS0247E The backup or archive object is excluded from processing.

Explanation: The backup or archive object is excluded from processing.
System Action: The system returns to the calling procedure.
User Response: Verify the objName and Exclude lists.



ANS0248E The backup object does not have a copy group.

Explanation: The backup object does not have a copy group.
System Action: The system returns to the calling procedure.
User Response: Verify server policy definitions.



ANS0249E The archive object does not have a copy group.

Explanation: The archive object does not have a copy group.
System Action: The system returns to the calling procedure.
User Response: Verify server policy definitions.



ANS0250E Memory used by the TSM API has been corrupted.

Explanation: Memory used by the TSM API has been corrupted.
System Action: The system returns to the calling procedure.
User Response: Retry the operation. If the problem continues, contact your system administrator or service representative.



ANS0251E The sendObj Archive description is too long.

Explanation: The sendObj Archive description is too long.
System Action: The system returns to the calling procedure.
User Response: The sndArchiveData.descr string must be less than or equal to DSM_MAX_DESCR_LENGTH.



ANS0252E The sendObj ObjAttr.objInfo is too long.

Explanation: The sendObj ObjAttr.objInfo is too long.
System Action: The system returns to the calling procedure.
User Response: The objInfo field must be less than or equal to DSM_MAX_OBJINFO_LENGTH.



ANS0253E The sendObj dsmObjName.hl is too long.

Explanation: The sendObj dsmObjName.hl is too long.
System Action: The system returns to the calling procedure.
User Response: The hl field must be less than or equal to DSM_MAX_HL_LENGTH.



ANS0254E The dsmChangePW password is too long.

Explanation: The dsmChangePW password is too long.
System Action: The system returns to the calling procedure.
User Response: The password field must be less than or equal to DSM_MAX_VERIFIER_LENGTH.



ANS0255E The sendObj dsmObjName.fs is too long.

Explanation: The sendObj dsmObjName.fs is too long.
System Action: The system returns to the calling procedure.
User Response: The fs field must be less than or equal to DSM_MAX_FS_LENGTH.



ANS0256E The sendObj dsmObjName.ll is too long.

Explanation: The sendObj dsmObjName.ll is too long.
System Action: The system returns to the calling procedure.
User Response: The ll field must be less than or equal to DSM_MAX_LL_LENGTH.



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

Explanation: On RegisterFS or UpdateFS the fsAttr's fsInfo is too long.
System Action: The system returns to the calling procedure.
User Response: The fsInfo field must be less than or equal to DSM_MAX_FSINFO_LENGTH.



ANS0258I On dsmGetNextQObj or dsmGetData there is more available data.

Explanation: On dsmGetNextQObj or dsmGetData there is more available data.
System Action: The system returns to the calling procedure.
User Response: Call the function again.



ANS0259E The dataBlk buffer is too small for the query response.

Explanation: The dataBlk buffer is too small for the query response.
System Action: The system returns to the calling procedure.
User Response: On dsmGetNextQObj ensure that the dataBlk buffer is at least as big as the query response structure.



ANS0260E An invalid option keyword was found during option parsing.

Explanation: An invalid option keyword was found in the dsmInit configuration file, the option string, dsm.sys, or dsm.opt.
System Action: The system returns to the calling procedure.
User Response: Correct the spelling of the option keywords. Verify that the dsmInit configuration file only has a subset of the dsm.sys options. Check the error log for more details about the error.



ANS0261E The configuration file specified on dsmInit cannot be opened.

Explanation: The configuration file specified on dsmInit cannot be opened.
System Action: The system returns to the calling procedure.
User Response: Verify the file name.



ANS0262E The Include/Exclude definition file was not found.

Explanation: The Include/Exclude definition file was not found.
System Action: The system returns to the calling procedure.
User Response: Verify the file name on the Inclexcl option.



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

Explanation: Either the dsm.sys file was not found, or the Inclexcl file specified in dsm.sys was not found.
System Action: The system returns to the calling procedure.
User Response: The dsm.sys file must be in the directory referenced by the environment variable DSMI_DIR. Verify the file name on the Inclexcl option in the dsm.sys file.



ANS0264E Only a UNIX root user can execute dsmChangePW or dsmDeleteFS.

Explanation: Only a UNIX root user can execute dsmChangePW or dsmDeleteFS.
System Action: The system returns to the calling procedure.
User Response: Run this program as a root user.



ANS0265E You must issue dsmBindMC before dsmSendObj.

Explanation: You must issue dsmBindMC before dsmSendObj.
System Action: The system returns to the calling procedure.
User Response: Modify your program.



ANS0266I The dsmEndTxn vote is ABORT, so check the reason field.

Explanation: After a dsmEndTxn call, the transaction is aborted by either the server or client with a DSM_VOTE_ABORT and the reason is returned.
System Action: The system returns to the calling procedure.
User Response: Check the reason field for the code which explains why the transaction has been aborted.



ANS0268E Server problem: Destination not defined.

Explanation: Server problem: Destination not defined.
System Action: Processing stopped.
User Response: Have your service representative check the error log.



ANS0269S The structured file data type is unknown.

Explanation: An unknown and unexpected error code occurred within the client program. The structured file data type is unknown. This is a programming failure and the client program ends.
System Action: Processing stopped.
User Response: Retry the operation. If the problem continues, contact your system administrator.



ANS0270S The data buffer overflowed.

Explanation: The data buffer overflowed. This is a programming failure and the client program ends.
System Action: Processing stopped.
User Response: Retry the operation. If the problem continues, contact your system administrator.



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

Explanation: No more files can be restored or retrieved since the destination directory is full.
System Action: Processing stopped.
User Response: Free up disk space, or restore or retrieve the file to another disk.



ANS0272I The operation is finished.

Explanation: The operation is finished.
System Action: The system returns to the calling procedure.
User Response: Proceed with next function call.



ANS0273E The trusted agent execution/owner permissions are invalid.

Explanation: The trusted agent execution/owner permissions are invalid.
System Action: Processing stopped.
User Response: Have your system administrator check the installation instructions for the client to ensure that the trusted agent permissions are set correctly.



ANS0274S Process killed.

Explanation: Processing stopped. This is a programming failure and the client program ends.
System Action: Processing stopped.
User Response: Retry the operation. If the problem continues, contact your system administrator.



ANS0275S Trusted agent would block the operation.

Explanation: The trusted agent blocks the operation. This is a programming failure and the client program ends.
System Action: Processing stopped.
User Response: Retry the operation. If the problem continues, contact your system administrator.



ANS0276S The area for the include/exclude pattern is too small.

Explanation: The area for the include/exclude pattern is too small. This is a programming failure and the client program ends.
System Action: Processing stopped.
User Response: Retry the operation. If the problem continues, contact your system administrator.



ANS0277S There is no closing bracket in the pattern.

Explanation: There is no closing bracket in the pattern. This is a programming failure and the client program ends.
System Action: Processing stopped.
User Response: Retry the operation. If the problem continues, contact your system administrator.



ANS0278S The transaction will be aborted.

Explanation: The server encountered an error and will abort the transaction.
System Action: The transaction will be aborted. The reason code is passed on the dsmEndTxn call.
User Response: Issue the dsmEndTxn with a vote of DSM_VOTE_COMMIT and examine the reason code.



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

Explanation: A file was skipped during a restore operation because the file is off line and the application has chosen not to wait for a tape mount.
System Action: File skipped.
User Response: Verify the application sets the mountWait value correctly on dsmBeginGetData.



ANS0280E Unable to find Trusted Agent module.

Explanation: TSM was unable to find the TSM Trusted Agent module in the specified directory. For V1R1 the name is dsmapita, for V1R2 the name is dsmtca, for V2R1 the name is dsmapitca.
System Action: TSM ends.
User Response: Make sure the Trusted Agent module is in the directory specified by DSMI_DIR.



ANS0281E Access denied for dsmapitca.

Explanation: An attempt to access a system function has been denied.
System Action: Processing stopped.
User Response: Contact your system administrator.



ANS0282E Password file is not available.

Explanation: The file containing the stored password for the specified server-name is unavailable.
System Action: TSM ends.
User Response: The root user must set and store a new password.



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

Explanation: The high level qualifier for the object name is invalid.
System Action: The system returns to the calling procedure.
User Response: High level qualifier of the object name should start with the directory delimiter.



ANS0284E The number of objects on dsmBeginGetData exceeds DSM_MAX_GET_OBJ | DSM_MAX_PARTIAL_GET_OBJ.

Explanation: The number of objects (numObjId) specified on the dsmBeginGetData call exceeds DSM_MAX_GET_OBJ | DSM_MAX_PARTIAL_GET_OBJ.
System Action: The system returns to the calling procedure.
User Response: Check the number of objects before calling dsmBeginGetData. If it is greater than DSM_MAX_GET_OBJ | DSM_MAX_PARTIAL_GET_OBJ, then issue multiple Get call sequences.



ANS0285E The update action is invalid.

Explanation: The dsmUpdateFS or dsmUpdateObj action is invalid.
System Action: The system returns to the calling procedure.
User Response: Correct the action value. Valid values are defined in dsmapitd.h and documented in our Using the API book.



ANS0286E The key file is missing.

Explanation: The key file for Tivoli Data Protection application client for Oracle cannot be found.
System Action: The system returns to the calling procedure.
User Response: Ensure that you have ordered the Tivoli Data Protection application client which contains TDP for Oracle, and install the key file.



ANS0287E The key file content is invalid.

Explanation: The key file content for Tivoli Data Protection application client for Oracle is invalid.
System Action: The system returns to the calling procedure.
User Response: Ensure that you have ordered the Tivoli Data Protection application client which contains the TDP for Oracle, and install the key file.



ANS0296E The PC/3270 EHLLAPI DLL pcshll.dll cannot be found in the user's path.

Explanation: The PC/3270 EHLLAPI DLL pcshll.dll cannot be found in the user's path.
System Action: Communications link is not established.
User Response: Contact your system administrator. Make sure that the PS/3270 EHLLAPI DLLs are in a directory that is included in the user's path.



ANS0301E The TSM DLL dsm3270.dll cannot be found in the user's path.

Explanation: The TSM DLL dsm3270.dll cannot be found in the user's path.
System Action: Communications link is not established.
User Response: Make sure that the TSM DLL dsm3270.dll is in a directory that is included in the user's path.



ANS0302I Successfully done.

Explanation: The operation successfully completed.
System Action: None.
User Response: None.



ANS0315E Unable to open message text file.

Explanation: The system is unable to open the message txt file (dscameng.txt or dsmclientV3.cat for AIX). On the AS/400 platform this file is QANSAPI/QAANSAMENG(TXT).
System Action: The system returns to the calling procedure.
User Response: Verify that the dscameng.txt file is in the directory pointed to by DSMI_DIR. For AIX, verify that the dsmclientV3.cat file has a symbolic link to /usr/lib/nls/msg/<locale>/dsmclientV3.cat .



ANS0316E Unable to use message text file.

Explanation: The system is unable to use the message text file (dscameng.txt or dsmclientV3.cat for AIX) because of an invalid header. On the AS/400 platform this file is QANSAPI/QAANSAMENG(TXT).
System Action: The system returns to the calling procedure.
User Response: Install the message text file again.



ANS0317E Unable to use message text file.

Explanation: The system is unable to use the message txt file (dscameng.txt or dsmclientV3.cat for AIX) because of an invalid control record. On the AS/400 platform this file is QANSAPI/QAANSAMENG(TXT).
System Action: The system returns to the calling procedure.
User Response: Install the message text file again.



ANS0318E Invalid value for DATEFORMAT specified.

Explanation: An invalid value is specified for DATEFORMAT.
System Action: The system returns to the calling procedure.
User Response: Specify a valid value.



ANS0319E Invalid value for TIMEFORMAT specified.

Explanation: An invalid value is specified for TIMEFORMAT.
System Action: The system returns to the calling procedure.
User Response: Specify a valid value.



ANS0320E Invalid value for NUMBERFORMAT specified.

Explanation: An invalid value is specified for NUMBERFORMAT.
System Action: The system returns to the calling procedure.
User Response: Specify a valid value.



ANS0321E msg parameter for dsmRCMsg is a NULL pointer.

Explanation: The message parameter for dsmRCMsg is a NULL pointer.
System Action: The system returns to the calling procedure.
User Response: Allocate enough space for the message parameter.



ANS0322E no text available for this return code.

Explanation: The dsmRC parameter for dsmRCMsg is an unsupported return code.
System Action: The system returns to the calling procedure.
User Response: Specify a valid value.



ANS0323E partialObjOffset value for partial object retrieve is invalid.

Explanation: The partialObjOffset value for partial object retrieve is invalid.
System Action: The system returns to the calling procedure.
User Response: Specify a valid value.



ANS0324E partialObjLength value for partial object retrieve is invalid.

Explanation: partialObjLength value for partial object retrieve is invalid.
System Action: The system returns to the calling procedure.
User Response: Specify a valid value.



ANS0325E Partial Object Retrieve is not supported on this server.

Explanation: The TSM server specified by the user does not support partial object retrieve.
System Action: The system returns to the calling procedure.
User Response: Specify a TSM server which supports the partial object retrieve function.



ANS0326E Node has exceeded max tape mounts allowed.

Explanation: All the tape mount points for this node are in use.
System Action: The system returns to the calling procedure.
User Response: Increase the number of allowed tape mounts for this node on the server.



ANS0327E A duplicate object was found, operation cannot complete.

Explanation: A duplicate object was found, operation cannot complete.
System Action: The requested operation failed.
User Response: Try the operation with a different file specification.



ANS0328E The specified objects failed the merge test.

Explanation: The specified objects failed the merge test, operation cannot complete.
System Action: The requested operation failed.
User Response: See documentation for the merge test parameters.



ANS0330E The dsmSetAccess access Type is invalid.

Explanation: The dsmSetAccess accessType is invalid.
System Action: The system returns to the calling procedure.
User Response: The accessType must be one of the following:

atBackup

atArchive



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

Explanation: You tried to set access to files when no files for the specified filename, drive or file system were previously backed up.
System Action: Processing stopped.
User Response: Ensure that the correct drive or file system was specified and that files are backed up for you to set access.



ANS0332E No files have been previously archived for this filename/filespace.

Explanation: You tried to set access to files when no files for the specified filename, drive or file system were previously archived.
System Action: Processing stopped.
User Response: Ensure that the correct drive or file system was specified and that files are archived for you to set access.



ANS0400E License file could not be opened.

Explanation: The license file was not found, or could not be opened because of permissions or the file is corrupted.
System Action: The system returns to the calling procedure.
User Response: Check permissions on file. See if the license file is in the correct place.



ANS0401E Read failure on the license file.

Explanation: The license file was not found, or could not be opened because of permissions, or the file is corrupted.
System Action: The system returns to the calling procedure.
User Response: Check permissions on file. See if the license file is in the correct place.



ANS0402E Write failure on the license file.

Explanation: The license file was not found, or could not be opened because of permissions or the file is corrupted.
System Action: The system returns to the calling procedure.
User Response: Check permissions on file. See if license file is in the correct place.



ANS0403E Data in the license file is not in a valid format.

Explanation: The license file is not valid.
System Action: The system returns to the calling procedure.
User Response: User needs to obtain a new license.



ANS0404E The checksum in the license file does not match the licenseregistration string.

Explanation: The registration string is not valid.
System Action: The system returns to the calling procedure.
User Response: User needs to obtain a new license.



ANS0405E This is an expired try and buy license.

Explanation: The registration string is not valid.
System Action: The system returns to the calling procedure.
User Response: User needs to obtain a new license.


[ Top of Page | Previous Page | Next Page | Table of Contents ]