Using the Application Program Interface


Appendix D. API Return Codes With Explanations

This appendix describes the return codes. The return codes are listed in numeric order. For each return code, the following information is provided:

Many of the return codes describe errors that cause processing to stop. You can send a message to the end user that describes the problem and suggest a course of action. To identify different messages, use these return code values or develop your own numbering system.

-452 EDSM_RC_SHM_NOTAUTH

Explanation: The user issuing the command does not have authority to connect to the shared memory segment. When the shared memory segment is created by the server, it will be owned by the effective user identification number (uid) of the server process (dsmserv). Only processes running under this uid or root will be allowed to connect to the segment (and thus to the server).

System Action: The session is rejected, and processing stops.

User Response: Run the command under the uid of the processing by running dsmserv, if possible. Otherwise contact your system administrator for further help.

-451 EDSM_RC_SHM_FAILURE

Explanation: An error has occurred while reading or writing data through the Shared Memory communications protocol.

System Action: TSM cannot complete the requested operation.

User Response: Check the trace log for additional information and retry the operation. If the problem continues, see your system administrator for further help.

-450 EDSM_RC_SHM_TCPIP_FAILURE

Explanation: An attempt to connect to the local server by using the Shared Memory protocol has failed during initial TCP/IP communications. This error can occur if the server is not listening on the correct port, or if the server is down.

System Action: The session was rejected. Processing stopped.

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

-219 SDSM_RC_CPIC_MISSING_TP

Explanation: For CPIC, you must supply a TPname if a SYMbolicdestination is not given.

System Action: Processing stopped.

User Response: Retry the operation by using the TPname option or define the SYMbolicdestination option.

-218 SDSM_RC_CPIC_MISSING_LU

Explanation: For CPIC, you must supply a PARtnerluname if no SYMbolicdestination is given.

System Action: Processing stopped.

User Response: Retry the operation by using an LU name or a symbolic destination name.

-217 EDSM_RC_UNKNOWN_CPIC_PROBLEM

Explanation: An unexpected CPI Communication error occurs.

System Action: Processing stops.

User Response: Contact your service representative.

-216 SDSM_RC_CPIC_UNSUCCESSFUL

Explanation: CPIC session not immediately available. All the sessions for SNA communications are in use.

System Action: Processing stopped.

User Response: Stop and start SNA communications and retry the command.

-215 SDSM_RC_CPIC_PROGRAM_PARAM_CHECK

Explanation: A parameter to a CPIC call was in error.

System Action: Processing stopped.

User Response: A symbolic destination or transaction program name was given that was not valid. Check these values and retry the command.

-214 SDSM_RC_CPIC_PROGRAM_STATE_CHECK

Explanation: CPIC program state check.

System Action: Processing stopped.

User Response: This is a program error. See your service representative.

-213 SDSM_RC_CPIC_SVC_ERROR

Explanation: A CPIC SVC error occurred.

System Action: Processing stopped.

User Response: See your service representative.

-212 WDSM_RC_CPIC_DEALLOCATE_ERROR

Explanation: CPIC conversation deallocation error. TSM received an incorrect return code from the deallocate verb. This error does not affect the TSM program.

System Action: None.

User Response: None.

-211 SDSM_RC_CPIC_RESOURCE_ERROR

Explanation: CPIC resource error. The conversation ended prematurely.

System Action: Processing stopped.

User Response: Exit TSM and retry the TSM command. API applications should close the session with dsmTerminate.

-210 SDSM_RC_CPIC_PROGRAM_ERROR

Explanation: An unexpected CPIC program error occurred.

System Action: Processing stopped.

User Response: This is a program error. See your service representative.

-209 SDSM_RC_CPIC_PROD_SPECIFIC_ERR

Explanation: TSM detected a CPIC product-specific error that occurred when making a CPIC call.

System Action: Processing stopped.

User Response: Ensure that LU6.2 is working properly at your installation. See your system administrator.

-208 SDSM_RC_CPIC_PARAMETER_ERROR

Explanation: A parameter to a CPIC call was in error.

System Action: Processing stopped.

User Response: A symbolic destination or transaction program name was given that was not valid. Check these values and retry the command.

-207 SDSM_RC_CPIC_TP_ERROR

Explanation: CPIC transaction program not available. The server is not responding to the local program's request.

System Action: Processing stopped.

User Response: Ensure that the server is running and retry the command. Stop and start the local communications program.

-206 SDSM_RC_CPIC_TPN_NOT_RECOGNIZED

Explanation: A CPIC transaction program name was not recognized. TSM cannot find the name of the server.

System Action: Processing stopped.

User Response: Ensure that you have the correct TSM server name listed in your CPIC side information entry and that the server is running.

-205 SDSM_RC_CPIC_SYNC_LVL_NO_SUPPORT

Explanation: The conversation cannot continue because the CPIC synchronization level of either the local or remote system is not supported.

System Action: Processing stopped.

User Response: TSM defaults to no synchronization level. See your service representative.

-204 SDSM_RC_CPIC_SECURITY_NOT_VALID

Explanation: The conversation cannot be allocated because the CPIC security is not valid.

System Action: Processing stopped.

User Response: Change the security in the CPIC side information table.

-203 SDSM_RC_CPIC_PIP_NOT_SPECIFY_ERR

Explanation: An unexpected CPIC error occurred. The CPIC PIP is not specified correctly.

System Action: Processing stopped.

User Response: This is a program error. See your service representative.

-202 SDSM_RC_CPIC_TYPE_MISMATCH

Explanation: An unexpected CPIC error occurred. There is a CPIC conversation type mismatch between the client and the server.

System Action: Processing stopped.

User Response: This is a program error. See your service representative.

-201 SDSM_RC_CPIC_ALLOCATE_FAILURE

Explanation: TSM client cannot allocate a CPIC conversation to the server.

System Action: Processing stopped.

User Response: Ensure that the symbolic destination name matches a valid side information table entry in your local communications program.

-190 EDSM_RC_NP_ERROR

Explanation: An attempt to connect to the server by using Named Pipes communications failed. This might have occurred if an incorrect NAMEDPIPENAME was specified in the options files or if your system administrator canceled a backup operation.

System Action: Processing stopped.

User Response: Retry the operation, or wait until the server comes back up and retry the operation. Ensure that the value specified on the NAMEDPIPENAME option is the same as the one that is used by the server. If the problem continues, contact your system administrator for further help.

-161 EDSM_RC_NETB_REBOOT

Explanation: A DOS or Windows NETBIOS error has occurred which requires that the adapter be reset. This may be caused by a software installation or adapter configuration error.

System Action: Processing stopped.

User Response: Start the machine again. If the error recurs, check the TSM error log to find the NETBIOS return code. See your system administrator for help with your NETBIOS installation/configuration problem.

-160 EDSM_RC_NETB_NOTINST

Explanation: The product for NETBIOS is not installed.

System Action: Processing stopped.

User Response: Verify that the product for NETBIOS, such as the LAN Support Program, is installed. If the problem continues, see your system administrator for further help.

-159 EDSM_RC_NETB_TIMEOUT

Explanation: A timeout occurred when transmitting data with the NETBIOS protocol.

System Action: Processing stopped.

User Response: Make sure that the server is operational. You may need to increase the NETBIOSTIMEOUT value or use a value of 0 for no timeout. If the problem continues, see your system administrator for further help.

-158 EDSM_RC_NETB_NAME_ERR

Explanation: An attempt to add the client NETBIOS name failed, or an attempt to call the server NETBIOS name failed.

System Action: Processing stopped.

User Response: Verify that your NETBIOSNAME option value is unique. Verify that your NETBIOSSERVERNAME option value is correct. Verify that the server has NETBIOS support running. If the problem continues, see your system administrator for further help.

-155 EDSM_RC_NETB_LAN_ERR

Explanation: A LAN communications failure was detected while in session with server.

System Action: Communications link is not established.

User Response: See your system administrator.

-152 EDSM_RC_NETB_NO_DLL

Explanation: The OS/2 LAN file ACSNETB.DLL is not available to establish that a communications link, or the file is incorrect.

System Action: Communications link is not established.

User Response: See your system administrator.

-151 EDSM_RC_NETB_ERROR

Explanation: The client cannot access the NETBIOS server.

System Action: Session is not established.

User Response: Ensure that NETBIOS is loaded and that the NETBIOS server is active. See your system administrator on status of the LAN.

-124 EDSM_RC_3270COMM_MISSING_DLL

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.

-123 EDSM_RC_PC3270_MISSING_DLL

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.

-057 EDSM_RC_TCPIP_LOADFAILURE

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.

-056 EDSM_RC_TCPIP_DLL_LOADFAILURE

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.

-055 EDSM_RC_WINSOCK_MISSING

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

System Action: Processing stopped.

User Response: Verify your TCP/IP installation.

-054 EDSM_RC_NETWORK_UNREACHABLE

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

System Action: Processing stopped.

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

-053 EDSM_RC_BAD_HOST_NAME

Explanation: A TCP/IP host name or address that is not valid was specified.

System Action: Processing stopped.

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

-052 EDSM_RC_CONN_REFUSED

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

System Action: Processing stopped.

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

-051 EDSM_RC_CONN_TIMEDOUT

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

System Action: Processing stopped.

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

-050 EDSM_RC_TCPIP_FAILURE

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

System Action: The session was rejected. Processing stopped.

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

0000 IDSM_RC_SUCCESSFUL

Explanation: The operation successfully completed.

System Action: None.

User Response: None.

0000 IDSM_RC_OK

Explanation: The operation successfully completed.

System Action: None.

User Response: None.

0001 EDSM_RC_ABORT_SYSTEM_ERROR

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

System Action: Processing stopped.

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

0002 EDSM_RC_ABORT_NO_MATCH

Explanation: No objects on the server match the query operation being performed.

System Action: Processing stopped.

User Response: Ensure that the names are properly entered.

0003 EDSM_RC_ABORT_BY_CLIENT

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

System Action: Processing stopped.

User Response: Restart the session.

0004 WDSM_RC_ABORT_ACTIVE_NOT_FOUND

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

System Action: None.

User Response: None.

0005 EDSM_RC_ABORT_NO_DATA

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

System Action: TSM ended the current operation.

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

0006 EDSM_RC_ABORT_BAD_VERIFIER

Explanation: You entered an incorrect password (verifier).

System Action: Processing stopped.

User Response: Retry the session with the correct password.

0007 EDSM_RC_ABORT_NODE_IN_USE

Explanation: The node you are running on is in use by another operation on the server. This might be from another client or from some activity on the server.

System Action: Processing stopped.

User Response: Retry the operation, or see your system administrator to see what other operations are running for your node.

0008 EDSM_RC_ABORT_EXPDATE_TOO_LOW

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

System Action: TSM canceled the current operation.

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

0009 WDSM_RC_ABORT_DATA_OFFLINE

Explanation: For the restore or retrieve operation, one or more of the requested files must be recalled from offline storage media (generally tape). The wait time depends on your site's offline storage management policies.

System Action: TSM waits for offline storage media to become available, and then continues.

User Response: None.

0010 EDSM_RC_ABORT_EXCLUDED_BY_SIZE

Explanation: The object is too large. The configuration of the server does not have any data storage space that accepts the object.

System Action: The file skipped.

User Response: See your system administrator to determine the maximum file (object) size for which your site's server is configured.

0011 EDSM_RC_ABORT_NO_REPOSIT_SPACE

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

System Action: TSM ended the current operation.

User Response: You can take any of the following actions:

0012 EDSM_RC_ABORT_MOUNT_NOT_POSSIBLE

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

System Action: File skipped.

User Response: Retry later when server volumes can be mounted.

0013 EDSM_RC_ABORT_SIZESTIMATE_EXCEED

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

System Action: Processing stopped.

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

0014 EDSM_RC_ABORT_DATA_UNAVAILABLE

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

System Action: Processing stopped.

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

0015 EDSM_RC_ABORT_RETRY

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

System Action: Client retries the operation.

User Response: None.

0016 EDSM_RC_ABORT_NO_LOG_SPACE

Explanation: The server ran out of recovery log space.

System Action: TSM ended the current operation.

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

0017 EDSM_RC_ABORT_NO_DB_SPACE

Explanation: The server ran out of database space.

System Action: TSM ended the current operation.

User Response: See your system administrator.

0018 EDSM_RC_ABORT_NO_MEMORY

Explanation: The server ran out of memory.

System Action: TSM ended the current operation.

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

0020 EDSM_RC_ABORT_FS_NOT_DEFINED

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

System Action: TSM canceled the current operation.

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

0021 SDSM_RC_ABORT_NODE_ALREADY_DEFED

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

System Action: TSM canceled the current operation.

User Response: Retry with another node name.

0022 SDSM_RC_ABORT_NO_DEFAULT_DOMAIN

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

System Action: TSM canceled the current operation.

User Response: See your system administrator.

0023 SDSM_RC_ABORT_INVALID_NODENAME

Explanation: Open registration failed because the specified node name contains characters that are not valid.

System Action: TSM canceled the current operation.

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

0024 SDSM_RC_ABORT_INVALID_POL_BIND

Explanation: Server problem. Policy binding is not permitted.

System Action: Processing stopped.

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

0025 EDSM_RC_ABORT_DEST_NOT_DEFINED

Explanation: Server problem: Destination was not defined.

System Action: Processing stopped.

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

0026 SDSM_RC_ABORT_WAIT_FOR_SPACE

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

System Action: TSM ended the current operation.

User Response: See your system administrator.

0027 EDSM_RC_ABORT_NOT_AUTHORIZED

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

System Action: Delete processing fails.

User Response: See your system administrator.

0028 EDSM_RS_ABORT_RULE_ALREADY_DEFED

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

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

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

0029 SDSM_RC_ABORT_NO_STOR_SPACE_STOP

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

System Action: TSM ended the current operation.

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

0033 EDSM_RC_ABORT_INVALID_OFFSET

Explanation: The partialObjOffset value for partial object retrieve is not valid.

System Action: The system returns to the calling procedure.

User Response: Specify a valid value.

0034 EDSM_RC_ABORT_INVALID_LENGTH

Explanation: partialObjLength value for partial object retrieve is not valid.

System Action: The system returns to the calling procedure.

User Response: Specify a valid value.

0051 EDSM_RC_REJECT_NO_RESOURCES

Explanation: TSM has all available sessions in use and cannot accept a new one at this time.

System Action: TSM canceled the current operation.

User Response: Retry the operation. If the problem continues, see your system administrator to increase the number of concurrently active sessions to the server.

0052 EDSM_RC_REJECT_VERIFIER_EXPIRED

Explanation: Your TSM password has expired.

System Action: TSM canceled the current operation. You are not allowed to connect to the server until the password is updated.

User Response: Update your password.

0053 EDSM_RC_REJECT_ID_UNKNOWN

Explanation: The node name you entered is not known by the server, or you are attempting to access a file that is migrated to a different node.

System Action: TSM canceled the current operation. You are not allowed to connect to the server until your node name is registered with the server. If attempting to access a migrated file, your node name must be the same node which migrated the file.

User Response: Ensure that you entered your TSM node name correctly. If you did, go to your system administrator. Verify that the server is using closed registration and that your node name is registered with the server.

0054 EDSM_RC_REJECT_DUPLICATE_ID

Explanation: Another process using this node name is active with the server.

System Action: TSM cannot connect to the server. TSM canceled the current operation.

User Response: If you are running a UNIX-based system, ensure that another process is not active with TSM under the same name. Also, ensure that your node name is unique to the server so that it cannot be used by another person. See your system administrator to identify the owner of that node name.

0055 EDSM_RC_REJECT_SERVER_DISABLED

Explanation: The server is in a disabled state and cannot be accessed for normal activity.

System Action: TSM canceled the current operation.

User Response: Retry the operation after the server returns to an enabled state. If the problem continues, see your system administrator.

0056 EDSM_RC_REJECT_CLOSED_REGISTER

Explanation: No authorization. Registration is required by your system administrator. The server is not configured to allow open registration.

System Action: The session has not started.

User Response: You must obtain a TSM node and password from your system administrator.

0057 SDSM_RC_REJECT_CLIENT_DOWNLEVEL

Explanation: The server version and your client version do not match. The client code is downlevel.

System Action: TSM canceled the current operation.

User Response: See your system administrator to see what version of TSM to run for your location.

0058 SDSM_RC_REJECT_SERVER_DOWNLEVEL

Explanation: The server version and your client version do not match. The server code is downlevel.

System Action: TSM canceled the current operation.

User Response: See your system administrator to see what version of TSM to run for your location.

0059 EDSM_RC_REJECT_ID_IN_USE

Explanation: The node name you specified is in use on the server.

System Action: Session was not started.

User Response: The server is probably performing a task that prevents your node from establishing a session. Retry later or check with your system administrator.

0061 EDSM_RC_REJECT_ID_LOCKED

Explanation: The node name you specified is currently locked on the server.

System Action: Session was not started.

User Response: Check with your system administrator to find out why your node name is locked.

0062 SDSM_RC_SIGNONREJECT_LICENSE_MAX

Explanation: Adding a new enrollment will exceed the product license count for TSM.

System Action: Processing of the client enrollment or connection request ends.

User Response: See your system administrator.

0063 EDSM_RC_REJECT_NO_MEMORY

Explanation: The server does not have enough memory to allow your client to establish a connection with the server.

System Action: Session was not started.

User Response: Retry later or see your system administrator.

0064 EDSM_RC_REJECT_NO_DB_SPACE

Explanation: The server ran out of database space.

System Action: Session was not started.

User Response: See your system administrator.

0065 EDSM_RC_REJECT_NO_LOG_SPACE

Explanation: The server ran out of recovery log space.

System Action: Session was not started.

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

0066 EDSM_RC_REJECT_INTERNAL_ERROR

Explanation: The client cannot establish a connection to the server because of an internal server error.

System Action: Session was not started.

User Response: See your system administrator immediately.

0067 SDSM_RC_SIGNONREJECT_INVALID_CLI

Explanation: The server is not licensed for the requesting client type.

System Action: Processing of the client enrollment or connection request ends.

User Response: See your system administrator.

0068 WDSM_RC_SESSION_CANCELED

Explanation: The server administrator canceled the current client session.

System Action: Processing of the client connection request ends.

User Response: See your system administrator.

0101 IDSM_RC_USER_ABORT

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

System Action: Processing stopped.

User Response: Continue with normal operations.

0102 EDSM_RC_NO_MEMORY

Explanation: The program has used all available storage.

System Action: Processing stopped.

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

0104 EDSM_RC_FILE_NOT_FOUND

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

System Action: File skipped.

User Response: None.

0105 EDSM_RC_PATH_NOT_FOUND

Explanation: You specified an incorrect directory path.

System Action: Processing stopped.

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

0106 EDSM_RC_ACCESS_DENIED

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

System Action: Processing stopped.

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

0107 EDSM_RC_NO_HANDLES

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

System Action: Processing stopped.

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

0108 EDSM_RC_FILE_EXISTS

Explanation: The file being restored or retrieved exists.

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

User Response: None.

0109 EDSM_RC_INVALID_PARM

Explanation: The system encountered an internal program error due to a parameter that is not valid.

System Action: The system returns to the calling procedure.

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

0110 EDSM_RC_INVALID_HANDLE

Explanation: An internal system error occurred. A file operation failed because a file handle was passed that is not valid.

System Action: Processing stopped.

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

0111 EDSM_RC_DISK_FULL

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

System Action: Processing stopped.

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

0113 EDSM_RC_PROTOCOL_VIOLATION

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

System Action: TSM ended the current operation.

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

0114 EDSM_RC_UNKNOWN_ERROR

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

System Action: Processing stopped.

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

0115 EDSM_RC_UNEXPECTED_ERROR

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

System Action: Processing stopped.

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

0116 EDSM_RC_FILE_BEING_EXECUTED

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

System Action: File skipped.

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

0117 EDSM_RC_DIR_NO_SPACE

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.

0118 EDSM_RC_LOOPED_SYM_LINK

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

System Action: File skipped.

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

0119 EDSM_RC_FILE_NAME_TOO_LONG

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

System Action: File is skipped.

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

0120 EDSM_RC_FILE_SPACE_LOCKED

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

System Action: TSM cannot complete the operation.

User Response: See your system administrator.

0121 IDSM_RC_FINISHED

Explanation: The operation is finished.

System Action: The system returns to the calling procedure.

User Response: Proceed with next function call.

0122 EDSM_RC_UNKNOWN_FORMAT

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

System Action: File skipped.

User Response: See your system administrator.

0123 EDSM_RC_NO_AUTHORIZATION

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.

0124 EDSM_RC_FILE_SPACE_NOT_FOUND

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

System Action: Processing stopped.

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

0125 EDSM_RC_TXN_ABORTED

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

System Action: TSM canceled the current operation.

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

0126 EDSM_RC_SUBDIR_AS_FILE

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

System Action: Processing stopped.

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

0127 EDSM_RC_PROCESS_NO_SPACE

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

System Action: Processing stopped.

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

0128 EDSM_RC_PATH_TOO_LONG

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

System Action: Processing stopped.

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

0129 EDSM_RC_NOT_COMPRESSED

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

System Action: Processing stopped.

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

0130 EDSM_RC_TOO_MANY_BITS

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

System Action: TSM canceled the operation.

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

0131 SDSM_RC_SYSTEM_ERROR

Explanation: An unexpected program failure occurred.

System Action: Processing stopped.

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

0132 EDSM_RC_NO_SERVER_RESOURCES

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

System Action: TSM canceled the current operation.

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

0133 EDSM_RC_FS_NOT_KNOWN

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

System Action: Processing stopped.

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

0134 EDSM_RC_NO_LEADING_DIRSEP

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.

0135 EDSM_RC_WILDCARD_DIR

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.

0136 EDSM_RC_COMM_PROTOCOL_ERROR

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

System Action: TSM canceled the current operation.

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

0137 EDSM_RC_AUTH_FAILURE

Explanation: Authentication failure. You entered an incorrect password.

System Action: TSM canceled the current operation.

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

0138 EDSM_RC_TA_NOT_VALID

Explanation: The trusted agent execution/owner permissions are not permitted.

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.

0139 SDSM_RC_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.

0145 SDSM_RC_WOULD_BLOCK

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.

0146 SDSM_RC_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.

0147 SDSM_RC_UNCLOSED

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.

0148 SDSM_RC_NO_STARTING_DELIMITER

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

System Action: Processing stopped.

User Response: Correct the syntax for the pattern.

0149 SDSM_RC_NEEDED_DIR_DELIMITER

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

System Action: Processing stopped.

User Response: Correct the syntax for the pattern.

0150 SDSM_RC_UNKNOWN_FILE_DATA_TYPE

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.

0151 SDSM_RC_BUFFER_OVERFLOW

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.

0154 EDSM_RC_NO_COMPRESS_MEMORY

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

System Action: Processing stopped.

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

0155 TDSM_RC_COMPRESS_GREW

Explanation: During compression, the compressed data grew in size compared to the original data.

System Action: Processing stopped.

User Response: Send the file, uncompressed.

0156 EDSM_RC_INV_COMM_METHOD

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

System Action: Processing stopped.

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

0157 SDSM_RC_WILL_ABORT

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.

0158 EDSM_RC_FS_WRITE_LOCKED

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

System Action: File skipped.

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

0159 IDSM_RC_SKIPPED_BY_USER

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 that the application sets the mountWait value correctly on dsmBeginGetData.

0160 EDSM_RC_TA_NOT_FOUND

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, and for V2R1 the name is dsmapitca.

System Action: TSM ends.

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

0161 EDSM_RC_TA_ACCESS_DENIED

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

System Action: Processing stopped.

User Response: Contact your system administrator.

0162 EDSM_RC_FS_NOT_READY

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

System Action: Processing stopped.

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

0163 EDSM_RC_FS_IS_BAD

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

System Action: Processing stopped.

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

0164 EDSM_RC_FIO_ERROR

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

System Action: File or file system is skipped.

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

0165 EDSM_RC_WRITE_FAILURE

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

System Action: File skipped.

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

0166 EDSM_RC_OVER_FILE_SIZE_LIMIT

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

System Action: File skipped.

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

0167 EDSM_RC_CANNOT_MAKE

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

System Action: File skipped.

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

0168 EDSM_RC_NO_PASS_FILE

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.

0169 EDSM_RC_VERFILE_OLD

Explanation: Either the password is not stored locally, or it was changed at the server.

System Action: TSM prompts you for the password if TSM is running in the foreground.

User Response: If TSM was running as a background process, issue any TSM command from the foreground. Enter the password in answer to the prompt. Then try your background TSM command again.

0173 EDSM_RC_INPUT_ERROR

Explanation: Unable to read commands that are entered from the keyboard. TSM cannot process your intended command.

System Action: Processing stopped.

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

0174 EDSM_RC_REJECT_PLATFORM_MISMATCH

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

System Action: TSM canceled the current operation.

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

0175 EDSM_RC_TL_NOT_FILE_OWNER

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

System Action: TSM skips the file.

User Response: None.

0176 SDSM_RC_DBCS_IN_RANGE

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

System Action: Processing stopped.

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

0177 SDSM_RC_UNMATCHED_QUOTE

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

System Action: Processing stopped.

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

0184 EDSM_RC_TL_NOBCG

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

System Action: Processing stopped.

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

0185 WDSM_RC_TL_EXCLUDED

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

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

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

0186 EDSM_RC_TL_NOACG

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

System Action: Processing stopped.

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

0187 EDSM_RC_PS_INVALID_ARCHMC

Explanation: You entered a management class that is not valid.

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

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

0188 SDSM_RC_NO_PS_DATA

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

System Action: Processing stopped.

User Response: See your system administrator.

0189 SDSM_RC_PS_INVALID_DIRMC

Explanation: A management class was assigned to directories that is not valid.

System Action: Processing stopped.

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

0190 SDSM_RC_PS_NO_CG_IN_DIR_MC

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

System Action: Processing stopped.

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

0200 EDSM_RC_TCA_ATTACH_SHR_MEM_ERR

Explanation: An error has occurred while attaching the trusted agent's shared memory.

System Action: Return to caller.

User Response: Stop application, check shared memory usage and retry the command. Read the tca.log file for the system error number.

0292 EDSM_RC_TCA_FORK_FAILED

Explanation: An error has occurred starting the Trusted Communication Agent process; specifically, the fork() function has failed.

System Action: TSM ends.

User Response: Probable system error. If the problem persists, restart the workstation.

0294 EDSM_RC_TCA_DIED

Explanation: The Trusted Communication Agent has unexpectedly ended.

System Action: TSM ends.

User Response: Check the error log for more information. Retry the activity. If the problem persists, contact your service representative.

0295 EDSM_RC_TCA_INVALID_REQUEST

Explanation: The Trusted Communication Agent has received an unknown request from the TSM client.

System Action: TSM ends.

User Response: Internal error. If the problem recurs, contact your service representative.

0296 EDSM_RC_TCA_NOT_ROOT

Explanation: An activity has been attempted that must be performed by the TSM administrator (for example, open registration, filespace delete or password update).

System Action: TSM ends.

User Response: If the activity is required, the administrator for this system must perform it.

0297 EDSM_RC_TCA_SEMGET_ERROR

Explanation: An error has occurred because the semaphores you are attempting to allocate have become insufficient.

System Action: Processing ends.

User Response: Ask your system administrator for assistance, and possibly increase the number of semaphores in your system.

0298 EDSM_RC_TCA_SEM_OP_ERROR

Explanation: An error has occurred while attempting to set or wait on a semaphore.

System Action: Processing ends.

User Response: Probable system error. If the problem persists, restart the workstation.

0400 EDSM_RC_INVALID_OPT

Explanation: An option was found that is not valid.

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).

0405 EDSM_RC_NO_HOST_ADDR

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

System Action: TSM initialization fails, and the program ends.

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

0406 SDSM_RC_NO_OPT_FILE

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

System Action: The TSM client ends.

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

0408 EDSM_RC_MACHINE_SAME

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

System Action: Initialization fails, and the program ends.

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

0409 EDSM_RC_INVALID_SERVER

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

System Action: TSM initialization fails, and the program ends.

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

0410 EDSM_RC_INVALID_KEYWORD

Explanation: An option keyword that is not valid 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.

0411 SDSM_RC_PATTERN_TOO_COMPLEX

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

System Action: Processing stopped.

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

0412 SDSM_RC_NO_CLOSING_BRACKET

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

System Action: Processing stopped.

User Response: Correct the syntax for the pattern.

0600 EDSM_RC_DUP_LABEL

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

System Action: TSM cannot select the drive.

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

0601 EDSM_RC_NO_LABEL

Explanation: The selected drive does not have a label.

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

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

0610 EDSM_RC_NLS_CANT_OPEN_TXT

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 .

0611 EDSM_RC_NLS_CANT_READ_HDR

Explanation: The system is unable to use the message text file (dscameng.txt or dsmclientV3.cat for AIX) because of a header that is not valid. 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.

0612 EDSM_RC_NLS_INVALID_CNTL_REC

Explanation: The system is unable to use the message txt file (dscameng.txt or dsmclientV3.cat for AIX) because of a control record that is not valid. 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.

0613 EDSM_RC_NLS_INVALID_DATE_FMT

Explanation: A value that is not permitted is specified for DATEFORMAT.

System Action: The system returns to the calling procedure.

User Response: Specify a valid value.

0614 EDSM_RC_NLS_INVALID_TIME_FMT

Explanation: A value that is not permitted is specified for TIMEFORMAT.

System Action: The system returns to the calling procedure.

User Response: Specify a valid value.

0615 EDSM_RC_NLS_INVALID_NUM_FMT

Explanation: A value that is not permitted is specified for NUMBERFORMAT.

System Action: The system returns to the calling procedure.

User Response: Specify a valid value.

0620 EDSM_RC_LOG_CANT_BE_OPENED

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 that the value specified for ERRORLOGNAME in the API options file.

0621 EDSM_RC_LOG_ERROR_WRITING_TO_LOG

Explanation: There was an error in 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 that is specified for ERRORLOGNAME in the API options file.

0622 EDSM_RC_LOG_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 that is specified for ERRORLOGNAME in the API options file.

0927 EDSM_RC_NOT_ADSM_AUTHORIZED

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

System Action: Processing stopped.

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

2000 EDSM_RC_NULL_OBJNAME

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

System Action: The system returns to the calling procedure.

User Response: Provide an address for the dsmObjName structure.

2001 EDSM_RC_NULL_DATABLKPTR

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

System Action: The system returns to the calling procedure.

User Response: Provide an address for the DataBlk structure.

2002 EDSM_RC_NULL_MSG

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.

2004 EDSM_RC_NULL_OBJATTRPTR

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

System Action: The system returns to the calling procedure.

User Response: Provide an address for the ObjAttr structure.

2006 EDSM_RC_NO_SESS_BLK

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.

2007 EDSM_RC_NO_POLICY_BLK

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.

2008 EDSM_RC_ZERO_BUFLEN

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.

2009 EDSM_RC_NULL_BUFPTR

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

System Action: The system returns to the calling procedure.

User Response: Provide an address for the bufferPtr.

2010 EDSM_RC_INVALID_OBJTYPE

Explanation: The value for the objType is not valid.

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.

2011 EDSM_RC_INVALID_VOTE

Explanation: The dsmEndTxn vote is not valid.

System Action: The system returns to the calling procedure.

User Response: The vote must be DSM_VOTE_COMMIT or DSM_VOTE_ABORT.

2012 EDSM_RC_INVALID_ACTION

Explanation: The dsmUpdateFS or dsmUpdateObj action is not valid.

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.

2014 EDSM_RC_INVALID_DS_HANDLE

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 ended by a dsmTerminate call. If the problem continues, contact your system administrator or service representative.

2015 EDSM_RC_INVALID_REPOS

Explanation: The repository type is not valid.

System Action: The system returns to the calling procedure.

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

2016 EDSM_RC_INVALID_FSNAME

Explanation: The filespace name is not valid.

System Action: The system returns to the calling procedure.

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

2017 EDSM_RC_INVALID_OBJNAME

Explanation: The object name is not valid 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.

2018 EDSM_RC_INVALID_LLNAME

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

System Action: The system returns to the calling procedure.

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

2019 EDSM_RC_INVALID_OBJOWNER

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.

2020 EDSM_RC_INVALID_ACTYPE

Explanation: The dsmBindMC sendType is not valid.

System Action: The system returns to the calling procedure.

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

stBackup

stArchive

stBackupMountWait

stArchiveMountWait

2021 EDSM_RC_INVALID_RETCODE

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.

2022 EDSM_RC_INVALID_SENDTYPE

Explanation: The dsmSendObj sendType is not valid.

System Action: The system returns to the calling procedure.

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

stBackup

stArchive

stBackupMountWait

stArchiveMountWait

2023 EDSM_RC_INVALID_PARAMETER

Explanation: The dsmDeleteObj delType is not valid.

System Action: The system returns to the calling procedure.

User Response: The delType must be dtBackup or dtArchive.

2024 EDSM_RC_INVALID_OBJSTATE

Explanation: The query Backup objState is not valid.

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

2025 EDSM_RC_INVALID_MCNAME

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.

2026 EDSM_RC_INVALID_DRIVE_CHAR

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 referred field is dsmDosFSAttrib.driveLetter.

2027 EDSM_RC_NULL_FSNAME

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

System Action: The system returns to the calling procedure.

User Response: Provide a filespace name on dsmRegisterFS.

2028 EDSM_RC_INVALID_HLNAME

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

System Action: The system returns to the calling procedure.

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

2029 EDSM_RC_NUMOBJ_EXCEED

Explanation: The number of objects (numObjId) that are 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 that number is greater than DSM_MAX_GET_OBJ | DSM_MAX_PARTIAL_GET_OBJ, then issue several Get call sequences.

2030 EDSM_RC_NEWPW_REQD

Explanation: There is no value that is provided for new password.

System Action: The system returns to the calling procedure.

User Response: Provide a new password on dsmChangePW.

2031 EDSM_RC_OLDPW_REQD

Explanation: There is no value that is provided for the old password.

System Action: The system returns to the calling procedure.

User Response: Provide an old password on dsmChangePW.

2032 EDSM_RC_NO_OWNER_REQD

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.

2033 EDSM_RC_NO_NODE_REQD

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.

2034 EDSM_RC_KEY_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.

2035 EDSM_RC_KEY_BAD

Explanation: The key file content for Tivoli Data Protection application client for Oracle is not valid.

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.

2041 EDSM_RC_BAD_CALL_SEQUENCE

Explanation: The sequence of calls is not valid.

System Action: The system returns to the calling procedure.

User Response: Verify the transaction call sequence.

2050 EDSM_RC_WILDCHAR_NOTALLOWED

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

System Action: The system returns to the calling procedure.

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

2060 EDSM_RC_FSNAME_NOTFOUND

Explanation: The filespace to delete cannot be found.

System Action: The system returns to the calling procedure.

User Response: Verify the filespace name.

2061 EDSM_RC_FS_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.

2062 WDSM_RC_FS_ALREADY_REGED

Explanation: On dsmRegisterFS the filespace is already registered.

System Action: The system returns to the calling procedure.

User Response: Verify the filespace name.

2063 EDSM_RC_OBJID_NOTFOUND

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.

2064 EDSM_RC_WRONG_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.

2065 EDSM_RC_WRONG_VERSION_PARM

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.

2070 EDSM_RC_NEEDTO_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.

System Action: The system returns to the calling procedure.

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

2080 EDSM_RC_OBJ_EXCLUDED

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.

2081 EDSM_RC_OBJ_NOBCG

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.

2082 EDSM_RC_OBJ_NOACG

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.

2090 EDSM_RC_APISYSTEM_ERROR

Explanation: Memory used by the TSM API has been damaged.

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.

2100 EDSM_RC_DESC_TOOLONG

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.

2101 EDSM_RC_OBJINFO_TOOLONG

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.

2102 EDSM_RC_HL_TOOLONG

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.

2103 EDSM_RC_PASSWD_TOOLONG

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.

2104 EDSM_RC_FILESPACE_TOOLONG

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.

2105 EDSM_RC_LL_TOOLONG

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.

2106 EDSM_RC_FSINFO_TOOLONG

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.

2110 EDSM_RC_INVALID_ACCESS_TYPE

Explanation: The dsmSetAccess accessType is not valid.

System Action: The system returns to the calling procedure.

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

atBackup

atArchive

2111 EDSM_RC_QUERY_COMM_FAILURE

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

System Action: Processing stopped.

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

2112 EDSM_RC_NO_FILES_BACKUP

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.

2113 EDSM_RC_NO_FILES_ARCHIVE

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.

2114 EDSM_RC_INVALID_SETACCESS

Explanation: None.

System Action: Processing stopped.

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

2120 EDSM_RC_STRING_TOO_LONG

Explanation: The message text and inserts were too large to send to the server in the available internal buffer.

System Action: Refer to the local client error log for more information.

User Response: None.

2200 IDSM_RC_MORE_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.

2210 EDSM_RC_BUFF_TOO_SMALL

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.

2228 EDSM_RC_NO_API_CONFIGFILE

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.

2229 EDSM_RC_NO_INCLEXCL_FILE

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.

2230 EDSM_RC_NO_SYS_OR_INCLEXCL

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 that is referred by the environment variable DSMI_DIR. Verify the file name on the Inclexcl option in the dsm.sys file.

2231 EDSM_RC_REJECT_NO_POR_SUPPORT

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.

2300 EDSM_RC_NEED_ROOT

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

System Action: The system returns to the calling procedure.

User Response: Run this program as a root user.

2301 EDSM_RC_NEEDTO_CALL_BINDMC

Explanation: You must issue dsmBindMC before dsmSendObj.

System Action: The system returns to the calling procedure.

User Response: Change your program.

2302 IDSM_RC_CHECK_REASON_CODE

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.

2400 EDSM_RC_ALMGR_OPEN_FAIL

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

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.

2401 EDSM_RC_ALMGR_READ_FAIL

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

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.

2402 EDSM_RC_ALMGR_WRITE_FAIL

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

System Action: The system returns to the calling procedure.

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

2403 EDSM_RC__ALMGR_DATA_FMT

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.

2404 EDSM_RC_ALMGR_CKSUM_BAD

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.

2405 EDSM_RC_ALMGR_TRIAL_EXPRD

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.

2410 EDSM_RC_ORC_INVALID_MODE

Explanation: Mode passed by Oracle is not valid.

System Action: The system returns to the calling procedure.

User Response: Contact your system administrator.

2411 EDSM_RC_ORC_NULL_FILENAME

Explanation: Null filename passed by Oracle.

System Action: The system returns to the calling procedure.

User Response: Contact your system administrator.

2412 EDSM_RC_ORC_WRONG_BLKSIZE

Explanation: Wrong Block Size.

System Action: The system returns to the calling procedure.

User Response: Contact your system administrator.

2413 EDSM_RC_ORC_OBJ_EXISTS

Explanation: Backup or Restore Object already exists.

System Action: The system returns to the calling procedure.

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

2414 EDSM_RC_ORC_NOTSAME_HANDLE

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

System Action: The system returns to the calling procedure.

User Response: Contact your system administrator.

2415 EDSM_RC_ORC_END_OF_FILE

Explanation: End of file reached.

System Action: The system returns to the calling procedure.

User Response: None.

2416 EDSM_RC_ORC_WRONG_RDSTATE

Explanation: The operation must be in READ state.

System Action: The system returns to the calling procedure.

User Response: Contact IBM ADSM support.

2417 EDSM_RC_ORC_LOWER_APIVER

Explanation: Runtime API is lower than compile time API.

System Action: The system returns to the calling procedure.

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

2418 EDSM_RC_ORC_WRONG_WRTSTATE

Explanation: The operation must be in WRITE state.

System Action: The system returns to the calling procedure.

User Response: Contact IBM ADSM support.

2419 EDSM_RC_ORC_INVALID_FLAG

Explanation: Flag passed from Oracle is not valid.

System Action: The system returns to the calling procedure.

User Response: Contact your system administrator.


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