Messages


Chapter 7. Client Common Messages (1000-1999)



ANS1000E Attempting to use a communications method that is not supported

Explanation: You specified a communication method that is not supported.
System Action: Processing stopped.
User Response: Specify a valid communication interface for the TSM client and your operating system.



ANS1001EVolume being backed up was not a system volume. Skipped.

Explanation: User specified to back up system volume only. This volume was not backed up since this volume is not a system volume.
System Action: Volume was not backed up.
User Response: Use All option or use image backup command to backup this volume.



ANS1002IMOS image is being created. It may take a while.

Explanation: Mini Operating System image is beging created. It may take a while to create it.
System Action: TSM is gathering necessary information.
User Response: None.



ANS1003WYou are trying to compress the data for this backup. If the data is compressed, file by file restore will not be performed. Do you wish to continue?

Explanation: User is trying to compress the data for this backup. If the data is compressed, file by file restore will not be performed during restore. Only image restore will be performed.
System Action: If user's response is yes, the data will be compressed, otherwise operation will be aborted.
User Response: Enter either Yes or No.



ANS1009ESession rejected: Specified gateway name gateway cannot be connected to. See your system administrator.

Explanation: Cannot connect to specified gateway.
System Action: Communications link is not established.
User Response: See your system administrator on status of the LAN.



ANS1010E Session rejected: NETBIOS session not established.

Explanation: The client cannot access the NETBIOS server.
System Action: Session is not established.
User Response: Ensure that NETBIOS is loaded and that the NETBIOS server is active. See your system administrator on status of the LAN.



ANS1011E Session rejected: The OS/2 LAN file ACSNETB.DLL is not available or is invalid.

Explanation: The OS/2 LAN file ACSNETB.DLL is not available to establish a communications link, or the file is incorrect.
System Action: Communications link is not established.
User Response: See your system administrator.



ANS1012ESession rejected: Communication session was unexpectedly ended

Explanation: The communication session ended unexpectedly.
System Action: Communications link is not established.
User Response: See your system administrator.



ANS1013ESession rejected: Error accessing the LAN. See your system administrator.

Explanation: Error accessing the LAN.
System Action: Communications link is not established.
User Response: See your system administrator.



ANS1014E Session rejected: LAN failure while in session with server

Explanation: LAN communications failure detected while in session with server.
System Action: Communications link is not established.
User Response: See your system administrator.



ANS1015ESession rejected: LAN resources are exhausted for your system. See your system administrator.

Explanation: LAN resources are exhausted for your system and the session was rejected.
System Action: Communications link is not established.
User Response: See your system administrator.



ANS1016ESession rejected: Unexpected LAN error. Unknown cause. See your system administrator.

Explanation: An unexpected LAN error occurred.
System Action: Communications link is not established.
User Response: These errors may be caused by a failure on the LAN external to TSM. See your system administrator to ensure that your LAN is operating properly.



ANS1017E Session rejected: TCP/IP connection failure

Explanation: An attempt to connect to the server using TCP/IP communications failed. This error can occur if the LAN connection went down or if your system administrator canceled a backup operation.
System Action: 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.



ANS1018E Session rejected: NETBIOS name error

Explanation: An attempt to add the client NETBIOS name failed, or an attempt to call the server NETBIOS name failed.
System Action: Processing stopped.
User Response: Verify that your NETBIOSNAME option value is unique. Verify that your NETBIOSSERVERNAME option value is correct. Verify that the server has NETBIOS support running. If the problem continues, see your system administrator for further help.



ANS1019E Session rejected: NETBIOS timeout

Explanation: A timeout occurred when transmitting data with the NETBIOS protocol.
System Action: Processing stopped.
User Response: Make sure the server is operational. You may need to increase the NETBIOSTIMEOUT value or use a value of 0 for no timeout. If the problem continues, see your system administrator for further help.



ANS1020E Session rejected: NETBIOS not installed

Explanation: The product for NETBIOS is not installed.
System Action: Processing stopped.
User Response: Verify that the product for NETBIOS, such as the LAN Support Program, is installed. If the problem continues, see your system administrator for further help.



ANS1021E NETBIOS configuration error: Reboot the machine.

Explanation: A DOS or Windows NETBIOS error has occurred which requires that the adapter be reset. This may be caused by a software installation or adapter configuration error.
System Action: Processing stopped.
User Response: Reboot the machine. If the error recurs, check the TSM error log to find the NETBIOS return code. See your system administrator for help with your NETBIOS installation/configuration problem.



ANS1022ECannot start application specified on the BOOKS option.

Explanation: Could not start the application specified on the BOOKS option.
System Action: Processing continues.
User Response: Correct the option and restart the program.



ANS1023E Session rejected: Node type mismatch

Explanation: Your node name is associated with a different type of operating system (such as OS/2 or AIX) and cannot be used on this system.
System Action: TSM canceled the current operation.
User Response: If you need a new node name, see your system administrator to assign a new one to you. Generally, you have a unique node name for each machine and operating system pair that requires access to the server.



ANS1024ESession rejected: Unable to locate required file WSOCK32.DLL

Explanation: The 32-Bit Windows Sockets DLL WSOCK32.DLL could not be located
System Action: Communications link is not established. Session rejected.
User Response: See your system administrator.



ANS1025E Session rejected: Authentication failure

Explanation: Authentication failure. You entered an incorrect password.
System Action: TSM canceled the current operation.
User Response: Enter your correct password. If you cannot remember the correct password, see your system administrator to have a new one assigned for your node name.



ANS1026E Session rejected: Communications protocol error

Explanation: Communications protocol error. An unexpected communications message was received by the client.
System Action: TSM canceled the current operation.
User Response: Verify that your communication path is functioning properly. If the problem continues, have your service representative check for a possible program error.



ANS1027ESession failure: Server not available

Explanation: The server cannot be accessed at this time.
System Action: TSM canceled the current operation.
User Response: Retry the operation later. If the server continues to be unavailable, see your system administrator to see if the server is operating properly. If the server is operating properly, you might have your TSM client incorrectly installed or some parameter in your communication path might have been modified.



ANS1028S Internal program error. Please see your service representative.

Explanation: An unexpected program failure occurred.
System Action: Processing stopped.
User Response: Retry the operation. If the problem continues, see your system administrator or your service representative.



ANS1029ECommunications have been dropped.

Explanation: Communications with the server dropped.
System Action: Processing stopped.
User Response: Restart the TSM client and retry the operation.



ANS1030ESystem ran out of memory. Process ended.

Explanation: TSM cannot allocate storage for the specified operation.
System Action: TSM cannot complete the requested operation.
User Response: Stop TSM, restart TSM, and retry the operation. If unsuccessful, close all unneeded applications and retry the operation. 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 resource limits so that it will override the current default. The UNIX system root user has the authority to increase resource limits.



ANS1031E Establishment of a TCP/IP connection timed out before connection was made

Explanation: The attempt to establish a TCP/IP connection timed out before the connection was made.
System Action: Processing stopped.
User Response: Check for a networking problem. If the problem continues, see your system administrator. API applications should close the session with dsmTerminate.



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



ANS1033E An invalid TCP/IP host name was specified

Explanation: An invalid TCP/IP host name or address was specified.
System Action: Processing stopped.
User Response: Check your options file for the correct TCPSERVERADDRESS statement. See your administrator for the correct name of the server.



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



ANS1035S Options file 'file-name' not found

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



ANS1036SInvalid option 'option' found in options file 'file-name' at line number : number

Invalid entry : 'entry'


Explanation: The specified option in the TSM options file (file-name) is in error.
System Action: Processing stopped.
User Response: Correct the options file entry.



ANS1037SInvalid keyword specified

Explanation: TSM found an incorrect keyword in the options file.
System Action: Processing stopped.
User Response: Correct the options file with valid entries.



ANS1038SInvalid option specified

Explanation: An incorrect option was specified to TSM.
System Action: Processing stopped.
User Response: Correct the options used for running TSM.



ANS1039S Include/Exclude pattern too complex

Explanation: The include or exclude pattern issued is too complex to be accurately interpreted by TSM.
System Action: Processing stopped.
User Response: Recode the include or exclude pattern as shown in one of the examples in the appropriate Using the Backup-Archive Client book for the particular operating system.



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



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



ANS1042S Include/Exclude pattern has a '...' without beginning/ending directory delimiter

Explanation: The include/exclude pattern has a '...' without a beginning or ending directory delimiter.
System Action: Processing stopped.
User Response: Correct the syntax for the pattern.



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



ANS1044SUnresolved environment name 'environment-name'.This filespace is being ignored. Processing Continues.

Explanation: The specified environment-name in the options file is invalid.
System Action: TSM attempts to continue the current operation.
User Response: Check the environment variable in the options file and use a valid environment variable. Retry the operation.



ANS1045SEnvironment variable syntax error.

Explanation: Incorrect syntax is specified in the options file. Make sure that the variable is enclosed in curly braces.
System Action: TSM attempts to continue the current operation.
User Response: Check the syntax of environment variable in the options file. Correct it and retry the operation.



ANS1046SEnvironment string for variable 'environment-name' too long. Anything beyond 1024 characters is being ignored

Explanation: Environment variable expanded to a string which is too long. Make sure that the string is no more than 1023 characters long.
System Action: TSM attempts to continue the current operation.
User Response: Check the length of environment string and break it up into smaller strings using multiple environment variables.



ANS1047EEstablishment of an IPX/SPX connection timed out before the connection was made.

Explanation: The attempt to establish an IPX/SPX connection timed out before the connection was made.
System Action: Processing stopped.
User Response: Check for an IPX/SPX networking problem. Ensure that the server is fully initialized, is currently running, and is enabled for IPX/SPX communications. Verify that the server address is correct in the IPXSERVERADDRESS statement in the options file. If the problem continues, see your system administrator.



ANS1048EAn attempt to establish an IPX/SPX connection was refused.

Explanation: An attempt to establish an IPX/SPX 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 IPX/SPX communications, or an incorrect IPX/SPX port number was specified. Verify that th IPX/SPX port number is correct in the IPXSOCKET statement in the options file. If the problem continues, see your system administrator.



ANS1049EThe specified IPX/SPX server address is unreachable.

Explanation: The IPX/SPX host name specified in the IPXSERVERADDRESS statement cannot be reached.
System Action: Processing stopped.
User Response: Check your options file for the correct IPXSERVERADDRESS statement. See your administrator for the correct name of the server.



ANS1050S DBCS Characters are not allowed in an Include/Exclude range

Explanation: Only single-byte characters are allowed in an include/exclude list; you cannot use a double-byte character set (DBCS).
System Action: Processing stopped.
User Response: Remove the double-byte characters from the include/exclude list and retry the operation.



ANS1051EInvalid password

Explanation: You entered an invalid password.
System Action: TSM cannot connect to the server without the correct password.
User Response: Enter the password, or ask your system administrator for the correct password.



ANS1052EA beginning delimiter (begin-delimiter) was not matched by the corresponding ending delimiter (end-delimiter)

Explanation: The beginning delimiter must be paired with the required ending delimiter to make a valid argument.
System Action: The process is stopped.
User Response: Correct the input and re-submit.



ANS1058ERestore destination is unreachable.

Explanation: Trying to restore to destination that cannot be reached. Either the drive letter is not valid, or you are specifying a local share name that cannot be resolved.
System Action: Processing stopped.
User Response: Retry the command and specify a different destination.



ANS1063EInvalid path specification

Explanation: The path specified is not a valid file-system or logical volume name.
System Action: The requested logical volume operation is not performed.
User Response: Retry the operation, using a valid path.



ANS1064EInternal error

Explanation: An error occurred in the image utility internals.
System Action: The requested logical volume operation is not performed.
User Response: Contact your TSM administrator.



ANS1065ELibrary version of the image utility does not match that of the TSM API

Explanation: The current system has a mix of installed components.
System Action: The requested logical volume operation is not performed.
User Response: Re-install all TSM components



ANS1066ERestore successful. File system mount failed.

Explanation: The file system was successfully restored, but the attempt to re-mount it failed.
System Action: The file system is left unmounted.
User Response: Use the mount command to mount the file system. On AIX, run fsck if requested by the operating system.



ANS1067EError in system call, check log file for more information

Explanation: An error occurred during a system call, check the error log for more information.
System Action: The requested logical volume operation is not performed.
User Response: Check error log.



ANS1068EDevice is not local

Explanation: The selected path is not a local device and therefore is not a valid object for image operations
System Action: The requested logical volume operation is not performed.
User Response: Choose another object.



ANS1069EAn error occurred while reading data from the device

Explanation: An error occurred while reading data from the device.
System Action: The requested logical volume operation is not performed.
User Response: Re-try the operation, check error log for more information.



ANS1070EWrite error

Explanation: An error occurred while writing data to the device.
System Action: The requested logical volume operation is not performed.
User Response: Re-try the operation, check error log for more information.



ANS1131E Unable to continue operation. Duplicate labels exist.

Explanation: The selected drive has a duplicate volume label. Because TSM uses the volume label to keep track of backup/archive information, it cannot back up or archive files from a drive with a duplicate volume label.
System Action: TSM cannot select the drive.
User Response: If the volume needs to be available to the system, exit TSM, and assign a volume label to the drive. Restart TSM and retry the operation.



ANS1150EUnable to restore current user profile because you are running as a local system account.

Explanation: The local system account does not have a profile. Therefore you cannot restore its profile.
System Action: Processing stops.
User Response: Log on to the user whose profile you want to restore.



ANS1151EDrive drive-name1: is not a cluster disk. Not valid for backup/archive when CLUSTERNODE option is YES.

Explanation: The drive-name1 is not a cluster disk. Backup/archive is not allowed when the CLUSTERNODE option is set to YES.
System Action: Processing stops.
User Response: Set CLUSTERNODE option to NO, then backup/archive the drive. Otherwise, you cannot backup/archive the drive.



ANS1152EDrive filespace is not a cluster disk. Not valid for backup/archive when CLUSTERNODE option is YES.

Explanation: The filespace is not a cluster disk. Backup/archive is not allowed when the CLUSTERNODE option is set to YES.
System Action: Processing stops.
User Response: Set CLUSTERNODE option to NO, then backup/archive the drive. Otherwise, you cannot backup/archive the drive.



ANS1153EDrive drive-name1: is a cluster disk. Not valid for backup/archive when CLUSTERNODE option is NO.

Explanation: The drive-name1 is a cluster disk. Backup/archive is not allowed when the CLUSTERNODE option is set to NO.
System Action: Processing stops.
User Response: Set CLUSTERNODE option to YES, then backup/archive the drive. Otherwise, you cannot backup/archive the drive.



ANS1154EDrive filespace is a cluster disk. Not valid for backup/archive when CLUSTERNODE option is NO.

Explanation: The filespace is a cluster disk. Backup/archive is not allowed when the CLUSTERNODE option is set to NO.
System Action: Processing stops.
User Response: Set CLUSTERNODE option to YES, then backup/archive the drive. Otherwise, you cannot backup/archive the drive.



ANS1155ECLUSTERNODE option is set to YES but cluster is not enabled. Either the machine does not have cluster server installed, or the cluster server is not running.

Explanation: If CLUSTERNODE option is set to YES, TSM must be running on a Windows NT Server Enterprise Edition machine with the cluster server installed and running.
System Action: Processing stops.
User Response: Ensure TSM is running in a cluster environment and that the cluster server has been started.



ANS1156ENODENAME cannot be the local machine name when CLUSTERNODE is set to YES

Explanation: When TSM is running as a cluster node, the nodename cannot be the local machine name.
System Action: Processing stops.
User Response: Change the nodename either to the cluster name or to any other name, and restart TSM.



ANS1157IBackup/Restore of the registry is not allowed when running as a cluster node.

Explanation: When running as a cluster node, registry cannot be backed up or restored.
System Action: Processing continues.
User Response: None.



ANS1158IBackup/Restore of the event logs is not allowed when running as a cluster node.

Explanation: When running as a cluster node, event logs cannot be backed up or restored.
System Action: Processing continues.
User Response: None.



ANS1162EFilesystem could not be mounted

Explanation: The system call to mount the file system failed.
System Action: The file system remains unmounted.
User Response: Use the mount command to mount the file system. On AIX, run fsck if requested by the operating system.



ANS1163EFilesystem could not be unmounted.

Explanation: The system call to unmount the file system failed.
System Action: The logical volume operation is not performed.
User Response: Make sure the device or file system is not being accessed, then retry the operation.



ANS1164EFilesystem is not mounted

Explanation: The named file system is not currently mounted. It must be mounted for TSM to perform an image backup.
System Action: The logical volume operation is not performed.
User Response: Mount the file system.



ANS1165EDestination is smaller than source

Explanation: The space allocation for the selected destination is smaller than the source.
System Action: The restore operation is not performed.
User Response: Choose a different, bigger destination or increase the size of the destination file space.



ANS1166ESource and destination are not the same file system type.

Explanation: The source and destination file system types do not match.
System Action: The requested logical volume operation is not performed.
User Response: Choose a destination that has the same file system type as the source.



ANS1202ETOC backup for the image failed. Check log files.

Explanation: An error occurred during backup of the table of contents. Chek the error log for more information.
System Action: The requested logical volume operation is not performed.
User Response: Check error log.



ANS1203EDeactivating the TOC object failed.

Explanation: An error occurred while deactivating the table of contents object.
System Action: Image backup was successful. But deactivating the TOC object from the previous backup failed.
User Response: Check error log.



ANS1204EImage restore failed. Check the error log.

Explanation: An error occurred while restoring the image. Check log file for more information.
System Action: Restore stops. The file system is not mounted back.
User Response: Check error log.



ANS1205EImage backup failed. Check the error log.

Explanation: An error occurred while backing up the image. Check log file for more information.
System Action: Backup stopped. The file system is not mounted back.
User Response: Check error log.



ANS1206ETOC backup of a raw device is not supported. But the raw device is backed up.

Explanation: TOC backup of a raw device is not supported. But the raw device is backed up.
System Action: Raw device is backed up with no TOC object.
User Response: NONE.



ANS1207ENo TOC has been previously backed up for this file system.

Explanation: The user is trying to query the TOC of a file system. TOC backup for that file system has not been previously done.
System Action: Query stopped.
User Response: Backup the file system again with -TOC option.



ANS1229EMODE=INCREMENTAL invalid on file-space. Image backup not processed.

Explanation: The MODE=INCREMENTAL option is not valid on file-space because the filespace has been the subject of a progressive incremental backup since the last full image backup was performed.
System Action: File system skipped.
User Response: If an image backup of the named file-system is desired, retry without the MODE=INCREMENTAL option.



ANS1270EError Loading ACPOCPIC.DLL - not in Search Path

Explanation: TSM cannot find the PWSCS CPIC support file (ACPOCPIC.DLL) in the current search path. This message only applies when using PWSCS communications.
System Action: Connection to server fails.
User Response: Shut down Windows and place the directory where this file resides in the DOS path statement.



ANS1271EError Loading WINSOCK.DLL - not in Search Path

Explanation: TSM cannot find the Windows Socket support file (WINSOCK.DLL) in the current search path. This message only applies when using TCP/IP communications.
System Action: Connection to server fails.
User Response: Shut down Windows and place the directory where this file resides in the DOS path statement.



ANS1274EError Loading WINSOCK.DLL

Explanation: Error loading the Windows socket support file into memory. This error only applies when using TCP/IP communications.
System Action: Connection to server fails.
User Response: Because this error is caused by insufficient memory, shut down running applications and retry. If the problem persists, see your system administrator.



ANS1275EError Loading Function(s) from WINSOCK.DLL

Explanation: Error loading one or more functions from the Windows socket support file.
System Action: Connection to server fails.
User Response: Since this might possibly be caused by insufficient memory, shut down running applications and retry. If the problem persists, see your system administrator.



ANS1276EError Loading ACPOCPIC.DLL

Explanation: Error loading the PWSCS CPIC support file into memory. This error only applies when using PWSCS communications.
System Action: Connection to server fails.
User Response: Since this might possibly be caused by insufficient memory, shut down running applications and retry. If the problem persists, see your system administrator.



ANS1277EError Loading Function(s) from ACPOCPIC.DLL

Explanation: Error loading one or more functions from the PWSCS CPIC support file. This error only applies when using PWSCS communications.
System Action: Connection to server fails.
User Response: Since this might possibly be caused by insufficient memory, shut down running applications and retry. If the problem persists, see your system administrator.



ANS1290ENSDW.DLL not found in search path.

Explanation: TSM cannot find the NS/DOS communications support file (NSDW.DLL) in the current search path. This message only applies when using SNALU6.2 communications.
System Action: Connection to server fails.
User Response: Shut down Windows and place the directory where this file resides in the DOS path statement.



ANS1291EError loading NSDW.DLL.

Explanation: An error occurs while loading the NS/DOS communications support file (NSDW.DLL) into memory. This error only applies when using SNALU6.2 communications.
System Action: Connection to server fails.
User Response: Because this is probably caused by insufficient memory, shut down running applications and retry. If the problem persists, contact your support personnel.



ANS1292EError loading one or more functions from NDSW.DLL.

Explanation: An error occurs while loading one or more functions from the NS/DOS communications support file (NSDW.DLL). This error only applies when using SNALU6.2 communications.
System Action: Connection to server fails.
User Response: Because this is probably caused by insufficient memory, shut down running applications and retry. If the problem persists, contact your support personnel.



ANS1293EEHNAPPC.DLL not found in search path.

Explanation: TSM cannot find the Client Access/400 or PC Support/400 communications support file (EHNAPPC.DLL) in the current search path. This message only applies when using 400 APPC communications.
System Action: Connection to server fails.
User Response: Shut down Windows and place the directory where this file resides in the DOS path statement.



ANS1294EError loading EHNAPPC.DLL.

Explanation: An error occurs while loading the Client Access/400 or PC Support/400 communications support file (EHNAPPC.DLL) into memory. This error only applies when using 400 APPC communications.
System Action: Connection to server fails.
User Response: Because this is probably caused by insufficient memory, shut down running applications and retry. If the problem persists, contact your support personnel.



ANS1295EError loading one or more functions from EHNAPPC.DLL.

Explanation: An error occurs while loading one or more functions from the Client Access/400 or PC Support/400 communications support file (EHNAPPC.DLL). This error only applies when using 400 APPC communications.
System Action: Connection to server fails.
User Response: Because this is probably caused by insufficient memory, shut down running applications and retry. If the problem persists, contact your support personnel.



ANS1296EError Loading WCPIC32.DLL - not in Search Path

Explanation: TSM cannot find the Windows SNA client CPIC support file (WCPIC32.DLL) in the current search path. This message only applies when using SNALU6.2 communications.
System Action: Connection to server fails.
User Response: Shut down Windows and place the directory where this file resides in the DOS path statement.



ANS1297EError Loading WCPIC32.DLL

Explanation: Error loading the Windows SNA client CPIC support file into memory. This error only applies when using SNALU6.2 communications.
System Action: Connection to server fails.
User Response: Since this might possibly be caused by insufficient memory, shut down running applications and retry. If the problem persists, contact your system administrator.



ANS1298EError Loading Function(s) from WCPIC32.DLL

Explanation: Error loading one or more functions from the Windows SNA client CPIC support file. This error only applies when using SNALU6.2 communications.
System Action: Connection to server fails.
User Response: Since this might possibly be caused by insufficient memory, shut down running applications and retry. If the problem persists, contact your system administrator.



ANS1299ESession rejected: SNALU6.2 connection failure. Unable to register as a Windows CPIC application.

Explanation: An attempt to register the application with the Windows SNA client CPIC implementation failed. This error may occur when the the network subsystem is not ready for network communications or when the version of the Windows SNA client CPIC implementation is not supported. This error only applies when using SNALU6.2 communications.
System Action: Connection to server fails.
User Response: Verify that the network subsystem is ready for network communications and that the version of the Windows SNA client CPIC implementation is supported and retry. If the problem persists, contact your system administrator.



ANS1300EUnable to reconstruct '': necessary component was not restored.

Explanation: A subfile component was not received by the client during the restore process.
System Action: Processing stopped.
User Response: Please check error log for more information.



ANS1341EDelta file 'delta-file-name' already exists on client cache.

Explanation: The number defining the correspondence between drive letter or file (domain name) and volume label is not known to the server.
System Action: Processing stopped.
User Response: Report the program error to your service representative.



ANS1342EClient cache is locked; unable to continue with operation.

Explanation: The client cache is currently locked by another process.
System Action: Processing stopped.
User Response: Report the program error to your service representative.



ANS1343EWrong Key entered; unable to restore the file.

Explanation: Key entered does not match the key used for the backed up file.
System Action: Processing stopped.
User Response: Recollect the key used for backup.



ANS1344EJob is running in the background. Cannot prompt for the Key.

Explanation: When jobs are run in the background, the client cannot prompt for the key.
System Action: Processing stopped.
User Response: Run the Job in the foreground.



ANS1345EThe client cache verification record cannot be located.

Explanation: The client cache verification record cannot be located. This record is located based on information made available during product installation. The product must be re-installed in order to update this information correctly.
System Action: Processing stopped.
User Response: Report the program error to your service representative.



ANS1351E Session rejected: All server sessions are currently in use

Explanation: TSM has all available sessions in use and cannot accept a new one at this time.
System Action: TSM canceled the current operation.
User Response: Retry the operation. If the problem continues, see your system administrator to increase the number of concurrently active sessions to the server.



ANS1352E Session rejected: Password has expired

Explanation: Your TSM password has expired.
System Action: TSM canceled the current operation. You are not allowed to connect to the server until the password is updated.
User Response: Update your password.



ANS1353E Session rejected: Unknown or incorrect ID entered

Explanation: The node name you entered is not known by the server, or you are attempting to access a file migrated to a different node.
System Action: TSM canceled the current operation. You are not allowed to connect to the server until your node name is registered with the server. If attempting to access a migrated file, your nodename must be the same node which migrated the file.
User Response: Ensure that you entered your TSM node name correctly. If yes, see your system administrator. Verify that the server is using closed registration and that your node name is registered with the server.



ANS1354E Session rejected: Duplicate ID entered

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



ANS1355E Session rejected: Server disabled

Explanation: The server is in a disabled state and cannot be accessed for normal activity.
System Action: TSM canceled the current operation.
User Response: Retry the operation after the server returns to an enabled state. If the problem continues, see your system administrator.



ANS1356E 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 TSM node and password from your system administrator.



ANS1357S Session rejected: Downlevel client code version

Explanation: The server version and your client version do not match. The client code is downlevel.
System Action: TSM canceled the current operation.
User Response: See your system administrator to see what version of TSM to run for your location.



ANS1358S Session rejected: Downlevel server code version

Explanation: The server version and your client version do not match. The server code is downlevel.
System Action: TSM canceled the current operation.
User Response: See your system administrator to see what version of TSM to run for your location.



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



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



ANS1362S SLM LICENSE EXCEEDED: The client licenses for TSM are exceeded. See your system administrator.

Explanation: Adding a new enrollment will exceed the product license count for TSM.
System Action: Execution of the client enrollment or connection request ends.
User Response: See your system administrator.



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



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



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



ANS1366E Session Rejected: The server has an internal error

Explanation: The client cannot establish a connection to the server because of an internal server error.
System Action: Session was not started.
User Response: See your system administrator immediately.



ANS1367ESession Rejected: The server does not allow a signon as a Unicode enabled client

Explanation: The client can not establish a connection to the server because of a unicode enabling mismatch between server and client.
System Action: Session was not started.
User Response: See your system administrator immediately.



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



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



ANS1370EThe user ID entered does not have the correct level of authority to access the client machine.

Explanation: The user ID entered cannot access this TSM client.
System Action: The TSM operation ends.
User Response: Grant authority to this user ID on the TSM server so that it can access this TSM client.



ANS1371EUnable to reconstruct '' from subfile components.

Explanation: An error occurred while reconstructing this file from its subfile components.
System Action: Processing stopped.
User Response: Please check error log for more information.



ANS1400ETSM encounters a TLI error

Explanation: TSM encounters a TLI error. A more detailed description of the error may be found in the log file. This error only applies when using IPX/SPX communications.
System Action: The client terminates.
User Response: See your system administrator with the log file.



ANS1401ESession rejected: IPX/SPX connection failure

Explanation: An attempt to connect to the server using IPX/SPX communications failed. The server address is incorrect, or the server is not up, or a system error has occurred. This error only applies when using IPX/SPX communications.
System Action: Session is not established.
User Response: Check your server address and make sure that the server is up and running. Retry the operation, and if the problem continues, shut down the system, reboot and retry the operation. If the problem continues, see your system administrator.



ANS1402ETLI.DLL not found in search path

Explanation: TSM cannot find the TLI DLL in the current search path. This error only applies when using IPX/SPX communications.
System Action: Session is not established.
User Response: Place the directory where this file resides in the path statement. Shut down the system and reboot.



ANS1403EError loading TLI.DLL

Explanation: An error occurs while loading the TLI.DLL into memory. This error only applies when using IPX/SPX communications.
System Action: Session is not established.
User Response: This error is caused by insufficient memory. Shut down the system and reboot. If the problem continues, see your system administrator.



ANS1404EError loading one or more functions from the TLI.DLL

Explanation: An error occurs while loading one or more functions from the TLI.DLL file. This error only applies when using IPX/SPX communications.
System Action: Session is not established.
User Response: This error is caused by insufficient memory. Shut down the system and reboot. If the problem continues, see your system administrator.



ANS1450EAPPC unable to allocate conversation.

Explanation: The client is unable to allocate an APPC conversation to the server.
System Action: The client terminates.
User Response: Ensure that the partner LU name and transaction program name in the client configuration file (dsm.opt) are correct. See your system administrator to get the proper partner LU name and transaction program name.



ANS1451EAPPC deallocate error.

Explanation: TSM receives an incorrect return code from the deallocate verb. This error does not affect the TSM program.
System Action: None.
User Response: None.



ANS1452EAPPC missing LU name.

Explanation: A logical unit name is necessary to complete the operation.
System Action: Processing stops.
User Response: Retry the operation using the PARTNERLUNAME option.



ANS1453EAPPC missing TP name.

Explanation: A transaction program name is necessary to complete the operation.
System Action: Processing stops.
User Response: Retry the operation using the TPNAME option.



ANS1454EAPPC parameter error.

Explanation: A parameter to an APPC communication call is in error.
System Action: Processing stops.
User Response: This usually indicates that an invalid transaction program name has been given. Check this value and retry.



ANS1455EAPPC product specific error.

Explanation: TSM detects an error that occurs when making an APPC communication call.
System Action: Processing stops.
User Response: Be sure that LU6.2 is working properly at your installation. Contact your support personnel.



ANS1456EAPPC program error.

Explanation: An unexpected APPC communication error occurs.
System Action: Processing stops.
User Response: This is a program error. Contact your support personnel.



ANS1457EAPPC program parameter check.

Explanation: A parameter to an APPC communication call is in error.
System Action: Processing stops.
User Response: An invalid transaction program name has been given. Check this value in the client configuration file (dsm.opt) and retry.



ANS1458EAPPC program state check.

Explanation: An unexpected APPC communication error occurs.
System Action: Processing stopped.
User Response: This is a program error. Contact your support personnel.



ANS1459EAPPC resource error.

Explanation: The conversation ends prematurely.
System Action: Processing stops.
User Response: Exit TSM and retry the TSM command.



ANS1460EAPPC security not valid.

Explanation: The conversation cannot be allocated because the access security is incorrect.
System Action: Processing stops.
User Response: Contact your support personnel. information table.



ANS1461EAPPC sync level not supported.

Explanation: The conversation cannot continue because the synchronization level of either the local or remote system is not supported.
System Action: Processing stops.
User Response: TSM defaults to no synchronization level. Contact your system administrator.



ANS1462EAPPC TPN not recognized.

Explanation: TSM cannot find the name of the server.
System Action: Processing stops.
User Response: Ensure that the TPNAME option references the correct server name and that the server is running.



ANS1463EAPPC TP error.

Explanation: The server is not responding to the local program's request.
System Action: Processing stops.
User Response: Ensure that the server is running and retry. Stop and start the local communications program.



ANS1464EAPPC type mismatch.

Explanation: An unexpected APPC communication error occurs.
System Action: Processing stops.
User Response: This is a program error. Contact your support personnel.



ANS1465EAPPC unsuccessful.

Explanation: All the sessions for SNA communications have been exhausted.
System Action: Processing stops.
User Response: Stop and start SNA communications and retry the command.



ANS1466EAPPC unknown error occurred.

Explanation: An unexpected APPC communication error occurs.
System Action: Processing stops.
User Response: Contact your support personnel.



ANS1467EAPPC insufficient memory.

Explanation: There is insufficient memory to perform the requested APPC function.
System Action: Processing stops.
User Response: Shut down running applications and retry. If the problem persists, contact your support personnel.



ANS1468EThe APPC router is not installed.

Explanation: A connection to the server cannot be established because the Client Access/400 or PC Support/400 router is not installed.
System Action: Connection to server fails.
User Response: Install the Client Access/400 or PC Support/400 router and retry the command.



ANS1469EError processing 'filespace namepath-namefile-name': invalid encryption key

Explanation: Key entered does not match the key used for the backed up file.
System Action: Processing stopped.
User Response: Recollect the key used for backup.



ANS1470EThe APPC router installed does not support the Windows API.

Explanation: A connection to the server cannot be established because a Client Access/400 or PC Support/400 router supporting Windows is not installed.
System Action: Connection to server fails.
User Response: Install the correct version of the Client Access/400 or PC Support/400 router and retry the command.



ANS1471EPCSWIN is not loaded.

Explanation: A connection to the server cannot be established because the Client Access/400 or PC Support/400 program PCSWIN is not loaded.
System Action: Connection to server fails.
User Response: Load PCSWIN and retry the command.



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



ANS1474E 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: TSM cannot complete the requested operation.
User Response: Check the trace log for additional information and retry the operation. If the problem continues, see your system administrator for further help.



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



ANS1500EModule dsmtca not found in secure directory.

Explanation: TSM cannot find the Trusted Communication Agent module (dsmtca) in the appropriate directory.
System Action: TSM ends.
User Response: Log on as root user, then create a link to dsmtca module in /usr/bin with the command: ln -s /usr/tivoli/tsm/client/ba/bin/dsmtca /usr/bin/dsmtca



ANS1501ETrusted agent execution/owner permissions are invalid

Explanation: The Trusted Communication Agent execution/owner permissions are invalid.
System Action: TSM ends.
User Response: Have your system administrator check the installation instructions for the client to ensure that the Trusted Communication Agent permissions are set correctly. This error can be caused by installing TSM as a non-root user. For the UNIX platforms that have the installation program (dsm.install), you must run dsm.install while logged in as the root user.



ANS1502EAccess to system function required to run has been denied

Explanation: The permissions of the Trusted Communication Agent do not allow it to be accessed by the user of the TSM client.
System Action: TSM ends.
User Response: See your system administrator.



ANS1503EValid password not available for server 'server-name'. The administrator for your system must run TSM and enter the password to store it locally.

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



ANS1504E Error starting the Trusted Communication Agent process.

Explanation: An error has occurred starting the Trusted Communication Agent process; specifically, the fork() function has failed.
System Action: TSM ends.
User Response: Probable system error. If the problem persists, restart the workstation.



ANS1505E Trusted Communication Agent has terminated unexpectedly.

Explanation: The Trusted Communication Agent has terminated unexpectedly.
System Action: TSM ends.
User Response: Check the error log for more information. Retry the activity. If the problem persists, contact your service representative.



ANS1506E Trusted Communication Agent received invalid request.

Explanation: The Trusted Communication Agent has received an unknown request from the TSM client.
System Action: TSM ends.
User Response: Internal error. If the problem recurs, contact your service representative.



ANS1507E This action requires TSM administrative authority on this system.

Explanation: An activity has been attempted that must be performed by the TSM administrator (for example, open registration, filespace delete or password update).
System Action: TSM ends.
User Response: If the activity is required, the administrator for this system must perform it.



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



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



ANS1510E Trusted Communications Agent error attaching shared memory.

Explanation: An error has occurred while attaching the trusted agent's shared memory.
System Action: Return to caller.
User Response: Stop application, check shared memory usage and retry the command. Read the tca.log file for the system error number.



ANS1513EInvalid trace keyword - 'keyword'. Please reenter traceflags.

Explanation: A TRACEFLAG option in the user configuration file or on the command line is incorrect.
System Action: Tracing was not enabled.
User Response: Correct the value. See the entry for TRACEFLAGS in the Trace Facility Guide document for a list of valid trace flags.



ANS1514EInvalid trace keyword. Please reenter traceflags.

Explanation: A TRACEFLAG option in the user configuration file or on the command line is incorrect.
System Action: Tracing was not enabled.
User Response: Correct the value. See the entry for TRACEFLAGS in the Trace Facility Guide document for a list of valid trace flags.



ANS1822SOption 'option-name' is ignored. Processing Continues.

Explanation: The specified option in the options file is invalid for this version of the backup client executable.
System Action: None.
User Response: Either remove this option or ignore the message.



ANS1823EInvalid trace keyword - 'keyword'

Explanation: A TRACEFLAG option in the user configuration file or on the command line is incorrect.
System Action: Client program did not initialize or tracing was not enabled in the applet.
User Response: Correct the value. See the entry for TRACEFLAGS in the Trace Facility Guide document for a list of valid trace flags.



ANS1824EInvalid trace file name (name too long).

Explanation: A TRACEFILE option in the preferences files used a file name that is too long.
System Action: Client program did not initialize.
User Response: Change the file name used as the TRACEFILE so that it is equal to or less than 255 characters in length.



ANS1825EUnable to close trace output file file-name.

Explanation: An error occurred during the closing of a trace output file-name (for example, not enough disk space).
System Action: Processing continues.
User Response: Check the options.doc file for a description of possible causes of the error, or see your system administrator.



ANS1826EUnable to open trace output file file-name.

Explanation: A TRACEFILE option in the user configuration file or on the command line used a directory path and file-name combination to which you do not have write access.
System Action: Client program did not initialize.
User Response: Change the TRACEFILE value so that it is a location to which you have write access.



ANS1827EYou are editing the file, file-name. Please save it and press 'Enter' to continue, or 'q' to exit.

Explanation: You are editing the specified file-name.
System Action: None.
User Response: Save the file and press Enter to continue, or enter 'q' to quit the file.



ANS1828EScreen size is too small for using the PICK option.

Explanation: You cannot use the PICK option on a workstation that has a screen smaller than 20 characters across and 10 lines down.
System Action: TSM did not complete the operation.
User Response: Retry the operation using a workstation that has a screen with the minimum size, or do not use the PICK option.



ANS1830EUnable to write to trace file tracefile. Tracing disabled.

Explanation: An error occurred when writing to the specified tracefile.
System Action: Tracing is disabled. Processing continues.
User Response: Ensure the device that the tracefile access is available and has sufficient space for the tracefile. Retry the command.



ANS1831EPassword expired. The administrator for this system must run TSM to update the password.

Explanation: The password expired.
System Action: TSM ends.
User Response: The administrator for this system must update the password.



ANS1832SUnable to send generated password using MailProg 'option'

Explanation: TSM cannot send the file containing the generated password to the user ID specified in the MailProg option.
System Action: TSM ends.
User Response: Have your service representative check the error log for reasons why the file was not sent to the user ID.



ANS1833SUnable to create 'directory-name' directory for storing passwords

Explanation: TSM cannot create the specified directory-name.
System Action: Processing continues.
User Response: Check to see if you have enough disk space and retry the operation. If unsuccessful, see your system administrator.



ANS1834SUnable to write to 'file-name' for storing password

Explanation: TSM cannot write to the specified file-name.
System Action: Processing continues.
User Response: Check access permissions and disk space. If unsuccessful, see your system administrator.



ANS1835E 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: TSM prompts you for the password if TSM is running in the foreground.
User Response: If TSM was running as a background process, issue any TSM command from the foreground. Enter the password in answer to the prompt. Then try your background TSM command again.



ANS1836SMailProg file-name failed with return code = value.

Explanation: An error occurred with the specified MailProg file-name.
System Action: TSM ends.
User Response: Check the return code for the MailProg file-name. See your system administrator if you are unable to resolve the problem.



ANS1837SFile space filespace-name is ignored. Processing continues.

Explanation: The specified filespace-name in the system options file is invalid.
System Action: TSM attempts to continue the current operation.
User Response: Check the file space in the system options file and use a valid file space. Retry the operation.



ANS1838EError opening user specified options file 'filespace-name' .

Explanation: The specified options file-name could not be located or opened.
System Action: TSM attempts to open default option file.
User Response: Make sure specified option file exists and is valid.



ANS1839ECannot read password.

Explanation: An error occurred in setting up the input file (for example, the terminal) to be read.
System Action: Processing stopped.
User Response: Check the attributes of the terminal.



ANS1841IAttempting to open default options file ...

Explanation: TSM is attempting to open the default options file.
System Action: Processing continues.
User Response: None.



ANS1842S Session rejected: SNALU6.2 connection failure. CPIC unable to allocate conversation

Explanation: TSM client cannot allocate a CPIC conversation to the server.
System Action: Processing stopped.
User Response: Ensure that the symbolic destination name matches a valid side information table entry in your local communications program.



ANS1843S Session rejected: SNALU6.2 connection failure. CPIC conversation type mismatch between the client and the server.

Explanation: An unexpected CPIC error occurred. There is a CPIC conversation type mismatch between the client and the server.
System Action: Processing stopped.
User Response: This is a program error. See your service representative.



ANS1844S Session rejected: SNALU6.2 connection failure. CPIC PIP not specified correctly

Explanation: An unexpected CPIC error occurred. The CPIC PIP is not specified correctly.
System Action: Processing stopped.
User Response: This is a program error. See your service representative.



ANS1845S Session rejected: SNALU6.2 connection failure. CPIC security not valid

Explanation: The conversation cannot be allocated because the CPIC security is not valid.
System Action: Processing stopped.
User Response: Change the security in the CPIC side information table.



ANS1846S Session rejected: SNALU6.2 connection failure. CPIC synchronization level not supported

Explanation: The conversation cannot continue because the CPIC synchronization level of either the local or remote system is not supported.
System Action: Processing stopped.
User Response: TSM defaults to no synchronization level. See your service representative.



ANS1847S Session rejected: SNALU6.2 connection failure. CPIC transaction program name not recognized

Explanation: CPIC transaction program name not recognized. TSM cannot find the name of the server.
System Action: Processing stopped.
User Response: Ensure that you have the correct TSM server name listed in your CPIC side information entry and that the server is running.



ANS1848S Session rejected: SNALU6.2 connection failure. CPIC transaction program not available.

Explanation: CPIC transaction program not available. The server is not responding to the local program's request.
System Action: Processing stopped.
User Response: Ensure that the server is running and retry the command. Stop and start the local communications program.



ANS1849S Session rejected: SNALU6.2 connection failure. CPIC parameter error

Explanation: A parameter to a CPIC call was in error.
System Action: Processing stopped.
User Response: An invalid symbolic destination or invalid transaction program name was given. Check these values and retry the command.



ANS1850S Session rejected: SNALU6.2 connection failure. CPIC product-specific error.

Explanation: TSM detected a CPIC product-specific error that occurred when making a CPIC call.
System Action: Processing stopped.
User Response: Ensure that LU6.2 is working properly at your installation. See your system administrator.



ANS1851S Session rejected: SNALU6.2 connection failure. CPIC program error.

Explanation: An unexpected CPIC program error occurred.
System Action: Processing stopped.
User Response: This is a program error. See your service representative.



ANS1852S Session rejected: SNALU6.2 connection failure. CPIC resource error

Explanation: CPIC resource error. The conversation ended prematurely.
System Action: Processing stopped.
User Response: Exit TSM and retry the TSM command. API applications should close the session with dsmTerminate.



ANS1853W Session rejected: SNALU6.2 connection failure. CPIC conversation deallocation error

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



ANS1854S Session rejected: SNALU6.2 connection failure. CPIC SVC error

Explanation: A CPIC SVC error occurred.
System Action: Processing stopped.
User Response: See your service representative.



ANS1855SSession rejected: SNALU6.2 connection failure. CPIC conversation has been lost

Explanation: The CPIC conversation no longer exists.
System Action: Processing stopped.
User Response: Retry the TSM command.



ANS1856S Session rejected: SNALU6.2 connection failure. CPIC program parameter check

Explanation: A parameter to a CPIC call was in error.
System Action: Processing stopped.
User Response: An invalid symbolic destination or invalid transaction program name was given. Check these values and retry the command.



ANS1857S Session rejected: SNALU6.2 connection failure. CPIC program state check

Explanation: CPIC program state check.
System Action: Processing stopped.
User Response: This is a program error. See your service representative.



ANS1858S Session rejected: SNALU6.2 connection failure. CPIC session not immediately available

Explanation: CPIC session not immediately available. All the sessions for SNA communications are in use.
System Action: Processing stopped.
User Response: Stop and start SNA communications and retry the command.



ANS1859S Session rejected: SNALU6.2 connection failure. CPIC: You must supply an PARtnerluname if no SYMbolicdestination given.

Explanation: For CPIC, you must supply a PARtnerluname if no SYMbolicdestination is given.
System Action: Processing stopped.
User Response: Retry the operation using an LU name or a symbolic destination name.



ANS1860S Session rejected: SNALU6.2 connection failure CPIC: You must supply a TPname if no SYMbolicdestination given.

Explanation: For CPIC, you must supply a TPname if no SYMbolicdestination is given.
System Action: Processing stopped.
User Response: Retry the operation using the TPname option or define the SYMbolicdestination option.



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



ANS1056EShare/network path cannot be resolved. Path does not exist. Specify a destination or restore the directory first.

Explanation: Trying to restore to a share/network path that can't be resolved. The directory path does not exist. Retry the command and specifying a destination or restore the directory tree first before trying to restore the share point.
System Action: Processing stopped.
User Response: None.



ANS1071EInvalid domain name entered: 'domain-name'

Explanation: You entered an invalid domain-name.
System Action: Processing stopped.
User Response: Enter a valid drive or file system name (domain).



ANS1072EUnable to continue operation; Drive 'drive-name' has no volume label.

Explanation: The specified drive-name in the domain list does not have a volume label.
System Action: Processing stopped.
User Response: Use the system format utility to place a unique volume label on all drives on which you intend to run TSM.



ANS1092ENo files matching search criteria were found

Explanation: You entered a search pattern or file name that cannot be found in the server database.
System Action: Processing stopped.
User Response: Ensure that your search pattern is correct, or specify a new search string.



ANS1095ISpecified directory branch structure has been restored

Explanation: The specified directory branch was successfully restored.
System Action: TSM restored the directory branch.
User Response: Continue with normal operations.



ANS1096S Either an Active Policy Set or a node was not found on the server; Unable to proceed

Explanation: Either no Active Policy Set data was found on the server or a fromnode option contained a nodename not found on the server.
System Action: Processing stopped.
User Response: See your system administrator.



ANS1103E Invalid management class entered

Explanation: You entered an invalid management class.
System Action: TSM is unable to do the requested operation.
User Response: Retry the operation using a valid management class.



ANS1130E Unable to continue operation. Drive has no label.

Explanation: The selected drive does not have a label.
System Action: TSM is unable to do the requested operation without a drive or label entered.
User Response: If the drive is a floppy drive, place a disk with a volume label in it and retry the operation. If the disk is a hard drive, ensure the drive has a volume label, and retry the operation.



ANS1134EDrive drive-name is an invalid drive specification

Explanation: The specified drive-name was found to be invalid; the drive probably has not been defined.
System Action: TSM skips the invalid drive and continues to the next drive.
User Response: Check the invalid drive.



ANS1135EDrive drive-name1 is a virtual drive of drive-name2 Not a valid drive to be backed up

Explanation: The drive-name1 was found to be a substitute (SUBST) of another drive-name2. It is not available for backup/archive.
System Action: TSM skips the SUBST drive and continues to the next drive.
User Response: None.



ANS1147EFile is temporarily unavailable.

Explanation: File is temporarily unavailable.
System Action: File skipped.
User Response: Check and see if file is locked by other process. If not, retry the command.



ANS1190ESymbolic link 'linkname' to 'target' was successfully deleted.

Explanation: Log 'linkname' cannot be a symbolic link.
System Action: The symbolic link 'linkname' is deleted, the log is recreated, and processing stops.
User Response: Check the location of the new file. To specify the location of log files, refer to the user's manual for the 'errorlogname' option, the 'schedlogname' option, and the 'DSM_LOG' environmental variable.



ANS1191EUnable to delete symbolic link 'link'.

Explanation: Log 'linkname' cannot be a symbolic link.
System Action: Processing stops.
User Response: Delete the symbolic link 'linkname'.



ANS1192ESpecifying the error log 'link' as a symbolic link is not allowed.

Explanation: Error log 'linkname' cannot be a symbolic link.
System Action: The symbolic link 'linkname' is deleted, the error log is recreated, and processing stops.
User Response: Check the location of the new error log. To specify the location of the error logs, refer to the user's manual for the 'errorlogname' option and 'DSM_LOG' environmental variable.



ANS1193ESpecifying the trace file 'link' as a symbolic link is not allowed.

Explanation: Trace file 'linkname' cannot be a symbolic link.
System Action: The symbolic link 'linkname' is deleted, the trace file is recreated, and processing stops.
User Response: Specify the trace file location with the 'tracefile' option.



ANS1194ESpecifying the schedule log 'link' as a symbolic link is not allowed.

Explanation: Schedule log 'linkname' cannot be a symbolic link.
System Action: The symbolic link 'linkname' is deleted, the schedule log is recreated, and processing stops.
User Response: Check the location of the new schedule log. To specify the location of the schedule log, refer to the user's manual for the 'schedlogname' option.



ANS1216ENot authorized to run TSM. See the administrator for your system.

Explanation: The system options file for the server that you are attempting to connect to contains a user entry, a group entry, or both a user and group entry. Your user ID, or group ID, was not found in any of the entries. You are currently not authorized to run TSM to this server.
System Action: TSM initialization fails and the program ends.
User Response: See the TSM administrator for your system, and ask to be added to the user or group list for this server.



ANS1217E Server name not found in System Options File

Explanation: The system options file does not contain the SERVERNAME option.
System Action: TSM initialization fails and the program ends.
User Response: See the TSM administrator for your system, and make sure that the system options file contains the server name.



ANS1218E 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: TSM initialization fails and the program ends.
User Response: See the TSM administrator for your system, and make sure that the server to which you are trying to connect, has a valid TCPSERVERADDRESS defined in the system options file.



ANS1219E NODENAME cannot be the same as HostName

Explanation: The NODENAME defined in the options file cannot be the same as the system HostName.
System Action: Initialization fails and the program ends.
User Response: See your system administrator or the root user.



ANS1230EStale NFS File Handle

Explanation: An NFS file system becomes stale.
System Action: File system skipped.
User Response: Check the NFS mounted filesystem.



ANS1237EServer problem. Please see error log.

Explanation: This is a server problem.
System Action: Processing stopped.
User Response: Have your service representative check the error log.



ANS1238S Internal Error. Please see error log.

Explanation: Server problem. Invalid policy binding.
System Action: Processing stopped.
User Response: Have your service representative check the error log.



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



ANS1265EEncountered bad mount or filesystem, processing stopped.

Explanation: The getmnt system call returned an error indication. Error was encountered trying to determine what the mounted file systems are.
System Action: Processing stopped. Cannot recover.
User Response: There is a bad file system or mount point on your system. Look at file systems and mounts, and correct any errors. If unsuccessful, see your system administrator for more information.



ANS1266EEncountered bad mount or filesystem, processing stopped.

Explanation: An error was encountered trying to determine what the mounted file systems are.
System Action: Processing stopped. Cannot recover.
User Response: There is a bad filesystem or mount point on your system. Look at file systems and mounts, and correct any errors. If you used to have an FSM (HSM) file system but then removed HSM from it, make sure that there is no FSM mount for that filesystem; if it is still there then unmount it. If unsuccessful, see your system administrator for more information.



ANS1267EThe management class for file file-name does not allow migration. This file will not be migrated.

Explanation: The management class for this file does not allow migration
System Action: File is skipped.
User Response: Either have the TSM administrator change the Space Management Technique within the management class to a value other than NONE or change the include/exclude list to specify a management class with the appropriate Space Management Technique value.



ANS1410EUnable to access the network path.

Explanation: The network path cannot be accessed due to a possible network problem.
System Action: The client terminates.
User Response: Ensure that the network is up and the path can be accessed using a system command, and retry the operation.



ANS1411EA communication session was dropped.

Explanation: A communication session was dropped due to a possible network problem.
System Action: The client terminates.
User Response: Ensure that the network is up and retry the operation.



ANS1412EDirectory or file has bad EA data or inconsistent data.

Explanation: Directory or file has bad EA data or inconsistent data.
System Action: The client terminates.
User Response: Check failing directory or file for bad EA data. Copy the directory to a new location and retry the operation.



ANS1861EError loading the SNA Services/6000 CPIC routines.

Explanation: TSM cannot load the SNA Services/6000 driver file. This message only applies when using CPI Communications via SNA Services/6000.
System Action: Connection to the server fails.
User Response: Make sure the SNA Services/6000 CPI Communications library file, '/usr/lib/libcpic.a', exists. This file is installed when SNA Services/6000 was installed. Also, make sure the TSM SNA Services/6000 driver file, dsmsna.drv, exists in the TSM installation directory.



ANS1904EThe archive description may not contain any wildcard characters like '?' or '*'.

Explanation: Descriptions for archive files must not contain wildcard characters.
System Action: Processing stopped.
User Response: Enter an archive description that does not contain wildcard characters.



ANS1933EError accessing file or device 'name'.

Explanation: An error has occurred while accessing the file or device.
System Action: Backup set operation is not completed.
User Response: Verify that the file or device exists and is accessible.



ANS1934EBackup set 'name' not found.

Explanation: The backup set name was not found on the server.
System Action: The backup set operation is not processed.
User Response: Verify that the backup set name is correct.



ANS13375ESession Rejected: The specified user id is currently locked

Explanation: The user id 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 user id is locked.


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