ADSM V3R1 Messages

Chapter 27. Command-Line Client (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 ADSM client and your operating system.

ANS1001E Session rejected: The 3270 emulator session cannot be accessed.
Explanation: The 3270 terminal emulator was not active or cannot be accessed by ADSM. Ensure that your 3270 terminal emulator is active and that it is at the proper level as supported by ADSM.
System Action: ADSM cannot connect to the server. ADSM canceled the current operation.
User Response: Ensure that the emulator is active and at the proper release level.

ANS1002E Session rejected: The 3270 emulator session session-name is invalid.
Explanation: The 3270 emulator session cannot be accessed by ADSM.
System Action: ADSM cannot connect to the server. ADSM canceled the current operation.
User Response: Ensure that the correct short name is specified for the 3270 terminal session that ADSM is to access. The short name is usually shown in the lower left corner of the 3270 session. Valid names are single alphabetic characters from a through z.

ANS1003E Session rejected: The 3270 emulator session session-name is connected to another HLLAPI application.
Explanation: Another application (typically a HLLAPI application) is running on your machine and has access to the 3270 host session.
System Action: ADSM cannot connect to the server. ADSM canceled the current operation.
User Response: Try running ADSM again to see if the condition clears. If the condition remains, see what other applications are running on your system and suspend or end the one that is preventing ADSM from accessing the server.

ANS1004E Session rejected: The server cannot be started on the specified 3270 host session. Host session might be down or in an incorrect state.
Explanation: ADSM cannot access the specified 3270 host session to connect to the server. Host session might be down or in an incorrect state.
System Action: ADSM cannot connect to the server. ADSM canceled the current operation.
User Response: Check to see if your host system is active. If so, ensure that the 3270 terminal session is in the proper state to receive the 3270 startup command sequence. If the system fails, make sure the server is active.

ANS1005E Session rejected: The OS/2 CM file ACS3ELKE.DLL is not available or is invalid.
Explanation: The OS/2 CM file ACS3ELKE.DLL is not available or is invalid.
System Action: Communications link is not established. Session rejected.
User Response: See your system administrator.

ANS1006E Session rejected: Unexpected 3270 emulator error. Unknown cause.
Explanation: An unknown error was returned from the 3270 emulator session to ADSM.
System Action: ADSM canceled the current operation. Session rejected.
User Response: Ensure that the 3270 session is functioning properly. If the problem continues, see your service representative for further problem determination.

ANS1007S Session rejected: 3270 emulator is backlevel. Please upgrade.
Explanation: You are running a back level version of the 3270 emulator that is not supported by ADSM.
System Action: ADSM cannot connect to the server. ADSM canceled the current operation.
User Response: Install the current version of the 3270 emulator.

ANS1008E Session rejected: Corrupted data received over 3270 session. Check your connection path for errors.
Explanation: Corrupted data was received over the 3270 connection.
System Action: The client ends its current activity with the server.
User Response: Check your connection path for errors. Verify that you have installed and set up your 3270 emulator properly. Also, ensure that your 3270BUFFERSIZE as specified in your ADSM options file is not too large for your site. Typically, values of 4,000 bytes are accepted without error, but values over 32,000 bytes might cause this error if your communication link does not support the larger sizes.

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

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

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

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

ANS1016E Session 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 ADSM. 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 ADSM error log to find the NETBIOS return code. See your system administrator for help with your NETBIOS installation/configuration problem.

ANS1022E Cannot 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 DOS, OS/2, or AIX) and cannot be used on this system.
System Action: ADSM 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.

ANS1024E Session 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: ADSM 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: ADSM 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.

ANS1027E Session failure: Server not available.
Explanation: The server cannot be accessed at this time.
System Action: ADSM 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 ADSM 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.

ANS1029E Communications have been dropped.
Explanation: Communications with the server dropped.
System Action: Processing stopped.
User Response: Restart the ADSM client and retry the operation.

ANS1030E System ran out of memory. Process ended.
Explanation: ADSM cannot allocate storage for the specified operation.
System Action: ADSM cannot complete the requested operation.
User Response: Stop ADSM, restart ADSM, and retry the operation. If unsuccessful, close all unneeded applications and retry the operation.

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 ADSM client ends.
User Response: See if you have the environment variable DSM_CONFIG (or DSMI_CONFIG for the API) set, which explicitly identifies the ADSM 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 ADSM looks for the file dsm.opt in the current directory. If neither of these cases is met, you receive this error message.

ANS1036S Invalid option 'option' found in options file 'file-name'
at line number : number
Invalid entry : 'entry'.
Explanation: The specified option in the ADSM options file (file-name) is in error.
System Action: Processing stopped.
User Response: Correct the options file entry.

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

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

ANS1039S Include/Exclude pattern too complex.
Explanation: The include or exclude pattern issued is too complex to be accurately interpreted by ADSM.
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.

ANS1044S Unresolved environment name 'environment-name'.This filespace is being ignored. Processing Continues.
Explanation: The specified environment-name in the options file is invalid.
System Action: ADSM 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.

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

ANS1046E 3270 Communications time-out has occurred.
Explanation: The client timed out waiting for data to arrive from the server via a 3270 connection.
System Action: Connection with the server is dropped.
User Response: If system response time is very slow, increase the timeout value with the 3270HOSTTIMEOUT option. Also, make sure the specified emulator session is in the right state.

ANS1047E Establishment 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.

ANS1048E An 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.

ANS1049E The 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.

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

ANS1052E A 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.

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

ANS1072E Unable 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 ADSM.

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

ANS1074I *** User Abort ***.
Explanation: An abort signal to stop an operation was received.
System Action: Processing stopped.
User Response: Continue with normal operations.

ANS1075E *** Program memory exhausted ***.
Explanation: The program has exhausted all available storage.
System Action: Processing stopped.
User Response: Free any unnecessary programs, for example, terminate and stay resident programs (TSRs), that are running and retry the operation. Reducing the scope of queries and the amount of data returned can also solve the problem.

ANS1076E *** Directory path not found ***.
Explanation: You specified an incorrect directory path.
System Action: Processing stopped.
User Response: Correct the syntax specified on the call and retry the operation.

ANS1077E ARCHMC Keyword is only valid for the ARCHIVE subcommand.
Explanation: You entered an incorrect subcommand for the keyword ARCHMC.
System Action: Processing stopped.
User Response: Correct the command and retry the operation.

ANS1078S *** Unknown system error error-code; program ending ***.
Explanation: An unknown and unexpected error-code occurred within the client program. This is a programming failure and the client program ends.
System Action: Processing stopped.
User Response: Retry the operation. If the problem continues, see your administrator.

ANS1079E No file specification entered.
Explanation: You did not enter a file specification as prompted.
System Action: ADSM did not continue with the requested operation.
User Response: Enter a file specification to continue.

ANS1080E Unable to continue backup; Drive 'drive-name' has no label.
Explanation: The specified drive-name being backed up does not have a volume label.
System Action: ADSM cannot complete the requested operation.
User Response: Use the system format utility to place a unique volume label on this drive and all the drives on which you intend to run ADSM.

ANS1081E Invalid search file specification 'string' entered.
Explanation: You entered a file specification or search string that contains incorrect characters or contains wildcard characters in the drive specification or file system name.
System Action: Processing stopped.
User Response: Enter a correct file specification as described in the appropriate Using the Backup-Archive Client book for the particular operating system.

ANS1082E Invalid destination file specification 'file-name' entered.
Explanation: You entered a destination file-name specification that contains incorrect characters or has wildcard characters in the specification.
System Action: Processing stopped.
User Response: Enter a correct file specification as described in the appropriate Using the Backup-Archive Client book for the particular operating system.

ANS1083E No files have previously been archived for 'filespace-name'.
Explanation: You tried to retrieve files when no files for the specified drive or file system (filespace-name) 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 retrieve.

ANS1084E No files have previously been backed up for 'filespace-name'.
Explanation: You tried to restore files when no files for the specified drive or file system (filespace-name) 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 restore.

ANS1085E No memory available to store Archive Management Class override name.
Explanation: Not enough memory was available for the operation.
System Action: Processing stopped.
User Response: Retry the operation or restart the system with fewer programs in memory.

ANS1086E 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 deletes the file before it can be backed up, archived or migrated by ADSM.
System Action: File skipped.
User Response: None.

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

ANS1088E File space 'filespace-name' does not exist.
Explanation: The specified file space (domain) is incorrect or does not exist on the workstation.
System Action: Processing stopped.
User Response: Retry the operation specifying an existing domain (drive letter or file system name).

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

ANS1090E Unable to build directory branch; A file exists with the same name as a directory.
Failing path was: 'path-name'.
Explanation: ADSM tried to create a directory path-name, but is unable to because a file exists that has the same name as a directory.
System Action: Processing stopped.
User Response: Remove the file that has the same name as the directory. Refer to the given failing path, and either remove or move the file that caused this problem and restart the restore/retrieve operation.

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

ANS1092E No 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.

ANS1093E Server does not support point-in-time option.
Explanation: The server to which you are connected, does not support point in time values.
System Action: Processing stopped.
User Response: Enter the command without specifying the point in time option.

ANS1094I The EXPIRATION option is ignored. Processing continues.
Explanation: The EXPIRATION option on the ARCHIVE command is ignored.
System Action: Processing continues.
User Response: None.

ANS1095I Specified directory branch structure has been restored.
Explanation: The specified directory branch was successfully restored.
System Action: ADSM 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.

ANS1097E Unable to read help text.
Explanation: The Help facility cannot read the help text file.
System Action: Processing stopped.
User Response: Make sure the DSM_DIR environment variable points to the correct directory containing the current level of ADSM program files.

ANS1098E Process terminated; Program memory exhausted.
Explanation: The program used all available storage.
System Action: Processing stopped.
User Response: Free any unnecessary programs (TSRs) that are running, and retry the operation. Reducing the scope of queries and the amount of data returned can also solve the problem.

ANS1101S Internal program error. Failing message value was value.
Please see your service representative.
Explanation: An unexpected catastrophic program failure occurred, indicated by value.
System Action: Processing stopped.
User Response: Retry the operation. If the problem continues, see your system administrator or service representative.

ANS1102E Excessive number of command line arguments passed to the program.
Explanation: This command processing routine received more operands than it can use. Query can contain only one file specification. Restore and Retrieve can contain two file specifications. Archive, Delete, and Selective can contain a maximum of 20 file specifications.
System Action: Processing stopped.
User Response: Reduce the number of arguments and retry the operation. For UNIX-based systems, ensure that you do not omit the quotes around pattern matching characters.

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

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

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

ANS1107E Invalid option/value: 'option'.
Explanation: You specified an incorrect ADSM option.
System Action: Processing stopped.
User Response: Specify a correct ADSM option as defined in the appropriate Using the Backup-Archive Client book for the particular operating system.

ANS1108E Invalid option (option) for the function command.
Explanation: The option option was specified for a command or subcommand (function) that cannot make use of that option.
System Action: Processing stopped.
User Response: See the appropriate Using the Backup-Archive Client book for your operating system for correct use of the named option.

ANS1110E Unable to open Help file file-name.
Explanation: The Help facility cannot find the help file file-name.
System Action: Processing stopped.
User Response: Ensure that the DSM_DIR environment variable points to the correct directory containing the current level of ADSM program files.

ANS1111E Unable to get Help file table of contents.
Explanation: The Help facility cannot read the help text file, or the file is corrupted.
System Action: Processing stopped.
User Response: Make sure the DSM_DIR environment variable points to the correct directory containing the current level of ADSM program files, and that the files are intact.

ANS1112I One or more files will be stored on offline media.
Explanation: For the backup or archive operation, one or more files must be sent to offline storage media (generally tape). The wait time depends on your site's offline storage management policies.
System Action: ADSM waits for offline storage media to become available and then continues.
User Response: None.

ANS1113I One or more requested files are stored on offline media.
Explanation: For the restore or retrieve operation, one or more files must be recalled from offline storage media (generally tape). The wait time depends on your site's offline storage management policies.
System Action: ADSM waits for offline storage media to become available and then continues.
User Response: None.

ANS1114I Waiting for mount of offline media.
Explanation: The server is waiting for the requested media to become available before the operation can continue.
System Action: ADSM waits for requested data.
User Response: None.

ANS1115W File 'file-namefile-namefile-name' excluded by Include/Exclude list.
Explanation: You tried to back up or migrate a file (file-name) that was specified to be excluded from backup.
System Action: ADSM did not back up or migrate the file.
User Response: Specify the file using the Include option and retry the operation.

ANS1116E Unable to read commands entered from keyboard. Exiting...
Explanation: Unable to read commands entered from keyboard. ADSM cannot process your intended command.
System Action: Processing stopped.
User Response: Ensure that you are entering a correct command.

ANS1117E The PICK and LATEST options are not valid together.
Explanation: During a restore, PICK and LATEST options cannot be used together.
System Action: Processing stopped.
User Response: Try again using either the PICK or the LATEST option.

ANS1118W Invalid file space number entered.
Try again.
Explanation: The number that represents a file space was incorrect while you were using the PICK option.
System Action: ADSM waits for your specification.
User Response: Enter a correct file space number.

ANS1119I Initiating the removal of 'filespace-name' file space.
Explanation: Indicates that file space deletion has started on the specified filespace-name.
System Action: None.
User Response: None.

ANS1120E Removal of file space 'filespace-name' failed.
Explanation: Deletion of the specified filespace-name failed.
System Action: Processing stopped.
User Response: Try again. If the problem continues, see your system administrator to delete the file space for you.

ANS1121I Removal of file space 'filespace-name' successfully completed.
Explanation: ADSM successfully deleted the specified filespace-name.
System Action: None.
User Response: None.

ANS1122W File space 'filespace-name' does not exist on the server. The file space might have been deleted by another client using your client's node name or an administrator.
Explanation: The specified filespace-name does not exist on the server. Your system administrator deleted the file space or another client using your client's node name might have deleted it.
System Action: None.
User Response: None.

ANS1123E The vertical screen dimension is too small to display the Help directory. Increase your window height.
Explanation: Execution of the HELP command requires space for both the user prompts and at least one line of the HELP directory.
System Action: The help directory is not displayed, and the help command cannot complete.
User Response: Increase the size of your display window to allow more rows of text to be displayed.

ANS1125E Unmatched Quotes: 'string'.
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 using matching quotes in the syntax.

ANS1126E Unable to delete the file space because this node does not have
permission to delete archived data and/or backed up file space.
Explanation: During a delete filespace operation, you specified a file space to which your node does not have permission to delete archived data and/or backed up data.
System Action: Delete processing fails.
User Response: See your system administrator.

ANS1127E Your node does not have permission to delete archived files.
Explanation: Your node is not allowed by the server to delete archived files.
System Action: ADSM did not delete the archived files.
User Response: See your system administrator.

ANS1128S Invalid Management Class assigned to directories. Please see the error log.
Explanation: An invalid management class was assigned to directories.
System Action: Processing stopped.
User Response: Have your service representative check the error log.

ANS1129S No backup copy group in the management class used for directories.
Please see the error log.
Explanation: The management class used for directories does not have a backup copy group.
System Action: Processing stopped.
User Response: Have your service representative check the error log.

ANS1130E Unable to continue operation. Drive has no label.
Explanation: The selected drive does not have a label.
System Action: ADSM 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.

ANS1131E Unable to continue operation. Duplicate labels exist.
Explanation: The selected drive has a duplicate volume label. Because ADSM 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: ADSM cannot select the drive.
User Response: If the volume needs to be available to the system, exit ADSM, and assign a volume label to the drive. Restart ADSM and retry the operation.

ANS1132E '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: ADSM 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.

ANS1133W An expression might contain a wildcard not enclosed in quotes.
Explanation: ADSM cannot process the command because a UNIX shell expands a wildcard expression, for example, asterisk (*) or question mark (?), that has no quotes.
System Action: Command dependent.
User Response: Enclose the wildcard expression in quotes and enter the command.

ANS1134E Drive 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: ADSM skips the invalid drive and continues to the next drive.
User Response: Check the invalid drive.

ANS1135E Drive 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: ADSM skips the SUBST drive and continues to the next drive.
User Response: None.

ANS1136E Not file owner.
Explanation: The file cannot be backed up because the client is not the file owner.
System Action: ADSM skips the file.
User Response: None.

ANS1137W Invalid Index 'number' skipped.
Explanation: An incorrect number was entered for the Index.
System Action: Processing stopped.
User Response: Correct the Index entry and retry the operation.

ANS1138E The 'command-name' command must be followed by a subcommand.
Explanation: You entered an incomplete command-name.
System Action: Processing stopped.
User Response: Enter the correct syntax of the command and continue.

ANS1139E 'Subcommand-name' is an invalid subcommand for 'command-name'.
Explanation: You entered an incorrect subcommand-name for the specified command-name.
System Action: Processing stopped.
User Response: Enter the command with a correct subcommand.

ANS1140E Invalid format for Set Access command.
Explanation: None.
System Action: Processing stopped.
User Response: Enter the SET ACCESS command using the correct syntax.

ANS1141W Unknown command - command-name.
Explanation: You entered an incorrect command-name.
System Action: None.
User Response: Enter the correct command.

ANS1143E The DIRSONLY and FILESONLY options are not valid together.
Explanation: The DIRSONLY and FILESONLY options cannot be used together.
System Action: Processing stopped.
User Response: Try again using either the DIRSONLY or the FILESONLY option.

ANS1144W Password authentication not active on server.
Explanation: None.
System Action: Processing stopped.
User Response: Because password authentication is turned off on the server, you do not need to update the password.

ANS1145E Maximum macro nesting level exceeded.
Explanation: Too many levels of macro nesting are encountered.
System Action: The macro is ignored and an error is returned.
User Response: Reduce the level of macro nesting.

ANS1146E Macro file 'file spec' cannot be opened.
Explanation: A macro command has been entered that specifies the macro file name shown. However, that file cannot be opened for reading.
System Action: The macro is ignored and an error is returned.
User Response: Enter the command with the proper macro name.

ANS1147E File 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.

ANS1148I 'Command-name' command successfully completed.
Explanation: The specified command-name was successfully completed.
System Action: ADSM completed the command.
User Response: Continue with normal operations.

ANS1149E No domain available for incremental backup.
Explanation: An incremental backup was started, but no domain was selected.
System Action: Processing stopped.
User Response: Choose a domain and restart the incremental backup.

ANS1201E Unable to build a directory path; a file exists with the same name as
a directory.
Explanation: ADSM tried to create a directory path, but is unable to because a file exists that has the same name as a directory.
System Action: Processing stopped.
User Response: Remove the file that has the same name as the directory. Refer to the last restore/retrieve operation and check all directories along the path.

ANS1216E Not authorized to run ADSM. See the ADSM 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 ADSM to this server.
System Action: ADSM initialization fails and the program ends.
User Response: See the ADSM 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: ADSM initialization fails and the program ends.
User Response: See the ADSM 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: ADSM initialization fails and the program ends.
User Response: See the ADSM 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.

ANS1220E Server out of resources.
Explanation: The server ran out of resources. A lack of storage or a condition does not allow any new activity.
System Action: ADSM canceled the current operation.
User Response: Retry the operation at a later time. If the problem continues, see your system administrator to isolate what resource is unavailable.

ANS1221E Transaction aborted.
Explanation: The current transaction between the server and the client stopped. A server, client, or communication failure cannot be recovered.
System Action: ADSM canceled the current operation.
User Response: Retry the operation. If the problem continues, see your system administrator to isolate the problem.

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

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

ANS1224E 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: ADSM canceled the operation.
User Response: Obtain a machine with more memory and retry the operation.

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

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

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

ANS1228E Sending of object 'object-nameobject-nameobject-name' failed.
Explanation: The specified file (object-name) cannot be sent to the server.
System Action: File skipped.
User Response: Retry the operation. If the problem continues, see your system administrator to isolate the problem through use of the server console.

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

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

ANS1232E File exists.
Explanation: The file being restored or retrieved exists.
System Action: File is replaced or skipped depending on client options.
User Response: None.

ANS1233E Invalid file handle passed; System Error.
Explanation: An internal system error occurred. A file operation failed because an invalid file handle was passed.
System Action: Processing stopped.
User Response: Report the problem to your system administrator, and then retry the operation.

ANS1234E Protocol violation.
Explanation: A communications protocol error occurred. The communication subsystem is not properly defined or is itself in error.
System Action: ADSM ended the current operation.
User Response: Verify that the communication processes are operating properly, and then retry the operation.

ANS1235E Unknown system error.
Explanation: An unknown error occurred. This might be a low-level system or communication error that ADSM cannot handle or recover from.
System Action: Processing stopped.
User Response: Retry the operation. If the problem continues, determine where the problem exists. See your system administrator for further help.

ANS1236E Unexpected error.
Explanation: An unexpected error occurred. This might be a low-level system or communication error that ADSM cannot handle or recover from.
System Action: Processing stopped.
User Response: Retry the operation. If the problem continues, determine where the problem exists. See your system administrator for further help.

ANS1237E Server 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.

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

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

ANS1243E File name too long.
Explanation: The file name specified is too long to be handled by ADSM.
System Action: File is skipped.
User Response: See the appropriate Using the Backup-Archive Client book for the particular operating system, for the file names that are handled by ADSM.

ANS1244E File system is locked by system.
Explanation: File system cannot be accessed because it is locked by the system.
System Action: ADSM cannot complete the operation.
User Response: See your system administrator.

ANS1245E Format unknown.
Explanation: ADSM tried to restore or retrieve a file, but it had an unknown format.
System Action: File skipped.
User Response: See your system administrator.

ANS1247I Waiting for files from the server...
Explanation: Restore request has been sent to the server. The wait time depends on how many files you are restoring.
System Action: ADSM waits for files to restore from the server.
User Response: None.

ANS1248E An active restore for the same source file specification exists.
Unable to continue with this request.
Explanation: Currently, there is an active restore for the same source file specification. Another restore of the same source file specification cannot be started.
System Action: The requested restore fails.
User Response: Start another restore with a different source file specification.

ANS1249W Server cannot restart the last restore request.
Do you want to restore without restart or abort the request?
Explanation: The restart restore token has expired. The server cannot restart the restore from where it last ended.
System Action: Processing stopped; waiting for user intervention.
User Response: Retry the request without restart or abort the request.

ANS1251E 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 to ADSM, and then retry the operation.

ANS1252E File system/drive is bad. A directory exists that is missing either a '.' or '..' entry. Have your service
representative check the error log.
Explanation: The drive was not available for access. A directory exists that does not have either a '.' or '..' entry.
System Action: Processing stopped.
User Response: Ensure that the drive is operational, and then retry the operation. If unsuccessful, have your service representative check the error log.

ANS1253E File input/output error.
Explanation: An error was found while reading from or writing to the file.
System Action: File skipped.
User Response: Check your system to ensure that it is operating properly. For OS/2, run CHKDSK /F for the failing drive which can be found in dsmerror.log.

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

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

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.

ANS1260E File is being recalled or has been recalled.
Explanation: The file is being recalled by another process or has been recalled.
System Action: File skipped.
User Response: None

ANS1262E The active policy set does not contain any backup copy groups. If you
continue with the incremental backup, any currently backed up files are deactivated on the server and assigned the Backup Grace Period.
Explanation: You tried to back up the files using a policy set that contains no backup management information (the copy group). None of the management classes within the active policy set contain any backup copy groups.
System Action: If you continue with the incremental backup, the workstation file is not backed up, and any backup versions currently residing in data storage are assigned to the backup retention grace period defined for the policy domain. ADSM prompts you for a yes or no response.
User Response: Reply yes to accept the Backup Grace Retention Period or no to cancel the operation. If you cancel the operation, you can retry the incremental backup by creating a management class that has a backup copy group and bind the file to that management class in your include-exclude list. If unsuccessful, see your system administrator for more information.

ANS1263E The active policy set does not contain any backup copy groups. Unable to continue with selective backup.
Explanation: You tried to do a selective backup and have specified a policy set that does not contain a backup management information (the copy group).
System Action: ADSM did not backup the file.
User Response: Create a management class that has a backup copy group, bind the file to that management class in your include-exclude list, and retry the operation. If unsuccessful, see your system administrator for more information.

ANS1264E The active policy set does not contain any archive copy groups. Unable to continue with archive.
Explanation: You tried to archive a file or group of files and have specified a policy set that does not contain an archive management information (the copy group).
System Action: ADSM did not archive the file.
User Response: Create a management class that has an archive copy group, assign the file to the management class, either through your include-exclude list or with the ARCHMC option, and retry the operation. If unsuccessful, see your system administrator for more information.

ANS1265E Encountered 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.

ANS1266E Encountered 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.

ANS1267E The 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 ADSM 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.

ANS1268E This file has been migrated.
Explanation: File has been migrated. If files that are hard linked together are migrated then files subsequent to the first one encountered get this.
System Action: File is skipped.
User Response: None.

ANS1269I File is implicitly excluded.
Explanation: You tried to back up or migrate a file that is implicitly excluded.
System Action: ADSM will not back up or migrate an implicitly excluded file.
User Response: None.

ANS1270E Error Loading ACPOCPIC.DLL - not in Search Path.
Explanation: ADSM 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.

ANS1271E Error Loading WINSOCK.DLL - not in Search Path.
Explanation: ADSM 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.

ANS1272E Error Loading PCSHLL.DLL - not in Search Path.
Explanation: ADSM cannot find the PC3270W 3.00 EHLLAPI support file in the current search path. This message only applies when using 3270 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.

ANS1273E Error Loading DSM3270.DLL - not in Search Path.
Explanation: ADSM cannot find the ADSM 3270 support file in the current search path. This message only applies when using 3270 communications.
System Action: Connection to server fails.
User Response: Make sure this file was loaded from the ADSM Windows client installation disk into a directory that is in the current path. This installation program copies this file into the same directory as the ADSM Windows client executables.

ANS1274E Error 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.

ANS1275E Error 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.

ANS1276E Error 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.

ANS1277E Error 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.

ANS1278E Error Loading DSM3270.DLL.
Explanation: Error loading the ADSM 3270 support file into memory. This error only applies when using 3270 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.

ANS1279E Error Loading One or More Functions from DSM3270.DLL.
Explanation: Error loading one or more functions from the ADSM 3270 support file. This error only applies when using 3270 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.

ANS1280E Error Loading PCSHLL.DLL.
Explanation: Error loading the PC3270W v3.00 EHLLAPI support file. This error only applies when using 3270 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.

ANS1281E Error Loading One or More Functions from PCSHLL.DLL.
Explanation: Error loading one or more functions from the PC3270W v3.00 EHLLAPI support file. This error only applies when using 3270 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.

ANS1282E 3270 Communications Connection Error.
Explanation: Connection to the ADSM server using 3270 communications failed.
System Action: Connection to server fails.
User Response: See your service representative.

ANS1283E Error Allocating 3270 Communications Buffer.
Explanation: A 3270 communications buffer could not be allocated. This is usually caused by insufficient memory.
System Action: Connection to server fails.
User Response: Shut down some running applications or reduce the communication buffer sizes by using the 3270BUFFERSIZE option. If the problem persists, see your system administrator.

ANS1284E Error Sending Keystrokes to 3270 Host Session.
Explanation: An error occurred sending the host startup command specified in the 3270HOSTCOMMAND option to the specified host session.
System Action: Connection fails.
User Response: Make sure that the specified emulator session is in the correct state (Input is not inhibited, and so on).

ANS1285E 3270 Packet Check or Checksum Error.
Explanation: A packet or checksum error occurred when receiving data from the server.
System Action: Connection dropped.
User Response: Retry the operation. If the problem persists, see your system administrator.

ANS1286E 3270 Host Timeout Error.
Explanation: The client timed out waiting for data to arrive from the server.
System Action: Connection is dropped/fails.
User Response: If system response time is very slow, try increasing the timeout value with the 3270HOSTTIMEOUT option. Also, make sure the specified emulator session is in the correct state.

ANS1287E 3270 Send Error.
Explanation: An error occurred sending data to the server.
System Action: Connection is dropped.
User Response: See your system administrator.

ANS1288E 3270 Receive Error.
Explanation: Error receiving data from the server.
System Action: Connection is dropped.
User Response: See your system administrator.

ANS1289E 3270 Communications Error.
Explanation: General 3270 communication error. Connection to server was dropped or failed.
System Action: Communications link not established.
User Response: See your system administrator.

ANS1290E NSDW.DLL not found in search path.
Explanation: ADSM 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.

ANS1291E Error 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.

ANS1292E Error 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.

ANS1293E EHNAPPC.DLL not found in search path.
Explanation: ADSM 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.

ANS1294E Error 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.

ANS1295E Error 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.

ANS1296E Error Loading WCPIC32.DLL - not in Search Path.
Explanation: ADSM 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.

ANS1297E Error 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.

ANS1298E Error 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.

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

ANS1301E Server detected system error.
Explanation: The server detected a system error and notified the clients.
System Action: Processing stopped.
User Response: See your system administrator for further information on server activity.

ANS1302E No objects on server match query.
Explanation: No objects on the server match the query operation being performed.
System Action: Processing stopped.
User Response: Ensure the names are properly entered.

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

ANS1304W Active object not found.
Explanation: ADSM did not find an active object flagged for expiration on the server. The object is marked as expired by another ADSM operation.
System Action: None.
User Response: None.

ANS1305E No data on server.
Explanation: ADSM tried to do a restore or retrieve on an object that has no data associated with it.
System Action: ADSM ended the current operation.
User Response: See your system administrator to verify the problem. If the problem continues, see your system administrator.

ANS1306E Bad verifier.
Explanation: You entered an incorrect password (verifier).
System Action: Processing stopped.
User Response: Retry the session with the correct password.

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

ANS1308E 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: ADSM canceled the current operation.
User Response: Retry archiving the file with an expiration date that is higher than today's date.

ANS1309W 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: ADSM waits for offline storage media to become available and then continues.
User Response: None.

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

ANS1311E Server out of data storage space.
Explanation: The server does not have any space available to store the object.
System Action: ADSM ended the current operation.
User Response: Inform your system administrator that a storage pool on the server is full.

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

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

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

ANS1315E Unexpected Retry request.
Explanation: Unexpected Retry request. The server found an error while writing data to the server's data storage.
System Action: Client retries the operation.
User Response: None.

ANS1316E 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: ADSM ended the current operation.
User Response: This error is a temporary problem. Retry later or see your system administrator.

ANS1317E The server does not have enough database space to continue the current operation.
Explanation: The server ran out of database space.
System Action: ADSM ended the current operation.
User Response: See your system administrator.

ANS1318E The server does not have enough memory to continue the current operation.
Explanation: The server ran out of memory.
System Action: ADSM ended the current operation.
User Response: This is a temporary problem. Retry later or see your system administrator.

ANS1320E 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: ADSM canceled the current operation.
User Response: Check the file space name to see if it is correct, and retry the operation.

ANS1321S 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: ADSM canceled the current operation.
User Response: Retry with another node name.

ANS1322S 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: ADSM canceled the current operation.
User Response: See your system administrator.

ANS1323S Open Registration failed because an invalid node name was specified.
Explanation: Open registration failed because the specified node name contains invalid characters.
System Action: ADSM canceled the current operation.
User Response: Retry with another node name that does not have any invalid characters.

ANS1326S Unexpected Wait For Space from the server.
Explanation: The client received an unexpected Wait For Space message from the server.
System Action: ADSM ended the current operation.
User Response: See your system administrator.

ANS1329S Server out of data storage space.
Explanation: The server does not have space available to store the object.
System Action: ADSM ended the current operation.
User Response: Report to your system administrator that a storage pool on the server is full.

ANS1330S This node currently has a pending restartable restore session. The requested operation cannot complete until this session either completes or is canceled.
Explanation: This operation can not be completed because a restartable restore session is pending. The operation is not allowed because the restartable session and the current operation affect the same file space.
System Action: ADSM ended the current operation.
User Response: Issue a query restart to see the conflict. Issue the cancel restore command to delete any unneeded restartable restore sessions.

ANS1351E Session rejected: All server sessions are currently in use.
Explanation: ADSM has all available sessions in use and cannot accept a new one at this time.
System Action: ADSM 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 ADSM password has expired.
System Action: ADSM 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: ADSM 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 ADSM 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: ADSM cannot connect to the server. ADSM canceled the current operation.
User Response: If you are running a UNIX-based system, ensure that another process is not active with ADSM 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: ADSM 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 an ADSM 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: ADSM canceled the current operation.
User Response: See your system administrator to see what version of ADSM 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: ADSM canceled the current operation.
User Response: See your system administrator to see what version of ADSM 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 ADSM are exceeded.
See your system administrator.
Explanation: Adding a new enrollment will exceed the product license count for ADSM.
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.

ANS1367E Session Rejected: The server does not allow a signon as a Unicode enabled client.
Explanation: The client cannot 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 ADSM server administrator.
Explanation: The ADSM server administrator canceled the current client session.
System Action: Execution of the client connection request ends.
User Response: See your system administrator.

ANS1400E ADSM encounters a TLI error.
Explanation: ADSM 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.

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

ANS1402E TLI.DLL not found in search path.
Explanation: ADSM 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.

ANS1403E Error 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.

ANS1404E Error 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.

ANS1410E Unable 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.

ANS1411E A 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.

ANS1412E Directory 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.

ANS1425E Administrator authority is required to run ADSM Backup.
Explanation: The user attempting to run the backup client is not an administrator.
System Action: The client terminates.
User Response: Run the client from an administrative logon.

ANS1426E An error occurred creating the Backup Registry Directory structure.
Explanation: An error occurred while creating the directory structure to the save/replace registry key.
System Action: Registry function fails.
User Response: See your system administrator.

ANS1427I Registry Backup function completed successfully.
Explanation: Registry backup was successful.
System Action: None.
User Response: Continue with normal operations.

ANS1428E Registry Backup function failed.
Explanation: An error occurred while backing up the registry.
System Action: Registry backup function fails.
User Response: See your system administrator.

ANS1429I Registry Restore function completed successfully.
Explanation: Registry Restore was successful.
System Action: None.
User Response: Continue with normal operations.

ANS1430I The machine must be rebooted for the changes to take effect.
Explanation: The machine must be started for the restored registry changes to take effect.
System Action: None
User Response: Reboot the machine

ANS1431E Registry Restore Function Failed.
Explanation: An error occurred while restoring the registry key(s) from the server.
System Action: Registry restore function fails.
User Response: See your system administrator.

ANS1432E Keyword Expected after keyword keyword.
Explanation: A registry command was incorrectly entered.
System Action: Registry function is not invoked.
User Response: Refer to the command reference for this command.

ANS1433E Extraneous argument 'input' after keyword 'keyword'.
Explanation: A registry command was incorrectly entered.
System Action: Registry function not invoked.
User Response: Refer to the command reference for this command.

ANS1434E Invalid argument 'input' after keyword 'keyword'.
Explanation: A registry command was incorrectly entered.
System Action: Registry function not invoked.
User Response: Refer to the command reference for this command.

ANS1435E An Error Occurred saving the Key.
Explanation: The active registry key cannot be saved.
System Action: Registry backup operation terminates.
User Response: See your system administrator.

ANS1436E An Error Occurred replacing the Key.
Explanation: The backed up registry key is restored from the server but cannot be made active into the registry.
System Action: Current Registry key remains active.
User Response: See your system administrator.

ANS1450E APPC 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.

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

ANS1452E APPC 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.

ANS1453E APPC 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.

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

ANS1457E APPC 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.

ANS1458E APPC 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.

ANS1459E APPC resource error.
Explanation: The conversation ends prematurely.
System Action: Processing stops.
User Response: Exit ADSM and retry the ADSM command.

ANS1460E APPC security not valid.
Explanation: The conversation cannot be allocated because the access security is incorrect.
System Action: Processing stops.
User Response: Change the security in the APPC communication side information table.
User Response: Contact your support personnel.

ANS1461E APPC 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: ADSM defaults to no synchronization level. Contact your system administrator.

ANS1462E APPC TPN not recognized.
Explanation: ADSM 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 ADSM server is running.

ANS1463E APPC TP error.
Explanation: The ADSM 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.

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

ANS1465E APPC 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.

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

ANS1467E APPC 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.

ANS1468E The 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.

ANS1470E The 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.

ANS1471E PCSWIN 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: ADSM 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.

ANS1483I Schedule log pruning started.
Explanation: The schedule log pruning function has begun.
System Action: The schedule log is pruned.
User Response: None.

ANS1484I Schedule log pruning finished successfully.
Explanation: The schedule log pruning function completed with no errors.
System Action: None.
User Response: None.

ANS1485E Schedule log pruning failed.
Explanation: The schedule log pruning function failed.
System Action: The schedule log pruning function stops.
User Response: Retry the command with the tracing turned on to help determine why the pruning function failed.

ANS1500E Module dsmtca not found in secure directory.
Explanation: ADSM cannot find the Trusted Communication Agent module (dsmtca) in the appropriate directory.
System Action: ADSM ends.
User Response: Make sure the dsmtca module is in the proper directory (/etc/ADSM or /etc/security/ADSM). Reinstall the ADSM client if necessary.

ANS1501E Trusted agent execution/owner permissions are invalid.
Explanation: The Trusted Communication Agent execution/owner permissions are invalid.
System Action: ADSM 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 ADSM 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.

ANS1502E Access 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 ADSM client.
System Action: ADSM ends.
User Response: See your system administrator.

ANS1503E Valid password not available for server 'server-name'.
The ADSM administrator for your system must run ADSM 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: ADSM ends.
User Response: The ADSM 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: ADSM 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: ADSM ends.
User Response: Check the error log for more information. Retry the activity. If the problem persists, contact IBM customer support.

ANS1506E Trusted Communication Agent received invalid request.
Explanation: The Trusted Communication Agent has received an unknown request from the ADSM client.
System Action: ADSM ends.
User Response: Internal error. If the problem recurs, contact IBM customer support.

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

ANS1508E Error allocating semaphores.
Explanation: An error has occurred while attempting to allocate semaphores.
System Action: Processing ends.
User Response: Probable system error. If the problem persists, restart the workstation.

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.

ANS1512E Scheduled event 'event' failed. Return code = value.
Explanation: The scheduled event did not complete successfully.
System Action: Scheduled event failed.
User Response: Ensure that your environment is set up correctly. If the problem continues, see your system administrator to correct the problem.

ANS1802E Incremental backup of 'file-name' finished with number failure.
Explanation: The incremental backup of the specified file-name completed with the specified number of failures.
System Action: Processing continues.
User Response: Check the reasons for the failures.

ANS1803E Archive processing of 'file-space name' finished with failures.
Explanation: The archive of the specified file-space name completed with failures.
System Action: Processing continues.
User Response: Check the reasons for the failures.

ANS1804E Selective Backup processing of 'file-space name' finished with failures.
Explanation: The selective backup of the specified file-space name completed with failures.
System Action: Processing continues.
User Response: Check the reasons for the failures.

ANS1805E Unable to restore symbolic link 'file-name'.
Explanation: The client operating system is not able to create a symbolic link because the link points to a filename that is not given.
System Action: Processing continues.
User Response: Try the restore on a different operating system.

ANS1806W Size exceeded the maximum file size limit on your system
for 'filespace namepath-namefile-name' of 'file-size'.
Explanation: You tried to restore or retrieve a file that has exceeded the maximum file size limitation on your system.
System Action: ADSM cannot restore or retrieve the file.
User Response: Restore or retrieve this file on a system that supports the file size. See your system administrator.

ANS1807E Unable to recall file from server due to error from recall daemon.
Explanation: Unable to recall file. The recall daemon reported an error while trying to recall a file. Look in the recall daemon's error log for more information. This can happen if the server is down, the connection is broken, or the file is missing on the server. It is also possible that the migration server in the system option file has been changed to a different server. The recall daemon does not check the system option file for changes once it has started.
System Action: File skipped.
User Response: See if the ADSM server is up, and retry. If the problem still exists, look in the error log. Also have the workstation administrator run dsmreconcile against the file system and see if the file shows up in the .SpaceMan/orphan.stubs file. If system option file has been changed, stop all recall daemons and restart the master recall daemon to pick up the changes.

ANS1808E Invalid option/value for an interactive session: 'session'.
Explanation: You entered an option that cannot be used during an interactive session.
System Action: Processing stopped.
User Response: Quit out of the interactive session and try the option/value on the command line as you start the interactive session.

ANS1809E Session is lost; initializing session reopen procedure.
Explanation: The session with the server has been lost.
System Action: The system will attempt to reestablish session with ADSM.
User Response: None.

ANS1810E ADSM session has been reestablished.
Explanation: The session with the server has been reestablished.
System Action: Processing will now continue.
User Response: None.

ANS1811S ADSM session could not be reestablished.
Explanation: The session with the server has been lost. Attempts to reestablish the session were unsuccessful. Possible causes include, but are not limited to the following:

The ADSM server has been halted.
The network connection to the ADSM server is down.
The communication program that ADSM is interacting with has encountered some problem.

System Action: Processing is stopped.
User Response: Check network connection to the ADSM server. Insure that the ADSM server is running. Insure that the communication program underlying ADSM is working properly.

ANS1812E Out of storage.
Explanation: The system ran out of storage resources.
System Action: Processing stopped.
User Response: Free up extra storage to continue, and retry the operation.

ANS1813E Invalid scheduled command - 'command-name command-name command-name command-name'.
Explanation: You entered a command for schedule that is incorrect.
System Action: Processing stopped.
User Response: Enter the command correctly and retry the operation.

ANS1814E Unable to start scheduled event 'event'.
Explanation: Scheduled event was no longer valid on the server. Either the window has elapsed or the schedule has been deleted.
System Action: The client scheduler queries the server to obtain the next scheduled event.
User Response: If the problem continues, see your system administrator to correct the problem on the server.

ANS1815E Either the window has elapsed or the schedule has been deleted.
Explanation: Scheduled event was no longer valid on the server.
System Action: The client scheduler queries the server to obtain the next scheduled event.
User Response: If the problem continues, see your system administrator to correct the problem on the server.

ANS1816E Invalid scheduling mode.
Explanation: The mode entered for the scheduled event was not correct.
System Action: Event does not occur.
User Response: Enter the correct scheduling mode and retry the operation.

ANS1817E Schedule function can only be run by an ADSM authorized user.
Explanation: An attempt to use the schedule function failed because of improper authority.
System Action: Processing stopped.
User Response: See the ADSM authorized user for schedule function information.

ANS1818E Schedule function not allowed in loop mode.
Explanation: The operation cannot be scheduled during a loop mode.
System Action: Event does not occur.
User Response: Enter the command again without the loop.

ANS1819E Server cannot register address.
Explanation: An address for a server was entered that cannot be recorded.
System Action: Processing stopped.
User Response: Ensure that you have the server specified correctly, and retry the operation.

ANS1820E Command line options must be preceded by a '-'.
Explanation: An option was specified without a '-' delimiter.
System Action: Processing stopped.
User Response: Enter the command again with a dash preceding each option.

ANS1821E This platform does not support creating a new process.
Explanation: The requested action required a new process to be created. Either an option or a schedule "action" that requested an operating system command to be executed was entered.
System Action: Request is ignored.
User Response: Remove the request from the options file or the schedule defined on the server.

ANS1822S Option '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.

ANS1823E Invalid 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.
User Response: Correct the value. See the entry for TRACEFLAGS in the Trace Facility Guide document for a list of valid trace flags.

ANS1824E Invalid 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.

ANS1825E Unable 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.

ANS1826E Unable 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.

ANS1827E You 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.

ANS1828E Screen 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: ADSM 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.

ANS1830E Unable 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.

ANS1831E Password expired. The ADSM administrator for this system must run ADSM to update the password.
Explanation: The password expired.
System Action: ADSM ends.
User Response: The ADSM administrator for this system must update the password.

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

ANS1833S Unable to create 'directory-name' directory for storing passwords.
Explanation: ADSM 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.

ANS1834S Unable to write to 'file-name' for storing password.
Explanation: ADSM 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: ADSM prompts you for the password if ADSM is running in the foreground.
User Response: If ADSM was running as a background process, issue any ADSM command from the foreground. Enter the password in answer to the prompt. Then try your background ADSM command again.

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

ANS1837S File space filespace-name is ignored. Processing continues.
Explanation: The specified filespace-name in the system options file is invalid.
System Action: ADSM 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.

ANS1838E Error opening user specified options file 'filespace-name'.
Explanation: The specified options file-name could not be located or opened.
System Action: ADSM attempts to open default option file.
User Response: Make sure specified option file exists and is valid.

ANS1839E Cannot 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.

ANS1840E File 'file-namefile-namefile-name' changed during processing. File skipped.
Explanation: The specified file-name was skipped during backup, archive, or migrate because it was changing during the attempt to process it.
System Action: ADSM skipped the file.
User Response: If you want the file backed up, archived, or migrated retry the operation. If it fails, determine why the file is being changed. For more information on backing up, archiving, or migrating changing files, see your system administrator.

ANS1842S Session rejected: SNALU6.2 connection failure. CPIC unable to allocate conversation.
Explanation: ADSM client cannot allocate a CPIC conversation to the ADSM 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 ADSM server.
Explanation: An unexpected CPIC error occurred. There is a CPIC conversation type mismatch between the client and the ADSM 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: ADSM 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. ADSM cannot find the name of the ADSM server.
System Action: Processing stopped.
User Response: Ensure that you have the correct ADSM server name listed in your CPIC side information entry and that the ADSM server is running.

ANS1848S Session rejected: SNALU6.2 connection failure.
CPIC transaction program not available.
Explanation: CPIC transaction program not available. The ADSM server is not responding to the local program's request.
System Action: Processing stopped.
User Response: Ensure that the ADSM 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: ADSM 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 ADSM and retry the ADSM 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. ADSM received an incorrect return code from the deallocate verb. This error does not affect the ADSM 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.

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

ANS1861E Error loading the SNA Services/6000 CPIC routines.
Explanation: ADSM 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 ADSM SNA Services/6000 driver file, dsmsna.drv, exists in the ADSM installation directory.

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

ANS1868E Invalid Management Class 'management-class' found in the Include Exclude file.
Explanation: The management-class included in the Include Exclude file does not exist. See ADSM error log for more information.
System Action: Processing continued using the default Management Class.
User Response: Correct the Include Exclude file entry.

ANS1869E The NDS object requires its parent, or container, to be present before this object can be restored. Try first restoring the parent of this object.
Explanation: SMS requires the parent of the object (container) to be present before the child or object can be created.
System Action: Processing stops.
User Response: Retry restoring, at least one level up. For instance, restore 'dir\.o=ibm\*' instead of 'dir\ou=gpl.o=ibm\*'.

ANS1872E Unable to connect to NetWare target service 'server-name'.
Make sure the TSA NLM is loaded on the specified machine.
Explanation: ADSM interacts with the Target Service Agent (TSA) and the connection cannot be made to the Netware server-name.
System Action: Processing stopped.
User Response: Ensure that the TSA is loaded and retry the ADSM command.

ANS1874E Login denied to NetWare Target Service Agent 'server-name'.
Explanation: The connection to the Target Service Agent (TSA) requires a NetWare user name and a password. The password you entered at the prompt may be incorrect.
System Action: Processing stopped.
User Response: Retry the ADSM command, supplying the correct LAN password.

ANS1875E Unable to connect to target service. Out of memory.
Explanation: Not enough memory to connect to the Target Service Agent (TSA).
System Action: Processing stopped.
User Response: Either add memory to the server or free memory by unloading some programs, or by restarting the server.

ANS1876E Unable to connect to target service. NetWare SMS return code = value.
Explanation: Unexpected return code value.
System Action: Processing stopped.
User Response: See your service representative.

ANS1877E The name is too long for ADSM to process.
Explanation: The name was being parsed. The parsing routine detected that ADSM cannot process it.
System Action: ADSM canceled the current operation.
User Response: See your service representative if this error persists.

ANS1878I Changing User field from 'user name' to '*'.
Explanation: ADSM changed the user field during the set command. User field is not currently used by this program. It has been changed to the default name.
System Action: The set access continues to operate.
User Response: Continue with normal operations.

ANS1896I ***** Restored number objects *****.
Explanation: Indicates the number of objects ADSM has restored. During a restore session, the running total is periodically printed to the screen of a command line client.
System Action: Continue with restore.
User Response: None.

ANS1897I ***** Retrieved number objects *****.
Explanation: Indicates the number of objects ADSM has retrieved. During a retrieve session, the running total is periodically printed to the screen of a command line client.
System Action: Continue with retrieve.
User Response: None.

ANS1900W The archive description you specified is not unique. Please enter a unique archive description.
Explanation: Descriptions for archive files must be unique per archive operation.
System Action: Processing stopped.
User Response: Enter an archive description that is unique.

ANS1901W The server needs to do a one-time conversion of your archive data before you can continue. This operation may take a long time, and cannot be canceled once it has started. Are you willing to wait for the conversion to complete?
Explanation: The server must do a conversion of the archive date before continuing. The conversion could take a long time, and cannot be canceled once it is started.
System Action: Processing stopped; waiting for user intervention.
User Response: Answer 'Yes' to start the archive data conversion. If you answer 'No', the current operation will be canceled.

ANS1904E The 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.

ANS1905E NetWare SMS error processing 'filespace-namepath-namefile-name':
error-text.
Explanation: ADSM received an unexpected error from the Novell SMS interface.
System Action: Object skipped.
User Response: Report the program error to your service representative.

ANS1906I Destination must be specified for this operation when using FROMNODE.
Explanation: The user must specify a destination with a Restore/Retrieve command when using FROMNODE processing.
System Action: Processing stopped.
User Response: Retry the Restore/Retrieve command with a destination specified.

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