ANS messages

-452 E DSM_RC_SHM_NOTAUTH Insufficient authority to connect to the shared memory region

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 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 running dsmserv, if possible. Otherwise contact your system administrator for further help.

-451 E DSM_RC_SHM_FAILURE An error occurred using the Shared Memory protocol

Explanation

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

System action

IBM Storage Protect 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 E DSM_RC_SHM_TCPIP_FAILURE Session rejected: TCP/IP connection failure for Shared Memory

Explanation

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

System action

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

-365 E DSM_RC_SSL_BAD_CERTIFICATE Bad server certificate.

Explanation

The process was unable to open SSL connection to server because of a bad certificate. This error usually occurs when the server certificate cannot be verified by the client.

System action

Processing stopped

User response

Make sure you have configured the key database for SSL communication as described in the documentation. Make sure to import the correct certificate from the IBM Storage Protect server you are trying to connect to.

-364 E DSM_RC_SSL_KEYFILE_BAD_PASSWORD The key database password is incorrect or unavailable.

Explanation

The client was unable to open the certificate key database using the stored password, or the stored password could not be read.

System action

Processing stops.

User response

Make sure that you configure the key database for SSL communication as described in the Client Installation and User's Guide. Also make sure that the stash file, dsmcert.sth, is readable by the current user.

-363 E DSM_RC_SSL_KEYFILE_OPEN_FAILED Cannot open the key database.

Explanation

The process was unable to open the keyfile that is expected to contain the server certificate for SSL communications.

System action

Processing stopped

User response

Make sure you have configured the key database for SSL communication as described in the documentation. If the problem persists, contact IBM Storage Protect customer support.

-362 E DSM_RC_SSL_INIT_FAILED Failed to initialize SSL protocol.

Explanation

The process was unable to initialize the SSL protocol. This could be because the node is in a strict 'sessionsecurity' state and the client certificate key database could not be found.

System action

Processing stopped

User response

Check for GSKit related messages in the error log. Make sure you have configured the key database for SSL communication as described in the documentation. You must manually import the client certificate by using the dsmcert utility. If the problem persists, contact IBM Storage Protect customer support.

-361 E DSM_RC_SSL_NOT_SUPPORTED SSL protocol is not supported.

Explanation

SSL protocol is not supported on this platform.

System action

Processing stopped

User response

Refer to IBM Storage Protect documentation for the list of supported platforms.

-190 E DSM_RC_NP_ERROR Session rejected: Named Pipes connection failure.

Explanation

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

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 used by the server. If the problem continues, contact your system administrator for further help.

-057 E DSM_RC_TCPIP_LOADFAILURE 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.

-056 E DSM_RC_TCPIP_DLL_LOADFAILURE 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.

-055 E DSM_RC_WINSOCK_MISSING 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.

-054 E DSM_RC_NETWORK_UNREACHABLE The specified TCP/IP host name is 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 E DSM_RC_BAD_HOST_NAME An invalid TCP/IP address was specified.

Explanation

The TCP/IP address specified by the IBM Storage Protect client's TCPSERVERADDRESS setting could not be found on the network. Common reasons for this error include:
  • The TCPSERVERADDRESS client option specifies the wrong TCP/IP address for the IBM Storage Protect server".
  • The machine that hosts the IBM Storage Protect server is not on the network.
  • A network problem is preventing the IBM Storage Protect client from reaching the machine that hosts the IBM Storage Protect server.

System action

processing stops.

User response

Verify that the TCPSERVERADDRESS and TCPPORT settings have the correct values for your IBM Storage Protect server. Use your operating system's "ping" (or similar) utility to ensure that your machine can locate the machine that hosts the IBM Storage Protect server across the network. Try the operating again. If the problem persists, ask your IBM Storage Protect administrator for further assistance.

-052 E DSM_RC_CONN_REFUSED An attempt to establish a TCP/IP connection was rejected by the host

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 E DSM_RC_CONN_TIMEDOUT The attempt to establish a TCP/IP connection timed out before the connection was made.

Explanation

The Object of the connection attempt failed to respond within the the allotted wait time. In the case of the B/A client, this message is preceded in dsmerror.log by message ANS5216E that gives details of the connection that failed. The condition may be temporary.

System action

processing stops.

User response

  • Restart the IBM Storage Protect client and retry the operation.
  • Check the client options file and verify that TCPSERVERADDRESS and TCPPORT specify the correct TCP/IP address and port number for your IBM Storage Protect server.
  • Verify that network connectivity exists between the IBM Storage Protect client machine and the IBM Storage Protect server machine.
  • If the problem persists, see your IBM Storage Protect administrator for further assistance.

-050 E DSM_RC_TCPIP_FAILURE Session rejected: TCP/IP connection failure.

Explanation

An attempt to connect to the server using TCP/IP communications failed. This can be a result of incorrect TCP/IP option settings in your client options file. This error can also occur if the LAN connection went down or if your system administrator canceled a backup operation.

System action

Session 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 I DSM_RC_OK Successfully done.

Explanation

The operation successfully completed.

System action

None.

User response

None.

0001 E DSM_RC_ABORT_SYSTEM_ERROR This operation cannot continue due to an error on the IBM Storage Protect server. See your IBM Storage Protect server administrator for assistance.

Explanation

The IBM Storage Protect server encountered an error condition that prevents the IBM Storage Protect client operation from continuing. Your IBM Storage Protect server administrator can review the IBM Storage Protect server activity log for more details about the error.

System action

Processing stopped.

User response

Contact your IBM Storage Protect server administrator for assistance. The administrator can review the IBM Storage Protect server activity log for further information about the conditions that lead to this error.

0002 E DSM_RC_ABORT_NO_MATCH No objects on server match query

Explanation

No objects on the server match the query operation being performed. If this object is part of a backupset generated on a node, and the node name is changed on the server, any backup set objects that were generated prior to the name change will not match the new node name.

System action

Processing stopped.

User response

Ensure the names are properly entered. If the object is part of a backupset generated prior to a node name change, ensure that the node name is the same as the node for which the backup set was generated.

0003 E DSM_RC_ABORT_BY_CLIENT Client ended transaction

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 W DSM_RC_ABORT_ACTIVE_NOT_FOUND An active backup version could not be found.

Explanation

An attempt was made to expire an object, but the IBM Storage Protect server was unable to find an active backup version of the object. This message is preceded by message ANS1228E which specifies the object name.

For instance, this message could be issued if two separate client processes are backing up the same file system at the same time. If one of the processes expires a file, then the IBM Storage Protect server will make that file inactive. If the second process subsequently attempts to expire that same file, the IBM Storage Protect server will not find an active version of the file, so the second process will issue this message for that file.

System action

The object is not expired. Processing continues with the next object.

User response

  • Review the console output, schedule log, or error log and locate the ANS1228E message that immediately precedes this message. ANS1228E will identify the object that could not be expired.
  • Examine the conditions under which the problem occurred and assess whether those conditions explain the occurrence of this message. For example, this message could appear if multiple instances of the client were attempting to back up the file system concurrently.

  • If the reason this message occurred can not be determined and the message occurs when the operation is tried again, then contact IBM support for further assistance. Also try searching for this message number on http://www.ibm.com for possible solutions.

0005 E DSM_RC_ABORT_NO_DATA The IBM Storage Protect server has no data for the object.

Explanation

IBM Storage Protect tried to do a restore or retrieve on an object that has no data associated with it. If a corrective action is possible, it is with the IBM Storage Protect server.

System action

IBM Storage Protect ends the current operation.

User response

Ask the IBM Storage Protect administrator to check the IBM Storage Protect activity log for any messages related to this error that might help identify the problem.

0006 E DSM_RC_ABORT_BAD_VERIFIER You entered an incorrect password.

Explanation

You entered an incorrect current password or you entered a new password that does not fulfill the password length requirements set on the server.

System action

Processing stops.

User response

Retry the session with the correct password. If this fails or you have forgotten your password, ask the IBM Storage Protect administrator to assign a new password.

0007 E DSM_RC_ABORT_NODE_IN_USE 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 E DSM_RC_ABORT_EXPDATE_TOO_LOW Expiration date must be greater than today's date

Explanation

Archive expiration date is too low, the date must be greater than today's date.

System action

IBM Storage Protect canceled the current operation.

User response

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

0009 W DSM_RC_ABORT_DATA_OFFLINE The requested data is 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

IBM Storage Protect waits for offline storage media to become available and then continues.

User response

None.

0010 E DSM_RC_ABORT_EXCLUDED_BY_SIZE Object too large for server limits

Explanation

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

System action

File skipped.

User response

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

0011 E DSM_RC_ABORT_NO_REPOSIT_SPACE Server out of data storage space

Explanation

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

System action

Processing Ends.

User response

You can take any of the following actions:
  • Request the system administrator to add space to the storage pool.
  • For IBM Storage Protect client, set COMPRESSALWAYS=NO and COMPRESSIon=YES in the options file (DSM.OPT), then the file will be resent uncompressed if it grows during compression.
  • For API Applications, consult the application's documentation for recommendations regarding compression.
  • Turn off disk caching in the disk storage pool, and issue MOVE DATA commands to each disk pool volume to clear out the cached bitfiles.

0012 E DSM_RC_ABORT_MOUNT_NOT_POSSIBLE Server media 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. Ensure that the MAXNUMMP (maximum number of mount points) defined on the server for this node is greater than 0.

0013 E DSM_RC_ABORT_SIZESTIMATE_EXCEED Size estimate exceeded

Explanation

The total amount of data for a backup or archive operation exceeds the estimated size 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 E DSM_RC_ABORT_DATA_UNAVAILABLE File data currently unavailable on server

Explanation

The file data is currently unavailable on the server. A retrieve or restore operation was attempted. Possible causes are:
  • Data was corrupted at the server
  • Server found a read error
  • File is temporarily involved in a reclaim operation at the server
  • Server requested a tape volume that was marked unavailable.

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 E DSM_RC_ABORT_RETRY Unexpected retry request. The IBM Storage Protect server found an error while writing the data.

Explanation

None.

System action

If the current operation supports another attempt, the client tries the operation again. Otherwise, processing stops.

User response

None.

0016 E DSM_RC_ABORT_NO_LOG_SPACE The server does not have enough recovery log space to
continue the current operation

Explanation

The server ran out of recovery log space.

System action

Processing ends.

User response

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

0017 E DSM_RC_ABORT_NO_DB_SPACE The server does not have enough database space to continue
the current operation

Explanation

The server ran out of database space.

System action

Processing ends.

User response

See your system administrator.

0018 E DSM_RC_ABORT_NO_MEMORY The server does not have enough memory to continue the current operation.

Explanation

The server ran out of memory.

System action

Processing ends.

User response

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

0020 E DSM_RC_ABORT_FS_NOT_DEFINED The specified file space does not exist on the server. The
file space might have been deleted by another client or an
administrator.

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

Current operation has been cancelled.

User response

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

0021 S DSM_RC_ABORT_NODE_ALREADY_DEFED Open Registration failed because the specified node name is defined in the server

Explanation

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

System action

Current operation has been cancelled.

User response

Retry with another node name.

0022 S DSM_RC_ABORT_NO_DEFAULT_DOMAIN Open Registration failed because no default domain exists

Explanation

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

System action

Current operation has been cancelled.

User response

See your system administrator.

0023 S DSM_RC_ABORT_INVALID_NODENAME Open Registration failed because an invalid node name was specified

Explanation

Open registration failed because the specified node name contains invalid characters.

System action

Current operation has been cancelled.

User response

Retry with another node name that does not have any invalid characters.

0024 E DSM_RC_ABORT_NO_INVALID_POL_BIND An object in the transaction has been bound to an invalid management class.

Explanation

One of the objects in the transaction is bound to a management class that is not part of this node's policy, or the management class type is not supported for this client level.

System action

The current operation ends.

User response

Make sure all objects are bound to a valid management class, or upgrade the client to the proper level.

0024 S DSM_RC_ABORT_INVALID_POL_BIND A policy management problem has occurred on the IBM Storage Protect server.

Explanation

The client error log and IBM Storage Protect server activity log may contain additional information about this error.

System action

Processing is stops.

User response

Try the operation again. If the problem persists, examine the client error log and IBM Storage Protect server activity log for additional information about this error. If the problem cannot be resolved, then obtain a SERVICE trace that captures the problem and contact IBM technical support for additional assistance. Your IBM Storage Protect administrator can help you configure the trace.

0025 E DSM_RC_ABORT_DEST_NOT_DEFINED 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.

0026 S DSM_RC_ABORT_WAIT_FOR_SPACE The IBM Storage Protect server does not currently have space in the storage pool for this file. This may be a temporary condition.

Explanation

This message is typically issued when the storage pool in which the data is being placed does not have sufficient space to store the data, but the space will be available soon. For example, a storage pool migration might free up sufficient space to store the data.

System action

Current operation has been cancelled.

User response

Try the operation at a later time. If this fails, contact the IBM Storage Protect administrator and request more storage pool space.

0027 E DSM_RC_ABORT_NOT_AUTHORIZED The file space cannot be deleted because this node does not have permission to delete archived or backed up data.

Explanation

You cannot delete the file space data unless your IBM Storage Protect administrator has authorized your node to do so. Authorization permits you to delete backup data, archive data, or both.

System action

Delete processing fails.

User response

Use the DSMC QUERY SESSION command to verify your authorization. Ask your IBM Storage Protect administrator to provide the necessary authorization or to delete the file space for you.

0028 E DSM_RS_ABORT_RULE_ALREADY_DEFED 'Access rule' Access Rule already defined for node 'node'.
Old rule must be deleted before new one can be defined.

Explanation

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

System action

IBM Storage Protect 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 S DSM_RC_ABORT_NO_STOR_SPACE_STOP Server out of data storage space

Explanation

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

System action

Processing Ends.

User response

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

0030 E DSM_RC_ABORT_LICENSE_VIOLATION The operation is not permitted due to server licenses values.

Explanation

The node or user is trying to perform an operation that either exceeds license values, or is not licensed.

System action

The session is rejected or the transaction is cancelled, ending the current operation.

User response

See your system administrator.

0032 E DSM_RC_ABORT_DUPLICATE_OBJECT 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.

0033 E DSM_RC_ABORT_INVALID_OFFSET 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.

0034 E DSM_RC_ABORT_INVALID_LENGTH 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.

0036 E DSM_RC_END_NODE_NOT_AUTHORIZED The node or user does not have proper authority to perform this operation

Explanation

The node or user does not have proper authority to perform this operation.

System action

The transaction is ended.

User response

Check the authority for the specified object.

0041 E DSM_RC_ABORT_EXCEED_MAX_MP This node has exceeded its maximum number of mount points.

Explanation

Either no tape or sequential disk mount points are permitted for this operation, or the maximum number of mount points allowed are already in use. The operation can not be completed. The IBM Storage Protect administrator defines the maximum number of mount points with the MAXNUMMP property of your node definition.

System action

The object is skipped

User response

If you are performing any other operations that might be using mount points, wait until those operations are complete, then try the failed operation again. Otherwise contact your IBM Storage Protect administrator for further assistance

0045 E DSM_RC_ABORT_MERGE_ERROR 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.

0047 E DSM_RC_ABORT_INVALID_OPERATION An invalid operation was attempted on a node

Explanation

The operation is not valid.

System action

Current operation has ended.

User response

Contact your system administrator for more information.

0048 E DSM_RC_ABORT_STGPOOL_UNDEFINED The specified target storage pool is not defined.

Explanation

The storage pool is not defined.

System action

Current operation has ended.

User response

Contact your system administrator for more information.

0049 E DSM_RC_ABORT_INVALID_DATA_FORMAT A target storage pool does not have the correct data format for the given node type.

Explanation

none

System action

Current operation has ended.

User response

Contact your system administrator for more information.

0050 E DSM_RC_ABORT_DATAMOVER_UNDEFINED No associated data mover is defined for the given node.

Explanation

none

System action

Current operation has ended.

User response

Contact your system administrator for more information.

0051 E DSM_RC_REJECT_NO_RESOURCES Session rejected: All server sessions are currently in use

Explanation

IBM Storage Protect has all available sessions in use and cannot accept a new one at this time.

System action

Current operation has been cancelled.

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 E DSM_RC_REJECT_VERIFIER_EXPIRED The session is rejected. Your password has expired.

Explanation

The password for IBM Storage Protect user ID has expired. It can be either IBM Storage Protect node name password or administrative user ID password or both.

System action

Current operation has been cancelled. You are not allowed to connect to the server until the password is updated.

User response

Update your password. It may require updating the node name password or the corespondent administrative ID password or both. You may use the SET PASSWORD command, or have the IBM Storage Protect administrator update your node or your administrative ID.

0053 E DSM_RC_REJECT_ID_UNKNOWN Session rejected: User ID is incorrect, does not have admin authority, or is not known by the server

Explanation

The user ID, which is either IBM Storage Protect node name or administrative user ID, is not known by the server. Possible reasons for this include:
  • Your node name is not registered with the IBM Storage Protect server
  • The node name is correct but does not have a corresponding administrative ID with the same name and client owner authority
  • you are attempting to access a file that was migrated to a different node.

System action

Current operation has been cancelled.

User response

Do the following checks:
  • Check that your IBM Storage Protect user ID is entered correctly.
  • Check the administrative ID associated with your IBM Storage Protect node and verify that the IBM Storage Protect node name has a matching administrative ID with client owner authority for the node. If it does not, your IBM Storage Protect administrator needs to create it.
  • Check that the server is using closed registration and that your node name is registered with the server.
  • If attempting to access a migrated file, your node name must be the same node that migrated the file.

0054 E DSM_RC_REJECT_DUPLICATE_ID Session rejected: Duplicate ID entered

Explanation

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

System action

IBM Storage Protect cannot connect to the server. Current operation has been cancelled.

User response

If you are running a UNIX-based system, ensure that another process is not active with IBM Storage Protect 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 E DSM_RC_REJECT_SERVER_DISABLED Session rejected: Server disabled.

Explanation

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

System action

Current operation has been cancelled.

User response

On the IBM Storage Protect server, run the ENABLE SESSIONS administrative command. Try the operation again after the server returns to an enabled state. If the problem continues, see your system administrator.

0056 E DSM_RC_REJECT_CLOSED_REGISTER The server is not configured to allow open registration

Explanation

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

System action

Session not started.

User response

You must obtain a IBM Storage Protect node and password from your system administrator.

0057 S DSM_RC_REJECT_CLIENT_DOWNLEVEL Session rejected: Downlevel client code version

Explanation

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

System action

Current operation has been cancelled.

User response

See your system administrator to see what version of IBM Storage Protect to run for your location.

0058 S DSM_RC_REJECT_SERVER_DOWNLEVEL Session rejected: Downlevel server code version

Explanation

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

System action

Current operation has been cancelled.

User response

See your system administrator to see what version of IBM Storage Protect to run for your location.

0059 E DSM_RC_REJECT_ID_IN_USE Session Rejected: The specified node name is currently 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 E DSM_RC_REJECT_ID_LOCKED Session Rejected: The specified node name is currently 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 S DSM_RC_SIGNONREJECT_LICENSE_MAX SLM LICENSE EXCEEDED: The client licenses for IBM Storage Protect are exceeded.
See your system administrator.

Explanation

Adding a new enrollment will exceed the product license count for IBM Storage Protect.

System action

Execution of the client enrollment or connection request ends.

User response

See your system administrator.

0063 E DSM_RC_REJECT_NO_MEMORY Session Rejected: The server does not have enough memory to
allow a connection to be established.

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 E DSM_RC_REJECT_NO_DB_SPACE Session Rejected: The server does not have enough database
space to allow a connection to be established.

Explanation

The server ran out of database space.

System action

Session was not started.

User response

See your system administrator.

0065 E DSM_RC_REJECT_NO_LOG_SPACE Session Rejected: The server does not have enough recovery log
space to allow a connection to be established.

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 E DSM_RC_REJECT_INTERNAL_ERROR The session is rejected. The IBM Storage Protect server has an internal error.

Explanation

The client cannot establish a connection to the IBM Storage Protect server because of an internal server error.

System action

The session was not started.

User response

Notify your IBM Storage Protect administrator of this error.

0067 S DSM_RC_SIGNONREJECT_INVALID_CLI Session Rejected: The server is not licensed for this platform type.
See your system administrator.

Explanation

The server is not licensed for the requesting client type.

System action

Execution of the client enrollment or connection request ends.

User response

See your system administrator.

0068 E DSM_RC_CLIENT_NOT_ARCHRETPROT The session is rejected. The server does not allow a signon of a client that is not archive-retention protection enabled.

Explanation

The client cannot establish a connection to the server because the server is enabled for archive-retention protection enabled and the client is not.

System action

The session is not started.

User response

See your system administrator.

0069 E DSM_RC_SESSION_CANCELED Session Rejected: The session was canceled by the server administrator.

Explanation

The server administrator canceled the current client session.

System action

Execution of the client connection request ends.

User response

See your system administrator.

0073 E DSM_RC_REJECT_INVALID_NODE_TYPE An inconsistency was detected between the client node and
the node that is registered to the IBM Storage Protect server.

Explanation

The user has probably coded the node option incorrectly. For instance, the node that is registered to the IBM Storage Protect server might be a type of NAS, but the node is actually a non-NAS client.

System action

Operation ends.

User response

Ensure that the node name is correct in the client options file. Make sure to use a node of type NAS only with the nasnodename option.

0074 E DSM_RC_REJECT_INVALID_SESSIONINIT Server does not allow client-initiated connections for this node.

Explanation

The node is not allowed to initiate connections due to the configuration parameters for this node on the server. Server is able to initiate connections to the client scheduler running in prompted mode.

System action

The IBM Spectrum Protect operation ends.

User response

Contact your systems administrator to enable client-initiated sessions for your node or update the SESSIONINITIATION option and run the client scheduler.

0075 E DSM_RC_REJECT_WRONG_PORT Wrong server port.

Explanation

You were trying to open a backup/archive client session on the server port set up for administrative sessions only.

System action

The IBM Spectrum Protect operation ends.

User response

Contact your systems administrator and/or use the correct values for TCP port and TCP Admin Port.

0079 E DSM_RC_CLIENT_NOT_SPMRETPROT The session is rejected. The server does not allow a signon of a client that is not enabled for space-management retention-protection.

Explanation

The client cannot establish a connection to the server because the server is enabled for space-management retention-protection and the client is not.

System action

The session is not started.

User response

See your system administrator.

0101 W DSM_RC_USER_ABORT The operation was stopped by the user.

Explanation

The operation was stopped at the request of the user. This usually occurs when the 'Q' key is pressed two times.

System action

Processing stopped.

User response

None.

0102 E DSM_RC_NO_MEMORY file name(line number)The operating system refused a IBM Spectrum Protect request for memory allocation.

Explanation

IBM Spectrum Protect requires access to memory in order to store information as processing proceeds. In this case, more memory was requested than the operating system would allocate. Possible reasons include:
  • The system is low on memory.
  • The process in which the program runs has exceeded the maximum allocated memory.
  • Some other error condition occurred. No memory is available.

System action

IBM Spectrum Protect cannot complete the requested operation.

User response

Close all unneeded applications and try the operation again. If the operation still fails, try dividing the task into several smaller units. For example, if a file specification contains several high-level directories, run the IBM Spectrum Protect task serially for each directory. If the IBM Spectrum Protect task is an incremental backup, use the option "-memoryefficientbackup=yes".

For UNIX systems that support resource limits, you can check if the memory resource limit is too low by entering the following command: ulimit -a

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

0104 E DSM_RC_FILE_NOT_FOUND File not found during Backup, Archive or Migrate processing

Explanation

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

System action

File skipped.

User response

None.

0105 E DSM_RC_PATH_NOT_FOUND The specified directory path 'pathname' could not be found.

Explanation

An invalid or unreachable directory path was specified.

System action

Processing stopped.

User response

Try the operation again using a valid directory path.

0106 E DSM_RC_ACCESS_DENIED Access to the specified file or directory is 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.

0106 E DSM_RC_ACCESS_DENIED The specified file is being used by another process

Explanation

The specified file is being used by another process. You tried to read from or write to a file that is currently being used by another process.

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 E DSM_RC_NO_HANDLES No file handles available

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 modify your system setup to allow for more files to be open at the same time.

0108 E DSM_RC_FILE_EXISTS The file exists and cannot be overwritten.

Explanation

The file being restored or retrieved exists and cannot be overwritten due to lack of authority or access permissions.

System action

The file is skipped.

User response

Verify that you have sufficient access permissions to overwrite the file, then try the operation again. If the problem persists, contact your system administrator or IBM Storage Protect administrator for further assistance.

0109 E DSM_RC_INVALID_PARM 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.

0110 E DSM_RC_INVALID_HANDLE An invalid file handle was passed; system error.

Explanation

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

System action

processing stops.

User response

Try the operation again. If the failure persists, obtain a service trace that captures the problem and contact IBM technical support for additional assistance. Your IBM Storage Protect administrator can help you configure the trace.

0111 E DSM_RC_DISK_FULL Processing stopped; Disk full condition

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 E DSM_RC_PROTOCOL_VIOLATION Protocol violation

Explanation

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

System action

Processing Ends.

User response

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

0114 E DSM_RC_UNKNOWN_ERROR An unknown system error has occurred from which IBM Storage Protect cannot recover.

Explanation

An unknown error occurred. This might be a low-level system or communication error from which IBM Storage Protect cannot recover.

System action

Processing stops.

User response

Try the operation again. If the problem persists, review the IBM Storage Protect error log for any related messages. Obtain a service trace that captures the problem and contact IBM technical support for additional assistance. Your IBM Storage Protect administrator can help you configure the trace.

0115 E DSM_RC_UNEXPECTED_ERROR An unexpected error occurred.

Explanation

This is usually caused by a low-level system error or communication error from which IBM Storage Protect cannot recover.

System action

Processing stopped.

User response

Examine the client error log for any additional messages that might be related to this problem. Try the operation again. If the problem persists, contact IBM Storage Protect technical support for further assistance.

0116 E DSM_RC_FILE_BEING_EXECUTED File is in use; Write permission denied.

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 E DSM_RC_DIR_NO_SPACE 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.

0118 E DSM_RC_LOOPED_SYM_LINK Too many symbolic links were detected while resolving name

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 E DSM_RC_FILE_NAME_TOO_LONG The file name is too long and can not be processed by IBM Storage Protect

Explanation

The size limit for file names may vary by operating system. The most common limit is 256 characters. The file name being processed exceeds the limit supported by IBM Storage Protect on this system.

System action

The file is skipped.

User response

Enter HELP FILE SPEC or see the client manual for the operating system on which you are receiving this error. The "File specification syntax" section of the manual explains file name lengths supported by IBM Storage Protect.

0120 E DSM_RC_FILE_SPACE_LOCKED File system is locked by system

Explanation

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

System action

The operation cannot be completed.

User response

See your system administrator.

0121 I DSM_RC_FINISHED 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.

0122 E DSM_RC_UNKNOWN_FORMAT The file has an unknown format.

Explanation

The process tried to restore or retrieve a file, but it had an unknown format.

System action

The file is skipped.

User response

The file was either backed up by another application, or the data is invalid. If the file belongs to this system, try the operation again. If the problem persists, contact IBM technical support for further assistance.

0123 E DSM_RC_NO_AUTHORIZATION 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.

0124 E DSM_RC_FILE_SPACE_NOT_FOUND File space 'filespace-name' does not exist

Explanation

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

System action

Processing stopped.

User response

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

0125 E DSM_RC_TXN_ABORTED Transaction aborted

Explanation

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

System action

Current operation has been cancelled.

User response

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

0126 E DSM_RC_SUBDIR_AS_FILE IBM Storage Protect cannot build a directory path because a file exists with the same name as
the directory.

Explanation

None

System action

Processing stopped.

User response

Remove or rename the file that has the same name as the directory. Alternatively, you can restore the directory to a different location.

0127 E DSM_RC_PROCESS_NO_SPACE Disk space limit for this process reached

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 E DSM_RC_PATH_TOO_LONG Destination directory path length exceeds system maximum

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 E DSM_RC_NOT_COMPRESSED File is not compressed; System failure.

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 E DSM_RC_TOO_MANY_BITS File compressed on a different client machine that has more memory

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

Current operation has been cancelled.

User response

Obtain a machine with more memory and retry the operation.

0131 S DSM_RC_SYSTEM_ERROR An internal program error occurred.

Explanation

An unexpected condition was encountered and the operation can not continue. This might be a programming error.

System action

processing stops.

User response

Try the operation again. If the problem persists, contact your IBM Storage Protect administrator or IBM technical support for further assistance.

0131 E DSM_RC_COMPRESSED_DATA_CORRUPTED The compressed file is corrupted and cannot be expanded correctly.

Explanation

The compressed file cannot be expanded correctly due to one of the following reasons:
  • There is a problem on the tape.
  • There is a communications problem.
  • The compressed file was corrupted on the IBM Storage Protect Server.

System action

File skipped.

User response

1) The compressed file is corrupted because there is a problem on the tape. To know if this is the problem, please issue the following command on the IBM Storage Protect Server: audit volume <volume_name> fix=no If there is any problem reported, you could move the data from that volume to a new one (see command MOVE DATA) and try again the restore. 2) There are communications problems between the IBM Storage Protect Server and the IBM Storage Protect Client and the results is that the file is corrupted during the transmission. If you use a gigabit Ethernet adapter on the Server please upgrade the card driver (AIX platform) or add provided by SUN suggested changes to some system network options which have resolved this problem (SUN platform). 3) Please verify with your network support if during the restore there are no any problems between the IBM Storage Protect Client/Server that is originating the file corruption.

0132 E DSM_RC_NO_SERVER_RESOURCES The IBM Storage Protect server is out of resources.

Explanation

A lack of a storage resource or a maximum value condition does not allow any new activity.

System action

Current operation has been cancelled.

User response

Try the operation again at a later time. If the problem continues, contact your IBM Storage Protect administrator to isolate what resource is unavailable. The IBM Storage Protect administrator can check the IBM Storage Protect server activity log for messages that might explain the problem.

0133 E DSM_RC_FS_NOT_KNOWN The file space for domain 'domain-name' could not be found on the IBM Storage Protect server.

Explanation

The specified file space was expected to be found on the server, but it no longer exists. It is possible that a command was issued to delete the file space from the server while the current operation was in progress.

System action

IBM Storage Protect processing stops.

User response

Try the operation again. If the problem recurs, check the error log for any other messages that might indicate a reason for the failure. Try to correct any indicated problems, then try the operation again. If the problem persists, contact IBM technical support for further assistance.

0134 E DSM_RC_NO_LEADING_DIRSEP 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.

0135 E DSM_RC_WILDCARD_DIR 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.

0136 E DSM_RC_COMM_PROTOCOL_ERROR The session is rejected: There was a communications protocol error.

Explanation

An unexpected network message was received by the client. This could be caused by network problems or a programming error.

System action

The current operation has been cancelled.

User response

Verify that your communication path is functioning properly and try the operation again. If the problem persists, contact your IBM Storage Protect administrator for further assistance.

0137 E DSM_RC_AUTH_FAILURE Session rejected: Authentication failure

Explanation

Authentication failure. You entered an incorrect user id or password.

System action

Current operation has been cancelled.

User response

Enter your correct user id and password. If you cannot remember the correct user id or password, see your system administrator to have new credentials assigned for your node name.

0138 E DSM_RC_TA_NOT_VALID The dsmtca execution/owner permissions are invalid.

Explanation

The dsmtca 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 dsmtca permissions are set correctly.

0139 S DSM_RC_KILLED 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.

0145 S DSM_RC_WOULD_BLOCK The dsmtca would block the operation.

Explanation

The dsmtca 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 S DSM_RC_TOO_SMALL 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.

0147 S DSM_RC_UNCLOSED 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.

0148 S DSM_RC_NO_STARTING_DELIMITER Include/Exclude pattern must start with a directory 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 S DSM_RC_NEEDED_DIR_DELIMITER A beginning or ending directory delimiter is missing from the Include/Exclude pattern.

Explanation

  1. The include/exclude pattern has a '...' without a beginning or ending directory delimiter.
  2. For Windows, the drive seperator is not immediately followed by a directory delimiter.

System action

Processing stopped.

User response

Correct the syntax for the pattern.

0151 S DSM_RC_BUFFER_OVERFLOW 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.

0154 E DSM_RC_NO_COMPRESS_MEMORY Insufficient memory for file compression/expansion

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 T DSM_RC_COMPRESS_GREW Compressed Data Grew

Explanation

The size of the file after compression is greater than the size of the file before compressed.

System action

Even though the size of the file increased, the file is compressed.

User response

None.

0156 E DSM_RC_INV_COMM_METHOD An unsupported communications method was specified.

Explanation

None.

System action

processing stops.

User response

Specify a communications interface that is supported by the IBM Storage Protect client on your operating system. See the IBM Storage Protect client manual for your operating system for further information on configuring IBM Storage Protect client communications.

0157 S DSM_RC_WILL_ABORT 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.

0158 E DSM_RC_FS_WRITE_LOCKED Destination file or directory is write locked

Explanation

The file or directory 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 I DSM_RC_SKIPPED_BY_USER 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.

0160 E DSM_RC_TA_NOT_FOUND Unable to find the dsmtca module.

Explanation

IBM Storage Protect was unable to find the dsmtca module in the specified directory.

System action

Processing ends.

User response

Make sure the dsmtca module is in the directory specified by DSMI_DIR.

0162 E DSM_RC_FS_NOT_READY File system/drive not ready

Explanation

The file system/drive was not ready for access.

System action

Processing stopped.

User response

Ensure that the drive is available , and then retry the operation.

0164 E DSM_RC_FIO_ERROR File input/output 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.

0165 E DSM_RC_WRITE_FAILURE File write error

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 E DSM_RC_OVER_FILE_SIZE_LIMIT File exceeds system/user file limits

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 E DSM_RC_CANNOT_MAKE Cannot make file/directory

Explanation

The directory path for files 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 E DSM_RC_NO_PASS_FILE Password file is not available.

Explanation

The file containing the stored password for the specified server-name is unavailable.

System action

Processing ends.

User response

The root user must set and store a new password.

0169 E DSM_RC_VERFILE_OLD PASSWORDACCESS is GENERATE, but password needed for server 'server-name'.
Either the password is not stored locally, or it was changed at the server.

Explanation

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

System action

IBM Storage Protect prompts you for the password if IBM Storage Protect is running in the foreground.

User response

If IBM Storage Protect was running as a background process, issue any IBM Storage Protect command from the foreground. Enter the password in answer to the prompt. Then try your background IBM Storage Protect command again.

0173 E DSM_RC_INPUT_ERROR The process is running in a non-interactive mode, but requires user input.

Explanation

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

System action

processing stops.

User response

Perform the following actions to resolve this error:
  • Run the product in interactive mode.
  • Ensure your password is set correctly.

0174 E DSM_RC_REJECT_PLATFORM_MISMATCH Session rejected: Node type mismatch

Explanation

Your node name is associated with a different type of operating system and cannot be used on this system.

System action

Current operation has been cancelled.

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 E DSM_RC_TL_NOT_FILE_OWNER Not file owner

Explanation

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

System action

The file is skipped.

User response

None.

0177 S DSM_RC_UNMATCHED_QUOTE Quotes are not matched

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 E DSM_RC_TL_NOBCG The management class for this file does not have a valid backup copy group.
This file will not be backed up.

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 W DSM_RC_TL_EXCLUDED File 'file-namefile-namefile-name' excluded by Include/Exclude list

Explanation

You can not back up, archive, or migrate files that are excluded.

System action

The file can not be processed.

User response

If the file is intentionally excluded, then this message can be ignored. Otherwise modify the include/exclude list, restart the client, and try the operation again. Contact your IBM Storage Protect administrator for further assistance.

0186 E DSM_RC_TL_NOACG The management class for this file does not have a valid archive copy group.
This file will not be archived.

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 E DSM_RC_PS_INVALID_ARCHMC Invalid management class entered

Explanation

You entered an invalid management class.

System action

Requested operation is not possible.

User response

Retry the operation using a valid management class.

0188 S DSM_RC_NO_PS_DATA Either the node does not exist on the server or there is no active policy set for the node.

Explanation

This error occurs when you try to access another node's data. Either the node is not registered with the IBM Storage Protect server, or there is no active policy set for the node.

System action

Processing stops.

User response

Verify that the node whose data you are trying to access is registered with the IBM Storage Protect server. If you have more than one IBM Storage Protect server, make sure you are connecting to the correct server, then try the operation again. If the problem persists, contact your IBM Storage Protect administrator for further assistance.

0189 S DSM_RC_PS_INVALID_DIRMC The management class assigned to directories does not exist.

Explanation

The management class named on the DIRMC option does not exist in your assigned policy set on the server. The error log contains an entry showing the invalid management class name.

System action

processing stops.

User response

Remove the current DIRMC option from the client options file, then run DSMC QUERY MGMTCLASS -DETAIL to view information about available management classes. Make sure the management class you select has a backup copy group. If you have more than one IBM Storage Protect server, make sure you are connecting to the correct server. If you are unable to find a suitable management class, contact your IBM Storage Protect administrator for further assistance.

0190 S DSM_RC_PS_NO_CG_IN_DIR_MC There is no backup copy group in the management class used for directories.

Explanation

The DIRMC option names a management class that contains no backup copy group.

System action

processing stops.

User response

Remove the current DIRMC option from the client options file, then run DSMC QUERY MGMTCLASS -DETAIL to view information about available management classes. Make sure the management class you select has a backup copy group. If you have more than one IBM Storage Protect server, make sure you are connecting to the correct server. If you are unable to find a suitable management class, contact your IBM Storage Protect administrator for further assistance.

0231 E DSM_RC_ABORT_MOVER_TYPE Unknown Remote Mover type

Explanation

The specified Remote Mover type is unknown.

System action

Current operation has ended.

User response

Contact your system administrator for more information.

0232 E DSM_RC_ABORT_ITEM_IN_USE An Operation for the requested node and file space is already in progress.

Explanation

A request has been made to use a data mover to perform an operation for the indicated node and file space. Since an operation for this node and file space is already in progress, the new operation cannot be performed.

System action

Current operation has ended.

User response

Retry the operation at a later time.

0233 E DSM_RC_ABORT_LOCK_CONFLICT System resource in use

Explanation

A required resource is in use by another command or process.

System action

Current operation has ended.

User response

Retry the operation at a later time.

0234 E DSM_RC_ABORT_SRV_PLUGIN_COMM_ERROR Server plugin communication error

Explanation

Communication between a server plugin module and a NAS filer failed.

System action

Current operation has ended.

User response

Contact your system administrator for more information.

0235 E DSM_RC_ABORT_SRV_PLUGIN_OS_ERROR Server plugin detected unsupported NAS filer operating system.

Explanation

A plugin module detected that a NAS filer is running an unsupported operating system or operating system level.

System action

Current operation has ended.

User response

Contact your system administrator for more information.

0236E DSM_RC_ABORT_CRC_FAILED The CRC received from the Server does not match the CRC calculated by the client.

Explanation

The server sent a CRC for a buffer. The client calculated a CRC for the same buffer. These did not match. The mismatch indicates a communication failure.

System action

In some cases, the client can indicate the failure to the server and retry the operation.

User response

Check the trace log for additional information and retry the operation. If the problem persists, contact your system administrator.

0237E DSM_RC_ABORT_INVALID_GROUP_ACTION An invalid operation was attempted on a group leader or group member.

Explanation

An invalid operation was attempted on a logical group.

System action

The current operation stops.

User response

Retry a valid operation.

0238E DSM_RC_ABORT_DISK_UNDEFINED Remote disk not defined.

Explanation

An operation was attempted on a remote disk that is not defined.

System action

The current operation stops.

User response

Define the proper remote disk.

0239E DSM_RC_ABORT_BAD_DESTINATION Input destination does not match expected destination.

Explanation

Input destination does not match expected destination.

System action

The current operation stops.

User response

Retry operation with proper destination.

0240E DSM_RC_ABORT_DATAMOVER_NOT_AVAILABLE Data mover is not available.

Explanation

Data mover is not available.

System action

The current operation stops.

User response

Retry operation with a proper Data mover.

0241E DSM_RC_ABORT_STGPOOL_COPY_CONT_NO Operation failed because the copy continue option was set to NO.

Explanation

Operation failed because the copy continue option was set to NO.

System action

The current operation stops.

User response

This abort code indicates that a store operation, like backup or archive failed because the copy continue option was set to NO. The sysadmin will need to resolve the problem on the server end.

0242E DSM_RC_ABORT_RETRY_SINGLE_TXN Transaction failed because of a problem during a store operation.

Explanation

Transaction failed because of a problem during a store operation. This error is typical when the next storage pool has a different copy storage pool list and we switch to this pool in the middle of a transaction.

System action

Transaction is aborted.

User response

Resend objects in separate transactions.

0245 E DSM_RC_ABORT_PATH_RESTRICTED The current client configuration does not comply with the value of the DATAWRITEPATH or DATAREADPATH server option for this node.

Explanation

The values of the DATAWRITEPATH and DATAREADPATH server options specify where the client is allowed to send data, and where data is read from. The values for the specified node name should correspond with the client configuration. For example, you will get this error message if DATAWRITEPATH contains a LAN value and the client is configured to use LAN-free protocol, or vice versa.

System action

Processing stopped.

User response

Check the client, server, and storage agent logs to determine why the client was not able to send data LAN-free. Make sure the client configuration and server options are compatible.

0247 E DSM_RC_ABORT_INSERT_NOT_ALLOWED This server does not support backup operations.

Explanation

This server only supports archive operations, backup is not allowed.

System action

The current operation ends.

User response

Use only archive operations with this server.

0248 E DSM_RC_ABORT_DELETE_NOT_ALLOWED Deleting this object: "fshlll" is not allowed.

Explanation

The object is either under a hold and cannot be deleted, or it is on a retention-protection enabled server and has not expired.

System action

The object is skipped and processing continues.

User response

Check the status of the object through a query to see if it is held, or when it expires.

0249 E DSM_RC_ABORT_TXN_LIMIT_EXCEEDED The number of objects in this transaction exceed TXNGROUPMAX values.

Explanation

There are too many objects in this transaction.

System action

The current operation ends.

User response

Try the operation again with fewer objects in the transaction, or increase the TXNGROUPMAX value on the server.

0250 E DSM_RC_ABORT_OBJECT_ALREADY_HELD fshlll is already under hold.

Explanation

One of the objects in the transaction The specified object is already under hold, and it cannot be placed under a new hold.

System action

The current operation ends. This object is skipped and processing continues.

User response

Issue a query to see the status of the objects, and try the operation again, without the object that is already held.

0292 E DSM_RC_TCA_FORK_FAILED Error starting the dsmtca or dsmenc process.

Explanation

An error has occurred starting the dsmtca or dsmenc process; specifically, the fork() function has failed.

System action

Processing ends.

User response

Probable system error. If the problem persists, restart the workstation.

0295 E DSM_RC_TCA_INVALID_REQUEST The IBM Storage Protect dsmtca received an invalid request.

Explanation

The dsmtca or dsmenc process was invoked by the backup-archive client and received an unknown request argument in the call.

System action

Processing ends.

User response

It is possible that the dsmtca or dsmenc process was mistakenly invoked by a process other than the backup-archive client. If that is not the case, then this is an internal error. If the problem recurs, contact your IBM service representative.

0296 E DSM_RC_TCA_NOT_ROOT This action requires IBM Storage Protect administrative authority on this system.

Explanation

An activity has been attempted that must be performed by the IBM Storage Protect administrator (for example, open registration, file space delete or password update).

System action

Processing ends.

User response

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

0297 E DSM_RC_TCA_SEMGET_ERROR Error allocating semaphores.

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 E DSM_RC_TCA_SEM_OP_ERROR Error setting semaphore value or waiting on semaphore.

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 E DSM_RC_INVALID_OPT 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/QOPTIBM Storage Protect(APIOPT).

0405 E DSM_RC_NO_HOST_ADDR TCPSERVERADDRESS not defined for this server in the System Options File

Explanation

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

System action

IBM Storage Protect initialization fails and the program ends.

User response

See the IBM Storage Protect administrator for your system, and make sure that the server to which you are trying to connect, has a valid TCPSERVERADDRESS defined in the system options file.

0406 S DSM_RC_NO_OPT_FILE Options file 'file-name' could not be found, or it cannot be read.

Explanation

Common reasons for this error include:
  • The default options file does not exist.
  • You specified the -OPTFILE option when starting the IBM Spectrum Protect client, but the options file you provided does not exist.
  • The DSM_CONFIG (or DSMI_CONFIG if you are using the IBM Spectrum Protect API) environment variable specifies an options file that does not exist.
  • You specified the -OPTFILE option when starting the IBM Spectrum Protect client, but the options file that you provided is not in the standard file encoding of the system. For example, on Windows the expected file encoding is ANSI.
  • You specified the -OPTFILE option when starting the IBM Spectrum Protect client, but the options file that you provided does not have appropriate read permissions for the user that is running the operation.

System action

IBM Spectrum Protect client processing stops.

User response

Make sure that the options file you want to use exists, it has the read rights set for the user that is running the operation, and it is in the standard file encoding of the system. For example, on Windows the expected file encoding is ANSI. Review the configuration information in the IBM Spectrum Protect client manual specific to your operating system. If the problem persists, ask your IBM Spectrum Protect administrator for further assistance.

0408 E DSM_RC_MACHINE_SAME A virtual node name must not equal either a node name or the system host name.

Explanation

A VIRTUALNODENAME option was entered with a name the same as either a NODENAME option or the system host name.

System action

Initialization fails and the program ends.

User response

If the virtual node name entered was the same as the host name, remove the virtual node name option. If it was the same as the node name option, you can remove either one, depending upon the intended usage. Node name is used to assign an alternate name to your system. Virtual node name is used to access another system's server data.

0409 E DSM_RC_INVALID_SERVER Server name not found in System Options File

Explanation

The system options file does not contain the SERVERNAME option.

System action

IBM Storage Protect initialization fails and the program ends.

User response

See the IBM Storage Protect administrator for your system, and make sure that the system options file contains the server name.

0410 E DSM_RC_INVALID_KEYWORD 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.

0411 S DSM_RC_PATTERN_TOO_COMPLEX The include or exclude pattern cannot be parsed.

Explanation

The pattern is formatted incorrectly or is too complex to be interpreted.

System action

Processing stopped.

User response

Verify that the include or exclude pattern is specified correctly. If the pattern is correct, then contact IBM technical support for further assistance.

0412 S DSM_RC_NO_CLOSING_BRACKET Include/Exclude pattern is missing a 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.

0426 E DSM_RC_CANNOT_OPEN_TRACEFILE Initialization functions cannot open the trace file specified.

Explanation

The file could not be opened during initialization. The specified path might be incorrect. It is also possible that the current user does not have permission to write to the tracefile in the directory specified. It is also possible that no space is available at the tracefile location.

System action

Processing stops.

User response

Make sure the tracefile option points to a valid path and that the user has proper permissions to write to the specified file.

0427 E DSM_RC_CANNOT_OPEN_LOGFILE Initialization functions cannot open the error log file specified.

Explanation

The error log file could not be opened during initialization. The specified path may be incorrect. It is also possible that the current user does not have permission to write to the logfile in the directory specified. It is also possible that no space is available at the given logfile location.

System action

Processing terminates.

User response

Make sure the logfile option points to a valid path and that the user has proper permissions to write to the file specified.

0600 E DSM_RC_DUP_LABEL A duplicate volume label exists. The operation cannot continue.

Explanation

For removable media, IBM Storage Protect uses the volume label as the file space name. To prevent data from different volumes being stored in the same file space on the IBM Storage Protect server, backup or archive of removable media volumes having duplicate volume labels is not allowed.

System action

The requested operation does not run.

User response

Change the volume labels on the removable media volumes so that there are no duplicate labels. Then restart IBM Storage Protect and try the operation again.

0601 E DSM_RC_NO_LABEL The drive has no label. The operation cannot continue.

Explanation

Backup or archive of removable media requires that the media have a volume label. An attempt was made to back up or archive data on a removable volume that has no label.

System action

The requested operation does not run.

User response

Create a volume label on the removable media, then try the operation again.

0610 E DSM_RC_NLS_CANT_OPEN_TXT Unable to open message text file.

Explanation

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

System action

The system returns to the calling procedure.

User response

Verify that the dscenu.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 E DSM_RC_NLS_CANT_READ_HDR Unable to use message text file.

Explanation

The system is unable to use the message text file (dscenu.txt or dsmclientV3.cat for AIX) because of an invalid header. On the AS/400 platform this file is QANSAPI/QAANSENU(TXT).

System action

The system returns to the calling procedure.

User response

Install the message text file again.

0612 E DSM_RC_NLS_INVALID_CNTL_REC Unable to use message text file.

Explanation

The system is unable to use the message txt file (dscenu.txt or dsmclientV3.cat for AIX) because of an invalid control record. On the AS/400 platform this file is QANSAPI/QAANSENU(TXT).

System action

The system returns to the calling procedure.

User response

Install the message text file again.

0613 E DSM_RC_NLS_INVALID_DATE_FMT 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.

0614 E DSM_RC_NLS_INVALID_TIME_FMT 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.

0615 E DSM_RC_NLS_INVALID_NUM_FMT 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.

0620 E DSM_RC_LOG_CANT_BE_OPENED 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.

0621 E DSM_RC_LOG_ERROR_WRITING_TO_LOG 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.

0622 E DSM_RC_LOG_NOT_SPECIFIED 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.

0927 E DSM_RC_NOT_ADSM_AUTHORIZED Only a IBM Storage Protect authorized user can perform this Action.

Explanation

User must be a IBM Storage Protect 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 and the set effective user id bit is set to 'on' ('s' bit).

961 E DSM_RC_DIRECT_STORAGE_AGENT_UNSUPPORTED Direct connection to the Storage Agent is not allowed.

Explanation

You cannot connect directly to the Storage Agent.

System action

Processing stopped.

User response

To perform Lanfree operations using the Storage Agent, specify the ENABLELANFREE option in your options file, and restart the process.

963 E DSM_RC_FS_NAMESPACE_DOWNLEVEL The long namespace has been removed from the local file space. If you wish to proceed with the backup/archive operation, rename your file space on the server.

Explanation

The process has detected that the server namespace is NTW:LONG, but the local volume does not have long name support. If you would like to back up the volume using the short names, rename the file space on the server. If you would like to back up using long names, add the long namespace support back to the volume in question.

System action

Processing stopped.

User response

Add the long namespace support to the volume or rename(remove) the corresponding server file space.

0996 E DSM_RC_SERVER_DOWNLEVEL_FUNC The IBM Storage Protect server is downlevel and does not support the requested function. See error log for version information.

Explanation

The function being used requires a more current IBM Storage Protect Server.

System action

The operation fails.

User response

Upgrade your IBM Storage Protect Server to a level that supports this function. See error log for version information.

0997 E DSM_RC_STORAGEAGENT_DOWNLEVEL The IBM Storage Protect Storage Agent is downlevel and does not support the requested function. See error log for version information.

Explanation

The function being used requires a more current IBM Storage Protect Storage Agent.

System action

The operation fails.

User response

Upgrade your IBM Storage Protect Storage Agent to a level that supports this function. See error log for version information.

0998 E DSM_RC_SERVER_AND_SA_DOWNLEVEL The IBM Storage Protect Server and IBM Storage Protect Storage agent are downlevel and do not support the requested function. See error log for version information.

Explanation

The function being used requires a more current IBM Storage Protect Server and IBM Storage Protect Storage agent

System action

The operation fails.

User response

Upgrade your IBM Storage Protect Server and IBM Storage Protect Storage agent to a level that supports this function. See error log for version information.

2000 E DSM_RC_NULL_OBJNAME 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.

2001 E DSM_RC_NULL_DATABLKPTR 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.

2002 E DSM_RC_NULL_MSG 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.

2004 E DSM_RC_NULL_OBJATTRPTR 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.

2006 E DSM_RC_NO_SESS_BLK 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.

2007 E DSM_RC_NO_POLICY_BLK 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.

2008 E DSM_RC_ZERO_BUFLEN 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.

2009 E DSM_RC_NULL_BUFPTR 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.

2010 E DSM_RC_INVALID_OBJTYPE 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.

2011 E DSM_RC_INVALID_VOTE 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.

2012 E DSM_RC_INVALID_ACTION 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.

2014 E DSM_RC_INVALID_DS_HANDLE There was an error in the IBM Storage Protect 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.

2015 E DSM_RC_INVALID_REPOS 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:
  • DSM_ARCHIVE_REP
  • DSM_BACKUP_REP
  • DSM_REPOS_ALL.

2016 E DSM_RC_INVALID_FSNAME 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.

2017 E DSM_RC_INVALID_OBJNAME 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.

2018 E DSM_RC_INVALID_LLNAME 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.

2019 E DSM_RC_INVALID_OBJOWNER 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.

2020 E DSM_RC_INVALID_ACTYPE 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

2021 E DSM_RC_INVALID_RETCODE 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.

2022 E DSM_RC_INVALID_SENDTYPE 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

2023 E DSM_RC_INVALID_PARAMETER 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.

2024 E DSM_RC_INVALID_OBJSTATE 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

2025 E DSM_RC_INVALID_MCNAME 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.

2026 E DSM_RC_INVALID_DRIVE_CHAR 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 only.

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.

2027 E DSM_RC_NULL_FSNAME 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.

2028 E DSM_RC_INVALID_HLNAME 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.

2029 E DSM_RC_NUMOBJ_EXCEED 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.

2030 E DSM_RC_NEWPW_REQD 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.

2031 E DSM_RC_OLDPW_REQD 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.

2032 E DSM_RC_NO_OWNER_REQD On dsmInit, the owner is not allowed to establish a session when PASSWORDACCESS=generate.

Explanation

PASSWORDACCESS=GENERATE establishes a session with the current login user as the owner. The application should set clientOwnerNameP to NULL when PASSWORDACCESS=GENERATE is in effect.

System action

The system returns to the calling procedure. Whether the application can continue processing depends on how the application handles the error.

User response

This message applies to applications that utilize the IBM Storage Protect API, and is intended primarily for the vendor of the application for which the message is issued. Depending on the application, this could be a configuration issue.

Consult the documentation for the application and verify that the application is configured correctly. If the problem persists, contact the application vendor for further assistance.

2033 E DSM_RC_NO_NODE_REQD 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 clientNodeNameP to NULL.

2034 E DSM_RC_KEY_MISSING The key file is missing.

Explanation

The key file for Data Protection for Oracle cannot be found.

System action

The system returns to the calling procedure.

User response

Ensure that you have ordered the Data Protection for Oracle, and install the key file.

2035 E DSM_RC_KEY_BAD The key file content is invalid.

Explanation

The key file content for Data Protection for Oracle is invalid.

System action

The system returns to the calling procedure.

User response

Ensure that you have ordered the Data Protection for Oracle, and install the key file.

2041 E DSM_RC_BAD_CALL_SEQUENCE The sequence of calls is invalid.

Explanation

Then API requires function calls to be made in a specific sequence. The function calls were not made in the expected sequence. The error can be triggered by the following issues:
  • An error in the network.
  • A bug in the IBM Storage Protect API.
  • A bug in the IBM Storage Protect server.
  • A bug in the application (IBM or third party) that uses the IBM Storage Protect API.

System action

The system returns to the calling procedure.

User response

An end user can respond in the following ways:
  • Check the network for errors.
  • Look for clues in the IBM Storage Protect server activity log file, client side dsierror.log log file, and log files that are specific to the problem application.
  • Search the IBM support pages for APARs that match the problem. The support site is at IBM Spectrum Protect Support Portal
  • If the API application is developed by a third party (not IBM), search that third party's support pages for known issues that match the problem.

If none of the above actions resolve the problem, report the problem to the vendor of the application that uses the IBM Storage Protect API.

A developer of an application that uses the IBM Storage Protect API must investigate the reason for the problem, including reviewing the IBM Storage Protect API state diagram. The IBM Storage Protect API state diagram is in the product documentation at IBM Spectrum Protect product documentation

2042 E DSM_RC_INVALID_TSMBUFFER The tsmBuffHandle is invalid, or the value of dataPtr is invalid.

Explanation

An invalid value for a handle or dataPtr has been passed into the API.

System action

The system returns to the calling procedure.

User response

There is a problem with the calling application. Verify the values of the tsmBuffHandle and dataptr passed to the API.

2043 E DSM_RC_TOO_MANY_BYTES The number of bytes copied into the tsmBuffer is larger than the allowed value.

Explanation

An invalid number of bytes was copied to a tsmBuffer.

System action

The system returns to the calling procedure.

User response

There is a problem with the calling application. Verify the number of bytes copied into the tsmBuffer.

2044 E DSM_RC_MUST_RELEASE_BUFFER dsmTerminate cannot finish because the application is holding on to 1 or more tsmBuffers.

Explanation

An application is trying to terminate a session, but is still holding some tsmBuffers.

System action

The system returns to the calling procedure.

User response

The application must return all buffers for this session by calling tsmReleaseBuffer, and then issue dsmTerminate.

2045 E DSM_RC_BUFF_ARRAY_ERROR An internal error occurred in the tsmBuffer array.

Explanation

An internal API buffer array error occurred.

System action

The system returns to the calling procedure.

User response

Try the operation again. If the problem continues, contact your system administrator or service representative.

2046 E DSM_RC_INVALID_DATABLK When using useTsmBuffers, dataBlk must be NULL in calls to dsmSendObj and dsmGetObj.

Explanation

The value for dataBlk must be NULL when using useTsmBuffers.

System action

The system returns to the calling procedure.

User response

There is a problem with the calling application. Contact your application provider

2047 E DSM_RC_ENCR_NOT_ALLOWED Encryption is not allowed when using useTsmBuffers.

Explanation

useTsmBuffers does not support encryption.

System action

The system returns to the calling procedure.

User response

Try the operation again, without using useTsmBuffers, or disable encryption for this operation.

2048 E DSM_RC_OBJ_COMPRESSED This object cannot be restored/retrieved using useTsmBuffers, because it is compressed.

Explanation

useTsmBuffers does not support compression.

System action

The system returns to the calling procedure.

User response

Try the operation again, without using useTsmBuffers.

2049 E DSM_RC_OBJ_ENCRYPTED This object cannot be restored/retrieved using useTsmBuffers, because it is encrypted.

Explanation

useTsmBuffers does not support encryption.

System action

The system returns to the calling procedure.

User response

Try the operation again, without using useTsmBuffers.

2050 E DSM_RC_WILDCHAR_NOTALLOWED 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.

2051 E DSM_RC_POR_NOT_ALLOWED When using useTsmBuffers, a restore/retrieve with partial object restore is not allowed.

Explanation

useTsmBuffers does not support partial object restore.

System action

The system returns to the calling procedure.

User response

Make sure the calling application is either using Partial object restore or useTsmBuffers.

2052 E DSM_RC_NO_ENCRYPTION_KEY No encryption key was found. If you are using -encryptkey=prompt make sure there is a value in the encryptionPasswordP field and that bEncryptKeyEnabled is set to true.

Explanation

There was no encryption key found in the password file, or no key was provided by the application.

System action

The system returns to the calling procedure.

User response

If you are using -encryptkey=prompt, make sure there is a value in encryptionPasswordP and that bEncryptKeyEnabled is set to true.

2053 E DSM_RC_ENCR_CONFLICT Conflicting encryption key options have been specified.

Explanation

When using the ENABLEENCRYPTKEY option, the parameter bEncryptKeyEnabled for the IBM Storage Protect API dsmInitExIn_t and tsmInitExIn_t structures cannot be set to bTrue.

System action

The system returns to the calling procedure.

User response

Either remove the ENABLEENCRYPTKEY option from the options file, or set the parameter bEncryptKeyEnabled to bFalse in the program using the IBM Storage Protect API.

2060 E DSM_RC_FSNAME_NOTFOUND 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.

2061 E DSM_RC_FS_NOT_REGISTERED 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.

2062 W DSM_RC_FS_ALREADY_REGED 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.

2063 E DSM_RC_OBJID_NOTFOUND 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.

2064 E DSM_RC_WRONG_VERSION On dsmInit, the caller API version is different than the IBM Storage Protect library version.

Explanation

On dsmInit, the caller API version is later than the IBM Storage Protect library version.

System action

The system returns to the calling procedure.

User response

Install the latest IBM Storage Protect API library.

2065 E DSM_RC_WRONG_VERSION_PARM The caller's structure version is different than the IBM Storage Protect library version.

Explanation

The caller's structure version is different than the IBM Storage Protect 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 E DSM_RC_NEEDTO_ENDTXN 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.

2080 E DSM_RC_OBJ_EXCLUDED 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.

2081 E DSM_RC_OBJ_NOBCG 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.

2082 E DSM_RC_OBJ_NOACG 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.

2090 E DSM_RC_APISYSTEM_ERROR Memory used by the IBM Storage Protect API has been corrupted.

Explanation

Memory used by the IBM Storage Protect 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.

2100 E DSM_RC_DESC_TOOLONG 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.

2101 E DSM_RC_OBJINFO_TOOLONG 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.

2102 E DSM_RC_HL_TOOLONG 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.

2103 E DSM_RC_PASSWD_TOOLONG The password, or encryptionPassword string provided is too long.

Explanation

The value provided for password or encryptionPassword is too long.

System action

The system returns to the calling procedure.

User response

The password or encrypionPassword field must be less than DSM_MAX_VERIFIER_LENGTH.

2104 E DSM_RC_FILESPACE_TOOLONG 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.

2105 E DSM_RC_LL_TOOLONG 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.

2106 E DSM_RC_FSINFO_TOOLONG 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.

2107 E DSM_RC_SENDDATA_WITH_ZERO_SIZE Cannot Send data with a zero byte sizeEstimate.

Explanation

You cannot send data for an object with size estimate = 0.

System action

The system returns to the calling procedure.

User response

Set size estimate greater than 0 in dsmSendObj.

2110 E DSM_RC_INVALID_ACCESS_TYPE 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

2111 E DSM_RC_QUERY_COMM_FAILURE Communications error with server during object query

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 E DSM_RC_NO_FILES_BACKUP 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.

2113 E DSM_RC_NO_FILES_ARCHIVE 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.

2114 E DSM_RC_INVALID_SETACCESS Invalid format for Set Access command.

Explanation

The SET ACCESS command must have at least three operands, the first of which must be either BACKUP or ARCHIVE. A validly formed file specification must follow.

System action

Processing stopped, the command is not executed.

User response

Use the HELP SET ACCESS command for complete details of usage, then enter the SET ACCESS command using the correct syntax.

2120 E DSM_RC_STRING_TOO_LONG The following message was too long to log to the server: 'shortened message with message number'

Explanation

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

System action

The message number message is written to the local client error log, then shortened and sent to the server as a part of this message. The message is reduced in length by substituting '...' in the middle of the original message.

User response

The message referred to has been shortened, but describes the error that occurred. See the documentation for that message for more information.

2200 I DSM_RC_MORE_DATA 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.

2210 E DSM_RC_BUFF_TOO_SMALL 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.

2228 E DSM_RC_NO_API_CONFIGFILE 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.

2229 E DSM_RC_NO_INCLEXCL_FILE 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.

2230 E DSM_RC_NO_SYS_OR_INCLEXCL 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.

2231 E DSM_RC_REJECT_NO_POR_SUPPORT Partial Object Retrieve is not supported on this server.

Explanation

The IBM Storage Protect server specified by the user does not support partial object retrieve.

System action

The system returns to the calling procedure.

User response

Specify a IBM Storage Protect server which supports the partial object retrieve function.

2300 E DSM_RC_NEED_ROOT 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.

2301 E DSM_RC_NEEDTO_CALL_BINDMC 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.

2302 I DSM_RC_CHECK_REASON_CODE 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.

2400 E DSM_RC_ALMGR_OPEN_FAIL 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.

2401 E DSM_RC_ALMGR_READ_FAIL 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.

2402 E DSM_RC_ALMGR_WRITE_FAIL 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.

2403 E DSM_RC__ALMGR_DATA_FMT 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.

2404 E DSM_RC_ALMGR_CKSUM_BAD 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.

2405 E DSM_RC_ALMGR_TRIAL_EXPRD 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.

4580 E DSM_RC_ENC_WRONG_KEY Error processing 'filespace namepath-namefile-name'; invalid encryption key.

Explanation

The key you entered does not match the key that was used to encrypt the file during backup. The file can not be restored unless the matching key is entered.

System action

processing stops.

User response

Try the restore operation again and provide the correct key.

4582 E DSM_RC_ENC_NOT_AUTHORIZED User is not authorized to encrypt file-space namedirectory_pathfile_name.

Explanation

The user is not authorized to encrypt the file. Normally, only a IBM Spectrum Protect authorized user or a root user can use IBM Spectrum Protect encryption. However, a certain combination of PASSWORDACCESS and ENCRYPTKEY options may allow encryption operations by a non-authorized user.

System action

The file is not backed up or restored.

User response

Log in as a root or IBM Spectrum Protect authorized user and try the operation again. See IBM Spectrum Protect Backup-Archive Client Installation and User's Guide for the correct usage of the ENCRYPTKEY option.

4584 E DSM_RC_ENC_TYPE_UNKOWN Error processing 'filespace namepath-namefile-name': unsupported encryption type.

Explanation

The files you are trying to restore or retrieve have been backed up or archived by a later version of the IBM Storage Protect client. The file encryption method is not supported by the current client.

System action

Object skipped.

User response

Restore or retrieve the file with the most recent version of the IBM Storage Protect client.

4600 E DSM_RC_CLUSTER_INFO_LIBRARY_NOT_LOADED CLUSTERNODE is set to YES but the Cluster Information Daemon is not
started.

Explanation

The HACMP Cluster Information Daemon must be started in order to specify the CLUSTERNODE option.

System action

Processing ends.

User response

Start the HACMP Cluster Information Dameon.

4601 E DSM_RC_CLUSTER_LIBRARY_INVALID CLUSTERNODE is set to YES but the cluster load library is not valid.

Explanation

The load library that the operating system provides to obtain the cluster name is not valid. A possible cause is an out-of-date load library which does not contain the proper routines this product expects.

System action

Processing ends.

User response

Ensure that the latest cluster software is installed on the system.

4602 E DSM_RC_CLUSTER_LIBRARY_NOT_LOADED CLUSTERNODE is set to YES but the cluster software is not available
on this system.

Explanation

The load library that the operating systems provides to obtain the cluster name is not available on this system.

System action

Processing ends.

User response

Ensure that the cluster software is installed on the system.

4603 E DSM_RC_CLUSTER_NOT_MEMBER_OF_CLUSTER CLUSTERNODE is set to YES but this machine is not a member of a
cluster.

Explanation

This machine is not a member of a cluster node. Possible causes are that the cluster service has not been configured correctly, or that the cluster is in the process of initialization.

System action

Processing ends.

User response

Ensure that the cluster software is configured properly. If the cluster is in the process of initialization, retry the operation at a later time.

4604 E DSM_RC_CLUSTER_NOT_ENABLED CLUSTERNODE is set to YES but the cluster service is not enabled
on this system.

Explanation

The cluster service has not been enabled on this system.

System action

Processing ends.

User response

Enable the cluster service on the system.

4605 E DSM_RC_CLUSTER_NOT_SUPPORTED The CLUSTERNODE option is not supported on this system.

Explanation

This option is not supported on this system.

System action

Processing ends.

User response

Disable the CLUSTERNODE option in the local options file.

4606 E DSM_RC_CLUSTER_UNKNOWN_ERROR An unexpected error (retcode) occurred while the program was trying to obtain the cluster name from the system.

Explanation

An unknown error occurred while the program was trying to obtain the cluster name from the cluster service. The error code is the reason code provided directly from the cluster service being used in this operating system environment.

System action

Processing ends.

User response

Consult the documentation for your clustering software for an explanation of the reason code. Insure that your clustering service is operational, then try the IBM Storage Protect operation again.

5200 E DSM_RC_ABORT_CERTIFICATE_NOT_FOUND The remote node is not properly configured on the IBM Spectrum Protect server.

Explanation

The remote node is not properly configured on the IBM Spectrum Protect server.

System action

Processing stopped.

User response

Ensure that the remote node is properly configured and connected to the IBM Spectrum Protect server by using TLS. This validates the remote node configuration and ensures that the information that is related to the remote node is sent to the server.

5702 E DSM_RC_PROXY_REJECT_NO_RESOURCES Proxy Rejected: The IBM Storage Protect server has run out of memory.

Explanation

There is not enough memory available to allow this operation to continue.

System action

Current operation has been cancelled.

User response

Try the operation again. If the problem continues, see your system administrator to increase the amount of memory of the server.

5705 E DSM_RC_PROXY_REJECT_DUPLICATE_ID Proxy Rejected: The ASNODENAME and NODENAME options have the same value.

Explanation

The ASNODENAME and NODENAME options cannot have the same value.

System action

The current operation is cancelled.

User response

Use the ASNODENAME option only to access another node. It is not necessary to set the ASNODENAME option to access your own node. Remove the ASNODENAME option from your option file unless you are actually trying to access a node that you have been granted authority to access with the administrative command "Grant Proxynode".

5710 E DSM_RC_PROXY_REJECT_ID_IN_USE Proxy Rejected: The node name you specified in the ASNODENAME option is locked.

Explanation

The IBM Storage Protect administrator has locked the node you specified as the ASNODENAME option.

System action

The IBM Storage Protect operation ends.

User response

The IBM Storage Protect server administrator must unlock the node before you can access it. Try the operation later, or check with your IBM Storage Protect administrator.

5717 E DSM_RC_PROXY_REJECT_INTERNAL_ERROR Proxy Rejected: The server has an internal error.

Explanation

The client cannot proxy to the node named by the ASNODENAME option because of an internal server error.

System action

Current operation has been cancelled.

User response

See your system administrator immediately.

5722 E DSM_RC_PROXY_REJECT_NOT_AUTHORIZED Proxy Rejected: Proxy authority has not been granted to this node.

Explanation

The node has not been granted proxy authority to access the node named by the ASNODENAME option. The IBM Storage Protect administrator must first grant proxy authority.

System action

The IBM Storage Protect operation ends.

User response

The IBM Storage Protect server administrator must grant proxy authority for this node. See the administrator command "Grant Proxynode".

5746 E DSM_RC_PROXY_INVALID_FROMNODE The ASNODENAME option is not valid with the FROMNODE option.

Explanation

None.

System action

Processing stops.

User response

Remove the ASNODENAME option from the options file or do not use the FROMNODE option.

5748 E DSM_RC_PROXY_INVALID_CLUSTER The ASNODENAME option cannot be used with the CLUSTERNODE option.

Explanation

None.

System action

Processing stops.

User response

Remove the ASNODENAME option and retry the operation.

5749 E DSM_RC_PROXY_INVALID_FUNCTION The operation that is being attempted cannot be invoked using the ASNODENAME option.

Explanation

None.

System action

Processing stops.

User response

Remove the ASNODENAME option and retry the operation.

5801 E DSM_RC_CRYPTO_ICC_ERROR Unexpected error in cryptography library.

Explanation

There was an unexpected error in the cryptography library. See the error log for more information.

System action

processing stops.

User response

Check the error log for ANS1467E to determine the cause of failure. Verify you IBM Storage Protect client is installed properly. If needed, reinstall client and/or API. If the problem still exists, contact IBM Storage Protect technical support.

5802 S DSM_RC_CRYPTO_ICC_CANNOT_LOAD Cannot load ICC encryption library.

Explanation

The process is using a cryptography library which is installed automatically with the client and is being loaded at runtime. The client cannot proceed if the library is not loaded.

System action

Client exits.

User response

Check the error log for ANS1467E to determine the cause of failure. Verify your IBM Storage Protect client is installed properly. If needed, reinstall the client and/or API. If the problem still exists, contact IBM Storage Protect technical support.

6300 E DSM_RC_DIGEST_VALIDATION_ERROR Error processing 'filespace name path-namefile-name'; end-to-end digest validation failed.

Explanation

Cryptographic digest of the restored or retrieved data did not match the digest generated during the backup or archive operation. Possible causes are a transmission error, data corruption, or a hash collision.

System action

Processing stops

User response

Try the restore operation again. If the problem persists, contact IBM technical support for additional assistance.

6301 E DSM_RC_DATA_FINGERPRINT_ERROR Unexpected error while fingeprinting the data

Explanation

There was an error while fingerprinting the data. See the error log for more information.

System action

The object is not backed up.

User response

Retry the operation. Retry the operation without client-side deduplication. If the problem persists, contact IBM Storage Protect technical support.

6302 E DSM_RC_DATA_DEDUP_ERROR Unexpected error while deduplicating the data

Explanation

There was an error while deduplicating the data. See the error log for more information.

System action

The object is not backed up.

User response

Retry the operation. Retry the operation without client-side deduplication. If the problem persists, contact IBM Storage Protect technical support.