ANS1053I Existing filespace name filespace-name has been renamed to filespace-name.
Explanation: The existing filespace name using the volume label has been renamed to the UNC format naming convention.
System Action: Processing continues.
User Response: None.

ANS1054E Unable to rename existing filespace filespace-name to new filespace filespace-name.RC=retcode from cuFSUpd().
Explanation: Unable to rename the existing filespace name using the volume label to the UNC format naming convention.
System Action: Processing stopped.
User Response: None.

ANS1055I Trying to rename existing filespace filespace-name to new filespace filespace-name,
but drive letters do not match, old=drive-letter, new=drive-letter. Ignore the old filespace and backup to the new filespace.
Explanation: Trying to rename the existing filespace name using the volume label to the UNC format naming convention but the drive letters do not match. Leave the existing filespace alone and create a new filespace.
System Action: Processing continues.
User Response: None.

ANS1057I Trying to rename existing filespace filespace-name to new filespace filespace-name,
but both filespaces exist. Ignore the old filespace and backup tothe new filespace.
Explanation: Trying to rename the existing filespace name using the volume label to the UNC format naming convention but both filespaces exists. Leave the existing filespace alone and backup to the new filespace.
System Action: Processing continues.
User Response: None.

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

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 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 deleted the file before it could 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 machine.
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.

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.

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.

ANS1099E File 'filename' not previously archived.
Explanation: You tried to give access to a file, which is not stored on the server.
System Action: Processing stopped.
User Response: Ensure that the correct filename is specified.

ANS1100E File 'filename' not previously backed up.
Explanation: You tried to give access to a file, which is not stored on the server.
System Action: Processing stopped.
User Response: Ensure that the correct filename is specified.

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.

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

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.

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.

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.

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.

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.

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 or file system is skipped.
User Response: Check your system to ensure that it is operating properly. For OS/2, run CHKDSK /F for the failing drive which can be found in dsmerror.log.

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.

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.

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.

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.

ANS1331E Only an ADSM authorized user can perform this Action.
Explanation: User must be an ADSM authorized user to perform this action. User is not password authorized and this action requires authorization.
System Action: Processing stopped.
User Response: User must be root user, or user must be the owner of the executable and the set effective user id bit is set to 'on' ('s' bit).

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.

ANS1437I Event Log Backup function completed successfully.
Explanation: Event Log backup was successful.
System Action: None.
User Response: Continue with normal operations.

ANS1438E Event Log Backup function failed.
Explanation: An error occurred while backing up the event logs.
System Action: Event log backup function fails.
User Response: See your system administrator.

ANS1439I Event Log Restore function completed successfully.
Explanation: Event Log Restore was successful.
System Action: None.
User Response: Continue with normal operations.

ANS1440E Event Log Restore Function Failed.
Explanation: An error occurred while restoring the event log(s) from the server.
System Action: Event Log Restore function fails.
User Response: See your system administrator.

ANS1441E Keyword Expected after keyword 'keyword'.
Explanation: A event log command was incorrectly entered.
System Action: Event Log function is not invoked.
User Response: Refer to the command reference for this command.

ANS1442E Extraneous argument 'input' after keyword 'keyword'.
Explanation: A event log command was incorrectly entered.
System Action: Event Log function not invoked.
User Response: Refer to the command reference for this command.

ANS1443E Invalid argument 'input' after keyword 'keyword'.
Explanation: A event log command was incorrectly entered.
System Action: Event Log function not invoked.
User Response: Refer to the command reference for this command.

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

ANS1447I Current user does not need to back up the default profile.
Explanation: You are currently using the default profile, and there is no need to back it up.
System Action: None.
User Response: None.

ANS1448E An error occurred accessing NTFS security information.
Explanation: An error occurred while attempting to access NTFS security information.
System Action: Object will not be processed.
User Response: See your system administrator or bypass by using SkipNTSecurity option.

ANS1449E A required NT privilege is not held.
Explanation: The user account running ADSM does not possess a required NT user right/privilege for performing the current operation.
System Action: Object will not be processed.
User Response: See your system administrator.

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.

ANS1511W Invalid Restore session number entered.
Try again.
Explanation: You entered an invalid restore session number.
System Action: Processing stops.
User Response: Enter a correct restore session number, and try again.

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.

ANS1801E Unable to register the new ID with server. Unable to register the new ID with server.
Explanation: ADSM is unable to register the new ID with the server.
System Action: Processing stops.
User Response: Ask your system administrator to verify the new ID.

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 Unable to start POSTSCHEDULECMD/PRESCHEDULECMD 'command'.
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.

ANS1868E Invalid Management Class 'management-class' found in the Include Exclude file.
Explanation: The management-classincluded 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, but 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.

ANS1879E NetWare NDS error on restore processing:
**object 'nds_objectnds_object'
**TSA error 'tsa_error', tsa_error_text.
Explanation: ADSM received an unexpected error from the Novell TSA interface.
System Action: Object skipped.
User Response: Report the program error to your service representative.

ANS1880E TSA Connect error,
NWSMConnectToTargetService 'TSA_Target_Service'
password file 'password_file'.
Userid = 'NetWare_userid'
failed with cc = TSA_ccode.
Explanation: ADSM received an unexpected error from the Novell TSA interface while processing the userid and password from NWPWFILE.
System Action: If the failure is a 'Login Denied' the user will be prompted for a Novell NetWare Userid and Password, and a password file will be created.
User Response: The cc is returned from the TSA which belongs to Novell NetWare. If you get cc = FFFDFFD7 'Login Denied', please check the following:

The user-id has been disabled.

The user-id/password is invalid or expired.

The user-id has inadequate security access.

The user-id has insufficent rights to files and directorys.

The user-id specified has a login restriction based on time-0f-day.

The user-id specified has a Network address restriction.

The user-id specified has a login restriction based on number of concurrent connections.

NetWare is not allowing logins (DISABLE LOGIN was issued at the console).

If you are unable to determine what is wrong, report the problem to your service representative.

ANS1881E ADSM is unable to use NWPWFILE 'password_file' to connect TSA target service 'TSA_Target_Service', the file is corrupted.
Explanation: ADSM could not use the NWPWFILE to connect to Novell TSA interface. The file was corrupted.
System Action: User will be prompted for Novell NetWare Userid and Password, and password file will be created.
User Response: The file can be corrupted via another application or hardware failures. If problem is persistent contact your service representative. A copy of the corrupted password file will be needed. This corrupted file must be preserved before you enter a new userid and password, because ADSM will overwrite the corrupted file with correct information.

ANS1882W Unable to open NWPWFILE 'password_file' for TSA target service 'TSA_Target_Service'.
Explanation: ADSM could not open the NWPWFILE to connect to Novell TSA interface.
System Action: User will be prompted for Novell NetWare Userid and Password, and password file will be created.
User Response: This can be normal if you are using NWPWFILE for the first time and it does not exist. If the file does exist it may be locked and ADSM can not read it, determine why the file is locked. If the problem persists, report it to your service representative.

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

ANS1902I The archive conversion completed successfully.
Explanation: The archive conversion is completed successfully.
System Action: None.
User Response: None.

ANS1903I Waiting for archive conversion to complete...
Explanation: ADSM is waiting for the archive conversion to complete.
System Action: Processing continues.
User Response: None.

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.

ANS3000I communication-type communications available on port port-number.
Explanation: The specified communications are available on the specified port number.
System Action: None.
User Response: None.

ANS3001E Error initializing HTTPS communications - Secure HTTP not available.
Explanation: An error occurred initializing HTTPS communications. Processing will continue, but secure HTTP communications will not be available.
System Action: Proccessing continues, but secure HTTP communications will not be available.
User Response: Check the console and error logs to determine why secure HTTP communications was unable to start, correct the problem, and restart the client.

ANS3002I Session started for user userid (communication-method address).
Explanation: A session was started for the specified user.
System Action: None.
User Response: None.

ANS3003I Session ended for user userid.
Explanation: A session ended for the specified user.
System Action: None.
User Response: None.

ANS3004E Session for user userid terminated - invalid password entered.
Explanation: A session was terminated for the specified user because an invalid password was entered.
System Action: The session with the specified user is terminated.
User Response: Re-start the remote client and enter the correct password for the specified user.

ANS3005I Session for user userid terminated - idle for idle-minutes minutes.
Explanation: A session was terminated for the specified user because there was no activity on the session for the specified number of minutes.
System Action: The session with the specified user is terminated.
User Response: Re-start the remote client to begin a new session.

ANS3006I Processing request for the ADSM Web Client (ip-address).
Explanation: A request for the Web Client is being processed.
System Action: None.
User Response: None.

ANS3007I ADSM client-name terminating - idle for idle-minutes minutes.
Explanation: The specified client is terminating because it has been idle for the specified time. It will be automatically started when it is needed.
System Action: The client program stops.
User Response: None.