Messages


Chapter 3. Common and Platform Specific Messages (ANR0100-ANR9999)

This chapter contains the common and platform-specific server messages. The organization of the messages are grouped by the message prefix ANR and documented in ascending numeric order. If a message is platform specific and a duplicate, the appropriate platform name is added after the message number and it is also documented alphabetically by platform name.

ANR0100ESource file(line number): Error error code creating table "table name".

Explanation: An internal error has occurred in an attempt to create a server database table. This message always accompanies another error message and provides more detail about that error.

System Action: The activity that generated this error fails.

User Response: Contact your service representative.

ANR0101ESource file(line number): Error error code opening table "table name".

Explanation: An internal error has occurred in an attempt to access a server database table. This message always accompanies another error message and provides more detail about that error.

System Action: The activity that generated this error fails.

User Response: Contact your service representative.

ANR0102ESource file(line number): Error error code inserting row in table "table name".

Explanation: An internal error has occurred in an attempt to add data to a server database table. This message always accompanies another error message and provides more detail about that error.

System Action: The activity that generated this error fails.

User Response: Contact your service representative.

ANR0103ESource file(line number): Error error code updating row in table "table name".

Explanation: An internal error has occurred in an attempt to update data in a server database table. This message always accompanies another error message and provides more detail about that error.

System Action: The activity that generated this error fails.

User Response: Contact your service representative.

ANR0104ESource file(line number): Error error code deleting row from table "table name".

Explanation: An internal error has occurred in an attempt to remove data from a server database table. This message always accompanies another error message and provides more detail about that error.

System Action: The activity that generated this error fails.

User Response: Contact your service representative.

ANR0105ESource file(line number): Error setting search bounds for table "table name".

Explanation: An internal error has occurred in an attempt to access data in a server database table. This message always accompanies another error message and provides more detail about that error.

System Action: The activity that generated this error fails.

User Response: Contact your service representative.

ANR0106ESource file(line number): Unexpected error error code fetching row in table "table name".

Explanation: An internal error has occurred in an attempt to access data in a server database table. This message always accompanies another error message and provides more detail about that error.

System Action: The activity that generated this error fails.

User Response: Contact your service representative.

ANR0107WSource file(line number): Transaction transaction ID was not committed due to an internal error.

Explanation: An internal error was detected during transaction commit. This message should be preceded by another error message which provides more detail about that error.

System Action: The activity that generated this error fails.

User Response: Contact your service representative.

ANR0108ESource file(line number): could not start a new transaction.

Explanation: An error occurred while attempting to start a new transaction. Possibly there is not enough memory.

System Action: The activity that generated this error fails.

User Response: Allocate additional storage to the server. For details, issue HELP MEMORY to display the information online or see "Appendix A. Allocating Additional Server Memory".

ANR0110EAn unexpected system date has been detected; the server is disabled. Use the ACCEPT DATE command to establish the current date as valid.

Explanation: The server has noted that the current system date is suspect. It is earlier than the server install date or has suddenly moved into the future by 30 days or more.

System Action: The server is disabled for client access. Server expiration will not execute.

User Response: If the current system date is not valid, reset the date. Use the ACCEPT DATE command to establish the current date as valid on the server. After executing this command, you can use the ENABLE SESSIONS command to enable the server for client sessions.

ANR0130EDiagnosticID: Server LOG space exhausted.

Explanation: There is no space to write data to the server recovery log.

System Action: The activity that generated this error fails.

User Response: To increase the amount of log space available to the server, an authorized administrator can add log volumes by using the DEFINE LOGVOLUME command, and extend the size of the log by using the EXTEND LOG command.

ANR0131EDiagnosticID: Server DB space exhausted.

Explanation: There is no space to write data to the server database.

System Action: The activity that generated this error fails.

User Response: To increase the amount of database space available to the server, an authorized administrator can add database volumes by using the DEFINE DBVOLUME command, and extend the size of the database by using the EXTEND DB command.

ANR0132EDiagnosticID: Memory allocation failed: object object name, size size.

Explanation: The server cannot obtain enough memory to create the object named.

System Action: The activity that generated this error fails.

User Response: Allocate additional storage to the server. For details, issue HELP MEMORY to display the information online or see "Appendix A. Allocating Additional Server Memory".

ANR0200IRecovery log assigned capacity is size megabytes.

Explanation: The amount of space allocated to the recovery log is shown.

System Action: None.

User Response: None.

ANR0201IDatabase assigned capacity is size megabytes.

Explanation: The amount of space allocated to the database is shown.

System Action: None.

User Response: None.

ANR0202WDatabase volume volume name varied offline due to excessive read errors.

Explanation: The database volume shown has been varied offline because too many read errors have been encountered.

System Action: If available, a mirrored copy of the volume is used.

User Response: Correct the cause of the read errors.

ANR0203WDatabase volume volume name varied offline due to excessive write errors.

Explanation: The database volume shown has been varied offline because too many write errors have been encountered.

System Action: If available, a mirrored copy of the volume is used.

User Response: Correct the cause of the write errors.

ANR0204WRecovery log volume volume name varied offline due to excessive read errors.

Explanation: The recovery log volume shown has been varied offline because too many read errors have been encountered.

System Action: If available, a mirrored copy of the volume is used.

User Response: Correct the cause of the read errors.

ANR0205WRecovery log volume volume name varied offline due to excessive write errors.

Explanation: The recovery log volume shown has been varied offline because too many write errors have been encountered.

System Action: If available, a mirrored copy of the volume is used.

User Response: Correct the cause of the write errors.

ANR0206WPartial write detected on database volume volume name, logical page logical page number (physical page physical page number).

Explanation: During a write of a database page, an error occurred so that the page was not completely written to disk.

System Action: The failed I/O operation is retried on a mirrored volume.

User Response: See accompanying messages for information about the volume in error.

ANR0207EPage address mismatch detected on database volume volume name, logical page logical page number (physical page physical page number); actual: logical page number.

Explanation: During a read of a database page, the page does not contain the expected page address.

System Action: The failed I/O operation is retried on a mirrored volume.

User Response: See accompanying messages for information about the volume in error.

ANR0208WPartial write detected on recovery log volume volume name, logical page logical page number (physical page physical page number).

Explanation: During a write of a recovery log page, an error occurs so that the page is not completely written to disk.

System Action: The failed I/O operation is retried on a mirrored volume.

User Response: See accompanying messages for information about the volume in error.

ANR0209EPage address mismatch detected on recovery log volume volume name, logical page logical page number (physical page physical page number); actual: logical page number.

Explanation: During a read of a recovery log page, the page does not contain the expected page address.

System Action: The failed I/O operation is retried on a mirrored volume.

User Response: See accompanying messages for information about the volume in error.

ANR0210SInconsistency found in LVM data page page number - partial write detected.

Explanation: During a write of an LVM internal page, an error occurs so that the page is not completely written to disk.

System Action: The failed I/O operation is retried on a mirrored volume.

User Response: See accompanying messages for information about the volume in error.

ANR0211SInconsistency found in LVM data page page number - page address mismatch (actual page number).

Explanation: During a read of an LVM internal page, the page does not contain the expected page address.

System Action: The failed I/O operation is retried on a mirrored volume.

User Response: See accompanying messages for information about the volume in error.

ANR0212EUnable to read disk definition file file specification.

Explanation: At startup, the server cannot read the indicated file in order to obtain a list of disk volumes to mount.

System Action: Server initialization fails.

User Response: Use a text editor to recreate the file; it should contain one line with the name of a single log or database volume. Then restart the server.

ANR0213WUnable to rewrite disk definition file.

Explanation: An error occurs trying to update the disk definition file.

System Action: None.

User Response: Attempt to determine the cause of the write error and correct it.

ANR0214WDatabase volume volume name is in the offline state - VARY ON required.

Explanation: At system startup, the server finds that the specified database volume is in the offline state.

System Action: The volume is not accessed.

User Response: Determine the reason for the volume being offline; if possible, vary it online.

ANR0215WRecovery log volume volume name is in the offline state - VARY ON required.

Explanation: At system startup, the server finds that the recovery log volume shown is in the offline state.

System Action: The volume is not accessed.

User Response: Determine the reason for the volume being offline; if possible, vary it online.

ANR0216IDatabase volume volume name is in the "stale" state - synchronization process started.

Explanation: At system startup, the server finds that the database volume shown is not synchronized.

System Action: A process is started to synchronize the volume.

User Response: None.

ANR0217IRecovery log volume volume name is in the "stale" state - synchronization process started.

Explanation: At system startup, the server finds that the recovery log volume shown is not synchronized.

System Action: A process is started to synchronize the volume.

User Response: None.

ANR0218IUnable to install database volume volume name - capacity must be at least 5 megabytes.

Explanation: An attempt has been made to add a database volume that is smaller than the server minimum.

System Action: The volume is not added.

User Response: Increase the size of the volume or supply another larger volume.

ANR0219IUnable to install recovery log volume volume name - capacity must be at least 5 megabytes.

Explanation: An attempt has been made to add a recovery log volume that is smaller than the server minimum.

System Action: The volume is not added.

User Response: Increase the size of the volume or supply another larger volume.

ANR0220ISynchronization of database volume volume name started as process process ID.

Explanation: A background process was started to synchronize the contents of the database volume shown with its copy volume. The background process was assigned the process ID shown.

System Action: The background process starts to synchronize the volume and server operation continues.

User Response: The administrator may query the status of the background process by using the QUERY PROCESS command, or cancel the process by using the CANCEL PROCESS command.

ANR0221ISynchronization of recovery log volume volume name started as process process ID.

Explanation: A background process was started to synchronize the contents of the recovery log volume shown with its copy volume(s). The background process was assigned the process ID shown.

System Action: The background process starts to synchronize the volume and server operation continues.

User Response: The administrator may query the status of the background process by using the QUERY PROCESS command, or cancel the process by using the CANCEL PROCESS command.

ANR0222EError action disk definition file file specification.

Explanation: An error occurred creating or changing the disk definition file.

System Action: None.

User Response: Attempt to determine the cause of the write error and correct it.

ANR0223EError writing list of disks to disk definition file.

Explanation: The disk definition file cannot be written.

System Action: Installation ends.

User Response: Determine the cause of the write error and correct it.

ANR0224EVolume volume name is specified more than once - server installation failed.

Explanation: The specified volume name was specified more than once in the server installation execution.

System Action: Installation ends.

User Response: Reinitialize the server install specifying a unique name for each database and recovery log volume.

ANR0230ESynchronization process failed for database volume volume name.

Explanation: The process that was attempting to synchronize the database volume shown has failed.

System Action: The volume is in the stale state.

User Response: See accompanying messages for more information.

ANR0231ESynchronization process failed for recovery log volume volume name.

Explanation: The process that was attempting to synchronize the recovery log volume shown has failed.

System Action: The volume is in the stale state.

User Response: See accompanying messages for more information.

ANR0232ISynchronization process canceled for database volume volume name.

Explanation: The process that was attempting to synchronize the database volume shown has been canceled.

System Action: The volume is in the stale state.

User Response: If desired, issue a VARY ONLINE command to start another synchronize process.

ANR0233ISynchronization process canceled for recovery log volume volume name.

Explanation: The process that was attempting to synchronize the database volume shown has been canceled.

System Action: The volume is in the stale state.

User Response: If desired, issue a VARY ONLINE command to start another synchronize process.

ANR0234ISynchronization complete for database volume volume name.

Explanation: The synchronization process for the database volume named has finished successfully.

System Action: The volume is varied online.

User Response: None.

ANR0235ISynchronization complete for recovery log volume volume name.

Explanation: The synchronization process for the recovery log volume named has finished successfully.

System Action: The volume is varied online.

User Response: None.

ANR0240EDeletion process failed for database volume volume name.

Explanation: The process that was attempting to delete the database volume shown has failed.

System Action: The volume is not deleted.

User Response: See accompanying messages for more information.

ANR0241EDeletion process failed for recovery log volume volume name.

Explanation: The process that was attempting to delete the recovery log volume shown has failed.

System Action: The volume is not deleted.

User Response: See accompanying messages for more information.

ANR0242IDeletion process canceled for database volume volume name.

Explanation: The process that was attempting to delete the database volume shown has been canceled.

System Action: The volume is not deleted.

User Response: None.

ANR0243IDeletion process canceled for recovery log volume volume name.

Explanation: The process that was attempting to delete the recovery log volume shown has been canceled.

System Action: The volume is not deleted.

User Response: None.

ANR0244IDeletion complete for database volume volume name.

Explanation: The delete process for the database volume named has finished successfully.

System Action: The volume is deleted.

User Response: None.

ANR0245IDeletion complete for recovery log volume volume name.

Explanation: The delete process for the recovery log volume named has finished successfully.

System Action: The volume is deleted.

User Response: None.

ANR0246EError reading logical page logical page number (physical page physical page number) from database volume volume name.

Explanation: An error has been encountered when attempting to read a page from the specified database volume.

System Action: The failed I/O operation is retried on a mirrored volume, if available.

User Response: See accompanying messages for information about the volume in error. If the error persists and another mirrored copy of the volume is available, the failing volume should be taken offline by using the VARY OFF command, and repaired. Otherwise, halt the server and repair the volume. Then restart the server.

ANR0247IDatabase page logical page number successfully read from an alternate copy on volume volume name.

Explanation: After a read error, the server is able to read the desired page from another synchronized mirrored volume.

System Action: Processing continues.

User Response: None.

ANR0248EUnable to read database page logical page number from any alternate copy.

Explanation: After a read error, the server is unable to read the desired page from another mirrored volume because no other mirrored volume is in the synchronized state. This message is normally preceded by a message indicating which volume failed.

System Action: Processing is ended.

User Response: You can repair the failed volume by halting the server and correcting the volume errors.

ANR0249EError reading logical page logical page number (physical page physical page number) from recovery log volume volume name.

Explanation: An error has been encountered when attempting to read a page from the specified recovery log volume.

System Action: The failed I/O operation is retried on a mirrored volume, if available.

User Response: See accompanying messages for information about the volume in error. If the error persists and another mirrored copy of the volume is available, the failing volume should be taken offline, by using the VARY OFF command, and repaired.

ANR0250IRecovery log page logical page number successfully read from an alternate copy on volume volume name.

Explanation: After a read error, the server is able to read the desired page from another synchronized mirrored volume.

System Action: Processing continues.

User Response: None.

ANR0251EUnable to read recovery log page logical page number from any alternate copy.

Explanation: After a read error, the server is unable to read the desired page from another mirrored volume because no other mirrored volume was in the synchronized state. This message is normally preceded by a message indicating which volume failed.

System Action: Processing is ended.

User Response: You can repair the failed volume by halting the server and correcting the volume errors.

ANR0252EError writing logical page logical page number (physical page physical page number) to database volume volume name.

Explanation: An error has been encountered when attempting to write a page to the specified database volume.

System Action: If a mirrored volume is available then the failing volume is forced into the offline state.

User Response: Repair the failing volume, and then use the VARY ON command to bring the volume back online.

ANR0253EUnable to write database page logical page number to any alternate copy.

Explanation: After a write error, the server is unable to write the desired page to another mirrored volume because no other mirrored volume is in the synchronized state. This message is normally preceded by a message indicating which volume failed.

System Action: Processing is ended.

User Response: Repair the failed volume.

ANR0254EError writing logical page logical page number (physical page physical page number) to recovery log volume volume name.

Explanation: An error has been encountered when attempting to write a page to the specified recovery log volume.

System Action: If a mirrored volume is available, the failing volume is forced into the offline state.

User Response: Repair the failing volume, and then use the VARY ON command to bring the volume back online.

ANR0255EUnable to write recovery log page logical page number to any alternate copy.

Explanation: After a write error, the server is unable to write the desired page to another mirrored volume because no other mirrored volume is in the synchronized state. This message is normally preceded by a message indicating which volume failed.

System Action: Processing is ended.

User Response: You can repair the failed volume by halting the server and correcting the volume errors.

ANR0256EError writing physical page physical page number to restart/checkpoint area on database volume volume name.

Explanation: An error has been encountered when attempting to write a page to the specified database volume.

System Action: If a mirrored volume is available, the failing volume is forced into the offline state.

User Response: Repair the failing volume, and then use the VARY ON command to bring the volume back online.

ANR0257EError writing physical page physical page number to restart/checkpoint area on recovery log volume volume name.

Explanation: An error has been encountered when attempting to write a page to the specified database volume.

System Action: If a mirrored volume is available, the failing volume is forced into the offline state.

User Response: Repair the failing volume, and then use the VARY ON command to bring the volume back online.

ANR0258EUnable to write complete restart/checkpoint information to disk.

Explanation: While writing restart/checkpoint information to disk, the server encounters an error writing to a database or recovery log volume for which no synchronized mirrored copy is available. This message is normally preceded by a message indicating which volume failed.

System Action: Processing is ended.

User Response: Repair the failing volume.

ANR0259EUnable to read complete restart/checkpoint information from any database or recovery log volume.

Explanation: During server restart, the server is unable to read a complete set of restart/checkpoint information from any of the defined database or recovery log volumes.

System Action: Server restart is ended.

User Response: Ensure that all defined database and recovery log volumes are available for use by the server.

ANR0260IDatabase page logical page number successfully resynchronized.

Explanation: After detecting a partially-written database page, the server is able to rewrite the page by using a synchronized mirror copy.

System Action: Processing continues.

User Response: None.

ANR0261IRecovery log page logical page number successfully resynchronized.

Explanation: After detecting a partially-written recovery log page, the server is able to rewrite the page by using a synchronized mirror copy.

System Action: Processing continues.

User Response: None.

ANR0265ELog disk processing failed: sufficient memory is not available.

Explanation: At server installation, the server is unable to process the server log disks due to insufficient memory.

System Action: Server installation stops.

User Response: Restart the server installation process with more memory available.

ANR0266EDatabase disk processing failed: sufficient memory is not available.

Explanation: At server installation, the server is unable to process the server database disks due to insufficient memory.

System Action: Server installation stops.

User Response: Restart the server installation process with more memory available.

ANR0267ELog volume volume name is not available.

Explanation: The specified volume cannot be found during installation.

System Action: Server installation stops.

User Response: Determine the reason the disk is unavailable, and correct the problem. Restart the server installation process.

ANR0268EDatabase volume volume name is not available.

Explanation: The specified volume cannot be found during installation.

System Action: Server installation stops.

User Response: Determine the reason the disk is unavailable, and correct the problem. Restart the server.

ANR0269EProcess for Log volume volume name terminated - thread resource not available.

Explanation: During installation for the indicated volume, the server cannot start a thread to service I/O requests.

System Action: Server installation stops.

User Response: Allocate additional storage to the server. For details, issue HELP MEMORY to display the information online or see "Appendix A. Allocating Additional Server Memory". Restart the server installation process.

ANR0270EProcess for Database volume volume name terminated - thread resource not available.

Explanation: During installation for the indicated volume, the server cannot start a thread to service I/O requests.

System Action: Server installation stops.

User Response: Allocate additional storage to the server. For details, issue HELP MEMORY to display the information online or see "Appendix A. Allocating Additional Server Memory". Restart the server installation process.

ANR0271EMaximum number of recovery log volumes exceeded.

Explanation: More recovery log volumes have been specified than the server can manage.

System Action: Server installation stops.

User Response: Reduce the number of recovery log volumes specified. Restart the server installation process.

ANR0272EMaximum number of database volumes exceeded.

Explanation: More database volumes have been specified than the server can manage.

System Action: Server installation stops.

User Response: Reduce the number of database volumes specified. Restart the server installation process.

ANR0285IDatabase page shadowing started using file file name.

Explanation: The database page shadowing function was started. The file specified is used to store the shadowed database pages.

System Action: None.

User Response: None.

ANR0286WDatabase page shadowing using file file name failed to start.

Explanation: The database page shadowing function could not start. An error has been encountered accessing the page shadow file specified.

System Action: None.

User Response: Verify that there is enough space for the page shadow file. That page shadow file requires approximately 65 kilobytes of space, if this space is not available a new location for the file should be specified.

ANR0287WContents of the page shadow file file name are not valid.

Explanation: The database page shadowing function could not use the contents of the existing file. Restart recovery using this file is not possible.

System Action: The server attempts to start without having the database page shadow file available.

User Response: The database page shadow file contents are not valid. This can be caused by: a partial write to the page shadow file itself, the file being manipulated by a process outside of the server, the file being overlayed by a different file, or the file could have been erased.

ANR0288WOne or more database pages in the last batch written is corrupt - contents of database page shadow file will be used to fix the page or pages.

Explanation: One or more pages from the last batch of pages written to the server database has been detected to be corrupt. The server will attempt to use the contents of database page shadow file and replace the corrupted database page.

System Action: Server startup continues.

User Response: A corruption of a database page within the server database, is typically caused by a partial write. A partial write may occur when the server is brought down external to normal server processing. If the server terminated without a halt command being issued or if the machine the server is running on crashed unexpectedly, this may account for the partial write. Other possible causes of a partial write are a disk drive failure, improperly terminated scsi bus, or a failure in a device controller. Please try to identify the cause of the partial write and take the appropriate action to prevent this from occurring in the future.

ANR0289WDamaged database pages were successfully replaced using contents of page shadow file.

Explanation: The damaged database pages were replaced using the corresponding pages from the page shadow file. The pages were successfully replaced.

System Action: The server continues to restart.

User Response: None.

ANR0290WFailure occurred attempting to replace one or more damaged database pages using the contents of the page shadow file.

Explanation: The damaged database pages could not be replaced using the corresponding pages from the page shadow file.

System Action: The server continues to restart.

User Response: None.

ANR0291EError writing to db page shadow file - restart will be attempted.

Explanation: The server encountered an error writing to the database page shadow file. The page shadowing for the server is currently disabled.

System Action: The server will attempt to restart the database page shadowing for the server once a minute until it is restarted or until the server is halted.

User Response: Check the file specified as the database page shadow file. It may be that there is not enough space for the file. If enough space is available, check the filesystem, drive, or disk that it resides on for an indication of the error. Once the error preventing the server from writing to the page shadow file has been resolved, the server will recovery and begin writing to the page shadow file again.

ANR0292WDatabase page shadow file file name does not exist.

Explanation: The server attempted to use the page shadow file referenced but was unable to open the file. The file does not exist.

System Action: The server will continue to operate and will attempt to create this as a new database page shadow file.

User Response: None.

ANR0300IRecovery log format started; assigned capacity count megabytes.

Explanation: Initial formatting of the server recovery log has started.

System Action: The log is formatted for use by the server.

User Response: None.

ANR0301IRecovery log format in progress; count megabytes of count.

Explanation: The amount of the server recovery log shown has been successfully formatted.

System Action: Formatting continues.

User Response: None.

ANR0302IRecovery log formatting took mseconds milliseconds.

Explanation: Formatting of the recovery log has completed and took the number of milliseconds shown.

System Action: None.

User Response: None.

ANR0303IFormat rate: rate pages/second.

Explanation: During formatting, the formatter processed the number of pages indicated each second.

System Action: None.

User Response: None.

ANR0304IPage service time: rate ms.

Explanation: During formatting, the formatter required the number of milliseconds indicated to process each page.

System Action: None.

User Response: None.

ANR0305IRecovery log format complete.

Explanation: Formatting of the server recovery log completed successfully.

System Action: None.

User Response: None.

ANR0306IRecovery log volume mount in progress.

Explanation: During restart, the server is mounting required recovery log volumes.

System Action: None.

User Response: None.

ANR0307IRecovery log extend in progress; count megabytes of count formatted.

Explanation: As a result of an EXTEND LOG command, the additional recovery log pages are being formatted.

System Action: Formatting continues.

User Response: None.

ANR0309IRecovery log extend terminated - process canceled.

Explanation: The process started as a result of an EXTEND LOG command and has been canceled.

System Action: The EXTEND command is ended.

User Response: None.

ANR0311IRecovery log reduce in progress; count megabytes of count moved.

Explanation: As a result of a REDUCE LOG command, the amount of data from the recovery log shown has been moved.

System Action: The REDUCE LOG command continues.

User Response: None.

ANR0313IRecovery log reduce terminated - process canceled.

Explanation: The process started as a result of a REDUCE LOG command and has been canceled.

System Action: The REDUCE command is ended.

User Response: None.

ANR0314WRecovery log usage exceeds utilization percentage % of its assigned capacity.

Explanation: This message is issued to notify the administrator that the server recovery log utilization exceeds 90% or more of its assigned capacity.

System Action: Server operation continues.

User Response:

ANR0350IRecovery checkpoint started.

Explanation: During server initialization, the process of bringing the server database back to a state of consistency has begun.

System Action: None.

User Response: None.

ANR0351IRecovery checkpoint complete.

Explanation: During server initialization, the process of bringing the server database back to a state of consistency has completed successfully.

System Action: None.

User Response: None.

ANR0352ITransaction recovery complete.

Explanation: During server initialization, the process of recovering any incomplete transactions has completed successfully.

System Action: None.

User Response: None.

ANR0353IRecovery log analysis pass in progress.

Explanation: During server initialization, the process of analyzing the server recovery log has begun.

System Action: None.

User Response: None.

ANR0354IRecovery log redo pass in progress.

Explanation: During server initialization, the process of committing incomplete transactions has begun.

System Action: None.

User Response: None.

ANR0355IRecovery log undo pass in progress.

Explanation: During server initialization, the process of rolling back incomplete transactions has begun.

System Action: None.

User Response: None.

ANR0356IRecovery log compression started.

Explanation: The process of removing unneeded data from the server recovery log has begun.

System Action: None.

User Response: None.

ANR0357IRecovery log compression ended.

Explanation: The process of removing unneeded data from the server recovery log has completed.

System Action: None.

User Response: None.

ANR0358EDatabase initialization failed: sufficient memory is not available.

Explanation: During server initialization, the server database fails initialization because sufficient server memory is not available.

System Action: Initialization fails.

User Response: Make more memory available to the server.

ANR0359EDatabase initialization failed: unable to read database restart record.

Explanation: During server initialization, the server database initialization fails because the required restart record cannot be read.

System Action: Initialization fails.

User Response: Contact your service representative.

ANR0360EDatabase initialization failed: database size mismatch; LVM size = size, expected size = size.

Explanation: During server initialization, the server database initialization fails because the size of the database does not match its prior size.

System Action: Initialization fails.

User Response: Contact your service representative.

ANR0361EDatabase initialization failed: error initializing database page allocator.

Explanation: During server initialization, the server database initialization fails because the page allocator cannot be started.

System Action: Initialization fails.

User Response: Contact your service representative.

ANR0362WDatabase usage exceeds utilization percentage % of its assigned capacity.

Explanation: This message is issued to notify the administrator that the server database utilization exceeds 80% or more of its assigned capacity.

System Action: Server operation continues.

User Response: Depending upon the size of your database, add database volumes, or extend the database, or both, before it fills completely. The server expiration process may also free up database space making it available to other server processes. Refer to the EXPIRE INVENTORY, DEFINE DBVOL, and EXTEND DB commands for more information on these operations.

ANR0363IDatabase was automatically upgraded to the server program level.

Explanation: This message is issued to notify the administrator that the server database was automatically upgraded to the current server program level. The upgrade is performed when the UPGRADEDB parameter is specified at server start-up and the server is started over a database that was written by a down-level version of the server program.

System Action: Server operation continues.

User Response: None. The UPGRADEDB parameter does not need to be specified during future server start-ups.

ANR0380WThe database buffer pool recovered from an overcommit of number of pages pages. Consider increasing your buffer pool size by kilobytes needed kilobytes under current server load.

Explanation: During normal processing, additional buffer pool space is required beyond that specified in the BUFPOOLSIZE in the server options file. The additional kilobytes of buffer pool space that are required are indicated in the message.

System Action: Server operation continues; the additional buffer pool space is obtained from available server memory.

User Response: If the current server load is typical, consider increasing the size specified for your BUFPOOLSIZE option by the number of kilobytes specified in the message. To do this, you must halt the server, change the options file, and then restart the server.

ANR0381IBufferpool statistics were successfully reset.

Explanation: Bufferpool statistics, such as the Cache Hit Ratio, have been reset by the RESET BUFPOOL command.

System Action: Server operation continues.

User Response: The QUERY DB command (FORMAT=DETAILED) can be used to to display the current values for the buffer pool statistics.

ANR0382IThe database maximum utilization statistic was successfully reset.

Explanation: The database maximum utilization statistic has been reset by the RESET DBMAXUTILIZATION command to the current utilization.

System Action: Server operation continues.

User Response: The QUERY DB command (FORMAT=DETAILED) can be used to display the current value for the maximum utilization.

ANR0383IThe recovery log maximum utilization statistic was successfully reset.

Explanation: The recovery log maximum utilization statistic has been reset by the RESET LOGMAXUTILIZATION command to the current utilization.

System Action: Server operation continues.

User Response: The QUERY LOG command (FORMAT=DETAILED) can be used to display the current value for the maximum utilization.

ANR0384IThe recovery log consumption statistic was successfully reset.

Explanation: The recovery log consumption statistic has been reset by the RESET LOGCONSUMPTION command.

System Action: Server operation continues.

User Response: The QUERY LOG command (FORMAT=DETAILED) can be used to display the current value for recovery log consumption.

ANR0385ICould not free sufficient buffers to reach reduced BUFPoolsize.

Explanation: A reduction in the Data Base buffer pool size was requested. However, too many buffers were in use to reach the lower buffer pool size.

System Action: Server operation continues. Whatever buffer pool size reduction that could be achieved is in effect. The new bufpoolsize is written to the options file for use on the next server startup.

User Response: None.

ANR0386IThe BUFPoolsize has been changed to buffer pool size.

Explanation: The BUFPoolsize option has been changed to the indicated value.

System Action: Server operation continues.

User Response: None.

ANR0390WA server database deadlock situation has been encountered: lock request for transaction transaction ID will be denied to resolve the deadlock.

Explanation: The server detected a deadlock situation between a number of processes attempting to access database information. A lock request for one of the processes will be denied to resolve the database deadlock. When server processes encounter a database deadlock, they usually reattempt the function that was in progress when the deadlock was encountered. Not all process can explicitly re-try an operation. For example, migration and reclamation will eventually retry. However, something like a delete volume run in a macro will only retry if the delete command is reissued either in the macro or the command line.

System Action: A lock request fails for one of the deadlocked processes. Server operation continues.

User Response: If a process can retry (like migration), then monitor the re-try attempt to see if it succeeds or not. If it fails, contact a service representative. If the process or command is not able to retry on it's own, then reissue the command or macro that caused the action to occur. If it fails again, contact a service representative for further assistance to better isolate the deadlock condition.

ANR0400ISession session number started for node node name (client platform) (communication method).

Explanation: A new client session has been initiated by the specified node. The session number, client platform type and communication method used by this session are included in the message.

System Action: The server begins a communications session to service the client node.

User Response: None.

ANR0401ISession session number started for node node name (client platform) (communication method) (WDSF client).

Explanation: A new WDSF client session has been initiated by the specified node. The session number, client platform type and communication method used by this session are included in the message.

System Action: The server begins a communications session to service the client node.

User Response: None.

ANR0402ISession session number started for administrator administrator ID (administrator's platform) (communication method).

Explanation: A new administrator client session has been initiated by the specified administrator. The session number, administrator's platform type and communication method used by this session are included in the message.

System Action: The server begins a communications session to service the administrator client.

User Response: None.

ANR0403ISession session number ended for node node name (client platform).

Explanation: A client session has completed normally.

System Action: Server operation continues.

User Response: None.

ANR0404ISession session number ended for node node name (client platform) (WDSF client).

Explanation: A WDSF client session has completed normally.

System Action: Server operation continues.

User Response: None.

ANR0405ISession session number ended for administrator administrator ID (client platform).

Explanation: An administrative client session has completed normally.

System Action: Server operation continues.

User Response: None.

ANR0406ISession session number started for node node name (client platform) (communication method communication address).

Explanation: A new client session has been initiated by the specified node. The session number, client platform type, communication method and address used by this session are included in the message.

System Action: The server begins a communications session to service the client node.

User Response: None.

ANR0407ISession session number started for administrator administrator ID (administrator's platform) (communication method communication address).

Explanation: A new administrator client session has been initiated by the specified administrator. The session number, administrator's platform type, communication method and address used by this session are included in the message.

System Action: The server begins a communications session to service the administrator client.

User Response: None.

ANR0408ISession session number started for server server name (server's platform) (communication method) for purpose.

Explanation: A new server session has been initiated by the specified server for the specified purpose. The session number, server's platform type and communication method used by this session are included in the message.

System Action: The server begins a communications session to service the administrator client.

User Response: None.

ANR0409ISession session number ended for server server name (client platform).

Explanation: A server has completed normally.

System Action: Server operation continues.

User Response: None.

ANR0418WSession session number for administrator administrator name (client platform) refused - invalid password submitted.

Explanation: The server refuses a request to start a client session because an invalid password has been submitted by the client during sign-on processing. The server will continue to deny access attempts by this client until a valid password is submitted.

System Action: Server operation continues.

User Response: Enter the proper password. If the password has been forgotten by the user, an authorized administrator can assign a new password by using the UPDATE ADMIN command.

ANR0419WAdministrative client userid administrative ID cannot be used when authentication is on.

Explanation: The server refuses a request for a client (administrative) session because the user ID specified cannot be used when authentication of IDs is in effect. SERVER_CONSOLE is an administrative ID that has this restriction.

System Action: Server operation continues.

User Response: Use an administrative ID that was registered for this server and that has a password.

ANR0420WSession session number for node node name (client platform) refused - server disabled for user access.

Explanation: The server refuses a request for a client (backup-archive) session because the server is currently disabled for client access.

System Action: Server operation continues. Administrative clients are permitted access to the server.

User Response: An authorized administrator must issue the ENABLE command before client nodes are permitted access to the server.

ANR0421WSession session number for node node name (client platform) refused - sign-on protocol violation.

Explanation: The server refuses a request for a client session because sign-on protocol has been violated.

System Action: Server operation continues.

User Response: This error is usually the result of a client programming error in which the sign-on verb has been incorrectly formatted and delivered to the server. This error can also result when the server is contacted by an application that is not a part of this product.

ANR0422WSession session number for node node name (client platform) refused - node name not registered.

Explanation: The server refuses a request to start a client session because the client node name is not registered in the server database.

System Action: Server operation continues.

User Response: Register the node name with the server before establishing a session. If the server is running with OPEN registration, no action is required; the client prompts the user for a password and registers the client with the server. If CLOSED registration is in effect on the server, an authorized administrator must use the REGISTER NODE command to register the client node name with the server.

ANR0423WSession session number for administrator administrator ID (client platform) refused - administrator name not registered.

Explanation: The server refuses a request to start an administrative session because the administrator name is not registered in the server database.

System Action: Server operation continues.

User Response: Register the administrator name with the server before establishing a session. An authorized administrator must use the REGISTER ADMIN command to register the administrator with the server.

ANR0424WSession session number for node node name (client platform) refused - invalid password submitted.

Explanation: The server refuses a request to start a client session because an invalid password has been submitted by the client during sign-on processing. The server will continue to deny access attempts by this client until a valid password is submitted.

System Action: Server operation continues.

User Response: Enter the proper password. If the password has been forgotten by the user, an authorized administrator can assign a new password by using the UPDATE NODE command.

ANR0425WSession session number for node node name (client platform) refused - password has expired.

Explanation: The server refuses the specified session because the administrator or client node's password has expired.

System Action: Server operation continues.

User Response: Upon receipt of this error condition, the client program immediately reconnects to the server specifying a password update session and prompts the user for a new password. After the user enters a new password, the client reconnects to the server for normal operations. Alternatively, an authorized administrator can update the client password using the UPDATE NODE or UPDATE ADMIN command.

ANR0426WSession session number for node node name (client platform) refused - open registration not permitted.

Explanation: The server refuses a client session because an open registration action has been attempted and the server is running with CLOSED registration.

System Action: Server operation continues.

User Response: Ask an authorized administrator to submit the request using the REGISTER NODE or REGISTER ADMIN command.

ANR0427WSession session number for node node name (client platform) refused - server version is down-level with this client.

Explanation: The server refuses a client session because the client program version level is newer than that supported by the server program.

System Action: Server operation continues.

User Response: Apply service to the server program to make it compatible with the newer client program, or use an older client program to contact the server.

ANR0428WSession session number for node node name (client platform) refused - client is down-level with this server version.

Explanation: The server refuses a client session because the client program version level is older than that supported by the server program. For certain problems (such as the compression fix), once a node connects to the server using the newer client, the server records this fact and will not let this node back off this client version to a version that does not include the fix.

System Action: Server operation continues.

User Response: Apply service to the client program to make it compatible with the newer server program.

ANR0429WSession session number for node node name (client platform) refused - maximum server sessions (max sessions allowed) exceeded.

Explanation: The server refuses the specified client or administrative session because the maximum number of concurrent client sessions has been exceeded.

System Action: Server operation continues.

User Response: If necessary, increase the maximum number of permitted sessions. To do this, update the value for the MAXSESSIONS parameter in the server options file and restart the server with the updated options file. Note that increasing the MAXSESSIONS value requires additional memory resource by the server. You may want to retry the connection at a later time.

ANR0430WSession session number for node node name (client platform) refused - node name is locked.

Explanation: The server refuses the specified client session because the node is locked from server access (with the LOCK NODE command).

System Action: Server operation continues.

User Response: Before the client node is permitted to access the server, a properly authorized administrator must unlock the node with the UNLOCK NODE command.

ANR0431WSession session number refused - administrator administrator ID (client platform) is locked.

Explanation: The server refuses the specified administrative session because the administrator is locked from server access (with the LOCK ADMIN command).

System Action: Server operation continues.

User Response: Before the administrator is permitted to access the server, a properly authorized administrator must unlock the administrator with the UNLOCK ADMIN command.

ANR0432WSession session number for node node name (client platform) refused - insufficient memory.

Explanation: The server ends the specified session because sufficient memory (virtual memory) is not available.

System Action: The server ends the session and continues operation.

User Response: Allocate additional storage to the server. For details, issue HELP MEMORY to display the information online or see "Appendix A. Allocating Additional Server Memory".

ANR0433WSession session number for node or administrator ID (client platform) refused - insufficient recovery log space.

Explanation: The server ends the specified client or administrative session because sufficient log space is not available to complete a database transaction.

System Action: The server ends the session and continues operation.

User Response: To increase the amount of log space available to the server, an authorized administrator can add log volumes using the DEFINE LOGVOLUME command, and extend the size of the log using the EXTEND LOG command.

ANR0434WSession session number for node or administrator ID (client platform) refused - insufficient database space.

Explanation: The server ends the specified client or administrative session because sufficient database space is not available to complete a database transaction.

System Action: The server ends the session and continues operation.

User Response: To increase the amount of database space available to the server, an authorized administrator can add database volumes using the DEFINE DBVOLUME command, and extend the size of the database using the EXTEND DB command.

ANR0435WSession session number for node node name (client platform) refused - internal error detected.

Explanation: The server ends the specified session because an internal logic error is detected.

System Action: The server ends the session and continues operation.

User Response: To determine the source of the error, the administrator can examine server messages issued prior to this message. The QUERY ACTLOG command can be used to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative.

ANR0436WSession session number refused - a WDSF client is attempting to access the server using client name client node name (client platform), associated with a non-WDSF client.

Explanation: The server refuses a client session because a Workstation DataSave Facility (WDSF) client is attempting to access the server using a node name associated with a non-WDSF client. When converting from WDSF, WDSF client programs cannot be used to access the server with a specific node name once the non-WDSF client program has been used to access the server with that node name.

System Action: Server operation continues.

User Response: Access the server using a non-WDSF client program for the node name.

ANR0437WSession session number for node client node name (client platform) encountered an internal server error while checking license compliance.

Explanation: The server encountered an internal error in determining if the server is in compliance with license terms.

System Action: The client session is ended.

User Response: Use the QUERY LICENSE and QUERY STATUS commands to determine if the server is in compliance with license terms. Start an AUDIT LICENSES process to re-adjust server license information. When this process completes you may restart the session. If the problem persists, contact your service representative.

ANR0438WSession session number archive operation for client client node name (client platform) has been denied - Server is not in compliance with license terms.

Explanation: The server refuses a client archive operation because the current server configuration is not in compliance with license terms.

System Action: Server operation continues. Clients may perform any action except backup or archive.

User Response: Use the QUERY LICENSE command to determine the license terms that are no longer in compliance.

ANR0439WSession session number backup operation for client client node name (client platform) has been denied - Server is not in compliance with license terms.

Explanation: The server refuses a client backup operation because the current server configuration is not in compliance with license terms.

System Action: Server operation continues. Clients may perform any action except backup or archive.

User Response: Use the QUERY LICENSE command to determine the license terms that are no longer in compliance.

ANR0440WProtocol error on session session number for node client node name (client platform) - invalid verb header received.

Explanation: The server detects a protocol error on the specified session because an invalid verb header has been received from the client. Verb headers always precede communication sent to the server from the client or from the server to the client.

System Action: The server ends the client session.

User Response: Correct the programming error in the client program if it has been written by your installation using WDSF verbs. Otherwise, contact your service representative.

ANR0441WProtocol error on session session number for node client node name (client platform) - invalid data length received.

Explanation: The server detects a protocol error on the specified session because an invalid verb length has been received from the client.

System Action: The server ends the client session.

User Response: Correct the programming error in the client program if it has been written by your installation using WDSF verbs. Otherwise, contact your service representative.

ANR0442WProtocol error on session session number for node client node name (client platform) - excessively large verb received.

Explanation: The server detects a protocol error on the specified session because an invalid verb length has been received from the client.

System Action: The server ends the client session.

User Response: Correct the programming error in the client program if it has been written by your installation using WDSF verbs. Otherwise, contact your service representative.

ANR0443WProtocol error on session session number for node client node name (client platform) - invalid "field name" field found in "verb name" verb (offset offset position).

Explanation: The server detects a protocol error on the specified session because an invalid field has been found in a verb sent from the client node.

System Action: The server ends the client session.

User Response: Correct the programming error in the client program if it has been written by your installation using WDSF verbs. Otherwise, contact your service representative.

ANR0444WProtocol error on session session number for node client node name (client platform) - out-of-sequence verb (type verb name) received.

Explanation: The server detects a protocol error on the specified session because a verb has been received that does not adhere to the client-server exchange sequence.

System Action: The server ends the client session.

User Response: If the client generating the error is not an API client, contact your service representative. If the client generating the error is an API client, contact the owner of the API client. If the client generating the error is a client that you have created using WDSF verbs, correct the programming error in your client program.

ANR0445WProtocol error on session session number for node client node name (client platform) - maximum group transaction size exceeded.

Explanation: The server detects a protocol error on the specified session because the client has attempted to group more than the maximum database update operations in a single database transaction.

System Action: The server ends the client session.

User Response: Correct the programming error in the client program if it has been written by your installation using WDSF verbs. Otherwise, contact your service representative.

ANR0446WSession session number client client node name compression method unsupported - Compression forced OFF. Please obtain the latest level of the client code.

Explanation: The client is using a compression method that is no longer supported by the Server.

System Action: Server operation continues. The client's backup operation continues, without compressing the data.

User Response: The compression method used by the client is no longer supported. In order to use compression, the client needs to be upgraded to a client service level that supports the newer compression method.

ANR0447WSession session number space management migration operation for client client node name (client platform) has been denied - Server is not in compliance with license terms.

Explanation: The server refuses a client space management migration operation because the current server configuration is not in compliance with license terms.

System Action: Server operation continues. Clients may perform any action except backup, archive, or space-managed file migration.

User Response: Use the QUERY LICENSE command to determine the license terms that are no longer in compliance.

ANR0448WSession session number space management migration operation for client client node name (client platform) has been denied - server is not licensed for space management support.

Explanation: The server refuses a client space management migration operation because the server is not licensed to support space-managed clients.

System Action: Server operation continues.

User Response: Licenses to support space-managed clients can be obtained from your service provider or reseller. The REGISTER LICENSE command can be used with these licenses to enable space management support.

ANR0449WSession session number space management migration operation for client client node name (client platform) is in violation of server license terms - server is not licensed for space management support.

Explanation: The server warns about a client space management migration operation because the server is not licensed to support space-managed clients.

System Action: Server operation continues.

User Response: Licenses to support space-managed clients can be obtained from your service provider or reseller. The REGISTER LICENSE command can be used with these licenses to enable space management support.

ANR0450WSession session number for server server name (client platform) refused - server name not defined for server to server communications.

Explanation: The server refuses a request to start a server session because the requesting server name is not defined in the server database, or the requesting server definition does not have a SERVERPASSWORD.

System Action: Server operation continues.

User Response: Register the requesting server name with the server before establishing a session, or update the existing requesting server definition and set a SERVERPASSWORD. An authorized administrator must use the DEFINE SERVER or UPDATE SERVER command to register the requesting server and set the password.

ANR0451WSession session number for server server name (server platform) refused - invalid password submitted.

Explanation: The server refuses a request to start a server session because an invalid password has been submitted during sign-on processing. The server will continue to deny access attempts by that server until valid passwords are submitted.

System Action: Server operation continues.

User Response: Set the proper passwords. If the password has been changed on either server, an authorized administrator can set new passwords by using the UPDATE SERVER command with the SERVERPASSWORD parameter.

ANR0452WSession for server server name refused - server name not defined for server to server communications.

Explanation: The server refuses a request to start a server to server session because a server name is not defined in the server database, or the server definition does not have a SERVERPASSWORD. Server to server communications using the serverpassword requires that the each server has had a server definition for the other server.

System Action: Server operation continues.

User Response: Register the server names on both both servers before establishing a session, or update the server's existing server definition and set a SERVERPASSWORD. An authorized administrator must use the DEFINE SERVER or UPDATE SERVER command register the servers and set the passwords.

ANR0453WServer to server session refused - no password defined.

Explanation: The server to server session cannot be initiated because no server password has been defined for this server.

System Action: Server operation continues.

User Response: Define a server password with the SET SERVERPASSWORD command and retry the command.

ANR0454ESession rejected by server server name, reason: rejection reason.

Explanation: The server has attempted to open a session with the shown server. The session was rejected for the indicated reason.

System Action: The operation fails.

User Response: Check both the servers for any additional messages that might further describe the reason the session was rejected. For a reason of AUTHENTICATION FAILURE, ensure that all passwords have been set correctly on both servers. The password for the server (set by SET SERVERPASSWORD on server X) and the password in the server definition (set by DEFINE or UPDATE SERVER X SERVERPASSWORD=) are the same password. For a reason of VERIFICATION FAILURE, use the QUERY SERVER command to determine that the HLADDRESS and LLADDRESS of the target server are correct. If they are not, correct them with the UPDATE SERVER command. If they are correct, resyncronize with the target server by issuing the UPDATE SERVER FORCESYNC=YES. For a reason of COMMUNICATION FAILURE ensure that the target server is available and that TCPIP is available on both servers. For a reason of NO RESOURCE, ensure that the receiving server is enabled, has sufficient DB, LOG, and memory resource to support the source server session. For a reason of INTERNAL ERROR, use the messages on the target server to determine the problem and contact your service representative. Retry the failing operation.

ANR0455WInvalid Command command name for SNMP session.

Explanation: An SNMP administrative session attempted to run a command which is not an macro invocation. SNMP administrative sessions are only allowed to issue macro commands.

System Action: The server ends the client session.

User Response: Enter commands through the SNMP administrative interface which are macros defined on the server.

ANR0456WSession rejected for server name server name at High level address Low level address does not match.

Explanation: The server name at the address specified does not match the name in the server definition. The connection is not established.

System Action: The server continues.

User Response: Insure the HLADDRESS and LLADDRESS in the define server command are correct, and that the servername on the server being contacted matches the name used in the DEFINE SERVER command.

ANR0457WSession for server server name refused - crossdefine is not allowed on this server.

Explanation: The server refuses a request to start a server to server session for crossdefine because it is not allowed on this server. The server will deny any sessions for crossdefine until crossdefine is allowed on this server.

System Action: Server operation continues.

User Response: An authorized administrator must use the SET CROSSDEFINE ON command to allow cross registration of servers.

ANR0458SServer server name does not support access by the Storage Agent.

Explanation: The storage agent attempted to contact a Database Server, but the server contacted was not at the correct level.

System Action: The Storage Agent terminates.

User Response: Specify a correct Database Server in the devconfig file for the Storage Agent.

ANR0459WSignon for administrator administrator name refused - invalid administrator name and/or password submitted.

Explanation: The server refuses a request to start an administrative session because an invalid administrator name and/or password has been submitted by the user during sign-on processing. The server will continue to deny access attempts by this administrator until a valid password is submitted, or until the administrator is locked due to maximum number of invalid password attempts being exceeded.

System Action: Server operation continues.

User Response: Enter the proper password. If the password has been forgotten by the user, an authorized administrator can assign a new password by using the UPDATE ADMIN command.

ANR0460WOpen registration failed for session session number - node name node name (client platform) already exists.

Explanation: The server refuses a client session during open registration because the client has specified a node name that is already registered on the server.

System Action: Server operation continues.

User Response: The client program user must specify a different node name for the client in the client options file.

ANR0461WOpen registration failed for session session number for node node name (client platform) - policy domain STANDARD does not exist.

Explanation: The server refuses a client session during open registration because the STANDARD policy domain does not exist. All nodes added to the server database under open registration are automatically assigned to the STANDARD policy domain. This policy domain must be defined and have an active policy set to support open registration.

System Action: Server operation continues.

User Response: If you want to support open registration, define a policy domain using the DEFINE DOMAIN command with the name STANDARD and activate a valid policy set in the domain. You can issue the UPDATE NODE command to move nodes to different policy domains after the nodes have registered themselves through open registration.

ANR0462WOpen registration failed for session session number for node node name (client platform) - invalid node name.

Explanation: The server refuses a client session during open registration because the node name specified by the client is not valid.

System Action: Server operation continues.

User Response: Specify a node name in the options file of the client program that contains valid characters and does not exceed the maximum length in size. Refer to Using the Backup-Archive Client for a description of the node name restrictions.

ANR0463WOpen registration failed for session session number for node node name (client platform) - invalid password.

Explanation: The server refuses a client session during open registration because the password name specified by the user is not valid.

System Action: Server operation continues.

User Response: Specify a password that uses valid characters and is less than the maximum length in size. Refer to Using the Backup-Archive Client for a description of the password restrictions.

ANR0464WOpen registration failed for session session number for node node name (client platform) - exceeded number of nodes available under license terms.

Explanation: The server detected an attempt to register more nodes than allowed by the terms of the current license.

System Action: Server operation continues, but the REGISTER NODE command fails, and the node is not registered.

User Response: Use the QUERY LICENSE command to determine the license terms that are no longer in compliance.

ANR0465WOpen registration failed for session session number for node node name (client platform) - policy domain STANDARD does not have an ACTIVE policy set.

Explanation: The server refuses a client session during open registration because the STANDARD policy domain does not have an active policy set. All nodes added to the server database under open registration are automatically assigned to the STANDARD policy domain. This policy domain must be defined and have an active policy set to support open registration.

System Action: Server operation continues.

User Response: If you want to support open registration, define a policy domain using the DEFINE DOMAIN command with the name STANDARD and activate a valid policy set in the domain. You can issue the UPDATE NODE command to move nodes to different policy domains after the nodes have registered themselves through open registration.

ANR0479WSession session number for server server name (server platform) terminated - connection with server severed.

Explanation: If server A has opened a connection with server B, server B's session is ended because the communications link has been closed by a network error or by server A's program.

System Action: Server A continues operation.

User Response: If server B halts operation or in some way stops communicating with server A, this message will be displayed on server A indicating that the connection was closed suddenly by server B. A network failure can also cause this message to be displayed. If a large number of these messages occur simultaneously, check the network for failure and correct any problems.

ANR0480WSession session number for node node name (client platform) terminated - connection with client severed.

Explanation: The specified client session is ended because the communications link has been closed by a network error or by the client program.

System Action: Server operation continues.

User Response: If a user breaks out of a client program, this message will be displayed on the server as the connection is suddenly closed by the client. A network failure can also cause this message to be displayed. If a large number of these messages occur simultaneously, check the network for failure and correct any problems.

ANR0481WSession session number for node node name (client platform) terminated - client did not respond within commtimeout seconds seconds.

Explanation: The server ends a client session because the client has been holding database locks (a transaction was in progress) and the client has not responded in the number of seconds specified by the COMMTIMEOUT parameter in the server options file.

System Action: The server rolls back the transaction that has been in progress and the session is ended. Server operation continues.

User Response: If a large number of these messages appear, you may want to increment the value specified for the COMMTIMEOUT value in the server options file and restart the server. The amount of time that it takes for a client to respond is dependent upon the speed and processor load for the client and the network load.

ANR0482WSession session number for node node name (client platform) terminated - idle for more than idletimeout minutes minutes.

Explanation: The server ends a client session because it has been idle for more minutes than specified in the IDLETIMEOUT parameter in the server options file. The client program will automatically attempt to reconnect to the server when necessary.

System Action: Server operation continues.

User Response: If the problems persists, increase the value specified for the IDLETIMEOUT parameter in the server options file and restart the server. Many times, the client program is idle while waiting for the user to choose an action to perform (for example, backup, archive, restore, or retrieve files). If a user starts the client program and does not choose an action to perform, the session will eventually time out. The client program automatically reconnects to the server when the user chooses an action that requires server participation. Note that a large number of idle sessions can inadvertently prevent other users from connecting to the server, so care should be used when increasing the IDLETIMEOUT parameter.

ANR0483WSession session number for node node name (client platform) terminated - forced by administrator.

Explanation: The server ends a client session in response to a CANCEL SESSION command issued by an authorized administrator.

System Action: The server rolls back any transactions in progress for the terminated client session.

User Response: None.

ANR0484WSession session number for node node name (client platform) terminated - protocol violation detected.

Explanation: The server ends the specified session because a communications protocol error by the client has been detected.

System Action: The server ends the client session.

User Response: Examine the client message to determine the problem. Correct the programming error in the client program. If the error cannot be isolated and resolved, contact your service representative.

ANR0485WSession session number for node node name (client platform) terminated - sufficient memory is not available.

Explanation: The server ends the specified session because sufficient memory (virtual memory) is not available.

System Action: The server ends the session and continues operation.

User Response: Allocate additional storage to the server. For details, issue HELP MEMORY to display the information online or see "Appendix A. Allocating Additional Server Memory".

ANR0486WSession session number for node node name (client platform) terminated - internal error detected.

Explanation: The specified client session is ended by the server because an internal processing error has been detected on the server. A programming error may have occurred in the server program.

System Action: The session is ended and server operation continues.

User Response: Contact your service representative.

ANR0487WSession session number for node node name (client platform) terminated - preempted by another operation.

Explanation: The server ends a client session in response to a cancel request issued by a higher priority operation that needed the mount point that the client was using.

System Action: The server rolls back any transactions in progress for the terminated client session.

User Response: Reissue the operation. If this message appears frequently, consider increasing the mountlimit value for the affected device class.

ANR0488WSession session number for node node name (client platform) terminated - transfer rate is less than (transfer rate) and more than (elapsed time since first data transfer) minutes have elapsed since first data transfer.

Explanation: The server is canceling client session number session number. Depending on the state of the session, it may take a while for the session to be canceled. The server ends a client session because it has been active for more minutes than specified in the THROUGHPUTTIMETHRESHOLD parameter in the server options file and the data transfer rate is less than the amount sepcified with the THROUGHPUTDATATHRESHOLD parameter in the server options file. The client is transferring data to the server at an abnormally slow rate and may have become a bottleneck for handling data from other clients. If the client has caused log records to be written, it is possible that this client will prevent log space reclamation.

System Action: The session is canceled and server operation continues.

User Response: If a low data transfer rate is not a problem, the THROUGHPUTTIMETHRESHOLD or THROUGHPUTDATATHRESHOLD parameters in the server options file can be set to zero - this will disable the throughput check. The change can be made without taking down the server and restarting it by using the SETOPT THROUGHPUTTIMETHRESHOLD or the SETOPT THROUGHPUTDATATHRESHOLD commands. If a low data transfer rate is not expected, external causes should be investigated. This would include network problems and problems in accessing data on the client node. The client program may automatically reconnect to the server, so this message may appear on susbsequent sessions until the data transfer problem is resolved. The default server operation is not to perform a throughput check.

ANR0490ICanceling session session number for node node name (client platform) .

Explanation: The server is canceling client session number session number. This message is displayed in response to the CANCEL SESSION command. Depending on the state of the session, it may take a while for the session to be canceled.

System Action: The session is canceled and server operation continues.

User Response: None.

ANR0491INo matching session(s) found to cancel.

Explanation: The server cannot find any sessions to cancel matching the specifications entered in the CANCEL SESSION command.

System Action: Server operation continues.

User Response: Use the QUERY SESSION command to ensure that the session you wish to cancel is connected. Reissue the command using the appropriate session number to cancel the client session.

ANR0492IAll drives in use. Session session number for node node name (client platform) being preempted by higher priority operation.

Explanation: When a high priority operation attempted to find an available drive, all the drives were being used. To free up a drive for this operation, the client session identified is being cancelled by the system.

System Action: The lower priority client session is cancelled to free up a mount point (drive).

User Response: When a drive again becomes available, restart the session that was cancelled. This session was most likely a backup/archive session and you may just want to let it restart automatically during its next scheduled backup window. If this message appears frequently, you may want to increase the number of drives available. See the MOUNTLIMIT parameter on the UPDATE DEVCLASS command.

ANR0493IRestore session session number canceled.

Explanation: The specified session was canceled with the CANCEL RESTORE command.

System Action: The restore session is canceled and server operation continues.

User Response: None.

ANR0494IVolume volume name in use. Session session number for node node name (client platform) being preempted by higher priority operation.

Explanation: When a high priority operation attempted to acquire a specific volume, it was being used. To free the volume for this operation, the client session identified is being cancelled by the system.

System Action: The lower priority client session is cancelled to free up the volume.

User Response: Restart the session that was cancelled, it will wait until the higher priority operation if finished with the volume. This cancelled session was most likely a backup/archive session and you may just want to let it restart automatically during its next scheduled backup window.

ANR0500WTransaction failed for session session number for node node name (client platform) - invalid password submitted.

Explanation: The server ends a password update transaction because the user has not correctly specified the current password.

System Action: Server operation continues.

User Response: Update your password by correctly specifying the current password. If the current password has been misplaced, the administrator can reassign a password for the client by using the UPDATE NODE or UPDATE ADMIN command.

ANR0501WTransaction failed for session session number for node node name (client platform) - invalid policy binding specified.

Explanation: The server ends a database update transaction for the specified session because an invalid management class has been specified for a file or directory object.

System Action: The specified session is ended and server operation continues.

User Response: Correct the programming error in the client program if it has been written by your installation using WDSF verbs. Otherwise, contact your service representative.

ANR0520WTransaction failed for session session number for node node name (client platform) - storage pool pool name is not defined.

Explanation: The server rolls back a database update transaction for the specified session because the destination specified for a management class copy group specifies the named storage pool, but that storage pool does not exist.

System Action: Server operation continues.

User Response: An administrator with policy authority over the client policy domain must correct management class definitions so that copy group destinations refer to defined storage pools, or the specified storage pool must be created by an authorized administrator.

ANR0521WTransaction failed for session session number for node node name (client platform) - object excluded by size in storage pool pool name and all successor pools.

Explanation: The server ends a database update transaction for the specified session because the size of a file sent from the client node is larger than that allowed in the storage pool specified in the client's management class copy group. No successor storage pools to the one specified on the copy group can accept the large file.

System Action: The specified session is ended and server operation continues.

User Response: If the client is not using compression to send files to the host, turn compression on for the client (using the UPDATE NODE command) to try and resolve the problem. Otherwise, the maximum file size for one or more of the storage pools in the storage hierarchy can be increased to accommodate the file. An authorized administrator can increase the MAXSIZE parameter by issuing the UPDATE STGPOOL command.

ANR0522WTransaction failed for session session number for node node name (client platform) - no space available in storage pool pool name and all successor pools.

Explanation: The server ends a database update transaction for the specified session because the storage pool specified in the client's management class copy group does not contain enough free space to hold the files sent from the client. Successor storage pools to the one specified on the copy group do not contain enough free space.

System Action: The specified session is ended and server operation continues.

User Response: An authorized administrator can issue the DEFINE VOLUME command to add storage to one or more storage pools in the storage hierarchy. This action may also involve creating storage space by using an operating system specific utility.

ANR0523WTransaction failed for session session number for node node name (client platform) - error on output storage device.

Explanation: The server ends a database update transaction for the specified client because an I/O error has been encountered by the server in writing to a device.

System Action: The specified session is ended and server operation continues.

User Response: Query the activity log to find messages preceding this one that specify the failing device. Storage pool volumes can be varied offline (by using the VARY command), or the server may need to be halted to correct the hardware problem. After the problem is corrected, the client should retry the operation.

ANR0524WTransaction failed for session session number for node node name (client platform) - data transfer interrupted.

Explanation: The database transaction associated with session session number was aborted because data transfer to or from data storage was interrupted by an external event.

System Action: The session is canceled and server operation continues.

User Response: Examine the messages issued prior to this message to determine why the data transfer was interrupted. Attempt the client operation again if the problem can be resolved.

ANR0525WTransaction failed for session session number for node node name (client platform) - storage media inaccessible.

Explanation: The server ends a transaction for the specified session because storage volumes are not available in the storage pools in which the client's files are to be stored.

System Action: The server ends the specified session and server operation continues.

User Response: An authorized administrator can issue the DEFINE VOLUME command to add storage to one or more storage pools in the storage hierarchy. The VARY ONLINE command can be used to vary offline storage volumes online in the storage hierarchy to make them available to client nodes for file storage.

ANR0526WTransaction failed for session session number for node node name (client platform) - sufficient recovery log space is not available.

Explanation: The server ends a database update transaction for the specified session because sufficient log space is not available on the server.

System Action: The server ends the specified session and server operation continues.

User Response: An authorized administrator can issue the DEFINE LOGVOLUME command to add volumes for use by the log, and can issue the EXTEND LOG command to extend the size of the log so that the new volumes are used.

ANR0527WTransaction failed for session session number for node node name (client platform) - sufficient database space is not available.

Explanation: The server ends a database update transaction for the specified session because sufficient database space is not available on the server.

System Action: The server ends the specified session and server operation continues.

User Response: An authorized administrator can issue the DEFINE DBVOLUME command to add volumes for use by the database, and can issue the EXTEND DB command to extend the size of the database so that the new volumes are used.

ANR0528WTransaction failed for session session number for node node name (client platform) - thread resource not available.

Explanation: The server ends a database update transaction for the specified session because sufficient memory is not available for starting additional processes on the server.

System Action: The server ends the specified session and server operation continues.

User Response: Allocate additional storage to the server. For details, issue HELP MEMORY to display the information online or see "Appendix A. Allocating Additional Server Memory".

ANR0529WTransaction failed for session session number for node node name (client platform) - insufficient memory.

Explanation: The server ends a database update transaction for the specified session because sufficient memory is not available on the server.

System Action: The server ends the specified session and server operation continues.

User Response: Allocate additional storage to the server. For details, issue HELP MEMORY to display the information online or see "Appendix A. Allocating Additional Server Memory".

ANR0530WTransaction failed for session session number for node node name (client platform) - internal server error detected.

Explanation: The server ends a database update transaction for the specified session because an internal logic error is detected.

System Action: The server ends the specified session and server operation continues.

User Response: Examine the server messages issued prior to this message to determine the source of the error. Issue the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative.

ANR0531WTransaction failed for session session number for node node name (client platform) - invalid file space identifier specified by client.

Explanation: The server ends a database update transaction for the specified session because the file space identified by the client for the transaction does not exist.

System Action: This action usually occurs when a client is operating on a file space that is currently being deleted as a result of an administrative command or client action. The server ends the specified session and server operation continues.

User Response: Use the QUERY PROCESS command to monitor and wait for any file space deletion processes to complete, or cancel the process if you do not want to delete the file space. Try the client action again after this action has been taken.

ANR0532WDiagnosticID: Transaction transaction ID was aborted for session session number for node node name (client platform).

Explanation: An error has been detected during a transaction commit for the specified session. This message should be preceded by other messages that give additional information about the failed transaction.

System Action: The activity that generated this error fails.

User Response: Check for additional messages and eliminate the condition that caused the failed transaction. If the error cannot be isolated and resolved, contact your service representative.

ANR0533WTransaction failed for session session number - compression method used by client not supported. Please obtain the latest level of the client code.

Explanation: The server ends the transaction for the specified session because the compression method that is used by the client is no longer supported by the server.

System Action: The server ends the specified session and server operation continues.

User Response: The client must either backup the data with compression turned off, or upgrade to a client that supports the newer compression method. If the client is a WDSF client, upgrade to a non-WDSF client in order to use the compression performed by the client.

ANR0534WTransaction failed for session session number for node node name (client platform) - size estimate exceeded and server is unable to obtain additional space in storage pool pool name.

Explanation: The server ends a database update transaction for the specified session because the size estimate provided by the client is too small. The server has attempted to obtain additional space in the indicated storage pool, but was unable to do so.

System Action: The specified session is ended and server operation continues. If pool name is a random access storage pool with caching enabled, it is also possible that additional space can be made available in this storage pool by eliminating cached files. When the server allocates space based on the size estimate provided by the client, it frees space occupied by cached files if this space is needed to obtain the estimated space. However, if the server later determines that the file size estimate was too low, it attempts to obtain additional space that is not utilized, but does not delete cached files to do so. If the client sending the data has the option COMPRESSALWAYS YES set, it is possible that a file grew during the compression operation and when the client sent it to the server it exceeded the space available in storage pool pool name.

User Response: This message may indicate that there is no additional space in pool name. The following are possible circumventions:

An authorized administrator can issue the DEFINE VOLUME command to add storage to this pool.

If the suspected cause of the failure is that pool name is a DISK storage pool and that space in use by cached files was not freed, turn off caching for the storage pool and issue the MOVE DATA command for the volumes in pool pool name.

If the suspected cause of the failure is that a file grew in size during compression on the client, another possible circumvention is to set the COMPRESSALWAYS option in the client options file to NO and retry the operation. This may allow the client to accurately report the file size and possibly avoid the out of space condition in the storage pool.

ANR0535WTransaction failed for session session number for node node name (client platform) - insufficient mount points available to satisfy the request.

Explanation: The server was unable to allocate sufficient mount points to process the transaction.

System Action: The operation is ended and server operation continues.

User Response: If necessary, make more mount points available.

ANR0536WTransaction failed for session session number for node node name (client platform) - downlevel client does not support format of stored files.

Explanation: A client attempts to perform an operation involving files that are stored in a format that is not supported by that client level.

System Action: The operation is ended and server operation continues.

User Response: Upgrade the client to a later level.

ANR0540WRetrieve or restore failed for session session number for node node name (client platform) - data integrity error detected.

Explanation: The server ends a file retrieval operation for the specified session because an internal database integrity error has been encountered on the server.

System Action: The server ends the specified session and continues operation.

User Response: Contact your service representative.

ANR0541WRetrieve or restore failed for session session number for node node name (client platform) - error on input storage device.

Explanation: The server ends a client retrieval or restore operation for the specified session because an I/O error has been encountered by the server in reading from a device.

System Action: The server ends the specified session and server operation continues.

User Response: Query the activity log to find messages preceding this one that specify the device that is failing. Storage pool volumes can be varied offline (by using the VARY OFFLINE command), or the server may need to be shut down by using the HALT command to correct the hardware problem. After the problem is corrected, the client may try the operation again.

ANR0542WRetrieve or restore failed for session session number for node node name (client platform) - storage media inaccessible.

Explanation: The server ends a client retrieval or restore operation for the specified session because a needed storage pool volume has been varied offline.

System Action: The server ends the specified session and server operation continues.

User Response: Use the VARY ONLINE command to vary offline storage volumes online in the storage hierarchy, and make them available to client nodes for file storage.

ANR0543WRetrieve or restore failed for session session number for node node name (client platform) - data transfer interrupted.

Explanation: The database transaction associated with session session number was aborted because data transfer to or from data storage was interrupted by an external event.

System Action: The session is canceled and server operation continues.

User Response: Examine the messages issued prior to this message to determine why the data transfer was interrupted. Attempt the client operation again, if the problem can be resolved.

ANR0544WRetrieve or restore failed for session session number for node node name (client platform) - thread resource not available.

Explanation: The server ends a file retrieval or restore operation for the specified session because sufficient memory is not available for starting additional processes on the server.

System Action: The server ends the specified session and server operation continues.

User Response: Allocate additional storage to the server. For details, issue HELP MEMORY to display the information online or see "Appendix A. Allocating Additional Server Memory".

ANR0545WRetrieve or restore failed for session session number for node node name (client platform) - insufficient memory.

Explanation: The server ends a file retrieval or restore operation for the specified session because sufficient memory is not available on the server.

System Action: The server ends the specified session and server operation continues.

User Response: Allocate additional storage to the server. For details, issue HELP MEMORY to display the information online or see "Appendix A. Allocating Additional Server Memory".

ANR0546WRetrieve or restore failed for session session number for node node name (client platform) - internal server error detected.

Explanation: The server ends a file retrieval or restore operation for the specified session because an internal logic error is detected in the server program.

System Action: The server ends the specified session and continues operation.

User Response: Examine the server messages issued prior to this message to determine the source of the error. Use the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative.

ANR0547EInvalid data was encountered in the command processor output stream: output formatting terminated for the last command entered.

Explanation: The server console session encounters an error in formatting output from a command.

System Action: The command output is discarded and server operation continues.

User Response: Use the server QUERY command to determine if the command you entered had the desired affect in the server. Use the QUERY ACTLOG command to see if a server error condition (like out of memory) occurred prior to the command. Resolve the error if it is found. Contact your service representative if you cannot resolve the error, or if an error is not found.

ANR0548WRetrieve or restore failed for session session number for node node name (client platform) processing filespace filespace for file file name stored as storage repository - data integrity error detected.

Explanation: The server ends a file retrieval operation for the specified session because an internal database integrity error has been encountered on the server.

System Action: The server ends the specified session and continues operation.

User Response: Re-try the restore or retrieve operation and if the file is also backed up in a copy storage pool, the operation will attempt to read the file from the alternate location.

ANR0566WRetrieve or restore failed for session session number for node node name (client platform) - file was deleted from data storage during retrieval.

Explanation: The server ends a file retrieval operation for the specified session because the file has been deleted from data storage by another process before retrieval is complete.

System Action: The server ends the specified session and continues operation.

User Response: Contact your administrator to find out if DELETE FILESPACE, DELETE VOLUME, or inventory expiration processes are running; these processes can delete data storage files during retrieval. Reissue the restore or retrieve operation and specify a different file version.

ANR0567WRetrieve or restored failed for session session number for node node name (client platform) - insufficient mount points available to satisfy the request.

Explanation: The server was unable to allocate sufficient mount points to process the retrieve or restore operation.

System Action: The operation is ended and server operation continues.

User Response: If necessary, make more mount points available.

ANR0568WSession session number for admin admin name (client platform) terminated - connection with client severed.

Explanation: The specified admin session is ended because the communications link has been closed by a network error or by the client program.

System Action: Server operation continues.

User Response: If a user breaks out of a client program, this message will be displayed on the server as the connection is suddenly closed by the client. A network failure can also cause this message to be displayed. If a large number of these messages occur simultaneously, check the network for failure and correct any problems.

ANR0569IObject not processed for node name: type=type, file space=filespace name, object=object name.

Explanation: An error occurred. The object for node name, identified by type, file space and object name was not processed.

System Action: Server action is defined by the error that occurred.

User Response: Issue QUERY ACTLOG to determine the source of the error.

ANR0570EExport command: Invalid value for DURUNITS parameter detected while exporting administrative schedule schedule name - default or existing value is used during import.

Explanation: During processing of command export command, an invalid value is encountered for the DURUNITS parameter for administrative schedule schedule name.

System Action: Export processing continues, but the exported data contains an unknown DURUNITS value for this schedule. If this data is imported, the server uses the default or existing DURUNITS value.

User Response: Update the DURUNITS value for this schedule and restart the export command. Alternatively, the export data with the unknown value can be used, and the DURUNITS value can be checked and updated after import processing has been performed.

ANR0571EExport command: Invalid value for PERUNITS parameter detected while exporting administrative schedule schedule name - default or existing value is used during import.

Explanation: During processing of command export command, an invalid value is encountered for the PERUNITS parameter for administrative schedule schedule name.

System Action: Export processing continues, but the exported data will contain an unknown PERUNITS value for this schedule. If this data is imported, the server uses the default or existing PERUNITS value.

User Response: Update the PERUNITS value for this schedule and restart the export command. Alternatively, use the export data with the unknown value, and check and update the PERUNITS value after import processing has been performed.

ANR0572EExport command: Invalid value for DAYOFWEEK parameter detected while exporting administrative schedule schedule name - default or existing value is used during import.

Explanation: During processing of command export command, an invalid value is encountered for the DAYOFWEEK parameter for administrative schedule schedule name.

System Action: Export processing continues, but the exported data contains an unknown DAYOFWEEK value for this schedule. If this data is imported, the server uses the default or existing DAYOFWEEK value.

User Response: Update the DAYOFWEEK value for this schedule and restart the export command. Alternatively, use the export data with the unknown value, and check and update the DAYOFWEEK value after import processing has been performed.

ANR0573IExport/import command: Processing administrative schedule schedule name.

Explanation: The background export or import process to service the command export/import command is currently processing the schedule definition information for administrative schedule schedule name.

System Action: Export or import processing for the command continues.

User Response: None.

ANR0574EImport command: Invalid value for DURUNITS or PERUNITS parameter in exported data for administrative schedule schedule name.

Explanation: During preview processing of command import command, an invalid value is encountered for the DURUNITS or PERUNITS parameter for administrative schedule schedule name.

System Action: Processing of the command continues. If a later command is issued that causes the data to be imported, the default or existing values are used for DURATION, DURUNITS, PERIOD, and PERUNITS.

User Response: If the data is imported with a later command, verify that the correct values for DURATION, DURUNITS, PERIOD, and PERUNITS are used for this schedule.

ANR0575EImport command: Invalid value for DAYOFWEEK parameter in exported data for administrative schedule schedule name.

Explanation: During preview processing of command import command, an invalid value is encountered for the DAYOFWEEK parameter for administrative schedule schedule name.

System Action: Processing of the command continues. If a later command is issued that causes the data to be imported, the default or existing DAYOFWEEK value is used.

User Response: If the data is imported with a later command, verify that the correct DAYOFWEEK value is used for this schedule.

ANR0576EImport command: Invalid value for DURUNITS or PERUNITS parameter in exported data - administrative schedule schedule name defined with default values for DURATION, DURUNITS, PERIOD, and PERUNITS.

Explanation: During processing of command import command, an invalid value is encountered for the DURUNITS or PERUNITS parameter for administrative schedule schedule name.

System Action: Processing of the command continues, by using the default values for DURATION, DURUNITS, PERIOD, and PERUNITS.

User Response: Verify that the correct values have been used for DURATION, DURUNITS, PERIOD, and PERUNITS. Update these values, if necessary.

ANR0577EImport command: Invalid value for DAYOFWEEK parameter in exported data - administrative schedule schedule name defined with default DAYOFWEEK value.

Explanation: During processing of command import command, an invalid value is encountered for the DAYOFWEEK parameter for administrative schedule schedule name.

System Action: Processing of the command continues, by using the default DAYOFWEEK value for this schedule.

User Response: Verify that the correct DAYOFWEEK value has been used for this schedule. Update this value, if necessary.

ANR0578EImport command: Invalid value for DURUNITS or PERUNITS parameter in exported data - existing values for DURATION, DURUNITS PERIOD, and PERUNITS for administrative schedule schedule name were not updated.

Explanation: During processing of command import command, an invalid value is encountered for the DURUNITS or PERUNITS parameter for administrative schedule schedule name.

System Action: Processing of the command continues, by using the existing values for DURATION, DURUNITS, PERIOD, and PERUNITS.

User Response: Verify that the correct values have been used for DURATION, DURUNITS, PERIOD, and PERUNITS. Update these values, if necessary.

ANR0579EImport command: Invalid value for DAYOFWEEK parameter in exported data - existing DAYOFWEEK value for administrative schedule schedule name was not updated.

Explanation: During processing of command import command, an invalid value is encountered for the DAYOFWEEK parameter for administrative schedule schedule name.

System Action: Processing of the command continues, by using the existing DAYOFWEEK value for this schedule.

User Response: Verify that the correct DAYOFWEEK value has been used for this schedule. Update this value, if necessary.

ANR0580EExport command: Invalid value for SPACEMGTECHNIQUE parameter detected while exporting management class management class name in domain domain name, set policy set name - default or existing value is used during import.

Explanation: During processing of command export command, an invalid value is encountered for the SPACEMGTECHNIQUE parameter for management class management class name in domain domain name, policy set policy set name.

System Action: Export processing continues, but the exported data contains an unknown SPACEMGTECHNIQUE value for this management class. If this data is imported, the default or existing SPACEMGTECHNIQUE value is used.

User Response: Update the SPACEMGTECHNIQUE value for this copy group and restart the export. Alternatively, use the export data with the unknown value, and check and update the SPACEMGTECHNIQUE value after import processing has been performed.

ANR0581EExport command: Invalid value for MIGREQUIRESBKUP parameter detected while exporting management class management class name in domain domain name, set policy set name - default or existing value is used during import.

Explanation: During processing of command export command, an invalid value is encountered for the MIGREQUIRESBKUP parameter for management class management class name in domain domain name, policy set policy set name.

System Action: Export processing continues, but the exported data contains an unknown value for this management class. If this data is imported, the default or existing MIGREQUIRESBKUP value is used.

User Response: Update the MIGREQUIRESBKUP value for this copy group and restart the export. Alternatively, use the export data with the unknown value, and check and update the MIGREQUIRESBKUP value after import processing has been performed.

ANR0582EImport command: Invalid value for SPACEMGTECHNIQUE parameter in exported data for management class management class name in domain domain name, set policy set name.

Explanation: During preview processing of command import command, an invalid value is encountered for the SPACEMGTECHNIQUE parameter for management class management class name, in policy domain domain name, policy set policy set name.

System Action: Processing of the command continues. If a later command is issued that causes the data to be imported, the default or existing SPACEMGTECHNIQUE value is used.

User Response: None. If the data is imported with a later command, verify that the correct SPACEMGTECHNIQUE value is used for this management class.

ANR0583EImport command: Invalid value for SPACEMGTECHNIQUE parameter in exported data - management class management class name in domain domain name, set policy set name defined with default SPACEMGTECHNIQUE value.

Explanation: During processing of command import command, an invalid value is encountered for the SPACEMGTECHNIQUE parameter for management class management class name, in policy domain domain name, policy set policy set name.

System Action: Processing of the command continues, by using the default SPACEMGTECHNIQUE value for this management class.

User Response: Verify that the correct SPACEMGTECHNIQUE value has been used for this management class. Update this value, if necessary.

ANR0584EImport command: Invalid value for SPACEMGTECHNIQUE parameter in exported data - SPACEMGTECHNIQUE value for management class management class name in domain domain name, set policy set name was not updated.

Explanation: During processing of command import command, an invalid value is encountered for the SPACEMGTECHNIQUE parameter for management class management class name, in policy domain domain name, policy set policy set name.

System Action: Processing of the command continues, by using the existing SPACEMGTECHNIQUE value for this management class.

User Response: Verify that the correct SPACEMGTECHNIQUE value has been used for this management class. Update this value, if necessary.

ANR0585EImport command: Invalid value for MIGREQUIRESBKUP parameter in exported data for management class management class name in domain domain name, set policy set name.

Explanation: During preview processing of command import command, an invalid value is encountered for the MIGREQUIRESBKUP parameter for management class management class name, in policy domain domain name, policy set policy set name.

System Action: Processing of the command continues. If a later command causes the data to be imported, the default or existing MIGREQUIRESBKUP value is used.

User Response: None. If the data is imported with a later command, verify that the correct MIGREQUIRESBKUP value is used for this management class.

ANR0586EImport command: Invalid value for MIGREQUIRESBKUP parameter in exported data - management class management class name in domain domain name, set policy set name defined with default MIGREQUIRESBKUP value.

Explanation: During processing of command import command, an invalid value is encountered for the MIGREQUIRESBKUP parameter for management class management class name, in policy domain domain name, policy set policy set name.

System Action: Processing of the command continues, by using the default MIGREQUIRESBKUP value for this management class.

User Response: Verify that the correct MIGREQUIRESBKUP value has been used for this management class. Update this value, if necessary.

ANR0587EImport command: Invalid value for MIGREQUIRESBKUP parameter in exported data - MIGREQUIRESBKUP value for management class management class name in domain domain name, set policy set name was not updated.

Explanation: During processing of command import command, an invalid value is encountered for the MIGREQUIRESBKUP parameter.

System Action: Processing of the command continues, by using the existing MIGREQUIRESBKUP value for this management class.

User Response: Verify that the correct MIGREQUIRESBKUP parameter has been used for this management class. Update this value, if necessary.

ANR0588EImport command: Server is down-level compared to export data version version number.

Explanation: An attempt is made to import data to a down-level server. The server on which the import is performed must be at the same or later level than the server from which the data was exported.

System Action: The import process ends and server operation continues.

User Response: Import to a server that is at the same or later level than the server from which the export was performed.

ANR0589EImport command: Preview processing terminated abnormally - server is down-level.

Explanation: Processing for the command import command in preview mode ends when it is determined that the server is down-level compared to the export data.

System Action: Import processing ends and server operation continues.

User Response: Import to a server that is at the same or later level than the server from which the export was performed.

ANR0590EImport command: Processing terminated abnormally - server is down-level.

Explanation: Processing for the command import command ends when it is determined that the server is down-level compared to the export data.

System Action: Import processing ends and server operation continues.

User Response: Import to a server that is at the same or later level than the server from which the export was performed.

ANR0591EExport/import command: Invalid value for FILELIST parameter - parameter value.

Explanation: The value (parameter value) specified for the FILELIST parameter in command export/import command is not a valid value for this parameter.

System Action: The command fails and server operation continues.

User Response: Reissue the command and specify a valid FILELIST parameter. For information on valid values for the FILELIST parameter for the command, refer to the Administrator's Reference for your particular platform.

ANR0592EExport/import command: Invalid value for TOC parameter - parameter value.

Explanation: The value (parameter value) specified for the TOC parameter in command export/import command is not a valid value for this parameter.

System Action: The command fails and server operation continues.

User Response: Reissue the command and specify a valid TOC parameter. For information on valid values for the TOC parameter for the command, refer to the Administrator's Reference for your particular platform.

ANR0593EExport/import command: Invalid value for NOSPAN parameter - parameter value.

Explanation: The value (parameter value) specified for the NOSPAN parameter in command export/import command is not a valid value for this parameter.

System Action: The command fails and server operation continues.

User Response: Reissue the command and specify a valid NOSPAN parameter. For information on valid values for the NOSPAN parameter for the command, refer to the Administrator's Reference for your particular platform.

ANR0594Edevice class: NOSPAN parameter can only be used with a 3590 device class.

Explanation: The device class specified must be a 3590 device class when NOSPAN is set to True.

System Action: The command fails and server operation continues.

User Response: Reissue the command and specify a valid NOSPAN/Device Class parameter. For information on valid values for the NOSPAN parameter for the command, refer to the Administrator's Reference for your particular platform.

ANR0596WSpace-managed object object name for client node node name, filespace filespace name already exists on the server - it will be skipped.

Explanation: While attempting to import a spaced-managed object, the server discovers that the object already exists. The space-managed object is skipped.

System Action: Server operation continues.

User Response: None.

ANR0597WIMPORT: Space management attributes in management class management class name for domain domain name is not defined - default management class will be used.

Explanation: During import processing, the server finds that the space management attributes for a space-managed file being imported does not exist in the active policy set for the domain to which the node is assigned.

System Action: The default management class for the node's policy domain is bound to the space-managed file and import processing continues.

User Response: If you want to define the missing management class, an authorized administrator may cancel the import operation, define the missing space management attributes or management class for the domain, and process the import operation again.

ANR0598WIMPORT: Space management attributes not found for default management class in domain domain name - space managed files bound to management class management class name in this domain cannot be imported.

Explanation: During import processing, the server finds that a management class bound to a space-managed file being imported does not exist in the active policy set for the domain to which the node is assigned. When trying to rebind the space-managed file to the default management class for the domain, the server finds that the space-managed attributes are not defined for the default management class.

System Action: The file is not imported; import processing continues.

User Response: If you want to define the missing copy group, an authorized administrator may cancel the import operation, define the missing space management attributes or management class for the domain, and process the import operation again.

ANR0599EExport/import command: Invalid volume name volume name specified for device class device class name.

Explanation: One of the volume names specified in the VOLUMENAMES parameter for an import or export command is not a valid volume name for the device class specified in the DEVCLASS parameter.

System Action: The export or import command fails.

User Response: Specify volume names in the VOLUMENAMES parameter that are valid for the device class specified in the DEVCLASS parameter.

ANR0600IExport command: No matching policy domains found for exporting.

Explanation: The background export process does not find any policy domains that match the specification entered in the export command.

System Action: The export process continues and no policy domains are exported from the server.

User Response: None.

ANR0601IExport command: No policy sets found in policy domain domain name for exporting.

Explanation: The background export process does not find any policy sets defined in domains matching domain name.

System Action: The export process continues and no policy sets are exported from the domain.

User Response: None.

ANR0602IExport command: No management classes were found in policy domain domain name for exporting.

Explanation: The background export process does not find any management classes defined in policy domains matching domain name.

System Action: The export process continues and no management classes are exported from the domain.

User Response: None.

ANR0603IExport command: No copy groups were found in policy domain domain name for exporting.

Explanation: The background export process does not find any copy groups defined in policy domains matching domain name.

System Action: The export process continues and no copy groups are exported from the domain.

User Response: None.

ANR0604IExport command: No schedules were found in policy domain domain name for exporting.

Explanation: The background export process does not find any schedules defined for policy domains matching domain name.

System Action: The export process continues and no schedules are exported for the domain.

User Response: None.

ANR0605IExport command: No schedule associations were found in policy domain domain name for exporting.

Explanation: The background export process does not find any schedule node associations defined for policy domains matching domain name.

System Action: The export process continues and no schedule associations are exported for the domain.

User Response: None.

ANR0606IExport command: No node definitions were found for exporting.

Explanation: The background export process does not find any node definitions to export as specified in the command export command.

System Action: The export process continues.

User Response: None.

ANR0607IExport command: No administrator definitions were found for exporting.

Explanation: The background export process does not find any administrator definitions to export as specified in the command export command.

System Action: The export process continues.

User Response: None.

ANR0608IExport command: No file spaces were found for exporting.

Explanation: The background export process does not find any file space definitions to export as specified in the command export command.

System Action: The export process continues.

User Response: None.

ANR0609ICommand started as process process ID.

Explanation: A background process has been started to service the command command. The background process is defined as process process ID.

System Action: Server operation continues.

User Response: To query the progress of the background process, use the QUERY PROCESS command. To cancel the background process, use the CANCEL PROCESS command. Use the process ID number to specify this specific process.

ANR0610ICommand started by administrator name as process process ID.

Explanation: A background process has started to service the command command entered by administrator administrator name. The background process is defined as process process ID.

System Action: Server operation continues.

User Response: To query the progress of the background process, use the QUERY PROCESS command. To cancel the background process, use the CANCEL PROCESS command. Use the process ID number to specify this specific process.

ANR0611ICommand started by administrator name as process process ID has ended.

Explanation: The background process to service the command command by administrator administrator name has completed processing.

System Action: The specified process ends, and server operation continues.

User Response: None.

ANR0612IImport command: Reading EXPORT SERVER data from server server name exported export date export time.

Explanation: The background import process to service the command import command is importing information exported from server server name with the EXPORT SERVER command on export date at export time.

System Action: Import processing continues.

User Response: None.

ANR0613IImport command: Reading EXPORT POLICY data from server server name exported export date export time.

Explanation: The background import process to service the command import command is importing information exported from server server name with the EXPORT POLICY command on export date at export time.

System Action: Import processing continues.

User Response: None.

ANR0614IImport command: Reading EXPORT ADMIN data from server server name exported export date export time.

Explanation: The background import process to service the command import command is importing information exported from server server name with the EXPORT ADMIN command on export date at export time.

System Action: Import processing continues.

User Response: None.

ANR0615IImport command: Reading EXPORT NODE data from server server name exported export date export time.

Explanation: The background import process to service the command import command is importing information exported from server server name with the EXPORT NODE command on export date at export time.

System Action: Import processing continues.

User Response: None.

ANR0616IExport/import command: Preview processing completed successfully.

Explanation: The background export or import process to service the command export/import command in preview (Preview=Yes) mode has completed successfully.

System Action: Export or import processing for the command completes. Statistics on the projected number and type of objects moved, together with the projected total number of bytes copied, are displayed on the server console following this message.

User Response: None.

ANR0617IExport/import command: Processing completed with status status.

Explanation: The background export or import process to service the command export/import command has completed with status status. If the status is INCOMPLETE, some files have been skipped due to errors reading or writing the file.

System Action: Export or import processing for the command completes. Statistics on the number and type of objects moved, together with the total number of bytes copied, are displayed on the server console following this message. A summary of the number of files that were skipped is also displayed.

User Response: None.

ANR0618IExport/import command: Preview processing canceled before completion.

Explanation: The background export or import process to service the command export/import command in preview (Preview=Yes) mode has been canceled with the CANCEL PROCESS command.

System Action: Export or import processing for the command ends. Statistics on the projected number and type of objects moved, together with the projected total number of bytes copied, are displayed on the server console following this message.

User Response: None.

ANR0619ICommand: Processing canceled before completion.

Explanation: The background process to service the command command has been canceled with the CANCEL PROCESS command.

System Action: Processing for the command command ends. Statistics on the number and type of objects moved, together with the total number of bytes copied, are displayed on the server console following this message.

User Response: None.

ANR0620IExport/import command: Copied number domain(s).

Explanation: The background export or import process to service the command export/import command copies number policy domain definitions from the server database to export media or from export media into the server database. Data is not actually moved if Preview=Yes is specified in the command export/import command.

System Action: Export or import processing for the command completes. Server operation continues.

User Response: None.

ANR0621IExport/import command: Copied number policy sets.

Explanation: The background export or import process to service the command export/import command copies number policy set definitions from the server database to export media or from export media into the server database. Data is not actually moved if Preview=Yes is specified in the command export/import command.

System Action: Export or import processing for the command completes. Server operation continues.

User Response: None.

ANR0622IExport/import command: Copied number management classes.

Explanation: The background export or import process to service the command export/import command copies number management class definitions from the server database to export media or from export media into the server database. Data is not moved if Preview=Yes is specified in the command export/import command.

System Action: Export or import processing for the command completes. Server operation continues.

User Response: None.

ANR0623IExport/import command: Copied number copy groups.

Explanation: The background export or import process to service the command export/import command copies number copy group definitions from either the server database to export media or from export media into the server database. Data is not moved if Preview=Yes is specified in the command export/import command.

System Action: Export or import processing for the command completes. Server operation continues.

User Response: None.

ANR0624IExport/import command: Copied number schedules.

Explanation: The background export or import process to service the command export/import command copies number schedule definitions from either the server database to export media or from export media into the server database. Data is not moved if Preview=Yes is specified in the command export/import command.

System Action: Export or import processing for the command completes. Server operation continues.

User Response: None.

ANR0625IExport/import command: Copied number administrators.

Explanation: The background export or import process to service the command export/import command copies number administrator definitions from either the server database to export media or from export media into the server database. Data is not moved if Preview=Yes is specified in the command export/import command.

System Action: Export or import processing for the command completes. Server operation continues.

User Response: None.

ANR0626IExport/import command: Copied number node definitions.

Explanation: The background export or import process to service the command export/import command copies number client node definitions from the server database to export media or from export media into the server database. Data is not moved if Preview=Yes is specified in the command export/import command.

System Action: Export or import processing for the command completes. Server operation continues.

User Response: None.

ANR0627IExport/import command: Copied filespace number file space archive number archive files, backup number backup files, and spacemg number space managed files.

Explanation: The background export or import process to service the command export/import command copies filespace number client file space definitions, archive number archive file copies, backup number backup file copies, and spacemg number space-managed files from either the server database to export media or from import media into the server database. Data is not actually moved if Preview=Yes is specified in the command export/import command.

System Action: Export or import processing for the command completes. Server operation continues.

User Response: None.

ANR0629IExport/import command: Copied number bytes of data.

Explanation: The background export or import process to service the command export/import command copies number bytes of data from the server database and data storage to the export media or from the export media to the server database and data storage. Data is not moved if Preview=Yes is specified in the command export/import command. This figure can be used during export preview processing to estimate the number of removable media volumes needed to hold the exported information from the server.

System Action: Export or import processing for the command completes. Server operation continues.

User Response: None.

ANR0630IExport/import command: Copied number kilobytes of data.

Explanation: The background export or import process to service the command export/import command copies number kilobytes of data from the server database and data storage to the export media or from the export media to the server database and data storage. This figure can be used during export preview processing to estimate the number of removable media volumes needed to hold the exported information from the server.

System Action: Export or import processing for the command completes. Server operation continues.

User Response: None.

ANR0631IExport/import command: Copied number megabytes of data.

Explanation: The background export or import process to service the command export/import command copies number megabytes of data from the server database and data storage to the export media or from the export media to the server database and data storage. This figure can be used during export preview processing to estimate the number of removable media volumes needed to hold the exported information from the server.

System Action: Export or import processing for the command completes. Server operation continues.

User Response: None.

ANR0632IExport/import command: Copied number gigabytes of data.

Explanation: The background export or import process to service the command export/import command copies number gigabytes of data from the server database and data storage to the export media or from the export media to the server database and data storage. This figure can be used during export preview processing to estimate the number of removable media volumes needed to hold the exported information from the server.

System Action: Export or import processing for the command completes. Server operation continues.

User Response: None.

ANR0633IExport/import command: Copied number terabytes of data.

Explanation: The background export or import process to service the command export/import command copies number terabytes of data from the server database and data storage to the export media or from the export media to the server database and data storage. This figure can be used during export preview processing to estimate the number of removable media volumes needed to hold the exported information from the server.

System Action: Export or import processing for the command completes. Server operation continues.

User Response: None.

ANR0634IExport/import command: Detected number errors.

Explanation: The background export or import process to service the command export/import command detects number errors while copying information from the server database and data storage to the export media or from the export media to the server database and data storage.

System Action: Export or import processing for the command completes. Server operation continues.

User Response: Examine the server messages issued prior to this message to view the error. Use the QUERY ACTLOG command to view the activity log and search for messages.

ANR0635IExport/import command: Processing node node name in domain domain name.

Explanation: The background export or import process to service the command export/import command is currently processing the client node definition information for node node name. The node will be imported to domain domain name.

System Action: Export or import processing for the command continues.

User Response: None.

ANR0636IImport command: Processing file space filespace name for node node name as file space new filespace name.

Explanation: The background import process to service the command import command is currently processing the client file space definition information for file space filespace name belonging to client node node name. The file space is imported under the name new filespace name. During import processing, file spaces defined for clients are not replaced, and file copy information in the file spaces are imported to new file space names so that client file copies are not mixed with existing definitions. Import processing can then create file spaces with names generated by the import processor for client nodes that existed prior to the import operation.

System Action: Import processing for the command continues.

User Response: None; however, clients may want to examine the contents of the file space with the name new filespace name so that they know where certain file copies are kept.

ANR0637IExport/import command: Processing file space filespace name for node node name.

Explanation: The background export or import process to service the command export/import command is currently processing client node file space information for file space filespace name belonging to client node node name.

System Action: Export or import processing for the command continues.

User Response: None.

ANR0638IExport/import command: Processing administrator administrator name.

Explanation: The background export or import process to service the command export/import command is currently processing the administrator definition information for administrator administrator name.

System Action: Export or import processing for the command continues.

User Response: None.

ANR0639IExport/import command: Processing domain domain name.

Explanation: The background export or import process to service the command export/import command is currently processing the policy domain definition information for domain domain name.

System Action: Export or import processing for the command continues.

User Response: None.

ANR0640IExport/import command: Processing policy set set name in policy domain domain name.

Explanation: The background export or import process to service the command export/import command is currently processing the policy set definition information for policy set set name belonging to policy domain domain name.

System Action: Export or import processing for the command continues.

User Response: None.

ANR0641IExport/import command: Processing management class class name in domain domain name, set set name.

Explanation: The background export or import process to service the command export/import command is currently processing the management class definition information for management class class name belonging to policy set set name in policy domain domain name.

System Action: Export or import processing for the command continues.

User Response: None.

ANR0642IExport/import command: Processing backup copy group in domain domain name, set set name, management class class name.

Explanation: The background export or import process to service the command export/import command is currently processing the backup copy group definition information for management class class name belonging to policy set set name in policy domain domain name.

System Action: Export or import processing for the command continues.

User Response: None.

ANR0643IExport/import command: Processing archive copy group in domain domain name, set set name, management class class name.

Explanation: The background export process to service the command export/import command is currently processing the archive copy group definition information for management class class name belonging to policy set set name in policy domain domain name.

System Action: Export processing for the command continues.

User Response: None.

ANR0644IExport command: Processing copy group of unknown type in domain domain name, set set name, management class class name.

Explanation: The background export or import process to service the command export command is currently processing copy group definition information for management class class name belonging to policy set set name in policy domain domain name. The type of copy group being processed is unknown.

System Action: Export or import processing for the command continues. The import or export process assumes that the copy group is a backup copy group.

User Response: After policy definitions are imported, use the QUERY MGMTCLASS and QUERY COPYGROUP commands to query the server definitions for management class class name to ensure that the copy groups defined have the desired attributes and types. Alternatively, the copy group can be deleted and defined with the correct type, and then the export command can be issued again.

ANR0645IExport/import command: Processing schedule schedule name in domain domain name.

Explanation: The background export or import process to service the command export/import command is currently processing the schedule definition information for schedule schedule name belonging to policy domain domain name.

System Action: Export or import processing for the command continues.

User Response: None.

ANR0646IExport/import command: message

Explanation: The background export or import process to service the command export/import command has received the message message from the server.

System Action: Export or import processing for the command continues, but errors may have been encountered.

User Response: Examine the documentation for the message message and resolve the problem reported.

ANR0647ICancel in progress

Explanation: The export or import operation has been canceled and will end when resources have been freed for the background process. This message may be displayed in response to a QUERY PROCESS command for an export or import operation.

System Action: Server operation continues.

User Response: None.

ANR0648IHave copied the following:

Explanation: The export or import operation has copied the number and types of objects displayed. This message may be displayed in response to a QUERY PROCESS command for an export or import operation.

System Action: Server operation continues.

User Response: None.

ANR0649IImport command: Domain domain name does not exist - the system will attempt to import node node name to domain STANDARD.

Explanation: The background import process to service the command import command is currently processing client node node name. This node was assigned to domain domain name at the time of export. However, domain domain name does not exist on the server to which the import is being performed.

System Action: Import processing continues, but node node name will be assigned to domain STANDARD during import unless one of the following conditions exist:

User Response: If Preview=Yes, consider defining domain domain name before nodes are actually imported. Otherwise, domain domain name can be created after the node is imported and the UPDATE NODE command can be used to assign the node to domain domain name.

ANR0650WIMPORT: Archive copygroup copy group name in management class management class name for domain domain name is not defined, default management class will be used.

Explanation: During import processing, the server finds that a management class or copy group bound to an archive file being imported does not exist in the active policy set for the domain to which the node is assigned.

System Action: The default management class for the node's policy domain is bound to the archive file and import processing continues.

User Response: If you want to define the missing management class, an authorized administrator may cancel the import operation, define the missing management class or copy group for the domain, and process the import operation again.

ANR0651WIMPORT: Backup copygroup copy group name in management class management class name for domain domain name is not defined, default management class will be used.

Explanation: During import processing, the server finds that a management class or copy group bound to a backup file being imported does not exist in the active policy set for the domain to which the node is assigned.

System Action: The default management class for the node's policy domain is bound to the backup file copy and import processing continues.

User Response: If you want to define the missing management class, an authorized administrator may cancel the import operation, define the missing management class or copy group for the domain, and process the import operation again.

ANR0652WIMPORT: Archive copygroup not found for default management class in domain domain name - archive files bound to management class management class name in this domain cannot be imported.

Explanation: During import processing, the server finds that a management class or copy group bound to an archive file being imported does not exist in the active policy set for the domain to which the node is assigned. When trying to rebind the archive file to the default management class for the domain, the server finds that an archive copy group is not defined for the default management class.

System Action: The file is not imported; import processing continues.

User Response: If you want to define the missing copy group, an authorized administrator may cancel the import operation, define the missing management class or copy group for the domain, and process the import operation again.

ANR0653WIMPORT: Backup copygroup not found for default management class in domain domain name - backup files bound to management class management class name in this domain cannot be imported.

Explanation: During import processing, the server finds that a management class or copy group bound to a backup file being imported does not exist in the active policy set for the domain to which the node is assigned. When trying to rebind the backup file to the default management class for the domain, the server finds that a backup copy group is not defined for the default management class.

System Action: The file is not imported; import processing continues.

User Response: If you want to define the missing copy group, an authorized administrator may cancel the import operation, define the missing management class or copy group for the domain, and process the import operation again.

ANR0655WCommand: Retrieve or restore failed - file was deleted from data storage during retrieval.

Explanation: The server ends a file retrieval operation for the specified command because the file has been deleted from data storage by another process before retrieval is complete.

System Action: The server ends the command and continues operation.

User Response: Contact your administrator to find out if DELETE FILESPACE, DELETE VOLUME, or inventory expiration processes are running; these processes can delete data storage files during retrieval. Reissue the command after these processes have been completed or canceled.

ANR0656WExport/import command: Skipped archive number archive files, backup number backup files, and spacemg number space managed files.

Explanation: The background export or import process to service the command export/import command skipped archive number archive file copies, backup number backup file copies, and spacemg number space-managed files from either the server database to export media or from import media into the server database. Data is not actually moved if Preview=Yes is specified in the command export/import command.

System Action: Export or import processing for the command completes. Server operation continues.

User Response: Check previous messages for the names of the files that were not exported or imported, and problem determination information.

ANR0657WExport command: Invalid authorization rule type rule type encountered for file space filespace name in node node name - both backup and archive will be assumed during import.

Explanation: During import processing, the server encounters an invalid file space authorization rule type for the indicated file space and node.

System Action: Server operation continues.

User Response: After import processing is completed, ask the user of node node name to query the access rules and ensure that they are specified as desired. The user should correct any rules that grant access to objects that the user does not want others to access.

ANR0658WExport command: The password for administrator administrator name could not be obtained. The value 'password value' will be assumed: The system administrator may wish to change this password after importing administrator administrator name.

Explanation: During processing of command export command, the export processor cannot obtain the password for administrator administrator name. The value password value is assigned as the password for the administrator on the export media.

System Action: Processing of the command continues.

User Response: After the administrative definition has been imported to another server, an authorized administrator should use the UPDATE ADMIN command to set a password for the administrator administrator name.

ANR0659WExport command: The password for node node name could not be obtained. The value 'password value' will be assumed: The system administrator may wish to change this password after importing node node name.

Explanation: During processing of command export command, the export processor cannot obtain the password for client node node name. The value password value is assigned as the password for the client node on the export media.

System Action: Processing of the command continues.

User Response: After the client node definition has been imported to another server, an authorized administrator should use the UPDATE NODE command to set a password for the node node name.

ANR0660ECommand: Insufficient memory available in accessing data storage.

Explanation: The server encounters a memory shortage in accessing data storage during command command operation.

System Action: The command command operation ends and server operation continues.

User Response: Allocate additional storage to the server. For details, issue HELP MEMORY to display the information online or see "Appendix A. Allocating Additional Server Memory".

ANR0661ECommand: Internal error encountered in accessing data storage.

Explanation: The server encounters an internal error in accessing data storage while processing command command operation.

System Action: The command command operation is ended and server operation continues.

User Response: Use the QUERY ACTLOG command to examine messages prior to this error to determine the cause of the data storage failure. If the failure can be found and resolved, reissue the command command operation. If the failure cannot be found, contact your service representative for assistance in resolving the problem.

ANR0662ECommand: Output error encountered in accessing data storage.

Explanation: The command command operation ends because an error has been encountered by the server in writing to a device. Possible reasons include:

System Action: The command command operation ends and server operation continues.

User Response: Query the activity log to find messages preceding this one to determine the cause of the error. After the problem is corrected, the command can be retried.

ANR0663ECommand: Data transfer was interrupted in accessing data storage.

Explanation: The database transaction associated with command command operation failed because data transfer to or from data storage was interrupted by an external event.

System Action: The command command operation is ended and server operation continues.

User Response: Examine the messages issued prior to this message to determine why the data transfer was interrupted. Reissue the command command after the problem is resolved.

ANR0664EExport/import command: Media not accessible in accessing data storage.

Explanation: The server ends a transaction for an export or import operation because storage volumes are not available in the storage pools in which the client files are to be stored.

System Action: The server ends the export or import operation and server operation continues.

User Response: An authorized administrator can issue the DEFINE VOLUME command to add storage to one or more storage pools in the storage hierarchy. The VARY ONLINE command can be used to vary offline storage volumes online in the storage hierarchy to make them available for file storage.

ANR0665WImport command: Transaction failed - storage pool pool name is not defined.

Explanation: The server rolls back a database update transaction for an import operation because the destination specified for a management class copy group specifies the named storage pool, but that storage pool does not exist.

System Action: The import operation is ended and server operation continues.

User Response: An administrator with policy authority over the client policy domain must correct management class definitions so that copy group destinations refer to defined storage pools, or the specified storage pool must be created by an authorized administrator.

ANR0666WImport command: Transaction failed - object excluded by size in storage pool pool name and all successor pools.

Explanation: The server ends a database update transaction for an import operation because the size of an imported file is larger than that allowed in the storage pool specified in the bound management class copy group for the file. No successor storage pools to the one specified on the copy group can accept the large file.

System Action: The import operation is ended and server operation continues.

User Response: The maximum file size for one or more of the storage pools in the storage hierarchy can be increased to accommodate the file. An authorized administrator can increase the MAXSIZE parameter by issuing the UPDATE STGPOOL command. Alternatively, the appropriate copygroup definition can be updated so that a different destination storage pool is specified.

ANR0667WImport command: Transaction failed - no space available in storage pool pool name and all successor pools.

Explanation: The server ends an import operation because the storage pool specified in a management class copy group does not contain enough free space to hold the files being imported. Successor storage pools to the one specified on the copy group do not contain enough free space.

System Action: The import operation is ended and server operation continues.

User Response: An authorized administrator can issue the DEFINE VOLUME command to add storage to one or more storage pools in the storage hierarchy.

ANR0668WExport/import command: Transaction failed - error on output storage device.

Explanation: The server ends an export or import operation for the specified session because an I/O error has been encountered by the server in writing to a device.

System Action: The server ends the export or import operation and server operation continues.

User Response: Query the activity log to find messages preceding this one that specify the device that is failing. Storage pool volumes can be varied offline (by using the VARY OFFLINE command), or the server may need to be shut down by using the HALT command to correct the hardware problem. After the problem is corrected, the client may be able to try the operation again.

ANR0669WExport/import command: Transaction failed - data transfer interrupted.

Explanation: The database transaction associated with an export or import operation failed because data transfer to or from data storage was interrupted by an external event.

System Action: The export or import operation is ended and server operation continues.

User Response: Examine the messages issued prior to this message to determine why the data transfer was interrupted. Attempt the export/import operation again after problem is resolved.

ANR0670WExport/import command: Transaction failed - storage media inaccessible.

Explanation: The server ends a transaction for an export or import operation because storage volumes are not available in the storage pools in which the client files are to be stored.

System Action: The server ends the export or import operation and server operation continues.

User Response: An authorized administrator can issue the DEFINE VOLUME command to add storage to one or more storage pools in the storage hierarchy. The VARY ONLINE command can be used to vary offline storage volumes online in the storage hierarchy to make them available for file storage.

ANR0671WExport/import command: Transaction failed - sufficient recovery log space is not available.

Explanation: The server ends a database update transaction for an export or import operation because sufficient log space is not available on the server.

System Action: The server ends the export or import operation and server operation continues.

User Response: An authorized administrator can issue the DEFINE LOGVOLUME command to add volumes for use by the log, and the EXTEND LOG command to extend the size of the log so that the new volumes are used.

ANR0672WExport/import command: Transaction failed - sufficient database space is not available.

Explanation: The server ends a database update transaction for an export or import operation because sufficient database space is not available on the server.

System Action: The server ends the export or import operation and server operation continues.

User Response: An authorized administrator can issue the DEFINE DBVOLUME command to add volumes for use by the database, and the EXTEND DB command to extend the size of the log so that the new volumes are used.

ANR0673WExport/import command: Data storage retrieve or restore failed - data integrity error detected.

Explanation: The server ends an export or import operation because an internal database integrity error has been encountered on the server.

System Action: The server ends the export or import operation and continues operation.

User Response: Contact your service representative.

ANR0674WExport command: Retrieve failed - error on input storage device.

Explanation: The server ends an export operation for the specified session because an I/O error has been encountered by the server in reading from a device. The object for which the I/O was issued is reported in a later message.

System Action: Export processing skips this file, and continues operation.

User Response: Query the activity log to find messages preceding this one that specify the device that is failing. Storage pool volumes can be varied offline (by using the VARY OFFLINE command), or the server may need to be shut down with the HALT command to correct the hardware problem.

ANR0675EEXPORT/IMPORT: Error starting the Export/Import Session.

Explanation: The server export/import process is not able to start the session to export information from the server or import information into the server.

System Action: The export or import process ends and server operation continues.

User Response: Allocate additional storage to the server. For details, issue HELP MEMORY to display the information online or see "Appendix A. Allocating Additional Server Memory".

ANR0676EEXPORT/IMPORT: Invalid Communications Buffer State in SEND.

Explanation: The server export/import process encounters a communications error in transferring information to or from the server.

System Action: The export or import process ends and server operation continues.

User Response: Contact your service representative.

ANR0677EEXPORT/IMPORT: Invalid Communications Buffer State in RECEIVE.

Explanation: The server export/import process encounters a communications error in transferring information to or from the server.

System Action: The export or import process ends and server operation continues.

User Response: Contact your service representative.

ANR0678EEXPORT/IMPORT: Communications Failure in Sending "verb type" verb.

Explanation: The server export/import process encounters a communications error in using the verb type verb to transfer information to or from the server.

System Action: The export or import process ends and server operation continues.

User Response: Contact your service representative.

ANR0679EEXPORT/IMPORT: Communications Failure in Receiving "verb type" verb.

Explanation: The server export/import process encounters a communications error in using the verb type verb to transfer information to or from the server.

System Action: The export or import process ends and server operation continues.

User Response: Contact your service representative.

ANR0681EEXPORT/IMPORT: Authentication Failure.

Explanation: The server export/import process encounters an authentication error in transferring information to or from the server.

System Action: The export or import process ends and server operation continues.

User Response: Contact your service representative.

ANR0682EEXPORT/IMPORT: Communications Failure in Sending "verb type" verb (command).

Explanation: The server export/import process encounters a communications error in using the verb type verb to issue command command.

System Action: The export or import process ends and server operation continues.

User Response: Contact your service representative.

ANR0683EEXPORT/IMPORT: Receive Buffer overflow.

Explanation: The server export/import process encounters an overflow error in transferring information to or from the server.

System Action: The export or import process ends and server operation continues.

User Response: Contact your service representative.

ANR0684EEXPORT/IMPORT: Communications failure: bad verb received (verb type).

Explanation: The server encounters an invalid communications verb during export or import processing and is not able to continue processing.

System Action: The export or import process ends and server operation continues.

User Response: Contact your service representative.

ANR0685EEXPORT/IMPORT: Internal error: Invalid table output handle detected.

Explanation: The server export/import process encounters an internal error in transferring information to or from the server.

System Action: The export or import process ends and server operation continues.

User Response: Contact your service representative.

ANR0686EExport/import command: Transaction failure - could not start database transaction.

Explanation: During processing of command export/import command, a database transaction cannot be started in the server database.

System Action: Processing of the command terminates.

User Response: Examine the server messages issued prior to this message to determine the source of the error. Use the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative.

ANR0687EExport/import command: Transaction failure - could not commit database transaction.

Explanation: During processing of command export/import command, a database transaction cannot be committed to the server database.

System Action: Processing of the command ends.

User Response: Examine the server messages issued prior to this message to determine the source of the error. Use the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative.

ANR0688EExport/import command: Transaction failure - commit called when no transaction started.

Explanation: During processing of command export/import command, a database transaction cannot be started in the server database.

System Action: Processing of the command ends.

User Response: Examine the server messages issued prior to this message to determine the source of the error. Use the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative.

ANR0689WImport command: Client platform type (platform type) for imported node node name conflicts with an existing node with the same name - the node will not be imported.

Explanation: During import processing, the server encounters an imported node definition that has the same name as an existing node, but has a different client platform type (for example, OS/2 or AIX). Because file data may not be compatible across different client platforms, the node is not imported.

System Action: Import processing continues, and the named node is skipped by import processing.

User Response: If you want to import the named node, cancel the import process, rename the existing node to a new name by using the RENAME NODE command, and run the import again. After you have imported the node, use the RENAME NODE command to set the node names as you desire.

ANR0690EExport/import command: Transaction failure - server aborted the transaction (abort code).

Explanation: During processing of command export/import command, a database transaction cannot be committed in the server database. The reason code abort code is returned.

System Action: Processing of the command ends.

User Response: Examine the server messages issued prior to this message to determine the source of the error. Use the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative.

ANR0691EExport command: Error abort code writing export data.

Explanation: During processing of command export command, an input/output error occurs when writing the exported information to the export media.

System Action: Processing of the command ends.

User Response: Examine the server messages issued prior to this message to determine the source of the error. Use the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative.

ANR0692ECommand: Out of space on sequential media, scratch media could not be mounted.

Explanation: During command command processing, the process encounters an out-of-space condition writing to the sequential media. Command command ends when there is no more space on the sequential media for storing data and SCRATCH=NO has been specified on command command.

System Action: Command command processing ends. Server processing continues.

User Response: Reissue the command and specify SCRATCH=YES or specify additional volume names on the command.

ANR0693EImport command: Error abort code reading export data.

Explanation: During processing of command import command, an input/output error occurs when reading the exported information from the export media.

System Action: Processing of the command ends.

User Response: Examine the server messages issued prior to this message to determine the source of the error. Use the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative.

ANR0694EImport command: Invalid record format (format code) detected on import.

Explanation: During processing of command import command, an invalid record type is detected when reading the exported information from the export media.

System Action: Processing of the command ends.

User Response: Examine the server messages issued prior to this message to determine the source of the error. Use the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative.

ANR0695EExport command: Unexpected error error code encountered in receiving table output data.

Explanation: During processing of command export command, an unexpected error is detected.

System Action: Processing of the command ends.

User Response: Examine the server messages issued prior to this message to determine the source of the error. Use the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative.

ANR0696EExport command: Output table error encountered - 0 columns reported in the table.

Explanation: During processing of command export command, an unexpected error is detected.

System Action: Processing of the command ends.

User Response: Examine the server messages issued prior to this message to determine the source of the error. Use the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative.

ANR0697EExport command: Output table error encountered - not positioned to the first column in the table.

Explanation: During processing of command export command, an unexpected error is detected.

System Action: Processing of the command ends.

User Response: Examine the server messages issued prior to this message to determine the source of the error. Use the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative.

ANR0698EExport/import command: Invalid value for FILEDATA parameter - parameter value.

Explanation: The value (parameter value) specified for the FILEDATA parameter in command export/import command is not a valid value for this parameter.

System Action: The command fails and server operation continues.

User Response: Reissue the command and specify a valid FILEDATA parameter. For information on valid values for the FILEDATA parameter for the command, refer to the Administrator's Reference for your particular platform.

ANR0699EExport/import command: Device class DISK cannot be specified for this command.

Explanation: The DEVCLASS value DISK cannot be specified for the command export/import command.

System Action: The command fails and server operation continues.

User Response: Reissue the command and specify a valid device class. Issue the QUERY DEVCLASS command for a list of valid device classes for the server.

ANR0700EExport/import command: Invalid value for PREVIEW parameter - parameter value.

Explanation: The value (parameter value) specified for the PREVIEW parameter in command export/import command is not a valid value for this parameter.

System Action: The command fails and server operation continues.

User Response: Reissue the command and specify a valid PREVIEW parameter. For information on valid values for the PREVIEW parameter for the command, refer to the Administrator's Reference for your particular platform.

ANR0701EExport/import command: Invalid value for SCRATCH parameter - parameter value.

Explanation: The value (parameter value) specified for the SCRATCH parameter in command export/import command is not a valid value for this parameter.

System Action: The command fails and server operation continues.

User Response: Reissue the command and specify a valid SCRATCH parameter. For information on valid values for the SCRATCH parameter for the command, refer to the Administrator's Reference for your particular platform.

ANR0705EExport command: The VOLUMENAMES parameter must be specified when SCRATCH=NO is specified.

Explanation: The SCRATCH parameter is specified as NO for the command export command but the VOLUMENAMES parameter is not specified. When scratch volumes are not allowed, the VOLUMENAMES parameter must be specified to indicate the volumes that can be used for the command.

System Action: The command fails and server operation continues.

User Response: Reissue the command and specify a valid VOLUMENAMES parameter. For information on valid parameter values for the command, refer to the Administrator's Reference for your particular platform.

ANR0706EExport command: A device class must be specified unless PREVIEW=YES is specified.

Explanation: The DEVCLASS parameter is not specified in the command export command. Unless PREVIEW=YES is specified, a DEVCLASS value must be specified.

System Action: The command fails and server operation continues.

User Response: Reissue the command and specify a valid device class. Issue the QUERY DEVCLASS command for a list of valid device classes for the server.

ANR0707EExport command: The FILESPACE parameter cannot be specified.

Explanation: The FILESPACE parameter is specified for the command export command, but the FILEDATA parameter is specified as NONE, or is not specified and defaults to NONE. File spaces are only copied if the FILEDATA parameter is specified with a value other than NONE.

System Action: The command fails and server operation continues.

User Response: Reissue the command and specify a valid FILEDATA parameter. For information on valid parameter values for the command, refer to the Administrator's Reference for your particular platform.

ANR0708EImport command: The FILESPACE parameter cannot be specified unless the FILEDATA parameter specifies that files should be imported.

Explanation: The FILESPACE parameter is specified for the command import command, but the FILEDATA parameter is specified as NONE, or is not specified and defaults to NONE. File spaces are only copied if the FILEDATA parameter is specified with a value other than NONE.

System Action: The command fails and server operation continues.

User Response: Reissue the command and specify a valid FILEDATA parameter. For information on valid parameter values for the command, refer to the Administrator's Reference for your particular platform.

ANR0709ECommand: No matching nodes registered in the specified domains.

Explanation: The DOMAIN parameter has been specified for this command, but no nodes matching the node name specification are found in the domains specified.

System Action: The command fails and server operation continues.

User Response: Reissue the command and specify a valid combination of node and domain names. Use the QUERY NODE command to view the names of nodes in the domains that you are interested in exporting.

ANR0710ECommand: Unable to start background process.

Explanation: The server command processor is not able to start a background process to perform the command command.

System Action: The command process ends and server operation continues.

User Response: Allocate additional storage to the server. For details, issue HELP MEMORY to display the information online or see "Appendix A. Allocating Additional Server Memory".

ANR0711EImport command: Unable to start import process.

Explanation: The server import command processor is not able to start a background process to perform the import operation.

System Action: The export or import process ends and server operation continues.

User Response: Allocate additional storage to the server. For details, issue HELP MEMORY to display the information online or see "Appendix A. Allocating Additional Server Memory".

ANR0712EImport command: Invalid value for DATES parameter - parameter value.

Explanation: The value (parameter value) specified for the DATES parameter in command import command is not a valid value for this parameter.

System Action: The command fails and server operation continues.

User Response: Reissue the command and specify a valid DATES parameter. For information on valid values for the DATES parameter for the command, refer to the Administrator's Reference for your particular platform.

ANR0713EImport command: Invalid value for REPLACEDEFS parameter - parameter value.

Explanation: The value (parameter value) specified for the REPLACEDEFS parameter in command import command is not a valid value for this parameter.

System Action: The command fails and server operation continues.

User Response: Reissue the command and specify a valid REPLACEDEFS parameter. For information on valid values for the REPLACEDEFS parameter for the command, refer to the Administrator's Reference for your particular platform.

ANR0714EImport command: The EXTFILE device class cannot be specified when the VOLUMENAMES parameter is specified.

Explanation: An invalid combination of parameters has been entered for command import command. The EXTFILE device class cannot be used in combination with the VOLUMENAMES parameter.

System Action: The command fails and server operation continues.

User Response: Reissue the command with the correct syntax.

ANR0715EImport command: A device class must be specified.

Explanation: The command import command has been specified, but does not include specification of the DEVCLASS parameter. The DEVCLASS parameter must be specified for this command.

System Action: The command fails and server operation continues.

User Response: Reissue the command and specify a valid device class. For a list of valid device classes for the server, issue the QUERY DEVCLASS command.

ANR0716EImport command: Invalid export data detected.

Explanation: The command import command encounters invalid data on the export media while trying to import server information.

System Action: The command fails and server operation continues.

User Response: Ensure that the mounted export tapes are in the correct order (mounted in the same order as they were mounted during export). Reissue the command, and mount the tapes in the correct order. If the VOLUMENAMES parameter has been specified, make sure that the volume names in the command are specified in the correct order.

ANR0717EExport/import command: Preview processing terminated abnormally - communications send or receive failed.

Explanation: Processing for the command export/import command in preview mode has been terminated when an internal communications error is encountered in the server.

System Action: Export/import processing is ended and server operation continues.

User Response: Examine the server messages issued prior to this message to determine the source of the error. Use the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative.

ANR0718EExport/import command: Processing terminated abnormally - communications send or receive failed.

Explanation: Processing for the command export/import command ends when an internal communications error is encountered in the server.

System Action: Export/import processing is ended and server operation continues.

User Response: Examine the server messages issued prior to this message to determine the source of the error. Use the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative.

ANR0719EExport/import command: Preview processing terminated abnormally - insufficient memory.

Explanation: Processing for the command export/import command in preview mode is ended because sufficient memory is not available on the server.

System Action: Export/import processing is ended and server operation continues.

User Response: Allocate additional storage to the server. For details, issue HELP MEMORY to display the information online or see "Appendix A. Allocating Additional Server Memory".

ANR0720Ecommand: Processing terminated abnormally - insufficient memory.

Explanation: Processing for the command ends because sufficient memory is not available on the server.

System Action: Command processing is ended and server operation continues.

User Response: Allocate additional storage to the server. For details, issue HELP MEMORY to display the information online or see "Appendix A. Allocating Additional Server Memory".

ANR0721EExport/import command: Preview processing terminated abnormally - unexpected verb received from server.

Explanation: Processing for the command export/import command in preview mode ends when an internal communications error is encountered in the server.

System Action: Export/import processing ends and server operation continues.

User Response: Examine the server messages issued prior to this message to determine the source of the error. Use the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative.

ANR0722EExport/import command: Processing terminated abnormally - unexpected verb received from server.

Explanation: Processing for the command export/import command ends when an internal communications error is encountered in the server.

System Action: Export/import processing ends and server operation continues.

User Response: Examine the server messages issued prior to this message to determine the source of the error. Use the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative.

ANR0723EExport/import command: Preview processing terminated abnormally - transaction failure.

Explanation: Processing for the command export/import command in preview mode ends when a database transaction error is encountered in the server.

System Action: Export/import processing ends and server operation continues.

User Response: Examine the server messages issued prior to this message to determine the source of the error. Use the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative.

ANR0724EExport/import command: Processing terminated abnormally - transaction failure.

Explanation: Processing for the command export/import command ends when a database transaction error is encountered in the server.

System Action: Export/import processing ends and server operation continues.

User Response: Examine the server messages issued prior to this message to determine the source of the error. Use the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative.

ANR0725EExport/import command: Preview processing terminated abnormally - authentication failure.

Explanation: Processing for the command export/import command in preview mode ends when an authentication error is encountered in the server.

System Action: Export/import processing ends and server operation continues.

User Response: Examine the server messages issued prior to this message to determine the source of the error. Use the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative.

ANR0726EExport/import command: Processing terminated abnormally - authentication failure.

Explanation: Processing for the command export/import command ends when an authentication error is encountered in the server.

System Action: Export/import processing ends and server operation continues.

User Response: Examine the server messages issued prior to this message to determine the source of the error. Use the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative.

ANR0727EExport/import command: Preview processing terminated abnormally - internal error.

Explanation: Processing for the command export/import command in preview mode ends when an internal error is encountered in the server.

System Action: Export/import processing ends and server operation continues.

User Response: Examine the server messages issued prior to this message to determine the source of the error. Use the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative.

ANR0728EExport/import command: Processing terminated abnormally - internal error.

Explanation: Processing for the command export/import command ends when an internal error is encountered in the server.

System Action: Export/import processing ends and server operation continues.

User Response: Examine the server messages issued prior to this message to determine the source of the error. Use the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative.

ANR0729EImport command: Syntax error from command \'server command\'.

Explanation: During processing of the command import command, an internal syntax error is encountered in the server.

System Action: Import processing continues, but the indicated command will have no effect.

User Response: Examine the server messages issued prior to this message to determine the source of the error. Use the QUERY ACTLOG command to view the activity log and search for messages. After import processing is complete, it may be necessary to issue additional commands manually to obtain the necessary definitions.

ANR0730EImport command: Internal error from command \'server command\'.

Explanation: Processing for the command import command ends when an internal command error is encountered in the server.

System Action: Import processing ends and server operation continues.

User Response: Examine the server messages issued prior to this message to determine the source of the error. Use the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative.

ANR0731EImport command: Invalid value for COMPRESSION parameter in exported data for node node name.

Explanation: During preview processing of command import command, an invalid value is encountered for the COMPRESSION parameter for node node name.

System Action: Processing of the command continues. If a later command causes the data to be imported, the default or existing COMPRESSION value is used.

User Response: None. If the data is imported with a later command, verify that the correct COMPRESSION value is used for this node.

ANR0732EImport command: Invalid value for ARCHDELETE parameter in exported data for node node name.

Explanation: During preview processing of command import command, an invalid value is encountered for the ARCHDELETE parameter for node node name.

System Action: Processing of the command continues. If a later command causes the data to be imported, the default or existing ARCHDELETE value is used.

User Response: None. If the data is imported with a later command, verify that the correct ARCHDELETE value is used for this node.

ANR0733EImport command: Invalid value for BACKDELETE parameter in exported data for node node name.

Explanation: During preview processing of command import command, an invalid value is encountered for the BACKDELETE parameter for node node name.

System Action: Processing of the command continues. If a later command causes the data to be imported, the default or existing BACKDELETE value is used.

User Response: None. If the data is imported with a later command, verify that the correct BACKDELETE value is used for this node.

ANR0734EImport command: Invalid value for COMPRESSION parameter in exported data - node node name registered with default COMPRESSION value.

Explanation: During processing of command import command, an invalid value is encountered for the COMPRESSION parameter for node node name.

System Action: Processing of the command continues, by using the default COMPRESSION value for this node.

User Response: Verify that the correct COMPRESSION value has been used for this node. Update this value, if necessary.

ANR0735EImport command: Invalid value for ARCHDELETE parameter in exported data - node node name registered with default ARCHDELETE value.

Explanation: During processing of command import command, an invalid value is encountered for the ARCHDELETE parameter for node node name.

System Action: Processing of the command continues, by using the default ARCHDELETE value for this node.

User Response: Verify that the correct ARCHDELETE value has been used for this node. Update this value, if necessary.

ANR0736EImport command: Invalid value for BACKDELETE parameter in exported data - node node name registered with default BACKDELETE value.

Explanation: During processing of command import command, an invalid value is encountered for the BACKDELETE parameter for node node name.

System Action: Processing of the command continues, by using the default BACKDELETE value for this node.

User Response: Verify that the correct BACKDELETE value has been used for this node. Update this value, if necessary.

ANR0737EImport command: Invalid value for COMPRESSION parameter in exported data - existing COMPRESSION value for node node name was not updated.

Explanation: During processing of command import command, an invalid value is encountered for the COMPRESSION parameter for node node name.

System Action: Processing of the command continues, by using the existing COMPRESSION value for this node.

User Response: Verify that the correct COMPRESSION value has been used for this node. Update this value, if necessary.

ANR0738EImport command: Invalid value for ARCHDELETE parameter in exported data - existing ARCHDELETE value for node node name was not updated.

Explanation: During processing of command import command, an invalid value is encountered for the ARCHDELETE parameter for node node name.

System Action: Processing of the command continues, by using the existing ARCHDELETE value for this node.

User Response: Verify that the correct ARCHDELETE value has been used for this node. Update this value, if necessary.

ANR0739EImport command: Invalid value for BACKDELETE parameter in exported data - existing BACKDELETE value for node node name was not updated.

Explanation: During processing of command import command, an invalid value is encountered for the BACKDELETE parameter for node node name.

System Action: Processing of the command continues, by using the existing BACKDELETE value for this node.

User Response: Verify that the correct BACKDELETE value has been used for this node. Update this value, if necessary.

ANR0740EImport command: Invalid value for TYPE parameter in exported data for copy group copy group name in domain domain name, set policy set name, management class management class name - backup is assumed.

Explanation: During processing of command import command, an invalid value is encountered for the TYPE parameter for copy group copy group, in policy domain domain name, policy set policy set name, management class management class name.

System Action: Processing of the command continues. Based upon other copy group parameters, a copy group type of backup is assigned.

User Response: Verify that the assigned TYPE value of backup for this copy group is correct.

ANR0741EImport command: Invalid value for TYPE parameter in exported data for copy group copy group name in domain domain name, set policy set name, management class management class name - archive is assumed.

Explanation: During processing of command import command, an invalid value is encountered for the TYPE parameter for copy group copy group, in policy domain domain name, policy set policy set name, management class management class name.

System Action: Processing of the command continues. Based upon other copy group parameters, a copy group type of archive is assigned.

User Response: Verify that the assigned TYPE value of archive for this copy group is correct.

ANR0742EImport command: Invalid value for TYPE parameter in exported data for copy group copy group name in domain domain name, set policy set name, management class management class name - this copy group will not be imported.

Explanation: During processing of command import command, an invalid value is encountered for the TYPE parameter for copy group copy group, in policy domain domain name, policy set policy set name, management class management class name.

System Action: Processing of the command continues. However, this copy group is not imported because a TYPE value cannot be assigned.

User Response: Manually define this copy group, if necessary.

ANR0743EImport command: Invalid value for MODE parameter in exported data for archive copy group copy group name in domain domain name, set policy set name, management class management class name.

Explanation: During preview processing of command import command, an invalid value is encountered for the MODE parameter for archive copy group copy group name, in policy domain domain name, policy set policy set name, management class management class name.

System Action: Processing of the command continues. If a later command causes the data to be imported, the default or existing MODE value is used.

User Response: None. If the data is imported with a later command, verify that the correct MODE value is used for this archive copy group.

ANR0744EImport command: Invalid value for MODE parameter in exported data for backup copy group copy group name in domain domain name, set policy set name, management class management class name.

Explanation: During preview processing of command import command, an invalid value is encountered for the MODE parameter for backup copy group copy group name, in policy domain domain name, policy set policy set name, management class management class name.

System Action: Processing of the command continues. If a later command causes the data to be imported, the default or existing MODE value is used.

User Response: None. If the data is imported with a later command, verify that the correct MODE value is used for this backup copy group.

ANR0745EImport command: Invalid value for SERIALIZATION parameter in exported data for archive copy group copy group name in domain domain name, set policy set name, management class management class name.

Explanation: During preview processing of command import command, an invalid value is encountered for the SERIALIZATION parameter for archive copy group copy group name, in policy domain domain name, policy set policy set name, management class management class name.

System Action: Processing of the command continues. If a later command causes the data to be imported, the default or existing SERIALIZATION value is used.

User Response: None. If the data is imported with a later command, verify that the correct SERIALIZATION value is used for this archive copy group.

ANR0746EImport command: Invalid value for SERIALIZATION parameter in exported data for backup copy group copy group name in domain domain name, set policy set name, management class management class name.

Explanation: During preview processing of command import command, an invalid value is encountered for the SERIALIZATION parameter for backup copy group copy group name, in policy domain domain name, policy set policy set name, management class management class name.

System Action: Processing of the command continues. If a later command causes the data to be imported, the default or existing SERIALIZATION value is used.

User Response: None. If the data is imported with a later command, verify that the correct SERIALIZATION value is used for this backup copy group.

ANR0747EImport command: Invalid value for MODE parameter in exported data - archive copy group copy group name in domain domain name, set policy set name, management class management class name defined with default MODE value.

Explanation: During processing of command import command, an invalid value is encountered for the MODE parameter for archive copy group copy group name, in policy domain domain name, policy set policy set name, management class management class name.

System Action: Processing of the command continues, by using the default MODE value for this archive copy group.

User Response: Verify that the correct MODE value has been used for this copy group. Update this value, if necessary.

ANR0748EImport command: Invalid value for MODE parameter in exported data - backup copy group copy group name in domain domain name, set policy set name, management class management class name defined with default MODE value.

Explanation: During processing of command import command, an invalid value is encountered for the MODE parameter for backup copy group copy group name, in policy domain domain name, policy set policy set name, management class management class name.

System Action: Processing of the command continues, by using the default MODE value for this backup copy group.

User Response: Verify that the correct MODE value has been used for this copy group. Update this value, if necessary.

ANR0749EImport command: Invalid value for SERIALIZATION parameter in exported data - archive copy group copy group name in domain domain name, set policy set name, management class management class name defined with default SERIALIZATION value.

Explanation: During processing of command import command, an invalid value is encountered for the SERIALIZATION parameter for archive copy group copy group name, in policy domain domain name, policy set policy set name, management class management class name.

System Action: Processing of the command continues, by using the default SERIALIZATION value for this archive copy group.

User Response: Verify that the correct SERIALIZATION value has been used for this copy group. Update this value, if necessary.

ANR0750EImport command: Invalid value for SERIALIZATION parameter in exported data - backup copy group copy group name in domain domain name, set policy set name, management class management class name defined with default SERIALIZATION value.

Explanation: During processing of command import command, an invalid value is encountered for the SERIALIZATION parameter for backup copy group copy group name, in policy domain domain name, policy set policy set name, management class management class name.

System Action: Processing of the command continues, by using the default SERIALIZATION value for this backup copy group.

User Response: Verify that the correct SERIALIZATION value has been used for this copy group. Update this value, if necessary.

ANR0751EImport command: Invalid value for MODE parameter in exported data - existing MODE value for archive copy group copy group name in domain domain name, set policy set name, management class management class name was not updated.

Explanation: During processing of command import command, an invalid value is encountered for the MODE parameter for archive copy group copy group name, in policy domain domain name, policy set policy set name, management class management class name.

System Action: Processing of the command continues, by using the existing MODE value for this archive copy group.

User Response: Verify that the correct MODE value has been used for this copy group. Update this value, if necessary.

ANR0752EImport command: Invalid value for MODE parameter in exported data - existing MODE value for backup copy group copy group name in domain domain name, set policy set name, management class management class name was not updated.

Explanation: During processing of command import command, an invalid value is encountered for the MODE parameter for backup copy group copy group name, in policy domain domain name, policy set policy set name, management class management class name.

System Action: Processing of the command continues, by using the existing MODE value for this backup copy group.

User Response: Verify that the correct MODE value has been used for this copy group. Update this value, if necessary.

ANR0753EImport command: Invalid value for SERIALIZATION parameter in exported data - existing SERIALIZATION value for archive copy group copy group name in domain domain name, set policy set name, management class management class name was not updated.

Explanation: During processing of command import command, an invalid value is encountered for the SERIALIZATION parameter for archive copy group copy group name, in policy domain domain name, policy set policy set name, management class management class name.

System Action: Processing of the command continues, by using the existing SERIALIZATION value for this archive copy group.

User Response: Verify that the correct SERIALIZATION value has been used for this copy group. Update this value, if necessary.

ANR0754EImport command: Invalid value for SERIALIZATION parameter in exported data - existing SERIALIZATION value for backup copy group copy group name in domain domain name, set policy set name, management class management class name was not updated.

Explanation: During processing of command import command, an invalid value is encountered for the SERIALIZATION parameter for backup copy group copy group name, in policy domain domain name, policy set policy set name, management class management class name.

System Action: Processing of the command continues, by using the existing SERIALIZATION value for this backup copy group.

User Response: Verify that the correct SERIALIZATION value has been used for this copy group. Update this value, if necessary.

ANR0755EImport command: Invalid value for ACTION parameter in exported data for schedule schedule name in domain domain name.

Explanation: During preview processing of command import command, an invalid value is encountered for the ACTION parameter for schedule schedule name in policy domain domain name.

System Action: Processing of the command continues. If a later command causes the data to be imported, the default or existing ACTION value is used.

User Response: If the data is imported with a later command, verify that the correct ACTION value is used for this schedule.

ANR0756EImport command: Invalid value for DURUNITS or PERUNITS parameter in exported data for schedule schedule name in domain domain name.

Explanation: During preview processing of command import command, an invalid value is encountered for the DURUNITS or PERUNITS parameter for schedule schedule name in policy domain domain name.

System Action: Processing of the command continues. If a later command causes the data to be imported, the default or existing values are used for DURATION, DURUNITS, PERIOD, and PERUNITS.

User Response: If the data is imported with a later command, verify that the correct values for DURATION, DURUNITS, PERIOD, and PERUNITS are used for this schedule.

ANR0757EImport command: Invalid value for DAYOFWEEK parameter in exported data for schedule schedule name in domain domain name.

Explanation: During preview processing of command import command, an invalid value is encountered for the DAYOFWEEK parameter for schedule schedule name in policy domain domain name.

System Action: Processing of the command continues. If a later command causes the data to be imported, the default or existing DAYOFWEEK value is used.

User Response: If the data is imported with a later command, verify that the correct DAYOFWEEK value is used for this schedule.

ANR0758EImport command: Invalid value for ACTION parameter in exported data - schedule schedule name in domain domain name defined with default ACTION value.

Explanation: During processing of command import command, an invalid value is encountered for the ACTION parameter for schedule schedule name in policy domain domain name.

System Action: Processing of the command continues, by using the default ACTION value for this schedule.

User Response: Verify that the correct ACTION value has been used for this schedule. Update this value, if necessary.

ANR0759EImport command: Invalid value for DURUNITS or PERUNITS parameter in exported data - schedule schedule name in domain domain name defined with default values for DURATION, DURUNITS, PERIOD, and PERUNITS.

Explanation: During processing of command import command, an invalid value is encountered for the DURUNITS or PERUNITS parameter for schedule schedule name in policy domain domain name.

System Action: Processing of the command continues, by using the default values for DURATION, DURUNITS, PERIOD, and PERUNITS.

User Response: Verify that the correct values have been used for DURATION, DURUNITS, PERIOD, and PERUNITS. Update these values, if necessary.

ANR0760EImport command: Invalid value for DAYOFWEEK parameter in exported data - schedule schedule name in domain domain name defined with default DAYOFWEEK value.

Explanation: During processing of command import command, an invalid value is encountered for the DAYOFWEEK parameter for schedule schedule name in policy domain domain name.

System Action: Processing of the command continues, by using the default DAYOFWEEK value for this schedule.

User Response: Verify that the correct DAYOFWEEK value has been used for this schedule. Update this value, if necessary.

ANR0761EImport command: Invalid value for ACTION parameter in exported data - existing ACTION value for schedule schedule name in domain domain name was not updated.

Explanation: During processing of command import command, an invalid value is encountered for the ACTION parameter for schedule schedule name in policy domain domain name.

System Action: Processing of the command continues, by using the existing ACTION value for this schedule.

User Response: Verify that the correct ACTION value has been used for this schedule. Update this value, if necessary.

ANR0762EImport command: Invalid value for DURUNITS or PERUNITS parameter in exported data - existing values for DURATION, DURUNITS PERIOD, and PERUNITS for schedule schedule name in domain domain name were not updated.

Explanation: During processing of command import command, an invalid value is encountered for the DURUNITS or PERUNITS parameter for schedule schedule name in policy domain domain name.

System Action: Processing of the command continues, by using the existing values for DURATION, DURUNITS, PERIOD, and PERUNITS.

User Response: Verify that the correct values have been used for DURATION, DURUNITS, PERIOD, and PERUNITS. Update these values, if necessary.

ANR0763EImport command: Invalid value for DAYOFWEEK parameter in exported data - existing DAYOFWEEK value for schedule schedule name in domain domain name was not updated.

Explanation: During processing of command import command, an invalid value is encountered for the DAYOFWEEK parameter for schedule schedule name in policy domain domain name.

System Action: Processing of the command continues, by using the existing DAYOFWEEK value for this schedule.

User Response: Verify that the correct DAYOFWEEK value has been used for this schedule. Update this value, if necessary.

ANR0764EImport command: Invalid lock status detected while importing node node name - this node will not be locked.

Explanation: During processing of command import command, an invalid value is encountered for the lock status for node node name.

System Action: Processing of the command continues, but the node is not locked.

User Response: An administrator with the proper authorization must issue the LOCK NODE command, if necessary.

ANR0765EImport command: Invalid lock status detected while importing administrator administrator name - this administrator will not be locked.

Explanation: During processing of command import command, an invalid value is encountered for the lock status for administrator administrator name.

System Action: Processing of the command continues, but the administrator is not locked.

User Response: An administrator with the proper authorization must issue the LOCK ADMIN command, if necessary.

ANR0766EExport command: Invalid value for TYPE parameter detected while exporting copy group copy group name in domain domain name, set policy set name, management class management class name - system will attempt to assign value during import.

Explanation: During processing of command export command, an invalid value is encountered for the TYPE parameter for copy group copy group name, in domain domain name, policy set policy set name, management class management class name.

System Action: Export processing continues, but the exported data contains an unknown TYPE value for this copy group. If this data is imported, the system attempts to assign a TYPE value based upon values for other copy group parameters.

User Response: Delete and define this copy group to eliminate the invalid data, and then restart the export command. Alternatively, use the export data with the unknown value, and the system will attempt to assign a TYPE during import processing.

ANR0767EExport command: Invalid value for MODE parameter detected while exporting copy group copy group name in domain domain name, set policy set name, management class management class name - default or existing value is used during import.

Explanation: During processing of command export command, an invalid value is encountered for the MODE parameter for copy group copy group name in domain domain name, policy set policy set name, management class management class name.

System Action: Export processing continues, but the exported data contains an unknown MODE value for this copy group. If this data is imported, the default or existing MODE value is used.

User Response: Update the MODE value for this copy group and restart the export command. Alternatively, use the export data with the unknown value, and check and update the MODE value after import processing has been performed.

ANR0768EExport command: Invalid value for SERIALIZATION parameter detected while exporting copy group copy group name in domain domain name, set policy set name, management class management class name - default or existing value is used during import.

Explanation: During processing of command export command, an invalid value is encountered for the SERIALIZATION parameter for copy group copy group name, in domain domain name, policy set policy set name, management class management class name.

System Action: Export processing continues, but the exported data contains an unknown SERIALIZATION value for this copy group. If this data is imported, the default or existing SERIALIZATION value is used.

User Response: Update the SERIALIZATION value for this copy group and restart the export command. Alternatively, use the export data with the unknown value, and check and update the SERIALIZATION value after import processing has been performed.

ANR0769EExport command: Invalid value for ACTION parameter detected while exporting schedule schedule name in domain domain name - default or existing value is used during import.

Explanation: During processing of command export command, an invalid value is encountered for the ACTION parameter for schedule schedule name in domain domain name.

System Action: Export processing continues, but the exported data will contain an unknown ACTION value for this schedule. If this data is imported, the default or existing ACTION value is used.

User Response: Update the ACTION value for this schedule and restart the export command. Alternatively, use the export data with the unknown value, and check and update the ACTION value after import processing has been performed.

ANR0770EExport command: Invalid value for DURUNITS parameter detected while exporting schedule schedule name in domain domain name - default or existing value is used during import.

Explanation: During processing of command export command, an invalid value is encountered for the DURUNITS parameter for schedule schedule name in domain domain name.

System Action: Export processing continues, but the exported data contains an unknown DURUNITS value for this schedule. If this data is imported, the default or existing DURUNITS value is used.

User Response: Update the DURUNITS value for this schedule and restart the export command. Alternatively, use the export data with the unknown value, and check and update the DURUNITS value after import processing has been performed.

ANR0771EExport command: Invalid value for PERUNITS parameter detected while exporting schedule schedule name in domain domain name - default or existing value is used during import.

Explanation: During processing of command export command, an invalid value is encountered for the PERUNITS parameter for schedule schedule name in domain domain name.

System Action: Export processing continues, but the exported data will contain an unknown PERUNITS value for this schedule. If this data is imported, the default or existing PERUNITS value is used.

User Response: Update the PERUNITS value for this schedule and restart the export command. Alternatively, use the export data with the unknown value, and check and update the PERUNITS value after import processing has been performed.

ANR0772EExport command: Invalid value for DAYOFWEEK parameter detected while exporting schedule schedule name in domain domain name - default or existing value is used during import.

Explanation: During processing of command export command, an invalid value is encountered for the DAYOFWEEK parameter for schedule schedule name in domain domain name.

System Action: Export processing continues, but the exported data contains an unknown DAYOFWEEK value for this schedule. If this data is imported, the default or existing DAYOFWEEK value is used.

User Response: Update the DAYOFWEEK value for this schedule and restart the export command. Alternatively, use the export data with the unknown value, and check and update the DAYOFWEEK value after import processing has been performed.

ANR0773EExport command: Invalid lock status detected while exporting administrator administrator name - this administrator will not be locked during import.

Explanation: During processing of command export command, an invalid value is encountered for the lock status for administrator administrator name.

System Action: Export processing continues, but the exported data contains an unknown lock status for this administrator. If this data is imported, the administrator will not be locked.

User Response: An administrator with the proper authorization must issue the LOCK NODE or UNLOCK NODE command to achieve the desired lock status, and then restart the export command. Alternatively, use the export data with the unknown status, and issue a LOCK ADMIN or UNLOCK ADMIN command after import processing has been performed.

ANR0774EExport command: Invalid value for COMPRESSION parameter detected while exporting node node name - default or existing value is used during import.

Explanation: During processing of command export command, an invalid value is encountered for the COMPRESSION parameter for node node name.

System Action: Export processing continues, but the exported data contains an unknown COMPRESSION value for this node. If this data is imported, the default or existing COMPRESSION value is used.

User Response: Update the COMPRESSION parameter for this node and restart the export command. Alternatively, use the export data with the unknown value, and check and update the COMPRESSION value after import processing has been performed.

ANR0775EExport command: Invalid lock status detected while exporting node node name - this node will not be locked during import.

Explanation: During processing of command export command, an invalid value is encountered for the lock status for node node name.

System Action: Export processing continues, but the exported data contains an unknown lock status for this node. If this data is imported, the node will not be locked.

User Response: Lock or unlock the node to achieve the desired lock status, and then restart the export command. Alternatively, use the export data with the unknown status, and lock or unlock the node after import processing has been performed.

ANR0776EExport command: Invalid value for ARCHDELETE parameter detected while exporting node node name - default or existing value is used during import.

Explanation: During processing of command export command, an invalid value is encountered for the ARCHDELETE parameter for node node name.

System Action: Export processing continues, but the exported data contains an unknown ARCHDELETE value for this node. If this data is imported, the default or existing ARCHDELETE value is used.

User Response: Update the ARCHDELETE parameter for this node and restart the export command. Alternatively, use the export data with the unknown value, and check and update the ARCHDELETE value after import processing has been performed.

ANR0777EExport command: Invalid value for BACKDELETE parameter detected while exporting node node - default or existing value is used during import.

Explanation: During processing of command export command, an invalid value is encountered for the BACKDELETE parameter for node node name.

System Action: Export processing continues, but the exported data contains an unknown BACKDELETE value for this node. If this data is imported, the default or existing BACKDELETE value is used.

User Response: Update the BACKDELETE parameter for this node and restart the export command. Alternatively, use the export data with the unknown value, and check and update the BACKDELETE value after import processing has been performed.

ANR0778ECommand: Error encountered in accessing data storage - device class device class name is not defined.

Explanation: During command command processing, an error occurred because the specified device class is not defined.

System Action: The command command is ended and server operation continues.

User Response: Make sure the specified device class is defined.

ANR0779ECommand: Error encountered in accessing data storage - disk volume specified.

Explanation: During command command processing, an error occurred because a specified volume is a disk volume rather than a tape volume.

System Action: The command command is ended and server operation continues.

User Response: Make sure that all volumes specified for the command command are tape volumes.

ANR0780EExport/import command: Process aborted - a server communications session could not be established.

Explanation: The server export/import process encounters an internal error in establishing an intermemory communications session with other server components.

System Action: The export or import process ends and server operation continues.

User Response: Allocate additional storage to the server. For details, issue HELP MEMORY to display the information online or see "Appendix A. Allocating Additional Server Memory". If the error is not resolved, contact your service representative.

ANR0781EExport/import command: Process aborted - server sign on failed.

Explanation: The server export/import process encounters an internal error in establishing an intermemory communications session with other server components.

System Action: The export or import process ends and server operation continues.

User Response: Contact your service representative.

ANR0782EExport/import command: Process aborted - a server data storage session could not be established (rc return code).

Explanation: The server export/import process encounters an internal error in establishing a session with the data storage services.

System Action: The export or import process ends and server operation continues.

User Response: Examine the server messages issued prior to this message to determine the source of the error. Use the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative.

ANR0783EExport/import command: Process aborted - a server data storage Export/Import stream could not be established (rc return code).

Explanation: The server export/import process encounters an internal error in establishing a session with the data storage services.

System Action: The export or import process ends and server operation continues.

User Response: Examine the server messages issued prior to this message to determine the source of the error. Use the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative.

ANR0784EExport/import command: Process aborted - internal error detected with the Export/Import level: level number.

Explanation: The server export/import process encounters an internal error in evaluating the export/import level (SERVER, NODE, ADMIN, POLICY).

System Action: The export or import process ends and server operation continues.

User Response: Examine the server messages issued prior to this message to determine the source of the error. Use the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative.

ANR0785EImport command: Invalid record type xrecord type read from export data.

Explanation: The server export/import process encounters an internal error in reading data from the export media. An invalid record type of record type is encountered during the read operation.

System Action: The export or import process ends and server operation continues.

User Response: Examine the server messages issued prior to this message to determine the source of the error. Use the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative.

ANR0786EImport command: Invalid export version version number in exported data.

Explanation: The server import process encounters an internal error in reading data from the export media. An invalid export version number (version number) is encountered during the read operation.

System Action: The export or import process ends and server operation continues.

User Response: Examine the server messages issued prior to this message to determine the source of the error. Use the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative.

ANR0787EImport command: Import of file space filespace name in node node name aborted by server (abort reason).

Explanation: The server import process encounters an internal error in importing file space filespace name for client node node name. The reason code abort reason is encountered.

System Action: The export or import process ends and server operation continues.

User Response: Examine the server messages issued prior to this message to determine the source of the error. Use the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative.

ANR0788EImport command: Error error code during import of data storage data.

Explanation: The server import process encounters an internal data storage error. The error code error code is encountered.

System Action: The export or import process ends and server operation continues.

User Response: Examine the server messages issued prior to this message to determine the source of the error. Use the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative.

ANR0789EImport command: Failure in normalizing transaction identifier for sending to the server.

Explanation: The server import process encounters an internal database transaction error in importing information into the server database.

System Action: The export or import process ends and server operation continues.

User Response: Examine the server messages issued prior to this message to determine the source of the error. Use the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative.

ANR0790EImport command: Error in absorbing data records.

Explanation: The server import process encounters an internal error in importing information into the server database.

System Action: The export or import process ends and server operation continues.

User Response: Examine the server messages issued prior to this message to determine the source of the error. Use the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative.

ANR0791EExport/import command: Protocol error - verb "verb type" with length verb length received, expected "expected type".

Explanation: The server export or import process encounters an internal protocol error in exporting information from or importing information into the server database. The verb verb type is encountered with a length of verb length when a verb type of expected type was expected.

System Action: The export or import process ends and server operation continues.

User Response: Examine the server messages issued prior to this message to determine the source of the error. Use the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative.

ANR0792EImport command: Invalid copy type encountered in an imported file space authorization rule for node node name, file space filespace name - a type of BACKUP will be assumed.

Explanation: During import processing for command import command, an invalid copy type is encountered for an authorization rule that grants access for file space filespace name on node node name. Authorization rules typically specify copy types of backup or archive, depending on whether backup file access or archive file access is granted by the file space owner to other users. Because the imported information for the rule is ambiguous, the server assumes that the rule is for backup data.

System Action: The import process continues.

User Response: The user for node node name should query the access rules for the specified node name after the import process has completed, and correct or delete any access rules that are in error or not needed.

ANR0793EExport/import command: Preview processing terminated abnormally - error accessing data storage.

Explanation: The server encountered an internal error in accessing data storage while executing an import or export preview operation.

System Action: The export or import operation is ended and server operation continues.

User Response: Use the QUERY ACTLOG command to examine messages prior to this error to determine the cause of the data storage failure. If you find and resolve the error, retry the export or import operation. If you cannot find the error, contact your service representative for assistance in resolving the problem.

ANR0794EExport/import command: Processing terminated abnormally - error accessing data storage.

Explanation: The server encountered an internal error in accessing data storage while executing an import or export operation.

System Action: The export or import operation is ended and server operation continues.

User Response: Use the QUERY ACTLOG command to examine messages prior to this error to determine the cause of the data storage failure. If you find and resolve the error, retry the export or import operation. If you cannot find the error, contact your service representative for assistance in resolving the problem.

ANR0795ECommand: Error encountered in accessing data storage - invalid volume name specified.

Explanation: The server encounters an error in accessing data storage while processing command command. The error occurred because an attempt has been made to access a volume with an invalid name.

System Action: The command command operation is ended and server operation continues.

User Response: Issue the command with a valid volume name.

ANR0796ECommand: Error encountered in accessing data storage - insufficient number of mount points available for removable media.

Explanation: During command command processing, the server cannot allocate sufficient mount points.

System Action: The command command operation is ended and server operation continues.

User Response: If necessary, make more mount points available.

ANR0797ECommand: Error encountered in accessing data storage - required volume was not mounted.

Explanation: During command command processing, a required volume cannot be mounted. The mount request may have been canceled.

System Action: The command command operation is ended and server operation continues.

User Response: Issue the command again and make sure the necessary volumes are accessible.

ANR0798EImport command: Error encountered in accessing data storage - volume cannot be used.

Explanation: During import processing, a volume has been mounted but cannot be used.

System Action: The import operation is ended and server operation continues.

User Response: Query the activity log for messages preceding this one that give additional information. Make sure a usable volume is specified and mounted.

ANR0799ECommand: Error encountered in accessing data storage - volume already in use.

Explanation: During command command processing, a volume cannot be used because it is already defined in a storage pool, or has been previously used by an export, database dump, or database backup operation (as recorded in the volume history) or is in use by another process.

System Action: The command command operation is ended and server operation continues.

User Response: Specify a volume that is not in use or defined in a storage pool, and that has not been previously used for an export, database dump, or database backup operation as recorded in the server volume history information. Use the QUERY VOLUME command to display the names of volumes that are defined to server storage pools. Use the QUERY VOLHISTORY command to display the names of volumes that have been used for export, database dump, or database backup operations.

ANR0800ICommand: command for node node name started as process process ID.

Explanation: A file space deletion process has started to delete one or more file spaces for the specified node. The process is assigned the ID specified in the message.

System Action: The server starts a background process to perform the operation in response to the DELETE FILESPACE command entered by an administrator.

User Response: To obtain status on the file space deletion process, issue the QUERY PROCESS command. The process may be canceled with the CANCEL PROCESS command.

ANR0801IDelete Filespace filespace name for node node name started as process process ID.

Explanation: The specified client node has started a file space deletion process (on the server) to delete one or more file spaces. The process has been assigned the ID specified in the message.

System Action: The server starts a background process to perform the operation in response to a request from the client node.

User Response: To obtain status on the file space deletion process, issue the QUERY PROCESS command. The process may be canceled by an authorized administrator using the CANCEL PROCESS command.

ANR0802IDelete Filespace filespace name (backup/archive data) for node node name started.

Explanation: A background server process has started (on the server) to delete the specified file space belonging to the node indicated. If a file space name is not included in the message, all file spaces belonging to the node are deleted.

System Action: The background process deletes backup and archive objects for the specified file space while server operation continues.

User Response: To obtain status on the file space deletion process, issue the QUERY PROCESS command. The process may be canceled by an authorized administrator using the CANCEL PROCESS command.

ANR0803IDelete Filespace filespace name (backup data) for node node name started.

Explanation: A background server process has started (on the server) to delete backup objects in the specified file space belonging to the node indicated. If a file space name is not included in the message, then the backup objects for all file spaces that belong to the node are deleted.

System Action: The background process deletes backup objects for the specified file space while server operation continues.

User Response: To obtain status on the file space deletion process, issue the QUERY PROCESS command. The process may be canceled by an authorized administrator using the CANCEL PROCESS command.

ANR0804IDelete Filespace filespace name (archive data) for node node name started.

Explanation: A background server process has started (on the server) to delete archive objects in the specified file space belonging to the node indicated. If a file space name is not included in the message, then the archive objects for all file spaces that belong to the node are deleted.

System Action: The background process deletes archive objects for the specified file space while server operation continues.

User Response: To obtain status on the file space deletion process, issue the QUERY PROCESS command. The process may be canceled by an authorized administrator using the CANCEL PROCESS command.

ANR0805IDelete Filespace filespace name canceled for node node name: number of objects objects deleted.

Explanation: A background server process that has been deleting file space data for the indicated node is canceled by the CANCEL PROCESS command. The number of objects deleted before the cancel ended the operation are reported in the message.

System Action: The server process is ended and server operation continues.

User Response: No action is required. An authorized administrator can issue the DELETE FILESPACE command to delete remaining objects in the file space.

ANR0806IDelete Filespace filespace name complete for node node name: number of objects objects deleted.

Explanation: A server process deleting file space data for the node specified has completed. The total number of objects deleted is reported in the message.

System Action: The server process is ended and server operation continues.

User Response: None.

ANR0811IInventory client file expiration started as process process ID.

Explanation: The server has started roll-off processing to remove expired client backup and archive file copies, based on the management class policy that is bound to the files. The copy group retention and version parameters for each file's copy group are used by the server to determine if copies are to be deleted from the server. The expiration process was started as process number process ID, and may be queried or canceled with the QUERY PROCESS or CANCEL PROCESS commands, respectively.

System Action: The expiration process is now cancellable. Server operation continues.

User Response: None.

ANR0812IInventory file expiration process process ID completed: examined number of objects objects, deleting number of backup objects backup objects, number of archive objects archive objects, number of DB backup volumes DB backup volumes, and number of recovery plan files recovery plan files. error count errors were encountered.

Explanation: Server roll-off processing has completed. The number of client objects examined and deleted, based on management class policy, are displayed in the message. A total error count is also displayed. The number of DB backup volumes deleted is based on the value specified on the SET DRMDBBACKUPEXPIREDAYS. The number of recovery plan files deleted is based on the value specified on the SET DRMRPFEXPIREDAYS. Server roll-off processing deletes the DB backup volumes and recovery plan files only if DRM is licensed on the server and the volumes or plan files are created on the server to server virtual volumes.

System Action: The roll-off process is ended and server operation continues.

User Response: If the error count is not equal to 0, examine messages that may have been issued in the activity log to determine the cause for the errors.

ANR0813IInventory file expiration process process ID canceled prior to completion: examined number of objects objects, deleting number of backup objects backup objects, number of archive objects archive objects, number of DB backup volumes DB backup volumes, and number of recovery plan files recovery plan files. error count errors were encountered.

Explanation: The inventory file expiration process was canceled by an administrator. The number of objects examined and deleted prior to the cancelation are reported. A total error count is also displayed.

System Action: The server ends the file expiration process.

User Response: None.

ANR0814IExpiration retry retry number of maximum retries in number of seconds seconds.

Explanation: Server roll-off processing has encountered an error in attempting to remove expired client file copies from the server database. The operation will be tried again in the number of seconds indicated.

System Action: The server waits for the number of seconds indicated and retries the file expiration operation.

User Response: Expiration retry processing occurs when the server database is full, the log is full, or sufficient server memory is not available to continue processing. Use the QUERY ACTLOG command to look for messages issued prior to this one that indicate the type of error encountered. If the server is out of database space, issue the DEFINE DBVOLUME and EXTEND DB commands to add volumes to the server database and extend the database size. If the server is out of log space, issue the DEFINE LOGVOLUME and EXTEND LOG commands to add volumes to the server log and extend the log size. If the server is low on memory, allocate additional storage to the server. For details, issue HELP MEMORY to display the information online or see "Appendix A. Allocating Additional Server Memory".

ANR0815IExpiration retry in progress.

Explanation: The server is retrying an operation during client file roll-off processing. Expiration retry processing occurs when the server database is full, the log is full, or sufficient server memory is not available to continue processing.

System Action: The roll-off operation is retried.

User Response: Use the QUERY ACTLOG command to look for messages issued prior to this one that indicate the type of error encountered. If the server is out of database space, issue the DEFINE DBVOLUME and EXTEND DB commands to add volumes to the server database and extend the database size. If the server is out of log space, issue the DEFINE LOGVOLUME and EXTEND LOG commands to add volumes to the server log and extend the log size. If the server is low on memory, allocate additional storage to the server. For details, issue HELP MEMORY to display the information online or see "Appendix A. Allocating Additional Server Memory".

ANR0816IExpiration retry was successful.

Explanation: In accordance with management class policy, server roll-off processing has been successful in retrying a client file expiration.

System Action: Server roll-off processing continues.

User Response: None.

ANR0818IWaiting to retry expiration because of insufficient resources.

Explanation: The server inventory expiration process is waiting to retry expiration processing that failed because of insufficient memory, database, or log resources on the server.

System Action: Server operation continues. The expiration processing is reattempted automatically.

User Response: Use the QUERY ACTLOG command to examine messages issued prior to this one, which indicated the resource that is not available to the expiration process. Correct the shortage.

ANR0819ICancel in progress

Explanation: This message is displayed in response to a QUERY PROCESS command, and indicates that an inventory expiration process has been canceled. The process will end shortly.

System Action: The expiration process terminates and server operation continues.

User Response: None.

ANR0820ISorting information for number objects has been deleted.

Explanation: A background server process has deleted sorting information for number files from the server database. This process is started during initialization to remove any sorting information which is left over from previous export operations.

System Action: The actual backup or archive objects were not deleted, but only information used to sort these objects during the previous export operation.

User Response: None.

ANR0821EFilespace identifier fsId is not valid.

Explanation: The identifier assigned for a filespace is out of range.

System Action: The filespace is not added.

User Response: Contact your service representative.

ANR0822Icommand: Filespace filespace name successfully renamed to new filespace name for node node name.

Explanation: The filespace specified was renamed to the new name specified for the node. This message is displayed in response to successful completion of the RENAME FILESPACE command.

System Action: The system renames the filespace for the node as indicated

User Response: None.

ANR0823Ecommand: Filespace filespace name cannot be renamed to new filespace name, a filespace with this name already exists for node node name.

Explanation: The filespace name specified as a target name for the command was found to already exist for the node specified. The command fails.

System Action: Server operation continues, the command fails.

User Response: Reissue the command with a different target filespace name

ANR0824IDelete Filespace filespace name (space-managed data) for node node name started.

Explanation: A background server process has started (on the server) to delete space-managed objects in the specified file space belonging to the node indicated. If a file space name is not included in the message, then the space-managed objects for all file spaces that belong to the node are deleted.

System Action: The background process deletes space-managed objects for the specified file space while server operation continues.

User Response: To obtain status on the file space deletion process, issue the QUERY PROCESS command. The process may be canceled by an authorized administrator using the CANCEL PROCESS command.

ANR0826IDELETE FILESPACE filespace name for node node name encountered a transaction failure.

Explanation: A background server process that has been deleting file space data for the indicated node encountered a transaction failure.

System Action: The server process is retried if the maximum number of retry attempts have not been exceeded.

User Response: Transaction failure usually indicates that a database deadlock was detected during filespace deletion. These deadlock conditions are sometimes encountered when multiple filespace deletion processes are running at the same time. No action is required unless the DELETE FILESPACE terminates without completing the deletion process (see message ANR0828).

ANR0827IDELETE FILESPACE filespace name will be retried for node node name.

Explanation: A filespace deletion process for the node indicated is being retried because an error was encountered.

System Action: The server process is retried.

User Response: None.

ANR0828WDELETE FILESPACE filespace name for node node name terminated before completion due to transaction failure: number of objects objects deleted.

Explanation: A background server process that has been deleting file space data for the indicated node is terminated prematurely because of transaction failure. The number of objects deleted before the operation ended are reported in the message.

System Action: The server process is ended and server operation continues.

User Response: Termination of this process because of transaction failure usually indicates that a database deadlock was detected during filespace deletion. These deadlock conditions are sometimes encountered when multiple filespace deletion processes are running at the same time. The command should be started again when fewer filespace deletion processes are active. An authorized administrator can issue the DELETE FILESPACE command to delete remaining files in the file space(s).

ANR0829ECommand: Invalid combination of TYPE and DATA parameters.

Explanation: The specified command has been issued with an invalid combination of the TYPE and DATA parameters. DATA=IMAGES can only be specified if TYPE=ANY or TYPE=BACKUP.

System Action: Server operation continues, but the command is not processed.

User Response: Issue the command and specify a valid combination of parameters.

ANR0830WManagement class class name in domain domain name used by node node name in file space filespace name is no longer active, or no longer has a BACKUP copy group: DEFAULT management class attributes will be used for expiration.

Explanation: During policy roll-off processing, the server has found a client file copy whose management class or backup copy group no longer exists.

System Action: The server obtains the DEFAULT management class for the specified domain and uses its backup copy group version and retention parameters to determine if file copies need to be expired.

User Response: No action is required. A policy administrator with authority over the specified domain may use the DEFINE COPYGROUP, DEFINE MGMTCLASS, and ACTIVATE POLICY commands to define and activate a policy set that contains definitions for the missing management class or copy group.

ANR0831WThe DEFAULT management class class name in domain domain name does not have a BACKUP copy group: GRACE PERIOD will be used for expiration.

Explanation: During policy roll-off processing, the server found a client file copy whose management class or backup copy group no longer exists. The DEFAULT management class for the indicated policy domain does not contain a backup copy group; therefore, the server uses the GRACE PERIOD retention value defined for the specified policy domain to determine if client file copies need to be expired and removed from the server database.

System Action: The server obtains the GRACE PERIOD retention values for the specified domain and then determines if backup file copies need to be expired.

User Response: No action is required. A policy administrator with authority over the specified domain may use the DEFINE COPYGROUP, DEFINE MGMTCLASS, and ACTIVATE POLICY commands to define and activate a policy set that contains definitions for the missing management class or backup copy group.

ANR0832WManagement class class name in domain domain name used by node node name in filespace filespace name is no longer active, or no longer has an ARCHIVE copy group: DEFAULT management class attributes will be used for expiration.

Explanation: During policy roll-off processing, the server found a client file copy whose management class or archive copy group no longer exists.

System Action: The server obtains the DEFAULT management class for the specified domain and uses its archive copy group retention parameter to determine if file copies need to be expired.

User Response: No action is required. A policy administrator with authority over the specified domain may use the DEFINE COPYGROUP, DEFINE MGMTCLASS, and ACTIVATE POLICY commands to define and activate a policy set that contains definitions for the missing management class or copy group.

ANR0833WThe DEFAULT management class class name in domain domain name does not have an ARCHIVE copy group: GRACE PERIOD will be used for expiration.

Explanation: During policy roll-off processing, the server found a client file copy whose management class or archive copy group no longer exists. The DEFAULT management class for the indicated policy domain does not contain an archive copy group; therefore, the server uses the GRACE PERIOD retention value defined for the specified policy domain to determine if client file copies need to be expired and removed from the server database.

System Action: The server obtains the GRACE PERIOD retention values for the specified domain and then determines if archive file copies need to be expired.

User Response: No action is required. A policy administrator with authority over the specified domain may use the DEFINE COPYGROUP, DEFINE MGMTCLASS, and ACTIVATE POLICYSET commands to define and activate a policy set that contains definitions for the missing management class or backup copy group.

ANR0834WInventory client file expiration cannot start because of insufficient memory - will retry in number of seconds seconds.

Explanation: The server inventory expiration process is pausing to retry an operation that failed because sufficient memory is not available on the server.

System Action: Server operation continues; the expiration process will be retried after the stated delay.

User Response: Allocate additional storage to the server. For details, issue HELP MEMORY to display the information online or see "Appendix A. Allocating Additional Server Memory".

ANR0835WManagement class class name in domain domain name is no longer active, or no longer has a BACKUP copy group, or no longer has an ARCHIVE copy group. DEFAULT management class used to delete number of backup files backup files and number of archive files archive files. Retention grace period used to delete number of backup files backup files and number of archive files archive files.

Explanation: During policy roll-off processing, the server found a management class or backup copy group or archive copy group that no longer exists. When a management class or backup copy group no longer exists, the number of backup client file copies that have been deleted using the default management class or the retention grace period is displayed in the message. When a management class or archive copy group no longer exists, the number of archive client files that have been deleted using the default management class or the retention grace period is displayed in the message.

System Action: The server obtains the DEFAULT management class for the specified domain and uses its backup copy group or archive copy group version and retention parameters to determine if file copies need to be expired. If, however, the needed backup copy group or archive copy group does not exist in the DEFAULT management class, the server will use the retention grace period for the domain.

User Response: No action is required. This message is only issued when expiration processing has been started with the QUIET option to suppress detailed messages. Expiration processing can be started without the QUIET option to see the detailed messages which will indicate specific node and filespaces and will further distinguish between backup and archive copy groups. A policy administrator with authority over the specified domain may use the DEFINE COPYGROUP, DEFINE MGMTCLASS, and ACTIVATE POLICY commands to define and activate a policy set that contains definitions for the missing management class or copy group.

ANR0836WNo query restore processing session session id for node node name and filespace name failed to retrieve file high-level file namelow-level file name - file being skipped.

Explanation: The no query restore processing for the session listed relating to the specified node name and filespace failed to retrieve the specified file. An error occurred while retrieving this file so it will be skipped.

System Action: The no query restore operation continues.

User Response: Determine the cause of the file retieve failure and correct it. After this situation is correct, the client can do a restore of the specific file that was skipped.

ANR0837IThe expire inventory running duration of number of minutes minutes has expired. The expire inventory process ends.

Explanation: An ADSM Administrator or schedule issued the command EXPIRE INVENTORY ... DURATION=xxx, where xxx is the number of minutes for the expire inventory process to run. That xxx number of minutes has been reached, so the expire inventory process ends.

System Action: The expire inventory process ends.

User Response: None.

ANR0838ICommand: Archive directory cleanup job Job ID started as background process process ID.

Explanation: An archive directory cleanup job started under the indicated background server process with the indicated process identifier.

System Action: Server processing continues.

User Response: None.

ANR0839ECommand: There are no restartable jobs. Job Job ID not found.

Explanation: A QUERY ARCHDIRCLEAN command was issued but no archive directory cleanup jobs were found. The jobid is 0 if a specific job id was specified on the Query command.

System Action: Server processing continues.

User Response: None.

ANR0840ICommand: Archive directory cleanup job Job ID started as foreground process process ID.

Explanation: An archive directory cleanup job started under the indicated foreground server process with the indicator process identifier.

System Action: Server processing continues.

User Response: None.

ANR0841I( Job ID ): Skipping node node ID; node being cleaned by job Other Job ID.

Explanation: The indicated archive directory cleanup job is skipping the indicated node because a different archive directory cleanup job ( as specified ) is working on the same node.

System Action: Server processing continues.

User Response: None.

ANR0842ICommand: ( Job ID ): Archive cleanup was cancelled - number of nodes nodes processed, last node was last node.

Explanation: The indicated archive directory cleanup job was cancelled. Prior to cancellation, the indicated number of nodes were processed. The last processed node is also displayed.

System Action: The archive cleanup operation ends. Server processing continues.

User Response: The archive directory cleanup may be restarted by specifying the JOBID parameter on the CLEAN ARCHDIRectories command.

ANR0843ICommand: Archive directory cleanup job Job ID completed successfully number of nodes nodes were processed.

Explanation: An archive directory cleanup job completed successfully. The job identifier and the number of nodes that were processed are displayed.

System Action: The archive directory cleanup operation ends.

User Response: None.

ANR0844EJob ID: Skipping node node name - node not found.

Explanation: The indicated nodename was not processed by the indicated archive directory cleanup job. The node was not found by the time the job got around to working on it.

System Action: The node is skipped. Other nodes are processed.

User Response: None.

ANR0845IJob ID: Skipping node node name - is not a backup/archive node.

Explanation: The indicated nodename was not processed by the indicated archive directory cleanup job. The node was not a backup/archive client node.

System Action: The node is skipped. Other nodes are processed.

User Response: None.

ANR0846IJob ID: Deleted ( objIdHi.objIdHi ) for node ( Node name ) fsId( File Space Id hl( Dir Name Part 1 ) ll( Dir Name Part 2 ) descr( Dir Description ).

Explanation: The indicated archive directory cleanup job deleted a duplicate directory entry. Information from the data base about the duplicate entry is displayed, including the two part object identifier, node name, file space identifier, two part directory name and the description from the archive information.

System Action: The entry is deleted. Processing continues.

User Response: None.

ANR0847IJob ID: Found directory ( objIdHi.objIdHi ) for node ( Node name ) filespace( File Space hl( Dir Name Part 1 ) ll( Dir Name Part 2 ) descr( Dir Description ).

Explanation: The indicated archive directory cleanup job found a duplicate directory entry. Information from the data base about the duplicate entry is displayed, including the two part object identifier, node name, file space name, two part directory name and the description from the archive information. The duplicate directory will be deleted if the FIX=YES parameter of the CLEAN ARCHDIR command is specified. Since FIX=NO was specified or defaulted, the duplicate directory is not removed.

System Action: The entry is not deleted. Processing continues.

User Response: None.

ANR0848WExpiration failed to delete file type file file name for node node name and filespace filespace name - file will be skipped.

Explanation: The expiration process was unable to delete the indicated file. The file will be skipped by expiration.

System Action: The expiration process continues.

User Response: Re-try expiration to determine if the cause of the deletion failure was an intermittent problem or if it is a permanent problem. If after a subsequent expiration attempt the file still is not deleted, please contact your service representative.

ANR0849ECommand: Not permitted for node Node Name - node of type SERVER.

Explanation: The indicated DELETE FILESPACE process is not started because the node specified is of NODETYPE=SERVER. A DELETE FILESPACE may only be processed for nodes of this type with the TYPE=SERVER parameter specified.

System Action: The DELETE FILESPACE command is ended and server processing continues.

User Response: If this filespace must be deleted, Reissue the command with the TYPE parameter set to TYPE=SERVER. Please use caution when using the TYPE=SERVER parameter as this can impact the availability of data for the server that owns these files.

ANR0850ECommand: Cannot Start process name Process.

Explanation: The indicated DELETE FILESPACE process cannot be started on the server.

System Action: The DELETE FILESPACE command is ended and server processing continues.

User Response: This usually indicates that sufficient server memory is not available on the server. Allocate additional storage to the server. For details, issue HELP MEMORY to display the information online or see "Appendix A. Allocating Additional Server Memory".

ANR0851ECannot start delete file space thread for node node name.

Explanation: The indicated DELETE FILESPACE process cannot be started on the server. Sufficient memory on the server may not be available.

System Action: The DELETE FILESPACE command is ended and server processing continues.

User Response: Allocate additional storage to the server. For details, issue HELP MEMORY to display the information online or see "Appendix A. Allocating Additional Server Memory".

ANR0852ECommand: No matching file spaces found for node node name.

Explanation: The server did not find any file spaces for the node indicated matching the names specified in the command.

System Action: The server ends the command.

User Response: Enter the command with file space names that refer to defined file spaces for the specified node. Note that file space names are case sensitive. Enter them by using exactly the same uppercase and lowercase characters that match the file space name defined on the server. Use the QUERY FILESPACE command to determine which file spaces are defined for a node on the server.

ANR0853ETransaction failed in file space deletion, DELETE FILESPACE process aborted.

Explanation: A database transaction fails while the server is deleting file space data.

System Action: The server ends the file space deletion process.

User Response: Examine the server messages issued prior to this message to determine the source of the error. Issue the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative.

ANR0854EInventory file space query failure, DELETE FILESPACE process aborted.

Explanation: The server encounters an error in querying the inventory database during a file space deletion process.

System Action: The server ends the file space deletion process.

User Response: Examine the server messages issued prior to this message to determine the source of the error. Issue the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative.

ANR0855EServer LOG space exhausted, DELETE FILESPACE process aborted.

Explanation: Insufficient server log space has been encountered during file space deletion processing.

System Action: The server ends the file space deletion process.

User Response: To increase the amount of log space available to the server, an authorized administrator can add log volumes by using the DEFINE LOGVOLUME command, and can extend the size of the log by using the EXTEND LOG command.

ANR0856EServer database space exhausted, DELETE FILESPACE process aborted.

Explanation: Insufficient server database space has been encountered during file space deletion processing.

System Action: The server ends the file space deletion process.

User Response: To increase the amount of database space available to the server, an authorized administrator can add log volumes using the DEFINE DBVOLUME command and can extend the size of the database using the EXTEND DB command.

ANR0857EData storage session failure, DELETE FILESPACE process aborted.

Explanation: The server encounters an error accessing data storage during file space deletion processing.

System Action: The server ends the file space deletion process.

User Response: Examine the server messages issued prior to this message to determine the source of the error. Issue the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative.

ANR0858EInventory object search failure, DELETE FILESPACE process aborted.

Explanation: The server encounters an error accessing the inventory database during file space deletion processing.

System Action: The server ends the file space deletion process.

User Response: Examine the server messages issued prior to this message to determine the source of the error. Issue the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative.

ANR0859EData storage object erasure failure, DELETE FILESPACE process aborted.

Explanation: The server encounters an error in removing file copies from data storage during file space deletion processing.

System Action: The server ends the file space deletion process.

User Response: Examine the server messages issued prior to this message to determine the source of the error. Issue the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative.

ANR0860EExpiration process process ID terminated due to internal error: examined number of objects objects, deleting number of backup objects backup objects, number of archive objects archive objects, number of DB backup volumes DB backup volumes, and number of recovery plan files recovery plan files. error count errors were encountered.

Explanation: The server encounters an internal error during file expiration processing. The number of files examined and deleted prior to the error are reported. A total error count is also displayed.

System Action: The server ends the expiration process.

User Response: Examine the server messages issued prior to this message to determine the source of the error. Issue the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative.

ANR0861ETransaction failed in expiration, inventory expiration aborted.

Explanation: The server encounters a database transaction failure during policy roll-off processing.

System Action: The server ends roll-off processing.

User Response: Examine the server messages issued prior to this message to determine the source of the error. Issue the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative.

ANR0862EExpiration processing suspended - insufficient memory.

Explanation: The server ends policy roll-off processing because sufficient server memory is not available.

System Action: The server ends policy roll-off processing and server operation continues.

User Response: Allocate additional storage to the server. For details, issue HELP MEMORY to display the information online or see "Appendix A. Allocating Additional Server Memory".

ANR0863EExpiration processing suspended - insufficient DB space.

Explanation: The server ends policy roll-off processing because sufficient server database space is not available.

System Action: The server ends policy roll-off processing and server operation continues.

User Response: To increase the amount of database space available to the server, an authorized administrator can add database volumes by using the DEFINE DBVOLUME command and can extend the size of the database using the EXTEND DB command.

ANR0864EExpiration processing suspended - insufficient LOG space.

Explanation: The server ends policy roll-off processing because sufficient server log space is not available.

System Action: The server ends policy roll-off processing and server operation continues.

User Response: To increase the amount of log space available to the server, an authorized administrator can add log volumes by using the DEFINE LOGVOLUME command and can extend the size of the log by using the EXTEND LOG command.

ANR0865EExpiration processing failed - internal server error.

Explanation: Server retry processing during policy roll-off fails.

System Action: The server ends policy roll-off processing.

User Response: Examine the server messages issued prior to this message to determine the source of the error. Issue the QUERY ACTLOG command to view the activity log and search for messages. If the server is out of database space, issue the DEFINE DBVOLUME and EXTEND DB commands to add volumes to the server database and extend the database size. If the server is out of log space, issue the DEFINE LOGVOLUME and EXTEND LOG commands to add volumes to the server log and extend the log size. If the server is low on memory, allocate additional storage to the server. For details, issue HELP MEMORY to display the information online or see "Appendix A. Allocating Additional Server Memory". If the error cannot be isolated and resolved, contact your service representative.

ANR0866EExpiration processing retries failed - no success after maximum retries retries.

Explanation: Server policy roll-off processing ends because retry processing has not been successful in expiring client file copies from the server database.

System Action: The server ends policy roll-off processing and server operation continues.

User Response: Examine the server messages issued prior to this message to determine the source of the error. Issue the QUERY ACTLOG command to view the activity log and search for messages. If the server is out of database space, issue the DEFINE DBVOLUME and EXTEND DB commands to add volumes to the server database and extend the database size. If the server is out of log space, issue the DEFINE LOGVOLUME and EXTEND LOG commands to add volumes to the server log and extend the log size. If the server is low on memory, allocate additional storage to the server. For details, issue HELP MEMORY to display the information online or see "Appendix A. Allocating Additional Server Memory". If the error cannot be isolated and resolved, contact your service representative.

ANR0867EUnable to open policy domain for node node name during expiration processing.

Explanation: Policy roll-off processing on the server encounters an error while obtaining policy information related to the specified node.

System Action: The server ends roll-off processing and server operation continues.

User Response: Examine the server messages issued prior to this message to determine the source of the error. Issue the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative.

ANR0868ECannot find management class name for ID management class ID.

Explanation: Policy roll-off processing on the server encounters an error while obtaining policy information.

System Action: The server ends roll-off processing and server operation continues.

User Response: Examine the server messages issued prior to this message to determine the source of the error. Issue the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative.

ANR0869ECannot find policy domain for node node ID.

Explanation: Policy roll-off processing on the server encounters an error while obtaining policy information related to the specified node.

System Action: The server ends roll-off processing and server operation continues.

User Response: Examine the server messages issued prior to this message to determine the source of the error. Issue the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative.

ANR0870ECannot find node name for node node ID.

Explanation: Policy roll-off processing on the server encounters a database error in obtaining information for a client node.

System Action: The server ends roll-off processing and server operation continues.

User Response: Examine the server messages issued prior to this message to determine the source of the error. Issue the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative.

ANR0871ECannot find file space name for node node ID, file space file space ID.

Explanation: Policy roll-off processing on the server encounters a database error in obtaining information for a client node.

System Action: The server ends roll-off processing and server operation continues.

User Response: Examine the server messages issued prior to this message to determine the source of the error. Issue the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative.

ANR0872EGrace Period retention for domain domain name could not be obtained.

Explanation: Policy roll-off processing on the server encounters a database error in obtaining GRACE PERIOD values for the specified policy domain.

System Action: The server ends roll-off processing and server operation continues.

User Response: Examine the server messages issued prior to this message to determine the source of the error. Issue the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative.

ANR0873EInvalid copy type encountered in expiring files: copytype ID

Explanation: Policy roll-off processing on the server encounters a database error in obtaining copy group information.

System Action: The server ends roll-off processing and server operation continues.

User Response: Examine the server messages issued prior to this message to determine the source of the error. Issue the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative.

ANR0874EBackup object object.ID not found during inventory processing.

Explanation: Inventory processing on the server encounters a database error in obtaining backup information in data storage.

System Action: The server ends roll-off processing, or client session(s) and server operation continues.

User Response: Examine the server messages issued prior to this message to determine the source of the error. Issue the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative.

ANR0875EArchive object object.ID not found during expiration processing.

Explanation: Policy roll-off processing on the server encounters a database error in obtaining archive information in data storage.

System Action: The server ends roll-off processing and server operation continues.

User Response: Examine the server messages issued prior to this message to determine the source of the error. Issue the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative.

ANR0876EData storage erasure failed during expiration processing.

Explanation: Policy roll-off processing on the server encounters a database error while deleting information from data storage.

System Action: The server ends roll-off processing and server operation continues.

User Response: Examine the server messages issued prior to this message to determine the source of the error. Issue the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative.

ANR0877ECopy type not backup for object object.ID.

Explanation: Policy roll-off processing on the server encounters a database error in accessing inventory information.

System Action: The server ends roll-off processing and server operation continues.

User Response: Examine the server messages issued prior to this message to determine the source of the error. Issue the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative.

ANR0878EEntry for backup object object.ID not found.

Explanation: Policy roll-off processing on the server encounters a database error in accessing inventory information.

System Action: The server ends roll-off processing and server operation continues.

User Response: Examine the server messages issued prior to this message to determine the source of the error. Issue the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative.

ANR0879EError opening inventory file space query.

Explanation: Policy roll-off processing on the server encounters a database error in accessing inventory information.

System Action: The server ends roll-off processing and server operation continues.

User Response: Examine the server messages issued prior to this message to determine the source of the error. Issue the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative.

ANR0880EFilespace command: No matching file spaces.

Explanation: The server did not find any file space names matching the specifications entered in the filespace command.

System Action: Server operation continues.

User Response: Use the QUERY FILESPACE command to determine which file spaces are defined on the server. Note, that file space names are case sensitive. Reissue the file space command and specify the proper file space name (in proper case).

ANR0881EPolicy Error : the GRACE PERIOD archive retention value could not be obtained for domain domain ID during client inventory processing.

Explanation: The server encounters an internal error in accessing policy information.

System Action: The operation is ended and server operation continues.

User Response: Contact your service representative.

ANR0882EPolicy Error: Unable to open policy domain for node node name during client inventory query processing.

Explanation: The server encounters an internal error in accessing policy information.

System Action: The client operation is ended and server operation continues.

User Response: Contact your service representative.

ANR0883ECannot obtain node name for node node ID.

Explanation: The server encounters an internal error in accessing client node information.

System Action: The operation is ended and server operation continues.

User Response: Contact your service representative.

ANR0884EError code during deletion of sorting information for number objects.

Explanation: A background server process encountered an internal error after deleting sorting information for number files from the server database. This process is started during initialization to remove any sorting information which is left over from previous export operations.

System Action: The backup or archive objects were not deleted. Only the information used to sort these objects during the previous export operation was deleted. The background process was terminated before all sorting information had been deleted. The system will not perform further export processing of file data until this problem has been resolved.

User Response: Examine the server messages issued prior to this message to determine the source of the error. Issue the QUERY ACTLOG command to view the activity log and search for messages. Then restart the server. If the error cannot be isolated and resolved, contact your service representative.

ANR0885IImport command: Processing management class management class name for domain domain name and policy set policy set name as management class new management class name.

Explanation: The background import process to service the command import command is currently processing the policy information for management class management class name in domain domain name and policy set policy set name. The management class is imported under the name new management class name. During import processing, management classes defined as either DEFAULT or GRACE_PERIOD must be renamed so that the management class does not conflict with existing server policy conventions. Import processing is then able to import file data by using the renamed management class.

System Action: Import processing for the command continues.

User Response: None. However, an administrator may want to examine the policy definitions for new management class name so they are aware of the management classes that may be used if the policy set containing this management class is activated.

ANR0886EManagement class class name in domain domain name used by node node name in file space filespace name has no BACKUP copy group with id copy group id; Expiration will not be performed for files from this node and filespace that are bound to this management class and copy group id.

Explanation: During policy roll-off processing, the server finds a client file copy with a management class or a backup copy group that no longer exists.

System Action: The server skips the files in error.

User Response: For programming support, contact your service representative.

ANR0887EManagement class class name in domain domain name used by node node name in file space filespace name has no ARCHIVE copy group with id copy group id; Expiration will not be performed for files from this node and filespace that are bound to this management class and copy group id.

Explanation: During policy roll-off processing, the server finds a client file copy with a management class or an archive copy group that no longer exists.

System Action: The server skips the files in error.

User Response: For programming support, contact your service representative.

ANR0888ESQL commands cannot be issued from the server console.

Explanation: An SQL command was issued from the server console. SQL commands cannot be issued from the server console because they may require a long time complete and the server console should be available to control other server functions.

System Action: The server ignores the command and continues processing.

User Response: Issue the SQL command from an administrative client.

ANR0889EThe server is not licensed for Central Administration functions. This includes the ability to issue SQL commands.

Explanation: An SQL command was issued but the server is not licensed to support Central Administrative functions, including SQL query support.

System Action: The server ignores the command and continues processing.

User Response: If you have purchased the Central Administration license, use the REGISTER LICENSE command to enable the license on the server. If you have not purchased the license and wish to do so, contact your service representative.

ANR0890IExport/import command: Processing optionset optionset name.

Explanation: The background export or import process to service the command export/import command is currently processing optionset definition information.

System Action: Export or import processing for the command continues.

User Response: None.

ANR0891IExport/import command: Copied number optionset definitions.

Explanation: The background export or import process to service the command export/import command copies number client optionset definitions from the server database to export media or from export media into the server database. Data is not moved if Preview=Yes is specified in the command export/import command.

System Action: Export or import processing for the command completes. Server operation continues.

User Response: None.

ANR0892IExport command: No matching optionsets found for exporting.

Explanation: The background export process does not find any client optionsets for export command.

System Action: The export process continues and no optionsets from the server.

User Response: None.

ANR0893IAre you sure that you want to accept the current system date as valid ?

Explanation: This message is displayed when the ACCEPT DATE command has been issued to confirm that you want to accept the date on the system as valid.

System Action: The command waits for you to confirm the action.

User Response: Specify Yes if you want to accept the system date as valid, or No if you do nt want to execute the command.

ANR0894ICurrent system has been accepted as valid.

Explanation: This messages is displayed when the ACCEPT DATE command has been issued and the date has been accepted as valid byu the server.

System Action: The current system date is accepted as valid by the server

User Response: None.

ANR0895ECommand: Cannot Start process name Process.

Explanation: The indicated process cannot be started on the server.

System Action: The specified command is ended and server processing continues.

User Response: This usually indicates that sufficient server memory is not available on the server. Allocate additional storage to the server. For details, issue HELP MEMORY to display the information online or see "Appendix A. Allocating Additional Server Memory".

ANR0900IProcessing options file filespec.

Explanation: At server initialization, the server is reading the server options file whose name is shown in the message.

System Action: The server reads and processes the options in this file.

User Response: None.

ANR0901WInvalid option statement found in file filespec.

Explanation: While processing the server options file named, the server has encountered an invalid statement. The invalid statement type is shown in the message. The lines following this message provide more information.

System Action: The server ignores the statement in error. Server initialization continues. The default value is used for any missing or ignored options.

User Response: Ignore the error, or use a text editor to correct the error and restart the server.

ANR0902WUnsupported keyword found in file filespec.

Explanation: While processing the server options file named, the server has encountered an invalid keyword on an option statement. The lines following this message provide more information.

System Action: The server ignores the option statement in error. Server initialization continues. The default value is used for any missing or ignored options.

User Response: Ignore the error, or use a text editor to correct the error and restart the server.

ANR0903WExcessive option statement found in file filespec.

Explanation: While processing the specified server options file, the server has encountered more of the named statement type than can be processed.

System Action: The server ignores the extra statement. Server initialization continues.

User Response: Ignore the error, or use a text editor to correct the error and restart the server.

ANR0904WDuplicate option statement found in file filespec.

Explanation: While processing the server options file named, the server has encountered a duplicate statement of the type shown.

System Action: The server ignores the duplicate statement. Server initialization continues.

User Response: Ignore the error, or use a text editor to correct the error and restart the server.

ANR0905WOptions file filespec not found.

Explanation: At server initialization, the server is unable to locate the server options file named.

System Action: The server uses the default values for all options. Server initialization continues.

User Response: If the default values are acceptable, ignore the error. Otherwise, move a valid server options file to the proper location, rename a valid options file to the proper name, or use a text editor to build the proper server options file, and then restart the server.

ANR0909EInsufficient memory to process options file.

Explanation: At server initialization, the server is unable to process the server options file due to insufficient memory.

System Action: Server initialization ends.

User Response: Restart the server with more memory available. Refer to the Administrator's Guide for your particular platform.

ANR0915EUnable to open language language name for message formatting.

Explanation: The server is unable to open the specified message repository.

System Action: Server initialization continues with the default message repository.

User Response: Ensure that a valid language is specified in the LANGUAGE option of the server options file. If a change is made to the options file, restart the server to activate changes.

ANR0916IProduct Name distributed by Company is now ready for use.

Explanation: The server has completed startup processing and is now ready for use.

System Action: None.

User Response: None.

ANR0917WSession session number for node node name (client platform) - in domain domain name failed because of policy length.

Explanation: The client cannot handle very long policies.

System Action: The client operation is ended and server operation continues.

User Response: Upgrade the client to the latest level, or activate a policy set with fewer management classes.

ANR0920ITracing is now active to standard output.

Explanation: In response to a TRACE START command, server trace records are being written to the standard output destination (usually the server console).

System Action: None.

User Response: None.

ANR0921ITracing is now active to file file spec.

Explanation: In response to a TRACE START command, server trace records are being written to the file named.

System Action: None.

User Response: None.

ANR0922ITrace ended.

Explanation: In response to a TRACE END command, server trace records are no longer being written.

System Action: None.

User Response: None.

ANR0923ETracing is inactive.

Explanation: A TRACE END command has been entered, but tracing is not active.

System Action: The command is ignored.

User Response: If tracing is desired, use the TRACE ENABLE and TRACE START commands to activate server tracing.

ANR0924ETracing is already active to file file spec.

Explanation: A TRACE BEGIN command has been entered, but tracing is already active to the file named.

System Action: The command is ignored.

User Response: If the current trace output file is acceptable, no action is required. Otherwise use the TRACE END command to stop tracing and then reissue the TRACE BEGIN command as desired.

ANR0925ETracing is already active to standard output.

Explanation: A TRACE BEGIN command has been entered, but tracing is already active to the standard output destination (usually the server console).

System Action: The command is ignored.

User Response: If the current trace output destination is acceptable, no action is required. Otherwise use the TRACE END command to stop tracing and then reissue the TRACE BEGIN command as desired.

ANR0926EMissing or invalid TRACE command parameter.

Explanation: The TRACE command issued contains an invalid parameter, or is missing a required parameter.

System Action: The command is ignored.

User Response: Reissue the command with the proper parameters.

ANR0927EUnknown trace class keyword - class.

Explanation: A TRACE ENABLE command has been entered which specifies an unknown trace class.

System Action: The command is ignored.

User Response: Reissue the TRACE command with the correct class.

ANR0928EUnable to open trace file file spec for appending.

Explanation: A TRACE BEGIN command specifies an output file, but the server cannot write to that file.

System Action: The command is ignored.

User Response: Check the file for proper access permissions, or reissue the TRACE command specifying a different output file.

ANR0929EInsufficient memory to activate tracing.

Explanation: A TRACE BEGIN command has been entered, but the server has insufficient memory available to activate tracing.

System Action: The command is ignored.

User Response: If tracing is required, make more memory available to the server then restart the server.

ANR0940ICancel request accepted for process process ID.

Explanation: A CANCEL PROCESS command has been entered for the specified process.

System Action: None.

User Response: None.

ANR0941ICommand: Cancel for process process ID is already pending.

Explanation: A CANCEL PROCESS command has been entered for the specified process, but a cancel is already pending for that process.

System Action: The server ignores the command.

User Response: None.

ANR0942ECommand: Process process ID cannot be found.

Explanation: A CANCEL PROCESS command has been entered for the specified process, but the process is not active. Either the process has already ended or the wrong process number has been entered.

System Action: The server ignores the command.

User Response: If the wrong process number has been entered, reissue the command with the correct process number.

ANR0943ECommand: Process process ID could not be canceled.

Explanation: A CANCEL PROCESS command has been entered for the specified process, but the process specified is an automatic process, such as migration or reclamation, that cannot be canceled.

System Action: The server ignores the command.

User Response: None.

ANR0944ECommand: No active processes found.

Explanation: A QUERY PROCESS command has been entered, and no processes are active.

System Action: The server ignores the command.

User Response: None.

ANR0945WDiagnosticID: Transaction transaction ID was aborted for process process ID.

Explanation: An error is detected during transaction commit for the specified process. This message should be preceded by other messages that give additional information about the failed transaction.

System Action: The activity that generated this error fails.

User Response: Check for additional messages and eliminate the condition that caused the failed transaction. If the error cannot be isolated and resolved, contact your service representative.

ANR0960IProcess process ID waiting for mount point in device class device class name.

Explanation: The process whose ID is shown has begun to wait for a mount point that can be used for a volume in the device class shown.

System Action: The process waits for the mount point.

User Response: Respond to any mount requests.

ANR0961IProcess process ID waiting for multiple mount points in device class device class name.

Explanation: The process whose ID is shown has begun to wait for multiple mount points that can be used for a volume in the device class shown.

System Action: The process waits for the mount points.

User Response: Respond to any mount requests.

ANR0962IProcess process ID waiting for mount points in device classes device class name and device class name.

Explanation: The process whose ID is shown has begun to wait for mount points that can be used for a volume in the two device classes shown.

System Action: The process waits for the mount points.

User Response: Respond to any mount requests.

ANR0963IProcess process ID waiting for mount of input volume volume name.

Explanation: The process whose ID is shown has begun to wait for the mount of the input volume shown.

System Action: The process waits for the mount.

User Response: Respond to any mount requests.

ANR0964IProcess process ID waiting for mount of output volume volume name.

Explanation: The process whose ID is shown has begun to wait for the mount of the output volume shown.

System Action: The process waits for the mount.

User Response: Respond to any mount requests.

ANR0965IProcess process ID waiting for mount of scratch volume.

Explanation: The process whose ID is shown has begun to wait for the mount of a scratch volume.

System Action: The process waits for the mount.

User Response: Respond to any mount requests.

ANR0966IProcess process ID waiting for access to input volume volume name.

Explanation: The process whose ID is shown has begun to wait for availability of the input volume shown.

System Action: The process waits for the volume to become available.

User Response: None.

ANR0967IProcess process ID waiting for access to output volume volume name.

Explanation: The process whose ID is shown has begun to wait for availability of the output volume shown.

System Action: The process waits for the volume to become available.

User Response: None.

ANR0980EThe server database must be audited with FIX=YES before the server can be started.

Explanation: The server has been restarted after a DSMSERV LOADDB command processed a database image that was known to have inconsistencies. In order to bring the database back to a consistent state, you must run the AUDITDB command.

System Action: Server initialization stops.

User Response: Issue the DSMSERV AUDITDB FIX=YES command. For complete details on this command, refer to the Administrator's Reference.

ANR0981EThe server database must be restored before the server can be started.

Explanation: The server has been restarted after an incomplete RESTORE DB. In order to start the server, you must restore to the database to a consistent state using the DSMSERV RESTORE DB command.

System Action: Server initialization stops.

User Response: Issue the DSMSERV RESTORE DB command. For complete details on this command, refer to the Administrator's Reference.

ANR0982EThe server database must be initialized before the database can be loaded.

Explanation: The server database must be initialized before it can be loaded with the LOADDB parameter, by issuing the DSMSERV FORMATL command. The server database is not currently in the initialized state.

System Action: Server LOADDB processing stops.

User Response: Issue the DSMSERV FORMATL command. For complete details on this command, refer to the Administrator's Reference.

ANR0983WThe server database was recorded by a down-level version of the server program. The UPGRADEDB parameter is required to start the server and automatically upgrade the database contents to the current server version. Please refer to installation instructions for precautionary backup procedures prior to doing this.

Explanation: At server startup, the server has discovered that the database information was written by an earlier version of the server program and is not compatible with this version. To automatically upgrade the server database to this version of the server program, the UPGRADEDB parameter must be specified when starting the server.

System Action: The server ends.

User Response: Refer to installation instructions for specific information on precautionary measures that you may want to take to back up the database prior to upgrading it to the current server level. After you have taken these measures, start the server and specify the UPGRADEDB parameter. This parameter only needs to be specified once to start the server, and should NOT be included in any automated programs that start the server.

ANR0984IProcess process ID for process name started in the process state at process start time.

Explanation: The process whose ID is shown has been started for the process indicated by the process name running in the indicated state.

System Action: None.

User Response: None.

ANR0985IProcess process ID for process name running in the process state completed with completion state completion state at process start time.

Explanation: The process whose ID is shown that was running for the process indicated by the process name running in the indicated state has completed with the completion state indicated.

System Action: None.

User Response: If the completion state was SUCCESS then no action is necessary. However, if the completion state is FAILURE then the user should review the activity log and/or event log to try to determine the cause of the failure.

ANR0986IProcess process ID for process name running in the process state processed items processed items for a total of bytes processed bytes with a completion state of completion state at process start time.

Explanation: The process whose ID is shown that was running for the process indicated by the process name running in the indicated state has completed processing the stated number of items and total number of bytes with the completion state indicated.

System Action: None.

User Response: If the completion state was SUCCESS then no action is necessary. However, if the completion state is FAILURE then the user should review the activity log and/or event log to try to determine the cause of the failure.

ANR0987IProcess process ID for process name running in the process state processed items processed items with a completion state of completion state at process start time.

Explanation: The process whose ID is shown that was running for the process indicated by the process name running in the indicated state has completed processing the stated number of items with the completion state indicated.

System Action: None.

User Response: If the completion state was SUCCESS then no action is necessary. However, if the completion state is FAILURE then the user should review the activity log and/or event log to try to determine the cause of the failure.

ANR0988IProcess process ID for process name running in the process state processed bytes processed bytes with a completion state of completion state at process start time.

Explanation: The process whose ID is shown that was running for the process indicated by the process name running in the indicated state has completed processing the stated number of bytes with the completion state indicated.

System Action: None.

User Response: If the completion state was SUCCESS then no action is necessary. However, if the completion state is FAILURE then the user should review the activity log and/or event log to try to determine the cause of the failure.

ANR0989EThe server database must be loaded or restored before the server can be started.

Explanation: The server has been restarted after an FORMATL. In order to start the server, you must load the database using either the DSMSERV LOADDB te or the DSMSERV RESTORE DB command.

System Action: Server initialization stops.

User Response: Issue the DSMSERV LOADDB or DSMSERV RESTORE DB command. For complete details on these commands, refer to the Administrator's Reference.

ANR0990IServer restart-recovery in progress.

Explanation: The server has been restarted after a halt or system failure. If necessary, the server performs recovery processing in order to bring the system back to a consistent state.

System Action: Server initialization continues.

User Response: None.

ANR0991IServer shutdown complete.

Explanation: In response to a HALT command, the server has completed its termination processing.

System Action: The server ends.

User Response: None.

ANR0992IServer installation complete.

Explanation: The server installation procedure has completed successfully. The server is now available for normal operation.

System Action: Server completes installation processing.

User Response: None.

ANR0993IServer initialization complete.

Explanation: The server has been restarted after a halt or system failure. It is now ready to resume normal operation.

System Action: Server completes initialization.

User Response: None.

ANR0994WThis server has not been properly installed.

Explanation: The server was started for normal operation, but had not yet been installed.

System Action: The server ends.

User Response: Install the server properly before starting it.

ANR0995WThis version of the server program is down-level with respect to the information recorded on disk; a newer version of the program should be used.

Explanation: At server startup, the server has discovered that the disk information was written by a later version of the server program. This version of the server program should not be used.

System Action: The server ends.

User Response: Start a version of the server program that is at the same level as the prior server program used.

ANR0996WThe information on disk was recorded by a down-level version of the server program; re-installation is required to use this version.

Explanation: At server startup, the server has discovered that the disk information was written by an earlier version of the server program and is not compatible with this version.

System Action: The server ends.

User Response: Install this version of the server to bring the information up to the level of the program being used.

ANR1000IMigration process process ID started for storage pool storage pool name.

Explanation: Because the high migration threshold for the storage pool shown has been exceeded, a process has been started to migrate files from the storage pool.

System Action: Data is moved from this storage pool to the next (target) pool.

User Response: None.

ANR1001IMigration process process ID ended for storage pool storage pool name.

Explanation: A migration process for the named storage pool ends. This action can occur because the low migration threshold for the storage pool has been reached or because there are no more nodes with files to be migrated.

System Action: None.

User Response: None.

ANR1002IMigration for storage pool storage pool name will be retried in number of seconds seconds.

Explanation: Because of a problem encountered attempting migration for the named storage pool, migration is delayed but will be retried after the time period shown.

System Action: The server waits for the specified period and then retries migration for the storage pool. This delay applies to a single migration process. After a number of unsuccessful retries, the server will automatically cancel the process. If other migration processes are executing for the named storage pool, these processes will continue migration.

User Response: If possible, correct the condition that has caused delayed migration.

ANR1003IMigration retry delay ended; checking migration status for storage pool storage pool name.

Explanation: Because migration for the indicated storage pool had been delayed due to a problem, the system waited before retrying. The retry wait period has ended, and the system will now retry migration.

System Action: Migration processing for the storage pool resumes.

User Response: None.

ANR1004IServer formatting complete, database ready for loading.

Explanation: The server formatting procedure has completed successfully. The server is ready to loaded using the DSMSERV LOADDB or DSMSERV RESTORE DB command.

System Action: Server completes formatting processing.

User Response: The DSMSERV LOADDB or DSMSERV RESTORE DB command must be used to load the database before the server will be ready for use. For complete details on these commands, refer to the Administrator's Reference.

ANR1020WMigration process process ID terminated for storage pool storage pool name - process canceled.

Explanation: During migration for the indicated storage pool, a process performing the migration has been canceled.

System Action: The migration process is terminated. If other migration processes are executing for the named storage pool, these processes will continue migration.

User Response: None.

ANR1021WMigration process process ID terminated for storage pool storage pool name - storage media inaccessible.

Explanation: During migration for the indicated storage pool, a required volume could not be mounted.

System Action: The indicated migration process ends. The server waits for the retry period to expire and then tries the migration again. If other migration processes are executing for the named storage pool, these processes will continue migration.

User Response: None.

ANR1022WMigration process process ID terminated for storage pool storage pool name - excessive read errors encountered.

Explanation: During migration for the indicated storage pool, read errors occur that prevented the migration from continuing.

System Action: The indicated migration process ends. The server waits for the retry period to expire and then tries the migration again. If other migration processes are executing for the named storage pool, these processes will continue migration.

User Response: If possible, correct the cause of the read errors.

ANR1023WMigration process process ID terminated for storage pool storage pool name - excessive write errors encountered.

Explanation: During migration for the indicated storage pool, write errors occur that prevent the migration from continuing.

System Action: The indicated migration process ends. The server waits for the retry period to expire and then tries the migration again. If other migration processes are executing for the named storage pool, these processes will continue migration.

User Response: If possible, correct the cause of the write errors.

ANR1024WMigration process process ID terminated for storage pool storage pool name - data transfer interrupted.

Explanation: During migration for the indicated storage pool, a data transfer operation was interrupted and could not be continued.

System Action: The indicated migration process ends. The server waits for the retry period to expire and then tries the migration again. If other migration processes are executing for the named storage pool, these processes will continue migration.

User Response: If possible, correct the cause of the interruption.

ANR1025WMigration process process ID terminated for storage pool storage pool name - insufficient space in subordinate storage pool.

Explanation: During migration for the indicated storage pool, the server cannot move the data from the storage pool, because there is not enough space on the next storage pool to hold it.

System Action: The indicated migration process ends. The server waits for the retry period to expire and then tries the migration again.

User Response: Make more space available in the next storage pool, or use the UPDATE STGPOOL command to change the next storage pool to one with more space.

ANR1026WMigration process process ID terminated for storage pool storage pool name - unable to move file to subordinate storage pool due to exclusion by size.

Explanation: During migration for the indicated storage pool, the server cannot move the data from the storage pool, because a file is larger than what is allowed on the next storage pool.

System Action: The indicated migration process ends. The server waits for the retry period to expire and then tries the migration again. If other migration processes are executing for the named storage pool, these processes will continue migration.

User Response: Use the UPDATE STGPOOL command to change the next storage pool maximum file size or to change the next storage pool target.

ANR1027WMigration process process ID terminated for storage pool storage pool name - sufficient recovery log space is not available.

Explanation: During migration for the indicated storage pool, the server runs out of recovery log space.

System Action: The indicated migration process ends. The server waits for the retry period to expire and then tries the migration again.

User Response: If necessary, make more server recovery log space available.

ANR1028WMigration process process ID terminated for storage pool storage pool name - sufficient database space is not available.

Explanation: During migration for the indicated storage pool, the server runs out of database space.

System Action: The indicated migration process ends. The server waits for the retry period to expire and then tries the migration again.

User Response: If necessary, make more server database space available.

ANR1029WMigration process process ID terminated for storage pool storage pool name - lock conflict.

Explanation: During migration for the indicated storage pool, the server needs to obtain a lock that is not available.

System Action: The indicated migration process ends. The server waits for the retry period to expire and then tries the migration again. If other migration processes are executing for the named storage pool, these processes will continue migration.

User Response: Wait for the server to retry the migration.

ANR1030WMigration process process ID terminated for storage pool storage pool name - thread resource not available.

Explanation: During migration for the indicated storage pool, the server cannot start a thread for the migration process.

System Action: The indicated migration process ends. The server waits for the retry period to expire and then tries the migration again. If other migration processes are executing for the named storage pool, these processes will continue migration.

User Response: Wait for the server to retry the migration. If the error persists, it may indicate a shortage of server memory.

ANR1031WMigration process process ID terminated for storage pool storage pool name - sufficient memory is not available.

Explanation: During migration for the indicated storage pool, there is not enough server memory available.

System Action: The indicated migration process ends. The server waits for the retry period to expire and then tries the migration again.

User Response: If necessary, make more memory available to the server.

ANR1032WMigration process process ID terminated for storage pool storage pool name - internal server error detected.

Explanation: During migration for the indicated storage pool, the server encounters an internal error.

System Action: The indicated migration process ends. The server waits for the retry period to expire and then tries the migration again. If other migration processes are executing for the named storage pool, these processes will continue migration.

User Response: Contact your service representative.

ANR1033WMigration process process ID terminated for storage pool storage pool name - transaction aborted.

Explanation: During migration for the indicated storage pool, the server detected an error while attempting to commit a transaction. This message should be preceded by other messages that give additional information about the failed transaction.

System Action: The indicated migration process ends. The server waits for the retry period to expire and then tries the migration again. If other migration processes are executing for the named storage pool, these processes will continue migration.

User Response: Check for additional messages and eliminate the condition that caused the failed transaction.

ANR1034WFiles stored on volume volume name cannot be migrated - volume is offline or access mode is "unavailable" or "destroyed".

Explanation: During migration, files on the indicated volume cannot be migrated either because the volume has been varied offline or because of the volume's access mode.

System Action: The server continues migration processing, but skips files stored on the indicated volume.

User Response: If necessary, use the VARY ON or UPDATE VOLUME command for this volume.

ANR1040ISpace reclamation started for volume volume name, storage pool storage pool name (process number process ID).

Explanation: The percentage of reclaimable space on the volume shown has reached the reclaim percentage specified for the storage group; as a result, data from the volume is moved to another volume so that the volume can be reclaimed.

System Action: The server starts volume space reclamation.

User Response: None.

ANR1041ISpace reclamation ended for volume volume name.

Explanation: Space reclamation for the volume named is complete.

System Action: None.

User Response: None.

ANR1042ISpace reclamation for storage pool storage pool name will be retried in number of seconds seconds.

Explanation: Because of a problem encountered attempting space reclamation for the named storage pool, reclamation stops but will be retried after the time period shown. After a number of unsuccessful retries, the process will be automatically cancelled.

System Action: The system waits for the specified period and then retries space reclamation for the storage pool.

User Response: If possible, correct the condition that has stopped reclamation.

ANR1043ISpace reclamation retry delay ended; checking volume reclamation status for storage pool storage pool name.

Explanation: Because space reclamation for the indicated storage pool had been stopped due to a problem, the system waited before retrying. The retry wait period has ended, and the system can now retry space reclamation.

System Action: Reclamation for the pool begins.

User Response: None.

ANR1044IRemovable volume volume name is required for space reclamation.

Explanation: During space reclamation processing, the server determines that a removable volume is required in order to complete processing.

System Action: The server attempts to mount the removable volume.

User Response: Respond to any mount request for the indicated volume.

ANR1060WError initiating space reclamation for storage pool storage pool name - lock conflict.

Explanation: While attempting to initiate space reclamation for the indicated storage pool, the server needs to obtain a lock that is not available.

System Action: Space reclamation stops. The server waits for the retry period to expire and then tries the reclamation again.

User Response: Wait for the server to retry the reclamation.

ANR1061WError initiating space reclamation for storage pool storage pool name - sufficient memory is not available.

Explanation: During an attempt to initiate space reclamation for the indicated storage pool, there is not enough server memory available.

System Action: Space reclamation stops. The server waits for the retry period to expire and then tries the reclamation again.

User Response: If necessary, make more memory available to the server.

ANR1062WError initiating space reclamation for storage pool storage pool name - internal server error detected.

Explanation: During an attempt to initiate space reclamation for the indicated storage pool, an internal server error is encountered.

System Action: Space reclamation stops. The server will wait for the retry period to expire and then tries the reclamation again.

User Response: Contact your service representative.

ANR1080WSpace reclamation terminated for volume volume name - process canceled.

Explanation: During space reclamation for the indicated volume, the process performing the reclamation has been canceled.

System Action: Space reclamation stops. The server waits for the retry period to expire and then tries the reclamation again.

User Response: None.

ANR1081WSpace reclamation terminated for volume volume name - storage media inaccessible.

Explanation: During space reclamation for the indicated volume, a required volume cannot be mounted.

System Action: Space reclamation stops. The server waits for the retry period to expire and then tries the reclamation again.

User Response: None.

ANR1082WSpace reclamation terminated for volume volume name - insufficient number of mount points available for removable media.

Explanation: During space reclamation for the indicated volume, the server could not allocate sufficient mount points for the volumes required.

System Action: Space reclamation stops. The server waits for the retry period to expire and then tries the reclamation again.

User Response: If necessary, make more mount points available.

ANR1083WSpace reclamation terminated for volume volume name - excessive read errors encountered.

Explanation: During space reclamation for the indicated volume, read errors occur that prevent reclamation from continuing.

System Action: Space reclamation stops. The server waits for the retry period to expire and then tries the reclamation again.

User Response: If possible, determine and correct the cause of the read errors.

ANR1084WSpace reclamation terminated for volume volume name - excessive write errors encountered.

Explanation: During space reclamation for the indicated volume, write errors occur that prevent reclamation from continuing.

System Action: Space reclamation stops. The server waits for the retry period to expire and then tries the reclamation again.

User Response: If possible, determine and correct the cause of the write errors.

ANR1085WSpace reclamation terminated for volume volume name - data transfer interrupted.

Explanation: During space reclamation for the indicated volume, a data transfer operation has been interrupted and cannot be continued.

System Action: Space reclamation stops. The server waits for the retry period to expire and then tries the reclamation again.

User Response: If possible, determine and correct the cause of the interruption.

ANR1086WSpace reclamation terminated for volume volume name - insufficient space in storage pool.

Explanation: During space reclamation for the indicated volume, the server determines that data cannot be moved from the volume due to insufficient space on other volumes in the storage pool.

System Action: Space reclamation stops. The server waits for the retry period to expire and then tries the reclamation again.

User Response: Make more space available on other volumes in the storage pool.

ANR1087WSpace reclamation terminated for volume volume name - sufficient recovery log space is not available.

Explanation: During space reclamation for the indicated volume, the server runs out of recovery log space.

System Action: Space reclamation stops. The server waits for the retry period to expire and then tries the reclamation again.

User Response: If necessary, make more server recovery log space available.

ANR1088WSpace reclamation terminated for volume volume name - sufficient database space is not available.

Explanation: During space reclamation for the indicated volume, the server runs out of database space.

System Action: Space reclamation stops. The server waits for the retry period to expire and then tries the reclamation again.

User Response: If necessary, make more server database space available.

ANR1089WSpace reclamation terminated for volume volume name - lock conflict.

Explanation: During space reclamation for the indicated volume, the server needed to obtain a lock that is not available.

System Action: Space reclamation stops. The server waits for the retry period to expire and then tries the reclamation again.

User Response: Wait for the server to retry the reclamation.

ANR1090WSpace reclamation terminated for volume volume name - thread resource not available.

Explanation: During space reclamation for the indicated volume, the server cannot start a thread for the reclamation process.

System Action: Space reclamation stops. The server waits for the retry period to expire and then tries the reclamation again.

User Response: Wait for the server to retry the reclamation. If the error persists, it may indicate a shortage of server memory.

ANR1091WSpace reclamation terminated for volume volume name - sufficient memory is not available.

Explanation: During space reclamation for the indicated volume, there was not enough server memory available.

System Action: Space reclamation stops. The server waits for the retry period to expire and then tries the reclamation again.

User Response: If necessary, make more memory available to the server.

ANR1092WSpace reclamation terminated for volume volume name - internal server error detected.

Explanation: During space reclamation for the indicated volume, the server encounters an internal error.

System Action: Space reclamation stops. The server waits for the retry period to expire and then tries the reclamation again.

User Response: Contact your service representative.

ANR1093WSpace reclamation terminated for volume volume name - transaction aborted.

Explanation: During space reclamation for the indicated volume, the server detected an error while attempting to commit a transaction.

System Action: Space reclamation stops. The server waits for the retry period to expire and then tries the reclamation again.

User Response: Check for additional messages and eliminate the condition that caused the failed transaction.

ANR1100IMigration started for volume volume name, storage pool storage pool name (process number process ID).

Explanation: Because the high migration threshold for the indicated storage pool has been exceeded, migration of files from the volume shown begins.

System Action: The system moves the data from this volume to the next (target) pool.

User Response: None.

ANR1101IMigration ended for volume volume name.

Explanation: Because the low migration threshold for the indicated storage pool has been reached, migration of files from the indicated volume ends.

System Action: None.

User Response: None.

ANR1102IRemovable volume volume name is required for migration.

Explanation: During migration processing, the server determines that a removable volume is required in order to complete processing.

System Action: The server attempts to mount the removable volume.

User Response: Respond to any mount request for the indicated volume.

ANR1115WError initiating migration for storage pool storage pool name - lock conflict.

Explanation: While trying to start migration for the indicated storage pool, the server needs to obtain a lock that is not available.

System Action: Migration stops. The server waits for the retry period to expire and then tries the migration again.

User Response: Wait for the server to retry the migration.

ANR1116WError initiating migration for storage pool storage pool name - sufficient memory is not available.

Explanation: While trying to start migration for the indicated storage pool, there is not enough server memory available.

System Action: Migration stops. The server waits for the retry period to expire and then tries the migration again.

User Response: If necessary, make more memory available to the server.

ANR1117WError initiating migration for storage pool storage pool name - internal server error detected.

Explanation: While trying to start migration for the indicated storage pool, the server encounters an internal error.

System Action: Migration stops. The server waits for the retry period to expire and then tries the migration again.

User Response: Contact your service representative.

ANR1120WMigration terminated for volume volume name - process canceled.

Explanation: During migration for the indicated volume, the process performing the migration has been canceled.

System Action: The migration process is terminated. If other migration processes are executing for the named storage pool, these processes will continue migration.

User Response: None.

ANR1121WMigration terminated for volume volume name - storage media inaccessible.

Explanation: During migration for the indicated volume a required volume cannot be mounted.

System Action: Migration stops. The server waits for the retry period to expire and then tries the migration again.

User Response: None.

ANR1122WMigration terminated for volume volume name - insufficient number of mount points available for removable media.

Explanation: During migration for the indicated volume the server could not allocate sufficient mount points for the volumes required.

System Action: Migration stops. The server waits for the retry period to expire and then tries the migration again.

User Response: If necessary, make more mount points available.

ANR1123WMigration terminated for volume volume name - excessive read errors encountered.

Explanation: During migration for the indicated volume, read errors occurred that prevent the migration from continuing.

System Action: Migration stops. The server waits for the retry period to expire and then tries the migration again.

User Response: If possible, correct the cause of the read errors.

ANR1124WMigration terminated for volume volume name - excessive write errors encountered.

Explanation: During migration for the indicated volume, write errors occurred that prevent the migration from continuing.

System Action: Migration stops. The server waits for the retry period to expire and then tries the migration again.

User Response: If possible, correct the cause of the write errors.

ANR1125WMigration terminated for volume volume name - data transfer interrupted.

Explanation: During migration for the indicated volume a data transfer operation was interrupted and could not be continued.

System Action: Migration stops. The server waits for the retry period to expire and then tries the migration again.

User Response: If possible, determine and correct the cause of the interruption.

ANR1126WMigration terminated for volume volume name - insufficient space in subordinate storage pools.

Explanation: During migration for the indicated volume, the server cannot move the data from the volume because there is not enough space on the next storage pool to hold it.

System Action: Migration stops. The server waits for the retry period to expire and then tries the migration again.

User Response: Make more space available in the next storage pool or use the UPDATE STGPOOL command to change the next storage pool to one with more space.

ANR1127WMigration terminated for volume volume name - unable to move file to subordinate storage pool due to exclusion by size.

Explanation: During migration for the indicated volume, the server cannot move the data from the volume because a file size is larger than allowed on the next storage pool.

System Action: Migration stops. The server waits for the retry period to expire and then tries the migration again.

User Response: Use the UPDATE STGPOOL command to change the next storage pool maximum file size or to change the next storage pool target.

ANR1128WMigration terminated for volume volume name - sufficient recovery log space is not available.

Explanation: During migration for the indicated volume, the server runs out of recovery log space.

System Action: Migration stops. The server waits for the retry period to expire and then tries the migration again.

User Response: If necessary, make more server recovery log space available.

ANR1129WMigration terminated for volume volume name - sufficient database space is not available.

Explanation: During migration for the indicated volume pool, the server runs out of database space.

System Action: Migration stops. The server waits for the retry period to expire and then tries the migration again.

User Response: If necessary, make more server database space available.

ANR1130WMigration terminated for volume volume name - lock conflict.

Explanation: During migration for the indicated volume, the server needs to obtain a lock that is not available.

System Action: Migration stops. The server waits for the retry period to expire and then tries the migration again.

User Response: Wait for the server to retry the migration.

ANR1131WMigration terminated for volume volume name - thread resource not available.

Explanation: During migration for the indicated volume, the server cannot start a thread for the migration process.

System Action: Migration stops. The server waits for the retry period to expire and then tries the migration again.

User Response: Wait for the server to retry the migration. If the error persists, it may indicate a shortage of server memory.

ANR1132WMigration terminated for volume volume name - sufficient memory is not available.

Explanation: During migration for the indicated volume, there is not enough server memory available.

System Action: Migration stops. The server waits for the retry period to expire and then tries the migration again.

User Response: If necessary, make more memory available to the server.

ANR1133WMigration terminated for volume volume name - internal server error detected.

Explanation: During migration for the indicated volume, the server encounters an internal error.

System Action: Migration stops. The server waits for the retry period to expire and then tries the migration again.

User Response: Contact your service representative.

ANR1134WMigration terminated for storage pool storage pool name - insufficient number of mount points available for removable media.

Explanation: During migration for the indicated storage pool the server could not allocate sufficient mount points in the next storage pool.

System Action: Migration stops. The server waits for the retry period to expire and then tries the migration again.

User Response: If necessary, make more mount points available.

ANR1135WMigration terminated for volume volume name - transaction aborted.

Explanation: During migration for the indicated volume, the server detected an error while attempting to commit a transaction.

System Action: Migration stops. The server waits for the retry period to expire and then tries the migration again.

User Response: Check for additional messages and eliminate the condition that caused the failed transaction.

ANR1140IMove data process started for volume volume name (process ID process ID).

Explanation: As a result of a MOVE DATA command, a process begins to move data from the volume shown.

System Action: The server moves all data from the volume.

User Response: None.

ANR1141IMove data process ended for volume volume name.

Explanation: The MOVE DATA command for the volume shown completes.

System Action: None.

User Response: None.

ANR1142IMoving data for collocation cluster cluster number of total clusters on volume volume name.

Explanation: As a result of a MOVE DATA command, data moves from the volume indicated to new volumes; the message shows the total number of clusters (data objects) on the volume and the current cluster being processed.

System Action: None.

User Response: None.

ANR1143WMove data process terminated for volume volume name - process canceled.

Explanation: During move data processing for the indicated volume, the process performing the move data was canceled.

System Action: The server ends the MOVE DATA command.

User Response: None.

ANR1144WMove data process terminated for volume volume name - storage media inaccessible.

Explanation: During move data processing for the indicated volume, a required volume cannot be mounted.

System Action: The server ends the MOVE DATA command.

User Response: None.

ANR1145WMove data process terminated for volume volume name - insufficient number of mount points available for removable media.

Explanation: During move data processing for the indicated volume, the server could not allocate sufficient mount points for the volumes required.

System Action: The server ends the MOVE DATA command.

User Response: If necessary, make more mount points available.

ANR1146WMove data process terminated for volume volume name - excessive read errors encountered.

Explanation: During move data processing for the indicated volume, read errors occurred that prevented the move from continuing.

System Action: The server ends the MOVE DATA command.

User Response: If possible, correct the cause of the read errors and then reissue the MOVE DATA command.

ANR1147WMove data process terminated for volume volume name - excessive write errors encountered.

Explanation: During move data processing for the indicated volume, write errors occurred that prevented the move from continuing.

System Action: The server ends the MOVE DATA command.

User Response: If possible, correct the cause of the write errors and then reissue the MOVE DATA command.

ANR1148WMove data process terminated for volume volume name - data transfer interrupted.

Explanation: During move data processing for the indicated volume a data transfer operation was interrupted and could not be continued.

System Action: The server ends the MOVE DATA command.

User Response: If possible, determine and correct the cause of the interruption.

ANR1149WMove data process terminated for volume volume name - insufficient space in target storage pool.

Explanation: During move data processing for the indicated volume, the server cannot move the data from the volume, because there is not enough space on the destination storage pool to hold it.

System Action: The server ends the MOVE DATA command.

User Response: Make more space available in the next storage pool, or specify a storage pool with more space, and reissue the MOVE DATA command.

ANR1150WMove data process terminated for volume volume name - unable to move file to target storage pool due to exclusion by size.

Explanation: During move data processing for the indicated volume, the server cannot move the data from the volume because a file size is larger than allowed on the next storage pool.

System Action: The server ends the MOVE DATA command.

User Response: Use the UPDATE STGPOOL command to change the next storage pool maximum file size or to change the next storage pool target, and then reissue the MOVE DATA command.

ANR1151WMove data process terminated for volume volume name - sufficient recovery log space is not available.

Explanation: During move data processing for the indicated volume, the server runs out of recovery log space.

System Action: The server ends the MOVE DATA command.

User Response: If necessary, make more server recovery log space available.

ANR1152WMove data process terminated for volume volume name - sufficient database space is not available.

Explanation: During move data processing for the indicated volume, the server runs out of database space.

System Action: The server ends the MOVE DATA command.

User Response: If necessary, make more server database space available.

ANR1153WMove data process terminated for volume volume name - lock conflict.

Explanation: During move data processing for the indicated volume, the server needs to obtain a lock that was not available.

System Action: The server ends the MOVE DATA command.

User Response: Reissue the MOVE DATA command.

ANR1154WMove data process terminated for volume volume name - thread resource not available.

Explanation: During move data processing for the indicated volume, the server cannot start a thread for the migration process.

System Action: The server ends the MOVE DATA command.

User Response: Reissue the MOVE DATA command. If the error persists, it may indicate a shortage of server memory.

ANR1155WMove data process terminated for volume volume name - sufficient memory is not available.

Explanation: During move data processing for the indicated volume, there is not enough server memory available.

System Action: The server ends the MOVE DATA command.

User Response: If necessary, make more memory available to the server, and then reissue the MOVE DATA command.

ANR1156WMove data process terminated for volume volume name - internal server error detected.

Explanation: During move data processing for the indicated volume, the server encounters an internal error.

System Action: The server ends the MOVE DATA command.

User Response: Contact your service representative.

ANR1157IRemovable volume volume name is required for Move Data process.

Explanation: During move data processing for the indicated volume, the server determines that a removable volume is required in order to complete processing.

System Action: The server attempts to mount the removable volume.

User Response: Respond to any mount request for the indicated volume.

ANR1160WTransaction was aborted for volume volume name.

Explanation: An error was detected during transaction commit. This message should be preceded by other messages that give additional information about the failed transaction.

System Action: The activity that generated this error fails.

User Response: Check for additional messages and eliminate the condition that caused the failed transaction. If the error cannot be isolated and resolved, contact your service representative.

ANR1161WMove Data skipping damaged file on volume volume name: Node node name, Type file type, File space filespace name, File name file name.

Explanation: During move data, a file is encountered that was previously found to be damaged. If this file is part of an aggregate, the entire aggregate was previously marked damaged, possibly because an integrity error was detected for some other file within the aggregate.

System Action: The damaged file is not moved.

User Response: Audit the indicated volume with FIX=NO to verify that the file is damaged. The audit will reset the file status if the file is found to be undamaged during the audit. If the file is part of an aggregate, the audit will reset the aggregate status if the entire aggregate is found to be undamaged. If this volume is in a primary storage pool that has previously been backed up to a copy storage pool, attempt to restore damaged files by using the RESTORE STGPOOL command.

ANR1162WSpace reclamation skipping damaged file on volume volume name: Node node name, Type file type, File space filespace name, File name file name.

Explanation: During reclamation, a file is encountered that was previously found to be damaged. If this file is part of an aggregate, the entire aggregate was previously marked damaged, possibly because an integrity error was detected for some other file within the aggregate.

System Action: The damaged file is not moved.

User Response: Audit the indicated volume with FIX=NO to verify that the file is damaged. The audit will reset the file status if the file is found to be undamaged during the audit. If the file is part of an aggregate, the audit will reset the aggregate status if the entire aggregate is found to be undamaged. If this volume is in a primary storage pool that has previously been backed up to a copy storage pool, attempt to restore damaged files by using the RESTORE STGPOOL command.

ANR1163WOffsite volume volume name still contains files which could not be moved.

Explanation: During processing of a MOVE DATA command or reclamation, the server determined that the indicated offsite volume contained one or more files that could not be moved. One or more files could not be copied from the other available volumes.

System Action: None.

User Response: Check for messages indicating reasons why files could not be moved. To complete the move operation, you have several options:

ANR1165EData-integrity error detected for file in storage pool storage pool name: Node node name, Type file type, File space filespace name, File name file name.

Explanation: The server has detected a data-integrity error for the indicated file.

System Action: The file will be marked damaged in the server database, and will not be accessed for future operations. If this file is part of an aggregate, the entire aggregate will be marked damaged. If a usable copy of the file exists in another storage pool, that copy may be accessed for future operations involving the file.

User Response: If the indicated storage pool is a primary pool, and a usable copy of the file exists in a copy storage pool, you can recreate the file in the primary pool using the RESTORE STGPOOL command. If the indicated storage pool is a copy storage pool, it is possible that the primary copy of the file is usable, but was not accessed because the access mode for the primary storage pool or volume is unavailable. If this is the case, the primary copy of the file may be made accessible by changing the access mode of the primary pool or volume.

ANR1166EMove Data for offsite volume cannot copy damaged file in storage pool storage pool name: Node node name, Type file type, File space filespace name, File name file name.

Explanation: A move data process for an offsite volume cannot locate an undamaged copy of the specified file in any storage pool accessible by the server. If this file is part of an aggregate, the process could not locate an undamaged copy of the aggregate to which the file belongs.

System Action: The file will skipped and will not be moved from the offsite volume.

User Response: The indicated storage pool is a primary pool that contains a damaged copy of the file. The only usable copy of the file may now only reside on the offsite volume that was involved in the move data process. If you bring this volume back onsite, you can recreate the file in the primary pool by using the RESTORE STGPOOL command. After the restore, you can reissue the MOVE DATA command.

ANR1167ESpace reclamation for offsite volume(s) cannot copy damaged file in storage pool storage pool name: Node node name, Type file type, File space filespace name, File name file name.

Explanation: A reclamation process of offsite volumes cannot locate an undamaged copy of the specified file in any storage pool accessible by the server. If this file is part of an aggregate, the process could not locate an undamaged copy of the aggregate to which the file belongs.

System Action: The file is skipped and will not be moved from the offsite volume.

User Response: The indicated storage pool is a primary pool that contains a damaged copy of the file. The only usable copy of the file may now only reside on an offsite volume that was involved in the reclamation process, but was not totally reclaimed. If you bring this volume back onsite, you can recreate the file in the primary pool by using the RESTORE STGPOOL command.

ANR1168WMigration skipping damaged file on volume volume name: Node node name, Type file type, File space filespace name, File name file name.

Explanation: During migration, a file is encountered that was previously found to be damaged. If this file is part of an aggregate, the entire aggregate was previously marked damaged, possibly because an integrity error was detected for some other file within the aggregate.

System Action: The damaged file will not be moved.

User Response: Audit the indicated volume with FIX=NO to verify that the file is damaged. The audit will reset the file status if the file is found to be undamaged during the audit. If the file is part of an aggregate, the audit will reset the aggregate status if the entire aggregate is found to be undamaged. If this volume is in a primary storage pool that has previously been backed up to a copy storage pool, you can also attempt to restore damaged files by using the RESTORE STGPOOL command.

ANR1169WLock conflict on movement of offsite file - file is skipped.

Explanation: During migration, reclamation, or move data processing of a volume that is offsite, a copy of the file that resides in a primary disk storage pool is locked by another process.

System Action: The file is skipped and the process will try to find another copy of the file in a copy storage pool. If another copy cannot be used, the move operation on the volume may be incomplete.

User Response: If a move operation was incomplete, try repeating the operation.

ANR1170EOut of Space in target copy storage pool: copy storage pool name.

Explanation: During reclamation, or move data processing of a volume that is offsite, there was no volume available in the specified target copy storage pool.

System Action: The operation is terminated.

User Response: Define volumes to the copy storage pool or raise the MAXSCRATCH value.

ANR1171WUnable to move files associated with node node name, filespace filespace name on volume volume name due to restore in progress.

Explanation: During movement of data (migration, reclamation, move data) from a sequential volume, one or more files were encountered that were locked by a restore operation.

System Action: The files are not moved, but are skipped.

User Response: Use the QUERY RESTORE FORMAT=DETAILED command to determine if the restore operation is active or is in restartable state. A restartable restore operation will keep the files locked from movement until the RESTOREINTERVAL is reached. QUERY OPTION will display this interval. You may wish to lower the RESTOREINTERVAL to cause a restartable restore operation to be removed and free up the locked files. The RESTOREINTERVAL is a server option.

ANR1172EMove Data for offsite volume cannot copy file in storage pool storage pool name: Node node name, Type file type, File space filespace name, File name file name.

Explanation: A move data process for an offsite volume cannot locate a copy of the specified file in any storage pool accessible by the server. If this file is part of an aggregate, the process could not locate copy of the aggregate to which the file belongs on an accessible volume.

System Action: The file will skipped and will not be moved from the offsite volume.

User Response: The indicated storage pool is a primary pool that should contain a primary copy of the file. Perhaps the volume on which that file resides is on a destroyed volume. The only usable copy of the file may now only reside on the offsite volume that was involved in the move data process. If you bring this volume back onsite, you can recreate the file in the primary pool by using the RESTORE STGPOOL command. After the restore, you can reissue the MOVE DATA command.

ANR1173ESpace reclamation for offsite volume(s) cannot copy file in storage pool storage pool name: Node node name, Type file type, File space filespace name, File name file name.

Explanation: A reclamation process of offsite volumes cannot locate a copy of the specified file in any storage pool accessible by the server. If this file is part of an aggregate, the process could not locate a copy of the aggregate to which the file belongs on an accessible volume.

System Action: The file is skipped and will not be moved from the offsite volume.

User Response: The indicated storage pool is a primary pool that should contain a copy of the file. Perhaps the volume on which that file resides is on a destroyed volume. The only usable copy of the file may now only reside on an offsite volume that was involved in the reclamation process, but was not totally reclaimed. If you bring this volume back onsite, you can recreate the file in the primary pool by using the RESTORE STGPOOL command.

ANR1174WOne or more cached files were not deleted on volume volume name.

Explanation: The MOVE DATA command could not delete one or more cached files on the disk volume shown. Migration was probably running at the same time, creating cached files while the MOVE DATA command was trying to delete them.

System Action: The MOVE DATA command ran to completion.

User Response: If you want the remaining cached files removed from the disk volume, reissue the MOVE DATA command.

ANR1175WVolume volume name contains files which could not be reclaimed.

Explanation: After reclamation of the indicated volume, it still contains one or more files that could not be reclaimed. These files were skipped because of read errors, or because the files are marked damaged.

System Action: The volume is marked unavailable so it will not be chosen again for reclamation.

User Response:

ANR1180WAccess mode for volume volume name has been set to "unavailable" due to file read or integrity errors.

Explanation: During processing of a storage pool volume, input/output or other errors occur that force the server to mark the volume unavailable for further processing.

System Action: The server sets the volume status to unavailable.

User Response: Correct the errors that set the volume to unavailable, or use the DELETE VOLUME command to remove it from the system.

ANR1181EDiagnosticID: Data storage transaction transaction ID was aborted.

Explanation: A database transaction failed because of an error that was detected during data storage processing. This message should be preceded by other messages that give additional information about the failed transaction.

System Action: The server operation that encountered this error during data storage processing fails.

User Response: Check for additional messages and eliminate the condition that caused the failed transaction.

ANR1199IRemovable volume volume name is required for audit process.

Explanation: During audit volume processing for the indicated volume, the server determines that a removable volume is required in order to complete processing.

System Action: The server attempts to mount the removable volume.

User Response: Respond to any mount request for the indicated volume.

ANR1210IBackup of primary storage pool primary pool name to copy storage pool copy pool name started as process process ID.

Explanation: A process has been started to back up a primary storage pool to the indicated copy storage pool.

System Action: For every noncached file in the primary pool, a backup copy is made in the copy pool, if a copy of that file does not already exist.

User Response: None.

ANR1211IBackup preview of primary storage pool primary pool name to copy storage pool copy pool name started as process process ID.

Explanation: A preview process has been started to back up a primary storage pool to the indicated copy storage pool.

System Action: Preview information about the backup operation is collected and displayed, but files are not backed up.

User Response: None.

ANR1212IBackup process process ID ended for storage pool storage pool name.

Explanation: A backup process for the named primary storage pool has ended.

System Action: None.

User Response: None.

ANR1213IBackup process process ID terminated for storage pool storage pool name - process canceled.

Explanation: During backup of the indicated primary storage pool, a process performing the backup has been canceled.

System Action: If other backup processes are executing for the named storage pool, these processes continue.

User Response: None.

ANR1214IBackup of primary storage pool primary pool name to copy storage pool copy pool name has ended. Files Backed Up: number of files, Bytes Backed Up: number of bytes, Unreadable Files: number of unreadable files, Unreadable Bytes: number of bytes in unreadable files.

Explanation: Backup processing for the specified storage pool has ended with the results shown.

System Action: None.

User Response: Examine previous messages to determine whether all backup processes ended successfully.

ANR1215IBackup preview of primary storage pool primary pool name to copy storage pool copy pool name has ended. Files Backed Up: number of files, Bytes Backed Up: number of bytes.

Explanation: Backup preview processing for the specified storage pool has ended with the results shown.

System Action: None.

User Response: None.

ANR1216ECommand: Process process ID terminated - storage media inaccessible.

Explanation: During backup processing, a required volume could not be mounted.

System Action: The indicated backup process ends.

User Response: None.

ANR1217ECommand: Process process ID terminated - insufficient number of mount points available for removable media.

Explanation: During backup processing, the server could not allocate sufficient mount points for the volumes required.

System Action: The indicated backup process ends.

User Response: If necessary, make more mount points available.

ANR1218ECommand: Process process ID terminated - excessive read errors encountered.

Explanation: During backup processing, read errors occur that prevent the backup from continuing.

System Action: The indicated backup process ends.

User Response: If possible, correct the cause of the read errors and reissue the backup command.

ANR1219ECommand: Process process ID terminated - excessive write errors encountered.

Explanation: During backup processing, write errors occur that prevent the backup from continuing.

System Action: The indicated backup process ends.

User Response: If possible, correct the cause of the write errors and reissue the backup command.

ANR1220ECommand: Process process ID terminated - data transfer interrupted.

Explanation: During backup processing, a data transfer operation was interrupted and could not be continued.

System Action: The indicated backup process ends.

User Response: If possible, correct the cause of the interruption and reissue the backup command.

ANR1221ECommand: Process process ID terminated - insufficient space in target copy storage pool.

Explanation: During backup processing, the server cannot copy data to the copy storage pool because not enough space is available in the copy storage pool.

System Action: The indicated backup process ends.

User Response: Make more space available in the copy storage pool and reissue the backup command, or reissue the backup command and specify another copy storage pool with more space.

ANR1222ECommand: Process process ID terminated - sufficient recovery log space is not available.

Explanation: During backup processing, the server runs out of recovery log space.

System Action: The indicated backup process ends.

User Response: If necessary, make more server recovery log space available.

ANR1223ECommand: Process process ID terminated - sufficient database space is not available.

Explanation: During backup processing, the server runs out of database space.

System Action: The indicated backup process ends.

User Response: If necessary, make more server database space available.

ANR1224ECommand: Process process ID terminated - lock conflict.

Explanation: During backup processing, the server needs to obtain a lock that is not available.

System Action: The indicated backup process ends.

User Response: Reissue the backup command.

ANR1225ECommand: Process process ID terminated - thread resource not available.

Explanation: During backup processing, the server cannot start a thread.

System Action: The indicated backup process ends.

User Response: Reissue the backup command. If the error persists, it may indicate a shortage of server memory.

ANR1226ECommand: Process process ID terminated - sufficient memory is not available.

Explanation: During backup processing, not enough server memory is available.

System Action: The indicated backup process ends.

User Response: If necessary, make more memory available to the server, and then reissue the backup command.

ANR1227ECommand: Process process ID terminated - internal server error detected.

Explanation: During backup processing, the server encounters an internal error.

System Action: The indicated backup process ends.

User Response: Contact your service representative.

ANR1228IRemovable volume volume name is required for storage pool backup.

Explanation: During processing of a BACKUP STGPOOL command, the server determines that a removable volume is required.

System Action: Unless this is a preview process, the server attempts to mount the removable volume.

User Response: Respond to any mount request for the indicated volume.

ANR1229WVolume volume name cannot be backed up - volume is offline or access mode is "unavailable" or "destroyed".

Explanation: During storage pool backup, a volume cannot be backed up either because it has been varied offline or because of the volume's access mode.

System Action: The server continues backup processing, but skips the indicated volume.

User Response: If necessary, use the VARY ON or UPDATE VOLUME command for this volume and restart the backup command.

ANR1230IRestore of primary storage pool primary pool name started as process process ID.

Explanation: A process has been started to restore the indicated primary storage pool.

System Action: Non-cached files that reside in the named primary storage pool are restored if either of the following criteria are met:

User Response: None.

ANR1231IRestore preview of primary storage pool primary pool name started as process process ID.

Explanation: A preview process has been started to restore a primary storage pool.

System Action: Preview information about the restore operation is collected and displayed, but files are not restored. The restore preview includes noncached files that reside in the specified primary storage pool and that meet either of the following conditions:

User Response: None.

ANR1232IRestore of volumes in primary storage pool primary pool name started as process process ID.

Explanation: A process has been started to restore one or more volumes in the indicated primary storage pool.

System Action: Noncached files that reside on selected volumes in the primary storage pool are restored.

User Response: None.

ANR1233IRestore preview of volumes in primary storage pool primary pool name started as process process ID.

Explanation: A preview process has been started to restore one or more volumes in the indicated primary storage pool.

System Action: Preview information about the restore operation is collected and displayed, but files are not restored. The restore preview includes noncached files that reside on selected volumes in the primary storage pool.

User Response: None.

ANR1234IRestore process process ID ended for storage pool storage pool name.

Explanation: A restore process for the named primary storage pool has ended.

System Action: None.

User Response: None.

ANR1235IRestore process process ID ended for volumes in storage pool storage pool name.

Explanation: A restore process for volumes in the named primary storage pool has ended.

System Action: None.

User Response: None.

ANR1236IRestore process process ID terminated for storage pool storage pool name - process canceled.

Explanation: During restore of the indicated primary storage pool, a process performing the restore has been canceled.

System Action: If other restore processes are executing for the named storage pool, these processes continue.

User Response: None.

ANR1237IRestore process process ID terminated for volumes in storage pool storage pool name - process canceled.

Explanation: During restore of volumes in the indicated primary storage pool, a process performing the restore has been canceled.

System Action: If other restore processes are executing for the volumes, these processes continue.

User Response: None.

ANR1238IRestore of primary storage pool primary pool name has ended. Files Restored: number of files, Bytes Restored: number of bytes, Unreadable Files: number of unreadable files, Unreadable Bytes: number of bytes in unreadable files.

Explanation: Restore processing for the specified storage pool has ended with the results shown.

System Action: None.

User Response: Examine previous messages to determine whether all restore processes ended successfully.

ANR1239IRestore preview of primary storage pool primary pool name has ended. Files Restored: number of files, Bytes Restored: number of bytes.

Explanation: Restore preview processing for the specified storage pool has ended with the results shown.

System Action: None.

User Response: None.

ANR1240IRestore of volumes in primary storage pool primary pool name has ended. Files Restored: number of files, Bytes Restored: number of bytes, Unreadable Files: number of unreadable files, Unreadable Bytes: number of bytes in unreadable files.

Explanation: Restore processing for volumes in the specified storage pool has ended with the results shown.

System Action: None.

User Response: Examine previous messages to determine whether all restore processes ended successfully.

ANR1241IRestore preview of volumes in primary storage pool primary pool name has ended. Files Restored: number of files, Bytes Restored: number of bytes.

Explanation: Restore preview processing for volumes in the specified storage pool has ended with the results shown.

System Action: None.

User Response: None.

ANR1242ECommand: Process process ID terminated - storage media inaccessible.

Explanation: During restore processing, a required volume could not be mounted.

System Action: The indicated restore process ends.

User Response: None.

ANR1243ECommand: Process process ID terminated - insufficient number of mount points available for removable media.

Explanation: During restore processing, the server could not allocate sufficient mount points for the volumes required.

System Action: The indicated restore process ends.

User Response: If necessary, make more mount points available.

ANR1244ECommand: Process process ID terminated - excessive read errors encountered.

Explanation: During restore processing, read errors occur that prevent the restore from continuing.

System Action: The indicated restore process ends.

User Response: If possible, correct the cause of the read errors and reissue the restore command.

ANR1245ECommand: Process process ID terminated - excessive write errors encountered.

Explanation: During restore processing, write errors occur that prevent the restore from continuing.

System Action: The indicated restore process ends.

User Response: If possible, correct the cause of the write errors and reissue the restore command.

ANR1246ECommand: Process process ID terminated - data transfer interrupted.

Explanation: During restore processing, a data transfer operation was interrupted and could not be continued.

System Action: The indicated restore process ends.

User Response: If possible, correct the cause of the interruption and reissue the restore command.

ANR1247ECommand: Process process ID terminated - insufficient space in target primary storage pool.

Explanation: During restore processing, the server cannot copy data to the target primary storage pool, because not enough space is available in the target pool.

System Action: The indicated restore process ends.

User Response: Make more space available in the target primary storage pool, and then reissue the restore command.

ANR1248ECommand: Process process ID terminated - sufficient recovery log space is not available.

Explanation: During restore processing, the server runs out of recovery log space.

System Action: The indicated restore process ends.

User Response: If necessary, make more server recovery log space available.

ANR1249ECommand: Process process ID terminated - sufficient database space is not available.

Explanation: During restore processing, the server runs out of database space.

System Action: The indicated restore process ends.

User Response: If necessary, make more server database space available.

ANR1250ECommand: Process process ID terminated - lock conflict.

Explanation: During restore processing, the server needs to obtain a lock that is not available.

System Action: The indicated restore process ends.

User Response: Reissue the restore command.

ANR1251ECommand: Process process ID terminated - thread resource not available.

Explanation: During restore processing, the server cannot start a thread.

System Action: The indicated restore process ends.

User Response: Reissue the restore command. If the error persists, it may indicate a shortage of server memory.

ANR1252ECommand: Process process ID terminated - sufficient memory is not available.

Explanation: During restore processing, there is not enough server memory available.

System Action: The indicated restore process ends.

User Response: If necessary, make more memory available to the server; and then reissue the restore command.

ANR1253ECommand: Process process ID terminated - internal server error detected.

Explanation: During restore processing, the server encounters an internal error.

System Action: The indicated restore process ends.

User Response: Contact your service representative.

ANR1254IRemovable volume volume name is required for restore processing.

Explanation: During processing of a RESTORE STGPOOL or RESTORE VOLUME command, the server determines that a removable volume is required.

System Action: Unless this is a preview process, the server attempts to mount the removable volume.

User Response: Respond to any mount request for the indicated volume.

ANR1255WFiles on volume volume name cannot be restored - access mode is "unavailable" or "offsite".

Explanation: During processing of a RESTORE STGPOOL or RESTORE VOLUME command, files on a copy storage pool volume cannot be restored because of the volume's access mode.

System Action: The server continues restore processing, but skips the indicated volume.

User Response: If the volume is stored at an offsite location, bring the volume onsite. Use the UPDATE VOLUME command to change the access mode for the volume and restart the restore command.

ANR1256WVolume volume name contains files that could not be restored.

Explanation: During processing of a RESTORE STGPOOL or RESTORE VOLUME command, the server determines that the indicated volume contains one or more files that could not be restored. If this is a preview operation, this message indicates that a restorable backup copy cannot be found for one or more files on the indicated volume. If this is an actual restore operation, this message could result if any of the following conditions exist for a file on the indicated volume:

System Action: None.

User Response: If this was an actual restore operation, check for messages indicating that files could not be restored because a copy storage pool volume was unavailable or offsite. Check to see if a move data, delete volume, audit volume, or reclamation process occurred for a copy storage pool while the restore was in progress. If either of these conditions existed, correct the situation and reissue the restore command.

ANR1257WStorage pool backup skipping damaged file on volume volume name: Node node name, Type file type, File space filespace name, File name file name.

Explanation: During storage pool backup, a file is encountered that was previously found to be damaged. If this file is part of an aggregate, the entire aggregate was previously marked damaged, possibly because an integrity error was detected for some other file within the aggregate.

System Action: The damaged file will not be backed up.

User Response: Audit the indicated volume with FIX=NO to verify that the file is damaged. The audit will reset the file status if the file is found to be undamaged during the audit. If the file is part of an aggregate, the audit will reset the aggregate status if the entire aggregate is found to be undamaged. If this file has previously been backed up to a copy storage pool, you can also attempt to restore damaged files using the RESTORE STGPOOL command.

ANR1258WFiles on volume volume name needed for move data cannot be accessed - access mode is "unavailable" or "offsite".

Explanation: During a move data operation on an offsite volume, files on a storage pool volume cannot be copied because of the volume's access mode.

System Action: The server continues move data processing, but one or more files were not moved from the offsite volume.

User Response: If the specified volume can be made available, use the UPDATE VOLUME command to change the access mode for the volume and reissue the MOVE DATA command.

ANR1259WFiles on volume volume name needed for offsite reclamation cannot be accessed - access mode is "unavailable" or "offsite".

Explanation: During reclamation processing of an offsite volume, files on a storage pool volume cannot be copied because of the volume's access mode.

System Action: The server continues reclamation, but one or more files were not moved from an offsite volume, which prevents it from being reclaimed.

User Response: If the specified volume can be made available, use the UPDATE VOLUME command to change the access mode for the volume and initiate reclamation again by updating the reclamation threshold for the copy storage pool.

ANR1260WVolume volume name contains one or more damaged, primary files.

Explanation: This message is issued during RESTORE STGPOOL processing. The indicated volume contains one or more primary, noncached files that have previously been found to be damaged.

System Action: If this is not a preview operation, the restore processing attempts to restore the damaged files from copies located in a copy storage pool. If this is a preview operation, no system action is taken.

User Response: You can take the following actions:

ANR1263Icommand: Processing completed successfully.

Explanation: The background process to service the command command has completed successfully.

System Action: Processing for the command completes. Statistics on the number and type of objects moved, together with the total number of bytes copied, are displayed on the server console following this message.

User Response: None.

ANR1264ICommand: Processing canceled before completion.

Explanation: The background process to service the command command has been canceled with the CANCEL PROCESS command.

System Action: Processing for the command command ends. Statistics on the number and type of objects moved, together with the total number of bytes copied, are displayed on the server console following this message.

User Response: None.

ANR1265ESalvage volume command: Processing terminated abnormally - error accessing data storage.

Explanation: The server encountered an internal error in accessing data storage while executing a salvage volume operation.

System Action: The operation is ended and server operation continues.

User Response: Use the QUERY ACTLOG command to examine messages prior to this error to determine the cause of the data storage failure. If you find and resolve the error, retry the operation. If you cannot find the error, contact your service representative for assistance in resolving the problem.

ANR1266ESalvage volume command: Processing terminated abnormally - volume not a storage pool volume.

Explanation: The server encountered an internal error in accessing data storage while executing a salvage volume operation.The error occurred because an attempt has been made to access a volume that was not a storage pool volume.

System Action: The command command operation is ended and server operation continues.

User Response: Issue the command with a valid volume name.

ANR1267ISalvage volume command: Processed number volume(s).

Explanation: The background process to service the command Salvage volume command inspected number input volumes.

System Action: Salvage processing for the command completes. Server operation continues.

User Response: None.

ANR1268ISalvage volume command: Recovered number byte(s).

Explanation: The background process to service the command Salvage volume command recovered number bytes worth of data.

System Action: Salvage processing for the command completes. Server operation continues.

User Response: None.

ANR1269ISalvage volume command: Recovered number file(s).

Explanation: The background process to service the command Salvage volume command recovered number files.

System Action: Salvage processing for the command completes. Server operation continues.

User Response: None.

ANR1270ISalvage volume command: File (internal file identifierinternal file identifier) recovered.

Explanation: The background process to service the command Salvage volume command recovered a file. The new file was given a new, system generated name based on the internal file identifier and the name of the volume from which the file was recovered. The internal file identifier is the identifier by which the file was known to the server before the file was deleted.

System Action: Salvage processing for the command completes. Server operation continues.

User Response: None.

ANR1271ISalvage volume command: * number bytes recovered from volume volume.

Explanation: The background process to service the command Salvage volume command recovered a file from the volume volume. The number of bytes recovered from the volume is listed.

System Action: Salvage processing for the command completes. Server operation continues.

User Response: None.

ANR1272ISalvage volume command: * File is complete -- it began and ended on volume volume.

Explanation: The background process to service the command Salvage volume command recovered a file from the volume volume. The file was completely contained on volume.

System Action: Salvage processing for the command completes. Server operation continues.

User Response: None.

ANR1273ISalvage volume command: * File is incomplete -- it began on volume volume but did not end.

Explanation: The background process to service the command Salvage volume command recovered a file from the volume volume. The file was not completely contained on volume. Although the file began on this volume, it spanned out to a different volume.

System Action: Salvage processing for the command completes. Server operation continues.

User Response: None.

ANR1274ISalvage volume command: * File is incomplete -- it ended on volume volume but did not begin there.

Explanation: The background process to service the command Salvage volume command recovered a file from the volume volume. The file was not completely contained on volume. Although the file ended on this volume, it spanned in from a different volume.

System Action: Salvage processing for the command completes. Server operation continues.

User Response: None.

ANR1275ISalvage volume command: * File is incomplete -- it did not began or end on volume volume.

Explanation: The background process to service the command Salvage volume command recovered a file from the volume volume. The file was not completely contained on volume. It spanned in from one volume and spanned out to a another.

System Action: Salvage processing for the command completes. Server operation continues.

User Response: None.

ANR1276ECommand: Process terminated - sufficient memory is not available.

Explanation: During salvage processing, not enough server memory is available.

System Action: The salvage process ends.

User Response: If necessary, make more memory available to the server, and then reissue the salvage command.

ANR1277ECommand: Process terminated - the default management class in the active policy set in policy domain domain name does not contain an archive copy group. Unable to continue with salvage.

Explanation: The background process to service the command Salvage volume command was unable to recover any files because the default management class in the active policy set in policy domain does not contain an archive copy group.

System Action: The salvage process ends.

User Response: Add an archive copy group to the default management class in the active policy set of the specified domain, and then reissue the salvage command.

ANR1278IOccupancy is incorrect for storage pool storage pool name. Occupancy is being reset.

Explanation: The server has detected incorrect occupancy information.

System Action: The server recalculates the occupancy value based on current storage pool information.

User Response: None.

ANR1279IOccupancy is incorrect for volume name volume name. Occupancy is being reset.

Explanation: The server has detected incorrect occupancy information.

System Action: The server recalculates the occupancy value based on current sequential volume information.

User Response: None.

ANR1280ECommand: Process process ID terminated - transaction aborted.

Explanation: During backup processing, the server detected an error while attempting to commit a transaction. This message should be preceded by other messages that give additional information about the failed transaction.

System Action: The indicated backup process ends.

User Response: Check for additional messages and eliminate the condition that caused the failed transaction.

ANR1281ECommand: Process process ID terminated - transaction aborted.

Explanation: During restore processing, the server detected an error while attempting to commit a transaction. This message should be preceded by other messages that give additional information about the failed transaction.

System Action: The indicated restore process ends.

User Response: Check for additional messages and eliminate the condition that caused the failed transaction.

ANR1282ILogical occupancy is incorrect for storage pool storage pool name. Logical occupancy is being reset.

Explanation: The server has detected incorrect logical occupancy information.

System Action: The server recalculates the logical occupancy value based on current storage pool information.

User Response: None.

ANR1283IFile count is incorrect for storage pool storage pool name - file count is being reset.

Explanation: The server has detected an incorrect count of the number of files within this storage pool.

System Action: The server will correct this information.

User Response: None.

ANR1300IVARY ONLINE command initiated for disk volume volume name.

Explanation: A VARY ONLINE command has caused a vary-on process to be started for the volume specified.

System Action: The volume is varied online.

User Response: None.

ANR1301IVARY OFFLINE command initiated for disk volume volume name.

Explanation: A VARY OFFLINE command has caused a vary-off process to be started for the volume specified.

System Action: The volume is varied offline.

User Response: None.

ANR1302EDisk volume volume name is already online.

Explanation: A VARY ONLINE command specified a volume that was already online.

System Action: None.

User Response: None.

ANR1303EDisk volume volume name is already offline.

Explanation: A VARY OFFLINE command specified a volume that was already offline.

System Action: None.

User Response: None.

ANR1304EDisk volume volume name is currently in use.

Explanation: A VARY OFFLINE command specified a volume that is currently in use and cannot be varied offline at this time.

System Action: None.

User Response: Try the command again at a later time, or attempt to determine how it is currently being used and free it.

ANR1305IDisk volume volume name varied online.

Explanation: The specified volume has been varied online as the result of a VARY ONLINE command.

System Action: None.

User Response: None.

ANR1306IDisk volume volume name varied online (read-only).

Explanation: The specified volume has been varied online in read-only mode as the result of a VARY ONLINE command.

System Action: None.

User Response: None.

ANR1307IDisk volume volume name varied offline.

Explanation: The specified volume has been varied offline as the result of a VARY OFFLINE command.

System Action: None.

User Response: None.

ANR1310EVary-on failed for disk volume volume name - insufficient memory.

Explanation: A VARY ONLINE command has been issued for the disk volume specified, but sufficient memory is not available to process the command.

System Action: The volume is not varied online.

User Response: Reissue the command at a later time, or make more memory available to the server.

ANR1311EVary-on failed for disk volume volume name - unable to access disk device.

Explanation: A VARY ONLINE command has been issued for the disk volume specified, but the server is unable to access the disk.

System Action: The volume is not varied online.

User Response: Attempt to determine the cause of the inability to access the volume and correct the problem.

ANR1312EVary-on failed for disk volume volume name - error reading disk.

Explanation: A VARY ONLINE command has been issued for the disk volume specified but the server encounters an error reading the disk.

System Action: The volume is not varied online.

User Response: Attempt to determine the cause of the read error and correct the problem.

ANR1313EVary-on failed for disk volume volume name - unsupported block size (block size).

Explanation: A VARY ONLINE command has been issued for the disk volume specified, but the volume is formatted with a block size that cannot be used.

System Action: The volume is not varied online.

User Response: Reformat the disk with a block size that is an evenly divisible by 4096.

ANR1314EVary-on failed for disk volume volume name - reduced capacity (was count blocks, now count blocks.

Explanation: A VARY ONLINE command has been issued for the disk volume specified, but the size of the volume does not match the size expected.

System Action: The volume is not varied online.

User Response: Restore the volume or otherwise correct the disk volume size, and reissue the command.

ANR1315EVary-on failed for disk volume volume name - invalid label block.

Explanation: A VARY ONLINE command has been issued for the disk volume specified, but the label block of the volume is invalid or cannot be read.

System Action: The volume is not varied online.

User Response: Restore or reformat the disk volume.

ANR1316EVary-on failed for disk volume volume name - internal error detected.

Explanation: A VARY ONLINE command has been issued for the disk volume specified, but fails due to an internal server error.

System Action: The volume is not varied online.

User Response: Contact your service representative.

ANR1320WVary-on not possible for disk volume volume name - access state is "unavailable".

Explanation: A VARY ONLINE command has been issued for the disk volume specified, but the status of the volume is unavailable.

System Action: The volume is not varied online.

User Response: If necessary, use the UPDATE VOLUME command to change the status of the volume, and reissue the command.

ANR1321WVary-on not possible for disk volume volume name - access state is "destroyed".

Explanation: A VARY ONLINE command has been issued for the disk volume specified, but the status of the volume is destroyed.

System Action: The volume is not varied online.

User Response: If necessary, use the UPDATE VOLUME command to change the status of the volume, and reissue the command.

ANR1340IScratch volume volume name is now defined in storage pool storage pool name.

Explanation: The scratch volume specified has been added to the storage pool shown.

System Action: None.

User Response: None.

ANR1341IScratch volume volume name has been deleted from storage pool storage pool name.

Explanation: The scratch volume specified is no longer in use and has been removed from the indicated storage pool.

System Action: None.

User Response: None.

ANR1342IScratch volume volume name is now pending - volume will be deleted from storage pool storage pool name after the reuse delay period for this storage pool has elapsed.

Explanation: All files have been deleted from the indicated scratch volume. The volume will not be removed from the storage pool until the reuse delay time period for the indicated storage pool has elapsed. If the storage pool does not have a reuse delay specified, the indicated volume was emptied after it had been requested by another process. It will be in the full or filling state if the process places more data on the tape, or it will be removed from the storage pool after it is no longer required.

System Action: None.

User Response: None.

ANR1343IUnable to delete scratch volume volume name.

Explanation: A scratch volume cannot be deleted from the server and returned to scratch at this time because all the locks have not be released. A number of retries have been attempted.

System Action: None

User Response: The scratch volume will be automatically deleted when the server is restarted. Or, you may manually delete this volume later, using the DELETE VOLUME command.

ANR1344IVolume volume name cannot be reused, remove from server storage.

Explanation: A volume that was full and is now empty cannot be reused by the server due to the WORM (Write Once - Read Many) characteristics of the media.

System Action: The volume will have a state where the access mode is READONLY, the status is FULL and the percent utilized is 0.0. The volume is considered empty for storage pool occupancy and utilization fields.

User Response: If the volume is in a library, it must first be removed using the CHECKOUT LIBVOLUME command prior to manually deleting the volume. Use the DELETE VOLUME command to remove the volume from server storage.

ANR1360IOutput volume volume name opened (sequence number sequence number).

Explanation: During a sequential data operation, the volume specified has been opened for output as the volume number shown.

System Action: None.

User Response: None.

ANR1361IOutput volume volume name closed.

Explanation: During a sequential data operation, the volume specified has been closed because the export or dump is complete.

System Action: None.

User Response: None.

ANR1362IOutput volume volume name closed (full).

Explanation: During a sequential data operation, the volume specified has been closed because the volume is full.

System Action: None.

User Response: None.

ANR1363IInput volume volume name opened (sequence number sequence number).

Explanation: Because of a sequential data operation, the volume specified has been opened for input as the volume number shown.

System Action: None.

User Response: None.

ANR1364IInput volume volume name closed.

Explanation: During a sequential data operation, the volume specified has been closed because the operation is complete.

System Action: None.

User Response: None.

ANR1365IVolume volume name closed (end reached).

Explanation: During a sequential data operation, the volume specified has been closed because processing of the volume is complete.

System Action: None.

User Response: None.

ANR1366WInput volume volume name contains an invalid identifier.

Explanation: During a sequential data operation, the volume specified has been mounted but contains an invalid identifier.

System Action: The volume is not used.

User Response: Make sure you specified the correct volume for the operation. If a LOADDB operation was being performed on MVS, the command syntax may be specified by using a ddname or by specifying a device class name. You must use the same method that was used when the data base was originally dumped. If you did not, this error message will be displayed. Try loading the data base by using the other method of syntax (ddname).

ANR1367WImport volume volume name was written by a different export process.

Explanation: During an IMPORT operation, the volume specified has been mounted but contains an export identifier that does not match the import process.

System Action: The volume is not used.

User Response: Supply a volume created by the proper export process.

ANR1368WInput volume volume name contains sequence number sequence number; volume sequence number sequence number is required.

Explanation: During a sequential data operation, the volume specified has been mounted but contains the wrong volume sequence number.

System Action: The volume is not used.

User Response: Supply the volume with the proper sequence number. The volume history file can help you choose the correct volume.

ANR1369EInput volume volume name contains Version 1 dump.

Explanation: During a sequential data operation, the volume specified has been mounted but appears to contain a version 1 data base dump.

System Action: The volume is not used. The operation is terminated.

User Response: Make sure you specified the correct volume for the operation. A Version 1 database dump may not be loaded into a Version 2 server. The Version 1 database dump must only be loaded into a Version 1 server.

ANR1370EInsufficient number of mount points available in device class device class name.

Explanation: During IMPORT or EXPORT processing, the server cannot allocate sufficient mount points for the device class specified. The device class associated with the EXPORT or IMPORT drive only has a mount limit of one. The operation needs to read or write file data from or to the same device class because file data is being imported or exported.

System Action: The IMPORT or EXPORT command is ended and server operation continues.

User Response: Make more mount points available.

ANR1400WMount request denied for volume volume name - mount canceled.

Explanation: The volume shown cannot be mounted because the mount request has been canceled.

System Action: The volume is not mounted.

User Response: None.

ANR1401WMount request denied for volume volume name - mount failed.

Explanation: The volume shown cannot be mounted because the mount request cannot be completed successfully. Possible reasons include, an error in device specifications to the server or the mount request timed out.

System Action: The volume is not mounted.

User Response: If the device specifications (DEFINE DEVCLASS and so forth) are in error, correct them and reissue the command that requested the volume to be mounted.

ANR1402WMount request denied for volume volume name - volume unavailable.

Explanation: The volume shown cannot be mounted because it is not available.

System Action: The volume is not mounted.

User Response: None.

ANR1403WScratch volume mount request denied - mount canceled.

Explanation: A scratch volume cannot be mounted because the mount request has been canceled.

System Action: The scratch volume is not mounted.

User Response: None.

ANR1404WScratch volume mount request denied - mount failed.

Explanation: A scratch volume cannot be mounted because the mount request cannot be completed successfully. Possible reasons include, an error in device specifications to the server or the mount request timed out.

System Action: The scratch volume is not mounted.

User Response: If the device specifications (for example, DEFINE DEVCLASS) are in error, correct them and reissue the command that requested the volume to be mounted.

ANR1405WScratch volume mount request denied - no scratch volume available.

Explanation: A scratch volume cannot be mounted because no scratch volume is available.

System Action: The scratch volume is not mounted.

User Response: None.

ANR1409WVolume command already in use - skipped.

Explanation: During an export or database backup, a volume cannot be used because it is already defined in a storage pool, or has been previously used by an export or database backup operation (as recorded in the volume history) or is in use by another process.

System Action: The operation continues and the volume is skipped.

User Response: Use the QUERY VOLUME command to display the names of volumes that are defined to server storage pools. Use the QUERY VOLHISTORY command to display the names of volumes that have been used for export or database backup operations.

ANR1410WAccess mode for volume volume name now set to "unavailable".

Explanation: The status of the volume shown has been set to unavailable.

System Action: None.

User Response: None.

ANR1411WAccess mode for volume volume name now set to "read-only" due to write error.

Explanation: Because of an unrecoverable write error on the volume shown, the status of the volume has been set to read-only.

System Action: None.

User Response: None.

ANR1412WVolume volume name access mode is "unavailable".

Explanation: At server startup, the status of the indicated volume is unavailable.

System Action: None.

User Response: None.

ANR1413WVolume volume name access mode is "read-only".

Explanation: At server startup, the status of the indicated volume is read-only.

System Action: None.

User Response: None.

ANR1414WVolume volume name access mode is "read-only" due to previous write error.

Explanation: At server startup, the status of the indicated volume is read-only due to an unrecoverable write error, or because an administrator used the UPDATE VOLUME command to set the volume access mode to read-only.

System Action: None.

User Response: None.

ANR1415WVolume volume name access mode is "destroyed".

Explanation: At server startup, the status of the indicated volume is destroyed.

System Action: None.

User Response: None.

ANR1416WVolume volume name access mode is "offsite".

Explanation: At server startup, the status of the indicated volume is offsite.

System Action: None.

User Response: None.

ANR1417WAccess mode for volume volume name now set to "read-only" due to excessive read error.

Explanation: Because of an numerous read errors on the volume shown, the status of the volume has been set to read-only.

System Action: None.

User Response: Use QUERY VOLUME FORMAT=DETAILED for the volume to view the access mode and number of read errors. You may want to use the MOVE DATA command to move the retrievable data from this volume to another volume. For the damaged files, use the RESTORE VOLUME command to restore a readable copy of the file to the storage pool.

ANR1420WRead access denied for volume volume name - volume access mode = "unavailable".

Explanation: An attempt to access the named volume for reading fails because the volume status is unavailable.

System Action: The volume is not used for read access.

User Response: None.

ANR1421WRead access denied for volume volume name - volume offline.

Explanation: An attempt to access the named volume for reading failed because the volume is offline.

System Action: The volume is not used.

User Response: None.

ANR1422WRead access denied for volume volume name - volume access mode = "offsite".

Explanation: An attempt to access the named volume for reading failed because the volume status is offsite.

System Action: The volume is not used for read access.

User Response: None.

ANR1423WScratch volume volume name is empty but will not be deleted - volume access mode is "offsite".

Explanation: The named scratch volume is empty but will not be deleted at this time because the access mode is offsite.

System Action: The volume is not deleted.

User Response: After bringing the volume onsite, change the access mode to read-only so the volume will be deleted.

ANR1424WRead access denied for volume volume name - volume access mode = "destroyed".

Explanation: An attempt to access the named volume for reading failed because the volume status is destroyed.

System Action: The volume is not used for read access.

User Response: None.

ANR1425WScratch volume volume name is empty but will not be deleted - volume state is "mountablenotinlib".

Explanation: The named scratch volume is empty but will not be deleted at this time because the state of the volume is MOUNTABLENOTINLIB.

System Action: The volume is not deleted.

User Response: When the volume is moved by MOVE MEDIA WHERESTATE=MOUNTABLENOTINLIB, the scratch empty volume is deleted.

ANR1430WRetrieval request denied for storage pool storage pool name - access mode = "unavailable".

Explanation: An attempt was made to retrieve a file from the storage pool shown, but the access mode of the storage pool is unavailable.

System Action: The file is not retrieved from this storage pool. If possible, the file is retrieved from another storage pool.

User Response: Consider changing the access mode for the storage pool.

ANR1431EAn error occurred while writing to side A of volume volume name. An attempt will be made to write to side B of this volume.

Explanation: An error occurred while writing to side A of a two-sided volume.

System Action: No additional data will be written to side A of this volume. Any remaining space on side A will not be used. An attempt will be made to use the reverse side (side B) of the volume.

User Response: None required if the side B can be used successfully. However, the administrator should investigate the cause of the error and may want to move data from this volume.

ANR1432IUpdating device configuration information to defined files.

Explanation: The server is updating device configuration information for the files or data sets specified with the DEVCONFIG option in the server options file.

System Action: Server operation continues.

User Response: None.

ANR1433IDevice configuration information successfully written to file name.

Explanation: Device configuration information was successfully written to the file specified.

System Action: Server operation continues.

User Response: None.

ANR1434WNo files have been identified for automatically storing device configuration information.

Explanation: The server is unable to automatically update device configuration file. No files were identified using the DEVCONFIG option in the server options file.

System Action: Server operation continues.

User Response: If you would like to have the server automatically record device configuration information to assist in server recovery, use the DEVCONFIG option in the server options file to specify where device configuration information should be written. If you update the options file, halt and then restart the server so the changes can take effect.

ANR1435EServer could not write device configuration information to devconfig file name.

Explanation: While attempting to write device configuration information to defined files, the server cannot write to the file name specified.

System Action: The server cannot write device configuration information to the specified file.

User Response: Examine error messages that may have been displayed prior to this message and correct any problems, if possible. Make sure that the server has proper authority to write to the file indicated and that there is sufficient space in the file system for the file. On MVS, make sure that the data set has been allocated and that the server has authority to write to the data set. After the problem has been corrected, use the BACKUP DEVCONFIG command to write device configuration information to the file.

ANR1436EDevice configuration file devconfig file name cannot be opened.

Explanation: While attempting to write device configuration information to device configuration files, the server cannot open the file name specified.

System Action: The server does not write device configuration information to the file specified.

User Response: Examine error messages that may have been displayed prior to this message and correct any problems, if possible. Make sure that the server has proper authority to write to the file indicated and that there is sufficient space in the file system for the file. On MVS, make sure that the data set has been allocated and that the server has authority to write to the data set. After the problem has been corrected, use the BACKUP DEVCONFIG command to write device configuration information to the file.

ANR1437ENo device configuration files could be used.

Explanation: The server attempts to read device configuration information from defined files and cannot open any of the files.

System Action: The operation is ended.

User Response: Examine error messages that may have been displayed prior to this message and correct any problems, if possible. Ensure that the defined device configuration files have been created. If you can start the server, you can create the files by using the BACKUP DEVCONFIG command. If you cannot start the server, you will need to create a device configuration file by editing the file and adding the appropriate DEFINE commands for the device class, drive, and library definitions. The contents and requirements for this file are described in the Administrator's Guide. Make sure that the server has proper authority to read from the defined device configuration files.

ANR1438WSkipping device configuration file: devconfig file name.

Explanation: While attempting to read device configuration information from a defined device configuration file, the server encounters problems in processing the definitions included in the file.

System Action: The specified file is skipped, and the next one specified in the server options file will be used.

User Response: Examine error messages that may have been displayed prior to this message to understand why the file could not be used. When you can start the server again, you can refresh this file by using the BACKUP DEVCONFIG command.

ANR1439EAllocate prohibited - transaction failed.

Explanation: While attempting to preallocate storage on a storage pool, the server detected that the transaction for this operation has previously failed. This error may occur when a large file is selected for backup and the client did not properly estimate the file size. There may not be enough space in the storage pool for the file.

System Action: An internal error is reported by the server and the operation being performed is ended.

User Response: Examine error messages that may have been displayed prior to this message for more information.

ANR1440IAll drives in use. Process process number being preempted by higher priority operation.

Explanation: When a high priority operation attempted to find an available drive, all the drives were in use. To make a drive available for this operation, the indicated process is being cancelled by the system.

System Action: The lower priority process is cancelled to make a mount point (drive) available.

User Response: When a drive again becomes available, restart the process that was cancelled. If the process was a migration or reclamation process, it will be automatically restarted when needed. If this message appears frequently, you may want to increase the number of drives available. See the MOUNTLIMIT parameter on the UPDATE DEVCLASS command.

ANR1441IVolume volume name is in use. Process process number being preempted by higher priority operation.

Explanation: When a high priority operation attempted to use a volume, it was in use. To make a volume available for this operation, the indicated process is being cancelled by the system.

System Action: The lower priority process is cancelled to the volume available.

User Response: Restart the process that was cancelled. It will wait until the higher priority process is finished with the volume. If the cancelled process was a migration or reclamation process, it will be automatically restarted when needed.

ANR1450Ecommand name: Invalid command script name: command script name.

Explanation: An invalid script name was specified for a DEFINE, UPDATE, or DELETE SCRIPT command.

System Action: The operation fails.

User Response: Reenter the command specifying a valid command name.

ANR1451Ecommand name: Invalid command: command.

Explanation: An invalid command was specified for a DEFINE, UPDATE, or DELETE SCRIPT command.

System Action: The operation fails.

User Response: Reenter the command specifying a valid server command.

ANR1452Ecommand name: Invalid line number: line number.

Explanation: An invalid line number was specified for a DEFINE, UPDATE, or DELETE SCRIPT command.

System Action: The operation fails.

User Response: Reenter the command specifying a valid line number.

ANR1453Ecommand name: Command script command script name already exists.

Explanation: The script name specified in a DEFINE SCRIPT command already exists.

System Action: The operation fails.

User Response: Reenter the command specifying a different command name.

ANR1454Icommand name: Command script command script name defined.

Explanation: The script name specified in a DEFINE SCRIPT command was successfully defined.

System Action: None

User Response: None

ANR1455Ecommand name: Command script command script name does not exist.

Explanation: The script name specified in a DEFINE, UPDATE, or DELETE SCRIPT command does not exist.

System Action: The operation fails.

User Response: Reenter the command specifying a different command name.

ANR1456Icommand name: Command script command script name updated.

Explanation: The script name specified in an UPDATE SCRIPT command was successfully updated.

System Action: None

User Response: None

ANR1457Icommand name: Command script command script name deleted.

Explanation: The script name specified in a DELETE COMMAND command was successfully deleted.

System Action: None

User Response: None

ANR1458Icommand name: Line line number was deleted from command script command script name.

Explanation: The specified line number was deleted from the command script as a result of a DELETE SCRIPT command.

System Action: None

User Response: None

ANR1459Ecommand name: Command script command script name, line line number does not exist.

Explanation: The line in command script name specified in a UPDATE, or DELETE SCRIPT command does not exist.

System Action: The operation fails.

User Response: Reenter the command specifying a different line number.

ANR1460Icommand name: Command script command script name copied to new command script name.

Explanation: The specified command script was copied to a new script with the COPY SCRIPT command.

System Action: None

User Response: None

ANR1461Icommand name: Executing command script command script name.

Explanation: The specified command script is being executed as a result of a RUN command.

System Action: None

User Response: None

ANR1462Icommand name: Command script command script name completed successfully.

Explanation: The specified command script, started with a RUN command, has successfully completed.

System Action: None

User Response: None

ANR1463Ecommand name: Command script command script name completed in error.

Explanation: The specified command script, started with a RUN command, encountered errors.

System Action: Part or all of the command lines in the script ended in error. Command processing is terminated.

User Response: Examine the messages preceeding this message to determine the cause of the error. Correct the command script and reissue the command.

ANR1464Ecommand name: Command script command script name, line line number, parameter parameter number was not specified: command line.

Explanation: All parameters required to execute a command script were not specified in the RUN command.

System Action: The command fails.

User Response: Reenter the RUN command specifying all required parameters.

ANR1465Ecommand name: Command script command script name, line line number, parameter is invalid: command line.

Explanation: An invalid parameter was encountered in a command script.

System Action: The command fails.

User Response: Correct the script definition and reexecute the RUN command.

ANR1466Icommand name: Command script command script name, Line line number : command line.

Explanation: The specified line for the command script is being executed. The contects of the line being executed are displayed.

System Action: None

User Response: None

ANR1467Ecommand name: Command script command script name, did not end in a non-continued line command line.

Explanation: The specified command script did not end in a line that had no continuation character (-).

System Action: The command fails.

User Response: Correct the specified script so that it ends in a line that is not continued to the next line.

ANR1468Ecommand name: Command script command script name, continued line is too long

Explanation: The specified command script with continuation lines is too long to be executed.

System Action: The command fails.

User Response: Correct the specified command script so that it is shorter.

ANR1469Ecommand name: Command script command script name, Line line number is an INVALID command : command line.

Explanation: The specified line for the command script is not a valid server command. This message is displayed when a RUN command is executed with the PREVIEW=YES parameter specified.

System Action: Command Preview processing fails

User Response: Correct the script and reenter the RUN command.

ANR1470Icommand name: Command script command script name completed successfully (PREVIEW mode).

Explanation: The specified command script, started with a RUN command, has successfully completed.

System Action: None.

User Response: None.

ANR1471Ecommand name: Command script command script name completed in error (PREVIEW mode).

Explanation: The specified command script, started with a RUN command, encountered errors.

System Action: Part or all of the command lines in the command script ended in error. Command processing is terminated.

User Response: Examine the messages preceeding this message to determine the cause of the error. Correct the script and reissue the command.

ANR1472Icommand name: Command script command script name renamed to new command script name.

Explanation: The specified command script was renamed with the RENAME SCRIPT command.

System Action: None.

User Response: None.

ANR1473Ecommand name: A command line cannot be specified when the FILE= parameter is used.

Explanation: The FILE= parameter was specified in the DEFINE SCRIPT command AND a command line was also specified for the SCRIPT. When the FILE= parameter is specified, a command line cannot be specified.

System Action: The command fails.

User Response: Reenter the command without the command line OR the FILE= parameter.

ANR1474Ecommand name: A line number cannot be specified when the FILE= parameter is used.

Explanation: The FILE= parameter was specified in the DEFINE SCRIPT command AND a line number was also specified for the SCRIPT. When the FILE= parameter is specified, a line number cannot be specified.

System Action: The command fails.

User Response: Reenter the command without the line number OR the FILE= parameter.

ANR1475Ecommand name: File file name could not be opened.

Explanation: A filename was specified in a command but the specified file could not be opened by the server.

System Action: The command fails.

User Response: Examine any messages that might appear prior to this one in the activity log to determine if the error can be found. If the file was to exist for use by the command, ensure that the file does exists and that the server has proper authority to access the file. If the file was to be created by the command, ensure that the filesystem has sufficient space and that the server has authority to create the file in the location specified.

ANR1476Ecommand name: File file name contains no data.

Explanation: The FILE= parameter was specified in a command but the specified file did not contain script command lines.

System Action: The command fails.

User Response: Add script command lines to the file or specify another file and reenter the command.

ANR1477Ecommand name: The OUTPUTFILE parameter may only be specified when FORMAT=RAW or FORMAT=MACRO is specified.

Explanation: The OUTPUTFILE parameter was specified in a QUERY SCRIPT command but the FORMAT parameter did not specify RAW or MACRO output. When outputting the QUERY to a file, you MUST specify RAW or MACRO output format.

System Action: The command fails.

User Response: Reenter the command specifyingthe proper value for the FORMAT parameter or do not specify the OUTPUTFILE parameter.

ANR1478Ecommand name: Error writing to file file name.

Explanation: An error was encountered while writing to the file specified.

System Action: The command fails.

User Response: Examine any messages that might appear prior to this one in the activity log to determine if the error can be found. Ensure that the filesystem has sufficient space and that the server has authority to create the file in the location specified.

ANR1479Icommand name: Query output was written to file file name.

Explanation: The output from the specified query was successfully written to the specified file.

System Action: The command completes successfully.

User Response: None.

ANR1480Ecommand name: Description text is too long.

Explanation: The specified description text is too long for a command that allows description text to be specified.

System Action: The command fails.

User Response: Reenter the command specifying a shorter description.

ANR1481Ecommand name: A command line or description must be specified.

Explanation: An UPDATE SCRIPT command was specified with out a command line (script line) or description text.

System Action: The command fails.

User Response: Reenter the command specifying a command line or description text.

ANR1482Icommand name: Found label statement label on line line number and continuing.

Explanation: This message is issued during a RUN command (VERBOSE=YES) to indicate that the target label for a GOTO statement was found.

System Action: Command processing continues.

User Response: None.

ANR1483Icommand name: Line line number condition IF(condition) is NOT true - statement is skipped.

Explanation: This message is issued during a RUN command (VERBOSE=YES) to indicate that the a return code condition check failed and the IF(..) statement is skipped.

System Action: Command processing continues.

User Response: None.

ANR1484Icommand name: Line line number condition IF(condition) is TRUE - statement will be executed.

Explanation: This message is issued during a RUN command (VERBOSE=YES) to indicate that the a return code condition check succeeded and the IF(..) statement is executed.

System Action: Command processing continues.

User Response: None.

ANR1485Icommand name: Ending SCRIPT with EXIT statement on line line number.

Explanation: This message is issued during a RUN command (VERBOSE=YES) to indicate that an EXIT statement was encountered and SCRIPT termination will end.

System Action: The SCRIPT command ends.

User Response: None.

ANR1486Icommand name: Executing line line number GOTO label name.

Explanation: This message is issued during a RUN command (VERBOSE=YES) to indicate that a GOTO statment was encountered and processing will skip to the named label.

System Action: SCRIPT processing continues.

User Response: None.

ANR1487Icommand name: Command return code is symbolic return code (return code severity).

Explanation: This message is issued during a RUN command (VERBOSE=YES) to indicate the return code that was returned from the latest command.

System Action: SCRIPT processing continues.

User Response: None.

ANR1488Ecommand name: Line line number condition IF(condition) is not a valid condition.

Explanation: This message is issued if an IF() statment in a SCRIPT does not specify proper condition values.

System Action: Command processing fails.

User Response: Reenter the command using valid conditions for the IF() statement.

ANR1489Ecommand name: Line line number is a GOTO to a label (label name) that does not exist or is associated with a line prior to line line number.

Explanation: This message is issued if a GOTO statment in a SCRIPT does not specify a label that exists in the SCRIPT, or that does exist but is associated with a line prior to the line that contains the GOTO statement.

System Action: Command processing fails.

User Response: Correct the SCRIPT definition and reenter the RUN command.

ANR1490Wcommand name: Command script command script name does not contain any commands.

Explanation: The script name specified in a RUN command does not contain any commands.

System Action: The RUN operation fails (has nothing to do).

User Response: Server command Scripts that contain no commands will not execute. Add command lines to the Script and re-enter the RUN command.

ANR1491EServer command scripts cannot be started from the server console.

Explanation: A server command script RUN command was issued from the server console. Server command scripts cannot be started from the server console because they may require a long time complete and the server console should be available to control other server functions.

System Action: The server ignores the command and continues processing.

User Response: Start the server command script from an administrative client or schedule it for execution using the administrative command scheduler.

ANR1492Ecommand name: A loop has been detected in server command script RUN commands - command failed.

Explanation: A server command script DEFINE or UPDATE command has created a situation where one or more scripts invoke each other in a loop that can cause the scripts to run idefinitely.

System Action: The command fails to update the server command script.

User Response: Server command scripts can invoke each other, but not in a fashion that causes a potential loop in their execution. Specify the scripts in a manner that does not cause them to invoke each other in a loop.

ANR1493ECommand: Administrator administrator name is not authorized to update or delete command script command script name.

Explanation: The specified administrator has entered the indicated command, but this administrator does not have the proper authority necessary to update or delete this command script. If an administrator does not have system authority, they must have previously created or updated the script.

System Action: The server does not process the command.

User Response: Issue the command from a properly authorized administrator ID, or contact the administrator that created the script.

ANR1494Icommand name: Command return code is numeric return code.

Explanation: This message is issued during a RUN command (VERBOSE=YES) to indicate the numeric return code that was returned from the latest command.

System Action: SCRIPT processing continues.

User Response: None.

ANR1496I

Explanation: The ISSUE MESSAGE command with a severity indicator of INFORMATION was issued.

System Action: Server operation continues.

User Response: None.

ANR1497W

Explanation: The ISSUE MESSAGE command with a severity indicator of WARNING was issued.

System Action: Server operation continues.

User Response: None.

ANR1498E

Explanation: The ISSUE MESSAGE command with a severity indicator of ERROR was issued.

System Action: Server operation continues.

User Response: None.

ANR1499S

Explanation: The ISSUE MESSAGE command with a severity indicator of SEVERE was issued.

System Action: Server operation continues.

User Response: None.

ANR1500IPolicy domain domain name defined.

Explanation: In response to the DEFINE DOMAIN command, the policy domain domain name has been defined in the server database.

System Action: Server operation continues.

User Response: None.

ANR1501IPolicy domain domain name deleted.

Explanation: In response to the DELETE DOMAIN command, the policy domain domain name has been deleted from the server database. All policy sets, management classes, copy groups, and schedules related to the domain have also been removed.

System Action: Server operation continues.

User Response: None.

ANR1502IPolicy domain domain name updated.

Explanation: In response to the UPDATE DOMAIN command, the policy domain domain name has been updated in the server database.

System Action: Server operation continues.

User Response: None.

ANR1503IPolicy domain domain name copied to domain target domain.

Explanation: In response to the COPY DOMAIN command, the policy domain domain name has been copied to a new policy domain named target domain. All policy sets, management classes, and copy groups are also copied to the target domain policy domain.

System Action: Server operation continues.

User Response: None.

ANR1504ICommand: No matching domains.

Explanation: The server cannot find any policy domains with names that match the specification entered in the command command.

System Action: Server operation continues.

User Response: Reissue the command with a specification that matches an existing policy domain name. Use the QUERY DOMAIN command to obtain a list of the names of existing policy domains.

ANR1510IPolicy set set name defined in policy domain domain name.

Explanation: In response to the DEFINE POLICYSET command, the policy set named set name has been defined in the policy domain named domain name in the server database.

System Action: Server operation continues.

User Response: None.

ANR1511IPolicy set set name deleted from policy domain domain name.

Explanation: In response to the DELETE POLICYSET command, the policy set set name has been deleted from the policy domain domain name in the server database.

System Action: Server operation continues.

User Response: None.

ANR1512IPolicy set set name updated in policy domain domain name.

Explanation: In response to the UPDATE POLICYSET command, the policy set set name has been updated in the policy domain domain name in the server database.

System Action: Server operation continues.

User Response: None.

ANR1513IPolicy set set name copied to set new set name in policy domain domain name.

Explanation: In response to the COPY POLICYSET command, the policy set set name has been copied to the policy set new set name in the policy domain named domain name. All management classes and copy groups are also copied to the policy set new set name.

System Action: Server operation continues.

User Response: None.

ANR1514IPolicy set set name activated in policy domain domain name.

Explanation: In response to the ACTIVATE POLICYSET command, the policy set set name has been activated in the policy domain domain name. All management class and copy group definitions in the policy set will be used by clients that start sessions after this command is committed. Clients that currently have sessions established with the server will use the policy definitions in the previously active policy set for the domain.

System Action: The server replaces the active management class and copy group definitions for the policy domain with the definitions found in the specified policy set. These values are returned to client nodes that start a session with the server after this command is committed to the server database.

User Response: None.

ANR1515IPolicy set set name validated in domain domain name (ready for activation).

Explanation: This message may be displayed in response to a VALIDATE POLICYSET command. The policy set set name has been checked in the domain domain name to see if the management class and copy group definitions are adequate for activating the policy set. This message indicates that the policy set may be activated. Warning messages may be issued prior to this message if there are discrepancies in the policy set with respect to the set that is currently active in the policy domain.

System Action: The server checks its definitions to determine the policy set's qualifications for activation. The server does not activate the policy set.

User Response: If you are satisfied with any warning messages that may have been issued prior to this message concerning any possible discrepancies in the policy set, issue the ACTIVATE POLICYSET command to activate the policy set in the policy domain. Otherwise, correct the discrepancies prior to activating the policy set. Before the ACTIVATE POLICYSET command is used to activate the policy set, use the validate command to check policy set contents.

ANR1520IManagement class class name defined in policy domain domain name, set set name.

Explanation: In response to the DEFINE MGMTCLASS command, the management class named class name has been defined in the policy set set name belonging to the policy domain named domain name.

System Action: Server operation continues.

User Response: None.

ANR1521IManagement class class name deleted from policy domain domain name, set set name.

Explanation: In response to a DELETE MGMTCLASS command, the management class named class name has been deleted from the policy set set name belonging to the policy domain domain name. All copy groups defined for the management class are also removed.

System Action: Server operation continues.

User Response: None.

ANR1522IManagement class class name updated in policy domain domain name, set set name.

Explanation: In response to the UPDATE MGMTCLASS command, the management class named class name has been updated in the policy domain domain name, policy set set name.

System Action: Server operation continues.

User Response: None.

ANR1523IManagement class class name copied to class new class name in policy domain domain name, set set name.

Explanation: In response to the COPY MGMTCLASS command, the management class named class name has been copied to a new management class named new class name in policy set set name belonging to policy domain domain name. All copy groups defined for management class class name are also copied to management class new class name.

System Action: Server operation continues.

User Response: None.

ANR1530IBackup copy group group name defined in policy domain domain name, set set name, management class class name.

Explanation: In response to the DEFINE COPYGROUP command, a backup copy group named group name has been defined for the management class named class name in the policy set set name belonging to policy domain domain name.

System Action: Server operation continues.

User Response: None.

ANR1531IBackup copy group group name deleted from policy domain domain name, set set name, management class class name.

Explanation: In response to the DELETE COPYGROUP command, the backup copy group named group name has been deleted from the management class named class name in the policy set set name belonging to policy domain domain name.

System Action: Server operation continues.

User Response: None.

ANR1532IBackup copy group group name updated in policy domain domain name, set set name, management class class name.

Explanation: In response to the UPDATE COPYGROUP command, the backup copy group named group name has been updated in the management class named class name in the policy set set name belonging to policy domain domain name.

System Action: Server operation continues.

User Response: None.

ANR1535IArchive copy group group name defined in policy domain domain name, set set name, management class class name.

Explanation: In response to the DEFINE COPYGROUP command, an archive copy group named group name has been defined for the management class named class name in the policy set set name belonging to policy domain domain name.

System Action: Server operation continues.

User Response: None.

ANR1536IArchive copy group group name deleted from policy domain domain name, set set name, management class class name.

Explanation: In response to the DELETE COPYGROUP command, the archive copy group named group name has been deleted from the management class named class name in the policy set set name belonging to policy domain domain name.

System Action: Server operation continues.

User Response: None.

ANR1537IArchive copy group group name updated in policy domain domain name, set set name, management class class name.

Explanation: In response to the UPDATE COPYGROUP command, the archive copy group named group name has been updated in the management class named class name in the policy set set name belonging to policy domain domain name.

System Action: Server operation continues.

User Response: None.

ANR1538IDefault management class set to class name for policy domain domain name, set set name.

Explanation: The default management class for the policy set set name in policy domain domain name has been set to the management class named class name.

System Action: If this policy set is activated, clients use this management class for backup-archive processing by default, or if other management classes specified for binding do not exist in the policy set.

User Response: None.

ANR1550WManagement class class name is NOT defined in policy set set name but IS defined in the ACTIVE policy set for domain domain name: files bound to this management class will be REBOUND to the default management class if/when this set is activated.

Explanation: This message may be returned from the VALIDATE POLICYSET or ACTIVATE POLICYSET command. During policy set validation processing, the server has found a management class named class name in the currently active policy set, but not defined in the policy set being validated or activated (set name). If policy set set name is activated, files bound to this management class in domain domain name are automatically rebound to the default management class in policy set set name.

System Action: Server operation continues.

User Response: If you do not want files to be rebound to the default management class, define a management class with the name specified in the message for the policy set. To define the proper copy group attributes, reference the management class definition in the ACTIVE policy set or copy the management class class name from the ACTIVE policy set to policy set set name using the COPY MGMTCLAS command.

ANR1551WBACKUP copygroup group name in management class class name is NOT defined in policy set set name but is defined in the ACTIVE policy set for domain domain name: files bound to this management class will no longer be backed up if/when set name is activated.

Explanation: This message may be returned from the VALIDATE POLICYSET or ACTIVATE POLICYSET command. During policy set validation processing, the server has found a backup copy group named group name for management class class name in the currently active policy set, but the copy group is not defined for the management class in the policy set being validated or activated (set name). If policy set set name is activated, files bound to management class class name in domain domain name will no longer be eligible for backup processing.

System Action: Server operation continues.

User Response: If you want files bound to this management class to be eligible for backup processing, define an archive copy group for management class class name by using the DEFINE COPYGROUP command.

ANR1552WARCHIVE copygroup group name in management class class name is NOT defined in policy set set name but is defined in the ACTIVE policy set for domain domain name: files bound to this management class will no longer be archived if/when set name is activated.

Explanation: This message may be returned from the VALIDATE POLICYSET or ACTIVATE POLICYSET command. During policy set validation processing, the server has found an archive copy group named group name for management class class name in the currently active policy set, but the copy group is not defined for the management class in the policy set being validated or activated (set name). If policy set set name is activated, files bound to management class class name in domain domain name will no longer be eligible for archive processing.

System Action: Server operation continues.

User Response: If you want files bound to this management class to be eligible for archive processing, define an archive copy group for management class class name by using the DEFINE COPYGROUP command.

ANR1553WDEFAULT Management class class name in policy set domain name set name does not have a BACKUP copygroup: files will not be backed up by default if this set is activated.

Explanation: This message may be returned from the VALIDATE POLICYSET or ACTIVATE POLICYSET command. During policy set validation for policy set set name in policy domain domain name, the server has found that the default management class named class name does not have a backup copy group. This message warns the administrator that activation of this policy set results in client files not being backed up, unless they are bound to a management class (which has a copy group) other than the default.

System Action: Server operation continues.

User Response: To define a backup copy group for the management class, issue the DEFINE COPYGROUP command. To assign a different default management class for the domain, issue the ASSIGN DEFMGMTCLASS command. Take either action if you want files to be backed up by default.

ANR1554WDEFAULT Management class class name in policy set domain name set name does not have an ARCHIVE copygroup: files will not be archived by default if this set is activated.

Explanation: This message may be returned from the VALIDATE POLICYSET or ACTIVATE POLICYSET command. During policy set validation for policy set set name in policy domain domain name, the server has found that the default management class named class name does not have an archive copy group. This message warns the administrator that activation of this policy set will result in client files not being allowed archive processing unless they are bound to a management class (which has an archive copy group) other than the default.

System Action: Server operation continues.

User Response: To define a backup copy group for the management class, issue the DEFINE COPYGROUP command. To assign a different default management class for the domain, issue the ASSIGN DEFMGMTCLASS command. Take either action if you want files to be eligible for archive processing by default.

ANR1555WThe BACKUP copy group in management class management class name specifies a destination that does not refer to a defined storage pool: storage pool name. If this pool does not exist when policy set policy set name is activated, clients will fail when using this management class to backup files to the server.

Explanation: This message may be returned from the VALIDATE POLICYSET or ACTIVATE POLICYSET command. During policy set validation for set name, the server has found a backup copy group destination that references an undefined storage pool named pool name. If this storage pool is undefined when the policy set is activated, backup or archive operations will fail for clients with files bound to the management class whose copy groups reference this pool.

System Action: Server operation continues.

User Response: To locate the copy groups that refer to the undefined storage pool, issue the QUERY COPYGROUP command. To change the destination to refer to an existing storage pool, issue the UPDATE COPYGROUP command. To define the storage pool, an authorized administrator can issue the DEFINE STGPOOL command.

ANR1556WThe ARCHIVE copy group in management class management class name specifies a destination that does not refer to a defined storage pool: storage pool name. If this pool does not exist when policy set policy set name is activated, clients will fail when using this management class to archive files to the server.

Explanation: This message may be returned from the VALIDATE POLICYSET or ACTIVATE POLICYSET command. During policy set validation for set name, the server has found a archive copy group destination that references an undefined storage pool named pool name. If this storage pool is undefined when the policy set is activated, backup or archive operations will fail for clients with files bound to the management class whose copy groups reference this pool.

System Action: Server operation continues.

User Response: To locate the copy groups that refer to the undefined storage pool, issue the QUERY COPYGROUP command. To change the destination to refer to an existing storage pool, issue the UPDATE COPYGROUP command. To define the storage pool, an authorized administrator can issue the DEFINE STGPOOL command.

ANR1557WThe space management migration destination in management class management class name does not refer to a defined storage pool: storage pool name. If this pool does not exist when policy set policy set name is activated, clients will fail when using this management class to migrate space-managed files to the server.

Explanation: This message may be returned from the VALIDATE POLICYSET or ACTIVATE POLICYSET command. During policy set validation for set name, the server has found a space management migration destination that references an undefined storage pool named pool name. If this storage pool is undefined when the policy set is activated, space management migration operations will fail for clients with files bound to the management class that references this pool.

System Action: Server operation continues.

User Response: To locate the management class that refers to the undefined storage pool, issue the QUERY MGMTCLASS command. To change the destination to refer to an existing storage pool, issue the UPDATE MGMTCLASS command. To define the storage pool, an authorized administrator can issue the DEFINE STGPOOL command.

ANR1558EThe space management migration destination in management class management class name in policy set policy set name refers to copy storage pool: storage pool name. Copy storage pools are not a valid migration destination.

Explanation: This message may be returned from the VALIDATE POLICYSET or ACTIVATE POLICYSET command. During policy set validation for set name, the server has found a space management migration destination that references a copy storage pool named pool name.

System Action: Server operation continues. The policy set is not activated.

User Response: To locate the management class that refers to the copy storage pool, issue the QUERY MGMTCLASS command. To change the destination to refer to a non-copy storage pool, issue the UPDATE MGMTCLASS command.

ANR1559EThe copy group destination for type copy group type in management class management class name in policy set policy set name refers to copy storage pool: storage pool name. Copy storage pools are not a valid copy group destination.

Explanation: This message may be returned from the VALIDATE POLICYSET or ACTIVATE POLICYSET command. During policy set validation for set name, the server has found a copy group destination that references a copy storage pool named pool name.

System Action: Server operation continues. The policy set is not activated.

User Response: To locate the management class that refers to the copy storage pool, issue the QUERY MGMTCLASS command. To change the destination to refer to a non-copy storage pool, issue the UPDATE MGMTCLASS command.

ANR1560ECommand: Invalid policy domain name - domain name.

Explanation: Server processing for the command command fails because the policy domain name domain name specified does not contain valid characters or contains too many characters.

System Action: Database changes for the command are rolled back and server operation continues. The command is not successful in changing the server database.

User Response: Reissue the command and specify a policy domain name that conforms to these name requirements. For information on the character and length specifications for valid policy domain names, refer to the Administrator's Reference for your particular platform.

ANR1561ECommand: Missing policy domain name.

Explanation: Server processing for the command command fails because the required policy domain parameter has not been specified.

System Action: Database changes for the command are rolled back and server operation continues. The command is not successful in changing the server database.

User Response: Reissue the command and specify a valid policy domain name.

ANR1562ECommand: Policy domain description exceeds length limit characters.

Explanation: Server processing for the command command fails because the policy domain description specified is longer than the length limit number of characters allowed.

System Action: Database changes for the command are rolled back and server operation continues. The command is not successful in changing the server database.

User Response: Reissue the command and specify a shorter policy domain description.

ANR1563ECommand: Invalid retention period for BACKRETN parameter - retention value.

Explanation: Server processing for the copy group command command fails because the value (retention value) specified for the BACKRETN parameter is not valid.

System Action: Database changes for the command are rolled back and server operation continues. The command is not successful in changing the server database.

User Response: Reissue the command and specify a valid BACKRETN value. For valid BACKRETN values for the DEFINE COPYGROUP or UPDATE COPYGROUP commands, refer to the Administrator's Reference for your particular platform.

ANR1564ECommand: Invalid retention period for ARCHRETN parameter - retention value.

Explanation: Server processing for the copy group command command fails because the value (retention value) specified for the ARCHRETN parameter is not valid.

System Action: Database changes for the command are rolled back and server operation continues. The command is not successful in changing the server database.

User Response: Reissue the command and specify a valid ARCHRETN value. For valid ARCHRETN values for the DEFINE COPYGROUP or UPDATE COPYGROUP commands, refer to the Administrator's Reference for your particular platform.

ANR1565ECommand: Invalid policy set name - set name.

Explanation: Server processing for the command command fails because the policy set name set name specified does not contain valid characters or contains too many characters.

System Action: Database changes for the command are rolled back and server operation continues. The command is not successful in changing the server database.

User Response: Reissue the command and specify a policy set name that conforms to valid name requirements. For information on the character and length specifications for valid policy set names, refer to the Administrator's Reference for your particular platform.

ANR1566ECommand: Policy set description exceeds length limit characters.

Explanation: Server processing for the command command fails because the policy set description specified is longer than the length limit number of characters allowed.

System Action: Database changes for the command are rolled back and server operation continues. The command is not successful in changing the server database.

User Response: Reissue the command and specify a shorter policy set description.

ANR1567ECommand: Invalid management class name - class name.

Explanation: Server processing for the command command fails because the management class name class name specified does not contain valid characters or contains too many characters.

System Action: Database changes for the command are rolled back and server operation continues. The command is not successful in changing the server database.

User Response: Reissue the command and specify a management class name that conforms to valid name requirements. For information on the character and length specifications for valid management class names, refer to the Administrator's Reference for your particular platform.

ANR1568ECommand: Management class description exceeds length limit characters.

Explanation: Server processing for the command command fails because the management class description specified is longer than the length limit number of characters allowed.

System Action: Database changes for the command are rolled back and server operation continues. The command is not successful in changing the server database.

User Response: Reissue the command and specify a shorter management class description. Refer to the Administrator's Guide for your particular platform for more information.

ANR1569ECommand: Invalid copy group name - group name.

Explanation: Server processing for the command command fails because the copy group name group name specified does not contain valid characters or contains too many characters.

System Action: Database changes for the command are rolled back and server operation continues. The command is not successful in changing the server database.

User Response: Reissue the command and specify a copy group name that conforms to valid name requirements. For information on the character and length specifications for valid copy group names, refer to the Administrator's Reference for your particular platform.

ANR1570ECommand: Invalid copy frequency - frequency value.

Explanation: Server processing for the copy group command command fails because the value (frequency value) specified for the FREQUENCY parameter is not valid.

System Action: Database changes for the command are rolled back and server operation continues. The command is not successful in changing the server database.

User Response: Reissue the command and specify a valid FREQUENCY value. For valid FREQUENCY values for the DEFINE COPYGROUP or UPDATE COPYGROUP commands, refer to the Administrator's Reference for your particular platform.

ANR1571ECommand: Invalid copy destination - pool name.

Explanation: Server processing for the command command fails because the storage pool name pool name specified for the copy group destination does not contain valid characters or contains too many characters.

System Action: Database changes for the command are rolled back and server operation continues. The command is not successful in changing the server database.

User Response: Reissue the command and specify a storage pool name that conforms to valid name requirements. For information on the character and length specifications for valid storage pool names, refer to the Administrator's Reference for your particular platform. For a list of names of defined storage pools, issue the QUERY STGPOOL command.

ANR1572ECommand: Missing copy destination.

Explanation: Server processing for the copy group command command fails because the required copy group destination is not specified.

System Action: Database changes for the command are rolled back and server operation continues. The command is not successful in changing the server database.

User Response: Reissue the command and specify the required copy group destination (DEST).

ANR1573ECommand: Invalid copy type - type value.

Explanation: Server processing for the copy group command command fails because the value (type value) specified for the TYPE parameter is not valid.

System Action: Database changes for the command are rolled back and server operation continues. The command is not successful in changing the server database.

User Response: Reissue the command and specify a valid TYPE value. For valid TYPE values for the DEFINE COPYGROUP or UPDATE COPYGROUP commands, refer to the Administrator's Reference for your particular platform.

ANR1574ECommand: Invalid version count for VEREXISTS parameter - version value.

Explanation: Server processing for the copy group command command fails because the value (version value) specified for the VEREXISTS parameter is not valid.

System Action: Database changes for the command are rolled back and server operation continues. The command is not successful in changing the server database.

User Response: Reissue the command and specify a valid VEREXISTS value. For valid VEREXISTS values for the DEFINE COPYGROUP or UPDATE COPYGROUP commands, refer to the Administrator's Reference for your particular platform.

ANR1575ECommand: Invalid version count for VERDELETED parameter - version value.

Explanation: Server processing for the copy group command command fails because the value (version value) specified for the VERDELETED parameter is not valid.

System Action: Database changes for the command are rolled back and server operation continues. The command is not successful in changing the server database.

User Response: Reissue the command and specify a valid VERDELETED value. For valid VERDELETED values for the DEFINE COPYGROUP or UPDATE COPYGROUP commands, refer to the Administrator's Reference for your particular platform.

ANR1576ECommand: Invalid retention period for RETEXTRA parameter - retention value.

Explanation: Server processing for the copy group command command fails because the value (retention value) specified for the RETEXTRA parameter is not valid.

System Action: Database changes for the command are rolled back and server operation continues. The command is not successful in changing the server database.

User Response: Reissue the command and specify a valid RETEXTRA value. For valid RETEXTRA values for the DEFINE COPYGROUP or UPDATE COPYGROUP commands, refer to the Administrator's Reference for your particular platform.

ANR1577ECommand: Invalid retention period for RETONLY parameter - retention value.

Explanation: Server processing for the copy group command command fails because the value (retention value) specified for the RETONLY parameter is not valid.

System Action: Database changes for the command are rolled back and server operation continues. The command is not successful in changing the server database.

User Response: Reissue the command and specify a valid RETONLY value. For valid RETONLY values for the DEFINE COPYGROUP or UPDATE COPYGROUP commands, refer to the Administrator's Reference for your particular platform.

ANR1578ECommand: Invalid version count for RETVER parameter - retention value.

Explanation: Server processing for the copy group command command fails because the value (retention value) specified for the RETVER parameter is not valid.

System Action: Database changes for the command are rolled back and server operation continues. The command is not successful in changing the server database.

User Response: Reissue the command and specify a valid RETVER value. For valid RETVER values for the DEFINE COPYGROUP or UPDATE COPYGROUP commands, refer to the Administrator's Reference for your particular platform.

ANR1579ECommand: Invalid copy mode - mode value.

Explanation: Server processing for the copy group command command fails because the value (mode value) specified for the MODE parameter is not valid.

System Action: Database changes for the command are rolled back and server operation continues. The command is not successful in changing the server database.

User Response: Reissue the command and specify a valid MODE value. For valid MODE values for the DEFINE COPYGROUP or UPDATE COPYGROUP commands, refer to the Administrator's Reference for your particular platform.

ANR1580ECommand: Invalid copy serialization mode - serialization value.

Explanation: Server processing for the copy group command command fails because the value (serialization value) specified for the SERIALIZATION parameter is not valid.

System Action: Database changes for the command are rolled back and server operation continues. The command is not successful in changing the server database.

User Response: Reissue the command and specify a valid SERIALIZATION value. For valid SERIALIZATION values for the DEFINE COPYGROUP or UPDATE COPYGROUP commands, refer to the Administrator's Reference for your particular platform.

ANR1581ECommand: The option option is valid only for backup copy groups.

Explanation: Server processing for the archive copy group command command fails because the option specified is only valid for backup copy group definitions.

System Action: Database changes for the command are rolled back and server operation continues. The command is not successful in changing the server database.

User Response: Reissue the command specifying valid archive copy group options, or specify TYPE=BACKUP if the intent is to operate on a backup copy group. For valid archive copy group options, refer to the Administrator's Reference and Administrator's Guide for your particular platform.

ANR1582ECommand: The option option is valid only for archive copy groups.

Explanation: Server processing for the backup copy group command command fails because the option specified is only valid for archive copy group definitions.

System Action: Database changes for the command are rolled back and server operation continues. The command is not successful in changing the server database.

User Response: Reissue the command specifying valid backup copy group options, or specifying TYPE=ARCHIVE if the intent is to operate on an archive copy group. For valid backup copy group options, refer to the Administrator's Reference and Administrator's Guide for your particular platform.

ANR1583ECommand: Copy frequency for archive copy groups must be CMD - frequency value is not valid.

Explanation: Server processing for the archive copy group command command fails because a value other than CMD has been specified for the FREQUENCY parameter. The only value that may be specified for the archive copy group FREQUENCY parameter is CMD.

System Action: Database changes for the command are rolled back and server operation continues. The command is not successful in changing the server database.

User Response: Reissue the command specifying CMD for the FREQUENCY parameter, or omitting the FREQUENCY parameter because the default value for FREQUENCY is CMD for archive copy groups. For valid archive copy group options, refer to the Administrator's Reference and Administrator's Guide for your particular platform.

ANR1584ECommand: Copy mode for archive copy groups must be ABSOLUTE - mode value is not valid.

Explanation: Server processing for the archive copy group command command fails because a value other than ABSOLUTE has been specified for the MODE parameter. The only value that may be specified for the archive copy group MODE parameter is ABSOLUTE.

System Action: Database changes for the command are rolled back and server operation continues. The command is not successful in changing the server database.

User Response: Reissue the command specifying ABSOLUTE for the MODE parameter, or omitting the MODE parameter because the default value for MODE is ABSOLUTE for archive copy groups. For valid archive copy group options, refer to the Administrator's Reference and Administrator's Guide for your particular platform.

ANR1585ECommand: Policy set ACTIVE cannot be modified.

Explanation: Server processing for the command command fails because the policy set name ACTIVE is specified. Objects in the ACTIVE policy set for a domain may only be changed through activation of another policy set.

System Action: Database changes for the command are rolled back and server operation continues. The command is not successful in changing the server database.

User Response: Reissue the command specifying a policy set other than ACTIVE. To copy the ACTIVE policy set for a policy domain to another name so that commands may be used to change its contents, issue the COPY POLICYSET command. Then to activate the changes, issue the ACTIVATE POLICYSET command.

ANR1586ECommand: Invalid migration destination - pool name.

Explanation: Server processing for the command command fails because the storage pool name pool name specified for the migration destination is a copy pool. A copy pool is not a valid migration destination.

System Action: Database changes for the command are rolled back and server operation continues. The command is not successful in changing the server database.

User Response: Reissue the command using a storage pool name that is not a copy pool. For a list of names of defined storage pools, issue the QUERY STGPOOL command.

ANR1587ECommand: Invalid copy group destination - pool name.

Explanation: Server processing for the command command fails because the storage pool name pool name specified for the copy group destination is a copy pool. A copy pool is not a valid copy group destination.

System Action: Database changes for the command are rolled back and server operation continues. The command is not successful in changing the server database.

User Response: Reissue the command using a storage pool name that is not a copy pool. For a list of names of defined storage pools, issue the QUERY STGPOOL command.

ANR1590ECommand: Policy domain domain name is not defined.

Explanation: Server processing for the command command fails because the policy domain name domain name specified does not refer to a defined policy domain in the server database.

System Action: Database changes for the command are rolled back and server operation continues. The command is not successful in changing the server database.

User Response: Reissue the command specifying a policy domain name that is defined in the server database. For a list of the names of defined policy domains in the server database, issue the QUERY DOMAIN command.

ANR1591ECommand: Policy domain domain name is already defined.

Explanation: Server processing for the command command fails because the policy domain name domain name specified refers to a policy domain that is already defined in the server database.

System Action: Database changes for the command are rolled back and server operation continues. The command is not successful in changing the server database.

User Response: Reissue the command specifying a policy domain name that is not defined in the server database. For a list of the names of defined policy domains in the server database, issue the QUERY DOMAIN command.

ANR1592ECommand: Policy domain domain name still contains at least one policy set.

Explanation: Server processing for the delete command command fails because the policy domain name domain name specified refers to a policy domain that still contains at least one policy set.

System Action: Database changes for the command are rolled back and server operation continues. The command is not successful in changing the server database.

User Response: To delete the policy set from the policy domain, issue the DELETE POLICYSET command.

ANR1593ECommand: Policy domain domain name still contains at least one node.

Explanation: Server processing for the delete command command fails because the policy domain name domain name specified refers to a policy domain that still contains at least one node. A policy domain cannot be deleted if one or more client nodes are still assigned to the domain.

System Action: Database changes for the command are rolled back and server operation continues. The command is not successful in changing the server database.

User Response: To remove remaining nodes from the policy domain, issue the REMOVE NODE command. After all nodes are removed, issue the delete command again.

ANR1594ECommand: Policy domain domain name has no active policy set.

Explanation: Server processing for the update or register node command command fails because the policy domain name domain name specified refers to a policy domain that does not have an active policy set defined. Nodes cannot be assigned to policy domains that do not have an active policy set.

System Action: Database changes for the command are rolled back and server operation continues. The command is not successful in changing the server database.

User Response: To activate a policy set for the specified policy domain, issue the ACTIVATE POLICYSET command. After a policy set has been activated, client nodes may be assigned to the policy domain.

ANR1595ECommand: Policy set set name is not defined in policy domain domain name.

Explanation: Server processing for the command command fails because the policy set name set name specified does not refer to a defined set in policy domain domain name in the server database.

System Action: Database changes for the command are rolled back and server operation continues. The command is not successful in changing the server database.

User Response: Reissue the command specifying a policy set name that is defined in the policy domain. For a list of the names of defined policy sets in the policy domain, issue the QUERY POLICYSET command.

ANR1596ECommand: Policy set set name is already defined in policy domain domain name.

Explanation: Server processing for the command command fails because the policy set name set name specified refers to a policy set that is already defined in policy domain domain name.

System Action: Database changes for the command are rolled back and server operation continues. The command is not successful in changing the server database.

User Response: Reissue the command specifying a policy set name that is not defined in the policy domain. For a list of the names of defined policy sets in the policy domain, issue the QUERY POLICYSET command.

ANR1597Epolicy set command: Policy set set name in domain domain name still contains at least one management class.

Explanation: The policy set command failed because the set still contains at least one management class definition.

System Action: The command fails and server operation continues.

User Response: Remove the remaining management classes from the policy set and reissue the command.

ANR1598ECommand: No default management class has been assigned for policy set set name in domain domain name.

Explanation: Server processing for the command command fails because the policy set set name in policy domain domain name does not have a default management class assigned.

System Action: Database changes for the command are rolled back and server operation continues. The command is not successful in changing the server database.

User Response: To assign a default management class in the policy set, issue the ASSIGN DEFMGMTCLASS command.

ANR1599ECommand: Management class class name is not defined in policy domain domain name, set set name.

Explanation: Server processing for the command command fails because the management class name class name specified does not refer to a defined management class in policy set set name belonging to policy domain domain name.

System Action: Database changes for the command are rolled back and server operation continues. The command is not successful in changing the server database.

User Response: Reissue the command specifying a policy set name that is defined in the policy domain. For a list of the names of defined policy sets in the policy domain, issue the QUERY POLICYSET command.

ANR1600ECommand: Management class class name is already defined in policy domain domain name, set set name.

Explanation: Server processing for the command command fails because the specified management class name class name refers to a management class that is already defined in policy set set name belonging to policy domain domain name.

System Action: Database changes for the command are rolled back and server operation continues. The command is not successful in changing the server database.

User Response: Reissue the command specifying a management class name that is not defined in the policy set. For a list of the names of defined management classes in the policy domain and policy set, issue the QUERY MGMTCLASS command.

ANR1602ECommand: Backup copy group group name is not defined in policy domain domain name, set set name, management class class name.

Explanation: Server processing for the command command fails because the backup copy group named group name specified for management class class name does not refer to a defined backup copy group in policy set set name belonging to policy domain domain name.

System Action: Database changes for the command are rolled back and server operation continues. The command is not successful in changing the server database.

User Response: Reissue the command specifying a copy group name that is defined. For a list of the names of defined copy groups and management classes in the policy domain or policy set, issue the QUERY COPYGROUP command.

ANR1603ECommand: Backup copy group group name is already defined in policy domain domain name, set set name, management class class name.

Explanation: Server processing for the command command fails because the specified backup copy group named group name refers to a copy group that is already defined for management class (class name) in policy set set name belonging to policy domain domain name.

System Action: Database changes for the command are rolled back and server operation continues. The command is not successful in changing the server database.

User Response: Reissue the command specifying a copy group that is not defined in the policy set. For a list of the names of defined copy groups for management classes in the policy domain and policy set, issue the QUERY COPYGROUP command.

ANR1604ECommand: Archive copy group group name is not defined in policy domain domain name, set set name, management class class name.

Explanation: Server processing for the command command fails because the archive copy group named group name specified for management class class name does not refer to a defined archive copy group in policy set set name belonging to policy domain domain name.

System Action: Database changes for the command are rolled back and server operation continues. The command is not successful in changing the server database.

User Response: Reissue the command specifying a copy group name that is defined. For a list of the names of defined copy groups and management classes in the policy domain or policy set, issue the QUERY COPYGROUP command.

ANR1605ECommand: Archive copy group group name is already defined in policy domain domain name, set set name, management class class name.

Explanation: Server processing for the command command fails because the specified archive copy group named group name refers to a copy group that is already defined for management class class name in policy set set name belonging to policy domain domain name.

System Action: Database changes for the command are rolled back and server operation continues. The command is not successful in changing the server database.

User Response: Reissue the command specifying a copy group that is not defined in the policy set. For a list of the names of defined copy groups for management classes in the policy domain and policy set, issue the QUERY COPYGROUP command.

ANR1606EOut of server LOG space in accessing policy tables.

Explanation: The server ends a database update transaction for policy information because sufficient log space is not available on the server.

System Action: The policy operation is ended and server operation continues.

User Response: An authorized administrator can issue the DEFINE LOGVOLUME command to add volumes for use by the log and can issue the EXTEND LOG command to extend the size of the log so that the new volumes are used.

ANR1607EOut of server DB space in accessing policy tables.

Explanation: The server ends a database update transaction for policy information because sufficient database space is not available on the server.

System Action: The policy operation is ended and server operation continues.

User Response: An authorized administrator can issue the DEFINE DBVOLUME command to add volumes for use by the database and can issue the EXTEND DB command to extend the size of the database so that the new volumes are used.

ANR1608EError fetching entry for domain domain name, set set name.

Explanation: An internal server database error occurs while retrieving policy information for policy set set name in domain domain name.

System Action: The policy operation is ended and server operation continues.

User Response: Examine the server messages issued prior to this message to determine the source of the error. Use the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative.

ANR1609EPolicy error: unable to find management class ID for class class name in policy set set name belonging to domain domain name.

Explanation: An internal server database error has been encountered while retrieving policy information for management class class name in policy set set name belonging to policy domain domain name.

System Action: The policy operation is ended and server operation continues.

User Response: Examine the server messages issued prior to this message to determine the source of the error. Use the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative.

ANR1610EInternal Server error: invalid copy type copy type integer encountered in policy set validation.

Explanation: An internal server database error has been encountered while validating a policy set in response to the VALIDATE POLICYSET or ACTIVATE POLICYSET command.

System Action: The policy operation is ended and server operation continues.

User Response: Examine the server messages issued prior to this message to determine the source of the error. Use the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative.

ANR1611ECommand: Invalid management class name - management class name.

Explanation: Server processing for the command command fails because the specified management class name may not be used as a management class name.

System Action: Database changes for the command are rolled back and server operation continues. The command is not successful in changing the server database.

User Response: Reissue the command and specify another management class name.

ANR1612ECommand: Management class management class name in policy set set name, domain domain name specifies MIGREQUIRESBKUP=YES, but contains no backup copy group.

Explanation: During policy set validation or activation for policy set set name in policy domain domain name, the server has found that the management class named class name specifies the MIGREQUIRESBKUP=YES parameter but does not contain a backup copy group. Policy set validation or activation fails in this case because it would not be possible to ensure that space-managed client files are backed up prior to being migrated to the server.

System Action: Database changes for the command are rolled back and server operation continues. The command is not successful in changing the server database.

User Response: To define a backup copy group within the management class, issue the DEFINE COPYGROUP command. To change the MIGREQUIRESBKUP parameter, issue the UPDATE MGMTCLASS command.

ANR1650EServer server name is not defined.

Explanation: The server name was not created using the DEFINE SERVER command. This entry was created using the REGISTER NODE NODETYPE=SERVER command and is not a valid reference.

System Action: The current action for the device class referring to this server fails.

User Response: The device class referring to this node as the SERVERNAME should be updated to refer to a valid server entry. Specifically, it should refer to an entry created using the DEFINE SERVER command.

ANR1651EServer information for server name is not available.

Explanation: The information for server name was not available.

System Action: The current server action fails.

User Response: Please review any other messages prior to this message to determine the cause of the failure.

ANR1652EServer information for server name could not be read from a device configuration file.

Explanation: An attempt to a server definition for server name from any device configuration files failed.

System Action: The current action for the device class referring to this server fails.

User Response: Please verify the existence of a device configuration file and the DEFINE SERVER stanza within that file.

ANR1653EResource lock acquisition for server server name failed.

Explanation: The acquisition of the resource lock for server server name failed.

System Action: The current action for the device class referring to this server fails.

User Response: Retry the action referring to the device class that refers to this server name. If the lock failure persists, please contact your service representative.

ANR1654EServer server name will not be written to a device configuration file.

Explanation: An error occurred accessing the information for server name while trying to write this information to a device configuration file.

System Action: This DEFINE SERVER entry is not processing.

User Response: Verify that the necessary DEFINE SERVER entries were written to a device configuration file. If this error persists, please contact your service representative.

ANR1655EFailure processing password for Server server name when writing a device configuration file.

Explanation: An error occurred processing the password for server name while trying to write this information to a device configuration file.

System Action: This DEFINE SERVER entry is written to the device configuration file without the password.

User Response: The password needs to be specified after PASSWORD= for this DEFINE SERVER entry in the device configuration file.

ANR1656EFailure writing server definitions to a device configuration file.

Explanation: An error occurred writing the server information to a device configuration file.

System Action: The BACKUP DEVCONFIG action fails.

User Response: Check that the device configuration file exists and that the file system the file resides on is not out of space.

ANR1657ECommand: Invalid server or group name - server or group name.

Explanation: The command shown specifies an invalid server or server group name.

System Action: The server does not process the command.

User Response: Reissue the command with a valid name.

ANR1658ECommand: Failure determining NODENAME for server server name.

Explanation: The command shown was unable to determine a node name either from the NODENAME= parameter on this command or from the server name previously set using the SET SERVERNAME command.

System Action: The server does not process the command.

User Response: Reissue the command with a valid node name parameter or else update the server name using the SET SERVERNAME command so that a valid name is available.

ANR1659ECommand: Server or server group server or group name is already defined.

Explanation: A DEFINE SERVER or DEFINE SERVERGROUP command has been entered that specifies a server or server group name that already exists. The name specified must be a unique name. It must not duplicate a node name used by a registered node, a server name used by a defined server, or a server group name used by a defined server group.

System Action: The server does not process the command.

User Response: To define the server or server group, reissue the command and specify a different name.

ANR1660IServer server name defined successfully.

Explanation: The requested server has been defined to the system in response to a DEFINE SERVER command.

System Action: None.

User Response: None.

ANR1661IServer server name deleted.

Explanation: In response to a DELETE SERVER command, the requested server has been removed from the system.

System Action: None.

User Response: None.

ANR1662IServer server name updated.

Explanation: One or more attributes of a server have been updated by an UPDATE SERVER command.

System Action: None.

User Response: None.

ANR1663Ecommand: Server server name not defined

Explanation: The server server name is not defined to the system.

System Action: The command fails.

User Response: None.

ANR1664WCommand: Server server name is currently in use.

Explanation: The command shown specifies a server that is currently in use. The server is referenced by one or more of the following: a device class of DEVTYPE=SERVER that specifies this server for the 'SERVERNAME=' parameter, it is defined as the event server, or a connection with this server is currently open and in use.

System Action: The server does not process the command.

User Response: Reissue the command at a later time. In order to delete the server specified, it must not be currently connected to the server, it may not be referenced in a device class, and it can not be defined to be the event server.

ANR1665Ecommand: Failure updating password for server server name.

Explanation: An error occurred updating the password for server name.

System Action: The command fails.

User Response: Re-try the command specifying a different password.

ANR1666Ecommand: FILEAGGR not allowed with NODETYPE=SERVER.

Explanation: The FILEAGGR= parameter may not be specified with the NODETYPE=SERVER parameter also being specified.

System Action: The command fails.

User Response: Reissue the command command without the FILEAGGR= parameter if this is a NODETYPE=SERVER.

ANR1667Ecommand: Action not permitted against node node name.

Explanation: The command is not permitted against the entry for node node name. This node entry has a NODETYPE of SERVER.

System Action: The command fails.

User Response: None.

ANR1668Ecommand: Not allowed for server server name.

Explanation: The DELETE SERVER command is not permitted for server server name. The specified server is either the event server or else it is a node entry rather than a server definition.

System Action: The command fails.

User Response: If the specified server is the event server, and you want to delete it, issue the DELETE EVENTSERVER command and then reissue the DELETE SERVER command. To remove a node entry, issue the REMOVE NODE command for the specified name.

ANR1669IServer event server name is defined as the event server.

Explanation: The specified server is defined.

System Action: None.

User Response: None.

ANR1670EServer event server name is already defined as the event server. You must issue the DELETE EVENTSERVER command before defining a new event server.

Explanation: An event server is already defined.

System Action: The command fails.

User Response: Delete the existing Event Server and try the command again.

ANR1671IThe event server definition has been deleted.

Explanation: The event server definition has been deleted.

System Action: None.

User Response: If an event server definition is desired, use the DEFINE EVENTSERVER command.

ANR1672INo event server is currently defined.

Explanation: A query was issued to get the name of the event server; however, no event server is currently defined.

System Action: None.

User Response: If an event server definition is desired, use the DEFINE EVENTSERVER command.

ANR1673IServer group group name defined successfully.

Explanation: The requested server group is defined to the system in response to a DEFINE SERVERGROUP command.

System Action: None.

User Response: None.

ANR1674IMember member name defined successfully in server group group name.

Explanation: The requested member is defined in the server group in response to a DEFINE GRPMEMBER command.

System Action: None.

User Response: None.

ANR1675IServer group server group name deleted.

Explanation: The requested server is removed from the system in response to a DELETE SERVERGROUP command.

System Action: None.

User Response: None.

ANR1676IMember member name deleted from server group server group name.

Explanation: The requested member is removed from the server group in response to a DELETE GRPMEMBER command,

System Action: None.

User Response: None.

ANR1677IServer group server group name updated.

Explanation: One or more attributes of a server group is updated by an UPDATE SERVERGROUP command.

System Action: None.

User Response: None.

ANR1678IServer group original server group name renamed new server group name.

Explanation: A server group is renamed by a RENAME SERVERGROUP command. The original name is not valid.

System Action: None.

User Response: None.

ANR1679ECommand: Server group server group name not defined

Explanation: The server server group name is not defined to the system.

System Action: The command fails.

User Response: Retry the command specifying an existing group.

ANR1680ECommand: Member member name not defined in server group server group name.

Explanation: The member member name is not defined in server group server group name.

System Action: The command fails.

User Response: Retry the command specifying an existing member of the group.

ANR1681ECommand: Member member name is already in server group server group name.

Explanation: The member member name is defined in server group server group name.

System Action: The command fails.

User Response: Retry the command and specify a new member name.

ANR1682EA group cannot be a member of itself.

Explanation: The member and group name are the same. A group may not be a member of itself.

System Action: The command fails.

User Response: Retry the command and specify another member name.

ANR1683ECommand: Member member name not defined.

Explanation: The member member name is not defined to the system. Server group members must be a defined server or server group.

System Action: The command fails.

User Response: Retry the command specifying existing server or group.

ANR1684ERoute:command: Routed commands cannot be routed.

Explanation: The command part of a routed command may not contain route information itself. The allowable syntax for routed commands is ":". The command may not contain route information. Only one level of routing is allowed.

System Action: Routed commands where the command portion contains additional routing information are not processed.

User Response: Reissue the command without specifying route information in the command portion of this routed command.

ANR1685IServer group server group copied to server group new server group.

Explanation: This message is displayed in response to the COPY SERVERGROUP command. The server group named server group is copied to the server group named new server group.

System Action: None.

User Response: None.

ANR1686IMember member name moved from server group group name to server group new group name.

Explanation: The requested member member name is moved from server group group name to the server group new server group in response to a MOVE GRPMEMBER command.

System Action: None.

User Response: None.

ANR1687IOutput for command \'command\' issued against server server name follows:

Explanation: The output for the command issued against the indicated server follows this message.

System Action: None.

User Response: None.

ANR1688IOutput for command \'command\' issued against server server name completed.

Explanation: This message marks the end of the output for the command specified that was issued against the indicated server.

System Action: None.

User Response: None.

ANR1689EOutput for command \'command\' issued against server server name terminated.

Explanation: An error condition occurred causing the output for the command issued against the specified server to be terminated.

System Action: None.

User Response: Re-try the command against the requested server once the error condition has been resolved. If the cause of the error can not be determined, please contact your local service representative.

ANR1690EError sending command \'command\' to server server name.

Explanation: An error was encountered sending the specified command to the server indicated.

System Action: None.

User Response: Re-try the command against the requested server once the error condition has been resolved. If the cause of the error can not be determined, please contact your local service representative.

ANR1691EError receiving response from server server name for command \'command\'.

Explanation: An error was encountered receiving the response from the server indicated for the command that was issued against it.

System Action: None.

User Response: Re-try the command against the requested server once the error condition has been resolved. If the cause of the error can not be determined, please contact your local service representative.

ANR1692EResponse for command \'command\' from server server name contains invalid data.

Explanation: The output returned from the specified server for the command that was issued, contains invalid output. The command response can not be processed.

System Action: Output processing for this command response terminates.

User Response: Please contact your local service representative.

ANR1693EUnable to issue command \'command\' against server server name - failure starting thread.

Explanation: A thread could not be started to issue the specified command against the server indicated.

System Action: This command is not issued against the server specified. The process will attempt to issue the command against any other servers that were specified for the command routing information.

User Response: Examine the server messages issued prior to this message to determine the source of the error. Re-try routing this command to the indicated server after the cause of the error has been determined and resolved. If the error cannot be isolated and resolved, contact your service representative.

ANR1694IServer server name processed command \'command\' and completed successfully.

Explanation: The server indicated processed the command successfully.

System Action: None.

User Response: None.

ANR1695WServer server name processed command \'command\' but completed with warnings.

Explanation: The server indicated processed the command but encountered warnings. However, the warnings did not prevent the execution of the command.

System Action: None.

User Response: None.

ANR1696EServer server name attempted to process command \'command\' but encountered errors.

Explanation: The server indicated processed the command but encountered errors. These errors prevented the successful completion of the command.

System Action: None.

User Response: Examine any error messages issued on either the server sending the command or else the server executing the command to determine the cause of the failure. Reissue the command once these errors are corrected.

ANR1697ICommand \'command\' processed by total number for servers server(s): number of successful servers successful, number of servers with warnings with warnings, and number of servers with errors with errors.

Explanation: The indicated command was processed by the number of servers specified. For the total number of servers, the number indicated were successful, the number indicated encountered a warning condition but processed anyway, and finally, the number indicated encountered errors and could not process.

System Action: None.

User Response: None.

ANR1698ICommand \'command\' was not issued against any other servers.

Explanation: The indicated command was not issued against any other server. Either the routing information did not resolve to any valid servers or else failures occurred issuing the command against the required servers. indicated number of server.

System Action: None.

User Response: Check to see that valid route information was provided for the command or else check the activity log for error messages that indicate why the command was not issued to the other server.

ANR1699IResolved route information to number of servers server(s) - issuing command command against server(s).

Explanation: The route information was resolved to the number of servers indicated. The specified command will be issued against those servers.

System Action: None.

User Response: None.

ANR1700EUnable to resolve \'route information\' to any server(s).

Explanation: The route information provided for this command did not resolve to any server names or group names. Because of this, the command will not be issued.

System Action: None.

User Response: Examine the route information provided. Reissue the command providing correct route information.

ANR1701ECommand: No matching servers defined.

Explanation: No matching servers are found for the specified command.

System Action: Server operation continues, but the command is not processed.

User Response: Issue the command and specify different servers.

ANR1702WSkipping \'server name\' - unable to resolve to a valid server name.

Explanation: The server name specified is being skipped because it could not be resolved to a valid server name.

System Action: None.

User Response: Reissue the command providing the correct server name.

ANR1703EFailure resolving server names.

Explanation: An error occurred while resolving the server names. Specifically, the resolution of the server names has terminated because of a significant failure.

System Action: None.

User Response: Check the activity log and server console for other messages about the cause of the failure. Once the cause has been resolved, reissue the command.

ANR1704EFailure obtaining credentials for administrator admin name.

Explanation: An error occurred obtaining the credentials for the administrator referenced.

System Action: Command processing fails.

User Response: Check the activity log and server console for other messages about the cause of the failure. Once the cause has been resolved, reissue the command.

ANR1705WPing for server \'server name\' was not able to establish a connection.

Explanation: The ping command was unable to establish a connection to the server specified. This could indicate a problem on the server issuing the ping, a problem with the communication connection between the two servers, or else it is a problem with the other server.

System Action: None.

User Response: Check the activity log and server console for messages that indicate a failure or problem on the server issuing this command. Next, check the communication connection between the two servers. Also, check the server definition and password on both the server issuing the command and the server specified. And finally, verify that the server specified is running.

ANR1706IPing for server \'server name\' was able to establish a connection.

Explanation: The ping command was able to establish a connection to the server specified.

System Action: None.

User Response: Check the activity log and server console for messages that indicate a failure or problem on the server issuing this command. Next, check the communication connection between the two srevers. And finally, verify the operation of the server specified.

ANR1707IServer information not complete, crossdefine not allowed.

Explanation: The SERVERHLADDRESS, SERVERLLADDRESS or SERVERPASSWORD has not been set for this server. These are required for the CROSSDEFINE option on the define server command.

System Action: The command fails.

User Response: Use the QUERY STATUS command to find what values need to be set. An authorized administratormust issue the SET SERVERHLADDRESS, SET and SERVERLLADDRESS or SET SERVERPASSWORD command to set the missing values.

ANR1708IDefine server for Server name failed because the crossdefine failed.

Explanation: The define server command failed because the crossdefine parameter was included, and the crossdefine was not successful.

System Action: The command fails.

User Response: Check this server, and the server being defined for other messages indicating the reason for the failure.

ANR1709ECommand.: Failure determining current usage for server or group name Server name.

Explanation: The specified command failed to determine the current use of the server name or server group specified.

System Action: The command fails.

User Response: Retry the command. If it continues to fail and the cause of the failure cannot be determined, please contact your local service representative.

ANR1710ECommand.: Name Name not valid for this command.

Explanation: The name specified for this command is not valid for this operation. The first case is that a server name was specified for a command requiring a server group name. The other case is where a server group name was specified for a command requiring a server name.

System Action: The command fails.

User Response: Retry the command specifying the proper name.

ANR1711EError accessing the server or server group name Name.

Explanation: A server operation attempted to access the server name or server group name specified. An error occurred while trying to access the information for this server name or server group name.

System Action: The server opteration fails.

User Response: Review the activity log to try to determine the cause of the failure. If a cause cannot be determines, please contact your local service representative.

ANR1712WCommand routing not allowed from server console.

Explanation: Command routing is not allowed from the server console.

System Action: The command is not executed.

User Response: Reissue the command from an Administrative client.

ANR1713ICommand \'command\' issued against server server name.

Explanation: The specified command has been sent to the indicated server. The command is to terminate the specified server, no confirmation will be recieved.

System Action: None.

User Response: None.

ANR1714WThe password for administrator administartor name has expired. The password for this administrator must be updated on the configuration manager server server name.

Explanation: The password for the named administrator has expired, but the administrator is a managed object on this server. The password must be updated on the named configuration manager server.

System Action: The administrator is allow access to the server.

User Response: Change the administrator's password on the named configuration manager server.

ANR1715EEvent server cannot be deleted - it is currently active.

Explanation: The event server cannot be deleted since it is currently active for event logging.

System Action: The server does not delete the event server entry.

User Response: In order to delete the event server, it must not be currently active for event logging. To stop event logging to the event server issue END EVENTLOGGING EVENTSERVER. Then reissue the DELETE EVENTSERVER command.

ANR1716IServer cannot be crossdefined to itself, crossdefine not allowed.

Explanation: An attempt was made to crossdefine the server to itself.

System Action: The command fails.

User Response: None.

ANR1800EMissing or invalid EVENTLOG command parameter.

Explanation: The event logging command issued contains an invalid parameter, or is missing a required parameter.

System Action: The command is ignored.

User Response: Reissue the command with the proper parameters.

ANR1801EEventlog command: Invalid event or event class - Event or event class name.

Explanation: An event logging command has been entered which specifies an unknown event or event class.

System Action: The command is ignored for the invalid event or event class. Any valid events or classes specified are processed.

User Response: Reissue the command with the correct event or event class.

ANR1808EUnable to open event log file file spec for appending.

Explanation: The server cannot write to a file which has been specified for event logging.

System Action: No logging will be done to the file receiver.

User Response: Check the file for proper access permissions, or specify a different file for logging.

ANR1809EInsufficient memory to activate event logging.

Explanation: A BEGIN EVENTLOGGING command has been entered, but the server has insufficient memory available to activate logging.

System Action: The command is ignored.

User Response: If logging is required, make more memory available to the server then restart the server.

ANR1810EEventlog command: Invalid receiver - receiverName.

Explanation: An event logging command has been entered which specifies an unknown event log receiver (maybe unknown just to this platform).

System Action: The command is ignored for the invalid receiver. Any valid receivers specified are processed.

User Response: Reissue the command with the correct receiver.

ANR1822IEvent logging ended for the receiverName receiver.

Explanation: In response to an END EVENTLOGGING command or because an error occurred, event log records are no longer being output to the specified receiver.

System Action: None.

User Response: None.

ANR1823IEvent logging ended for all receivers.

Explanation: In response to an END EVENTLOGGING command, event log records are no longer being output to any receiver.

System Action: None.

User Response: None.

ANR1824EEvent logging is inactive for the specified receiver.

Explanation: An END EVENTLOGGING command has been entered, but logging is not active for the specified receiver.

System Action: The command is ignored.

User Response: If logging is desired, use the ENABLE EVENT and BEGIN EVENTLOGGING commands to activate event logging.

ANR1825IEvent logging active for the receiverName receiver.

Explanation: In response to a BEGIN EVENTLOGGING command, event log records are now being output to the specified receiver.

System Action: None.

User Response: None.

ANR1826IEvent logging active for all receivers.

Explanation: In response to a BEGIN EVENTLOGGING command, event log records are now being output to all receivers.

System Action: None.

User Response: None.

ANR1827EEventlog command: No valid receiver specified.

Explanation: An event logging command has been entered, and no valid receivers were specified.

System Action: The command is ignored.

User Response: Reissue the command with the correct receiver.

ANR1828EEventlog command: No valid event specified.

Explanation: An event logging command has been entered and no valid events or event classes were specified.

System Action: The command is ignored.

User Response: Reissue the command with the correct events or event classes.

ANR1829EEventlog command: Server events may not be disabled for the activity log receiver.

Explanation: A DISABLE EVENT command has been entered for the activity log receiver.

System Action: The command is ignored for the activity log receiver. Any valid receivers specified are processed.

User Response: Reissue the command with the correct receiver.

ANR1830EreceiverName receiver options not defined in the server options file.

Explanation: A BEGIN EVENTLOGGING command has been entered for a receiver, but the required receiver options were not specified in the server options file.

System Action: Logging is not started for the specified receiver.

User Response: Enter the receiver options in the server options file and restart the server.

ANR1831IEvent logging of client events ended for ACTLOG receiver.

Explanation: An END EVENTLOGGING command has been entered for the activity log receiver.

System Action: The server no longer records client events in the activity log. Server events continue to be recorded in the activity log.

User Response: None.

ANR1842EAn error occurred on the receiverName receiver.

Explanation: An error occurred on the specified receiver.

System Action: The server no longer sends events to the receiver.

User Response: Issue a BEGIN EVENTLOGGING command for the receiver to attempt to start logging events to the receiver again.

ANR1843IEvent log receiver initialization in progress.

Explanation: Initialization is starting for the eventlog receivers.

System Action: None.

User Response: None.

ANR1844IEventlog command command processed.

Explanation: The specified command was processed.

System Action: None.

User Response: If any previous messages indicate that parts of the command failed, reissue the command for those parts only.

ANR1850ECircular event logging detected. The event server has previously handled event Event number from Source trail. To prevent looping, events which have already been logged by the event server are not sent again. Please correct the situation causing circular logging to avoid wasting system resources.

Explanation: The server is attempting to log an event which has previously been handled by the event server that is currently defined.

System Action: The event is not sent to the event server. Other events will still be sent, and this message will be issued periodically if this situation is detected again.

User Response: Determine what is wrong with the server to server event logging setup, and fix the problem.

ANR1851EThe source trail for server to server event logging has exceeded the maximum length of Maximum sourcetrail length bytes.

Explanation: While attempting to log an event to the event server, the server has found that the source trail length is too long.

System Action: The server continues to try to send the event to the event server, but the source trail may be truncated and appear something like:



name1>...>namex>namey

where,
name1 is the originator of the event.
... is where intervening server name(s) have been left off the source trail.

User Response: Most likely you are using very long server names and/or have excessive hops from server to server. Either use shorter server names or change your configuration to reduce the number of hops.

ANR1852EUnable to send header to TEC at TEC server rc return code

Explanation: A network error has occurred in attempting to send the event header to the Tivoli Enterprise Console.

System Action: None.

User Response: Verify network connections and contact your service representative if this error persists.

ANR1853EUnable to send data to TEC at TEC server rc return code

Explanation: A network error has occurred in attempting to send the event data to the Tivoli Enterprise Console.

System Action: None.

User Response: Verify network connections and contact your service representative if this error persists.

ANR1854EUnable to flush data to TEC at TEC server rc return code

Explanation: A network error has occurred in attempting to flush data to the Tivoli Enterprise Console .

System Action: None.

User Response: Verify network connections and contact your service representative if this error persists.

ANR2000EUnknown command - command.

Explanation: The specified command is not a valid server command.

System Action: The server ignores the command.

User Response: Reissue the correct command.

ANR2001EInsufficient server memory to initiate command.

Explanation: A command has been entered, but the server cannot obtain enough internal memory to process the command.

System Action: The server ignores the command.

User Response: Allocate additional storage to the server. For details, issue HELP MEMORY to display the information online or see "Appendix A. Allocating Additional Server Memory".

ANR2002EMissing closing quote character.

Explanation: A server command that contains a quoted parameter has been entered, but a matching closing quote is missing.

System Action: The server ignores the command.

User Response: Reissue the command with properly matched quotes.

ANR2003EIllegal use of keyword parameter character (=) - parameter.

Explanation: A server command contains the parameter shown followed by an equal sign (=), but the parameter is not a keyword parameter.

System Action: The server ignores the command.

User Response: Reissue the command and enter the proper syntax.

ANR2004EMissing value for keyword parameter - parameter.

Explanation: A server command containing a keyword parameter has been entered, but the value for the parameter is missing.

System Action: The server ignores the command.

User Response: Reissue the command and supply a value for the keyword parameter.

ANR2005EKeyword parameter character (=) may not be surrounded by blanks.

Explanation: A server command contains a keyword parameter followed by an equal sign (=), but the equal sign is preceded or followed by a blank, or both.

System Action: The server ignores the command.

User Response: Reissue the command without blanks next to the equal sign.

ANR2006EActivity log process was not started, the default output stream cannot be opened.

Explanation: The process that monitors the default (console) output stream and maintains the activity log cannot access that output stream.

System Action: The server does not update the activity log.

User Response: Contact your service representative.

ANR2007EActivity log process was not started, due to an internal error.

Explanation: The process that monitors the default (console) output stream and maintains the activity log cannot start due to a server internal error.

System Action: The server does not update the activity log.

User Response: Examine the server messages issued prior to this message to determine the source of the error. Issue the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative.

ANR2008EActivity log process has stopped - database transaction could not be started.

Explanation: The process that monitors the default (console) output stream and maintains the activity log cannot continue due to a server transaction failure. This may be a memory shortage error.

System Action: The server stops updating the activity log.

User Response: Allocate additional storage to the server. For details, issue HELP MEMORY to display the information online or see "Appendix A. Allocating Additional Server Memory".

ANR2009EActivity log process has stopped - database error.

Explanation: The process that monitors the default (console) output stream and maintains the activity log cannot continue due to a server database error.

System Action: The server stops updating the activity log.

User Response: Contact your service representative.

ANR2010WServer is out of LOG space in adding entries to the Activity Log. Console messages will not be logged until LOG space is available.

Explanation: The process that monitors the default (console) output stream and maintains the activity log cannot update the activity log due to a lack of recovery log space.

System Action: The server does not update the activity log.

User Response: An authorized administrator can issue the DEFINE LOGVOLUME command to add volumes for use by the log, and can issue the EXTEND LOG command to extend the size of the log so that the new volumes are used.

ANR2011WServer is out of DB space in adding entries to the Activity Log. Console messages will not be logged until DB space is available.

Explanation: The process that monitors the default (console) output stream and maintains the activity log cannot update the activity log due to a lack of database space.

System Action: The server does not update the activity log.

User Response: An authorized administrator can issue the DEFINE DBVOLUME command to add volumes for use by the database, and can issue the EXTEND DB command to extend the size of the database so that the new volumes are used.

ANR2012WActivity log process has encountered unexpected table data output in the default output stream.

Explanation: The process that monitors the default (console) output stream and maintains the activity log has detected invalid data in the console stream.

System Action: The server stops updating the activity log.

User Response: Contact your service representative.

ANR2013EThe activity log process has encountered unexpected output data in the console output stream. The process will be restarted.

Explanation: The process that monitors console output and maintains the activity log has detected invalid data (unknown data type) in the console stream.

System Action: The server restarts the activity log recording process. While the process is restarting, the server may not be able to record some console messages in the activity log.

User Response: The server may be low on available memory. Allocate additional storage to the server. For details, issue HELP MEMORY to display the information online or see "Appendix A. Allocating Additional Server Memory".

ANR2014EActivity log pruning process could not be started, due to an internal error.

Explanation: The process that removes expired records from the server activity log cannot begin execution due to a server internal error.

System Action: The server does not prune the activity log.

User Response: Examine the server messages issued prior to this message to determine the source of the error. Issue the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative.

ANR2015EActivity log failure - database transaction could not be started.

Explanation: The process that removes expired records from the server activity log has failed due to a database transaction failure, which may be a memory shortage error.

System Action: The server ends activity log pruning.

User Response: Allocate additional storage to the server. For details, issue HELP MEMORY to display the information online or see "Appendix A. Allocating Additional Server Memory".

ANR2016EActivity log failure - database error.

Explanation: The process that removes expired records from the server activity log has failed due to a server database error.

System Action: The server ends activity log pruning.

User Response: Contact your service representative.

ANR2017IAdministrator Administrator Name issued command: Command

Explanation: This message records the fact that the named administrator issued the command specified. The messages is issued and looged to provide an audit trail for administrative commands.

System Action: Server operation continues

User Response: None.

ANR2019ICommand: No nodes updated.

Explanation: An UPDATE NODE command has been entered, but no objects were updated.

System Action: None.

User Response: None.

ANR2020ECommand: Invalid parameter - parameter.

Explanation: The specified server command has been entered with an invalid parameter.

System Action: The server ignores the command.

User Response: Reissue the command and enter the proper syntax.

ANR2021ECommand: Missing subcommand keyword.

Explanation: The specified server command has been entered without a valid subcommand (second parameter).

System Action: The server ignores the command.

User Response: Reissue the command and enter the proper syntax.

ANR2022ECommand: One or more parameters are missing.

Explanation: The specified server command has been entered without all required parameters.

System Action: The server ignores the command.

User Response: Reissue the command and enter the proper syntax.

ANR2023ECommand: Extraneous parameter - parameter.

Explanation: The specified server command contains more positional parameters than is allowed.

System Action: The server ignores the command.

User Response: Reissue the command and enter the proper syntax.

ANR2024ECommand: Too many parameters specified.

Explanation: The specified server command contains more positional parameters than is allowed.

System Action: The server ignores the command.

User Response: Reissue the command and enter the proper syntax.

ANR2025ECommand: Command failed - server thread resource not available.

Explanation: A server command, which has a requirement to start a server thread, has been entered but cannot be executed because no server thread is available.

System Action: The command is not executed.

User Response: Reissue the command. If the command fails with the same error, wait for server activity to decrease and try again.

ANR2026ECommand: Command failed - sufficient server memory is not available.

Explanation: A server command has been entered but cannot be processed because sufficient memory is not available to the server.

System Action: The server does not process the command.

User Response: Allocate additional storage to the server. For details, issue HELP MEMORY to display the information online or see "Appendix A. Allocating Additional Server Memory".

ANR2027ECommand: Command failed - sufficient server recovery log space is not available.

Explanation: A server command has been entered but cannot be processed because sufficient recovery log space is not available.

System Action: The server does not process the command.

User Response: An authorized administrator can issue the DEFINE LOGVOLUME command to add volumes for use by the log, and can issue the EXTEND LOG command to extend the size of the log so that the new volumes are used.

ANR2028ECommand: Command failed - sufficient server database space is not available.

Explanation: A server command has been entered but cannot be processed because sufficient database space is not available.

System Action: The server does not process the command.

User Response: An authorized administrator can issue the DEFINE DBVOLUME command to add volumes for use by the database, and can issue the EXTEND DB command to extend the size of the database so that the new volumes are used.

ANR2029ECommand: Transaction failed; command not executed.

Explanation: A command that is part of the current transaction has failed; therefore, any additional commands fail.

System Action: The server does not process the command.

User Response: Stop the administrative session, restart it, and try the command again. If this problem persists, contact your service representative.

ANR2030ECommit not accepted; transaction failed.

Explanation: A command that is part of the current transaction has failed; therefore, a COMMIT command cannot be processed.

System Action: The server does not process the COMMIT command.

User Response: Stop the administrative session, restart it, and try the command again. If this problem persists, contact your service representative.

ANR2031ECommand: At least one attribute must be specified for update.

Explanation: The specified UPDATE command has been entered, but no attributes have been specified for updating.

System Action: The server ignores the command.

User Response: Reissue the UPDATE command with one or more attributes to be updated.

ANR2032ECommand: Command failed - internal server error detected.

Explanation: An internal error has occurred during an attempt to process a server command. This message always accompanies another error message and provides more detail about that error.

System Action: The server does not process the command.

User Response: Examine the server messages issued prior to this message to determine the source of the error. Issue the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative.

ANR2033ECommand: Command failed - lock conflict.

Explanation: A server command that requires the server to lock a system resource has been entered. The command cannot be executed because the resource is already in use by another command or process.

System Action: The server does not process the command.

User Response: Try the command again at a later time.

ANR2034ECommand: No match found using this criteria.

Explanation: The specified command has been entered, but no objects that match the criteria can be found.

System Action: None.

User Response: None.

ANR2035ECommand: Administrator administrator name is not authorized to issue this command.

Explanation: The specified administrator has entered the indicated command, but this administrator does not have the proper authority necessary to run the command. Note: This message can be issued as a result of the server option REQSYSAUTHOUTFILE YES being in effect.

System Action: The server does not process the command.

User Response: Examine previous messages for any additional information. Issue the command from a properly authorized administrator ID, or contact the system administrator to have additional authority granted to the current administrator ID.

ANR2036ECommand: Process could not be started - sufficient memory is not available.

Explanation: A background process cannot be started for the indicated command because sufficient memory is not available to the server.

System Action: A new process is not started to execute this command.

User Response: Allocate additional storage to the server. For details, issue HELP MEMORY to display the information online or see "Appendix A. Allocating Additional Server Memory".

ANR2037ECommand: Process could not be started - lock conflict.

Explanation: A background process cannot be started for the indicated command because a required system resource is already locked by another command or process.

System Action: A new process is not started to execute this command. If other processes have been started for this command, these processes may execute successfully.

User Response: If necessary, try the command again at a later time.

ANR2038ECommand: Process could not be started - server thread resource not available.

Explanation: A background process cannot be started for the indicated command because no server thread is available.

System Action: A new process is not started to execute this command. If other processes have been started for this command, these processes may execute successfully.

User Response: If necessary, reissue the command. If the command fails with the same error, wait for server activity to decrease and try again.

ANR2039ECommand: Process could not be started - internal server error detected.

Explanation: A background process cannot be started for the indicated command because an internal error has occurred.

System Action: A new process is not started to execute this command. If other processes have been started for this command, these processes may execute successfully.

User Response: Examine the server messages issued prior to this message to determine the source of the error. Issue the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative.

ANR2040WThis command attempts to restore all files in storage pool storage pool which have previously been found to be damaged or which reside on a volume with access mode "destroyed"; existing references to files in storage pool storage pool will be deleted from the database after the files have been restored.

Explanation: Issuing the RESTORE STGPOOL command will result in deletion of existing files in the indicated primary storage pool after these files have been restored from a copy storage pool. If a volume with access mode destroyed becomes empty because all files on the volume have been restored to another location, the destroyed volume will be deleted from the database.

System Action: The administrator is asked whether to continue.

User Response: Enter 'Y' to restore the storage pool, 'N' otherwise.

ANR2041WThis command attempts to restore all files in storage pool storage pool which reside on one of the volumes specified in the command; existing references to files on these volumes will be deleted from the database after the files have been restored.

Explanation: Issuing the RESTORE VOLUME command causes the access mode of the specified volumes to be updated to destroyed. Existing files will be deleted from the specified volumes after these files have been restored from a copy storage pool. If a volume with access mode destroyed becomes empty because all files on the volume have been restored to another location, the destroyed volume will be deleted from the database.

System Action: The administrator is asked whether to continue.

User Response: Enter 'Y' to restore the volumes, 'N' otherwise.

ANR2042ECommand: Copied parameter not valid for copy storage pool volume.

Explanation: The QUERY CONTENT server command has been entered with an invalid parameter. COPIED is not a valid parameter when the volume specified belongs to a copy storage pool.

System Action: The server ignores the command.

User Response: Reissue the command without the COPIED parameter.

ANR2043ECommand: WAIT parameter not allowed from server console.

Explanation: The WAIT parameter is not allowed for commands issued from the server console.

System Action: The command is not executed.

User Response: Either reissue the command without the WAIT parameter or else reissue the command from an administrator using an Administrative Client.

ANR2044ECommand: Invalid option's value - Option's value.

Explanation: The set option command has been entered with an invalid value.

System Action: The server does not process the command.

User Response: Reissue the command with a valid value.

ANR2045ECommand: An error (error code) occurred during a write operation.

Explanation: The server detects an error while attempting a write operation.

System Action: Server processing continues.

User Response: Refer to the other displayed messages to determine why the write operation has failed.

ANR2046Ioptionset name: Optionset optionset name defined.

Explanation: The requested option set has been added to the system in response to a DEFINE OPTIONSET command.

System Action: None.

User Response: None.

ANR2047ECommand: Optionset optionset name is already defined.

Explanation: A DEFINE OPTIONSET command has been entered that specifies an optionset name already defined to the server.

System Action: The server does not process the command.

User Response: To define the optionset, reissue the command and specify a different optionset name.

ANR2048ICommand: Optionset optionset name deleted.

Explanation: The requested option set has been deleted from the system in response to a DELETE OPTIONSET command.

System Action: None.

User Response: None.

ANR2049ECommand: Optionset optionset name is not defined.

Explanation: The command shown specifies an optionset that is not defined in the server.

System Action: The server does not process the command.

User Response: None.

ANR2050ICommand: Option option name defined in optionset option set name.

Explanation: The requested option has been added to the specified optionset in response to a DEFINE OPTIONSET command.

System Action: None.

User Response: None.

ANR2051ECommand: Option option name, sequence number sequence number is already defined in optionset option set name.

Explanation: The requested option already exists in the optionset specified by the DEFINE CLIENTOPT command.

System Action: The server does not process the command.

User Response: None.

ANR2052ECommand: Option option name, sequence number sequence number is not defined in optionset option set name.

Explanation: The requested option is not defined in the optionset specified by the DELETE CLIENTOPT command.

System Action: The server does not process the command.

User Response: None.

ANR2053ICommand: Option option name, sequence number sequence number, has been deleted from optionset option set name.

Explanation: The requested option has been deleted from the specified optionset in response to a DELETE CLIENTOPT command.

System Action: None.

User Response: None.

ANR2054ICommand: Optionset optionset name updated.

Explanation: The requested option set has been updated in the system in response to an UPDATE OPTIONSET command.

System Action: None.

User Response: None.

ANR2055ICommand: Optionset source optionset name copied to optionset target optionset name.

Explanation: This message is displayed in response to the COPY OPTIONSET command. The optionset named source optionset name has been copied to the optionset named target optionset name.

System Action: Server operation continues.

User Response: None. The requested option set has been added to the system in response to a COPY OPTIONSET command.

ANR2056ECommand: Invalid option name - option name. Retry using the full optionname.

Explanation: The command shown specifies an invalid option name.

System Action: The server does not process the command.

User Response: Reissue the command with a valid option name.

ANR2057ECommand: Invalid option value - option value.

Explanation: The command shown specifies an invalid option value.

System Action: The server does not process the command.

User Response: Reissue the command with a valid option value.

ANR2058WCommand: Options file Filespec not found - user needs to update the file manually.

Explanation: The server options file cannot be opened or found.

System Action: The command is processed but the option is not updated in the options file.

User Response: Use a text editor to update the server options file if the user wants to use this value when the server restarts later. If the user does not update the file, the current value in the options file will be used when the server restarts.

ANR2059WCommand: Error occurs when writing to Filespec - user needs to update the file manually.

Explanation: An error occurs when trying to write the new value to the server options file.

System Action: The command is processed but the option is not updated in the options file.

User Response: Use a text editor to update the server options file if the user wants to use this value when the server restarts later. If the user does not update the file, the current value in the options file will be used when the server restarts.

ANR2060INode node name registered in policy domain domain name.

Explanation: The requested backup-archive node has been added to the system in response to a REGISTER NODE command and has been assigned to the policy domain indicated.

System Action: None.

User Response: None.

ANR2061INode node name removed from policy domain domain name.

Explanation: In response to a REMOVE NODE command, the requested backup-archive node has been removed from the system.

System Action: None.

User Response: None.

ANR2062INode node name renamed to new node name.

Explanation: In response to a RENAME NODE command, the requested backup-archive node has been renamed to the new name shown.

System Action: None.

User Response: None.

ANR2063INode node name updated.

Explanation: One or more attributes of a backup-archive node have been updated by an UPDATE NODE command.

System Action: None.

User Response: None.

ANR2064INode node name locked.

Explanation: In response to a LOCK NODE command, the indicated backup-archive node has been locked.

System Action: None.

User Response: None.

ANR2065INode node name is already locked.

Explanation: The indicated backup-archive node referenced in the LOCK NODE command is already locked.

System Action: None.

User Response: None.

ANR2066INode node name unlocked.

Explanation: In response to an UNLOCK NODE command, the indicated backup-archive node is unlocked.

System Action: None.

User Response: None.

ANR2067INode node name is already unlocked.

Explanation: The indicated backup-archive node referenced in the UNLOCK NODE command is not locked.

System Action: None.

User Response: None.

ANR2068IAdministrator administrator ID registered.

Explanation: In response to a REGISTER ADMIN command, the requested administrator ID has been added to the system.

System Action: None.

User Response: None.

ANR2069IAdministrator administrator ID removed.

Explanation: In response to a REMOVE ADMIN command, the requested administrator ID has been removed from the system.

System Action: None.

User Response: None.

ANR2070IAdministrator administrator ID renamed to new administrator ID.

Explanation: In response to a RENAME ADMIN command, the requested administrator ID has been changed to the new name shown.

System Action: None.

User Response: None.

ANR2071IAdministrator administrator ID updated.

Explanation: One or more attributes of an administrative user have been updated by an UPDATE ADMIN command.

System Action: None.

User Response: None.

ANR2072IAdministrator administrator ID locked.

Explanation: In response to a LOCK ADMIN command, the indicated administrator ID has been locked.

System Action: None.

User Response: None.

ANR2073IAdministrator administrator ID is already locked.

Explanation: The indicated administrator ID referenced in the LOCK ADMIN command is already locked.

System Action: None.

User Response: None.

ANR2074IAdministrator administrator ID unlocked.

Explanation: In response to an UNLOCK ADMIN command, the indicated administrator ID is unlocked.

System Action: None.

User Response: None.

ANR2075IAdministrator administrator ID is already unlocked.

Explanation: The indicated administrator ID referenced in the UNLOCK ADMIN command is not locked.

System Action: None.

User Response: None.

ANR2076ISystem privilege granted to administrator administrator ID.

Explanation: In response to a GRANT AUTHORITY command, system privilege class has been granted to the indicated administrator.

System Action: None.

User Response: None.

ANR2077IUnrestricted policy privilege granted to administrator administrator ID.

Explanation: In response to a GRANT AUTHORITY command, unrestricted policy privilege has been granted to the indicated administrator.

System Action: None.

User Response: None.

ANR2078IRestricted policy privilege granted to administrator administrator ID - policy domain domain name.

Explanation: In response to a GRANT AUTHORITY command, restricted policy privilege for the specified policy domain has been granted to the indicated administrator.

System Action: None.

User Response: None.

ANR2079IUnrestricted storage privilege granted to administrator administrator ID.

Explanation: In response to a GRANT AUTHORITY command, unrestricted storage privilege has been granted to the indicated administrator.

System Action: None.

User Response: None.

ANR2080IRestricted storage privilege granted to administrator administrator ID - storage pool storage pool name.

Explanation: In response to a GRANT AUTHORITY command, restricted storage privilege for the specified storage pool has been granted to the indicated administrator.

System Action: None.

User Response: None.

ANR2081IAnalyst privilege granted to administrator administrator ID.

Explanation: In response to a GRANT AUTHORITY command, analyst privilege class has been granted to the indicated administrator.

System Action: None.

User Response: None.

ANR2082IOperator privilege granted to administrator administrator ID.

Explanation: In response to a GRANT AUTHORITY command, operator privilege class has been granted to the indicated administrator.

System Action: None.

User Response: None.

ANR2083ISystem privilege revoked for administrator administrator ID.

Explanation: In response to a REVOKE AUTHORITY command, system privilege class has been revoked from the indicated administrator.

System Action: None.

User Response: None.

ANR2084IPolicy privilege revoked for administrator administrator ID.

Explanation: In response to a REVOKE AUTHORITY command, policy privilege class for all policy domains has been revoked from the indicated administrator.

System Action: None.

User Response: None.

ANR2085IRestricted policy privilege revoked for administrator administrator ID - policy domain domain name.

Explanation: In response to a REVOKE AUTHORITY command, restricted policy privilege for the specified policy domain has been revoked from the indicated administrator.

System Action: None.

User Response: None.

ANR2086IStorage privilege revoked for administrator administrator ID.

Explanation: In response to a REVOKE AUTHORITY command, storage privilege class for all storage pools has been revoked from the indicated administrator.

System Action: None.

User Response: None.

ANR2087IRestricted storage privilege revoked for administrator administrator ID - storage pool storage pool name.

Explanation: In response to a REVOKE AUTHORITY command, restricted storage privilege for the storage pool indicated has been revoked from the indicated administrator.

System Action: None.

User Response: None.

ANR2088IAnalyst privilege revoked for administrator administrator ID.

Explanation: In response to a REVOKE AUTHORITY command, analyst privilege class has been revoked from the indicated administrator.

System Action: None.

User Response: None.

ANR2089IOperator privilege revoked for administrator administrator ID.

Explanation: In response to a REVOKE AUTHORITY command, operator privilege class has been revoked from the indicated administrator.

System Action: None.

User Response: None.

ANR2090IActivity log retention period set to number of days days.

Explanation: The number of days that activity records are kept in the server activity log has been set to the value indicated with the SET ACTLOGRETENTION command.

System Action: None.

User Response: None.

ANR2091IAccounting parameter set to value.

Explanation: Accounting record generation has been turned on or off as indicated with the SET ACCOUNTING command.

System Action: None.

User Response: None.

ANR2092IPassword expiration period set to number of days days.

Explanation: The number of days that a password can be used before it must be changed has been set to the value indicated with the SET PASSEXP command.

System Action: None.

User Response: None.

ANR2093IRegistration parameter set to registration method.

Explanation: Backup-archive node registration has been set to the method indicated with the SET REGISTRATION command.

System Action: None.

User Response: None.

ANR2094IServer name set to server name.

Explanation: The name that the server displays and communicates to backup-archive nodes has been set to the value indicated with the SET SERVERNAME command.

System Action: None.

User Response: None.

ANR2095IAuthentication parameter set to value.

Explanation: The requirement for a node or administrator to enter a password when establishing a session with the server has been turned on or off as indicated with the SET AUTHENTICATION command.

System Action: None.

User Response: None.

ANR2096IServer now enabled for backup/archive client access.

Explanation: The server has been made available for use by backup-archive clients with the ENABLE command.

System Action: None.

User Response: None.

ANR2097IServer now disabled for backup/archive client access.

Explanation: The server has been made unavailable for use by backup-archive clients with the DISABLE command.

System Action: None.

User Response: None.

ANR2098ECommand: Invalid URL specification - url.

Explanation: The specified URL is too long.

System Action: The server ignores the command.

User Response: Reissue the command and enter a shorter URL value

ANR2099IAdministrative userid admininstrator name defined for OWNER access to node node name.

Explanation: An administrator with the specified name was created having OWNER access to the client node. This administrator is created for accessing the client node from an interactive interface.

System Action: None.

User Response: None.

ANR2100IActivity log process has started.

Explanation: The automatic server process that removes expired server activity log records has begun processing.

System Action: None.

User Response: None.

ANR2101IActivity log process stopped, activity log retention set to 0.

Explanation: A SET ACTLOGRETENTION command has set the retention period to zero days. As a result, activity logging stops.

System Action: The activity log process stops recording console output in the server activity log.

User Response: None.

ANR2102IActivity log pruning started: removing entries prior to date time.

Explanation: Server activity log records older than the date and time indicated are being removed from the activity log.

System Action: None.

User Response: None.

ANR2103IActivity log pruning completed: number of records records removed.

Explanation: All expired (older than the log archive retention value) server activity log records have been removed; the number of records deleted is shown.

System Action: None.

User Response: None.

ANR2104IActivity log process restarted - recovered from an insufficient space condition in the Log or Database.

Explanation: The process that records data in the server activity log has failed because of insufficient space in the server recovery log or database; space is now available and the process is again recording data.

System Action: Activity logging resumes.

User Response: None.

ANR2105WCommand: Node was registered in excess of license terms - node registration will fail after 120% of the licensed quantity of nodes have been registered.

Explanation: The server has detected the addition of a node in excess of the terms under which the server is licensed. The REGISTER NODE command will fail after 120% of the licensed number of nodes have been registered.

System Action: Server operation continues.

User Response: Use the QUERY LICENSE command to determine the license terms that are no longer in compliance. You may remove nodes to reduce the number of registered nodes or purchase additional client node connections. If additional nodes have been purchased, issue the AUDIT LICENSES command to resynchronize the server configuration with license terms.

ANR2106IServer HALT command: Quiescing database update activity.

Explanation: The server is quiescing transactions that update the database so that the database is in a consistent state when the server is halted. This action occurs when HALT QUIESCE is specified to halt the server with the database in a consistent state.

System Action: When database update transaction activity has been stopped, the server program ends.

User Response: None.

ANR2107IServer HALT command: Database update activity is now quiesced.

Explanation: The server has stopped all database update transaction activity. This action occurs when HALT QUIESCE is specified to halt the server with the database in a consistent state.

System Action: The server program ends.

User Response: None.

ANR2108IServer HALT command: Reattempting to quiesce database update activity.

Explanation: The server is quiescing transactions that update the database so that the database is in a consistent state when the server is halted. The previous attempt at quiescing database activity failed because of the current transaction load on the server. The quiesce operation is being reattempted. This action occurs when HALT QUIESCE is specified to halt the server with the database in a consistent state.

System Action: When database update transaction activity has been stopped, the server program ends.

User Response: None.

ANR2109IServer HALT command: Database update transaction activity could not be successfully quiesced.

Explanation: After repeated attempts, server database update transaction activity could not be quiesced. The server is not halted with the HALT QUIESCE command. Attempts to quiesce database update transaction activity can fail if heavy transaction load is on the server when a HALT QUIESCE command is entered.

System Action: Server operation continues.

User Response: You may disable the server, cancel all client sessions accessing the server, cancel all processes, and reenter the HALT QUIESCE command to stop server processing. The HALT command may also be used to stop server processing without quiescing database transaction update activity. Server recovery logic will be used when the server is restarted to reconcile database transaction activity.

ANR2110ICommand started as process process ID.

Explanation: A background process has been started to service the command command. The background process is defined as process process ID.

System Action: The server processes the indicated command.

User Response: To query the progress of the background process, use the QUERY PROCESS command. To cancel the background process, use the CANCEL PROCESS command. Use the process ID number to specify this process.

ANR2111WCommand: No data to process.

Explanation: The indicated command does not have any data to process. This can occur if the command specifies an empty volume or pool. The command ends without starting a background process.

System Action: None.

User Response: None.

ANR2112ECommand: Volume volume name is not in a primary storage pool.

Explanation: The command indicated specifies the name of a volume that does not belong to a primary storage pool. The command syntax requires that a volume in a primary storage pool be specified.

System Action: The server does not process the command.

User Response: Reissue the command with a volume in a primary pool.

ANR2113ECommand: Volume volume name does not belong to the same storage pool (storage pool name) as previously listed volumes.

Explanation: The indicated command accepts a list of one or more volumes which belong to the same storage pool. The named volume does not belong to the same storage pool as the previously listed volumes.

System Action: The server does not process the command.

User Response: Issue the command with a list of volumes that belong to the same storage pool.

ANR2114ICommand: Access mode for volume volume name updated to "destroyed".

Explanation: A RESTORE VOLUME command has updated the access mode of the indicated volume to destroyed.

System Action: Restore processing continues.

User Response: None.

ANR2115ECommand: Access mode for volume volume name cannot be changed to "destroyed" - volume is still online.

Explanation: A RESTORE VOLUME command cannot change the access mode of the indicated volume to destroyed because the volume is still online.

System Action: The server does not process the command.

User Response: Issue the VARY OFFLINE command, and reissue the RESTORE VOLUME command.

ANR2116ECommand: Access mode for volume volume name cannot be changed to "destroyed" - volume does not belong to a primary storage pool.

Explanation: The access mode for the indicated volume cannot be changed to destroyed because the volume does not belong to a primary storage pool.

System Action: The access mode for this volume is not changed.

User Response: None.

ANR2117ECommand: Access mode for volume volume name cannot be changed to "offsite" - volume either does not belong to a copy storage pool or from a device class of DEVTYPE=SERVER.

Explanation: The access mode for the indicated volume cannot be changed to offsite because the volume either does not belong to a copy storage pool or is of a device class with a DEVTYPE of SERVER.

System Action: The access mode for this volume is not changed.

User Response: None.

ANR2118EStorage pool storage pool name specified on the MOVE DATA command is not a valid poolname and or pooltype for volume volume name.

Explanation: If the volume belongs to a primary storage pool, then the storage pool specified must also be a primary storage pool. If the volume belongs to a copy storage pool, then the specified storage pool must be the same storage pool as that of the volume.

System Action: The MOVE DATA process fails.

User Response: Provide a valid primary storage pool name if the volume belongs to a primary storage pool. If the volume belongs to a copy storage pool, remove the storage pool name from the command.

ANR2119IThe Option option has been changed in the options file.

Explanation: The option is updated in the server options file.

System Action: Server continues.

User Response: None.

ANR2120ECommand: Invalid platform name - platform name.

Explanation: The command shown specifies an invalid platform name.

System Action: The server does not process the command.

User Response: Reissue the command with a valid platform name.

ANR2121WATTENTION: More than megabytes changed MB of the database has changed and the last database backup was more than hours name hours ago. Use the BACKUP DB command to provide for database recovery.

Explanation: The server issues this warning when a significant amount of database change activity has occurred and the server database has not been backed up.

System Action: Server operation continues.

User Response: To provide for server database recovery should a hardware or software problem affect your database, use the BACKUP DB command to back up the database.

ANR2122Ecommand name: The DOMAINS parameter cannot be specified when the NODES parameter is specified.

Explanation: Both the NODES and DOMAINS parameters were specified. The NODES parameter may be specified, or the DOMAINS parameter may be specfied, but both should not be specified at the same time.

System Action: The command fails.

User Response: Reenter the command specifying either the NODES parameter or the DOMAINS parameter, but not both.

ANR2123Ecommand name: The NODES parameter cannot be specified when the DOMAINS parameter is specified.

Explanation: Both the NODES and DOMAINS parameters were specified. The NODES parameter may be specified, or the DOMAINS parameter may be specfied, but both should not be specified at the same time.

System Action: The command fails.

User Response: Reenter the command specifying either the NODES parameter or the DOMAINS parameter, but not both.

ANR2124Ecommand name: Invalid Client authority specified: authority.

Explanation: An invalid client authority was specified in a GRANT AUTHORITY or REVOKE AUTHORITY command when the CLASS=NODE parameter was specified.

System Action: The command fails.

User Response: Reenter the command specifying a valid client authority.

ANR2125Icommand name: Administrator administrator name was granted OWNER authority for client client name.

Explanation: The named administrator was granted OWNER authority over the named client node as the result of a GRANT AUTHORITY command.

System Action: Processing continues.

User Response: None.

ANR2126Icommand name: Administrator administrator name was granted ACCESS authority for client client name.

Explanation: The named administrator was granted ACCESS authority over the named client node as the result of a GRANT AUTHORITY command.

System Action: Processing continues.

User Response: None.

ANR2127Icommand name: Owner authority for node client node was revoked for administrator administrator.

Explanation: OWNER authority over the named client node was revoked from the named administrator as a result of a REVOKE AUTHORITY command.

System Action: Processing continues.

User Response: None.

ANR2128Icommand name: Access authority for node client node was revoked for administrator administrator.

Explanation: ACCESS authority over the named client node was revoked from the named administrator as a result of a REVOKE AUTHORITY command.

System Action: Processing continues.

User Response: None.

ANR2129IAdministrative userid admininstrator name defined ONLY for authority over node node name has been removed.

Explanation: The specified administrator has been removed because the client node was removed and the administrator onyly had OWNER access to the specified node.

System Action: None.

User Response: None.

ANR2130SEarly Product Version has Expired. Server is HALTing.

Explanation: This server is pre-release version of the server. The pre-release version's expiration date has been reached.

System Action: The server halts.

User Response: Install the product version of the server.

ANR2131IServer password set.

Explanation: The password that the server uses to allow other servers to communicate with it has been set, changed or removed with the SET SERVERPASSWORD command.

System Action: None.

User Response: None.

ANR2132IServer hladdress set to hladdress.

Explanation: The high level address that other servers use to communicate with this server has been set to the value indicated with the SET SERVERHLADDRESS command.

System Action: None.

User Response: None.

ANR2133IServer lladdress set to lladdress.

Explanation: The low level address that other servers use to communicate with this server has been set to the value indicated with the SET SERVERLLADDRESS command.

System Action: None.

User Response: None.

ANR2134IServer url set to url.

Explanation: The url that other servers use to communicate with this server has been set to the value indicated with the SET SERVERURL command.

System Action: None.

User Response: None.

ANR2135ICrossdefine set to state.

Explanation: The ability for another server to automatically define itself to this server has been turned on or off as indicated with the SET CROSSDEFINE command.

System Action: None.

User Response: None.

ANR2136IAdministrator administrator name already has POLICY access for domain policy domain name.

Explanation: The named administrator already has POLICY authority over the named policy domain. An attempt to grant client authority over this domain is ignored.

System Action: The policy domain is skipped.

User Response: None.

ANR2137IAdministrator administrator name already has POLICY access for domain policy domain name to which node node name belongs.

Explanation: The named administrator already has POLICY authority over the named policy domain. An attempt to grant client authority for a client in this domain is ignored.

System Action: The client is skipped.

User Response: None.

ANR2138IMinimum password length set to length.

Explanation: The minimum length of a password a node or administrator may send to the server is indicated with the SET MINPWLENGTH command.

System Action: None.

User Response: None.

ANR2139ECommand: The value supplied for the minimum password length is not valid - length.

Explanation: A SET MINPWLENGTH command has been entered that specifies a value for the length is not valid. Valid values are from 0 to 64, inclusive.

System Action: The server does not process the command.

User Response: Reissue the command with a valid value.

ANR2140ECommand: Invalid activity log retention period - retention value.

Explanation: A SET ACTLOGRETENTION command has been entered that specifies an invalid log retention period.

System Action: The server does not process the command.

User Response: Reissue the command with a valid retention period.

ANR2141ECommand: Invalid password expiration period - days value.

Explanation: A SET PASSEXP command has been entered that specifies an invalid days value.

System Action: The server does not process the command.

User Response: Reissue the command with a password expiration period.

ANR2142ECommand: Invalid server name - server name.

Explanation: A SET SERVERNAME command has been entered that specifies an invalid server name.

System Action: The server does not process the command.

User Response: Reissue the command with a valid server name.

ANR2143ECommand: Invalid node name - node name.

Explanation: The command shown specifies an invalid node name.

System Action: The server does not process the command.

User Response: Reissue the command with a valid node name.

ANR2144ECommand: Invalid password - password.

Explanation: The command shown specifies an invalid node password.

System Action: The server does not process the command.

User Response: Reissue the command with a valid password.

ANR2145ECommand: Contact information exceeds maximum characters characters.

Explanation: A REGISTER NODE or REGISTER ADMIN command has been entered that specifies a contact information value that is too long. The maximum valid length is shown in the command.

System Action: The server does not process the command.

User Response: Reissue the command with less contact information.

ANR2146ECommand: Node node name is not registered.

Explanation: The command shown specifies a node that is not registered with the server.

System Action: The server does not process the command.

User Response: None.

ANR2147ECommand: Node node name is already registered.

Explanation: A REGISTER NODE command has been entered that specifies a node name already registered with the server.

System Action: The server does not process the command.

User Response: To register the node, reissue the command and specify a different node name.

ANR2148ECommand: Administrator administrator ID is not registered.

Explanation: The command shown specifies an administrator ID that is not registered with the server.

System Action: The server does not process the command.

User Response: None.

ANR2149ECommand: Administrator administrator ID is already registered.

Explanation: A REGISTER ADMIN command has been entered that specifies an administrator ID already registered with the server.

System Action: The server does not process the command.

User Response: To register the administrator, reissue the command and specify a different administrator ID.

ANR2150ECommand: Node node name is currently accessing the server.

Explanation: The command shown specifies a node that has an active session with the server.

System Action: The server does not process the command.

User Response: Reissue the command at a later time, or if necessary, cancel the current session and reissue the command.

ANR2151ECommand: Administrator administrator ID is currently accessing the server.

Explanation: An UPDATE ADMIN or REMOVE ADMIN command has been entered that specifies an administrator ID that is having an active session with the server.

System Action: The server does not process the command.

User Response: Reissue the command at a later time, or if necessary, cancel the current session and reissue the command.

ANR2152ECommand: Inventory references still exist for node node name.

Explanation: A REMOVE NODE command has been entered for a node for which the server is still storing backup or archive data, or both.

System Action: The server does not process the command.

User Response: To remove the node, delete all of its file spaces from the server and reissue the command.

ANR2153ECommand: Invalid file space name - filespace name.

Explanation: The specified server command has been entered with a file space name that is longer than allowed.

System Action: The server does not process the command.

User Response: Reissue the command with a valid file space name.

ANR2154ECommand: Invalid administrator name - administrator ID.

Explanation: The command shown specifies an invalid administrator ID.

System Action: The server does not process the command.

User Response: Reissue the command with a valid administrator ID.

ANR2155ECommand: Invalid privilege class - privilege class.

Explanation: A command specifies an invalid administrative privilege class.

System Action: The server does not process the command.

User Response: Reissue the command with a valid privilege class.

ANR2156ECommand: Administrator administrator ID has already been granted system privilege.

Explanation: A GRANT AUTHORITY command has been issued to grant system authority to an administrator ID that already has system authority.

System Action: The server does not process the command.

User Response: None.

ANR2157ECommand: Other privileges cannot be granted with system privilege.

Explanation: A GRANT AUTHORITY command has been issued to grant system authority to an administrator ID, and at the same time to grant other privileges.

System Action: The server does not process the command.

User Response: Reissue the GRANT AUTHORITY command specifying only system privilege class.

ANR2158ECommand: Policy domains cannot be specified for unrestricted policy administrator administrator ID.

Explanation: A REVOKE AUTHORITY command has been issued to revoke an administrator's policy authority over a specific policy domain, but the administrator has unrestricted policy authority.

System Action: The server does not process the command.

User Response: None.

ANR2159ECommand: Storage pools cannot be specified for unrestricted storage administrator administrator ID.

Explanation: A REVOKE AUTHORITY command has been issued to revoke an administrator's storage authority over a specific storage pool, but the administrator has unrestricted storage authority.

System Action: The server does not process the command.

User Response: None.

ANR2160ECommand: No new privileges granted to administrator administrator ID.

Explanation: A GRANT AUTHORITY command has been issued to grant authority to an administrator ID, but the administrator already has all privileges specified.

System Action: The server does not process the command.

User Response: None.

ANR2161ECommand: Only system privilege can be revoked for administrator administrator ID.

Explanation: A REVOKE AUTHORITY command has been issued to revoke one or more of an administrator's privileges, but the administrator has system authority.

System Action: The server does not process the command.

User Response: None.

ANR2162ECommand: No privileges revoked for administrator administrator ID.

Explanation: A REVOKE AUTHORITY command has been issued to revoke authority from an administrator ID, but the administrator does not have any of the privileges specified.

System Action: The server does not process the command.

User Response: None.

ANR2163ECommand: Command is invalid for administrator ID.

Explanation: The command specified cannot be issued for the server console. For instance, the server console administrator ID cannot be removed.

System Action: The server does not process the command.

User Response: None.

ANR2164ECommand: Command rejected - administrator ID is the only system administrator.

Explanation: A REMOVE ADMIN or REVOKE AUTHORITY command has been issued to remove or revoke the authority of the last administrator who had system authority.

System Action: The server does not process the command.

User Response: To remove or revoke this ID, grant system authority to another administrator ID before reissuing the command.

ANR2165ECommand: Invalid begin date - date.

Explanation: A QUERY ACTLOG command has been entered that specifies an invalid begin date as a search criteria.

System Action: The server does not process the command.

User Response: Reissue the command with a valid begin date.

ANR2166ECommand: Invalid begin time - time.

Explanation: A QUERY ACTLOG command has been entered that specifies an invalid begin time as a search criteria.

System Action: The server does not process the command.

User Response: Reissue the command with a valid begin time.

ANR2167ECommand: Invalid end date - date.

Explanation: A QUERY ACTLOG command has been entered that specifies an invalid end date as a search criteria.

System Action: The server does not process the command.

User Response: Reissue the command with a valid end date.

ANR2168ECommand: Invalid end time - time.

Explanation: A QUERY ACTLOG command has been entered that specifies an invalid end time as a search criteria.

System Action: The server does not process the command.

User Response: Reissue the command with a valid end time.

ANR2169ECommand: Invalid message number - message number.

Explanation: A QUERY ACTLOG command has been entered that specifies an invalid message number as a search criteria.

System Action: The server does not process the command.

User Response: Reissue the command with a valid message number.

ANR2170ECommand: Invalid message search string argument - search string.

Explanation: A QUERY ACTLOG command has been entered that specifies an invalid search string as a search criteria.

System Action: The server does not process the command.

User Response: Reissue the command with a valid search string.

ANR2171ECommand: Invalid time range - Begin: date time End: date time.

Explanation: A QUERY ACTLOG command has been entered that specifies an invalid beginning and ending date/time range. This error can occur when the beginning date/time is not before the ending date/time.

System Action: The server does not process the command.

User Response: Reissue the command with a valid date/time range.

ANR2172ECommand: No matching administrators.

Explanation: The command shown specified an administrator ID that does not match any administrator registered with the server.

System Action: The command is not executed.

User Response: If desired, reissue the command with a different administrator ID.

ANR2173ECommand: Location information exceeds maximum characters characters.

Explanation: A DEFINE or UPDATE VOLUME command has been entered that specifies a location information value that is too long. The maximum valid length is shown in the command.

System Action: The server does not process the command.

User Response: Reissue the command with less location information.

ANR2174EAdministrator administrator ID is not registered. Schedule schedule name is not processed and is marked as failed.

Explanation: The command shown specifies an administrator ID that is not registered with the server. The schedule and related command are not processed.

System Action: The server does not process the command.

User Response: Update the command schedule with a valid administrator ID which has the proper authority to execute the scheduled command.

ANR2175IInvalid password limit set to password attempts limit attempts.

Explanation: The maximum number of consecutive invalid passwords a node or administrator may send to the server is indicated with the SET INVALIDPWLIMIT command.

System Action: None.

User Response: None.

ANR2176ECommand: The value supplied for the invalid password attempts limit is not valid - password attempts limit.

Explanation: A SET INVALIDPWLIMIT command has been entered that specifies a value for the consecutive invalid password attempts limit that is not valid. Valid values are from 0 to 9999, inclusive.

System Action: The server does not process the command.

User Response: Reissue the command with a valid value.

ANR2177Inode/admin name has count invalid sign-on attempts. The limit is limit.

Explanation: The server detected an invalid password for the specified node during sign-on processing. The node currently has sent count consecutive invalid passwords. The maximum allowed is limit. The server will lock the node when limit is reached.

System Action: The node or administrator session will be refused.

User Response: Before the client node is permitted to access the server, a properly authorized administrator must unlock the node or administrator with the UNLOCK NODE or UNLOCK ADMIN command.

ANR2178Enode/admin name has been locked. Invalid sign-on attempt limit (limit) reached.

Explanation: The specified node has been locked by the server. The limit for consecutive invalid passwords has been reached.

System Action: The node or administrator session will be refused.

User Response: Before the client node is permitted to access the server, a properly authorized administrator must unlock the node or administrator with the UNLOCK NODE or UNLOCK ADMIN command.

ANR2179EAdministrator administrator should have been locked, but was not.

Explanation: The indicated administrator reached the limit for consecutive invalid passwords and should have been locked. If it were locked, there would be no means to execute commands requiring system authority.

System Action: The administrator session will be refused.

User Response: Sign-on again using the correct password.

ANR2180WUnable to update last access date for administrator administrator ID - insufficient recovery log space.

Explanation: While establishing an administrative session for the indicated ID, the server is unable to update the administrator's date of last access due to insufficient recovery log space.

System Action: The server establishes the administrative session, but the last access date is not updated.

User Response: An authorized administrator can issue the DEFINE LOGVOLUME command to add volumes for use by the log, and can issue the EXTEND LOG command to extend the size of the log so that the new volumes are used.

ANR2181WUnable to update last access date for administrator administrator ID - insufficient database space.

Explanation: While establishing an administrative session for the indicated ID, the server cannot update the administrator's date of last access due to insufficient database space.

System Action: The server establishes the administrative session, but the last access date is not updated.

User Response: An authorized administrator can issue the DEFINE DBVOLUME command to add volumes for use by the database, and can issue the EXTEND DB command to extend the size of the database so that the new volumes are used.

ANR2182WUnable to update last access date for administrator administrator ID - internal server error.

Explanation: While establishing an administrative session for the indicated ID, the server cannot update the administrator's date of last access due to a server internal error.

System Action: The server establishes the administrative session, but the last access date is not updated.

User Response: Examine the server messages issued prior to this message to determine the source of the error. Issue the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative.

ANR2183WDiagnosticID: Transaction transaction ID was aborted.

Explanation: An error was detected during transaction commit. This message should be preceded by other messages that give additional information about the failed transaction.

System Action: The activity that generated this error fails.

User Response: Check for additional messages and eliminate the condition that caused the failed transaction. If the error cannot be isolated and resolved, contact your service representative.

ANR2184WDiagnosticID: Transaction transaction ID was aborted for command command.

Explanation: An error was detected during transaction commit for the specified server command. This message should be preceded by other messages that give additional information about the failed transaction.

System Action: The activity that generated this error fails.

User Response: Check for additional messages and eliminate the condition that caused the failed transaction. If the error cannot be isolated and resolved, contact your service representative.

ANR2185WTransaction was aborted for command command.

Explanation: An error was detected during transaction commit. This message should be preceded by other messages that give additional information about the failed transaction.

System Action: The activity that generated this error fails.

User Response: Check for additional messages and eliminate the condition that caused the failed transaction. If the error cannot be isolated and resolved, contact your service representative.

ANR2186WTransaction was aborted for session session number for node node name (client platform).

Explanation: An error was detected during transaction commit. This message should be preceded by other messages that give additional information about the failed transaction.

System Action: The activity that generated this error fails.

User Response: Check for additional messages and eliminate the condition that caused the failed transaction. If the error cannot be isolated and resolved, contact your service representative.

ANR2187WTransaction was aborted for node/admin name.

Explanation: An error is detected during a transaction commit for the specified node or administrator name. This message should be preceded by other messages that give additional information about the failed transaction.

System Action: The activity that generated this error fails.

User Response: Check for additional messages and eliminate the condition that caused the failed transaction. If the error cannot be isolated and resolved, contact your service representative.

ANR2188WA Transaction was aborted. The activity is terminating.

Explanation: An error is detected during a transaction commit. This message should be preceded by other messages that give additional information about the failed transaction.

System Action: The activity that generated this error ends.

User Response: Check for additional messages and eliminate the condition that caused the failed transaction. If the error cannot be isolated and resolved, contact your service representative.

ANR2189WDiagnosticID: Transaction transaction ID was aborted for node/admin name.

Explanation: An error is detected during a transaction commit for the specified node or administrator name. This message should be preceded by other messages that give additional information about the failed transaction.

System Action: The activity that generated this error fails.

User Response: Check for additional messages and eliminate the condition that caused the failed transaction. If the error cannot be isolated and resolved, contact your service representative.

ANR2190Ecommand: Device class DISK cannot be specified for this command.

Explanation: The DEVCLASS value DISK cannot be specified for the command.

System Action: The command fails and server operation continues.

User Response: Reissue the command and specify a valid device class. Issue the QUERY DEVCLASS command for a list of valid device classes for the server.

ANR2191Ecommand: Volume list contains defined and undefined volumes.

Explanation: The list of volumes specified on the SALVAGE VOLUME command must all be defined to the server, or all not defined to the server.

System Action: The command fails and server operation continues.

User Response: Reissue the command and specify a valid list of volumes.

ANR2192ECommand: Unable to start background process.

Explanation: The server command processor is not able to start a background process to perform the command command.

System Action: The command process ends and server operation continues.

User Response: Allocate additional storage to the server. For details, issue HELP MEMORY to display the information online or see "Appendix A. Allocating Additional Server Memory".

ANR2193ECommand: Invalid option set name - option set name.

Explanation: The command shown specifies an invalid option set name.

System Action: The server does not process the command.

User Response: Reissue the command with a valid option set name.

ANR2194ECommand: Invalid option set description - too long.

Explanation: The command shown specifies an invalid description. The description is too long.

System Action: The server does not process the command.

User Response: Reissue the command with a valid description.

ANR2195ECommand: Invalid option sequence number - option sequence number name.

Explanation: The command shown specifies an invalid option sequence number.

System Action: The server does not process the command.

User Response: Reissue the command with a valid option sequence number.

ANR2196ECommand: Option name and/or Option value is missing for define.

Explanation: The specified DEFINE command has been entered, but no attributes have been specified for the definition.

System Action: The server does not process the command.

User Response: Reissue the DEFINE command with one or more attributes to be defined

ANR2197ECommand: The value supplied for the WEB authentication time out is not valid - time-out value.

Explanation: A SET WEBAUTHTIMEOUT command has been entered that specifies a value that is not valid. Valid values are from 0 to 9999, inclusive.

System Action: The server does not process the command.

User Response: Reissue the command with a valid value.

ANR2198ICommand: Web authentication time-out set to time-out value minutes.

Explanation: The time-out value that determines how often WEB browser administrative users need to re-authenticate with the server has been set with the SET WEBAUTHTIMEOUT command to the value displayed.

System Action: None.

User Response: None.

ANR2199IPassword expiration period for node node name set to number of days days.

Explanation: The number of days that the node's password can be used before it must be changed has been set to the value indicated with the SET PASSEXP command.

System Action: None.

User Response: None.

ANR2200IStorage pool storage pool name defined (device class device class name).

Explanation: A DEFINE STGPOOL command has created the storage pool indicated of the device class shown.

System Action: None.

User Response: None.

ANR2201IStorage pool storage pool name deleted.

Explanation: A DELETE STGPOOL command has deleted the storage pool indicated.

System Action: None.

User Response: None.

ANR2202IStorage pool storage pool name updated.

Explanation: An UPDATE STGPOOL command has updated the storage pool indicated.

System Action: None.

User Response: None.

ANR2203IDevice class device class name defined.

Explanation: A DEFINE DEVCLASS command has created the device class indicated.

System Action: None.

User Response: None.

ANR2204IDevice class device class name deleted.

Explanation: A DELETE DEVCLASS command has deleted the device class indicated.

System Action: None.

User Response: None.

ANR2205IDevice class device class name updated.

Explanation: An UPDATE DEVCLASS command has updated the device class indicated.

System Action: None.

User Response: None.

ANR2206IVolume volume name defined in storage pool storage pool name (device class device class name).

Explanation: A DEFINE VOLUME command has defined the volume indicated in the storage pool shown that belongs to the device class shown.

System Action: None.

User Response: None.

ANR2207IVolume volume name updated.

Explanation: An UPDATE VOLUME command has updated the volume indicated.

System Action: None.

User Response: None.

ANR2208IVolume volume name deleted from storage pool storage pool name.

Explanation: The volume indicated has been deleted by one of the following:

System Action: None.

User Response: None.

ANR2209WVolume volume name contains no data.

Explanation: The AUDIT VOLUME or MOVE DATA command entered specifies a volume that contains no data.

System Action: The server does not process the command.

User Response: None.

ANR2210IVary online initiated for disk volume volume name.

Explanation: A VARY ONLINE command for the volume shown is being processed, and if no errors occur the volume will be varied online.

System Action: None.

User Response: None.

ANR2211IVary offline initiated for disk volume volume name.

Explanation: A VARY OFFLINE command for the volume shown is being processed and, if no errors occur, the volume will be varied offline.

System Action: None.

User Response: None.

ANR2212ICommand: No volumes updated.

Explanation: An UPDATE VOLUME command has been entered, but no objects were updated.

System Action: None.

User Response: None.

ANR2213ICommand: Storage pool storage pool name renamed to storage pool name.\n

Explanation: A RENAME STGPOOL command has been entered. The rename of the storage pool was successful.

System Action: None.

User Response: None.

ANR2214ECommand: Invalid backup set name - backup set name.

Explanation: The command shown specifies an invalid backup set name.

System Action: The command fails.

User Response: Reissue the command with a valid backup set name.

ANR2215ECommand: Description text is too long.

Explanation: The specified description text is too long for a command that allows description text to be specified.

System Action: The command fails

User Response: Reissue the command specifying a shorter description

ANR2216ECommand: Device class is must be a sequential device class.

Explanation: The device class specified on the command is not a sequential device class.

System Action: The command fails

User Response: Reissue the command specifying the name of a sequential device class

ANR2217ECommand: Invalid backup set retention period - retention value.

Explanation: Server processing for the backup set command command fails because the value (retention value) specified for the RETENTION parameter is not valid.

System Action: The command fails

User Response: Reissue the command specifying a valid RETENTION value.

ANR2218ECommand: A device class must be specified.

Explanation: The DEVCLASS parameter is not specified in the command command name. A DEVCLASS value must be specified.

System Action: The command fails.

User Response: Reissue the command specifying a valid device class. Issue the QUERY DEVCLASS command for a list of valid device classes for the server.

ANR2219IDiscard Data process ended for volume volume name - volume is not deleted from storage pool storage pool name because the volume access is offsite.

Explanation: The process that deleted data for the volume shown has ended, but the volume has not been deleted because the volume access is marked as offsite.

System Action: None.

User Response: To delete the volume, change the volume access to readwrite, readonly, or unavailable.

ANR2220WThis command will delete volume volume name from its storage pool after verifying that the volume contains no data.

Explanation: A DELETE VOLUME command with the Discarddata=No option has been entered.

System Action: The system asks whether you wish to continue with the command.

User Response: To process the DELETE VOLUME command, enter 'Y' to continue or 'N' to stop the process.

ANR2221WThis command will result in the deletion of all inventory references to the data on volume volume name, thereby rendering the data unrecoverable.

Explanation: A DELETE VOLUME command with the Discarddata=Yes option has been entered.

System Action: The system asks whether you wish to continue with the command.

User Response: To process the DELETE VOLUME command, enter 'Y' to continue or 'N' to stop the process.

ANR2222IDiscard Data process started for volume volume name (process ID process ID).

Explanation: As a result of a DELETE VOLUME command with the Discarddata=Yes option, the process whose ID is displayed has begun to delete the data on the volume shown.

System Action: The server deletes the data on the volume.

User Response: None.

ANR2223IDiscard Data process ended for volume volume name - volume deleted from storage pool storage pool name.

Explanation: The process that deleted data for the volume shown has ended, and the volume has been deleted.

System Action: None.

User Response: None.

ANR2224WDiscard Data process terminated for volume volume name - process canceled.

Explanation: The process that was deleting data for the volume shown, in preparation for deleting the volume, has been canceled.

System Action: The server does not delete the volume.

User Response: None.

ANR2225WDiscard Data process terminated for volume volume name - volume still contains data.

Explanation: The process that was deleting data for the volume shown, in preparation for deleting the volume, has ended. However, the volume contains data.

System Action: The server does not delete the volume.

User Response: Contact your service representative.

ANR2226WDiscard data process terminated for volume volume name - sufficient recovery log space is not available.

Explanation: The process that was deleting data for the volume shown, in preparation for deleting the volume, has ended due to a shortage of recovery log space.

System Action: The server does not delete the volume.

User Response: An authorized administrator can issue the DEFINE LOGVOLUME command to add volumes for use by the log, and can issue the EXTEND LOG command to extend the size of the log so that the new volumes are used.

ANR2227WDiscard data process terminated for volume volume name - sufficient memory is not available.

Explanation: The process that was deleting data for the volume shown, in preparation for deleting the volume, has ended due to a shortage of memory.

System Action: The server does not delete the volume.

User Response: Allocate additional storage to the server. For details, issue HELP MEMORY to display the information online or see "Appendix A. Allocating Additional Server Memory".

ANR2228WDiscard data process terminated for volume volume name - lock conflict detected.

Explanation: The process that was deleting data for the volume shown, in preparation for deleting the volume, has ended due to a locking conflict.

System Action: The server does not delete the volume.

User Response: Reissue the command at a later time. If this problem persists, contact your service representative.

ANR2229WDiscard data process terminated for volume volume name - internal server error detected.

Explanation: The process that was deleting data for the volume shown, in preparation for deleting the volume, has ended due to a server internal error.

System Action: The server does not delete the volume

User Response: Contact your service representative.

ANR2232WThis command will move all of the data stored on volume volume name to other volumes within the same storage pool; the data will be inaccessible to users until the operation completes.

Explanation: A move data has been entered that will move data from the indicated volume to other volumes in the same storage pool. While the data is being moved, it will not be available to users.

System Action: The administrator is asked whether to continue.

User Response: Enter 'Y' to continue with the command or 'N' to end the process.

ANR2233WThis command will move all of the data stored on volume volume name to other volumes in storage pool storage pool name; the data will be inaccessible to users until the operation completes.

Explanation: A move data has been entered that will move data from the indicated volume to volumes in the storage pool shown. While the data is being moved it will not be available to users.

System Action: The administrator is asked whether to continue.

User Response: Enter 'Y' to continue with the command or 'N' to end the process.

ANR2234WThis command will halt the server; if the command is issued from a remote client, it may not be possible to restart the server from the remote location.

Explanation: A HALT command has been entered.

System Action: The administrator is asked whether to continue.

User Response: Enter 'Y' to halt the server or 'N' to leave the server activated.

ANR2235WThis command will remove administrator adminName. This administrator has defined or updated schedules. Removing this authority WILL cause these schedules to fail.

Explanation: A REMOVE ADMINISTRATOR command has been entered for an administrator that owns administrative schedules. If you confirm that you want to proceed with this command, the schedules owned by this administrator will fail when executed in the future.

System Action: The system asks whether you wish to continue with the command.

User Response: To process the REMOVE ADMINISTRATOR command, enter 'Y' to continue or 'N' to stop the process. To deal with schedules owneed by the administratirr, use the QUERY SCHEDULE command OR an SQL SELECT statement on the ADMIN_SCHEDULES table to determine which schedules were last updated by the administrator. Use the UPDATE SCHEDULE command to update those schedules under an administrator that has authority to execute them, or use the DELETE SCHEDULE command to remove the schedules.

ANR2236WThis command has removed administrator adminName. This administrator has defined or updated schedules. This WILL cause these schedules to fail in the future.

Explanation: A REMOVE ADMINISTRATOR command has been entered and the administrator removed owns administrative schedules. The schedules will fail when executed in the future because they do not belong to a valid administrator.

System Action: The system removes the administrator.

User Response: Use the QUERY SCHEDULE command OR an SQL SELECT statement on the ADMIN_SCHEDULES table to determine which schedules were last updated by the administrator. Use the UPDATE SCHEDULE command to update those schedules under an administrator that has authority to execute them, or use the DELETE SCHEDULE command to remove the schedules.

ANR2237WThis command has revoked privileges for administrator adminName. This administrator has defined or updated schedules. This may cause these schedules to fail in the future.

Explanation: A REVOKE AUTHORITY command has been entered.

System Action: The system removes the authority.

User Response: None.

ANR2238WThis command will result in the deletion of all inventory references to the data on filespaces that match the pattern filespace name for node node name, whereby rendering the data unrecoverable.

Explanation: A DELETE FILESPACE command has been entered.

System Action: The system asks whether you wish to continue with the command.

User Response: To process the DELETE FILESPACE command, enter 'Y'; otherwise, enter 'N'.

ANR2239WThis command will revoke privileges for administrator adminName. This administrator has defined or updated schedules. Revoking this authority may cause schedules to fail.

Explanation: A REVOKE AUTHORITY command has been entered.

System Action: The system asks whether you wish to continue with the command.

User Response: To process the REVOKE AUTHORITY command, enter 'Y' to continue or 'N' to stop the process.

ANR2240IDatabase volume volume name defined.

Explanation: A DEFINE DBVOLUME command has defined the database volume indicated.

System Action: None.

User Response: None.

ANR2241IDatabase volume copy volume name defined.

Explanation: A DEFINE DBCOPY command has defined the database volume indicated.

System Action: None.

User Response: None.

ANR2242IDatabase volume copy volume name defined; synchronization process started (process ID process ID).

Explanation: A DEFINE DBCOPY command has added the volume shown as a database copy volume. The process whose ID is displayed will copy data to the new volume to synchronize it with existing volumes.

System Action: None.

User Response: None.

ANR2243IDatabase volume volume name deleted.

Explanation: A DELETE DBVOLUME command has deleted the database volume indicated.

System Action: None.

User Response: None.

ANR2244IDelete process initiated for database volume volume name (process id process ID).

Explanation: In response to a DELETE DBVOLUME command, the process with the process ID shown has been started to delete the volume.

System Action: None.

User Response: None.

ANR2245IDatabase volume volume name varied online.

Explanation: A VARY ONLINE command has put the database volume indicated into an online state.

System Action: None.

User Response: None.

ANR2246IVary online process initiated for database volume volume name (process ID process ID).

Explanation: In response to a VARY ONLINE command, the process with the process ID shown has been started to vary on the database volume indicated.

System Action: None.

User Response: None.

ANR2247IDatabase volume volume name varied offline.

Explanation: A VARY OFFLINE command has put the indicated database volume into an offline state.

System Action: None.

User Response: None.

ANR2248IDatabase assigned capacity has been extended.

Explanation: An EXTEND DB command has increased the storage capacity of the database.

System Action: None.

User Response: None.

ANR2249IDatabase extension process initiated (process ID process ID).

Explanation: In response to an EXTEND DB command, the process with the process ID shown has been started to extend the database.

System Action: None.

User Response: None.

ANR2250IDatabase assigned capacity has been reduced.

Explanation: A REDUCE DB command has decreased the storage capacity of the database.

System Action: None.

User Response: None.

ANR2251IDatabase reduction process initiated (process ID process ID).

Explanation: In response to a REDUCE DB command, the process with the process ID shown has been started to reduce the database.

System Action: None.

User Response: None.

ANR2252WDatabase volume copy volume name is larger than volume volume name by count megabyte(s).

Explanation: A DEFINE DBCOPY command has defined a database copy volume whose size is larger than the volume it mirrors by the amount shown.

System Action: The excess capacity is ignored.

User Response: None.

ANR2253WThe database volume copy to be defined (volume name) is larger than volume volume name; use of the volume will result in count megabyte(s) of unusable space.

Explanation: A DEFINE DBCOPY command is attempting to define a database copy volume whose size is larger than the volume it mirrors by the amount shown. The excess capacity would not be used.

System Action: The administrator is asked whether to continue.

User Response: Enter 'Y' to define the copy, 'N' otherwise.

ANR2254ECommand: The VOLUMENAMES parameter must be specified when SCRATCH=NO is specified.

Explanation: The SCRATCH parameter is specified as NO for the command Command but the VOLUMENAMES parameter is not specified. When scratch volumes are not allowed, the VOLUMENAMES parameter must be specified to indicate the volumes that can be used for the command.

System Action: The command fails.

User Response: Reissue the command and specify a valid VOLUMENAMES parameter.

ANR2255ECommand: The VOLUMENAMES parameter must be specified.

Explanation: The VOLUMENAMES parameter must be specified to indicate the volumes that can be used for the command.

System Action: The command fails.

User Response: Reissue the command and specify a valid VOLUMENAMES parameter.

ANR2256ECommand: The RETENTION parameter must be specified.

Explanation: The RETENTION parameter must be specified to indicate the retention period to be used for the command.

System Action: The command fails.

User Response: Reissue the command and specify a valid RETENTION parameter.

ANR2257ECommand: Administrator administrator name is not authorized to issue this command for node node name.

Explanation: The specified administrator has entered the indicated command, but this administrator does not have the proper authority necessary to run the command for the indicated node. Note: This message can be issued as a result of the server option REQSYSAUTHOUTFILE YES being in effect.

System Action: The server does not process the command for the indicated node. If multiple nodes were specified on the command, the server may continue processing the command for the other nodes.

User Response: Examine previous messages for any additional information. Issue the command from a properly authorized administrator ID, or contact the system administrator to have additional authority granted to the current administrator ID.

ANR2258ECommand: Invalid summary retention period - retention value.

Explanation: A SET SUMMARYRETENTION command has been entered that specifies an invalid retention period.

System Action: The server does not process the command.

User Response: Reissue the command with a valid retention period.

ANR2259ISummary retention period set to number of days days.

Explanation: The number of days that activity sumary records are kept in the server database has been set to the value indicated with the SET SUMMARYRETENTION command.

System Action: None.

User Response: None.

ANR2260IRecovery log volume volume name defined.

Explanation: A DEFINE LOGVOLUME command has defined the recovery log volume indicated.

System Action: None.

User Response: None.

ANR2261IRecovery log volume copy volume name defined.

Explanation: A DEFINE LOGCOPY command has defined the recovery log volume indicated.

System Action: None.

User Response: None.

ANR2262IRecovery log volume copy volume name defined; synchronization process started (process ID process ID).

Explanation: A DEFINE LOGCOPY command has added the volume shown as a log copy volume. The process whose ID is displayed copied data to the new volume to synchronize it with existing volumes.

System Action: None.

User Response: None.

ANR2263IRecovery log volume volume name deleted.

Explanation: A DELETE LOGVOLUME command has removed the recovery log volume indicated.

System Action: None.

User Response: None.

ANR2264IDelete process initiated for recovery log volume volume name (process id process ID).

Explanation: In response to a DELETE LOGVOLUME command, the process with process ID shown has been started to delete the volume.

System Action: None.

User Response: None.

ANR2265IRecovery log volume volume name varied online.

Explanation: A VARY ONLINE command has put the recovery log volume indicated into an online state.

System Action: None.

User Response: None.

ANR2266IVary online process initiated for recovery log volume volume name (process ID process ID).

Explanation: In response to a VARY ONLINE command, the process with process ID shown has been started to vary on the recovery log volume indicated.

System Action: None.

User Response: None.

ANR2267IRecovery log volume volume name varied offline.

Explanation: A VARY OFFLINE command has put the recovery log volume indicated into an offline state.

System Action: None.

User Response: None.

ANR2268IRecovery log assigned capacity has been extended.

Explanation: An EXTEND LOG command has increased the storage capacity of the recovery log.

System Action: None.

User Response: None.

ANR2269IRecovery log extension process initiated (process ID process ID).

Explanation: In response to an EXTEND LOG command, the process with the process ID shown has been started to extend the recovery log.

System Action: None.

User Response: None.

ANR2270IRecovery log assigned capacity has been reduced.

Explanation: A REDUCE LOG command has decreased the storage capacity of the recovery log.

System Action: None.

User Response: None.

ANR2271IRecovery log reduction process initiated (process ID process ID).

Explanation: In response to a REDUCE LOG command, the process with the process ID shown has been started to reduce the recovery log.

System Action: None.

User Response: None.

ANR2272WRecovery log volume copy volume name is larger than volume volume name by count megabytes.

Explanation: A DEFINE LOGCOPY command has defined a recovery log copy volume whose size is larger than the volume it mirrors by the amount shown.

System Action: The excess capacity is ignored.

User Response: None.

ANR2273WThe recovery log volume copy to be defined (volume name) is larger than volume volume name; use of the volume will result in count megabytes of unusable space.

Explanation: A DEFINE LOGCOPY command is attempting to define a recovery log copy volume whose size is larger than the volume it mirrors by the amount shown. The excess capacity would not be used.

System Action: The administrator is asked whether to continue.

User Response: Enter 'Y' to define the copy or 'N' to stop the process.

ANR2274IData Base Space trigger defined and enabled.

Explanation: The data base space trigger has been defined with a DEFINE SPACETRIGGER command. The percentage of utilization specified with the FULLPCT parameter is used to automatically expand the data base.

System Action: None.

User Response: None.

ANR2275IData Base Space trigger defined, but is disabled.

Explanation: A data base space trigger has been defined, but because the space expansion percentage is currently set to 0, the space trigger is disabled.

System Action: None.

User Response: To activate the space trigger, use the UPDATE SPACETRIGGER command to set the space expansion percentage to a value greater than 0.

ANR2276IData Base Space trigger updated and enabled.

Explanation: An UPDATE SPACETRIGGER command has successfully completed for the data base space trigger. The updated parameters specified on the command are used to automatically trigger space expansion for the data base.

System Action: None.

User Response: None.

ANR2277IData Base Space trigger updated, but disabled.

Explanation: An UPDATE SPACETRIGGER command has successfully completed for the data base space trigger. However, the space expansion percentage is currently set to 0, which disables the space trigger.

System Action: None.

User Response: To activate the space trigger, use the UPDATE SPACETRIGGER command with the SPACEexpansion parameter to set a value greater than zero.

ANR2278IDatabase Space trigger deleted.

Explanation: A DELETE SPACETRIGGER command has successfully completed for the data base space trigger. Space expansions are no longer triggered automatically for the database.

System Action: None.

User Response: None.

ANR2279IRecovery Log Space trigger defined and enabled.

Explanation: The recovery log space trigger has been defined with a DEFINE SPACETRIGGER command. The percentage of utilization specified with the FULLPCT parameter is used to automatically expand the recovery log.

System Action: None.

User Response: None.

ANR2280IFull database backup started as process process ID.

Explanation: A background process was started to backup the contents of the database. The full database backup process was assigned the process ID shown.

System Action: The database backup process starts and server operation continues.

User Response: The administrator may query the status of the database backup process by using the QUERY PROCESS command, or cancel the process with the CANCEL PROCESS command.

ANR2281IIncremental database backup started as process process ID.

Explanation: A background process was started to backup the contents of the database. The incremental database backup process was assigned the process ID shown.

System Action: The database backup process starts and server operation continues.

User Response: The administrator may query the status of the database backup process by using the QUERY PROCESS command, or cancel the process with the CANCEL PROCESS command.

ANR2282IDatabase backup trigger defined and enabled.

Explanation: A database backup trigger has been defined with a DEFINE DBBACKUPTRIGGER command. The percentage of recovery log utilization specified with the LOGFULLPCT parameter is used to automatically trigger database backups.

System Action: None.

User Response: None.

ANR2283IDatabase backup trigger defined, but is disabled.

Explanation: A database backup trigger has been defined, but because the recovery log mode is currently set to NORMAL, the database backup trigger is disabled. Database backups can only be triggered when the log mode is set to ROLLFORWARD with a SET LOGMODE command.

System Action: None.

User Response: To activate the database backup trigger, use the SET LOGMODE ROLLFORWARD command.

ANR2284IDatabase backup trigger updated and enabled.

Explanation: An UPDATE DBBACKUPTRIGGER command has successfully completed. The updated parameters specified on the command are used to automatically trigger database backups.

System Action: None.

User Response: None.

ANR2285IDatabase backup trigger updated, but disabled.

Explanation: An UPDATE DBBACKUPTRIGGER command has successfully completed, but because the recovery log mode is currently set to NORMAL, the database backup trigger is disabled. Database backups can only be triggered when the log mode is set to ROLLFORWARD with a SET LOGMODE command.

System Action: None.

User Response: To activate the database backup trigger, use the SET LOGMODE ROLLFORWARD command.

ANR2286IDatabase backup trigger deleted.

Explanation: A DELETE DBBACKUPTRIGGER command has successfully completed. Database backups are no longer triggered automatically by recovery log utilization.

System Action: None.

User Response: None.

ANR2287ISnapshot database backup started as process process ID.

Explanation: A background process was started to backup the contents of the database. The snapshot database backup process was assigned the process id shown.

System Action: The database backup process starts and server operation continues.

User Response: The administrator may query the started process by using the QUERY PROCESS command, or may cancel the process using the CANCEL PROCESS command.

ANR2288ISubfile set to state.

Explanation: The SET SUBFILE command has been used to specify whether this server will allow clients to back up subfiles. If a value of CLIENT is specified, clients are given the option of backing up subfiles. If a value of NO is specified, clients are not allowed to back up subfiles.

System Action: None.

User Response: None.

ANR2290WChanging the log mode to NORMAL will prevent roll-forward recovery.

Explanation: The system has determined that changing the recovery log mode from ROLLFORWARD to NORMAL mode will cause the log records being kept for ROLLFORWARD and single database volume restore processing to be discarded. Without these log records, only point-in-time database restores can be performed.

System Action: The administrator is asked whether to continue.

User Response: Enter 'Y' to change the LOGMODE, 'N' otherwise.

ANR2291WChanging the log mode to NORMAL will disable the database backup trigger.

Explanation: Changing the recovery log mode from ROLLFORWARD to NORMAL disables the setting specified in the DEFINE DBBACKUPTRIGGER command. Database backups can only be triggered when the recovery log mode is set to ROLLFORWARD with the SET LOGMODE command.

System Action: The administrator is asked whether to continue.

User Response: Enter 'Y' to change the log mode, 'N' otherwise. Responding 'Y' does not delete the DEFINE DBBACKUPTRIGGER settings.

ANR2292WChanging the log mode to ROLLFORWARD will enable the database backup trigger.

Explanation: Changing the recovery log mode from NORMAL to ROLLFORWARD causes a previously issued DEFINE DBBACKUPTRIGGER command to become effective, and immediately start a full database backup. Database backups can only be triggered when the recovery log mode is set to ROLLFORWARD with a SET LOGMODE command.

System Action: The administrator is asked whether to continue.

User Response: Enter 'Y' to change the log mode, 'N' otherwise.

ANR2293IOnly point-in-time database recovery is now possible.

Explanation: An administrator has changed the recovery log mode from ROLLFORWARD to NORMAL with a SET LOGMODE command. Only point-in-time database restores can be performed. ROLLFORWARD database restores and individual database volume restores are not possible.

System Action: None.

User Response: None.

ANR2294ILog mode set to log mode.

Explanation: The mode for saving recovery log records has been set as indicated by the SET LOGMODE command. When set to NORMAL, only those log records needed to resume database processing if a system failure occurs are saved. When set to ROLLFORWARD, all log records created since the last database backup are saved. ROLLFORWARD mode also enables the database backup trigger to be used to automatically start database backups based on the percentage of recovery log utilization.

System Action: None.

User Response: None.

ANR2295ILog mode set to ROLLFORWARD; database backup trigger enabled.

Explanation: The mode for saving recovery log records has been set to ROLLFORWARD, and a previously defined database backup trigger has been enabled. All log records created since the last database backup are saved in this mode. The database backup trigger will automatically start a database backup based on the percentage of recovery log utilization.

System Action: None.

User Response: None.

ANR2296ILog mode set to NORMAL; database backup trigger disabled.

Explanation: The mode for saving recovery log records has been set to NORMAL mode, and the defined database backup trigger is disabled. Only those log records needed to resume database processing if a system failure occurs are saved in this mode. Database backups can only be started using the BACKUP DB command.

System Action: None.

User Response: None.

ANR2297ICommand: Optionset optionset name, option option name, sequence number old sequence number, has been changed to new sequence number.

Explanation: The requested option sequence number has been updated in response to an UPDATE CLIENTOPT command.

System Action: None.

User Response: None.

ANR2298ICommand: Optionset optionset name, option option name, sequence number old sequence number, is not updated.

Explanation: The requested option sequence number is not updated in response to an UPDATE CLIENTOPT command.

System Action: None.

User Response: Reissue the UPDATE CLIENTOPT command with a valid old sequence number.

ANR2299IPassword expiration period for administrator administrator name set to number of days days.

Explanation: The number of days that the administrator's password can be used before it must be changed has been set to the value indicated with the SET PASSEXP command.

System Action: None.

User Response: None.

ANR2300ECould not open "file spec" the server help file.

Explanation: The named help file could not be accessed.

System Action: The requested help text is not displayed.

User Response: Contact the system administrator.

ANR2301EErrors were encountered while setting up the index to the help text.

Explanation: Either insufficient memory or a help file read failure has occurred during setup of the help index.

System Action: The server does not display the requested help text.

User Response: Contact the system administrator.

ANR2302EThe argument operand is not valid for the HELP command.

Explanation: The argument supplied on the HELP command is not an integer or the name of a command.

System Action: The server does not process the HELP command.

User Response: Issue the HELP command with no operands and select from the numbered list displayed in response.

ANR2303EThere is no help section numbered section number.

Explanation: The numeric operand supplied on the HELP command is either less than 1 or greater than the highest-numbered entry in the help index.

System Action: The server does not process the HELP command.

User Response: Issue the HELP command with no operands and select from the numbered list (help index) displayed in response.

ANR2304EI/O error reading "help file name" the file of help text.

Explanation: An error is detected when reading help text from the named file.

System Action: The server ends display of the help text.

User Response: Contact the system administrator.

ANR2305ENo such command/subcommand: command subcommand.

Explanation: The operands you entered for the HELP command do not match any named entry into the file of help text.

System Action: The server does not process the HELP command.

User Response: Check your input for a misspelled command or subcommand name.

ANR2306ENo help text could be found for this command/subcommand: command.

Explanation: The operands you entered for the HELP command, although valid command/subcommand names, do not match any named entry into the file of help text.

System Action: The server does not process the HELP command.

User Response: Contact the system administrator.

ANR2307ENo help text could be found for this message: message ID.

Explanation: The message ID you entered for the help command does not match any message entry in the file of help text.

System Action: The help command is not processed.

User Response: Contact the system administrator.

ANR2308WAudit Volume marking damaged file as damaged on volume volume name: Node node name, Type file type, File space filespace name, File Name file name.

Explanation: As the result of an AUDIT VOLUME command that specified FIX=YES for the volume shown, the file whose information is displayed is marked as damaged in the server. The file is marked as damaged because it can be recovered from a copy known to exist in a COPY storage pool. If this file belongs to an aggregate, the entire aggregate is marked damaged, and this message will be issued for every file in the aggregate.

System Action: The file is marked as damaged in the server database.

User Response: To recover the damaged file use the RESTORE STGPOOL or RESTORE VOLUME command.

ANR2309EThe server log mode is currently set to roll-forward. You may run out of log space when auditing the server in this mode. Specify LOGMODE=NORMAL to set the log mode to NORMAL for the audit operation, or LOGMODE=ROLLFORWARD to force the audit operation with the logmode set to roll-forward.

Explanation: An AUDITDB operation was specified and the server log mode is set to roll-forward mode. When in roll-forward mode, the server may run out of log space during the AUDITDB operation, requiring an emergency extend of the recovery log to re-start the server. The recommended log mode for executing an AUDITDB operation is NORMAL.

System Action: The AUDITDB operation fails

User Response: To force the server log mode to NORMAL for the AUDITDB operation, specify LOGMODE=NORMAL on the AUDITDB command. Specify LOGMODE=ROLLFORWARD on the AUDITDB command to allow the audit to run with a roll-forward log mode setting.

ANR2310WThis command will compare all inventory references to volume volume name with the actual data stored on the volume and will report any discrepancies; the data will be inaccessible to users until the operation completes.

Explanation: During the execution of an AUDIT VOLUME command, any data the volume named would be unavailable to users.

System Action: The administrator is asked whether to continue.

User Response: Enter 'Y' to audit the volume or 'N' to stop the process.

ANR2311WThis command will discard any inventory references to volume volume name associated with missing or inconsistent stored data, thereby rendering the data unrecoverable; the valid data on the volume will be inaccessible to users until the operation completes.

Explanation: During the execution of an AUDIT VOLUME command, any data the volume named would be unavailable to users. After the command has ended, any inconsistent data found will be discarded.

System Action: The administrator is asked whether to continue.

User Response: Enter 'Y' to audit the volume or 'N' to stop the process.

ANR2312IAudit Volume (Repair) process started for volume volume name (process ID process ID).

Explanation: As the result of an AUDIT VOLUME command that specified FIX=YES for the volume shown, the process whose ID is displayed has begun auditing the volume.

System Action: The volume is audited and inconsistent data is discarded.

User Response: None.

ANR2313IAudit Volume (Inspect Only) process started for volume volume name (process ID process ID).

Explanation: As the result of an AUDIT VOLUME command that specified FIX=NO for the volume shown, the process whose ID is displayed has begun auditing the volume.

System Action: The volume is audited and inconsistent data is displayed.

User Response: None.

ANR2314IAudit volume process ended for volume volume name; file count files inspected, file count damaged files deleted, file count damaged files marked as damaged.

Explanation: The AUDIT VOLUME command specifying FIX=YES for the volume shown has ended. The number of files audited and the number of inconsistent files deleted or marked as damaged are displayed. The number of files marked as damaged includes all files belonging to aggregates that were marked damaged during the audit. Files are marked as damaged in primary storage pools and not deleted when backup copies for the files are known to exist in COPY storage pools.

System Action: None.

User Response: To recover files that have been marked as damaged on the volume, use the RESTORE STGPOOL or RESTORE volume command.

ANR2315IAudit volume process ended for volume volume name; file count files inspected, file count damaged files found and marked as damaged.

Explanation: The AUDIT VOLUME command specifying FIX=NO for the volume shown has ended. The number of files audited and the number of inconsistent files found are displayed. The number of files marked damaged includes all files belonging to aggregates that were marked damaged during the audit. Inconsistent files are marked as damaged in the database and can be recovered by using the RESTORE STGPOOL or RESTORE VOLUME command if copies of the files reside in a COPY storage pool. Another AUDIT VOLUME command may be able to access the files and reset the damaged indicator in the database if the audit volume process cannot access the files due to hardware problems (for example, dirty tape heads).

System Action: None.

User Response: If you suspect that files were inaccessible because of hardware problems such as dirty tape heads, correct the hardware problem and reissue the AUDIT VOLUME FIX=NO command for this volume. To remove damaged file references, issue the AUDIT VOLUME command and specify FIX=YES.

ANR2316WAudit Volume deleting damaged file on volume volume name: Node node name, Type file type, File space filespace name, File Name file name.

Explanation: As the result of an AUDIT VOLUME command that specified FIX=YES for the volume shown, the file whose information is displayed is deleted from the server.

System Action: The file is deleted.

User Response: None.

ANR2317WAudit Volume found damaged file on volume volume name: Node node name, Type file type, File space filespace name, File name file name.

Explanation: As the result of an AUDIT VOLUME command that specified FIX=NO for the volume shown, the file whose information is displayed is found to be in error and not accessible. If this file belongs to an aggregate, the entire aggregate is marked damaged, and this message will be issued for every file in the aggregate.

System Action: None.

User Response: None.

ANR2318WAudit volume process terminated for volume volume name - process canceled.

Explanation: During processing of an AUDIT VOLUME command for the volume shown, the process performing the audit was canceled.

System Action: The AUDIT VOLUME command is ended.

User Response: None.

ANR2319WAudit volume process terminated for volume volume name - error reading device.

Explanation: During processing of an AUDIT VOLUME command for the volume shown, an unrecoverable read error occurred on the volume.

System Action: The AUDIT VOLUME command is ended.

User Response: Attempt to correct the cause of the read error, and reissue the command.

ANR2320WAudit volume process terminated for volume volume name - data transfer interrupted.

Explanation: During processing of an AUDIT VOLUME command for the volume shown, a data transfer operation has been interrupted and cannot be continued.

System Action: The AUDIT VOLUME command is ended.

User Response: If possible, determine and correct the cause of the interruption, and reissue the command.

ANR2321WAudit volume process terminated for volume volume name - storage media inaccessible.

Explanation: During processing of an AUDIT VOLUME command for the volume shown, a required volume cannot be mounted.

System Action: The AUDIT VOLUME command is ended.

User Response: None.

ANR2322WAudit volume process terminated for volume volume name - sufficient recovery log space is not available.

Explanation: During processing of an AUDIT VOLUME command for the volume shown, the server does not have sufficient recovery log space to continue.

System Action: The AUDIT VOLUME command is ended.

User Response: If necessary, make more recovery log space available to the server.

ANR2323WAudit volume process terminated for volume volume name - sufficient database space is not available.

Explanation: During processing of an AUDIT VOLUME command for the volume shown, the server does not have sufficient database space to continue.

System Action: The AUDIT VOLUME command is ended.

User Response: If necessary, make more database space available to the server.

ANR2324WAudit volume process terminated for volume volume name - thread resource not available.

Explanation: During processing of an AUDIT VOLUME command for the volume shown, the server cannot start a thread for the audit process.

System Action: The AUDIT VOLUME command is ended.

User Response: Reissue the AUDIT VOLUME command. If the error persists, it may indicate a shortage of server memory.

ANR2325WAudit volume process terminated for volume volume name - sufficient memory is not available.

Explanation: During processing of an AUDIT VOLUME command for the volume shown, the server does not have enough memory available to complete the command.

System Action: The AUDIT VOLUME command is ended.

User Response: If necessary make more memory available to the server.

ANR2326WAudit volume process terminated for volume volume name - lock conflict detected.

Explanation: During processing of an AUDIT VOLUME command for the volume shown, the server cannot obtain a required lock.

System Action: The AUDIT VOLUME command is ended.

User Response: Reissue the command.

ANR2327WAudit volume process terminated for volume volume name - internal server error detected.

Explanation: During processing of an AUDIT VOLUME command for the volume shown, an internal server error occurs.

System Action: The AUDIT VOLUME command is ended.

User Response: Contact your service representative.

ANR2332WObject object.ID deleted by another process during execution of an AUDIT VOLUME command for volume volume name.

Explanation: During processing of an AUDIT VOLUME command, a data storage object was deleted from the volume that was being audited. The AUDIT VOLUME process was unable to locate this object on the specified volume. Normally, this action is not considered an error condition, because the object was probably deleted by a process such as a DELETE FILESPACE command.

System Action: Processing of the AUDIT VOLUME command continues.

User Response: Check the activity log to verify that some process (such as a DELETE FILESPACE command) was in progress during the AUDIT VOLUME command that would account for the deleted object. If no such process can be identified, contact your service representative.

ANR2333WMissing or incorrect information detected by AUDIT VOLUME for volume volume name.

Explanation: An AUDIT VOLUME command detects missing or incorrect information for the specified volume.

System Action: Audit processing continues.

User Response: Reissue the audit command with FIX=YES so that the information can be created or corrected.

ANR2334WMissing or incorrect information detected by AUDIT VOLUME for volume volume name - information will be created or corrected.

Explanation: An AUDIT VOLUME process detects missing or incorrect information for the specified volume. Because FIX=YES has been specified for the audit command, the information is created or corrected.

System Action: Audit processing continues.

User Response: None.

ANR2335WAudit Volume has encountered an I/O error for volume volume name while attempting to read: Node node name, Type file type, Filespace filespace name, File Name file name.

Explanation: The AUDIT VOLUME process encountered an I/O error for the specified volume while attempting to read the specified file. If this file belongs to an aggregate, the entire aggregate is marked damaged, and this message will be issued for every file in the aggregate.

System Action: None.

User Response: Identify and resolve the I/O error for the volume if possible. Verify that the volume's device is functioning properly and that the volume is usable. For example, if the volume is a tape volume, make sure the drive is clean or that the tape volume is usable by testing it by using a different drive.

ANR2336WAudit Volume terminated for volume volume name - insufficient number of mount points available for removable media.

Explanation: During Audit Volume for the indicated volume, the server could not allocate sufficient mount points for the volume required.

System Action: Audit Volume stops.

User Response: If necessary, make more mount points available.

ANR2339ECommand: Object sets still exist for node node name.

Explanation: A REMOVE NODE command has been entered for a node for which the server is still storing backup sets. To remove a node, the node must not have any files or backup sets stored on the server.

System Action: The server does not process the command.

User Response: To remove the node, delete all backup sets from the server and reissue the command.

ANR2340ECommand: Invalid storage pool name - storage pool name.

Explanation: The command indicated contains an invalid storage pool name.

System Action: The server does not process the command.

User Response: Reissue the command with a valid storage pool name.

ANR2341ECommand: Missing next storage pool name.

Explanation: The command indicated requires a storage pool name, but none has been entered.

System Action: The server does not process the command.

User Response: Reissue the command with a storage pool name.

ANR2342ECommand: Storage pool description exceeds maximum characters characters.

Explanation: The command indicated contains a storage pool description that exceeds the maximum length allowed.

System Action: The server does not process the command.

User Response: Reissue the command with a valid storage pool description.

ANR2343ECommand: Invalid device class name - device class name.

Explanation: The command indicated contains an invalid device class name.

System Action: The server does not process the command.

User Response: Reissue the command with a valid device class name.

ANR2344ECommand: The "option" option is not valid for device class device class name.

Explanation: The command indicated specifies an option shown that is not valid for a storage pool that belongs to the device class shown.

System Action: The server does not process the command.

User Response: Reissue the command with options appropriate to the device class.

ANR2345ECommand: Invalid volume name - volume name.

Explanation: The command indicated contains an invalid volume name.

System Action: The server does not process the command.

User Response: Reissue the command with a valid volume name.

ANR2346ECommand: Volume name "volume name" is not valid for device class device class name.

Explanation: The command indicated specifies the name of a volume that cannot be used with the device class shown.

System Action: The server does not process the command.

User Response: Reissue the command with a valid volume name.

ANR2347ECommand: Volume name "volume name" is ambiguous; resolves to multiple defined volume names.

Explanation: The command shown was entered with a volume name pattern that matches more than one volume. The command can only process a single volume.

System Action: The command is not executed.

User Response: Reissue the command with a more specific volume name.

ANR2348ECommand: The "option" option is not valid for a volume assigned to a primary storage pool.

Explanation: The command indicated specifies an option that is not valid for a volume in a primary storage pool.

System Action: The server does not process the command.

User Response: Reissue the command with valid options for a volume in a primary storage pool.

ANR2349ECommand: The "option" option is not valid for a volume assigned to a copy storage pool.

Explanation: The command indicated specifies an option that is not valid for a volume in a copy storage pool.

System Action: The server does not process the command.

User Response: Reissue the command with valid options for a volume in a copy storage pool.

ANR2350ECommand: Device class device class name is already defined.

Explanation: The command indicated has attempted to define a device class that already exists.

System Action: The server does not process the command.

User Response: None.

ANR2351ECommand: Device class device class name is not defined.

Explanation: The command indicated references a device class that does not exist.

System Action: The server does not process the command.

User Response: None.

ANR2352ECommand: Device class device class name may not be deleted.

Explanation: A DELETE DEVCLASS command specifies the class name DISK, which is a system-defined device class and may not be deleted.

System Action: The server does not process the command.

User Response: None.

ANR2353ECommand: Device class device class name may not be updated.

Explanation: An UPDATE DEVCLASS command specifies the class name DISK, which is a system-defined device class and may not be changed.

System Action: The server does not process the command.

User Response: None.

ANR2354ECommand: Device class device class name is still referenced by one or more storage pools, or database backup or export volumes.

Explanation: The DELETE DEVCLASS command has attempted to delete a device class that has storage pools assigned to it, or is referenced by database backup or export volumes.

System Action: The server does not process the command.

User Response: Issue Q DEVCLASS to view the storage pool reference count, Q STGPOOL to determine which pool references the device class, and Q VOLHIST to locate database backup or export volume references.

ANR2355ECommand: Required parameter is missing - missing parameter.

Explanation: The specified server command has been entered without the required parameter. The required parameter is shown.

System Action: The server ignores the command.

User Response: Reissue the command and enter the proper syntax.

ANR2356ECommand: Incompatible parameters specified - first parameter, second parameter.

Explanation: The specified server command has been entered with mutually exclusive parameters. The two parameters are listed.

System Action: The server ignores the command.

User Response: Reissue the command and enter the proper syntax.

ANR2357ECommand: The DISK device class is not supported for copy storage pools.

Explanation: An attempt is made to define a copy storage pool using a device of DISK. Copy storage pools can only be assigned to a sequential device class.

System Action: The server does not process the command.

User Response: Reissue the command specifying a sequential device class.

ANR2358ECommand: Device class device class name is still referenced in the volume history file.

Explanation: The DELETE DEVCLASS command has attempted to delete a device class that is associate with entries in the volume history file. These entries are for volumes that contain database backup or export data.

System Action: The server does not process the command.

User Response: Use the DELETE VOLHIST command to remove that entries before deleting the device class.

ANR2359ECommand: Volume name "volume name" must be specified with a DISK STGPOOL.

Explanation: The command indicated specifies the name of a volume that must be specified with a disk storage pool.

System Action: The server does not process the command.

User Response: Reissue the command with a valid volume name and storage pool.

ANR2360ECommand: Device class device class name may not be used for database backup.

Explanation: The command specifies the DISK device class, which cannot be used for database backup, backup trigger, or restore operations.

System Action: The server does not process the command.

User Response: Reissue the command with a valid device class.

ANR2361ECommand: A full database backup is required.

Explanation: A BACKUP DB command specified an incremental backup, but a full backup is required.

System Action: The server does not process the command.

User Response: Reissue the command specifying a full backup.

ANR2362ECommand: Database backup is not currently possible - compressed log records exist in the current transaction checkpoint.

Explanation: A BACKUP DB command was issued but a database backup cannot be started. Log compression has recently taken place, and the compressed log records are still part of the current transaction checkpoint. After these log records are no longer part of the current checkpoint a backup can take place.

System Action: The server does not process the command.

User Response: Reissue the command at a later time.

ANR2363ECommand: One of the following parameter must be supplied but is missing - missing parameter, missing parameter, missing parameter, missing parameter.

Explanation: The specified server command has been entered without one of the mutually exclusive required parameters. One of the parameters from the list must be specified.

System Action: The server ignores the command.

User Response: Reissue the command and enter the proper syntax.

ANR2364ECommand: Missing reclaim-storage pool name.

Explanation: The command indicated requires a storage pool name, but none has been entered.

System Action: The server does not process the command.

User Response: Reissue the command with a storage pool name.

ANR2365IBackupset backup set name for node node name has been deleted.

Explanation: The backup set has been deleted.

System Action: The server has deleted the backupset.

User Response: None.

ANR2366IBackupset backup set name for node node name would have been deleted.

Explanation: The backup set would have been deleted as the result of a DELETE BACKUPSET command, but the PREVIEW=YES parameter was specified.

System Action: None.

User Response: If the backup set is to be deleted, reissue the command without specifying PREVIEW=YES.

ANR2367IRetention period for backupset backup set name for node node name has been updated.

Explanation: The backup set's retention period has been updated.

System Action: The server has updated the backupset's retention period.

User Response: None.

ANR2368IRetention period for backupset backup set name for node node name would have been updated.

Explanation: The backup set's retention period would have been updated as the result of an UPDATE BACKUPSET command, but the PREVIEW=YES parameter was specified.

System Action: None.

User Response: If the backup set is to be updated, reissue the command without specifying PREVIEW=YES.

ANR2369IDatabase backup volume and recovery plan file expiration starting under process process ID.

Explanation: The server has started expiration processing to remove expired database backup volumes and recovery plan files created on a remote server. This message is issued only if DRM is licensed on the server. The DB backup volumes expired is based on the value specified on the SET DRMDBBACKUPEXPIREDAYS. The recovery plan files expired is based on the value specified on the SET DRMRPFEXPIREDAYS. Server inventory expiration processing deletes the DB backup volumes and recovery plan files only if the volumes or plan files are created on the server to server virtual volumes.

System Action: Server operation continues. The expiration process is cancellable.

User Response: None.

ANR2370ECommand: Database backup trigger is already defined.

Explanation: The database backup trigger cannot be defined because it is already defined.

System Action: The server does not process the command.

User Response: Use the UPDATE DBBACKUPTRIGGER command to modify the database backup trigger parameters.

ANR2371ECommand: Database backup trigger is not defined.

Explanation: The database backup trigger cannot be updated or deleted because it is not currently defined.

System Action: The server does not process the command.

User Response: None.

ANR2372ECommand: Data Base Space trigger is already defined.

Explanation: The database space trigger cannot be defined because it is already defined.

System Action: The server does not process the command.

User Response: Use the UPDATE SPACETRIGGER command to modify the indicated space trigger parameters.

ANR2373ECommand: Database backup trigger is not defined.

Explanation: The data base space trigger cannot be updated or deleted because it is not currently defined.

System Action: The server does not process the command.

User Response: None.

ANR2374ECommand: Recovery Log Space trigger is already defined.

Explanation: The recovery log space trigger cannot be defined because it is already defined.

System Action: The server does not process the command.

User Response: Use the UPDATE SPACETRIGGER command to modify the indicated space trigger parameters.

ANR2375ECommand: Recovery Log trigger is not defined.

Explanation: The recovery log space trigger cannot be updated or deleted because it is not currently defined.

System Action: The server does not process the command.

User Response: None.

ANR2376IRecovery Log Space trigger defined, but is disabled.

Explanation: A recovery log space trigger has been defined, but because the space expansion percentage is currently set to 0, the space trigger is disabled.

System Action: None.

User Response: To activate the space trigger, use the UPDATE SPACETRIGGER command to set the space expansion percentage to a value greater than 0.

ANR2377IRecovery Log Space trigger updated and enabled.

Explanation: An UPDATE SPACETRIGGER command has successfully completed for the recovery log space trigger. The updated parameters specified on the command are used to automatically trigger space expansion for the data base.

System Action: None.

User Response: None.

ANR2378IRecovery Log Space trigger updated, but disabled.

Explanation: An UPDATE SPACETRIGGER command has successfully completed for the recovery log space trigger. However, the space expansion percentage is currently set to 0, which disables the space trigger.

System Action: None.

User Response: To activate the space trigger, use the UPDATE SPACETRIGGER command with the SPACEexpansion parameter to set a value greater than zero.

ANR2379IRecovery Log Space trigger deleted.

Explanation: A DELETE SPACETRIGGER command has successfully completed for the recovery log space trigger. Space expansions are no longer triggered automatically for the recovery log.

System Action: None.

User Response: None.

ANR2380ECommand: Storage pool storage pool name is not defined.

Explanation: The command indicated specifies the name of a nonexistent storage pool.

System Action: The server does not process the command.

User Response: Reissue the command with a valid storage pool name.

ANR2381ECommand: Storage pool storage pool name is already defined.

Explanation: A DEFINE STGPOOL command specifies the name of a storage pool that already exists.

System Action: The server does not process the command.

User Response: None.

ANR2382ECommand: Storage pool storage pool name still contains at least one volume.

Explanation: A DELETE STGPOOL command specifies a storage pool that has volumes assigned to it.

System Action: The server does not process the command.

User Response: Delete the volume belonging to the storage pool and reissue the command.

ANR2383ECommand: Storage pool storage pool name is currently in use by clients and/or data management operations.

Explanation: The command indicated references a storage pool that is in use.

System Action: The server does not process the command.

User Response: Reissue the command at a later time.

ANR2384ECommand: Next or Reclaim storage pool storage pool name introduces a cycle into the storage pool chain.

Explanation: A DEFINE STGPOOL or UPDATE STGPOOL command specifies a next storage pool that eventually points to the pool being processed.

System Action: The server does not process the command.

User Response: Reissue the command with a different next pool value.

ANR2385ECommand: Storage pool storage pool name is in use as the next or reclaim pool for one or more other storage pools.

Explanation: A DELETE STGPOOL command specifies a pool that is the next pool or the reclaim pool for other storage pools.

System Action: The server does not process the command.

User Response: If necessary, update other storage pools so that they do not reference the pool to be deleted, and reissue the command.

ANR2386ECommand: High migration threshold must be set greater than or equal to the low migration threshold.

Explanation: A DEFINE or UPDATE STGPOOL command has attempted to set the storage pool low migration threshold (LOWMIG) parameter greater than the high migration threshold (HIGHMIG).

System Action: The server does not process the command.

User Response: Reissue the command with a low migration threshold less than or equal to the high migration threshold.

ANR2387ECommand: Storage pool storage pool name is not a primary pool.

Explanation: The command indicated specifies the name of a storage pool which is not a primary pool. The command syntax requires that a primary storage pool name be specified.

System Action: The server does not process the command.

User Response: Reissue the command with a valid primary storage pool name.

ANR2388ECommand: Storage pool storage pool name is not a copy pool.

Explanation: The command indicated specifies the name of a storage pool which is not a copy pool. The command syntax requires that a copy storage pool name be specified.

System Action: The server does not process the command.

User Response: Reissue the command with a valid copy storage pool name.

ANR2389ECommand: The "option" option is not valid for a primary storage pool.

Explanation: The command indicated specifies an option that is not valid for a primary storage pool.

System Action: The server does not process the command.

User Response: Reissue the command with options appropriate for a primary storage pool.

ANR2390ECommand: The "option" option is not valid for a copy storage pool.

Explanation: The command indicated specifies an option that is not valid for a copy storage pool.

System Action: The server does not process the command.

User Response: Reissue the command with options appropriate for a copy storage pool.

ANR2391ECommand: Server could not write device configuration information to file name.

Explanation: The BACKUP DEVCONFIG command does not successfully complete because the server cannot write to the file name specified.

System Action: The server does not process the command.

User Response: Make sure that the server has proper authority to write to the file indicated and that sufficient space is available in the file system for the file. On MVS, make sure that the data set has been allocated and that the server has authority to write to the data set.

ANR2392ECommand: An internal error was encountered in writing device configuration information to file name.

Explanation: The BACKUP DEVCONFIG command does not successfully complete because the server cannot write to the file name specified.

System Action: The server does not process the command.

User Response: Examine error messages on the server console that may have been displayed prior to this message and correct any problems, if possible. Make sure that the server has proper authority to write to the file indicated and that sufficient space is available in the file system for the file. On MVS, make sure that the data set has been allocated and that the server has authority to write to the data set.

ANR2393ICommand: Server device configuration information was written to file name.

Explanation: This message is displayed in response to the BACKUP DEVCONFIG command and indicates that device configuration information was successfully written to the file name indicated.

System Action: The server records device configuration information to the file name specified

User Response: None.

ANR2394ICommand: Server device configuration information was written to all device configuration files.

Explanation: This message is displayed in response to the BACKUP DEVCONFIG command and indicates that device configuration information was successfully written to all files that were specified in the server options file.

System Action: The server records device configuration information to the device configuration files.

User Response: None.

ANR2395ICommand: Device configuration files have NOT been defined for automatic recording - specify a file name for device configuration information.

Explanation: This message is displayed in response to the BACKUP DEVCONFIG command and indicates that device configuration information cannot be written because no files were specified in the options file.

System Action: The device configuration information is not written. Server operation continues.

User Response: Reissue the BACKUP DEVCONFIG command and specify the name of a file to which you would like to have device configuration information recorded. If desired, you may configure files that should be automatically updated with the DEVCONFIG option and restart the server.

ANR2396ECommand: An I/O error was encountered in writing device configuration information to one or more of the defined device configuration files.

Explanation: The BACKUP DEVCONFIG command does not complete successfully because the server cannot write to one or more of the defined device configuration files.

System Action: The server does not process the command.

User Response: Examine error messages on the server console that may have been displayed prior to this message and correct any problems, if possible. Make sure that the server has proper authority to write to the file indicated and that sufficient space is available in the file system for the file. On MVS, make sure that the data set has been allocated and that the server has authority to write to the data set.

ANR2397ECommand: An internal server error was encountered in writing device configuration information to one or more of the defined device configuration files.

Explanation: The BACKUP DEVCONFIG command does not complete successfully because the server cannot write to one or more of the defined device configuration files.

System Action: The server does not process the command.

User Response: Examine error messages on the server console that may have been displayed prior to this message and correct any problems, if possible. Contact your service representative if you are unable to resolve the problem.

ANR2398ECommand: The device configuration file contains a statement with invalid syntax.

Explanation: While processing the device configuration information, an invalid statement has been encountered.

System Action: The server ends the operation being performed.

User Response: Examine error messages on the server console that may have been displayed prior to this message and correct any problems if you have constructed the device configuration file manually. Make sure the statements are in the proper order. If you let the server construct the device configuration file automatically, restart the server, refresh the device configuration file by issuing the BACKUP DEVCONFIG command, and reissue the operation. If the problem persists, contact your service representative.

ANR2399ECommand: Storage pool storage pool name is not a sequential pool.

Explanation: The command indicated specifies the name of a storage pool which is not a sequential pool. All storage pools are either fixed disk or sequential archival. All tape devices, as well as optical and file device classes, are sequential.

System Action: The server does not process the command.

User Response: Reissue the command with a valid sequential storage pool name.

ANR2400ECommand: Volume volume name is already defined in a storage pool or has been used previously to store export, database dump, or database backup information.

Explanation: The command indicated specifies the name of a storage pool volume that already exists or has been used to store server export, database dump, or database backup information as recorded in the server volume history file.

System Action: The server does not process the command.

User Response: Specify a volume that is not in use, is not defined in a storage pool, and which has not been previously used for an export, a database dump, or database backup operation as recorded in the server volume history information. Use the QUERY VOLUME command to display the names of volumes that are defined to server storage pools. Use the QUERY VOLHISTORY command to display the names of volumes that have been used for export, a database dump, or database backup operations.

ANR2401ECommand: Volume volume name is not defined in a storage pool.

Explanation: The command indicated specifies the name of a storage pool volume that does not exist.

System Action: The server does not process the command.

User Response: None.

ANR2402ECommand: Volume volume name is already online.

Explanation: A VARY ONLINE command specifies the name of a volume that is already online.

System Action: The server does not process the command.

User Response: None.

ANR2403ECommand: Volume volume name is not online.

Explanation: The command indicated specifies the name of a volume that is not online.

System Action: The server does not process the command.

User Response: None.

ANR2404ECommand: Volume volume name is not available.

Explanation: The command indicated has attempted to access a volume that cannot be found.

System Action: The server does not process the command.

User Response: Check the spelling of the volume name to ensure it is correct. If the volume does not exist, preallocate it with the appropriate mechanism for the operating system on which the server is running.

ANR2405ECommand: Volume volume name is currently in use by clients and/or data management operations.

Explanation: The command indicated specifies the name of a data storage volume that is currently in use.

System Action: The server does not process the command.

User Response: None.

ANR2406ECommand: Volume volume name still contains data.

Explanation: The indicated command tries to delete a data storage volume that contains data.

System Action: The server does not process the command.

User Response: None.

ANR2407ECommand: Maximum number of mirrored copies exceeded.

Explanation: A DEFINE LOGCOPY or DEFINE DBCOPY command has attempted to add a mirror volume, but the maximum number of mirrors for the target volume already exists.

System Action: The server does not process the command.

User Response: None.

ANR2408ECommand: Capacity of volume volume name must be at least as large as capacity of volume volume name.

Explanation: A DEFINE LOGCOPY or DEFINE DBCOPY command has attempted to add a mirror volume, but the size of the volume to be added is less than the size of the target volume.

System Action: The server does not process the command.

User Response: Use a larger mirror volume.

ANR2409ECommand: Capacity of volume volume name must be at least 5 megabytes.

Explanation: A define command for a database or log volume or copy has specified a volume that is too small to be used by the server for a database or log volume. The minimum size for one of these volumes is 5 megabytes.

System Action: The server does not process the command.

User Response: Reissue the command and specify a volume that is at least 5 megabytes in size.

ANR2410ECommand: Unable to access volume volume name - access mode is set to "unavailable".

Explanation: The command shown specifies the volume whose name is displayed, but the volume cannot be accessed because its status is unavailable.

System Action: The server does not process the command.

User Response: If necessary, reset the status of the volume and reissue the command.

ANR2411ECommand: Unable to access associated volume volume name - access mode is set to "unavailable".

Explanation: The command shown would require access to the volume whose name is displayed (because data from the volume specified in the command spans into this volume); the volume shown cannot be accessed because its status is unavailable.

System Action: The server does not process the command.

User Response: If necessary, reset the status of the volume and reissue the command.

ANR2412ECommand: Audit operation already in progress for volume volume name.

Explanation: The command shown specifies the volume whose name is displayed, but that volume is currently in use by an audit volume operation.

System Action: The server does not process the command.

User Response: Reissue the command after the audit volume operation ends.

ANR2413ECommand: Audit operation already in progress for associated volume volume name.

Explanation: The command shown would require access to the volume whose name is displayed (because data from the volume specified in the command spans into this volume); the volume shown cannot be accessed because it is in use by an audit volume operation.

System Action: The server does not process the command.

User Response: Reissue the command after the audit volume operation ends.

ANR2414ECommand: Deletion operation already in progress for volume volume name.

Explanation: The command shown specifies the volume whose name is displayed, but that volume is currently in use by a delete volume operation.

System Action: The server does not process the command.

User Response: Reissue the command after the delete volume operation ends.

ANR2415ECommand: Deletion operation already in progress for associated volume volume name.

Explanation: The command shown would require access to the volume whose name is displayed (because data from the volume specified in the command spans into this volume); the volume shown cannot be accessed because it is in use by a delete volume operation.

System Action: The server does not process the command.

User Response: Reissue the command after the delete volume operation ends.

ANR2416ECommand: Move Data operation already in progress for volume volume name.

Explanation: The command shown specifies the volume whose name is displayed, but that volume is currently in use by a move data operation.

System Action: The server does not process the command.

User Response: Reissue the command after the move data process ends.

ANR2417ECommand: Move Data operation already in progress for associated volume volume name.

Explanation: The command shown would require access to the volume whose name is displayed (because data from the volume specified in the command spans into this volume); the volume shown cannot be accessed because it is in use by a move data operation.

System Action: The server does not process the command.

User Response: Reissue the command after the move data operation ends.

ANR2418ECommand: Migration operation already in progress for volume volume name.

Explanation: The command shown specifies the volume whose name is displayed, but that volume is currently in use by a migration operation.

System Action: The server does not process the command.

User Response: Reissue the command after the migration ends.

ANR2419ECommand: Migration operation already in progress for associated volume volume name.

Explanation: The command shown would require access to the volume whose name is displayed (because data from the volume specified in the command spans into this volume); the volume shown cannot be accessed because it is in use by a migration operation.

System Action: The server does not process the command.

User Response: Reissue the command after the migration ends.

ANR2420ECommand: Space reclamation operation already in progress for volume volume name.

Explanation: The command shown specifies the volume whose name is displayed, but that volume is currently in use by a reclamation operation.

System Action: The server does not process the command.

User Response: Reissue the command after the reclamation ends.

ANR2421ECommand: Space reclamation operation already in progress for associated volume volume name.

Explanation: The command shown would require access to the volume whose name is displayed (because data from the volume specified in the command spans into this volume); the volume shown cannot be accessed because it is in use by a reclamation operation.

System Action: The server does not process the command.

User Response: Reissue the command after the reclamation ends.

ANR2422ECommand: Volume volume name is not a defined disk volume.

Explanation: The command shown specifies a volume name that does not match any known disk volume.

System Action: The server does not process the command.

User Response: Reissue the command with the correct volume name.

ANR2423ECommand: Volume volume name is still online.

Explanation: An UPDATE VOLUME command specifies access=unavailable for a disk volume that is still online.

System Action: The server does not process the command.

User Response: Issue the VARY OFFLINE command, and reissue the UPDATE VOLUME command.

ANR2424ECommand: Unable to access volume volume name - access mode is set to "destroyed".

Explanation: The command shown specifies the volume whose name is displayed, but the volume cannot be accessed because its status is destroyed.

System Action: The server does not process the command.

User Response: If necessary, reset the status of the volume and reissue the command.

ANR2425ECommand: Unable to access volume volume name - access mode is set to "offsite".

Explanation: The command shown specifies the volume whose name is displayed, but the volume cannot be accessed because its status is offsite.

System Action: The server does not process the command.

User Response: If necessary, reset the status of the volume and reissue the command.

ANR2426IBackupset backup set name defined for node node name.

Explanation: The backup set has been defined for the indicated node.

System Action: The server has defined the backupset.

User Response: None.

ANR2427EBackupset backup set name for node node name was not deleted. Device class device class name was not found.

Explanation: The specified backupset was not deleted because the device class used to generate it was not found.

System Action: The backupset is not deleted.

User Response: If the device class was inadvertently deleted, redefine it, then delete the backupset again.

ANR2428EBackupset backup set name for node node name has not been deleted due to error error code.

Explanation: The backupset has not been deleted.

System Action: The server has not deleted the backupset.

User Response: Check related error messages.

ANR2429ECommand: Maximum database capacity exceeded.

Explanation: Do not allocate any volume that would cause the database to exceed 500GB. A subsequent DEFINE DBVOLUME command for that volume would fail.

System Action: The server does not process the command.

User Response: None.

ANR2430ECommand: Volume volume name is already defined as a database volume.

Explanation: A DEFINE DBVOLUME command specifies the name of a database volume that already exists.

System Action: The server does not process the command.

User Response: None.

ANR2431ECommand: Volume volume name is not a defined database volume.

Explanation: A DELETE DBVOLUME command specifies the name of a database volume that does not exist.

System Action: The server does not process the command.

User Response: None.

ANR2432ECommand: Maximum number of database volumes exceeded.

Explanation: A DEFINE DBVOLUME command has attempted to add more database volumes than the server can manage.

System Action: The server does not process the command.

User Response: None.

ANR2433ECommand: A database define, delete, extend, reduce, or backup operation is already in progress.

Explanation: The specified command has been entered while a command that is modifying or backing up the database is already active.

System Action: The server does not process the command.

User Response: Wait for other activity to end, and reissue the command.

ANR2434ECommand: Insufficient space on other database volumes to delete volume volume name.

Explanation: A DELETE DBVOLUME command has been entered, but the data on the volume to be deleted cannot be copied to other volumes due to insufficient free space.

System Action: The server does not process the command.

User Response: Make more database space available, and reissue the command.

ANR2435ECommand: Unable to delete database volume volume name - mirrored copies not synchronized.

Explanation: A DELETE DBVOLUME command has been entered, but mirrors of the volume to be deleted are not up to date.

System Action: The server does not process the command.

User Response: Try the command at a later time (after database volumes have been synchronized).

ANR2436ECommand: Insufficient space to extend database by requested amount.

Explanation: An EXTEND DB command has been entered, but not enough allocated, unused space is available to the database to add the amount of space requested.

System Action: The server does not process the command.

User Response: Make more database space available, and reissue the command.

ANR2437ECommand: Output error encountered while attempting to extend database.

Explanation: An EXTEND DB command has been entered, but an I/O error occurs during the command.

System Action: The server does not process the command.

User Response: Reissue the command. If the problem persists, identify and remove or repair the volume that caused the error.

ANR2438ECommand: Insufficient database space would be available following a reduction by the requested amount.

Explanation: A REDUCE DB command has been entered, but the database does not have enough free space to reduce by the amount specified.

System Action: The server does not process the command.

User Response: None.

ANR2439ECommand: Unable to vary database volume volume name offline - mirrored copies not synchronized.

Explanation: A VARY OFFLINE command has been entered, but mirrors of the volume to be varied are not up to date.

System Action: The server does not process the command.

User Response: Try the command at a later time (after database volumes have been synchronized).

ANR2440ECommand: Unable to vary database volume volume name offline - only copy.

Explanation: A VARY OFFLINE command has been entered, but the database volume has no mirrors and therefore contains the only copy of the data on that volume.

System Action: The server does not process the command.

User Response: None.

ANR2441ECommand: Volume volume name is already defined as a recovery log volume.

Explanation: A DEFINE LOGVOLUME command specifies the name of a recovery log volume that already exists.

System Action: The server does not process the command.

User Response: None.

ANR2442ECommand: Volume volume name is not a defined recovery log volume.

Explanation: A DELETE LOGVOLUME command specifies the name of a recovery log volume that does not exist.

System Action: The server does not process the command.

User Response: None.

ANR2443ECommand: Maximum number of recovery log volumes exceeded.

Explanation: A DEFINE LOGVOLUME command attempts to add more recovery log volumes than the server can manage.

System Action: The server does not process the command.

User Response: None.

ANR2444ECommand: A recovery log define, delete, extend, or reduce operation is already in progress.

Explanation: The specified command has been entered while a command that is modifying the recovery log is already active.

System Action: The server does not process the command.

User Response: Wait for other activity to end, and reissue the command.

ANR2445ECommand: Insufficient space on other recovery log volumes to delete volume volume name.

Explanation: A DELETE LOGVOLUME command has been entered, but the data on the volume to be deleted cannot be copied to other volumes due to insufficient free space.

System Action: The server does not process the command.

User Response: Make more recovery log space available, and reissue the command.

ANR2446ECommand: Unable to delete recovery log volume volume name - mirrored copies not synchronized.

Explanation: A DELETE LOGVOLUME command has been entered, but mirrors of the volume to be deleted are not up to date.

System Action: The server does not process the command.

User Response: Try the command at a later time (after recovery log volumes have been synchronized).

ANR2447ECommand: Insufficient space to extend recovery log by requested amount.

Explanation: An EXTEND LOG command has been entered, but there is not enough allocated, unused space available to the recovery log to add the amount of space requested.

System Action: The server does not process the command.

User Response: Make more recovery log space available, and reissue the command.

ANR2448ECommand: Output error encountered while attempting to extend recovery log.

Explanation: An EXTEND LOG command has been entered, but an I/O error occurs during the command.

System Action: The server does not process the command.

User Response: Reissue the command. If the problem persists, identify and remove or repair the volume that caused the error.

ANR2449ECommand: Insufficient recovery log space would be available following a reduction by the requested amount.

Explanation: A REDUCE LOG command has been entered, but the recovery log does not have enough free space to reduce by the amount specified.

System Action: The server does not process the command.

User Response: None.

ANR2450ECommand: Unable to vary recovery log volume volume name offline - mirrored copies not synchronized.

Explanation: A DELETE LOGVOLUME command has been entered, but mirrors of the volume to be deleted are not up to date.

System Action: The server does not process the command.

User Response: Try the command at a later time (after recovery log volumes have been synchronized).

ANR2451ECommand: Unable to vary recovery log volume volume name offline - only copy.

Explanation: A VARY OFFLINE command has been entered, but the recovery log volume has no mirrors and contains the only copy of the data on that volume.

System Action: The server does not process the command.

User Response: None.

ANR2452ECommand: Maximum recovery log capacity exceeded.

Explanation: Do not allocate any volume that would cause the recovery log to exceed 5GB. A subsequent DEFINE LOGVOLUME command for that volume would fail.

System Action: The server does not process the command.

User Response: None.

ANR2453ECommand: Unable to reduce recovery log - log mode must be set to NORMAL.

Explanation: A REDUCE LOG command has been entered, but the recovery log mode of the server is currently set to ROLLFORWARD. The recovery log can only be reduced when the log mode is set to NORMAL with a SET LOGMODE command.

System Action: The server does not process the command.

User Response: Set the log mode to NORMAL with the SET LOGMODE command, reissue the REDUCE LOG command, and set the log mode back to ROLLFORWARD with the SET LOGMODE command. If you change the log mode to NORMAL, you can only recover your database to the time of the last complete database backup.

ANR2454ECommand: Unable to reduce database - LOGMODE must be set to NORMAL.

Explanation: A REDUCE DB command has been entered, but the recovery log mode of the server is currently set to ROLLFORWARD. The database can only be reduced when log mode is set to NORMAL with the SET LOGMODE command.

System Action: The server does not process the command.

User Response: Set the log mode to NORMAL with the SET LOGMODE command, reissue the REDUCE DB command, and reset the log mode to ROLLFORWARD with the SET LOGMODE command. If you change the log mode to NORMAL, you can only recover your database to the time of the last complete database backup.

ANR2455ECommand: Unable to access associated volume volume name - access mode is set to "destroyed".

Explanation: The specified command would require access to the volume whose name is displayed (because data from the volume specified in the command spans into this volume); the volume shown cannot be accessed because its status is destroyed.

System Action: The server does not process the command.

User Response: If necessary, reset the status of the volume and reissue the command.

ANR2456ECommand: Unable to access associated volume volume name - access mode is set to "offsite".

Explanation: The command shown would require access to the volume whose name is displayed (because data from the volume specified in the command spans into this volume); the volume shown cannot be accessed because its status is offsite.

System Action: The server does not process the command.

User Response: If necessary, reset the status of the volume and reissue the command.

ANR2457ECommand: Backup of primary storage pool primary pool name to copy storage pool copy pool name already in progress.

Explanation: The command shown specifies a backup operation that is already in progress.

System Action: The server does not process the command.

User Response: Reissue the command after the current backup operation ends.

ANR2458ECommand: Restore of primary storage pool primary pool name (or volumes in that storage pool) already in progress.

Explanation: The command shown cannot be processed because a restore operation involving the indicated storage pool is already in progress. Either a RESTORE STGPOOL command is in progress for the indicated storage pool or a RESTORE VOLUME command is in progress for volumes that belong to the indicated storage pool.

System Action: The server does not process the command.

User Response: Reissue the command after the current restore operation ends.

ANR2459ECommand: Volume volume name cannot be updated - a restore operation involving that volume is in progress.

Explanation: The indicated volume has an access mode of destroyed. Either a RESTORE STGPOOL command or a RESTORE VOLUME command is in progress to restore the contents of the indicated volume.

System Action: The server does not process the command.

User Response: If necessary, cancel the restore processing and update the volume.

ANR2460ECommand: Server could not write sequential volume history information to File name.

Explanation: The BACKUP VOLHISTORY command does not complete successfully because the server cannot write to the file name specified.

System Action: The server does not process the command.

User Response: Make sure that the server has proper authority to write to the file indicated and that sufficient space is available in the file system for the file. On MVS, make sure that the data set has been allocated and that the server has authority to write to the data set.

ANR2461ECommand: An internal error was encountered in writing sequential volume history information to file name.

Explanation: The BACKUP VOLHISTORY command does not complete successfully because the server cannot write to the file name specified.

System Action: The server does not process the command.

User Response: Examine error messages on the server console that may have been displayed prior to this message and correct any problems, if possible. Make sure that the server has proper authority to write to the file indicated and that sufficient space is available in the file system for the file. On MVS, make sure that the data set has been allocated and that the server has authority to write to the data set.

ANR2462ICommand: Server sequential volume history information was written to file name.

Explanation: This message is displayed in response to the BACKUP VOLHISTORY command and indicates that sequential volume history information was successfully written to the file name indicated.

System Action: The server records sequential volume history information to the file name specified.

User Response: None.

ANR2463ICommand: Server sequential volume history information was written to all configured history files.

Explanation: This message is displayed in response to the BACKUP VOLHISTORY command and indicates that sequential volume history information was successfully written to all files that were specified in the server options file.

System Action: The server records sequential volume history information to the configured files.

User Response: None.

ANR2464ICommand: Volume history files have NOT been defined for automatic history recording - specify a file name for recording history information.

Explanation: This message is displayed in response to the BACKUP VOLHISTORY. It indicates that sequential volume history information cannot automatically be written because no files were defined in the server options file for recording this information.

System Action: The sequential volume history information is not written. Server operation continues.

User Response: Reissue the BACKUP VOLHISTORY command and specify the name of a file for recording sequential volume history information. If desired, you may configure files that should be automatically updated with the VOLUMEHISTORY parameter and restart the server.

ANR2465ECommand: An I/O error was encountered in writing sequential volume history information to one or more of the defined volume history files.

Explanation: The BACKUP VOLHISTORY command does not complete successfully because the server cannot write to one or more of the defined volume history files.

System Action: The server does not process the command.

User Response: Examine error messages on the server console that may have been displayed prior to this message and correct any problems, if possible. Make sure that the server has proper authority to write to the file indicated and that sufficient space is available in the file system for the file. On MVS, make sure that the data set has been allocated and that the server has authority to write to the data set.

ANR2466ECommand: An internal server error was encountered in writing sequential volume history information to one or more of the defined volume history files.

Explanation: The BACKUP VOLHISTORY command does not complete successfully because the server cannot write to one or more of the defined volume history files.

System Action: The server does not process the command.

User Response: Examine error messages on the server console that may have been displayed prior to this message and correct any problems, if possible. Contact your service representative if you are unable to resolve the problem.

ANR2467ICommand: number of entries deleted sequential volume history entries were successfully deleted.

Explanation: The DELETE VOLHISTORY command successfully deleted the number of entries specified.

System Action: Server operation continues.

User Response: None.

ANR2468ECommand: An internal server error was encountered while deleting server sequential volume history information.

Explanation: The DELETE VOLHISTORY command fails because an internal server error has been encountered.

System Action: The DELETE VOLHISTORY command fails, and server operation continues.

User Response: Examine the messages in the activity log or server console that were displayed prior to the error to see if the error can be resolved. Contact your service representative if this error cannot be resolved.

ANR2469ECommand: Invalid volume history type: history type.

Explanation: The command failed because an invalid sequential volume history type was specified for the TYPE= parameter.

System Action: The command fails, and server operation continues.

User Response: Refer to the Administrator's Reference for an explanation of the valid types for this command. Reissue the command and specify a valid type value.

ANR2470IMessage output being re-directed to file file name.

Explanation: The message output is being redirected to the specified file instead of being displayed at the console.

System Action: None.

User Response: None.

ANR2471EMessage output re-direction to file file name failed - unable to open file.

Explanation: An error occurs while trying to open the file. The message output will not be redirected to the specified file.

System Action: None.

User Response: Determine the cause of the file open failure and take corrective action.

ANR2472ECommand: Invalid volume specified: volume name.

Explanation: The command failed because the sequential history volume specified is not a DB DUMP, DB BACKUP, or EXPORT volume.

System Action: The command fails, and server operation continues.

User Response: Reissue the command and specify a valid volume name.

ANR2473ICommand for volume volume name completed.

Explanation: The command completed and the volume history file has been updated.

System Action: The server records sequential volume history information.

User Response: None.

ANR2474ECommand: Input volume names must be specified with the VOLumenames= parameter.

Explanation: The command failed because input volume names were not specified with the VOLumenames parameter.

System Action: The command fails.

User Response: On some platforms, or with certain device classes, the server cannot prompt to mount input removable media volumes, so the names of the required volumes must be specified in the command. Reissue the command specifying the name(s) of volumes that should be mounted for input.

ANR2475ECommand: File file name could not be opened.

Explanation: The DSMSERV command could not be completed successfully because the file specified (to contain the list of volumes to be used) cannot be opened.

System Action: The DSMSERV command fails.

User Response: Examine the file name that was specified in the DSMSERV command. Correct the specification, if necessary, so that it specifies the name of a file that exists and is accessible by the server program. Reissue the DSMSERV command if this can be corrected. Contact your service representative if this error cannot be resolved.

ANR2476ILicense storage auditing is disabled, no output available.

Explanation: The license storage occupancy function is currently disabled.

System Action: None.

User Response: To obtain storage occupancy results, remove the NOAUDITSTORAGE or AUDITSTORAGE NO option from the server options file, then restart the server and issue the AUDIT LICENSES command.

ANR2477ILicense storage auditing is disabled, storage values may be outdated and should be ignored.

Explanation: The license storage occupancy function is currently disabled.

System Action: None.

User Response: To obtain storage occupancy results, remove the NOAUDITSTORAGE or AUDITSTORAGE NO option from the server options file, then restart the server and issue the AUDIT LICENSES command.

ANR2478ECommand: Command cannot be executed in this session.

Explanation: The command indicated is not supported by the session in which it was invoked. For example, a DEFINE CURSOR command can not be invoked from the server's primary console.

System Action: The server does not process the command.

User Response: The command must be issued from a standard administrator session.

ANR2479ECommand: Invalid SQL cursor name - SQL cursor name.

Explanation: The command indicated contains an invalid SQL cursor name.

System Action: The server does not process the command.

User Response: Reissue the command with a valid SQL cursor name.

ANR2480ECommand: SQL cursor name SQL cursor name is already defined.

Explanation: The command indicated specifies an SQL cursor name that has already been defined.

System Action: The server does not process the command.

User Response: Reissue the command and specify a different cursor name.

ANR2481ECommand: SQL cursor name SQL cursor name is not defined.

Explanation: The command indicated specifies an SQL cursor name that has not been defined.

System Action: The server does not process the command.

User Response: Use the DEFINE CURSOR command to first define the cursor.

ANR2482ECommand: SQL cursor SQL cursor name is already open.

Explanation: The command indicated failed because an SQL cursor is already open.

System Action: The server does not process the command.

User Response: Use the CLOSE CURSOR command to first close the current cursor.

ANR2483ECommand: No SQL cursor is currently open.

Explanation: The command indicated failed because no SQL cursor is currently open.

System Action: The server does not process the command.

User Response: Use the OPEN CURSOR command to first open a cursor.

ANR2484ECommand: Invalid SQL date-time display format - SQL date-time display format name.

Explanation: The command indicated contains an invalid SQL date-time display format name.

System Action: The server does not process the command.

User Response: Reissue the command with a valid SQL date-time format name.

ANR2485ECommand: Invalid SQL display format - SQL display format name.

Explanation: The command indicated contains an invalid SQL display format name.

System Action: The server does not process the command.

User Response: Reissue the command with a valid SQL display format name.

ANR2486ECommand: Invalid SQL character arithmetic mode - SQL arithmetic mode.

Explanation: The command indicated contains an invalid SQL arithmetic mode name.

System Action: The server does not process the command.

User Response: Reissue the command with a valid SQL arithmetic mode name.

ANR2487ECommand: An SQL expression is required.

Explanation: The command indicated requires that an SQL expression be provided through the SQL keyword parameter.

System Action: The server does not process the command.

User Response: Reissue the command specifying an SQL expression.

ANR2488WVolume list file volume list file name could not be opened.

Explanation: While attempting to read or write a sequential file for volume list information, the server cannot open the file name specified.

System Action: The server does not use the volume list file.

User Response: Examine error messages that may have been displayed prior to this message and correct any problems, if possible. For OUTFILE files, make sure that the server has proper authority to write to the file indicated and that there is sufficient space in the file system for the file. On MVS, make sure that the server has authority to write to the data set.

ANR2489WAn error was encountered writing to volume list file volume list file name.

Explanation: While attempting to write to the sequential file for a volume list an error occurs on the file name specified. The volume list is not be complete and should not be used for input.

System Action: The server stops writing to the file.

User Response: Examine error messages that may have been displayed prior to this message and correct any problems, if possible. Make sure that the server has proper authority to write to the file indicated and that there is sufficient space in the file system for the file. On MVS, make sure that the server has authority to write to the data set. Obtain the volume list from console messages, the QUERY VOLHISTORY command or the volume history file, if it is used.

ANR2490ECommand: NODENAMES and SERVERNAMES parameters cannot both be specified in the same command.

Explanation: The command indicated failed because both the nodenames parameter and the servernames parameter were specified.

System Action: None.

User Response: Determine whether you want the action taken for one or more nodes or for one or more servers and reenter the command with only the correct parameter specified.

ANR2491IVolume Creation Process starting for volume name, Process Id process ID.

Explanation: As a result of a DEFINE VOLUME, DEFINE DBVOLUME, or DEFINE LOGVOLUME command with the SIZE=xxx parameter, a new volume is being created. The process whose ID is displayed has begun to create the volume shown.

System Action: The server creates the volume and adds it to the server.

User Response: None.

ANR2500ISchedule schedule name defined in policy domain domain name.

Explanation: This message is displayed in response to the DEFINE SCHEDULE command. The schedule named schedule name has been defined in the policy domain named domain name in the server database.

System Action: Server operation continues.

User Response: None.

ANR2501ISchedule schedule name deleted from policy domain domain name.

Explanation: This message is displayed in response to the DELETE SCHEDULE command. The schedule named schedule name has been deleted from the policy domain named domain name in the server database.

System Action: Server operation continues.

User Response: None.

ANR2502ISchedule schedule name updated in policy domain domain name.

Explanation: This message is displayed in response to the UPDATE SCHEDULE command. The schedule named schedule name has been updated in the policy domain named domain name in the server database.

System Action: Server operation continues.

User Response: None.

ANR2503ISchedule schedule name in domain domain name copied to schedule new schedule name in domain new domain name.

Explanation: This message is displayed in response to the COPY SCHEDULE command. The schedule named schedule name in policy domain domain name has been copied to the schedule named new schedule name in the policy domain named new domain name. Node associations have not been copied.

System Action: Server operation continues.

User Response: None.

ANR2504ISchedule schedule name deleted.

Explanation: This message is displayed in response to the DELETE SCHEDULE command. The schedule named schedule name has been deleted from the server database.

System Action: Server operation continues.

User Response: None.

ANR2505Inumber of schedules schedules were defined for command.

Explanation: number of schedules were generated and nodes successfully associated for the command issued.

System Action: Server operation continues.

User Response: If the number is less than expected, check the nodeList and domainList combination specified to the DEFINE CLIENTACTION command. Schedules are generated when at least one node in the nodeList exists in a domain in the domainList.

ANR2506INode node name associated with schedule schedule name in policy domain domain name processed. rc=return code.

Explanation: This message is displayed in response to the DEFINE CLIENTACTION WAIT=YES command. Node node name is associated with the schedule named schedule name in policy domain domain name has been processed. name The result is indicated in the return code return code.

System Action: Server operation continues.

User Response: If the return code is non-zero, issue the QUERY ACTLOG command to to view the activity log and search for the error messages. After the error has been resolved, restart the scheduled operations.

ANR2510INode node name associated with schedule schedule name in policy domain domain name.

Explanation: This message is displayed in response to the DEFINE ASSOCIATION command. Node node name is associated with the schedule named schedule name in policy domain domain name. Schedule schedule name is now applied to node node name.

System Action: Server operation continues.

User Response: None.

ANR2511INode node name disassociated from schedule schedule name in policy domain domain name.

Explanation: This message is displayed in response to the DELETE ASSOCIATION command. Node node name is no longer associated with the schedule named schedule name in policy domain domain name.

System Action: Server operation continues.

User Response: None.

ANR2512IEvent records deleted: record count.

Explanation: This message is displayed in response to the DELETE EVENT command. A total of record count event records have been deleted from the database.

System Action: Server operation continues.

User Response: None.

ANR2513ISchedule schedule name copied to schedule new schedule name.

Explanation: This message is displayed in response to the COPY SCHEDULE command. The schedule named schedule name has been copied to the schedule named new schedule name.

System Action: Server operation continues.

User Response: None.

ANR2520IScheduled sessions set to percent percent.

Explanation: This message is displayed in response to the SET MAXSCHEDSESSIONS command. It indicates the percentage of total server sessions that can be used for the processing of scheduled work.

System Action: Server operation continues.

User Response: None.

ANR2521IEvent record retention period set to days days.

Explanation: This message is displayed in response to the SET EVENTRETENTION command. It indicates the number of days for which event records are retained in the database.

System Action: Server operation continues.

User Response: None.

ANR2522IRandomization set to percent percent.

Explanation: This message is displayed in response to the SET RANDOMIZE command. It indicates the percentage of the startup window over which the start times for individual clients are distributed.

System Action: Server operation continues.

User Response: None.

ANR2523ISchedule query period set to hours hour(s).

Explanation: This message is displayed in response to the SET QUERYSCHEDPERIOD command. It indicates the number of hours between attempts by the client to contact the server for scheduled commands.

System Action: Server operation continues.

User Response: None.

ANR2524ISchedule query period reset to value determined by each client.

Explanation: This message is displayed in response to the SET QUERYSCHEDPERIOD command.

System Action: Server operation continues.

User Response: None.

ANR2525IMaximum number of command retries set to retries.

Explanation: This message is displayed in response to the SET MAXCMDRETRIES command. It indicates the maximum number of times the client scheduler retries a command after a failed attempt to process a scheduled command.

System Action: Server operation continues.

User Response: None.

ANR2526IMaximum number of command retries reset to value determined by each client.

Explanation: This message is displayed in response to the SET MAXCMDRETRIES command.

System Action: Server operation continues.

User Response: None.

ANR2527IRetry period set to minutes minutes.

Explanation: This message is displayed in response to the SET RETRYPERIOD command. It indicates the number of minutes between attempts by the client scheduler to retry, after a failed attempt, to contact the server or to process a scheduled command.

System Action: Server operation continues.

User Response: None.

ANR2528IRetry period reset to value determined by each client.

Explanation: This message is displayed in response to the SET RETRYPERIOD command.

System Action: Server operation continues.

User Response: None.

ANR2529IScheduling mode set to POLLING.

Explanation: This message is displayed in response to the SET SCHEDMODES command. With client-polling scheduling, a client queries the server at prescribed time intervals to obtain scheduled work or to ensure that the schedules the client is waiting to process have not changed.

System Action: Server operation continues.

User Response: None.

ANR2530IScheduling mode set to PROMPTED.

Explanation: This message is displayed in response to the SET SCHEDMODES command. With server-prompted scheduling, the server contacts the client when scheduled work needs to be performed and a session is available.

System Action: Server operation continues.

User Response: None.

ANR2531IScheduling mode set to ANY.

Explanation: This message is displayed in response to the SET SCHEDMODES command. The server now allows clients to run in either the client-polling or the server-prompted scheduling mode.

System Action: Server operation continues.

User Response: None.

ANR2532ISchedule schedule name updated.

Explanation: This message is displayed in response to the UPDATE SCHEDULE command. The schedule named schedule name has been updated in the server database.

System Action: Server operation continues.

User Response: None.

ANR2533IClient action schedule duration set to days days.

Explanation: This message is displayed in response to the Set CLIENTACTDuration command. It indicates the number of days for which schedules and associations generated by the DEFine CLIENTAction are retained in the database.

System Action: Server operation continues.

User Response: None.

ANR2534IClient action schedule schedule name was not executed by node name in domain name.

Explanation: Immediate client action schedule name was not executed by node node name, which is in domain domain name. The schedule is being deleted.

System Action: Server operation continues.

User Response: None.

ANR2550Wcommand name: Administrative schedule schedule name does not have valid activation information.

Explanation: This message is displayed during a database audit and indicates that the 'ACTIVE=YES or NO' information is not recorded correctly for an administrative schedule in the server database.

System Action: Server database audit operation continues.

User Response: Execute the AUDITDB operation specifying FIX=YES so that the activation information can be corrected.

ANR2551Icommand name: Administrative schedule schedule name does not have valid activation information - activation information will be deleted.

Explanation: This message is displayed during a database audit and indicates that the 'ACTIVE=YES or NO' information is not recorded correctly for an administrative schedule in the server database. The audit operation corrects this discrepancy by removing the invalid activation information.

System Action: Server database audit operation continues.

User Response: The named administrative schedule will now appear to be inactive in the server database (as if ACTIVE=NO was specified). If you want this schedule to be active, execute the UPDATE SCHEDULE command with the ACTIVE=YES parameter to activate the schedule when the server is restarted.

ANR2560ISchedule manager started.

Explanation: The schedule manager is started when the server is initialized. The schedule manager maintains entries of scheduled operations.

System Action: Server operation continues.

User Response: None.

ANR2561ISchedule prompter contacting node name (session session number) to start a scheduled operation.

Explanation: The schedule prompter contacts the client scheduler for node node name because a scheduled operation should be started for that node.

System Action: Server operation continues.

User Response: None.

ANR2562IAutomatic event record deletion started.

Explanation: A process has been started to delete event records for which the retention period has elapsed.

System Action: Server operation continues.

User Response: None.

ANR2563IRemoving event records dated prior to date time.

Explanation: Events that were scheduled to start prior to date time are automatically deleted unless their startup window has not yet elapsed.

System Action: Server operation continues.

User Response: None.

ANR2564IAutomatic event record deletion ended - record count records deleted.

Explanation: The event deletion process has ended. A total of record count event records have been deleted from the database.

System Action: Server operation continues.

User Response: None.

ANR2565Ischedules schedules for immediate client actions have been deleted.

Explanation: A total of schedules that were generated by the DEFINE CLIENTACTION command have expired and been deleted from the database.

System Action: Server operation continues.

User Response: None.

ANR2566EAn error occurred while deleting immediate client action schedules.

Explanation: Processing did not complete for deleting schedules that were generated by the DEFINE CLIENTACTION command.

System Action: Server operation continues.

User Response: Check the activity log for other messages that might relate to this failure. Correct any memory or space problems.

ANR2570WA scheduled session has been denied. The schedule manager is not active.

Explanation: The client scheduler attempts to connect with the server, but it is denied a session because the schedule manager is not active.

System Action: Server operation continues, but central scheduling is not operational.

User Response: Issue the QUERY OPTION command to determine if the option DISABLESCHEDS YES has been specified in the server options file. If so, scheduling can be enabled by updating the server options file with DISABLESCHEDS NO and restarting the server. If DISABLESCHEDS YES was not specfied in the server options file, determine the source of the error by examining the QUERY ACTLOG command to view the activity log and search for messages. After the error has been resolved, restart the server to restore central scheduler operations. If the error cannot be isolated and resolved, contact your service representative.

ANR2571WScheduled session from node node name (platform name) has been denied, scheduled sessions are not currently available.

Explanation: The client scheduler for node node name attempts to connect with the server, but is denied a session. All sessions that have been allocated for scheduled operations are already in use.

System Action: Server operation continues.

User Response: Issue the QUERY OPTION command to determine if the option DISABLESCHEDS YES has been specified in the server options file. If so, scheduling can be enabled by updating the server options file with DISABLESCHEDS NO and restarting the server. If DISABLESCHEDS YES was not specfied in the server options file, change the total number of sessions by altering the MAXSESSIONS parameter in the server options file and then restarting the server. The percentage of sessions that are available for scheduled operations can be increased by using the SET MAXSCHEDSESSIONS command.

ANR2572WSchedule prompter session to node node name has been denied, scheduled sessions are not currently available.

Explanation: The server attempts to prompt the client scheduler for node node name, but all sessions that have been allocated for scheduled operations are already in use.

System Action: The server continues to attempt contact with the client scheduler until the startup window for the scheduled event has elapsed.

User Response: To change the total number of sessions, alter the MAXSESSIONS parameter in the server options file and then restart the server. The percentage of sessions that are available for scheduled operations can be increased by using the SET MAXSCHEDSESSIONS command.

ANR2573WSufficient memory is not available for the central scheduler - will retry in number of seconds seconds.

Explanation: The server suspends central scheduler processing because sufficient server memory is not available.

System Action: Server operation continues; the scheduler operation will be retried after the specified delay.

User Response: Allocate additional storage to the server. For details, issue HELP MEMORY to display the information online or see "Appendix A. Allocating Additional Server Memory".

ANR2574WInsufficient recovery log space available for the central scheduler - will retry in number of seconds seconds.

Explanation: The server suspends central scheduler processing because sufficient recovery log space is not available.

System Action: Server operation continues; the scheduler operation will be retried after the specified delay.

User Response: To increase the amount of log space available to the server, an authorized administrator can add log volumes by using the DEFINE LOGVOLUME command, and can extend the size of the log by using the EXTEND LOG command.

ANR2575WInsufficient database space available for the central scheduler - will retry in number of seconds seconds.

Explanation: The server suspends central scheduler processing because sufficient database space is not available.

System Action: Server operation continues; the scheduler operation will be retried after the specified delay.

User Response: To increase the amount of database space available to the server, an authorized administrator can add database volumes by using the DEFINE DBVOLUME command, and can extend the size of the log by using the EXTEND DB command.

ANR2576WAn attempt was made to update an event record for a scheduled operation which has already been executed - multiple client schedulers may be active for node node name.

Explanation: The server has attempted to update an event record for a scheduled operation for the specified client node. However, the existing event record shows that this scheduled operation has already been executed, either successfully or unsuccessfully. Two or more client schedulers may be running for this node.

System Action: Server operation continues. The existing event record is not modified. No further processing is performed for this scheduled operation.

User Response: Contact the user for this client node, and make sure that only one client scheduler is running.

ANR2577ISchedule schedule name defined.

Explanation: This message is displayed in response to the DEFINE SCHEDULE command. The schedule named schedule name in the server database.

System Action: Server operation continues.

User Response: None.

ANR2578ISchedule schedule name in domain domain name for node node name has missed its scheduled start up window.

Explanation: This message is displayed when the scheduled startup window for this schedule has passed and the schedule has not begun.

System Action: Server operation continues. The scheduled operation is not processed by the server.

User Response: Ensure that a scheduled session for node node name has been initiated from the client to the server. Refer to Administrator's Guide and Administrator's Reference for more information on setting up scheduling operations.

ANR2579ESchedule schedule name in domain domain name for node node name failed (return code return code).

Explanation: This message is displayed when a client reports failure in executing a scheduled action. The return code reported by the client is displayed.

System Action: Server operation continues.

User Response: Examine the node's schedule log to determine the cause for the failure.

ANR2580ESchedule schedule name in domain domain name for node node name failed.

Explanation: This message is displayed when the server finds that a scheduled start window has elapsed for a client schedule and the client is not currently running the schedule.

System Action: Server operation continues.

User Response: Examine the node's schedule log to determine the cause for the failure. Ensure that the client scheduler is started.

ANR2600ECommand: Invalid schedule name - schedule name.

Explanation: The specified command has been issued with an invalid schedule name.

System Action: Server operation continues, but the command is not processed.

User Response: Issue the command with a valid schedule name.

ANR2601ECommand: Schedule description exceeds maximum length characters.

Explanation: The specified command has been issued with a description that exceeds the maximum length.

System Action: Server operation continues, but the command is not processed.

User Response: Issue the command and specify a valid description.

ANR2602ECommand: Invalid action - action.

Explanation: The specified command has been issued with an invalid action.

System Action: Server operation continues, but the command is not processed.

User Response: Issue the command and specify a valid action.

ANR2603ECommand: Options string exceeds maximum length characters.

Explanation: The specified command has been issued with an options string that exceeds the maximum length.

System Action: Server operation continues, but the command is not processed.

User Response: Issue the command with a valid options string.

ANR2604ECommand: Objects string exceeds maximum length characters.

Explanation: The specified command has been issued with an objects string that exceeds the maximum length.

System Action: Server operation continues, but the command is not processed.

User Response: Issue the command with a valid objects string.

ANR2605ECommand: Invalid priority - priority.

Explanation: The specified command has been issued with an invalid priority.

System Action: Server operation continues, but the command is not processed.

User Response: Issue the command and specify a valid priority.

ANR2606ECommand: Invalid start date - date.

Explanation: The specified command has been issued with an invalid start date.

System Action: Server operation continues, but the command is not processed.

User Response: Issue the command and specify a valid start date.

ANR2607ECommand: Invalid start time - time.

Explanation: The specified command has been issued with an invalid start time.

System Action: Server operation continues, but the command is not processed.

User Response: Issue the command and specify a valid start time.

ANR2608ECommand: Invalid duration - duration.

Explanation: The specified command has been issued with an invalid duration.

System Action: Server operation continues, but the command is not processed.

User Response: Issue the command and specify a valid duration.

ANR2609ECommand: Invalid duration units - duration units.

Explanation: The specified command has been issued with an invalid value for duration units.

System Action: Server operation continues, but the command is not processed.

User Response: Issue the command and specify a valid value for duration units.

ANR2610ECommand: Invalid period - period.

Explanation: The specified command has been issued with an invalid period.

System Action: Server operation continues, but the command is not processed.

User Response: Issue the command and specify a valid period.

ANR2611ECommand: Invalid period units - period units.

Explanation: The specified command has been issued with an invalid value for period units.

System Action: Server operation continues, but the command is not processed.

User Response: Issue the command and specify a valid value for period units.

ANR2612ECommand: Invalid day of week - day of week.

Explanation: The specified command has been issued with an invalid value for day of the week.

System Action: Server operation continues, but the command is not processed.

User Response: Issue the command and specify a valid value for day of the week.

ANR2613ECommand: Invalid expiration - date.

Explanation: The specified command has been issued with an invalid expiration date.

System Action: Server operation continues, but the command is not processed.

User Response: Issue the command and specify a valid expiration date.

ANR2614ECommand: Invalid combination of the following parameters: duration, duration units, period, period units.

Explanation: The specified command has been issued with an invalid combination of the DURATION, DURUNITS, PERIOD, and PERUNITS parameters. This message may be displayed if the duration of the startup window for the schedule is not shorter than the period between windows. This message may also be displayed if DURUNITS=INDefinite is specified, but PERUNITS=Onetime is not specified.

System Action: Server operation continues, but the command is not processed.

User Response: Issue the command and specify a valid combination of parameters.

ANR2615ECommand: Expiration date date has elapsed.

Explanation: The specified command has been issued with an elapsed expiration date date.

System Action: Server operation continues, but the command is not processed.

User Response: Issue the command and specify an expiration date that has not already elapsed.

ANR2616ECommand: Start date start date must be earlier than expiration date expiration.

Explanation: The specified command has been issued with a start date that is not earlier than the expiration date.

System Action: Server operation continues, but the command is not processed.

User Response: Issue the command using a schedule start date that is earlier than the expiration date.

ANR2617ECommand: Schedule schedule name is not defined in policy domain domain name.

Explanation: The specified command has been issued with a schedule name that has not been defined in the indicated policy domain.

System Action: Server operation continues, but the command is not processed.

User Response: Issue the command using a schedule that has already been defined for this domain.

ANR2618ECommand: Schedule schedule name is already defined in policy domain domain name.

Explanation: The specified command has been issued with a schedule name that has already been defined for the indicated policy domain.

System Action: Server operation continues, but the command is not processed.

User Response: Issue the command using a schedule that has not already been defined for this domain.

ANR2619ECommand: Currently defined period period is invalid with updated period units.

Explanation: The specified command has been issued with a value for period units that is not allowed with the existing period.

System Action: Server operation continues, but the command is not processed.

User Response: Issue the command and specify a new period.

ANR2620ECommand: Currently defined duration duration is invalid with updated duration units.

Explanation: The specified command has been issued with a value for duration units that is not allowed with the existing duration.

System Action: Server operation continues, but the command is not processed.

User Response: Issue the command and specify a new duration.

ANR2621ECommand: No matching schedules.

Explanation: The specified command has been issued but no matching schedules have been found.

System Action: Server operation continues, but the command is not processed.

User Response: Issue the command and specify different schedules.

ANR2622ECommand: No new node associations added.

Explanation: The specified command has been issued but no new node associations are defined.

System Action: Server operation continues, but the command has no effect.

User Response: Issue the command and specify different nodes.

ANR2623ECommand: No node associations deleted.

Explanation: The specified command has been issued but no node associations are deleted.

System Action: Server operation continues, but the command has no effect.

User Response: Issue the command and specify different nodes.

ANR2624ECommand: No matching nodes registered.

Explanation: No matching nodes are found for the specified command.

System Action: Server operation continues, but the command is not processed.

User Response: Issue the command and specify different nodes.

ANR2625ECommand: No matching nodes registered in policy domain domain name.

Explanation: The specified command has been issued, but no matching nodes are registered in the indicated policy domain.

System Action: Server operation continues, but the command is not processed.

User Response: Issue the command and specify different nodes.

ANR2626ECommand: Invalid value for replace - replace.

Explanation: The specified command has been issued with an invalid value for replace.

System Action: Server operation continues, but the command is not processed.

User Response: Issue the command using a valid value for replace.

ANR2627ECommand: Invalid value for format - format.

Explanation: The specified command has been issued with an invalid value for format.

System Action: Server operation continues, but the command is not processed.

User Response: Issue the command using a valid value for format.

ANR2628ECommand: Invalid date - date.

Explanation: The specified command has been issued with an invalid date.

System Action: Server operation continues, but the command is not processed.

User Response: Issue the command with a valid date.

ANR2629ECommand: Invalid time - time.

Explanation: The specified command has been issued with an invalid time.

System Action: Server operation continues, but the command is not processed.

User Response: Issue the command with a valid time.

ANR2630ECommand: Event deletion is already in process.

Explanation: The specified command has been issued while event deletion is already in progress.

System Action: Server operation continues, but the command is not processed.

User Response: Wait for event deletion to complete before issuing the command.

ANR2631ECommand: Invalid begin date - date.

Explanation: The specified command has been issued with an invalid begin date.

System Action: Server operation continues, but the command is not processed.

User Response: Issue the command with a valid begin date.

ANR2632ECommand: Invalid begin time - date.

Explanation: The specified command has been issued with an invalid begin time.

System Action: Server operation continues, but the command is not processed.

User Response: Issue the command with a valid begin time.

ANR2633ECommand: Invalid end date - date.

Explanation: The specified command has been issued with an invalid end date.

System Action: Server operation continues, but the command is not processed.

User Response: Issue the command with a valid end date.

ANR2634ECommand: Invalid end time - time.

Explanation: The specified command has been issued with an invalid end time.

System Action: Server operation continues, but the command is not processed.

User Response: Issue the command with a valid end time.

ANR2635ECommand: Invalid time range - Begin: begin End: end.

Explanation: The specified command has been issued with an invalid time range. This occurs if the date and time for the beginning of the time range (begin) do not precede the date and time for the end of the time range (end).

System Action: Server operation continues, but the command is not processed.

User Response: Issue the command with a valid time range.

ANR2636ECommand: Invalid value for exceptions only - exceptions only.

Explanation: The specified command has been issued with an invalid value for exceptions only.

System Action: Server operation continues, but the command is not processed.

User Response: Issue the command with a valid value for exceptions only.

ANR2640ECommand: Invalid percentage of sessions for scheduled processing - value.

Explanation: The specified command has been issued with an invalid value.

System Action: Server operation continues, but the command is not processed.

User Response: Issue the command with a valid value.

ANR2641ECommand: Invalid event record retention period - value.

Explanation: The specified command has been issued with an invalid value.

System Action: Server operation continues, but the command is not processed.

User Response: Issue the command with a valid value.

ANR2642ECommand: Invalid percentage for randomization - value.

Explanation: The specified command has been issued with an invalid value.

System Action: Server operation continues, but the command is not processed.

User Response: Issue the command with a valid value.

ANR2643ECommand: Invalid schedule query period - value.

Explanation: The specified command has been issued with an invalid value.

System Action: Server operation continues, but the command is not processed.

User Response: Issue the command with a valid value.

ANR2644ECommand: Invalid maximum number of command retries - value.

Explanation: The specified command has been issued with an invalid value.

System Action: Server operation continues, but the command is not processed.

User Response: Issue the command with a valid value.

ANR2645ECommand: Invalid retry period - value.

Explanation: The specified command has been issued with an invalid value.

System Action: Server operation continues, but the command is not processed.

User Response: Issue the command with a valid value.

ANR2646ECommand: Invalid scheduling mode - value.

Explanation: The specified command has been issued with an invalid value.

System Action: Server operation continues, but the command is not processed.

User Response: Issue the command with a valid value.

ANR2647ECommand: Invalid type - type.

Explanation: The specified command has been issued with an invalid type.

System Action: Server operation continues, but the command is not processed.

User Response: Issue the command with a valid type.

ANR2648ECommand: Type string exceeds maximum length characters.

Explanation: The specified command has been issued with a type string that exceeds the maximum length.

System Action: Server operation continues, but the command is not processed.

User Response: Issue the command with a valid type string.

ANR2649ECommand: Schedule schedule name is not defined.

Explanation: The specified command has been issued with a schedule name that has not been defined.

System Action: Server operation continues, but the command is not processed.

User Response: Issue the command with a schedule that has already been defined.

ANR2650ECommand: Schedule schedule name is already defined.

Explanation: The specified command has been issued with a schedule name that has already been defined.

System Action: Server operation continues, but the command is not processed.

User Response: Issue the command with a schedule name that has not already been defined.

ANR2651ECommand: Invalid combination of one or more of the following parameters: cmd, type, action, objects, options.

Explanation: The specified command has been issued with an invalid combination of the CMD, ACTION, OBJECTS, and OPTIONS parameters. This message is displayed when the CMD parameter is specified and TYPE=CLIENT is not specified, or when TYPE=ADMIN is specified, and one or more of the following is specified: ACTION, OBJECTS, or OPTIONS.

System Action: Server operation continues, but the command is not processed.

User Response: Issue the command with a valid combination of parameters.

ANR2652ECommand: Invalid combination of one or more of the following parameters: active, cmd, type.

Explanation: The specified command has been issued with an invalid combination of the TYPE, CMD, or ACTIVE parameters. This message is displayed when TYPE=CLIENT is specified and one or more of the following is specified: ACTIVE, CMD.

System Action: Server operation continues, but the command is not processed.

User Response: Issue the command with a valid combination of parameters.

ANR2653WCommand: Node node name cannot be processed because it is not registered or does not belong to the specified domain.

Explanation: This command cannot be processed for the indicated node. Either the node is not registered or it is not assigned to the required domain.

System Action: The indicated node is not processed, but other nodes may be processed if specified by this command.

User Response: If the node name was entered incorrectly, reissue the command with the correct node name.

ANR2654ECommand: The NODES parameter cannot be used when querying administrative schedules.

Explanation: A QUERY SCHEDULE command has been issued with TYPE=ADMINISTRATIVE and the NODES parameter both specified. The NODES parameter cannot be specified when querying administrative schedules.

System Action: Server operation continues, but the command is not processed.

User Response: Issue the command without the NODES parameter.

ANR2655ECommand: Invalid client action schedule duration - days.

Explanation: The specified command has been issued with an invalid number of days. Valid values are 1 to 9999 inclusive. days specifies the length of time during which a schedule defined by the DEFine CLIENTAction command must be executed by an associated node. After that, the schedule will be deleted from the database.

System Action: Server operation continues, but the command is not processed.

User Response: Reissue the command with a valid number of days.

ANR2700ESchedule manager aborted.

Explanation: The schedule manager has ended because of an error condition and is not able to maintain entries for scheduled operations.

System Action: Server operation continues, but the central scheduler is not operational.

User Response: To determine the source of the error, examine server messages issued prior to this message. Issue the QUERY ACTLOG command to view the activity log and search for messages. After the error has been resolved, restart the server to restore central scheduler operations. If the error cannot be isolated and resolved, contact your service representative.

ANR2701EThe schedule manager could not be started: diagcode.

Explanation: The schedule manager cannot be started during initialization because sufficient memory is not available. Diagnostic code diagcode is issued.

System Action: Initialization fails.

User Response: Allocate additional storage to the server. For details, issue HELP MEMORY to display the information online or see "Appendix A. Allocating Additional Server Memory".

ANR2702EThe schedule prompter could not be started: diagcode.

Explanation: The schedule prompter cannot be started during initialization because sufficient memory is not available. Diagnostic code diagcode is issued.

System Action: Initialization fails.

User Response: Allocate additional storage to the server. For details, issue HELP MEMORY to display the information online or see "Appendix A. Allocating Additional Server Memory".

ANR2703ESchedule prompter aborted.

Explanation: The schedule prompter ends because of a processing error.

System Action: Server operation continues, but prompted scheduling is not operational.

User Response: To determine the source of the error, examine server messages issued prior to this message. Issue the QUERY ACTLOG command to view the activity log and search for messages. After the error has been resolved, restart the server to restore central scheduler prompting operations. If the error cannot be isolated and resolved, contact your service representative.

ANR2707EOut of server log space in central scheduler.

Explanation: The server ends a database update transaction for the central scheduler because sufficient log space is not available on the server.

System Action: Server operation continues, but the database update fails.

User Response: An authorized administrator can use the DEFINE LOGVOLUME command to add volumes for use by the log and can issue the EXTEND LOG command to extend the size of the log so that the new volumes are used.

ANR2708EOut of server database space in central scheduler.

Explanation: The server ends a database update transaction for the central scheduler because sufficient database space is not available on the server.

System Action: Server operation continues, but the database update fails.

User Response: An authorized administrator can use the DEFINE DBVOLUME command to add volumes for use by the database and can use the EXTEND DB command to extend the size of the database so that the new volumes are used.

ANR2709ESchedule manager: Unable to start event record deletion.

Explanation: Event record deletion cannot be started because sufficient memory is not available.

System Action: Server operation continues, but event records are not automatically deleted after their retention period has elapsed.

User Response: Allocate additional storage to the server. For details, issue HELP MEMORY to display the information online or see "Appendix A. Allocating Additional Server Memory".

ANR2712ENode node1 requested scheduling information for node node2 - session rejected.

Explanation: A request for pending scheduled operations has been sent from the client scheduler for node node1. However, the request is for scheduling information concerning another node node2.

System Action: Server operation continues, but the client scheduler for node node1 will not be able to process pending operations.

User Response: Try restarting the client scheduler for node node1. If the problem persists, contact your service representative to resolve the client program error.

ANR2713ENode node1 trying to start scheduled operation for node node2 - session rejected.

Explanation: The client scheduler for node node1 has attempted to execute a scheduled operation for another node, node2.

System Action: Server operation continues, but the scheduled operation is not processed.

User Response: Try restarting the client scheduler for node node1. If the problem persists, contact your service representative to resolve client program error.

ANR2714ENode node1 trying to report scheduled operation results for node node2 - session rejected.

Explanation: The client scheduler for node node1 has attempted to report the results of a scheduled operation using another node name, node2.

System Action: Server operation continues, but the results that were sent from node node1 are not be stored in the server's database.

User Response: Try restarting the client scheduler for node node1. If the problem persists, contact your service representative to resolve the client program error.

ANR2715EClient node node name unable to register valid address for server prompting: type address type (high address low address).

Explanation: The client scheduler for node node name has attempted to register an invalid address for server-prompted central scheduling. The address was type address type with high-level field high address and low-level field low address. The only valid address type is 1.

System Action: Server operation continues, but the node node name will not be prompted to perform scheduled operations.

User Response: Verify that the address type and address are correct for this client. The only valid address type is 1 (for TCP/IP). Make sure the client scheduler is not using an invalid address obtained from the client's options file or from the command line when the client scheduler was started.

ANR2716ESchedule prompter was not able to contact client node name using type address type (high address low address).

Explanation: The server has attempted to prompt the client scheduler for node node name because a scheduled operation should be started. The server is unable to contact the client by using address type address type, with high-level field high address and low-level field low address.

System Action: Server operation continues, but node node name is not prompted to start the scheduled operation. If operations should be started for other nodes, the server will attempt to prompt the client schedulers for these nodes. This error is usually caused by network outages or the client scheduler program not being run on the client node.

User Response: Verify that the address type and address are correct for this client. The only valid address type is 1 (for TCP/IP). Make sure the client scheduler is not using an invalid address, obtained at the time the client scheduler was started, from either the client's options file or from the command line. Verify that the client scheduler for node node name is running and that the necessary communication links to that scheduler are operational.

ANR2717ESchedule prompter cannot contact client node name using address type (address type).

Explanation: The server attempts to prompt the client scheduler for node node name because scheduled work should be started. However, either the server does not support address type address type needed for server-prompted scheduling, or the communication method is not currently available. The only valid address type is 1 (for TCP/IP).

System Action: Server operation continues, but the server does not prompt node node name.

User Response: If the server does not support the address type specified, clients may only use the polling mode of scheduling. If the communication method is temporarily not available, prompted mode scheduling will resume after the communication problem is fixed and service restored. If the problem persists, contact your service representative.

ANR2718WSchedule manager disabled.

Explanation: The schedule manager has been disabled because the DISABLESCHEDS YES option was specified in the server options file.

System Action: Server operation continues, but the central scheduler is not operational.

User Response: To enable the schedule manager, specify DISABLESCHEDS NO in the server options file and restart the server.

ANR2750IStarting scheduled command schedule name ( scheduled command ).

Explanation: This message is displayed when the server starts the execution of a scheduled command. The name of the schedule and the actual command scheduled is displayed.

System Action: Server operation continues, the scheduled command is processed.

User Response: None.

ANR2751IScheduled command schedule name completed successfully.

Explanation: This message is displayed when the server successfully completes processing of a scheduled command.

System Action: Server operation continues.

User Response: None.

ANR2752EScheduled command schedule name failed.

Explanation: This message is displayed when the server encounters a failure in processing a scheduled command.

System Action: Server operation continues. The scheduled command is ended.

User Response: Examine messages issued prior to this message and use the UPDATE SCHEDULE command to correct the scheduled command. The QUERY EVENT command may also be used to determine the cause of the failure for this scheduled command.

ANR2753I(Schedule name):command response

Explanation: This message is used to display the server response to a scheduled command. The name of the command schedule is included at the beginning of the message in parentheses.

System Action: Server operation continues. The scheduled command is ended.

User Response: None.

ANR2754EDEFINE SCHEDULE or UPDATE SCHEDULE parameter CMD='command' - Unknown command.

Explanation: The specified command is not a valid server command.

System Action: The DEFINE SCHEDULE or UPDATE SCHEDULE command is not processed.

User Response: Reissue the correct command.

ANR2755EDEFINE SCHEDULE or UPDATE SCHEDULE parameter CMD='command' - not eligible for scheduling.

Explanation: The specified command is not eligible for scheduling.

System Action: The DEFINE SCHEDULE or UPDATE SCHEDULE command is not processed.

User Response: None.

ANR2756IScheduled command schedule name started successfully.

Explanation: This message is displayed when the server successfully starts processing of a background process for a scheduled command.

System Action: Server operation continues.

User Response: None.

ANR2757ECommand: The NODES parameter cannot be used when querying events for administrative schedules.

Explanation: A QUERY EVENT command has been issued with TYPE=ADMINISTRATIVE and the NODES parameter both specified. The NODES parameter cannot be specified when querying events for administrative schedules.

System Action: Server operation continues, but the command is not processed.

User Response: Issue the command without the NODES parameter.

ANR2780WCommand: Updates for nodes previously processed during this command will be rolled back.

Explanation: An error has occurred during an UPDATE NODE operation. If the UPDATE NODE command was processing more than one node, updates for nodes which were previously processed will be rolled back.

System Action: Server operation continues.

User Response: Correct the error and reissue the command.

ANR2800EThe license manager cannot be started: diagcode.

Explanation: The license manager cannot be started during initialization because sufficient memory is not available. Diagnostic code diagcode is issued.

System Action: Initialization fails.

User Response: Allocate additional storage to the server. For details, issue HELP MEMORY to display the information online or see "Appendix A. Allocating Additional Server Memory".

ANR2803ILicense manager started.

Explanation: The license manager is started when the server is initialized. The license manager monitors license compliance.

System Action: Server operation continues.

User Response: None.

ANR2804WInsufficient memory is available for the license manager - will retry in number of seconds seconds.

Explanation: The server suspends license manager processing because sufficient server memory is not available.

System Action: Server operation continues; the license manager operation will be retried after the specified delay.

User Response: Allocate additional storage to the server. For details, issue HELP MEMORY to display the information online or see "Appendix A. Allocating Additional Server Memory".

ANR2805WInsufficient recovery log space available for the license manager - will retry in number of seconds seconds.

Explanation: The server suspends license manager processing because sufficient recovery log space is not available.

System Action: Server operation continues; the license manager operation will be retried after the specified delay.

User Response: To increase the amount of log space available to the server, an authorized administrator can add log volumes using the DEFINE LOGVOLUME command, and can extend the size of the log using the EXTEND LOG command.

ANR2806WInsufficient database space available for the license manager - will retry in number of seconds seconds.

Explanation: The server suspends license manager processing because sufficient database space is not available.

System Action: Server operation continues; the license manager operation will be retried after the specified delay.

User Response: To increase the amount of database space available to the server, an authorized administrator can add database volumes using the DEFINE DBVOLUME command, and can extend the size of the log using the EXTEND DB command.

ANR2807EOut of server log space in license manager.

Explanation: The server ends a database update transaction for the license manager because sufficient recovery log space is not available on the server.

System Action: Server operation continues, but the database update fails.

User Response: An authorized administrator can use the DEFINE LOGVOLUME command to add volumes for use by the log and can issue the EXTEND LOG command to extend the size of the log so that the new volumes are used.

ANR2808EOut of server database space in license manager.

Explanation: The server ends a database update transaction for the license manager because sufficient database space is not available on the server.

System Action: Server operation continues, but the database update fails.

User Response: An authorized administrator can use the DEFINE DBVOLUME command to add volumes for use by the database and can use the EXTEND DB command to extend the size of the database so that the new volumes are used.

ANR2811IAudit License completed - Server is in compliance with license terms.

Explanation: The results from the AUDIT LICENSES command indicate the server is in compliance with the terms of the current license.

System Action: Server operation continues.

User Response: None.

ANR2812WLicense Audit completed - ATTENTION: Server is NOT in compliance with license terms.

Explanation: The results from the AUDIT LICENSES command indicate the server is not in compliance with the terms of the current license.

System Action: Server operation continues, but the REGISTER NODE command or backup-archive requests, or both, will fail.

User Response: Use the QUERY LICENSE command to determine the license terms that are no longer in compliance.

ANR2813IServer is licensed for a capacity of capacity gigabytes and number of clients clients.

Explanation: This message is issued during server startup.

System Action: Server operation continues.

User Response: None.

ANR2814IAudit command: License audit period changed to number of days days.

Explanation: This message is displayed in response to the SET LICENSEAUDITPERIOD command used to change the interval in days between automatic license audits.

System Action: Server processing continues.

User Response: None.

ANR2815ECommand: Invalid value specified for interval between license audits - value.

Explanation: The specified command has been issued with an invalid value.

System Action: Server operation continues, but the command is not processed.

User Response: Issue the command with a valid value.

ANR2816ECommand: License audit operation already in progress.

Explanation: The server is currently performing a license audit.

System Action: The server does not process the specified command.

User Response: Reissue the command after the license audit process ends.

ANR2817ICommand: License audit started as process process ID.

Explanation: A background process has been started to audit the server for license compliance.

System Action: The server checks the existing configuration for the server and compares it against the values for which the server is licensed.

User Response: The administrator may query the status of the background process by using the QUERY PROCESS command, or cancel the process with the CANCEL PROCESS command.

ANR2818ICommand: Licensed capacity is capacity GB with number of clients clients.

Explanation: This message displays the license information that existed before issuing the REGISTER LICENSE command.

System Action: None.

User Response: None.

ANR2819ICommand: Licensed capacity changed to capacity GB with number of clients clients.

Explanation: The license information has been changed to the indicated values with the REGISTER LICENSE command.

System Action: None.

User Response: To implement the changed license information, issue an AUDIT LICENSES command or wait until an automatic license audit occurs.

ANR2820IAutomatic license audit started as process process ID.

Explanation: A background process has been started to audit the server for license compliance.

System Action: The server checks storage utilization and registered nodes for the server and licensed factors, comparing these against the values for which the server is licensed.

User Response: The administrator may query the status of the background process using the QUERY PROCESS command.

ANR2821EAutomatic license audit could not be started: diagcode.

Explanation: The license manager cannot start an automatic process to audit server licenses because sufficient memory is not available. Diagnostic code diagcode is issued.

System Action: Server processing continues.

User Response: Allocate additional storage to the server. For details, issue HELP MEMORY to display the information online or see "Appendix A. Allocating Additional Server Memory".

ANR2822ICancel in progress

Explanation: The license audit operation has been cancelled and will end when resources have been freed for the background process. This message may be displayed in response to a QUERY PROCESS command for an AUDIT LICENSES operation.

System Action: Server operation continues.

User Response: None.

ANR2823IHave audited number of nodes nodes

Explanation: An AUDIT LICENSES operation is in progress. The process has audited the specified number of nodes. This message may be displayed in response to a QUERY PROCESS command for an AUDIT LICENSES operation.

System Action: Server operation continues.

User Response: None.

ANR2824ILicense audit process process number canceled - number of nodes nodes audited.

Explanation: A background server process to audit server licenses has been canceled by using the CANCEL PROCESS command. The number of nodes that have been audited before the operation ended are reported in the message.

System Action: The server process is ended and server operation continues.

User Response: None.

ANR2825ILicense audit process process number completed successfully - number of nodes nodes audited.

Explanation: A background server process to audit server licenses has completed successfully after auditing the specified number of nodes.

System Action: The server process is ended and server operation continues.

User Response: None.

ANR2826ILicense audit process process number terminated in error - number of nodes nodes audited.

Explanation: A background server process to audit server licenses encounters an error and is ended. The number of nodes that have been audited before the operation ended is reported in the message.

System Action: The server process is ended and server operation continues.

User Response: None.

ANR2832ICommand: The License Manager has not yet completed initialization - please retry this command later.

Explanation: While attempting to process the specified license command, the server detects that the licensing component of the server had not completed initialization. The licensing facility used on some platforms may require some time to initialize because network calls are involved, and waits may occur.

System Action: Server operation continues; the command is not processed.

User Response: Reissue the command after waiting 10 minutes. If this message is displayed after a number of retry attempts, contact your service representative.

ANR2833ICommand: Auditing license definitions.

Explanation: The server has started to audit database definitions that describe licensing information.

System Action: Server database audit operation continues.

User Response: None.

ANR2834WLicense Audit completed - WARNING: Server is NOT in compliance with license terms.

Explanation: The results from the AUDIT LICENSES command indicate that the server is not in compliance with the terms of the current license.

System Action: Server operation continues, but the REGISTER NODE command fails.

User Response: Use the QUERY LICENSE command to determine the license terms that are no longer in compliance. Remove nodes or purchase additional client node connections. After these actions have been taken, reissue the AUDIT LICENSES command to resynchronize the server configuration with license terms.

ANR2836ICommand: License audit started as process process ID.

Explanation: A background process has been started to audit the server for license compliance.

System Action: The server checks registered nodes for the server and compares this against the value for which the server is licensed.

User Response: The administrator may query the status of the background process using the QUERY PROCESS command, or cancel the process with the CANCEL PROCESS command.

ANR2839IAutomatic license audit started as process process ID.

Explanation: A background process has been started to audit the server for license compliance.

System Action: The server checks registered nodes and compares them against the value for which the server is licensed.

User Response: The administrator may query the status of the background process by using the QUERY PROCESS command.

ANR2841WServer is NOT IN COMPLIANCE with license terms.

Explanation: This message is issued periodically when the server configuration does not comply with the terms for which it is licensed.

System Action: Server operation continues.

User Response: Use the QUERY LICENSE command to display the current server configuration with respect to licensed terms to discover which factors of the configuration do not conform to your license. Contact your service representative to obtain more licenses, if required.

ANR2852ICurrent license information:

Explanation: This message is issued during a REGISTER LICENSE command to display the current licensing information for the server before the new license has been interpreted by the command. Messages appearing after this message display the factors under which the server is currently licensed.

System Action: Server operation continues.

User Response: None.

ANR2853INew license information:

Explanation: This message is issued during a REGISTER LICENSE command to display the updated licensing information for the server after the new license has been interpreted by the command. Messages appearing after this message display the updated factors under which the server is licensed.

System Action: Server operation continues.

User Response: Check to make sure that the new license information includes the updates that you intended for the REGISTER LICENSE command. If the license terms do not change, check the parameters and reissue the command, if you find that it was not entered correctly. If the REGISTER LICENSE command does not produce the desired updates in terms of licensing, contact your service representative.

ANR2855IServer is licensed to support Tivoli Space Manager clients.

Explanation: This message is issued during server startup.

System Action: Server operation continues.

User Response: None.

ANR2860IServer is licensed to support Tivoli Disaster Recovery Manager.

Explanation: This message is issued during server startup.

System Action: Server operation continues.

User Response: None.

ANR2900WThe character string 'string' was truncated during assignment.

Explanation: Truncation occurred during assignment of an SQL character string. For example, the expression CAST( 'Hello' AS CHAR(2) ) will result in truncation because the string 'Hello' (length 5) can not fit in the target type CHAR(2) without loss of trailing characters.

System Action: This warning can occur before or after SQL query processing, but does not terminate query processing.

User Response: None.

ANR2901WThe result of character string concatenation was truncated.

Explanation: Truncation occurred when the concatenation of character strings resulted in a length that exceeds the maximum character string length (250 for data type CHAR, and 2000 for data type VARCHAR).

System Action: This warning can occur before or after SQL query processing, but does not terminate query processing.

User Response: None.

ANR2902EInsufficient memory was available to process the SQL statement.

Explanation: Sufficient memory was not available to complete the processing of an SQL query.

System Action: The SQL query is terminated.

User Response: None.

ANR2903EAn SQL parser stack overflow occurred while processing token 'token'.

Explanation: The internal stack used by the SQL query parser has overflowed. This typically occurs when too many column names or expressions have been specified in the SELECT clause.

System Action: The SQL query is terminated.

User Response: None.

ANR2904EUnexpected SQL key word token - 'token'.

Explanation: A syntax error occurred because an SQL key word was found that can not legally be used at the specified position within the SQL statement. Examples of SQL key words are SELECT, FROM, and WHERE.

System Action: The SQL query is terminated.

User Response: None.

ANR2905EUnexpected SQL identifier token - 'token'.

Explanation: A syntax error occurred because an SQL identifier was found that can not legally be used at the specified position within the SQL statement. Examples of SQL identifiers are table names and column names.

System Action: The SQL query is terminated.

User Response: None.

ANR2906EUnexpected SQL literal token - 'token'.

Explanation: A syntax error occurred because an SQL literal token was found that can not legally be used at the specified position within the SQL statement. Examples of SQL literal tokens are 'abc', 1.567, and DATE '1/1/96'.

System Action: The SQL query is terminated.

User Response: None.

ANR2907EUnexpected SQL operator token - 'token'.

Explanation: A syntax error occurred because an SQL operator token was found that can not legally be used at the specified position within the SQL statement. Examples of SQL operator tokens are +, *, <, and =.

System Action: The SQL query is terminated.

User Response: None.

ANR2908EUnexpected SQL punctuation token - 'token'.

Explanation: A syntax error occurred because an SQL punctuation token was found that can not legally be used at the specified position within the SQL statement. Examples of SQL punctuation tokens are the period, the comma, and the parenthesis.

System Action: The SQL query is terminated.

User Response: None.

ANR2909EThe SQL statement is incomplete; additional tokens are required.

Explanation: A syntax error occurred because, although the syntax of the SQL query expression was correct up to the end of the string, the parser expected additional tokens in order to form a syntactically-correct SQL statement.

System Action: The SQL query is terminated.

User Response: None.

ANR2910EInvalid SQL token - 'token'.

Explanation: An invalid SQL token was found. For example, the token formed by the character sequence "::!" is not a valid SQL token.

System Action: The SQL query is terminated.

User Response: None.

ANR2911EInvalid SQL numeric literal token - 'token'.

Explanation: An invalid SQL numeric literal token was found. For example, the floating point literal "1.456E" is not valid.

System Action: The SQL query is terminated.

User Response: None.

ANR2912EInvalid character string literal token - 'token'.

Explanation: An invalid SQL character string literal token was found. For example, the hexadecimal literal X'78FG' is not valid because it contains the character 'G'.

System Action: The SQL query is terminated.

User Response: None.

ANR2913EInvalid SQL identifier token - 'token'.

Explanation: An invalid SQL identifier token was found. For example, the character sequence "ABC.123" is not a valid identifier because the second part of the identifier, "123", does not begin with a letter.

System Action: The SQL query is terminated.

User Response: None.

ANR2914ESQL identifier token 'token' is too long; name or component exceeds 18 characters.

Explanation: An SQL identifier token was found that exceeds the maximum length of 18 characters per component.

System Action: The SQL query is terminated.

User Response: None.

ANR2915EThe SQL token beginning with 'token' is missing an ending delimiter.

Explanation: An SQL token was found that is missing its ending delimiter. For example, each of the tokens 'abc, "abc, and X'abc is missing its ending delimiter.

System Action: The SQL query is terminated.

User Response: None.

ANR2916EThe SQL data types data type and data type are incompatible for operator 'operator'.

Explanation: The data types of the operands are not compatible when used with the specified operator. For example, the expression 3 + 'abc' is not valid because the operand data types INTEGER and CHAR(3) are not compatible for the addition operator "+".

System Action: The SQL query is terminated.

User Response: None.

ANR2917EThe SQL data type of expression 'expression' is data type; expecting an integer expression.

Explanation: An SQL expression of data type SMALLINT, INTEGER, or DECIMAL with scale zero is expected.

System Action: The SQL query is terminated.

User Response: None.

ANR2918EThe SQL data type of expression 'expression' is data type; expecting a Boolean expression.

Explanation: An SQL expression of data type BOOLEAN is expected.

System Action: The SQL query is terminated.

User Response: None.

ANR2919EThe SQL data type of expression 'expression' is data type; expecting a numeric expression.

Explanation: An SQL expression of numeric data type SMALLINT, INTEGER, DECIMAL, NUMERIC, REAL, FLOAT, or DOUBLE_PRECISION is expected.

System Action: The SQL query is terminated.

User Response: None.

ANR2920EThe SQL data type of expression 'expression' is data type; expecting a numeric or interval expression.

Explanation: An SQL expression of numeric data type (SMALLINT, INTEGER, DECIMAL, NUMERIC, REAL, FLOAT, DOUBLE) or of interval data type (INTERVAL) is expected.

System Action: The SQL query is terminated.

User Response: None.

ANR2921EThe SQL data type of expression 'expression' is data type; expecting a character string expression.

Explanation: An SQL expression of character string type CHAR or VARCHAR is expected.

System Action: The SQL query is terminated.

User Response: None.

ANR2922EThe SQL data type of expression 'expression' is data type; expecting a date, timestamp, character string date, character string timestamp, or interval expression.

Explanation: An SQL expression was expected of one of the types DATE, TIMESTAMP, CHAR, VARCHAR, or INTERVAL as the operand to the EXTRACT function. In the case of CHAR or VARCHAR, the expression must be a valid character string representation of a date or a timestamp.

System Action: The SQL query is terminated.

User Response: None.

ANR2923EThe SQL data type of expression 'expression' is data type; expecting a time, timestamp, character string time, character string timestamp, or interval expression.

Explanation: An SQL expression was expected of one of the types TIME, TIMESTAMP, CHAR, VARCHAR, or INTERVAL as the operand to the EXTRACT function. In the case of CHAR or VARCHAR, the expression must be a valid character string representation of a time or a timestamp.

System Action: The SQL query is terminated.

User Response: None.

ANR2924EThe SQL data type of expression 'expression' is data type; expecting a date or character string date expression.

Explanation: An SQL expression was expected of one of the types DATE, CHAR, or VARCHAR. In the case of CHAR or VARCHAR, the expression must be a valid character string representation of a date.

System Action: The SQL query is terminated.

User Response: None.

ANR2925EThe SQL data type of expression 'expression' is data type; expecting a time or character string time expression.

Explanation: An SQL expression was expected of one of the types TIME, CHAR, or VARCHAR. In the case of CHAR or VARCHAR, the expression must be a valid character string representation of a time.

System Action: The SQL query is terminated.

User Response: None.

ANR2926EThe SQL data type of expression 'expression' is data type; expecting a date, timestamp, character string date, or character string timestamp expression.

Explanation: An SQL expression was expected of one of the types DATE, TIMESTAMP, CHAR, or VARCHAR. In the case of CHAR or VARCHAR, the expression must be a valid character string representation of a date or a timestamp.

System Action: The SQL query is terminated.

User Response: None.

ANR2927EThe SQL data type of expression 'expression' is data type; expecting an interval containing a single date-time field.

Explanation: An SQL expression was expected of data type INTERVAL YEAR, INTERVAL MONTH, INTERVAL DAY, INTERVAL HOUR, INTERVAL MINUTE, or INTERVAL SECOND, all of which contain a single date-time field. Multi-field interval types (for example, INTERVAL DAY TO SECOND) are not allowed.

System Action: The SQL query is terminated.

User Response: None.

ANR2928EA number can not be converted to SQL data type INTERVAL if the interval contains multiple date-time fields.

Explanation: An attempt was made to convert a number to the data type INTERVAL, but the target interval contains multiple date-time fields (for example, INTERVAL DAY TO SECOND). Only the single-field interval types INTERVAL YEAR, INTERVAL MONTH, INTERVAL DAY, INTERVAL HOUR, INTERVAL MINUTE, or INTERVAL SECOND can be specified.

System Action: The SQL query is terminated.

User Response: None.

ANR2929EThe expression 'expression' is not an integer constant.

Explanation: An integer constant such as 1 or -9 is expected. For example, the DECIMAL function requires that the precision and scale operands be integer constants. A decimal constant such as 1.67 is not valid.

System Action: The SQL query is terminated.

User Response: None.

ANR2930EA subquery used in an SQL expression must specify a single result column.

Explanation: A subquery used in an expression can not specify multiple result columns. For example, the expression X > (select A,B from T) is invalid because it specifies two result columns (A and B).

System Action: The SQL query is terminated.

User Response: None.

ANR2931EA subquery expression may not contain a reference to a column name that is contained in an outer query expression.

Explanation: A subquery contains a reference to a column name in an outer query expression.

System Action: The SQL query is terminated.

User Response: None.

ANR2932EThe maximum nesting depth for subquery expressions has been exceeded.

Explanation: Too many nested subqueries were specified.

System Action: The SQL query is terminated.

User Response: None.

ANR2933EThe WHERE clause must not contain an aggregate function.

Explanation: The use of the aggregate functions COUNT, MAX, MIN, SUM, AVG, VARIANCE, or STDDEV in the WHERE clause is not allowed.

System Action: The SQL query is terminated.

User Response: None.

ANR2934EThe result data type of a CASE expression can not be determined; at least one non-null THEN or ELSE expression must be specified.

Explanation: The result data type of a CASE expression can not be determined because all of the THEN expressions and the ELSE expression (if present) specifies the NULL key word.

System Action: The SQL query is terminated.

User Response: None.

ANR2935EThe date-time field field is not present in the expression 'expression' (data type data type).

Explanation: The specified date-time field (YEAR, MONTH, DAY, HOUR, MINUTE, or SECOND) is not contained in the data type of the expression.

System Action: The SQL query is terminated.

User Response: None.

ANR2936EThe SQL aggregate function function can not be nested within another aggregate function.

Explanation: One of the aggregate functions COUNT, MAX, MIN, SUM, AVG, VARIANCE, or STDDEV was found nested within another aggregate expression.

System Action: The SQL query is terminated.

User Response: None.

ANR2937EAn SQL subquery expression can not be nested within an aggregate function.

Explanation: An expression containing a subquery was found nested within one of the aggregate functions COUNT, MAX, MIN, SUM, AVG, VARIANCE, or STDDEV.

System Action: The SQL query is terminated.

User Response: None.

ANR2938EThe column 'column' is not allowed in this context; it must either be named in the GROUP BY clause or be nested within an aggregate function.

Explanation: A column reference was specified that is neither a column specified in a GROUP BY clause nor is a column nested in one of the aggregate functions COUNT, MAX, MIN, SUM, AVG, VARIANCE, or STDDEV. The use of the column reference is prohibited because either 1) the GROUP BY clause has been specified, 2) the HAVING clause has been specified, or 3) at least one aggregate function is present.

System Action: The SQL query is terminated.

User Response: None.

ANR2939EThe reference 'reference' is an unknown SQL table name.

Explanation: The specified table reference is not one of the base tables defined by the server's database. The rows of the table SYSCAT.TABLES can be selected to obtain a list of all of the valid base tables.

System Action: The SQL query is terminated.

User Response: None.

ANR2940EThe reference 'reference' is an unknown SQL column name.

Explanation: The specified column reference is not one of the base table columns defined by the server's database. The rows of the table SYSCAT.COLUMNS can be selected to obtain a list of all of the valid base table columns. If a two-part (compound) column reference such as X.Y is specified, then the correlation name X must be one of the active correlation names for the query.

System Action: The SQL query is terminated.

User Response: None.

ANR2941EThe column reference 'column reference' matches more than one SQL column name.

Explanation: The specified column reference is ambiguous because it matches the columns associated with multiple tables.

System Action: The SQL query is terminated.

User Response: None.

ANR2942EThe column reference 'column reference' is not allowed in this context because it is part of an outer SQL query expression.

Explanation: The specified column reference is not allowed because it names a columns of some outer query expression. Such references are not allowed when contained within the expressions of the HAVING and SELECT clauses.

System Action: The SQL query is terminated.

User Response: None.

ANR2943EThe column reference 'column reference' is a duplicate of another SQL column name in the same list.

Explanation: A duplicate column reference was specified within the same GROUP BY or ORDER BY list of columns.

System Action: The SQL query is terminated.

User Response: None.

ANR2944EThe reference 'reference' is an unknown SQL scalar function name.

Explanation: The specified function reference is not the name of a valid scalar function.

System Action: The SQL query is terminated.

User Response: None.

ANR2945EToo few arguments are specified for SQL scalar function function.

Explanation: Too few function arguments were specified. For example, the expression LEFT(x) is invalid because the LEFT function requires at least two arguments.

System Action: The SQL query is terminated.

User Response: None.

ANR2946EToo many arguments are specified for SQL scalar function function.

Explanation: Too many function arguments were specified. For example, the expression UPPER(x,y) is invalid because the UPPER function requires exactly one argument.

System Action: The SQL query is terminated.

User Response: None.

ANR2947EDivision by zero was detected for operator 'operator'.

Explanation: An attempt to divide by the number zero was detected for the specified SQL operator. The most likely cause of the problem is that one of the values of a column is zero, and that column is used in the denominator of a division operation. To protect against this case the NULLIF function can be used. For example, instead of the expression 1/X, specify 1/NULLIF(X,0), which will set the expression to null whenever the value if X is zero.

System Action: The SQL query is terminated.

User Response: None.

ANR2948EThe value 'value' can not be assigned or converted to SQL data type data type.

Explanation: A value could not assigned or converted to a value in the specified SQL data type because either 1) the data type of the value can not be legally cast to the target data type (for example, data type TIME can not be converted to data type INTEGER); 2) the assignment of the value results in overflow in the target data type (for example, the decimal value 12345678.34 can not be assigned to data type DECIMAL(3,2) because the precision of the target type is exceeded); or 3) the syntax of a character string value is not appropriate for the target data type (for example, the string 'abc' can not be converted to data type DATE).

System Action: The SQL query is terminated.

User Response: None.

ANR2949EArithmetic overflow occurred for SQL operator 'operator'.

Explanation: An arithmetic overflow occurred for the specified operator. Examples of this include: 1) the application of the unary negation operator to the smallest INTEGER value (-2147483648) causes overflow because the result can not be represented in 2's complement; 2) the sum of the set of INTEGER column values applied to the SUM aggregate function can not be represented within the precision of INTEGER type.

System Action: The SQL query is terminated.

User Response: None.

ANR2950EArithmetic or date-time overflow occurred for SQL operator 'operator' for values 'value' (data type data type) and 'value' (data type data type).

Explanation: An arithmetic or date-time overflow occurred for the specified operator. The values that caused the overflow (and their SQL data types) are displayed.

System Action: The SQL query is terminated.

User Response: None.

ANR2951EThe value 'value' (data type data type) is not a valid argument for operator 'operator'.

Explanation: An invalid value was specified as an argument to an SQL operator. For example, the expression SQRT(-1) is not valid because the argument to the SQRT function is negative.

System Action: The SQL query is terminated.

User Response: None.

ANR2952EThe value 'value' (data type data type) is not a valid character string representation of an SQL date or a timestamp for operator 'operator'.

Explanation: An invalid character string representation of a DATE or TIMESTAMP was specified. For example, the string 'abc' is neither a valid date nor a timestamp.

System Action: The SQL query is terminated.

User Response: None.

ANR2953EThe value 'value' (data type data type) is not a valid character string representation of an SQL time or a timestamp for operator 'operator'.

Explanation: An invalid character string representation of a TIME or TIMESTAMP was specified. For example, the string 'g pm' is neither a valid time nor a timestamp.

System Action: The SQL query is terminated.

User Response: None.

ANR2954EAn SQL subquery used in a scalar expression must yield a table that contains at most one row.

Explanation: This error results when a subquery used in a scalar expression returns multiple rows, thereby making it ambiguous as to which value should be returned.

System Action: The SQL query is terminated.

User Response: Respecify the subquery (for example, using the WHERE clause) so that the subquery returns at most one row.

ANR2955EThe SQL character string expression 'expression' must return a single character.

Explanation: A single-character character string was expected for the ESCAPE clause of the LIKE operator, for the trim character of the TRIM operator, or for the pad character of the LEFT or RIGHT function. For example, the string 'Hello' is invalid because it contains multiple characters.

System Action: The SQL query is terminated.

User Response: None.

ANR2956EUnable to access SQL base table 'table'.

Explanation: An error occurred when attempting to read rows from one of the SQL base tables. This message is typically preceded by another error describing the condition.

System Action: The SQL query is terminated.

User Response: None.

ANR2957EAn error occurred inserting a row in an SQL temporary table. The server database size may need to be increased

Explanation: An error occurred when attempting to insert a row into a temporary table being used for an SQL query. This message is typically preceded by another error describing the condition. In many cases this error can be resolved by increasing the size of the server database. Free space in the database is used to store temporary tables created during the execution of an SQL SELECT query.

System Action: The SQL query is terminated.

User Response: None.

ANR2958ESQL temporary table storage has been exhausted.

Explanation: The result of an SQL query could not be computed because insufficient temporary table storage space was available. Free space in the server database is used to store temporary tables created during the execution of an SQL SELECT query. In many cases the web admin client uses SQL commands to retrieve necessary data from the server. Complex SQL queries such as those containing the following conditions can cause temporary table space to be required: the ORDER BY clause, the GROUP BY clause, and, the DISTINCT operator. In most cases this error can be resolved by increasing the size of the server database.

System Action: The SQL query is terminated.

User Response: None.

ANR2959ESQL temporary table row is too wide.

Explanation: A row could not be inserted into an SQL temporary table because the row is too wide. This can occur if 1) there are too many columns in the row being inserted, or 2) the sum of the lengths of the columns in the row is too wide. Temporary tables are used when 1) the ORDER BY clause is specified; 2) the GROUP BY clause is specified; or 3) the DISTINCT operator is specified.

System Action: The SQL query is terminated.

User Response: Reduce the number of columns specified in the ORDER BY and/or GROUP BY clauses.

ANR2960EUnexpected SQL enumerated type name token - 'token'.

Explanation: A syntax error occurred because an SQL enumerated type name was found that can not legally be used at the specified position within the SQL statement. A list of all of the enumerated types declared by the server can be found in the SQL catalog table SYSCAT.ENUMTYPES.

System Action: The SQL query is terminated.

User Response: None.

ANR2961EInvalid SQL enumerated type name - 'name'.

Explanation: A syntax error occurred because an SQL enumerated type name was expected, but the specified name is not one of the declared enumerated types. For example, the literal expression XXX::YYYY is illegal because XXX is not a valid enumerated type name. A list of all of the enumerated types declared by the server can be found in the SQL catalog table SYSCAT.ENUMTYPES.

System Action: The SQL query is terminated.

User Response: None.

ANR2962EUnable to resolve SQL enumerated type for value 'value'.

Explanation: A syntax error occurred because an unqualified SQL enumerated value name was specified, but, because that value name is a member of more than one enumerated type, its type could not be resolved. For example, the enumerated value name YES belongs to more than one enumerated type, and so the result type of the expression YES = YES can not be resolved. A list of all of the enumerated types declared by the server can be found in the SQL catalog table SYSCAT.ENUMTYPES.

System Action: The SQL query is terminated.

User Response: None.

ANR2963WThis SQL query may produce a very large result table, or may require a significant amount of time to compute.

Explanation: An SQL query has been posed that could potentially cause a very large number of rows to be returned and displayed, or may involve a large amount of processing time before the first result table row can be generated.

System Action: The administrator is asked whether to continue.

User Response: Enter 'Y' to continue with SQL query processing or 'N' to terminate the query.

ANR2964EThe reference 'reference' is not a column of the SQL result table.

Explanation: The ORDER BY clause specified a column that is not part of the result table for the SQL query. Only those columns named in the select list are part of the result table.

System Action: The SQL query is terminated.

User Response: None.

ANR2965EAn SQL temporary table cannot be built. required columns columns are needed. maximum columns is the maximum.

Explanation: A temporary table required columns wide is needed to complete processing for an SQL query. The maximum degree of an SQL table is maximum columns. The table will not be created.

System Action: The SQL query is terminated.

User Response: If the ORDER BY and/or GROUP BY clauses were specified, reduce the number of columns needed for the result table.

ANR2966Ecommand/process: Database temporary table storage has been exhausted.

Explanation: The named command or operation could not be completed because insufficient temporary table storage space was available. Free space in the server database is used to store temporary tables created during the execution of the named command or process.

System Action: The named command or process is terminated.

User Response: Extend the server datbase (after adding database volumes if necessary) and rerun the commmand or process.

ANR3000Ecommand: Command can only be issued on a configuration manager.

Explanation: The command can only be issued on a server that is a configuration manager.

System Action: Server operation continues. The command is not processed.

User Response: Issue this command from a configuration manager.

ANR3001Ecommand: Command can only be issued on a managed server.

Explanation: The command can only be issued on a managed server.

System Action: Server operation continues. The command is not processed.

User Response: Issue this command from a managed server.

ANR3002Ecommand: Profile name exceeds maximum length characters.

Explanation: The profile name specified in the command is longer than the maximum length allowed.

System Action: Server operation continues. The command is not processed.

User Response: Select a profile name that does not exceed the maximum length.

ANR3003Ecommand: Profile description exceeds maximum length characters.

Explanation: The profile description specified in the command is longer than the maximum length allowed.

System Action: Server operation continues. The command is not processed.

User Response: Select a description that does not exceed the maximum length.

ANR3004Ecommand: The configuration manager name exceeds maximum length characters.

Explanation: The configuration manager name specified in the command is longer than the maximum length allowed.

System Action: Server operation continues. The command is not processed.

User Response: Select a configuration manager name that does not exceed the maximum length.

ANR3005Ecommand: The server name exceeds maximum length characters.

Explanation: The configuration manager name specified in the command is longer than the maximum length allowed.

System Action: Server operation continues. The command is not processed.

User Response: Select a configuration manager name that does not exceed the maximum length.

ANR3006Ecommand: The configuration refresh interval value must be between minimum value and maximum value.

Explanation: The specified command has been issued with an invalid refresh interval.

System Action: Server operation continues. The command is not processed.

User Response: Issue the command and specify a valid refresh interval value.

ANR3007Ecommand: The option option must be specified.

Explanation: When the command is issued on a a server that is neither a configuration manager nor a managed server, the specified option must be supplied.

System Action: Server operation continues. The command is not processed.

User Response: Reissue the command with the specified option.

ANR3010WThis command will delete an object that is associated with one or more profiles on a configuration manager. Subsequent configuration refresh processing will delete the object on managed servers that subscribe to a profile with which the object is associated.

Explanation: A command has been entered that will delete an object from a configuration manager. Since this object is associated with one or more profiles on a configuration manager, configuration refresh processing will delete this object on subscribing managed servers.

System Action: The system asks whether you wish to continue with the command.

User Response: To process the command, enter 'Y' to continue or 'N' to stop the process.

ANR3011Ecommand: Subscription for profile profile name was not deleted because one or more objects could not be discarded.

Explanation: This message was issued because one or more objects could not be discarded by the indicated command. A previous message gives an explanation for each object that could not be discarded.

System Action: The system may discard some of the managed objects that are associated with profile profile name The subscription itself is not deleted.

User Response: Examine previous messages to determine the action that must be taken before remaining objects can be discarded. Alternatively, you can delete the subscription without using the DISCARDOBJECTS=YES option.

ANR3012Icommand: Configuration manager state set to state.

Explanation: The command has successfully set the configuration manager state.

System Action: The command succeeded.

User Response: None.

ANR3013Wcommand: Configuration manager state already set to state.

Explanation: The specified state is already in force on the server.

System Action: Server operation continues. The command is not processed.

User Response: This server is already set to the specified state. If the state should be set differently, reissue the command specifying the new state value.

ANR3014Ecommand: One or more subscriptions still exist.

Explanation: A configuration manager state cannot be set to OFF is one or more subscription still exist. The server still has a record of one or more subscriptions to its profiles.

System Action: Server operation continues. The command is not processed.

User Response: Use the QUERY SUBSCRIBERS command to determine which subscriptions still exist. The DELETE SUBSCRIBER command can be used to remove the record of these subscriptions. You may instead want to delete the actual subscription(s) on the managed server(s). When there are no more subscriptions recorded on the configuration manager, you must then delete all the profiles. Once the profiles have been deleted, you can reissue the command.

ANR3015Ecommand: One or more profiles still exist.

Explanation: A configuration manager state cannot be set to OFF is one or more profiles still exist.

System Action: Server operation continues. The command is not processed.

User Response: Use the QUERY PROFILE command to determine which profiles still exist on the configuration manager then use the DELETE PROFILE command. After all the profiles have been deleted, reissue the command.

ANR3016Icommand: Configuration refresh interval set to interval.

Explanation: The command has successfully set the configuration refresh interval to the specified value. Automatic configuration refresh processing will immediatly be attempted and then will again be performed after the specified number of minutes of elapsed.

System Action: The command succeeded.

User Response: None.

ANR3017Icommand: Profile profile name defined.

Explanation: The command has successfully define a profile.

System Action: The command succeeded.

User Response: None.

ANR3018Ecommand: Profile profile name already exists.

Explanation: The profile specified already exists on the configuration manager.

System Action: Server operation continues. The command is not processed.

User Response: Decide on another profile name and reissue the command.

ANR3019Icommand: Profile profile name updated.

Explanation: The command has successfully updated a profile.

System Action: The command succeeded.

User Response: None.

ANR3020Ecommand: Profile profile name not found.

Explanation: The profile specified could not be found.

System Action: Server operation continues. The command is not processed.

User Response: Check to see if the profile name was specified correctly on the command. Use the QUERY PROFILE command to check to see if the profile exists on the configuration manager. Reissue the command with the correct profile name.

ANR3021Icommand: Profile profile name copied to profile profile name.

Explanation: The command has successfully copied the first profile to the newly created second profile. All the profile associations were also copied.

System Action: The command succeeded.

User Response: None.

ANR3022Ecommand: The profile lock timeout interval value must be between minimum value and maximum value.

Explanation: The specified command has been issued with an invalid lock timeout interval.

System Action: Server operation continues. The command is not processed.

User Response: Issue the command and specify a valid lock timeout interval value.

ANR3023Icommand: Profile profile name locked.

Explanation: The command has successfully locked the profile. No configuration information can be propogated to the subscribers of the profile until it is unlocked.

System Action: The command succeeded.

User Response: None.

ANR3024Wcommand: Profile profile already locked with timeout interval greater than interval.

Explanation: An attempt was made to lock the specified profile. The profile is already locked with a timeout interval greater than the value specifed.

System Action: The profile remains locked with the original timeout interval.

User Response: If you want to lower the timeout interval, unlock the profile and then lock the profile again specifying the lower value.

ANR3025Icommand: Profile profile name unlocked.

Explanation: The command has successfully unlocked the profile. Configuration information can now be propogated to the subscribers of the profile.

System Action: The command succeeded.

User Response: None.

ANR3026Icommand: Profile profile name deleted.

Explanation: The command has successfully deleted the profile from the configuration manager.

System Action: The command succeeded.

User Response: None.

ANR3027Ecommand: One or more subscriptions still exist to profile profile name.

Explanation: An attempt was made to delete a profile that still has subscriptions defined on one or more managed servers. The configuration manager still has a record of one or more subscriptions to the profiles.

System Action: Server operation continues. The command is not processed.

User Response: Use the QUERY SUBSCRIBERS command to determine which subscriptions still exist. Use the DELETE SUBSCRIPTION command on the managed server(s) to delete the subscriptions, and then reissue the DELETE PROFILE command on the configuration manager. Alternatively, the FORCE=YES option can be used on the DELETE PROFILE command to delete the profile even if there are subscriptions to the profile. In this case, messages will be issued when the managed server requests updates for that profile, informing the managed server that the profile has been deleted.

ANR3028Ecommand: Profile profile name is locked.

Explanation: The specifed command cannot be performed on a locked profile.

System Action: Server operation continues. The command is not processed.

User Response: Unlock the profile using the UNLOCK PROFILE command and then reissue the command.

ANR3029Ecommand: Profile name not specified.

Explanation: A profile name must be specifed on this command using the PROFILE= parameter.

System Action: Server operation continues. The command is not processed.

User Response: Reissue the command and specify a profile name.

ANR3030Icommand: Subscription defined for profile profile name.

Explanation: The command has successfully defined a subscription to the specified profile. A refresh of the configuration information has been initiated.

System Action: The command succeeded.

User Response: None.

ANR3031Wcommand: Subscription for profile profile name already exists.

Explanation: A subscription already exists for the specified profile.

System Action: Server operation continues. The command is not processed.

User Response: Check to make sure you specified the correction profile name, and reissue the command if needed.

ANR3032Ecommand: Server name not specified.

Explanation: A server name must be specifed on this command using the SERVER= parameter. This identifies the configuration manager.

System Action: Server operation continues. The command is not processed.

User Response: Reissue the command and specify a server name.

ANR3033Ecommand: Server server is not the managed server's configuration manager.

Explanation: A server name was specified on the command which does not match the current configuration manager. A managed server may only have one configuration manager.

System Action: Server operation continues. The command is not processed.

User Response: Reissue the command and leave off the server parameter. It will default to use the current configuration manager. A QUERY SUBSCRIPTION will display the configuration manager currently in use.

ANR3034Ecommand: Server server cannot be used as this server's configuration manager.

Explanation: A server name was specified on the command which cannot be used as a configuration manager.

System Action: Server operation continues. The command is not processed.

User Response: Find out the currect name for the configuration manager and then reissue the command.

ANR3035Icommand: Subscriber subscriber name deleted.

Explanation: The command has successfully deleted a subscriber from the record kept in the configuration manager. If the subscriber (managed server) still has a subscription to a valid profile, the record of the subscription will reappear when it performs its next configuration refresh.

System Action: The command succeeded.

User Response: None.

ANR3036Ecommand: Subscriber subscriber name not found.

Explanation: The specified subscriber name was not found in the configuration manager's records as being a valid subscriber of any profiles.

System Action: Server operation continues. The command is not processed.

User Response: Check to see that the subscriber (managed server) name is correction. If you think the name is correct, perhaps the managed server has not yet successfully contacted the configuration manager to inform it that the subscription exists.

ANR3037Icommand: Subscription deleted for profile profile name.

Explanation: The command has successfully deleted a subscription for the specified profile. A refresh of the configuration information has been initiated.

System Action: The command succeeded.

User Response: None.

ANR3038Ecommand: Subscription for profile profile name not found.

Explanation: A subscription was not found for the specified profile.

System Action: Server operation continues. The command is not processed.

User Response: Check to see that the profile name was specified correctly. Issue the QUERY SUBSCRIPTION command to check to see which profiles have subscriptions. Reissue the command with the correct profile name.

ANR3039Ecommand: No matching administrators found in configuration.

Explanation: No administrator definitions were found on the configuration manager that match the admin(s) specified on the DEFINE PROFASSOCIATION command.

System Action: Server operation continues. The command is not processed.

User Response: Use the QUERY ADMIN command to check which administrators that are defined on the server and then reissue to DEFINE PROFASSOCIATION command.

ANR3040Icommand: All administrators associated with profile profilename.

Explanation: The command has successfully associated all the administrators with the specified profile. All administrator definitions will be automatically propogated to managed servers which subscribe to the profile. If an administrator is added to the configuration manager in the future, its definition will also be automatically propogated to the managed servers.

System Action: The command succeeded.

User Response: None.

ANR3041Icommand: Administrator admin associated with profile profilename.

Explanation: The command has successfully associated the administrator with the specified profile. The administrator definition will be automatically propogated to managed servers which subscribe to the profile.

System Action: The command succeeded.

User Response: None.

ANR3042Wcommand: No additional administrators associated with profile profilename.

Explanation: No additional administrator were associated with the profile. The administrator(s) specified are already associated with the profile.

System Action: Server operation continues. The command is not processed.

User Response: Use the QUERY ADMIN command to check which administrators are defined on the server and then reissue to DEFINE PROFASSOCIATION command. The QUERY PROFASSOCIATION FORMAT=DETAILED can be used to see which administrators are already associated with the profile.

ANR3043Ecommand: No matching domains found in configuration.

Explanation: No domain definitions were found on the configuration manager that match the domain(s) specified on the DEFINE PROFASSOCIATION command.

System Action: Server operation continues. The command is not processed.

User Response: Use the QUERY DOMAIN command to check which domains that are defined on the server and then reissue to DEFINE PROFASSOCIATION command.

ANR3044Icommand: All domains associated with profile profilename.

Explanation: The command has successfully associated all the domains with the specified profile. All domain definitions will be automatically propogated to managed servers which subscribe to the profile. If a domain is added to the configuration manager in the future, its definition will also be automatically propogated to the managed servers.

System Action: The command succeeded.

User Response: None.

ANR3045Icommand: Domain domain associated with profile profilename.

Explanation: The command has successfully associated the domain with the specified profile. The domain definition will be automatically propogated to managed servers which subscribe to the profile.

System Action: The command succeeded.

User Response: None.

ANR3046Wcommand: No additional domains associated with profile profilename.

Explanation: No additional domains were associated with the profile. The domain(s) specified are already associated with the profile.

System Action: Server operation continues. The command is not processed.

User Response: Use the QUERY DOMAIN command to check which domains are defined on the server and then reissue to DEFINE PROFASSOCIATION command. The QUERY PROFASSOCIATION FORMAT=DETAILED can be used to see which domains are already associated with the profile.

ANR3047Ecommand: No matching admin schedules found in configuration.

Explanation: No admin schedule definitions were found on the configuration manager that match the admin schedule(s) specified on the DEFINE PROFASSOCIATION command.

System Action: Server operation continues. The command is not processed.

User Response: Use the QUERY SCHEDULE TYPE=ADMIN command to check which admin schedules are defined on the server and then reissue to DEFINE PROFASSOCIATION command.

ANR3048Icommand: All admin schedules associated with profile profilename.

Explanation: The command has successfully associated all the admin schedules with the specified profile. All admin schedule definitions will be automatically propogated to managed servers which subscribe to the profile. If an admin schedule is added to the configuration manager in the future, its definition will also be automatically propogated to the managed servers.

System Action: The command succeeded.

User Response: None.

ANR3049Icommand: Admin Schedule admin schedule associated with profile profilename.

Explanation: The command has successfully associated the admin schedule with the specified profile. The admin schedule definition will be automatically propogated to managed servers which subscribe to the profile.

System Action: The command succeeded.

User Response: None.

ANR3050Wcommand: No additional admin scheduless associated with profile profilename.

Explanation: No additional admin schedules were associated with the profile. The admin schedule(s) specified are already associated with the profile.

System Action: Server operation continues. The command is not processed.

User Response: Use the QUERY SCHEDULE TYPE=ADMIN command to check which admin schedules are defined on the server and then reissue to DEFINE PROFASSOCIATION command. The QUERY PROFASSOCIATION FORMAT=DETAILED can be used to see which admin schedules are already associated with the profile.

ANR3051Ecommand: No matching scripts found in configuration.

Explanation: No script definitions were found on the configuration manager that match the script(s) specified on the DEFINE PROFASSOCIATION command.

System Action: Server operation continues. The command is not processed.

User Response: Use the QUERY SCRIPT command to check which scripts that are defined on the server and then reissue to DEFINE PROFASSOCIATION command.

ANR3052Icommand: All scripts associated with profile profilename.

Explanation: The command has successfully associated all the scripts with the specified profile. All script definitions will be automatically propogated to managed servers which subscribe to the profile. If a script is added to the configuration manager in the future, its definition will also be automatically propogated to the managed servers.

System Action: The command succeeded.

User Response: None.

ANR3053Icommand: Script script associated with profile profilename.

Explanation: The command has successfully associated the script with the specified profile. The script definition will be automatically propogated to managed servers which subscribe to the profile.

System Action: The command succeeded.

User Response: None.

ANR3054Wcommand: No additional scripts associated with profile profilename.

Explanation: No additional scripts were associated with the profile. The script(s) specified are already associated with the profile.

System Action: Server operation continues. The command is not processed.

User Response: Use the QUERY SCRIPT command to check which scripts are defined on the server and then reissue to DEFINE PROFASSOCIATION command. The QUERY PROFASSOCIATION FORMAT=DETAILED can be used to see which scripts are already associated with the profile.

ANR3055Ecommand: No matching client option sets found in configuration.

Explanation: No client option set definitions were found on the configuration manager that match the client option set(s) specified on the DEFINE PROFASSOCIATION command.

System Action: Server operation continues. The command is not processed.

User Response: Use the QUERY CLOPTSET command to check which client option sets that are defined on the server and then reissue to DEFINE PROFASSOCIATION command.

ANR3056Icommand: All client option sets associated with profile profilename.

Explanation: The command has successfully associated all the client option sets with the specified profile. All client option set definitions will be automatically propogated to managed servers which subscribe to the profile. If a client option set is added to the configuration manager in the future, its definition will also be automatically propogated to the managed servers.

System Action: The command succeeded.

User Response: None.

ANR3057Icommand: Client option set client option set associated with profile profilename.

Explanation: The command has successfully associated the client option set with the specified profile. The client option set definition will be automatically propogated to managed servers which subscribe to the profile.

System Action: The command succeeded.

User Response: None.

ANR3058Wcommand: No additional client option sets associated with profile profilename.

Explanation: No additional client option sets were associated with the profile. The client option set(s) specified are already associated with the profile.

System Action: Server operation continues. The command is not processed.

User Response: Use the QUERY CLOPTSET command to check which client option sets are defined on the server and then reissue to DEFINE PROFASSOCIATION command. The QUERY PROFASSOCIATION FORMAT=DETAILED can be used to see which client option sets are already associated with the profile.

ANR3059Ecommand: No matching servers found in configuration.

Explanation: No server definitions were found on the configuration manager that match the server(s) specified on the DEFINE PROFASSOCIATION command.

System Action: Server operation continues. The command is not processed.

User Response: Use the QUERY SERVER command to check which servers that are defined on the server and then reissue to DEFINE PROFASSOCIATION command.

ANR3060Icommand: All servers associated with profile profilename.

Explanation: The command has successfully associated all the servers with the specified profile. All server definitions will be automatically propogated to managed servers which subscribe to the profile. If a server is added to the configuration manager in the future, its definition will also be automatically propogated to the managed servers.

System Action: The command succeeded.

User Response: None.

ANR3061Icommand: Server server associated with profile profilename.

Explanation: The command has successfully associated the server with the specified profile. The server definition will be automatically propogated to managed servers which subscribe to the profile.

System Action: The command succeeded.

User Response: None.

ANR3062Wcommand: No additional servers associated with profile profilename.

Explanation: No additional servers were associated with the profile. The server(s) specified are already associated with the profile.

System Action: Server operation continues. The command is not processed.

User Response: Use the QUERY SERVER command to check which servers are defined on the server and then reissue to DEFINE PROFASSOCIATION command. The QUERY PROFASSOCIATION FORMAT=DETAILED can be used to see which servers are already associated with the profile.

ANR3063Ecommand: No matching server groups found in configuration.

Explanation: No server group definitions were found on the configuration manager that match the server group(s) specified on the DEFINE PROFASSOCIATION command.

System Action: Server operation continues. The command is not processed.

User Response: Use the QUERY SERVERGROUP command to check which server groups that are defined on the server and then reissue to DEFINE PROFASSOCIATION command.

ANR3064Icommand: All server groups associated with profile profilename.

Explanation: The command has successfully associated all the server groups with the specified profile. All server group definitions will be automatically propogated to managed servers which subscribe to the profile. If a server group is added to the configuration manager in the future, its definition will also be automatically propogated to the managed servers.

System Action: The command succeeded.

User Response: None.

ANR3065Icommand: Server group server group associated with profile profilename.

Explanation: The command has successfully associated the server group with the specified profile. The server group definition will be automatically propogated to managed servers which subscribe to the profile.

System Action: The command succeeded.

User Response: None.

ANR3066Wcommand: No additional server groups associated with profile profilename.

Explanation: No additional server groups were associated with the profile. The server group(s) specified are already associated with the profile.

System Action: Server operation continues. The command is not processed.

User Response: Use the QUERY SERVERGROUP command to check which server groups are defined on the server and then reissue to DEFINE PROFASSOCIATION command. The QUERY PROFASSOCIATION FORMAT=DETAILED can be used to see which server groups are already associated with the profile.

ANR3067Ecommand: No matching administrators associated with profile profile.

Explanation: No matching administrator definitions are associated with the specified specified profile.

System Action: Server operation continues. The command is not processed.

User Response: Use the QUERY PROFASSOCIATION command to check which administrators are associated with the profile and then reissue to DELETE PROFASSOCIATION command.

ANR3068Icommand: All administrator associations deleted from profile profilename.

Explanation: The command has successfully deleted all administrators associations from the specified profile. This will automatically delete these administrators from the managed servers that are subscribed to this profile.

System Action: The command succeeded.

User Response: None.

ANR3069Icommand: Administrator association admin deleted from profile profilename.

Explanation: The command has successfully deleted an administrator association from the specified profile. This will automatically delete this administrator from the managed servers that are subscribed to this profile.

System Action: The command succeeded.

User Response: None.

ANR3070Ecommand: No matching domains associated with profile profile.

Explanation: No matching domain definitions are associated with the specified specified profile.

System Action: Server operation continues. The command is not processed.

User Response: Use the QUERY PROFASSOCIATION command to check which domains are associated with the profile and then reissue to DELETE PROFASSOCIATION command.

ANR3071Icommand: All domain associations deleted from profile profilename.

Explanation: The command has successfully deleted all domains associations from the specified profile. This will automatically delete these domains from the managed servers that are subscribed to this profile.

System Action: The command succeeded.

User Response: None.

ANR3072Icommand: Domain association domain deleted from profile profilename.

Explanation: The command has successfully deleted a domain association from the specified profile. This will automatically delete this domain from the managed servers that are subscribed to this profile.

System Action: The command succeeded.

User Response: None.

ANR3073Ecommand: No matching admin schedules associated with profile profile.

Explanation: No matching admin schedule definitions are associated with the specified specified profile.

System Action: Server operation continues. The command is not processed.

User Response: Use the QUERY PROFASSOCIATION command to check which admin schedules are associated with the profile and then reissue to DELETE PROFASSOCIATION command.

ANR3074Icommand: All admin schedule associations deleted from profile profilename.

Explanation: The command has successfully deleted all admin schedules associations from the specified profile. This will automatically delete these admin schedules from the managed servers that are subscribed to this profile.

System Action: The command succeeded.

User Response: None.

ANR3075Icommand: Admin schedule association admin schedule deleted from profile profilename.

Explanation: The command has successfully deleted an admin schedule association from the specified profile. This will automatically delete this admin schedule from the managed servers that are subscribed to this profile.

System Action: The command succeeded.

User Response: None.

ANR3076Ecommand: No matching scripts associated with profile profile.

Explanation: No matching script definitions are associated with the specified specified profile.

System Action: Server operation continues. The command is not processed.

User Response: Use the QUERY PROFASSOCIATION command to check which scripts are associated with the profile and then reissue to DELETE PROFASSOCIATION command.

ANR3077Icommand: All script associations deleted from profile profilename.

Explanation: The command has successfully deleted all scripts associations from the specified profile. This will automatically delete these scripts from the managed servers that are subscribed to this profile.

System Action: The command succeeded.

User Response: None.

ANR3078Icommand: Script association script deleted from profile profilename.

Explanation: The command has successfully deleted a script association from the specified profile. This will automatically delete this script from the managed servers that are subscribed to this profile.

System Action: The command succeeded.

User Response: None.

ANR3079Ecommand: No matching client option sets associated with profile profile.

Explanation: No matching clent option set definitions are associated with the specified specified profile.

System Action: Server operation continues. The command is not processed.

User Response: Use the QUERY PROFASSOCIATION command to check which client option sets are associated with the profile and then reissue to DELETE PROFASSOCIATION command.

ANR3080Icommand: All client option set associations deleted from profile profilename.

Explanation: The command has successfully deleted all client option sets associations from the specified profile. This will automatically delete these client option sets from the managed servers that are subscribed to this profile.

System Action: The command succeeded.

User Response: None.

ANR3081Icommand: Client option set association client option set deleted from profile profilename.

Explanation: The command has successfully deleted a client option set association from the specified profile. This will automatically delete this client option set from the managed servers that are subscribed to this profile.

System Action: The command succeeded.

User Response: None.

ANR3082Ecommand: No matching servers associated with profile profile.

Explanation: No matching server definitions are associated with the specified specified profile.

System Action: Server operation continues. The command is not processed.

User Response: Use the QUERY PROFASSOCIATION command to check which servers are associated with the profile and then reissue to DELETE PROFASSOCIATION command.

ANR3083Icommand: All server associations deleted from profile profilename.

Explanation: The command has successfully deleted all servers associations from the specified profile. This will automatically delete these servers from the managed servers that are subscribed to this profile.

System Action: The command succeeded.

User Response: None.

ANR3084Icommand: Server association server deleted from profile profilename.

Explanation: The command has successfully deleted a server association from the specified profile. This will automatically delete this server definition from the managed servers that are subscribed to this profile.

System Action: The command succeeded.

User Response: None.

ANR3085Ecommand: No matching server groups associated with profile profile.

Explanation: No matching server group definitions are associated with the specified specified profile.

System Action: Server operation continues. The command is not processed.

User Response: Use the QUERY PROFASSOCIATION command to check which server groups are associated with the profile and then reissue to DELETE PROFASSOCIATION command.

ANR3086Icommand: All server group associations deleted from profile profilename.

Explanation: The command has successfully deleted all server groups associations from the specified profile. This will automatically delete these server groups from the managed servers that are subscribed to this profile.

System Action: The command succeeded.

User Response: None.

ANR3087Icommand: Server group association server group deleted from profile profilename.

Explanation: The command has successfully deleted a server group association from the specified profile. This will automatically delete this server group from the managed servers that are subscribed to this profile.

System Action: The command succeeded.

User Response: None.

ANR3088WThis command will cause the deletion of objects on any managed server subscribed to profile profile name.

Explanation: A DELETE PROFASSOCIATION command option has been entered. This action will not only delete the association from the profile, but it will also result in the deletion of managed object(s) on any managed server subscribing to this profile. The deletion of these objects will occurr during the next configuration refresh for that managed server.

System Action: The system asks whether you wish to continue with the command.

User Response: To process the DELETE PROFASSOCATION command, enter 'Y' to continue or 'N' to stop the command.

ANR3089Ecommand: Command failed - Server-to-server communication error with server server name.

Explanation: The specified command failed while attempting to communicate with the indicated server.

System Action: Server operation continues. The command is not processed.

User Response: Verify that the indicated server name is correctly defined. Try reissuing the command. Use the server PING command to see if the other server is up. If the problem persists, consult with your network administrator.

ANR3090Ecommand: Server server name is not a configuration manager.

Explanation: The specified command failed because it tried to contact the specified server, and discovered that the server is not a configuration manager.

System Action: Server operation continues. The command is not processed.

User Response: Reissue the command and specify a correct configuration manager name.

ANR3091Ecommand: Profile list not specified.

Explanation: The specified command failed because you did not specify a profile list on the command.

System Action: Server operation continues. The command is not processed.

User Response: Reissue the command specifying a profile list.

ANR3092Icommand: Subscriber notification processing has begun.

Explanation: A NOTIFY SUBSCRIBER process has begun. The managed server(s) are being contacted, asking them to immediately perform a configuration refresh.

System Action: Server operation continues. The command succeeded.

User Response: None.

ANR3093Icommand: No matching profiles or subscriptions were found.

Explanation: No subscriptions were found for the profiles specified. Either the profiles do not exist, or there are no subscriptions to the profiles.

System Action: Server operation continues. The command is not processed.

User Response: Use the QUERY PROFILE and QUERY SUBSCRIBER command to determine which profiles exist and which profiles have subscribers. Reissue the command specifying the correct profile name(s).

ANR3150EConfiguration refresh failed with configuration manager server name. Will retry in minutes minutes.

Explanation: While receiving configuration information from the specified configuration manager, processing failed because of a communications error.

System Action: Server operation continues. The configuration refresh process was stopped and will be automatically retried.

User Response: Perhaps the configuration manager is not active. If the problem continues, contact the administrator for the configuration manager, or contact a network administrator. The refresh will automatically retry several times and then give up until the configuration refresh interval is reached again.

ANR3151EConfiguration refresh failed with configuration manager server name.

Explanation: While receiving configuration information from the specified configuration manager, processing failed.

System Action: Server operation continues. The configuration refresh process was stopped.

User Response: Examine the activity log for other messages that may explain why the configuration refresh failed. The refresh will attempted again when the configuration refresh interval is reached.

ANR3152IConfiguration refresh started with configuration manager server name.

Explanation: Configuration refresh processing has started. A server-to-server session was opened to receive configuration information from the configuration manager. Updates will be sent for objects associated with any subscribed-to profiles.

System Action: Refresh processing continues.

User Response: None.

ANR3153IConfiguration refresh ended successfully with configuration manager server name.

Explanation: Configuration refresh processing ended successfully. All updates have been made to managed objects associated with any subscribed-to profiles.

System Action: Server processing continues. The next automatic refresh will start when the configuration refresh interval is reached.

User Response: None.

ANR3154ECommunication error on notify to managed server server name. Will retry in minutes minutes.

Explanation: While attempting a notify subscriber request to the specified managed server, a communications error was detected.

System Action: Server operation continues. The notify subscriber request was stopped and will be automatically retried.

User Response: Perhaps the managed server is not active. If the problem continues, contact the administrator for the managed server, or contact a network administrator. The notify subscriber request will automatically retry several times and then give up.

ANR3155EError attempting notify subscribers request to managed server server.

System Action: Server operation continues. The notify subscriber request failed.

User Response: Examine the activity log for other messages that may explain why the notify subscriber request failed.

ANR3156EConfiguration refresh failed for managed server server name.

Explanation: While sending configuration information to the specified managed server, processing failed.

System Action: Server operation continues. The configuration refresh process ended.

User Response: Examine the activity log of both the managed server and the configuration manager for other messages that may explain why the configuration refresh failed. The refresh will attempted again by the managed server when its configuration refresh interval is reached.

ANR3157IConfiguration refresh started for managed server server name.

Explanation: Configuration refresh processing has started. A server-to-server session was opened by the managed server to receive configuration information from the configuration manager. Updates will be sent for objects associated with any subscribed-to profiles.

System Action: Refresh processing continues.

User Response: None.

ANR3158IConfiguration refresh ended successfully for managed server server name.

Explanation: Configuration refresh processing ended successfully. All updates have been made to managed objects associated with any subscribed-to profiles on the managed server.

System Action: Server processing continues.

User Response: None.

ANR3159EManaged server server name has newer version for profile profile name.

Explanation: While sending configuration information to the specified managed server, it has been detected that the managed server has a newer version of configuration information for the specified profile than does the configuration manager. This condition can happen if the configuration manager's database has been restored to an earlier point in time. Another possibility is that the profile was deleted on the configuration manager and a new profile by the same name was created.

System Action: Server operation continues. No configuration information for this profile will be sent to the managed server until this condition is corrected.

User Response: Before correcting the situation, you may want to use QUERY PROFILE to examine the profile associations defined on both the configuration manager and the managed server. To correct the situation, on the managed server delete the subscription to the profile and define the subscription again. This will cause the managed server to be refreshed at the configuration manager's current level.

ANR3160EUnable to receive confirmation of refresh from managed server server name.

Explanation: While sending configuration information to the specified managed server, a communication error occurred when trying to receive confirmation from the managed server that information was processed successfully.

System Action: Server operation continues. Configuration refresh processing ended.

User Response: Determine if communication can be established with the managed server by using the server PING command. Use the NOTIFY SUBSCRIBERS command to force the configuration refresh to retry.

ANR3161EPremature end of configuration refresh for managed server server server name.

Explanation: While sending configuration information to the specified managed server, processing ended prematurely because of on error.

System Action: Server operation continues. Configuration refresh processing ended.

User Response: Examine the activity log on the managed server for any error messages that might explain why the refresh failed. Use the NOTIFY SUBSCRIBERS command on the configuration manager to force the configuration refresh to retry.

ANR3162EManaged server server name aborted configuration refresh processing due to a low memory condition.

Explanation: While sending configuration information to the specified managed server, processing ended prematurely because of a low memory condition on the managed server.

System Action: Server operation continues. Configuration refresh processing ended.

User Response: Make more memory available to the managed server.

ANR3163EManaged server server name aborted configuration refresh processing due to an internal error.

Explanation: While sending configuration information to the specified managed server, processing ended prematurely because of an internal error on the managed server.

System Action: Server operation continues. Configuration refresh processing ended.

User Response: Examine the activity log of the managed server for messages that explain the cause of the internal error.

ANR3164EManaged server server name aborted configuration refresh processing due to a lock conflict.

Explanation: While sending configuration information to the specified managed server, processing ended prematurely because of a lock conflict on the managed server.

System Action: Server operation continues. Configuration refresh processing ended.

User Response: Use the NOTIFY SUBSCRIBERS command to retry the configuration refresh. If this problem persists, contact your service representative.

ANR3165EManaged server server name aborted configuration refresh processing due to a protocol error.

Explanation: While sending configuration information to the specified managed server, processing ended prematurely because of a protocol error detected on the managed server.

System Action: Server operation continues. Configuration refresh processing ended.

User Response: Use the NOTIFY SUBSCRIBERS command to retry the configuration refresh. If this problem persists, contact your service representative.

ANR3166EUnable to receive configuration refresh information from server server name.

Explanation: While receiving configuration information from the specified configuration manager, processing ended prematurely because of a communications error.

System Action: Server operation continues. Configuration refresh processing ended.

User Response: Use the server PING command to see if the configuration manager can be reached. If the problem persists, contact your network administrator.

ANR3167EConfiguration manager server name aborted configuration refresh processing due to a low memory condition.

Explanation: While receiving configuration information from the specified configuration manager, processing ended prematurely because of a low memory condition on the configuration manager.

System Action: Server operation continues. Configuration refresh processing ended.

User Response: Notify the administrator of the configuration manager.

ANR3168EConfiguration manager server name aborted configuration refresh processing due to an internal error.

Explanation: While receiving configuration information from the specified configuration manager, processing ended prematurely because of an internal error on the configuration manager.

System Action: Server operation continues. Configuration refresh processing ended.

User Response: Examine the activity log of the configuration manager for messages that explain the cause of the internal error.

ANR3169EConfiguration manager server name aborted configuration refresh processing due to a lock conflict.

Explanation: While receiving configuration information from the specified managed server, processing ended prematurely because of a lock conflict on the configuration manager.

System Action: Server operation continues. Configuration refresh processing ended.

User Response: Retry the configuration refresh by issuing the SET CONFIGREFRESH command (using the current refresh interval value). If this problem persists, contact your service representative.

ANR3170EConfiguration manager server name aborted configuration refresh processing due to a protocol error.

Explanation: While receiving configuration information from the specified configuration manager, processing ended prematurely because of a protocol error detected on the configuration manager.

System Action: Server operation continues. Configuration refresh processing ended.

User Response: Retry the configuration refresh by issuing the SET CONFIGREFRESH command (using the current refresh interval value). If this problem persists, contact your service representative.

ANR3171EConfiguration refresh with configuration manager server name had to skip processing for one or more objects.

Explanation: While receiving configuration information from the specified configuration manager, it became necessary to skip the creation or deletion of one or more objects.

System Action: Server operation continues. Configuration refresh processing ended.

User Response: Examine the managed server's activity log for earlier messages that identfy the object, and take the actions identified in those messages. Configuration refresh processing will not complete successfully until the problem is clear up.

ANR3172WSubscription exists for deleted profile profile name.

Explanation: While receiving configuration information from the configuration manager, it has been detected that the managed server has a subscription to an profile that no longer exists on the configuration manager. This condition can exist because the profile was deleted with FORCE=YES on the configuration manager. This out-of-synch condition can also occur because one of the server's database was regressed because of a restore db.

System Action: Server operation continues.

User Response: The DELETE SUBSCRIPTION command is used to correct this situation. You need to decide if you want the managed objects to remain on the server. If you want them to be deleted, specify DISCARD=YES. If you want the objects to remain on the managed server as local objects, specify DISCARD=NO.

ANR3173EServer has newer version for profile profile name than the configuration manager server name.

Explanation: While receiving configuration information from the configuration manager, it has been detected that the managed server has a newer version of configuration information for the specified profile than does the configuration manager. This condition can happen if the configuration manager's database has been restored to an earlier point in time. Another possibility is that the profile was deleted on the configuration manager with FORCE=YES and a new profile by the same name was created.

System Action: Server operation continues. No configuration information for this profile will be sent to the managed server until this condition is corrected.

User Response: Before correcting the situation, you may want to use QUERY PROFILE to examine the profile associations defined on both the configuration manager and the managed server. To correct the situation, on the managed server delete the subscription to the profile and define the subscription again. This will cause the managed server to be refreshed at the configuration manager's current level.

ANR3174ECommunication error with managed server server name.

Explanation: While receiving or sending information to the specified managed server, a communcations error was experienced.

System Action: Server operation continues. The operation in progress fails.

User Response: If this error happens often, consult with your network administrator. Also check to see that the managed server is up.

ANR3175WProfile profile name is locked and could not be refreshed from configuration manager server name.

Explanation: While receiving configuration refresh information from the specified managed server, it was detected that a subscribed-to profile is locked.

System Action: Server operation continues. Refresh processings skips over this profile.

User Response: Normally, the profile will later be unlocked automatically, or by an administrator. If you think that it should not be locked, have ask the configuration manager admin to unlock it using the UNLOCK PROFILE command.

ANR3176WProfile profile name is locked and could not be refreshed for managed server server name.

Explanation: While sending configuration refresh information to the specified managed server, it was detected that a subscribed-to profile is locked.

System Action: Server operation continues. Refresh processings skips over this profile.

User Response: If the profile should no longer be locked, use the UNLOCK PROFILE command to unlock it.

ANR3177WServer level does not support object in profile profile name.

Explanation: While receiving configuration refresh information from the configuration manager, an object was received that is not supported on this managed server.

System Action: Server operation continues. Refresh processings skips over this object. The refresh for the profile fails.

User Response: The configuration manager is at a higher release level than the managed server. The managed server subscribed to a profile that contains an unsupported object. Delete the subscription to this profile until service can be applied to the server to bring it to a higher release level.

ANR3200Ecommand: Command cannot be executed - domain domain name is a managed object.

Explanation: The specified command cannot be executed because it would alter the contents of the indicated managed domain. With the exception of policy set activation, a managed domain can only be modified using configuration information propagated from the configuration manager.

System Action: The command fails and server operation continues.

User Response: None.

ANR3201Ecommand: Domain domain name is a managed object and cannot be deleted.

Explanation: The indicated domain is a managed object and cannot be deleted on the managed server.

System Action: The command fails and server operation continues.

User Response: To delete this object, you can delete the subscription to the configuration profiles with which domain domain name is associated.

ANR3202Ecommand: Domain domain name is a managed object and cannot be updated.

Explanation: The indicated domain is a managed object and cannot be updated on the managed server.

System Action: The command fails and server operation continues.

User Response: To update this object, you can delete the subscription to the configuration profiles with which domain domain name is associated.

ANR3203Ecommand: Policy set set name in domain domain name is a managed object and cannot be deleted.

Explanation: The indicated policy set is a managed object and cannot be deleted on the managed server.

System Action: The command fails and server operation continues.

User Response: To delete this object, you can delete the subscription to the configuration profiles with which domain domain name is associated.

ANR3204Ecommand: Policy set set name in domain domain name is a managed object and cannot be updated.

Explanation: The indicated policy set is a managed object and cannot be updated on the managed server.

System Action: The command fails and server operation continues.

User Response: To update this object, you can delete the subscription to the configuration profiles with which domain domain name is associated.

ANR3205Ecommand: Management class class name in domain domain name, policy set set name is a managed object and cannot be deleted.

Explanation: The indicated management class is a managed object and cannot be deleted on the managed server.

System Action: The command fails and server operation continues.

User Response: To delete this object, you can delete the subscription to the configuration profiles with which domain domain name is associated.

ANR3206Ecommand: Management class class name in domain domain name, policy set set name is a managed object and cannot be updated.

Explanation: The indicated management class is a managed object and cannot be updated on the managed server.

System Action: The command fails and server operation continues.

User Response: To update this object, you can delete the subscription to the configuration profiles with which domain domain name is associated.

ANR3207Ecommand: Backup copy group group name in domain domain name, policy set set name, management class class name is a managed object and cannot be deleted.

Explanation: The indicated backup copy group is a managed object and cannot be deleted on the managed server.

System Action: The command fails and server operation continues.

User Response: To delete this object, you can delete the subscription to the configuration profiles with which domain domain name is associated.

ANR3208Ecommand: Archive copy group group name in domain domain name, policy set set name, management class class name is a managed object and cannot be deleted.

Explanation: The indicated archive copy group is a managed object and cannot be deleted on the managed server.

System Action: The command fails and server operation continues.

User Response: To delete this object, you can delete the subscription to the configuration profiles with which domain domain name is associated.

ANR3209Ecommand: Backup copy group group name in domain domain name, policy set set name, management class class name is a managed object and cannot be updated.

Explanation: The indicated backup copy group is a managed object and cannot be updated on the managed server.

System Action: The command fails and server operation continues.

User Response: To update this object, you can delete the subscription to the configuration profiles with which domain domain name is associated.

ANR3210Ecommand: Archive copy group group name in domain domain name, policy set set name, management class class name is a managed object and cannot be updated.

Explanation: The indicated archive copy group is a managed object and cannot be updated on the managed server.

System Action: The command fails and server operation continues.

User Response: To update this object, you can delete the subscription to the configuration profiles with which domain domain name is associated.

ANR3211Ecommand: Client schedule schedule name in domain domain name is a managed object and cannot be deleted.

Explanation: The indicated client schedule is a managed object and cannot be deleted on the managed server.

System Action: The command fails and server operation continues.

User Response: To delete this object, you can delete the subscription to the configuration profiles with which domain domain name is associated.

ANR3212Ecommand: Client schedule schedule name in domain domain name is a managed object and cannot be updated.

Explanation: The indicated client schedule is a managed object and cannot be updated on the managed server.

System Action: The command fails and server operation continues.

User Response: To update this object, you can delete the subscription to the configuration profiles with which domain domain name is associated.

ANR3213Ecommand: Administrative schedule schedule name is a managed object and cannot be deleted.

Explanation: The indicated administrative schedule is a managed object and cannot be deleted on the managed server.

System Action: The command fails and server operation continues.

User Response: To delete this object, you can delete the subscription to the configuration profiles with which the object is associated.

ANR3214Ecommand: Administrative schedule schedule name is a managed object and cannot be updated, except to activate or deactivate the schedule.

Explanation: The indicated administrative schedule is a managed object and cannot be updated on the managed server, except to change the active state of the schedule.

System Action: The command fails and server operation continues.

User Response: To update this object, you can delete the subscription to the configuration profiles with which the object is associated.

ANR3215WManaged domain domain name contains at least one node and cannot be discarded.

Explanation: This message is issued while processing a DELETE SUBSCRIPTION command with DISCARDOBJECTS=YES. The indicated domain cannot be discarded on the managed server because it still contains one or more nodes.

System Action: Domain domain name is not deleted. Policy sets, management classes, copy groups, and client schedules belonging to this domain are also not deleted.

User Response: Before this domain can be deleted, nodes in the domain must be removed or assigned another domain.

ANR3216WManaged administrative schedule schedule name is active and cannot be discarded.

Explanation: This message is issued while processing a DELETE SUBSCRIPTION command with DISCARDOBJECTS=YES. The indicated administrative schedule cannot be discarded on the managed server because it is in the active state.

System Action: Administrative schedule schedule name is not deleted.

User Response: Before this administrative schedule can be deleted, it must be deactivated using the Update Schedule command.

ANR3217Ecommand: Administrator administrator name is a managed object and cannot be removed.

Explanation: The indicated administrator is a managed object and cannot be removed on the managed server.

System Action: The command fails and server operation continues.

User Response: To remove this administrator, you can delete the subscription to the configuration profiles with which the object is associated.

ANR3218Ecommand: Administrator administrator name is a managed object and cannot be updated.

Explanation: The indicated administrator is a managed object and cannot be updated on the managed server.

System Action: The command fails and server operation continues.

User Response: To update this administrator, you can delete the subscription to the configuration profiles with which the object is associated.

ANR3219Ecommand: Administrator administrator name is a managed object and cannot be renamed.

Explanation: The indicated administrator is a managed object and cannot be renamed on the managed server.

System Action: The command fails and server operation continues.

User Response: To rename this administrator, you can delete the subscription to the configuration profiles with which the object is associated.

ANR3220Ecommand: Administrator administrator name is a managed object - authority cannot be granted.

Explanation: The indicated administrator is a managed object. Authority cannot be granted to this administrator on the managed server.

System Action: The command fails and server operation continues.

User Response: To grant authority to this administrator, you can delete the subscription to the configuration profiles with which the object is associated.

ANR3221Ecommand: Administrator administrator name is a managed object - authority cannot be revoked.

Explanation: The indicated administrator is a managed object. Authority of this administrator cannot be revoked on the managed server.

System Action: The command fails and server operation continues.

User Response: To revoke authority of this administrator, you can delete the subscription to the configuration profiles with which the object is associated.

ANR3222WManaged administrator administrator name is the only system administrator and cannot be discarded.

Explanation: This message is issued while processing a DELETE SUBSCRIPTION command with DISCARDOBJECTS=YES. The indicated administrator cannot be discarded on the managed server because it is the only system administrator.

System Action: Administrator administrator name is not deleted.

User Response: Before this administrator can be deleted, another administrator must be given system authority.

ANR3223WManaged administrator administrator name is currently accessing the server and cannot be discarded.

Explanation: This message is issued while processing a DELETE SUBSCRIPTION command with DISCARDOBJECTS=YES. The indicated administrator cannot be discarded on the managed server because it has an active session with the server.

System Action: Administrator administrator name is not deleted.

User Response: Quit or cancel all sessions for this administrator before discarding the administrator definition.

ANR3224Ecommand: Command script command script name is a managed object and cannot be deleted.

Explanation: The indicated command script is a managed object and cannot be deleted on the managed server.

System Action: The command fails and server operation continues.

User Response: To delete this script, you can delete the subscription to the configuration profiles with which the object is associated.

ANR3225Ecommand: Command script command script name is a managed object and cannot be updated.

Explanation: The indicated command script is a managed object and cannot be updated on the managed server.

System Action: The command fails and server operation continues.

User Response: To update this script, you can delete the subscription to the configuration profiles with which the object is associated.

ANR3226Ecommand: Command script command script name is a managed object and cannot be renamed.

Explanation: The indicated command script is a managed object and cannot be renamed on the managed server.

System Action: The command fails and server operation continues.

User Response: To rename this script, you can delete the subscription to the configuration profiles with which the object is associated.

ANR3227Ecommand: Option set optionset name is a managed object and cannot be deleted.

Explanation: The indicated option set is a managed object and cannot be deleted on the managed server.

System Action: The command fails and server operation continues.

User Response: To delete this option set, you can delete the subscription to the configuration profiles with which the object is associated.

ANR3228Ecommand: Option set optionset name is a managed object and cannot be updated.

Explanation: The indicated option set is a managed object and cannot be updated on the managed server.

System Action: The command fails and server operation continues.

User Response: To update this option set, you can delete the subscription to the configuration profiles with which the object is associated.

ANR3229Ecommand: Command cannot be executed - option set optionset name is a managed object.

Explanation: The specified command cannot be executed because it would alter the contents of the indicated managed option set.

System Action: The command fails and server operation continues.

User Response: None.

ANR3230Ecommand: Server group group name is a managed object and cannot be deleted.

Explanation: The indicated server group is a managed object and cannot be deleted on the managed server.

System Action: The command fails and server operation continues.

User Response: To delete this server group, you can delete the subscription to the configuration profiles with which the object is associated.

ANR3231Ecommand: Server group group name is a managed object and cannot be updated.

Explanation: The indicated server group is a managed object and cannot be updated on the managed server.

System Action: The command fails and server operation continues.

User Response: To update this server group, you can delete the subscription to the configuration profiles with which the object is associated.

ANR3232Ecommand: Server group group name is a managed object and cannot be renamed.

Explanation: The indicated server group is a managed object and cannot be renamed on the managed server.

System Action: The command fails and server operation continues.

User Response: To rename this server group, you can delete the subscription to the configuration profiles with which the object is associated.

ANR3233Ecommand: Command cannot be executed - server group group name is a managed object.

Explanation: The specified command cannot be executed because it would alter the membership of the indicated managed server group.

System Action: The command fails and server operation continues.

User Response: None.

ANR3234Ecommand: Server server name is a managed object and cannot be deleted.

Explanation: The indicated server is a managed object and cannot be deleted on the managed server.

System Action: The command fails and server operation continues.

User Response: To delete this object, you can delete the subscription to the configuration profiles with which the object is associated.

ANR3235Ecommand: Server server name is a managed object - one or more specified attributes cannot be updated.

Explanation: Because the indicated server is a managed object, certain attributes cannot be updated on the managed server. These attributes are: SERVERPASSWORD, HLADDRESS, LLADDRESS, COMMMETHOD, DESCRIPTION, URL, and ALLOWREPLACE.

System Action: The command fails and server operation continues.

User Response: You can restrict the update to attributes that can be updated on the managed server. For example, the PASSWORD, NODENAME, FORCESYNC, and DELGRACEPERIOD attributes can be updated, even if the server is a managed object. Alternatively, you can delete the subscription to the configuration profiles with which the object is associated, so that the server is no longer a managed object.

ANR3236WServer server name is currently in use and cannot be discarded.

Explanation: This message is issued while processing a DELETE SUBSCRIPTION command with DISCARDOBJECTS=YES. The indicated server cannot be discarded on the managed server because server name is in use. This could occur if the managed server has an active connection to server name or if the managed server has a device class with DEVTYPE=SERVER that refers to server name.

System Action: Server server name is not deleted.

User Response: Before server name can be deleted, the managed server must not have a connection to that server and the managed server cannot have any device-class references to that server.

ANR3237WServer server name is the event server and cannot be discarded.

Explanation: This message is issued while processing a DELETE SUBSCRIPTION command with DISCARDOBJECTS=YES. The indicated server cannot be discarded because it is the event server for the managed server.

System Action: Server server name is not deleted.

User Response: Before server name can be deleted, the DELETE EVENTSERVER command must be used to remove the event server reference to server name.

ANR3238Ecommand: This object cannot be renamed because it is associated with one or more configuration profiles.

Explanation: This message is issued on a configuration manager when an attempt is made to rename an object that is associated with one or more configuration profiles. Associated objects cannot be renamed because the enterprise configuration facility does not support renaming of objects.

System Action: The command fails and server operation continues.

User Response: If you must change the object name you can delete the object, define it with a new name, and then define a profile association to the new object (unless a wildcard profile association already exists). This will cause the object to be deleted and re-defined on managed servers with subscriptions to the profiles with which this object is associated.

ANR3350WLocally defined domain domain name contains at least one node and cannot be replaced with a definition from the configuration manager.

Explanation: During configuration refresh processing the indicated locally defined domain could not be replaced with a definition from the configuration manager. The domain definition was not replaced because the domain still contains one or more assigned nodes.

System Action: Refresh processing continues, but this domain is not replaced. The system will attempt to replace the local domain during later configuration refresh operations.

User Response: If you want existing nodes to be assigned to the domain from the configuration manager, you can temporarily assign them to another domain. After the domain definition has successfully been propagated from the configuration manager, reassign the nodes to the new domain. Alternatively, if you want to prevent further attempts to replace the local domain definition during configuration refresh processing, delete the subscription to the profiles with which domain domain name is associated.

ANR3351WManaged domain domain name contains at least one node and cannot be deleted during configuration refresh processing.

Explanation: During configuration refresh processing, the enterprise configuration facility attempted to remove the indicated domain because it has been deleted from the configuration manager or because the profile association no longer exists. The domain could not be deleted on the managed server because it still contains one or more nodes.

System Action: Refresh processing continues, but this domain is not deleted. The system will attempt to delete the domain during later configuration refresh operations.

User Response: Assign nodes in this domain to another domain. Alternatively, you can delete the subscription to the profiles with which domain domain name is associated.

ANR3352ILocally defined domain domain name replaced during configuration refresh processing.

Explanation: During configuration refresh processing, a local domain definition was replaced with a definition from the configuration manager. The system also deleted all policy sets, management classes, copy groups, and client schedules belonging to the locally defined domain and added definitions from the configuration manager.

System Action: None.

User Response: None.

ANR3353IManaged domain domain name deleted during configuration refresh processing.

Explanation: During configuration refresh processing, the indicated managed domain was removed from the managed server. This occurred either because the domain has been deleted from the configuration manager or because the profile association no longer exists. The system also deleted all policy sets, management classes, copy groups, and client schedules belonging to the managed domain.

System Action: None.

User Response: None.

ANR3354WLocally defined administrative schedule schedule name is active and cannot be replaced with a definition from the configuration manager.

Explanation: During configuration refresh processing the indicated locally defined administrative schedule could not be replaced with a definition from the configuration manager. The schedule definition was not replaced because the schedule is in the active state.

System Action: Refresh processing continues, but this administrative schedule is not replaced. The system will attempt to replace the local administrative schedule during later configuration refresh operations.

User Response: If you want this administrative schedule to be replaced with the schedule definition from the configuration manager, deactivate the local schedule using the Update Schedule command. After the administrative schedule definition has successfully been propagated from the configuration manager, you can activate the new schedule. Alternatively, if you want to prevent further attempts to replace the local schedule definition during configuration refresh processing, delete the subscription to the profiles with which the schedule name is associated.

ANR3355WManaged administrative schedule schedule name is active and cannot be deleted during configuration refresh processing.

Explanation: During configuration refresh processing, the enterprise configuration facility attempted to remove the indicated administrative schedule because it has been deleted from the configuration manager or because the profile association no longer exists. The schedule could not be deleted on the managed server because the schedule is in the active state.

System Action: Refresh processing continues, but this schedule is not deleted. The system will attempt to delete the administrative schedule during later configuration refresh operations.

User Response: If you want this administrative schedule to be deleted in accordance with changes that have been made on the configuration manager, deactivate the managed schedule using the Update Schedule command. Alternatively, if you want to prevent further attempts to delete the managed schedule definition during configuration refresh processing, delete the subscription to the profiles with which the schedule name is associated.

ANR3356ILocally defined administrative schedule schedule name replaced during configuration refresh processing.

Explanation: During configuration refresh processing, a local administrative schedule definition was replaced with a definition from the configuration manager.

System Action: None.

User Response: None.

ANR3357IManaged administrative schedule schedule name deleted during configuration refresh processing.

Explanation: During configuration refresh processing, the indicated managed administrative schedule was removed from the managed server. This occurred either because the schedule has been deleted from the configuration manager or because the profile association no longer exists.

System Action: None.

User Response: None.

ANR3358WLocally defined administrator administrator name is the only system administrator and cannot be replaced with a definition from the configuration manager.

Explanation: During configuration refresh processing the indicated locally defined administrator could not be replaced with a definition from the configuration manager. The administrator definition was not replaced because it is the only system administrator and the definition from the configuration manager does not include system authority.

System Action: Refresh processing continues, but this administrator definition is not replaced. The system will attempt to replace the local administrator definition during later configuration refresh operations.

User Response: If you want this administrator definition to be replaced with a definition from the configuration manager, you can grant system authority to another administrator. Alternatively, if you want to prevent further attempts to replace the local administrator definition during configuration refresh processing, delete the subscription to the profiles with which administrator administrator name is associated.

ANR3359WManaged system administrator administrator name is the only system administrator and cannot be deleted during configuration refresh processing.

Explanation: During configuration refresh processing, the enterprise configuration facility attempted to remove the indicated administrator because it has been deleted from the configuration manager or because the profile association no longer exists. The administrator could not be deleted on the managed server because it is the only system administrator.

System Action: Refresh processing continues, but this administrator is not deleted. The system will attempt to delete the administrator during later configuration refresh operations.

User Response: Grant system authority to another administrator. Alternatively, you can delete the subscription to the profiles with which administrator administrator name is associated.

ANR3360WManaged system administrator administrator name is the only system administrator - authority cannot be revoked during configuration refresh processing.

Explanation: During configuration refresh processing, the enterprise configuration facility attempted to revoke authority for the indicated administrator because authority has been revoked on the configuration manager. The authority of the administrator could not be revoked on the managed server because this is the only system administrator.

System Action: Refresh processing continues, but authority is not revoked for this administrator. The system will attempt to revoke administrator during later configuration refresh operations.

User Response: Grant system authority to another administrator. Alternatively, you can delete the subscription to the profiles with which administrator administrator name is associated.

ANR3361ILocally defined administrator administrator name replaced during configuration refresh processing.

Explanation: During configuration refresh processing, a local administrator definition was replaced with a definition from the configuration manager.

System Action: None.

User Response: None.

ANR3362IManaged administrator administrator name deleted during configuration refresh processing.

Explanation: During configuration refresh processing, the indicated managed administrator was removed from the managed server. This occurred either because the administrator has been deleted from the configuration manager or because the profile association no longer exists.

System Action: None.

User Response: None.

ANR3363WManaged administrator administrator name is currently accessing the server and cannot be deleted during configuration refresh processing.

Explanation: During configuration refresh processing, the enterprise configuration facility attempted to remove the indicated administrator because it has been deleted from the configuration manager or because the profile association no longer exists. The administrator could not be deleted on the managed server because it currently has an active session with the server.

System Action: Refresh processing continues, but this administrator is not deleted. The system will attempt to delete the administrator during later configuration refresh operations.

User Response: Quit or cancel all sessions for the indicated administrator. Alternatively, you can delete the subscription to the profiles with which administrator administrator name is associated.

ANR3364WAdministrator administrator name has been removed. This administrator has defined or updated administrative schedules that will fail when executed.

Explanation: This message is issued during configuration refresh processing or as a result of a DELETE SUBSCRIPTION command with the DISCARDOBJECTS=YES option. The indicated managed administrator was removed from the server, but this administrator owns one or more administrative schedules. These schedules will fail when executed in the future because they do not belong to a valid administrator.

System Action: The indicated administrator was removed.

User Response: Use the QUERY SCHEDULE command OR an SQL SELECT statement on the ADMIN_SCHEDULES table to determine which schedules were last updated by the administrator. Use the UPDATE SCHEDULE command to update those schedules under an administrator that has authority to execute them, or use the DELETE SCHEDULE command to remove the schedules.

ANR3365ILocally defined command script command script name replaced during configuration refresh processing.

Explanation: During configuration refresh processing, a local command script definition was replaced with a definition from the configuration manager.

System Action: None.

User Response: None.

ANR3366IManaged command script command script name deleted during configuration refresh processing.

Explanation: During configuration refresh processing, the indicated managed command script was removed from the managed server. This occurred either because the script has been deleted from the configuration manager or because the profile association no longer exists.

System Action: None.

User Response: None.

ANR3367ILocally defined option set option set name replaced during configuration refresh processing.

Explanation: During configuration refresh processing, a local option set definition was replaced with a definition from the configuration manager.

System Action: None.

User Response: None.

ANR3368IManaged option set option set name deleted during configuration refresh processing.

Explanation: During configuration refresh processing, the indicated managed option set was removed from the managed server. This occurred either because the option set has been deleted from the configuration manager or because the profile association no longer exists.

System Action: None.

User Response: None.

ANR3369ILocally defined server group group name replaced during configuration refresh processing.

Explanation: During configuration refresh processing, a local server group definition was replaced with a definition from the configuration manager.

System Action: None.

User Response: None.

ANR3370IManaged server group group name deleted during configuration refresh processing.

Explanation: During configuration refresh processing, the indicated managed server group was removed from the managed server. This occurred either because the server group has been deleted from the configuration manager or because the profile association no longer exists.

System Action: None.

User Response: None.

ANR3371WServer group group name cannot be defined during configuration refresh processing because a server already exists with this name.

Explanation: During configuration refresh processing, the enterprise configuration facility attempted to define the indicated server group on a managed server. The server group could not be defined because a server definition with the same name already exists on the managed server.

System Action: Refresh processing continues, but this server group is not defined. The system will attempt to define the server group during later configuration refresh operations.

User Response: You can delete the subscription to the profile with which the indicated server group is associated or delete the conflicting server definition on the managed server. Alternatively, you can rename the server group on the configuration manager, after first deleting the profile association for that server group.

ANR3372ILocally defined server server name replaced during configuration refresh processing.

Explanation: During configuration refresh processing, a local server definition was replaced with a definition from the configuration manager.

System Action: None.

User Response: None.

ANR3373IServer server name deleted during configuration refresh processing.

Explanation: During configuration refresh processing, the definition for managed object server name was removed from the managed server. This occurred either because server name has been deleted from the configuration manager or because the profile association no longer exists.

System Action: None.

User Response: None.

ANR3374IServer group group name replaced with server server name during configuration refresh processing.

Explanation: During configuration refresh processing, a server group definition was replaced with a server definition from the configuration manager. The server has the same name as the deleted server group.

System Action: None.

User Response: None.

ANR3375WServer server name is currently in use cannot be deleted during configuration refresh processing.

Explanation: During configuration refresh processing, the enterprise configuration facility attempted to remove the indicated server definition because it has been deleted from the configuration manager or because the profile association no longer exists. The indicated server could not be deleted on the managed server because server name is in use. This could occur if the managed server has an active connection to server name or if the managed server has a device class with DEVTYPE=SERVER that refers to server name.

System Action: Refresh processing continues, but this server definition is not deleted. The system will attempt to delete the server during later configuration refresh operations.

User Response: Before server name can be deleted, the managed server must not have a connection to that server and the managed server cannot have any device-class references to that server.

ANR3376WServer server name is the event server and cannot be deleted during configuration refresh processing.

Explanation: During configuration refresh processing, the enterprise configuration facility attempted to remove the indicated server definition because it has been deleted from the configuration manager or because the profile association no longer exists. The indicated server could not be deleted on the managed server because it is the event server for the managed server.

System Action: Refresh processing continues, but this server definition is not deleted. The system will attempt to delete the server during later configuration refresh operations.

User Response: Before server name can be deleted, the DELETE EVENTSERVER command must be used to remove the event server reference to server name.

ANR3377WReplacement of local server server name with a definition from the configuration manager is not allowed.

Explanation: During configuration refresh processing, the enterprise configuration facility attempted to replace the indicated server definition with a definition from the configuration manager. This operation could not be performed because ALLOWREPLACE=NO for the indicated server.

System Action: Refresh processing continues, but this server definition is not replaced. The system will attempt to replace the server definition during later configuration refresh operations.

User Response: Before the local server definition for server name can be replaced with a definition from the configuration manager, the UPDATE SERVER command must be used to set the ALLOWREPLACE attribute to ON.

ANR3470ICommand: Auditing enterprise configuration definitions.

Explanation: The server has started to audit database definitions used by the enterprise configuration facility.

System Action: Server database audit operation continues.

User Response: None.

ANR3471EAudit command: Enterprise configuration global attributes are missing.

Explanation: A database audit process finds that the global attributes used by the enterprise configuration facility are missing.

System Action: Audit processing continues.

User Response: Reissue the audit command with FIX=YES specified so that the enterprise configuration global attributes can be recreated.

ANR3472IAudit command: Enterprise configuration global attributes are missing - attributes will be recreated using available database information or default values.

Explanation: A database audit process finds that the global attributes used by the enterprise configuration facility are missing. Because FIX=YES has been specified on the AUDIT command, these attributes will be recreated using available information from the database or default values.

System Action: Audit processing continues.

User Response: When the audit completes, you can use the QUERY STATUS command to examine the values set for the enterprise configuration global attributes. Then use the appropriate SET command to change the attributes, if desired.

ANR3473EAudit command: Enterprise configuration global attribute(s) are incorrect.

Explanation: A database audit process finds that global attributes used by the enterprise configuration facility are incorrect.

System Action: Audit processing continues.

User Response: Reissue the audit command with FIX=YES specified so that the enterprise configuration global attributes can be corrected.

ANR3474IAudit command: Enterprise configuration global attribute(s) are incorrect - attributes will be corrected using available database information or default values.

Explanation: A database audit process finds that global attributes used by the enterprise configuration facility are incorrect. Because FIX=YES has been specified on the AUDIT command, these attributes will be corrected using available information from the database or default values.

System Action: Audit processing continues.

User Response: When the audit completes, you can use the QUERY STATUS command to examine the values set for the enterprise configuration global attributes. Then use the appropriate SET command to change the attributes, if desired.

ANR3475EAudit command: Extraneous profile information found.

Explanation: A database audit process finds extraneous configuration profile information.

System Action: Audit processing continues.

User Response: Reissue the audit command with FIX=YES so that the information is deleted.

ANR3476EAudit command: Extraneous profile information found - information will be deleted.

Explanation: A database audit process finds extraneous configuration profile information. Because FIX=YES has been specified for the audit command, the extraneous information will be deleted.

System Action: Audit processing continues.

User Response: None.

ANR3477EAudit command: Profile information is inconsistent.

Explanation: A database audit process detects inconsistent configuration profile information. This information can be corrected.

System Action: Audit processing continues.

User Response: Reissue the audit command with FIX=YES so that the information can be corrected.

ANR3478EAudit command: Profile information is inconsistent - it will be corrected.

Explanation: A database audit process detects inconsistent configuration profile information. Because FIX=YES has been specified for the audit command, the information will be corrected.

System Action: Audit processing continues.

User Response: None.

ANR3479EAudit command: Profile association information is missing.

Explanation: A database audit process detects missing profile association information. This information can be recreated.

System Action: Audit processing continues.

User Response: Reissue the audit command with FIX=YES so that the information can be recreated.

ANR3480EAudit command: Profile association information is missing - it will be recreated.

Explanation: A database audit process detects missing profile association information. Because FIX=YES has been specified for the audit command, the information will be recreated.

System Action: Audit processing continues.

User Response: None.

ANR3481EAudit command: Extraneous profile association information found.

Explanation: A database audit process finds extraneous profile association information.

System Action: Audit processing continues.

User Response: Reissue the audit command with FIX=YES so that the information is deleted.

ANR3482EAudit command: Extraneous profile association information found - information will be deleted.

Explanation: A database audit process finds extraneous profile association information. Because FIX=YES has been specified for the audit command, the extraneous information will be deleted.

System Action: Audit processing continues.

User Response: None.

ANR3483EAudit command: Subscription information is inconsistent.

Explanation: A database audit process detects inconsistent profile subscription information. This information can be corrected.

System Action: Audit processing continues.

User Response: Reissue the audit command with FIX=YES so that the information can be corrected.

ANR3484EAudit command: Profile subscription information is inconsistent - it will be corrected.

Explanation: A database audit process detects inconsistent profile subscription information. Because FIX=YES has been specified for the audit command, the information will be corrected.

System Action: Audit processing continues.

User Response: None.

ANR3485EAudit command: Profile subscriptions were found to more than one configuration manager.

Explanation: A database audit process determines that a managed server has subscriptions to more than one configuration manager. This may cause the enterprise configuration facility to behave in an unpredictable manner.

System Action: Audit processing continues.

User Response: Delete subscriptions for all but one configuration manager. To do this, it may be necessary to delete subscriptions to all configuration managers and then define the desired subscriptions.

ANR3500IBackup set for node node name as set name being generated.

Explanation: The named object set is being created for the specified node.

System Action: The server generates a backup set.

User Response: None.

ANR3501IBackupset for node name as set name completed successfully - processed files files.

Explanation: The named object set was successfully created for the specified node. The number of files processed is specified.

System Action: None.

User Response: None.

ANR3502WBackupset for node name as set name completed with file processing errors - processed files files with error files files skipped.

Explanation: The named object set was successfully created for the specified node. However, during processing errors were encountered accessing some files - these files were skipped.

System Action: None.

User Response: Evaluate other server messages for an indication of why the files where skipped. Files can be skipped because of failures locking those files or for other more serious problems. First, re-try the command and see if it completes without any skipped files. If you are unable to generate the backup set without skipping files, please contact your local service representative for assistance.

ANR3503EGeneration of backupset for node name as set name failed.

Explanation: The named object for the specified node was not created. An error was encountered causing the creation of this object set not to complete successfully.

System Action: Server operation continues.

User Response: Evaluate other messages that were issued and try to determine the cause of the failure. After determining the cause of the failure, retry the command. If the cause can not be determined, please contact your local service representative.

If ANR3504W was received, an error occurred while logging the volumes used to the server volume history. It is possible to issue a DEFINE BACKUPSET listing these volumes. That would cause the server to create the necessary entries for this backup set on this server.

ANR3504WBackupset for node name as set name was not able to log the volumes used for this operation to the server volume history.

Explanation: The named object for the specified node was created. However, when the process attempted to add the volumes, used for this operation to the volume history for the server, an error occurred and this could not be completed.

System Action: Server operation continues.

User Response: Review other messages issued to determine which volumes where used for to generate this backup set. The volumes can be inserted into the server volume history for use by issuing a DEFINE BACKUPSET and listing these volumes. This will also allow this backup set to be queried from a client as well since there is not a server entry for this backup set. Only issue the DEFINE BACKUPSET if this generate backupset operation completed successfully.

ANR3505IBackupset for node name as set name used volume volume name.

Explanation: The named object for the specified node used the specified volume.

System Action: Server operation continues.

User Response: None.

ANR3507ICancel in progress

Explanation: This message is displayed in response to a QUERY PROCESS command, and indicates that a generate backupset process has been canceled. The process will end shortly.

System Action: The process terminates and server operation continues.

User Response: None.

ANR3508WGeneration of backup set for node name as set name failed - no filespaces to process.

Explanation: The named object for the specified node was not created. No filespaces were available to process.

System Action: Server operation continues.

User Response: Reissue the command against a node that has filespaces associated with it. If no filespaces exist for a given node, then there is no file data to write to the backupset.

ANR3509ECommand: Error encountered in accessing data storage - device class device class name is not defined.

Explanation: During command command processing, an error occurred because the specified device class is not defined.

System Action: The command command is ended and server operation continues.

User Response: Make sure the specified device class is defined.

ANR3510ECommand: Error encountered in accessing data storage - disk volume specified.

Explanation: During command command processing, an error occurred because a specified volume is a disk volume rather than a tape volume.

System Action: The command command is ended and server operation continues.

User Response: Make sure that all volumes specified for the command command are tape volumes.

ANR3511ECommand: Error encountered in accessing data storage - invalid volume name specified.

Explanation: The server encounters an error in accessing data storage while processing command command. The error occurred because an attempt has been made to access a volume with an invalid name.

System Action: The command command operation is ended and server operation continues.

User Response: Issue the command with a valid volume name.

ANR3512ECommand: Error encountered in accessing data storage - insufficient number of mount points available for removable media.

Explanation: During command command processing, the server cannot allocate sufficient mount points.

System Action: The command command operation is ended and server operation continues.

User Response: If necessary, make more mount points available.

ANR3513ECommand: Output error encountered in accessing data storage.

Explanation: The command command operation ends because an error has been encountered by the server in writing to a device. Possible reasons include:

System Action: The command command operation ends and server operation continues.

User Response: Query the activity log to find messages preceding this one to determine the cause of the error. After the problem is corrected, the command can be retried.

ANR3514ECommand: Data transfer was interrupted in accessing data storage.

Explanation: The database transaction associated with command command operation failed because data transfer to or from data storage was interrupted by an external event.

System Action: The command command operation is ended and server operation continues.

User Response: Examine the messages issued prior to this message to determine why the data transfer was interrupted. Reissue the command command after the problem is resolved.

ANR3515ECommand: Error encountered in accessing data storage - volume already in use.

Explanation: During command command processing, a volume cannot be used because it is already defined in a storage pool, or has been previously used by an export, database dump, or database backup operation (as recorded in the volume history) or is in use by another process.

System Action: The command command operation is ended and server operation continues.

User Response: Specify a volume that is not in use or defined in a storage pool, and that has not been previously used for an export, database dump, or database backup operation as recorded in the server volume history information. Use the QUERY VOLUME command to display the names of volumes that are defined to server storage pools. Use the QUERY VOLHISTORY command to display the names of volumes that have been used for export, database dump, or database backup operations.

ANR3516ECommand: Out of space on sequential media, scratch media could not be mounted.

Explanation: During command command processing, the process encounters an out-of-space condition writing to the sequential media. Command command ends when there is no more space on the sequential media for storing data and SCRATCH=NO has been specified on command command.

System Action: Command command processing ends. Server processing continues.

User Response: Reissue the command and specify SCRATCH=YES or specify additional volume names on the command.

ANR3517ECommand: Error encountered in accessing data storage - required volume was not mounted.

Explanation: During command command processing, a required volume cannot be mounted. The mount request may have been canceled.

System Action: The command command operation is ended and server operation continues.

User Response: Issue the command again and make sure the necessary volumes are accessible.

ANR3518ICommand: Processing canceled before completion.

Explanation: The background process to service the command command has been canceled with the CANCEL PROCESS command.

System Action: Processing for the command command ends. Statistics on the number and type of objects moved, together with the total number of bytes copied, are displayed on the server console following this message.

User Response: None.

ANR3519ECommand: Insufficient memory available in accessing data storage.

Explanation: The server encounters a memory shortage in accessing data storage during command command operation.

System Action: The command command operation ends and server operation continues.

User Response: Allocate additional storage to the server. For details, issue HELP MEMORY to display the information online or see "Appendix A. Allocating Additional Server Memory".

ANR3520ECommand: Internal error encountered in accessing data storage.

Explanation: The server encounters an internal error in accessing data storage while processing command command operation.

System Action: The command command operation is ended and server operation continues.

User Response: Use the QUERY ACTLOG command to examine messages prior to this error to determine the cause of the data storage failure. If the failure can be found and resolved, reissue the command command operation. If the failure cannot be found, contact your service representative for assistance in resolving the problem.

ANR3521WBackupSet command: Data storage retrieve or restore failed - data integrity error detected.

Explanation: The server ends an backup set operation because an internal database integrity error has been encountered on the server.

System Action: The server ends the backup set operation and continues operation.

User Response: Contact your service representative.

ANR3522WCommand: Retrieve or restore failed - file was deleted from data storage during retrieval.

Explanation: The server ends a file retrieval operation for the specified command because the file has been deleted from data storage by another process before retrieval is complete.

System Action: The server ends the command and continues operation.

User Response: Contact your administrator to find out if DELETE FILESPACE, DELETE VOLUME, or inventory expiration processes are running; these processes can delete data storage files during retrieval. Reissue the command after these processes have been completed or canceled.

ANR3523WBackup set command: Retrieve failed - error on input storage device.

Explanation: The server ends a backup set operation for the specified session because an I/O error has been encountered by the server in reading from a device. The object for which the I/O was issued is reported in a later message.

System Action: Backup set processing skips this file, and continues operation.

User Response: Query the activity log to find messages preceding this one that specify the device that is failing. Storage pool volumes can be varied offline (by using the VARY OFFLINE command), or the server may need to be shut down with the HALT command to correct the hardware problem.

ANR3524WBackup set command: Transaction failed - data transfer interrupted.

Explanation: The database transaction associated with a backup set operation failed because data transfer to or from data storage was interrupted by an external event.

System Action: The backup set operation is ended and server operation continues.

User Response: Examine the messages issued prior to this message to determine why the data transfer was interrupted. Attempt the backup set operation again after problem is resolved.

ANR3525WBackup set command: Transaction failed - storage media inaccessible.

Explanation: The server ends a transaction for an backup set operation because storage volumes are not available in the storage pools in which the client files are to be stored.

System Action: The server ends the backup set operation and server operation continues.

User Response: An authorized administrator can issue the DEFINE VOLUME command to add storage to one or more storage pools in the storage hierarchy. The VARY ONLINE command can be used to vary offline storage volumes online in the storage hierarchy to make them available for file storage.

ANR3526EBackup set command: Error encountered in accessing data storage - volume cannot be used.

Explanation: During backup set processing, a volume has been mounted but cannot be used.

System Action: The backup set operation is ended and server operation continues.

User Response: Query the activity log for messages preceding this one that give additional information. Make sure a usable volume is specified and mounted.

ANR3527EBackup set command operation terminated - incomplete input volume list.

Explanation: The list of volumes needed to process the command was incomplete. At least one volume needed for the operation is missing from the end of the list.

System Action: The command operation is ended.

User Response: Issue the command again and make sure the necessary volumes are included in the volume list.

ANR3528EBackup set command: Media not accessible in accessing data storage.

Explanation: The server ends a transaction for a backup set operation because storage volumes are not available in the storage pools in which the client files are to be stored.

System Action: The server ends the backup set operation and server operation continues.

User Response: An authorized administrator can issue the DEFINE VOLUME command to add storage to one or more storage pools in the storage hierarchy. The VARY ONLINE command can be used to vary offline storage volumes online in the storage hierarchy to make them available for file storage.

ANR3529WGenerate backupset skipping damaged file on volume volume name: Node node name, Type file type, File space filespace name, File name file name.

Explanation: During generate backupset process, a file is encountered that was previously found to be damaged. If this file is part of an aggregate, the entire aggregate was previously marked damaged, possibly because an integrity error was detected for some other file within the aggregate.

System Action: The damaged file is not added to the backupset.

User Response: Audit the indicated volume with FIX=NO to verify that the file is damaged. The audit will reset the file status if the file is found to be undamaged during the audit. If the file is part of an aggregate, the audit will reset the aggregate status if the entire aggregate is found to be undamaged. If the file is reset to the undamaged state and it is important that the file be included in the backupset, rerun the generate backupset command. If, however, the audit does not clear the damaged state of the file and if this volume is in a primary storage pool that has previously been backed up to a copy storage pool, attempt to restore damaged files by using the RESTORE STGPOOL command. If it is still important that the file be included in the backupset, rerun the generate backupset command.

ANR3540EObject set set node:set name was not found for session session number, node.

Explanation: The indicated session id requested to restore the object set. The object set was not found on the server.

System Action: The error is returned to the client.

User Response: None.

ANR3541EError error code occurred opening object set set node:set name for session session number, node.

Explanation: An error occurred while opening the indicated object set.

System Action: An error is returned to the client.

User Response: Correct the problem reported by previous messages, if possible.

ANR3542EError error code occurred reading object set set node:set name for session session number, node.

Explanation: An error occurred while reading the indicated object set.

System Action: An error is returned to the client.

User Response: Correct the problem reported by previous messages, if possible.

ANR3543EError error code occurred while sending entries from object set set node:set name for session session number, node.

Explanation: An error occurred while sending entries for the indicated object set.

System Action: An error is returned to the client.

User Response: Correct the problem reported by previous messages, if possible.

ANR3550EDefinition of backup set set name for node name failed because it has an unknown format.

Explanation: The named object for the specified node was not defined. It was generated on a server that is at a higher level than this server and contains data that cannot be properly interpreted by this server.

System Action: Server operation continues.

User Response: Define the object on a server that is compatible with the server that generated the object, or upgrade this server to be compatible with the server that generated the object.

ANR3601WPolicy Domain release failed for domain domain id due to communications failure.

Explanation: The storage service was attempting to inform the data base server that it was finished with the domain indicated by the domain id, but was unable to communicate with the data base server. The cached policy information will be cleaned up when the storage server terminates or re-starts or when the data base server re-starts.

System Action: The storage service continues operation. The policy information is deleted from the storage service policy cache.

User Response: Policy caches are cleaned up on the storage service or server re-start. Network communication between the storage service and data base server should be checked.

ANR3602EUnable to communicate with data base server.

Explanation: The storage service was attempting to communicate with the data base server but was unable to do so.

System Action: The storage service operation fails.

User Response: Check the configuration of the storage service and server to ensure that communication parameters are correct. Ensure that the data base server is running and is accepting messages.

ANR3603EStorage Service server name was unable to load policy information due to a protocol error.

Explanation: While receiving policy information from a data base server, processing ended prematurely because of a protocol error.

System Action: Server operation continues. Policy is loaded from the data base server database.

User Response: If this problem persists, contact your service representative.

ANR3604EThis command is not supported in the current operating environment.

Explanation: A command was issued that is valid under most circumstances, but not in the current server environment.

System Action: Server operation continues.

User Response: Issue commands which are allowed in the current environment.

ANR3605EUnable to communicate with storage service.

Explanation: The data base server was attempting to communicate with the storage service but was unable to do so.

System Action: The data base server operation fails.

User Response: Check the configuration of the storage service and server to ensure that communication parameters are correct.

ANR3606EThe storage service was communicating with the data base server on a restore request with verb verb name and received return code return code.

Explanation: The storage service and data base server were coordinating a restore request. While communicating using the indicated verb (an internal request mechanism between the storage service and data base server), an unexpected return code was received. The verb name and return code are provided for Tivoli support personnel.

System Action: Data base server and storage service continue. The restore request fails, but may be retried by the client.

User Response: Check the configuration of the storage service and server to ensure that communication parameters are correct.

If this problem persists, contact your service representative.

ANR3607EThe storage service was communicating with the client on a restore request with verb verb name and received return code return code.

Explanation: The storage service was communicating with a client for a restore request. While communicating using the indicated verb (an internal request mechanism between the storage service and client), an unexpected return code was received.The verb name and return code are provided for Tivoli support personnel.

System Action: Data base server and storage service continue. The restore request fails, but may be retried by the client.

User Response: Check the configuration of the storage service and client to ensure that communication parameters are correct.

If this problem persists, contact your service representative.

ANR3608EThe storage service was communicating with the data base server on a restore request. An unexpected request (id verb) was received from the data base server.

Explanation: The storage service and data base server were coordinating a restore request. While communicating, the indicated verb (an internal request mechanism between the storage service and data base server), was unexpected. The verb number is provided for Tivoli support personnel.

System Action: Data base server and storage service continue. The restore request may fail, but may be retried by the client.

User Response: If this problem persists, contact your service representative.

ANR4000IDump command: Database dump process started.

Explanation: The database dump process has started.

System Action: The server dumps the contents of the database to a file or removable media.

User Response: None.

ANR4001IDump command: Database dump process completed.

Explanation: The database dump process has ended.

System Action: The server completes processing.

User Response: None.

ANR4002IDump command: Database dump process terminated due to error (error indicator).

Explanation: The database dump process has ended prematurely due to an error.

System Action: The server ends dump processing.

User Response: Examine previously issued messages to determine if an error can be corrected, such as an output error. If you cannot resolve the error, contact your service representative.

ANR4003ILoad command: Database load process started.

Explanation: The database load process has started.

System Action: The server loads the contents of the database from a file or removable media.

User Response: None.

ANR4004ILoad command: Database load process completed.

Explanation: The database load process has ended.

System Action: The server completes processing.

User Response: None.

ANR4005ELoad command: Database load process terminated due to error (error indicator).

Explanation: The database load process has ended prematurely due to an error.

System Action: The server ends load processing.

User Response: Examine previously issued messages to determine if an error can be corrected, such as a syntax error. If you cannot resolve the error, contact your service representative.

ANR4006ICommand: Volume volume number written by process is volume name.

Explanation: A sequential data process wrote to the volume named in the series of one or more volumes that were used to store output. The volume's position in the series in indicated by the volume number reported.

System Action: The server ends processing.

User Response: None.

ANR4007ECommand: A transaction error was encountered in recording volume usage history.

Explanation: The command process encounters a database transaction error in recording the names of the volumes used for the process in the server database.

System Action: The server ends processing.

User Response: Examine previously issued messages to determine if there is an error that can be corrected, such as a syntax error. If you cannot resolve the error, contact your service representative. The volumes used by the process are valid for the corresponding input process, but are not recorded in sequential volume history lists generated by the server.

ANR4008WLoad command: Database object object name does not exist.

Explanation: The database load process attempts to delete a database object, but the object does not exist.

System Action: Database processing continues.

User Response: None.

ANR4009ELoad command: Database object object name cannot be deleted because it is in use by another process.

Explanation: The database load process attempts to delete a database object, but the object is currently being used by another process.

System Action: Database processing ends.

User Response: Reissue the command. If it fails, contact your service representative.

ANR4010EDump/load command: Database dump/load processing failed - insufficient memory.

Explanation: The database dump/load process fails due to insufficient memory.

System Action: Database processing ends.

User Response: Allocate additional storage to the server. There are two ways to do this:

ANR4011WDump command: Database page page number is invalid - it will be skipped.

Explanation: The specified page is invalid, and it will not be used during dump processing.

System Action: Processing continues.

User Response: None.

ANR4012WDump command: Database page page number is damaged.

Explanation: The specified database page is damaged; it will not be dumped.

System Action: Processing continues.

User Response: None.

ANR4013IDump command: Dumped number of entries database entries (cumulative).

Explanation: This message indicates the number of database entries that have been dumped so far during database dump processing.

System Action: Server processing continues.

User Response: None.

ANR4014ELoad command: The specified input volume does not contain a server database dump.

Explanation: The specified volume does not contain a dump created from the database dump command.

System Action: Processing ends.

User Response: None.

ANR4015ELoad command: Invalid record format (format code) detected.

Explanation: During processing of command load command, an invalid record type is detected when reading the dumped information from the dump media.

System Action: Processing of the command ends.

User Response: Examine the server messages issued prior to this message to determine the source of the error. On MVS or VM, the LOADDB command syntax may be specified by using a ddname or by specifying a device class name. You must use the same method that was used when the data base was originally dumped. If you did not, this error message will be displayed. Try loading the data base by using the other method of syntax (devclass). If the error cannot be isolated and resolved, contact your service representative.

ANR4016ELoad command: Invalid header sequence number detected in database dump. Expected expected sequence number; Actual actual sequence number.

Explanation: During processing of command load command, an invalid sequence number is detected when reading the dumped information from the dump media.

System Action: Processing of the command ends.

User Response: Examine previously issued server messages to determine the source of the error. If the error cannot be isolated and resolved, contact your service representative.

ANR4017ELoad command: Invalid record type record type read from database dump data.

Explanation: The server database load process encounters an invalid record in reading data from the dump media.

System Action: The database load process ends.

User Response: Examine previously issued server messages to determine the source of the error. If the error cannot be isolated and resolved, contact your service representative.

ANR4018ELoad command: Load processing failed - insufficient recovery log space.

Explanation: The load process fails due to insufficient recovery log space.

System Action: Database load processing ends.

User Response: Reinstall the server and specify a larger recovery log and reissue the database load command.

ANR4019ELoad command: Load processing failed - insufficient database space.

Explanation: The load process fails due to insufficient database space.

System Action: Load processing ends.

User Response: Reinstall the server and specify a larger database and reissue the database load command.

ANR4020ELoad command: Batch database insert failed.

Explanation: The database load process fails when it attempts to insert a batch of rows into the database.

System Action: Database load processing ends.

User Response: Examine the messages issued prior to this one to determine if an error can be corrected. You may wish to reinstall the server with a new recovery log and database and reissue the load command. If the problem persists, contact your service representative.

ANR4021EDump/load command: Error (error code) occurred during an open operation.

Explanation: An error occurs while attempting an open operation on the dump media for a database dump/load operation.

System Action: Server processing continues.

User Response: Refer to the other displayed messages to determine why the operation failed; correct the problem and restart the process.

ANR4022EDump command: Error (error code) occurred during a write operation.

Explanation: The server database dump process encounters an error while writing to the dump media.

System Action: Server processing continues, the dump processing ends.

User Response: Refer to the other displayed messages to determine why the operation failed; correct the problem and restart the process.

ANR4023ELoad command: Error (error code) occurred during a read operation.

Explanation: The server database load process encounters an error reading from the dump media.

System Action: The database load operation ends.

User Response: Refer to the other displayed messages to determine why the operation failed; correct the problem and restart the process.

ANR4025IDumped number of pages database pages, number of bit vectors bit vectors, and number of database entries database entries; number of bad pages bad database pages have been encountered; number of bytes copied.

Explanation: This message is displayed in response to a QUERY PROCESS command executed against an online database dump process. The message displays information about the progress of the dump.

System Action: Database dump processing continues.

User Response: None. You may cancel the dump process with the CANCEL PROCESS command.

ANR4026IDump command: Process process number, database dump has completed.

Explanation: The online server database dump process started as process process number has completed.

System Action: Database dump processing ends.

User Response: None.

ANR4027IDump command: Process process number, database dump was canceled.

Explanation: The online server database dump process started as process process number has been canceled with the CANCEL PROCESS command.

System Action: Database dump processing ends.

User Response: None.

ANR4028IDump command: Process process number, Database dump terminated due to an error (error code).

Explanation: The online database dump process has ended prematurely due to an error.

System Action: The server ends dump processing.

User Response: Examine the messages issued prior to this message to see if an error can be corrected, such as output error. If you cannot resolve the error, contact your service representative.

ANR4029IDump command: Database checkpoint started.

Explanation: The database dump process is flushing updated database pages from the database buffer pool to stable storage so that they can be dumped.

System Action: Database dump processing continues.

User Response: None.

ANR4030IDump command: Database checkpoint completed.

Explanation: The database dump process has flushed all updated pages from the database buffer pool to stable storage.

System Action: Database load processing continues.

User Response: None.

ANR4031IDump/load command: Copied number of pages database pages.

Explanation: This message is displayed at the end of a server database dump or load command to indicate the number of database pages copied.

System Action: Database dump or load processing ends.

User Response: None.

ANR4032IDump/load command: Copied number of records database records.

Explanation: This message is displayed at the end of a server database dump or load command to indicate the number of database records copied.

System Action: Database dump or load processing ends.

User Response: None.

ANR4033IDump/load command: Copied number of bit vectors bit vectors.

Explanation: This message is displayed at the end of a server database dump or load command to indicate the number of database bit vectors copied.

System Action: Database dump or load processing ends.

User Response: None.

ANR4034IDump/load command: Encountered number of bit vectors bad database pages.

Explanation: This message is displayed at the end of a server database dump or load command to indicate the number of invalid database pages that have been encountered.

System Action: Database dump or load processing ends.

User Response: None.

ANR4035IDump/load command: Encountered number of bit vectors bad database records.

Explanation: This message is displayed at the end of a server database dump or load command to indicate the number of invalid database records that have been encountered.

System Action: Database dump or load processing ends.

User Response: None.

ANR4036IDump/load command: Copied number of bit vectors database entries.

Explanation: This message is displayed at the end of a server database dump or load command to indicate the number of database entries that have been copied.

System Action: Database dump or load processing ends.

User Response: None.

ANR4037IDump/load command: number of bit vectors copied.

Explanation: This message is displayed at the end of a server database dump or load command to indicate the number of bytes that have been copied.

System Action: Database dump or load processing ends.

User Response: None.

ANR4038ILoad command: Loading database information dumped on dump date at dump time.

Explanation: At the beginning of a server database load process, this message indicates the date and time that the dump took place for the database information that is loaded into the server.

System Action: Database load processing continues.

User Response: None.

ANR4039ILoad command: Loaded number of entries database entries (cumulative).

Explanation: This message indicates the number of database entries that have been loaded so far during database load processing.

System Action: Database load processing continues.

User Response: None.

ANR4040IAudit command: Auditing client node and administrator definitions.

Explanation: This message is displayed during a database audit and indicates that the client node and administrator definitions are being examined by the database audit process.

System Action: Audit processing continues.

User Response: None.

ANR4041IAudit command: Node node name is assigned to Domain domain name, but not verified by server database policy entries.

Explanation: A database audit process finds a node assigned to a policy domain that is not recorded properly in policy database entries.

System Action: Audit processing continues.

User Response: If FIX=YES has not been specified for the audit command, you may want to run this command again, and specify FIX=YES so that the audit process can correct the policy domain assignment for the node.

ANR4042IAudit command: Node node name is assigned to Domain domain name, but not found in server database policy entries - attempting to assign the node to domain domain name.

Explanation: A database audit process finds a node assigned to a policy domain that cannot be referenced in database policy entries. Because FIX=YES has been specified for the audit command, the audit function will attempt to correct the policy domain assignment for the node.

System Action: Audit processing continues.

User Response: When the audit command completes, you may want to check the domain assignment for this node, and reassign the node to a different policy domain, if desired.

ANR4043IAudit command: Node node name assignment failed - will attempt to assign the node to domain domain name.

Explanation: A database audit process finds a node assigned to a policy domain that cannot be located in database policy entries. Because FIX=YES has been specified for the audit command, the audit function is attempting to assign the node to an existing policy domain. The function attempts to assign the node to the domain name specified.

System Action: Audit processing continues.

User Response: When the audit command completes, you may want to check the domain assignment for this node, and reassign the node to a different policy domain, if desired.

ANR4044IAudit command: Could not assign Node node name to a policy domain; use the UPDATE NODE command to assign a policy domain for this node.

Explanation: A database audit process cannot find an appropriate policy domain for assigning the specified node.

System Action: Audit processing continues.

User Response: When the audit command completes, use the UPDATE NODE command to assign the specified node to an appropriate policy domain.

ANR4045IAudit command: Invalid compression value encountered for node node name.

Explanation: A database audit process encounters an invalid node compression value for the node indicated.

System Action: Audit processing continues.

User Response: If FIX=YES has not been specified for the audit command, you may want to run this command again, and specify FIX=YES so that the audit process can correct the problem.

ANR4046IAudit command: Invalid compression value encountered for node node name the default value will be set.

Explanation: A database audit process encounters an invalid node compression value for the node indicated. Because FIX=YES has been specified, the audit function sets the node's compression value to the default value.

System Action: Audit processing continues.

User Response: If you want the compression value for the specified node to be set to a value other than the default, use the UPDATE NODE command to change the value after the audit command has completed.

ANR4047IAudit command: Invalid archive delete value encountered for node node name.

Explanation: A database audit process encounters an invalid archive delete permission value for the node indicated.

System Action: Audit processing continues.

User Response: If FIX=YES has not been specified for the audit command, you may want to run this command again, and specify FIX=YES so that the audit process can correct the problem.

ANR4048IAudit command: Invalid archive delete value encountered for node node name the default value will be set.

Explanation: A database audit process encounters an invalid archive delete permission value for the node indicated. Because FIX=YES has been specified, the audit function sets the node's archive delete permission value to the default value.

System Action: Audit processing continues.

User Response: If you want the archive delete value for the specified node to be set to a value other than the default, use the UPDATE NODE command to change the value after the audit command has completed.

ANR4049IAudit command: Invalid backup delete value encountered for node node name.

Explanation: A database audit process encounters an invalid backup delete permission value for the node indicated.

System Action: Audit processing continues.

User Response: If FIX=YES has not been specified for the audit command, you may want to run this command again, and specify FIX=YES so that the audit process can correct the problem.

ANR4050IAudit command: Invalid backup delete value encountered for node node name the default value will be set.

Explanation: A database audit process encounters an invalid backup delete permission value for the node indicated. Because FIX=YES has been specified, the audit function sets the node's backup delete permission value to the default value.

System Action: Audit processing continues.

User Response: If you want the backup delete value for the specified node to be set to a value other than the default, use the UPDATE NODE command to change the value after the audit command has completed.

ANR4051IAudit command: Invalid lock state encountered for node node name.

Explanation: A database audit process encounters an invalid lock state value for the node indicated.

System Action: Audit processing continues.

User Response: If FIX=YES has not been specified for the audit command, you may want to run this command again, and specify FIX=YES so that the audit process can correct the problem.

ANR4052IAudit command: Invalid lock state encountered for node node name the node will be unlocked.

Explanation: A database audit process encounters an invalid lock state value for the node indicated. Because FIX=YES has been specified, the audit function sets the node's lock state to unlocked.

System Action: Audit processing continues.

User Response: If you want the lock state for the specified node to be set to a value other than unlocked, use the LOCK NODE command to change the value after the audit command has completed.

ANR4053IAudit command: Invalid Node conversion state encountered for node node name.

Explanation: A database audit process encounters an invalid Node conversion state value for the node indicated.

System Action: Audit processing continues.

User Response: If FIX=YES has not been specified for the audit command, you may want to run this command again, and specify FIX=YES so that the audit process can correct the problem. However, next time this node logs onto the server, the node conversion state will be reset.

ANR4054IAudit command: Invalid Node conversion state encountered for node node name the node will be set as an ADSM Version 2 node.

Explanation: A database audit process encounters an invalid Node conversion state value for the node indicated. Because FIX=YES has been specified, the audit function sets the node as an ADSM version 2 node.

System Action: Audit processing continues.

User Response: The specified node must use the ADSM Version 2 client program to access the server after the audit completes.

ANR4055IAudit command: Invalid lock state encountered for administrator administrator name.

Explanation: A database audit process encounters an invalid lock state value for the administrator indicated.

System Action: Audit processing continues.

User Response: If FIX=YES has not been specified for the audit command, you may want to run this command again, and specify FIX=YES so that the audit process can correct the problem.

ANR4056IAudit command: Invalid lock state encountered for administrator administrator name the administrator will be unlocked.

Explanation: A database audit process encounters an invalid lock state value for the administrator indicated. Because FIX=YES has been specified, the audit function sets the administrator's lock state to unlocked.

System Action: Audit processing continues.

User Response: If you want the lock state for the specified administrator to be set to a value other than unlocked, use the LOCK ADMIN command to change the value after the audit command has completed.

ANR4057EAudit command: Administrative global attributes are missing.

Explanation: A database audit process finds that the global attributes used for server administrative activities are missing.

System Action: Audit processing continues.

User Response: Reissue the audit command with FIX=YES specified so that the administrative global attributes can be recreated.

ANR4058IAudit command: Administrative global attributes are missing - default values will be used to recreate the attributes.

Explanation: A database audit process finds that the global attributes used for server administrative activities are missing. Because FIX=YES has been specified on the AUDIT command, default attribute values will be used to recreate the administrative global attributes.

System Action: Audit processing continues.

User Response: When the audit completes, you can use the QUERY STATUS command to examine the values set for the administrative global attributes, and use the appropriate SET command to change the attributes, if desired.

ANR4059EAudit command: Administrative ID assignments are incorrect.

Explanation: A database audit process finds that the global attributes used for server administrative activities are incorrect.

System Action: Audit processing continues.

User Response: Reissue the audit command with FIX=YES specified so that the administrative global attributes can be corrected.

ANR4060IAudit command: Administrative ID assignments are incorrect - value(s) will be corrected.

Explanation: A database audit process finds that the global attributes used for server administrative activities are incorrect. Because FIX=YES has been specified on the AUDIT command, the attribute value will be corrected in the server database.

System Action: Audit processing continues.

User Response: None.

ANR4061EAudit command: Administrative global attribute(s) are incorrect.

Explanation: A database audit process finds that the global attributes used for server administrative activities are incorrect.

System Action: Audit processing continues.

User Response: Reissue the audit command with FIX=YES specified so that the administrative global attributes can be corrected.

ANR4062IAudit command: Administrative global attribute(s) are incorrect - default values will be set.

Explanation: A database audit process finds that the global attributes used for server administrative activities are incorrect. Because FIX=YES has been specified on the AUDIT command, default attribute values will be used to correct the administrative global attributes.

System Action: Audit processing continues.

User Response: When the audit completes, you can use the QUERY STATUS command to examine the values set for the administrative global attributes, and use the appropriate SET command to change the attributes, if desired.

ANR4063EAudit command: Client node node number not found in the server database.

Explanation: A database audit process finds a client node reference that is not defined correctly in the server database.

System Action: Audit processing continues.

User Response: If the audit command has not been issued with FIX=YES specified, reissue the audit function specifying FIX=YES so that the error can be corrected.

ANR4064IAudit command: Client node node number created as node node name assigned to policy domain domain name in the server database.

Explanation: A database audit process finds a client node reference that is not defined correctly in the server database. Because FIX=YES has been specified for the audit command, the audit function creates a new node definition for the node with the name specified.

System Action: Audit processing continues.

User Response: After the AUDIT command completes, use the QUERY NODE command to examine the node that was added. Use the RENAME NODE command to rename the corrected node and the UPDATE NODE command to set attributes for the corrected node, such as its password. You can issue the QUERY FILESPACE command for the node, to determine which node and platform type was originally represented by the corrected node.

ANR4065EAudit command: Administrator administrator number not found in the server database.

Explanation: A database audit process finds an administrator reference that is not defined correctly in the server database.

System Action: Audit processing continues.

User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected.

ANR4066IAudit command: Administrator administrator number not found in the server database - reference will be removed.

Explanation: A database audit process finds an administrator reference that is not defined correctly in the server database. The invalid reference will be removed from the database.

System Action: Audit processing continues.

User Response: After the audit command completes, review your administrator definitions with the QUERY ADMIN command. You can then use the REGISTER ADMIN and UPDATE ADMIN commands to change any definitions desired.

ANR4067EAudit command: Domain domain name referenced by an administrator authority does not exist.

Explanation: A database audit process finds a policy administrator reference to a policy domain that does not exist.

System Action: Audit processing continues.

User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected.

ANR4068IAudit command: Policy domain domain name referenced by an administrator authority does not exist - the authority will be removed.

Explanation: A database audit process finds a policy administrator reference to a policy domain that does not exist. Because FIX=YES has been specified, the authority will be removed.

System Action: Audit processing continues.

User Response: After the audit command completes, review your administrator definitions with the QUERY ADMIN command. You can then use the REGISTER ADMIN, UPDATE ADMIN, and GRANT AUTHORITY commands to change any definitions.

ANR4069EAudit command: Storage pool storage pool name referenced by an administrator authority does not exist.

Explanation: A database audit process finds a storage administrator reference to a storage pool that does not exist.

System Action: Audit processing continues.

User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected.

ANR4070IAudit command: Storage pool storage pool name referenced by an administrator authority does not exist - the authority will be removed.

Explanation: A database audit process finds a policy administrator reference to a storage pool that does not exist. Because FIX=YES has been specified, the authority will be removed.

System Action: Audit processing continues.

User Response: After the audit command completes, review your administrator definitions with the QUERY ADMIN command. You can then use the REGISTER ADMIN, UPDATE ADMIN, and GRANT AUTHORITY commands to change any definitions.

ANR4071IAudit command: Invalid sign-on attempts is not valid for node/administrator name.

Explanation: A database audit process encounters an invalid sign-on attempts value that is not valid for the node or administrator indicated.

System Action: Audit processing continues.

User Response: If FIX=YES has not been specified for the audit command, you may want to run this command again, and specify FIX=YES so that the audit process can correct the problem.

ANR4072IAudit command: Invalid file aggregation information encountered for node node name.

Explanation: A database audit process encounters invalid information used for controlling aggregation of files for the node indicated.

System Action: Audit processing continues.

User Response: If FIX=YES has not been specified for the audit command, you may want to run this command again, and specify FIX=YES so that the audit process can correct the problem.

ANR4073IAudit command: Invalid file aggregation information encountered for node node name - information will be corrected.

Explanation: A database audit process encounters invalid information used for controlling aggregation of files for the node specified. Because FIX=YES has been specified, the audit function corrects the information.

System Action: Audit processing continues.

User Response: None.

ANR4075IAudit command: Auditing policy definitions.

Explanation: This message is displayed during a database audit and indicates that the server policy information (domain, policy set, management classes, and copy groups) are being examined by the database audit process.

System Action: Audit processing continues.

User Response: None.

ANR4076EAudit command: Invalid client node count detected for policy domain domain name.

Explanation: A database audit process finds that the count of nodes recorded for the specified policy domain do not match the actual number of nodes assigned to the domain.

System Action: Audit processing continues.

User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected.

ANR4077IAudit command: Invalid client node count detected for policy domain domain name count will be corrected.

Explanation: A database audit process finds that the count of nodes recorded for the specified policy domain do not match the actual number of nodes assigned to the domain. Because FIX=YES has been specified for the command, the node count will automatically be corrected.

System Action: Audit processing continues.

User Response: None.

ANR4078EAudit command: Invalid activation indicators encountered for policy domain domain name.

Explanation: A database audit process finds incorrect policy set activation entries for the specified policy domain.

System Action: Audit processing continues.

User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected.

ANR4079IAudit command: Invalid activation indicators encountered for policy domain domain name - entry will be corrected.

Explanation: A database audit process finds incorrect policy set activation entries for the specified policy domain. Because FIX=YES has been specified for the audit command, the entry will be corrected.

System Action: Audit processing continues.

User Response: None.

ANR4080EAudit command: Invalid grace period backup retention value encountered for policy domain domain name.

Explanation: A database audit process finds an incorrect grace period retention value for the specified policy domain.

System Action: Audit processing continues.

User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected.

ANR4081IAudit command: Invalid grace period backup retention value encountered for policy domain domain name - default value will be set.

Explanation: A database audit process finds an incorrect grace period retention value for the specified policy domain. Because FIX=YES has been specified for the audit command, the default value will be set.

System Action: Audit processing continues.

User Response: None.

ANR4082EAudit command: Invalid grace period archive retention value encountered for policy domain domain name.

Explanation: A database audit process finds an incorrect grace period retention value for the specified policy domain.

System Action: Audit processing continues.

User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected.

ANR4083IAudit command: Invalid grace period archive retention value encountered for policy domain domain name - default value will be set.

Explanation: A database audit process finds an incorrect grace period retention value for the specified policy domain. Because FIX=YES has been specified for the audit command, the default value will be set.

System Action: Audit processing continues.

User Response: None.

ANR4084EAudit command: Invalid administrator update information encountered for policy domain domain name.

Explanation: A database audit process finds incorrect last updated information for the specified policy domain.

System Action: Audit processing continues.

User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected.

ANR4085IAudit command: Invalid administrator update information encountered for policy domain domain name - information will be corrected.

Explanation: A database audit process finds incorrect last updated information for the specified policy domain. Because FIX=YES has been specified for the command, the information is corrected.

System Action: Audit processing continues.

User Response: None.

ANR4086EAudit command: Invalid node node number found assigned to domain domain name.

Explanation: A database audit process finds a node number assigned to a policy domain that does not reference a valid client node definition.

System Action: Audit processing continues.

User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected.

ANR4087IAudit command: Invalid node node number found assigned to domain domain name reference will be deleted.

Explanation: A database audit process finds a node number assigned to a policy domain that does not reference a valid client node definition. Because FIX=YES has been specified for the audit command, the reference will be deleted.

System Action: Audit processing continues.

User Response: None.

ANR4088EAudit command: Default management class management class name specified for policy set policy set name in domain domain name does not exist.

Explanation: A database audit process finds a policy set with a default management class specified that does not exist.

System Action: Audit processing continues.

User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected.

ANR4089IAudit command: Default management class management class name specified for policy set policy set name in domain domain name does not exist - the reference will be removed.

Explanation: A database audit process finds a policy set with a default management class specified that does not exist. Because FIX=YES has been specified for the audit command, the reference will be removed from the policy set.

System Action: Audit processing continues.

User Response: When the audit command completes, examine the policy set specified, and set a new default management class for the set. If the policy set is the ACTIVE policy set, you must activate a new policy set for the domain with a valid default management class.

ANR4090EAudit command: Active Policy set for domain domain name does not contain a valid default management class - policy will fail for this domain. Please correct the ACTIVE policy set.

Explanation: A database audit process finds an active policy set for the specified policy domain that does not have a valid active management class specified.

System Action: Audit processing continues.

User Response: When the audit command completes, you must activate a new policy set for the domain with a valid default management class.

ANR4091EAudit command: Invalid administrator update information encountered for policy set set name in policy domain domain name.

Explanation: A database audit process finds incorrect last updated information for the specified policy set.

System Action: Audit processing continues.

User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected.

ANR4092IAudit command: Invalid administrator update information encountered for policy set set name in policy domain domain name - information will be corrected.

Explanation: A database audit process finds incorrect last updated information for the specified policy set. Because FIX=YES has been specified for the command, the information is corrected.

System Action: Audit processing continues.

User Response: None.

ANR4093EAudit command: A management class identifier is not defined for management class management class name in policy set set name, domain domain name.

Explanation: A database audit process finds incorrect information for the specified management class.

System Action: Audit processing continues.

User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected.

ANR4094EAudit command: A management class identifier is not defined for management class management class name in policy set set name, domain domain name - an identifier will be generated for this management class.

Explanation: A database audit process finds incorrect information for the specified management class. The audit process generates an identifier, because FIX=YES has been specified for the audit command.

System Action: Audit processing continues.

User Response: None.

ANR4095EAudit command: An invalid management class identifier (actual identifier) was encountered for management class management class name in policy set set name, domain domain name (expected expected identifier).

Explanation: A database audit process finds incorrect information for the specified management class.

System Action: Audit processing continues.

User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected.

ANR4096EAudit command: An invalid management class identifier (actual identifier) was encountered for management class management class name in policy set set name, domain domain name (expected expected identifier) - the correct identifier will be stored.

Explanation: A database audit process finds incorrect information for the specified management class. The audit process corrects the identifier, because FIX=YES has been specified for the audit command.

System Action: Audit processing continues.

User Response: None.

ANR4097EAudit command: Invalid administrator update information encountered for management class management class name in policy set set name in policy domain domain name.

Explanation: A database audit process finds incorrect last updated information for the specified management class.

System Action: Audit processing continues.

User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected.

ANR4098IAudit command: Invalid administrator update information encountered for management class management class name in policy set set name in policy domain domain name - information will be corrected.

Explanation: A database audit process finds incorrect last updated information for the specified management class. Because FIX=YES has been specified for the command, the information is corrected.

System Action: Audit processing continues.

User Response: None.

ANR4099EAudit command: Copy group copy group name in management class management class name, policy set set name, domain domain name has an invalid name or type.

Explanation: A database audit process encounters a copy group that has an invalid name or copy group type.

System Action: Audit processing continues.

User Response: If FIX=YES has not been specified for the audit command, reissue the command specifying FIX=YES so that the error can be corrected.

ANR4100IAudit command: Attempting to reinsert the copy group as a BACKUP copy group.

Explanation: A database audit process encounters a copy group that has an invalid name or copy group type. The process attempts to reinsert the definition as a backup copy group.

System Action: Audit processing continues.

User Response: None.

ANR4101IAudit command: A backup copy group already exists - the invalid copy group will be deleted.

Explanation: A database audit process encounters a copy group that has an invalid name or copy group type. While attempting to reinsert the copy group as a backup copy group, the process discovers that a backup copy group already exists for the management class. The copy group is deleted.

System Action: Audit processing continues.

User Response: After the audit command completes, you may examine the server copy groups using the QUERY COPYGROUP command, and correct them with the DEFINE COPYGROUP and UPDATE COPYGROUP commands if desired.

ANR4102IAudit command: Attempting to reinsert the copy group as an ARCHIVE copy group.

Explanation: A database audit process encounters a copy group that has an invalid name or copy group type. The process attempts to reinsert the definition as an archive copy group.

System Action: Audit processing continues.

User Response: None.

ANR4103IAudit command: An archive copy group already exists - the invalid copy group will be deleted.

Explanation: A database audit process encounters a copy group that has an invalid name or copy group type. While attempting to reinsert the copy group as an archive copy group, the process discovers that a backup copy group already exists for the management class. The copy group is deleted.

System Action: Audit processing continues.

User Response: After the audit command completes, you may examine the server copy groups using the QUERY COPYGROUP command, and correct them with the DEFINE COPYGROUP and UPDATE COPYGROUP commands, if desired.

ANR4104EAudit command: An invalid management class identifier (actual identifier) was encountered for a copy group in management class management class name, policy set set name, domain domain name (expected expected identifier).

Explanation: A database audit process finds incorrect information for the specified copy group.

System Action: Audit processing continues.

User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected.

ANR4105EAudit command: An invalid management class identifier (actual identifier) was encountered for a copy group in management class management class name, policy set set name, domain domain name (expected expected identifier) - the correct identifier will be stored.

Explanation: A database audit process finds incorrect information for the specified copy group. The audit process corrects the identifier, since FIX=YES has been specified for the audit command.

System Action: Audit processing continues.

User Response: None.

ANR4106EAudit command: An invalid copy group identifier (actual identifier) was encountered for a copy group in management class management class name, policy set set name, domain domain name (expected expected identifier).

Explanation: A database audit process finds incorrect information for the specified copy group.

System Action: Audit processing continues.

User Response: For programming support, contact your service representative.

ANR4107EAudit command: An invalid copy group identifier (actual identifier) was encountered for copy group name copy group name (expected expected identifier).

Explanation: A database audit process finds incorrect information for the specified copy group name.

System Action: Audit processing continues.

User Response: For programming support, contact your service representative.

ANR4108EAudit command: Invalid backup copy group attributes encountered for copy group copy group name in management class management class name, policy set set name, domain domain name.

Explanation: A database audit process encounters invalid backup copy group attributes for the specified copy group.

System Action: Audit processing continues.

User Response: If FIX=YES has not been specified for the audit command, reissue the command specifying FIX=YES so that the inconsistency can be corrected.

ANR4109IAudit command: Invalid backup copy group attributes encountered for copy group copy group name in management class management class name, policy set set name, domain domain name - the copy group will be corrected using default attributes.

Explanation: A database audit process encounters invalid backup copy group attributes for the specified copy group. Because FIX=YES has been specified for the command, the copy group will be corrected using default values for the attributes found in error.

System Action: Audit processing continues.

User Response: After the audit command completes, examine the copy group by using the QUERY COPYGROUP command, and correct attributes with the UPDATE COPYGROUP command, if desired.

ANR4110EAudit command: Invalid archive copy group attributes encountered for copy group copy group name in management class management class name, policy set set name, domain domain name.

Explanation: A database audit process encounters invalid archive copy group attributes for the specified copy group.

System Action: Audit processing continues.

User Response: If FIX=YES has not been specified for the audit command, reissue the command and specify FIX=YES so that the inconsistency can be corrected.

ANR4111IAudit command: Invalid archive copy group attributes encountered for copy group copy group name in management class management class name, policy set set name, domain domain name - the copy group will be corrected using default attributes.

Explanation: A database audit process encounters invalid archive copy group attributes for the specified copy group. Because FIX=YES has been specified for the command, the copy group will be corrected using default values for the attributes found in error.

System Action: Audit processing continues.

User Response: After the audit command completes, examine the copy group by using the QUERY COPYGROUP command, and correct the attributes with the UPDATE COPYGROUP command, if desired.

ANR4112WAudit command: Storage pool storage pool name, specified as a destination for copy group copy group name in management class management class name, policy set set name, domain domain name, does not exists.

Explanation: A database audit process encounters a storage pool specified for the destination of the specified copy group that is not defined in the server database. If this copy group is used in an active policy set, then backup or archive operations will fail when attempting to put client data in the destination.

System Action: Audit processing continues.

User Response: After the audit command completes, use the DEFINE STGPOOL command to define the missing storage pool or the UPDATE COPYGROUP command to update the copy group to refer to an existing storage pool.

ANR4113EAudit command: Invalid administrator update information encountered for copy group copy group name in management class management class name, policy set set name, policy domain domain name.

Explanation: A database audit process finds incorrect last updated information for the specified copy group.

System Action: Audit processing continues.

User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected.

ANR4114IAudit command: Invalid administrator update information encountered for copy group copy group name in management class management class name, policy set set name, policy domain domain name - information will be corrected.

Explanation: A database audit process finds incorrect last updated information for the specified copy group. Because FIX=YES has been specified for the command, the information is corrected.

System Action: Audit processing continues.

User Response: None.

ANR4115EAudit command: Policy domain domain name is referenced, but not formally defined.

Explanation: A database audit process finds a reference to the specified policy domain, but the domain is not formally defined in the server database.

System Action: Audit processing continues.

User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected.

ANR4116IAudit command: Policy domain domain name is referenced, but not formally defined - a policy domain with default attributes will be defined with this name.

Explanation: A database audit process finds a reference to the specified policy domain, but the domain is not formally defined in the server database. Because FIX=YES has been specified, a new policy domain with this name will be defined by the audit processor.

System Action: Audit processing continues.

User Response: After the audit command has completed, you can view the attributes for this policy domain using the QUERY DOMAIN command, and update attributes with the UPDATE DOMAIN command, if desired.

ANR4117EAudit command: Policy set set name in domain domain name is referenced, but not formally defined.

Explanation: A database audit process finds a reference to the specified policy set, but the set is not formally defined in the server database.

System Action: Audit processing continues.

User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected.

ANR4118IAudit command: Policy set set name in domain domain name is referenced, but not formally defined - a policy set with this name will be created.

Explanation: A database audit process finds a reference to the specified policy set, but the set is not formally defined in the server database. Because FIX=YES has been specified, the audit process will create a new policy set with this name.

System Action: Audit processing continues.

User Response: After the audit command has completed, you can view the attributes for this policy set by using the QUERY POLICYSET command, and update attributes with the UPDATE POLICYSET command, if desired.

ANR4119EAudit command: Management class class name in policy set set name, domain domain name is referenced, but not formally defined.

Explanation: A database audit process finds a reference to the specified management class, but the class is not formally defined in the server database.

System Action: Audit processing continues.

User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected.

ANR4120IAudit command: Management class class name in policy set set name, domain domain name is referenced, but not formally defined - the management class will be created.

Explanation: A database audit process finds a reference to the specified management class, but the class is not formally defined in the server database. Because FIX=YES has been specified for the audit command, the audit process defines a management class in the server with this name.

System Action: Audit processing continues.

User Response: After the audit command has completed, you can view the attributes for this management class by using the QUERY MGMTCLASS command, and update attributes with the UPDATE MGMTCLASS command, if desired.

ANR4122EAudit command: The instance count for management class class name does not agree with the actual management class data (number of instances instances).

Explanation: A database audit process finds a reference count for the specified management class that did not match the actual number of instances for this class.

System Action: Audit processing continues.

User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected.

ANR4123IAudit command: The instance count for management class class name does not agree with the actual management class data (number of instances instances) - the number will be corrected.

Explanation: A database audit process finds a reference count for the specified management class that does not match the actual number of instances for this class. The audit process corrects the count because FIX=YES has been specified for the audit command.

System Action: Audit processing continues.

User Response: None.

ANR4124EAudit command: The instance count for copy group copy group name does not agree with the actual copy group data (number of instances instances).

Explanation: A database audit process finds a reference count for the specified copy group that does not match the actual number of instances for this copy group.

System Action: Audit processing continues.

User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected.

ANR4125IAudit command: The instance count for copy group copy group name does not agree with the actual copy group data (number of instances instances) - the number will be corrected.

Explanation: A database audit process finds a reference count for the specified copy group that does not match the actual number of instances for this copy group. The audit process corrects the count because FIX=YES has been specified for the audit command.

System Action: Audit processing continues.

User Response: None.

ANR4126EAudit command: Policy global attributes cannot be found.

Explanation: A database audit process is not able to locate the global attributes for policy information in the server database.

System Action: Audit processing continues.

User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected.

ANR4127IAudit command: Policy global attributes cannot be found - attributes will recreated.

Explanation: A database audit process is not able to locate the global attributes for policy information in the server database. Because FIX=YES has been specified for the audit command, the attributes will be regenerated.

System Action: Audit processing continues.

User Response: None.

ANR4128EAudit command: Policy global high-water marks do not match the identifiers in use.

Explanation: A database audit process finds the attributes used to track policy identifiers are incorrect.

System Action: Audit processing continues.

User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected.

ANR4129EAudit command: Policy global high-water marks do not match the identifiers in use - they will be corrected.

Explanation: A database audit process finds the attributes used to track policy identifiers are incorrect. Because FIX=YES has been specified for the audit command, the attributes will be corrected.

System Action: Audit processing continues.

User Response: None.

ANR4130WAudit Volume updating object information for volume volume name: Node node name, Type file type, File space filespace name, File Name file name.

Explanation: As the result of an AUDIT VOLUME command that specified FIX=YES for the volume shown, object information for the specified file will be updated.

System Action: The object information is updated.

User Response: None.

ANR4131WAudit Volume found incorrect object information for volume volume name: Node node name, Type file type, File space filespace name, File name file name.

Explanation: As the result of an AUDIT VOLUME command that specified FIX=NO for the volume shown, object information for the specified file is found to be in error.

System Action: None.

User Response: None.

ANR4132IAudit volume process ended for volume volume name; file count files inspected, file count damaged files deleted, file count damaged files marked as damaged, file count objects updated.

Explanation: The AUDIT VOLUME command specifying FIX=YES for the volume shown has ended. The number of files audited, the number of inconsistent files deleted or marked as damaged, and the number of updated objects are displayed. The number of files marked as damaged includes all files belonging to aggregates that were marked damaged during the audit. Files are marked as damaged in primary storage pools and not deleted when backup copies for the files are known to exist in COPY storage pools.

System Action: None.

User Response: To recover files that have been marked as damaged on the volume, use the RESTORE STGPOOL or RESTORE volume command.

ANR4133IAudit volume process ended for volume volume name; file count files inspected, file count damaged files found and marked as damaged, file count objects need updating.

Explanation: The AUDIT VOLUME command specifying FIX=NO for the volume shown has ended. The number of files audited, the number of inconsistent files found, and the number of files with incorrect object information are displayed. The number of files marked damaged includes all files belonging to aggregates that were marked damaged during the audit. Inconsistent files are marked as damaged in the database and can be recovered by using the RESTORE STGPOOL or RESTORE VOLUME command if copies of the files reside in a COPY storage pool. Another AUDIT VOLUME command may be able to access the files and reset the damaged indicator in the database if the audit volume process cannot access the files due to hardware problems (for example, dirty tape heads).

System Action: None.

User Response: If you suspect that files were inaccessible because of hardware problems such as dirty tape heads, correct the hardware problem and reissue the AUDIT VOLUME FIX=NO command for this volume. To remove damaged file references and update the object information, issue the AUDIT VOLUME command and specify FIX=YES.

ANR4135IAudit command: Auditing central scheduler definitions.

Explanation: This message is displayed during a database audit and indicates that the server scheduling information is examined by the database audit process.

System Action: Audit processing continues.

User Response: None.

ANR4136IAudit command: Auditing server inventory.

Explanation: This message is displayed during a database audit and indicates that server information about client file spaces is currently being examined by the database audit process.

System Action: Audit processing continues.

User Response: None.

ANR4137IAudit command: Auditing inventory file spaces.

Explanation: This message is displayed during a database audit and indicates that server information about client file spaces is currently being examined by the database audit process.

System Action: Audit processing continues.

User Response: None.

ANR4138IAudit command: Auditing inventory backup objects.

Explanation: This message is displayed during a database audit and indicates that server information about client backup objects is currently being examined by the database audit process.

System Action: Audit processing continues.

User Response: None.

ANR4139IAudit command: Auditing inventory archive objects.

Explanation: This message is displayed during a database audit and indicates that server information about client archive objects is currently being examined by the database audit process.

System Action: Audit processing continues.

User Response: None.

ANR4140IAudit command: Database audit process started.

Explanation: This message is displayed during a database audit and indicates that the audit process has started.

System Action: Audit processing continues.

User Response: None.

ANR4141IAudit command: Database audit process completed.

Explanation: This message is displayed during a database audit and indicates that the database audit has successfully completed.

System Action: Audit processing ends.

User Response: None.

ANR4142IAudit command: Database audit process terminated in error.

Explanation: This message is displayed during a database audit and indicates that the audit process ended prematurely due to an internal server database error.

System Action: Audit processing ends.

User Response: Examine the messages issued prior to this one to see if the error can be corrected. If the situation cannot be resolved, contact your service representative.

ANR4143EAudit command: Central scheduler global attributes cannot be found.

Explanation: A database audit process cannot locate the global attributes for scheduling information in the server database.

System Action: Audit processing continues.

User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected.

ANR4144IAudit command: Central scheduler global attributes cannot be found - attributes will be recreated.

Explanation: A database audit process cannot locate the global attributes for scheduler information in the server database. Because FIX=YES has been specified for the audit command, the attributes will be regenerated.

System Action: Audit processing continues.

User Response: None.

ANR4145EAudit command: One or more central scheduler attributes are incorrect.

Explanation: A database audit process finds that the global attributes used for server scheduling activities are incorrect.

System Action: Audit processing continues.

User Response: Reissue the audit command and specify FIX=YES so that the administrative global attributes can be corrected.

ANR4146IAudit command: One or more central scheduler global attribute(s) are incorrect - default values will be set.

Explanation: A database audit process finds that the global attributes used for server scheduling activities are incorrect. Because FIX=YES has been specified on the AUDIT command, default attribute values will be used to correct the scheduling global attributes.

System Action: Audit processing continues.

User Response: When the audit completes, you can use the QUERY STATUS command to examine the values set for the administrative global attributes, and use the appropriate SET command to change the attributes, if desired.

ANR4147EAudit command: Policy domain domain name referenced by schedule schedule name does not exist.

Explanation: A database audit process finds a schedule that references a policy domain that is not defined in the server database.

System Action: Audit processing continues.

User Response: Reissue the audit command and specify FIX=YES so that the administrative global attributes can be corrected.

ANR4148IAudit command: Policy domain domain name referenced by schedule schedule name does not exist - the schedule will be deleted.

Explanation: A database audit process finds a schedule that references a policy domain that is not defined in the server database. Because FIX=YES has been specified for the audit command, the specified schedule will be deleted from the server database.

System Action: Audit processing continues.

User Response: None.

ANR4149EAudit command: One or more attributes for schedule schedule name in policy domain domain name are incorrect.

Explanation: A database audit process finds one or more invalid attributes for the specified schedule.

System Action: Audit processing continues.

User Response: Reissue the audit command and specify FIX=YES so that the administrative global attributes can be corrected.

ANR4150IAudit command: One or more attributes for schedule schedule name in policy domain domain name are incorrect - default values will be set.

Explanation: A database audit process finds one or more invalid attributes for the specified schedule. Because FIX=YES has been specified for the audit command the invalid attributes will be set to default values.

System Action: Audit processing continues.

User Response: When the audit completes, you can use the QUERY SCHEDULE command to examine the values set for the schedule, and use the UPDATE SCHEDULE command to change any attributes desired.

ANR4151EAudit command: Schedule schedule name in policy domain domain name not found, but is referenced by a client node.

Explanation: A database audit process finds a schedule reference from a client node for a schedule that is not defined in the server database.

System Action: Audit processing continues.

User Response: Reissue the audit command and specify FIX=YES so that the administrative global attributes can be corrected.

ANR4152IAudit command: Schedule schedule name in policy domain domain name not found, but is referenced by a client node - the schedule association will be deleted.

Explanation: A database audit process finds a schedule reference from a client node for a schedule that is not defined in the server database. Because FIX=YES has been specified for the audit command, the schedule association will be deleted from the server database.

System Action: Audit processing continues.

User Response: None.

ANR4153EAudit command: Schedule schedule name in policy domain domain name references a client node that does not exist.

Explanation: A database audit process finds a schedule that references a client node that is not defined in the server database.

System Action: Audit processing continues.

User Response: Reissue the audit command and specify FIX=YES so that the administrative global attributes can be corrected.

ANR4154IAudit command: Schedule schedule name in policy domain domain name references a client node that does not exist - the node reference will be deleted.

Explanation: A database audit process finds a schedule that references a client node that is not defined in the server database. Because FIX=YES has been specified for the audit command, the reference will be removed from the server database.

System Action: Audit processing continues.

User Response: None.

ANR4155EAudit command: Invalid administrator update information encountered for a schedule assignment.

Explanation: A database audit process finds incorrect last updated information for a schedule-node assignment.

System Action: Audit processing continues.

User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected.

ANR4156IAudit command: Invalid administrator update information encountered for a schedule assignment - information will be corrected.

Explanation: A database audit process finds incorrect last updated information for a schedule-node assignment. Because FIX=YES has been specified for the command, the information is corrected.

System Action: Audit processing continues.

User Response: None.

ANR4157EAudit command: Scheduling callback address is registered for a client node that does not exist.

Explanation: A database audit process finds a server-prompted-scheduling callback address for a node that does not exist.

System Action: Audit processing continues.

User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected.

ANR4158IAudit command: Scheduling callback address is registered for a client node that does not exist - callback information will be deleted.

Explanation: A database audit process finds a server-prompted-scheduling callback address for a node that does not exist. Because FIX=YES has been specified for the command, the callback information will be deleted from the server database.

System Action: Audit processing continues.

User Response: None.

ANR4159IAudit command: An inventory authorization rule specifies an invalid node (node ID) or file space (filespace ID) - the rule will be deleted.

Explanation: A database audit process finds that either a node ID or file space ID is invalid for an authorization rule. Since FIX=YES has been specified, the invalid authorization rule will be deleted.

System Action: Audit processing continues.

User Response: None.

ANR4160IAudit command: An inventory authorization rule specifies an invalid node (node ID) or file space (filespace ID).

Explanation: A database audit process finds that either a node ID or file space ID is invalid for an authorization rule.

System Action: Audit processing continues.

User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected.

ANR4161IAudit command: Inventory global attributes could not be found - they will be created.

Explanation: A database audit process cannot find the inventory global attributes. Because FIX=YES has been specified for the command, the information is corrected by the creation of the global attributes.

System Action: Audit processing continues.

User Response: None.

ANR4162IAudit command: Inventory global attributes could not be found.

Explanation: A database audit process cannot find the inventory global attributes.

System Action: Audit processing continues.

User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected.

ANR4163IAudit command: Invalid object ID high-water mark encountered for inventory global attributes - the value will be corrected.

Explanation: A database audit process finds that the object ID high-water mark for the inventory global attributes is invalid. Because FIX=YES has been specified for the command, the object ID high-water mark is determined by the current inventory and set accordingly.

System Action: Audit processing continues.

User Response: None.

ANR4164IAudit command: Invalid object ID high-water mark encountered for inventory global attributes.

Explanation: A database audit process finds that the object ID high-water mark for the inventory global attributes is invalid.

System Action: Audit processing continues.

User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected.

ANR4165IAudit command: An inventory node assignment entry was not found for node node ID - an entry will be created.

Explanation: A database audit process cannot find the node assignment entry corresponding to the specified node. Since FIX=YES has been specified for the command, the required inventory entry will be created using default values.

System Action: Audit processing continues.

User Response: None.

ANR4166IAudit command: An inventory node assignment entry was not found for node node ID.

Explanation: A database audit process cannot find the node assignment entry corresponding to the specified node.

System Action: Audit processing continues.

User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected.

ANR4167IAudit command: The file space high-water mark for node node ID is incorrect - the value will be corrected.

Explanation: A database audit process finds that a file space high-water mark is incorrect for the specified node ID. Since FIX=YES has been specified for the command, the information is corrected.

System Action: Audit processing continues.

User Response: None.

ANR4168IAudit command: The file space high-water mark for node node ID is incorrect.

Explanation: A database audit process finds that a file space high-water mark is incorrect for the specified node ID.

System Action: Audit processing continues.

User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected.

ANR4169IAudit command: The file space high-water mark for node node ID is incorrect - the value will be corrected.

Explanation: A database audit process finds that an authorization rule high-water mark is incorrect for the specified node ID. Since FIX=YES has been specified for the command, the information is corrected.

System Action: Audit processing continues.

User Response: None.

ANR4170IAudit command: The authorization rule high-water mark for node node ID is incorrect.

Explanation: A database audit process finds that an authorization rule high-water mark is incorrect for the specified node ID.

System Action: Audit processing continues.

User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected.

ANR4171IAudit command: Primary backup entry for an expiring object (object.ID) cannot be found - the expiring object entry will be deleted.

Explanation: A database audit process cannot find the primary backup entry for the specified expiring object. Because FIX=YES has been specified for the command, the information is corrected by deleting the expiring object entry.

System Action: Audit processing continues.

User Response: None.

ANR4172IAudit command: Primary backup entry for an expiring object (object.ID) cannot be found.

Explanation: A database audit process cannot find the primary backup entry for the specified expiring object.

System Action: Audit processing continues.

User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected.

ANR4173IAudit command: Primary archive entry for an expiring object (object.ID) cannot be found - the expiring object entry will be deleted.

Explanation: A database audit process cannot find the primary archive entry for the specified expiring object. Because FIX=YES has been specified for the command, the information is corrected by deleting the expiring object entry.

System Action: Audit processing continues.

User Response: None.

ANR4174IAudit command: Primary archive entry for an expiring object (object.ID) cannot be found.

Explanation: A database audit process cannot find the primary archive entry for the specified expiring object.

System Action: Audit processing continues.

User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected.

ANR4175IAudit command: Invalid copy type encountered for an expiring objects entry (object.ID) - the expiring object entry will be deleted.

Explanation: A database audit process finds that the copy type for the specified expiring object is invalid. Because FIX=YES has been specified for the command, the information is corrected by deleting the expiring object entry. The entry will be recreated later if it is necessary.

System Action: Audit processing continues.

User Response: None.

ANR4176IAudit command: Invalid copy type encountered for an expiring objects entry (object.ID).

Explanation: A database audit process finds that the copy type for the specified expiring object is invalid.

System Action: Audit processing continues.

User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected.

ANR4177IAudit command: Primary backup entry for an object (object.ID) cannot be found - entry will be deleted.

Explanation: A database audit process cannot find the specified primary backup object. Because FIX=YES has been specified for the command, the entry is deleted.

System Action: Audit processing continues.

User Response: None.

ANR4178IAudit command: Primary backup entry for an object (object.ID) cannot be found.

Explanation: A database audit process cannot find the specified primary backup object.

System Action: Audit processing continues.

User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected.

ANR4179IAudit command: Primary archive entry for an object (object.ID) cannot be found - entry will be deleted.

Explanation: A database audit process cannot find the specified primary archive object. Because FIX=YES has been specified for the command, the entry is deleted.

System Action: Audit processing continues.

User Response: None.

ANR4180IAudit command: Primary archive entry for an object (object.ID) cannot be found.

Explanation: A database audit process cannot find the specified primary archive object.

System Action: Audit processing continues.

User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected.

ANR4181IAudit command: Invalid copy type encountered for object object.ID - object found as a backup object - correcting the invalid copy type

Explanation: A database audit process encounters an invalid copy type for the specified object ID but finds a corresponding backup object for the entry. Because FIX=YES has been specified for the command, the invalid copy type is corrected.

System Action: Audit processing continues.

User Response: None.

ANR4182IAudit command: Invalid copy type encountered for object object.ID - object found as an archive object - correcting the invalid copy type

Explanation: A database audit process encounters an invalid copy type for the specified object ID but finds a corresponding archive object for the entry. Because FIX=YES has been specified for the command, the invalid copy type is corrected.

System Action: Audit processing continues.

User Response: None.

ANR4183IAudit command: Invalid copy type encountered for object object.ID - primary archive entry created for object using default values.

Explanation: A database audit process encounters an invalid copy type for the specified object ID and is unable to find corresponding primary backup or primary archive objects. Because FIX=YES has been specified for the command, a primary archive entry is created using default values.

System Action: Audit processing continues.

User Response: None.

ANR4184IAudit command: Invalid copy type encountered for object object.ID.

Explanation: A database audit process encounters an invalid copy type for the specified object ID and is unable to find corresponding primary backup or primary archive objects.

System Action: Audit processing continues.

User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected.

ANR4185IAudit command: Object entry for backup object object.ID not found - entry will be created.

Explanation: A database audit process cannot find an object entry for the specified backup object. Because FIX=YES has been specified for the command, an object entry is created using default values.

System Action: Audit processing continues.

User Response: None.

ANR4186IAudit command: Object entry for backup object object.ID not found.

Explanation: A database audit process cannot find an object entry for the specified backup object.

System Action: Audit processing continues.

User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected.

ANR4187IAudit command: Inventory object fields for object object.ID do not match the primary backup entry - the object will be updated.

Explanation: A database audit process determines that the object fields for the specified object ID do not match the fields for the corresponding primary backup object. Because FIX=YES has specified for the command, the incorrect object fields will be corrected.

System Action: Audit processing continues.

User Response: None.

ANR4188IAudit command: Inventory object fields for object object.ID do not match the primary backup entry.

Explanation: A database audit process determines that the object fields for the specified object ID do not match the fields for the corresponding primary backup object.

System Action: Audit processing continues.

User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected.

ANR4189IAudit command: Expiring entry for inactive backup object object.ID not found - the entry will be created.

Explanation: A database audit process cannot find an expiring entry for the specified inactive backup entry. Because FIX=YES has been specified for the command, an expiring entry will be created.

System Action: Audit processing continues.

User Response: None.

ANR4190IAudit command: Expiring entry for inactive backup object object.ID not found.

Explanation: A database audit process cannot find an expiring entry for the specified inactive backup entry.

System Action: Audit processing continues.

User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected.

ANR4191IAudit command: Object entry for archive object object.ID not found - entry will be created.

Explanation: A database audit process cannot find an object entry for the specified archive object. Because FIX=YES has been specified for the command, the information is corrected by creating an object entry.

System Action: Audit processing continues.

User Response: None.

ANR4192IAudit command: Object entry for archive object object.ID not found.

Explanation: A database audit process cannot find an object entry for the specified archive object.

System Action: Audit processing continues.

User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected.

ANR4193IAudit command: Inventory object fields for object object.ID do not match the primary archive entry - the object will be updated.

Explanation: A database audit process determines that the object fields for the specified object ID do not match the fields for the corresponding primary archive object. Because FIX=YES has been specified for the command, the incorrect object fields will be corrected.

System Action: Audit processing continues.

User Response: None.

ANR4194IAudit command: Inventory object fields for object object.ID do not match the primary archive entry.

Explanation: A database audit process determines that the object fields for the specified object ID do not match the fields for the corresponding primary archive object.

System Action: Audit processing continues.

User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected.

ANR4195IAudit command: Expiring entry for archive object object.ID not found - the entry will be created.

Explanation: A database audit process cannot find an expiring entry for the specified archive object. Because FIX=YES has been specified for the command, an expiring entry will be created.

System Action: Audit processing continues.

User Response: None.

ANR4196IAudit command: Expiring entry for archive object object.ID not found.

Explanation: A database audit process cannot find an expiring entry for the specified archive object.

System Action: Audit processing continues.

User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected.

ANR4197IAudit command: File space entry filespace ID not found for node node ID.

Explanation: A database audit process cannot find a file space entry for the specified node.

System Action: Audit processing continues.

User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected.

ANR4198IAudit command: File space entry filespace ID not found for node node name - an entry will be created.

Explanation: A database audit process cannot find a file space entry for the specified node. Because FIX=YES has been specified for the command, a file space entry has been created.

System Action: Audit processing continues.

User Response: None.

ANR4199IAudit command: File space entry filespace ID not found for node node name - unable to create an entry.

Explanation: A database audit process cannot find a file space entry for the specified node. Because FIX=YES has been specified for the command, the audit process has attempted to create a file space entry but is not successful.

System Action: Audit processing continues.

User Response: Contact your system administrator.

ANR4200IAudit command: Expiring entry node ID and file space filespace ID does not match the object entry for object ID object.ID - the entry will be deleted.

Explanation: A database audit process determines that the specified expiring object entry does not match the corresponding object entry for the specified object ID. Because FIX=YES has been specified for the command, the expiring object entry is deleted.

System Action: Audit processing continues.

User Response: None.

ANR4201IAudit command: Expiring entry node ID and file space filespace ID does not match the object entry for object ID object.ID.

Explanation: A database audit process determines that the specified expiring object entry does not match the corresponding object entry for the specified object ID.

System Action: Audit processing continues.

User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected.

ANR4202IAudit command: The base date for expiration processing of entry object.ID is not valid - the entry will be deleted.

Explanation: A database audit process determines that the specified expiring object has a date that is not valid. Because FIX=YES has been specified for the command, the expiring object entry is deleted.

System Action: Audit processing continues.

User Response: None.

ANR4203IAudit command: The base date for expiration processing of object object.ID is not valid.

Explanation: A database audit process determines that the specified expiring object has a date value that is not valid.

System Action: Audit processing continues.

User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected.

ANR4204IAudit command: One or more date values for a backup entry object.ID is not valid.

Explanation: A database audit process determines that one or more of the date values is improperly formatted or contains incorrect information for the specified backup object.

System Action: Audit processing continues.

User Response: Contact your system administrator.

ANR4205IAudit command: The insertion date value for archive entry object.ID is not valid.

Explanation: A database audit process determines that the insertion date for the specified archive object is improperly formatted or contains incorrect information.

System Action: Audit processing continues.

User Response: Contact your system administrator.

ANR4206IAudit command: Object entry for expiring object object.ID not found - expiring object entry will be deleted.

Explanation: A database audit process cannot find an object entry corresponding to the specified expiring object. Because FIX=YES has been specified for the command, the expiring object entry for the specified object ID is deleted.

System Action: Audit processing continues.

User Response: None.

ANR4207IAudit command: Object entry for expiring object object.ID not found.

Explanation: A database audit process cannot find an object entry corresponding to the specified expiring object.

System Action: Audit processing continues.

User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected.

ANR4208IAudit command: An inventory node assignment entry is not valid for node node ID - the entry will be deleted.

Explanation: A database audit process finds that a node assignment entry for the specified node ID is not valid. Since FIX=YES has been specified for the command, the required inventory entry is deleted.

System Action: Audit processing continues.

User Response: None.

ANR4209IAudit command: An inventory node assignment entry was not found for node node ID.

Explanation: A database audit process finds that a node assignment entry for the specified node ID is not valid.

System Action: Audit processing continues.

User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected.

ANR4210IAudit command: Auditing physical volume repository definitions.

Explanation: This message is displayed during a database audit and indicates that the physical volume repository definitions are being examined by the database audit process.

System Action: Audit processing continues.

User Response: None.

ANR4211IAudit command: Drive entry library name for library drive name in the physical volume repository is invalid.

Explanation: A database audit process finds that a drive entry is missing a corresponding library entry.

System Action: Audit processing continues.

User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected.

ANR4212IAudit command: An object entry for library library name and drive drive name in the physical volume repository is invalid - the entry will be deleted.

Explanation: A database audit process finds that a drive entry is missing a corresponding library entry. Because FIX=YES has been specified for the command, the invalid drive entry is deleted.

System Action: Audit processing continues.

User Response: None.

ANR4213IAudit command: A device type for library library name and drive drive name in the physical volume repository is invalid.

Explanation: A database audit process finds that a device type for the specified library and drive is invalid.

System Action: Audit processing continues.

User Response: Contact the system administrator so that appropriate action may be taken.

ANR4214IAudit command: A drive model for library library name and drive drive name in the physical volume repository is invalid.

Explanation: A database audit process finds that the drive model for the specified library and drive is invalid.

System Action: Audit processing continues.

User Response: Contact the system administrator so that appropriate action may be taken.

ANR4215IAudit command: An object entry for library library name and volume volume name in the physical volume repository is invalid.

Explanation: A database audit process finds that a library inventory entry is missing a corresponding library entry.

System Action: Audit processing continues.

User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected.

ANR4216IAudit command: An object entry for library library name and volume volume name in the physical volume repository is invalid - the entry will be deleted.

Explanation: A database audit process finds that a library inventory entry is missing a corresponding library entry. Because FIX=YES has been specified for the command, the invalid library inventory entry is deleted.

System Action: Audit processing continues.

User Response: None.

ANR4217IAudit command: The volume status for library library name and volume volume name in the physical volume repository is invalid.

Explanation: A database audit process finds that the volume status for the specified library and volume is set to scratch. This is incorrect because storage services has a volume name for the library and volume indicating that it should have a volume status of private.

System Action: Audit processing continues.

User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected.

ANR4218IAudit command: The volume status for library library name and volume volume name in the physical volume repository is invalid - the volume status will be changed to private.

Explanation: A database audit process finds that the volume status for the specified library and volume is set to scratch. This is incorrect because storage services has a volume name for the library and volume which indicates that it should have a volume status of private. Because FIX=YES has been specified for the command, the incorrect volume status is set to private.

System Action: Audit processing continues.

User Response: None.

ANR4219IAudit command: A library type specified for library library name in the physical volume repository is invalid.

Explanation: A database audit process finds that the library type for the specified library is invalid.

System Action: Audit processing continues.

User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected.

ANR4220IAudit command: A library type specified for library library name in the physical volume repository is invalid - the library type has been changed to the default of library type default.

Explanation: A database audit process finds that the library type for the specified library is invalid. Because FIX=YES has been specified for the command, the information is corrected by changing the library type to the default type.

System Action: Audit processing continues.

User Response: None.

ANR4221IAudit command: An error (error code) was found with archive description for node (node identifier), description (description), objects (old object count, new object count), count (old directory count, new directory count) - entry will be deleted or updated.

Explanation: A database audit process has found an error with the specified archive description. Because FIX=YES has been specified for the command, the entry is deleted or updated.

System Action: Audit processing continues.

User Response: None.

ANR4222IAudit command: An error (error code) was found with archive description for node (node identifier), description (description), objects (old object count, new object count), count (old directory count, new directory count).

Explanation: A database audit process has found an error with the specified archive description.

System Action: Audit processing continues.

User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected.

ANR4223IAudit command: An error (error code) was found with converted archive object for node (node identifier), description (description identifier), object (object.ID), filespace (filespace identifier) - entry will be deleted.

Explanation: A database audit process has found an error with the specified converted archive object. Because FIX=YES has been specified for the command, the entry is deleted.

System Action: Audit processing continues.

User Response: None.

ANR4224IAudit command: An error (error code) was found with converted archive object for node (node identifier), description (description identifier), object (object.ID), filespace (filespace identifier).

Explanation: A database audit process has found an error with the specified converted archive object.

System Action: Audit processing continues.

User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected.

ANR4225IAudit command: table entry for archive object (object.ID), node (node identifier), description (description), filespace (filespace identifier) not found - the entry will be created.

Explanation: A database audit process cannot find a converted table table entry for the specified archive object. Because FIX=YES has been specified for the command, an entry will be created.

System Action: Audit processing continues.

User Response: None.

ANR4226IAudit command: table entry for archive object (object.ID), node (node identifier), description (description), filespace (filespace identifier) not found.

Explanation: A database audit process cannot find a converted table table entry for the specified archive object.

System Action: Audit processing continues.

User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected.

ANR4227EAudit command: Inconsistent information detected for file aggregate (Aggregate.ID).

Explanation: A database audit process finds inconsistent information for a file aggregate. This problem cannot be corrected by the audit process, but the file data is not deleted.

System Action: Audit processing continues.

User Response: Contact your service representative.

ANR4228EAudit command: Missing or incorrect information detected for file aggregate (Aggregate.ID).

Explanation: A database audit process detects missing or incorrect information for a file aggregate. This information can be corrected.

System Action: Audit processing continues.

User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected.

ANR4229EAudit command: Missing or incorrect information detected for file aggregate (Aggregate.ID) - It will be corrected.

Explanation: A database audit process detects missing or incorrect information for a file aggregate. Because FIX=YES has been specified for the audit command, the error will be corrected.

System Action: Audit processing continues.

User Response: None.

ANR4230IAudit command: Auditing data storage definitions.

Explanation: This message is displayed during a database audit and indicates that the data storage definitions are being examined by the database audit process.

System Action: Audit processing continues.

User Response: None.

ANR4231EAudit command: Invalid device class strategy strategy for device class device class name.

Explanation: A database audit process finds a device class with an invalid access strategy.

System Action: Audit processing continues.

User Response: Reissue the audit command with FIX=YES so that the access strategy can be corrected.

ANR4232EAudit command: Invalid device class strategy strategy for device class device class name - information will be corrected.

Explanation: A database audit process finds a device class with an invalid access strategy. Because FIX=YES has been specified for the audit command, the access strategy will be corrected for this device class.

System Action: Audit processing continues.

User Response: None.

ANR4233EAudit command: Pool ID information is missing or incorrect for storage pool storage pool name.

Explanation: A database audit process finds a storage pool whose pool ID information is missing or incorrect.

System Action: Audit processing continues.

User Response: Reissue the audit command with FIX=YES so that the access strategy can be corrected.

ANR4234EAudit command: Pool ID information is missing or incorrect for storage pool storage pool name - information will be created or corrected.

Explanation: A database audit process finds a storage pool whose pool ID information is missing or incorrect. Because FIX=YES has been specified for the audit command, the pool ID information will be created or corrected for this storage pool.

System Action: Audit processing continues.

User Response: None.

ANR4235EAudit command: Device class ID referenced by storage pool storage pool name is not defined - data in this pool may not be available.

Explanation: A database audit process finds a storage pool which references a device class ID which is not defined.

System Action: Audit processing continues.

User Response: Contact your service representative.

ANR4236EAudit command: An invalid access strategy was encountered for storage pool storage pool name.

Explanation: A database audit process encounters an invalid device access strategy for the specified storage pool.

System Action: Audit processing continues.

User Response: Reissue the audit command with FIX=YES so that the attribute can be corrected.

ANR4237EAudit command: An invalid access strategy was encountered for storage pool storage pool name - the strategy will be corrected.

Explanation: A database audit process encounters an invalid device access strategy for the specified storage pool. Because FIX=YES has been specified for the command, the storage pool access strategy will be corrected.

System Action: Audit processing continues.

User Response: After the audit command completes, examine the storage pool using the QUERY STGPOOL command, and verify that the correct information is displayed for this storage pool.

ANR4238EAudit command: Storage pool storage pool name specifies an undefined pool ID for its next storage pool.

Explanation: The specified storage pool references an invalid pool ID as its next storage pool.

System Action: Audit processing continues.

User Response: Use the UPDATE STGPOOL command to update the next pool. Alternatively, if the audit command is reissued with FIX=YES, the reference to the next pool will be deleted.

ANR4239EAudit command: Storage pool storage pool name specifies an undefined pool ID for its next storage pool - reference will be deleted.

Explanation: The specified storage pool references an invalid pool ID as its next storage pool. Because FIX=YES has been specified for the command, the reference is deleted. The specified storage pool will not have a next pool.

System Action: Audit processing continues.

User Response: After the audit command completes, use the UPDATE STGPOOL command to assign a next storage pool, if desired.

ANR4240EAudit command: An invalid attribute was encountered for storage pool storage pool name.

Explanation: A database audit process encounters an invalid attribute for the specified storage pool.

System Action: Audit processing continues.

User Response: Reissue the audit command with FIX=YES so that the attribute can be corrected.

ANR4241EAudit command: An invalid attribute was encountered for storage pool storage pool name - the attribute will be assigned its default value.

Explanation: A database audit process encounters an invalid attribute for the specified storage pool. Because FIX=YES has been specified for the command, the storage pool will be corrected using the default value for the attribute.

System Action: Audit processing continues.

User Response: After the audit command completes, examine the storage pool using the QUERY STGPOOL command, and correct attributes with the UPDATE STGPOOL command, if desired.

ANR4242EAudit command: Invalid administrator update information encountered for storage pool storage pool name.

Explanation: A database audit process finds incorrect information pertaining to the last update for the specified storage pool.

System Action: Audit processing continues.

User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected.

ANR4243EAudit command: Invalid administrator update information encountered for storage pool storage pool name - information will be corrected.

Explanation: A database audit process finds incorrect information pertaining to the last update for the specified storage pool. Because FIX=YES has been specified for the command, the information is corrected.

System Action: Audit processing continues.

User Response: None.

ANR4244EAudit command: Storage pool ID referenced by volume volume name is not defined - data on this volume may not be available.

Explanation: A database audit process finds a data storage volume which references a storage pool ID that is not defined.

System Action: Audit processing continues.

User Response: You can attempt to move data on the specified volume to other volumes using the MOVE DATA command; then delete the specified volume and redefine it. If this does not work, contact your service representative.

ANR4245EAudit command: An invalid access strategy was encountered for volume volume name.

Explanation: A database audit process encounters an invalid device access strategy for the specified volume.

System Action: Audit processing continues.

User Response: Reissue the audit command with FIX=YES so that the strategy can be corrected.

ANR4246EAudit command: An invalid access strategy was encountered for volume volume name - the strategy will be corrected.

Explanation: A database audit process encounters an invalid device access strategy for the specified volume. Because FIX=YES has been specified for the command, the access strategy will be corrected for this volume.

System Action: Audit processing continues.

User Response: None.

ANR4247EAudit command: Missing information for volume volume name cannot be created. Delete the volume after optionally moving any files from the volume.

Explanation: A database audit process encounters missing database information for the specified volume. Since FIX=YES has been specified for the audit command, an attempt is made to create the missing information where possible. However, some of the information cannot be created, and the volume must be deleted.

System Action: The access mode for the volume is set to UNAVAILABLE to prevent further attempts to write to this volume. Audit processing continues.

User Response: After audit processing completes, an administrator should take the following actions to eliminate the volume

ANR4248EAudit command: Missing or incorrect information for storage volume volume name.

Explanation: A database audit process finds a data storage volume for which information is missing or incorrect.

System Action: Audit processing continues.

User Response: Reissue the audit command with FIX=YES so that the information can be created or corrected.

ANR4249EAudit command: Missing or incorrect information for storage volume volume name - information will be created or corrected.

Explanation: A database audit process finds a data storage volume for which information is missing or incorrect. Since FIX=YES has been specified for the audit command, the information will be created or corrected.

System Action: Audit processing continues.

User Response: None.

ANR4250EAudit command: Extraneous reference found.

Explanation: A database audit process finds a reference to a nonexistent entity such as a storage pool or volume.

System Action: Audit processing continues.

User Response: Reissue the audit command with FIX=YES so that the information is deleted.

ANR4251EAudit command: Extraneous reference found - information will be deleted.

Explanation: A database audit process finds a reference to a nonexistent entity such as a storage pool or volume. Since FIX=YES has been specified for the audit command, the extraneous information will be deleted.

System Action: Audit processing continues.

User Response: None.

ANR4252EAudit command: Data storage global attributes cannot be found.

Explanation: A database audit process is not able to locate the global attributes for data storage in the server database.

System Action: Audit processing continues.

User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected.

ANR4253EAudit command: Data storage global attributes cannot be found - attributes will be recreated.

Explanation: A database audit process is not able to locate the global attributes for data storage in the server database. Because FIX=YES has been specified for the audit command, the attributes will be regenerated.

System Action: Audit processing continues.

User Response: None.

ANR4254EAudit command: Data storage high-water marks do not match the identifiers in use.

Explanation: A database audit process finds that the information used to track data storage identifiers is incorrect.

System Action: Audit processing continues.

User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected.

ANR4255EAudit command: Data storage high-water marks do not match the identifiers in use - they will be corrected.

Explanation: A database audit process finds that the information used to track data storage identifiers is incorrect. Because FIX=YES has been specified for the audit command, the error will be corrected.

System Action: Audit processing continues.

User Response: None.

ANR4256IAudit command: Auditing data storage definitions for disk volumes.

Explanation: This message is displayed during a database audit and indicates that the database information relating to data storage disk volumes is being examined by the database audit process.

System Action: Audit processing continues.

User Response: None.

ANR4257EAudit command: A correctable data-integrity error was detected on volume volume name.

Explanation: A database audit process finds a data-integrity error for a file stored on the specified volume. This error is correctable.

System Action: Audit processing continues.

User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected.

ANR4258EAudit command: A data-integrity error was detected on volume volume name - the error will be corrected.

Explanation: A database audit process finds a correctable data-integrity error for a file stored on the specified volume. Because FIX=YES has been specified for the audit command, the error will be corrected.

System Action: Audit processing continues.

User Response: None.

ANR4259EAudit command: Invalid data encountered for a file in data storage - data can be corrected.

Explanation: A database audit process finds invalid data for a file in data storage. The error should be correctable.

System Action: Audit processing continues.

User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected.

ANR4260EAudit command: Invalid data encountered for a file in data storage - the error will be corrected.

Explanation: A database audit process finds invalid data for a file in data storage. Because FIX=YES has been specified for the audit command, the error will be corrected.

System Action: Audit processing continues.

User Response: None.

ANR4261EAudit command: Invalid access information was encountered for volume volume name.

Explanation: A database audit process encounters invalid access information for the specified volume.

System Action: Audit processing continues.

User Response: After audit processing has completed, use the UPDATE VOLUME command to set the access information for this volume. Or reissue the audit command with FIX=YES, which sets access to the default value.

ANR4262EAudit command: Invalid access information was encountered for volume volume name - the information will be corrected.

Explanation: A database audit process encounters invalid access information for the specified volume. Because FIX=YES has been specified for the command, the information will be corrected by setting the default value.

System Action: Audit processing continues.

User Response: After audit processing has completed, use the UPDATE VOLUME command to set the access information for this volume, if desired.

ANR4263IAudit command: Auditing data storage definitions for sequential volumes.

Explanation: This message is displayed during a database audit and indicates that the database information relating to data storage sequential volumes is being examined by the database audit process.

System Action: Audit processing continues.

User Response: None.

ANR4264IAudit command: Auditing file information.

Explanation: This message is displayed during a database audit and indicates that information on stored files is being examined by the database audit process.

System Action: Audit processing continues.

User Response: None.

ANR4265IAudit command: Auditing disk file information.

Explanation: This message is displayed during a database audit and indicates that information on files stored on disk media is being examined by the database audit process.

System Action: Audit processing continues.

User Response: None.

ANR4266IAudit command: Auditing sequential file information.

Explanation: This message is displayed during a database audit and indicates that information on files stored on sequential media is being examined by the database audit process.

System Action: Audit processing continues.

User Response: None.

ANR4267EAudit command: A storage pool containing file data cannot be located - file data may not be accessible.

Explanation: This message is displayed during a database audit and indicates that the storage pool containing a file's data cannot be located or is not defined. This problem cannot be corrected by the audit process, but the file data is not deleted.

System Action: Audit processing continues.

User Response: Contact your service representative.

ANR4268EAudit command: A storage volume containing file data cannot be located - file data may not be accessible.

Explanation: This message is displayed during a database audit and indicates that the storage volume containing a file's data cannot be located or is not defined. This problem cannot be corrected by the audit process, but the file data is not deleted.

System Action: Audit processing continues.

User Response: Contact your service representative.

ANR4269EAudit command: Extraneous file data reference found.

Explanation: A database audit process finds a reference to a file that no longer exists.

System Action: Audit processing continues.

User Response: Reissue the audit command with FIX=YES so that the information can be deleted.

ANR4270EAudit command: Extraneous file data reference found - information will be deleted.

Explanation: A database audit process finds a reference to a file that no longer exists. Because FIX=YES has been specified for the audit command, the information will be deleted.

System Action: Audit processing continues.

User Response: None.

ANR4271EAudit command: Missing or incorrect occupancy information detected.

Explanation: A database audit process detects missing or incorrect occupancy information for a data storage pool or a data storage volume.

System Action: Audit processing continues.

User Response: Reissue the audit command with FIX=YES so that the information can be created or corrected.

ANR4272EAudit command: Missing or incorrect occupancy information detected - information will be created or corrected.

Explanation: A database audit process detects missing or incorrect occupancy information for a data storage pool or a data storage volume. Because FIX=YES has been specified for the audit command, the information will be created or corrected.

System Action: Audit processing continues.

User Response: None.

ANR4273EAudit command: A data-integrity error was detected on volume volume name - Issue the AUDIT VOLUME command to correct the error.

Explanation: A database audit process finds a data-integrity error for a file stored on the specified volume.

System Action: Audit processing continues.

User Response: Issue the AUDIT VOLUME command on the specified volume to correct the data-integrity error.

ANR4274EAudit command: A correctable data-integrity error was detected.

Explanation: A database audit process finds a data-integrity error for a stored file. This error can be corrected.

System Action: Audit processing continues.

User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected.

ANR4275EAudit command: A data-integrity error was detected - it will be corrected.

Explanation: A database audit process finds a data-integrity error for a stored file. Because FIX=YES has been specified for the audit command, the error will be corrected.

System Action: Audit processing continues.

User Response: None.

ANR4276EAudit command: Invalid file storage information detected - file data is not accessible.

Explanation: A database audit process finds invalid file storage information for a stored file, and it cannot be corrected.

System Action: Audit processing continues.

User Response: Issue the AUDIT VOLUME command on all your volumes to correct the data-integrity error.

ANR4277EAudit command: Invalid file storage information detected.

Explanation: A database audit process finds invalid file storage information for a stored file. This information can be corrected.

System Action: Audit processing continues.

User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected.

ANR4278EAudit command: Invalid file storage information detected - It will be corrected.

Explanation: A database audit process finds invalid file storage information for a stored file. Because FIX=YES has been specified for the audit command, the error will be corrected.

System Action: Audit processing continues.

User Response: None.

ANR4279EAudit command: Administrator administrator number assigned to more than just system authority class.

Explanation: A database audit process finds that an administrator is assigned to other authority classes. Being assigned with 'SYSTEM' authority supersedes all other classes and the other privilege class entries should be deleted.

System Action: Audit processing continues.

User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected.

ANR4280IAudit command: Administrator administrator number assigned to more than just system authority class - the other class entries will be deleted.

Explanation: A database audit process finds that an administrator is assigned to other authority classes. Being assigned with 'SYSTEM' authority supersedes all other classes and the other privilege class entries should be deleted. Because FIX=YES has been specified for the command, any authority class other than system will be deleted.

System Action: Audit processing continues.

User Response: None.

ANR4281EAudit command: Administrator administrator number assigned as an unrestricted policy administrator is also assigned as a restricted administrator for domain domain name.

Explanation: A database audit process finds the specified administrator is assigned as an unrestricted policy administrator. The specified administrator is also assigned as the restricted administrator for the specified policy domain. The unrestricted policy administration class supersedes any restricted policy class definitions for an administrator. The administrator's authority needs to be corrected.

System Action: Audit processing continues.

User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected.

ANR4282IAudit command: Administrator administrator number assigned as an unrestricted policy administrator is also assigned as administrator for domain domain name - restricted class entry will be deleted.

Explanation: A database audit process finds the specified administrator is assigned as an unrestricted policy administrator. The specified administrator is also assigned as the restricted administrator for the specified policy domain. The unrestricted policy administration class supersedes any restricted policy class definitions for an administrator. Because FIX=YES has been specified for the command, the restricted administrator policy class will be deleted.

System Action: Audit processing continues.

User Response: None.

ANR4283EAudit command: Administrator administrator number assigned as an unrestricted storage administrator is also assigned as a restricted administrator for storage pool storage pool name.

Explanation: A database audit process finds the specified administrator is assigned as an unrestricted storage administrator. The specified administrator is also assigned as the restricted administrator for the specified storage pool. The unrestricted storage administration class supersedes any restricted storage class definitions for an administrator. The administrator's authority needs to be corrected.

System Action: Audit processing continues.

User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected.

ANR4284IAudit command: Administrator administrator number assigned as an unrestricted storage administrator is also assigned as a restricted administrator for storage pool storage pool name - restricted class entry will be deleted.

Explanation: A database audit process finds the specified administrator is assigned as an unrestricted storage administrator. The specified administrator is also assigned as the restricted administrator for the specified storage pool. The unrestricted storage administration class supersedes any restricted storage class definitions for an administrator. Because FIX=YES has been specified for the command, the restricted administrator storage class will be deleted.

System Action: Audit processing continues.

User Response: None.

ANR4285EAudit command: A data-integrity error was detected on a storage volume for object (Object.ID).

Explanation: A database audit process found a data-integrity error for a file stored on a storage volume, but the specific volume name is not known. If fix=yes was specified, the audit process will attempt to correct the data-integrity error.

System Action: Audit processing continues.

User Response: None.

ANR4286EAudit command: A correctable storage allocation error detected for volume volume name.

Explanation: A database audit process finds incorrect block allocation information for the specified storage volume; the error can be corrected.

System Action: Audit processing continues.

User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected.

ANR4287EAudit command: Storage allocation error detected for volume volume name - It will be corrected.

Explanation: A database audit process finds incorrect block allocation information for the specified storage volume; the error will be corrected.

System Action: Audit processing continues.

User Response: None.

ANR4288EAudit command: Multiple files allocated the same disk storage block on volume volume name.

Explanation: A database audit process finds multiple files allocated the same disk storage block on the specified volume; this error cannot be corrected by the audit process.

System Action: Audit processing continues.

User Response: Contact your service representative.

ANR4289EAudit command: Multiple files allocated the same disk storage block on volume volume name.

Explanation: A database audit process finds multiple files allocated the same disk storage block on the specified volume; this error cannot be corrected by the audit process.

System Action: Audit processing continues.

User Response: Contact your service representative.

ANR4290IAudit command: License global attributes could not be found - they will be created.

Explanation: A database audit process cannot find the license global attributes. Because FIX=YES has been specified for the command, the information is corrected by the creation of the global attributes.

System Action: Audit processing continues.

User Response: None.

ANR4291IAudit command: License global attributes could not be found.

Explanation: A database audit process cannot find the license global attributes.

System Action: Audit processing continues.

User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected.

ANR4292IAudit command: Invalid table active column encountered for license global attribute - the value will be corrected.

Explanation: A database audit process finds that the active column license global attribute is invalid. Because FIX=YES has been specified for the command, the active column is reset to a proper value.

System Action: Audit processing continues.

User Response: None.

ANR4293IAudit command: Invalid table active column encountered for license global attributes.

Explanation: A database audit process finds that the active column license global attribute is invalid.

System Action: Audit processing continues.

User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected.

ANR4294IAudit command: A license node assignment entry was not found for node node ID - an entry will be created.

Explanation: A database audit process cannot find the node assignment entry corresponding to the specified node. Since FIX=YES has been specified for the command, the required license entry will be created using default values.

System Action: Audit processing continues.

User Response: None.

ANR4295IAudit command: A license node assignment entry was not found for node node ID.

Explanation: A database audit process cannot find the node assignment entry corresponding to the specified node.

System Action: Audit processing continues.

User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected.

ANR4296IAudit command: An invalid license node assignment entry was found for node node ID - the entry will be deleted.

Explanation: A database audit process finds that the license node assignment entry is invalid. Because FIX=YES has been specified for the command, the node entry is deleted.

System Action: Audit processing continues.

User Response: None.

ANR4297IAudit command: An invalid license node assignment entry was found for node node ID.

Explanation: A database audit process finds that the license node assignment entry is invalid.

System Action: Audit processing continues.

User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected.

ANR4298IExpiration thread already processing - unable to begin another expiration process.

Explanation: The expiration thread is already processing. The processing expiration thread is either an EXPIRE INVENTORY command or is the automatic background expiration process. In either case, another expiration process cannot be started until the current expiration process completes or is canceled.

System Action: Current expiration process continues.

User Response: Use the QUERY PROCESS command to determine the status of the current expiration process.

ANR4299IAudit command: Invalid audit interval encountered for license global attribute - the value will be set to the default.

Explanation: A database audit process finds that the audit interval license global attribute is invalid. Because FIX=YES has been specified for the command, the audit interval is reset to the default value.

System Action: Audit processing continues.

User Response: None.

ANR4300IAudit command: Invalid audit interval encountered for license global attributes.

Explanation: A database audit process finds that the audit interval license global attribute is invalid.

System Action: Audit processing continues.

User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected.

ANR4301IAudit command: Invalid last audit date encountered for license global attribute - the value will be set to 0.

Explanation: A database audit process finds that the last audit date license global attribute is invalid. Because FIX=YES has been specified for the command, the last audit date is set to 0. The next execution of AUDIT LICENSES will set a new last audit date.

System Action: Audit processing continues.

User Response: None.

ANR4302IAudit command: Invalid last audit date encountered for license global attribute.

Explanation: A database audit process finds that the last audit date license global attribute is invalid.

System Action: Audit processing continues.

User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected.

ANR4303EAudit command: Inventory references for object(Object.ID) deleted.

Explanation: A database audit process deleted all inventory references for the specified object ID. This process corrects a data-integrity error if FIX=YES was specified.

System Action: Audit processing continues.

User Response: None.

ANR4304EAudit command: object name missing entry for cluster cluster ID - cluster entries deleted.

Explanation: A database audit process is missing a corresponding entry for the specified comparison object and cluster ID. This process indicates a data-integrity error for the database cluster information. If FIX=YES was specified, the invalid cluster information will be deleted.

System Action: Audit processing continues.

User Response: None.

ANR4305EAudit command: object name missing entry for cluster cluster ID.

Explanation: A database audit process is missing a corresponding entry for the specified comparison object and cluster ID. This indicates a data-integrity error for the database cluster information.

System Action: Audit processing continues.

User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected.

ANR4306IAUDITDB: Processed number of entries database entries (cumulative).

Explanation: This message indicates the number of database entries that have been processed during database audit processing.

System Action: Database audit processing continues.

User Response: None.

ANR4307IAudit command: Auditing inventory external space-managed objects.

Explanation: This message is displayed during a database audit and indicates that server information about external space-managed client objects is currently being examined by the database audit process.

System Action: Audit processing continues.

User Response: None.

ANR4308IAudit command: External space-managed entry for node node ID and file space filespace ID is missing a corresponding space-managed object entry - the external space-managed entry will be deleted.

Explanation: A database audit process finds that an external space-managed entry is missing a corresponding space-managed entry. Because FIX=YES has been specified, the orphaned external space-managed entry is deleted.

System Action: Audit processing continues.

User Response: None.

ANR4309IAudit command: External space-managed entry for node node ID and file space filespace ID is missing a corresponding space-managed object entry.

Explanation: A database audit process finds that an external space-managed entry is missing a corresponding space-managed entry.

System Action: Audit processing continues.

User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected.

ANR4310IAudit command: Auditing inventory space-managed objects.

Explanation: This message is displayed during a database audit and indicates that server information about space-managed client objects is currently being examined by the database audit process.

System Action: Audit processing continues.

User Response: None.

ANR4311IAudit command: Object entry for space-managed object object.ID not found - entry will be created.

Explanation: A database audit process cannot find an object entry for the specified space-managed object. Because FIX=YES has been specified for the command, an object entry is created by using default values.

System Action: Audit processing continues.

User Response: None.

ANR4312IAudit command: Object entry for space-managed object object.ID not found.

Explanation: A database audit process cannot find an object entry for the specified backup object.

System Action: Audit processing continues.

User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected.

ANR4313IAudit command: Space-managed object (object ID) for node node ID and file space filespace ID has one or more incorrect fields - the values will be corrected.

Explanation: A database audit process determined that one or more field values for the specified space-managed object is not valid. Because FIX=YES was specified the values are corrected.

System Action: Audit processing continues.

User Response: None.

ANR4314IAudit command: Space-managed object (object ID) for node node ID and file space filespace ID has one or more incorrect fields.

Explanation: A database audit process determined that one or more field values for the specified space-managed object is not valid.

System Action: Audit processing continues.

User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected.

ANR4315IAudit command: Space-managed object (object ID) for node node ID and file space filespace ID is missing the corresponding external space managed entry - the entry will be created.

Explanation: A database audit process determines that the space-managed object entry is missing a corresponding external space managed entry. Because FIX=YES was specified, the missing entry will be created.

System Action: Audit processing continues.

User Response: None.

ANR4316IAudit command: Space-managed object (object ID) for node node ID and file space filespace ID is missing the corresponding external space managed entry.

Explanation: A database audit process determines that the space-managed object entry is missing a corresponding external space-managed entry.

System Action: Audit processing continues.

User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected.

ANR4317IAudit command: External space-managed object (object ID) for node node ID and file space filespace ID has one or more incorrect fields - the values will be corrected.

Explanation: A database audit process determined that one or more field values for the specified external space-managed object is not valid. Because FIX=YES was specified, the values will be corrected.

System Action: Audit processing continues.

User Response: None.

ANR4318IAudit command: External space-managed object (object ID) for node node ID and file space filespace ID has one or more incorrect fields.

Explanation: A database audit process determined that one or more field values for the specified external space-managed object is not valid.

System Action: Audit processing continues.

User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected.

ANR4319IAudit command: Space-managed object not found for object object.ID - object entry will be deleted.

Explanation: A database audit process cannot find a space-managed object entry for the specified object. Because FIX=YES was specified the object entry will be deleted.

System Action: Audit processing continues.

User Response: None.

ANR4320IAudit command: Space-managed object not found for object object.ID.

Explanation: A database audit process cannot find a space-managed object entry for the specified object.

System Action: Audit processing continues.

User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected.

ANR4321IAudit command: Invalid copy type encountered for object object.ID - object found as an space-managed object - correcting the invalid copy type

Explanation: A database audit process encounters an invalid copy type for the specified object ID, but finds a corresponding space-managed object for the entry. Because FIX=YES has been specified for the command, the invalid copy type is corrected.

System Action: Audit processing continues.

User Response: None.

ANR4322EAudit command: Management class class name in policy set set name, domain domain name does not have a valid space management technique defined.

Explanation: A database audit process finds a management class that does not have a valid value specified.

System Action: Audit processing continues.

User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected.

ANR4323EAudit command: Management class class name in policy set set name, domain domain name does not have a valid space management technique defined - the default value will be set.

Explanation: A database audit process finds a management class that does not have a valid value specified. Because FIX=YES was specified for the AUDITDB operation, the default space management technique value will be set for the management class specified.

System Action: Audit processing continues.

User Response: Refer to the DEFINE MGMTCLASS command in the Administrator's Reference for valid values.

ANR4324EAudit command: Management class class name in policy set set name, domain domain name does not have a valid AUTOMIGNONUSE value specified.

Explanation: A database audit process finds a management class that does not have a valid value specified.

System Action: Audit processing continues.

User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected.

ANR4325EAudit command: Management class class name in policy set set name, domain domain name does not have a valid AUTOMIGNONUSE value defined - the default value will be set.

Explanation: A database audit process finds a management class that does not have a valid value specified. Because FIX=YES was specified for the AUDITDB operation, the default AUTOMIGNONUSE value will be set for the management class specified.

System Action: Audit processing continues.

User Response: Refer to the DEFINE MGMTCLASS command in the Administrator's Reference for valid values.

ANR4326EAudit command: Management class class name in policy set set name, domain domain name does not have a valid MIGREQUIRESBKUP value specified.

Explanation: A database audit process finds a management class that does not have a valid value specified.

System Action: Audit processing continues.

User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected.

ANR4327EAudit command: Management class class name in policy set set name, domain domain name does not have a valid MIGREQUIRESBKUP value defined - the default value will be set.

Explanation: A database audit process finds a management class that does not have a valid value specified. Because FIX=YES was specified for the AUDITDB operation, the default MIGREQUIRESBKUP value will be set for the management class specified.

System Action: Audit processing continues.

User Response: Refer to the DEFINE MGMTCLASS command in the Administrator's Reference for valid values.

ANR4328WAudit command: Storage pool storage pool name, specified as a space management destination for management class management class name, policy set set name, domain domain name, does not exist.

Explanation: A database audit process encounters a storage pool specified for the space management destination of the specified management class that is not defined in the server database. If this management class is used in an active policy set, then migration operations will fail when attempting to put client data in the destination.

System Action: Audit processing continues.

User Response: After the audit command completes, use the DEFINE STGPOOL command to define the missing storage pool or the UPDATE MGMTCLASS command to update the management class to refer to an existing storage pool.

ANR4329IAudit command: Inactive reference found for active backup entry (Object.ID) - the inactive reference will be deleted.

Explanation: A database audit process found that an active backup entry for the specified object has a corresponding inactive backup entry. Since FIX=YES was specified for the command, the information is corrected by deleting the inactive backup object entry.

System Action: Audit processing continues.

User Response: None.

ANR4330IAudit command: Inactive reference found for active backup entry (Object.ID).

Explanation: A database audit process found that an active backup entry for the specified object has a corresponding inactive backup entry.

System Action: Audit processing continues.

User Response: None.

ANR4331Ecommand process terminated, no matching device classes.

Explanation: The server did not find any device class names matching the specifications entered in the RECONCILE VOLUMES command.

System Action: Server operation continues.

User Response: Use the QUERY DEVCLASS command to determine which device classes are defined on the server and reissue the RECONCILE VOLUMES command.

ANR4332WThis command will compare all volumes used by the specified device class(es) with the actual data stored on the associated server for those volumes and will report any discrepancies; the data will be inaccessible to users until the operation completes.

Explanation: During the execution of a RECONCILE VOLUMES command, any data a volume named would be unavailable to users.

System Action: The administrator is asked whether to continue.

User Response: Enter 'Y' to reconcile the volumes or 'N' to stop the process.

ANR4333WThis command will discard any references to volumes used by the specified device class(es) that are missing from the associated server, thereby rendering the data unrecoverable; the valid volumes will be inaccessible to users until the operation completes.

Explanation: During the execution of a RECONCILE VOLUMES command, any data on a volume being reconciled would be unavailable to users. After the command has ended, any inconsistent volumes found will be discarded.

System Action: The administrator is asked whether to continue.

User Response: Enter 'Y' to reconcile the volumes or 'N' to stop the process.

ANR4334Icommand (Repair) process started, process ID process ID.

Explanation: As the result of a RECONCILE VOLUMES command that specified FIX=YES, the process whose ID is displayed has begun reconciling the volumes associated with the given device class.

System Action: The volumes are reconciled and invalid volumes are displayed.

User Response: None.

ANR4335Icommand (Inspect Only) process started, process ID process ID.

Explanation: As the result of a RECONCILE VOLUMES command that specified FIX=NO, the process whose ID is displayed has begun reconciling the volumes associated with the given device class.

System Action: The volumes are reconciled and inconsistent volumes are displayed.

User Response: None.

ANR4336Wcommand process ended, process ID process ID.

Explanation: The RECONCILE VOLUMES command for the specified device class has ended.

System Action: None.

User Response: For complete details on the results of the RECONCILE VOLUMES command, examine the previous messages.

ANR4337Wcommand process terminated - process canceled.

Explanation: During processing of a RECONCILE VOLUMES command, the process performing the reconcile was canceled.

System Action: The RECONCILE VOLUMES command is ended.

User Response: None.

ANR4338Wcommand process terminated - sufficient recovery log space is not available.

Explanation: During processing of a RECONCILE VOLUMES command, the source server does not have sufficient recovery log space to continue.

System Action: The RECONCILE VOLUMES command is ended.

User Response: If necessary, make more recovery log space available to the source server.

ANR4339Wcommand process terminated - sufficient database space is not available.

Explanation: During processing of a RECONCILE VOLUMES command, the source server does not have sufficient database space to continue.

System Action: The RECONCILE VOLUMES command is ended.

User Response: If necessary, make more database space available to the source server.

ANR4340Wcommand process terminated - thread resource not available.

Explanation: During processing of a RECONCILE VOLUMES command, the source server cannot start a thread for the reconcile process.

System Action: The RECONCILE VOLUMES command is ended.

User Response: Reissue the RECONCILE VOLUMES command. If the error persists, it may indicate a shortage of source server memory.

ANR4341Wcommand process terminated - sufficient memory is not available.

Explanation: During processing of a RECONCILE VOLUMES command, the source server does not have enough memory available to complete the command.

System Action: The RECONCILE VOLUMES command is ended.

User Response: If necessary make more memory available to the source server.

ANR4342Wcommand process terminated - lock conflict detected.

Explanation: During processing of a RECONCILE VOLUMES command, the source server cannot obtain a required lock.

System Action: The RECONCILE VOLUMES command is ended.

User Response: Reissue the RECONCILE VOLUMES command.

ANR4343Wcommand process terminated - internal server error detected.

Explanation: During processing of a RECONCILE VOLUMES command, an internal server error occurs on the source server.

System Action: The RECONCILE VOLUMES command is ended.

User Response: Contact your service representative.

ANR4344Icommand started for device class device class (process ID process ID).

Explanation: The RECONCILE VOLUMES process whose ID is displayed has started reconciling volumes associated with the given device class.

System Action: The volumes are reconciled and inconsistent volumes are displayed.

User Response: None.

ANR4345Icommand completed for device class device class; (process ID process ID); volume count volumes inspected, volume count invalid volumes found, volume count volumes deleted.

Explanation: The RECONCILE VOLUMES process whose ID is displayed has finished reconciling volumes associated with the given device class. The number of volumes reconciled and the number of invalid volumes found or deleted are displayed.

System Action: None.

User Response: For complete details on the results of the RECONCILE VOLUMES command for the shown device class, examine the previous messages.

ANR4346Icommand completed for device class device class; (process ID process ID); volume count volumes inspected, volume count invalid volumes found.

Explanation: The RECONCILE VOLUMES process whose ID is displayed has finished reconciling volumes associated with the given device class. The number of volumes reconciled and the number of invalid volumes found are displayed.

System Action: None.

User Response: For complete details on the results of the RECONCILE VOLUMES command for the shown device class, examine the previous messages. If you suspect that volumes were inaccessible because of communications problems, correct the problems and retry the RECONCILE VOLUMES command. If the errors are valid, reissue the reconcile volumes command with FIX=YES so that the source server can attempt to correct the information.

ANR4352IContacting Server server name

Explanation: This message is displayed in response to a QUERY PROCESS command, and indicates that a reconciliation process is attempting to obtain volume information from the shown server.

System Action: The reconciliation process continues.

User Response: None.

ANR4353ICancel in progress

Explanation: This message is displayed in response to a QUERY PROCESS command, and indicates that a reconciliation process has been canceled. The process will end shortly.

System Action: The reconciliation process terminates and server operation continues.

User Response: None.

ANR4354Wcommand: Source server not authorized to reconcile target server server name.

Explanation: During processing of a RECONCILE VOLUMES command, the source server was not permitted to reconcile volume on the shown target server.

System Action: The reconciliation process continues.

User Response: If the source server should have permission to reconcile volumes on the shown target server, issue the UPDATE SERVER command with FORCESYNC=YES to cause the target server to accept reconcile operations for the source server. Reissue the RECONCILE VOLUMES command.

ANR4355Wcommand: Volume volume name not valid, source server missing corresponding entry for target server.

Explanation: As the result of a RECONCILE VOLUMES command, the volume shown was reported by the target server and it has no matching volume on the source server.

System Action: The reconciliation process continues.

User Response: The database on either the source or target server has been regressed by either a RESTORE DATABASE operation or some system facility external to the server. Investigate the action that caused one or both of the databases to be regressed to there current condition. If a newer database images exist for that server, consider restoring the server to that point in time. If the condition of the database on each server is acceptable and the RECONCILE VOLUMES command was issued with FIX=NO, reissue the RECONCILE VOLUMES command with FIX=Yes to have the volume deleted from the target server.

ANR4356Wcommand: Volume volume name not valid, target server missing corresponding entry for source server.

Explanation: As the result of a RECONCILE VOLUMES command, the volume shown was found on the source server and it has no matching volume on the target server.

System Action: The reconciliation process continues.

User Response: The database on either the source or target server has been regressed by either an RESTORE DATABASE operation or some system facility external to the server. Investigate the action that caused one or both of the databases to be regressed to there current condition. If a newer database images exist for that server, consider restoring the server to that point in time. If the RECONCILE VOLUMES command was issued with FIX=Yes and the volume is defined in a storage pool, the access mode of the volume will changed to unavailable to prevent attempted mounts on the source server. If the condition of the database on each server is acceptable, issue the DELETE VOLUME or DELETE VOLHISTORY command on the source server to remove the volume from the database.

ANR4357Wcommand: Volume volume name not valid, target server volume refers to device class device class that does not exist on the source server.

Explanation: As the result of a RECONCILE VOLUMES command, the volume shown was found on the target server and it is associated with the device class shown. The source server has NO corresponding device class.

System Action: The reconciliation process continues.

User Response: The database on either the source or target server has been regressed by either an RESTORE DATABASE operation or some system facility external to the server. Investigate the action that caused one or both of the databases to be regressed to their current condition. If a newer database image exist for that server, consider restoring the server to that point in time. In the case of a volume in the VOLHISTORY, the device class may have been deleted from the source server. If possible, issue the DEFINE DEVCLASS command to correct the situation. If the condition of the database on each server is acceptable and the RECONCILE VOLUMES command was issued with FIX=NO, reissue the RECONCILE VOLUMES command with FIX=Yes to have the volume deleted from the target server.

ANR4358Wcommand: Volume volume name not valid, the attributes of the volume on target server do not match the attributes on the source server.

Explanation: As the result of a RECONCILE VOLUMES command, the volume shown was found on both the source and target server, but the attributes describing the volume does not match.

System Action: The reconciliation process continues.

User Response: The database on either the source or target server has been regressed by either a RESTORE DATABASE operation or some system facility external to the server. Investigate the action that caused one or both of the databases to be regressed to there current condition. If a newer database image exist for that server, consider restoring the server to that point in time. If the condition of the database on each server is acceptable, additional actions will have to be taken because RECONCILE VOLUMES FIX=YES is unable to correct this situation. In the case of a volume in the VOLHISTORY, an IMPORT PREVIEW=YES or a RESTORE DATABASE PREVIEW=YES will determine the integrity of the volume. If the volume is in error, a DELETE VOLHISTORY will remove the volume from both the source and target servers. In the case of a volume in a storage pool, an AUDIT VOLUME FIX=NO will determine the integrity of the volume. If errors are found, an AUDIT VOLUME FIX=YES may make some data on the volume accessible. Otherwise, issue the DELETE VOLUME command on the source server to remove the volume from both the source and target servers.

ANR4359Wcommand: Volume volume name not valid, the size of the volume on target server does not match the size on the source server.

Explanation: As the result of a RECONCILE VOLUMES command, the volume shown was found on both the source and target server, but the size of the volume does not match.

System Action: The reconciliation process continues.

User Response: The database on either the source or target server has been regressed by either an RESTORE DATABASE operation or some system facility external to the server. Investigate the action that caused one or both of the databases to be regressed to there current condition. If a newer database image exist for that server, consider restoring the server to that point in time. If the condition of the database on each server is acceptable, additional actions will have to be taken because RECONCILE VOLUMES FIX=YES is unable to correct this situation. In the case of a volume in the VOLHISTORY, an IMPORT PREVIEW=YES or a RESTORE DATABASE PREVIEW=YES will determine the integrity of the volume. If the volume is in error, a DELETE VOLHISTORY will remove the volume from both the source and target servers. In the case of a volume in a storage pool, an AUDIT VOLUME FIX=NO will determine the integrity of the volume. If errors are found, an AUDIT VOLUME FIX=YES may make some data on the volume accessible. Otherwise, issue the DELETE VOLUME command on the source server to remove the volume from both the source and target servers.

ANR4360Wcommand: Volume volume name not valid, the type of the volume on target server does not match the type on the source server.

Explanation: As the result of a RECONCILE VOLUMES command, the volume shown was found on both the source and target server, but the type of the volume does not match. For example, the volume on the target server is defined in a storage pool, but the target server indicates that volume was used for a DATABASE BACKUP.

System Action: The reconciliation process continues.

User Response: The database on either the source or target server has been regressed by either an RESTORE DATABASE operation or some system facility external to the server. Investigate the action that caused one or both of the databases to be regressed to there current condition. If a newer database image exists for that server, consider restoring the server to that point in time. If the condition of the database on each server is acceptable, additional actions will have to be taken because RECONCILE VOLUMES FIX=YES is unable to correct this situation. These actions may have to be performed on one or both servers. Use the QUERY VOLHISTORY and QUERY VOLUME commands on both servers to determine the volume type on each server. In the case of a volume in the VOLHISTORY, a DELETE VOLHISTORY on the appropriate server that will remove the volume on that server. In the case of a volume in a storage pool, the DELETE VOLUME command on the appropriate server will remove the volume on that server.

ANR4361Wcommand: Volume volume name not valid, the target server has reported damage to all or part of the volume.

Explanation: As the result of a RECONCILE VOLUMES command, the volume shown was found on both the source and target server, but the target server has reported damage to all or part of the volume.

System Action: The reconciliation process continues.

User Response: On the target server, an audit with FIX=NO of the volumes in the storage pool used by the source server will indicate what which volume on the target server is damaged. This AUDIT VOLUME command may be able to reset the damaged indicator in the database if the damage was temporary due to hardware problems (for example, dirty tape heads). If the volume on the target server is in a primary storage pool that has previously been backed up to a copy storage pool, attempt to correct the damage by using the RESTORE STGPOOL command. If attempts to correct the damage on the target server fail, an AUDIT VOLUME command FIX=YES from the source server will mark as damaged in the source server database each file that is inaccessible and those files will not be accessed for future operations. If the files are part of an aggregate, the entire aggregate will be marked damaged. If a usable copy of the file exists in another storage pool, that copy may be accessed for future operations involving the file.

ANR4362Wcommand: Invalid volume volume name deleted from server server name for device class device class.

Explanation: As the result of a RECONCILE VOLUMES command that specified FIX=YES, the volume shown whose information is displayed is deleted from the target server.

System Action: The volume is deleted.

User Response: None.

ANR4363Wcommand: Volume volume name access changed to access mode.

Explanation: As the result of a RECONCILE VOLUMES command that specified FIX=YES, the access mode of the source volume has been changed to the value shown.

System Action: The volume's access mode is changed.

User Response: Review any additional messages issued by the RECONCILE VOLUMES command and correct the errors that set the volume to unavailable, or use the DELETE VOLUME command to remove it from the system.

ANR4364Wcommand: Unable to connect to target server server name.

Explanation: During processing of indicated command, the source server was unable to maintain communications with the shown target server.

System Action: The command process continues.

User Response: Check both the source server and the target server for any additional messages that might further describe the communications problem.

ANR4370EThe source server is not authorized to create volumes on target server server name.

Explanation: The source server has attempted to create a volume on the shown target server, but the operation failed because the source server does not have the authority to create volumes.

System Action: The operation fails.

User Response: If the source server should have permission to create volumes on the shown target server, issue the UPDATE SERVER command with FORCESYNC=YES to cause the target server to accept volume create operations for the source server. Retry the failing operation.

ANR4371EInformation on the source server does not match information on target server server name.

Explanation: The source server has determined that information contained on the shown target server no longer matches information contained on the source server.

System Action: The operation fails.

User Response: Issue the RECONCILE VOLUMES command to determine the problem. If possible, correct the problem and retry the failing operation.

ANR4372EThe password on the source server does not match the password on target server server name.

Explanation: The source server has attempted to update both the source password and the target password. An error occurred that prevented the source server from updating the target server. The passwords no longer match.

System Action: The operation fails.

User Response: On the target server, issue the UPDATE NODE command to change the password. On the source server, issue the UPDATE SERVER command to change the password to match the new password on the target server. Retry the failing operation.

ANR4373ESession rejected by target server server name, reason: rejection reason.

Explanation: The source server has attempted to open a session with the shown target server. The session was rejected for the indicated reason.

System Action: The operation fails.

User Response: Check both the source server and the target server for any additional messages that might further describe the reason the session was rejected. For a reason of AUTHENTICATION FAILURE, ensure that both the source and target servers are using the same password. For a reason of NO RESOURCE, ensure that the target server is enabled, has sufficient DB, LOG, and memory resource to support the source server session and that the node name of the source server is not locked or in use. If this is a routed command, check to make sure that the administator id being used to route the command is not locked or in use. For a reason of LICENSE FAILURE, ensure that the target server is properly licensed to support the source server session. For a reason of DOWN LEVEL, ensure that the target server program is a level new enough to support the source server session. For a reason of NODE TYPE, the source server is not allowed to establish a session with the given target server. The NODETYPE on the target server is CLIENT. The NODENAME parameter of the server definition on the source server is incorrect. The NODETYPE parameter of the registered node on the target server is incorrect and should be NODETYPE=SERVER. For a reason of INTERNAL ERROR, use the messages on the target server to determine the problem and contact your service representative. Retry the failing operation.

ANR4374ESession failure, source server detected an internal error.

Explanation: The source server ends the session because an internal logic error is detected.

System Action: The source server ends the session and continues operation.

User Response: To determine the source of the error, the administrator can examine server messages issued prior to this message. The QUERY ACTLOG command can be used to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative.

ANR4375ESession failure, source server has insufficient memory.

Explanation: The source server ends the session because sufficient memory (virtual memory) is not available.

System Action: The source server ends the session and continues operation.

User Response: Allocate additional storage to the server. For details, issue HELP MEMORY to display the information online or see "Appendix A. Allocating Additional Server Memory".

ANR4376ESession failure, target server server name is locked on the source server.

Explanation: The source server ends the session because shown target server is locked from source server access.

System Action: The source server ends the session and continues operation.

User Response: Before the source server is permitted to access the target server, a properly authorized administrator must unlock the target server.

ANR4377ESession failure, target server server name is not defined on the source server.

Explanation: The source server ends the session because shown target server is not defined on the source server.

System Action: The source server ends the session and continues operation.

User Response: Before the source server is permitted to access the target server, the target server must be properly defined.

ANR4378EFor device class device class, the retry of a session with target server server name has timed out.

Explanation: The source server has attempted to re-establish a session with the shown target server, but the RETRYPERIOD from the given device class has been exceeded.

System Action: The source server ends the operation.

User Response: Determine it the target server is having a problem or considering increasing the RETRYPERIOD value.

ANR4379EThe source server was unable to update the password on target server server name.

Explanation: The source server has attempted to update the target password. An error occurred that prevented the source server from updating the target server.

System Action: The operation fails.

User Response: On the target server, determine the cause of the problem and correct it. It may be necessary for an administrator to correct the passwords with the following actions. On the target server, issue the UPDATE NODE command to change the password. On the source server, issue the UPDATE SERVER command to change the password to match the new password on the target server. Retry the failing operation.

ANR4380EThe source server was unable to update the server validation key on target server server name.

Explanation: The source server has attempted to update it's server validation key on the target server. An error occurred that prevented the source server from updating the target server.

System Action: The operation fails.

User Response: On the target server, determine the cause of the problem and correct it. It may be necessary for an administrator to correct the keys with the following actions. On the source server, issue the UPDATE SERVER command with FORCESYNC=YES to cause an attempt to synchronize the keys on both the source and target servers. Retry the failing operation.

ANR4381EThe source server was unable to register with target server server name.

Explanation: The source server has attempted to register with the shown target server. An error occurred that prevented the source server from registering with the target server.

System Action: The operation fails.

User Response: Ask an authorized administrator to submit the request on the use of the target server using REGISTER NODE command. Retry the failing operation.

ANR4382ESession failure, policy information from target server server name is incomplete, missing policy object.

Explanation: The source server ends the session because the shown target server has provided policy information which is incomplete. The missing policy object is shown.

System Action: The source server ends the session and continues operation.

User Response: Use the appropriate commands on the target server to complete the policy definitions being used by the source server. Retry the failing operation.

ANR4383ESession failure, target server server name has aborted current transaction; reason: abort reason.

Explanation: The source server ends the session because the shown target server has aborted the current transaction for the given reason.

System Action: The source server ends the session and continues operation.

User Response: Check both the source server and the target server for any additional messages that might further describe the reason the transaction was aborted. Retry the failing operation.

ANR4384ENode node name is not allowed to establish a session as a target server.

Explanation: The node specified has attempted to establish a session with this system and this is not permitted due to the NODETYPE for this node.

System Action: The operation fails.

User Response: To allow the specified node to establish a session as a target server, the node must be registered with a NODETYPE of SERVER. Or else change the node name on the target server to a node name that is allowed to establish a session using a node name that was registered with the NODETYPE=SERVER parameter specified.

ANR4385ISession retry in progress with target server server name.

Explanation: The source server is attempting to re-establish a session with the shown target server. Session retry processing occurs when the source server has lost the connection with a target server and a RETRYPERIOD value is specified,

System Action: The source server attempts to contact the target server.

User Response: Determine if the target server is having a problem and considering canceling the operation on the source server or correcting the problem with the target server.

ANR4386ISession retry was successful for target server server name.

Explanation: The source server has re-establish a session with the shown target server.

System Action: Source server processing continues.

User Response: None.

ANR4387ESession session number for node node name (client platform) refused - node name not registered as TYPE=CLIENT.

Explanation: The server refuses a request to start a client session because the client node name is not registered as a node of TYPE=CLIENT. This node name is already in use either as a server definition as defined by a DEFINE SERVER command or else as a node of TYPE=SERVER using the REGISTER NODE command.

System Action: Server operation continues.

User Response: Issue a QUERY NODE TYPE=SERVER or a QUERY SERVER to determine which server definition already is using this node name. This client should be registered using the REGISTER NODE TYPE=CLIENT command and specify a name that is not in use by any other nodes or server defined to this server.

ANR4388WNo expiration process to cancel.

Explanation: The CANCEL EXPIRATION command was issued but there were no expiration processes currently running.

System Action: Server operation continues.

User Response: None.

ANR4389IExpiration process cancelled.

Explanation: The CANCEL EXPIRATION command was issued and successfully cancelled the current process.

System Action: Server operation continues.

User Response: None.

ANR4390ECANCEL EXPIRATION failed - unable to cancel expiration process.

Explanation: The CANCEL EXPIRATION command was issued but encountered an error. Due to this error, the command was unable to cancel the process.

System Action: Server operation continues.

User Response: Issue the command QUERY PROCESS to determine the process number for the expiration process and then issue the command CANCEL PROCESS for that process number. This will cancel the current expiration process.

ANR4391IExpiration processing node node name, filespace filespace name, domain domain name, and management class management class name - for type type files.

Explanation: Expiration processing is currently evaluating information for the node, filespace, domain name, and management class specified for the file type indicated.

System Action: Server operation continues.

User Response: None.

ANR4402IDatabase Dump command: Database update activity resumed

Explanation: Database update activities that were suspended by the database dump process are restarted.

System Action: Server operation continues.

User Response: None.

ANR4403IDatabase Load command: Database dump image is consistent - a database audit (AUDITDB) will NOT be required if this load completes successfully.

Explanation: The database dump that is currently being loaded by the LOADDB process is a consistent database image. This process implies that a database audit (AUDITDB) will not be required if the load completes successfully.

System Action: Server database load processing continues.

User Response: None

ANR4404IDatabase Load command: Loaded a consistent dump image - a database audit (AUDITDB) is NOT required.

Explanation: The database dump image loaded by the LOAD command was consistent. A database audit (AUDITDB) is not required. The server may be started normally.

System Action: Server database load processing completes.

User Response: None.

ANR4405IDatabase Load command: Loaded an inconsistent dump image - a database audit (AUDITDB) IS REQUIRED with FIX=YES.

Explanation: The database dump image loaded by the LOAD command was not consistent. A database audit (AUDITDB) with FIX=YES is required to return the database to a consistent state.

System Action: Server database load processing completes.

User Response: To check the database for inconsistencies and correct any inconsistencies, use the database audit (AUDITDB) utility as described in the Administrator's Reference.

ANR4406IAudit command: Client option Client option name sequence number option sequence number is not a member of an optionset. The option will be deleted.

Explanation: A database audit process found that the specified client option does not have a corresponding optionset. The option is deleted.

System Action: Audit processing continues.

User Response: None.

ANR4407IAudit command: Client option Client option name sequence number option sequence number is not a member of an optionset.

Explanation: A database audit process found that the specified client option does not have a corresponding optionset. The option is deleted.

System Action: Audit processing continues.

User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected.

ANR4408IAudit command: Client option Client option name sequence number option sequence number in optionset optionset name is not a valid option. The option will be deleted.

Explanation: A database audit process found that the specified client option is not a valid option. The option is deleted.

System Action: Audit processing continues.

User Response: None.

ANR4409IAudit command: Client option Client option name sequence number option sequence number in optionset option set is not a valid option.

Explanation: A database audit process found that the specified client option is not a valid option.

System Action: Audit processing continues.

User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected.

ANR4410ITriggered space expansion will be retried in number of seconds seconds.

Explanation: Because of a problem encountered during a triggered space expansion for the data base and/or recovery log, the current expansion stops but will be retried after the time period shown.

System Action: The system waits for the specified period and then retries to expand the data base and/or recovery log.

User Response: If possible, correct the condition that stopped the expansion. If the problem persists, contact your service representative.

ANR4411ITriggered space expansion retry delay ended; checking space trigger criteria.

Explanation: Because a triggered space expansion had been stopped due to a problem, the system waited before retrying. The retry wait period has ended, and the system can now retry to expand space for the data base and/or recovery log.

System Action: Space expansion begins.

User Response: None.

ANR4412IData Base and Recovery Log Space expansion triggered.

Explanation: A triggered space expansion had started.

System Action: Space expansion begins.

User Response: None.

ANR4413IRecovery Log Space expansion Is Needed, megabytes needed Megabytes needed.

Explanation: The recovery log is above the utilization percentage defined in a DEFINE SPACETRIGGER LOG command. An expansion of the indicated number of megabytes are needed to be above the space trigger utilization value.

System Action: Space expansion begins if supported on this platform.

User Response: None.

ANR4414IData Base Space expansion Is Needed, megabytes needed Megabytes needed.

Explanation: The data base is above the utilization percentage defined in a DEFINE SPACETRIGGER DB command. An expansion of the indicated number of megabytes are needed to be above the space trigger utilization value.

System Action: Space expansion begins if supported on this platform.

User Response: None.

ANR4415IData Base and Recovery Log Space Expansion Completed.

Explanation: A triggered space expansion had completed.

System Action: Normal operations resume.

User Response: None.

ANR4416WUnable to Determine Maximum Number of Data Base Volume Copies, rc=return code.

Explanation: The Data Base Space Trigger was in the processing of expanding the data base by creating new data base volumes. In doing so, the maximum number of copy volumes for any data base volume is determined. The process of determining this value failed.

System Action: Server operation continues. No additional data base copy volumes are created during this data base space expansion.

User Response: Use the Query DBVOL command to determine if your data base volume configuration is satisfactory. You may use the DEFINE DBCOPY command to define additional database volume copies, if necessary.

ANR4417WUnable to Create Data Base Copy Volume Data Base Copy Volume for volume Data Base Volume.

Explanation: The Data Base Space Trigger was in the processing of expanding the data base by creating new data base volumes. In doing so, data base copy volumes are created for mirroring. The indicated data base copy volume could not be created for the primary data base volume named.

System Action: Server operation continues. A data base copy volume is not created for the indicated primary volume.

User Response: Use the Query DBVOL command to determine if your data base volume configuration is satisfactory. You may use the DEFINE DBCOPY command to define additional data base volume copies, if necessary.

ANR4418WUnable to Define Data Base Copy Volume Data Base Copy Volume for volume Data Base Volume.

Explanation: The Data Base Space Trigger was in the processing of expanding the data base by creating new data base volumes. In doing so, data base copy volumes are created for mirroring. The indicated data base copy volume was created for the primary data base volume named, but could be registered with the server.

System Action: Server operation continues. A data base copy volumes is not registered for the indicated primary volume. The data base copy volume still exists on the system.

User Response: Use the Query DBVOL command to determine if your data base volume configuration is satisfactory. You may use the DEFINE DBCOPY command to retry the definition of the data base volume copy, if necessary.

ANR4419WUnable to Determine Maximum Number of Recovery Log Volume Copies, rc=return code.

Explanation: The Recovery Log Space Trigger was in the processing of expanding the recovery log by creating new recovery log volumes. In doing so, the maximum number of copy volumes for any recovery log volume is determined. The process of determining this value failed.

System Action: Server operation continues. No additional recovery log copy volumes are created during this recovery log space expansion.

User Response: Use the QUERY LOGVOL command to determine if your recovery log volume configuration is satisfactory. You may use the DEFINE LOGCOPY command to define additional recovery log volume copies, if necessary.

ANR4420WUnable to Create Recovery Log Copy Volume Recovery Log Copy Volume for volume Recovery Log Volume.

Explanation: The Recovery Log Space Trigger was in the processing of expanding the recovery log by creating new data base volumes. In doing so, recovery log copy volumes are created for mirroring. The indicated recovery log copy volume could not be created for the primary recovery log volume named.

System Action: Server operation continues. A recovery log copy volume is not created for the indicated primary volume.

User Response: Use the QUERY LOGVOL command to determine if your recovery log volume configuration is satisfactory. You may use the DEFINE LOGCOPY command to define additional recovery log volume copies, if necessary.

ANR4421WUnable to Define Recovery Log Copy Volume Recovery Log Copy Volume for volume Recovery Log Volume.

Explanation: The Recovery Log Space Trigger was in the processing of expanding the recovery log by creating new recovery log volumes. In doing so, recovery log copy volumes are created for mirroring. The indicated recovery log copy volume was created for the primary recovery log volume named, but could be registered with the server.

System Action: Server operation continues. A recovery log copy volume is not registered for the indicated primary volume. The recovery log copy volume still exists on the system.

User Response: Use the QUERY LOGVOL command to determine if your recovery log volume configuration is satisfactory. You may use the DEFINE LOGCOPY command to retry the definition of the recovery log volume copy, if necessary.

ANR4422IAUDITDB: Insufficient database space to optimze audit processing.

Explanation: A database audit process found that insufficient database space is available to optimize audit processing. If the audit can process, it will take much longer to complete than if the space was available.

System Action: Audit processing continues of possible, but may terminate if very little space is available.

User Response: Use the dsmserv extend db command to increase the size of the server datbase and restart the database audit function.

ANR4423IAUDITDB: Insufficient database space to continue audit processing.

Explanation: A database audit process found that insufficient database space is available to continue audit processing.

System Action: Audit processing terminates.

User Response: Use the dsmserv extend db command to increase the size of the server datbase and restart the database audit function.

ANR4424WData Base has reached Maximum Size in Space Trigger.

Explanation: The Data Base Space Trigger was specified with a maximum size for the data base. That value has been reached for the size of the data base.

System Action: Server operation continues. No additional data base space expansion will occur as a result of the data base space trigger.

User Response: None. You may review the space trigger settings and use the UPDATE SPACETRIGGER DB command to adjust space trigger values.

ANR4425WRecovery Log has reached Maximum Size in Space Trigger.

Explanation: The Recovery Log Space Trigger was specified with a maximum size for the recovery log. That value has been reached for the size of the recovery log.

System Action: Server operation continues. No additional recovery log expansion will occur as a result of the recovery log space trigger.

User Response: None. You may review the space trigger settings and use the UPDATE SPACETRIGGER LOG command to adjust space trigger values.

ANR4426WRecovery Log can no longer be Expanded by the Space Trigger.

Explanation: The Recovery Log Space Trigger was going to automatically expand the recovery log. Expanding the recovery log would cause the recovery log's size to exceed 5GB, which is beyond the server maximum limit for the recovery log.

System Action: Server operation continues, but the recovery log is not automatically expanded. No additional recovery log expansion will occur as a result of the recovery log space trigger.

User Response: None. You may review the space trigger settings and use the UPDATE SPACETRIGGER LOG command to adjust space trigger values. You may also backup the data base and/or setup a data base backup trigger to cause the data base to be backed up more often. Backing up the data base will decrease the recovery log utilization and you then use the REDUCE LOG and DELETE LOGVOLUME command to decrease the size of the recovery log.

ANR4427WOne or more Recovery Log Volumes differ in number of copy volumes.

Explanation: The Recovery Log Space Trigger was in the processing of expanding the recovery log by creating new volumes. In doing so, copy volumes are created for mirroring, and existing volumes are examined for mirroring. One or more recovery log volumes was found to have a different number of copy volumes than other volumes of the same type. It is recommended that the same number of copy volumes be created for each volume of the same type (database or log).

System Action: Server operation continues.

User Response: Use the QUERY LOGVOL command to determine if your volume configuration is satisfactory. You may use the DEFINE LOGCOPY command to define additional copy volumes, if necessary. You may use the DELETE LOGCOPY command to delete unnecessary copy volumes.

ANR4428WOne or more Data Base Volumes differs in number of copy volumes.

Explanation: The Data Base Space Trigger was in the processing of expanding the data base by creating new volumes. In doing so, copy volumes are created for mirroring, and existing volumes are examined for mirroring. One or more data base volumes was found to have a different number of copy volumes than other volumes of the same type. It is recommended that the same number of copy volumes be created for each volume of the same type (data base or log).

System Action: Server operation continues.

User Response: Use the QUERY DBVOL command to determine if your volume configuration is satisfactory. You may use the DEFINE DBCOPY command to define additional copy volumes, if necessary. You may use the DELETE DBCOPY command to delete unnecessary copy volumes.

ANR4429WUnable to Define Recovery Log Volume Recovery Log Volume.

Explanation: The Recovery Log Space Trigger was in the processing of expanding the recovery log by creating new recovery log volumes. The indicated recovery log volume was created, but could not be registered with the server.

System Action: Server operation continues. A recovery log volume is not registered with the server. The recovery log copy volume still exists on the system.

User Response: Use the Query LOGVOL command to determine if your recovery log volume configuration is satisfactory. You may use the DEFINE LOGCOPY command to retry the definition of the recovery log volume copy, if necessary. There will be an additional message in the activity log prior to this message indicating the reason for the failure.

ANR4430WUnable to Define Data Base Volume Data Base Volume.

Explanation: The Data Base Space Trigger was in the processing of expanding the data base by creating new data base volumes. The indicated data base volume was created, but could not be registered with the server.

System Action: Server operation continues. A data base volume is not registered with the server. The data base volume still exists on the system.

User Response: Use the Query DBVOL command to determine if your data base volume configuration is satisfactory. You may use the DEFINE DBVOLUME command for the data base volume named, to retry the definition of the data base volume copy, if necessary. There will be an additional message in the activity log prior to this message indicating the reason for the failure.

ANR4431IRecovery Log now Eligible for Expansion.

Explanation: The Recovery Log Space Trigger has previously hit a point where expanding the recovery log would have caused the recovery log's size to exceed 5GB, which is beyond the server maximum limit for the recovery log. This caused automatic recovery log expansion to be halted. The recovery log size has shrunk but once again needs expansion and is now eligible for expansion.

System Action: Server operation continues, and the automatic recovery log expansion will proceed.

User Response: None. None.

ANR4432WData Base can no longer be Expanded by the Space Trigger.

Explanation: The Data Base Space Trigger was going to automatically expand the data base. Expanding the data base would cause the size of the data base to exceed 500GB, which is beyond the server maximum limit for the data base.

System Action: Server operation continues, but the data base is not automatically expanded. No additional data base expansion will occur as a result of the recovery log space trigger until the data base size is less than the maximum size and the trigger attributes allow it to be expanded to a size less than the maxium.

User Response: None. You may review the space trigger settings and use the UPDATE SPACETRIGGER DB command to adjust space trigger values. You may also reduce the data base size, if possible.

ANR4433IData Base now Eligible for Expansion.

Explanation: The Data Base Space Trigger has previously hit a point where expanding the data base would have caused the size of the data base to exceed 500GB, which is beyond the server maximum limit for the data base. This caused automatic data base expansion to be halted. The data base size has shrunk or the space trigger values have been adjusted to allow expansion.

System Action: Server operation continues, and automatic data base expansion may proceed.

User Response: None.

ANR4434EAudit command: Password expiration found for unknown client node node name.

Explanation: A database audit process finds a password expiration period for a client node, but the client node is not defined correctly in the server database.

System Action: Audit processing continues.

User Response: If the audit command has not been issued with FIX=YES specified, reissue the audit function specifying FIX=YES so that the error can be corrected.

ANR4435IAudit command: Password expiration period deleted for unknown client node node name.

Explanation: A database audit process finds a password expiration period for a client node, but the client node is not defined correctly in the server database. Because FIX=YES has been specified for the audit command, the audit function deletes the password expiration period.

System Action: Audit processing continues.

User Response: None.

ANR4436EAudit command: Invalid password expiration password expiration period for client node node name.

Explanation: A database audit process finds an invalid password expiration period for a client node.

System Action: Audit processing continues.

User Response: If the audit command has not been issued with FIX=YES specified, reissue the audit function specifying FIX=YES so that the error can be corrected.

ANR4437IAudit command: Invalid password expiration period password expiration period deleted for client node node name.

Explanation: A database audit process finds an invalid password expiration period for a client node. Because FIX=YES has been specified for the audit command, the audit function deletes the password expiration period, causing the default, global password expiration period to take effect for the client node.

System Action: Audit processing continues.

User Response: After the AUDIT command completes, use the QUERY NODE command to examine the node that was updated. Use the UPDATE NODE command to set the correct password expiration period for the node.

ANR4438EAudit command: Password expiration found for unknown administrator administrator name.

Explanation: A database audit process finds a password expiration period for an administrator, but the administrator is not defined correctly in the server database.

System Action: Audit processing continues.

User Response: If the audit command has not been issued with FIX=YES specified, reissue the audit function specifying FIX=YES so that the error can be corrected.

ANR4439IAudit command: Password expiration period deleted for unknown administrator administrator name.

Explanation: A database audit process finds a password expiration period for an administrator, but the administrator is not defined correctly in the server database. Because FIX=YES has been specified for the audit command, the audit function deletes the password expiration period.

System Action: Audit processing continues.

User Response: None.

ANR4440EAudit command: Invalid password expiration password expiration period for administrator administrator name.

Explanation: A database audit process finds an invalid password expiration period for an administrator.

System Action: Audit processing continues.

User Response: If the audit command has not been issued with FIX=YES specified, reissue the audit function specifying FIX=YES so that the error can be corrected.

ANR4441IAudit command: Invalid password expiration period password expiration period deleted for administrator administrator name.

Explanation: A database audit process finds an invalid password expiration period for an administrator. Because FIX=YES has been specified for the audit command, the audit function deletes the password expiration period, causing the default, global password expiration period to take effect for the administrator.

System Action: Audit processing continues.

User Response: After the AUDIT command completes, use the QUERY ADMIN command to examine the administrator that was updated. Use the UPDATE ADMIN command to set the correct password expiration period for the administrator.

ANR4442EAudit command: Extended attribute extended attribute type is not a valid attribute type.

Explanation: A database audit process finds an extended attribute type that is not supported.

System Action: Audit processing continues.

User Response: If the audit command has not been issued with FIX=YES specified, reissue the audit function specifying FIX=YES so that the error can be corrected.

ANR4443IAudit command: Invalid extended attribute extended attribute type has been deleted.

Explanation: A database audit process finds an extended attribute type that is not supported. Because FIX=YES has been specified for the audit command, the audit function deletes extended attribute.

System Action: Audit processing continues.

User Response: None.

ANR4500IWriting sequential volume history information to defined files.

Explanation: The server is updating all sequential volume history files defined in the server options file with information on sequential volume usage information. The files updated are those specified with the VOLUMEHISTORY option in the server options file.

System Action: Server operation continues.

User Response: None.

ANR4501ISequential volume history information successfully written to file name.

Explanation: The server is updating all sequential volume history files defined in the server options file with information on sequential volume usage information. Volume history information was successfully written to the file specified.

System Action: Server operation continues.

User Response: None.

ANR4502WNo files have been defined for automatically storing sequential volume history information.

Explanation: The server is attempting to update all sequential volume history files defined in the server options file with information on sequential volume usage information. Because no files were configured for receiving this information, the automatic operation fails.

System Action: Server operation continues.

User Response: To have the server automatically record sequential volume history information to assist in server recovery, use the VOLUMEHISTORY option in the server options file to specify where history information should be written. If you update the options file, restart the server.

ANR4510EServer could not write sequential volume history information to volume history file name.

Explanation: While attempting to write sequential volume history information to defined history files, the server could not write to the file name specified.

System Action: The server does not write volume history information to the file specified

User Response: Examine error messages that may have been displayed prior to this message and correct any problems, if possible. Make sure that the server has proper authority to write to the file indicated and that there is sufficient space in the file system for the file. On MVS, make sure that the data set has been allocated and that the server has authority to write to the data set. After the problem has been corrected, use the BACKUP VOLHISTORY command to write sequential volume history information to the file.

ANR4511EVolume history file volume history file name could not be opened.

Explanation: While attempting to write sequential volume history information to or read information from defined history files, the server cannot open the file name specified.

System Action: The server does not write volume history information to or read volume history information from the file specified

User Response: Examine error messages that may have been displayed prior to this message and correct any problems, if possible. Make sure that the server has proper authority to write to the file indicated and that there is sufficient space in the file system for the file. On MVS, make sure that the data set has been allocated and that the server has authority to write to the data set.

ANR4512EA database transaction failure was encountered in processing sequential volume history information.

Explanation: While attempting to process sequential volume history information, the server encountered a database transaction error.

System Action: The operation fails. Usage for a sequential volume was not properly recorded for later reference.

User Response: Examine error messages that may have been displayed prior to this message and correct any problems, if possible. If this does not resolve the problem, contact your support representative.

ANR4513EA database lock conflict was encountered in processing sequential volume history information.

Explanation: While attempting to process sequential volume history information, the server encountered a database locking conflict.

System Action: The operation fails. This usually means that usage for a sequential volume was not properly recorded for later reference

User Response: Examine error messages that may have been displayed prior to this message and correct any problems, if possible. If this does not resolve the problem, contact your support representative.

ANR4514ESufficient database space is not available for the server while processing sequential volume history information.

Explanation: While attempting to process sequential volume history information, the server found that sufficient database space was not available for updates.

System Action: The operation fails. Usage for a sequential volume was not properly recorded for later reference.

User Response: To increase the amount of database space available to the server, an authorized administrator can add database volumes by using the DEFINE DBVOLUME command, and extend the size of the database by using the EXTEND DB command.

ANR4515ESufficient recovery log space is not available for the server while processing sequential volume history information.

Explanation: While attempting to process sequential volume history information, the server finds that sufficient recovery log space is not available for updates.

System Action: The operation fails. Usage for a sequential volume was not properly recorded for later reference.

User Response: To increase the amount of database space available to the server, an authorized administrator can add database volumes by using the DEFINE LOGVOLUME command, and extend the size of the database by using the EXTEND LOG command.

ANR4516EServer could not read sequential volume history information from any defined files.

Explanation: While attempting to read sequential volume history information from defined history files, the server finds that it cannot open any of the files defined in the server options file.

System Action: The server does not read volume history information. If the current server task requires this information, the task ends.

User Response: Examine error messages that may have been displayed prior to this message and correct any problems, if possible. Make sure that the server has proper authority to read from the defined volume history files. If you are doing a database restore, issue RESTORE DB DEVCLASS=VOL.

ANR4517ENo files have been defined for storing sequential volume history information - information cannot be read.

Explanation: The server is attempting to read from at least one of the volume history files defined in the server options file. Since no files were defined for this information the read operation fails.

System Action: Server operation ends.

User Response: You can restore the database specifying the volume names for each restore operation (in order) up to the desired point-in-time. If a volume history file is available, specify its name in the server options file and retry the operation.

ANR4518EVolume history file file name line line number does not have the proper format - read operation fails.

Explanation: The server is attempting to read from a volume history file and encounters a record that does not have the proper format.

System Action: Server operation terminates.

User Response: Examine the file specified to determine if the invalid record can be located and corrected. If the file is corrupted or does not contain valid volume history entries, it cannot be used for the desired operation.

ANR4549IDatabase dump command: A database dump is already in progress.

Explanation: This message is issued in response to a database dump command and indicates that a database dump cannot be started because a dump is already in progress.

System Action: Server operation continues. The requested database dump is not started.

User Response: Only one database dump can be started at one time. Use the QUERY PROCESS command to monitor the dump that is in progress. When completed, issue the database dump command to start another database dump if required.

ANR4550IFull database backup (process process ID) complete, number of database pages pages copied.

Explanation: A full database backup process has completed. The output volumes used in this backup may be used during a database restore operation.

System Action: None.

User Response: None.

ANR4551IIncremental database backup (process process ID) complete, number of database pages pages copied.

Explanation: An incremental database backup process has completed. The output volumes used in this backup may be used in conjunction with any preceding volumes in the backup series during a database restore operation.

System Action: None.

User Response: None.

ANR4552IFull database backup triggered; started as process process ID.

Explanation: A background process, triggered by the LOGFULLPCT parameter on a DEFINE DBBACKUPTRIGGER command, was started to back up the full contents of the database. The full database backup process is assigned the process ID shown.

System Action: The database backup process starts and server operation continues.

User Response: The administrator may query the status of the database backup process by using the QUERY PROCESS command, or cancel the process by using the CANCEL PROCESS command.

ANR4553IIncremental database backup triggered; started as process process ID.

Explanation: A background process, triggered by the LOGFULLPCT parameter on a DEFINE DBBACKUPTRIGGER command, was started to incrementally back up the contents of the database. The incremental database backup process was assigned the process ID shown.

System Action: The database backup process starts and server operation continues.

User Response: The administrator may query the status of the database backup process by using the QUERY PROCESS command, or cancel the process by using the CANCEL PROCESS command.

ANR4554IBacked up number of pages backed up of number of pages to back up in current operation database pages.

Explanation: Periodically, during a database backup, the server displays the number of pages backed up.

System Action: None.

User Response: None.

ANR4555IDatabase backup process process ID canceled.

Explanation: The database backup process was canceled by an administrator with the CANCEL PROCESS command.

System Action: The database backup process is ended.

User Response: None.

ANR4556WAttention: the database backup operation did not free sufficient recovery log space to lower utilization below the database backup trigger. The recovery log size may need to be increased.

Explanation: A database backup process has completed. The server is running in roll-forward mode and the recovery log utilization remains above that specified in the database backup trigger.

System Action: A database backup operation will be triggered. Unless this situation is corrected, database backups will be triggered rapidly, one after the other.

User Response: If a database backup operation does not free up enough recovery log space to reset utilization below the database backup trigger, the recovery log needs to be extended or the database backup trigger updated to a higher log full percentage.

ANR4560ITriggered database backup will be retried in number of seconds seconds.

Explanation: Because of a problem encountered during a triggered database backup, the current backup stops but will be retried after the time period shown.

System Action: The system waits for the specified period and then retries a database backup.

User Response: If possible, correct the condition that stopped the database backup. If the problem persists, contact your service representative.

ANR4561ITriggered database backup retry delay ended; checking database backup trigger criteria.

Explanation: Because a triggered database backup had been stopped due to a problem, the system waited before retrying. The retry wait period has ended, and the system can now retry the database backup.

System Action: Database backup begins.

User Response: None.

ANR4562IDatabase backup criteria is no longer met; triggered database backup canceled.

Explanation: Because a triggered database backup had been stopped due to a problem, the system waited before retrying. The retry wait period has ended, and the system determined that the criteria for triggering a database backup was no longer met.

System Action: The system waits until the database backup trigger criteria is met before triggering another database backup.

User Response: None.

ANR4563IUnable to trigger database backup - a database define, delete, extend, reduce, or backup operation is already in progress.

Explanation: A database backup was triggered, but a command that is modifying or backing up the database is already active.

System Action: The backup stops and the server waits for the retry period to expire and then tries the database backup again.

User Response: None.

ANR4564IUnable to trigger database backup - sufficient memory is not available.

Explanation: A database backup was triggered, but there is not enough server memory available.

System Action: The backup stops and the server waits for the retry period to expire and then tries the database backup again.

User Response: If necessary, make more memory available to the server.

ANR4565EUnable to trigger database backup - thread resource not available.

Explanation: A database backup was triggered, but the server cannot start a thread for the backup process.

System Action: The backup stops and the server waits for the retry period to expire and then tries the database backup again.

User Response: If the error persists, it may indicate a shortage of server memory. Allocate additional server memory.

ANR4570EDatabase backup/restore terminated - device class device class name not defined.

Explanation: During database backup or restore processing, an error occurred because the specified device class is not defined.

System Action: If the database backup was started with the BACKUP DB command, the database backup is ended and server operation continues. If the database backup was triggered automatically, the backup stops and the server waits for the retry period to expire and then tries the database backup again. A database restore is terminated.

User Response: For database backup, make sure the specified device class is defined. For database restore processing, make sure the device class has a definition in a device configuration file that is pointed to in the server options file.

ANR4571EDatabase backup/restore terminated - insufficient number of mount points available for removable media.

Explanation: During database backup or restore, the server cannot allocate sufficient mount points for the volumes required.

System Action: If the database backup was started with the BACKUP DB command, the database backup is ended and server operation continues. If the database backup was triggered automatically, the backup stops and the server waits for the retry period to expire and then tries the database backup again. A database restore is ended.

User Response: For database backup, make more mount points available if necessary. For database restore processing, make sure the device class has sufficient mount points defined in the device configuration information file that is pointed to in the server options file.

ANR4572EDatabase restore terminated - excessive read errors encountered.

Explanation: During database restore, read errors occur that prevent the restore from continuing.

System Action: Database restore processing stops.

User Response: Use a different device for the restore operation. If the problem persists, contact your service representative.

ANR4573EDatabase backup terminated - excessive write errors encountered.

Explanation: During database backup, write errors occur that prevent the backup from continuing.

System Action: If the database backup was started with the BACKUP DB command, the database backup is ended and server operation continues. If the database backup was triggered automatically, the backup stops and the server waits for the retry period to expire and then tries the database backup again.

User Response: If possible, determine and correct the cause of the write errors. If the problem cannot be corrected, contact your service representative.

ANR4574EDatabase backup/restore terminated - data transfer interrupted.

Explanation: During a database backup or restore operation, a data transfer operation has been interrupted and cannot be continued.

System Action: If the database backup was started with the BACKUP DB command, the database backup is ended and server operation continues. If the database backup was triggered automatically, the backup stops and the server waits for the retry period to expire and then tries the database backup again. A database restore is ended.

User Response: If possible, determine and correct the cause of the interruption. If the problem cannot be corrected, contact your service representative.

ANR4575EDatabase backup/restore terminated - sufficient recovery log space is not available.

Explanation: During a database backup or restore operation, the server runs out of recovery log space.

System Action: If the database backup was started with the BACKUP DB command, the database backup is ended and server operation continues. If the database backup was triggered automatically, the backup stops and the server waits for the retry period to expire and then tries the database backup again. A database restore is terminated.

User Response: For database backup, make more server recovery log space available, if necessary. For database restore, contact your service representative.

ANR4576EDatabase backup/restore terminated - sufficient database space is not available.

Explanation: During a database backup or restore operation, the server runs out of database space.

System Action: If the database backup was started with the BACKUP DB command, the database backup is ended and server operation continues. If the database backup was triggered automatically, the backup stops and the server waits for the retry period to expire and then tries the database backup again. The database restore process attempts to set the database capacity to the required capacity to hold the database being restored. If this fails, the restore operation is ended.

User Response: For database backup, make more server database space available, if necessary. For database restore, make sure that the size of the online database is at least the same capacity as the database being restored.

ANR4577EDatabase backup terminated - volume already in use.

Explanation: During a database backup operation, a volume cannot be used because it is already defined in a storage pool, or has been previously used by an export, a database dump, or a database backup operation (as recorded in the volume history) or is in use by another process.

System Action: If the database backup was started with the BACKUP DB command, the database backup is ended and server operation continues. If the database backup was triggered automatically, the backup stops and the server waits for the retry period to expire and then tries the database backup again.

User Response: Specify a volume that is not in use or defined in a storage pool, and that has not been previously used for an export, a database dump, or a database backup operation as recorded in the server volume history information. The QUERY VOLUME command may be used to display the names of volumes that are defined to server storage pools. The QUERY VOLHISTORY command may be used to display the names of volumes that have been used for export, database dump, or database backup operations.

ANR4578EDatabase backup/restore terminated - required volume was not mounted.

Explanation: During a database backup or restore operation, a required volume cannot be mounted, because the mount request was canceled.

System Action: If the database backup was started with the BACKUP DB command, the database backup is ended and server operation continues. If the database backup was triggered automatically, the backup stops and the server waits for the retry period to expire and then tries the database backup again. A database restore is terminated.

User Response: Issue the command again or wait for the server to retry the backup and make sure the necessary volumes are accessible. If you are restoring a database to a given date or doing a roll-forward restore, restart the entire restore operation. If you are restoring a single database backup with COMMIT=NO, reissue the restore command. If you are restoring a database backup with COMMIT=YES, restore the complete backup series from the beginning.

ANR4579EDatabase backup/restore terminated - thread resource not available.

Explanation: During a database backup or restore operation, the server cannot start a thread for the backup process.

System Action: If the database backup was started with the BACKUP DB command, the database backup is ended and server operation continues. If the database backup was triggered automatically, the backup stops and the server waits for the retry period to expire and then tries the database backup again. A database restore is terminated.

User Response: Retry the command or wait for the server to retry the backup if it was started by the backup trigger. If the error persists, it may indicate a shortage of server memory.

ANR4580EDatabase backup/restore terminated - insufficient memory available.

Explanation: During a database backup or restore operation, there was not enough server memory available.

System Action: If the database backup was started with the BACKUP DB command, the database backup is ended and server operation continues. If the database backup was triggered automatically, the backup stops and the server waits for the retry period to expire and then tries the database backup again. A database restore is terminated.

User Response: If necessary, make more memory available to the server.

ANR4581WDatabase backup/restore terminated - internal server error detected.

Explanation: During a database backup or restore operation, the server encounters an internal error.

System Action: If the database backup was started with the BACKUP DB command, the database backup is ended and server operation continues. If the database backup was triggered automatically, the backup stops and the server waits for the retry period to expire and then tries the database backup again. A database restore is terminated.

User Response: Contact your service representative.

ANR4582EDatabase restore terminated - volume cannot be used.

Explanation: During a database restore operation, a volume has been mounted but cannot be used.

System Action: The restore operation is terminated.

User Response: If a volume list was specified on the command, make sure the correct volume is being specified and mounted. If no volume list was specified, contact your service representative.

ANR4583EDatabase backup terminated - output media full and scratch media could not be mounted.

Explanation: During a database backup operation, an out-of-space condition occurred writing to the sequential media, and a scratch volume cannot be mounted.

System Action: The database backup is ended and server operation continues.

User Response: Reissue the command and specify additional volume names on the command, or specify SCRATCH=YES.

ANR4584EDatabase restore terminated - incomplete input volume list.

Explanation: The list of volumes needed for the restore operation was incomplete. At least one volume needed for the restore operation is missing from the end of the list.

System Action: The database restore is terminated.

User Response: If you are using a DSMSERV RESTORE DB command with the VOLUMENAMES parameter specified, verify that all the volumes within a database backup operation are included in the list. Ensure that all the volume names are specified in the correct sequential order. For a restore with COMMIT=NO, reissue the last restore command. For a restore with COMMIT=YES, restart the restore from the beginning of the full backup. If you are using a DSMSERV RESTORE DB command with the TODATE parameter specified, the server created a list of volumes needed for the restore operation. Examine the volume history files to try to determine the error or use a different volume history file if available. You can also restore the database by specifying the volume names for each restore operation up to the desired point in time.

ANR4590IBackup type backup series backup series number operation backup operation in series stream backup stream within operation (always 1) sequence backup volume sequence number in operation taken on date at time.

Explanation: During a DSMSERV DISPLAY DBBACKUPVOL command, the server displays the necessary information about a backup volume.

System Action: Processing continues for all volumes in the given volume list.

User Response: You can use this information to create a list of volumes for a database restore when a volume history backup file is not available.

ANR4600IProcessing volume history file file name.

Explanation: During a DSMSERV RESTORE DB command with the TODATE parameter specified, the server is processing the listed file in order to build a list of volumes needed for the restore operation.

System Action: None.

User Response: None.

ANR4601EIncomplete volume list found for TODATE date time - retrying.

Explanation: During a DSMSERV RESTORE DB command with the TODATE parameter specified, the server created a list of volumes needed for the restore operation, but the list was incomplete.

System Action: The server tries to build the list again using a different volume history file specified in the server options file. If no other volume history files are available, the server stops processing.

User Response: If the problem persists, examine the volume history files to try and determine the error. You can also restore the database by specifying the volume names for each restore operation up to the desired point in time.

ANR4602ENo volumes found for TODATE date time.

Explanation: No volumes were found in the volume history files that meet the date and time parameters specified.

System Action: The server does not process the command.

User Response: Reissue the command with a valid date and time.

ANR4610EDatabase volume DB volume name not found in current configuration.

Explanation: The command specified the name of a nonexistent database volume.

System Action: The server does not process the command.

User Response: Reissue the command with a valid database volume name.

ANR4611EUnable to restore database and roll forward updates - log mode was not previously set to ROLLFORWARD.

Explanation: The command specified that the database be restored and all updates rolled forward to the most current state. This process cannot be accomplished because the server recovery log mode was not set to ROLLFORWARD; therefore, no update information exists.

System Action: The server does not process the command.

User Response: Reissue the command and specify a point in time (TODATE/TOTIME) for restore.

ANR4612EUnable to restore database and roll forward updates.

Explanation: The command specified that the database be restored and all updates rolled forward to the most current state. This process cannot be accomplished because the internal list of volumes for the most recent full/incremental backup series is not available. Possible reasons include:

System Action: The server does not process the command.

User Response: Reissue the command and specify a point in time (TODATE/TOTIME) for restore.

ANR4619ISnapshot database backup series snapshot database backup series using device class device class.

Explanation: The device class used for the snapshot database backup is shown.

System Action: None.

User Response: None.

ANR4620IDatabase backup series Backup series operation backup operation device class device class.

Explanation: The device class used for the backup is shown.

System Action: None.

User Response: None.

ANR4621IDatabase backup device class device class.

Explanation: The device class for the backup is shown.

System Action: None.

User Response: None.

ANR4622I Volume volume sequence number in backup operation: volume name.

Explanation: The volume sequence and name for a full or an incremental database backup are shown.

System Action: None.

User Response: None.

ANR4623I Stream stream number in backup operation volume volume sequence number in backup stream: Volume name.

Explanation: The stream number, volume sequence and name for a full or an incremental database backup are shown.

System Action: None.

User Response: None.

ANR4630IStarting point-in-time database restore (commit).

Explanation: A point-in-time database restore with a specified list of volumes has started. When this restore is complete, the database will be committed to the point in time of this backup.

System Action: None.

User Response: If you inadvertently specified COMMIT=YES, restart the restore process from the beginning, starting with restoring the full backup (backup operation 0).

ANR4631IPoint-in-time database restore (commit) complete, restore date date time.

Explanation: A point-in-time database restore with a specified list of volumes is complete. The date shown is the date to which the database has been restored.

System Action: None.

User Response: None.

ANR4632IStarting point-in-time database restore (no commit).

Explanation: A point-in-time database restore with a specified list of volumes has started. When this restore is complete, the database will not yet be usable.

System Action: None.

User Response: To complete a database restore where a volume list is specified, specify COMMIT=YES on the command when restoring the last set of backup volumes. If you forgot to specify COMMIT=YES on the command, issue the last restore command again with COMMIT=YES.

ANR4633IPoint-in-time database restore (no commit) complete.

Explanation: A point-in-time database restore with a specified list of volumes is complete. The database is not yet usable.

System Action: None.

User Response: To complete a database restore where a volume list is specified, specify COMMIT=YES on the command when restoring the last set of backup volumes. If you forgot to specify COMMIT=YES on the command, issue the last restore command again with COMMIT=YES.

ANR4634IStarting point-in-time database restore to date date time.

Explanation: A point-in-time database restore with the TODATE parameter specified has begun. When this restore is complete, the database will be committed to the point in time of this backup.

System Action: None.

User Response: None.

ANR4635IPoint-in-time database restore complete, restore date date time.

Explanation: A point-in-time database restore with the TODATE parameter specified has completed. The database is committed to the point in time of this backup, which may be different than the TODATE specified. If this is the case, an additional message will be displayed.

System Action: None.

User Response: None.

ANR4636IStarting roll-forward database restore.

Explanation: A roll-forward database restore has begun. When this restore is complete, the database will be returned to its most recent state.

System Action: None.

User Response: None.

ANR4637IRoll-forward database restore complete.

Explanation: A roll-forward database restore has ended. All database backups in the most current backup series have been restored, and all updates to the database since the most recent backup have been rolled forward. The database has been returned to its most recent state.

System Action: None.

User Response: None.

ANR4638IRestore of backup series backup series number operation backup operation in series in progress.

Explanation: During a DSMSERV RESTORE DB, the server displays the backup series and operation currently being restored.

System Action: None.

User Response: None.

ANR4639IRestored number of pages restored of number of pages to restore from current backup operation database pages.

Explanation: Periodically, during a DSMSERV RESTORE DB, the server displays the number of pages restored from the current backup being restored.

System Action: None.

User Response: None.

ANR4640IRestored number of database pages pages from backup series backup series number operation backup operation in series.

Explanation: At the end of each restored backup, the server displays the number of database pages restored.

System Action: None.

User Response: None.

ANR4641ISequential media log redo pass in progress.

Explanation: During a DSMSERV RESTORE DB, the process of committing incomplete database updates has begun.

System Action: None.

User Response: None.

ANR4642ISequential media log undo pass in progress.

Explanation: During a DSMSERV RESTORE DB, the process of rolling back incomplete transactions has begun.

System Action: None.

User Response: None.

ANR4643IProcessed number of log records log records.

Explanation: Periodically, during the commit of a point-in-time restore or while rolling forward updates during a roll forward restore, the server displays the number of log records processed.

System Action: None.

User Response: None.

ANR4644IA full backup will be required for the next database backup operation.

Explanation: During a point-in-time restore of a database, this message is displayed to notify the administrator that the next database backup taken during normal operation must be a full backup. This process is normal for point-in-time database restores.

System Action: None.

User Response: At the next server restart, do a full database backup. A full database backup is started automatically if a DBBACKUPTRIGGER is defined.

ANR4645IThe restore date reflects the most recent backup available up to the specified TODATE.

Explanation: During a DSMSERV RESTORE DB with the TODATE parameter, the date of the restored backup was not identical to the date specified on the command. The backup series that was restored is the most recent backup series up to and including the specified date.

System Action: None.

User Response: Make sure the date of the restored database is satisfactory. If it is not, restore the database again by specifying a different TODATE or by restoring individual database backups.

ANR4646IDatabase capacity required for restore is number of megabytes megabytes.

Explanation: During a point-in-time restore of a database, the size of the database being restored is displayed. The available capacity of the online database volumes must be at least this size.

System Action: None.

User Response: None.

ANR4647IDatabase available capacity is number of megabytes megabytes.

Explanation: During a point-in-time restore of a database, the available capacity of the online database volumes is displayed. This capacity must be as large as the size of the database being restored.

System Action: If the available capacity of the online database volumes is not at least this size, the restore cannot continue.

User Response: If the available capacity of the online database is not sufficient, reinstall the server with the required database size, and try the restore operation again.

ANR4648IExtending database assigned capacity to number of megabytes megabytes.

Explanation: During a point-in-time restore of a database, the assigned capacity of the online database is smaller than that of the database being restored. However, the available capacity of the online database volumes is sufficient for restore.

System Action: The assigned capacity of the online database is extended to the size required for restore.

User Response: None.

ANR4649IReducing database assigned capacity to number of megabytes megabytes.

Explanation: During a point-in-time restore of a database, the assigned capacity of the online database is larger than that of the database being restored.

System Action: The assigned capacity of the online database is reduced to the size required for restore.

User Response: None.

ANR4650ERestore of backup series current series operation current operation is not in sequence; last restored backup was series previous series operation previous operation.

Explanation: During a DSMSERV RESTORE DB, a backup volume was mounted that is not in the correct sequence.

System Action: The database restore is terminated.

User Response: Ensure volume names are specified in the correct sequential order. For a restore with COMMIT=NO, reissue the last restore command. For a restore with COMMIT=YES, restart the restore from the beginning of the full backup.

ANR4651ERestore of backup series current series operation current operation is not in sequence; backup is part of another log epoch.

Explanation: During a DSMSERV RESTORE DB, a backup volume was mounted that is not in the correct sequence. The current backup operation cannot be restored in this series because it belongs to the same backup series from another point in time.

System Action: The database restore is terminated.

User Response: Restart the database restore from the beginning of the full backup. Omit all backups from the offending backup and later from the restore.

ANR4657ESNMP: Failed to connect to server at address address, port port.

Explanation: The SNMP client was attempting to run a session with the server at the indicated address and port number in response to an SNMP Get Request, which causes a Server Script to be run. The subagent failed to connect to the server.

System Action: The SNMP subagent ends this attempt to run the script and continues operation.

User Response: Ensure that the indicated server is up and able to initiate admin clients using the TCP/IP protocol.

ANR4659ESNMP: Communications failure: bad verb received (verb type).

Explanation: The SNMP client encountered an invalid communications verb during a session with the server and is not able to continue processing the session.

System Action: The SNMP session ends and subagent operation continues.

User Response: Contact your service representative.

ANR4660IConnected to SNMP subagent at SNMP subagent address on port port number.

Explanation: The server has successfully connected to the SNMP subagent at the indicated address and port.

System Action: The server will now register with the subagent.

User Response: None.

ANR4661ESNMP communication with the subagent failed because a thread resource was not available.

Explanation: The server could not continue with SNMP communication to the SNMP subagent because sufficient memory is not available for starting additional processes on the server.

System Action: The server discontinues SNMP processing and server operation continues.

User Response: Allocate additional storage to the server. For details, issue HELP MEMORY to display the information online or see "Appendix A. Allocating Additional Server Memory".

ANR4662WFailure sending message to SNMP subagent.

Explanation: The server experienced an error return code from TCP/IP while sending to the SNMP subagent. This message is also issued when the SNMP subagent has an error sending a verb to the server when acting as an SNMP client. This may be a normal event if either side of the connection is abruptly ended, as in the case of terminating the subagent program. The error is reflected in another message for TCP/IP which further describes the error.

System Action: The session is ended. Server operation continues. If a message is being forwarded to an SNMP managing node, the message is not sent. If a heartbeat message was being sent to the subagent, this heartbeat message is lost and the server attempts to re-start its session with the SNMP subagent.

User Response: If the session is ended as a result of intentionally stopping either the subagent, no response is required. Otherwise, ensure that the TCP/IP protocol stack is functioning by using the tools that come with the particular TCP/IP suite on the platform in use.

ANR4663WFailure receiving message from SNMP subagent.

Explanation: The server experienced an error return code from TCP/IP while receiving data from the SNMP subagent. This may be a normal event if either side of the connection is abruptly ended, as in the case of terminating the subagent program. The error is reflected in another message for TCP/IP which further describes the error.

System Action: The session is ended. Server operation continues. If a heartbeat message was being sent to the subagent, this heartbeat message is lost and the server attempts to re-start its session with the SNMP subagent. If the server was attempting to register to the SNMP subagent, heartbeat messaging will be disabled until the server is re-started.

User Response: If the session is ended as a result of intentionally stopping either the subagent, no response is required. Otherwise, ensure that the TCP/IP protocol stack is functioning by using the tools that come with the particular TCP/IP suite on the platform in use.

ANR4664WFailure in registering with SNMP subagent.

Explanation: The server experienced a problem while attempting to register with the SNMP subagent. This may be due to problems with communication or the SNMP subagent being unavailable.

System Action: Heartbeat messaging will be disabled until the server is re-started.

User Response: Ensure that the subagent is running and that the TCP/IP protocol stack is functioning by using the tools that come with the particular TCP/IP suite on the platform in use.

ANR4665WFailure re-trying registration with SNMP subagent.

Explanation: The server experienced a problem while attempting to re-register with the SNMP subagent after losing contact. This may be due to problems with communication or the SNMP subagent being unavailable.

System Action: Registration is re-tried for a number of attempts before giving up.

User Response: Ensure that the subagent is running and that the TCP/IP protocol stack is functioning by using the tools that come with the particular TCP/IP suite on the platform in use.

ANR4666WFailure sending heartbeat message to SNMP subagent.

Explanation: The server experienced a problem while attempting to send a heartbeat message to the SNMP subagent. This may be due to problems with communication or the SNMP subagent being unavailable.

System Action: The server will attempt to contact the SNMP subagent again and re-synchronize.

User Response: Ensure that the subagent is running and that the TCP/IP protocol stack is functioning by using the tools that come with the particular TCP/IP suite on the platform in use.

ANR4667WFailure re-trying heartbeat message to SNMP subagent.

Explanation: The server experienced a problem while attempting to send a heartbeat message to the SNMP subagent. This may be due to problems with communication or the SNMP subagent being unavailable.

System Action: The server attempted to contact the SNMP subagent again and re-synchronize, but this too failed. Heartbeat functions are disabled until the server is re-started.

User Response: Ensure that the subagent is running and that the TCP/IP protocol stack is functioning by using the tools that come with the particular TCP/IP suite on the platform in use. Re-start the server if the heartbeat function is required.

ANR4668IConnection successfully re-established with SNMP subagent.

Explanation: The server experienced a problem while attempting to send a heartbeat message to the SNMP subagent.

System Action: The server was able to successfully resynchronize with the SNMP subagent.

User Response: None.

ANR4669WHeartbeat message was not accepted by SNMP subagent.

Explanation: The server experienced a problem while attempting to send a heartbeat message to the SNMP subagent. The SNMP subagent was unable to accept the heartbeat message. If the subagent was stopped and re-started, this is a normal message.

System Action: The server will attempt to contact the SNMP subagent again and re-synchronize.

User Response: Ensure that the subagent is running and that the TCP/IP protocol stack is functioning by using the tools that come with the particular TCP/IP suite on the platform in use.

ANR4670WFailure in opening session with SNMP subagent.

Explanation: The server experienced a problem while attempting to open a session with the SNMP subagent.

System Action: Processing continues. Heartbeat and message forwarding function will not be available.

User Response: Ensure that the subagent is running and that the TCP/IP protocol stack is functioning by using the tools that come with the particular TCP/IP suite on the platform in use. If heartbeat and message forwarding functions are required, re-start the server.

ANR4671WSNMP subagent did not accept registration of this server.

Explanation: The server experienced a problem while attempting to open a session with the SNMP subagent. The subagent is available but disallowed registration by this server.

System Action: Processing continues. Heartbeat and message forwarding function will not be available.

User Response: It may be necessary to stop the subagent and re-start it. Then stop the server and re-start it if heartbeat and message forwarding functions are required.

ANR4672WSNMP message forwarding to the SNMP subagent was not started because a thread resource was not available.

Explanation: The server could not continue with SNMP communication to the SNMP subagent for message forwarding because sufficient memory is not available for starting additional processes on the server.

System Action: The server discontinues SNMP message processing and server operation continues.

User Response: Allocate additional storage to the server. For details, issue HELP MEMORY to display the information online or see "Appendix A. Allocating Additional Server Memory".

ANR4673EInsufficient memory for subagent initialization (the portion of initialization where the allocation of memory failed).

Explanation: The SNMP subagent could not initialize due to the inability to obtain the required memory.

System Action: Initialization of the subagent fails.

User Response: Allocate additonal storage to the subagent.

ANR4674EError starting DPI thread - Return code: Return code received from called routine.

Explanation: The SNMP subagent could not start the DPI thread.

System Action: Initialization of the subagent fails.

User Response: Contact your service representative.

ANR4675EServer/subagent protocol violation - invalid (where the protocol breakdown occurred).

Explanation: The SNMP subagent received an unexpected request from the server.

System Action: The subagent will stop processing requests from the server sending the invalid requests.

User Response: Contact your service representative.

ANR4676EUnable to register another server.

Explanation: The SNMP subagent received a request to register a new server and was unable to allocate the memory necessary to register the new server.

System Action: The subagent will not register the new server.

User Response: Contact your service representative.

ANR4677ISession established with server name: The name of the registered server..

Explanation: The SNMP subagent completed the registration of the identified server.

System Action: The subagent will wait for additional requests from the server.

User Response: None.

ANR4678ISession closed with server name: The name of the deregistered server..

Explanation: The SNMP subagent completed the deregistration of the identified server.

System Action: None.

User Response: None.

ANR4679WMessages are no longer being forwarded to the SNMP subagent.

Explanation: The server has encountered multiple errors in forwarding messages to the SNMP subagent. Messages are no longer being forwarded.

System Action: The server continues operating, but messages are no longer being forwarded.

User Response: Message forwarding can be re-initialized by either stopping the server and re-starting it. Message forwarding will also be re-started if the heartbeat function is in use and the server re-synchronizes with the subagent. This re-synchronization occurs if the subagent, dsmsnmp, is stopped for longer than a single heartbeat interval (the heartbeat interval is a server option and appears in the output of the QUERY OPT command) and then restarted.

ANR4680IDPI subagent (The subagent name.): "Connected" or "reconnected", ready to receive requests.

Explanation: The subagent has successfully connected or reconnected to the SNMP agent.

System Action: The subagent is ready to receive requests from servers.

User Response: None.

ANR4681WConnect to SNMP agent failed, will keep trying.

Explanation: The subagent has failed in an attempt to connect to the SNMP agent.

System Action: The subagent keeps retrying the connection.

User Response: Make sure that the SNMP daemon is up, running and correctly configured.

ANR4682WA SNMP agent connection error occurred. Attempting to re-establish connection.

Explanation: An error has occurred in the communication between the subagent and the SNMP agent.

System Action: The subagent will attempt to reconnect.

User Response: Make sure that the SNMP daemon is up, running and correctly configured.

ANR4683EUnable to open trace file 'file name'.

Explanation: An error occurred while opening the file for writing trace data.

System Action: The subagent continues operation without tracing.

User Response: Ensure there is adequate space on the drive from which you are running the subagent and retry the program.

ANR4684ETrap request failed - RC: Return code from the trap request. Server index: Server index number..

Explanation: An error occurred while attempting to process a trap request from a server. data.

System Action: The subagent processing continues.

User Response: Make sure that the SNMP daemon is up, running and correctly configured.

ANR4685EInsufficient memory for subagent initialization.

Explanation: The SNMP subagent could not initialize due to the inability to obtain the required memory.

System Action: Initialization of the subagent fails.

User Response: Allocate additional memory to the subagent.

ANR4686EInsufficient memory for subagent trace initialization.

Explanation: The SNMP subagent trace could not initialize due to the inability to obtain the required memory.

System Action: Initialization of the subagent fails.

User Response: Allocate additional memory to the subagent.

ANR4687EServer/subagent protocol violation - expecting registration request. Received request: The value of the request that was received.

Explanation: The SNMP subagent was expecting a registration request. It actually received something other than a registration request.

System Action: The subagent will stop processing requests from the server sending the invalid requests.

User Response: Contact your service representative.

ANR4688EServer/subagent protocol violation - incorrect request header version.

Explanation: The SNMP subagent received a request from a server that was not at the same maintenance level as the subagent.

System Action: The subagent will stop processing requests from the server sending the invalid requests.

User Response: Ensure the server and subagent are at the same maintenance level. If they are, contact your service representative.

ANR4689EInvalid request type received (The value of the request that was received.).

Explanation: The SNMP subagent received an unexpected request from the server.

System Action: The subagent will stop processing requests from the server sending the invalid requests.

User Response: Contact your service representative.

ANR4690EUnexpected request type (The value of the request that was received.) in trap data header.

Explanation: The SNMP subagent received an invalid trap request from a server.

System Action: The subagent will stop processing requests from the server sending the invalid requests.

User Response: Contact your service representative.

ANR4691IDPI subagent (The subagent name.): connected, ready to receive requests.

Explanation: The subagent has successfully connected to the SNMP agent.

System Action: The subagent is ready to receive request from servers.

User Response: None.

ANR4692IDPI subagent (The subagent name.): reconnected, ready to receive requests.

Explanation: The subagent has successfully reconnected to the SNMP agent.

System Action: The subagent is ready to receive request from servers.

User Response: None.

ANR4693IInterface Driver information will be loaded in quiet mode: Only warning and error messages will be displayed.

Explanation: The server is loading information needed for the Administrative WEB Interface. To minimize message traffic, only error and warning messages will be displayed.

System Action: When the command completes, WEB administrative information will be loaded into the server.

User Response: None.

ANR4694ESNMP Subagent Port Confirmation Has Failed.

Explanation: The server was communicating configuration data to the SNMP subagent. An error occurred in the exchange. The server could not communicate interface information to the subagent.

System Action: The server continues operation. The SNMP administrative interface is inoperative.

User Response: The most likely cause of this problem is a temporary network failure. The server should be re-started to retry the connection to the SNMP subagent. If this problem occurs repeatedly, please contact you service representative.

ANR4695ESNMP: Communications Failure in Receiving "verb type" verb.

Explanation: The SNMP client encountered a communications error in using the verb type verb to transfer information to or from the server and an SNMP client.

System Action: The SNMP session ends and server operation continues.

User Response: This may not be a problem if the SNMP subagent was terminated while the session was in progress. Otherwise, ensure that TCP/IP communications is running normally.

ANR4697ESNMP: Failed to authenticate to server at address address, port port.

Explanation: The SNMP client was attempting to run a session with the server at the indicated address and port number in response to an SNMP Get Request, which causes a Server Script to be run. The subagent connected to the indicated server, but failed in authentication.

System Action: The SNMP subagent ends this attempt to run the script and continues operation.

User Response: Ensure that the indicated server has an an administrative id of SNMPADMIN and that this adminstrative id has sufficient authority to run the script and commands it contains.

ANR4698ESNMP: Communications Failure in Sending "verb type" verb (command).

Explanation: The SNMP client encountered a communications error in using the verb type verb to issue command command.

System Action: The SNMP client session ends and subagent operation continues.

User Response: Contact your service representative.

ANR4699ESNMP: Receive Buffer overflow.

Explanation: The SNMP client encountered an overflow error in transferring information to or from the server.

System Action: The SNMP client session ends and subagent operation continues.

User Response: Contact your service representative.

ANR4700IThe server move batch size has been set to new batch size. Move operations that start after this point will use the new value.

Explanation: A SETOPT commmand was used to set the value for the move batch size value. This setting determines the maximum number of files that are moved on the server in one database transaction, dependent also on the setting for the move size thrshold. The setting influences file movement for server migration, reclmation, storage pool backup, and move data operations.

System Action: The server uses this new setting for move operations that are started after this message is issued.

User Response: Contact your service representative.

ANR4701IThe server move size threshold has been set to new threshold. Move operations that start after this point will use the new value.

Explanation: A SETOPT commmand was used to set the value for the move size threshold value. This setting determines the maximum number of megabytes that are moved on the server in one database transaction, dependent also on the setting for the move batch size. The setting influences file movement for server migration, reclmation, storage pool backup, and move data operations.

System Action: The server uses this new setting for move operations that are started after this message is issued.

User Response: Contact your service representative.

ANR4702IThe server transaction group maximum has been set to new value. Client sessions that are started after this point will use the new value.

Explanation: A SETOPT commmand was used to set the value for the maxmimum number of files that can be sent from the client in a single database transaction.

System Action: The server uses this new setting for client sessions that are started after this message is issued.

User Response: Contact your service representative.

ANR4703EInvalid key ring filename Key Ring Filename

Explanation: The key ring filename specified did not contain the .kyr extention.

System Action: None.

User Response: Rename your key ring filename to contain the .kyr extention. Reexcute the command with the new filename.

ANR4704IKey ring filename and password have been set. Restart the server to use the new settings

Explanation: The key ring filename have been set to the new value specified in the DEFINE KEYRING command.

System Action: None.

User Response: Restart the server to use the new key ring information.

ANR4705IThe server IDL definitions have not been installed. These definitions will need to be installed for the Web Administrator interface to work.

Explanation: The server attempted to query the server IDL interface and found no definitions defined. Because of this error the HTTP engine returns a 404 not found message.

System Action: None.

User Response: If you would like to use the server web administrator interface you will need to:

  1. Halt the server.
  2. Issue the command DSMSERV RUNFILE dsmserv.idl. For AS/400 command see next step.
  3. For AS/400, issue the command STRSVRADSM SVRMODE(*PRPWEB).
  4. Restart the server.

ANR4706WUnable to open file Filename to satisfy web session Session ID.

Explanation: A web browser requested a file and the server could not find the file on the local file system. Special note, some files requested from the server are not vaild and are caused by a browser error. For example, a request for CommandLineBeanInfo.class is not a valid file request. However, a request of a GIF image or HTML page should not produce this error.

System Action: None.

User Response: Verify that permission for the file are set correctly and file exists.

ANR4707EImport/Loaddb command operation terminated - incomplete input volume list.

Explanation: The list of volumes needed to process the command was incomplete. At least one volume needed for the operation is missing from the end of the list.

System Action: The command operation is ended.

User Response: Issue the command again and make sure the necessary volumes are included in the volume list.

ANR4708INative SSL support has been disabled, please use the web proxy.

Explanation: Starting in this version of this product native Secure Socket Layer support has been removed. This feature has been replace with the web proxy. Support for non-secure http request (COMMMETHOD HTTP) has not been disabled.

System Action: None.

User Response:

  1. Remove COMMMETHOD HTTPS from your option file.
  2. Install and configure the web proxy. See Quick Start Appendices for more information on how to install and configure the web proxy.

ANR4709WIntervention required to mount volume Volume Name on Library Manager Server Server Name.

Explanation: A volume mount is awaiting operator intervention on the specified library manager server.

System Action: The volume mount operation waits for operator intervention.

User Response: Refer to the server consol and/ir activity log on the named library manaer server to determine the action that needs to be performed to complete the mount operation.

ANR4710WLibrary manager Server Name could not be contacted to control library Library Name.

Explanation: The specified library manager server could not be contacted for control of the named library.

System Action: The server will continue to contact the named library manager server. Volume mounts in the library will fail until communication is successful.

User Response: Determine why the named server is not running or why the network prevents communication with te named server.

ANR4712ECommand: The DEVCLASS parameter is only valid for volume history types DBBACKUP or DBSNAPSHOT.

Explanation: The command failed because an invalid volume history type was specified for the TYPE= parameter.

System Action: The command fails, and server operation continues.

User Response: Re-issue the command and specify a valid type value.

ANR4980IAuditing Interface Driver definitions.

Explanation: The server is beginning an audit of the definitions for Web interface.

System Action: The server will audit all definitions for the Web interface and report any problems.

User Response: None.

ANR4981EInterface Driver audit completed - Inconsistencies were found.

Explanation: The server found errors during the audit of the definitions for Web interface.

System Action: The Web Interface is not correctly installed. The Web Admin will not work correctly, but the server may be run without any problems.

User Response: Insure you are using the correct IDL file for the server level you are running. Examine error messages that may have been displayed before and/or after this message and correct any problems, if possible. If the cause of this can not be determined or resolved, contact your support representative.

ANR4982IInterface Driver audit completed - definitions are consistent.

Explanation: The server successfully completed the installation of the definitions for the Web interface.

System Action: The Web Interface is now installed. The server may be run without any problems.

User Response: None.

ANR4983IAuditing Interface Driver Groups.

Explanation: The server is auditing the driver groups.

System Action: The server will audit the driver groups and proceed to the next step.

User Response: None.

ANR4984EError description

Explanation: The server found errors during the audit of the definitions for Web interface.

System Action: The audit will fail.

User Response: Insure you are using the correct IDL file for the server level you are running. Examine error messages that may have been displayed before this message and correct any problems, if possible. If the cause of this can not be determined or resolved, contact your support representative. If you contact your support representative, the entire text of this message should be reported.

ANR4985IAuditing Interface Driver Group Members.

Explanation: The server is auditing the driver group members.

System Action: The server will audit the driver group members and proceed to the next step.

User Response: None.

ANR4986IAuditing Interface Driver Classes.

Explanation: The server is auditing the driver classes.

System Action: The server will audit the driver classes and proceed to the next step.

User Response: None.

ANR4987EAudit processing failed: sufficient memory is not available for processing.

Explanation: At RUNFILE time, the server is unable to process the IDL data due to insufficient memory.

System Action: Server runfile stops.

User Response: Restart the server runfile process with more memory available.

ANR4988IAuditing Interface Driver Complex Class containers.

Explanation: The server is auditing the driver class containers.

System Action: The server will audit the driver class containers and proceed to the next step.

User Response: None.

ANR4989IAuditing Interface Driver Operations.

Explanation: The server is auditing the driver operations.

System Action: The server will audit the driver operations and proceed to the next step.

User Response: None.

ANR4990IAuditing Interface Driver Operation Parameters.

Explanation: The server is auditing the driver operation parameters.

System Action: The server will audit the driver operation parameters and proceed to the next step.

User Response: None.

ANR4991IAuditing Interface Driver Tasks.

Explanation: The server is auditing the driver tasks.

System Action: The server will audit the driver tasks and proceed to the next step.

User Response: None.

ANR4992IAuditing Interface Driver Task Members.

Explanation: The server is auditing the driver task members.

System Action: The server will audit the driver task members and proceed to the next step.

User Response: None.

ANR5000E (S/390)Unable to load tape deletion exit.

Explanation: The tape deletion exit module specified in the options file cannot be loaded.

System Action: Server operation continues.

User Response: Ensure that the tape deletion exit module is in the system linklist or in the JOBLIB/STEPLIB for the server.

ANR5010E (S/390)Unable to initialize disk driver - internal error code from IUCV.

Explanation: The server's disk driver cannot be initialized because the error code has been received from the IUCV DECLARE BUFFER function.

System Action: Server initialization fails.

User Response: For a description of the reported error code, refer to the IUCV documentation in the CP Programming Services publication for your specific operating system.

ANR5011E (S/390)Unable to open disk vaddr - invalid virtual device address.

Explanation: A disk cannot be opened for processing because the specified virtual address is beyond the supported range. Virtual addresses must be specified in the range 0001 to FFFF.

System Action: Server operation continues.

User Response: Specify a valid virtual address.

ANR5012E (S/390)Unable to open disk vaddr - error code received from FILEDEF.

Explanation: A disk cannot be opened for processing because the error code has been received from the FILEDEF command. The server enters one FILEDEF command per open disk so that the CMS DISKID function may be used.

System Action: Server operation continues.

User Response: For a description of the FILEDEF error code, refer to the CMS Command Reference publication for your operating system.

ANR5013E (S/390)Unable to open disk vaddr - virtual disk not attached.

Explanation: A disk cannot be opened because the virtual disk is not attached to the server's virtual machine.

System Action: Server operation continues.

User Response: Ensure that the VM DASD volume containing the disk is online, and that the disk is properly linked to the server's virtual machine.

ANR5014E (S/390)Unable to open disk vaddr - error code received from DISKID.

Explanation: A disk cannot be opened for processing because the error code has been received from the DISKID function.

System Action: Server operation continues.

User Response: For a description of the DISKID error code, refer to the CMS Command Reference publication for your operating system.

ANR5015E (S/390)Unable to open disk vaddr - internal error code connecting to Block I/O System Service.

Explanation: A disk cannot be opened for processing because the IUCV CONNECT error code is received when attempting to connect to the CP DASD Block I/O System Service.

System Action: Server operation continues.

User Response: For a description of the IUCV CONNECT error code, refer to the IUCV documentation in the CP Programming Services publication for your specific operating system.

ANR5016E (S/390)Unable to open disk vaddr - device type not supported.

Explanation: A disk cannot be opened for processing because its device type is not supported.

System Action: Server operation continues.

User Response: Use only the disk devices supported by the CP DASD Block I/O System Service.

ANR5017E (S/390)Unable to open disk vaddr - block size not supported.

Explanation: A disk cannot be opened for processing because its formatted block size is not supported.

System Action: Server operation continues.

User Response: Use only the disks formatted with block sizes supported by the CP DASD Block I/O System Service.

ANR5018E (S/390)Unable to open disk vaddr - IUCV path already exists to device.

Explanation: A disk cannot be opened because a path already exists for this device to the CP DASD Block I/O System Service.

System Action: Server operation continues.

User Response: Contact your service representative.

ANR5019E (S/390)Unable to open disk vaddr - internal error code from Block I/O System Service.

Explanation: A disk cannot be opened for processing because the connection to the CP DASD Block I/O System Service has been severed with error code.

System Action: Server operation continues.

User Response: For a description of the severed error code, refer to the documentation for the CP DASD Block I/O System Service in the CP Programming Services publication for your specific operating system.

ANR5020E (S/390)Unable to open disk vaddr - device is read-only.

Explanation: A disk cannot be opened for processing because it is accessible only as a read-only device. All server disks must be accessible in read/write mode.

System Action: Server operation continues.

User Response: Ensure that the disk is properly linked in read/write mode.

ANR5021E (S/390)Unable to perform I/O to disk vaddr - internal error code on IUCV send.

Explanation: The IUCV SEND error code is received when the server attempts to perform I/O to a disk.

System Action: Server operation continues.

User Response: For a description of the IUCV SEND error code, refer to the IUCV documentation in the CP Programming Services publication for your specific operating system.

ANR5022E (S/390)Unable to perform I/O to disk vaddr - permanent error writing to block block.

Explanation: The server encounters a permanent error while writing to the specified disk and block.

System Action: Server operation continues.

User Response: Reformat or replace the disk.

ANR5023E (S/390)Unable to perform I/O to disk vaddr - permanent error reading from block block.

Explanation: The server encounters a permanent error while reading from the specified disk and block.

System Action: Server operation continues.

User Response: Reformat or replace the disk.

ANR5024E (S/390)Unable to perform I/O to disk vaddr - format error detected.

Explanation: The server encounters a format error on the specified disk.

System Action: Server operation continues.

User Response: Reformat the disk by using the DSMDISK exec.

ANR5025E (S/390)Disk vaddr has been reset and is no longer available.

Explanation: A disk is reset during operation because a CP RESET or DETACH command has been entered from the server's console.

System Action: The disk is marked off-line.

User Response: Ensure that the disk is properly reattached to the server's virtual machine.

ANR5026E (S/390)Open of data set dsn failed, return code rc, reason code reason.

Explanation: Data set dsn cannot be opened.

System Action: Server operation continues.

User Response: Verify that dsn is a VSAM linear data set. If dsn is a valid VSAM linear data set, contact your service representative.

ANR5027E (S/390)Open of DDNAME ddname failed, insufficient memory.

Explanation: The server is unable to open ddname ddname due to a lack of storage.

System Action: Server operation continues.

User Response: Increase the region for the server or lower the MAXSESSIONS parameter in the server options file. There are three ways to do this:

  1. On VM, increase the size of the server's virtual machine. This requires that the default storage size be updated in the server's CP directory entry.
  2. On MVS, increase the size of the REGION parameter on the JOB or EXEC statement of the JCL used to start the server.
  3. Reduce the maximum number of client sessions permitted. To do this, edit the server options file and reduce the value specified for the MAXSESSIONS statement. Note that each client session causes an additional 64KB of memory to be allocated.
  4. Decrease the amount of space allocated to the server's database buffer pool. To do this, edit the server options file and reduce the value specified for the BUFPOOLSIZE statement. Note that each buffer pool page causes an additional 4 KB of memory to be allocated.

Note that the server must be shut down (with the HALT command) before changes can be made to the server options file.

ANR5028E (S/390)Open of data set dsn failed; zero pages in data set.

Explanation: The VSAM linear data set dsn has no space. This message appears when:

System Action: Server operation continues.

User Response: Run the dsmfmt utility, or reallocate the VSAM linear data set as appropriate.

ANR5030E (S/390)Dynamic allocation of data set dsn failed, return code rc, error code error-code, info code info-code.

Explanation: The dynamic allocation of data set dsn fails. The return code rc, error code error-code and information code info-code, are in decimal and can be found in the Dynamic Allocation section of MVS/ESA Programming: Authorized Assembler Services Guide.

System Action: Server operation continues.

User Response: Ensure that the data set dsn is available for allocation by the server.

ANR5032E (S/390)Unable to free DDNAME dsn, return code rc, error code error-code, info code info-code.

Explanation: The dynamic deallocation of data set dsn fails. The return code rc, error code error-code and information code info-code are in decimal and can be found in the Dynamic Allocation section of MVS/ESA Programming: Authorized Assembler Services Guide.

System Action: Server operation continues.

User Response: Contact your service representative.

ANR5033E (S/390)Close of ddname dsn failed, return code rc, reason code reason.

Explanation: Data set dsn cannot be closed.

System Action: Server operation continues.

User Response: Verify that dsn is a VSAM linear data set. If dsn is a valid VSAM linear data set, contact your service representative.

ANR5034E (S/390)Unable to allocate processor for ddname dsn.

Explanation: The number of simultaneous tapes supported by the server has been exceeded.

System Action: Server operation continues.

User Response: Contact your service representative for a fix that allows additional tapes.

ANR5035E (S/390)Dynamic allocation of tape unit unit failed, return code rc, error code error-code, info code info-code.

Explanation: The dynamic allocation of a tape unit unit fails. The return code rc, error code error-code, and information code info-code are in decimal and can be found in the Dynamic Allocation section of MVS/ESA Programming: Authorized Assembler Services Guide.

System Action: Server operation continues.

User Response: Examine the MVS messages preceding this message. They should explain the cause of the allocation problem; otherwise, contact your service representative.

ANR5036E (S/390)Open of tape unit unit (ddname ddname) failed, return code rc.

Explanation: Open of ddname ddname fails.

System Action: Server operation continues.

User Response: Examine the MVS messages preceding this message. The ANR1401W message and the volume name will explain the problem. If necessary, contact your service representative.

ANR5037E (S/390)Unable to acquire processor, dsn.

Explanation: The number of simultaneous tapes supported by the server has been exceeded.

System Action: Server operation continues.

User Response: Contact your service representative for a fix that allows additional tapes.

ANR5039E (S/390)Unable to open disk vaddr - IUCV MAXCONN value exceeded.

Explanation: The disk at virtual address vaddr cannot be opened due to a lack of IUCV connections.

System Action: Server operation continues.

User Response: Increase the IUCV MAXCONN value in the server CP directory entry and restart the server.

ANR5040E (S/390)Data set name dsn contains qualifier qual that is longer than 8 characters.

Explanation: Data set dsn qualifier qual is too long. Data set qualifiers must be 1 to 8 characters long.

System Action: Server operation continues.

User Response: Specify data set name qualifiers with a maximum of 8 characters.

ANR5041E (S/390)Data set name dsn contains a null qualifier.

Explanation: Data set dsn contains null qualifier (either 2 consecutive periods or an ending period without a subsequent qualifier). Data set qualifiers must be 1 to 8 characters long.

System Action: Server operation continues.

User Response: Specify valid data set name qualifiers.

ANR5042E (S/390)Data set name dsn contains qualifier qual that does not begin, with an alpha character.

Explanation: Data set dsn qualifier qual does not begin with an alpha character. Data set qualifiers must start with an alpha character.

System Action: Server operation continues.

User Response: Specify data set name qualifiers that begin with an alpha character.

ANR5043E (S/390)Data set name dsn contains qualifier qual that contains a character that is not alphanumeric.

Explanation: Data set dsn qualifier qual contains a character that is not alphanumeric. Data set qualifiers must contain only alphanumeric characters.

System Action: Server operation continues.

User Response: Specify data set name qualifiers that contain only alphanumeric characters.

ANR5044E (S/390)Cannot format data set dsn. Data set is not empty.

Explanation: The server will not format dsn because it is not empty.

System Action: Server operation continues.

User Response: Verify that dsn is the correct data set you'd like to format. The server formats empty data sets only.

ANR5045E (S/390)Failed to open dataset dsn. Error detected with the VSAM high-used (VSAM high-used value) or high-allocated (VSAM high-allocated value) values.

Explanation: The server did not open dataset dsn. The VSAM high-used and high-allocated attributes are outside of the range expected by the server. The values may have been corrupted by moving the dataset using anything other than a logical move.

System Action: Volume is marked read-only, or not brought on-line. Server operation continues.

User Response: Issue listcat entry(dsn) all to check the high-used and high-allocated values. If you moved the dataset, verify that a logical move was performed. Correct any user errors. Otherwise, contact your service representative.

ANR5046I (S/390)Dynamic allocation of tape unit unit was cancelled by the operator.

Explanation: The dynamic allocation of a tape unit unit was cancelled by the operator.

System Action: Server operation continues, tape mount fails.

User Response: None.

ANR5048E (S/390)Tape dataset allocation of block size changed from server value to current value.

Explanation: The server allocated the block size of its tape data set as server value, but it has been changed to current value.

System Action: Current tape operation fails.

User Response: Check for MVS or system application messages preceding this message that indicate what caused the change to the block size. Check for any system exits that may change the block size (for example, IEFDB401). Ensure that the server can use its original value for the block size.

ANR5049E (S/390)Tape data set allocation of data set organization changed from hex server value to hex current value.

Explanation: The server allocated the data set organization of its tape data set as server value, but it has been changed to current value in the data control block (DCB).

System Action: Current tape operation fails.

User Response: Check for MVS or system application messages preceding this message that indicate what caused the change to the data set organization. Check for any system exits that may change the data set organization (for example, IEFDB401). Ensure that the server can use its original value for the data set organization. See MVS/DFP V3R3 Macro Instructions for Data Sets for valid values.

ANR5050E (S/390)Tape data set allocation of record format changed from hex server value to hex current value.

Explanation: The server allocated the record format of its tape data set as server value, but it has been changed to current value in the data control block (DCB).

System Action: Current tape operation fails.

User Response: Check for MVS or system application messages preceding this message that indicate what caused the change to the record format. Check for any system exits that may change the record format (for example, IEFDB401). Ensure that the server can use its original value for the record format. See MVS/DFP V3R3 Macro Instructions for Data Sets for valid values.

ANR5051E (S/390)Tape data set allocation of logical record length changed from server value to current value.

Explanation: The server allocated the logical record length of its tape data set as server value, but it has been changed to current value.

System Action: Current tape operation fails.

User Response: Check for MVS or system application messages preceding this message that indicate what caused the change to the logical record length. Check for any system exits that may change the logical record length (for example, IEFDB401). Ensure that the server can use its original value for the logical record length.

ANR5060E (S/390)Unable to open VTAM ACB Name name, rc code.

Explanation: The server cannot be identified to VTAM with the ACB name specified.

System Action: Server operation continues. Support for the 3270 and SNALU6.2 COMMmethods is disabled. The server periodically tries to open the ACB and when successful, the 3270 and SNALU6.2 COMMmethods are enabled.

User Response: For a description of the reported error code, refer to VTAM Programming. If the ACB has been temporarily varied off, no action is required. The server periodically tries to open the ACB. If the ACB is not defined and the COMMmethods 3270 or SNALU6.2 are not supported for any clients, shut down the server with the HALT command and set the LUNAME statement in the server options file to *NONE*. If COMMmethods 3270 or SNALU6.2 are supported, contact your VTAM (network) administrator to ensure that the ACB name has been properly defined in a member of SYS1.VTAMLST.

ANR5061E (S/390)Unable to issue SETLOGON for VTAM ACB Name name, rc code, reas reason, rpl: rtncd return code fdb2 feedback.

Explanation: The server detects an error while informing VTAM that it is ready to accept a session.

System Action: Server operation continues. Support for the 3270 and SNALU6.2 COMMmethods is disabled. The server periodically tries to reissue the SETLOGON instruction.

User Response: For a description of the reported error code, refer to VTAM Programming.

ANR5062E (S/390)Unable to allocate number of bytes bytes for VTAM control blocks.

Explanation: The server is unable to access the storage it needs to support the COMMmethods 3270 and SNALU6.2.

System Action: The COMMmethods 3270 and SNALU6.2 are disabled. If the storage for the global control block cannot be accessed, these COMMmethods remain disabled until the server is shut down with the HALT command and restarted. Otherwise, the server periodically tries to access the needed storage and when successful, the 3270 and SNALU6.2 COMMmethods are enabled. Server operation continues.

User Response: If the support for the COMMmethods 3270 and SNALU6.2 is needed immediately, shut down the server (with the HALT command), resolve the storage problem, and restart the server. If the COMMmethods 3270 and SNALU6.2 are not used, shut down the server, set the LUNAME to *NONE*, and restart the server.

ANR5063E (S/390)Unable to allocate session number for LU LU ID.

Explanation: The server is unable to assign a session number to the incoming session.

System Action: Server operation continues. The server rejects the incoming session.

User Response: If the MAXSESSIONS statement in the server options file has been set correctly, the end-user (client) must wait until there is a free session before retrying to connect with the server. If the MAXSESSIONS statement is in error, shut down the server, correct the MAXSESSIONS statement, restart the server, and have the client retry connecting with the server.

ANR5064E (S/390)Unable to allocate number of bytes bytes for VTAM session with LU LU ID.

Explanation: The server is unable to access the storage needed to support the incoming 3270 dial-in session.

System Action: Server operation continues. The incoming session is rejected.

User Response: Allocate additional storage to the server virtual machine. There are four ways to do this:

  1. On VM, increase the size of the server's virtual machine. This requires that the default storage size be updated in the server's CP directory entry.
  2. On MVS, increase the size of the REGION parameter on the JOB or EXEC statement of the JCL used to start the server.
  3. Reduce the maximum number of client sessions permitted. To do this, edit the server options file and reduce the value specified for the MAXSESSIONS statement. Note that each client session causes an additional 64KB of memory to be allocated.
  4. Decrease the amount of space allocated to the server's database buffer pool. To do this, edit the server options file and reduce the value specified for the BUFPOOLSIZE statement. Note that each buffer pool page causes an additional 4 KB of memory to be allocated.

Note that the server must be shut down (with the HALT command) to allow changes made to the server options file to take place.

ANR5065E (S/390)Unable to open session with LU LU ID CID conversation ID, rc code reason reason, rpl: rtncd return code fdb2 feedback.

Explanation: The server encounters an error while accepting an incoming session by way of a VTAM OPNDST instruction. The session is rejected.

System Action: Server operation continues.

User Response: For a description of error code, refer to VTAM Programming.

ANR5066E (S/390)Unable to close session with LU LU ID CID conversation ID, rc code reason reason, rpl: rtncd return code fdb2 feedback.

Explanation: The server encounters an error while ending a session.

System Action: Server operation continues.

User Response: For a description of the error code, refer to VTAM Programming.

ANR5067E (S/390)Unable to close VTAM ACB Name name, rc code.

Explanation: The server detects an error while closing the ACB for the specified name.

System Action: The server proceeds with HALT command processing.

User Response: For a description of the reported error code, refer to VTAM Programming.

ANR5068E (S/390)Unable to receive on session with LU LU ID CID conversation ID, rc code reason reason, rpl: rtncd return code fdb2 feedback sense sense code.

Explanation: The server encounters an error while receiving data on the session.

System Action: Server operation continues, and the session is ended.

User Response: For a description of the reported error code, refer to VTAM Programming.

ANR5069E (S/390)Unable to send on session with LU LU ID CID conversation ID, rc code reason reason, rpl: rtncd return code fdb2 feedback sense sense code.

Explanation: The server encounters an error while sending data on the session.

System Action: Server operation continues, and the session is ended.

User Response: For a description of the reported error code, refer to VTAM Programming.

ANR5070I (S/390)3270 Dial-in driver terminated as requested.

Explanation: The server's 3270 dial-in communications driver is ending as requested.

System Action: Server operation continues with support for the 3270 COMMmethod disabled.

User Response: None.

ANR5071W (S/390)Application resource name was defined to VTAM with APPC=NO.

Explanation: The specified VTAM application has been defined with APPC=NO. This definition, may be normal for your installation if SNALU6.2 is not used by the clients. If this is true, then this message can be ignored.

System Action: Server operation continues. Support for the SNALU6.2 is disabled.

User Response: If clients are using SNALU6.2, define the VTAM application with APPC=YES. For the server to recognize the new definition, you must stop the server by using the HALT command and restart the server.

ANR5080I (S/390)IUCV driver ready for connection with clients.

Explanation: The server's IUCV communications driver is ready to receive connection requests from clients.

System Action: Server operation continues. The IUCV is enabled.

User Response: None.

ANR5081E (S/390)Unable to initialize IUCV driver - code code.

Explanation: The server's IUCV communications driver cannot initialize itself because it received the error code code when entering the IUCV DECLARE BUFFER function.

System Action: Server initialization fails.

User Response: For a description of the reported error code, refer to the IUCV documentation in the CP Programming Services publication for your specific operating system, and the TCP/IP for MVS Programmer's Reference for your version of TCP/IP.

ANR5082W (S/390)IUCV connection terminated - insufficient memory.

Explanation: An IUCV connection request is refused by the server's IUCV communications driver because sufficient memory is not available to construct a session.

System Action: Server operation continues.

User Response: Allocate additional storage to the server virtual machine. There are three ways to do this:

  1. On VM, increase the size of the server's virtual machine. This requires that the default storage size be updated in the server's CP directory entry.
  2. On MVS, increase the size of the REGION parameter on the JOB or EXEC statement of the JCL used to start the server.
  3. Reduce the maximum number of client sessions permitted. To do this, edit the server options file and reduce the value specified for the MAXSESSIONS statement. Note that each client session causes an additional 64 KB of memory to be allocated.
  4. Decrease the amount of space allocated to the server's database buffer pool. To do this, edit the server options file and reduce the value specified for the BUFPOOLSIZE statement. Note that each buffer pool page causes an additional 4 KB of memory to be allocated.

Note that the server must be shut down (with the HALT command) before changes can be made to the server options file.

ANR5083E (S/390)IUCV connection terminated - error code accepting connect request.

Explanation: The server's IUCV communications driver is unable to accept a new connection from a client because error code has been received from the IUCV ACCEPT function.

System Action: Server operation continues.

User Response: For a description of the IUCV ACCEPT error code, refer to the IUCV documentation in the CP Programming Services publication for your specific operating system, and the TCP/IP for MVS Programmer's Reference for your version of TCP/IP.

ANR5084W (S/390)IUCV connection terminated - server HALT in progress.

Explanation: The server's IUCV communications driver refuses a request for a client connection because the HALT command has been entered.

System Action: The server rejects the session and proceeds with HALT command processing.

User Response: None.

ANR5085I (S/390)IUCV driver unable to start. Server terminating.

Explanation: The server is unable to start the thread to monitor the status of the IUCV communications driver.

System Action: The server shuts down.

User Response: If sufficient storage is available when this error occurs, contact your service representative. On MVS, ensure the region size parameter on the JCL is at least 128MB. Otherwise if on VM, ensure that the server virtual machine is at least 128MB in size.

ANR5086I (S/390)IUCV driver terminated.

Explanation: The IUCV communications driver has shut down.

System Action: Server operation continues. Support for the IUCV COMMmethod is disabled. The server periodically tries to restart the IUCV communications driver.

User Response: None.

ANR5087I (S/390)IUCV driver starting.

Explanation: The server is reporting that it is in the process of starting the IUCV communications driver.

System Action: The server attempts to initiate a process that will monitor the status of the IUCV communications driver.

User Response: None.

ANR5088E (S/390)Unable to establish a wrap connection - return code code.

Explanation: The server is unable to establish an IUCV connection with itself.

System Action: Server operation continues. Support for the IUCV COMMmethod is disabled. The server will periodically retry the connect.

User Response: For a description of this IUCV CONNECT error code, refer to the IUCV documentation in the CP Programming Services publication for your specific operating system, and the TCP/IP for MVS Programmer's Reference for your version of TCP/IP.

ANR5089I (S/390)IUCV driver terminated as requested.

Explanation: The server's IUCV communications driver is ending as requested.

System Action: Server operation continues with support for the ADMIUCV COMMmethod disabled.

User Response: None.

ANR5090I (S/390)TCP/IP driver ready for connection with clients on port port number.

Explanation: The server's TCP/IP communications driver is ready to receive connection requests from clients.

System Action: Server operation continues. Support for the TCP/IP COMMmethod is enabled.

User Response: None.

ANR5091E (S/390)Unable to initialize TCP/IP driver - insufficient memory.

Explanation: The server's TCP/IP communications driver is unable to initialize itself due to insufficient memory (virtual storage).

System Action: Server initialization fails.

User Response: Allocate additional storage to the server virtual machine. There are four ways to do this:

  1. On VM, increase the size of the server's virtual machine. This requires that the default storage size be updated in the server's CP directory entry.
  2. On MVS, increase the size of the REGION parameter on the EXEC or JOB statement of the JCL used to start the server.
  3. Reduce the maximum number of client sessions permitted. To do this, edit the server options file and reduce the value specified for the MAXSESSIONS statement. Note that each client session causes an additional 64KB of memory to be allocated.
  4. Decrease the amount of space allocated to the server's database buffer pool. To do this, edit the server options file and reduce the value specified for the BUFPOOLSIZE statement. Note that each buffer pool page causes an additional 4KB of memory to be allocated.

Note that the server must be shut down (with the HALT command) before changes can be made to the server options file.

ANR5092E (S/390)Unable to initialize TCP/IP driver - error creating acceptor socket.

Explanation: The server's TCP/IP communications driver is unable to create its critical listening socket, and so TCP/IP communications cannot be initialized.

System Action: Server initialization continues. TCP/IP communications initialization will be retried.

User Response: Check that TCP/IP is running, and that TCPName in the options file matches the TCP/IP subsystem name you intend to use.

ANR5093E (S/390)Unable to establish TCP connection - accept error.

Explanation: The server's TCP/IP communications driver detects an internal error while attempting to accept a new client connection.

System Action: Server operation continues.

User Response: Report the error to your service representative.

ANR5094W (S/390)Unable to establish TCP connection - insufficient memory.

Explanation: A TCP/IP connection request has been refused by the server's TCP/IP communications driver because sufficient memory is not available to construct a session.

System Action: Server operation continues.

User Response: Allocate additional storage to the server virtual machine. There are three ways to do this:

  1. On VM, increase the size of the server's virtual machine. This requires that the default storage size be updated in the server's CP directory entry.
  2. On MVS, increase the size of the REGION parameter on the EXEC or JOB statement of the JCL used to start the server.
  3. Reduce the maximum number of client sessions permitted. To do this, edit the server options file and reduce the value specified for the MAXSESSIONS statement. Note that each client session causes an additional 64KB of memory to be allocated.
  4. Decrease the amount of space allocated to the server's database buffer pool. To do this, edit the server options file and reduce the value specified for the BUFPOOLSIZE statement. Note that each buffer pool page causes an additional 4 KB of memory to be allocated.

Note that the server must be shut down (with the HALT command) before changes can be made to the server options file.

ANR5095W (S/390)Unable to establish TCP connection - server HALT in progress.

Explanation: The server's TCP/IP communications driver refuses a request for a client connection because the HALT command has been entered.

System Action: The server rejects the session and proceeds with HALT command processing.

User Response: None.

ANR5096W (S/390)Unable to initialize OE BPX TCP/IP driver - TCP/IP is down level.

Explanation: Although the OS/390 is at V2R5 or above the level of TCP/IP is below V3R4 level, and so OE BPX TCP/IP communications cannot be initialized.

System Action: Server initialization continues. TCP/IP communications is initialized, instead of OE BPX TCP/IP.

User Response: Make sure the TCP/IP V3R4 or above is installed and running in the system if OE BPX TCP/IP communication is to be used.

ANR5097I (S/390)TCP/IP driver terminated as requested.

Explanation: The server's TCP/IP communications driver is ending as requested.

System Action: Server operation continues with support for the TCP/IP COMMmethod disabled.

User Response: None.

ANR5098I (S/390)TCP/IP driver starting.

Explanation: The server is in the process of starting the TCP/IP communications driver.

System Action: The server tries to initiate a thread that will monitor the status of the TCP/IP communications driver.

User Response: None.

ANR5099E (S/390)Unable to initialize TCP/IP driver - error binding acceptor socket socket number (rc = code).

Explanation: The server's TCP/IP communications driver detects an internal error while attempting to bind the acceptor socket.

System Action: The server ends the TCP/IP acceptor process. Server operation continues without support for the TCP/IP COMMmethod. The server tries to restart the acceptor process periodically.

User Response: Report the error to your service representative.

ANR5100E (S/390)Unable to initialize TCP/IP driver -error listening on acceptor socket socket number (rc = code).

Explanation: The server's TCP/IP communications driver detects an internal error while attempting to listen for a connection on the acceptor socket.

System Action: The server ends the TCP/IP acceptor process. Server operation continues without support for the TCP/IP COMMmethod. The server periodically tries to restart the acceptor process.

User Response: Report the error to your service representative.

ANR5101W (S/390)TCP/IP communications driver terminating.

Explanation: The server's TCP/IP communications driver has shut down.

System Action: Server operation continues without support for the TCP/IP COMMmethod option. The server periodically tries to restart the TCP/IP communications driver if the server is not in the process of shutting down.

User Response: If the server is not in the process of shutting down, this message may indicate that the TCP/IP server is not available or that a server internal error has occurred. Review the console log to determine if an internal error has occurred. If an internal error has occurred, contact your service representative. If the TCP/IP server is unavailable, correct the problem and the server will automatically reinitiate the TCP/IP communications driver.

ANR5102W (S/390)Error received for connection connection number (socket socket number). TCP/IP driver will stop, then re-start.

Explanation: The server's TCP/IP communications driver received an error for the specified connection.

System Action: The server stops the TCP/IP communications driver, and restarts the communications driver.

User Response: This process may take up to 5 minutes. If the condition persists, report the problem to your service representative.

ANR5103I (S/390)CLIO/S (IBM)TCP/IP driver ready for service on port clio port number.

Explanation: The server's CLIO/S TCP/IP communications driver is ready to handle connection requests to and from AIX clients using COMMmethod CLIO through an IBM TCP/IP host network.

System Action: Server operation continues. Support for the TCPName and CLIOPort server options is enabled.

User Response: None.

ANR5104E (S/390)Unable to initialize CLIO/S (IBM)TCP/IP driver - error creating listening socket.

Explanation: The server's CLIO/S communication driver is unable to create its critical listening socket; therefore, CLIO/S (IBM)TCP/IP communication cannot be initialized.

System Action: Server initialization continues. CLIO/S (IBM)TCP/IP communication initialization will be retried every minute. This message will be suppressed after being issued for the third time; however, attempts to initialize CLIO/S communications will continue every minute until message ANR5103I is issued indicating CLIO/S driver is ready for service.

User Response: Check that TCP/IP is running, and that TCPName, in the options file, matches the name of the target TCP/IP address space.

ANR5105I (S/390)Interlink TCPaccess driver is ready for service on port interlink port number.

Explanation: The server's Interlink TCPaccess communications driver is ready to receive connection requests from clients connected through Interlink TCPaccess.

System Action: Server operation continues. Support for the ICSSname and ICSPort server options is enabled.

User Response: None.

ANR5106E (S/390)Unable to initialize Interlink TCPaccess driver - error opening listen endpoint.

Explanation: The server's Interlink TCPaccess driver is unable to create its critical listen endpoint; Interlink TCPaccess communication cannot be initialized.

System Action: Server initialization continues. Interlink TCPaccess communications will be retried every minute and this message will suppressed after being issued three times.

User Response: Check that TCPaccess is running and that ICSSname, in the options file, matches the TCPaccess subsystem name you intend to use. The ICSSname option should match the SSN parameter of the PROC statement in the TCPaccess startup procedure. Refer to Interlink TCPaccess publications for details.

ANR5107E (S/390)Unable to initialize CLIO/S (IBM)TCP/IP driver - error binding acceptor socket socket number (rc = code).

Explanation: The server's TCP/IP communications driver detects an error while attempting to bind the acceptor socket.

System Action: The server ends the TCP/IP acceptor process. Server operation continues without support for the TCP/IP COMMmethod. The server tries to restart the acceptor process periodically.

User Response: Check that TCP/IP is running and that TCPName, in the options file, matches the name of the target TCP/IP address space.

ANR5108E (S/390)The CLIO/S functions have not been linked into this module.

Explanation: The server cannot find the CLIO/S functions required to support CLIO (IBM)TCP/IP communications.

System Action: The connection to the server fails.

User Response: The cause of this error is the omission of the required post-SMP/E link-edit step to merge CLIO functions from SYS1.SFCFLIB(FCFIADSM). Before retrying the operation, ensure that your installation has performed the required post install link-edit step. Find the ADSM SAMPLIB and use member ANRCLIOK for an example of the required post-SMP/E link edit to load ANRSERV with CLIO/S communication code.

ANR5109E (S/390)The CLIO/S communication driver cannot be started.

Explanation: The server is unable to start the CLIO/S communication driver because either TCPPort and CLIOPort server options are the same value or TCPName is coded with *NONE*.

System Action: The CLIO/S communication option will not be available and server initialization continues.

User Response: Check the server options file to ensure CLIOPort and TCPPort values are different. If the CLIOPort and TCPPort options are specified correctly, check the TCPName option to ensure *NONE* is not coded for this option. Specify a unique CLIOPort value and ensure a valid TCPName parameter is coded to allow the (IBM)TCP/IP CLIO/S communication driver to start. CLIOPort has no default value; however, TCPPort and TCPName default to 1500 and TCPIP respectively. This message can be eliminated if CLIO/S communication is not required by removing the CLIOPort option from the server option file and recycling the server.

ANR5110I (S/390)3270 Dial-in driver ready for connection with clients.

Explanation: The server's 3270 dial-in communications driver is ready to receive connection requests from clients.

System Action: Server operation continues. Support for the 3270 COMMmethod is enabled.

User Response: None.

ANR5111E (S/390)Unable to initialize 3270 dial-in driver - error defining GRAF devices.

Explanation: The server's 3270 dial-in communications driver is unable to define one or more CP GRAF devices, and is therefore unable to initialize itself.

System Action: Server initialization fails.

User Response: Contact your service representative.

ANR5112W (S/390)Unable to define additional GRAF devices for dial-in.

Explanation: The server's 3270 dial-in communications driver is unable to define additional CP GRAF devices, and may not be able to accept subsequent connections from clients.

System Action: Server operation continues.

User Response: Contact your service representative.

ANR5113W (S/390)3270 dial-in session terminated - insufficient memory.

Explanation: A 3270 dial-in connection request has been refused by the server's 3270 communications driver because sufficient memory is not available to construct a session.

System Action: Server operation continues.

User Response: Allocate additional storage to the server virtual machine. There are three ways to do this:

  1. On VM, increase the size of the server's virtual machine. This requires that the default storage size be updated in the server's CP directory entry.
  2. On MVS, increase the size of the REGION parameter on the EXEC or JOB statement of the JCL used to start the server.
  3. Reduce the maximum number of client sessions permitted. To do this, edit the server options file and reduce the value specified for the MAXSESSIONS statement. Note that each client session causes an additional 64KB of memory to be allocated.
  4. Decrease the amount of space allocated to the server's database buffer pool. To do this, edit the server options file and reduce the value specified for the BUFPOOLSIZE statement. Note that each buffer pool page causes an additional 4 KB of memory to be allocated.

Note that the server must be shut down (with the HALT command) before changes can be made to the server options file.

ANR5114W (S/390)3270 dial-in session terminated - device does not support structured fields.

Explanation: The server's 3270 communications driver has refused a client connection request because the 3270 device initiating the connection does not support structured fields.

System Action: Server operation continues.

User Response: Retry the 3270 connection from a device that properly supports structured fields.

ANR5115W (S/390)3270 dial-in session terminated - emulator not supported.

Explanation: The server's 3270 dial-in communications driver has refused a connection request from a client, because the client's 3270 emulator does not or is not configured for the level of 3270 extended data stream support that the server requires.

System Action: Server operation continues.

User Response: Retry the 3270 connection by using a supported emulator program, such as the OS/2 Communications Manager, or the IBM Personal Communications/3270 program.

ANR5116I (S/390)3270 Dial-in driver unable to start. Server terminating.

Explanation: The server is unable to start the thread that monitors the status of the 3270 dial-in communications driver.

System Action: The server shuts down.

User Response: If sufficient storage is available when this error occurs, contact your service representative. Otherwise for VM, ensure that the storage for the server virtual machine is at least 128MB. For MVS, ensure the region size parameter on the JCL is at least 128MB.

ANR5117I (S/390)3270 Dial-in driver terminated.

Explanation: The 3270 dial-in communications driver has shut down.

System Action: Server operation continues. Support for the 3270 COMMmethod is disabled. The server periodically tries to restart the 3270 dial-in communications driver.

User Response: None.

ANR5118I (S/390)3270 Dial-in driver starting.

Explanation: The server is reporting that it is in the process of starting the 3270 dial-in communications driver.

System Action: The server tries to initiate a process that will monitor the status of the 3270 dial-in communications driver.

User Response: None.

ANR5120I (S/390)APPC driver unable to start. Server terminating.

Explanation: The server is unable to start the thread that monitors the status of the APPC communications driver.

System Action: The server shuts down.

User Response: If sufficient storage is available when this error occurs, contact your service representative. Otherwise for VM, ensure that storage for the server virtual machine is at least 128MB. For MVS, ensure the region size parameter on the JCL is at least 128MB.

ANR5121I (S/390)APPC driver ready for connections with clients on resource resource name.

Explanation: The server's APPC communications driver is reporting that it is ready to receive connection requests from clients.

System Action: Server operation continues. Support for the SNALU6.2 COMMmethod is enabled.

User Response: None.

ANR5122I (S/390)APPC driver terminated.

Explanation: The APPC communications driver has shut down.

System Action: Server operation continues. Support for the SNALU6.2 COMMmethod is disabled. The server periodically tries to restart the APPC communications driver.

User Response: None.

ANR5123I (S/390)APPC driver starting.

Explanation: The server is reporting that it is in the process of starting the APPC communications driver.

System Action: The server tries to initiate a thread that will monitor the status of the APPC communications driver.

User Response: None.

ANR5124E (S/390)APPC driver unable to declare as resource resource name, rc code, reason reason.

Explanation: The server cannot connect to the *IDENT (the Identify System Service) to identify itself as the resource manager for the resource specified.

System Action: Server operation continues. Support for the SNALU6.2 COMMmethod is disabled. The server periodically tries to restart the APPC communications driver.

User Response: Ensure that the following IUCV statement is present in the CP directory entry for the server: IUCV *IDENT appc-resource GLOBAL REVOKE.

ANR5125E (S/390)APPC connection terminated - error code accepting connect request.

Explanation: The server's APPC communications driver is unable to accept a new connection from a client, because error code has been received from the IUCV ACCEPT function.

System Action: Server operation continues.

User Response: For a description of the IUCV ACCEPT error code, refer to the IUCV documentation in the CP Programming Services publication for your specific operating system.

ANR5126W (S/390)APPC connection terminated - server HALT in progress.

Explanation: The server's APPC communications driver refuses a request for a client connection because the HALT command has been entered.

System Action: The server rejects the session and proceeds with HALT command processing.

User Response: None.

ANR5127W (S/390)APPC connection terminated - insufficient memory.

Explanation: An IUCV connection request is refused by the server's APPC communications driver because sufficient memory is not available to construct a session.

System Action: Server operation continues.

User Response: Allocate additional storage to the server virtual machine. There are three ways to do this:

  1. On VM, increase the size of the server's virtual machine. This requires that the default storage size be updated in the server's CP directory entry.
  2. On MVS, increase the size of the REGION parameter on the EXEC or JOB statement of the JCL used to start the server.
  3. Reduce the maximum number of client sessions permitted. To do this, edit the server options file and reduce the value specified for the MAXSESSIONS statement. Note that each client session causes an additional 64KB of memory to be allocated.
  4. Decrease the amount of space allocated to the server's database buffer pool. To do this, edit the server options file and reduce the value specified for the BUFPOOLSIZE statement. Note that each buffer pool page causes an additional 4 KB of memory to be allocated.

Note that the server must be shut down (with the HALT command) before changes can be made to the server options file.

ANR5128E (S/390)Unable to allocate session number for LU LU ID.

Explanation: The server is unable to assign a session number to the incoming session.

System Action: Server operation continues. The server rejects the incoming session.

User Response: If the MAXSESSIONS statement in the server options file has been set correctly, the end-user (client) must wait until there is a free session before retrying to connect with the server. If the MAXSESSIONS statement is in error, shut down the server, correct the MAXSESSIONS statement, restart the server, and have the client retry to connect with the server.

ANR5129W (S/390)VTAM APPC (LU62) conversation terminated - server HALT in progress.

Explanation: The server's APPC communications driver rejects a conversation because the HALT command has been entered.

System Action: The server rejects the conversation and proceeds with HALT command processing.

User Response: None.

ANR5130W (S/390)VTAM APPC (LU62) conversation (conversation ID) with LU LU ID terminated - insufficient memory.

Explanation: An APPC conversation has been terminated by the server's APPC communications driver because sufficient memory is not available to support this conversation.

System Action: Server operation continues. The conversation is deallocated.

User Response: Allocate additional storage to the server virtual machine. There are three ways to do this:

  1. Increase the size of the REGION parameter on the JOB or EXEC statement of the JCL used to start the server.
  2. Reduce the maximum number of client sessions permitted. To do this, edit the server options file and reduce the value specified for the MAXSESSIONS statement. Note that each client session causes an additional 64KB of memory to be allocated.
  3. Decrease the amount of space allocated to the server's database buffer pool. To do this, edit the server options file and reduce the value specified for the BUFPOOLSIZE statement. Note that each buffer pool page causes an additional 4 KB of memory to be allocated.

Note that the server must be shut down (with the HALT command) before changes can be made to the server options file.

ANR5131I (S/390)APPC driver terminated as requested.

Explanation: The server's APPC communications driver is reporting that it is terminating as requested.

System Action: Server operation continues with support for the SNALU6.2 COMMmethod disabled.

User Response: None.

ANR5132W (S/390)VTAM APPC (LU62) support is not available with current session.

Explanation: The server's VTAM APPC (LU6.2) communications driver is not available. Clients that use the SNALU6.2 communications method cannot establish a session with the server. Refer to ANR5071W, which was displayed prior to this message, for additional information. If the SNALU6.2 communication method is not used, ignore this message and message ANR5071W.

System Action: Server operation continues without support for the SNALU6.2 COMMmethod.

User Response: Verify that the server application is defined correctly to VTAM. APPC=YES must be specified with the VTAM APPL macro when defining the server application when SNALU6.2 support is used.

ANR5133W (S/390)VTAM APPC (LU62) connect request rejected.

Explanation: A client's VTAM APPC (LU6.2) connect request was rejected because the LU6.2 communications driver is not available. This process may be the result of the server application not being defined correctly to VTAM. The application must be defined with APPC=YES with the APPL macro to enable SNALU6.2 support on the server.

System Action: VTAM message IST663I and other related messages are displayed; server operation continues.

User Response: Verify that the server application is defined correctly to VTAM. APPC=YES must be specified with the VTAM APPL macro when defining the server application.

ANR5140I (S/390)HTTP (IBM) communications is listening for clients on port port number.

Explanation: The server's HTTP (IBM) TCP/IP communications driver is ready to receive connection requests from Web clients.

System Action: Server operation continues. Support for Web Client HTTP communication is enabled.

User Response: None.

ANR5148I (S/390)HTTP (TCPaccess) driver is listening for clients on port port number.

Explanation: The server's HTTP (TCPaccess) TCP/IP communications driver is ready to receive connection requests from Web clients.

System Action: Server operation continues. Support for Web Client HTTP over TCPaccess is enabled.

User Response: None.

ANR5200S (S/390)Unable to connect to the *MSG System Service, rc = code.

Explanation: The server receives return code code from the IUCV CONNECT function when connecting to the *MSG System Service.

System Action: The server shuts down.

User Response: Determine the cause of the error code, correct the problem, and restart the server. For a description of the reported error code, refer to the IUCV documentation in the CP Programming Services publication, or the publication for your operating system that contains documentation for the IUCV CONNECT function.

ANR5201S (S/390)Error code from *MSG System Service path path ID.

Explanation: An error occurs on the IUCV path to the *MSG System Service.

System Action: The server shuts down.

User Response: Determine the cause of the error code, correct the problem, and restart the server. For a description of the reported error code, refer to the IUCV documentation in the CP Programming Services publication, or the publication for your operating system that contains IUCV documentation.

ANR5202E (S/390)Unable to communicate with any Notify user ID.

Explanation: The server is unable to send a message to any user ID specified on the NOTIFY option in the DSMSERV OPT file.

System Action: Server operation continues.

User Response: Have someone with an authorized NOTIFY user ID log on to the system.

ANR5203E (S/390)Unable to communicate with any Mount Operator.

Explanation: The server is unable to send a message to any user ID specified on the MOUNTOP option in the DSMSERV OPT file.

System Action: Server operation continues.

User Response: Have someone with an authorized MOUNTOP user ID log on to the system.

ANR5204I (S/390)Autolog-response

Explanation: The result of the XAUTOLOG command for the mount exit virtual machine is Autolog-response.

System Action: Server operation continues.

User Response: None.

ANR5205I (S/390)From userid: msg.

Explanation: The message msg has been received from a nonauthorized user ID userid.

System Action: Server operation continues.

User Response: If the user ID userid is a server mount operator, ensure that the user ID is in the MOUNTOP list in the server options file.

ANR5208I (S/390)Dismounting volume volser (updated).

Explanation: The volume volser is dismounted after being updated (written to) by the server. Possible reasons for the dismount include:

System Action: Server operation continues.

User Response: None.

ANR5209I (S/390)Dismounting volume volser (read-only access).

Explanation: The volume volser is dismounted after read-only access by the server. Possible reasons for the dismount include:

System Action: Server operation continues.

User Response: None.

ANR5210I (S/390)Request number: Mount devclass volume ID at vaddr mode within number of minutes minutes.

Explanation: The server has requested a volume be mounted.

System Action: The running task waits until the mount is satisfied or canceled.

User Response: Use the DSMOP command to satisfy or cancel the mount request.

ANR5211I (S/390)Request number: Mount devclass volume ID at vaddr mode (format) within number of minutes minutes.

Explanation: The server has requested a volume with a specific format be mounted.

System Action: The running task waits until the mount is satisfied or canceled.

User Response: Use the DSMOP command to satisfy or cancel the mount request.

ANR5212I (S/390)Request number: Mount devclass volume ID at vaddr mode via Exit Machine machine name.

Explanation: The server has requested a volume be mounted.

System Action: The running task waits until the mount is satisfied or canceled.

User Response: Use the DSMOP command to satisfy or cancel the mount request.

ANR5213I (S/390)Request number: Mount devclass volume ID at vaddr mode (format) via Exit Machine machine name.

Explanation: The server has requested a volume with a specific format be mounted.

System Action: The running task waits until the mount is satisfied or canceled.

User Response: Use the DSMOP command to satisfy or cancel the mount request.

ANR5214I (S/390)Request number: Mount devclass volume ID at vaddr mode waiting for available Exit Machine.

Explanation: The server has requested a volume be mounted.

System Action: The running task waits until the mount is satisfied or canceled.

User Response: Use the DSMOP command to satisfy or cancel the mount request.

ANR5215I (S/390)Request number: Mount devclass volume ID at vaddr mode (format) waiting for available Exit Machine.

Explanation: The server has requested a volume be mounted.

System Action: The running task waits until the mount is satisfied or canceled.

User Response: Use the DSMOP command to satisfy or cancel the mount request.

ANR5216I (S/390)Type volser is expected to be mounted (mode).

Explanation: The server requires the volume volser be in read/write or read/only mode as indicated by mode on a device type indicated by type.

System Action: Server operation continues.

User Response: Locate the specified volume and be prepared to make it available to the server.

ANR5217I (S/390)Dismounting volume volser - retention minute mount retention expired.

Explanation: The volume volser is dismounted because the MOUNTRETENTION value retention specified for this device class has elapsed without activity on this volume.

System Action: Server operation continues.

User Response: None.

ANR5218I (S/390)Detaching tape device vaddr - not requested by server.

Explanation: The virtual address vaddr is detached because it has not been requested by the server.

System Action: Server operation continues.

User Response: Check the virtual address requested by the server for tape mounts. Reissue the CP ATTACH command and specify the correct virtual address.

ANR5220I (S/390)Deleting type volser from Storage Pool pool.

Explanation: The volume volser of device type type has been removed from storage pool pool.

System Action: Server operation continues.

User Response: The server no longer uses the volume specified. You can return the volume to the scratch pool.

ANR5221I (S/390)Request: Delete type volser via Exit Machine userid.

Explanation: The deletion of volume volser of device type type is scheduled for Mount Exit Virtual Machine userid as request number request.

System Action: Server operation continues.

User Response: None.

ANR5222I (S/390)Request: Delete type volser waiting for available Exit Machine.

Explanation: The deletion of volume volser of device type type is waiting for an available Mount Exit Virtual Machine userid as request number request.

System Action: Server operation continues.

User Response: None.

ANR5223E (S/390)Deletion Exit for volser (storage pool pool) failed - unknown Rc=rc.

Explanation: The deletion of volume volser in storage pool pool fails.

System Action: Server operation continues.

User Response: Contact service representative.

ANR5224E (S/390)Deletion Exit for volser (storage pool pool) failed - ExitRc=rc, Rc=abend-indicated.

Explanation: The deletion of volume volser in storage pool pool fails.

System Action: Server operation continues.

User Response: If the exit return code rc is nonzero, check the documentation for the tape deletion exit specified in the server options file. If the tape deletion exit has abended, the indicator abend-indicated is nonzero.

ANR5225E (S/390)Deletion Exit for volser (storage pool pool) failed - unable to get device class information.

Explanation: The deletion of volume volser in storage pool pool has failed due to an internal server error.

System Action: Server operation continues.

User Response: Contact your service representative.

ANR5226E (S/390)Deletion Exit for volser (storage pool pool) failed - unable to start background thread.

Explanation: The deletion of volume volser in storage pool pool has failed due to an internal server error.

System Action: Server operation continues.

User Response: Contact your service representative.

ANR5227E (S/390)Deletion Exit for volser (storage pool pool) failed - insufficient memory.

Explanation: The deletion of volume volser in storage pool pool fails due to lack of available storage.

System Action: Server operation continues.

User Response: Increase the region or virtual machine size for the server or reduce the MAXSESSIONS value in the server options file.

ANR5228I (S/390)Deleting type volser from volume history (previous use volume).

Explanation: The volume volser in device type type has been deleted from the volume history. It was previously used for previous use.

System Action: Server operation continues.

User Response: The server no longer tracks the volume specified. You can return the volume to the scratch pool.

ANR5229W (S/390)RACROUTE Delete failed for volser, SAF return code System Authorized Facility return code, return code RACF return code, reason code RACF reason code.

Explanation: The deletion of the profile for volume volser failed. The return codes and reason code are the result of a RACROUTE call. The codes are in hex. The SAF return code is designated as x0yy where yy is the SAF return code and x indicates the call as follows:

x=1 RACROUTE REQUEST=DEFINE, TYPE=DELETE, CLASS='TAPEVOL', ENTITY=volume

x=2 RACROUTE REQUEST=STAT, CLASS='TAPEVOL'

x=3 RACROUTE REQUEST=DEFINE, TYPE=DELETE, CLASS='DATASET', VOLSER=volume, ENTITY=tape dataset name

The failure of the profile deletion is not an error if the volume did not have a profile. No profile will exist for a volume if the server was not set up to request a profile (DEVCLASS parameter PROTECTION=NO) when the volume was first used, or if the server never used the volume.

System Action: Server operation continues.

User Response: If the RACF profile exists for the volume, check the system log for error messages to find the cause of the problem. The profile for the volume specified in the message will have to be deleted by issuing the appropriate RACF commands. For Information on the return codes and reason code, see External Security Interface (RACROUTE) Macro Reference for MVS.

ANR5230I (S/390)Request number: Starting Exit Machine mountvm to mount devclass volume ID.

Explanation: The server has autologged a mount exit virtual machine to handle a mount request.

System Action: The server autologs a mount exit virtual machine.

User Response: None.

ANR5231I (S/390)Request number: Starting Exit Machine mountvm to delete devclass volume ID.

Explanation: The server autologs a mount exit virtual machine to handle a mount delete request.

System Action: The server autologs a mount exit virtual machine.

User Response: None.

ANR5232W (S/390)[XAUTOLOG] mountvm failed with return code code.

Explanation: An error occurs during XAUTOLOG of a mount exit virtual machine.

System Action: The server retries the command. If the command continues to fail, the mount exit machine is marked off-line, and another mount exit machine is used.

User Response: If the mount exit machine is placed in the off-line status, determine the cause, correct the problem, and use the DSMOP or administrator READY EXIT command to restore the mount exit machine to the ready status.

ANR5233E (S/390)Exit Machine mountvm taken offline - nn command attempts failed.

Explanation: The number of XAUTOLOG attempts has exceeded an internal threshold. The mount exit virtual machine is no longer used.

System Action: The server marks the mount exit virtual machine off-line.

User Response: To make the mount exit machine available, determine the cause of the autolog failure. Correct the problem and use the DSMOP or administrator READY EXIT command to restore the mount exit machine to the ready status.

ANR5234E (S/390)All Exit Machines are "Offline".

Explanation: All the defined mount exit virtual machines have been placed in the off-line status by the server.

System Action: Any mount requests by the server are queued.

User Response: Determine the cause of the autolog failures of all the mount exit virtual machines, correct any problems and use the DSMOP or administrator READY EXIT command to make the mount exit machines available.

ANR5240E (S/390)Request number: Mount for volume ID has timed out.

Explanation: The mount request has not been satisfied in the requested time.

System Action: The server cancels the mount request.

User Response: None.

ANR5241E (S/390)Exit Machine mountvm not logged on, mount for volume ID cancelled.

Explanation: A mount exit virtual machine has logged off without satisfying the server's mount request.

System Action: The server cancels the mount request.

User Response: None.

ANR5250E (S/390)Command: User user ID not authorized.

Explanation: An unauthorized user has attempted to enter a DSMOP command.

System Action: The server does not process the command.

User Response: If the user should be authorized, add that user ID on the REPLYOP option in the DSMSERV OPT file.

ANR5251E (S/390)Command: Invalid request number - request number.

Explanation: A DSMOP command has been entered with an incorrect request number.

System Action: The server does not process the command.

User Response: Enter the command with the correct request number.

ANR5252E (S/390)Command: No match found for this request number.

Explanation: The request number specified by the DSMOP command is not in the list of outstanding mount requests.

System Action: The server does not process the command.

User Response: Enter the command with the correct request number.

ANR5253E (S/390)Request: Invalid device address - raddr.

Explanation: The response to server request number request has specified an invalid real device address raddr.

System Action: Server operation continues.

User Response: Respond to the request again, by specifying a valid real device address.

ANR5254E (S/390)Command: CP command command name failed.

Explanation: A DSMOP CANCEL REQUEST or a DSMOP REPLY command fails.

System Action: The server tries to enter the CP command command and receives a nonzero return code.

User Response: If you have entered a DSMOP CANCEL REQUEST, force the mount exit virtual machine to cancel the mount request with the FORCE option. To use the DSMOP CANCEL REQUEST command when running the mount exit, the server must have FORCE privilege. If you have entered a DSMOP REPLY command, attach the device to the server with the ATTACH option. To use the DSMOP REPLY command, the server must have ATTACH privilege.

ANR5255E (S/390)Command: No matching Exit Machines were found "Offline".

Explanation: A READY EXIT command has been issued and all Mount Exit Virtual Machines are ready.

System Action: Server operation continues.

User Response: None.

ANR5256E (S/390)Command: Invalid match pattern specified for Exit Machine name.

Explanation: A DSMOP READY command has been entered specifying a user ID that is not a defined mount exit virtual machine.

System Action: The server does not process the command.

User Response: Enter the command and specify the correct mount exit virtual machine name.

ANR5257I (S/390)Command: No requests outstanding.

Explanation: A DSMOP QUERY MOUNTS command has been entered when no mount requests are outstanding.

System Action: Server operation continues.

User Response: None.

ANR5258E (S/390)Command: Command not valid when Exit is active.

Explanation: A DSMOP REPLY command has been entered by a reply operator when the mount exit is active.

System Action: The server does not process the command.

User Response: The DSMOP REPLY command is invalid when the mount exit is used. When using mount exit machines, all mount requests are issued from the mount exit machines using your installation's procedures.

ANR5259E (S/390)Command: Command not valid when Exit is not active.

Explanation: A DSMOP READY command or a DSMOP QUERY EXITS command has been entered when the mount exit is not being used.

System Action: The server does not process the command.

User Response: None.

ANR5260E (S/390)Command: Volume volume not found.

Explanation: A DISMOUNT VOLUME command was issued, but the volume to be dismounted cannot be found.

System Action: Server operation continues.

User Response: Ensure that the correct volume name is entered.

ANR5261E (S/390)Command: Volume volume is not "Idle".

Explanation: A DISMOUNT VOLUME command has been issued, but the volume is in use and cannot be dismounted.

System Action: Server operation continues.

User Response: If it is necessary to dismount the volume, cancel the session or process that is using the volume, and reissue the command.

ANR5262E (S/390)Command: Device raddr not found.

Explanation: A DISMOUNT DEVICE command has been issued, but the device to be dismounted cannot be found.

System Action: Server operation continues.

User Response: Ensure that the correct device has been specified.

ANR5263E (S/390)Command: Device raddr is not "Idle".

Explanation: A DISMOUNT DEVICE command has been issued, but the device is in use and cannot be dismounted.

System Action: Server operation continues.

User Response: If it is necessary to dismount the device, cancel the session or process that is using the volume, and reissue the command.

ANR5264I (S/390)Command not executed - password has expired.

Explanation: An administrative command has been issued, but the administrator's password has expired.

System Action: Server operation continues.

User Response: Update your password by starting an administrative client session. Alternatively, the server system administrator may use the UPDATE ADMIN command to update an administrator's password.

ANR5265I (S/390)Command not executed - administrator name is locked.

Explanation: An administrative command has been issued, but the administrator's user ID is locked from accessing the server.

System Action: Server operation continues.

User Response: The server system administrator can issue the UNLOCK ADMIN command to restore access to a server administrative user ID.

ANR5266I (S/390)Command not executed - insufficient memory.

Explanation: An administrative command has been issued, but there is insufficient memory to execute the command.

System Action: Server operation continues.

User Response: Increase the region or virtual machine size for the server or lower the MAXSESSIONS parameter in the server options file and restart the server.

ANR5267I (S/390)Command not executed - internal error detected.

Explanation: An administrative command has been issued, but there is a detected internal processing error that prevents the command from executing.

System Action: Server operation continues.

User Response: Look for preceding message concerning access to administrative user ID information within the server and contact your service representative.

ANR5268I (S/390)Command not executed - insufficient recovery log space.

Explanation: An administrative command has been issued, but there is insufficient recovery log space to complete the database transaction.

System Action: Server operation continues.

User Response: To increase the amount of log space available to the server, an authorized admininstrator can add log volumes using the DEFINE LOGVOLUME command, and extend the size of the log using the EXTEND LOG command.

ANR5269I (S/390)Command not executed - insufficient database space.

Explanation: An administrative command has been issued, but there is insufficient database space to complete the database transaction.

System Action: Server operation continues.

User Response: To increase the amount of database space available to the server, an authorized admininstrator can add database volumes using the DEFINE DBVOLUME command, and extend the size of the database using the EXTEND DB command.

ANR5270I (S/390)SMFWTM macro return code 40 (buffer shortage).

Explanation: SMFWTM completed with return code 40.

System Action: The server continues to operate.

User Response: Increase SMF buffer limit or disable server accounting.

ANR5280I (S/390)Command accepted.

Explanation: A DSMOP REPLY command is accepted.

System Action: The server processes the DSMOP REPLY command.

User Response: None.

ANR5281I (S/390)Request request number for volume ID canceled by user ID.

Explanation: A mount request is successfully canceled.

System Action: The system cancels the mount request.

User Response: None.

ANR5282I (S/390)Request request number for volume ID cancelled (PERM) by user ID.

Explanation: A mount request is successfully canceled with the PERM option.

System Action: The system cancels the mount request and marks the volume as unavailable.

User Response: None.

ANR5283I (S/390)Exit Machine mountvm status set to "Ready".

Explanation: A DSMOP READY command has been entered.

System Action: The server changes the status of the mount exit virtual machine to ready.

User Response: None.

ANR5284I (S/390)Requests outstanding:

Explanation: The list of currently outstanding mount requests follows.

System Action: The server lists all outstanding mount requests or the one specified on the DSMOP QUERY command.

User Response: None.

ANR5285I (S/390)Exit Machine Status:

Explanation: The list of mount exit virtual machine status follows.

System Action: The server lists the status of all mount exit virtual machines or the status of the one specified on the DSMOP QUERY command.

User Response: None.

ANR5286I (S/390)Exit Machine mountvm: "Ready".

Explanation: The status of a mount exit virtual machine is ready.

System Action: Server operation continues.

User Response: None.

ANR5287I (S/390)Exit Machine mountvm: "Busy".

Explanation: The status of a mount exit virtual machine is busy.

System Action: Server operation continues.

User Response: None.

ANR5288I (S/390)Exit Machine mountvm: "Offline".

Explanation: The status of a mount exit virtual machine is off-line.

System Action: Server operation continues.

User Response: None.

ANR5289I (S/390)Volume volume (class class) mounted mode on raddr, status: "Idle".

Explanation: Volume volume, which is of device class class and is mounted at address raddr in mode mode, is eligible for dismounting or reuse.

System Action: Server operation continues.

User Response: None.

ANR5290I (S/390)Volume volume (class class) mounted mode on raddr, status: "In Use".

Explanation: Volume volume, which is of device class class and is mounted at address raddr in mode mode, is in use by the server.

System Action: Server operation continues.

User Response: None.

ANR5291I (S/390)Volume volume (class class) mounted mode on raddr, status: "Dismounting".

Explanation: Volume volume, which is in device class class and is mounted at address raddr in mode mode, is in the process of dismounting.

System Action: Server operation continues.

User Response: None.

ANR5292I (S/390) number volume(s) found.

Explanation: A QUERY MOUNT command has been issued; number volumes are mounted.

System Action: Server operation continues.

User Response: None.

ANR5293I (S/390)Cancelling mount for volume volume.

Explanation: A CANCEL MOUNT command has been issued for volume volume. The CANCEL command is being processed.

System Action: Server operation continues.

User Response: Query the activity log to verify that the mount request has been cancelled.

ANR5294I (S/390)Volume volume (class class) mounted mode, status: "Idle".

Explanation: Volume volume, which is in device class class in mode mode, is eligible for dismounting or reuse.

System Action: Server operation continues.

User Response: None.

ANR5295I (S/390)Volume volume (class class) mounted mode, status: "In Use".

Explanation: Volume volume, which is in device class class in mode mode, is in use by the server.

System Action: Server operation continues.

User Response: None.

ANR5296I (S/390)Volume volume (class class) mounted mode, status: "Dismounting".

Explanation: Volume volume, which is in device class class in mode mode, is in the process of dismounting.

System Action: Server operation continues.

User Response: None.

ANR5297I (S/390)Volume volume (class class) mounted mode, status: "In Retry".

Explanation: Volume volume, which is in device class class in mode mode, is currently in RETRY. An attempt is being made to re-establish communications with another server. If the volume remains in retry status for the amount of time specified by the device class retry period, the operation will fail and the volume will be automatically dismounted.

System Action: Server operation continues.

User Response: None.

ANR5300I (S/390)Verifying volume label volume ID on device real address.

Explanation: The server is verifying the volume label of a mounted read/write volume again prior to dismounting the volume.

System Action: The server performs the reverification of the volume label as an integrity check of the volume.

User Response: None.

ANR5301I (S/390)Request number: Verifying volume label volume ID on device device.

Explanation: The server is verifying the volume label of a mounted volume during the mount process.

System Action: The server ensures that the volume mounted is acceptable.

User Response: None.

ANR5302I (S/390)Request number: Assigning volume volume ID to SCRTCH.

Explanation: The server has assigned the mounted volume to be used as the requested scratch volume.

System Action: The server dynamically adds the volume label of the mounted volume to the storage pool.

User Response: None.

ANR5303I (S/390)Request number: Assigning volume volume ID to EXPORT.

Explanation: The server has assigned the mounted volume to be used as the requested export volume.

System Action: The server uses the volume for the EXPORT operation.

User Response: None.

ANR5304I (S/390)Request number: Assigning volume volume ID to IMPORT.

Explanation: The server has assigned the mounted volume to be used as the requested import volume.

System Action: The server uses the volume for the IMPORT operation.

User Response: None.

ANR5305E (S/390)Request number: Device real address is not a supported devclass device.

Explanation: A device is attached to the server to satisfy a mount request, but it is the wrong device class. For example, a CARTRIDGE device has been used when the request is for a REEL device.

System Action: The server dismounts the volume, detaches the device, and requests the original volume again.

User Response: Make sure the device used to satisfy a mount request is the same type as the device requested.

ANR5306E (S/390)Request number: Device real address not capable.

Explanation: The server requested a volume with a specific density or format. The device used to satisfy the mount cannot write using the requested density or format.

System Action: The server dismounts the volume, detaches the device, and requests the original volume again.

User Response: Mount the volume on a device capable of the requested density or format.

ANR5307E (S/390)Request number: Volume on real address is write protected.

Explanation: The mounted volume is not enabled for writing.

System Action: The server dismounts the volume, detaches the device, and requests the original volume again.

User Response: Enable the volume for writing and reply to the mount again.

ANR5308E (S/390)Request number: Volume on real address is not write protected.

Explanation: The mounted volume is not write protected.

System Action: The server dismounts the volume, detaches the device, and requests the original volume again.

User Response: Disable the volume for writing and reply to the mount again.

ANR5309E (S/390)Request number: Volume on real address has no VOL1 label.

Explanation: The mounted volume does not have a standard label.

System Action: The server dismounts the volume, detaches the device, and requests the original volume again.

User Response: Make sure you are mounting the correct volume. All volumes must have a standard VOL1 label.

ANR5310E (S/390)Volume on real address has no VOL1 label - volume integrity compromised.

Explanation: During volume unmount label reverification, the server finds no VOL1 label.

System Action: The server marks the volume as unavailable.

User Response: The volume cannot be used because the VOL1 label has been overwritten. All active data on the volume cannot be recovered. Delete the volume from the storage pool with the DELETE VOLUME command by using the DISCARD=YES option. To use this volume again, the volume must be initialized with a VOL1 label. The volume may then be redefined in the storage pool.

ANR5311E (S/390)Request number: Volume label on raddr (volume ID found) does not match volume ID expected.

Explanation: During mount processing, the volume ID read on the mounted volume does not match the specifically requested partially full volume.

System Action: The server dismounts the volume, detaches the device, and requests the original volume again.

User Response: Make sure you are mounting the correct volume.

ANR5312E (S/390)Volume label on raddr (volume ID found) does not match volume ID expected - volume integrity compromised.

Explanation: During volume unmount label reverification, the server finds a different VOL1 label.

System Action: The server marks the volume as unavailable.

User Response: The volume cannot be used because the VOL1 label has been overwritten by a different VOL1 label. All active data on the volume cannot be recovered. Delete the volume from the repository with the DELETE VOLUME command by using the NORECLAIM option. To use this volume again, the volume must be initialized with a VOL1 label. The volume may then be redefined in the repository.

ANR5313I (S/390)Request number: Mount for volume ID complete on device real address.

Explanation: A volume mount has successfully completed.

System Action: The task waiting for a volume mount resumes.

User Response: None.

ANR5314E (S/390)Request number: Permanent I/O error on device real address.

Explanation: A permanent I/O error occurred when the device was opened.

System Action: The server dismounts the volume, detaches the device, and requests the original volume again.

User Response: Mount the volume on a different device.

ANR5315E (S/390)Read Data Check on device real address.

Explanation: A data check occurred during a read operation.

System Action: The server redrives the I/O by using Diagnose X'20' or Diagnose X'A8'.

User Response: None.

ANR5316E (S/390)Write Data Check on device real address.

Explanation: A data check occurred during a write operation.

System Action: The server redrives the I/O by using Diagnose X'20' or Diagnose X'A8'.

User Response: None.

ANR5317I (S/390)Make device real address ready.

Explanation: The device is in a not ready condition.

System Action: The server sends an intervention required message to the mount operator user IDs listed in the DSMSERV OPT file.

User Response: Make the device ready.

ANR5318I (S/390)Intervention cleared on device real address.

Explanation: The device requiring operator intervention is now ready.

System Action: The task waiting for the device continues.

User Response: None.

ANR5319I (S/390)Intervention required on device real address.

Explanation: The device requires operator intervention.

System Action: The task waits until the device is made ready.

User Response: Make the device ready.

ANR5320I (S/390)Volume volume ID already in use.

Explanation: A tape volume has been mounted for use by the server; after mounting the volume, the server determined that the volume was already in use by the server and could not be used to satisfy the current mount request.

System Action: The server dismounts the volume, detaches the device, and reissues the original request.

User Response: Mount a volume not already in use by the server.

ANR5321I (S/390)End of volume reached for volume ID on device real address.

Explanation: During processing of a read/write tape volume, the end of the tape volume has been reached.

System Action: The volume is marked read-only and kept mounted for later use.

User Response: None.

ANR5322I (S/390)Permanent error on volume volume ID on device real address.

Explanation: During processing of a tape volume, a permanent I/O error occurred.

System Action: The server places the volume in an I/O error state. If the volume was being used for writing, it is marked read-only.

User Response: None.

ANR5323I (S/390)Assigning volume volume ID to SCRTCH.

Explanation: The server has assigned the mounted volume to be used as the requested scratch volume.

System Action: The server dynamically adds the volume label of the mounted volume to the storage pool.

User Response: None.

ANR5324I (S/390)Assigning volume volume ID to EXPORT.

Explanation: The server has assigned the mounted volume to be used as the requested export volume.

System Action: The server uses the volume for the EXPORT operation.

User Response: None.

ANR5325I (S/390)Assigning volume volume ID to IMPORT.

Explanation: The server has assigned the mounted volume to be used as the requested import volume.

System Action: The server uses the volume for the IMPORT operation.

User Response: None.

ANR5326E (S/390)Volume label on raddr (volume ID found) does not match volume ID expected.

Explanation: During mount processing, the volume ID read on the mounted volume does not match the specifically requested partially full volume.

System Action: The server dismounts the volume, detaches the device, and requests the original volume again.

User Response: Make sure you are mounting the correct volume.

ANR5327I (S/390)Request number: Assigning volume volume ID to DUMPDB.

Explanation: The server has assigned the mounted volume to be used as the requested DUMPDB volume.

System Action: The server uses the volume for the DUMPDB operation.

User Response: None.

ANR5328I (S/390)Request number: Assigning volume volume ID to LOADDB.

Explanation: The server assigns the mounted volume for use as the requested LOADDB volume.

System Action: The server uses the volume for the LOADDB operation.

User Response: None.

ANR5329I (S/390)Assigning volume volume ID to DUMPDB.

Explanation: The server assigns the mounted volume for use as the requested DUMPDB volume.

System Action: The server uses the volume for the DUMPDB operation.

User Response: None.

ANR5330I (S/390)Assigning volume volume ID to LOADDB.

Explanation: The server assigns the mounted volume for use as the requested LOADDB volume.

System Action: The server uses the volume for the LOADDB operation.

User Response: None.

ANR5331S (S/390)Volume volume ID damaged - recovery required.

Explanation: The server detects an error on the specified volume. The volume has been unexpectedly repositioned during write processing. Data may have been lost.

System Action: The server halts the process that is using the volume and marks the volume as read-only.

User Response: For EXPORT, DBBACKUP, or DBDUMP tapes, restart the export, backup, or dump operation. Do not use the tape for an IMPORT, DBRESTORE, or DBLOAD operation. If the tape is a storage pool volume, you can attempt to recover the data with the following steps:

  1. To identify any missing data, issue the AUDIT VOLUME command by specifying FIX=NO.
  2. If recoverable data exists on the tape, delete references to the missing data from the database by issuing the AUDIT VOLUME command and specifying FIX=YES.
  3. Issue the MOVE DATA command to remove all data from the damaged tape after the AUDIT (FIX=YES) has completed.

NOTE: Issuing an audit command on a damaged volume can result in a large number of logged messages.

ANR5332I (S/390)Request number: Assigning volume volume ID to DBBKUP.

Explanation: The server assigns the mounted volume for use as the requested DBBKUP volume.

System Action: The server uses the volume for the DBBKUP operation.

User Response: None.

ANR5333I (S/390)Assigning volume volume ID to DBBKUP.

Explanation: The server assigns the mounted volume for use as the requested DBBKUP volume.

System Action: The server uses the volume for the DBBKUP operation.

User Response: None.

ANR5334W (S/390)Volume volume ID reached end of tape.

Explanation: The server has detected end of tape for the specified volume. The volume reached the end of tape before the maximum capacity value specified in the device class was reached.

System Action: The server requests another volume if one is available. The current process stops writing to the specified volume.

User Response: Reduce the maximum capacity in the device class. The QUERY VOLUME command will indicate the actual capacity of the volume after it is full. Use the UPDATE DEVCLASS command to change the maximum capacity for the device class.

ANR5335E (S/390)Volume volume ID already used.

Explanation: A tape volume is mounted as scratch for use by the server. After mounting the volume, the server determines that the volume has already been used by the server and cannot be used to satisfy the current mount request. Mounting the volume as scratch may have destroyed some of the data previously written on that volume.

System Action: The server dismounts the volume, detaches the device, and reissues the original request.

User Response: Mount a volume not already in use by the server. The damaged volume must be replaced, restored, or deleted from the volume history file.

It is strongly recommended that you use the DEVCLASS EXPIRATION or RETENTION parameter to protect your tapes and prevent damage to tapes you create in the future.

ANR5336E (S/390)Volume volume ID must be read-only on 3590 device.

Explanation: The server requests a volume in a mode other than read-only. The 3590 device that is used to satisfy the mount cannot be used to write to the volume.

System Action: The server cancels the current operation.

User Response: Update the volume access to READONLY or insure that a device of the type used to create the volume is used to satisfy the mount.

ANR5337I (S/390)Assigning volume volume ID to BACKUPSET.

Explanation: The server has assigned the mounted volume to be used as the requested backupset volume.

System Action: The server uses the volume for the BACKUPSET operation.

User Response: None.

ANR5350E (S/390)Error locating block block number on device real address.

Explanation: A Locate Block CCW failed.

System Action: The server marks the volume in an I/O error condition and requests another volume be mounted.

User Response: This failure may be due to a hardware problem. Reset the error condition with the UPDATE VOLUME command. If the problem persists, use the DELETE VOLUME command with the DISCARD=NO option to remove the volume from the storage pool.

ANR5351E (S/390)Error reading BlockID on device real address.

Explanation: A Read Block ID CCW failed.

System Action: The server marks the volume in an I/O error condition and requests another volume be mounted.

User Response: This failure may be due to a hardware problem. Reset the error condition with the UPDATE VOLUME command. If the problem persists, use the DELETE VOLUME command with the DISCARD=NO option to remove the volume from the storage pool.

ANR5352E (S/390)Synchronize failed on device real address.

Explanation: A Synchronize CCW failed.

System Action: The server marks the volume in an I/O error condition, and requests another volume be mounted.

User Response: Reply to the new mount request. Reset the error condition with the UPDATE VOLUME command. The integrity of the original volume may have been compromised. To delete the volume, issue the DELETE VOLUME command with the DISCARD=NO option.

ANR5353E (S/390)Load Display failed on device real address.

Explanation: A Load Display CCW failed.

System Action: Server operation continues. No text is loaded into the display window.

User Response: None.

ANR5354E (S/390)Block block number sequence error on device real address.

Explanation: During a read operation, the block ID of the block being read does not match the block ID stored in the data block header.

System Action: The server places the volume in an I/O error state.

User Response: The integrity of the volume may have been compromised. Reset the error condition with the UPDATE VOLUME command and attempt the operation on a different tape drive. If the problem persists, you can delete the volume with the DELETE VOLUME command, by using the DISCARD=NO option.

ANR5355E (S/390)Reload cartridge on device real address.

Explanation: The cartridge is not inserted correctly, or the tape is not processed correctly.

System Action: The task waits until the drive is made ready. An intervention required message is sent to the mount operator user IDs.

User Response: Make the drive ready.

ANR5356E (S/390)Unload cartridge on device real address.

Explanation: The drive cannot maintain tape tension and control tape movement during an unload operation.

System Action: The task waits until the drive is made ready. An intervention required message is sent to the mount operator user IDs.

User Response: Make the drive ready.

ANR5357E (S/390)Manual Rewind/Rewind-Unload on device real address.

Explanation: The Rewind Unload switch or the Rewind switch on the drive has been pressed.

System Action: The server verifies the volume label and attempts to reposition the tape and continue operation. If the volume label verification fails, the server marks the volume in the unavailable state. If the reposition fails, the server marks the volume in the I/O error state.

User Response: If the server succeeds in its recovery, no action is required. If recovery is unsuccessful, you can reset the error status of the volume with the UPDATE VOLUME command. Volume integrity may have been compromised. Issue the DELETE VOLUME command with the DISCARD=NO option to try to recover any data.

ANR5358E (S/390)Request number: I/O Error at beginning of tape on real address.

Explanation: An I/O error has occurred attempting to mount a tape volume; the beginning of the volume cannot be detected.

System Action: The server places the volume in an I/O error state.

User Response: The integrity of the volume may have been compromised. Reset the error condition with the UPDATE VOLUME command and attempt the operation on a different tape drive. If the problem persists, you can delete the volume with the DELETE VOLUME command, by using the DISCARD=NO option.

ANR5359E (S/390)Request number: Cartridge Length Error on device real address.

Explanation: A tape cartridge has been mounted that is too short for processing on the drive.

System Action: The server marks the volume in an I/O error condition and requests another volume be mounted.

User Response: Reply to the new mount request. If necessary, reset the error condition with the UPDATE VOLUME command. The integrity of the original volume may have been compromised. To delete the volume, issue the DELETE VOLUME command with the DISCARD=NO option.

ANR5360E (S/390)Request number: Cartridge Length Incompatible on device real address.

Explanation: A tape cartridge has been mounted on a drive and the tape is too long to be processed on the drive or has been initialized to the wrong length.

System Action: The server marks the volume in an I/O error condition and requests another volume be mounted.

User Response: Reply to the new mount request. If necessary, reset the error condition with the UPDATE VOLUME command. The integrity of the original volume may have been compromised. To delete the volume, issue the DELETE VOLUME command with the DISCARD=NO option.

ANR5361E (S/390)Request number: Cartridge Format Incompatible on device real address.

Explanation: A tape cartridge has been mounted on a drive, but the tape format cannot be processed on the drive.

System Action: The server marks the volume in an I/O error condition and requests another volume be mounted.

User Response: Reply to the new mount request. If necessary, reset the error condition with the UPDATE VOLUME command. The integrity of the original volume may have been compromised. To delete the volume, issue the DELETE VOLUME command with the DISCARD=NO option.

ANR5362E (S/390)Request number: Cartridge Length Violation on device real address.

Explanation: A tape cartridge has been mounted on a drive but the tape is too long to be processed on the drive.

System Action: The server marks the volume in an I/O error condition and requests another volume be mounted.

User Response: Reply to the new mount request. If necessary, reset the error condition with the UPDATE VOLUME command. The integrity of the original volume may have been compromised. To delete the volume, issue the DELETE VOLUME command with the DISCARD=NO option.

ANR5363E (S/390)Request number: Cartridge Compaction Incompatible on device real address.

Explanation: A tape cartridge has been mounted on a drive but the tape compression algorithm ID is not compatible with the drive.

System Action: The server marks the volume in an I/O error condition and requests another volume be mounted.

User Response: Reply to the new mount request. If necessary, reset the error condition with the UPDATE VOLUME command. The integrity of the original volume may have been compromised. To delete the volume, issue the DELETE VOLUME command with the DISCARD=NO option.

ANR5364E (S/390)Record sequence error on device real address.

Explanation: During processing of a tape volume, the record tape number read does not match that expected by the drive.

System Action: The server marks the volume in an I/O error condition.

User Response: This failure may be due to a hardware problem. Reset the error condition with the UPDATE VOLUME command. If the problem persists, use the DELETE VOLUME command with the DISCARD=NO option to remove the volume from the storage pool.

ANR5365E (S/390)Volume fenced on device real address.

Explanation: During processing of a tape volume, errors have occurred that caused the tape drive to lose the ability to process the volume.

System Action: The server marks the volume in an I/O error condition.

User Response: Unload and reload the tape to reset the drive. Reset the error condition with the UPDATE VOLUME command. This failure may be due to a hardware problem. If the problem persists, use the DELETE VOLUME command with the DISCARD=NO option to remove the volume from the storage pool.

ANR5366E (S/390)Request number: Volume volume ID data set name "label dsn" in HDR1 label cannot be overwritten with Export data set name "export dsn".

Explanation: During mount processing of an EXPORT tape volume, the server encountered a nonblank data set name in the HDR1 label. Normally, the server writes the export dsn in this field.

System Action: The server dismounts the volume, detaches the device, and requests the original volume again.

User Response: Most tape volume initialization programs only write VOL1 label. If your tape volume initialization program also writes a HDR1 label, the data set name in the HDR1 label must be blank. Be sure that the volume in question is the proper tape volume, and reinitialize it with only a VOL1 label, or with a blank data set name in the HDR1 label.

ANR5367I (S/390)Request number: Volume volume ID data set name "label dsn" in HDR1 label will be overwritten with Export data set name "export dsn".

Explanation: During mount processing of an EXPORT tape volume, the server encountered a nonblank data set name in the HDR1 label. This data set name will be overwritten with export dsn.

System Action: The server continues with mount processing.

User Response: None.

ANR5368E (S/390)Request number: Volume volume ID data set name "label dsn" in HDR1 label cannot be overwritten with DUMPDB data set name "dumpdb dsn".

Explanation: During mount processing of an DUMPDB tape volume, the server encountered a nonblank data set name in the HDR1 label. Normally, the server would write the dumpdb dsn in this field.

System Action: The server dismounts the volume, detaches the device, and requests the original volume again.

User Response: Most tape volume initialization programs only write a VOL1 label. If your tape volume initialization program also writes a HDR1 label, the data set name in the HDR1 label must be blank. Be sure the volume in question is the correct tape volume, and reinitialize it with only a VOL1 label, or with a blank data set name in the HDR1 label.

ANR5369I (S/390)Request number: Volume volume ID data set name "label dsn" in HDR1 label will be overwritten with DUMPDB data set name "dumpdb dsn".

Explanation: During mount processing of an DUMPDB tape volume, the server encountered a nonblank data set name in the HDR1 label. This data set name will be overwritten with dumpdb dsn.

System Action: The server continues with mount processing.

User Response: None.

ANR5370E (S/390)Invalid block header on device real address.

Explanation: During a read operation, the block header of the block read does not contain data recognized by the server.

System Action: The server may place the volume in an I/O error state.

User Response: The integrity of the volume may have been compromised. Reset the error condition with the UPDATE VOLUME command and attempt the operation on a different tape drive. If the problem persists, try to audit the volume by using the AUDIT VOLUME command to see if any files on the volume can be recovered. If not, you can delete the volume with the DELETE VOLUME command, by using the DISCARD=NO option.

If a LOADDB operation was being performed, specify the command syntax by either using a ddname or by specifying a device class name. You must use the same method that was used when the data base was originally dumped. Otherwise, this error message is displayed. Try loading the data base by using the other method of syntax (ddname). Also, verify that you specified the correct volume name. The integrity of the volume may have been compromised. In this case, the volume cannot be used by the LOADDB operation.

ANR5371E (S/390)Request number: Volume volume ID data set name "label dsn" in HDR1 label cannot be overwritten with DBBKUP data set name "dbbkup dsn".

Explanation: During mount processing of a DBBKUP tape volume, the server encountered a nonblank data set name in the HDR1 label. Normally, the server writes the dbbkup dsn in this field.

System Action: The server dismounts the volume, detaches the device, and requests the original volume again.

User Response: Most tape volume initialization programs only write VOL1 label. If your tape volume initialization program also writes a HDR1 label, the data set name in the HDR1 label must be blank. Be sure that the volume in question is the proper tape volume, and reinitialize it with only a VOL1 label, or with a blank data set name in the HDR1 label.

ANR5372I (S/390)Request number: Volume volume ID data set name "label dsn" in HDR1 label will be overwritten with DBBKUP data set name "dbbkup dsn".

Explanation: During mount processing of a DBBKUP tape volume, the server encountered a nonblank data set name in the HDR1 label. This data set name will be overwritten with dbbkup dsn.

System Action: The server continues with mount processing.

User Response: None.

ANR5373I (S/390)Unable to allocate tape drive with device type device type for tape volume ID. Reply 'C' (cancel), 'R' (retry), or 'W' (wait).

Explanation: The server attempts to allocate a tape drive. The allocation attempt fails because no acceptable tape drive is available. An acceptable tape drive has the device type indicated in the message.

Before more attempts are made to allocate the tape drive, the operator is prompted to indicate whether or not the tape drive allocation request can be satisfied. The device type and the VOLSER of the tape volume volser to be used for the pending request are provided in the message text.

System Action: If the operator replies 'R' (meaning retry), the server will retry the tape drive allocation. If no acceptable drive is available after retrying the allocation, the server will reissue this message.

If the operator replies 'W' (meaning wait), the server will retry the tape drive allocation. If the allocation request cannot be satisfied immediately, the server will wait while MVS Allocation Recovery issues message IEF238D. After IEF238D is issued, none of the following can occur in the server until the allocation completes or is canceled:

If the operator replies 'C' (meaning cancel), the server will fail the tape drive allocation and its associated server request.

Any other reply will cause the server to reissue this message. Determine if there are any tape drives which can be used to satisfy this request (either online or offline) prior to responding to this message.

User Response: None.

ANR5374I (S/390)Tape volume volume ID on real address real address has had an unsolicited interrupt, and may have been dismounted.

Explanation: An unsolicited interrupt is received for the drive where the volume is mounted. The drive is not ready or its state cannot be determined, so the tape may have been dismounted.

System Action: If the server can recover without possibility of data loss, it will reverify the label and continue operations. If the label is not verified or data loss is possible with continued use, the next operation will fail and the tape will be dismounted.

User Response: Check the tape drive.

ANR5404I (S/390)SERVER volume volume name mounted.

Explanation: The server has mounted the given volume.

System Action: Read or write operations, or both, will commence for the volume.

User Response: None.

ANR5405I (S/390)End-of-volume reached for SERVER volume volume name.

Explanation: The server has detected an end-of-volume condition for the given volume.

System Action: The volume is marked full. If more data must be stored, the server accesses another volume.

User Response: None.

ANR5410I (S/390)FILE volume volume name mounted.

Explanation: The server has opened the given file to simulate a tape volume.

System Action: Read or write operations, or both, will commence for the volume.

User Response: None.

ANR5411I (S/390)End-of-volume reached for FILE volume volume name.

Explanation: The server has detected an end-of-volume condition for the given volume.

System Action: The volume is marked full. If more data must be stored, the server accesses another volume.

User Response: None.

ANR5412I (S/390)FILE volume volume name MAXCAPACITY larger than allowed maximum. Overriding maximum capacity to FILE maximum capacityMB.

Explanation: The maximum capacity specified for the listed volume is larger than the maximum allowed for the FILE device class.

System Action: The volume capacity is set to the maximum allowed for the FILE device class.

User Response: Update the device class of the volume MAXCAPACITY value to less than or equal the maximum allowed for the FILE device class.

ANR5413E (S/390)Dynamic allocation of FILE volume volume on unit=unit volser=volser returned rc=rc, info code=info code, error code=error code.

Explanation: The dynamic allocation of FILE volume volume on unit unit and volume serial volser fails. The server uses the unit and volser device class parameters when allocating new FILE volumes, and always catalogs the actual MVS data sets. If these parameters are not defined, Dynamic Allocation uses system defaults to select a device on which to create the MVS sequential data set.

For previously allocated FILE volumes, the server allows Dynamic Allocation to locate the actual MVS data set using catalog services.

The return code rc, information code info code and error code error code are in decimal and can be found in the Dynamic Allocation section of MVS/ESA Programming: Authorized Assembler Services Guide.

System Action: Server operation continues.

User Response: For new FILE volumes, verify that all device class parameters are defined correctly and are compatible, and that space is available on the target DASD.

ANR5414E (S/390)Error error code returned while opening FILE volume volume

Explanation: The BSAM OPEN fails. Error code error code is returned. Check for accompanying MVS error messages.

Error codes greater than eight are MVS ABEND codes, documented in MVS/ESA System Codes, GC28-1486.

System Action: Server operation continues.

User Response: For previously allocated FILE volumes, verify that the MVS data set used for the FILE volume exists on the physical device designated by the catalog. Check the accompanying MVS system messages.

ANR5415W (S/390)SFS CSL call CSL name failed with return code rc, reason code rs. optional (file or directory being processed)

Explanation: A call to an SFS CSL routine failed.

System Action: See following server messages.

User Response: Check the return and reason codes in the System Messages and Codes manual, "Callable Services Library (CSL) Reason Codes" section, for information on the problem and on the action needed to correct it.

ANR5416E (S/390)Minidisk device class cannot be used with SFS file file name.

Explanation: A device class of DEVTYPE=FILE is defined with FILEMODE= where the file mode letter is associated with an SFS directory. Device classes defined with DEVTYPE=FILE and FILEMODE= parameters can only be associated with an accessed minidisk (CMS file mode letter A-Z).

System Action: File is not used.

User Response: When using a minidisk, define the DEVTYPE=FILE device class with the FILEMODE= parameter. When using an SFS directory, use the DIRECTORY= parameter.

ANR5417E (S/390)File file name already exists, it cannot be created.

Explanation: The server attempted to create a new file using file name but received indication that the file already exists. The server will create a new file after it determines that the file named file name is not in its database. The server will append to an existing file with the name file name only if it exists in its database. The server will not overwrite an existing file.

System Action: File is not used.

User Response: The file named file name must either be renamed or erased.

ANR5418E (S/390)File file name cannot be used.

Explanation: The server found that the file file name exists in its database, but either was accessed as read-only or the file did not exist on the minidisk identified by the file mode letter or the file did not exist in the SFS directory.

System Action: File is not used.

User Response: Make sure the minidisk is accessed with the file mode letter specified for the device class defined with DEVTYPE=FILE FILEMODE=?. If the file is in an SFS directory, make sure the SFS directory still exists and the server user ID has been granted read/write authority to the directory and to the file named command. If the volume status is read/write and the volume is not full, write access is required. If the file does not exist, the server cannot use the volume. Storage volumes should be deleted using the DELETE VOLUME command with DISCARDDATA=YES. Volumes for IMPORT, LOAD or RESTORE DB cannot be used.

ANR5419E (S/390)Filemode or directory filemode or directory name cannot be used.

Explanation: The server determined that a minidisk with the file mode letter filemode or that the SFS directory directory name were not available for use.

System Action: Server operation continues but file is not used.

User Response: Ensure that a minidisk is accessed with the file mode letter filemode or that an SFS directory directory directory exists and that the server user ID has been granted read/write authority to the directory and all files in that directory.

ANR5420W (S/390)FILE FILE name not deleted from system, return code return code.

Explanation: A volume associated with a device class defined with DEVTYPE=FILE was deleted from the server, but the associated CMS file or MVS data set FILE name could not be deleted.

System Action: Server operation continues. No other attempts will be made to delete the volume from the system.

User Response: If the volume was created and never used, a CMS file or an MVS dataset may not have been created and no action is required. If the CMS file or the MVS dataset FILE name exists it will have to be deleted manually.

ANR5450E (S/390)Error opening filespec.

Explanation: An error occurred while attempting an open operation.

System Action: Server processing continues.

User Response: Refer to the other displayed messages to determine why the open operation failed. Correct the problem and restart the process.

ANR5451E (S/390)An error (error code) occurred during a write operation.

Explanation: An error occurred while attempting a write operation.

System Action: Server processing continues.

User Response: Refer to the other displayed messages to determine why the write operation failed. Correct the problem and restart the process.

ANR5452E (S/390)An error (error code) occurred during a read operation.

Explanation: An error occurred while attempting a read operation.

System Action: Server processing continues.

User Response: Refer to the other displayed messages to determine why the read operation failed. Correct the problem and restart the process.

ANR5453E (S/390)Device type volume volume name cannot be overwritten by EXPORT operation.

Explanation: The specified volume already exists or contains data. The server does not allow new export data to be written to the volume.

System Action: The server detects that the given volume already contains some data that would be overwritten by the requested export operation.

User Response: If the specified volume does not contain any valuable data, delete it and retry the export operation.

ANR5454E (S/390)Device type volume volume name cannot be overwritten by DUMPDB operation.

Explanation: The specified volume already exists or contains data. The server does not allow new dump data to be written to the volume.

System Action: The server detects that the given volume already contains some data that would be overwritten by the requested dump operation.

User Response: If the specified volume does not contain any valuable data, delete it and retry the dump operation.

ANR5455E (S/390)Device type volume volume name cannot be overwritten by BACKUP DB operation.

Explanation: The specified volume already exists or contains data. The server does not allow new backup data to be written to the volume.

System Action: The server detects that the given volume already contains some data that would be overwritten by the requested backup operation.

User Response: If the specified volume does not contain any valuable data, delete it and retry the backup operation.

ANR5456E (S/390)Device type volume volume name cannot be overwritten by BACKUPSET operation.

Explanation: The specified volume already exists or contains data. The server does not allow new backupset data to be written to the volume.

System Action: The server detects that the given volume already contains some data that would be overwritten by the requested backupset operation.

User Response: If the specified volume does not contain any valuable data, delete it and retry the backupset operation.

ANR5499E (S/390)command: Required parameter was not specified parameter.

Explanation: The command command has been issued, but without a required parameter. If two parameters are listed, the command requires at least one of the parameters.

System Action: Server operation continues.

User Response: Reissue the command and specify the missing parameter and any additional parameters that are required for the command. The HELP DEFINE or HELP UPDATE commands may be used to obtain syntax assistance.

ANR5500E (S/390)Command: Device type not specified.

Explanation: The command command has been issued, but without the DEVTYPE keyword.

System Action: Server operation continues.

User Response: Reissue the command, and specify the DEVTYPE keyword and any additional parameters that are required for the command. The HELP DEFINE or HELP UPDATE commands may be used to obtain syntax assistance.

ANR5501E (S/390)Command: "attribute" is invalid for device type.

Explanation: The command command has been issued with an incompatible combination of device type and attribute.

System Action: Server operation continues.

User Response: Reissue the command, and specify a compatible set of attributes. The HELP DEFINE or HELP UPDATE commands may be used to obtain syntax assistance.

ANR5502E (S/390)Command: "LENGTH" is invalid with 3480 and 3480XF formats.

Explanation: The command command has been issued with an incompatible combination of device type, FORMAT, and LENGTH. A length specification is invalid with 3480 and 3480XF formats.

System Action: Server operation continues.

User Response: Reissue the command, and specify a compatible set of attributes. For 3480 and 3480XF formats, reenter the command without a LENGTH keyword. The HELP DEFINE or HELP UPDATE commands may be used to obtain syntax assistance.

ANR5503E (S/390)Command: Invalid parameter for update - parameter.

Explanation: The command command has been issued. However, the parameter is not an attribute that must be updated.

System Action: Server operation continues.

User Response: Reissue the command, and specify a compatible set of attributes. The HELP UPDATE command may be used to obtain syntax assistance.

ANR5504E (S/390)Command: "new attribute" conflicts with existing "old attribute".

Explanation: The command command has been issued. However, new attribute conflicts with old attribute in updating the device class.

System Action: Server operation continues.

User Response: Reissue the command, and specify a compatible set of attributes. You may have to specify additional keywords to update the device class in a compatible manner. The HELP UPDATE command may be used to obtain syntax assistance.

ANR5505E (S/390)Command: "MOUNTLIMIT" is less than current number of mounted volumes.

Explanation: The command command has been issued that specifies a MOUNTLIMIT smaller than the existing number of volumes that are already allocated.

System Action: Server operation continues.

User Response: You may wait until volumes are no longer in use to reissue the command. Alternatively, you may cancel sessions or processes that are using volumes; then issue DISMOUNT commands to free allocated volumes before reissuing the command. The QUERY MOUNT command can be issued to determine which volumes are mounted for use by the server.

ANR5506E (S/390)Command: Conflicting parameters "parm1" and "parm2".

Explanation: The command command has been issued that specifies conflicting parameters parm1 and parm2. Conflicting parameters include specifying FORMAT and LENGTH with DENSITY, and RETENTION with EXPIRATION.

System Action: Server operation continues.

User Response: Reissue the command, and specify a compatible set of parameters. The HELP DEFINE or HELP UPDATE commands may be used to obtain syntax assistance.

ANR5507E (S/390)Command: Device type "devtype" not supported on this platform.

Explanation: An unsupported device type has been specified for command. In MVS, for example, the REEL device type is not supported.

System Action: Server operation continues.

User Response: Specify a valid device type for the platform. The HELP DEFINE command may be used to obtain syntax assistance.

ANR5508E (S/390)Device class device class not defined in device configuration file.

Explanation: The issued command requires that the specified device class be defined in the device configuration file. The definition was not found.

System Action: The command is not processed.

User Response: Reissue the command, and specify a valid device class. You may also want to refresh your device configuration file by issuing the BACKUP DEVCONFIG command.

ANR5509E (S/390)Command: Parameter Parameter is larger than the allowed maximum of Maximum valueM.

Explanation: The specified parameter is larger than the allowed maximum for this device class.

System Action: The command is not processed.

User Response: Reissue the command, and specify a parameter less than or equal to the allowed maximum.

ANR5510E (S/390)Data set name dsn is not valid.

Explanation: Data set name dsn is not valid.

System Action: Server operation continues.

User Response: Reissue the server command, and specify a valid data set name.

ANR5511E (S/390)Unit name unit is not valid.

Explanation: Unit name unit is not valid.

System Action: Server operation continues.

User Response: Reissue the server command, and specify a valid unit name.

ANR5512E (S/390)Volume serial volser is not valid.

Explanation: Volume serial volser is not valid.

System Action: Server operation continues.

User Response: Reissue the server command, and specify a valid volume serial.

ANR5513E (S/390)Expiration date expdt is not valid.

Explanation: Expiration data expdt is not valid.

System Action: Server operation continues.

User Response: Reissue the server command, and specify a valid expiration date.

ANR5514E (S/390)Retention period retpd is not valid.

Explanation: Retention period retpd is not valid.

System Action: Server operation continues.

User Response: Reissue the server command, and specify a valid retention period.

ANR5953W (S/390)Unable to generate accounting record - ACCT option not specified in CP directory.

Explanation: The SET ACNT ON command has been entered, but the server is unable to generate an accounting record because the ACCT option has not been specified in the server's CP directory entry.

System Action: Server operation continues. No accounting record is generated.

User Response: Add the ACCT option to the server's CP directory entry. To suppress these messages until the CP directory can be updated, enter the SET ACNT OFF command.

ANR5954W (S/390)Unable to generate accounting record - insufficient memory.

Explanation: The SET ACNT ON command has been entered, but the server is unable to generate an accounting record due to a lack of memory (virtual storage). In some cases a 4096-byte buffer is required for accounting operations, and it is this buffer that cannot be allocated.

System Action: Server operation continues. No accounting record is generated.

User Response: Allocate additional storage to the server virtual machine. There are three ways to do this:

  1. Increase the size of the server's virtual machine. This requires that the default storage size be updated in the server's CP directory entry.
  2. Reduce the maximum number of client sessions permitted. To do this, edit the DSMSERV OPT file and reduce the value specified for the MAXSESSIONS statement. Note that each client session causes an additional 64KB of memory to be allocated.
  3. Decrease the amount of space allocated to the server's database buffer pool. To do this, edit the DSMSERV OPT file and reduce the value specified for the BUFPOOLSIZE statement. Note that each buffer pool page causes an additional 4 KB of memory to be allocated.

Note that the server must be shut down (with the HALT command) before changes can be made to the DSMSERV OPT file.

ANR5956E (S/390)C library not available, unable to continue.

Explanation: The C/370 or LE/370 library is not available.

System Action: Server operation ends.

User Response: Make the C/370 or LE/370 library available to the server.

ANR5957W (S/390)C library is at level level.

Explanation: The C run-time library is at a lower level (level) than expected.

System Action: Server attempts to continue operation.

User Response: Ensure that the proper level of the C/370 or LE/370 library is installed and available to the server.

ANR5958E (S/390)SVM is at level level, the server requires at least required-level, unable to continue.

Explanation: The SVM run-time library is at level level, but the server requires at least level required-level.

System Action: Server operation ends.

User Response: Check the required PTFs for the server. Ensure that the proper level of SVM is installed.

ANR5959E (S/390)Server not running APF authorized. The server and all JOBLIB/STEPLIB libraries (C library and other libraries) must be authorized.

Explanation: The server is not running with MVS authorization.

System Action: Server operation ends.

User Response: Ensure that all library data sets required by the server are authorized.

ANR5960E (S/390)Unable to initialize kernel - virtual machine requires ECMODE capability.

Explanation: The CP directory entry for the server does not contain an OPTION ECMODE statement.

System Action: Server operation ends.

User Response: Add an OPTION ECMODE statement to the CP directory entry for the server.

ANR5961E (S/390)Insufficient memory for server initialization.

Explanation: The server program cannot allocate enough memory (virtual storage) to fully initialize itself.

System Action: Server initialization fails. The server is not started.

User Response: Allocate additional storage to the server virtual machine or reduce the storage required by the server. There are three ways to do this:

  1. Increase the size of the server's virtual machine. This requires that the default storage size be updated in the server's CP directory entry.

    For MVS, increase the region size; 40M is the recommended minimum size for the server but larger servers require more.

  2. Reduce the maximum number of client sessions permitted. To do this, edit the DSMSERV OPT file and reduce the value specified for the MAXSESSIONS statement. Note that each client session causes an additional 64KB of memory to be allocated.
  3. Decrease the amount of space allocated to the server's database buffer pool. To do this, edit the DSMSERV OPT file and reduce the value specified for the BUFPOOLSIZE statement. Note that each buffer pool page causes an additional 4 KB of memory to be allocated.

Note that the server must be shut down (with the HALT command) before changes can be made to the DSMSERV OPT file.

ANR5962I (S/390)DSMSERV generated at time on date.

Explanation: The server module has been generated at the indicated date and time.

System Action: Server operation continues.

User Response: None.

ANR5963I (S/390)Server termination complete.

Explanation: The server has completed shut down.

System Action: Server operation ends.

User Response: None.

ANR5964E (S/390)Server unable to mark itself non-swappable. Return code rc from SYSEVENT TRANSWAP.

Explanation: The server cannot issue a SYSEVENT TRANSWAP macro.

System Action: Server operation ends.

User Response: Contact your service representative.

ANR5965I (S/390)Console command: command

Explanation: A server command command has been received from an MVS operator console.

System Action: Server operation continues.

User Response: None.

ANR5967W (S/390)Accounting record not produced, return code rc.

Explanation: There was a problem generating the accounting record.

System Action: Server operation continues.

User Response: Contact your service representative.

ANR5980E (S/390)Unable to initialize PDM driver - insufficient memory.

Explanation: The server's PDM communications driver is unable to initialize itself due to insufficient memory (virtual storage).

System Action: Server initialization fails.

User Response: Allocate additional storage to the server virtual machine. There are three ways to do this:

  1. Increase the size of the REGION parameter on the EXEC or JOB statement of the JCL used to start the server.
  2. Reduce the maximum number of client sessions permitted. To do this, edit the server options file and reduce the value specified for the MAXSESSIONS statement. Note that each client session causes an additional 64KB of memory to be allocated.
  3. Decrease the amount of space allocated to the server's database buffer pool. To do this, edit the server options file and reduce the value specified for the BUFPOOLSIZE statement. Note that each buffer pool page causes an additional 4KB of memory to be allocated.

Note that the server must be shut down (with the HALT command) before changes can be made to the server options file.

ANR5981I (S/390)InfoSpeed/PDM communication enabled on port port number.

Explanation: The server's PDM communications driver is ready to receive connection requests from clients.

System Action: Server operation continues.

User Response: None.

ANR5982E (S/390)InfoSpeed accept error rc = rc on port port number.

Explanation: The server's InfoSpeed communications driver has received an error from the ACCEPT function.

System Action: Server operation continues and InfoSpeed communications will be retried.

User Response: None.

ANR6200ICommand name: Level compression audit level compression audit started as process process ID.

Explanation: A compression audit at the specified level has been started as a background server process with the process identifier reported.

System Action: Server operation continues. The background audit attempts to identify client files that may be affected by the client compression problem.

User Response: None.

ANR6201ICommand name: Level compression audit level compression audit starting as background process process ID.

Explanation: A compression audit at the specified level was started as a background server process having the process identifier reported.

System Action: Server operation continues. The background audit attempts to identify client files that may be affected by the client compression problem.

User Response: None.

ANR6202ICommand name: Verifying candidates from last audit.

Explanation: A compression audit has started to verify the client file candidates that were identified in a previous compression audit execution. The verification process eliminates compression candidates that are now found to be expired by policy on the server.

System Action: The audit operation continues.

User Response: None.

ANR6203ICommand name: Starting level audit level compression audit from qualifying entries in the candidates list.

Explanation: A compression audit is starting to check qualifying candidates from the candidates list for the audit level specified. Client files that were identified as compression candidates at a lower level will be tested, subject to the qualifications that were specified for the command.

System Action: The audit operation continues.

User Response: The compression candidate list can be displayed with the QUERY COMPRESSION command. The QUERY PROCESS command can be used to monitor the progress of the audit operation.

ANR6204ICommand name: Process process ID, level audit level audit, ended successfully - compression suspects = total number of compression suspects.

Explanation: A compression audit ended and is reporting the total number of suspect client files that have been found.

System Action: The audit operation completes.

User Response: The compression candidate list can be displayed with the QUERY COMPRESSION command.

ANR6205ICommand name: Process process ID, continuing Level 1 compression audit with object object ID high order number.object ID low order number.

Explanation: A level 1 compression audit is starting to evaluate client files for signs that they may be affected by the client compression problem. Since a previous level 1 audit has been executed, this audit will continue where the last audit stopped starting with the object whose identifier is specified.

System Action: The audit operation continues.

User Response: The compression candidate list can be displayed with the QUERY COMPRESSION command. The QUERY PROCESS command can be used to monitor the progress of the audit operation.

ANR6206ICommand name: Process process ID, starting base level 1 compression audit.

Explanation: A level 1 compression audit is starting to evaluate client files for signs that they may be affected by the client compression problem. The audit starts with the first client file found on the server, even if previous level 1 audits have been executed.

System Action: The audit operation continues

User Response: The compression candidate list can be displayed with the QUERY COMPRESSION command. The QUERY PROCESS command can be used to monitor the progress of the audit operation.

ANR6207ICommand name: Process process ID, level audit level analysis detected candidate file high-level object name low-level object name in file space client filespace name for node client node name.

Explanation: A compression audit has found a candidate file at the audit level specified. The name of the client node, file space, and file are displayed. This message is issued whenever a candidate file is detected during a compression audit that was started with the VERBOSE=YES parameter specified.

System Action: The audit operation continues.

User Response: The compression candidate list can be displayed with the QUERY COMPRESSION command. The QUERY PROCESS command can be used to monitor the progress of the audit operation.

ANR6208ICommand name: Process process ID, was cancelled - number of candidate files candidate files were found in number of files examined files examined prior to cancellation.

Explanation: A compression audit operation was canceled with the CANCEL PROCESS command before completion. The number of candidate files that were found prior to the cancellation are displayed.

System Action: The audit operation ends.

User Response: The compression audit may be restarted with the AUDIT COMPRESSION command. The compression candidate list can be displayed with the QUERY COMPRESSION command.

ANR6209ICommand name: Process process ID, level audit level audit completed successfully - number of candidate files candidate files were found in number of files examined files examined.

Explanation: A compression audit operation completed successfully. The number of candidate files that were found are displayed.

System Action: The audit operation ends.

User Response: The compression candidate list can be displayed with the QUERY COMPRESSION command.

ANR6210ICommand name: Process process ID, level audit level audit completed successfully - number of candidate files candidate files were found.

Explanation: A compression audit operation completed successfully. The number of candidate files that have been found are displayed.

System Action: The audit operation ends.

User Response: The compression candidate list can be displayed with the QUERY COMPRESSION command.

ANR6211ICommand name: Process process ID, level audit level analysis detected candidate file object name in file space client filespace name for node client node name.

Explanation: A compression audit has found a candidate file at the audit level specified. The name of the client node, file space, and file are displayed. This message is issued whenever a candidate file is detected during a compression audit that was started with the VERBOSE=YES parameter specified.

System Action: The audit operation continues.

User Response: The compression candidate list can be displayed with the QUERY COMPRESSION command. The QUERY PROCESS command can be used to monitor the progress of the audit operation.

ANR6212ICommand name: Process process ID, level audit level analysis eliminated level candidate level candidate file object name in filespace client filespace name for node client node name from candidate status.

Explanation: A compression audit at the level specified has eliminated a candidate file through further analysis. The name of the client node, file space, and file are displayed. This message is issued whenever a candidate file is eliminated from consideration during a compression audit that was started with the VERBOSE=YES parameter specified.

System Action: The audit operation continues.

User Response: The compression candidate list can be displayed with the QUERY COMPRESSION command. The QUERY PROCESS command can be used to monitor the progress of the audit operation.

ANR6213ICommand name: Process process ID, was cancelled - number of files promoted candidate files were promoted as candidates at level audit level, number of files eliminated files were eliminated as candidates, and number of files expired candidates were eliminated because they were found to be expired on the server.

Explanation: A compression audit operation was cancelled with the CANCEL PROCESS command before completion. The number of candidate files that were promoted as candidates at this level of audit, eliminated as candidates at this level of audit, and found to be expired before the cancellation are reported.

System Action: The audit operation ends.

User Response: The compression audit can be restarted with the AUDIT COMPRESSION command. The compression candidate list can be displayed with the QUERY COMPRESSION command.

ANR6214ICommand name: Process process ID, completed successfully - number of files promoted candidate files were promoted as candidates at level audit level, number of files eliminated files were eliminated as candidates, and number of files expired candidates were eliminated because they were found to be expired on the server.

Explanation: A compression audit operation completed successfully. The number of candidate files that were promoted as candidates at this level of audit, eliminated as candidates at this level of audit, and found to be expired are reported.

System Action: The audit operation ends.

User Response: The compression candidate list can be displayed with the QUERY COMPRESSION command.

ANR6215ICommand name: Backup for file high-level object name low-level object name in filespace client filespace name for node client node name could not be forced.

Explanation: It is not possible to force a backup for the specified file using the FORCE BACKUP command. This file was either backed up using an API client or by an ADSM version 2 client or higher.

System Action: The force backup operation continues, the state of the compression record for this file is updated.

User Response: If the file was backed up using a Version 2 client, or higher, you may remove this entry as a candidate, using the REMOVE COMPRESSION command. If the file was backed up using an API client, notify the client owner to again back this file up. Do not remove this entry until it becomes an "inactive" entry.

ANR6220IDelete compression operation started as process process ID.

Explanation: A compression deletion operation was started as a background server process with the indicated identifier.

System Action: Server operation continues.

User Response: None.

ANR6221IForce backup operation started as process process ID.

Explanation: A force backup operation was started as a background server process with the indicated identifier.

System Action: Server operation continues.

User Response: None.

ANR6222ICommand name: Process process ID was cancelled - number of files files were processed prior to cancellation.

Explanation: The indicated process was cancelled prior to completion. This message displays the indicated number of files that were processed before the operation was cancelled.

System Action: The process ends.

User Response: The operation may be restarted by reissuing the indicated command.

ANR6223IDelete compression process process ID has completed - number of files files were deleted.

Explanation: The indicated process has completed processing. All database references have been deleted for the indicated number of files.

System Action: The process ends.

User Response: None.

ANR6224IForce backup process process ID has completed - number of files files were marked for forced backup.

Explanation: The indicated process has completed processing. The indicated number of files have been marked for forced backup. These files will be backed up during the next incremental backup.

System Action: The process ends.

User Response: None.

ANR6225IFile identifier removed as a suspect for compression errors.

Explanation: The file with the specified identifier has been removed from the database information concerning files with possible compression errors. Other database information concerning the file is not affected.

System Action: Server operation continues.

User Response: None.

ANR6226ICommand name: Started as background process process ID.

Explanation: A compression cleanup operation has been started to remove compression candidate information and temporary database entries from the server database. Client files are not affected by this operation.

System Action: Server operation continues.

User Response: The CANCEL PROCESS command can be used to cancel the compression cleanup operation. The QUERY PROCESS command may be used to query the status of the operation.

ANR6227Icleanup process name operation starting as process process ID.

Explanation: A compression cleanup operation has been started to remove compression candidate information and temporary database entries from the server database. Client files are not affected by this operation.

System Action: Server operation continues.

User Response: The CANCEL PROCESS command can be used to cancel the compression cleanup operation. The QUERY PROCESS command may be used to query the status of the operation.

ANR6228WCleanup process name: Process process ID has been cancelled - cleanup processing is incomplete.

Explanation: A compression cleanup operation has been cancelled prior to successful completion.

System Action: Server operation continues.

User Response: The CLEANUP COMPRESSION command can be used to restart the cleanup operation.

ANR6229ICleanup process name: Process process ID completed successfully.

Explanation: A compression cleanup operation has successfully completed.

System Action: The cleanup process ends.

User Response: None.

ANR6300ECommand name: Insufficient server memory available for the operation.

Explanation: A compression testing routine cannot continue because sufficient memory is not available on the server.

System Action: The operation fails.

User Response: Increase the memory available to the server by increasing the server region size, virtual machine size, paging space available on the system, or relocating the memory swap file, depending upon the platform on which the server is executing. Additional memory may also be made available by limiting server activity (sessions, migration, and other activities) while this operation is processing.

ANR6301ECommand name: Invalid LEVEL specified. This command only supports a value of 1 or 2 for the LEVEL parameter.

Explanation: An invalid LEVEL= parameter has been specified for the command.

System Action: The command fails.

User Response: Reissue the command specifying a value of 1 or 2 for the LEVEL parameter.

ANR6302ECommand name: Process process ID, failed - number of candidate files candidate files were found in number of files examined files examined prior to failure.

Explanation: A compression audit operation failed before completion. The number of candidate files that were found prior to the failure are displayed.

System Action: The audit operation ends.

User Response: Examine message that appear before this message on the server console or in the activity log to determine the source of the failure. If the error can be corrected, re-execute the compression audit. If the failure cannot be determined or corrected, contact your service representative. The compression candidate list can be displayed with the QUERY COMPRESSION command.

ANR6303ECommand name: Process process ID, failed - number of files promoted candidate files were promoted as candidates at level audit level, number of files eliminated files were eliminated as candidates, and number of files expired candidates were eliminated because they were found to be expired on the server.

Explanation: A compression audit operation failed before completion. The number of candidate files that were promoted as candidates at this level of audit, eliminated as candidates at this level of audit, and found to be expired before the audit failure are reported.

System Action: The audit operation ends.

User Response: Examine message that appear before this message on the server console or in the activity log to determine the source of the failure. If the error can be corrected, re-execute the compression audit. If the failure cannot be determined or corrected, contact your service representative. The compression candidate list can be displayed with the QUERY COMPRESSION command.

ANR6304ECommand name: Command cannot be processed until compression audit is performed.

Explanation: The indicated command cannot be processed until a compression audit is performed using the AUDIT COMPRESSION command.

System Action: The command fails.

User Response: Issue the AUDIT COMPRESSION command and then repeat the attempted operation.

ANR6305ECommand name: File identifier is not a suspect for compression errors.

Explanation: The file with the specified identifier is not listed in the database as a suspect for compression errors. The file cannot be removed from the suspect list.

System Action: Server operation continues.

User Response: Use the QUERY COMPRESSION command to obtain the correct identifier for the file to be removed.

ANR6306ECleanup process name: Process process ID failed due to server error - cleanup processing is incomplete.

Explanation: A compression cleanup operation has failed before successful completion.

System Action: The cleanup process ends.

User Response: Examine messages that appear on the server console or in the server activity log prior to this message to determine the cause of the error. If the error can be identified and corrected, restart the cleanup operation with the CLEANUP COMPRESSION command. If the error cannot be corrected, contact your service representative.

ANR6600ECommand: Invalid machine name - machine name.

Explanation: The machine name specified in the command is invalid.

System Action: The server does not process the command.

User Response: Issue the command again and specify a valid machine name.

ANR6601ECommand: Description information exceeds maximum length characters.

Explanation: The description specified in the command exceeds the maximum length of allowable characters.

System Action: The server does not process the command.

User Response: Issue the command again and specify a valid description.

ANR6602ECommand: Recovery instructions file name exceeds maximum length characters.

Explanation: The recovery instructions file name specified in the command exceeds the maximum length of allowable characters.

System Action: The server does not process the command.

User Response: Issue the command again and specify a valid recovery instructions file name.

ANR6603ECommand: Characteristics file name exceeds maximum length characters.

Explanation: The characteristics file name specified in the command exceeds the maximum length of allowable characters.

System Action: The server does not process the command.

User Response: Issue the command again and specify a valid characteristics file name.

ANR6604ECommand: Invalid building identifier - building.

Explanation: The building identifier specified in the command is invalid.

System Action: The server does not process the command.

User Response: Issue the command again and specify a valid building identifier.

ANR6605ECommand: Invalid floor identifier - floor.

Explanation: The floor identifier specified in the command is invalid.

System Action: The server does not process the command.

User Response: Issue the command again and specify a valid floor identifier.

ANR6606ECommand: Invalid room identifier - room.

Explanation: The room identifier specified in the command is invalid.

System Action: The server does not process the command.

User Response: Issue the command again and specify a valid room identifier.

ANR6607ECommand: Machine machine name is already defined.

Explanation: The machine specified in the command is already defined to the server.

System Action: The server does not process the command.

User Response: Issue the command again and specify another machine.

ANR6608ECommand: A machine containing a server is already defined.

Explanation: The ADSMSERVER=YES parameter specified in the command is invalid because another machine has already been defined with this parameter. Only one machine can be defined to the server as containing a server.

System Action: The server does not process the command.

User Response: Issue the command again and do not specify ADSMSERVER=YES as a parameter.

ANR6609IMachine machine name defined.

Explanation: A DEFINE MACHINE command has added the requested machine to the server.

System Action: None.

User Response: None.

ANR6610ECommand: Invalid recovery media name - recovery media name.

Explanation: The recovery media name specified in the command is invalid.

System Action: The server does not process the command.

User Response: Issue the command again and specify a valid recovery media name.

ANR6611ECommand: Location information exceeds maximum length characters.

Explanation: The location specified in the command exceeds the maximum length of allowable characters.

System Action: The server does not process the command.

User Response: Issue the command again and specify a valid location.

ANR6612IMachine machine name updated.

Explanation: An UPDATE MACHINE command has updated one or more attributes of a machine.

System Action: None.

User Response: None.

ANR6613IMachine machine name deleted.

Explanation: A DELETE MACHINE command has deleted the requested machine from the server.

System Action: None.

User Response: None.

ANR6614ECommand: Machine machine name is not defined.

Explanation: The machine specified in the command is not defined to the server.

System Action: The server does not process the command.

User Response: Issue the command again and specify a valid machine.

ANR6615ECommand: Failed to open input file - file name.

Explanation: The input file specified in the command cannot be opened by the server.

System Action: The server does not process the command.

User Response: Issue the command again and specify an input file that is in a file system accessible by the server.

ANR6616ECommand: Invalid sequence number - sequence number.

Explanation: The sequence number specified in the command is invalid.

System Action: The server does not process the command.

User Response: Issue the command again and specify a valid sequence number.

ANR6617WCommand: Node node name cannot be processed because it is not registered.

Explanation: The node indicated in the message cannot be processed because it is not registered.

System Action: The indicated node is not processed, but another node can be processed if specified by this command.

User Response: Issue the command again and specify a valid registered node.

ANR6618ECommand: No matching node registered.

Explanation: The node specified in the command does not match any node registered to the server.

System Action: The server does not process the command.

User Response: Issue the command again and specify a valid node.

ANR6619INode node name associated with machine machine name.

Explanation: A DEFINE MACHNODEASSOCIATION command has associated the specified node with the specified machine. The node node name is associated with the machine machine name.

System Action: None.

User Response: None.

ANR6620ECommand: Machine and node association is already defined.

Explanation: The machine and node association specified in the command is already defined to the server.

System Action: The server operation continues, but the command has no effect.

User Response: Issue the command again and specify a valid node.

ANR6621INode node name disassociated from machine machine name.

Explanation: A DELETE MACHNODEASSOCIATION command has deleted the requested association from the server. The node node name is not associated with the machine machine name.

System Action: None.

User Response: None.

ANR6622ECommand: Recovery media recovery media name is not defined.

Explanation: The recovery media specified in the command is not defined to the server.

System Action: The server does not process the command.

User Response: Issue the command again and specify a valid recovery media.

ANR6623WCommand: Machine machine name cannot be processed because it is not defined.

Explanation: The machine indicated in the message is not defined to the server.

System Action: The indicated machine is not processed, but another machine can be processed if specified by this command.

User Response: Issue the command again and specify a valid machine.

ANR6624ECommand: No matching machine defined.

Explanation: The machine specified in the command does not match any machine defined to the server.

System Action: The server does not process the command.

User Response: Issue the command again and specify a valid machine.

ANR6625IMachine machine name associated with recovery media recovery media name.

Explanation: A DEFINE RECOVERYMEDIAMACHASSOCIATION command has associated the specified machine with the specified recovery media. The machine machine name is associated with the recovery media recovery media name.

System Action: None.

User Response: None.

ANR6626ECommand: Recovery media/machine association is already defined.

Explanation: The recovery media/machine association specified in the command is already defined to the server.

System Action: The server operation continues, but the command has no effect.

User Response: Issue the command again and specify a valid machine.

ANR6627IMachine machine name disassociated from recovery media recovery media name.

Explanation: A DELETE RECOVERYMEDIAMACHASSOCIATION command has deleted the requested association from the server. Machine machine name is not associated with the recovery media recovery media name.

System Action: None.

User Response: None.

ANR6628ECommand: Volume list exceeds maximum length characters.

Explanation: The volume list specified in the command exceeds the maximum length of allowable characters.

System Action: The server does not process the command.

User Response: Issue the command again and specify a valid volume list.

ANR6629ECommand: Product name exceeds maximum length characters.

Explanation: The product name specified in the command exceeds the maximum length of allowable characters.

System Action: The server does not process the command.

User Response: Issue the command again and specify a valid product name.

ANR6630ECommand: Product information exceeds maximum length characters.

Explanation: The product information specified in the command exceeds the maximum length of allowable characters.

System Action: The server does not process the command.

User Response: Issue the command again and specify valid product information.

ANR6631ECommand: Missing volume list for boot recovery media.

Explanation: Boot recovery media cannot be defined to the server without specifying a volume list.

System Action: The server does not process the command.

User Response: Issue the command again and specify the volume list for the boot recovery media.

ANR6632IRecovery media recovery media name defined.

Explanation: A DEFINE RECOVERYMEDIA command has defined the recovery media to the server.

System Action: None.

User Response: None.

ANR6633IRecovery media recovery media name updated.

Explanation: An UPDATE RECOVERYMEDIA command has updated one or more attributes of the recovery media.

System Action: None.

User Response: None.

ANR6634IRecovery media recovery media name deleted.

Explanation: A DELETE RECOVERYMEDIA command has deleted the requested recovery media from the server.

System Action: None.

User Response: None.

ANR6635ECommand: Recovery media recovery media name is already defined.

Explanation: The recovery media specified in the command is already defined to the server.

System Action: The server does not process the command.

User Response: Issue the command again and specify a different recovery media.

ANR6636ECommand: The characteristics specified for machine machine name exceeds maximum length characters.

Explanation: The characteristics specified in the command exceeds the maximum length of allowable characters.

System Action: The server does not process the command.

User Response: Issue the command again and specify valid characteristics.

ANR6637ECommand: The recovery instructions specified for machine machine name exceeds maximum length characters.

Explanation: The recovery instructions specified in the command exceeds the maximum length of allowable characters.

System Action: The server does not process the command.

User Response: Issue the command again and specify valid recovery instructions.

ANR6638ECommand: The characteristics for machine machine name are already defined.

Explanation: The characteristics for the machine specified in the command are already defined to the server.

System Action: The server does not process the command.

User Response: If the specified machine is defined to the server, issue an UPDATE MACHINE command to update the existing characteristics. If the machine is not defined to the server, run AUDIT DRM FIX to delete the characteristics.

ANR6639ECommand: The recovery instructions for machine machine name are already defined.

Explanation: The recovery instructions for the machine specified in the command are already defined to the server.

System Action: The server does not process the command.

User Response: If the specified machine is defined to the server, issue an UPDATE MACHINE command to update the existing recovery instructions. If the machine is not defined to the server, run AUDIT DRM FIX to delete the recovery instructions.

ANR6640ECommand: Cannot delete volume list for boot recovery media.

Explanation: A volume list cannot be deleted for boot recovery media. A volume list must exist for each boot recovery media defined to the server.

System Action: The server does not process the command.

User Response: To delete the volume list, issue an UPDATE RECOVERYMEDIA command and specify a recovery media type of OTHER and VOLUMES="". To change the recovery media type to BOOT, issue an UPDATE RECOVERYMEDIA command and specify the volume list containing the boot recovery media and TYPE=BOOT.

ANR6641ECommand: No association found for machine and node pair specified.

Explanation: No association found for the machine and node pair specified in the command.

System Action: Server operation continues, but the command has no effect.

User Response: Issue the command again and specify a valid machine and node pair.

ANR6642ECommand: No association found for recovery media and machine pair specified.

Explanation: No association found for the recovery media and machine pair specified in the command.

System Action: Server operation continues, but the command has no effect.

User Response: Issue the command again and specify a valid recovery media and machine pair.

ANR6643ECommand: Invalid parameter value - parameter value.

Explanation: The parameter issued in the command is invalid.

System Action: The server does not process the command.

User Response: Issue the command again and specify a valid parameter.

ANR6644ECommand: A character string must be specified.

Explanation: The INSERT command is invalid. A character string must be specified.

System Action: The server does not process the command.

User Response: Issue the command again and specify a valid character string.

ANR6645WNode node name has already been associated with machine machine name.

Explanation: The node specified in the DEFINE MACHNODEASSOCIATION command is invalid. The node is already associated with another machine shown in the message. A node can only be associated with one machine.

System Action: The indicated node is not processed, but another node can be processed if specified by the command.

User Response: Issue the command again and specify a valid node name.

ANR6646IAudit command: Auditing disaster recovery manager definitions.

Explanation: This message is displayed during a database audit and indicates that the disaster recovery manager definitions are being examined by the database audit process.

System Action: Audit processing continues.

User Response: None.

ANR6647EAudit command: DRM global attributes are missing.

Explanation: A database audit process finds that the global attributes used for server DRM activities are missing.

System Action: Audit processing continues.

User Response: Issue the command again and specify FIX=YES to recreate the DRM global attributes.

ANR6648IAudit command: DRM global attributes are missing - default values will be used to recreate the attributes.

Explanation: A database audit process finds that the global attributes used for server DRM activities are missing. Because FIX=YES has been specified on the AUDIT command, default attribute values will be used to recreate the administrative global attributes.

System Action: Audit processing continues.

User Response: None.

ANR6649EAudit command: DRM machine ID assignments are incorrect.

Explanation: A database audit process finds that the global attributes machine ID used for server DRM activities are incorrect.

System Action: Audit processing continues.

User Response: Reissue the audit command with FIX=YES specified so that the DRM global attributes can be corrected.

ANR6650IAudit command: DRM machine ID Assignments are incorrect - values will be corrected.

Explanation: A database audit process finds that the global attributes machine ID used for server DRM activities are incorrect. Since FIX=YES has been specified on the AUDIT command, the attribute value will be corrected in the server database.

System Action: Audit processing continues.

User Response: None

ANR6651IAudit command: Invalid priority value encountered for machine machine name.

Explanation: A database audit process encounters an invalid priority value for the machine indicated.

System Action: Audit processing continues.

User Response: Issue the command again and specify FIX=YES to correct the priority. Or, issue an UPDATE MACHINE command and specify a new priority value.

ANR6652IAudit command: Invalid priority value encountered for machine machine name - the default value will be set.

Explanation: A database audit process encounters an invalid machine priority value for the machine indicated. Because FIX=YES has been specified, the audit function sets the machine priority value to the default value.

System Action: Audit processing continues.

User Response: To override the default value, issue an UPDATE MACHINE command to change the value after the audit command has completed.

ANR6653IAudit command: Invalid building value encountered for machine machine name.

Explanation: A database audit process encounters an invalid building value for the machine indicated.

System Action: Audit processing continues.

User Response: Issue the command again and specify FIX=YES to correct the building value. Or, issue an UPDATE MACHINE command and specify a new building value.

ANR6654IAudit command: Invalid building value encountered for machine machine name - the building value will be removed.

Explanation: A database audit process encounters an invalid building value for the machine indicated. Because FIX=YES has been specified, the audit function removes the machine building value.

System Action: Audit processing continues.

User Response: To set the building value to another value, issue an UPDATE MACHINE command after the audit command has completed.

ANR6655IAudit command: Invalid floor value encountered for machine machine name.

Explanation: A database audit process encounters an invalid floor value for the machine indicated.

System Action: Audit processing continues.

User Response: Issue the command again and specify FIX=YES to correct the floor value. Or, issue an UPDATE MACHINE command and specify a new floor value.

ANR6656IAudit command: Invalid floor value encountered for machine machine name - the floor value will be removed.

Explanation: A database audit process encounters an invalid floor value for the machine indicated. Because FIX=YES has been specified, the audit function removes the machine floor value.

System Action: Audit processing continues.

User Response: To set the floor value to another value, issue an UPDATE MACHINE command after the audit command has completed.

ANR6657IAudit command: Invalid room value encountered for machine machine name.

Explanation: A database audit process encounters an invalid room value for the machine indicated.

System Action: Audit processing continues.

User Response: Issue the command again and specify FIX=YES to correct the room value. Or, issue an UPDATE MACHINE command and specify a new room value.

ANR6658IAudit command: Invalid room value encountered for machine machine name - the room value will be removed.

Explanation: A database audit process encounters an invalid room value for the machine indicated. Because FIX=YES has been specified, the audit function removes the machine room value.

System Action: Audit processing continues.

User Response: To set the room value for the specified machine to another value, use the UPDATE MACHINE command after the audit command has completed.

ANR6659IAudit command: Invalid server value encountered for machine machine name.

Explanation: A database audit process encounters an invalid server value for the machine indicated.

System Action: Audit processing continues.

User Response: Issue the command again and specify FIX=YES to correct the server value. Or, issue an UPDATE MACHINE command and specify a new server value.

ANR6660IAudit command: Invalid server value encountered for machine machine name - the default value will be set.

Explanation: A database audit process encounters an invalid server value for the machine indicated. Because FIX=YES has been specified, the audit function sets the machine server value to the default value.

System Action: Audit processing continues.

User Response: To override the default value, issue an UPDATE MACHINE command to change the value after the audit command has completed.

ANR6661IAudit command: Multiple machines are indicated as servers. Only one machine should have the server indicator set to YES.

Explanation: A database audit process encounters more than one machine with the server indicator set to YES.

System Action: Audit processing continues.

User Response: For a list of machines with the server indicator set to YES, issue a QUERY MACHINE ADSMSERVER=YES command. Issue an UPDATE MACHINE command for each machine that is not a server.

ANR6662IAudit command: Characteristics for machine machine name not found.

Explanation: A database audit process finds a characteristics reference from a machine for characteristics that are not in the server database.

System Action: Audit processing continues.

User Response: Issue an UPDATE MACHINE command to load the characteristics into the database after the audit command has completed.

ANR6663IAudit command: Recovery instructions for machine machine name not found.

Explanation: A database audit process finds a recovery instructions reference from a machine for recovery instructions that are not in the server database.

System Action: Audit processing continues.

User Response: Issue an UPDATE MACHINE command to load the recovery instructions into the database after the audit command has completed.

ANR6664IAudit command: Invalid access value encountered for recovery media recovery media name.

Explanation: A database audit process encounters an invalid access value for the recovery media indicated.

System Action: Audit processing continues.

User Response: Issue the command again and specify FIX=YES to correct the access value. Or, issue an UPDATE RECOVERYMEDIA command and specify a new access value.

ANR6665IAudit command: Invalid access value encountered for recovery media recovery media name - the default value will be set.

Explanation: A database audit process encounters an invalid access value for the recovery media indicated. Because FIX=YES has been specified, the audit function sets the recovery media access value to the default value.

System Action: Audit processing continues.

User Response: To override the default value, issue an UPDATE RECOVERYMEDIA command to change the value after the audit command has completed.

ANR6666IAudit command: Invalid type value encountered for recovery media recovery media name.

Explanation: A database audit process encounters an invalid type value for the recovery media indicated.

System Action: Audit processing continues.

User Response: Issue the command again and specify FIX=YES to correct the type value. Or, issue an UPDATE RECOVERYMEDIA command and specify a new type value.

ANR6667IAudit command: Invalid type value encountered for recovery media recovery media name - the default value will be set.

Explanation: A database audit process encounters an invalid type value for the recovery media indicated. Because FIX=YES has been specified, the audit function sets the recovery media type value to the default value.

System Action: Audit processing continues.

User Response: To override the default value, issue an UPDATE RECOVERYMEDIA command to change the value after the audit command has completed.

ANR6668EAudit command: Machine is not found for internal machine ID machine ID, which is referenced by recovery media.

Explanation: A database audit process finds recovery media that references a machine that is not defined in the server database.

System Action: Audit processing continues.

User Response: Issue the command again and specify FIX=YES to correct recovery media attributes.

ANR6669IAudit command: Machine is not found for internal machine ID machine ID, which is referenced by recovery media - the machine reference will be deleted.

Explanation: A database audit process finds recovery media that references a machine that is not defined in the server database. Because FIX=YES has been specified for the audit command, the reference will be removed from the server database.

System Action: Audit processing continues.

User Response: None.

ANR6670EAudit command: Recovery media not found for internal recovery media ID recovery media ID, which is referenced by a machine.

Explanation: A database audit process finds a machine that references recovery media that is not defined in the server database.

System Action: Audit processing continues.

User Response: Issue the command again and specify FIX=YES to correct the recovery media attributes.

ANR6671IAudit command: Recovery media not found for internal recovery media ID recovery media ID, which is referenced by a machine - the recovery media reference will be deleted.

Explanation: A database audit process finds m machine that references recovery media that is not defined in the server database. Because FIX=YES has been specified for the audit command, the reference will be deleted from the server database.

System Action: Audit processing continues.

User Response: None.

ANR6672EAudit command: Client node not found for internal node ID node ID, which is referenced by a machine.

Explanation: A database audit process finds a machine that references a client node that is not defined in the server database.

System Action: Audit processing continues.

User Response: Issue the command again and specify FIX=YES to correct the machine attributes.

ANR6673IAudit command: Client node not found for internal node ID node ID, which is referenced by a machine - the client node reference will be deleted.

Explanation: A database audit process finds a machine that references a client node that is not defined in the server database. Because FIX=YES has been specified for the audit command, the reference will be removed from the server database.

System Action: Audit processing continues.

User Response: None.

ANR6674EAudit command: Machine not found for internal machine ID machine ID, which is referenced by a client node.

Explanation: A database audit process finds a client node that references a machine that is not defined in the server database.

System Action: Audit processing continues.

User Response: Issue the command again and specify FIX=YES to correct the machine attributes.

ANR6675IAudit command: Machine not found for internal machine ID machine ID, which is referenced by a client node - the machine reference will be deleted.

Explanation: A database audit process finds a client node that references a machine that is not defined in the server database. Because FIX=YES has been specified for the audit command, the reference will be removed from the server database.

System Action: Audit processing continues.

User Response: None.

ANR6676EAudit command: Machine not found for internal machine ID machine ID, which is referenced by characteristics.

Explanation: A database audit process finds characteristics that reference a machine that is not defined in the server database.

System Action: Audit processing continues.

User Response: Issue the command again and specify FIX=YES to correct the machine attributes.

ANR6677IAudit command: Machine not found for internal machine ID machine ID, which is referenced by characteristics - the machine reference will be deleted.

Explanation: A database audit process finds characteristics that reference a machine that is not defined in the server database. Because FIX=YES has been specified for the audit command, the reference will be removed from the server database.

System Action: Audit processing continues.

User Response: None.

ANR6678EAudit command: Machine not found for internal machine ID machine ID, which is referenced by recovery instructions.

Explanation: A database audit process finds recovery instructions that reference a machine that is not defined in the server database.

System Action: Audit processing continues.

User Response: Issue the command again and specify FIX=YES to correct the machine attributes.

ANR6679IAudit command: Machine not found for internal machine ID machine ID, which is referenced by recovery instructions - the machine reference will be deleted.

Explanation: A database audit process finds recovery instructions that reference a machine that is not defined in the server database. Because FIX=YES has been specified for the audit command, the reference will be removed from the server database.

System Action: Audit processing continues.

User Response: None.

ANR6680EAudit command: Missing or invalid internal database attribute encountered for machine machine name.

Explanation: A database audit process finds an invalid attribute for the specified machine.

System Action: Audit processing continues.

User Response: Issue the command again and specify FIX=YES to correct the machine attributes.

ANR6681IAudit command: Missing or invalid internal database attribute encountered for machine machine name - the attribute will be corrected.

Explanation: A database audit process finds an invalid attribute for the specified machine. Because FIX=YES has been specified for the audit command the invalid attribute will be corrected.

System Action: Audit processing continues.

User Response: None.

ANR6682ICommand command ended: number of volumes volumes processed.

Explanation: The indicated command ended. The total number of volumes successfully processed is shown in the message.

System Action: The indicated command ends.

User Response: None.

ANR6683ICommand: Volume volume name was moved from from state state to to state.

Explanation: Volume volume name is successfully moved from state1 to state2 by the indicated command.

System Action: The indicated volume is moved to the destination state.

User Response: None.

ANR6684ICommand: Volume volume name was deleted.

Explanation: The MOVE DRMEDIA * WHERESTATE=COURIERRETRIEVE command displays the message. Volume volume name is deleted from the server database. For database backup volume, after its expiration days have elapsed, the volume history record is deleted when it is returned onsite. For an empty scratch copy storage pool volume, the volume record is deleted when it is returned onsite.

System Action: The volume record is deleted from the server database.

User Response: Issue the CHECKIN LIBVOLUME command for each volume returned onsite if the volume is reused by the server.

ANR6685ECommand: Volume volume name not defined.

Explanation: Volume volume name is not defined to the server.

System Action: The indicated command is not processed if the volume name is explicitly specified on the command. If a volume pattern is specified on the command, the volume shown is not processed, but the other volumes are processed.

User Response: Reissue the command specifying a valid volume name.

ANR6686ECommand: Volume volume name in use.

Explanation: The MOVE DRMEDIA * WHERESTATE=MOUNTABLE command displays the message. Volume volume name is used for another operation.

System Action: The command is not processed if the volume is explicitly specified on the command. If a volume pattern is specified on the command, the indicated volume is not processed, but the other volumes are processed.

User Response: Wait until the conflicting volume activity has completed, and then reissue the command. If the volume is currently mounted, but idle, dismount the volume by using a DISMOUNT VOLUME command and then retry this operation.

ANR6687ECommand: Executable command string exceeds maximum length characters.

Explanation: The length of the executable command string specified with the CMD parameter exceeds the maximum length of allowable characters (255).

System Action: The server stops processing the command.

User Response: Issue the command again and specify a valid executable command with the CMD parameter.

ANR6690ECommand: Copy storage pool cstgp name not defined for Offsite Recovery Media.

Explanation: The MOVE DRMEDIA or QUERY DRMEDIA command displays the message. The indicated command was issued with a copy storage pool name specified, but the specified pool name is not defined to DRM for Offsite Recovery Media.

System Action: The indicated command is not processed.

User Response: Reissue the command, after defining the specified copy storage pool to DRM for Offsite Recovery Media.

ANR6691ECommand: No match is found for this move.

Explanation: The indicated command was issued, but no matching volumes are defined to the server or the volume specified is not managed by the command.

System Action: The command is not processed.

User Response: Reissue the command specifying the valid volume.

ANR6694ECommand: The ORM state state is invalid for a volume with access mode access mode.

Explanation: The indicated command specifies an Offsite Recovery Media state that is invalid for a volume with the access mode shown. Specify COURIER or COURIERRETRIEVE for a volume that has access mode of OFFSITE.

System Action: The server does not process the command.

User Response: Reissue the command specifying COURIER or COURIERRETRIEVE as the state for a volume that has access mode of OFFSITE.

ANR6695ECommand: Device class device class name not defined for volume volume name.

Explanation: The MOVE DRMEDIA or QUERY DRMEDIA command displays the message. The volume being processed has associated with the device class name shown that is not defined to the server.

System Action: The command is not processed if the volume is explicitly specified on the command. If a volume pattern is specified on the command, the indicated volume is not processed, but the other volumes not associated with the indicated class are processed.

User Response: Reissue the command after the indicated device class is defined to the server.

ANR6696Icommand: operation for volume volume name in library library name starting.

Explanation: The indicated operation is being started for the volume shown in the given library.

System Action: The server starts the operation in response to the indicated command entered by an administrator.

User Response: For SCSI library users, remove the volume from the slot and issue a REPLY command, along with the request ID, to tell the server the volume was removed from the library.

ANR6697Icommand: operation for volume volume name in library library name completed successfully.

Explanation: The indicated operation has completed successfully for the volume shown in the given library.

System Action: The volume is either deleted from the library inventory (if its status is something other than DATA) or marked not present (if its status is DATA).

User Response: None.

ANR6698Ecommand: operation for volume volume name in library library name failed.

Explanation: The indicated operation has failed for the volume shown in the given library. This message should be preceded by another error message which provides more detail about the error.

System Action: The volume is not processed.

User Response: Check for additional message and eliminate the condition that caused the failure, then retry the command.

ANR6699ICancel in progress.

Explanation: The MOVE DRMEDIA command has been canceled and will end when resources have been freed for the background process. This message may be displayed in response to a QUERY PROCESS command for a MOVE DRMEDIA command.

System Action: Server operation continues.

User Response: None.

ANR6700ICommand command completed successfully.

Explanation: The indicated command completed successfully.

System Action: None.

User Response: None.

ANR6701ECommand: Invalid courier name - courier name.

Explanation: The indicated command has been entered with an invalid courier name.

System Action: The server does not process the command.

User Response: Reissue the command with a valid courier name.

ANR6702ECommand: Invalid expiration days value - days value.

Explanation: The indicated command has been entered that specifies an invalid expiration days value.

System Action: The server does not process the command.

User Response: Reissue the command with a valid expiration days value.

ANR6703ECommand: Invalid recovery plan prefix - prefix.

Explanation: The indicated command has been entered with an invalid recovery plan prefix.

System Action: The server does not process the command.

User Response: Reissue the command with a valid recovery plan prefix.

ANR6704ECommand: Invalid plan instructions prefix - prefix.

Explanation: The indicated command has been entered with an invalid plan instructions prefix.

System Action: The server does not process the command.

User Response: Reissue the command with a valid plan instructions prefix.

ANR6705ECommand: Invalid character for volume postfix - postfix character.

Explanation: The indicated command has been entered with an invalid character that is to be added to the volumes names in the recovery plan file.

System Action: The server does not process the command.

User Response: Reissue the command with a valid character.

ANR6706ECommand: Invalid vault name - vault name.

Explanation: The indicated command has been entered with an invalid vault name.

System Action: The server does not process the command.

User Response: Reissue the command with a valid vault name.

ANR6711EAudit command: An invalid database backup series expiration days encountered.

Explanation: A database audit process encounters an invalid value for database backup series expiration days.

System Action: Audit processing continues.

User Response: Issue the command again and specify FIX=YES to correct the expiration days. Or, issue an SET DRMDBBACKUPEXPIREDAYS command and specify a new expiration days value.

ANR6712IAudit command: An invalid database backup series expiration days encountered - the default value will be set.

Explanation: A database audit process encounters an invalid value for database backup series expiration days. Because FIX=YES has been specified, the audit function sets the expiration days value to the default value.

System Action: Audit processing continues.

User Response: To override the default value, issue a SET DRMDBBACKUPEXPIREDAYS command to change the value after the audit command has completed.

ANR6713EAudit command: An invalid check label value encountered.

Explanation: A database audit process encounters an invalid check label value.

System Action: Audit processing continues.

User Response: Issue the command again and specify FIX=YES to correct the check label value. Or, issue a SET DRMCHECKLABEL command and specify a new check label value.

ANR6714IAudit command: An invalid check label value encountered - the default value will be set.

Explanation: A database audit process encounters an invalid check label value. Because FIX=YES has been specified, the audit function sets the check label value to the default value.

System Action: Audit processing continues.

User Response: To override the default value, issue a SET DRMCHECKLABEL command to change the value after the audit command has completed.

ANR6715EAudit command: An invalid file process value encountered.

Explanation: A database audit process encounters an invalid file process value.

System Action: Audit processing continues.

User Response: Issue the command again and specify FIX=YES to correct the file process value. Or, issue a SET DRMFILEPROCESS command and specify a new file process value.

ANR6716IAudit command: An invalid file process value encountered - the default value will be set.

Explanation: A database audit process encounters an invalid file process value. Because FIX=YES has been specified, the audit function sets the file process value to the default value.

System Action: Audit processing continues.

User Response: To override the default value, issue a SET DRMFILEPROCESS command to change the value after the audit command has completed.

ANR6717EAudit command: Extraneous DRM global attribute encountered.

Explanation: A database audit process finds a nonexistent DRM global attribute.

System Action: Audit processing continues.

User Response: Issue the command again and specify FIX=YES to delete the extraneous attribute.

ANR6718IAudit command: Extraneous DRM global attribute encountered - the attribute will be deleted.

Explanation: A database audit process finds a nonexistent DRM global attribute. Since FIX=YES has been specified, the extraneous attribute will be deleted.

System Action: Audit processing continues.

User Response: None.

ANR6719EAudit command: DRM machine ID assignments not found.

Explanation: A database audit process finds no entries in server database for DRM internal machine ID assignments.

System Action: Audit processing continues.

User Response: Issue the command again and specify FIX=YES to correct the error.

ANR6720IAudit command: DRM machine ID assignments not found - entry will be created.

Explanation: A database audit process finds no entries in server database for DRM internal machine ID assignments. Because FIX=YES has been specified for the audit command, the audit function creates an entry in the server database for the machine ID assignments.

System Action: Audit processing continues.

User Response: None.

ANR6721EAudit command: DRM recovery media ID assignments not found.

Explanation: A database audit process finds no entries in server database for DRM internal recovery media ID assignments.

System Action: Audit processing continues.

User Response: Issue the command again and specify FIX=YES to correct the error.

ANR6722IAudit command: DRM recovery media ID assignments not found - entry will be created.

Explanation: A database audit process finds no entries in server database for DRM internal recovery media ID assignments. Because FIX=YES has been specified for the audit command, the audit function creates an entry in the server database for the recovery media ID assignments.

System Action: Audit processing continues.

User Response: None.

ANR6723EAudit command: Prefix for DRM recovery plan not found.

Explanation: A database audit process finds no entries in server database for DRM recovery plan prefix definitions.

System Action: Audit processing continues.

User Response: Issue the audit command again and specify FIX=YES to correct the error.

ANR6724IAudit command: Prefix for DRM recovery plan not found - entry will be created.

Explanation: A database audit process finds no entries in server database for DRM recovery plan prefix definitions. Because FIX=YES has been specified for the audit command, the audit function creates an entry using the default value in the server database for the recovery plan file prefix.

System Action: Audit processing continues.

User Response: To override the default value, issue a SET DRMPLANFILEPREFIX command to change the value after the audit command has completed.

ANR6725EAudit command: Prefix for DRM recovery plan instructions not found.

Explanation: A database audit process finds no entries in server database for DRM recovery plan instructions prefix definitions.

System Action: Audit processing continues.

User Response: Issue the audit command again and specify FIX=YES to correct the error.

ANR6726IAudit command: Prefix for DRM recovery plan instructions not found - entry will be created.

Explanation: A database audit process finds no entries in server database for DRM recovery plan instructions prefix definitions. Because FIX=YES has been specified for the audit command, the audit function creates an entry using the default value in the server database for the recovery plan instructions file prefix.

System Action: Audit processing continues.

User Response: To override the default value, issue a SET DRMPLANINSTRPREFIX command to change the value after the audit command has completed.

ANR6727EAudit command: Postfix for DRM replacement volumes names not found.

Explanation: A database audit process finds no entries in server database for DRM postfix definitions for replacement volumes names.

System Action: Audit processing continues.

User Response: Issue the audit command again and specify FIX=YES to correct the error.

ANR6728IAudit command: Postfix for DRM replacement volumes names not found - entry will be created.

Explanation: A database audit process finds no entries in server database for DRM postfix definitions for replacement volumes names. Because FIX=YES has been specified for the audit command, the audit function creates an entry using the default value in the server database for the replacement volumes postfix.

System Action: Audit processing continues.

User Response: To override the default value, issue a SET DRMPLANVPOSTFIX command to change the value after the audit command has completed.

ANR6729EAudit command: Primary storage pools to be restored by DRM not found.

Explanation: A database audit process finds no entries in server database for primary storage pools to be restored by DRM.

System Action: Audit processing continues.

User Response: Issue the audit command again and specify FIX=YES to correct the error.

ANR6730IAudit command: Primary storage pools to be restored by DRM not found - entry will be created.

Explanation: A database audit process finds no entries in server database for primary storage pools to be restored by DRM. Because FIX=YES has been specified for the audit command, the audit function creates an entry using the default value in the server database for the primary storage pools to be restored by DRM.

System Action: Audit processing continues.

User Response: To override the default value, issue a SET DRMPRIMSTGPOOL command to change the value after the audit command has completed.

ANR6731EAudit command: Copy storage pools to be managed by DRM not found.

Explanation: A database audit process finds no entries in server database for copy storage pools to be managed by DRM.

System Action: Audit processing continues.

User Response: Issue the audit command again and specify FIX=YES to correct the error.

ANR6732IAudit command: Copy storage pools to be managed by DRM not found - entry will be created.

Explanation: A database audit process finds no entries in server database for copy storage pools to be managed by DRM. Because FIX=YES has been specified for the audit command, the audit function creates an entry using the default value in the server database for the copy storage pools to be managed by DRM.

System Action: Audit processing continues.

User Response: To override the default value, issue a SET DRMCOPYSTGPOOL command to change the value after the audit command has completed.

ANR6733ECommand: Cannot complete initialization for process name process.

Explanation: The indicated process fails during process initialization.

System Action: The indicated command is ended and server processing continues.

User Response: This usually indicates that sufficient server memory is not available on the server. Allocate additional storage to the server. For details, issue HELP MEMORY to display the information online or see "Appendix A. Allocating Additional Server Memory".

ANR6734ECommand: Volume volume name not processed: library library name not defined.

Explanation: The indicated volume is not processed since the designated library has not been defined or has been deleted.

System Action: The volume is not processed.

User Response: Reissue the command using a different library name, or define the library before retrying the command.

ANR6735EAudit command: Courier information for ORM not found.

Explanation: A database audit process finds no entries in server database for courier name definitions used by DRM Offsite Recovery Media (ORM).

System Action: Audit processing continues.

User Response: Issue the audit command again and specify FIX=YES to correct the error.

ANR6736IAudit command: Courier information for ORM not found - entry will be created.

Explanation: A database audit process finds no entries in server database for courier name definitions used by DRM Offsite Recovery Media (ORM). Because FIX=YES has been specified for the audit command, the audit function creates an entry using the default value in the server database for the courier name definitions.

System Action: Audit processing continues.

User Response: To override the default value, issue a SET DRMCOURIERNAME command to change the value after the audit command has completed.

ANR6737EAudit command: Vault name for ORM not found.

Explanation: A database audit process finds no entries in server database for vault name definitions used by DRM Offsite Recovery Media (ORM).

System Action: Audit processing continues.

User Response: Issue the audit command again and specify FIX=YES to correct the error.

ANR6738IAudit command: Vault name for ORM not found - entry will be created.

Explanation: A database audit process finds no entries in server database for vault name definitions used by DRM Offsite Recovery Media (ORM). Because FIX=YES has been specified for the audit command, the audit function creates an entry using the default value in the server database for the vault name definitions.

System Action: Audit processing continues.

User Response: To override the default value, issue a SET DRMVAULTNAME command to change the value after the audit command has completed.

ANR6739EAudit command: Database backup series expiration days for ORM not found.

Explanation: A database audit process finds no entries in server database for database backup series expiration days definitions used by DRM Offsite Recovery Media (ORM).

System Action: Audit processing continues.

User Response: Issue the audit command again and specify FIX=YES to correct the error.

ANR6740IAudit command: Database backup series expiration days for ORM not found - entry will be created.

Explanation: A database audit process finds no entries in server database for database backup series expiration days definitions used by DRM Offsite Recovery Media (ORM). Because FIX=YES has been specified for the audit command, the audit function creates an entry using the default value in the server database for the database backup series expiration days definitions.

System Action: Audit processing continues.

User Response: To override the default value, issue a SET DRMDBBACKUPEXPIREDAYS command to change the value after the audit command has completed.

ANR6741EAudit command: Check label indicator for ORM not found.

Explanation: A database audit process finds no entries in server database for check label definitions used by DRM Offsite Recovery Media (ORM).

System Action: Audit processing continues.

User Response: Issue the audit command again and specify FIX=YES to correct the error.

ANR6742IAudit command: Check label indicator for ORM not found - entry will be created.

Explanation: A database audit process finds no entries in server database for check label definitions used by DRM Offsite Recovery Media (ORM ). Because FIX=YES has been specified for the audit command, the audit function creates an entry using the default value in the server database for the check label definitions.

System Action: Audit processing continues.

User Response: To override the default value, issue a SET DRMCHECKLABEL command to change the value after the audit command has completed.

ANR6743EAudit command: File process indicator for ORM not found.

Explanation: A database audit process finds no entries in server database for file process definitions used by DRM Offsite Recovery Media (ORM).

System Action: Audit processing continues.

User Response: Issue the audit command again and specify FIX=YES to correct the error.

ANR6744IAudit command: File process indicator for ORM not found - entry will be created.

Explanation: A database audit process finds no entries in server database for file process definitions used by DRM Offsite Recovery Media (ORM). Because FIX=YES has been specified for the audit command, the audit function creates an entry using the default value in the server database for the file process definitions.

System Action: Audit processing continues.

User Response: To override the default value, issue a SET DRMFILEPROCESS command to change the value after the audit command has completed.

ANR6745EAudit command: DRM recovery media ID assignments are incorrect.

Explanation: A database audit process finds that the global attributes recovery media id used for server DRM activities are incorrect.

System Action: Audit processing continues.

User Response: Reissue the audit command with FIX=YES specified so that the DRM global attributes can be corrected.

ANR6746IAudit command: DRM recovery media ID assignments are incorrect - values will be corrected.

Explanation: A database audit process finds that the global attributes recovery media ID used for server DRM activities are incorrect. Since FIX=YES has been specified on the AUDIT command, the attribute value will be corrected in the server database.

System Action: Audit processing continues.

User Response: None.

ANR6747INumber of volumes processed: number

Explanation: The MOVE DRMEDIA command has processed the number of volumes displayed. This message may be displayed in response to a QUERY PROCESS command for a MOVE DRMEDIA command.

System Action: Server operation continues.

User Response: None.

ANR6748INumber of volumes processed: number. Checking out volume volume name from library library name.

Explanation: The MOVE DRMEDIA command displays the number of volumes already processed and the name of the volume currently being checked out from the indicated library. This message may be displayed in response to a QUERY PROCESS command for a MOVE DRMEDIA command.

System Action: Server operation continues.

User Response: None.

ANR6749ICommand: process process ID terminated before completion - process canceled.

Explanation: The indicated background process performing the command shown has been canceled.

System Action: If other processes are executing, these processes continue.

User Response: None.

ANR6750EDisaster recovery manager operation command being processed is denied - server is not in compliance with license terms.

Explanation: The server refuses a disaster recovery manager operation because the current server configuration is not in compliance with the license terms.

System Action: Server operation continues. Disaster recovery operations cannot be performed until the server is licensed for the Tivoli Disaster Recovery Manager product.

User Response: Issue a QUERY LICENSE command to determine which license terms are not in compliance.

ANR6751EDisaster recovery manager operation command being processed is denied - server is not licensed for disaster recovery manager support.

Explanation: The server refuses a disaster recovery manager operation because the server is not licensed to support the disaster recovery manager.

System Action: Server operation continues.

User Response: Obtain the license to support the disaster recovery manager from your service provider or reseller. Issue the REGISTER LICENSE command with this license to enable the disaster recovery manager support.

ANR6752WDisaster recovery manager operation Command being processed is in violation of server license terms - server is not licensed for disaster recovery manager support.

Explanation: The server warns about a disaster recovery manager operation because the server is not licensed to support disaster recovery manager.

System Action: Server operation continues.

User Response: Obtain the license to support disaster recovery manager from your service provider or reseller. Issue the REGISTER LICENSE command with this license to enable disaster recovery manager support.

ANR6753Ecommand being processed encountered an internal server error while checking license compliance.

Explanation: The server encountered an internal error in determining whether the server is in compliance with license terms.

System Action: Server operation continues.

User Response: Issue the QUERY LICENSE and QUERY STATUS commands to determine if the server is in compliance with license terms. Start an AUDIT LICENSES process to adjust server license information. When this process completes, start the session again. If the problem persists, contact your service representative.

ANR6754IMachine machine name characteristics deleted.

Explanation: A DELETE MACHINE command has deleted the requested characteristics from the server.

System Action: None.

User Response: None.

ANR6755IMachine machine name recovery instructions deleted.

Explanation: A DELETE MACHINE command has deleted the requested recovery instructions from the server.

System Action: None.

User Response: None.

ANR6756EMachine machine name characteristics not defined to the server.

Explanation: A DELETE MACHINE command cannot delete the requested characteristics from the server. The characteristics for the specified machine are not defined to the server.

System Action: The server operation continues, but the command has no effect.

User Response: Issue the command again and specify a machine that has characteristics defined to the server.

ANR6757EMachine machine name recovery instructions not defined to the server.

Explanation: A DELETE MACHINE command cannot delete the requested recovery instructions from the server. The recovery instructions for the specified machine are not defined to the server.

System Action: The server operation continues, but the command has no effect.

User Response: Issue the command again and specify a machine that has recovery instructions defined to the server.

ANR6758ECommand: Only one character string can be specified.

Explanation: The INSERT command is invalid. Either a characteristics string can be specified or a recovery instructions string can be specified on the command. Both types of strings cannot be specified on the command at the same time.

System Action: The server does not process the command.

User Response: Issue the command again and specify one valid character string.

ANR6759EDisaster recovery manager operation command being processed is denied - disaster recovery manager support is not available for server platform platform.

Explanation: The server refuses a disaster recovery manager operation because disaster recovery manager support is not available for the indicated server platform.

System Action: Server operation continues.

User Response: None.

ANR6760ECommand: Executable command line exceeds maximum length characters for volume volume name.

Explanation: While writing to a command file, one of the following conditions occurred:

System Action: The server stops processing the command.

User Response: Issue the command again and specify a valid executable command with the CMD parameter.

In the case where volumes are being ejected from the library, it is possible the server database does not reflect the true state of the volume. For MOVE DRMEDIA, rerun the command after determining the cause of the error. For MOVE MEDIA, an update volume command should be issued setting the access of the volume to read only.

If this message is issued by a MOVE or QUERY DRMEDIA command and the volume record has been deleted from the server database, you can not use the MOVE or QUERY DRMEDIA commands to create the command file entry for this volume. In this case, you must manually issue the proper command.

ANR6761ECommand: WHERESTATE parameter is required.

Explanation: The indicated command specifies a volume name containing a pattern matching character and the TOSTATE parameter. The WHERESTATE parameter is not specified. The specification is invalid. Pattern-matching for volume names is only allowed when the WHERESTATE parameter is specified.

System Action: The server does not process the command.

User Response: Reissue the command specifying a specific volume name or by specifying the WHERESTATE parameter along with the TOSTATE parameter.

ANR6762ECommand: The specified destination state tostate is invalid for volume volume name in current state state.

Explanation: The indicated command specifies a destination state that is invalid for the volume name shown in the indicated current state.

System Action: The server does not process the volume.

User Response: Issue the command again and specify a valid destination state for the volume name shown.

ANR6763ICommand: The specified command has been written to file 'file name'.

Explanation: The command string specified with the CMD parameter on the command shown is written to the indicated file for each volume successfully processed.

System Action: None.

User Response: Execute the commands written to the file.

ANR6764Ecommand: Command file name exceeds maximum characters characters.

Explanation: The file name specified for containing the executable commands generated by DRM exceeds the maximum valid length shown.

System Action: The server does not process the command.

User Response: Reissue the command specifying a valid file name.

ANR6765ECommand: Invalid not mountable location name - not mountable name.

Explanation: The indicated command has been entered with an invalid not mountable location name.

System Action: The server does not process the command.

User Response: Reissue the command with a valid not mountable location name.

ANR6766ECommand: No command string is specified for FORMAT=CMD.

Explanation: The indicated command has been entered with a FORMAT=CMD to write a command string to a file, but no command string is specified.

System Action: The server does not process the command.

User Response: Reissue the command specifying a command string to be written to a file.

ANR6767ECommand: Invalid command file name - command file name.

Explanation: The indicated command has been entered with an invalid command file name.

System Action: The server does not process the command.

User Response: Reissue the command with a valid command file name.

ANR6768Ecommand: Prefix exceeds maximum characters characters.

Explanation: The prefix specified for recovery plan files or for plan instructions files exceeds the maximum valid length. The maximum valid length is shown in the message.

System Action: The server does not process the command.

User Response: Reissue the command specifying a valid prefix.

ANR6769EAudit command: Not mountable name information for ORM not found.

Explanation: A database audit process finds no entries in server database for not mountable location name definitions used by DRM Offsite Recovery Media (ORM).

System Action: Audit processing continues.

User Response: Issue the audit command again and specify FIX=YES to correct the error.

ANR6770IAudit command: Not mountable name information for ORM not found - entry will be created.

Explanation: A database audit process finds no entries in server database for not mountable location name definitions used by DRM Offsite Recovery Media (ORM). Because FIX=YES has been specified for the audit command, the audit function creates an entry using the default value in the server database for the courier name definitions.

System Action: Audit processing continues.

User Response: To override the default value, issue a SET DRMNOTMOUNTABLENAME command to change the value after the audit command has completed.

ANR6771EAudit command: Command file name information for ORM not found.

Explanation: A database audit process finds no entries in server database for command file name definitions used by DRM Offsite Recovery Media (ORM).

System Action: Audit processing continues.

User Response: Issue the audit command again and specify FIX=YES to correct the error.

ANR6772IAudit command: Command file name information for ORM not found - entry will be created.

Explanation: A database audit process finds no entries in server database for command file name definitions used by DRM Offsite Recovery Media (ORM). Because FIX=YES has been specified for the audit command, the audit function creates an entry using the default value in the server database for the command file name definitions.

System Action: Audit processing continues.

User Response: To override the default value, issue a SET DRMCMDFILENAME command to change the value after the audit command has completed.

ANR6773ECommand: Unable to open file 'command file name' for output.

Explanation: An error occurred while opening the command file name shown. The file name shown in the message is specified with the indicated command, the SET command, or the default name generated by the indicated command.

System Action: The server does not process the indicated command.

User Response: Examine error messages that may have been displayed prior to this message and correct any problems, if possible. Make sure that the server has proper authority to write to the file indicated. In AIX, make sure that the file name specified in the command or in the SET command is a full path file name, not a directory path name. In MVS, make sure that the file name specified in the command or in the SET command is a valid MVS file name. Reissue the command after determining the cause of the error.

ANR6774ECommand: Invalid volume transition states - from 'specified WHERESTATE' state to 'specified TOSTATE' state.

Explanation: The TOSTATE specified is an invalid destination state for the WHERESTATE specified.

System Action: The server does not process the command.

User Response: Issue the command again and specify a valid destination state.

ANR6775ECommand: Error writing to file 'file name' for volume volume name.

Explanation: An error occurred while writing to the file name shown for the indicated volume.

System Action: The server stops processing the command.

User Response: Examine error messages that may have been displayed prior to this message and correct any problems, if possible. Make sure that the server has proper authority to write to the file indicated. Reissue the command after determining the cause of the error.

In the case where volumes are being ejected from the library, it is possible the server database does not reflect the true state of the volume. For MOVE DRMEDIA, rerun the command after determining the cause of the error. For MOVE MEDIA, an update volume command should be issued setting the access of the volume to read only.

If this message is issued by a MOVE or QUERY DRMEDIA command and the volume record has been deleted from the server database, you can not use the MOVE or QUERY DRMEDIA commands to create the command file entry for this volume. In this case, you must manually issue the proper command.

ANR6776ECommand: Could not delete file: file name

Explanation: The indicated command failed but the file created could not be deleted.

System Action: None.

User Response: Delete the file shown.

ANR6777ECommand: Command file 'file name' already in use.

Explanation: The command indicated references a command file name that is in use. The command file name shown is selected for use by the server in the following order:

System Action: The server does not process the command.

User Response: Reissue the command at a later time or reissue the command specifying a different command file name.

ANR6778ECommand: Volume volume name not processed: device type device type not supported.

Explanation: The indicated volume is not processed because the device type shown is not supported by the function.

System Action: The indicated volume is not processed.

User Response: None.

ANR6779EDisaster recovery manager operation command being processed is denied - disaster recovery manager support is not available for server platform.

Explanation: The server refuses a disaster recovery manager operation because disaster recovery manager support is not available for the server platform.

System Action: Server operation continues.

User Response: None.

ANR6780EAudit command: An invalid recovery plan file expiration days encountered.

Explanation: A database audit process encounters an invalid value for recovery plan file expiration days.

System Action: Audit processing continues.

User Response: Issue the command again and specify FIX=YES to correct the expiration days. Or, issue an SET DRMRPFEXPIREDAYS command and specify a new expiration days value.

ANR6781IAudit command: An invalid recovery plan file expiration days encountered - the default value will be set.

Explanation: A database audit process encounters an invalid value for recovery plan file expiration days. Because FIX=YES has been specified, the audit function sets the expiration days value to the default value.

System Action: Audit processing continues.

User Response: To override the default value, issue a SET DRMRPFEXPIREDAYS command to change the value after the audit command has completed.

ANR6782EAudit command: Recovery plan file expiration days not found.

Explanation: A database audit process finds no entries in server database for recovery plan file expiration days definitions.

System Action: Audit processing continues.

User Response: Issue the audit command again and specify FIX=YES to correct the error.

ANR6783IAudit command: Recovery plan file expiration days not found - entry will be created.

Explanation: A database audit process finds no entries in server database for recovery plan file expiration days definitions. Because FIX=YES has been specified for the audit command, the audit function creates an entry using the default value in the server database for the recovery plan file expiration days definitions.

System Action: Audit processing continues.

User Response: To override the default value, issue a SET DRMRPFEXPIREDAYS command to change the value after the audit command has completed.

ANR6784INumber of volumes processed: number volumes processed. Volumes sent to library library name for checkout: number volumes sent.

Explanation: The MOVE DRMEDIA command has processed the number of volumes shown. Currently, the MOVE DRMEDIA command has sent for processing the number of volumes shown to the library shown. This message may be displayed in response to a QUERY PROCESS command for a MOVE DRMEDIA command.

System Action: Server operation continues.

User Response: None.

ANR6785WWarning: The ADSM V3 Disaster Recovery Manager Disk Image Dump function is not supported in the Tivoli Disaster Recovery Manager. The ADSM V3 DRM Disk Image Restore function has been stabilized with no new maintenance or hardware support planned.

Explanation: None.

System Action: DRM Disk Image Dump and Restore function continues.

User Response: None.

ANR6900ICommand: The recovery plan file file name was created.

Explanation: The recovery plan file was created.

System Action: None.

User Response: None.

ANR6901INumber of plan stanzas processed: number.

Explanation: The PREPARE command has processed the number of stanzas displayed. This message may be displayed in response to a QUERY PROCESS command for a PREPARE command.

System Action: Server operation continues.

User Response: None.

ANR6902INumber of plan stanzas processed: number. Currently processing stanza: recovery plan stanza name.

Explanation: The PREPARE command displays the number of stanzas already processed and the name of the stanza currently being processed. This message may be displayed in response to a QUERY PROCESS command for a PREPARE command.

System Action: Server operation continues.

User Response: None.

ANR6903ICancel in progress.

Explanation: The PREPARE command has been canceled and will end when resources have been freed for the background process. This message may be displayed in response to a QUERY PROCESS command for a PREPARE command.

System Action: Server operation continues.

User Response: None.

ANR6904ISending recovery plan file to target server.

Explanation: The PREPARE command is sending the recovery plan file to the target server. This message may be displayed in response to a QUERY PROCESS command for a PREPARE command.

System Action: Server operation continues.

User Response: None.

ANR6905ICommand: Recovery plan file RPF volume name was created. Specified device class device class name.

Explanation: The recovery plan file was created on the target server.

System Action: Server operation continues.

User Response: None.

ANR6912WCommand: The database was not backed up.

Explanation: No backups have been made of the server data base.

System Action: Stanzas in the recovery plan do not include database recovery information.

User Response: Backup the server data base by issuing the BACKUP DB command.

ANR6913WCommand: No volumes with backup data exist in copy storage pool storage pool name.

Explanation: A copy storage pool does not contain any volumes with usable data.

System Action: Stanzas in the recovery plan do not include recovery information for any volumes in the storage pool.

User Response: Determine why this storage pool has no volumes with usable data.

ANR6915WCommand: Storage pool storage pool name storage pool type is not defined to the server.

Explanation: A storage pool that is not defined to the server was specified by SET DRMPRIMSTGPOOL, SET DRMCOPYSTGPOOL, or on the PREPARE command line.

System Action: Stanzas in the recovery plan do not include recovery information for the storage pool.

User Response: Correct the storage pool specification or define the storage pool to the server.

ANR6916WCommand: No copy storage pools are defined.

Explanation: The server has no copy storage pools defined.

System Action: Recovery plan file will not contain copy storage pool information.

User Response: Define copy storage pools in the server.

ANR6918WCommand: Recovery instructions file file name not found.

Explanation: A source file for recovery instructions was not found.

System Action: The recovery plan will not contain recovery instructions.

User Response: To get recovery instructions in the recovery plan, ensure the corresponding instructions source file exists. If it does, check authorizations to the file.

ANR6920WCommand: Generated replacement volume name volume name is not valid for server device type device type. Original volume name: volume name. Stanza is stanza name.

Explanation: Appending the replacement volume name postfix (as defined with SET DRMPLANVPOSTFIX) to the original volume name has created a name that is not valid for the server device type shown.

System Action: Replacement volume name is used in the recovery plan stanza.

User Response: Devise a naming convention that allows the use of the replacement volume name postfix or at restore time manually update the generated recovery plan with a legal replacement name. For additional information and related commands, refer to the Administrator's Reference for your particular platform.

ANR6921WCommand: Cannot locate server options file 'file name'.

Explanation: The Prepare command cannot open the specified server options file.

System Action: VOLHISTORY and DEVCONFIG options are added to the recovery plan file stanza DSMSERV.OPT.FILE.

User Response: None.

ANR6922WCommand: No machine information was defined for the machine that contains server server name.

Explanation: The machine information has not been saved in the server data base.

System Action: The recovery plan file does not contain the machine and recovery media information stanzas.

User Response: If you want to include the machine information in the recovery plan file, issue the DEFINE MACHINE command to save the machine information in the server data base and reissue the PREPARE command.

ANR6923WCommand: No recovery media defined for machine machine name.

Explanation: No recovery media has been defined to the server for the specified machine.

System Action: The recovery plan file does not contain the machine recovery media stanza.

User Response: If you want to include the machine recovery media information in the recovery plan file, issue the DEFINE RECOVERYMEDIA command. Reissue the PREPARE command after the appropriate commands have been issued to define the recovery media. For additional information and related commands, refer to the Administrator's Reference for your particular platform.

ANR6924WCommand: No recovery instructions defined for machine machine name.

Explanation: No recovery instructions have been defined to the server for the specified machine.

System Action: The recovery plan file does not contain the machine recovery instructions stanza.

User Response: If you want to include the machine recovery instructions in the recovery plan file, issue the INSERT command. Reissue the PREPARE command after the appropriate commands have been issued to define the recovery media. For additional information and related commands, refer to the Administrator's Reference for your particular platform.

ANR6925WCommand: No machine characteristics defined for machine machine name.

Explanation: No characteristics have been defined to the server for the specified machine.

System Action: The recovery plan file does not contain the machine characteristics stanza.

User Response: If you want to include the machine recovery instructions in the recovery plan file, issue the INSERT command. Reissue the PREPARE command after the appropriate commands have been issued to define the recovery media. For additional information and related commands, refer to the Administrator's Reference for your particular platform.

ANR6926WCommand: There is at least one invalid generated volume name associated with storage pool storage pool server device type device type in stanza stanza name.

Explanation: Appending the replacement volume name postfix (as defined with SET DRMPLANVPOSTFIX) to the original volume name has created a name that is not valid for the server device type shown.

System Action: Replacement volume name is used in the recovery plan stanza.

User Response: Devise a naming convention that allows the use of the replacement volume name postfix or at restore time manually update the generated recovery plan with a legal replacement name. For additional information and related commands, refer to the Administrator's Reference for your particular platform.

ANR6937Ecommand: parameter name parameter not allowed from the command line.

Explanation: The parameter shown is not allowed from the command line interface.

System Action: The server does not process the command.

User Response: Reissue the command with the parameter from the web.

ANR6938INo information found for stanza stanza name.

Explanation: No information found for recovery plan file stanza shown.

System Action: The server does not display the information for the stanza.

User Response: None

ANR6939ECommand: Invalid recovery plan file stanza name - stanza name.

Explanation: The specified recovery plan file stanza name is invalid.

System Action: The server does not process the command.

User Response: Issue the command again and specify a valid recovery plan file stanza name.

ANR6940Ecommand command not allowed from server console.

Explanation: The indicated command is not allowed to be issued from the server console.

System Action: The command is not executed.

User Response: Reissue the command from an administrator using an Administrative Client.

ANR6941EQuery recovery plan file content is waiting for mount point in device class device class name.

Explanation: Query recovery plan file content has begun to wait for a mount point that can be used for a volume in the device class shown.

System Action: The function waits for the mount point.

User Response: Respond to any mount requests.

ANR6942EQuery recovery plan file content is waiting for access to input volume volume name.

Explanation: Query recovery plan file content has begun to wait for availability of the input volume shown.

System Action: The function waits for the volume to become available.

User Response: None.

ANR6943EQuery recovery plan file content is waiting for mount of input volume volume name.

Explanation: Query recovery plan file content has begun to wait for the mount of the input volume shown.

System Action: The function waits for mount.

User Response: Respond to any mount requests.

ANR6944ECommand: Invalid recovery plan file name - recovery plan file name.

Explanation: The recovery plan file name specified in the command is invalid.

System Action: The server does not process the command.

User Response: Issue the command again and specify a valid recovery plan file name.

ANR6945ECommand: Cannot find filespace filespace name for recovery plan file recovery plan file name.

Explanation: The server cannot find the filespace (ADSM.SERVER) for recovery plan file specified in the server.

System Action: The retrieve operation ends, and the server operation continues.

User Response: Issue QUERY FILESPACE command on the target server to see if there is any filespaces created for the recovery plan file. The filespace name for the recovery plan file is ADSM.SERVER.

ANR6946ECommand: Retrieve failed for recovery plan file name - error on input storage device.

Explanation: The server ends an retrieve operation because an I/O error has been encountered by the server in reading from a device.

System Action: The retrieve operation ends, and the server operation continues.

User Response: Query the activity log to find messages preceding this one that specify the device that is failing. The server may need to be shut down with the HALT command to correct the hardware problem.

ANR6947ECommand: Data storage retrieve failed for recovery plan file name - data integrity error detected.

Explanation: The server ends the retrieve operation because an internal database integrity error has been encountered on the server.

System Action: The retrieve operation ends, and the server operation continues.

User Response: Contact your service representative.

ANR6948ECommand: Cannot find the recovery plan file for Recovery plan file name.

Explanation: The server cannot find the specified recovery plan file.

System Action: The server does not process the command.

User Response: Issue the command again and specify a valid recovery plan file name. Use the QUERY RPFILE command to view the name of the recovery plan file that you are interested in displaying its content.

ANR6949ECommand: No matching device class defined.

Explanation: The device class specified in the command does not match any device class defined to the server.

System Action: The server does not process the command.

User Response: Issue the command again and specify a valid device class.

ANR6950ECommand: The recovery plan file was not created.

Explanation: Due to a processing error, a recovery plan file was not created.

System Action: Recovery plan file not created.

User Response: Examine error messages that may have been displayed prior to this message and correct any problems, if possible. Reissue the command, after determining the cause of the error.

ANR6951ECommand: Recovery plan file file name was not created.

Explanation: Due to a processing error, a recovery plan file was not created.

System Action: Recovery plan file not created.

User Response: Examine error messages that may have been displayed prior to this message and correct any problems, if possible. Make sure that the server has proper authority to write to the file indicated and that there is sufficient space in the file system for the file. Reissue the command, after determining the cause of the error.

ANR6952ECommand: File name file name already exists.

Explanation: File already exits.

System Action: None.

User Response: Determine why file already exists. If possible, delete it. Reissue the command, after determining the cause of the error.

ANR6953ECommand: File write error.

Explanation: An error occurred while writing to the recovery plan file.

System Action: The recovery plan file was not created.

User Response: Examine error messages that may have been displayed prior to this message and correct any problems, if possible. Make sure that there is sufficient space in the file system for the file. Reissue the command after determining the cause of the error.

ANR6954ECommand: Unable to open file 'file name' for output.

Explanation: An error occurred while opening the recovery plan file for output.

System Action: The recovery plan file was not created.

User Response: Examine error messages that may have been displayed prior to this message and correct any problems, if possible. Make sure that the server has proper authority to write to the file indicated. Reissue the command after determining the cause of the error.

ANR6959ECommand: Plan instructions prefix 'instructions prefix' is not valid.

Explanation: The prefix specified for recovery instructions is not valid.

System Action: The recovery plan file was not created.

User Response: Reissue the command specifying a valid prefix.

ANR6960ECommand: Recovery plan prefix 'plan prefix' is not valid.

Explanation: The prefix specified for the recovery plan file is too long.

System Action: The recovery plan file was not created.

User Response: Reissue the command specifying a valid prefix.

ANR6962ECommand: Query database failed.

Explanation: A server database query error occurred. This message always accompanies another error message and provides more detail about that error.

System Action: The recovery plan file was not created.

User Response: Issue a QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative.

ANR6963ECommand: Query log failed.

Explanation: A server database query error occurred. This message always accompanies another error message and provides more detail about that error.

System Action: The recovery plan file was not created.

User Response: Issue a QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative.

ANR6964ECommand: Query storage pool failed.

Explanation: An server database query error occurred. This message always accompanies another error message and provides more detail about that error.

System Action: The recovery plan file was not created.

User Response: Issue a QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative.

ANR6965ECommand: Query volume failed.

Explanation: An server database query error occurred. This message always accompanies another error message and provides more detail about that error.

System Action: The recovery plan file was not created.

User Response: Issue a QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative.

ANR6966ECommand: Query database volume failed.

Explanation: A server database query error occurred. This message always accompanies another error message and provides more detail about that error.

System Action: The recovery plan file was not created.

User Response: Issue a QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative.

ANR6967ECommand: Query log volume failed.

Explanation: A server database query error occurred. This message always accompanies another error message and provides more detail about that error.

System Action: The recovery plan file was not created.

User Response: Issue a QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative.

ANR6968ECommand: Query volume history failed.

Explanation: An server database query error occurred. This message always accompanies another error message and provides more detail about that error.

System Action: The recovery plan file was not created.

User Response: Issue a QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative.

ANR6969ECommand: Query device class failed.

Explanation: An server database query error occurred. This message always accompanies another error message and provides more detail about that error.

System Action: The recovery plan file was not created.

User Response: Issue a QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative.

ANR6970ECommand: A recovery plan file is already being created.

Explanation: The server command processor will not start a background process to execute another PREPARE command.

System Action: The command process ends and server operation continues.

User Response: Reissue the command after the first PREPARE command has completed.

ANR6971ECommand: Could not delete plan file plan file name.

Explanation: Prepare command failed but the plan file created could not be deleted.

System Action: None.

User Response: Delete the plan file.

ANR6972ECommand: Query machine failed.

Explanation: A server machine query error occurred. This message always accompanies another error message and provides more detail about that error.

System Action: The recovery plan file was not created.

User Response: Issue a QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative.

ANR6973ECommand: Query recovery media failed.

Explanation: A server recovery media query error occurred. This message always accompanies another error message and provides more detail about that error.

System Action: The recovery plan file was not created.

User Response: Issue a QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative.

ANR6974ECommand: Unable to open file file name.

Explanation: An error occurred while PREPARE was attempting to open the local recovery plan file copy in order to send it to the target server.

System Action: The recovery plan file is not stored on the target server.

User Response: Examine error messages that may have been displayed prior to this message and correct any problems, if possible. Reissue the command after determining the cause of the error.

ANR6975ECommand: Unable to read file file name.

Explanation: An error occurred while PREPARE was attempting to read the local recovery plan file copy in order to send it to the target server.

System Action: The recovery plan file is not stored on the target server.

User Response: Examine error messages that may have been displayed prior to this message and correct any problems, if possible. Reissue the command after determining the cause of the error.

ANR6976ECommand: The recovery plan file was not stored on another server and the local copy file name cannot be deleted.

Explanation: Due to a processing error, a recovery plan file was not stored on target server and the local copy of the plan file cannot be deleted.

System Action: PREPARE processing ends.

User Response: Examine error messages that may have been displayed prior to this message and correct any problems, if possible. After determining the cause of the error, re-issue the PREPARE command and delete the local recovery plan file.

ANR6977ECommand: Device class name device class name exceeds maximum characters characters.

Explanation: The command shown has been entered and specifies a device class name that is too long. The maximum valid length for a device class name is shown in the message.

System Action: The server does not process the command.

User Response: Reissue the command specifying a valid device class name.

ANR6978ECommand: Invalid device class device class name.

Explanation: The specified device class cannot be used by the command shown. Possible reasons include:

System Action: The server does not process the command.

User Response: Reissue the command with a valid device class.

ANR6979ECommand: Recovery plan file was not created. Specified device class device class name.

Explanation: A recovery plan file cannot be not created using the specified device class.

System Action: Recovery plan file not created.

User Response: Examine error messages that may have been displayed prior to this message and correct any problems, if possible. Reissue the command, after determining the cause of the error.

ANR6980ECommand: Prefix prefix exceeds maximum characters characters.

Explanation: The command shown has been entered and specifies a plan or instructions prefix that is too long. The maximum valid length is shown in the message.

System Action: The server does not process the command.

User Response: Reissue the command specifying a shorter prefix.

ANR6984ECommand: Out of space on sequential media, scratch media could not be mounted. Specified device class device class name; maximum capacity: number of bytes bytes.

Explanation: During command PREPARE processing, the process encounters an out-of-space condition writing to the sequential media. Command PREPARE ends when there is no more space on the sequential media for storing data.

System Action: Command PREPARE processing ends. Server processing continues.

User Response: Increase the device class maximum capacity and reissue the PREPARE command. If an object was created on the target server, issue the RECONCILE VOLUMES FIX=YES to delete the object from the target server.

ANR6985ECommand: Error encountered in accessing data storage - volume already in use.

Explanation: During command command processing, a volume cannot be used because it is already defined in a storage pool, or has been previously used by an export, database dump, database backup, or DRM prepare operation or is in use by another process.

System Action: The command command operation is ended and server operation continues.

User Response: Re-issue the PREPARE command.

ANR6986ECommand: The DELETELATEST parameter is only valid for volume history types RPFILE or RPFSNAPSHOT.

Explanation: The command failed because an invalid volume history type was specified for the TYPE= parameter.

System Action: The command fails, and server operation continues.

User Response: Re-issue the command and specify a valid type value.

ANR7800I (AIX)DSMSERV generated at time on date.

Explanation: The server module was generated at the indicated date and time.

System Action: Server operation continues.

User Response: None.

ANR7800I (AS/400)QANRSERV generated at time on date.

Explanation: The ADSM server module has been generated at the indicated date and time.

System Action: Server operation continues.

User Response: None.

ANR7800I (HP-UX)DSMSERV generated at time on date.

Explanation: The server module was generated at the indicated date and time.

System Action: Server operation continues.

User Response: None.

ANR7800I (Solaris)DSMSERV generated at time on date.

Explanation: The server module was generated at the indicated date and time.

System Action: Server operation continues.

User Response: None.

ANR7800I (Windows NT)DSMSERV generated at time on date.

Explanation: The server module was generated at the indicated date and time.

System Action: Server operation continues.

User Response: None.

ANR7801I (AIX)Subsystem (master) PID is process identifier.

Explanation: The server kernel extension process has the indicated process identifier.

System Action: Server operation continues.

User Response: None.

ANR7801I (HP-UX)Subsystem (master) process ID is process identifier.

Explanation: The server's master HP-UX process has the indicated process identifier.

System Action: Server operation continues.

User Response: None.

ANR7801I (Solaris)Subsystem process ID is process identifier.

Explanation: The server process has the indicated process identifier.

System Action: Server operation continues.

User Response: None.

ANR7802E (AIX)Shared memory segments for a server running in the current directory already exist. The -F parameter can be used to overwrite.

Explanation: Shared memory segments are created for each instance of the server based on the current directory. This message indicates that the shared memory segments already exist. A server is presently running from the current directory or a server running from the current directory ended abnormally.

System Action: The server terminates.

User Response: If the server running in the current directory terminated abnormally, start dsmserv with the -F parameter to force the existing shared memory segments to be overwritten. If you want to run multiple instances of the server, each instance must be run from a separate directory with a separate dsmserv.dsk file and have separate log, database, and storage volumes.

ANR7803E (AIX)Attempt to overwrite a shared memory segment, as directed with the -F parameter, FAILED.

Explanation: The server has been started with the -F parameter and unsuccessfully attempted to overwrite existing shared memory segments. This error occurs when the user that starts the server with -F parameter is not the owner of the shared memory segments and lacks the required authority.

System Action: Server terminates.

User Response: Resolve the authorization problem and restart the server.

ANR7804I (AIX)An server is already running from this directory.

Explanation: The server has attempted to open the adsmserv.lock file in the current directory but failed to do so because an existing server already has the file open.

System Action: Server terminates.

User Response: Examine the contents of the adsmserv.lock file. The process ID for the server that is running is recorded in this file. Two servers cannot be started from the same directory. You may remove the adsmserv.lock file and attempt to start the server ONLY if the recorded process ID is NOT currently running dsmserv. The 'ps -e' AIX command can be used to display processes that are currently running.

ANR7804I (HP-UX)A server is already running from this directory.

Explanation: The server has attempted to open the adsmserv.lock file in the current directory but failed to do so because an existing server already has the file open.

System Action: Server terminates.

User Response: Examine the contents of the adsmserv.lock file. The process ID for the server that is running is recorded in this file. Two servers cannot be started from the same directory. You may remove the adsmserv.lock file and attempt to start the server ONLY if the recorded process ID is NOT currently running dsmserv. The 'ps -e' command can be used to display processes that are currently running.

ANR7805E (AIX)Volume volume name is in use by another server.

Explanation: The server has attempted to open a disk volume but has discovered that the volume is in use by another server.

System Action: The open operation fails for the volume.

User Response: To prevent concurrent RAW volume access by more than one server, files are created in the /tmp directory to 'lock' these volumes. The names of these temporary files are /tmp/adsm.disk.dev.<volumename> where <volumename> is the name of the RAW volume defined in the /dev directory. Please note that the name for the logical volume as defined in SMIT is represented in the /dev directory with a leading 'r' character (for example, a raw volume defined in SMIT as dsmstg1 will be represented in the /dev directory as the file /dev/rdsmstg1).

You may use the AIX 'ps -e' command to determine if other dsmserv processes are running. You may remove the temporary lock files and attempt to re-start the server ONLY if there are no other dsmserv processes running

ANR7805E (Solaris)Volume volume name is in use by another server.

Explanation: The server has attempted to open a disk volume but has discovered that the volume is in use by another server.

System Action: The open operation fails for the volume.

User Response: To prevent concurrent RAW volume access by more than one server, files are created in the /tmp directory to 'lock' these volumes. The names of these temporary files are /tmp/adsm.disk.dev.<volumename> where <volumename> is the name of the RAW volume defined in the /dev directory. Please note that the name for a RAW logical volume as defined in Solaris is in the /dev directory with a leading 'r' character (for example, a raw volume defined in Solaris on a regular SCSI drive as dsk/c0t0d0s0 will be represented in the /dev directory as the file /dev/rdsk/c0t0d0s0). For a REGULAR DISK volume, the server automatically locks/unlocks a volume. Different linked file names pointing to the same volume will cause this message since the server locks the linked volume, not the link name itself.

You may use the Solaris 'ps -ef | grep dsmserv' command to determine if other dsmserv processes are running. You may remove the temporary lock files for RAW volumes and attempt to re-start the server ONLY if there are no other dsmserv processes are running.

ANR7806W (AIX)Unable to open file file.

Explanation: The server was unable to open the indicated file.

System Action: The operation that was to use the indicated file fails. A subsequent unnumbered message had details from the system.

User Response: Determine the reason for being unable to open the file and re-attempt the operation. Common reasons for being unable to open the file include providing the wrong name, having insufficient authorization to open the file and not being the file's owner.

ANR7806W (HP-UX)Unable to open file file.

Explanation: The server was unable to open the indicated file.

System Action: The operation that was to use the indicated file fails. A subsequent unnumbered message had details from the system.

User Response: Determine the reason for being unable to open the file and re-attempt the operation. Common reasons for being unable to open the file include providing the wrong name, having insufficient authorization to open the file and not being the file's owner.

ANR7806W (Solaris)Unable to open file file.

Explanation: The server was unable to open the indicated file.

System Action: The operation that was to use the indicated file fails. A subsequent unnumbered message had details from the system.

User Response: Determine the reason for being unable to open the file and re-attempt the operation. Common reasons for being unable to open the file include providing the wrong name, having insufficient authorization to open the file and not being the file's owner.

ANR7806W (Windows NT)Unable to open file file.

Explanation: The server was unable to open the indicated file.

System Action: The operation that was to use the indicated file fails. A subsequent unnumbered message had details from the system.

User Response: Determine the reason for being unable to open the file and re-attempt the operation. Common reasons for being unable to open the file include providing the wrong name, having insufficient authorization to open the file and not being the file's owner. The file may be already opened by the server or another program.

ANR7807W (AIX)Unable to get information for file file.

Explanation: The server was unable to get information about the indicated file.

System Action: The operation that was to use the indicated file fails. A subsequent, unnumbered message has details from the system.

User Response: Determine the reason for being unable to access the file and re-attempt the operation. Common reasons for being unable to access the file include providing the wrong name, having insufficient authorization to open the file and not being the file's owner.

ANR7807I (AS/400)User is not authorized to reset password.

Explanation: The user must have either all object authority, security administrator authority, or security officer authority.

System Action: Server operation ends.

User Response: None.

ANR7807W (HP-UX)Unable to get information for file file.

Explanation: The server was unable to get information about the indicated file.

System Action: The operation that was to use the indicated file fails. A subsequent, unnumbered message has details from the system.

User Response: Determine the reason for being unable to access the file and re-attempt the operation. Common reasons for being unable to access the file include providing the wrong name, having insufficient authorization to open the file and not being the file's owner.

ANR7807W (Solaris)Unable to get information for file file.

Explanation: The server was unable to get information about the indicated file.

System Action: The operation that was to use the indicated file fails. A subsequent, unnumbered message has details from the system.

User Response: Determine the reason for being unable to access the file and re-attempt the operation. Common reasons for being unable to access the file include providing the wrong name, having insufficient authorization to open the file, not being the file's owner, or too many soft links to the file. If trying to access a RAW partition, the server must be started with superuser privileges.

ANR7808W (AS/400)AS/400 action returned exception exception ID.

Explanation: The server attempts to perform the given AS/400 action, and the indicated exception ID is returned. The server may issue additional error messages if this condition prevents it from completing an operation.

System Action: Server operation continues.

User Response: If the exception prevents the server from completing an operation, evaluate both the specified exception and the AS/400 action to determine the steps necessary to correct the problem.

ANR7809I (AS/400)Formatting file fileName at size fileSize.

Explanation: The specified file is being formatted.

System Action: Server operation continues.

User Response: None.

ANR7810W (AIX)Unable to create a new child process.

Explanation: The server cannot create a new child thread.

System Action: Server processing continues. Other error messages from the server component are displayed.

User Response: Ensure that sufficient paging space is available for AIX. If the server has been started from a non-root user ID, ensure that the AIX process limit per user is sufficient for the server. The server requires approximately 24 processes, in addition to one process per client session, and one process for each background operation. Each thread started by the server is an AIX process. To change the number of processes per user, use the SMIT menus for System Environment, and choose Change / Show Characteristics of Operating System. You may also use SMIT to determine if the number of applications is causing a memory shortage. It may be necessary to decrease the maximum number of client sessions by changing the MAXSESSIONS option in the server options file.

ANR7810I (AS/400)Connected to Tivoli event server at node name on port port.

Explanation: The server successfully established a connection with the Tivoli event server on the specified node name and port.

System Action: Server sends events to the Tivoli event server using this connection.

User Response: None.

ANR7810E (HP-UX)Error creating console input thread.

Explanation: Unable to start console input thread.

System Action: Server operation stops.

User Response: See other issued messages.

ANR7810E (Solaris)Error creating console input thread.

Explanation: Unable to start console input thread.

System Action: Server operation stops.

User Response: See other issued messages.

ANR7811E (AS/400)Unable to connect to the Tivoli event server at node name on port port.

Explanation: The server was unable to established a connection with the Tivoli event server on the specified node name and port.

System Action: Event logging to the Tivoli event server is disabled.

User Response: Ensure that the Tivoli event server is running on the specified system. If the system on which the event server is running does not support the TCP/IP Portmapper, then ensure that the value specifed for Tivoli Port in the ADSM server options file is correct.

ANR7811E (HP-UX)Insufficient memory for console initialization.

Explanation: The server is unable to allocate enough memory for console initialization.

System Action: Server operation stops.

User Response: Ensure that there is sufficient paging space for HP-UX. It may be necessary to reduce the maximum number of client sessions by changing the MAXSESSIONS option in the server options file.

ANR7811E (Solaris)Insufficient memory for console initialization.

Explanation: The server is unable to allocate enough memory for console initialization.

System Action: Server operation stops.

User Response: Ensure that there is sufficient paging space for Sun Solaris. It may be necessary to reduce the maximum number of client sessions by changing the MAXSESSIONS option in the server options file.

ANR7812E (AS/400)Unable to determine port of Tivoli event server on node name.

Explanation: The server was unable to determine the TCP/IP port on which the Tivoli event server on node name is listening.

System Action: Event logging to the Tivoli event server is disabled.

User Response: Ensure that the Tivoli event server is running on the specified system. If the system on which the event server is running does not support the TCP/IP Portmapper, then ensure that the value specified for Tivoli Port in the ADSM server options file is correct.

ANR7812E (HP-UX)Insufficient memory to buffer console input. The following input line was discarded: discarded console input.

Explanation: An error occurs during an attempt to allocate a buffer to hold the specified console input.

System Action: The console input is discarded.

User Response: Ensure that there is sufficient paging space for HP-UX. It may be necessary to reduce the maximum number of client sessions by changing the MAXSESSIONS option in the server options file.

ANR7812E (Solaris)Insufficient memory to buffer console input. The following input line was discarded: discarded console input.

Explanation: An error occurs during an attempt to allocate a buffer to hold the specified console input.

System Action: The console input is discarded.

User Response: Ensure that there is sufficient paging space for Sun Solaris. It may be necessary to reduce the maximum number of client sessions by changing the MAXSESSIONS option in the server options file.

ANR7813E (AS/400)Unable to connect to Tivoli event server because TCP/IP is not available.

Explanation: The server was unable to establish a TCP/IP connection with the Tivoli event server because TCP/IP services were not available.

System Action: Event logging to the Tivoli event server is disabled.

User Response: Ensure that TCP/IP is enabled in the server. If TCP/IP is enabled, use the BEGIN EVENTLOGGING TIVOLI to restart the event logging to Tivoli.

ANR7813W (Solaris)Unable to create a new child thread.

Explanation: The server cannot create a new child thread.

System Action: Server processing continues. Other error messages from the server component are displayed.

User Response: Ensure that sufficient swap space is available for Solaris. The amount of swap available can be obtain by executing 'swap -l'. If the number of free blocks is low, you can add swap files while the system is running by executing 'mkfile' and then 'swap -a'. See the Solaris man pages on 'mkfile' and 'swap' for more details. If the server has been started from a non-root user ID, ensure that the Solaris process limit per user is sufficient for the server. You can tune the 'maxusers=##' parameter in the /etc/system file to increase the number of number of users that can be on the system at one time. This will also force the kernel to allocate more memory/swap for user-processes. A system reboot with the 'reconfigure' option is required for the new user settings to take effect. It may be necessary to decrease the maximum number of client sessions by changing the MAXSESSIONS option in the server options file.

ANR7814E (AS/400)User exit exit name encountered an error. Exit is disabled.

Explanation: An error occurred when invoking the user exit.

System Action: The user exit is disabled.

User Response: Ensure that the program being invoked is correct. When the problem has been correct, END EVENTLOGGING USEREXIT and then BEGIN EVENTLOGGING USEREXIT to restart event logging to the user exit.

ANR7815E (AS/400)Unable to find user exit exit name.

Explanation: An error occurred when trying to resolve to the specified user exit.

System Action: The user exit is disabled.

User Response: Ensure that the program being invoked is correct. When the problem has been correct, END EVENTLOGGING USEREXIT and then BEGIN EVENTLOGGING USEREXIT to restart event logging to the user exit.

ANR7816E (AS/400)ADSM server does not have the authority to invoke exit exit name.

Explanation: An error occurred when trying to resolve to the specified user exit.

System Action: The user exit is disabled.

User Response: Ensure that the user starting the server or the user QADSM has authority to the specified exit. When the problem has been correct, END EVENTLOGGING USEREXIT and then BEGIN EVENTLOGGING USEREXIT to restart event logging to the user exit.

ANR7817E (AS/400)Unable to open file file name for file exit.

Explanation: An error occurred when trying to open the file specified for the file exit.

System Action: The file exit is disabled.

User Response: Ensure that the user starting the server or the user QADSM has authority to the specified file. When the problem has been correct, END EVENTLOGGING FILE and then BEGIN EVENTLOGGING FILE to restart event logging to the file.

ANR7818E (AS/400)Unable to write to file file name for file exit, errno errno.

Explanation: An error occurred when trying to write the file specified for the file exit.

System Action: The file is disabled.

User Response: Ensure that the user starting the server or the user QADSM has authority to the specified file. When the problem has been corrected, END EVENTLOGGING ... and then BEGIN EVENTLOGGING ... to restart event logging to the file.

ANR7819I (AS/400)User AS/400 user ID issued ENDSRVADSM.

Explanation: User issued ENDSRVADSM command.

System Action: Server operation terminates.

User Response: None.

ANR7820E (AIX)Insufficient memory to buffer console input; the following input line was discarded: discarded console input.

Explanation: An error occurs during an attempt to allocate a buffer large enough to read console input.

System Action: The console input is discarded.

User Response: Ensure that sufficient paging space is available for AIX. You may also use SMIT to determine if the number of applications is causing a memory shortage. It may be necessary to decrease the maximum number of client sessions by changing the MAXSESSIONS option in the server options file.

ANR7820E (AS/400)Unable to open file file name for filetext exit.

Explanation: An error occurred when trying to open the file specified for the filetext exit.

System Action: The filetext exit is disabled.

User Response: Ensure that the user starting the server or the user QADSM has authority to the specified file. When the problem has been correct, END EVENTLOGGING FILETEXT and then BEGIN EVENTLOGGING FILETEXT to restart event logging to the file.

ANR7820S (HP-UX)Server thread thread ID terminated in response to program abort.

Explanation: The thread has ended due to a program abort.

System Action: The server completes termination processing.

User Response: Note the associated messages and contact your service representative.

ANR7820S (Solaris)Server thread thread ID terminated in response to program abort.

Explanation: The thread has ended due to a program abort.

System Action: The server completes termination processing.

User Response: Note the associated messages and call your service representative.

ANR7820W (Windows NT)Insufficient Space Available for file file name.

Explanation: The server was attempting to create a file with the indicated name. There was insufficient space for the file on the disk.

System Action: Server processing continues. The file creation request fails.

User Response: Specify a file name on a drive with sufficient space or change the space request to a value consistent with the drive.

ANR7821E (AIX)Error reading from standard input.

Explanation: An error occurs during an attempt to read from standard input.

System Action: The console input thread is terminated.

User Response: Correct the standard input problem and restart the server.

ANR7821I (HP-UX)Server thread thread ID terminated in response to external signal.

Explanation: The thread has ended due to an external signal.

System Action: The server completes termination processing.

User Response: None.

ANR7821I (Solaris)Server thread thread ID terminated in response to external signal.

Explanation: The thread has ended due to an external signal.

System Action: The server completes termination processing.

User Response: None.

ANR7821W (Windows NT)Unable to create directory when creating volume file name.

Explanation: The server was attempting to create a file with the indicated name. A new directory was being created as well, but its creation failed.

System Action: Server processing continues. The file creation request fails.

User Response: Specify a file name in an existing directory or change the name request to specify a different directory name.

ANR7822E (AIX)Error creating console input thread.

Explanation: Unable to start console input thread.

System Action: Server operation stops.

User Response: See other issued messages.

ANR7822I (HP-UX)Server thread thread ID terminated in response to server shutdown.

Explanation: The thread has ended due to a server shutdown.

System Action: The server completes termination processing.

User Response: None.

ANR7822I (Solaris)Server thread thread ID terminated in response to server shutdown.

Explanation: The thread has ended due to a server shutdown.

System Action: The server completes termination processing.

User Response: None.

ANR7822W (Windows NT)File Already exists when creating volume file name.

Explanation: The server was attempting to create a file with the indicated name. The file already exists.

System Action: Server processing continues. The file creation request fails.

User Response: Specify a new file name. The server will not use an existing file name when creating a file.

ANR7823E (AIX)Insufficient memory for console initialization.

Explanation: Unable to allocate enough memory for console initialization.

System Action: Server operation stops.

User Response: Ensure that sufficient paging space is available for AIX. You may also use SMIT to determine if the number of applications is causing a memory shortage. It may be necessary to decrease the maximum number of client sessions by changing the MAXSESSIONS option in the server options file.

ANR7823W (Windows NT)Unable to create file file name.

Explanation: The server was attempting to create a file with the indicated name. The system reported an error in creating the file.

System Action: The server continues processing. The file creation request fails.

User Response: Specify a new file name.

ANR7824S (HP-UX)Server operation terminated.

Explanation: An error occurs that causes server operation to stop.

System Action: Server operation stops.

User Response: Contact your service representative.

ANR7824S (Solaris)Server operation terminated.

Explanation: An error occurs that causes server operation to stop.

System Action: Server operation stops.

User Response: Contact your service representative.

ANR7824W (Windows NT)Unable to write volume file name.

Explanation: The server was attempting to create a file with the indicated name. The server was able to partially write to the file before running out of space.

System Action: The server continues processing. The file creation request fails. The file is still present on the system.

User Response: Specify a new file name where there is sufficient space.

ANR7825E (Solaris)Server unable to allocate a shared memory segment of size Client requested shared memory size.

Explanation: A shared memory client has requested a shared memory segment size that Solaris is unable to fulfill.

System Action: Client is not allowed to logon

User Response: See the shared memory tuning guide for Solaris (a Sun document). You may need to increase the number/size of shared memory segments and/or message queues.

ANR7825W (Windows NT)Unable to create volume file name. Return code=return code.

Explanation: The server was attempting to create a file with the indicated name. The attempt failed with the indicated return code. The return code is an internal code from the server.

System Action: The server continues processing. The file creation request fails.

User Response: Specify a new file name. The return code may also be provided to your service representative for interpretation.

ANR7826W (Windows NT)Creation of Volume file name failed. Process was cancelled.

Explanation: The server was attempting to create a file with the indicated name. The attempt was cancelled by a cancel process command.

System Action: The server continues processing. The file creation request fails.

User Response: The DEFINE command may be re-entered.

ANR7830E (Solaris)Invalid RAW Partition Name: A valid raw partition name is in the form of /dev/.../rdsk/.../* , where ... means 0 or more directories.

Explanation: Use the proper format for specifying a Raw partition. The ... means zero or more directories.

System Action: Inform the user to use the right RAW partition specification.

User Response: Have user reenter the RAW partition with the proper partition name.

ANR7831E (Solaris)raw partition name has an existing filesystem.

Explanation: The RAW partition specified has an existing Solaris file system on it. Writing to this Partition will most likely destroy this filesystem.

System Action: Warn the user that an existing filesystem for the raw partition specified may be destroyed if written to.

User Response: Determine if user still wants the valid filesystem data. If not, user needs to destroy the filesystem by either formatting the partition, create a program to destroy the filesystem header information so that the server will not be able to detect the filesystem header information, or rearrange the starting and ending blocks of a partition by using the Solaris format() command. The user can read the format() function in the Sun manuals for further details on filesystems.

ANR7832I (AIX)The thread process ID terminated with exit code program exit code.

Explanation: The process has ended with the indicated exit code. This error is due to the problem caused and indicated by a preceding message.

System Action: The server completes termination processing.

User Response: None.

ANR7832E (Solaris)Raw partition name corresponds to a protected filesystem, such as / or /usr.

Explanation: The RAW partition specified has an existing file system on it. This filesystem is the / or /usr partition. If the SERVER writes to it, it will most likely crash the whole operating system.

System Action: Disallow access to this raw partition.

User Response: Have user specify another RAW partition that is not the / or /usr. It may be possible that this is not the actual / or /usr partition of the boot disk. Check, using the Solaris format() command, if your partition name tag is labeled incorrectly as / or /usr.

ANR7833S (AIX)The process thread ID terminated in response to program abort.

Explanation: The thread has ended due to a program abort.

System Action: The server completes termination processing.

User Response: None.

ANR7833E (Solaris)Symbolic links has too many symbolic links - the server only supports a maximum of 10.

Explanation: The file specified has too many symbolic links. The server will follow at most 10 links before ending this symbolic link name resolution.

System Action: Disallow access to this file

User Response: Have the user specify the actual file, where the file is not a symbolic link. Using ls -l, one can see if the file is a symbolic link.

ANR7834I (AIX)The thread thread ID terminated in response to external signal.

Explanation: The thread has ended due to an external signal.

System Action: The server completes termination processing.

User Response: None.

ANR7834E (Solaris)Specified raw partition name raw partition cannot contain the 0th disk cylinder.

Explanation: The raw partition specified has the 0th disk cylinder. The server should not be allowed to write into the 0th cylinder. It allowed, the disk label would be corrupted.

System Action: Disallow access to this raw partition

User Response: Have the system administrator change the starting cylinder of this partition to a number greater than 0.

ANR7834I (Windows NT)The server thread thread ID (tid Windows NT thread ID) terminated in response to external signal.

Explanation: The thread has terminated due to an external signal.

System Action: The server completes termination processing.

User Response: None.

ANR7835I (AIX)The server thread thread ID terminated in response to server shutdown.

Explanation: The thread has ended due to a server shutdown.

System Action: The server completes termination processing.

User Response: None.

ANR7835E (Solaris)Specified raw partition name raw partition is too big for this operating system to handle.

Explanation: The raw partition specified has greater than 2GB and the operating system is running below Solaris 2.6. Operating system below Solaris 2.6 cannot handle files natively more than 2GB. For operating system that is at Solaris 2.6 or above, the limit is 1TB.

System Action: Disallow access to this raw partition

User Response: Have the system administrator change the RAW partition size to be less than 2GB (4194303 512-byte disk blocks) for Solaris 2.5.1 or below, less than 1TB (2147483647 512-byte disk blocks) for Solaris 2.6 and above.

ANR7835I (Windows NT)The server thread thread ID (tid Windows NT thread ID) terminated in response to server shutdown.

Explanation: The thread has terminated due to a server shutdown.

System Action: The server completes termination processing.

User Response: None.

ANR7836S (AIX)Server initialization terminated.

Explanation: An error occurs that causes server initialization to end.

System Action: Server operation stops.

User Response: Contact your service representative.

ANR7838S (AIX)Server operation terminated.

Explanation: An error occurs that causes server operation to stop.

System Action: Server operation stops.

User Response: Contact your service representative.

ANR7839E (AS/400)Unable to open file filespec.

Explanation: An error occurs while the server tries to open the specified file.

System Action: Server processing continues.

User Response: Check job logs and previously issued messages for additional information regarding the error.

ANR7840E (AS/400)Error reading from file filespec.

Explanation: An error occurs while the server is trying to read from the specified file.

System Action: Server processing continues.

User Response: Check job logs and previously issued messages for additional information regarding the error.

ANR7841S (AIX)Insufficient kernel memory available.

Explanation: An error occurs due to insufficient kernel memory.

System Action: Server operation stops.

User Response: Contact your service representative.

ANR7841E (AS/400)Error positioning file filespec.

Explanation: An error occurs while the server is trying to locate a record in the specified file.

System Action: Server processing continues.

User Response: Check job logs and previously issued messages for additional information regarding the error.

ANR7842S (AIX)Monitor kernel extension not initialized.

Explanation: The monitor kernel extension is not initialized.

System Action: Server operation stops.

User Response: Contact your service representative.

ANR7842E (AS/400)Error writing to file filespec.

Explanation: An error occurs while the server is trying to write to the specified file.

System Action: Server processing continues.

User Response: Check job logs and previously issued messages for additional information regarding the error.

ANR7843W (AIX)Unable to determine real memory size.

Explanation: The server checks the amount of real memory in the system to optimize use of storage in the database buffer pool. The server uses Object Data Manager (ODM) to determine how much real memory is installed on the system. The routines used to call ODM failed or were unable to return the real memory size.

System Action: Server operation continues. The server allows the data base buffer pool size to grow withoug taking into account real memory.

User Response: The server may need to run as a root user to obtain this information.

ANR7843W (AS/400)Receiver records will be truncated.

Explanation: The receiver file records will be truncated because the file record length is smaller than expected.

System Action: Server processing continues.

User Response: None.

ANR7843W (HP-UX)Unable to determine real memory size.

Explanation: The server checks the amount of real memory in the system to optimize use of storage in the database buffer pool. The routines used to obtain this information returned a failing return code or were unable to return the real memory size.

System Action: Server operation continues. The server allows the data base buffer pool size to grow withoug taking into account real memory.

User Response: The server may need to run as a root user to obtain this information.

ANR7843W (Solaris)Unable to determine real memory size.

Explanation: The server checks the amount of real memory in the system to optimize use of storage in the database buffer pool. The routines used to obtain this information returned a failing return code or were unable to return the real memory size.

System Action: Server operation continues. The server allows the data base buffer pool size to grow withoug taking into account real memory.

User Response: The server may need to run as a root user to obtain this information.

ANR7843W (Windows NT)Unable to determine real memory size.

Explanation: The server checks the amount of real memory in the system to optimize use of storage in the database buffer pool. The routines used to obtain this information returned a failing return code or were unable to return the real memory size.

System Action: Server operation continues. The server allows the data base buffer pool size to grow withoug taking into account real memory.

User Response: The server may need to run as a root user to obtain this information.

ANR7844W (AS/400)Expected receiver file size recordLength but found size recordLength.

Explanation: The receiver file records will be truncated because the file record length is smaller than expected.

System Action: Server processing continues.

User Response: None.

ANR7849I (AIX)Server operation terminated - kernel extension has been reset.

Explanation: The kernel extension has been reinitialized by the server in response to a previous condition for which a message has been issued.

System Action: Server operation stops.

User Response: None.

ANR7850I (AIX)The process process ID has terminated on signal signal number (signal name).

Explanation: The specified process has ended due to the specified signal.

System Action: Server operation stops.

User Response: Contact your service representative.

ANR7851S (AIX)Error resetting handler for signal signal number (signal name).

Explanation: An error occurs resetting the specified signal handler.

System Action: Server operation stops.

User Response: Contact your service representative.

ANR7852I (Windows NT)The current process affinity mask is: 0xThe process affinity mask..

Explanation: The server is running on the processors indicated by the mask.

System Action: Server operation continues.

User Response: None.

ANR7853W (Windows NT)Could not obtain the current process affinity mask. Reason: NT return code..

Explanation: A problem was encounterd while obtaining the current process affinity.

System Action: Server operation continues.

User Response: None.

ANR7854W (Windows NT)The process affinity mask (0xAffinity mask.) specified in dsmserv.opt is out of range.

Explanation: The affinity mask value was out of range.

System Action: Server operation continues.

User Response: None.

ANR7855W (Windows NT)Could not set new process affinity mask. Reason: NT return code.

Explanation: A problem was encounterd in setting a new process affinity mask.

System Action: Server operation continues.

User Response: None.

ANR7856W (Windows NT)The affinity mask (0xNT return code.) was set to a value other than what was requested

Explanation: A new affinity mask was set but on verification it was found not to match what was requested.

System Action: Server operation continues.

User Response: None.

ANR7860W (AIX)Insufficient Space Available for file file name.

Explanation: The server was attempting to create a file with the indicated name. There was insufficient space for the file in the filesystem.

System Action: The server continues processing. The file creation request fails.

User Response: Specify a file name in a filesystem with sufficient space or change the space request to a value consistent with the filesystem.

ANR7860W (AS/400)Insufficient Space Available for file file name.

Explanation: ADSM was attempting to create a file with the indicated name. There was insufficient space for the file in the filesystem.

System Action: ADSM continues processing. The file creation request fails.

User Response: Specify a file name in a filesystem with sufficient space or change the space request to a value consistent with the filesystem.

ANR7860W (HP-UX)Insufficient Space Available for file file name.

Explanation: The server was attempting to create a file with the indicated name. There was insufficient space for the file in the filesystem.

System Action: The server continues processing. The file creation request fails.

User Response: Specify a file name in a filesystem with sufficient space or change the space request to a value consistent with the filesystem.

ANR7860W (Solaris)Insufficient Space Available for file file name.

Explanation: The server was attempting to create a file with the indicated name. There was insufficient space for the file in the filesystem.

System Action: The server continues processing. The file creation request fails.

User Response: Specify a file name in a filesystem with sufficient space or change the space request to a value consistent with the filesystem.

ANR7861W (AIX)Unable to create directory when creating volume file name.

Explanation: The server was attempting to create a file with the indicated name. A new directory was being created as well, but its creation failed.

System Action: The server continues processing. The file creation request fails.

User Response: Specify a file name in an existing directory or or change the name request to specify a different directory name.

ANR7861W (AS/400)Unable to create directory when creating volume file name.

Explanation: ADSM was attempting to create a file with the indicated name. A new directory was being created as well, but its creation failed.

System Action: ADSM continues processing. The file creation request fails.

User Response: Specify a file name in an existing directory or or change the name request to specify a different directory name.

ANR7861W (HP-UX)Unable to create directory when creating volume file name.

Explanation: The server was attempting to create a file with the indicated name. A new directory was being created as well, but its creation failed.

System Action: The server continues processing. The file creation request fails.

User Response: Specify a file name in an existing directory or or change the name request to specify a different directory name.

ANR7861W (Solaris)Unable to create directory when creating volume file name.

Explanation: The server was attempting to create a file with the indicated name. A new directory was being created as well, but its creation failed.

System Action: The server continues processing. The file creation request fails.

User Response: Specify a file name in an existing directory or or change the name request to specify a different directory name.

ANR7862W (AIX)File Already exists when creating volume file name.

Explanation: The server was attempting to create a file with the indicated name. The file already exists.

System Action: The server continues processing. The file creation request fails.

User Response: Specify a new file name. The server will not use an existing file name when creating a file.

ANR7862W (AS/400)File Already exists when creating volume file name.

Explanation: ADSM was attempting to create a file with the indicated name. The file already exists.

System Action: ADSM continues processing. The file creation request fails.

User Response: Specify a new file name. ADSM will not use an existing file name when creating a file.

ANR7862W (HP-UX)File Already exists when creating volume file name.

Explanation: The server was attempting to create a file with the indicated name. The file already exists.

System Action: The server continues processing. The file creation request fails.

User Response: Specify a new file name. The server will not use an existing file name when creating a file.

ANR7862W (Solaris)File Already exists when creating volume file name.

Explanation: The server was attempting to create a file with the indicated name. The file already exists.

System Action: The server continues processing. The file creation request fails.

User Response: Specify a new file name. The server will not use an existing file name when creating a file.

ANR7863W (AIX)Unable to create file file name.

Explanation: The server was attempting to create a file with the indicated name. The system reported an error in creating the file.

System Action: The server continues processing. The file creation request fails.

User Response: Specify a new file name.

ANR7863W (AS/400)Unable to create file file name.

Explanation: ADSM was attempting to create a file with the indicated name. The system reported an error in creating the file.

System Action: ADSM continues processing. The file creation request fails.

User Response: Specify a new file name.

ANR7863W (HP-UX)Unable to create file file name.

Explanation: The server was attempting to create a file with the indicated name. The system reported an error in creating the file.

System Action: The server continues processing. The file creation request fails.

User Response: Specify a new file name.

ANR7863W (Solaris)Unable to create file file name.

Explanation: The server was attempting to create a file with the indicated name. The system reported an error in creating the file.

System Action: The server continues processing. The file creation request fails.

User Response: Specify a new file name.

ANR7864W (AIX)Unable to write volume file name.

Explanation: The server was attempting to create a file with the indicated name. The server was able to partially write to the file before running out of space.

System Action: The server continues processing. The file creation request fails. The file is still present on the system.

User Response: Specify a new file name where there is sufficient space.

ANR7864W (AS/400)Unable to write volume file name.

Explanation: ADSM was attempting to create a file with the indicated name. ADSM was able to partially write to the file before running out of space.

System Action: ADSM continues processing. The file creation request fails. The file is still present on the system.

User Response: Specify a new file name where there is sufficient space.

ANR7864W (HP-UX)Unable to write volume file name.

Explanation: The server was attempting to create a file with the indicated name. The server was able to partially write to the file before running out of space.

System Action: The server continues processing. The file creation request fails. The file is still present on the system.

User Response: Specify a new file name where there is sufficient space.

ANR7864W (Solaris)Unable to write volume file name.

Explanation: The server was attempting to create a file with the indicated name. The server was able to partially write to the file before running out of space.

System Action: The server continues processing. The file creation request fails. The file is still present on the system.

User Response: Specify a new file name where there is sufficient space.

ANR7865W (AIX)Unable to create volume file name. Return code=return code.

Explanation: The server was attempting to create a file with the indicated name. The attempt failed with the indicated return code. The return code is an the server internal code.

System Action: The server continues processing. The file creation request fails.

User Response: Specify a new file name. The return code may also be provided to your service representative for interpretation.

ANR7865W (AS/400)Unable to create volume file name. Return code=return code.

Explanation: ADSM was attempting to create a file with the indicated name. The attempt failed with the indicated return code. The return code is an ADSM internal code.

System Action: ADSM continues processing. The file creation request fails.

User Response: Specify a new file name. The return code may also be provided to IBM service for interpretation.

ANR7865W (HP-UX)Unable to create volume file name. Return code=return code.

Explanation: The server was attempting to create a file with the indicated name. The attempt failed with the indicated return code. The return code is a server internal code.

System Action: The server continues processing. The file creation request fails.

User Response: Specify a new file name. The return code may also be provided to your service representative for interpretation.

ANR7865W (Solaris)Unable to create volume file name. Return code=return code.

Explanation: The server was attempting to create a file with the indicated name. The attempt failed with the indicated return code. The return code is a server internal code.

System Action: The server continues processing. The file creation request fails.

User Response: Specify a new file name. The return code may also be provided to your service representative for interpretation.

ANR7866W (AIX)Creation of Volume file name failed. Process was cancelled.

Explanation: The server was attempting to create a file with the indicated name. The attempt was cancelled by a cancel process command.

System Action: The server continues processing. The file creation request fails.

User Response: The DEFINE command may be re-entered.

ANR7866W (AS/400)Creation of Volume file name failed. Process was cancelled.

Explanation: ADSM was attempting to create a file with the indicated name. The attempt was cancelled by a cancel process command.

System Action: ADSM continues processing. The file creation request fails.

User Response: The DEFINE command may be re-entered.

ANR7866W (HP-UX)Creation of Volume file name failed. Process was cancelled.

Explanation: The server was attempting to create a file with the indicated name. The attempt was cancelled by a cancel process command.

System Action: The server continues processing. The file creation request fails.

User Response: The DEFINE command may be re-entered.

ANR7866W (Solaris)Creation of Volume file name failed. Process was cancelled.

Explanation: The server was attempting to create a file with the indicated name. The attempt was cancelled by a cancel process command.

System Action: The server continues processing. The file creation request fails.

User Response: The DEFINE command may be re-entered.

ANR7867W (AS/400)Size of file file name exceeds maximum.

Explanation: ADSM was attempting to create a file with the indicated name. The size of the file exceeded the maximum allowed in the filesystem.

System Action: ADSM continues processing. The file creation request fails.

User Response: Specify a file size that is less than or equal to 2047MB.

ANR7870W (AIX)Unable to initialize odm query. Error message from odm is odm message.

Explanation: The server uses the AIX Object Data Manager (ODM) to check information about AIX. For example, the server uses ODM to detemine how much real memory is installed on the system. The routine used to initialize an ODM query failed. ODM returned an error message as indicated.

System Action: Server operation continues. The server makes assumptions concerning information it could not obtain.

User Response: The server may need to run as a root user to obtain this information.

ANR7871W (AIX)Unable to complete odm query. Error message from odm is odm message.

Explanation: The server uses the AIX Object Data Manager (ODM) to check information about AIX. For example, the server uses ODM to detemine how much real memory is installed on the system. The routine used to perform and ODM query failed. ODM returned an error message as indicated.

System Action: Server operation continues. The server makes assumptions concerning information it could not obtain.

User Response: The server may need to run as a root user to obtain this information.

ANR8190I (AIX)HTTP driver ready for connection with clients on port port number.

Explanation: The server is now able to accept sessions with clients that use the HTTP protocol on the indicated port number.

System Action: Server operation continues.

User Response: None.

ANR8190I (HP-UX)HTTP driver ready for connection with clients on port port number.

Explanation: The server is now able to accept sessions with clients that use the HTTP protocol on the indicated port number.

System Action: Server operation continues.

User Response: None.

ANR8190I (Solaris)HTTP driver ready for connection with clients on port port number.

Explanation: The server is now able to accept sessions with clients that use the HTTP protocol on the indicated port number.

System Action: Server operation continues.

User Response: None.

ANR8191W (AIX)HTTP driver unable to initialize due to error in BINDing to Port port, reason code reason code.

Explanation: While initializing HTTP communications, the server has failed to connect to a master TCP/IP socket on which to listen for clients. The reason code is the return code from the TCP/IP bind API.

System Action: Server operation continues, but the server cannot accept sessions from administrative clients using HTTP protocol.

User Response: Ensure that no other application is using the port number specified in the server options file with the PORT option. If TCP/IP is also in use for client sessions, ensure that the same port number is not specified for both TCP/IP and HTTP communications. This may be done by issuing the TCP/IP netstat -s command. If the server is brought down and then started immediately, you may be within the TCP/IP one minute timeout period for port reusage. Bring down the server, wait one minute, and then restart the server. If that does not work, it may be necessary to restart Windows NT.

ANR8191W (HP-UX)HTTP driver unable to initialize due to error in BINDing to Port port, reason code reason code.

Explanation: While initializing HTTP communications, the server has failed to connect to a master TCP/IP socket on which to listen for clients. The reason code is the return code from the TCP/IP bind API.

System Action: Server operation continues, but the server cannot accept sessions from administrative clients using HTTP protocol.

User Response: Ensure that no other application is using the port number specified in the server options file with the PORT option. If TCP/IP is also in use for client sessions, ensure that the same port number is not specified for both TCP/IP and HTTP communications. This may be done by issuing the TCP/IP netstat -s command. If the server is brought down and then started immediately, you may be within the TCP/IP one minute timeout period for port reusage. Bring down the sever, wait one minute, and then restart the server. If that does not work, it may be necessary to restart HP-UX.

ANR8191W (Solaris)HTTP driver unable to initialize due to error in BINDing to Port port, reason code reason code.

Explanation: While initializing HTTP communications, the server has failed to connect to a master TCP/IP socket on which to listen for clients. The reason code is the return code from the TCP/IP bind API.

System Action: Server operation continues, but the server cannot accept sessions from administrative clients using HTTP protocol.

User Response: Ensure that no other application is using the port number specified in the server options file with the PORT option. If TCP/IP is also in use for client sessions, ensure that the same port number is not specified for both TCP/IP and HTTP communications. This may be done by issuing the TCP/IP netstat -s command. If the server is brought down and then started immediately, you may be within the TCP/IP one minute timeout period for port reusage. Bring down the sever, wait one minute, and then restart the server.

ANR8192I (AIX)HTTPS driver ready for connection with clients on port port number.

Explanation: The server is now able to accept sessions with clients that use the HTTPS protocol on the indicated port number.

System Action: Server operation continues.

User Response: None.

ANR8192I (HP-UX)HTTPS driver ready for connection with clients on port port number.

Explanation: The server is now able to accept sessions with clients that use the HTTPS protocol on the indicated port number.

System Action: Server operation continues.

User Response: None.

ANR8192I (Solaris)HTTPS driver ready for connection with clients on port port number.

Explanation: The server is now able to accept sessions with clients that use the HTTPS protocol on the indicated port number.

System Action: Server operation continues.

User Response: None.

ANR8193W (AIX)HTTPS driver unable to initialize due to error in BINDing to Port port, reason code reason code.

Explanation: While initializing HTTPS communications, the server has failed to connect to a master TCP/IP socket on which to listen for clients. The reason code is the return code from the TCP/IP bind API.

System Action: Server operation continues, but the server cannot accept sessions from administrative clients using HTTPS protocol.

User Response: Ensure that no other application is using the port number specified in the server options file with the PORT option. If TCP/IP is also in use for client sessions, ensure that the same port number is not specified for both TCP/IP and HTTPS communications. This may be done by issuing the TCP/IP netstat -s command. If the server is brought down and then started immediately, you may be within the TCP/IP one minute timeout period for port reusage. Bring down the server, wait one minute, and then restart the server.

ANR8193W (HP-UX)HTTPS driver unable to initialize due to error in BINDing to Port port, reason code reason code.

Explanation: While initializing HTTPS communications, the server has failed to connect to a master TCP/IP socket on which to listen for clients. The reason code is the return code from the TCP/IP bind API.

System Action: Server operation continues, but the server cannot accept sessions from administrative clients using HTTPS protocol.

User Response: Ensure that no other application is using the port number specified in the server options file with the PORT option. If TCP/IP is also in use for client sessions, ensure that the same port number is not specified for both TCP/IP and HTTPS communications. This may be done by issuing the TCP/IP netstat -s command. If the server is brought down and then started immediately, you may be within the TCP/IP one minute timeout period for port reusage. Bring down the sever, wait one minute, and then restart the server. If that does not work, it may be necessary to restart HP-UX.

ANR8193W (Solaris)HTTPS driver unable to initialize due to error in BINDing to Port port, reason code reason code.

Explanation: While initializing HTTPS communications, the server has failed to connect to a master TCP/IP socket on which to listen for clients. The reason code is the return code from the TCP/IP bind API.

System Action: Server operation continues, but the server cannot accept sessions from administrative clients using HTTPS protocol.

User Response: Ensure that no other application is using the port number specified in the server options file with the PORT option. If TCP/IP is also in use for client sessions, ensure that the same port number is not specified for both TCP/IP and HTTPS communications. This may be done by issuing the TCP/IP netstat -s command. If the server is brought down and then started immediately, you may be within the TCP/IP one minute timeout period for port reusage. Bring down the sever, wait one minute, and then restart the server. If that does not work, it may be necessary to restart Solaris

ANR8194W (HP-UX)HTTPS driver unable to initialize due to error in secure data initialization, reason code reason code.

Explanation: While initializing HTTPS communications, the server has failed initialize of the secure data certificate information.

System Action: Server operation continues, but the server cannot accept sessions from administrative clients using HTTPS protocol.

User Response: Ensure the keyring file name and keyring file password are correct and that the password has not expired. Check for earlier SKIT messages which may indicate the real problem. Replace keyring if necessary and re-start the server.

ANR8200I (AIX)TCP/IP driver ready for connection with clients on port port number.

Explanation: The server is now able to accept sessions with clients that use the TCP/IP protocol on the indicated port number.

System Action: Server operation continues.

User Response: None.

ANR8200I (AS/400)TCP/IP driver is ready for connection with clients on port port number.

Explanation: The ADSM server can accept sessions with clients using the TCP/IP communication protocol on the indicated port number.

System Action: Server operation continues.

User Response: None.

ANR8200I (HP-UX)TCP/IP driver ready for connection with clients on port port number.

Explanation: The server is now able to accept sessions with clients using the TCP/IP protocol on the indicated port number.

System Action: Server operation continues.

User Response: None.

ANR8200I (Solaris)TCP/IP driver ready for connection with clients on port port number.

Explanation: The server is now able to accept sessions with clients using the TCP/IP protocol on the indicated port number.

System Action: Server operation continues.

User Response: None.

ANR8200I (Windows NT)TCP/IP driver ready for connection with clients on port port number.

Explanation: The server can now accept sessions with clients using the TCP/IP protocol on the indicated port number.

System Action: Server operation continues.

User Response: None.

ANR8201W (AIX)Unable to initialize TCP/IP driver - insufficient memory.

Explanation: Because the operating system rejects a memory allocation request, the server cannot start communications through TCP/IP.

System Action: Server operation continues, but the server cannot accept sessions from clients using the TCP/IP protocol.

User Response: Ensure that sufficient paging space is available for AIX. You may also use SMIT to determine if the number of applications is causing a memory shortage. It may be necessary to decrease the maximum number of client sessions by changing the MAXSESSIONS option in the server options file.

ANR8201W (AS/400)Unable to initialize TCP/IP driver - insufficient memory.

Explanation: The ADSM server cannot communicate by way of TCP/IP. A memory allocation request has been rejected by the operating system.

System Action: Server operation continues, but the server cannot accept sessions from clients using the TCP/IP communication protocol.

User Response: Contact your service representative.

ANR8201E (HP-UX)Unable to initialize TCP/IP driver - socket creation failed; error error code.

Explanation: The server is unable to initialize the TCP/IP driver due to a socket creation error.

System Action: Server operation continues, but TCP/IP support is inoperative.

User Response: Ensure that TCP/IP is operational on your system by using the ping command with your TCP/IP address as a target. If TCP/IP is not active on your system, you must activate it; then halt and restart the server.

ANR8201E (Solaris)Unable to initialize TCP/IP driver - socket creation failed; error error code.

Explanation: The server is unable to initialize the TCP/IP driver due to a socket creation error.

System Action: Server operation continues, but TCP/IP support is inoperative.

User Response: Ensure that TCP/IP is operational on your system by using the ping command with your TCP/IP address as a target. If TCP/IP is not active on your system, you must activate it; then halt and restart the server.

ANR8201W (Windows NT)Unable to initialize TCP/IP driver - insufficient memory.

Explanation: The server is unable to communicate by way of TCP/IP. A memory allocation request has been rejected by the operating system.

System Action: Server operation continues, but the server cannot accept sessions from clients using the TCP/IP protocol.

User Response: Ensure that there is sufficient space for the Windows NT paging file. Click on the system icon in the Windows NT control panel and then click on the virtual memory button. Refer to the online help for instructions on how to increase the amount of virtual memory.

ANR8202W (AIX)Unable to initialize TCP/IP driver - error creating acceptor socket. Reason code reason code.

Explanation: Because TCP/IP rejects a request for a socket on which to listen, the server cannot start communications through TCP/IP.

System Action: Server operation continues, but the server cannot accept sessions from clients using the TCP/IP protocol.

User Response: Ensure that TCP/IP is operational on your system by using the ping command with your TCP/IP address as a target. If TCP/IP is not started, use the HALT command from a server prompt to stop the server and restart it.

ANR8202W (AS/400)Unable to initialize TCP/IP driver - error creating acceptor socket.

Explanation: The ADSM server cannot communicate by way of TCP/IP. TCP/IP has rejected a request for a socket on which the server listens.

System Action: Server operation continues, but the server cannot accept sessions from clients using the TCP/IP communication protocol.

User Response: Ensure that TCP/IP is operational on your system by using the ping command with your TCP/IP address as a target. If TCP/IP is not started, issue the ADSM HALT command to stop the server, and then restart the server.

ANR8202E (HP-UX)Unable to initialize TCP/IP driver - socket bind operation for port TCP port number failed; error error code.

Explanation: The server is unable to initialize the TCP/IP driver due to a socket binding error.

System Action: Server operation continues, but TCP/IP support is inoperative.

User Response: Ensure that TCP/IP is operational on your system by using the ping command with your TCP/IP address as a target. If TCP/IP is not active on your system, you must activate it; then halt and restart the server. This message may also result from more than one server running on the same machine with the same TCP/IP port number. Make sure that the dsmserv.opt file TCPPort option is different for each server.

ANR8202E (Solaris)Unable to initialize TCP/IP driver - socket bind operation for port TCP port number failed; error error code.

Explanation: The server is unable to initialize the TCP/IP driver due to a socket binding error.

System Action: Server operation continues, but TCP/IP support is inoperative.

User Response: Ensure that TCP/IP is operational on your system by using the ping command with your TCP/IP address as a target. If TCP/IP is not active on your system, you must activate it; then halt and restart the server. This message may also result from more than one server running on the same machine with the same TCP/IP port number. Make sure that the dsmserv.opt file TCPPort option is different for each server.

ANR8202W (Windows NT)Unable to initialize TCP/IP driver - error creating acceptor socket.

Explanation: The server is unable to communicate by way of TCP/IP. TCP/IP has rejected a request for a socket on which the server listens.

System Action: Server operation continues, but the server cannot accept sessions from clients using the TCP/IP protocol.

User Response: Ensure that TCP/IP is operational on your system by using the ping command with your TCP/IP address as a target. If TCP/IP is not started, issue the HALT command to stop the server, and then restart the server.

ANR8203W (AIX)Unable to establish TCP connection - accept error.

Explanation: The server cannot accept a client session due to a failure in TCP/IP.

System Action: Server operation continues, but the server cannot accept sessions from clients using the TCP/IP protocol.

User Response: Ensure that TCP/IP is operational on your system by using the ping command with your TCP/IP address as a target. If TCP/IP is not started, use the HALT command from a server prompt to terminate the server and restart it.

ANR8203W (AS/400)TCP has run out of buffer space - server will retry when buffer space is available.

Explanation: The ADSM server cannot send data to clients because no buffer space is available in TCP/IP data buffer.

System Action: Server operation continues. The server continues to communicate with clients but performance is degraded.

User Response: Ensure that not too many TCP/IP sessions are running at the same time. Increasing TCP/IP data buffers can alleviate the problem.

ANR8203E (HP-UX)Unable to initialize TCP/IP driver - listen operation failed; error error code.

Explanation: The server is unable to initialize the TCP/IP driver due to a socket listen error.

System Action: Server operation continues, but TCP/IP support is inoperative.

User Response: Ensure that TCP/IP is operational on your system by using the ping command with your TCP/IP address as a target. If TCP/IP is not active on your system, you must activate it; then halt and restart the server.

ANR8203E (Solaris)Unable to initialize TCP/IP driver - listen operation failed; error error code.

Explanation: The server is unable to initialize the TCP/IP driver due to a socket listen error.

System Action: Server operation continues, but TCP/IP support is inoperative.

User Response: Ensure that TCP/IP is operational on your system by using the ping command with your TCP/IP address as a target. If TCP/IP is not active on your system, you must activate it; then halt and restart the server.

ANR8203W (Windows NT)Unable to establish TCP connection - accept error.

Explanation: The server cannot accept a client session due to failure in TCP/IP.

System Action: Server operation continues, but the server cannot accept sessions from clients using the TCP/IP protocol.

User Response: Ensure that TCP/IP is operational on your system by using the ping command with your TCP/IP address as a target. If TCP/IP is not started, issue the HALT command to stop the server, and then restart the server.

ANR8204W (AIX)Unable to establish TCP connection - insufficient memory.

Explanation: The server cannot accept a client session due to a memory allocation request failure.

System Action: Server operation continues, but the session request for this session fails.

User Response: Ensure that sufficient paging space is available for AIX. You may also use SMIT to determine if the number of applications is causing a memory shortage. You may also decrease the maximum number of sessions that the server can accept with the MAXSESSIONS option in the server options file.

ANR8204W (AS/400)Unable to establish TCP connection - insufficient memory.

Explanation: The ADSM server cannot accept a client session due to a memory allocation request failure.

System Action: Server operation continues, but the session request for this session fails.

User Response: Contact your service representative.

ANR8204E (HP-UX)Unable to initialize TCP/IP driver - thread creation failed.

Explanation: The server is unable to initialize the TCP/IP driver due to an error creating a server thread.

System Action: Server operation continues, but TCP/IP support is inoperative.

User Response: This error often results from a lack of memory. Ensure that your system has sufficient paging space to support the current activities.

ANR8204E (Solaris)Unable to initialize TCP/IP driver - thread creation failed.

Explanation: The server is unable to initialize the TCP/IP driver due to an error creating a server thread.

System Action: Server operation continues, but TCP/IP support is inoperative.

User Response: This error often results from a lack of memory. Ensure that your system has sufficient paging space to support the current activities.

ANR8204W (Windows NT)Unable to establish TCP connection - insufficient memory.

Explanation: The server is unable to accept a client session due to a memory allocation request failure.

System Action: Server operation continues, but the session request for this session fails.

User Response: Ensure that there is sufficient space for the Windows NT paging file. Click on the system icon in the Windows NT control panel and then click on the virtual memory button. Refer to the online help for instructions on how to increase the amount of virtual memory. You may also wish to cut down on the maximum number of sessions that the server can accept with the MAXSESSIONS option in the server options file.

ANR8205W (AIX)Unable to establish TCP connection - server HALT in progress.

Explanation: The server cannot accept a client session due to server HALT processing that is in progress.

System Action: Server operation continues, but the session request for this session fails.

User Response: None.

ANR8205W (AS/400)Unable to initialize TCP/IP driver - no TCP/IP service.

Explanation: The ADSM server cannot communicate by way of TCP/IP. No TCP/IP service exists.

System Action: Server operation continues, but the server cannot accept sessions from clients using the TCP/IP communication protocol.

User Response: Ensure that TCP/IP is properly installed on your system, and has been started on your system. Issue the TCP/IP ping command to your own address to verify that TCP/IP is installed and active.

ANR8205E (HP-UX)Terminating TCP/IP driver - accept operation failed; error error code.

Explanation: The server is unable to initialize the TCP/IP driver due to a socket accept error.

System Action: Server operation continues, but TCP/IP support is inoperative.

User Response: Ensure that TCP/IP is operational on your system by using the ping command with your TCP/IP address as a target. If TCP/IP is not active on your system, you must activate it; then halt and restart the server.

ANR8205E (Solaris)Terminating TCP/IP driver - socket accept operation failed; error error code.

Explanation: The server is unable to initialize the TCP/IP driver due to a socket accept error.

System Action: Server operation continues, but TCP/IP support is inoperative.

User Response: Ensure that TCP/IP is operational on your system by using the ping command with your TCP/IP address as a target. If TCP/IP is not active on your system, you must activate it; then halt and restart the server.

ANR8205W (Windows NT)Unable to establish TCP connection - server HALT in progress.

Explanation: The server is unable to accept a client session due to server HALT processing that is in progress.

System Action: Server operation continues, but the session request for this session fails.

User Response: None.

ANR8206W (AIX)Socket socket (session session number) closed abruptly.

Explanation: The server detects that the indicated session on the specified TCP/IP socket is closed outside of the server.

System Action: Server operation continues, but the session is ended.

User Response: None.

ANR8206W (AS/400)TCPIP is not available.

Explanation: QTCP is not in the liblist of job description QADSM. Refer to ADSM Installing Server and Admin Client for more information.

System Action: Server operation continues, but TCPIP is not available.

User Response: None.

ANR8206E (HP-UX)Unable to establish TCP/IP session - invalid host address IP host address (port port number).

Explanation: The server is unable to establish a session because the designated address or port number is not valid.

System Action: Server operation continues.

User Response: Ensure that the specified host name is valid and is accessible over the network. If the TCPCLIENTPort option is specified for the remote system, ensure it does not conflict with another application.

ANR8206E (Solaris)Unable to establish TCP/IP session - invalid host address IP host address (port port number).

Explanation: The server is unable to establish a session because the designated address or port number is not valid.

System Action: Server operation continues.

User Response: Ensure that the specified host name is valid and is accessible over the network. If the TCPCLIENTPort option is specified for the remote system, ensure it does not conflict with another application.

ANR8207W (AIX)TCP/IP driver unable to initialize due to socket initialization error.

Explanation: While initializing TCP/IP communications, the server fails to set up an interface with TCP/IP.

System Action: Server operation continues, but the server cannot accept sessions from clients using the TCP/IP protocol.

User Response: Ensure that TCP/IP has been started and is active on your system. You may issue the TCP/IP ping command to your own address to verify that TCP/IP is both started and active.

ANR8207W (AS/400)TCP/IP driver unable to initialize due to socket initialization error.

Explanation: While initializing TCP/IP communications, ADSM has failed to set up an interface with TCP/IP for AS/400.

System Action: Server operation continues, but the server cannot accept sessions from clients using the TCP/IP communication protocol.

User Response: Ensure that TCP/IP is properly installed on your system, and has been started on your system. Issue the TCP/IP ping command to your own address to verify that TCP/IP is both installed and active.

ANR8207E (HP-UX)Unable to establish TCP/IP session with IP host address due to memory shortage.

Explanation: The server is unable to establish a session because of a memory shortage condition.

System Action: Server operation continues.

User Response: Ensure that your system has sufficient paging space to support the current level of system activities.

ANR8207E (Solaris)Unable to establish TCP/IP session with IP host address due to memory shortage.

Explanation: The server is unable to establish a session because of a memory shortage condition.

System Action: Server operation continues.

User Response: Ensure that your system has sufficient paging space to support the current level of system activities.

ANR8207W (Windows NT)TCP/IP driver unable to initialize due to socket initialization error.

Explanation: While initializing TCP/IP communications, the server has failed to set up an interface with TCP/IP for Windows NT.

System Action: Server operation continues, but the server cannot accept sessions from clients using the TCP/IP protocol.

User Response: Ensure that TCP/IP is properly installed on your system. Ensure that TCP/IP has been started on your system. Issue the TCP/IP ping command to your own address to verify that TCP/IP is both installed and active.

ANR8208W (AIX)TCP/IP driver unable to initialize due to error in BINDing to Port port, reason code reason code.

Explanation: While initializing TCP/IP communications, the server fails to connect to a master socket on which to listen for clients. The reason code is the return code from the TCP/IP bind API.

System Action: Server operation continues, but the server cannot accept sessions from clients using the TCP/IP protocol.

User Response: Ensure that no other application is using the port number specified in the server options file with the PORT option by issuing the TCP/IP netstat command. If HTTP is also in use for client sessions, ensure that the same port number is not specified for both TCP/IP and HTTP communications. If the server was brought down and client sessions were active, it may be necessary to terminate the client sessions on the client systems before the port can be freed.

ANR8208W (AS/400)TCP/IP driver unable to initialize due to error in BINDing to Port port.

Explanation: While initializing TCP/IP communications, ADSM has failed to connect to a master socket on which to listen for clients.

System Action: Server operation continues, but the server cannot accept sessions from clients using the TCP/IP communication protocol.

User Response: Ensure that no other application is using the port number specified in the server options file with the PORT option. This may be done by issuing the TCP/IP NETSTAT command. If the server is halted and then restarted immediately, you may be within the TCP/IP one minute timeout period for port reusage. Halt the server, wait one minute, and then restart the server.

ANR8208E (HP-UX)Unable to establish TCP/IP session with IP host address - socket creation failed; error error code.

Explanation: The server is unable to establish a session because of a socket creation error.

System Action: Server operation continues.

User Response: Ensure that TCP/IP is operational on your system by using the ping command with your TCP/IP address as a target. If TCP/IP is not active on your system, you must activate it; then halt and restart the server.

ANR8208E (Solaris)Unable to establish TCP/IP session with IP host address - socket creation failed; error error code.

Explanation: The server is unable to establish a session because of a socket creation error.

System Action: Server operation continues.

User Response: Ensure that TCP/IP is operational on your system by using the ping command with your TCP/IP address as a target. If TCP/IP is not active on your system, you must activate it; then halt and restart the server.

ANR8208W (Windows NT)TCP/IP driver unable to initialize due to error in BINDing to Port port, reason code reason code.

Explanation: While initializing TCP/IP communications, the server has failed to connect to a master socket on which to listen for clients. The reason code is the return code from the TCP/IP bind API.

System Action: Server operation continues, but the server cannot accept sessions from clients using the TCP/IP protocol.

User Response: Ensure that no other application is using the port number specified in the server options file with the PORT option. If HTTP is also in use for client sessions, ensure that the same port number is not specified for both TCP/IP and HTTP communications. This may be done by issuing the TCP/IP netstat -s command. If the server is brought down and then started immediately, you may be within the TCP/IP one minute timeout period for port reusage. Bring down the server, wait one minute, and then restart the server. If that does not work, it may be necessary to restart Windows NT.

ANR8209W (AIX)TCP/IP driver unable to initialize due to error in LISTENing on the specified Port, reason code reason code.

Explanation: While attempting to listen for session requests from clients using TCP/IP, TCP/IP returns an error. The reason code is the return code from the TCP/IP listen API.

System Action: Server operation continues, but the server cannot accept additional sessions from clients using the TCP/IP protocol.

User Response: Ensure that TCP/IP is running properly by issuing the TCP/IP netstat -s and ping commands to other nodes on your network. It may be possible to bring the server down and restart it to allow additional client sessions to start.

ANR8209W (AS/400)TCP/IP driver unable to initialize due to error in LISTENing on the specified Port.

Explanation: While attempting to listen for session requests from clients using TCP/IP, TCP/IP returns an error.

System Action: Server operation continues, but the server cannot accept additional sessions from clients using the TCP/IP communication protocol.

User Response: Ensure that TCP/IP is running properly. This may be done by issuing the TCP/IP NETSTAT and ping commands to other nodes on your network. It may be possible to correct this condition by restarting the server.

ANR8209E (HP-UX)Unable to establish TCP/IP session with IP host address - connection refused.

Explanation: The server is unable to establish a session because the remote system refused the connection request.

System Action: Server operation continues.

User Response: Ensure that the specified remote system is operational and is properly configured to run TCP/IP. Ensure that the client options file specifies the correct TCPServeraddress and TCPPort of the server you are attempting to contact.

ANR8209E (Solaris)Unable to establish TCP/IP session with IP host address - connection refused.

Explanation: The server is unable to establish a session because the remote system refused the connection request.

System Action: Server operation continues.

User Response: Ensure that the specified remote system is operational and is properly configured to run TCP/IP. Ensure that the client options file specifies the correct TCPServeraddress and TCPPort of the server you are attempting to contact.

ANR8209W (Windows NT)TCP/IP driver unable to initialize due to error in LISTENing on the specified Port, reason code reason code.

Explanation: While attempting to listen for session requests from clients using TCP/IP, TCP/IP returns an error. The reason code is the return code from the TCP/IP listen API.

System Action: Server operation continues, but the server cannot accept additional sessions from clients using the TCP/IP protocol.

User Response: Ensure that TCP/IP is running properly. This may be done by issuing the TCP/IP netstat -s and ping commands to other nodes on your network. It may be possible to correct this condition by restarting the server.

ANR8210W (AIX)TCP/IP driver is terminating due to error in accepting a new session, reason code reason code.

Explanation: While attempting to accept a session request from a client using TCP/IP, TCP/IP returns an error. The reason code is the return code from the TCP/IP accept API.

System Action: Server operation continues, but the server cannot accept additional sessions from clients using the TCP/IP protocol.

User Response: Ensure that TCP/IP is running properly. This may be done by issuing the TCP/IP netstat -s and ping commands to other nodes on your network. It may be possible to bring the server down and restart it to allow additional client sessions to start.

ANR8210W (AS/400)TCP/IP driver is terminating due to error in accepting a new session.

Explanation: While attempting to accept a session request from a client using TCP/IP, TCP/IP returns an error.

System Action: Server operation continues, but the server cannot accept additional sessions from clients using the TCP/IP communication protocol.

User Response: Ensure that TCP/IP is running properly. It may be possible to halt the server and start it again to allow additional client sessions to start.

ANR8210E (HP-UX)Unable to establish TCP/IP session with IP host address - connection request timed out.

Explanation: The server is unable to establish a session because the remote system did not respond to the connection request.

System Action: Server operation continues.

User Response: Ensure the following:

ANR8210E (Solaris)Unable to establish TCP/IP session with IP host address - connection request timed out.

Explanation: The server is unable to establish a session because the remote system did not respond to the connection request.

System Action: Server operation continues.

User Response: Ensure the following:

ANR8210W (Windows NT)TCP/IP driver is terminating due to error in accepting a new session, reason code reason code.

Explanation: While attempting to accept a session request from a client using TCP/IP, TCP/IP returns an error. The reason code is the return code from the TCP/IP accept API.

System Action: Server operation continues, but the server cannot accept additional sessions from clients using the TCP/IP protocol.

User Response: Ensure that TCP/IP is running properly. This may be done by issuing the TCP/IP netstat -s and ping commands to other nodes on your network. It may be possible to bring the server down and restart it to allow additional client sessions to start.

ANR8211W (AIX)TCP/IP driver is terminating due to error in creating a new thread.

Explanation: The server cannot initialize due to the inability to create a new thread of execution.

System Action: Server operation continues, but TCP/IP communications is inoperative.

User Response: The most likely cause is a lack of memory. Ensure that sufficient paging space is available for AIX. You may also use SMIT to determine if the number of applications is causing a memory shortage. You may also decrease the maximum number of sessions that the server can accept with the MAXSESSIONS option in the server options file.

ANR8211W (AS/400)An error occurs and the TCP/IP driver is not available.

Explanation: The ADSM server cannot initialize the TCP/IP driver.

System Action: Server operation continues, but TCP/IP communications is not available.

User Response: Contact your service representative.

ANR8211E (HP-UX)Unable to establish TCP/IP session with IP host address - system/network unreachable.

Explanation: The server is unable to establish a session because the remote system or network is unreachable.

System Action: Server operation continues.

User Response: Ensure that the specified remote system is operational and is properly configured to run TCP/IP. Also, ensure that necessary gateways and routers are functioning properly.

ANR8211E (Solaris)Unable to establish TCP/IP session with IP host address - system/network unreachable.

Explanation: The server is unable to establish a session because the remote system or network is unreachable.

System Action: Server operation continues.

User Response: Ensure that the specified remote system is operational and is properly configured to run TCP/IP. Also, ensure that necessary gateways and routers are functioning properly.

ANR8211W (Windows NT)TCP/IP driver is terminating due to error in creating a new thread.

Explanation: The server cannot initialize due its inability to create a new thread of execution.

System Action: Server operation continues, but TCP/IP communications is inoperative.

User Response: The most likely cause is a lack of memory. Ensure that there is sufficient space for the Windows NT paging file. Click on the system icon in the Windows NT control panel and then click on the virtual memory button. Refer to the online help for instructions on how to increase the amount of virtual memory. You may also wish to cut down on the maximum number of sessions that the server can accept with the MAXSESSIONS option in the server options file.

ANR8212W (AIX)Unable to resolve address for node name.

Explanation: The server attempts to obtain a TCP/IP address for the indicated node name. The attempt is unsuccessful.

System Action: The attempt to communicate with the indicated node fails. Server operation continues.

User Response: Ensure that the node name is properly specified and that it is accessible over the network. Use the TCP/IP ping command for this purpose.

ANR8212W (AS/400)Unable to resolve TCP/IP address for node name.

Explanation: The ADSM server attempts to obtain a TCP/IP address for the indicated node name. The attempt is unsuccessful.

System Action: The attempt to communicate with the indicated node fails. Server operation continues.

User Response: Ensure that the node name is properly specified and that it is accessible over the network. Use the TCP/IP ping command for this purpose.

ANR8212E (HP-UX)Unable to establish TCP/IP session with IP host address - connect failed; error error code.

Explanation: The server is unable to establish a session because of a connection error.

System Action: Server operation continues.

User Response: Ensure that the specified remote system is operational and is properly configured to run TCP/IP.

ANR8212E (Solaris)Unable to establish TCP/IP session with IP host address - connect failed; error error code.

Explanation: The server is unable to establish a session because of a connection error.

System Action: Server operation continues.

User Response: Ensure that the specified remote system is operational and is properly configured to run TCP/IP.

ANR8212W (Windows NT)Unable to resolve address for node name.

Explanation: The server attempts to obtain a TCP/IP address for the indicated node name. The attempt is unsuccessful.

System Action: The attempt to communicate with the indicated node fails. Server operation continues.

User Response: Ensure that the node name is properly specified and that it is accessible over the network. Use the TCP/IP ping command for this purpose.

ANR8213W (AIX)Session open with node name timed out.

Explanation: The server attempts to contact the indicated node name. The attempt is unsuccessful.

System Action: The attempt to communicate with the indicated node fails.

User Response: Ensure that the node name is properly specified and that it is accessible over the network. Use the TCP/IP ping command for this purpose.

ANR8213W (AS/400)Session open with node name timed out.

Explanation: The ADSM server attempts to contact the indicated node name. The attempt is unsuccessful.

System Action: The attempt to communicate with the indicated node fails.

User Response: Ensure that the node name is properly specified and that it is accessible over the network by using the TCP/IP ping command.

ANR8213E (HP-UX)Session Session identifier aborted due to send error; error error code.

Explanation: The session between the server and the specified client system experienced a disruptive error sending data.

System Action: The session with the remote system is ended.

User Response: Ensure that the specified remote system is operational and is properly configured to run TCP/IP.

ANR8213E (Solaris)Session Session identifier aborted due to send error; error error code.

Explanation: The session between the server and the specified client system experienced a fatal error sending data.

System Action: The session with the remote system is ended.

User Response: Ensure that the specified remote system is operational and is properly configured to run TCP/IP.

ANR8213W (Windows NT)Session open with node name timed out.

Explanation: The server attempts to contact the indicated node name. The attempt is unsuccessful.

System Action: The attempt to communicate with the indicated node fails.

User Response: Ensure that the node name is properly specified and that it is accessible over the network. Use the TCP/IP ping command for this purpose.

ANR8214E (AIX)Session open with IP host address failed due to connection refusal.

Explanation: The server is unable to establish a session because the remote system refused the connection request.

System Action: Server operation continues.

User Response: Ensure that the specified remote system is operational and is properly configured to run TCP/IP. Ensure that the client options file specifies the correct TCPServeraddress and TCPPort of the server you are attempting to contact.

ANR8214E (AS/400)Session open with IP host address failed due to connection refusal.

Explanation: The ADSM server is unable to establish a session because the remote system refused the connection request.

System Action: Server operation continues.

User Response: Ensure that the specified remote system is operational and is properly configured to run TCP/IP. Ensure that the client options file specifies the correct TCPServeraddress and TCPPort of the server you are attempting to contact.

ANR8214E (HP-UX)Session Session identifier aborted due to zero-length message.

Explanation: The session between the server and the specified client system experienced a disruptive error receiving data.

System Action: The session with the remote system is ended.

User Response: Ensure that the specified remote system is operational and is properly configured to run TCP/IP.

ANR8214E (Solaris)Session Session identifier aborted due to zero-length message.

Explanation: The session between the server and the specified client system experienced a fatal error receiving data.

System Action: The session with the remote system is ended.

User Response: Ensure that the specified remote system is operational and is properly configured to run TCP/IP.

ANR8214E (Windows NT)Session open with IP host address failed due to connection refusal.

Explanation: The server is unable to establish a session because the remote system refused the connection request.

System Action: Server operation continues.

User Response: Ensure that the specified remote system is operational and is properly configured to run TCP/IP. Ensure that the client options file specifies the correct TCPServeraddress and TCPPort of the server you are attempting to contact.

ANR8215W (AIX)Session open with IP host address failed as unreachable.

Explanation: The server is unable to establish a session because the remote system is unreachable.

System Action: Server operation continues.

User Response: Ensure that the IP host address is properly specified and that it is accessible over the network. Use the TCP/IP ping command for this purpose.

ANR8215W (AS/400)Session open with IP host address failed as unreachable.

Explanation: The ADSM server is unable to establish a session because the remote system is unreachable.

System Action: Server operation continues.

User Response: Ensure that the IP host address is properly specified and that it is accessible over the network. Use the TCP/IP ping command for this purpose.

ANR8215E (HP-UX)Session Session identifier aborted due to receive error; error error code.

Explanation: The session between the server and the specified client system experienced a disruptive error receiving data.

System Action: The session with the remote system is ended.

User Response: Ensure that the specified remote system is operational and is properly configured to run TCP/IP.

ANR8215E (Solaris)Session Session identifier aborted due to receive error; error error code.

Explanation: The session between the server and the specified client system experienced a fatal error receiving data.

System Action: The session with the remote system is ended.

User Response: Ensure that the specified remote system is operational and is properly configured to run TCP/IP.

ANR8215W (Windows NT)Session open with IP host address failed as unreachable.

Explanation: The server is unable to establish a session because the remote system is unreachable.

System Action: Server operation continues.

User Response: Ensure that the IP host address is properly specified and that it is accessible over the network. Use the TCP/IP ping command for this purpose.

ANR8216W (AIX)Error sending data on socket socket number. Reason return code.

Explanation: The server experiences an error return code from TCP/IP while sending data over the indicated socket. This may be a normal event if either side of the connection is abruptly ended.

System Action: The session is ended. Server operation continues.

User Response: If the session is ended as a result of intentionally stopping either the client or server, no response is required. Otherwise, ensure that the client and server can communicate through such means as Telnet or FTP applications, which are part of the TCP/IP suite.

ANR8216W (AS/400)Error sending data on socket socket number.

Explanation: The ADSM server experiences an error return code from TCP/IP while sending data over the indicated socket. This may be a normal event if either side of the connection is abruptly ended by the client or server.

System Action: The session is ended. Server operation continues.

User Response: If the session is ended as a result of intentionally stopping either the client or the server, no response is required. Otherwise, ensure that the client and the server can communicate through such means as Telnet or FTP applications, which are part of the TCP/IP suite.

ANR8216E (HP-UX)Unable to establish TCP/IP session with IP host address due to thread creation error.

Explanation: The server is unable to establish a session because of an error creating a thread.

System Action: Server operation continues.

User Response: Ensure that your system has sufficient paging space to support the current level of system activities.

ANR8216E (Solaris)Unable to establish TCP/IP session with IP host address due to thread creation error.

Explanation: The server is unable to establish a session because of an error creating a thread.

System Action: Server operation continues.

User Response: Ensure that your system has sufficient paging space to support the current level of system activities.

ANR8216W (Windows NT)Error sending data on socket socket number. Reason return code.

Explanation: The server experiences an error return code from TCP/IP while sending data over the indicated socket. This may be a normal event if either side of the connection is abruptly ended.

System Action: The session is ended. Server operation continues.

User Response: If the session is ended as a result of intentionally stopping either the client or server, no response is required. Otherwise, ensure that the client and server can communicate through such means as Telnet or FTP applications, which are part of the TCP/IP suite.

ANR8217W (AIX)Error receiving data on socket socket number. Reason return code.

Explanation: The server experiences an error return code from TCP/IP while receiving data on the indicated socket. This may be a normal event if either side of the connection is abruptly ended.

System Action: The session is ended. Server operation continues.

User Response: If the session is ended as a result of intentionally stopping either the client or server, no response is required. Otherwise, ensure that the client and server can communicate through such means as Telnet or FTP applications, which are part of the TCP/IP suite.

ANR8217W (AS/400)Error receiving data on socket socket number.

Explanation: The ADSM server experiences an error return code from TCP/IP while receiving data on the indicated socket. This may be a normal event if either side of the connection is abruptly ended by the client or server.

System Action: The session is ended. Server operation continues.

User Response: If the session is ended as a result of intentionally stopping either the client or the server, no response is required. Otherwise, ensure that the client and the server can communicate through such means as Telnet or FTP applications, which are part of the TCP/IP suite.

ANR8217W (HP-UX)TCP/IP driver is unable to set the window size to TCPWindowsize for client client. The default value will be used.

Explanation: The server cannot set the window size for the indicated client to the requested size shown. The server uses the default window size for the indicated session. There may be a lack of memory for TCP/IP buffers.

System Action: Server operation continues and the session continues with the default window size.

User Response: Retry the session with a smaller window size in the options file. Issue the QUERY OPTION command to determine the setting of the server TCPWindowsize.

ANR8217W (Solaris)Unable to initialize TCP/IP driver - insufficient memory.

Explanation: Because the operating system rejects a memory allocation request, the server cannot start communications through TCP/IP.

System Action: Server operation continues, but the server cannot accept sessions from clients using the TCP/IP protocol.

User Response: Ensure that sufficient paging space is available for Solaris. You may also use ps -ef to determine if the number of applications is causing a memory shortage. It may be necessary to decrease the maximum number of client sessions by changing the MAXSESSIONS option in the server options file.

ANR8217W (Windows NT)Error receiving data on socket socket number. Reason return code.

Explanation: The server experiences an error return code from TCP/IP while receiving data on the indicated socket. This may be a normal event if either side of the connection is abruptly ended.

System Action: The session is ended. Server operation continues.

User Response: If the session is ended as a result of intentionally stopping either the client or server, no response is required. Otherwise, ensure that the client and server can communicate through such means as Telnet or FTP applications, which are part of the TCP/IP suite.

ANR8218W (AIX)Session terminated when no data was read on socket socket number.

Explanation: The server is unable to read data on the indicated socket. This may be a normal event if either side of the connection is abruptly ended.

System Action: The session is ended. Server operation continues.

User Response: If the session is ended as a result of intentionally stopping either the client or server, no response is required. Otherwise, ensure that the client and server can communicate through such means as Telnet or FTP applications, which are part of the TCP/IP suite.

ANR8218W (AS/400)Session terminated when no data read on socket socket number.

Explanation: The ADSM server cannot read on the indicated socket. This may be a normal event if either side of the connection is abruptly ended by the client or server.

System Action: The session is ended. Server operation continues.

User Response: If the session is ended as a result of intentionally stopping either the client or the server, no response is required. Otherwise, ensure that the client and the server can communicate through such means as Telnet or FTP applications, which are part of the TCP/IP suite.

ANR8218W (HP-UX)TCP/IP driver is unable to use the TCP/IP NODELAY option for client client.

Explanation: The server cannot set TCP/IP NODELAY for the indicated client. The session proceeds with TCP/IP Delay processing in effect. This causes TCP/IP to buffer data prior to sending it to clients.

System Action: Server operation continues and the session continues with the delay processing on.

User Response: Further details for use in contacting your service representative can be obtained by issuing the following trace commands from an admin session or from the server console (proper administrative authority is required): TRACE ENABLE TCPINFO TRACE BEGIN tcptrace.out. After a session starts and gets message ANR8218W, issue the following commands: TRACE FLUSH TRACE END. This will create trace data in file tcptrace.out and will terminate the trace. This file should be supplied to your server representative on request.

ANR8218W (Solaris)Unable to resolve address for node name.

Explanation: The server attempts to obtain a TCP/IP address for the indicated node name. The attempt is unsuccessful.

System Action: The attempt to communicate with the indicated node fails. Server operation continues.

User Response: Ensure that the node name is properly specified and that it is accessible over the network. Use the TCP/IP ping command for this purpose.

ANR8218W (Windows NT)Session terminated when no data read on socket socket number.

Explanation: The server cannot read on the indicated socket. This may be a normal event if either side of the connection is abruptly ended.

System Action: The session is ended. Server operation continues.

User Response: If the session is ended as a result of intentionally stopping either the client or server, no response is required. Otherwise, ensure that the client and server can communicate through such means as Telnet or FTP applications, which are part of the TCP/IP suite.

ANR8219W (AIX)TCP/IP driver is unable to accept a new session with client at address TCP/IP address due to an error in creating a new thread.

Explanation: The server cannot accept a client session with the client at the indicated address due to an inability to create a new thread.

System Action: Server operation continues, the session request fails.

User Response: The most likely cause is lack of memory. Ensure that sufficient paging space is available for AIX. You may also use SMIT to determine if the number of applications is causing a memory shortage. You may also decrease the maximum number of sessions that the server can accept with the MAXSESSIONS option in the server options file.

ANR8219W (AS/400)An error occurs and the TCP/IP driver is unable to accept a new session.

Explanation: The ADSM server cannot accept a client session.

System Action: Server operation continues, and the session request fails.

User Response: Contact your service representative.

ANR8219W (HP-UX)Unable to initialize TCP/IP driver - insufficient memory.

Explanation: Because the operating system rejects a memory allocation request, the server cannot start communications through TCP/IP.

System Action: Server operation continues, but the server cannot accept sessions from clients using the TCP/IP protocol.

User Response: Ensure that sufficient paging space is available for HP-UX. You may also use SMIT to determine if the number of applications is causing a memory shortage. It may be necessary to decrease the maximum number of client sessions by changing the MAXSESSIONS option in the server options file.

ANR8219W (Solaris)Unable to establish TCP connection - insufficient memory.

Explanation: The server cannot accept a client session due to a memory allocation request failure.

System Action: Server operation continues, but the session request for this session fails.

User Response: Ensure that sufficient paging space is available for Solaris. You may also use 'swap -l' to determine the amount of swap available. You may also decrease the maximum number of sessions that the server can accept with the MAXSESSIONS option in the server options file.

ANR8219W (Windows NT)TCP/IP driver is unable to accept a new session due to error in creating a new thread.

Explanation: The server cannot accept a client session due to the inability to create a new thread.

System Action: Server operation continues, the session request fails.

User Response: The most likely cause is a lack of memory. Ensure that there is sufficient space for the Windows NT paging file. Click on the system icon in the Windows NT control panel and then click on the virtual memory button. Refer to the online help for instructions on how to increase the amount of virtual memory. You may also wish to to cut down on the maximum number of sessions that the server can accept with the MAXSESSIONS option in the server options file.

ANR8220W (AIX)TCP/IP driver is unable to set the window size to TCPWindowsize for client client. The default value will be used.

Explanation: The server cannot set the window size for the indicated client to the requested size shown. The server uses the default window size for the indicated session. There may be a lack of memory for TCP/IP buffers.

System Action: Server operation continues and the session continues with the default window size.

User Response: Retry the session with a smaller window size in the options file. Issue the QUERY OPTION command to determine the setting of the server TCPWindowsize.

ANR8220W (AS/400)TCP/IP driver is unable to contact node name.

Explanation: The ADSM server attempts to contact the indicated node name. The attempt is unsuccessful due to the inability to initialize a local socket.

System Action: The attempt to communicate with the indicated node fails.

User Response: Ensure that TCP/IP is operating properly on this node and that it can communicate remotely. Use the TCP/IP ping command for this purpose.

ANR8220W (HP-UX)Unable to establish TCP connection - insufficient memory.

Explanation: The server cannot accept a client session due to a memory allocation request failure.

System Action: Server operation continues, but the session request for this session fails.

User Response: Ensure that sufficient paging space is available for HP-UX. You may also use SMIT to determine if the number of applications is causing a memory shortage. You may also decrease the maximum number of sessions that the server can accept with the MAXSESSIONS option in the server options file.

ANR8220W (Solaris)TCP/IP driver is unable to set the window size to TCPWindowsize for client client. The default value will be used.

Explanation: The server cannot set the window size for the indicated client to the requested size shown. The server uses the default window size for the indicated session. There may be a lack of memory for TCP/IP buffers.

System Action: Server operation continues and the session continues with the default window size.

User Response: Retry the session with a smaller window size in the options file. Issue the QUERY OPTION command to determine the setting of the server TCPWindowsize.

ANR8220W (Windows NT)TCP/IP driver is unable to contact node name due to an output socket initialization error.

Explanation: The server attempts to contact the indicated node name. The attempt is unsuccessful due to the inability to initialize a local socket.

System Action: The attempt to communicate with the indicated node fails.

User Response: Ensure that TCP/IP is operating properly on this node and that it can communicate remotely. Use the TCP/IP ping command for this purpose.

ANR8221W (AIX)TCP/IP driver is unable to use the TCP/IP NODELAY option for client client.

Explanation: The server cannot set TCP/IP NODELAY for the indicated client. The session proceeds with TCP/IP Delay processing in effect. This causes TCP/IP to buffer data prior to sending it to clients.

System Action: Server operation continues and the session continues with the delay processing on.

User Response: Further details for use in contacting your service representative can be obtained by issuing the following trace commands from an admin session or from the server console (proper administrative authority is required): TRACE ENABLE TCPINFO TRACE BEGIN. After a session starts and gets message ANR8221W, issue the commands TRACE FLUSH TRACE END. This will create trace data in file tcptrace.out and will terminate the trace. This file should be supplied to your service representative on request.

ANR8221W (AS/400)Unable to initialize TCP/IP driver - TCP/IP is not activated.

Explanation: The ADSM server cannot communicate by way of TCP/IP. TCP/IP is not activated.

System Action: Server operation continues, but the server cannot accept sessions from clients using the TCP/IP communication protocol.

User Response: Ensure that TCP/IP is properly installed on your system, and has been started. Issue the TCP/IP ping command to your own address to verify that TCP/IP is installed and active.

ANR8221W (Solaris)TCP/IP driver is unable to use the TCP/IP NODELAY option for client client.

Explanation: The server cannot set TCP/IP NODELAY for the indicated client. The session proceeds with TCP/IP Delay processing in effect. This causes TCP/IP to buffer data prior to sending it to clients.

System Action: Server operation continues and the session continues with the delay processing on.

User Response: Further details for use in contacting your service representative can be obtained by issuing the following trace commands from an admin session or from the server console (proper administrative authority is required): TRACE ENABLE TCPINFO TRACE BEGIN tcptrace.out After a session starts and gets message ANR8221W, issue the following commands: TRACE FLUSH TRACE END This will create trace data in file tcptrace.out and will terminate the trace. This file should be supplied to your service representative on request.

ANR8221W (Windows NT)TCP/IP driver is unable to set the window size to TCPWindowsize for session session, client client. The default value will be used.

Explanation: The server cannot set the window size for the indicated session/client to the requested size shown. The server will use the default window size for the indicated session.

System Action: Server operation continues and the session continues with the default window size.

User Response: The most likely cause is lack of memory for TCP/IP buffers. You may retry with a smaller TCP window size in the options file. You can issue the QUERY OPTION command to display the current setting of the TCP window size.

ANR8222W (AIX)TCP/IP driver is unable to set the window size to TCPWindowsize for the server master socket. The default value will be used.

Explanation: The server cannot set the window size for the socket on which the server listens to the requested size shown. The server uses the default window size for listening for sessions. There may be a lack of memory for TCP/IP buffers.

System Action: Server operation continues with the default window size.

User Response: Restart the server with a smaller window size in the options file if necessary. Issue the QUERY OPTION command to determine the setting of the server TCPWindowsize.

ANR8222W (AS/400)Failure reason is given in spool file QSYSPRT.

Explanation: The ADSM server cannot communicate by way of TCP/IP. TCP/IP is not activated.

System Action: Server operation continues, but the server cannot accept sessions from clients using the TCP/IP communication protocol.

User Response: A spool file QSYSPRT provides the reason.

ANR8222W (Solaris)Unable to establish TCP connection - server HALT in progress.

Explanation: The server cannot accept a client session due to server HALT processing that is in progress.

System Action: Server operation continues, but the session request for this session fails.

User Response: None.

ANR8222W (Windows NT)TCP/IP driver is unable to use the TCP/IP NODELAY option for client client.

Explanation: The server cannot set TCP/IP NODELAY for the indicated client. The session proceeds with TCP/IP Delay processing in effect. This causes TCP/IP to buffer data prior to sending it to clients.

System Action: Server operation continues and the session continues with the delay processing on.

User Response: Further details for use in contacting your service representative can be obtained by issuing the following trace commands from an admin session or from the server console (proper administrative authority is required): TRACE ENABLE TCPINFO TRACE BEGIN tcptrace.out After a session starts and gets message ANR8222W, issue the following commands: TRACE FLUSH TRACE END This will create trace data in file tcptrace.out and will terminate the trace. This file should be supplied to your service representative on request.

ANR8223W (AIX)Unable to connect to remote system RemoteSystem due to unexpected return code ReturnCode

Explanation: The server was unable to connect to a remote system due to an unexpected return code from the connect Application Programming Interface. Common return code are handled with specific messages. This return code was unexpected.

System Action: Server operation continues but the connection to the remote system fails.

User Response: TCP/IP return code are listed in file /usr/include/sys/errno.h and may provide a pointer to the underlying problem. /usr/include/sys/errno.h is part of fileset bos.adt.include.

ANR8223I (AS/400)IPX available at address server address and port port number.

Explanation: The ADSM server can accept sessions with clients using the IPX communication protocol on the indicated port number and specified server address.

System Action: Server operation continues.

User Response: None.

ANR8223W (Solaris)TCP/IP driver is unable to accept a new session with client at address TCP/IP address due to an error in creating a new thread.

Explanation: The server cannot accept a client session with the client at the indicated address due to an inability to create a new thread.

System Action: Server operation continues, the session request fails.

User Response: The most likely cause is lack of memory. Ensure that sufficient paging space is available for Solaris. You may also use ps -ef to determine if the number of applications is causing a memory shortage. You may also decrease the maximum number of sessions that the server can accept with the MAXSESSIONS option in the server options file.

ANR8223W (Windows NT)Failed to connect to system at address address port port.

Explanation: The server attempted to contact the indicated node name at the specified port. The attempt is unsuccessful. The target port is not valid at the target node.

System Action: The attempt to communicate with the indicated node fails. Server operation continues.

User Response: Ensure that the node name still has TCP/IP running and that the client is active in SCHEDULE mode. If the server is attempting contact with the SNMP subagent, ensure that the hostname and port number for the subagent is correct in the server options file.

ANR8224W (AS/400)Unable to initialize IPX driver - error creating acceptor socket.

Explanation: The ADSM server cannot communicate by way of IPX. IPX has rejected a request for a socket on which the server listens.

System Action: Server operation continues, but the server cannot accept sessions from clients using the IPX communication protocol.

User Response: Ensure that IPX is operational on your system. If IPX is not started, issue the ADSM HALT command to stop the server, and then restart the server after IPX has been started.

ANR8224W (Solaris)TCP/IP driver is unable to set the window size to TCPWindowsize for the server master socket. The default value will be used.

Explanation: The server cannot set the window size for the socket on which the server listens to the requested size shown. The server uses the default window size for listening for sessions. There may be a lack of memory for TCP/IP buffers.

System Action: Server operation continues with the default window size.

User Response: Restart the server with a smaller window size in the options file if necessary. Issue the QUERY OPTION command to determine the setting of the server TCPWindowsize.

ANR8225I (AIX)NETBIOS driver ready for connection with clients on adapter network adapter number.

Explanation: The server is now able to accept sessions with clients using the NETBIOS protocol.

System Action: Server operation continues.

User Response: None.

ANR8225W (AS/400)Unable to establish IPX connection - insufficient memory.

Explanation: The ADSM server cannot accept a client session due to a memory allocation request failure.

System Action: Server operation continues, but the session request for this session fails.

User Response: Contact your service representative.

ANR8225I (Windows NT)NETBIOS driver ready for connection with clients on adapter network adapter number.

Explanation: The server is now able to accept sessions with clients using the NETBIOS protocol on the indicated network adapter.

System Action: Server operation continues.

User Response: None.

ANR8226W (AS/400)IPX driver unable to initialize due to error in BINDing to Port port.

Explanation: While initializing IPX communications, ADSM has failed to connect to a master socket on which to listen for clients.

System Action: Server operation continues, but the server cannot accept sessions from clients using the IPX communication protocol.

User Response: Ensure that no other application is using the port number specified in the server options file with the PORT option. If the server is halted and then restarted immediately, you may be within the IPX one minute timeout period for port reusage. Halt the server, wait one minute, and then restart the server.

ANR8226W (Windows NT)Unable to initialize NETBIOS driver on adapter network adapter number.

Explanation: The server cannot obtain sufficient NETBIOS resources to initialize communications on the indicated network adapter.

System Action: Server operation continues, but the server will not accept sessions from clients that use the NETBIOS protocol.

User Response: Ensure that NETBIOS is configured on the system. Ensure that all NETBIOS resources are not already in use. If the LAN Server or LAN Requester application is running, you have NETBIOS configured. In that case, starting the server prior to starting LAN Server or LAN Requester may allow the server to obtain the necessary NETBIOS resources.

ANR8227W (AIX)NETBIOS connection terminated - insufficient memory.

Explanation: The server cannot listen for client sessions due to a memory allocation request failure.

System Action: Server operation continues, but NETBIOS sessions are not accepted.

User Response: Ensure that sufficient paging space is available for AIX. You may also use SMIT to determine if the number of applications is causing a memory shortage. You may also decrease the maximum number of sessions that the server can accept with the MAXSESSIONS or the NETBIOSSESSIONS option, or both, in the server options file.

ANR8227W (AS/400)IPX driver unable to initialize due to error in LISTENing on the specified Port.

Explanation: While attempting to listen for session requests from clients using IPX, IPX returns an error.

System Action: Server operation continues, but the server cannot accept additional sessions from clients using the IPX communication protocol.

User Response: Ensure that IPX is running properly. It may be possible to correct this condition by restarting the server.

ANR8227W (Windows NT)NETBIOS connection terminated - insufficient memory, network adapter network adapter number.

Explanation: The server cannot listen for client sessions on the specified network adapter due to a memory allocation request failure.

System Action: Server operation continues, but the sessions will not be accepted on the specified adapter. Other network adapters remain unaffected.

User Response: The most likely cause is a lack of memory. Ensure that there is sufficient space for the Windows NT paging file. Click on the system icon in the Windows NT control panel and then click on the virtual memory button. Refer to the online help for instructions on how to increase the amount of virtual memory.

ANR8228W (AIX)NETBIOS connection terminated - server HALT in progress.

Explanation: The server cannot accept a client session due to server HALT processing that is in progress.

System Action: Server operation continues, but the session request for this session fails.

User Response: None.

ANR8228W (AS/400)IPX driver is terminating due to error in accepting a new session.

Explanation: While attempting to accept a session request from a client using IPX, IPX returns an error.

System Action: Server operation continues, but the server cannot accept additional sessions from clients using the IPX communication protocol.

User Response: Ensure that IPX is running properly. It may be possible to halt the server and start it again to allow additional client sessions to start.

ANR8228W (Windows NT)NETBIOS connection terminated - server HALT in progress.

Explanation: The server cannot accept a client session due to server HALT processing that is in progress.

System Action: Server operation continues, but the session request for this session fails.

User Response: None.

ANR8229W (AIX)Unable to add server name server name to adapter network adapter number.

Explanation: The server cannot initialize communications processing using the NETBIOS protocol on the indicated network adapter because the server name cannot be added as a NETBIOS name on the adapter. Another system on the network may be using the same name for NETBIOS communications. This may be another server or client or a LAN Requester node.

System Action: Server operation continues, but client sessions from clients using the NETBIOS protocol are not accepted on this adapter. Other adapters are not affected.

User Response: Change or add the NETBIOSNAME option for this adapter in your server options file and restart the server to allow this adapter to be used with NETBIOS communications.

ANR8229W (AS/400)An error occurs and the IPX driver is not available.

Explanation: The ADSM server cannot initialize the IPX driver.

System Action: Server operation continues, but IPX communications is not available.

User Response: Contact your service representative.

ANR8229W (Windows NT)Unable to add server name server name to adapter network adapter number.

Explanation: The server cannot initialize communications processing using the NETBIOS protocol on the indicated network adapter because the server name cannot be added as a NETBIOS name on the adapter.

System Action: Server operation continues, but client sessions from clients using the NETBIOS protocol will not be accepted on this adapter. Other adapters are not affected.

User Response: The most likely cause for this message is the presence of another system on the network that is using the same name for NETBIOS communications. This may be another server or client or a LAN Requester node. Changing or adding the NETBIOSNAME option for this adapter in your server options file and restarting the server may allow this adapter to be used with NETBIOS communications.

ANR8230W (AIX)Unable to create thread to monitor sessions on adapter network adapter number.

Explanation: The server cannot accept a client session due to a memory allocation request failure on the specified adapter.

System Action: Server operation continues, but the session request fails.

User Response: Ensure that sufficient paging space is available for AIX. You may also use SMIT to determine if the number of applications is causing a memory shortage. You may also decrease the maximum number of sessions that the server can accept with the MAXSESSIONS or the NETBIOSSESSIONS option, or both, in the server options file.

ANR8230W (AS/400)Error sending data on socket socket number.

Explanation: The ADSM server experiences an error return code from IPX while sending data over the indicated socket. This may be a normal event if either side of the connection is abruptly ended by the client or server.

System Action: The session is ended. Server operation continues.

User Response: If the session is ended as a result of intentionally stopping either the client or the server, no response is required. Otherwise, ensure that the client and the server can communicate.

ANR8230W (Windows NT)Insufficient memory to start NETBIOS session on adapter network adapter number.

Explanation: The server cannot accept a client session due to a memory allocation request failure on the specified adapter.

System Action: Server operation continues, but the session request fails.

User Response: The most likely cause is a lack of memory. Ensure that there is sufficient space for the Windows NT paging file. Click on the system icon in the Windows NT control panel and then click on the virtual memory button. Refer to the online help for instructions on how to increase the amount of virtual memory. You may also wish to cut down on the maximum number of sessions that the server can accept with the MAXSESSIONS or the NETBIOSSESSIONS option, or both, in the server options file.

ANR8231W (AIX)Unable to create thread to accept NETBIOS sessions.

Explanation: The server cannot initialize due to the inability to create a new thread of execution.

System Action: Server operation continues, but NETBIOS communications is inoperative.

User Response: The most likely cause is a lack of memory. The system process table may also be full. Ensure that sufficient paging space is available for AIX. You may also use SMIT to determine if the number of applications is causing a memory shortage. You may also decrease the maximum number of sessions that the server can accept with the MAXSESSIONS or the NETBIOSSESSIONS option, or both, in the server options file.

ANR8231W (AS/400)Error receiving data on socket socket number.

Explanation: The ADSM server experiences an error return code from IPX while receiving data on the indicated socket. This may be a normal event if either side of the connection is abruptly ended by the client or server.

System Action: The session is ended. Server operation continues.

User Response: If the session is ended as a result of intentionally stopping either the client or the server, no response is required. Otherwise, ensure that the client and the server can communicate.

ANR8231W (Windows NT)Unable to create thread to accept NETBIOS sessions.

Explanation: The server cannot initialize due to the inability to create a new thread of execution.

System Action: Server operation continues, but NETBIOS communications is inoperative.

User Response: The most likely cause is a lack of memory. Ensure that there is sufficient space for the Windows NT paging file. Click on the system icon in the Windows NT control panel and then click on the virtual memory button. Refer to the online help for instructions on how to increase the amount of virtual memory. You may also wish to cut down on the maximum number of sessions that the server can accept with the MAXSESSIONS or the NETBIOSSESSIONS option, or both, in the server options file.

ANR8232W (AIX)Unable to create thread to listen to NETBIOS sessions on adapter network adapter number.

Explanation: The server cannot initialize due to the inability to create a new thread of execution to monitor the indicated network adapter.

System Action: Server operation continues, but NETBIOS communications is inoperative on the indicated adapter. Other adapters remain unaffected.

User Response: The most likely cause is a lack of memory. The system process table may also be full. Ensure that sufficient paging space is available for AIX. You may also use SMIT to determine if the number of applications is causing a memory shortage. You may also decrease the maximum number of sessions that the server can accept with the MAXSESSIONS or the NETBIOSSESSIONS option, or both, in the server options file.

ANR8232W (AS/400)Session terminated when no data read on socket socket number.

Explanation: The ADSM server cannot read on the indicated socket. This may be a normal event if either side of the connection is abruptly ended by the client or server.

System Action: The session is ended. Server operation continues.

User Response: If the session is ended as a result of intentionally stopping either the client or the server, no response is required. Otherwise, ensure that the client and the server can communicate.

ANR8232W (Windows NT)Unable to create thread to listen for NETBIOS sessions on adapter network adapter number.

Explanation: The server cannot initialize due to the inability to create a new thread of execution to monitor the indicated network adapter.

System Action: Server operation continues, but NETBIOS communications is inoperative on the indicated adapter. Other adapters remain unaffected.

User Response: The most likely cause is a lack of memory. Ensure that there is sufficient space for the Windows NT paging file. Click on the system icon in the Windows NT control panel and then click on the virtual memory button. Refer to the online help for instructions on how to increase the amount of virtual memory. You may also wish to cut down on the maximum number of sessions that the server can accept with the MAXSESSIONS or the NETBIOSSESSIONS option, or both, in the server options file.

ANR8233W (AIX)Unable to create thread to handle NETBIOS session session number on adapter network adapter number.

Explanation: The server cannot start a new client session on the indicated adapter due to an inability to start a separate thread of execution for the session.

System Action: Server operation continues, but this session request fails.

User Response: The most likely cause is a lack of memory. The system process table may also be full. Ensure that sufficient paging space is available for AIX. You may also use SMIT to determine if the number of applications is causing a memory shortage. You may also decrease the maximum number of sessions that the server can accept with the MAXSESSIONS or the NETBIOSSESSIONS option, or both, in the server options file.

ANR8233W (AS/400)An error occurs and the IPX driver is unable to accept a new session.

Explanation: The ADSM server cannot accept a client session.

System Action: Server operation continues, and the session request fails.

User Response: Contact your service representative.

ANR8233W (Windows NT)Unable to create thread to handle NETBIOS session session number on adapter network adapter number.

Explanation: The server cannot start a new client session on the indicated adapter due to an inability to start a separate thread of execution for the indicated session.

System Action: Server operation continues, but this session request fails.

User Response: The most likely cause is a lack of memory. Ensure that there is sufficient space for the Windows NT paging file. Click on the system icon in the Windows NT control panel and then click on the virtual memory button. Refer to the online help for instructions on how to increase the amount of virtual memory. You may also wish to cut down on the maximum number of sessions that the server can accept with the MAXSESSIONS or the NETBIOSSESSIONS option, or both, in the server options file.

ANR8234W (AIX)Error loading modname for NetBIOS communications method.

Explanation: The server cannot load file module modname to initialize the NETBIOS communications driver. The dsmnetb1.drv module is for use with IBM AIX NETBIOS on Token-Ring/6000. The dsmnetb2.drv module is for use with the newer IBM NETBIOS for AIX.

System Action: Server operation continues. NetBIOS communications is inoperative.

User Response: The dsmnetb1.drv and dsmnetb2.drv modules are accessed as part of the load process for NetBIOS communications. Both should be in the same directory as the dsmserv executable or in a directory that is pointed to by the DSMSERV_DIR environment variable. The dsmnetb2.drv module will fail to load unless the STREAMS environment is active. The STREAMS environment is activated with the /usr/sbin/strload command. The server attempts to initialize the IBM AIX NETBIOS on Token-Ring/6000 environment first. If /dev/netbios does not open, the server attempts to initialize the IBM NETBIOS for AIX environment. Consequently, if you have IBM AIX NETBIOS on Token-Ring/6000, but do not have it available for use, you will receive this message naming dsmnetb2.drv as the module that failed to load.

ANR8235W (Windows NT)Requested number of NETBIOS sessions are not available on adapter network adapter number, proceeding with available sessions.

Explanation: The server cannot acquire the requested number of NETBIOS sessions for the indicated adapter. The server attempts to acquire the number of NETBIOS sessions as indicated by the NETBIOSSESSIONS parameter of the server options file or, if this option is not specified, by the MAXSESSIONS option.

System Action: Server operation continues, but the maximum number of NETBIOS sessions is limited to the number of sessions that are acquired.

User Response: Ensure that the required number of NETBIOS resources are not already in use. If the LAN Server or LAN Requester application is running, you have NETBIOS configured. In that case, starting the server prior to starting LAN Server or LAN Requester may allow the server to obtain the requested NETBIOS resources.

ANR8236W (AIX)Failure while listening for NETBIOS sessions on adapter network adapter number, NETBIOS listen return code=listen return code.

Explanation: The server cannot listen for NETBIOS sessions on the indicated adapter. The indicated listen return code has been received from the NetBIOS listen API.

System Action: Server operation continues, but no additional NETBIOS sessions will start using the indicated adapter until the problem is corrected and the server is restarted.

User Response: A NETBIOS listen failure is an indication of a network problem, an adapter problem, or a NETBIOS configuration problem. The following system configuration and system environment listen return codes (in hex) and resolution actions for a listen failure are found in the LAN Technical Reference IEEE 802.2 and NETBIOS APIs.

Return Code Description
11 Local session table full. The maximum number of sessions is in use. Change NETBIOS configuration to increase maximum number of sessions.
19 Name conflict. Ensure that the Server NETBIOS name is not in use elsewhere on the network.
22 Too many commands pending. The maximum number of sessions is in use. Change NETBIOS configuration to increase the maximum number of sessions.

ANR8236W (Windows NT)Failure while listening for NETBIOS sessions on adapter network adapter number, NETBIOS listen return code = listen return code.

Explanation: The server cannot listen for NETBIOS sessions on the indicated adapter. The indicated listen return code was received from the NETBIOS listen API. If the return code is 24, (hex 18), the listen is retried.

System Action: Server operation continues. If the return code is 24 (hex 18), a new listen is setup because return code 24 indicates a temporary failure. Otherwise, no additional NETBIOS sessions will start using the indicated adapter until the problem is corrected and the server is restarted.

User Response: A NETBIOS listen failure is an indication of a network problem, an adapter problem, or a NETBIOS configuration problem. The following system configuration and system environment listen return codes (in hex) and resolution actions for a listen failure are found in the IBM Local Area Network Technical Reference:

Return Code Description
11 The local session table is full. The maximum number of sessions are in use. Change NETBIOS configuration to increase the maximum number of sessions.
19 Name conflict. Ensure that the Server NETBIOS name is not in use elsewhere on the network.
22 There are too many commands pending. The maximum number of sessions are in use. Change NETBIOS configuration to increase the maximum number of sessions.
35 The operating system resources are exhausted. A reboot is probably required.

ANR8239I (AS/400)HTTP driver is ready for connection with clients on port port number.

Explanation: The ADSM server can accept sessions with clients using the HTTP communication protocol on the indicated port number.

System Action: Server operation continues.

User Response: None.

ANR8240I (AIX)APPC driver ready for connection with clients on LU LU name.

Explanation: The server is now able to accept sessions with clients using the APPC protocol through the indicated LU name.

System Action: Server operation continues.

User Response: None.

ANR8240I (AS/400)APPC driver ready for connection with clients on LU LU name.

Explanation: The ADSM server can accept sessions with clients using the APPC protocol through the indicated LU name.

System Action: Server operation continues.

User Response: None.

ANR8240I (Windows NT)IPX/SPX driver ready for connection with clients on port port number.

Explanation: The server can now accept sessions with clients using the IPX/SPX protocol on the indicated port number.

System Action: Server operation continues.

User Response: None.

ANR8241W (AIX)APPC connection terminated - insufficient memory.

Explanation: The server cannot accept a client session due to a memory allocation request failure. If this failure occurs prior to the first session request, APPC communications are not established.

System Action: Server operation continues.

User Response: The most likely cause is a lack of memory. The system process table may also be full. Ensure that sufficient paging space is available for AIX. You may also use SMIT to determine if the number of applications is causing a memory shortage. You may also decrease the maximum number of sessions that the server can accept with the MAXSESSIONS option in the server options file.

ANR8241W (AS/400)APPC connection terminated - insufficient memory.

Explanation: The ADSM server cannot accept a client session due to a memory allocation request failure. If this failure occurs prior to the first session request, APPC communications is inoperative.

System Action: Server operation continues.

User Response: Contact your service representative.

ANR8241W (Windows NT)Unable to initialize IPX/SPX driver - insufficient memory.

Explanation: The server is unable to communicate by way of IPX/SPX. A memory allocation request has been rejected by the operating system.

System Action: Server operation continues, but the server cannot accept sessions from clients using the IPX/SPX protocol.

User Response: Ensure that there is sufficient space for the Windows NT paging file. Click on the system icon in the Windows NT control panel and then click on the virtual memory button. Refer to the online help for instructions on how to increase the amount of virtual memory.

ANR8242W (AIX)Unable to create thread to monitor sessions on LU LU name.

Explanation: The server cannot initialize due to the inability to create a new thread of execution to monitor the indicated LU name.

System Action: Server operation continues, but APPC communications are not established for the indicated LU name. Other LU names remain unaffected.

User Response: The most likely cause is a lack of memory. The system process table may also be full. Ensure that sufficient paging space is available for AIX. You may also use SMIT to determine if the number of applications is causing a memory shortage. You may also decrease the maximum number of sessions that the server can accept with the MAXSESSIONS option in the server options file.

ANR8242W (Windows NT)Unable to initialize IPX/SPX driver - error creating acceptor socket.

Explanation: The server is unable to communicate by way of IPX/SPX. IPX/SPX has rejected a request for a socket on which the server listens.

System Action: Server operation continues, but the server cannot accept sessions from clients using the IPX/SPX protocol.

User Response: Ensure that IPX/SPX is operational on your system by using the network control panel applet. If IPX/SPX is not started, issue the HALT command to stop the server, and then restart the server.

ANR8243W (AIX)Unable to open APPC connection connection: errno error number.

Explanation: The server cannot open the connection with the client.

System Action: Server operation continues, but APPC communications is not established.

User Response: Make sure the default side information profile IDEFAULT exists and retry the operation.

ANR8243W (Windows NT)Unable to establish IPX/SPX connection - insufficient memory.

Explanation: The server is unable to accept a client session due to a memory allocation request failure.

System Action: Server operation continues, but the session request for this session fails.

User Response: Ensure that there is sufficient space for the Windows NT paging file. Click on the system icon in the Windows NT control panel and then click on the virtual memory button. Refer to the online help for instructions on how to increase the amount of virtual memory. You may also wish to cut down on the maximum number of sessions that the server can accept with the MAXSESSIONS option in the server options file.

ANR8244W (Windows NT)IPX/SPX driver unable to initialize due to socket initialization error.

Explanation: While initializing IPX/SPX communications, the server has failed to set up an interface with IPX/SPX for Windows NT.

System Action: Server operation continues, but the server cannot accept sessions from clients using the IPX/SPX protocol.

User Response: Ensure that IPX/SPX is properly installed on your system. Ensure that IPX/SPX has been started on your system. Verify that IPX/SPX is both installed and active on your system by using the network control panel applet.

ANR8245W (AIX)Unable to create APPC thread.

Explanation: The server cannot initialize due to the inability to create a new thread of execution.

System Action: Server operation continues, but APPC communications are not established.

User Response: The most likely cause is a lack of memory. The system process table may also be full. Ensure that sufficient paging space is available for AIX. You may also use SMIT to determine if the number of applications is causing a memory shortage. You may also decrease the maximum number of sessions that the server can accept with the MAXSESSIONS option in the server options file.

ANR8245W (Windows NT)IPX/SPX driver unable to initialize due to error in BINDing to Port port, reason code reason code.

Explanation: While initializing IPX/SPX communications, the server has failed to connect to a master socket on which to listen for clients. The reason code is the return code from the IPX/SPX bind API.

System Action: Server operation continues, but the server cannot accept sessions from clients using the IPX/SPX protocol.

User Response: Ensure that no other application is using the port number specified in the server options file with the PORT option.

ANR8246W (AIX)Error sending data on connection descriptor connection descriptor. Terminating session session number.

Explanation: The server experiences an error return code from APPC while sending data over the indicated server session number. This may be a normal event if either side of the connection is abruptly ended.

System Action: The session is ended. Server operation continues.

User Response: If the session is ended as a result of intentionally stopping either the client or server, no response is required. Otherwise, ensure that the client and server can communicate over an APPC connection.

ANR8246W (Windows NT)IPX/SPX driver unable to initialize due to error in LISTENing on the specified Port, reason code reason code.

Explanation: While attempting to listen for session requests from clients using IPX/SPX, IPX/SPX returns an error. The reason code is the return code from the IPX/SPX listen API.

System Action: Server operation continues, but the server cannot accept additional sessions from clients using the IPX/SPX protocol.

User Response: Ensure that IPX/SPX is running properly. This may be done using the network control panel applet.

ANR8247W (AIX)Error listening for session from APPC partner, return code from SET_PARTNER_LU_NAME is return code.

Explanation: The server experiences an error return code from APPC while attempting to set up to listen for client sessions. The return code is from the APPC set partner LU name call for appc listen.

System Action: Server operation continues. APPC communications is disabled.

User Response: Ensure that APPC is properly configured and activated. Ensure that APPC can communicate with other nodes through utility programs.

ANR8247E (AS/400)Device class device class not defined in device configuration information file.

Explanation: The command that has been issued requires that the specified device class be defined in the device configuration information file. This definition was not found or the statements in the file are in the wrong order.

System Action: The command is not processed.

User Response: You can either reissue the command and specify a valid device class or refresh your device configuration information file by issuing the BACKUP DEVCONFIG command.

ANR8247W (Windows NT)IPX/SPX driver is terminating due to error in accepting a new session, reason code reason code.

Explanation: While attempting to accept a session request from a client using IPX/SPX, IPX/SPX returns an error. The reason code is the return code from the IPX/SPX accept API.

System Action: Server operation continues, but the server cannot accept additional sessions from clients using the IPX/SPX protocol.

User Response: Ensure that IPX/SPX is running properly. This may be done using the network control panel applet.

ANR8248W (AIX)Error on allocate listen from APPC LU name LU name, return code return code.

Explanation: The server experiences an error return code from APPC while attempting to listen for client sessions on the indicated LU name. The return code is from the APPC allocate listen call.

System Action: Server operation continues. APPC communications is disabled.

User Response: Ensure that APPC is properly configured and activated. Ensure that APPC can communicate with other nodes through utility programs. Ensure that the server LU Name is properly configured within APPC.

ANR8248E (AS/400)Library library not defined in device configuration information file.

Explanation: The specified command requires that the specified library be defined in the device configuration information file. This definition was not found or the statements in the file are in the wrong order.

System Action: The command is not processed.

User Response: Refresh your device configuration information file by issuing the BACKUP DEVCONFIG command. Make sure a library is defined for the device class. Reissue the command.

ANR8248W (Windows NT)IPX/SPX driver is terminating due to error in creating a new thread.

Explanation: The server cannot initialize due its inability to create a new thread of execution.

System Action: Server operation continues, but IPX/SPX communications is inoperative.

User Response: The most likely cause is a lack of memory. Ensure that there is sufficient space for the Windows NT paging file. Click on the system icon in the Windows NT control panel and then click on the virtual memory button. Refer to the online help for instructions on how to increase the amount of virtual memory. You may also wish to cut down on the maximum number of sessions that the server can accept with the MAXSESSIONS option in the server options file.

ANR8249W (AIX)Server Transaction Program not registered with APPC. Mask returned 0xmask, return code return code.

Explanation: The server determines that the Server Transaction Program is not registered while initializing to communicate with clients over APPC. The indicated mask is returned with the indicated return code.

System Action: Server operation continues. APPC communications is disabled.

User Response: Ensure that APPC is properly configured and activated. Ensure that APPC can communicate with other nodes through utility programs. Ensure that ADSMSERV is properly registered as a transaction program.

ANR8249E (AS/400)Drive not defined for library library in device configuration information file.

Explanation: The specified command requires that the specified drive be defined in the device configuration information file for the specified library. This definition was not found or the statements in the file are in the wrong order.

System Action: The command is not processed.

User Response: Refresh your device configuration information file by issuing the BACKUP DEVCONFIG command. Make sure a drive is defined for the library associated with the device class. Reissue the command.

ANR8249W (Windows NT)Unable to resolve address for node name.

Explanation: The server attempts to obtain a IPX/SPX address for the indicated node name. The attempt is unsuccessful.

System Action: The attempt to communicate with the indicated node fails. Server operation continues.

User Response: Ensure that the node name is properly specified and that it is accessible over the network.

ANR8250E (AIX)APPC needs a transaction program name profile name in options file.

Explanation: The server cannot accept a client session due to the absence of a transaction program name profile name in the options file.

System Action: Server operation continues.

User Response: Supply a transaction program name profile name in the server options file. Stop and restart the server.

ANR8250W (Windows NT)Session open with node name timed out.

Explanation: The server attempts to contact the indicated node name. The attempt is unsuccessful.

System Action: The attempt to communicate with the indicated node fails.

User Response: Ensure that the node name is properly specified and that it is accessible over the network.

ANR8251W (AIX)Error receiving data on connection descriptor connection descriptor. Terminating session session number.

Explanation: The server encounters an error return code from APPC while receiving data over the indicated server session number. This may be a normal event if either side of the connection is abruptly ended.

System Action: The session is ended. Server operation continues.

User Response: If the session is ended as a result of intentionally stopping the client or server, no response is required. Otherwise, ensure that the client and server can communicate over an APPC connection.

ANR8251W (Windows NT)Session open with node name failed due to connection refusal.

Explanation: The server attempts to contact the indicated node name. The attempt is unsuccessful due to a refusal by the target node.

System Action: The attempt to communicate with the indicated node fails. Server operation continues.

User Response: Ensure that the node name still has IPX/SPX running and that the client is active in SCHEDULE mode.

ANR8252I (AIX)APPC driver is halting. This may take a minute.

Explanation: The APPC driver of the server is shutting down in response to the HALT command.

System Action: None.

User Response: None.

ANR8252W (Windows NT)Session open with node name failed as unreachable.

Explanation: The server attempts to contact the indicated node name. The attempt is unsuccessful.

System Action: The attempt to communicate with the indicated node fails. Server operation continues.

User Response: Ensure that the node name is properly specified and that it is accessible over the network.

ANR8253W (AIX)Error killing select tid select thread id return code rc.

Explanation: The server encounters an error return code from AIX while killing the select thread. This may hang the server.

System Action: Server operation continues.

User Response: If the server hangs, a manual kill of the server process might be necessary. See adsmserv.lock file in the directory where the server was started to find the server process id.

ANR8253W (Windows NT)Error sending data on socket socket number. Reason return code.

Explanation: The server experiences an error return code from IPX/SPX while sending data over the indicated socket. This may be a normal event if either side of the connection is abruptly ended.

System Action: The session is ended. Server operation continues.

User Response: If the session is ended as a result of intentionally stopping either the client or server, no response is required.

ANR8254W (Windows NT)Error receiving data on socket socket number. Reason return code.

Explanation: The server experiences an error return code from IPX/SPX while receiving data on the indicated socket. This may be a normal event if either side of the connection is abruptly ended.

System Action: The session is ended. Server operation continues.

User Response: If the session is ended as a result of intentionally stopping either the client or server, no response is required.

ANR8255W (Windows NT)Session terminated when no data read on socket socket number.

Explanation: The server cannot read on the indicated socket. This may be a normal event if either side of the connection is abruptly ended.

System Action: The session is ended. Server operation continues.

User Response: If the session is ended as a result of intentionally stopping either the client or server, no response is required.

ANR8256W (Windows NT)IPX/SPX driver is unable to accept a new session due to error in creating a new thread.

Explanation: The server cannot accept a client session due to the inability to create a new thread.

System Action: Server operation continues, the session request fails.

User Response: The most likely cause is a lack of memory. Ensure that there is sufficient space for the Windows NT paging file. Click on the system icon in the Windows NT control panel and then click on the virtual memory button. Refer to the online help for instructions on how to increase the amount of virtual memory. You may also wish to cut down on the maximum number of sessions that the server can accept with the MAXSESSIONS option in the server options file.

ANR8257W (Windows NT)IPX/SPX driver is unable to contact node name due to an output socket initialization error.

Explanation: The server attempts to contact the indicated node name. The attempt is unsuccessful due to the inability to initialize a local socket.

System Action: The attempt to communicate with the indicated node fails.

User Response: Ensure that IPX/SPX is operating properly on this node and that it can communicate remotely.

ANR8259I (AS/400)Request number: Waiting for the completion of an AS/400 MLB operation in device device name.

Explanation: The server is waiting for an AS/400 media library operation to complete.

System Action: The server waits for the AS/400 media library operation to complete.

User Response: None.

ANR8260I (AS/400)Exit type EXIT exit name defined.

Explanation: The designated exit has been successfully defined.

System Action: The server defines and records the exit in the database.

User Response: None.

ANR8260I (Windows NT)Named Pipes driver ready for connection with clients.

Explanation: The server is now able to accept sessions with clients using the Named Pipes protocol.

System Action: Server operation continues.

User Response: None.

ANR8261W (AIX)Unable to bind to NetBIOS endpoint on adapter Adapter number Return code TLI error, reason code system error.

Explanation: The server cannot initiate NetBIOS communications on the indicated adapter. The return codes represent the transport layer interface and system error codes.

System Action: Server operation continues, but communications using the NetBIOS protocol are not established.

User Response: Ensure that NetBIOS has been configured to run on this system through the mcsadm utility. Ensure that there is no other instance of the server running on this system or any other system in the network that is using the same NetBIOS name. Also ensure that the number of NetBIOS sessions has not been exceeded by using the mcsadm utility.

ANR8261I (AS/400)Exit type EXIT exit name deleted.

Explanation: The designated exit has been successfully deleted.

System Action: The server deletes the exit from the database.

User Response: None.

ANR8261W (Windows NT)Named Pipes connection terminated - insufficient memory.

Explanation: The server cannot accept a client session due to a memory allocation request failure.

System Action: Server operation continues. Named Pipes communications is inoperative.

User Response: The most likely cause is a lack of memory. Ensure that there is sufficient space for the Windows NT paging file. Click on the system icon in the Windows NT control panel and then click on the virtual memory button. Refer to the online help for instructions on how to increase the amount of virtual memory. You may also wish to cut down on the maximum number of sessions that the server can accept with the MAXSESSIONS option in the server options file.

ANR8262W (AIX)Unable to open NetBIOS endpoint adapter. Return code = return code.

Explanation: The server cannot initiate communications through the transport layer interface. The indicated return code is from the t_open call. The indicated endpoint is the adapter configured with the mcsadm utility.

System Action: Server operation continues, but communications using the NetBIOS protocol are not established.

User Response: Ensure that NetBIOS has been configured to run on this system through the mcsadm program, and that the NetBIOS stack is running. Also ensure that you have the ptf that allow NetBIOS over TLI to run using /usr/lib/libtli_r.a.

ANR8262I (AS/400)Exit type EXIT exit name updated.

Explanation: The designated exit has been successfully updated.

System Action: The server updates its information about the exit.

User Response: None.

ANR8262W (Windows NT)Named Pipes driver is terminating due to error in creating a new thread.

Explanation: The server cannot initialize due to the inability to create a new thread of execution.

System Action: Server operation continues, but Named Pipes communications is inoperative.

User Response: The most likely cause is a lack of memory. Ensure that there is sufficient space for the Windows NT paging file. Click on the system icon in the Windows NT control panel and then click on the virtual memory button. Refer to the online help for instructions on how to increase the amount of virtual memory. You may also wish to cut down on the maximum number of sessions that the server can accept with the MAXSESSIONS option in the server options file.

ANR8263W (AIX)NetBIOS driver unable to initialize due to error in LISTENing on adapter adapter, return code return code reason code reason code.

Explanation: While the server attempts to listen for session requests from clients using NetBIOS on the indicated adapter, the transport layer interface (TLI) returns an error. The return code is the return code from the TLI listen API. The reason code is the system error code.

System Action: Server operation continues, but the server cannot accept additional sessions from clients using the NetBIOS protocol.

User Response: Ensure that NetBIOS is still running properly and that it has not been intentionally or unintentionally brought down. Do this by using the mcsadm administrative utility.

ANR8263W (AS/400)End of tape detected on device type volume volume name in drive drive name of library library name.

Explanation: The server has detected end of tape for the specified volume. The volume reached the end of tape before arriving at the estimated capacity value specified in the device class.

System Action: The current process stops writing to the specified volume. The status of the volume is set to read-only. The server accesses another volume if more data must be stored.

User Response: Reduce the estimated capacity in the device class. You can issue the QUERY VOLUME command to view the actual capacity of the volume after it is full. Use the UPDATE DEVCLASS command to change the estimated capacity for the device class. Do not use the UPDATE VOLUME command to change the access mode.

ANR8263W (Windows NT)Error sending data on Named Pipes, session session number.WriteFile Return code is return code.

Explanation: The server experiences an error return code from the WriteFile Windows NT API while writing data to Named Pipes over the indicated session. This may be a normal event if either side of the connection is abruptly ended.

System Action: The session is ended. Server operation continues.

User Response: If the session is ended as a result of intentionally stopping either the client or server, no response is required.

ANR8264I (AIX)Unable to bind to NetBIOS secondary socket. Return code TLI error, reason code system error.

Explanation: The server cannot start communications with a client after listening for a session and finding that a request for a session is in progress. The return codes represent the transport layer interface and system error codes.

System Action: Server operation continues, but this session request fails.

User Response: Ensure that NetBIOS has been configured to run on this system through the mcsadm configuration program. Ensure that the number of NetBIOS sessions has not been exceeded.

ANR8264W (Windows NT)Error reading data on Named Pipes, session session number. ReadFile return code is return code.

Explanation: The server experiences an error return code from the ReadFile Windows NT API while reading data from Named Pipes in the indicated session. This may be a normal event if either side of the connection is ended abruptly.

System Action: The session is ended. Server operation continues.

User Response: If the session is ended as a result of intentionally stopping either the client or server, no response is required.

ANR8265W (AIX)Unable to establish NetBIOS connection - accept error. Return code TLI error Reason Code system error.

Explanation: The server cannot accept a client session due to a failure in accepting the connection from NetBIOS.

System Action: Server operation continues, but this session request fails.

User Response: Ensure that NetBIOS has been configured to run on this system though the mcsadm utility. Ensure that there is no other instance of the server running on the same system that is using the same NetBIOS name. Also check for the maximum number of sessions configured.

ANR8265W (Windows NT)Error open Named Pipes Named Pipes name, CreateNamedPipe return code return code.

Explanation: The server experiences an error return code when trying to open the indicated Named Pipes name for Named Pipes communication with a client. The return code shown is returned by the Windows NT CreateNamedPipe API.

System Action: The session is ended. Server operation continues. Named Pipes communications is inoperative.

User Response: The server may have run out of file handles. Stop and restart the server to reenable Named Pipes communications. It is not normal to run out of file handles. A system or logic error may be the underlying cause.

ANR8266W (AIX)Error receiving data on session session number. Reason return code.

Explanation: The server experiences an error return code from NetBIOS while receiving data on the indicated session. This may be a normal event if either side of the connection is abruptly ended.

System Action: The session is ended. Server operation continues.

User Response: If the session is ended as a result of intentionally stopping either the client or server, no response is required. Otherwise, ensure that NetBIOS is active.

ANR8266W (Windows NT)Error accepting connection on Named Pipes Named Pipes name, ConnectNamedPipe return code return code.

Explanation: The server experiences an error return code when trying to complete a connection on the indicated Named Pipes name for Named Pipes communication with a client. The return code shown is returned by the Windows NT ConnectNamedPipe API.

System Action: The session is ended. Server operation continues. Named Pipes communications is inoperative.

User Response: A system problem may be preventing use of Named Pipes. Stop and restart the server to reenable Named Pipes communications.

ANR8267W (AIX)Error sending data on session session number. Reason return code.

Explanation: The server experiences an error return code from NetBIOS while sending data on the indicated session. This may be a normal event if either side of the connection is abruptly ended.

System Action: The session is ended. Server operation continues.

User Response: If the session is ended as a result of intentionally stopping either the client or server, no response is required. Otherwise, ensure that NetBIOS is active.

ANR8267W (Windows NT)Error initializing a security descriptor for Named Pipes Named Pipes name, reason: System message.

Explanation: The server experiences an error return code when trying to initialize the indicated Named Pipe for Named Pipes communication with a client. The reason shown is returned by the Windows NT FormatMessage API.

System Action: The session is ended. Server operation continues. Named Pipes communications is inoperative.

User Response: Administrator Privileges are required. Login using an account wit h Administrator privileges and restart the server to reenable Named Pipes communications.

ANR8268W (AS/400)AS/400 Tape Management Exit Program unavailable.

Explanation: Based on ADSM library and device definitions, the server has attempted to use the AS/400 Tape Management Exit Program, QIBM_QTA_TAPE_TMS. The exit program is either in use or not installed. The exit program may be in use by a tape management system.

System Action: Server operation continues. The server issues additional error messages when this condition prevents it from completing an operation.

User Response: Ensure that the ADSM library and device definitions are correct. If a tape management system is available, it is possible that the ADSM definitions may be changed to use it. If the exit program is not installed, evaluate your system hardware to determine if the exit must be obtained for use by ADSM. The AS/400 Tape Management Exit Program is part of the Media and Storage Extensions (MSE) feature of OS/400. Additional information about this exit program is available in System API Reference, SC41-3801.

ANR8268W (Windows NT)Named Pipe communications were not enabled due to an error looking up the following NT group name: NT group name. Use the NT User manager to add the specified group. Members of the group will then use NT unified logon to access the server over Named pipes.

Explanation: The server experiences an error return code when trying to initialize the indicated Named Pipe for Named Pipes communication with a client. The system could not find the NT Account name specified in the server options file.

System Action: The session is ended. Server operation continues. Named Pipes communications is inoperative.

User Response: To use NT unified logon specify the name of a valid Windows NT account or group name. Restart the server to reenable Named Pipes communications.

ANR8269I (AS/400)Request number: exit type EXIT returned device device name.

Explanation: The specified exit program provides the indicated device name to the server.

System Action: Server operation continues.

User Response: None.

ANR8269W (Windows NT)Error opening Named Pipe Named Pipes name, reason: System message.

Explanation: The server experiences an error return code when trying to open the indicated Named Pipe name for Named Pipes communication with a client. The reason shown is returned by the Windows NT FormatMessage API.

System Action: The session is ended. Server operation continues. Named Pipes communications is inoperative.

User Response: Consider the reason text and take appropriate action. Stop and restart the server to reenable Named Pipes communications.

ANR8270I (AIX)IPX/SPX driver ready for connection with clients on socket IPX socket number.

Explanation: The server is now able to accept sessions with clients using the IPX/SPX protocol on the indicated socket number.

System Action: Server operation continues.

User Response: None.

ANR8270I (AS/400)Request number: exit type EXIT returned volume volume name.

Explanation: The specified exit program provides the indicated volume name to the server.

System Action: Server operation continues.

User Response: None.

ANR8271W (AIX)Unable to bind to IPX/SPX master socket. Return code TLI error, reason code system error.

Explanation: The server cannot initiate communications on the socket number designated for its use. The return codes represent the transport layer interface and system error codes.

System Action: Server operation continues, but communications using the IPX/SPX protocol are not established.

User Response: Ensure that SPX has been configured to run on this system through the requester configuration program. Ensure that there is no other instance of the server running on the same system that is using the same socket number. Also ensure that the number of SPX sessions has not been exceeded through other applications using the IPX/SPX protocol, such as NetWare for AIX clients.

ANR8271E (AS/400)Request number: Error opening volume volume name on drive drive name.

Explanation: ADSM detects an error while attempting to open a volume in the specified drive.

System Action: If a volume is mounted, it is ejected. If the library is of type USRDFN, this media operation fails. For any other library type, the server continues to wait for the requested volume to be mounted.

User Response: Ensure that a volume is inserted properly in the designated drive.

ANR8272W (AIX)IPX/SPX connection terminated - insufficient memory.

Explanation: The server cannot accept a client session due to a memory allocation request failure.

System Action: Server operation continues.

User Response: The most likely cause is a lack of memory. The system process table may also be full. Ensure that sufficient paging space is available for AIX. You may also use SMIT to determine if the number of applications is causing a memory shortage. You may decrease the maximum number of sessions that the server can accept with the MAXSESSIONS option in the server options file.

ANR8272I (AS/400)Request number: Waiting for the completion of an AS/400 I/O operation on device device name.

Explanation: The server is waiting for an AS/400 I/O operation to complete.

System Action: The server waits for the AS/400 I/O operation to complete.

User Response: None.

ANR8273W (AIX)Unable to open IPX/SPX endpoint. Return code = return code.

Explanation: The server cannot initiate communications through the transport layer interface. The indicated return code is from the t_open call.

System Action: Server operation continues, but communications using the IPX/SPX protocol are not established.

User Response: Ensure that SPX has been configured to run on this system through the NetWare for AIX configuration program, and that the Netware Protocol Stack daemon is running.

ANR8273I (AS/400)Request number: Waiting for a reply from the AS/400 message queue associated with device device name.

Explanation: The server is waiting for a reply from the AS/400 message queue associated with specified device.

System Action: The server waits for a reply to the message on the queue associated with the given device.

User Response: Locate the message and provide an appropriate reply.

ANR8273I (Windows NT)Shared memory driver ready for connection with clients.

Explanation: The server is now able to accept sessions with clients using the shared memory protocol.

System Action: Server operation continues.

User Response: None.

ANR8274W (AIX)IPX/SPX driver is terminating due to error in creating a new thread.

Explanation: The server cannot initialize due to the inability to create a new thread of execution.

System Action: Server operation continues, but IPX/SPX communications are not established.

User Response: The most likely cause is a lack of memory. Ensure that sufficient paging space is available for AIX. You may also use SMIT to determine if the number of applications is causing a memory shortage. You may also decrease the maximum number of sessions that the server can accept with the MAXSESSIONS option in the server options file.

ANR8274E (AS/400)Command: exit type EXIT exit name could not be located.

Explanation: The *PGM object with the specified exit name cannot be located on the AS/400.

System Action: The server does not process the command.

User Response: Reissue the command and specify a different exit name, or create the exit program before reissuing the command.

ANR8274W (Windows NT)Shared memory communications driver is terminating due to error in creating a new thread.

Explanation: The server cannot initialize due to the inability to create a new thread of execution.

System Action: Server operation continues, but shared memory communications is inoperative.

User Response: The most likely cause is a lack of memory. Ensure that there is sufficient space for the Windows NT paging file. Click on the system icon in the Windows NT control panel and then click on the virtual memory button. Refer to the online help for instructions on how to increase the amount of virtual memory.

ANR8275W (AIX)IPX/SPX driver unable to initialize due to error in LISTENing on the master socket, return code return code reason code reason code.

Explanation: While the server attempts to listen for session requests from clients using IPX/SPX, the transport layer interface (TLI) returns an error. The return code is the return code from the TLI listen API. The reason code is the system error code.

System Action: Server operation continues, but the server cannot accept additional sessions from clients using the IPX/SPX protocol.

User Response: Ensure that IPX/SPX is still running properly and that it has not been intentionally or unintentionally brought down. Do this by issuing the NetWare for AIX transport utilities. Ensure that the Netware Protocol Stack daemon is running.

ANR8275E (AS/400)Command: exit type EXIT is not defined.

Explanation: The designated exit has not been defined to the server.

System Action: The server does not process the command.

User Response: Reissue the command and specify a different exit type, or define the exit before reissuing the command.

ANR8275W (Windows NT)Shared memory connection terminated - insufficient memory.

Explanation: The server cannot accept a client session due to a memory allocation request failure.

System Action: Server operation continues. Shared memory communications is inoperative.

User Response: The most likely cause is a lack of memory. Ensure that there is sufficient space for the Windows NT paging file. Click on the system icon in the Windows NT control panel and then click on the virtual memory button. Refer to the online help for instructions on how to increase the amount of virtual memory. You may also wish to cut down on the maximum number of sessions that the server can accept with the MAXSESSIONS option in the server options file.

ANR8276I (AIX)Unable to bind to IPX/SPX secondary socket. Return code TLI error, reason code system error.

Explanation: The server cannot start communications with a client after listening for a session and finding that a request for a session is in progress. The return codes represent the transport layer interface and system error codes.

System Action: Server operation continues, but this session request fails.

User Response: Ensure that SPX has been configured to run on this system through the requester configuration program. Ensure that there is no other instance of the server running on the same system which is using the same socket number. Also ensure that the number of SPX sessions has not been exceeded through other applications using the IPX/SPX protocol, such as NetWare for AIX clients.

ANR8276E (AS/400)Command: exit type EXIT is already defined.

Explanation: The designated exit cannot be defined because it already exists.

System Action: The server does not process the command.

User Response: None.

ANR8276W (Windows NT)Shared memory connection terminated - unable to initialize. Key channel key, Reason: reason code.

Explanation: The server cannot accept a client session due being unable to initialize shared memory.

System Action: Server operation continues. Shared memory communications are inoperative.

User Response: Try a different shared memory session.

ANR8277W (AIX)Unable to establish IPX/SPX connection - accept error. Return code TLI error Reason Code system error.

Explanation: The server cannot accept a client session due to a failure in accepting the connection from IPX/SPX.

System Action: Server operation continues, but this session request fails.

User Response: Ensure that SPX has been configured to run on this system though the requester configuration program. Ensure that there is no other instance of the server running on the same system that is using the same socket number. Also ensure that the number of SPX sessions has not been exceeded through other applications using the IPX/SPX protocol, such as NetWare for AIX clients.

ANR8277E (AS/400)Command: exit type EXIT name exit name is invalid.

Explanation: The syntax of the specified exit program name is invalid.

System Action: The server does not process the command.

User Response: Reissue the command and specify valid syntax for the exit name.

ANR8278W (AIX)Error receiving data on session session number. Reason return code.

Explanation: The server experiences an error return code from IPX/SPX while receiving data on the indicated session. This may be a normal event if either side of the connection is abruptly ended.

System Action: The session is ended. Server operation continues.

User Response: If the session is ended as a result of intentionally stopping either the client or server, no response is required. Otherwise, ensure that IPX/SPX is active.

ANR8278E (AS/400)Command: exit type EXIT library name is invalid or does not exist.

Explanation: The specified AS/400 library name is invalid or it does not exist.

System Action: The server does not process the command.

User Response: Reissue the command and specify a different library name.

ANR8279W (AIX)Error sending data on session session number. Reason return code.

Explanation: The server experiences an error return code from IPX/SPX while sending data on the indicated session. This may be a normal event if either side of the connection is abruptly ended.

System Action: The session is ended. Server operation continues.

User Response: If the session is ended as a result of intentionally stopping either the client or server, no response is required. Otherwise, ensure that IPX/SPX is active.

ANR8279E (AS/400)Command: exit type EXIT program name is invalid.

Explanation: The syntax of the specified program name is invalid.

System Action: The server does not process the command.

User Response: Reissue the command and specify a different program name.

ANR8280W (AIX)Error loading dsmtli.drv for IPX/SPX or NetBIOS communications methods.

Explanation: The server cannot load file dsmtli.drv to initialize a communications driver.

System Action: Server operation continues. The communications method that was initializing is inoperative. This may be either NetBIOS, IPX/SPX or both, depending upon the contents of the server options file dsmserv.opt.

User Response: NetWare for AIX, IBM NetBIOS and IPX Support, or AIX Connections must be installed on your system to use IPX/SPX communications. IBM NetBIOS and IPX Support or AIX Connections must be installed on your system to use NetBIOS communications. File libtli.a is accessed as part of the load process through module dsmtli.drv. This file should be in the same directory as the dsmserv executable or it must be in a directory that is pointed to by the DSMSERV_DIR environment variable.

ANR8280E (AS/400)Command: One or more libraries are still defined to use the exit type EXIT.

Explanation: The designated exit cannot be deleted because there are still libraries defined to use the exit.

System Action: The server does not process the command.

User Response: Delete all the libraries that use the exit and reissue the command.

ANR8280I (Windows NT)HTTP driver ready for connection with clients on port port number.

Explanation: The server can now accept sessions with clients using the HTTP protocol on the indicated port number.

System Action: Server operation continues.

User Response: None.

ANR8281W (AIX)Error binding dsmtli.drv for IPX/SPX or NetBIOS communications method.

Explanation: The server cannot loadbind dsmtli.drv to initialize the IPX/SPX or NetBIOS communications driver after successfully loading dsmtli.drv.

System Action: Server operation continues. IPX/SPX or NetBIOS communications is inoperative.

User Response: NetWare for AIX, IPX and NetBIOS Support/6000, or AIX Connections must be installed on your system to use IPX/SPX communications. IPX and NetBIOS Support/6000 or AIX Connections must be installed on your system to use NetBIOS communications. File libtli.a is accessed as part of the load and loadbind process through module dsmtli.drv. Both files must be available for the load and loadbind system calls.

ANR8281E (AS/400)Exit type EXIT exit name cannot be accessed.

Explanation: The *PGM object with the given exit name cannot be accessed by the server. The attempt fails because the server does not have the authority necessary to access the designated *PGM object.

System Action: The server does not process the command.

User Response: Reissue the command and specify a different exit name, or obtain the required authority to access the designated *PGM object from the security officer or the exit program owner before reissuing the command.

ANR8281W (Windows NT)HTTP driver unable to initialize due to error in BINDing to Port port, reason code reason code.

Explanation: While initializing HTTP communications, the server has failed to connect to a master TCP/IP socket on which to listen for clients. The reason code is the return code from the TCP/IP bind API.

System Action: Server operation continues, but the server cannot accept sessions from administrative clients using HTTP protocol.

User Response: Ensure that no other application is using the port number specified in the server options file with the PORT option. If TCP/IP is also in use for client sessions, ensure that the same port number is not specified for both TCP/IP and HTTP communications. This may be done by issuing the TCP/IP netstat -s command. If the server is brought down and then started immediately, you may be within the TCP/IP one minute timeout period for port reusage. Bring down the sever, wait one minute, and then restart the server. If that does not work, it may be necessary to restart Windows NT.

ANR8282W (AS/400)Exit type EXIT is not defined.

Explanation: The designated exit has not been defined to the server.

System Action: Server operation continues. The server issues additional error messages if this condition prevents the server from completing an operation.

User Response: Correct the problem with the specified exit program and use the UPDATE EXIT command to notify the server that the exit has been changed.

ANR8282I (HP-UX)SNMP driver ready for connection with subagent on port port number.

Explanation: The server can now accept sessions with SNMP subagents on the indicated port number.

System Action: Server operation continues.

User Response: None.

ANR8282I (Solaris)SNMP driver ready for connection with subagent on port port number.

Explanation: The server can now accept sessions with SNMP subagents on the indicated port number.

System Action: Server operation continues.

User Response: None.

ANR8282I (Windows NT)HTTPS driver ready for connection with clients on port port number.

Explanation: The server can now accept sessions with clients using the HTTPS protocol on the indicated port number.

System Action: Server operation continues.

User Response: None.

ANR8283W (AS/400)Exit type EXIT exit name cannot be located.

Explanation: The *PGM object with the specified exit name cannot be located on the AS/400.

System Action: Server operation continues. The server issues additional error messages when this condition prevents it from completing an operation.

User Response: Correct the problem with the specified exit program and use the UPDATE EXIT command to notify the server that the exit has been changed.

ANR8283W (HP-UX)SNMP driver unable to initialize due to error in BINDing to Port port, reason code reason code.

Explanation: While initializing TCP/IP communications, the server has failed to connect to a master TCP/IP socket on which to listen to SNMP subagents. The reason code is the return code from the TCP/IP bind API.

System Action: Server operation continues, but the server cannot accept sessions from SNMP subagents to run macro commands.

User Response: Ensure that no other application is using the port number specified in the server options file with the PORT option. If TCP/IP or HTTP is also in use for client sessions, ensure that the same port number is not specified for TCP/IP or HTTP communications and SNMP communications. This may be done by issuing the TCP/IP netstat command.

ANR8283W (Solaris)SNMP driver unable to initialize due to error in BINDing to Port port, reason code reason code.

Explanation: While initializing TCP/IP communications, the server has failed to connect to a master TCP/IP socket on which to listen to SNMP subagents. The reason code is the return code from the TCP/IP bind API.

System Action: Server operation continues, but the server cannot accept sessions from SNMP subagents to run macro commands.

User Response: Ensure that no other application is using the port number specified in the server options file with the PORT option. If TCP/IP or HTTP is also in use for client sessions, ensure that the same port number is not specified for TCP/IP or HTTP communications and SNMP communications.

ANR8283W (Windows NT)HTTPS driver unable to initialize due to error in BINDing to Port port, reason code reason code.

Explanation: While initializing HTTPS communications, the server has failed to connect to a master TCP/IP socket on which to listen for clients. The reason code is the return code from the TCP/IP bind API.

System Action: Server operation continues, but the server cannot accept sessions from administrative clients using HTTP protocol.

User Response: Ensure that no other application is using the port number specified in the server options file with the PORT option. If TCP/IP is also in use for client sessions, ensure that the same port number is not specified for both TCP/IP and HTTPS communications. This may be done by issuing the TCP/IP netstat -s command. If the server is brought down and then started immediately, you may be within the TCP/IP one minute timeout period for port reusage. Bring down the sever, wait one minute, and then restart the server. If that does not work, it may be necessary to restart Windows NT.

ANR8284E (AIX)The Shared Memory Communications Protocol could not initialize.

Explanation: The server was unable to initialize the Shared Memory Communications Protocol due to an error.

System Action: Server operation continues without Shared Memory Communications.

User Response: Examine previous error messages for the cause of the failure.

ANR8284W (AS/400)Exit type EXIT exit name cannot be accessed.

Explanation: The *PGM object with the given exit name cannot be accessed by the server. The attempt fails because the server does not have the authority necessary to access the designated *PGM object.

System Action: Server operation continues. The server issues additional error messages when this condition prevents it from completing an operation.

User Response: Correct the problem with the specified exit program and use the UPDATE EXIT command to notify the server that the exit has been changed.

ANR8284W (Windows NT)HTTPS driver unable to initialize due to error in secure data initialization, reason code reason code.

Explanation: While initializing HTTPS communications, the server has failed to initialize the secure data certificate information.

System Action: Server operation continues, but the server cannot accept sessions from administrative clients using HTTPS protocol.

User Response: Ensure the keyring file name and keyring file password are correct and that the password has not expired. Check for earlier SKIT messages which may indicate the real problem. Replace keyring if necessary and re-start the server.

ANR8285I (AIX)Shared Memory driver ready for connection with clients on port 1;port

Explanation: The server is now able to accept sessions with clients using the Shared Memory protocol.

System Action: Server operation continues.

User Response: None.

ANR8285E (AS/400)Exit type EXIT exit name returned a non-zero result: exit result.

Explanation: The specified exit returned a non-zero result to the server.

System Action: Server operation continues. The server issues additional error messages when this condition prevents it from completing an operation.

User Response: Evaluate the specified exit and the given result to determine if the result is appropriate. If necessary, correct any problems in the exit and use the UPDATE EXIT command to notify the server that the exit has been changed.

ANR8285I (HP-UX)Shared Memory driver ready for connection with clients on port port

Explanation: The server is now able to accept sessions with clients using the Shared Memory protocol.

System Action: Server operation continues.

User Response: None.

ANR8285I (Solaris)Shared Memory driver ready for connection with clients on port port

Explanation: The server is now able to accept sessions with clients using the Shared Memory protocol.

System Action: Server operation continues.

User Response: None.

ANR8285I (Windows NT)SNMP driver ready for connection with subagent on port port number.

Explanation: The server can now accept sessions with SNMP subagents on the indicated port number.

System Action: Server operation continues.

User Response: None.

ANR8286W (AIX)Unable to initialize Shared Memory driver - insufficient memory.

Explanation: Because the operating system rejected a memory allocation request, the server cannot start communications through the Shared Memory protocol.

System Action: Server operation continues, but the server cannot accept sessions from clients using the Shared Memory protocol.

User Response: Ensure that there is sufficient paging space for AIX. You may also use SMIT to determine if the number of applications is causing a memory shortage. It may be necessary to cut down on the maximum number of client sessions by changing the MAXSESSIONS option in the server options file.

ANR8286E (AS/400)Exit type EXIT exit name has overwritten server memory.

Explanation: The specified exit has performed an operation that has resulted in server memory being overwritten.

System Action: Server operation continues. The server issues additional error messages when this condition prevents it from completing an operation.

User Response: Correct the problem with the specified exit program and use the UPDATE EXIT command to notify the server that the exit has been changed.

ANR8286W (HP-UX)Unable to initialize Shared Memory driver - insufficient memory.

Explanation: Because the operating system rejected a memory allocation request, the server cannot start communications through the Shared Memory protocol.

System Action: Server operation continues, but the server cannot accept sessions from clients using the Shared Memory protocol.

User Response: Ensure that there is sufficient paging space for HP-UX. You may also use SAM to determine if the number of applications is causing a memory shortage. It may be necessary to cut down on the maximum number of client sessions by changing the MAXSESSIONS option in the server options file.

ANR8286W (Solaris)Unable to initialize Shared Memory driver - insufficient memory.

Explanation: Because the operating system rejected a memory allocation request, the server cannot start communications through the Shared Memory protocol.

System Action: Server operation continues, but the server cannot accept sessions from clients using the Shared Memory protocol.

User Response: Ensure that there is sufficient swap space for Solaris. It may be necessary to cut down on the maximum number of client sessions by changing the MAXSESSIONS option in the server options file.

ANR8286W (Windows NT)SNMP driver unable to initialize due to error in BINDing to Port port, reason code reason code.

Explanation: While initializing TCP/IP communications, the server has failed to connect to a master TCP/IP socket on which to listen to SNMP subagents. The reason code is the return code from the TCP/IP bind API.

System Action: Server operation continues, but the server cannot accept sessions from SNMP subagents to run macro commands.

User Response: Ensure that no other application is using the port number specified in the server options file with the PORT option. If TCP/IP or HTTP is also in use for client sessions, ensure that the same port number is not specified for TCP/IP or HTTP communications and SNMP communications. This may be done by issuing the TCP/IP netstat -s command. If the server is brought down and then started immediately, you may be within the TCP/IP one minute timeout period for port reusage. Bring down the sever, wait one minute, and then restart the server. If that does not work, it may be necessary to restart Windows NT.

ANR8287W (AIX)Unable to initialize Shared Memory driver - error creating acceptor socket. Reason code reason code.

Explanation: Because TCP/IP rejected a request for a socket on which to listen, the server cannot start communications through Shared Memory.

System Action: Server operation continues, but the server cannot accept sessions from clients using the Shared Memory protocol.

User Response: If TCP/IP is not started, use the HALT command from any server prompt to stop the server, and restart it.

ANR8287E (AS/400)Exception exception ID occurred in exit type EXIT exit name.

Explanation: The specified AS/400 exception has occurred in the given exit.

System Action: Server operation continues. The server issues additional error messages when this condition prevents it from completing an operation.

User Response: Evaluate the specified exception and the given exit to determine the actions necessary to correct the problem. If necessary, use the UPDATE EXIT command to notify the server that the exit or its attributes have been changed.

ANR8287W (HP-UX)Unable to initialize Shared Memory driver - error creating acceptor socket. Reason code reason code.

Explanation: Because TCP/IP rejected a request for a socket on which to listen, the server cannot start communications through Shared Memory.

System Action: Server operation continues, but the server cannot accept sessions from clients using the Shared Memory protocol.

User Response: If TCP/IP is not started, use the HALT command from any server prompt to stop the server, and restart it.

ANR8287W (Solaris)Unable to initialize Shared Memory driver - error creating acceptor socket. Reason code reason code.

Explanation: Because TCP/IP rejected a request for a socket on which to listen, the server cannot start communications through Shared Memory.

System Action: Server operation continues, but the server cannot accept sessions from clients using the Shared Memory protocol.

User Response: If TCP/IP is not started, use the HALT command from any server prompt to stop the server, and restart it.

ANR8288W (AIX)Unable to establish Shared Memory connection - insufficient memory.

Explanation: The server cannot accept a client session due to a memory allocation request failure.

System Action: Server operation continues, but the session request for this session fails.

User Response: Ensure that there is sufficient paging space for AIX. You may also use SMIT to determine if the number of applications is causing a memory shortage. You may also wish to cut down on the maximum number of sessions that the server can accept with the MAXSESSIONS option in the server options file.

ANR8288E (AS/400)Request number: Device device name is not defined in library library name.

Explanation: The designated device has been provided to the server by the MOUNT exit program, but the device is not defined in the given library.

System Action: Server operation continues, but this media operation fails.

User Response: If appropriate, use the DEFINE DRIVE command to place the device in the specified library. If appropriate, correct the problem with the MOUNT exit program and use the UPDATE EXIT command to notify the server that the exit has been changed.

ANR8288W (HP-UX)Unable to establish Shared Memory connection - insufficient memory.

Explanation: The server cannot accept a client session due to a memory allocation request failure.

System Action: Server operation continues, but the session request for this session fails.

User Response: Ensure that there is sufficient paging space for HP-UX. You may also use SAM to determine if the number of applications is causing a memory shortage. You may also wish to cut down on the maximum number of sessions that the server can accept with the MAXSESSIONS option in the server options file.

ANR8288W (Solaris)Unable to establish Shared Memory connection - insufficient memory.

Explanation: The server cannot accept a client session due to a memory allocation request failure.

System Action: Server operation continues, but the session request for this session fails.

User Response: Ensure that there is sufficient swap space for Solaris. You may also wish to cut down on the maximum number of sessions that the server can accept with the MAXSESSIONS option in the server options file.

ANR8289W (AIX)Shared Memory driver is terminating due to error in creating a new thread.

Explanation: The server cannot initialize due to the inability to create a new thread of execution.

System Action: Server operation continues, but Shared Memory communications is inoperative.

User Response: The most likely cause is a lack of memory. Ensure that there is sufficient paging space for AIX. You may also use SMIT to determine if the number of applications is causing a memory shortage. You may also wish to cut down on the maximum number of sessions that the server can accept with the MAXSESSIONS option in the server options file.

ANR8289E (AS/400)Request number: Volume volume name cannot be mounted on device device name.

Explanation: The designated device has been provided to the server by the MOUNT exit program, but the attributes of the designated volume do not match the attributes of the device. The volume cannot be mounted on the device.

System Action: Server operation continues, but this media operation fails.

User Response: Correct the problem with the MOUNT exit program and use the UPDATE EXIT command to notify the server that the exit has been changed.

ANR8289W (HP-UX)Shared Memory driver is terminating due to error in creating a new thread.

Explanation: The server cannot initialize due to the inability to create a new thread of execution.

System Action: Server operation continues, but Shared Memory communications is inoperative.

User Response: The most likely cause is a lack of memory. Ensure that there is sufficient paging space for HP-UX. You may also use SAM to determine if the number of applications is causing a memory shortage. You may also wish to cut down on the maximum number of sessions that the server can accept with the MAXSESSIONS option in the server options file.

ANR8289W (Solaris)Shared Memory driver is terminating due to error in creating a new thread.

Explanation: The server cannot initialize due to the inability to create a new thread of execution.

System Action: Server operation continues, but Shared Memory communications is inoperative.

User Response: The most likely cause is a lack of memory. Ensure that there is sufficient swap space for Solaris. You may also wish to cut down on the maximum number of sessions that the server can accept with the MAXSESSIONS option in the server options file.

ANR8290W (AIX)Error sending data through Shared Memory. Reason return code.

Explanation: The server experienced an error return code while sending data through shared memory. This may be a normal event if either side of the connection is abruptly ended.

System Action: The session is ended. Server operation continues.

User Response: If the session is ended as a result of intentionally stopping either the client or server, no response is required.

ANR8290E (AS/400)Request number: Device Device name is not available in library Library name.

Explanation: The designated device has been provided to the server by the MOUNT exit program, but the device is not available to carry out an attempted operation in the given library. The device can be unavailable for the following reasons. The device may already be in use by the server. The device may already be in use by another job or another system. The AS/400 status of the device may render it unavailable to the server. An additional message is issued by the server.

System Action: Server operation continues, but this media operation fails.

User Response: Correct the problem with the MOUNT exit program and use the UPDATE EXIT command to notify the server that the exit has been changed.

ANR8290W (HP-UX)Error sending data through Shared Memory. Reason return code.

Explanation: The server experienced an error return code while sending data through shared memory. This may be a normal event if either side of the connection is abruptly ended.

System Action: The session is ended. Server operation continues.

User Response: If the session is ended as a result of intentionally stopping either the client or server, no response is required.

ANR8290W (Solaris)Error sending data through Shared Memory. Reason return code.

Explanation: The server experienced an error return code while sending data through shared memory. This may be a normal event if either side of the connection is abruptly ended.

System Action: The session is ended. Server operation continues.

User Response: If the session is ended as a result of intentionally stopping either the client or server, no response is required.

ANR8290I (Windows NT)IPX/SPX driver ready for connection with clients on socket IPX socket number.

Explanation: The server is now able to accept sessions with clients using the IPX/SPX protocol on the indicated socket number.

System Action: Server operation continues.

User Response: None.

ANR8291W (AIX)Error receiving data through Shared Memory. Reason return code.

Explanation: The server experienced an error return code while receiving data through the Shared Memory protocol. This may be a normal event if either side of the connection is abruptly ended.

System Action: The session is ended. Server operation continues.

User Response: If the session is ended as a result of intentionally stopping either the client or server, no response is required.

ANR8291W (AS/400)Number of automated library slots (slots in use) exceeds license terms (slots licensed).

Explanation: The number of slots in use within automated libraries exceeds the licensed value.

System Action: The operation completes.

User Response: Contact your service representative to update license values for slots in automated libraries, or reduce the number of slots in use by issuing CHECKOUT LIBVOLUME commands as necessary.

ANR8291W (HP-UX)Error receiving data through Shared Memory. Reason return code.

Explanation: The server experienced an error return code while receiving data through the Shared Memory protocol. This may be a normal event if either side of the connection is abruptly ended.

System Action: The session is ended. Server operation continues.

User Response: If the session is ended as a result of intentionally stopping either the client or server, no response is required.

ANR8291W (Solaris)Error receiving data through Shared Memory. Reason return code.

Explanation: The server experienced an error return code while receiving data through the Shared Memory protocol. This may be a normal event if either side of the connection is abruptly ended.

System Action: The session is ended. Server operation continues.

User Response: If the session is ended as a result of intentionally stopping either the client or server, no response is required.

ANR8291W (Windows NT)Unable to bind to IPX/SPX master socket. Return code = return code.

Explanation: The server cannot initiate communications on the socket number designated for its use.

System Action: Server operation continues, but communications using the IPX/SPX protocol is inoperative.

User Response: Ensure that SPX has been configured to run on this system through the requester configuration program. Ensure that there is no other instance of the server running on the same system that is using the same socket number. This is likely to be the case if the return code is zero. Also ensure that the number of SPX sessions (as specified in your NET.CFG file) has not been exceeded through other applications using the IPX/SPX protocol.

ANR8292W (AIX)Session terminated when no data was read through Shared Memory.

Explanation: The server is unable to read data from Shared Memory. This may be a normal event if either side of the connection is abruptly ended.

System Action: The session is ended. Server operation continues.

User Response: If the session is ended as a result of intentionally stopping either the client or server, no response is required.

ANR8292E (AS/400)CHECKIN LIBVOLUME not permitted with current license terms.

Explanation: The CHECKIN LIBVOLUME command is not permitted because the current license terms do not allow it.

System Action: The command fails.

User Response: Contact your service representative to update license values for slots in automated libraries, or reduce the number of slots in use by issuing CHECKOUT LIBVOLUME commands as necessary.

ANR8292W (HP-UX)Session terminated when no data was read through Shared Memory.

Explanation: The server is unable to read data from Shared Memory. This may be a normal event if either side of the connection is abruptly ended.

System Action: The session is ended. Server operation continues.

User Response: If the session is ended as a result of intentionally stopping either the client or server, no response is required.

ANR8292W (Solaris)Session terminated when no data was read through Shared Memory.

Explanation: The server is unable to read data from Shared Memory. This may be a normal event if either side of the connection is abruptly ended.

System Action: The session is ended. Server operation continues.

User Response: If the session is ended as a result of intentionally stopping either the client or server, no response is required.

ANR8292W (Windows NT)IPX/SPX connection terminated - insufficient memory.

Explanation: The server cannot accept a client session due to a memory allocation request failure.

System Action: Server operation continues.

User Response: The most likely cause is a lack of memory. Ensure that there is sufficient space for the Windows NT paging file. Click on the system icon in the Windows NT control panel and then click on the virtual memory button. Refer to the online help for instructions on how to increase the amount of virtual memory. You may also wish to cut down on the maximum number of sessions that the server can accept with the MAXSESSIONS option in the server options file.

ANR8293W (AIX)Shared Memory driver unable to initialize due to socket initialization error.

Explanation: While initializing Shared Memory communications, the server failed to set up an interface with TCP/IP.

System Action: Server operation continues, but the server cannot accept sessions from clients using the Shared Memory protocol.

User Response: Ensure that TCP/IP has been started and is active on your system. You may issue the TCP/IP ping command to your own address to verify that TCP/IP is both started and active.

ANR8293E (AS/400)This server is not licensed to support the device type device type. Device Support Module module number is required.

Explanation: A DEFINE DRIVE command or a volume mount operation cannot be processed because the server is not licensed to support the required device type.

System Action: The operation fails.

User Response: Contact your service representative to update the server license terms so that support for the required device type is enabled.

ANR8293W (HP-UX)Shared Memory driver unable to initialize due to socket initialization error.

Explanation: While initializing Shared Memory communications, the server failed to set up an interface with TCP/IP.

System Action: Server operation continues, but the server cannot accept sessions from clients using the Shared Memory protocol.

User Response: Ensure that TCP/IP has been started and is active on your system. You may issue the TCP/IP ping command to your own address to verify that TCP/IP is both started and active.

ANR8293W (Solaris)Shared Memory driver unable to initialize due to socket initialization error.

Explanation: While initializing Shared Memory communications, the server failed to set up an interface with TCP/IP.

System Action: Server operation continues, but the server cannot accept sessions from clients using the Shared Memory protocol.

User Response: Ensure that TCP/IP has been started and is active on your system. You may issue the TCP/IP ping command to your own address to verify that TCP/IP is both started and active.

ANR8293W (Windows NT)IPX/SPX driver unable to initialize due to error in LISTENing on the master socket, return code = return code.

Explanation: While attempting to listen for session requests from clients using IPX/SPX, the server encountered an error.

System Action: Server operation continues, but the server cannot accept additional sessions from clients using the IPX/SPX protocol.

User Response: Ensure that IPX/SPX is still running properly and that it has not been intentionally or unintentionally stopped. This may be done by using the getipxad command to determine if an endpoint can still be opened and bound; also determine if you can still connect to a NetWare server.

ANR8294W (AIX)Shared Memory session unable to initialize.

Explanation: While initializing a Shared Memory communications session, an error occurred during initial setup.

System Action: Server operation continues, but the session is terminated.

User Response: Contact your service representative for assistance in resolving the error.

ANR8294E (AS/400)This server is not licensed to support library device name. Device Support Module module number is required.

Explanation: Either a DEFINE LIBRARY command, a volume mount operation, or library initialization cannot be processed because the server is not licensed to support the given library.

System Action: The operation fails.

User Response: Contact your service representative to update the server license terms so that support for the given library device is enabled.

ANR8294W (HP-UX)Shared Memory session unable to initialize.

Explanation: While initializing a Shared Memory communications session, an error occurred during initial setup.

System Action: Server operation continues, but the session is terminated.

User Response: Contact your service representative for assistance in resolving the error.

ANR8294W (Solaris)Shared Memory session unable to initialize.

Explanation: While initializing a Shared Memory communications session, an error occurred during initial setup.

System Action: Server operation continues, but the session is terminated.

User Response: Contact your service representative for assistance in resolving the error.

ANR8294W (Windows NT)Unable to establish IPX/SPX connection - accept error. Return code = tli error.

Explanation: The server cannot accept a client session due to a failure in accepting the connection from IPX/SPX.

System Action: Server operation continues, but this session request fails.

User Response: Ensure that SPX has been configured to run on this system through the requester configuration program. Ensure that there is no other instance of the server running on the same system that is using the same socket number. Also ensure that the number of SPX sessions has not been exceeded through other applications using the IPX/SPX protocol, such as NetWare applications.

ANR8295W (AIX)Shared Memory driver unable to initialize due to error in BINDing to Port port, reason code reason code.

Explanation: While initializing Shared Memory communications, the server failed to connect to a master socket on which to listen for clients. The reason code is the return code from the TCP/IP bind API.

System Action: Server operation continues, but the server cannot accept sessions from clients using the Shared Memory protocol.

User Response: Ensure that no application is using the port number specified in the server options file with the SHMPORT option by issuing the TCP/IP netstat command. If the server was brought down and client sessions were active, it may be necessary to terminate the client sessions on the client systems before the port can be freed.

ANR8295E (AS/400)Command: Current license terms do not permit this operation.

Explanation: The specified command failed because the current license terms do not permit it.

System Action: The operation fails.

User Response: Contact your service representative to update the server license terms so that the requested operation can be processed.

ANR8295W (HP-UX)Shared Memory driver unable to initialize due to error in BINDing to Port port, reason code reason code.

Explanation: While initializing Shared Memory communications, the server failed to connect to a master socket on which to listen for clients. The reason code is the return code from the TCP/IP bind API.

System Action: Server operation continues, but the server cannot accept sessions from clients using the Shared Memory protocol.

User Response: Ensure that no application is using the port number specified in the server options file with the SHMPORT option by issuing the TCP/IP netstat command. If the server was brought down and client sessions were active, it may be necessary to terminate the client sessions on the client systems before the port can be freed.

ANR8295W (Solaris)Shared Memory driver unable to initialize due to error in BINDing to Port port, reason code reason code.

Explanation: While initializing Shared Memory communications, the server failed to connect to a master socket on which to listen for clients. The reason code is the return code from the TCP/IP bind API.

System Action: Server operation continues, but the server cannot accept sessions from clients using the Shared Memory protocol.

User Response: Ensure that no application is using the port number specified in the server options file with the SHMPORT option by issuing the TCP/IP netstat command. If the server was brought down and client sessions were active, it may be necessary to terminate the client sessions on the client systems before the port can be freed.

ANR8295W (Windows NT)Error sending data on session session number. Reason return code.

Explanation: The server experiences an error return code from IPX/SPX while sending data on the indicated session. This may be a normal event if either side of the connection is abruptly ended.

System Action: The session is ended. Server operation continues.

User Response: If the session is ended as a result of intentionally stopping either the client or server, no response is required. Otherwise, ensure that IPX/SPX is still active.

ANR8296W (AIX)Shared Memory driver unable to initialize due to error in LISTENing on the specified Port, reason code reason code.

Explanation: While attempting to listen for session requests from clients using TCP/IP, TCP/IP returns an error. The reason code is the return code from the TCP/IP listen API.

System Action: Server operation continues, but the server cannot accept additional sessions from clients using the Shared Memory protocol.

User Response: Ensure that TCP/IP is running properly by issuing the TCP/IP netstat -s and ping commands to other nodes on your network. It may be possible to bring the server down and restart it to allow additional client sessions to start.

ANR8296E (AS/400)Selecting swap volume to be checked out of library library name.

Explanation: A CHECKIN LIBVOL command was issued for a library that has no empty slots to hold the new cartridge. The SWAP=YES parameter was included in the command.

System Action: A CHECKOUT LIBVOL command will be automatically issued, specifying either a scratch volume or, if there are none, a volume with the lowest number of mounts.

User Response: When the CHECKOUT LIBVOL command completes, remove the swapped volume from the library and store it in a safe place. Issue a REPLY command to tell the server that the volume has been removed. The volume can be introduced back into the library with the CHECKIN LIBVOLUME command.

ANR8296W (HP-UX)Shared Memory driver unable to initialize due to error in LISTENing on the specified Port, reason code reason code.

Explanation: While attempting to listen for session requests from clients using TCP/IP, TCP/IP returns an error. The reason code is the return code from the TCP/IP listen API.

System Action: Server operation continues, but the server cannot accept additional sessions from clients using the Shared Memory protocol.

User Response: Ensure that TCP/IP is running properly by issuing the TCP/IP netstat -s and ping commands to other nodes on your network. It may be possible to bring the server down and restart it to allow additional client sessions to start.

ANR8296W (Solaris)Shared Memory driver unable to initialize due to error in LISTENing on the specified Port, reason code reason code.

Explanation: While attempting to listen for session requests from clients using TCP/IP, TCP/IP returns an error. The reason code is the return code from the TCP/IP listen API.

System Action: Server operation continues, but the server cannot accept additional sessions from clients using the Shared Memory protocol.

User Response: Ensure that TCP/IP is running properly by issuing the TCP/IP netstat -s and ping commands to other nodes on your network. It may be possible to bring the server down and restart it to allow additional client sessions to start.

ANR8297W (AIX)Shared Memory driver is terminating due to error in accepting a new session, reason code reason code.

Explanation: While attempting to accept a session request from a client using the Shared Memory protocol, TCP/IP returns an error. The reason code is the return code from the TCP/IP accept API.

System Action: Server operation continues, but the server cannot accept additional sessions from clients using the Shared Memory protocol.

User Response: Ensure that TCP/IP is running properly. This may be done by issuing the TCP/IP netstat -s and ping commands to other nodes on your network. It may be possible to bring the server down and restart it to allow additional client sessions to start.

ANR8297I (AS/400)Request number: device type volume volume name is required for use in library library name; CHECKIN LIBVOLUME required within time limit minutes.

Explanation: A mount request has been made for a volume that is defined in a storage pool, but which is currently checked out of the given library.

System Action: The server waits until it detects that the volume has been checked into the library, or the time limit expires.

User Response: Obtain the required volume, and insert it into the library by issuing a CHECKIN LIBVOLUME command. Use the SWAP=YES option of the CHECKIN LIBVOLUME command if the library is currently full. This process allows the server to select an appropriate volume to be swapped out to make room for the required volume.

ANR8297W (HP-UX)Shared Memory driver is terminating due to error in accepting a new session, reason code reason code.

Explanation: While attempting to accept a session request from a client using the Shared Memory protocol, TCP/IP returns an error. The reason code is the return code from the TCP/IP accept API.

System Action: Server operation continues, but the server cannot accept additional sessions from clients using the Shared Memory protocol.

User Response: Ensure that TCP/IP is running properly. This may be done by issuing the TCP/IP netstat -s and ping commands to other nodes on your network. It may be possible to bring the server down and restart it to allow additional client sessions to start.

ANR8297W (Solaris)Shared Memory driver is terminating due to error in accepting a new session, reason code reason code.

Explanation: While attempting to accept a session request from a client using the Shared Memory protocol, TCP/IP returns an error. The reason code is the return code from the TCP/IP accept API.

System Action: Server operation continues, but the server cannot accept additional sessions from clients using the Shared Memory protocol.

User Response: Ensure that TCP/IP is running properly. This may be done by issuing the TCP/IP netstat -s and ping commands to other nodes on your network. It may be possible to bring the server down and restart it to allow additional client sessions to start.

ANR8298I (AS/400)Request number: Mount of device type volume volume name mount mode waiting for completion of exit type EXIT exit name.

Explanation: The server is waiting for the specified exit program to complete.

System Action: The server waits for the exit to complete.

User Response: None.

ANR8299I (AS/400)Request number: Waiting for mount of device type volume volume name mount mode on drive drive name in library library name.

Explanation: The server is waiting for the specified volume mount to complete.

System Action: The server waits for the mount to complete.

User Response: None.

ANR8300EI/O error on library library name (OP=internal code, CC=internal code, KEY=internal code, ASC=internal code, ASCQ=internal code, SENSE=sense data, Description=error description). Refer to Appendix B in the 'Messages' manual for recommended action.

Explanation: An I/O error has occurred while operating on the designated library device.

System Action: The operation fails.

User Response: Ensure that the DEVICE parameter associated with the library was identified correctly in the DEFINE LIBRARY command, and that the library device is currently powered on and ready. If the library has an access door, make sure it is closed. The drive or library reference manual provided with the device usually contain tables that explain the values of the KEY, ASC, and ASCQ fields. If the problem persists, contact your service representative and provide the internal code values and sense data from this message.

ANR8300I (AS/400)Request number: Select a device type device in library library name within time limit minutes.

Explanation: The server requires the selection of an appropriate device in the designated library within the specified time limit. See associated messages for a list of device names.

System Action: The server waits for a device to be selected.

User Response: Choose a device from the list within the time limit. Use the REPLY command to communicate the device name to the server.

ANR8301EI/O error on library library name (OP=internal code, SENSE=internal code).

Explanation: An I/O error has occurred while operating on the designated library device.

System Action: The operation fails.

User Response: Ensure that the DEVICE parameter associated with the library was identified correctly in the DEFINE LIBRARY command, and that the library device is currently powered on and ready. If the library has an access door, make sure it is closed. If the problem persists, contact your service representative and provide the internal code values from this message.

ANR8301E (AS/400)Error on library library name: MLD message.

Explanation: An error has occurred while operating on the designated library device.

System Action: The operation fails.

User Response: Ensure that the MLD parameter associated with the library has been identified correctly in the DEFINE LIBRARY command, and that the library device is currently powered on and ready. If the library has an access door, make sure it is closed. If the problem persists, contact your service representative and provide the values from this message. The values can be found in Media Library Device Driver for Application System/400, GC35-0153.

ANR8302EI/O error on drive drive name (OP=internal code, CC=internal code, KEY=internal code, ASC=internal code, ASCQ=internal code, SENSE=sense data, Description=error description). Refer to Appendix B in the 'Messages' manual for recommended action.

Explanation: An I/O error has occurred while operating on the designated drive.

System Action: The operation fails.

User Response: Ensure that the DEVICE parameter associated with the drive was identified correctly in the DEFINE DRIVE command, and that the device is currently powered on and ready. The drive or library reference manual provided with the device usually contain tables that explain the values of the KEY, ASC, and ASCQ fields. If the problem persists, contact your service representative and provide the internal code values and sense data from this message.

ANR8302I (AS/400)Request number: Mount device type volume volume name mount mode on an appropriate device in library library name within time limit minutes.

Explanation: The server requires that the specified volume be mounted on an appropriate device in the designated library. See associated messages for a list of device names. The value of volume name can be either a specific volume or a nonspecific volume (scratch). If volume name is SCRATCH, EXPORT.n, or DUMP.n, you should mount a scratch volume. The value 'n' denotes the sequence number of the scratch volume being requested for DUMP DB or EXPORT operations.

System Action: The server waits for the volume to be mounted.

User Response: Mount the volume on an appropriate device in the specified library within the time limit. Use the REPLY command to communicate the device name to the server.

ANR8303EI/O error on drive drive name (OP=internal code, SENSE=internal code).

Explanation: An I/O error has occurred while operating on the designated drive.

System Action: The operation fails.

User Response: Ensure that the DEVICE parameter associated with the drive was identified correctly in the DEFINE DRIVE command, and that the device is currently powered on and ready. If the problem persists, contact your service representative and provide the internal code values from this message.

ANR8303I (AS/400)Request number: device list

Explanation: This message provides a list of devices that have the necessary attributes to satisfy the associated mount request.

System Action: The server lists all of the devices defined in the given library.

User Response: None.

ANR8304ETime out error on drive drive name in library library name.

Explanation: A time out condition occurred while waiting for the given drive to become ready so that automated library operations could be performed.

System Action: The operation fails.

User Response: Ensure that the DEVICE parameter associated with the drive was identified correctly in the DEFINE DRIVE command, and that the device is currently powered on and ready.

ANR8304E (AS/400)Time-out error on drive drive name in library library name.

Explanation: A time-out condition has occurred while waiting for the specified drive to become ready so that automated library operations can be performed.

System Action: The operation fails.

User Response: Ensure that the DEVICE parameter associated with the drive has been identified correctly in the DEFINE DRIVE command, and that the device is currently powered on and ready.

ANR8305ELibrary library name is not ready or not operational.

Explanation: The specified automated library device is either not ready or not in an operational state.

System Action: Initialization of the library device fails.

User Response: Ensure that the library is powered on and ready for automated operations. Further initialization attempts for the given library will usually be postponed until the next attempt is made to access the library for an automated operation. During server startup, however, initialization may be retried after a short waiting period.

ANR8305E (AS/400)Command: Category already exists.

Explanation: The category cannot be created because it already exists.

System Action: The server does not process the command.

User Response: None.

ANR8306IRequest number: Insert device type volume volume name mount mode into the slot with element number slot element of library library name within time limit minutes; issue 'REPLY' along with the request ID when ready.

Explanation: A CHECKIN LIBVOLUME or a LABEL LIBVOLUME command is in progress, and the specified volume is needed. The server expects the volume to be inserted into the slot with the specified element number of the given library within the time limit specified in the message. For the slot and element number diagram of your library, refer to the documentation provided with the current ptf level or refer to the Administrator's Guide for your release and platform.

System Action: The server waits until a REPLY command is issued, or until the time limit expires.

User Response: Insert the volume into the slot and issue a REPLY command, along with the request ID, to tell the server that the volume has been inserted.

ANR8306E (AS/400)Command: Device device name is not defined in library library name.

Explanation: The designated device has not been defined in the given library.

System Action: The server does not process the command.

User Response: Reissue the command and specify a different device name. If appropriate, use the DEFINE DRIVE command to place the device in the specified library before reissuing the command.

ANR8307IRequest number: Remove device type volume volume name from slot with element number slot name of library library name; issue 'REPLY' along with the request ID when ready.

Explanation: A CHECKOUT LIBVOLUME command has completed. You can remove the volume from the slot with the specified element number and store it outside the library. For the slot and element number diagram of your library, refer to the documentation provided with the current ptf level or refer to the Administrator's Guide manual for your release and platform.

System Action: The server waits until a REPLY command is issued.

User Response: Remove the volume from the slot and store it in a safe place. Issue a REPLY command, along with the request ID, to tell the server that the volume has been removed. The volume can be returned to the library with the CHECKIN LIBVOLUME command.

ANR8307E (AS/400)Command: Volume volume name cannot be mounted on device device name.

Explanation: The attributes of the designated volume do not match the attributes of the specified device. The volume cannot be mounted on the device.

System Action: The server does not process the command.

User Response: Reissue the command and specify a different device name.

ANR8308IRequest number: device type volume volume name is required for use in library library name; CHECKIN LIBVOLUME required within time limit minutes.

Explanation: A mount request has been made for a volume that is defined in a storage pool, but which is currently checked out of the given library.

System Action: The server waits until it detects that the volume has been checked into the library, or the time limit expires.

User Response: Obtain the required volume, and insert it into the library by issuing a CHECKIN LIBVOLUME command. Use the SWAP=YES option of the CHECKIN LIBVOLUME command if the library is currently full; this process allows the server to select an appropriate volume to be swapped out in order to make room for the required volume.

ANR8308E (AS/400)Request number: Incorrect volume inserted into library library name.

Explanation: The user has inserted the wrong volume into the indicated library.

System Action: The volume is ejected, and the server continues to wait for the requested volume to be inserted.

User Response: Ensure that the requested volume is inserted properly into the designated library.

ANR8309EMount attempt failed - library library name is not defined.

Explanation: An attempt has been made to mount a volume, but the attempt fails because the specified library is not defined.

System Action: The operation fails.

User Response: Ensure that the LIBRARY attribute of the device class associated with the mount operation identifies a defined library. If not, correct the value of the LIBRARY attribute, or define the specified library and retry the operation.

ANR8309E (AS/400)Mount attempt failed - library library name is not defined.

Explanation: An attempt has been made to mount a volume, but the attempt fails because the specified library is not defined.

System Action: The operation fails.

User Response: Ensure that the LIBRARY parameter of the device class associated with the mount operation identifies a defined library. If not, correct the value of the LIBRARY parameter or define the specified library.

ANR8310EAn I/O error occurred while accessing library library name.

Explanation: An I/O error occurs while accessing the designated library.

System Action: The operation fails.

User Response: Ensure that the DEVICE parameter associated with the library is identified correctly in the DEFINE LIBRARY command, and that the library is currently powered on and ready. If the library has an access door, make sure it is closed. After checking and correcting these potential problems, retry the operation.

ANR8310E (AS/400)An I/O error occurred while accessing library library name.

Explanation: An I/O error occurs while accessing the designated library.

System Action: The operation fails.

User Response: Ensure that the MLD parameter associated with the library is identified correctly in the DEFINE LIBRARY command, and that the library is currently powered on and ready. If the library has an access door, make sure it is closed. After checking and correcting these potential problems, try the operation again.

ANR8311EAn I/O error occurred while accessing drive drive name for low-level operation operation, errno = drive errno.

Explanation: An I/O error occurs while performing the operation on the specified drive.

System Action: The operation fails.

User Response: Ensure that the DEVICE parameter associated with the drive is identified correctly in the DEFINE DRIVE command, and that the drive is currently powered on and ready. After checking and correcting these potential problems, retry the operation.

ANR8311E (AS/400)An I/O error occurred while accessing drive drive name.

Explanation: An I/O error occurs while accessing the specified drive.

System Action: The operation fails.

User Response: Ensure that the DEVICE parameter associated with the drive is identified correctly in the DEFINE DRIVE command, and that the drive is currently powered on and ready. After checking and correcting these potential problems, try the operation again.

ANR8312EVolume volume name could not be located in library library name.

Explanation: The designated volume cannot be found at its expected location in the given library.

System Action: The operation fails.

User Response: Perform an AUDIT LIBRARY operation on the designated library, which forces the server to reevaluate its inventory information for volumes in the library.

ANR8312E (AS/400)Volume volume name could not be located in library library name.

Explanation: The designated volume cannot be found at its expected location in the specified library.

System Action: The operation fails.

User Response: Perform an AUDIT LIBRARY operation on the designated library, and force the server to reevaluate its inventory information for volumes in the library.

ANR8313EVolume volume name is not present in library library name.

Explanation: A mount request is made for the given volume in the specified library, but the volume is not currently checked into the library.

System Action: The mount operation fails. If the volume is being mounted for storage pool I/O (as opposed to import/export I/O), its ACCESS attribute is changed to UNAVAILABLE to prevent further mount requests.

User Response: Issue a CHECKIN LIBVOLUME command to return the volume into the library, and update the volumes ACCESS attribute to READONLY or READWRITE using the UPDATE VOLUME command. Retry the mount request.

ANR8313E (AS/400)Volume volume name is not present in library library name.

Explanation: A mount request is made for the given volume in the specified library, but the volume is not currently checked into the library.

System Action: The mount operation fails. If the volume is being mounted for storage pool I/O (as opposed to import/export I/O), its ACCESS attribute is changed to UNAVAILABLE to prevent further mount requests.

User Response: Issue a CHECKIN LIBVOLUME command to introduce the volume into the library, and then update the volume ACCESS attribute to READONLY or READWRITE by using the UPDATE VOLUME command.

ANR8314ELibrary library name is full.

Explanation: A library operation fails because all of the library's storage locations are occupied.

System Action: The operation fails.

User Response: Issue a CHECKOUT LIBVOLUME command to make room in the library. Retry the library operation.

ANR8314E (AS/400)Library library name is full.

Explanation: An attempt has been made to add a volume to the library. The operation fails because all of the library's storage locations are occupied.

System Action: The operation fails.

User Response: Issue a CHECKOUT LIBVOLUME command to make room in the library.

ANR8315ECommand: The device type of drive drive name is not supported in library type libraries.

Explanation: Drives of the type identified in the command are not supported in the given type of library.

System Action: The command is not processed.

User Response: Determine whether the drive and library combination is supported by the installed level of the server. If so, contact your service representative.

ANR8315E (AS/400)Command: The device type of drive drive name is not supported in library type libraries.

Explanation: Drives of the type identified in the command are not supported in the given type of library.

System Action: The server does not process the command.

User Response: Use a supported type of drive.

ANR8316ESelecting swap volume to be checked out of library library name.

Explanation: A CHECKIN LIBVOL command was issued for a library that has no empty slots to hold the new cartridge. The SWAP=YES parameter was included in the command.

System Action: A CHECKOUT LIBVOL command will be automatically be issued, specifying either a scratch volume or, if there are none, a volume with the lowest number of mounts.

User Response: Use a supported type of drive. volume from the library and store it in a safe place. Issue a REPLY command to tell the server that the volume has been removed. The volume can be introduced back into the library with the CHECKIN LIBVOLUME command.

ANR8316E (AS/400)Command: The drive drive name is NOT located in the Media Library Device associated with library library name.

Explanation: The drive identified in the command is not located in the Media Library Device associated with the given library.

System Action: The server does not process the command.

User Response: Use a drive located in the Media Library Device.

ANR8317IThe volume in device type drive drive name must be manually ejected.

Explanation: This device type does not automatically eject the volume when it is dismounted and requires that the volume be manually ejected from the drive.

System Action: None.

User Response: Physically eject the volume from the drive.

ANR8317E (AS/400)Unable to open file filespec - insufficient authority.

Explanation: An attempt has been made to open the specified file, but the attempt failed because the server does not have the authority necessary to access the file. This error may occur if the server does not have the proper authority to create the given member in the specified file.

System Action: The operation fails.

User Response: Obtain the necessary authority from the security officer or the file owner and try the operation again.

ANR8318IRequest number: Mount side side of device type volume volume name mount mode in drive drive name of library library name within time limit</ mv> minutes.

Explanation: The server requires that the specified volume be mounted as requested. Since the volume is two-sided, this message specifies which side (A or B) is needed by the server for I/O operations.

System Action: The server waits for the volume to be mounted.

User Response: Mount the volume in the specified drive.

ANR8318E (AS/400)Command: Device device name is not available in library library name.

Explanation: The designated device is not available to carry out an attempted operation in the given library. The device can be unavailable for the following reasons. The device may already be in use by the server. The device may already be in use by another job or another system. The AS/400 status of the device may render it unavailable to the server. An additional message will have been issued by the server.

System Action: The server does not process the command.

User Response: If another device is available in the library, reissue the command using that device name. If there are idle volumes mounted in the library, use the DISMOUNT VOLUME command to free a device, and then reissue the command using that device name. If the MOUNTWAIT value of the device class permits it, wait until a device is available in the library, and then reissue the command using that device name.

ANR8319IRequest number: Insert device type volume volume name mount mode into library library name within time limit minute(s).

Explanation: A CHECKIN LIBVOLUME command is in progress, and the specified volume is needed. The server expects the volume to be inserted into the library with the convenience I/O station mechanism.

System Action: The server waits until the volume is in the library, or until the time limit expires.

User Response: Insert the specified volume into the library. If the volume has already been inserted into the library, no user action is necessary.

ANR8319I (AS/400)Request number: Insert device type volume volume name mount mode into library library name within time limit minutes.

Explanation: A CHECKIN LIBVOLUME command is in progress, and the specified volume is needed. The server expects the volume to be inserted into the library with the convenience I/O station mechanism.

System Action: The server waits until the volume is in the library, or until the time limit expires.

User Response: Insert the volume into the library. If the volume has already been inserted into the library, no user action is necessary.

ANR8320IRequest number: Insert device type volume volume name mount mode in drive drive name of library library name within time limit minute(s); issue 'REPLY ' along with the request ID when ready.

Explanation: A CHECKIN LIBVOLUME or a LABEL LIBVOLUME command is in progress, and the specified volume is needed. The server expects the volume to be inserted in the designated drive of the given library within the time limit specified in the message.

System Action: The server waits until a REPLY command is issued, or until the time limit expires.

User Response: Insert the volume into the drive, and then issue a REPLY command, along with the request ID, to tell the server that the volume has been inserted.

ANR8320I (AS/400)Request number: Insert device type volume volume name mount mode in drive drive name of library library name within time limit minutes; Issue 'REPLY' when ready.

Explanation: A CHECKIN LIBVOLUME command is in progress, and the specified volume is needed. The server expects the volume to be inserted in the designated drive of the given library within the time limit specified in the message.

System Action: The server waits until a REPLY command is issued, or until the time limit expires.

User Response: Insert the volume into the drive, and then issue a REPLY command to tell the server that the volume has been inserted.

ANR8321IRequest number: Remove device type volume volume name from drive drive name of library library name; issue 'REPLY' along with the request ID when ready.

Explanation: A CHECKOUT LIBVOLUME or a LABEL LIBVOLUME command has completed. You can remove the specified volume from the designated drive and store it outside the library.

System Action: The server waits until a REPLY command is issued.

User Response: Remove the volume from the drive and store it in a safe place. Issue a REPLY command, along with the request ID, to tell the server that the volume has been removed. The volume can be returned to the library with the CHECKIN LIBVOLUME command.

ANR8321I (AS/400)Request number: Remove device type volume volume name from drive drive name of library library name; Issue 'REPLY' when ready.

Explanation: A CHECKOUT LIBVOLUME command has completed. You can remove the specified volume from the designated drive and store it outside the library.

System Action: The server waits until a REPLY command is issued.

User Response: Remove the volume from the drive and store it in a safe place. Then issue a REPLY command to tell the server that the volume has been removed. The volume can be checked back into the library with the CHECKIN LIBVOLUME command.

ANR8322IRequest number: Remove device type volume volume name from entry/exit port of library library name; issue 'REPLY' along with the request ID when ready.

Explanation: A CHECKOUT LIBVOLUME command has completed. You can remove the specified volume from the entry/exit port of the given library and store it elsewhere.

System Action: The server waits until a REPLY command is issued.

User Response: Remove the volume from the library and store it in a safe place. Issue a REPLY command, along with the request ID, to tell the server that the volume has been removed. The volume can be returned to the library with the CHECKIN LIBVOLUME command.

ANR8322I (AS/400)Request number: Remove device type volume volume name from entry/exit port of library library name; Issue 'REPLY' when ready.

Explanation: A CHECKOUT LIBVOLUME command has completed. You can remove the specified volume from the entry/exit port of the given library and store it elsewhere.

System Action: The server waits until a REPLY command is issued.

User Response: Remove the volume from the library and store it in a safe place. Then issue a REPLY command to tell the server that the volume has been removed. The volume can be checked back into the library with the CHECKIN LIBVOLUME command.

ANR8323IRequest number: Insert device type volume volume name mount mode into entry/exit port of library library name within time limit minute(s); issue 'REPLY' along with the request ID when ready.

Explanation: A CHECKIN LIBVOLUME or a LABEL LIBVOLUME cmmand is in progress, and the specified volume is needed. Mount the volume in the entry/exit port of the given library within the time limit specified in the message.

System Action: The server waits until a REPLY command is issued, or until the time limit expires.

User Response: Insert the volume into the library's entry/exit port; and issue a REPLY command, along with the request ID, to tell the server that the volume has been inserted.

ANR8323I (AS/400)Request number: Insert device type volume volume name mount mode into entry/exit port of library library name within time limit minutes; Issue 'REPLY' when ready.

Explanation: A CHECKIN LIBVOLUME command is in progress, and the specified volume is needed. Mount the volume in the entry/exit port of the given library within the time limit specified in the message.

System Action: The server waits until a REPLY command is issued, or until the time limit expires.

User Response: Insert the volume into the library's entry/exit port, and then issue a REPLY command to tell the server that the volume has been inserted.

ANR8324IDevice type volume volume name is expected to be mounted (mount mode).

Explanation: The specified volume is expected to be mounted in the near future so the server can access it for reading or writing.

System Action: None.

User Response: If the volume is stored offline, retrieve it so that it is readily accessible when the server requests that it be mounted.

ANR8324I (AS/400)Device type volume volume name is expected to be mounted (mount mode).

Explanation: The specified volume is expected to be mounted in the near future so that the server can access it for reading or writing.

System Action: None.

User Response: If the volume is stored offline, retrieve it so that it is readily accessible when the server requests that it be mounted.

ANR8325IDismounting volume volume name - mount retention period minute mount retention expired.

Explanation: The specified volume is dismounted because the given mount retention period has expired.

System Action: The volume is dismounted.

User Response: None.

ANR8325I (AS/400)Dismounting volume volume name - mount retention period minute mount retention expired.

Explanation: The specified volume is dismounted because the given mount retention period has expired.

System Action: The volume is dismounted.

User Response: None.

ANR8326IRequest number: Mount device type volume volume name mount mode in drive drive name of library library name within time limit minutes.

Explanation: If the volume name includes the names EXP, IMP, DUMP, or DBBK, the request is for a scratch volume.

System Action: The server waits for the volume to be mounted.

User Response: Mount the volume in the specified drive.

ANR8326I (AS/400)Request number: Mount device type volume volume name mount mode in drive drive name of library library name within time limit minutes.

Explanation: The server requires that the specified volume be mounted as requested. The value of volume name can be either a specific volume or a nonspecific volume (scratch). If volume name is SCRATCH, EXPORT.n, or DUMP.n, you should mount a scratch volume. The value 'n' denotes the sequence number of the scratch volume being requested for DUMP DB or EXPORT operations.

System Action: The server waits for the volume to be mounted.

User Response: Mount the volume in the specified drive within the time limit. If this is a request for a SCRATCH mount, use the REPLY command to indicate to the server that a volume has been mounted.

ANR8327ECommand: Cannot cancel request request number.

Explanation: The request, whose number is specified by the given command, cannot be canceled. The requested operation must be completed.

System Action: The cancel request command is not processed.

User Response: Proceed with the requested operation.

ANR8327E (AS/400)Command: Cannot cancel request request number.

Explanation: The request, whose number is specified by the given command, cannot be canceled. The requested operation must be completed.

System Action: The CANCEL REQUEST command is not processed.

User Response: Proceed with the requested operation.

ANR8328IRequest number: device type volume volume name mounted in drive drive name.

Explanation: The server verifies that a requested volume has been mounted properly in the given drive.

System Action: The volume is accessed for reading or writing, or both.

User Response: None.

ANR8328I (AS/400)Request number: device type volume volume name mounted in drive drive name.

Explanation: The server verifies that a requested volume has been mounted properly in the given drive.

System Action: The volume can be accessed for reading or writing, or both.

User Response: None.

ANR8329IDevice type volume volume name is mounted mount mode in drive drive name, status: IDLE.

Explanation: In response to a QUERY MOUNT command, the server indicates that the given volume is mounted in the specified drive. The volume is currently idle, meaning no active operations are being performed. If the volume remains in the idle state for the amount of time specified by the device class mount retention period, it will be automatically dismounted.

System Action: None.

User Response: None.

ANR8329I (AS/400)Device type volume volume name is mounted mount mode in drive drive name, status: IDLE.

Explanation: In response to a QUERY MOUNT command, the server indicates that the given volume is mounted in the specified drive. The volume is currently idle, that is, no active operations are being performed. If the volume remains in the idle state for the amount of time specified by the device class mount retention period, it is automatically dismounted.

System Action: None.

User Response: None.

ANR8330IDevice type volume volume name is mounted mount mode in drive drive name, status: IN USE.

Explanation: In response to a QUERY MOUNT command, the server indicates that the given volume is mounted in the specified drive. The volume is currently in use, meaning that read or write operations, or both, are being performed.

System Action: None.

User Response: None.

ANR8330I (AS/400)Device type volume volume name is mounted mount mode in drive drive name, status: IN USE.

Explanation: In response to a QUERY MOUNT command, the server indicates that the given volume is mounted in the specified drive. The volume is currently in use, meaning that read or write operations, or both, are being performed.

System Action: None.

User Response: None.

ANR8331IDevice type volume volume name is mounted mount mode in drive drive name, status: DISMOUNTING.

Explanation: In response to a QUERY MOUNT command, the server indicates that the given volume is mounted in the specified drive. The volume is currently being dismounted by the server.

System Action: None.

User Response: None.

ANR8331I (AS/400)Device type volume volume name is mounted mount mode in drive drive name, status: DISMOUNTING.

Explanation: In response to a QUERY MOUNT command, the server indicates that the given volume is mounted in the specified drive. The volume is currently being dismounted by the server.

System Action: None.

User Response: None.

ANR8332IDevice type volume volume name is mounted mount mode, status: IDLE.

Explanation: In response to a QUERY MOUNT command, the server indicates that the given volume is mounted for I/O operations. The volume is currently idle, meaning no active operations are being performed. If the volume remains in the idle state for the amount of time specified by the device class mount retention period, it will be automatically dismounted.

System Action: None.

User Response: None.

ANR8332I (AS/400)Device type volume volume name is mounted mount mode, status: IDLE.

Explanation: In response to a QUERY MOUNT command, the server indicates that the given volume is mounted for I/O operations. The volume is currently idle, that is, no active operations are being performed. If the volume remains in the idle state for the amount of time specified by the device class mount retention period, it is automatically dismounted.

System Action: None.

User Response: None.

ANR8333IDevice type volume volume name is mounted mount mode, status: IN USE.

Explanation: In response to a QUERY MOUNT command, the server indicates that the given volume is mounted for I/O operations. The volume is currently in use, meaning that read or write operations, or both are being performed.

System Action: None.

User Response: None.

ANR8333I (AS/400)Device type volume volume name is mounted mount mode, status: IN USE.

Explanation: In response to a QUERY MOUNT command, the server indicates that the given volume is mounted for I/O operations. The volume is currently in use, meaning that read or write operations, or both are being performed.

System Action: None.

User Response: None.

ANR8334I Number of volumes volumes found.

Explanation: This is a summary message for the QUERY MOUNT command. It indicates the total number of mounted volumes that have been reported in the command output.

System Action: None.

User Response: None.

ANR8334I (AS/400)Number of volumes volumes found.

Explanation: This is a summary message for the QUERY MOUNT command. It indicates the total number of mounted volumes that have been reported in the command output.

System Action: None.

User Response: None.

ANR8335IRequest number: Verifying label of device type volume volume name in drive drive name.

Explanation: The server verifies the label of the volume that has been requested by an earlier mount message. This is done to ensure that the correct volume has been mounted by the operator.

System Action: The server reads the volume label and checks it for validity.

User Response: None.

ANR8335I (AS/400)Request number: Verifying label of device type volume volume name in drive drive name.

Explanation: The server verifies the label of the volume that has been requested by an earlier mount message. This is done to ensure that the correct volume has been mounted by the operator.

System Action: The server reads the volume label and checks it for validity.

User Response: None.

ANR8336IVerifying label of device type volume volume name in drive drive name.

Explanation: The server verifies the label of a volume that is needed for read or write operations, or both. This is done to ensure that the correct volume has been mounted.

System Action: The server reads the volume label and checks it for validity.

User Response: None.

ANR8336I (AS/400)Verifying label of device type volume volume name in drive drive name.

Explanation: The server verifies the label of a volume that is needed for read or write operations, or both. This is done to ensure that the correct volume has been mounted.

System Action: The server reads the volume label and checks it for validity.

User Response: None.

ANR8337IRequest number volume volume name mounted in drive drive name.

Explanation: The server verifies that the specified mount request has been completed properly. Read or write operations, or both, can be performed on the volume.

System Action: The label of the volume has been verified.

User Response: None.

ANR8337I (AS/400)Request number volume volume name mounted in drive drive name.

Explanation: The server verifies that the specified mount request has been completed properly. Read or write operations, or both, can be performed on the volume.

System Action: The label of the volume has been verified.

User Response: None.

ANR8338EDevice type volume volume name cannot be overwritten by EXPORT operation.

Explanation: The specified volume already exists or contains data, so that the server cannot allow new export data to be written to it.

System Action: The server detects that the given volume already contains some data that would be overwritten by the requested export operation.

User Response: If the specified volume does not contain any valuable data, delete it and retry the export operation.

ANR8338E (AS/400)Device type volume volume name cannot be overwritten by operation operation.

Explanation: The specified volume already exists or contains data so that the server cannot allow new data to be written to it.

System Action: The server detects that the given volume already contains some data that would be overwritten by the requested operation.

User Response: If the specified volume does not contain any valuable data, delete it and try the given operation again.

ANR8339EDevice type volume intended volume name in drive drive name was replaced with volume incorrect volume name.

Explanation: The server detects that a previously mounted and verified volume (the desired volume) has been replaced with a different volume (the incorrect volume). No further read or write operations, or both, can occur on the given drive, because data corruption may occur.

System Action: The server dismounts the volume from the drive.

User Response: Mount the correct volume again if it is in a manual library and retry the operation.

ANR8339E (AS/400)Device type volume intended volume name in drive drive name was replaced with volume incorrect volume name.

Explanation: The server detects that a previously mounted and verified volume (the intended volume) has been replaced with a different volume (the incorrect volume). No further read or write operations, or both, can occur on the given drive because data corruption may occur.

System Action: The server dismounts the volume from the drive.

User Response: None.

ANR8340IDevice type volume volume name mounted.

Explanation: The server has mounted the given volume.

System Action: Read or write operations, or both, will commence for the volume.

User Response: None.

ANR8340I (AS/400)Device type volume volume name mounted.

Explanation: The server has mounted the given volume.

System Action: Read or write operations, or both, will commence for the volume.

User Response: None.

ANR8341IEnd-of-volume reached for device type volume volume name.

Explanation: The server has detected an end-of-volume condition for the given volume.

System Action: The volume is marked full. If more data must be stored, the server will access another volume for it.

User Response: None.

ANR8341I (AS/400)End-of-volume reached for device type volume volume name.

Explanation: The server has detected an end-of-volume condition for the given volume.

System Action: The volume is marked full. If more data must be stored, the server will access another volume to store it.

User Response: None.

ANR8342IRequest request number for volume volume name canceled by administrator name.

Explanation: A mount request is canceled by the given administrator.

System Action: The system cancels the mount request.

User Response: None.

ANR8342I (AS/400)Request request number for volume volume name canceled by administrator name.

Explanation: A mount request is canceled by the given administrator.

System Action: The system cancels the mount request.

User Response: None.

ANR8343IRequest request number for volume volume name canceled (PERMANENT) by administrator name.

Explanation: A mount request is successfully canceled with the PERMANENT option.

System Action: The system cancels the mount request and marks the volume as unavailable.

User Response: None.

ANR8343I (AS/400)Request request number for volume volume name canceled (PERMANENT) by administrator name.

Explanation: A mount request is successfully canceled with the PERMANENT option by the given administrator.

System Action: The system cancels the mount request and marks the volume as unavailable.

User Response: None.

ANR8344ECommand: Invalid request number - request number.

Explanation: A command has been entered with an incorrect request number.

System Action: The server does not process the command.

User Response: Issue the command with the correct request number.

ANR8344E (AS/400)Command: Invalid request number - request number.

Explanation: A command has been entered with an incorrect request number.

System Action: The server does not process the command.

User Response: Issue the command with the correct request number.

ANR8345ECommand: No match found for this request number.

Explanation: The request number specified by the command is not in the list of outstanding mount requests.

System Action: The server does not process the command.

User Response: Issue the command with the correct request number.

ANR8345E (AS/400)Command: No match found for this request number.

Explanation: The request number specified by the command is not in the list of outstanding mount requests.

System Action: The server does not process the command.

User Response: Issue the command with the correct request number.

ANR8346ICommand: No requests are outstanding.

Explanation: A QUERY REQUEST or CANCEL REQUEST command has been entered although no mount requests are outstanding.

System Action: Server operation continues.

User Response: None.

ANR8346I (AS/400)Command: No requests are outstanding.

Explanation: A QUERY REQUEST or CANCEL REQUEST command has been entered although no mount requests are outstanding.

System Action: Server operation continues.

User Response: None.

ANR8347ECommand: Volume volume not found.

Explanation: A DISMOUNT VOLUME command is issued, but the volume to be dismounted cannot be found.

System Action: Server operation continues.

User Response: Ensure that the correct volume name is entered.

ANR8347E (AS/400)Command: Volume volume not found.

Explanation: A DISMOUNT VOLUME command is issued, but the volume to be dismounted cannot be found.

System Action: Server operation continues.

User Response: Ensure that the correct volume name is entered.

ANR8348ECommand: Volume volume is not "Idle".

Explanation: A DISMOUNT VOLUME command has been issued, but the volume is still in use and cannot be dismounted.

System Action: Server operation continues.

User Response: If it is necessary to dismount the volume, cancel the session or process that is using the volume, and reissue the command.

ANR8348E (AS/400)Command: Volume volume is not "Idle".

Explanation: A DISMOUNT VOLUME command has been issued, but the volume is in use and cannot be dismounted.

System Action: Server operation continues.

User Response: If it is necessary to dismount the volume, cancel the session or process that is using the volume, and reissue the DISMOUNT VOLUME command.

ANR8349ECommand: Device device not found.

Explanation: A DISMOUNT DEVICE command has been issued, but the device to be dismounted cannot be found.

System Action: Server operation continues.

User Response: Ensure that the correct device has been specified.

ANR8349E (AS/400)Command: Cannot reply to request request number.

Explanation: The state of the request, whose number is specified by the given command, does not permit the use of the REPLY command.

System Action: The REPLY command is not processed.

User Response: The REPLY command is invalid for the current state of the specified request. The outstanding request must be satisfied by using your installation's procedures.

ANR8350ECommand: Device device is not "Idle".

Explanation: A DISMOUNT DEVICE command has been issued, but the device is still in use and cannot be dismounted.

System Action: Server operation continues.

User Response: If it is necessary to dismount the device, cancel the session or process that is using the device, and reissue the command.

ANR8350E (AS/400)Command: Device device is not "Idle".

Explanation: A DISMOUNT DEVICE command has been issued, but the device is in use and cannot be dismounted.

System Action: Server operation continues.

User Response: If it is necessary to dismount the device, cancel the session or process that is using the device, and reissue the DISMOUNT DEVICE command.

ANR8351ERequest number: Mount request for volume volume name has timed out.

Explanation: The mount request has not been satisfied in the requested time.

System Action: The server fails the mount request.

User Response: Retry the mount request and ensure that the volume is mounted within the time limit for the manual library. For an automated library, retry the mount request and increase the mount wait time for the device class.

ANR8351E (AS/400)Request number: Mount request for volume volume name has timed out.

Explanation: The mount request has not been performed in the requested time.

System Action: The server fails the mount request.

User Response: None.

ANR8352IRequests outstanding:

Explanation: This message provides a list of currently outstanding mount requests.

System Action: The server lists all outstanding mount requests or the one specified on the QUERY REQUEST command.

User Response: None.

ANR8352I (AS/400)Requests outstanding:

Explanation: This message provides a list of currently outstanding mount requests.

System Action: The server lists all outstanding mount requests or the one specified on the QUERY REQUEST command.

User Response: None.

ANR8353ERequest number: I/O error reading label of volume in drive drive name.

Explanation: The server detects an error while reading the volume label from the volume in the specified drive.

System Action: The volume is ejected, and the server continues to wait for the requested volume to be mounted.

User Response: Ensure the following:

After checking and correcting these potential problems, retry the operation.

ANR8353E (AS/400)Request number: I/O error reading label of volume in drive drive name.

Explanation: ADSM detects an I/O error while reading the volume label from the volume in the specified drive.

System Action: If a volume was mounted, it is ejected. If the library is of type USRDFN, this media operation fails. For any other library type, the server continues to wait for the requested volume to be mounted.

User Response: Ensure that the requested volume is inserted properly in the designated drive. Also, make sure that the volume has been labeled by using the INZTAP command before you attempt to use it with the server.

ANR8354ERequest number: Incorrect volume (volume name) mounted in drive drive name.

Explanation: The user has inserted the named volume into the indicated drive, but it is not the one requested by the server.

System Action: The volume is ejected, and the server continues to wait for the requested volume to be mounted.

User Response: Ensure that the requested volume is inserted properly into the designated drive.

ANR8354E (AS/400)Request number: Incorrect volume (volume name) mounted in drive drive name.

Explanation: The user has inserted the specified volume into the indicated drive, but it is not the one requested by the server.

System Action: If a volume was mounted, it is ejected. If the library is of type USRDFN, this media operation fails. For any other library type, the server continues to wait for the requested volume to be mounted.

User Response: Ensure that the requested volume is inserted properly into the designated drive.

ANR8355EI/O error reading label for volume volume name in drive drive name.

Explanation: The server detects an error while reading/verifying the volume label for the volume in the specified drive.

System Action: The volume is dismounted by the server.

User Response: Ensure the following:

After checking and correcting these potential problems, retry the operation.

ANR8355E (AS/400)I/O error reading label for volume volume name in drive drive name.

Explanation: ADSM detects an error while reading or verifying the volume label for the volume in the specified drive.

System Action: If a volume was mounted, it is ejected. If the library is of type USRDFN, this media operation fails. For any other library type, the server continues to wait for the requested volume to be mounted.

User Response: Check the integrity of the data on the volume by issuing an AUDIT VOLUME command.

ANR8356EIncorrect volume mounted volume name was mounted instead of volume expected volume name in library library name.

Explanation: The incorrect volume has been mounted in the designated library. This error can occur if the library inventory has been altered due to manual intervention or movement of volumes, or both.

System Action: The volume is dismounted; the expected volume may be marked unavailable if this error occurs during normal volume mount activity.

User Response: Use the AUDIT LIBRARY command to force the library to reevaluate its inventory of volumes.

ANR8356E (AS/400)Incorrect volume mounted volume name was mounted instead of volume expected volume name in library library name.

Explanation: The incorrect volume was mounted in the designated library. This error can occur if the library inventory has been altered due to manual intervention or movement of volumes, or both.

System Action: The volume is dismounted. The expected volume may be marked unavailable if this error occurs during normal volume mount activity.

User Response: Use the AUDIT LIBRARY command to force the library to reevaluate its inventory of volumes.

ANR8357IError reading label of volume from slot-element element address in drive drive name of library library name.

Explanation: While processing a search-mode CHECKIN LIBVOLUME command for the designated library, the server finds a volume whose label cannot be read.

System Action: The volume is dismounted and is not checked into the library.

User Response: Remove the volume from the library and ensure that it is properly labeled. After doing so, the volume can be checked into the library.

ANR8357E (AS/400)Error reading label of volume in drive drive name of library library name.

Explanation: While processing a search-mode CHECKIN LIBVOLUME command for the designated library, the server finds a volume whose label cannot be read.

System Action: The volume is dismounted and is not checked into the library.

User Response: Remove the volume from the library and ensure that it is properly labeled. Then check the volume back into the library.

ANR8358EAudit operation is required for library library name.

Explanation: The server encounters a problem managing the given library, and determines that an AUDIT LIBRARY operation should be performed.

System Action: The server may continue to access the library, but some volumes may not be accessible until an AUDIT LIBRARY command is issued against the library.

User Response: Issue an AUDIT LIBRARY command against the library.

ANR8358E (AS/400)Audit operation is required for library library name.

Explanation: The server encounters a problem managing the given library, and determines that an AUDIT LIBRARY operation should be performed.

System Action: The server may continue to access the library, but some volumes may not be accessible until an AUDIT LIBRARY command is issued against the library.

User Response: Issue an AUDIT LIBRARY command against the library to verify the library's inventory.

ANR8359EMedia fault detected on device type volume volume name in drive drive name of library library name.

Explanation: The server encounters a media fault while accessing the given volume using the specified drive.

System Action: The operation that is attempting to access the volume will fail, and the volume will be immediately dismounted from the drive.

User Response: In some cases, the server will automatically mark the volume unavailable. If this does not happen automatically, issue an UPDATE VOLUME command to set the volume's access value to unavailable. This will prevent the server from trying to mount the volume to satisfy user requests. Issue an AUDIT VOLUME command to determine if any data has been lost due to the media failure.

ANR8359E (AS/400)Media fault detected on device type volume volume name in drive drive name of library library name.

Explanation: The server encounters a media fault while accessing the given volume using the specified drive.

System Action: The operation that is attempting to access the volume fails, and the volume is immediately dismounted from the drive.

User Response: In some cases, the server automatically marks the volume unavailable. If this does not happen automatically, issue an UPDATE VOLUME command to set the volume's access value to unavailable. This prevents the server from trying to mount the volume to satisfy user requests. It is also necessary to issue an AUDIT VOLUME command to determine if any data has been lost due to the media failure.

ANR8360IVolume volume name has been deleted from MANUAL library library name.

Explanation: The specified volume has been deleted by the server. It can be returned to a scratch pool by the mount operator if desired.

System Action: The volume is removed from the server's inventory.

User Response: None.

ANR8360I (AS/400)Volume volume name has been deleted from library type library library name.

Explanation: The specified volume has been deleted by the server. It can be returned to a scratch pool by the mount operator if desired.

System Action: The volume is removed from the server's inventory.

User Response: No action is required.

ANR8361ECommand: Device type not specified.

Explanation: The specified command requires that the DEVTYPE parameter be supplied.

System Action: The command is not processed.

User Response: Reissue the command, and specify a valid DEVTYPE parameter.

ANR8361E (AS/400)Command: Device type not specified.

Explanation: The specified command requires that the DEVTYPE parameter be supplied.

System Action: The server does not process the command.

User Response: Reissue the command and specify a valid DEVTYPE parameter.

ANR8362ECommand: The parameter parameter is invalid for device type device type.

Explanation: The specified parameter is not valid for a device class with the given device type.

System Action: The command is not processed.

User Response: Reissue the command with a correct parameter.

ANR8362E (AS/400)Command: The parameter parameter is invalid for device type device type.

Explanation: The specified parameter is not valid for a device class with the given device type.

System Action: The server does not process the command.

User Response: Reissue the command with a correct parameter.

ANR8363ECommand: The parameter parameter is required for device type device type.

Explanation: The specified command requires that the given parameter be supplied when the indicated device type is used.

System Action: The command is not processed.

User Response: Reissue the command, providing the required parameter value.

ANR8363E (AS/400)Command: The parameter parameter is required for device type device type.

Explanation: The specified command requires that the given parameter be supplied when the indicated device type is used.

System Action: The server does not process the command.

User Response: Reissue the command and provide the required parameter value.

ANR8364ECommand: Cannot reduce MOUNTLIMIT below number of volumes currently mounted.

Explanation: The MOUNTLIMIT value cannot be reduced below the number of currently mounted volumes.

System Action: The command is not processed.

User Response: Wait until the server finishes using some of the mounted volumes, or force the server to dismount idle volumes using the DISMOUNT VOLUME command, then retry this command.

ANR8364E (AS/400)Command: Cannot reduce MOUNTLIMIT below number of volumes currently mounted.

Explanation: The MOUNTLIMIT value cannot be reduced below the number of currently mounted volumes.

System Action: The server does not process the command.

User Response: Wait until the server finishes using some of the mounted volumes, or force the server to dismount idle volumes using the DISMOUNT VOLUME command. Then reissue this command.

ANR8365ECommand: The parameter parameter cannot be changed.

Explanation: The specified parameter cannot be changed from the value that was provided with the associated DEFINE command.

System Action: The command is not processed.

User Response: If it is necessary to use a different value for the given parameter, the associated object must be deleted and then redefined using the new parameter value.

ANR8365E (AS/400)Command: The parameter parameter cannot be changed.

Explanation: The specified parameter cannot be changed from the value that was provided with the associated DEFINE command.

System Action: The server does not process the command.

User Response: To use a different value for the given parameter, the associated object must be deleted and then defined by using the new parameter value.

ANR8366ECommand: Invalid value for parameter parameter.

Explanation: An invalid value has been provided for the specified parameter.

System Action: The command is not processed.

User Response: Reissue the command, and specify a valid parameter value.

ANR8366E (AS/400)Command: Invalid value for parameter parameter.

Explanation: An invalid value has been provided for the specified parameter.

System Action: The server does not process the command.

User Response: Reissue the command and specify a valid parameter value.

ANR8367ECommand: Multiple parameter values are not allowed.

Explanation: The designated parameter is specified more than once in the command; this is not allowed.

System Action: The command is not processed.

User Response: Reissue the command, but specify the given parameter only once.

ANR8367E (AS/400)Command: Multiple parameter values are not allowed.

Explanation: The designated parameter is specified more than once in the command, which is not allowed.

System Action: The server does not process the command.

User Response: Reissue the command, but specify the given parameter only once.

ANR8368ERequest number: Incorrect side (side) of volume volume name mounted in drive drive name.

Explanation: The user inserted the wrong side of the requested volume into the indicated drive.

System Action: The volume is ejected, and the server continues to wait for the requested side of the volume to be mounted.

User Response: Insert the correct side of the requested volume into the designated drive.

ANR8368E (AS/400)Request number: Incorrect side (side) of volume volume name mounted in drive drive name.

Explanation: The user has inserted the wrong side of the requested volume into the indicated drive.

System Action: The volume is ejected, and the server continues to wait for the requested side of the volume to be mounted.

User Response: Insert the correct side of the requested volume into the designated drive.

ANR8369ELibrary library name is not defined.

Explanation: The designated library is not defined, but has been referenced in a mount request.

System Action: The mount request is rejected.

User Response: Define the given library, or update the LIBRARY parameter of the device class that references it.

ANR8369E (AS/400)Library library name is not defined.

Explanation: The designated library is not defined, but has been referenced in a mount request.

System Action: The mount request is rejected.

User Response: Define the given library or update the LIBRARY parameter of the device class that references it.

ANR8370IDevice type volume volume name is mounted mount mode, status: RETRY.

Explanation: In response to a QUERY MOUNT command, the server indicates that the given volume is mounted for I/O operations. The volume is currently in RETRY, meaning an attempt is being made to re-establish communications with another server. If the volume remains in the retry state for the amount of time specified by the device class retry period, the operation will fail and the volume will be automatically dismounted.

System Action: None.

User Response: None.

ANR8370I (AS/400)Device type volume volume name is mounted mount mode, status: RETRY.

Explanation: In response to a QUERY MOUNT command, the server indicates that the given volume is mounted for I/O operations. The volume is currently in RETRY, meaning an attempt is being made to re-establish communications with another server. If the volume remains in the retry state for the amount of time specified by the device class retry period, the operation will fail and the volume will be automatically dismounted.

System Action: None.

User Response: None.

ANR8371II/O is being bypassed for volume volume name.

Explanation: The indicated volume is mounted but the server is bypassing actual I/O operations for the volume. The pool associated with the volume matches the NULLPOOLNAME option in the options file or NULLFILEDEVCLASS YES has been specified in the options file.

System Action: None.

User Response: None.

ANR8372IRequest number: Remove device type volume volume name from drive drive name of library library name.

Explanation: A LABEL LIBVOLUME command has completed. You can remove the specified volume from the designated drive and store it outside the library.

System Action: None.

User Response: Remove the volume from the drive and store it in a safe place.

ANR8373IRequest number: Fill the bulk entry/exit port of library library name with all device type volumes to be processed within time limit minute(s); issue 'REPLY' along with the request ID when ready.

Explanation: A CHECKIN LIBVOLUME or LABEL LIBVOL command with SEARCH=BULK is in progress. Load all volumes to be processed into the multi-slot entry/exit port of the given library within the time limit specified in the message.

System Action: The server waits until a REPLY command is issued, or until the time limit expires.

User Response: Insert the volumes into the library's entry/exit port; and issue a REPLY command, along with the request ID, to tell the server that the volumes have been inserted.

ANR8374EUnable to unmount mountpoint mountpoint name.

Explanation: A removable file device class mountpoint had to be unmounted using the operating system unmount function. The server did not have permission to unmount the directory specified.

System Action: The server continues, but cannot use the mountpoint for removablefile support until the directory is unmounted.

User Response: It may be necessary to run the server as a root user to mounted directories to be unmounted.

ANR8375EDevice type volume volume name cannot be overwritten by BACKUPSET operation.

Explanation: The specified volume already exists or contains data, so that the server cannot allow new backup set data to be written to it.

System Action: The server detects that the given volume already contains some data that would be overwritten by the requested backup set operation.

User Response: If the specified volume does not contain any valuable data, delete it and retry the backup set operation.

ANR8400ILibrary library name defined.

Explanation: The designated library has been successfully defined.

System Action: The library is defined and recorded in the database.

User Response: None.

ANR8400I (AS/400)Library library name defined.

Explanation: The designated library has been successfully defined.

System Action: The library is defined and recorded in the database.

User Response: None.

ANR8401ECommand: Invalid library name library name.

Explanation: The designated library name is invalid; either it contains too many characters, or some of the characters are invalid.

System Action: The command is not processed.

User Response: Reissue the command using a valid library name.

ANR8401E (AS/400)Command: Invalid library name library name.

Explanation: The designated library name is invalid; either it contains too many characters, or some of the characters are invalid.

System Action: The server does not process the command.

User Response: Reissue the command and specify a valid library name.

ANR8402ECommand: Library library name is already defined.

Explanation: The designated library cannot be defined because it already exists.

System Action: The command is not processed.

User Response: If you want to define an additional library, reissue the command with a different library name.

ANR8402E (AS/400)Command: Library library name is already defined.

Explanation: The designated library cannot be defined because it already exists.

System Action: The server does not process the command.

User Response: None.

ANR8403ECommand: Operation not allowed for library type libraries.

Explanation: The requested operation is not allowed for libraries of the given type.

System Action: The command is not processed.

User Response: None.

ANR8403E (AS/400)Command: Operation not allowed for library type libraries.

Explanation: The requested operation is not allowed for libraries of the given type.

System Action: The server does not process the command.

User Response: None.

ANR8404IDrive Drive name defined in library library name.

Explanation: The designated drive has been successfully defined as a member of the specified library.

System Action: The drive is defined and recorded in the database.

User Response: None.

ANR8404I (AS/400)Drive Drive name defined in library library name.

Explanation: The designated drive has been successfully defined as a member of the specified library.

System Action: The drive is defined and recorded in the database.

User Response: None.

ANR8405ECommand: Invalid drive name drive name.

Explanation: The designated drive name is invalid; either it contains too many characters, or some of the characters are invalid.

System Action: The command is not processed.

User Response: Reissue the command using a valid drive name.

ANR8405E (AS/400)Command: Invalid drive name drive name.

Explanation: The designated drive name is invalid because it contains too many characters or some of the characters are invalid.

System Action: The server does not process the command.

User Response: Reissue the command and specify a valid drive name.

ANR8406ECommand: Drive drive name is already defined in library library name.

Explanation: The designated drive cannot be defined because it has already been defined for the specified library.

System Action: The command is not processed.

User Response: If you want to define an additional drive, reissue the command with a different drive name.

ANR8406E (AS/400)Command: Drive drive name is already defined in library library name.

Explanation: The designated drive cannot be defined because it has already been defined for the specified library.

System Action: The server does not process the command.

User Response: None.

ANR8407ECommand: The MODEL parameter is required for this command.

Explanation: The MODEL parameter has not been provided; it is required.

System Action: The command is not processed.

User Response: Reissue the command using the MODEL parameter.

ANR8407W (AS/400)Unable to VARY Command option drive Drive name.

Explanation: The AS/400 Vary Configuration (VRYCFG) command failed for the specified drive. The server issues additional error messages if this condition prevents the server from completing an operation.

System Action: Server operation continues.

User Response: If necessary, use the appropriate AS/400 commands to determine the status of the drive and correct any problems.

ANR8408ECommand: The DEVICE parameter is required for this command.

Explanation: The DEVICE parameter has not been provided; it is required.

System Action: The command is not processed.

User Response: Reissue the command using the DEVICE parameter.

ANR8408W (AS/400)The AS/400 STATUS of drive drive name is AS/400 status.

Explanation: The server has determined the current AS/400 status of the given drive. The AS/400 status of the drive may have prevented the server from using the drive. The server issues additional error messages if this condition prevents the server from completing an operation.

System Action: Server operation continues.

User Response: If necessary, use the appropriate actions to resolve any problems with the specified drive. If the drive is shared with other systems, ensure that the SHARE parameter associated with the drive is set correctly in the DEFINE DRIVE command.

ANR8409ECommand: Library library name is not defined.

Explanation: The designated library has not been defined.

System Action: The command is not processed.

User Response: Reissue the command using a different library name, or define the library before retrying the command.

ANR8409E (AS/400)Command: Library library name is not defined.

Explanation: The designated library has not been defined.

System Action: The server does not process the command.

User Response: Reissue the command and specify a different library name, or define the library before reissuing the command.

ANR8410ILibrary library name deleted.

Explanation: The designated library has been deleted successfully.

System Action: The library is deleted.

User Response: None.

ANR8410I (AS/400)Library library name deleted.

Explanation: The designated library has been deleted successfully.

System Action: The library is deleted.

User Response: None.

ANR8411ECommand: One or more drives are still defined in library library name.

Explanation: The designated library cannot be deleted because there are still drives defined within it.

System Action: The command is not processed.

User Response: Delete all drives from the library, and reissue the command.

ANR8411E (AS/400)Command: One or more drives are still defined in library library name.

Explanation: The designated library cannot be deleted because there are still drives defined within it.

System Action: The server does not process the command.

User Response: Delete all drives from the library, and reissue the command.

ANR8412IDrive drive name deleted from library library name.

Explanation: The designated drive has been deleted successfully from the specified library.

System Action: The drive is deleted.

User Response: None.

ANR8412I (AS/400)Drive drive name deleted from library library name.

Explanation: The designated drive has been deleted successfully from the specified library.

System Action: The drive is deleted.

User Response: None.

ANR8413ECommand: Drive drive name is currently in use.

Explanation: The designated drive cannot be deleted or updated because it is currently in use.

System Action: The command is not processed.

User Response: Wait until the drive is no longer in use, and reissue the command.

ANR8413E (AS/400)Command: Drive drive name is currently in use.

Explanation: The designated drive cannot be deleted or updated because it is currently in use.

System Action: The server does not process the command.

User Response: Wait until the drive is no longer in use, and then reissue the command.

ANR8414ECommand: Drive drive name is not defined in library library name.

Explanation: The designated drive has not been defined in the given library.

System Action: The command is not processed.

User Response: Reissue the command using a different drive name. If appropriate, define the drive before retrying the command.

ANR8414E (AS/400)Command: Drive drive name is not defined in library library name.

Explanation: The designated drive has not been defined in the given library.

System Action: The server does not process the command.

User Response: Reissue the command and specify a different drive name; or, if appropriate, define the drive before reissuing the command.

ANR8415ECommand: The parameter parameter is required for this command.

Explanation: The specified parameter must be provided when processing the given command.

System Action: The command is not processed.

User Response: Reissue the command, providing the required parameter value.

ANR8415E (AS/400)Command: The parameter parameter is required for this command.

Explanation: The specified parameter must be provided when processing the given command.

System Action: The server does not process the command.

User Response: Reissue the command and provide the required parameter value.

ANR8416ECommand: The parameter parameter is invalid for library type library type.

Explanation: The specified parameter is not valid for libraries of the given type. The scratch category must be at least 2 less than the private category for 349x libraries.

System Action: The command is not processed.

User Response: Reissue the command, using only the proper parameters. If using the scratchcategory make sure it is at least 2 less than the privatecategory.

ANR8416E (AS/400)Command: The parameter parameter is invalid for library type library type.

Explanation: The specified parameter is not allowed for libraries of the given type.

System Action: The server does not process the command.

User Response: Reissue the command and specify only valid parameters.

ANR8417ECommand: The parameter parameter is invalid for drives in library type libraries.

Explanation: The specified parameter is not allowed when defining or updating drives in a library of the given type.

System Action: The command is not processed.

User Response: Reissue the command, using only the proper parameters.

ANR8417E (AS/400)Command: The parameter parameter is invalid for drives in library type libraries.

Explanation: The specified parameter is not allowed when defining or updating drives in a library of the given type.

System Action: The server does not process the command.

User Response: Reissue the command and specify only valid parameters.

ANR8418ECommand: An I/O error occurred while accessing library library name.

Explanation: An I/O error occurs while accessing the designated library.

System Action: The operation fails.

User Response: Ensure that the DEVICE parameter associated with the library is identified correctly in the DEFINE LIBRARY command, and that the library is currently powered on and ready. If the library has an access door, make sure it is closed. After checking and correcting these potential problems, retry the operation.

ANR8418E (AS/400)Command: An I/O error occurred while accessing library library name.

Explanation: An I/O error occurs while accessing the designated library.

System Action: The operation fails.

User Response: Ensure that the MLD parameter associated with the library is identified correctly in the DEFINE LIBRARY command, and that the library is currently powered on and ready. If the library has an access door, make sure it is closed. After checking and correcting these potential problems, you can try the operation again.

ANR8419ECommand: The drive or element conflicts with an existing drive in library library name.

Explanation: Either there are no more physical drives in the library, or the specified ELEMENT parameter conflicts with an existing defined drive in the given library.

System Action: The command is not processed.

User Response: Specify a valid ELEMENT parameter that is not used by any other drive in the library.

ANR8420ECommand: An I/O error occurred while accessing drive drive name.

Explanation: An I/O error occurs while accessing the specified drive.

System Action: The operation fails.

User Response: Ensure that the DEVICE parameter associated with the drive is identified correctly in the DEFINE DRIVE command, and that the drive is currently powered on and ready. After checking and correcting these potential problems, retry the command.

ANR8420E (AS/400)Command: An I/O error occurred while accessing drive drive name.

Explanation: An I/O error occurs while accessing the specified drive.

System Action: The operation fails.

User Response: Ensure that the DEVICE parameter associated with the drive is identified correctly in the DEFINE DRIVE command, and that the drive is currently powered on and ready. After checking and correcting these potential problems, you can try the operation again.

ANR8421ECommand: Unable to start a process for this command.

Explanation: The server cannot start a background process to carry out the designated command.

System Action: The operation fails.

User Response: Check for and correct memory shortages or other server resource constraints, and reissue the command.

ANR8421E (AS/400)Command: Unable to start a process for this command.

Explanation: The server cannot start a background process to carry out the designated command.

System Action: The operation fails.

User Response: Check for and correct memory shortages or other server resource constraints, and then reissue the command.

ANR8422ICommand: Operation for library library name started as process process ID.

Explanation: A volume check-in process has been started to handle the insertion of a volume into the given library. The process is assigned the ID specified in the message.

System Action: The server starts a background process to perform the operation in response to the CHECKIN LIBVOLUME command entered by an administrator.

User Response: To obtain status on the process, issue the QUERY PROCESS command. The process may be canceled with the CANCEL PROCESS command.

ANR8422I (AS/400)Command: Operation for library library name started as process process ID.

Explanation: A volume check-in process has been started to handle the insertion of a volume into the given library. The process is assigned the ID specified in the message.

System Action: The server starts a background process to perform the operation in response to the CHECKIN LIBVOLUME command entered by an administrator.

User Response: To obtain status on the process, issue the QUERY PROCESS command. To cancel the process, issue the CANCEL PROCESS command.

ANR8423ICHECKIN LIBVOLUME process for library library name has been canceled.

Explanation: A background server process that has been working to check in one or more volumes for the given library is canceled by the CANCEL PROCESS command.

System Action: The server process is ended and server operation continues.

User Response: None.

ANR8423I (AS/400)CHECKIN LIBVOLUME process for library library name has been canceled.

Explanation: The CANCEL PROCESS command cancels a background server process that has been working to check in one or more volumes for the given library.

System Action: The server process is ended and server operation continues.

User Response: No action is required.

ANR8424IChecking in volume volume name in library library name.

Explanation: In response to a QUERY PROCESS command, this message displays the status for a CHECKIN LIBVOLUME process on the server. The given volume is being checked in to the designated library.

System Action: The background process operation continues.

User Response: None. The process may be canceled by an authorized administrator using the CANCEL PROCESS command.

ANR8424I (AS/400)Checking in volume volume name in library library name.

Explanation: In response to a QUERY PROCESS command, this message displays the status for a CHECKIN LIBVOLUME process on the server. The given volume is being checked into the designated library.

System Action: The background process operation continues.

User Response: No action is required. An authorized administrator can cancel the process by using the CANCEL PROCESS command.

ANR8425IChecking in volumes in search mode in library library name.

Explanation: In response to a QUERY PROCESS command, this message displays the status for a CHECKIN LIBVOLUME process on the server. Volumes are being checked into the given library automatically using a search for previously-unknown volumes.

System Action: The background process operation continues.

User Response: None. The process may be canceled by an authorized administrator using the CANCEL PROCESS command.

ANR8425I (AS/400)Checking in volumes using search mode in library library name.

Explanation: In response to a QUERY PROCESS command, this message displays the status for a CHECKIN LIBVOLUME process on the server. Volumes are being checked into the given library automatically using a search for previously unknown volumes.

System Action: The background process operation continues.

User Response: No action is required. An authorized administrator can cancel the process by using the CANCEL PROCESS command.

ANR8426ECHECKIN LIBVOLUME for volume volume name in library library name failed.

Explanation: The background process for a CHECKIN LIBVOLUME command has failed.

System Action: The background process ends, but the volume has not been checked into the library.

User Response: Make sure the library and drive devices associated with this command are powered on and ready, and then reissue the command.

ANR8426E (AS/400)CHECKIN LIBVOLUME for volume volume name in library library name failed.

Explanation: The background process for a CHECKIN LIBVOLUME command has failed.

System Action: The background process terminates, but the volume has not been checked into the library.

User Response: Make sure the library and drive devices associated with this command are powered on and ready, and then reissue the command.

ANR8427ICHECKIN LIBVOLUME for volume volume name in library library name completed successfully.

Explanation: The specified volume was successfully checked in to the library during processing of a CHECKIN LIBVOLUME or LABEL LIBVOLUME command.

System Action: The volume is made available for mounting in the given library.

User Response: None.

ANR8427I (AS/400)CHECKIN LIBVOLUME for volume volume name in library library name completed successfully.

Explanation: The background process for a CHECKIN LIBVOLUME command has completed successfully.

System Action: The volume is made available for mounting in the given library.

User Response: No action is required.

ANR8428ECommand: The STATUS parameter is required for this command.

Explanation: The STATUS parameter must be provided with the given command.

System Action: The command is not processed.

User Response: Reissue the command, and provide a valid STATUS parameter value.

ANR8428E (AS/400)Command: The STATUS parameter is required for this command.

Explanation: The STATUS parameter must be provided with the given command.

System Action: The server does not process the command.

User Response: Reissue the command and provide a valid STATUS parameter value.

ANR8429ECommand: No drives are currently defined in library library name.

Explanation: The command cannot be issued until at least one drive has been defined in the given library.

System Action: The command is not processed.

User Response: Define a drive in the library, using the DEFINE DRIVE command, and then retry the failed command.

ANR8429E (AS/400)Command: No drives are currently defined in library library name.

Explanation: The server cannot process the command until at least one drive has been defined in the given library.

System Action: The server does not process the command.

User Response: By using the DEFINE DRIVE command, define a drive in the library, and then reissue the failed command.

ANR8430IVolume volume name has been checked into library library name.

Explanation: A search-mode CHECKIN LIBVOLUME process has found the given volume and automatically checked it into the library.

System Action: The volume is added to the given library's inventory.

User Response: None.

ANR8430I (AS/400)Volume volume name has been checked into library library name.

Explanation: A search-mode CHECKIN LIBVOLUME process has found the given volume and automatically checked it into the library.

System Action: The volume is added to the given library's inventory.

User Response: No action is required.

ANR8431ICHECKIN LIBVOLUME process completed for library library name; volume count volume(s) found.

Explanation: A search-mode CHECKIN LIBVOLUME process is completed. The specified number of volumes have been successfully added to the library's inventory.

System Action: The volumes are made available for use by the server.

User Response: None.

ANR8431I (AS/400)CHECKIN LIBVOLUME process completed for library library name; volume count volumes found.

Explanation: A search-mode CHECKIN LIBVOLUME process is completed. The specified number of volumes have been successfully added to the library's inventory.

System Action: The volumes are made available for use by the server.

User Response: No action is required.

ANR8432ECommand: Volume volume name is already present in library library name.

Explanation: The specified volume cannot be checked into the given library because it is already present.

System Action: The command is not processed.

User Response: Provide the name of a volume that is not already present in the given library. Use the QUERY LIBVOLUME command to obtain a full list of volumes that have already been checked into the library.

ANR8432E (AS/400)Command: Volume volume name is already present in library library name.

Explanation: The specified volume cannot be checked into the given library because it is already present.

System Action: The server does not process the command.

User Response: Provide the name of a volume that is not already present in the given library. Use the QUERY LIBVOLUME command to obtain a full list of volumes that have already been checked into the library.

ANR8433ECommand: Volume volume name is not present in library library name.

Explanation: The specified volume cannot be checked out of the given library because it is not present.

System Action: The command is not processed.

User Response: Provide the name of a volume that is present in the given library. Use the QUERY LIBVOLUME command to obtain a full list of volumes that reside in the library.

ANR8433E (AS/400)Command: Volume volume name is not present in library library name.

Explanation: The specified volume cannot be checked out of the given library because it is not present.

System Action: The server does not process the command.

User Response: Provide the name of a volume that is present in the given library. Use the QUERY LIBVOLUME command to obtain a full list of volumes that reside in the library.

ANR8434ICommand: Operation for volume volume name in library library name started as process process ID.

Explanation: A volume check-out process has been started to handle the removal of a volume from the given library. The process is assigned the ID specified in the message.

System Action: The server starts a background process to perform the operation in response to the CHECKOUT LIBVOLUME command entered by an administrator.

User Response: To obtain status on the process, issue the QUERY PROCESS command. The process may be canceled with the CANCEL PROCESS command.

ANR8434I (AS/400)Command: Operation for volume volume name in library library name started as process process ID.

Explanation: A volume check-out process has been started to handle the removal of a volume from the given library. The process is assigned the ID specified in the message.

System Action: The server starts a background process to perform the operation in response to the CHECKOUT LIBVOLUME command entered by an administrator.

User Response: To obtain status on the process, issue the QUERY PROCESS command. The process may be canceled with the CANCEL PROCESS command.

ANR8435ICHECKOUT LIBVOLUME for volume volume name in library library name has been canceled.

Explanation: A background server process that has been working to check out the volume from the given library is canceled by the CANCEL PROCESS command.

System Action: The server process is ended and server operation continues.

User Response: None.

ANR8435I (AS/400)CHECKOUT LIBVOLUME for volume volume name in library library name has been canceled.

Explanation: The CANCEL PROCESS command cancels a background server process that has been working to check out the volume from the given library.

System Action: The server process is ended and server operation continues.

User Response: No action is required.

ANR8436IChecking out volume volume name from library library name.

Explanation: In response to a QUERY PROCESS command, this message displays the status for a CHECKOUT LIBVOLUME process on the server.

System Action: The background process operation continues.

User Response: None. The process may be canceled by an authorized administrator using the CANCEL PROCESS command.

ANR8436I (AS/400)Checking out volume volume name from library library name.

Explanation: In response to a QUERY PROCESS command, this message displays the status for a CHECKOUT LIBVOLUME process on the server.

System Action: The background process operation continues.

User Response: No action is required. An authorized administrator can cancel the process by using the CANCEL PROCESS command.

ANR8437ECHECKOUT LIBVOLUME for volume volume name in library library name failed.

Explanation: The background process for a CHECKOUT LIBVOLUME command has failed.

System Action: The background process ends, but the volume has not been checked out of the library.

User Response: Make sure the library and drive devices associated with this command are powered on and ready, then retry the command.

ANR8437E (AS/400)CHECKOUT LIBVOLUME for volume volume name in library library name failed.

Explanation: The background process for a CHECKOUT LIBVOLUME command has failed.

System Action: The background process ends, but the volume has not been checked out of the library.

User Response: Make sure the library and drive devices associated with this command are powered on and ready, and then reissue the command.

ANR8438ICHECKOUT LIBVOLUME for volume volume name in library library name completed successfully.

Explanation: The background process for a CHECKOUT LIBVOLUME command has completed successfully.

System Action: The volume is either deleted from the library's inventory (if its status is something other than DATA) or marked not present (if its status is DATA).

User Response: None.

ANR8438I (AS/400)CHECKOUT LIBVOLUME for volume volume name in library library name completed successfully.

Explanation: The background process for a CHECKOUT LIBVOLUME command has completed successfully.

System Action: The volume is either deleted from the library's inventory (if its status is something other than DATA) or marked "not present" (if its status is DATA).

User Response: No action is required.

ANR8439ISCSI library library name is ready for operations.

Explanation: The initialization process for the given library has completed successfully, and the library is ready for use.

System Action: The library is made ready for use.

User Response: None.

ANR8439E (AS/400)Command: The parameter parameter is invalid for the type of drive.

Explanation: The specified parameter is not allowed when defining or updating the given type of drive.

System Action: The server does not process the command.

User Response: Reissue the command using only valid parameters.

ANR8440EInitialization failed for SCSI library library name; will retry in delay time minute(s).

Explanation: The initialization process for the given library has failed. It will be retried automatically after the specified amount of time has elapsed.

System Action: The initialization will be retried later.

User Response: Ensure that the library device is powered on and ready. If the library has an access door, make sure it is in the closed position.

ANR8441EInitialization failed for SCSI library library name.

Explanation: The initialization process for the given library has failed, and will not be retried until the next time the server needs to access the library.

System Action: The library is made temporarily unavailable.

User Response: Make sure the library is powered on and attached.

ANR8442ECommand: Volume volume name in library library name is currently in use.

Explanation: The command cannot be processed because the specified volume is already being used for another operation.

System Action: The command is not processed.

User Response: Wait until the conflicting volume activity has completed, and then reissue the command. If the volume is currently mounted, but idle, you can dismount it with the DISMOUNT VOLUME command and then retry this operation.

ANR8442E (AS/400)Command: Volume volume name in library library name is currently in use.

Explanation: The command cannot be processed because the specified volume is already being used for another operation.

System Action: The server does not process the command.

User Response: Wait until the conflicting volume activity has completed, and then reissue the command. If the volume is currently mounted but idle, you can dismount it by using the DISMOUNT VOLUME command and then try this operation again.

ANR8443ECommand: Volume volume name in library library name cannot be assigned a status of SCRATCH.

Explanation: The volume cannot be assigned to the given library's scratch pool because there is a storage pool volume defined or a volume in the volume history file with this volume name. Such a volume may still contain valid data. Assigning the volume to the library's scratch pool might result in a destructive overwrite of the volume's data.

System Action: The command is not processed.

User Response: Reissue the command, specifying that the volume be assigned a status of PRIVATE.

ANR8443E (AS/400)Command: Volume volume name in library library name cannot be assigned a status of SCRATCH.

Explanation: The volume cannot be assigned to the given library's scratch pool because there is a storage pool volume defined with this volume name. Assigning the volume to the library's scratch pool may result in a destructive overwrite of the volume's data.

System Action: The server does not process the command.

User Response: Reissue the command, and specify that the volume be assigned a status of PRIVATE.

ANR8444ECommand: Library library name is currently unavailable.

Explanation: The requested operation cannot be completed because the specified library is unavailable for I/O operations. The library may still be carrying out its initialization operations.

System Action: The command is not processed.

User Response: Wait until the library initialization completes or the library becomes ready.

ANR8444E (AS/400)Command: Library library name is currently unavailable.

Explanation: The requested operation cannot be completed because the specified library is unavailable for I/O operations. The library may be carrying out its initialization operations.

System Action: The server does not process the command.

User Response: Retry the requested operation when the library initialization completes or when the library becomes ready.

ANR8445IVolume volume name in library library name updated.

Explanation: The specified library volume has been updated successfully.

System Action: The library volume inventory is updated.

User Response: None.

ANR8445I (AS/400)Volume volume name in library library name updated.

Explanation: The specified library volume has been updated successfully.

System Action: The library volume inventory is updated.

User Response: None.

ANR8446IManual intervention required for library library name.

Explanation: The specified library requires manual intervention.

System Action: Current library activity will be delayed until the required intervention occurs.

User Response: If the library has an access door, make sure it is in the closed position. If it has a cartridge carousel, make sure the carousel is installed. The server automatically detects when the appropriate action has been taken; it will then continue its operations.

ANR8446I (AS/400)Manual intervention required for library library name.

Explanation: The specified library requires manual intervention.

System Action: Current library activity is delayed until the required intervention occurs.

User Response: If the library has an access door, make sure it is in the closed position. If it has a cartridge carousel, make sure the carousel is installed. The server automatically detects when the appropriate action has been taken. It then continues its operations.

ANR8447ENo drives are currently available in library library name.

Explanation: The attempted operation cannot be completed on the specified library because there are no available drives. A drive may be unavailable because an application other than the server may have the driver opened. This message may also be issued if a CHECKIN or LABEL command is issued and no drive is available to service the operation. This can be because all the drives are mounted by other processes or sessions, or the device type was incorrectly specified.

System Action: The attempted operation is terminated.

User Response: Use the QUERY DRIVE command to check the online status of the drives. Drives that are marked "Unavailable since hh:mm yy/mm/dd" are drives taken offline by the server at the time specified because of hardware failures or the inability to open the drive. If the attempted operation is a CHECKIN or LABEL command, use the QUERY MOUNT command to determine if all the drives in the library are mounted and wait until one of these is available. If there are mounted volumes with an IDLE status, use the DISMOUNT VOLUME command to free its drive, and retry the original operation.

ANR8447E (AS/400)No drives are currently available in library library name.

Explanation: No drives are available to carry out an attempted operation for the specified library. The drives can be unavailable for the following reasons. One or more drives in the library may already be in use by the server. One or more drives in the library may be in use by other jobs or other systems. The AS/400 status of one or more drives may render them unavailable to the server. Additional messages may have been issued by the server.

System Action: The attempted operation is ended.

User Response: If the attempted operation is IMPORT/EXPORT or DUMP/LOAD, wait until a drive is available in the library, and then try the operation again. If there are idle volumes mounted in the library, use the DISMOUNT VOLUME command to free a drive, and then try the original operation again. If any of the drives in the library are shared, wait until the other system makes a drive available, and then try the original operation again. If the attempted operation is a normal data storage operation, make sure that the number of drives defined in the library is greater than or equal to the MOUNTLIMIT value of the device class that references the library. This can be accomplished by either defining more drives in the library or by reducing the MOUNTLIMIT value of the device class. If the drives are in use by other jobs or systems, attempt to coordinate server operations and the availability of the drives.

ANR8448EScratch volume volume name from library library name rejected - volume name is already in use.

Explanation: The designated volume has been used to satisfy a scratch mount, but the volume is already defined in a storage pool, or has been used to store server export, database dump, or database backup information as recorded in the server volume history file.

System Action: The volume is rejected.

User Response: Use a volume that is not in use, or check out and relabel the rejected volume, assigning it a new name in the process, or delete the existing volume that caused the name conflict.

ANR8448I (AS/400)Scratch volume volume name from library library name rejected - volume name is already in use.

Explanation: The designated volume has been used to satisfy a scratch mount, but the volume is already defined in a storage pool, or has been used to store server export, database dump, or database backup information as recorded in the server volume history file.

System Action: The volume is rejected.

User Response: Use a volume that is not in use, or check out and relabel the rejected volume, assigning it a new name in the process, or delete the existing volume that caused the name conflict.

ANR8449EScratch volume volume name rejected - volume name is already in use.

Explanation: The designated volume has been used to satisfy a scratch mount, but the volume is already defined in a storage pool, or has been used to store server export, database dump, or database backup information as recorded in the server volume history file.

System Action: The volume is rejected.

User Response: Use a volume that is not in use, or rename the rejected volume or delete the existing volume that caused the name conflict.

ANR8449I (AS/400)Scratch volume volume name rejected - volume name is already in use.

Explanation: The designated volume has been used to satisfy a scratch mount, but the volume is already defined in a storage pool, or has been used to store server export, database dump, or database backup information as recorded in the server volume history file.

System Action: The volume is rejected.

User Response: Use a volume that is not in use, or rename the rejected volume, or delete the existing volume that is causing the name conflict.

ANR8450ECommand: Library library name is currently in use.

Explanation: The designated library cannot be deleted or updated because it is currently in use for an I/O operation.

System Action: The command is not processed.

User Response: Wait until the library is no longer in use, and then retry the command.

ANR8450E (AS/400)Command: Library library name is currently in use.

Explanation: The designated library cannot be deleted or updated because it is currently in use for an I/O operation.

System Action: The server does not process the command.

User Response: Wait until the library is no longer in use, and reissue the command.

ANR8451I349X library library name is ready for operations.

Explanation: The initialization process for the given library has completed successfully, and the library is ready for use.

System Action: The library is made ready for use.

User Response: None.

ANR8451I (AS/400)Media Library Device library name is ready for operations.

Explanation: The initialization process for the given library has completed successfully, and the library is ready for use.

System Action: The library is made ready for use.

User Response: No action is required.

ANR8452EInitialization failed for 349X library library name; will retry in delay time minute(s).

Explanation: The initialization process for the given library has failed. It is retried automatically after the specified amount of time has elapsed.

System Action: The initialization will be retried later.

User Response: Ensure that the library device is powered on and ready.

ANR8452E (AS/400)Initialization failed for Media Library Device library name; will retry in delay time minutes.

Explanation: The initialization process for the given library has failed. It is tried again automatically after the specified amount of time has elapsed.

System Action: The initialization is tried again later.

User Response: Ensure that the library device is powered on and ready.

ANR8453EInitialization failed for 349X library library name.

Explanation: The initialization process for the given library has failed and will not be retried until the next time the server needs to access the library.

System Action: The library is made temporarily unavailable.

User Response: None.

ANR8453E (AS/400)Initialization failed for Media Library Device library name.

Explanation: The initialization process for the given library has failed and will not be retried until the next time the server needs to access the library. Check previously issued messages for additional information.

System Action: The library is made temporarily unavailable.

User Response: None.

ANR8454EMismatch detected between external label (volume name from external label) and media label (volume name from media label) in 349X library library name.

Explanation: The external label of a volume was found to differ from its media label in the designated library.

System Action: The volume will not be accessed.

User Response: Remove the volume from the library and ensure that it is properly labeled.

ANR8454I (AS/400)Mismatch detected between external label (volume name from external label) and media label in Media Library Device library name.

Explanation: The external label of a volume is different from its media label in the designated library.

System Action: The volume is not accessed.

User Response: Remove the volume from the library and ensure that it is properly labeled.

ANR8455EVolume volume name could not be located during audit of library library name. Volume has been removed from the library inventory.

Explanation: While processing an AUDIT LIBRARY command for the given library, the server cannot find the given volume in the library.

System Action: The volume is removed from the library inventory.

User Response: If the volume is needed, it should be located and checked into the library using the CHECKIN LIBVOLUME command.

ANR8455I (AS/400)Volume volume name could not be located during audit of library library name.

Explanation: While processing an AUDIT LIBRARY command for the given library, the server cannot find the given volume in the library.

System Action: The volume is removed from the library inventory.

User Response: If the volume is needed, locate it and check it into the library by using the CHECKIN LIBVOLUME command.

ANR8456EMultiple volumes named volume name were found during audit of library library name.

Explanation: While processing an AUDIT LIBRARY command for the given library, multiple physical volumes are found to have the same name.

System Action: The first instance of the volume is retained in the server inventory; all other instances are ignored.

User Response: Remove all of the redundant instances of the volume from the library. If the volume which the server retained is found to be the incorrect one, it can be checked out with the CHECKOUT LIBVOLUME command; then the correct instance can be checked into the library with a CHECKIN LIBVOLUME command.

ANR8456I (AS/400)Multiple volumes named volume name were found during audit of library library name.

Explanation: While processing an AUDIT LIBRARY command for the given library, multiple physical volumes are found to have the same name.

System Action: The first occurrence of the volume is retained in the server inventory. All other occurrences are ignored.

User Response: Remove all the duplicate occurrences of the volume from the library. If the volume that the server retained is the incorrect one, check it out with the CHECKOUT LIBVOLUME command. Check the correct instance into the library with a CHECKIN LIBVOLUME command.

ANR8457ICommand: Operation for library library name started as process process ID.

Explanation: A library audit process has been started for the given library. The process is assigned the ID specified in the message.

System Action: The server starts a background process to perform the operation in response to the AUDIT LIBRARY command entered by an administrator.

User Response: To obtain status on the process, issue the QUERY PROCESS command. The process may be canceled with the CANCEL PROCESS command.

ANR8457I (AS/400)Command: Operation for library library name started as process process ID.

Explanation: A library audit process has been started for the given library. The process is assigned the ID specified in the message.

System Action: The server starts a background process to perform the operation in response to the AUDIT LIBRARY command entered by an administrator.

User Response: To obtain status on the process, issue the QUERY PROCESS command. The process may be canceled with the CANCEL PROCESS command.

ANR8458IAUDIT LIBRARY process for library library name has been canceled.

Explanation: A background server process that has been working to audit the given library is canceled by the CANCEL PROCESS command.

System Action: The server process is ended and server operation continues.

User Response: None.

ANR8458I (AS/400)AUDIT LIBRARY process for library library name has been canceled.

Explanation: A background server process that has been working to audit the given library is canceled by the CANCEL PROCESS command.

System Action: The server process is ended and server operation continues.

User Response: No action is required.

ANR8459IAuditing volume inventory for library library name.

Explanation: In response to a QUERY PROCESS command, this message displays the status for an AUDIT LIBRARY process on the server.

System Action: Server operation continues.

User Response: None. The process may be canceled by an authorized administrator using the CANCEL PROCESS command.

ANR8459I (AS/400)Auditing volume inventory for library library name.

Explanation: In response to a QUERY PROCESS command, this message displays the status for an AUDIT LIBRARY process on the server.

User Response: No action is required. The process may be canceled by an authorized administrator by using the CANCEL PROCESS command.

ANR8460EAUDIT LIBRARY process for library library name failed.

Explanation: The background process for an AUDIT LIBRARY command has failed.

System Action: The background process ends.

User Response: Make sure the library and drive devices associated with this command are powered on and ready, then reissue the command.

ANR8460E (AS/400)AUDIT LIBRARY process for library library name failed.

Explanation: The background process for an AUDIT LIBRARY command has failed.

System Action: The background process ends.

User Response: Make sure the library and drive devices associated with this command are powered on and ready, and then reissue the command.

ANR8461IAUDIT LIBRARY process for library library name completed successfully.

Explanation: The background process for an AUDIT LIBRARY command has completed successfully.

System Action: The library inventory is updated to match the contents of the library as found during the audit operation.

User Response: None.

ANR8461I (AS/400)AUDIT LIBRARY process for library library name completed successfully.

Explanation: The background process for an AUDIT LIBRARY command has completed successfully.

System Action: The library inventory is updated to match the contents of the library as found during the audit operation.

User Response: No action is required.

ANR8462IEnd-of-side reached for device type volume volume name.

Explanation: The server has detected an end-of-side condition for the given two sided volume.

System Action: The server will access the second side of the volume.

User Response: None.

ANR8463EDevice type volume volume name is write protected.

Explanation: The server has detected a write-protect condition for the given volume.

System Action: The server will dismount the volume and continue processing with another volume.

User Response: Adjust the write-protect switch on the volume so that writing is allowed. If the volume is an optical volume and the write-protect switch is already set to allow writing, use the MOVE DATA command to move the data off of the volume. Rewritable volumes may be reformatted and reused after the data is moved to another volume.

ANR8463E (AS/400)Device type volume volume name is write protected.

Explanation: The server has detected a write protect condition for the given volume.

System Action: The server dismounts the volume and continues processing with another volume.

User Response: Adjust the write protect switch on the volume so that writing is allowed.

ANR8464Ecommand: Invalid update request for library library name.

Explanation: An invalid update request has been made for the given library. This can occur if a new device name is given and the characteristics of the device do not match the characteristics of the original device.

System Action: The server does not process the command.

User Response: If a different type of library device has been installed, the old library definition must be deleted with a DELETE LIBRARY command, and a new library must be defined. The UPDATE LIBRARY command cannot be used in this case.

ANR8464E (AS/400)Invalid update request for library library name.

Explanation: An invalid update request has been made for the given library. This can occur if a new device name is given and the characteristics of the device do not match the characteristics of the original device.

System Action: The server does not process the command.

User Response: If a different type of library device has been installed, delete the old library definition with a DELETE LIBRARY command, and define a new library. The UPDATE LIBRARY command cannot be used in this case.

ANR8465ILibrary library name updated.

Explanation: An UPDATE LIBRARY request has been successfully processed for the given library.

System Action: The server updates its information about the library.

User Response: None.

ANR8465I (AS/400)Library library name updated.

Explanation: An UPDATE LIBRARY request has been successfully processed for the given library.

System Action: The server updates its information about the library.

User Response: None.

ANR8466Ecommand: Invalid update request for drive drive name in library library name.

Explanation: An invalid update request has been made for the given drive. This can occur if a new device name is given and the characteristics of the device do not match the characteristics of the original device.

System Action: The server does not process the command.

User Response: If a different type of drive has been installed, the old drive definition must be deleted with a DELETE DRIVE operation, and a new drive must be defined. The UPDATE DRIVE command cannot be used in this case.

ANR8466E (AS/400)Invalid update request for drive drive name in library library name.

Explanation: An invalid update request has been made for the given drive. This can occur if a new device name is given and the characteristics of the device do not match the characteristics of the original device.

System Action: The server does not process the command.

User Response: If a different type of drive has been installed, delete the old drive definition with a DELETE DRIVE command, and define a new drive. The UPDATE DRIVE command cannot be used in this case.

ANR8467IDrive drive name in library library name updated.

Explanation: An UPDATE DRIVE request has been successfully processed for the given drive.

System Action: The server updates its information about the drive.

User Response: None.

ANR8467I (AS/400)Drive drive name in library library name updated.

Explanation: An UPDATE DRIVE request has been successfully processed for the given drive.

System Action: The server updates its information about the drive.

User Response: None.

ANR8468Idevice type volume volume name dismounted from drive drive name in library library name.

Explanation: The specified volume has been dismounted from the given drive.

System Action: None.

User Response: If the type of the given library is MANUAL, the operator may elect to remove the volume (which has already been ejected) from the drive and store it in an appropriate location. For automated libraries, this message is purely informational.

ANR8468I (AS/400)Device type volume volume name dismounted from drive drive name in library library name.

Explanation: The specified volume has been dismounted from the given drive.

System Action: None.

User Response: If the type of the given library is MANUAL or USRDFN, the operator may elect to remove the volume (which has already been ejected) from the drive and store it in an appropriate location. For automated libraries, this message is only informational.

ANR8469EDismount of device type volume volume name from drive drive name in library library name failed.

Explanation: An attempt to dismount the designated volume failed due to an I/O error.

System Action: None.

User Response: If the type of the given library is MANUAL, the volume can be manually ejected and removed from the drive. For automated libraries, manual intervention may be required to correct the problem.

ANR8469E (AS/400)Dismount of device type volume volume name from drive drive name in library library name failed.

Explanation: An attempt to dismount the designated volume failed due to an I/O error or a DISMOUNT Exit error.

System Action: None.

User Response: If the type of the given library is MANUAL or USRDFN, the volume can be manually ejected and removed from the drive. For automated libraries, manual intervention may be required to correct the problem.

ANR8470WInitialization failure on drive drive name in library library name.

Explanation: The specified drive could not be initialized at this time.

System Action: The initialization of the specified library continues.

User Response: Examine previous messages for additional information regarding the specified drive.

ANR8471EDrive drive name of library library name is offline; server no longer polling drive.

Explanation: The server is unable to use the mentioned drive. This may be for the following reasons:

System Action: The drive is offline and is not used for tape operations.

User Response: Determine the reason the drive is inaccessible, such as hardware errors reported in the system logs. Render any needed corrections to the drive. Then, the drive may be made online by issuing the UPDATE DRIVE command with the ONLINE=YES option.

ANR8472IError reading label of volume in drive drive name of library library name.

Explanation: While processing a search-mode CHECKIN LIBVOLUME command for the designated library, the server finds a volume whose label cannot be read.

System Action: The volume is dismounted and is not checked into the library.

User Response: Remove the volume from the library and ensure that it is properly labeled. After doing so, the volume can be checked into the library.

ANR8493Idevice type volume volume name mounted in drive drive name in library library name.

Explanation: The specified volume has been mounted in the specified drive.

System Action: None.

User Response: For automated libraries, this message is purely informational.

ANR8494ECommand: An option specified is not valid for library type libraries.

Explanation: A requested option is not valid for libraries of the given type for the specified command.

System Action: The command is not processed.

User Response: None.

ANR8495EDevice type volume volume name cannot be written by BACKUP DB operation.

Explanation: The specified volume already exists or contains data, so that the server cannot allow new BACKUP DB data to be written to it. Or there is no space available on the destination filespace to write this backup to.

System Action: The server detects that the given volume already contains some data that would be overwritten by the requested BACKUP DB command, or that there is not enough space available.

User Response: If the specified volume does not contain any valuable data, delete it and retry the BACKUP DB command.

ANR8496EDevice class device class not defined in device configuration information file.

Explanation: The command that has been issued requires that the specified device class be defined in the device configuration information file. This definition was not found or the statements in the file are in the wrong order.

System Action: The command is not processed.

User Response: Reissue the command, and specify a valid device class. Refresh your device configuration information file by issuing the BACKUP DEVCONFIG command.

ANR8497ELibrary library not defined in device configuration information file.

Explanation: The specified command requires that the specified library be defined in the device configuration information file. This definition was not found or the statements in the file are in the wrong order.

System Action: The command is not processed.

User Response: Refresh your device configuration information file by issuing the BACKUP DEVCONFIG command. Make sure a library is defined for the device class. Reissue the command.

ANR8498EDrive not defined for library library in device configuration information file.

Explanation: The specified command requires that the specified drive be defined in the device configuration information file for the specified library. This definition was not found or the statements in the file are in the wrong order.

System Action: The command is not processed.

User Response: Refresh your device configuration information file by issuing the BACKUP DEVCONFIG command. Make sure a drive is defined for the library associated with the device class. Reissue the command.

ANR8499ICommand accepted.

Explanation: The command is accepted and processed by the server.

System Action: The server processes the command.

User Response: None.

ANR8499I (AS/400)Command accepted.

Explanation: The command is accepted and processed by the server.

System Action: The server processes the command.

User Response: None.

ANR8511E (AS/400)Message queue library name/message queue name is not available.

Explanation: Either the message queue object does not exist or the authority is incorrect.

System Action: The command is not processed.

User Response: Correct the message queue object name, create the message queue object, or change the authority and reissue the command.

ANR8512I (AS/400)Message queue is set to library name/message queue name.

Explanation: The message queue is set successfully.

System Action: The message queue is set successfully. Messages will be sent to the message queue.

User Response: None.

ANR8513I (AS/400)Message queue is set to the value of the message queue.

Explanation: The message queue is set to a special value. For example, "*NONE" is to turn off the message queue; "*SYOPR" is to send the messages to the system operator's message queue.

System Action: The message queue is set successfully. Messages will be sent to the message queue.

User Response: None.

ANR8550E (AIX)Error opening filespec.

Explanation: An error occurs while attempting an open operation.

System Action: Server processing continues.

User Response: Refer to the other displayed messages to determine why the open operation failed. Correct the problem and restart the process.

ANR8550E (AS/400)Error opening filespec.

Explanation: ADSM detects an error while attempting an open operation.

System Action: Server processing continues.

User Response: Refer to the other displayed messages to determine why the open operation has failed. Correct the problem and restart the process.

ANR8550E (HP-UX)Error opening file name.

Explanation: An error occurs while the server attempts a file open operation.

System Action: Server processing continues.

User Response: Refer to the other displayed messages to determine why the open operation failed. Crrect the problem and restart the process.

ANR8550E (Solaris)Error opening file name.

Explanation: An error occurs while the server attempts a file open operation.

System Action: Server processing continues.

User Response: Refer to the other displayed messages to determine why the open operation failed. Correct the problem and restart the process.

ANR8550E (Windows NT)Error opening filespec.

Explanation: The server detects an error while attempting an open operation.

System Action: Server processing continues.

User Response: Refer to the other displayed messages to determine why the open operation has failed. Correct the problem and restart the process.

ANR8551E (AIX)An error (error code) occurred during a write operation.

Explanation: An error occurs while attempting a write operation.

System Action: Server processing continues.

User Response: Refer to the other displayed messages to determine why the write operation failed. Correct the problem and restart the process.

ANR8551E (AS/400)An error (error code) occurred during a write operation.

Explanation: ADSM detects an error while attempting a write operation.

System Action: Server processing continues.

User Response: Refer to the other displayed messages to determine why the write operation has failed. Correct the problem and restart the process.

ANR8551E (HP-UX)An error (error code) occurred during a write operation.

Explanation: An error occurs while the server attempts a write operation.

System Action: Server processing continues.

User Response: Refer to the other displayed messages to determine why the write operation failed. Correct the problem and restart the process.

ANR8551E (Solaris)An error (error code) occurred during a write operation.

Explanation: An error occurs while the server attempts a write operation.

System Action: Server processing continues.

User Response: Refer to the other displayed messages to determine why the write operation failed. Correct the problem and restart the process.

ANR8551E (Windows NT)An error (error code) occurred during a write operation.

Explanation: The server detects an error while attempting a write operation.

System Action: Server processing continues.

User Response: Refer to the other displayed messages to determine why the write operation has failed. Correct the problem and restart the process.

ANR8552E (AIX)An error (error code) occurred during a read operation.

Explanation: An error occurs while attempting a read operation.

System Action: Server processing continues.

User Response: Refer to the other displayed messages to determine why the read operation failed. Correct the problem and restart the process.

ANR8552E (AS/400)An error (error code) occurred during a read operation.

Explanation: ADSM detects an error while attempting a read operation.

System Action: Server processing continues.

User Response: Refer to the other displayed messages to determine why the read operation has failed. Correct the problem and restart the process.

ANR8552E (HP-UX)An error (error code) occurred during a read operation.

Explanation: An error occurs while the server attempts a read operation.

System Action: Server processing continues.

User Response: Refer to the other displayed messages to determine why the read operation failed. Correct the problem and restart the process.

ANR8552E (Solaris)An error (error code) occurred during a read operation.

Explanation: An error occurs while the server attempts a read operation.

System Action: Server processing continues.

User Response: Refer to the other displayed messages to determine why the read operation failed. Correct the problem and restart the process.

ANR8552E (Windows NT)An error (error code) occurred during a read operation.

Explanation: The server detects an error while attempting a read operation.

System Action: Server processing continues.

User Response: Refer to the other displayed messages to determine why the read operation has failed. Correct the problem and restart the process.

ANR8553E (AIX)Device type volume volume name cannot be overwritten by DUMPDB operation.

Explanation: The specified volume already exists or contains data, so that the server cannot allow new DUMPDB data to be written to it.

System Action: The server has detected that the given volume already contains some data that would be overwritten by the requested DUMPDB operation.

User Response: If the specified volume does not contain any valuable data, delete it and retry the DUMPDB operation.

ANR8553E (AS/400)Device type volume volume name cannot be overwritten by DUMPDB operation.

Explanation: The specified volume already exists or contains data, so that the server cannot allow new DUMPDB data to be written to it.

System Action: The server detects that the given volume already contains data that would be overwritten by the requested DUMPDB operation.

User Response: If the specified volume does not contain any valuable data, delete it, and try the DUMPDB operation again.

ANR8553E (HP-UX)Device type volume volume name cannot be overwritten by DUMPDB operation.

Explanation: The specified volume already exists or contains data, so that the server cannot allow new DUMPDB data to be written to it.

System Action: The server has detected that the given volume already contains data that would be overwritten by the requested DUMPDB operation.

User Response: If the specified volume does not contain any valuable data, delete it and retry the DUMPDB operation, or specify a different volume name.

ANR8553E (Solaris)Device type volume volume name cannot be overwritten by DUMPDB operation.

Explanation: The specified volume already exists or contains data, so that the server cannot allow new DUMPDB data to be written to it.

System Action: The server has detected that the given volume already contains data that would be overwritten by the requested DUMPDB operation.

User Response: If the specified volume does not contain any valuable data, delete it and retry the DUMPDB operation, or specify a different volume name.

ANR8553E (Windows NT)Device type volume volume name cannot be overwritten by DUMPDB operation.

Explanation: The specified volume already exists or contains data, so that the server cannot allow new DUMPDB data to be written to it.

System Action: The server detects that the given volume already contains some data that would be overwritten by the requested DUMPDB operation.

User Response: If the specified volume does not contain any valuable data, delete it and retry the DUMPDB operation.

ANR8554W (AIX)Dump/load command: Device class device class name not defined. Devtype of FILE is assumed.

Explanation: The specified device class name is not defined with the DUMPLOADDB DEVCLASS option, to the server in the server options file or the server is not able to define the specified device class.

System Action: Processing continues. The dump/load process assumes the device class is devtype=FILE and writes to or reads from a file.

User Response: Refer to the other displayed messages to determine why the device class is not defined. Correct the problem and restart the command if you do not wish to write to or read from a file.

ANR8554W (AS/400)Dump/load command: Device class device class name not defined. Devtype of FILE is assumed.

Explanation: The specified device class name is not defined with the DUMPLOADDB DEVCLASS option to the server in the server options file or the server cannot define the specified device class.

System Action: Processing continues. The dump/load process assumes the device class is devtype=FILE, and writes to or reads from a file.

User Response: Refer to the other displayed messages to determine why the device class has not been defined. Correct the problem and restart the command if you do not wish to write to or read from a file.

ANR8554W (HP-UX)Dump/load command: Device class device class name not defined. Devtype of FILE is assumed.

Explanation: The specified device class name is not defined with the DUMPLOADDB DEVCLASS option, to the server in the server options file or the server is not able to define the specified device class.

System Action: Processing continues. The dump/load process assumes the device class is devtype=FILE and writes to or reads from a file.

User Response: Refer to the other displayed messages to determine why the device class is not defined. Correct the problem and restart the command if you do not wish to write to or read from a file.

ANR8554W (Solaris)Dump/load command: Device class device class name not defined. Devtype of FILE is assumed.

Explanation: The specified device class name is not defined with the DUMPLOADDB DEVCLASS option, to the server in the server options file or the server is not able to define the specified device class.

System Action: Processing continues. The dump/load process assumes the device class is devtype=FILE and writes to or reads from a file.

User Response: Refer to the other displayed messages to determine why the device class is not defined. Correct the problem and restart the command if you do not wish to write to or read from a file.

ANR8555W (AS/400)Command: The value of this command results in ADSM recovery files that cannot be edited on the AS/400.

Explanation: The SET LRECLRECOVERYFILE command has changed the value of this option to greater than 240. An AS/400 file with an LRECL greater than 240 cannot be edited on the AS/400. The ADSM recovery files affected by this option are the volume history file, the device configuration file and the DRM recovery plan file.

System Action: The server processes the command.

User Response: Ignore the warning or set the LRECLRECOVERYFILE option to a value less than 241. If the warning is ignored and it becomes necessary to edit the ADSM recovery files, the files will have to be edited on a platform other than the AS/400 and returned to the AS/400. For example, it may be necessary to FTP the files to a PC Workstation, edit them there and FTP the changed files back to the AS/400. While editing the files, ensure that the new LRECL does not exceed that of the original files on the AS/400. If the LRECL of the files is increased during the edit process, they will be truncated when they are returned to the AS/400.

Note:If an ADSM recovery file exists with an LRECL that is different than what is being used on the LRECLRECOVERYFILE option, the existing file must be deleted and re-created with the appropriate BACKUP command. For example, the device configuration file is re-created with the BACKUP DEVCONFIG command.

ANR8556W (AS/400)LRECLRECOVERYFILE statement in file filespec results in ADSM recovery files that cannot be edited on the AS/400.

Explanation: While processing the specified server options file, the server has encountered an LRECLRECOVERYFILE statement with a value greater than 240. An AS/400 file with an LRECL greater than 240 cannot be edited on the AS/400. The ADSM recovery files affected by this option are the volume history file, the device configuration file and the DRM recovery plan file.

System Action: Server initialization continues.

User Response: Ignore the warning or change the LRECLRECOVERYFILE statement to a value less than 241 and restart the server. If the warning is ignored and it becomes necessary to edit the ADSM recovery files, the files will have to be edited on a platform other than the AS/400 and returned to the AS/400. For example, it may be necessary to FTP the files to a PC Workstation, edit them there and FTP the changed files back to the AS/400. While editing the files, ensure that the new LRECL does not exceed that of the original files on the AS/400. If the LRECL of the files is increased during the edit process, they will be truncated when they are returned to the AS/400.

Note:If an ADSM recovery file exists with an LRECL that is different than what is being used on the LRECLRECOVERYFILE option, the existing file must be deleted and re-created with the appropriate BACKUP command. For example, the device configuration file is re-created with the BACKUP DEVCONFIG command.

ANR8557E (AS/400)Truncation occurred during a write operation.

Explanation: ADSM has detected a truncation while attempting a write operation.

System Action: The server activity which encountered this error will end, but server processing continues.

User Response: Refer to the other displayed messages to determine which file was involved when the write operation failed. As a group, the volume history file, the device configuration file and the DRM recovery plan file are referred to as the ADSM recovery files. If the file that encountered the error is one of the ADSM recovery files, the problem can be corrected with one of two methods. First, the length of the statements being written to these files can be controlled by the values in certain ADSM definitions. Second, the LRECLRECOVERYFILE option can be changed in the server options file. The SET LRECLRECOVERYFILE command can be used to change it for the currently running server. If the SET LRECLRECOVERYFILE command is used, the server does not have to be halted. Once the server is halted and restarted, the value in the options file will be used. To make the change permanent, the options file should be updated. Prior to making a change to the LRECLRECOVERYFILE option, please consider that a value greater than 240 results in a file that cannot be edited on the AS/400. If the file that encountered the error is NOT one of the ADSM recovery files, correct the problem and restart the process.

ANR8570E (AIX)HTTPS Initialization failed. No keyring file or keyring password were specified.

Explanation: HTTPS required keyring file and keyring password are not found.

System Action: The HTTPS COMMMethod is not initialized.

User Response: Ensure server has access to keyring file and password. Re-start the server.

ANR8570E (HP-UX)HTTPS Initialization failed. No keyring file or keyring password were specified.

Explanation: HTTPS required keyring file and keyring password are not found.

System Action: The HTTPS COMMMethod is not initialized.

User Response: Ensure server has access to keyring file and password. Re-start the server.

ANR8570E (Solaris)HTTPS Initialization failed. No keyring file or keyring password were specified.

Explanation: HTTPS required keyring file and keyring password are not found.

System Action: The HTTPS COMMMethod is not initialized.

User Response: Ensure server has access to keyring file and password. Re-start the server.

ANR8570E (Windows NT)HTTPS Initialization failed. No keyring file or keyring password were specified.

Explanation: HTTPS required keyring file and keyring password are not found.

System Action: The HTTPS COMMMethod is not initialized.

User Response: Ensure server has access to keyring file and password. Re-start the server.

ANR8571E (AIX)HTTPS Initialization failed. The keyring file format is invalid.

Explanation: HTTPS required keyring file has an invalid format.

System Action: The HTTPS COMMMethod is not initialized.

User Response: Keyring file may be corrupted. Obtain new copy of the keyring file, then re-start the server.

ANR8571E (HP-UX)HTTPS Initialization failed. The keyring file format is invalid.

Explanation: HTTPS required keyring file has an invalid format.

System Action: The HTTPS COMMMethod is not initialized.

User Response: Keyring file may be corrupted. Obtain new copy of the keyring file, then re-start the server.

ANR8571E (Solaris)HTTPS Initialization failed. The keyring file format is invalid.

Explanation: HTTPS required keyring file has an invalid format.

System Action: The HTTPS COMMMethod is not initialized.

User Response: Keyring file may be corrupted. Obtain new copy of the keyring file, then re-start the server.

ANR8571E (Windows NT)HTTPS Initialization failed. The keyring file format is invalid.

Explanation: HTTPS required keyring file has an invalid format.

System Action: The HTTPS COMMMethod is not initialized.

User Response: Keyring file may be corrupted. Obtain new copy of the keyring file, then re-start the server.

ANR8572E (AIX)HTTPS Initialization failed. The keyring file password is invalid.

Explanation: An invalid password was specified for the HTTPS keyring file.

System Action: The HTTPS COMMMethod is not initialized.

User Response: Obtain the correct password for the keyring file. Then re-start the server.

ANR8572E (HP-UX)HTTPS Initialization failed. The keyring file password is invalid.

Explanation: An invalid password was specified for the HTTPS keyring file.

System Action: The HTTPS COMMMethod is not initialized.

User Response: Obtain the correct password for the keyring file. Then re-start the server.

ANR8572E (Solaris)HTTPS Initialization failed. The keyring file password is invalid.

Explanation: An invalid password was specified for the HTTPS keyring file.

System Action: The HTTPS COMMMethod is not initialized.

User Response: Obtain the correct password for the keyring file. Then re-start the server.

ANR8572E (Windows NT)HTTPS Initialization failed. The keyring file password is invalid.

Explanation: An invalid password was specified for the HTTPS keyring file.

System Action: The HTTPS COMMMethod is not initialized.

User Response: Obtain the correct password for the keyring file. Then re-start the server.

ANR8573E (AIX)HTTPS Initialization failed. I/O error occurred reading the keyring file.

Explanation: An unknown I/O error occurred reading the keyring file.

System Action: The HTTPS COMMMethod is not initialized.

User Response: Keyring file may be corrupted. Obtain new copy of the keyring file, then re-start the server.

ANR8573E (HP-UX)HTTPS Initialization failed. I/O error occurred reading the keyring file.

Explanation: An unknown I/O error occurred reading the keyring file.

System Action: The HTTPS COMMMethod is not initialized.

User Response: Keyring file may be corrupted. Obtain new copy of the keyring file, then re-start the server.

ANR8573E (Solaris)HTTPS Initialization failed. I/O error occurred reading the keyring file.

Explanation: An unknown I/O error occurred reading the keyring file.

System Action: The HTTPS COMMMethod is not initialized.

User Response: Keyring file may be corrupted. Obtain new copy of the keyring file, then re-start the server.

ANR8573E (Windows NT)HTTPS Initialization failed. I/O error occurred reading the keyring file.

Explanation: An unknown I/O error occurred reading the keyring file.

System Action: The HTTPS COMMMethod is not initialized.

User Response: Keyring file may be corrupted. Obtain new copy of the keyring file, then re-start the server.

ANR8574E (AIX)HTTPS Initialization failed. Could not open the the keyring file.

Explanation: The keyring file could not be found or did not allow access.

System Action: The HTTPS COMMMethod is not initialized.

User Response: Ensure the keyring file is present and has read access allowed. Then re-start the server.

ANR8574E (HP-UX)HTTPS Initialization failed. Could not open the the keyring file.

Explanation: The keyring file could not be found or did not allow access.

System Action: The HTTPS COMMMethod is not initialized.

User Response: Ensure the keyring file is present and has read access allowed. Then re-start the server.

ANR8574E (Solaris)HTTPS Initialization failed. Could not open the the keyring file.

Explanation: The keyring file could not be found or did not allow access.

System Action: The HTTPS COMMMethod is not initialized.

User Response: Ensure the keyring file is present and has read access allowed. Then re-start the server.

ANR8574E (Windows NT)HTTPS Initialization failed. Could not open the the keyring file.

Explanation: The keyring file could not be found or did not allow access.

System Action: The HTTPS COMMMethod is not initialized.

User Response: Ensure the keyring file is present and has read access allowed. Then re-start the server.

ANR8575E (AIX)HTTPS Initialization failed. The specified certificate within the keyring file has expired.

Explanation: The default or specified certificate within the keyring file has expired.

System Action: The HTTPS COMMMethod is not initialized.

User Response: The certificate must be renewed and re-instated into the keyring file. Then re-start the server.

ANR8575E (HP-UX)HTTPS Initialization failed. The specified certificate within the keyring file has expired.

Explanation: The default or specified certificate within the keyring file has expired.

System Action: The HTTPS COMMMethod is not initialized.

User Response: The certificate must be renewed and re-instated into the keyring file. Then re-start the server.

ANR8575E (Solaris)HTTPS Initialization failed. The specified certificate within the keyring file has expired.

Explanation: The default or specified certificate within the keyring file has expired.

System Action: The HTTPS COMMMethod is not initialized.

User Response: The certificate must be renewed and re-instated into the keyring file. Then re-start the server.

ANR8575E (Windows NT)HTTPS Initialization failed. The specified certificate within the keyring file has expired.

Explanation: The default or specified certificate within the keyring file has expired.

System Action: The HTTPS COMMMethod is not initialized.

User Response: The certificate must be renewed and re-instated into the keyring file. Then re-start the server.

ANR8576E (AIX)HTTPS Initialization failed. The specified cert within the keyring file has as an invalid distinguished name.

Explanation: The distinguished name for the specified cert is invalid.

System Action: The HTTPS COMMMethod is not initialized.

User Response: Ensure the correct keyring has been specified and that the keyring contains the correct distinguished name. Then re-start the server.

ANR8576E (HP-UX)HTTPS Initialization failed. The specified cert within the keyring file has as an invalid distinguished name.

Explanation: The distinguished name for the specified cert is invalid.

System Action: The HTTPS COMMMethod is not initialized.

User Response: Ensure the correct keyring has been specified and that the keyring contains the correct distinguished name. Then re-start the server.

ANR8576E (Solaris)HTTPS Initialization failed. The specified cert within the keyring file has as an invalid distinguished name.

Explanation: The distinguished name for the specified cert is invalid.

System Action: The HTTPS COMMMethod is not initialized.

User Response: Ensure the correct keyring has been specified and that the keyring contains the correct distinguished name. Then re-start the server.

ANR8576E (Windows NT)HTTPS Initialization failed. The specified cert within the keyring file has as an invalid distinguished name.

Explanation: The distinguished name for the specified cert is invalid.

System Action: The HTTPS COMMMethod is not initialized.

User Response: Ensure the correct keyring has been specified and that the keyring contains the correct distinguished name. Then re-start the server.

ANR8675E (AIX)File name with environment variable DSMSERV_DIR: File already exists for File or Filetext Exit.

Explanation: The specified file already exists and the file-exit option was set to PRESERVE.

System Action: Server continues running.

User Response: Specify a non-existent file.

ANR8675E (HP-UX)File name with environment variable DSMSERV_DIR: File already exists for File or FileText Exit.

Explanation: The specified file already exists and the file-exit option was set to PRESERVE.

System Action: Server continues running.

User Response: Specify a non-existent file.

ANR8675E (S/390)File name: File already exists for File Exit.

Explanation: The specified file already exists and the file-exit option was set to PRESERVE.

System Action: Server continues running.

User Response: Specify a non-existent file.

ANR8675E (Solaris)File name with environment variable DSMSERV_DIR: File already exists for File/FileText Exit, overwrite option not set to YES.

Explanation: The specified file already exists and the overwrite option was not set to Yes.

System Action: Server continues running.

User Response: Specify another file or set the overwrite option to YES in the server options file.

ANR8675E (Windows NT)File name with path within registry.: File already exists for File or FileText Exit.

Explanation: The specified file already exists and the File/FileText exit option was set to PRESERVE.

System Action: Server continues running.

User Response: Specify a non-existent file.

ANR8676E (S/390)User specified module: Cannot load into server, system errno = Error number generated by MVS.

Explanation: The server was unable to load the module specified. The module is not a properly C-compiled/linked dynamic module or an ASSEMBLER/PLI compiled module.

System Action: Server continues running.

User Response: Use the server supplied sample user-exit files as a starting point.

ANR8677E (AIX)User specified module, with environment variable DSMSERV_DIR: Cannot load into server, system errno = Error number generated by AIX.

Explanation: The server was unable to load the module specified. The module is not a properly C-compiled and linked dynamic module.

System Action: Server initialization stops or server continues running if already up.

User Response: Use the server supplied sample makefile and export files to compile-link the user-exit module. Make sure the export.ref file contains the server-defined function name, and the module actually contains the server-defined function name, with one void parameter declared.

ANR8677E (HP-UX)User specified module, with environment variable DSMSERV_DIR: Cannot load into server, system errno = Error number generated by HP-UX.

Explanation: The server was unable to load the module specified. The module is not a properly C-compiled and linked dynamic module.

System Action: Server initialization stops or server continues running if already up.

User Response: Use the server supplied sample makefile and export files to compile-link the user-exit module. Make sure the export.ref file contains the server-defined function name, and the module actually contains the server-defined function name, with one void parameter declared.

ANR8677E (S/390)The user-exit module loaded does not match with type specified in options file.

Explanation: The server was able to load a module, but the type of the module did not match the type specified in the server options file

System Action: Server initialization stops or server continues running if already up. The module is unloaded.

User Response: Check the user-exit module compilation type. Make sure it matches with what is specified in the options file. Only C, Assembler, and PLI compiled modules are supported.

ANR8677E (Solaris)User specified module, with environment variable DSMSERV_DIR: Cannot load into server, system errno = Error number generated by Solaris.

Explanation: The server was unable to load the module specified. The module is not a properly C-compiled and linked dynamic module.

System Action: Server continues running.

User Response: Use the server supplied sample makefile, c, and h files to generate the user-exit module. Make sure the module contains server-defined function name adsmV3UserExit, and the module actually contains the server-defined function name, with one void * parameter declared, and returns void.

ANR8677E (Windows NT)User specified module, with path within registry: Cannot load into server, system errno = Error number generated by NT.

Explanation: The server was unable to load the module specified. The module is not a properly C-compiled and linked dynamic module.

System Action: Server continues running.

User Response: Use the server supplied sample makefile compile-link the user-exit module.

ANR8678E (AIX)Cannot bind User specified module, with environment variable DSMSERV_DIR into server, system errno = Error number generated by AIX.

Explanation: The server was unable to bind with the module specified.

System Action: Server initialization stops or server continues running if already up.

User Response: Use the server supplied sample makefile and export files to compile-link the user-exit module. Make sure the export.ref file contains the server-defined function name, and the module actually contains the server-defined function name, with 1 void parameter declared. The module may contain a global variable name that conflicts with the server's.

ANR8678E (HP-UX)Cannot bind User specified module, with environment variable DSMSERV_DIR into server, system errno = Error number generated by HP-UX.

Explanation: The server was unable to bind with the module specified.

System Action: Server initialization stops or server continues running if already up.

User Response: Use the server supplied sample makefile and export files to compile-link the user-exit module. Make sure the export.ref file contains the server-defined function name, and the module actually contains the server-defined function name, with one void parameter declared. The module may contain a global variable name that conflicts with the server's.

ANR8678E (Solaris)Cannot bind User specified module, with environment variable DSMSERV_DIR into server, system errno = Error number generated by Solaris.

Explanation: The server was unable to bind with the module specified. The server could not find a function named adsmV3UserExit in the module.

System Action: Server continues running.

User Response: Use the server supplied sample makefile, c and header files to create the user exit module. Make sure the shared library module contains a function named adsmV3UserExit of type void, with one parameter of a void *.

ANR8678E (Windows NT)Cannot find/set User specified function name within DLL. in User specified DLL library name, with registry path, system errno = Error number generated by NT.

Explanation: The server was unable to find and/or bind with the function name in the DLL specified.

System Action: Server continues running.

User Response: Use the server supplied sample makefile to compile-link the user-exit module. Make sure there is a function name in the DLL as specified in the server options file. Make sure the function only accepts one argument, a void pointer.

ANR8679W (AIX)There is already an user-exit loaded.

Explanation: There was a previous successful load of an user-exit module, thus server cannot load another one.

System Action: Server initilization stops or server continues running if already up.

User Response: To load a new user-exit module, halt the server and then restart the server with the new user-exit module.

ANR8679W (HP-UX)There is already an user-exit loaded.

Explanation: There was a previous successful load of an user-exit module, thus server cannot load another one.

System Action: Server initialization stops or server continues running if already up.

User Response: To load a new user-exit module, the server must be halted and then restart the server with the new user-exit module.

ANR8679W (Solaris)Unable to unload user exit module: system errno = Error number generated by Solaris.

Explanation: The server was not able to unload the user-exit module.

System Action: Server continues running.

User Response: The server should be stopped at the earliest possible time before the user exit is to be reactivated.

ANR8679W (Windows NT)There is already an user-exit loaded.

Explanation: There was a previous successful load of an user-exit module, thus server cannot load another one.

System Action: Server continues running.

User Response: To load a new user-exit module, halt the server and then restart the server with the new user-exit module.

ANR8680W (AIX)There is already a file used for the file or filetext exit.

Explanation: There was a previous file open for the file or filetext exit. The server cannot open another one.

System Action: Server initialization stops or server continues running if already up.

User Response: To start a new file for the file or filetext exit, halt the server, then restart the server with the new file name.

ANR8680W (HP-UX)There is already a file used for the file or filetext exit.

Explanation: There was a previous file open for the file or filetext exit. The server cannot open another one.

System Action: Server initialization stops or server continues running if already up.

User Response: To start a new file for the file or filetext exit, halt the server, then restart the server with a new file name.

ANR8680W (Solaris)There is already a named file used for the file or filetext exit.

Explanation: There was a previous file open for the file or filetext exit. The server cannot open another one.

System Action: Server initialization stops or server continues running if already up.

User Response: To start a new file for the file or the filetext exit, halt the server, then restart the server with a new file name.

ANR8680W (Windows NT)There is already a file used for the file or filetext exit.

Explanation: There was a previous file open for the file or filetext exit. The server cannot open another one.

System Action: Server continues running.

User Response: To start a new file for the exit, halt the server, then restart the server with a new file name.

ANR8681I (AIX)Connected to Tivoli event server at node name on port port.

Explanation: The server successfully established a connection with the Tivoli event server on the specified node name and port.

System Action: The server sends events to the Tivoli event server using this connection.

User Response: None.

ANR8681I (HP-UX)Connected to Tivoli event server at node name on port port.

Explanation: The server successfully established a connection with the Tivoli event server on the specified node name and port.

System Action: The server sends events to the Tivoli event server using this connection.

User Response: None.

ANR8681I (S/390)Connected to Tivoli event server at node name on port port.

Explanation: The server successfully established a connection with the Tivoli event server on the specified node name and port.

System Action: The server sends events to the Tivoli event server using this connection.

User Response: None.

ANR8681I (Solaris)Connected to Tivoli event server at node name on port port.

Explanation: The server successfully established a connection with the Tivoli event server on the specified node name and port.

System Action: The server sends events to the Tivoli event server using this connection.

User Response: None.

ANR8681I (Windows NT)Connected to Tivoli event server at node name on port port.

Explanation: The server successfully established a connection with the Tivoli event server on the specified node name and port.

System Action: The server sends events to the Tivoli event server using this connection.

User Response: None.

ANR8682E (AIX)Unable to determine port of Tivoli event server on node name.

Explanation: The server was unable to determine the TCP/IP port on which the Tivoli event server on node name is listening.

System Action: Event logging to the Tivoli event server is disabled.

User Response: Ensure that the Tivoli event server is running on the specified system. If the system on which the event server is running does not support the TCP/IP Portmapper, then ensure that TECPORT is specified in the server options file.

ANR8682E (HP-UX)Unable to determine port of Tivoli event server on node name.

Explanation: The server was unable to determine the TCP/IP port on which the Tivoli event server on node name is listening.

System Action: Event logging to the Tivoli event server is disabled.

User Response: Ensure that the Tivoli event server is running on the specified system. If the system on which the event server is running does not support the TCP/IP Portmapper, then ensure that TECPORT is specified in the server options file.

ANR8682E (S/390)Unable to determine port of Tivoli event server on node name.

Explanation: The server was unable to determine the TCP/IP port on which the Tivoli event server on node name is listening.

System Action: Event logging to the Tivoli event server is disabled.

User Response: Ensure that the Tivoli event server is running on the specified system. If the system on which the event server is running does not support the TCP/IP Portmapper, then ensure that TECPORT is specified in the server options file.

ANR8682E (Solaris)Unable to determine port of Tivoli event server on node name.

Explanation: The server was unable to determine the TCP/IP port on which the Tivoli event server on node name is listening.

System Action: Event logging to the Tivoli event server is disabled.

User Response: Ensure that the Tivoli event server is running on the specified system. If the system on which the event server is running does not support the TCP/IP Portmapper, then ensure that TECPORT is specified in the server options file.

ANR8682E (Windows NT)Unable to determine port of Tivoli event server on node name.

Explanation: The server was unable to determine the TCP/IP port on which the Tivoli event server on node name is listening.

System Action: Event logging to the Tivoli event server is disabled.

User Response: Ensure that the Tivoli event server is running on the specified system. If the system on which the event server is running does not support the TCP/IP Portmapper, then ensure that TECPORT is specified in the server options file.

ANR8683E (AIX)Unable to connect to the Tivoli event server at node name on port port.

Explanation: The server was unable to establish a TCP/IP connection with the Tivoli event server on node name at port port.

System Action: Event logging to the Tivoli event server is disabled.

User Response: Ensure that the Tivoli event server is running on the specified system. If the system on which the event server is running does not support the TCP/IP Portmapper, then ensure that the value specified for TECPORT in the server options file is correct.

ANR8683E (HP-UX)Unable to connect to the Tivoli event server at node name on port port.

Explanation: The server was unable to establish a TCP/IP connection with the Tivoli event server on node name at port port.

System Action: Event logging to the Tivoli event server is disabled.

User Response: Ensure that the Tivoli event server is running on the specified system. If the system on which the event server is running does not support the TCP/IP Portmapper, then ensure that the value specified for TECPORT in the server options file is correct.

ANR8683E (S/390)Unable to connect to the Tivoli event server at node name on port port.

Explanation: The server was unable to establish a TCP/IP connection with the Tivoli event server on node name at port port.

System Action: Event logging to the Tivoli event server is disabled.

User Response: Ensure that the Tivoli event server is running on the specified system. If the system on which the event server is running does not support the TCP/IP Portmapper, then ensure that the value specified for TECPORT in the server options file is correct.

ANR8683E (Solaris)Unable to connect to the Tivoli event server at node name on port port.

Explanation: The server was unable to establish a TCP/IP connection with the Tivoli event server on node name at port port.

System Action: Event logging to the Tivoli event server is disabled.

User Response: Ensure that the Tivoli event server is running on the specified system. If the system on which the event server is running does not support the TCP/IP Portmapper, then ensure that the value specified for TECPORT in the server options file is correct.

ANR8683E (Windows NT)Unable to connect to the Tivoli event server at node name on port port.

Explanation: The server was unable to establish a TCP/IP connection with the Tivoli event server on node name at port port.

System Action: Event logging to the Tivoli event server is disabled.

User Response: Ensure that the Tivoli event server is running on the specified system. If the system on which the event server is running does not support the TCP/IP Portmapper, then ensure that the value specified for TECPORT in the server options file is correct.

ANR8684E (AIX)Unable to connect to the Tivoli event server because TCP/IP is not available.

Explanation: The server was unable to establish a TCP/IP connection with the Tivoli event server because TCP/IP services were not available.

System Action: Event logging to the Tivoli event server is disabled.

User Response:

ANR8684E (HP-UX)Unable to connect to the Tivoli event server because TCP/IP is not available.

Explanation: The server was unable to establish a TCP/IP connection with the Tivoli event server because TCP/IP services were not available.

System Action: Event logging to the Tivoli event server is disabled.

User Response:

ANR8684E (S/390)Unable to connect to the Tivoli event server because TCP/IP is not available.

Explanation: The server was unable to establish a TCP/IP connection with the Tivoli event server because TCP/IP services were not available.

System Action: Event logging to the Tivoli event server is disabled.

User Response:

ANR8684E (Solaris)Unable to connect to the Tivoli event server because TCP/IP is not available.

Explanation: The server was unable to establish a TCP/IP connection with the Tivoli event server because TCP/IP services were not available.

System Action: Event logging to the Tivoli event server is disabled.

User Response:

ANR8684E (Windows NT)Unable to connect to the Tivoli event server because TCP/IP is not available.

Explanation: The server was unable to establish a TCP/IP connection with the Tivoli event server because TCP/IP services were not available.

System Action: Event logging to the Tivoli event server is disabled.

User Response:

ANR8700I (AS/400)Device type volume volume name has been deleted.

Explanation: The specified volume has been deleted by the server. If the given device type is OPTICAL, the volume can be initialized for re-use by another application or the ADSM server if desired.

System Action: The volume is removed from the server's inventory.

User Response: No action is required.

ANR8701I (AS/400)End-of-side reached for device type volume volume name.

Explanation: The server has detected an end-of-side condition for the given two sided volume.

System Action: The server will access the second side of the volume.

User Response: None.

ANR8702I (AS/400)Initializing side side of device type volume volume name.

Explanation: The server has started to initialize the given side of the specified volume in preparation for a server operation. Since the volume is two-sided, this message specifies which side (A or B) is being initialized by the server for I/O operations.

System Action: The server waits for the given side of the volume to be initialized.

User Response: Failure to initialize the volume prevents the server from completing an operation. In the case of a failure, subsequent messages will provide the AS/400 exception encountered during the attempted initialization. Evaluate both the specified exception and the AS/400 action to determine the steps necessary to correct the problem.

ANR8703I (AS/400)device type volume volume name is ready for operations.

Explanation: The initialization process for the given volume has completed successfully, and the volume is ready for use.

System Action: The volume is made ready for use.

User Response: None.

ANR8704E (AS/400)Initialization failed for device type volume volume name.

Explanation: Initialization of the given volume has failed and has prevented the server from completing an operation.

System Action: Server operation ends.

User Response: Check previously issued messages for additional information regarding the error. Evaluate both the specified exception and the AS/400 action to determine the steps necessary to correct the problem.

ANR8705I (AS/400)Device type volume volume name is mounted mount mode, status: MSGW.

Explanation: In response to a QUERY MOUNT command, the server indicates that the given volume is mounted for I/O operations. The volume is currently in MSGW, meaning the AS/400 job that is processing the given volume for the ADSM server is waiting for a reply to a message on an AS/400 message queue. Locate the AS/400 message and provide an appropriate reply. The job should be located in the QSYSWRK subsystem.

System Action: The server waits for a reply to the AS/400 message.

User Response: Locate the AS/400 message and provide an appropriate reply.

ANR8706E (AS/400)Job job number for volume volume name is in status: MSGW.

Explanation: The specified AS/400 job is processing the given volume for the ADSM server. The status of the job indicates that the job is waiting for a reply to a message on an AS/400 message queue. Locate the AS/400 message and provide an appropriate reply. The job should be located in the QSYSWRK subsystem.

System Action: The server waits for a reply to the AS/400 message.

User Response: Locate the AS/400 message and provide an appropriate reply.

ANR8707W (AS/400)Access state for volume volume name in library library name has been set to "unavailable".

Explanation: The specified volume encountered an error during mount processing that makes it unusable. The access state of the volume in the library volume inventory is changed to unavailable so that the volume is not selected for future mounts. One of the following may be the cause of the error. The volume may already be queued for use in the media library device. The volume may be mounted in another tape resource that is not available to the media library device. The volume was marked not available, or in error by the library device manager. The volume identifier may be a duplicate. The volume may have been manually ejected from the library device.

System Action: The server sets the volume access state to unavailable. If the server operation requires a scratch volume, processing continues with another scratch volume. If the server operation required the given volume, the operation is terminated.

User Response: Check previously issued ADSM messages for additional information regarding the error. Check the spooled files of the AS/400 user that started the ADSM server for messages that describe the problem with the given volume. The AS/400 Display Tape Cartridge (DSPTAPCTG) command can be used to display the attributes of a tape volume. Once the problem is corrected, update the access state of the volume to available by using the UPDATE LIBVOL command. An audit of the ADSM library will also result in a re-evaluation of the condition of the volume. If the volume is usable, its access state will be changed to available. An audit of the ADSM library occurs automatically during server initialization or an audit of the library can be started with the AUDIT LIBRARY command.

ANR8708W (AS/400)The characteristics of device device name have changed: current device type new device type, original device type old device type.

Explanation: The current characteristics of the designated device do not match the characteristics of the device when it was originally defined to the server. Either the device type has changed or the supported formats have changed. One of the following may be the cause of the change. The original device may have been replaced with a new device. The AS/400 configuration has changed resulting in different names being assigned to existing devices. The original device may have been upgraded to a new model. The new device characteristics will be used. This may result in no devices capable of supporting tape operations for the original characteristics. If such problems should occur, server operations will fail and the will server issue additional error messages.

System Action: Server processing continues.

User Response: You must determine if the change in device characteristics is acceptable given the DEVICE CLASS definitions of the server. The AS/400 WRKHDWRSC and WRKDEVD commands can be used to display the information for a device. The QUERY DEVCLASS command can be used to evaluate server definitions. If necessary, you may need to take actions to correct the change in characteristis of the specified device. If possible, change the AS/400 configuration so that it again matches the server definition. Once the problem is corrected, the server must be halted and restarted so that the server may re-evaluate the device. If the change is correct but server operations are failing, you will need to modify the server definitions. If the device is associated with a server DRIVE definition, delete the old drive definition with a DELETE DRIVE command, and define a new drive. The UPDATE DRIVE command cannot be used in this case. If the device is associated with a server LIBRARY definition, delete the old library definition with a DELETE LIBRARY command, and define a new LIBRARY. The UPDATE LIBRARY command cannot be used in this case.

ANR8709E (AS/400)Request number: Wrong type of device type volume (volume name) mounted in device device name for device class device class.

Explanation: The server detects an error while attempting to open the given volume in the specified device. The format specified on the given device class is not a valid format that can be written to this volume.

System Action: The volume is dismounted.

User Response: Use a volume that allows the format associated with a the device class to be written or specify a format on the device class that can be written to this type of volume. Use the UPDATE DEVCLASS command to change the format for the device class.

ANR8740WNumber of automated library slots (slots in use) exceeds license terms (slots licensed).

Explanation: The number of slots in use within automated libraries exceeds the licensed value.

System Action: The operation completes.

User Response: Contact your service representative to update license values for slots in automated libraries, or reduce the number of slots in use by issuing CHECKOUT LIBVOLUME commands as necessary.

ANR8741ECHECKIN LIBVOLUME not permitted with current license terms.

Explanation: The CHECKIN LIBVOLUME operation is not permitted because the current license terms do not allow it.

System Action: The command fails.

User Response: Contact your service representative to update license values for slots in automated libraries, or reduce the number of slots in use by issuing CHECKOUT LIBVOLUME commands as necessary.

ANR8742EThis server is not licensed to support the device type device type. Device Support Module module number is required.

Explanation: A DEFINE DRIVE command or a volume mount operation cannot be processed because the server is not licensed to support the required device type.

System Action: The operation fails.

User Response: Contact your service representative to update the server license terms so that support for the required device type is enabled.

ANR8743EThis server is not licensed to support library device name. Device Support Module module number is required.

Explanation: Either a DEFINE LIBRARY command, a volume mount operation, or library initialization cannot be processed because the server is not licensed to support the given library.

System Action: The operation fails.

User Response: Contact your service representative to update the server license terms so that support for the given library device is enabled.

ANR8744ECommand: Current license terms do not permit this operation.

Explanation: The specified command failed because the current license terms do not permit it.

System Action: The operation fails.

User Response: Contact your service representative to update the server license terms so that the requested operation can be processed.

ANR8745ESupport for the 3590 device type is disabled for library library name.

Explanation: The requested operation fails because support for the 3590 device type is not currently enabled for the specified library.

System Action: The operation fails.

User Response: Make sure the ENABLE3590LIBRARY option is specified in the server options file, and that the scratch category number for 3590 volumes does not conflict with the private category or the CARTRIDGE volume scratch category.

ANR8746EDevice type device type is not supported in this release.

Explanation: The specified device type cannot be used by this release/platform of the server.

System Action: The device cannot be used.

User Response: Contact your sales or service representative to upgrade to the latest release of the server.

ANR8747IChecking in volume volume name in library library name- CANCEL PENDING.

Explanation: In response to a QUERY PROCESS command, this message displays the status for a CHECKIN LIBVOLUME process on the server. The given volume was being checked in to the designated library, but the process was canceled by an administrator.

System Action: The background process operation is in a wait queue. When the process comes off the queue, it will be terminated.

User Response: None.

ANR8748IChecking in volumes in search mode in library library name- CANCEL PENDING.

Explanation: In response to a QUERY PROCESS command, this message displays the status for a CHECKIN LIBVOLUME process on the server. Volumes were being checked into the given library in search mode, but the process was canceled by an administrator.

System Action: The background process operation is being terminated.

User Response: None.

ANR8749ELibrary order sequence check on library library name.

Explanation: An attempt has been made to mount or demount a volume, but the attempt fails for one of the following reasons:

System Action: The operation fails.

User Response: This error usually occurs when a demount fails and a cartridge is left in the drive. All subsequent mounts fail while attempting to insert another cartridge into the same drive. Demount the cartridge using the library manager or perform an AUDIT LIBRARY operation on the designated library. Retry the operation.

ANR8750EVolume is incompatible with specified device type in library library name.

Explanation: An attempt has been made to mount or check in a volume, but the attempt fails because the cartridge being mounted is not compatible with the drive (For example, attempting to mount a 3590 cartridge on a 3490 drive).

System Action: The operation fails.

User Response: Ensure the DEVTYPE parameter on the CHECKIN command matches the device type of the drive. Retry the operation.

ANR8751WThis server is not licensed to support the device type device type. Advanced Device Support is required.

Explanation: This message is issued when a DEFINE DRIVE command or a volume mount operation uses a device class that is not licensed on the server.

System Action: The operation fails if this is a try-and-buy server. For purchased servers, this message is to warn you that you are not in compliance with registered license terms.

User Response: Contact your service representative to update the server license terms so that support for the required device type is enabled.

ANR8752WThis server is not licensed to support library device type. Advanced Device Support is required.

Explanation: This message is issued when a DEFINE LIBRARY command or a volume mount operation uses a device class that is not licensed on the server.

System Action: The operation fails if this is a try-and-buy server. For purchased servers, this message is to warn you that you are not in compliance with registered license terms.

User Response: Contact your service representative to update the server license terms so that support for the required device type is enabled.

ANR8760ICancel in progress.

Explanation: The MOVE MEDIA command has been canceled and will end when resources have been freed for the background process. This message may be displayed in response to a QUERY PROCESS command for a MOVE MEDIA command.

System Action: Server operation continues.

User Response: None.

ANR8761INumber of volumes processed: number

Explanation: The MOVE MEDIA command has processed the number of volumes displayed. This message may be displayed in response to a QUERY PROCESS command for a MOVE MEDIA command.

System Action: Server operation continues.

User Response: None.

ANR8762INumber of volumes processed: number. Ejecting volume volume name from library library name.

Explanation: The MOVE MEDIA command displays the number of volumes already processed and the name of the volume currently being ejected from the indicated library. This message may be displayed in response to a QUERY PROCESS command for a MOVE MEDIA command.

System Action: Server operation continues.

User Response: None.

ANR8763ECommand: Volume volume name not processed: library library name not defined.

Explanation: The indicated volume is not processed since the designated library has not been defined or has been deleted.

System Action: The volume is not processed.

User Response: Reissue the command using a different library name, or define the library before retrying the command.

ANR8764ECommand: Volume volume name not processed: the operation is not allowed for library type library type.

Explanation: The indicated volume is not processed since the requested operation is not allowed for libraries of the given type.

System Action: The volume is not processed.

User Response: None.

ANR8765IRequest number: device type volume volume name in location location name is required for use in library library name; CHECKIN LIBVOLUME required within time limit minutes.

Explanation: A mount request has been made for a volume that is defined in a storage pool, but which is currently checked out of the given library and stored in the location shown.

System Action: The server waits until it detects that the volume has been checked into the library, or the time limit expires.

User Response: Obtain the required volume from the indicated location, and insert it into the library by issuing a CHECKIN LIBVOLUME command. Use the SWAP=YES option of the CHECKIN LIBVOLUME command if the library is currently full; this process allows the server to select an appropriate volume to be swapped out in order to make room for the required volume.

ANR8766IMOVE MEDIA command: CHECKOUT LIBVOLUME command for volume volume name in library library name completed successfully; Place the ejected volume in location location name.

Explanation: The CHECKOUT LIBVOLUME operation has completed successfully for the indicated volume in the given library. Place the ejected volume in the indicated location.

System Action: The volume is either deleted from the library inventory (if its status is something other than DATA) or marked not present (if its status is DATA).

User Response: If an *UNKNOWN* location is displayed, issue UPDATE STGPOOL OVFLOCATION command to define an overflow location name to be used on the subsequent MOVE MEDIA command. For the volumes ejected with an *UNKNOWN* location, use UPDATE VOLUME LOCATION command to update its location to your overflow location name.

ANR8767INumber of volumes processed: number volumes processed. Volumes sent to library library name for checkout: number volumes sent.

Explanation: The MOVE MEDIA command has processed the number of volumes shown. Currently, the MOVE MEDIA command has sent for processing the number of volumes shown to the library shown. This message may be displayed in response to a QUERY PROCESS command for a MOVE MEDIA command.

System Action: Server operation continues.

User Response: None.

ANR8769EExternal media management function request type returned result=result.

Explanation: A request of the indicated function type was sent to the external library manager program, which returned a result code which was not SUCCESS.

System Action: The server continues, but the server operation that was being attempted fails.

User Response: Consult the documentation for the external media management program to determine how to recover from the error condition. Then attempt the server operation again.

ANR8770WUnable to load external library manager filespec.

Explanation: A library of LIBTYPE=EXTERNAL is defined but the server cannot load the external library manager.

System Action: The server continues, but the external library cannot be accessed.

User Response: Verify that the EXTERNALMANAGER parameter for the external library is specified correctly on the DEFINE LIBRARY or UPDATE LIBRARY command.

ANR8771EVolume volume name in library library name is deleted. External Library is not synchronized with the server. Audit required.

Explanation: The server deleted a volume from its inventory, and its attempt to inform the external library manager has failed.

System Action: The server may continue to access the library, but some volumes may not be accessible until the external library is synchronized with the server.

User Response: Perform the appropriate type of processing on the external library in order to synchronize it with the server.

ANR8772IMoving volume volume name (if known) from drive drive name to slot slot element number in library library name.

Explanation: A volume found in the drive during library initialization is being moved to the slot.

System Action: The volume is moved from the drive to the slot.

User Response: None.

ANR8773EIncompatible options CHECKLABEL=NO and SEARCH=YES for SCSI libraries.

Explanation: If a barcode reader is not installed and detected by the server, the server requires the ability to check the tape label when searching for new volumes in a SCSI tape library. The CHECKLABEL=NO and SEARCH=YES parameters on the CHECKIN LIBVOL command are not compatible.

System Action: The command fails.

User Response: Reissue the CHECKIN LIBVOL command and specify CHECKLABEL=YES.

ANR8774WVolume volume name not checked into library library name but is using category category number.

Explanation: While processing a DEFINE LIBRARY or AUDIT LIBRARY command for the given library, the server found a volume that was not checked into the library (with the CHECKIN LIBVOL command), but is assigned to one of the categories in use by that library.

System Action: If the volume category equals the value of the library SCRATCHCAT the category is changed to the value of the library PRIVATECAT. This is to prevent the library from loading the volume when a scratch volume is requested.

User Response: If the volume is to be used by the server, it does not have to be reassigned but it must be checked into the library with the CHECKIN LIBVOL command. If the volume is not to be used by the server, use the mtlib program to reassign the volume to its correct category. For details about the mtlib program, refer to the documentation provided with the library device.

ANR8775IDrive drive name unavailable at library manager.

Explanation: The specified drive availability status at the library manager has changed from available to unavailable.

System Action: The drive status on the server is updated to reflect the availability to that of the library manager. The drive will not be considered as a candidate for the mount or demount request.

User Response: Contact your service representative to determine the cause of the drive becoming unavailable. Once the service representative has determined the cause and changed the availability status to available at the library manager, the server will resume use of the drive.

ANR8776WVolume volume name in drive drive name contains lost VCR data; performance may be degraded.

Explanation: The Vital Cartridge Records of the cartridge in the drive are lost or corrupted. This results in the inability of the drive to do fast locates to file positions on the cartridge, which causes the locate performance for read or append operations to become degraded.

System Action: The server continues the operation.

User Response: There are two methods to restore the VCR data. The first method uses the MOVE DATA command to move the data off the tape and to return the tape to scratch or empty status. The VCR data is rebuilt when the empty tape is rewritten from the beginning-of-tape. The second method rebuilds the VCR by loading the tape and locating directly to the end-of-data. This is done by the server in normal use when new data is appended to the end of the tape. It can also be done independent of the server by loading the tape in an unused drive and using the tapeutil program. Select the tapeutil option "Space to End-of-Data".

ANR8777EMount for volume volume name failed; media performance is degraded.

Explanation: The VCR data on the volume is lost or corrupted, resulting in degraded tape positioning. The mount fails because the tape drive was configured to fail mounts that indicate this condition.

System Action: The client command fails and the transaction is rolled back.

User Response: Until the VCR data can be restored, the user can issue the UPDATE VOLUME command to make the volume unavailable. There are two methods to restore the VCR data. The first method uses the MOVE DATA command to move the data off the tape and to return the tape to scratch or empty status. The VCR data is rebuilt when the empty tape is rewritten from the beginning-of-tape. The second method rebuilds the VCR by loading the tape and locating directly to the end-of-data. This is done by the server in normal use whenever data is appended to the end of the tape. It can also be done independent of the server by loading the tape in an unused drive and using the tapeutil program. Select the tapeutil option "Space to End-of-Data".

ANR8778WScratch volume volume name changed to Private Status to prevent re-access.

Explanation: The scratch volume encountered an error during mount processing that makes it unusable. The status of the volume is changed to private so that it is not selected for future scratch mounts. (Although the status has become private, it is not defined to a storage pool.)

System Action: Processing continues with another scratch volume.

User Response: See previous error messages to determine the cause of the mount failure, and correct the problem. If the problem is a mislabeled volume or unreadable label, relabel the scratch volume using the dsmlabel utility with the "-overwrite" option. If the volume is missing from its home slot, issue the AUDIT LIBRARY command against the library. If the volume has lost or corrupted VCR-data, relabel the volume. (This reinitializes the VCR-data by writing to the volume from beginning-of-tape.) Once the problem is corrected, update the status of the volume to scratch by using the UPDATE LIBVOL command.

ANR8779EUnable to open drive drive name, error number=errno value from open system call.

Explanation: The drive cannot be opened by the server. In AIX, error number is the value of errno returned by the operating system. In OS/2, it is the value of the return code from the call to DosOpen.

System Action: The transaction needing the drive fails.

User Response: Use the error number in conjunction with operating system documentation to narrow the scope of the cause. Inspect the drive. Ensure the drive is powered on and ready, the cables are properly connected and terminated, and that the device is properly configured to the operating system.

ANR8780EVolume in drive drive name has no label.

Explanation: The volume in the indicated drive does not have a label. The server requires that all media be uniquely labelled.

System Action: The volume is rejected and the server prompts for a new volume.

User Response: Use the appropriate labelling utility to label the media. In OS/2 and Windows NT, the LABEL command is used to label removable disk cartridges, diskettes and other media which appear as drive letters.

ANR8781EVolume in drive drive name has invalid label label.

Explanation: The volume in the indicated drive has the label shown. The name does not conform with server requirements. The server requires that all media be uniquely labelled and, for removable media, that the label with file naming conventions. The label found exceeded the maximum label size for removable media or did not conform to server labelling requirements. If ????? is shown for the label, it indicates that server was unable to read the label.

System Action: The volume is rejected.

User Response: Use the appropriate labelling utility to label the media. In OS/2 and Windows NT, the LABEL command is used to label removable disk cartridges, diskettes and other media which appear as drive letters. This label must still conform to server requirements.

ANR8782EVolume volume name could not be accessed by library library name.

Explanation: The designated volume is in the inventory of the Library Manager, but the physical location is either inaccessible or unknown.

System Action: The operation fails. The access mode of the volume is changed to UNAVAILABLE.

User Response: Ensure that the cartridge is physically in the library, and reinventory the library. If the volume location is resolved, restore the access mode of the volume to its previous value using the UPDATE VOLUME command.

ANR8783ELabel on volume in drive drive name could not be read.

Explanation: The server was unable to read the label on the indicated drive.

System Action: The volume is rejected.

User Response: Use the appropriate labelling utility to label the media. In OS/2 and Windows NT, the LABEL command is used to label removable disk cartridges, diskettes and other media which appear as drive letters. This label must still conform to server requirements.

ANR8784EFile file name on volume drive name could not be created.

Explanation: The server was unable to create the indicated file on the indicated volume. The server creates a file on removable media in which to store data.

System Action: The volume is rejected.

User Response: Ensure that the media is not defective, and is properly formatted. Ensure that there are not large numbers of files already in the root of the file system. Some file systems have limits on the number of files that may be created in the root directory.

ANR8785EOut-of-space in file system for device type volume volume name.

Explanation: The server detected an out-of-space condition for the file system in which the given volume resides.

System Action: The operation fails.

User Response: The file system must be expanded to accommodate volume growth.

ANR8786IRequest number: Remove device type volume from entry/exit port; insert volume volume name mount mode into entry/exit port of library library name within time limit minute(s); issue 'REPLY' along with the request ID when ready.

Explanation: A CHECKIN LIBVOLUME command is in progress, and the specified volume is needed. However, there is a volume awaiting to be removed from the entry/exit port before the specified volume is inserted into the port of the given library.

System Action: The server waits until a REPLY command is issued.

User Response: Remove the volume from the library and insert the correct volume into the entry/exit port. Issue a REPLY command, along with the request ID, to tell the server that the volume has been removed and a new volume has been inserted.

ANR8787WNo barcode labels detected in library library name.

Explanation: A command is issued with the CHECKLABEL=BARCODE option. The library is unable to detect that the cartridges have valid barcode labels. The barcode reader is disabled or it is unable to read the labels.

System Action: Unless the command is checking in cleaning cartridges, the process continues by loading the cartridges into the library's drives and reading the label from the tape. Cleaning cartridges have no internal label that can be checked by loading it in the drive.

User Response: Cancel the process if you do not want to load all of the cartridges into the library's drives. Examine the cartridges to ensure they have barcode labels and they are compatible with the barcode reader. Not all vendors' labels are readable by all libraries. Check that the barcode reader is configured and functioning properly, if necessary.

ANR8788WUnable to read the barcode of cartridge in slot-id Element number of slot in library library name; loading in drive to read label.

Explanation: The library barcode reader is unable to read the label of a tape cartridge. The cartridge is found in the slot with the given element number.

System Action: The cartridge is loaded into a drive and its label will be read from the tape.

User Response: Cancel the process if you do not want to load any cartridges into the library's drives. Examine the cartridge to ensure it has a barcode label and that it is compatible with the barcode reader. Not all vendors' labels are readable by all libraries. Check that the barcode reader is configured and is functioning properly, if necessary.

ANR8789WDynamic drive recovery being attempted on device type volume volume name due to errors.

Explanation: Due to a drive or media fault, the server is moving the volume to a new drive.

System Action: Read or write operations resume on the volume once it is remounted.

User Response: None.

ANR8790Idevice type volume volume name re-mounted in drive drive name.

Explanation: Due to a drive or media fault, the server has moved the volume to the specified drive. Read or write operations resume on the volume.

System Action: The label of the volume has been verified.

User Response: None.

ANR8791EUnable to move device type volume volume name to another drive.

Explanation: Dynamic drive recovery was being attempted on the volume, but was unable to move the volume to another drive.

System Action: The originating process terminates.

User Response: See previous error messages to determine the cause of the DDR failure, and correct the problem. If the problem is an unreadable label, any data on the volume may be lost.

ANR8792EUnrecoverable drive failures on drive drive name; drive is now taken offline.

Explanation: The drive has been determined to be faulty because of recurrent failures.

System Action: The drive is now marked offline.

User Response: Service the drive for failures. Delete and redefine the drive to bring it back online.

ANR8793EDynamic drive recovery failed for device type volume volume name because not enough drives are available.

Explanation: To recover a volume on another drive, there must be at least one other drive available that is not associated with the transaction which is driving the recovery. In addition, the maximum number of drives that can have dynamic drive recovery performed at the same time is one less than the number of drives. This is to prevent deadlock from occurring between two recovering transactions. One of these criteria has failed.

System Action: No DDR is performed and the transaction fails.

User Response: Restart the transaction.

ANR8794ERetry of operation name operation failed for device type volume volume name.

Explanation: After successfully mounting the volume on another drive, due to an I/O error, the original operation fails when retried.

System Action: No further recovery is performed and the transaction fails.

User Response: Restart the transaction.

ANR8795IRetry of operation name operation for device type volume volume name is successful.

Explanation: After mounting the volume on another drive, due to an I/O error, the operation is tried successfully.

System Action: The transaction continues from the point of interruption from the failure.

User Response: None.

ANR8796WDrive drive name of library library name is not online; UPDATE DRIVE required.

Explanation: During the initialization of a library, the server finds that the drive was updated to be offline.

System Action: The drive will not be accessible by the library during tape operations.

User Response: The drive may be made online by issuing the UPDATE DRIVE command with the ONLINE=YES option.

ANR8797Wcommand: Drive drive name of library library name is inaccessible.

Explanation: The server is unable to use the mentioned drive. This may be for the following reasons:

System Action: The drive is temporarily made offline and is not used for tape operations. The server polls the drive at one-half minute intervals to check if the condition has cleared. Once the drives is accessible again, the drive is brought online.

User Response: Determine the reason the drive is inaccessible, such as hardware errors reported in the system logs. Render any needed corrections to the drive. The drive will be brought online automatically when the polling process detects that is has become accessible.

ANR8798WDrive drive name in library library name is busy; some transactions may fail.

Explanation: The drive being made offline is currently mounted with an open tape volume. If the transaction using the volume requires subsequent tape mounts and is unable to acquire a drive, the transaction will fail.

System Action: If this tape volume is one of a sequence of volumes that are required to process a transaction, a drive must be available for each mount. This may be any drive in the library, but if all other library drives are currently busy and are still busy at the time the new tape must be mounted, the transaction will fail.

User Response: If possible, make the drive online until the transaction using it ends. If there is an idle volume on the drive, dismount the volume first.

ANR8799ICommand: Operation for library library name started as process process ID.

Explanation: A LABEL process has been started to write the label on the specified volume in the given library. The process is assigned the ID specified in the message.

System Action: The server starts a background process to perform the operation in response to the LABEL command entered by an administrator.

User Response: To obtain status on the process, issue the QUERY PROCESS command. The process may be canceled with the CANCEL PROCESS command.

ANR8800ILABEL LIBVOLUME for volume volume name in library library name completed successfully.

Explanation: The background process to LABEL a volume has succeeded.

System Action: The volume's label has been rewritten.

User Response: None.

ANR8801ILABEL LIBVOLUME process process Id for library library name completed; count of labelled volumes volume(s) labelled, count of checked in volumes volume(s) checked-in.

Explanation: A search-mode process to LABEL volumes has succeeded.

System Action: The volumes have been labelled.

User Response: None.

ANR8802ELABEL LIBVOLUME process process Id for library library name failed.

Explanation: The Label process terminated with a failure.

System Action: The process ends.

User Response: See previous error messages to determine the cause of the failure, and correct the problem.

ANR8803ILABEL VOLUME process process Id for library library name has been canceled; count of labeled volumes volume(s) labeled, count of checked in volumes volume(s) checked-in.

Explanation: A background server process that has been working to label the volumes for the given library is canceled by the CANCEL PROCESS command. The counts provided are for any volumes processed prior to the cancel.

System Action: The server process is ended and server operation continues.

User Response: None.

ANR8804ILabelling volume volume name in library library name.

Explanation: In response to a QUERY PROCESS command, this message displays the status for a LABEL process on the server.

System Action: The background process continues.

User Response: None. The process may be cancelled by an authorized administrator using the CANCEL PROCESS command.

ANR8805ILabelling volumes in library library name; volume count volumes(s) labelled.

Explanation: In response to a QUERY PROCESS command, this message displays the status of a LABEL process with the SEARCH option.

System Action: The background process continues.

User Response: None. The process may be cancelled by an authorized administrator using the CANCEL PROCESS command.

ANR8806ECould not write volume label volume name on the tape in library library name.

Explanation: The Label process could not write the label on the tape specified.

System Action: For a LABEL operation with SEARCH=YES, the background process continues to the next volume. For an individual volume, the process ends. The volume is not labelled and is not checked into the library.

User Response: Make sure the library and drive devices associated with this command are powered on and ready, and then reissue the command.

ANR8807WCould not write label volume name on the volume in drive drive name of library library name because volume is already labelled existing volume name.

Explanation: The check in or label process could not write the label on the tape specified because the volume is already labelled.

System Action: The check in process will not overwrite volumes that are already labelled, and the label process will only overwrite volumes when OVERWRITE=YES is specified. The volume is not labelled and cannot be checked in to the library. If SEARCH=YES, the process continues to the next volume. For an individual volume, the process ends.

User Response: Reissue the command with the correct parameters.

ANR8808ECould not write label label name on the volume in drive drive name of library library name because that volume is already labeled with volume name which is still defined in a storage pool or volume history.

Explanation: An attempt was made to overwrite the label of a volume that is still defined to a storage pool or is still found in the volume history file. Such a volume may still contain valid data.

System Action: The server process is ended and server operation continues.

User Response: It is usually not necessary to re-label volumes. If the volume must be relabeled, that volume must first be removed from the storage pool or volume history file where it is defined.

ANR8809IRequest number: Please provide the label name for the volume in slot element slot element number of library library name by issuing REPLY n LABEL=xxx within time limit minutes, where n is the re quest ID and xxx is the desired label name.

Explanation: A LABEL LIBVOLUME command is in progress, and the name of the next volume is needed.

System Action: The server waits until a REPLY command is issued.

User Response: Issue a REPLY command, along with the request ID, and the volume name for the next cartridge.

ANR8810IVolume volume name has been labeled in library library name.

Explanation: The Label process with the search option has found and labeled a volume.

System Action: The process ends.

User Response: None.

ANR8811ECommand: The LABELSOURCE parameter is required when using SEARCH with this command.

Explanation: The LABELSOURCE parameter must be provided with the given command.

System Action: The command is not processed.

User Response: Reissue the command, and provide a valid LABELSOURCE parameter value.

ANR8812ECommand: The SEARCH parameter is required when using LABELSOURCE with this command.

Explanation: When using the LABELSOURCE option with this command, the SEARCH parameter must be also provided.

System Action: The command is not processed.

User Response: Reissue the command, and provide a valid SEARCH parameter value.

ANR8813WUnable to read the barcode of cartridge in slot element Element number of slot in library library name.

Explanation: The library barcode reader is unable to read the label of a tape cartridge. The cartridge is found in the slot with the given element number.

System Action: When LABELSOURCE=BARCODE is specified on the LABEL LIBVOLUME command, volumes without a barcode cannot be labelled.

User Response: Examine the cartridge to ensure it has a barcode label and that it is compatible with the barcode reader. Not all vendors' labels are readable by all libraries. Check that the barcode reader is configured and is functioning properly, if necessary.

ANR8814IRemove volume Volume name from slot element Slot element number of library Library name.

Explanation: LABEL LIBVOLUME has ended for the specified volume and that volume must be removed from the library because either it was not checked in or there was an error.

System Action: The server continues normal operation.

User Response: Remove the specified volume from the library.

ANR8815IRemove volume Volume name from port element Port element number of library Library name.

Explanation: LABEL LIBVOLUME has ended for the specified volume and that volume must be removed from the library because either it was not checked in or there was an error.

System Action: The server continues normal operation.

User Response: Remove the specified volume from the library.

ANR8816Ecommand: Volume Volume name in library Library name cannot be labelled because it is currently defined in a storage pool or in the volume history file.

Explanation: During command command processing, a volume cannot be used because there is a storage pool volume defined or a volume in the volume history file with this volume name. Such a volme may still contain valid data. Applying the volume name to the cartridge can overwrite data and or cause library inventory corruption. If the volume is in the volume history file, it is has previously used by an export, database dump, or database backup operation (as recorded in the volume history).

System Action: If the SEARCH=YES option was specified, the current volume is skipped and command processing continues with the next volume found. If SEARCH=NO was specified, command processing terminates.

User Response: If the volume is present in an automated library, it should either be removed or checked into the library's inventory in the PRIVATE category.

ANR8817EName length for volume "Volume name" invalid; max is Maximum name length.

Explanation: During LABEL LIBVOL processing, the volume name provided to be written on the label exceeds the maximum length for the type of cartridge.

System Action: The label process fails for that cartridge.

User Response: Reissue the LABEL LIBVOL command and provide a volume name that is not longer than the maximum listed.

ANR8818EI/O Error on library library name; request for op. operation/function to the 3494 Library Manager has timed out.

Explanation: A command for the operation was issued to the Library Manager and a response was not received within the maximum timeout period.

System Action: The operation and the transaction fails.

User Response: Verify that communications with the library is operational, that it is online and ready for commands. Increase the time-out limit of the Library Manager Control Point device driver. If the problem persists, provide your service representative with the 3494 Library Manager transaction logs.

ANR8819ENo barcode reader detected in library library name.

Explanation: A LABEL command was issued with the LABELSOURCE=BARCODE option. The library was unable to detect that the cartridges had valid barcode labels or the library did not have a barcode reader. If a barcode reader is present the reader might be disabled or it is unable to read the labels.

System Action: Examine the cartridges to ensure they have barcode labels and they are compatible with the barcode reader. Not all vendors' labels are readable by all libraries. Check that the barcode reader is configured and functioning properly.

User Response: None.

ANR8820WRepairing VCR data for Volume volume name in drive drive name; dismount may be delayed.

Explanation: The Vital Cartridge Records of the cartridge in the drive are lost or corrupted, which results in the inability of the drive to do fast locates to file positions on the cartridge. The VCR is being rebuilt during the volume dismount process in order to avoid performance degradation on future mounts of the volume.

System Action: The server continues the dismount operation. There may be a long delay because the VCR is rebuilt by spacing the tape forward to the end-of-data.

User Response: None.

ANR8821EBarcode of element slot element address, 'hardware barcode string', exceeds maximum length characters in length.

Explanation: A barcode is encountered that was longer than a valid volume name.

System Action: The barcode is not considered valid and will not be used for the server process.

User Response: Replace the cartridge's barcode with one that is supported by the library and whose number of characters does not exceed the maximum length.

ANR8822E'Volume name' is not a valid volume name.

Explanation: The specified string is not a valid volume name.

System Action: The program prompts for a new volume name.

User Response: Enter a volume name that is within the length constraints for the media type being labeled, and which contains only alphanumeric characters.

ANR8823EHardware configuration error in library library name: number of drives drives, number of storage slots storage slots.

Explanation: The library device returned a count of zero for either the drives or the slots. The drives may have not yet been configured to the operating system, or to the library. The library must have at least one drive and multiple slots when properly configured in order to be defined to the server.

System Action: The operation fails.

User Response: Configure the drives to the operating system, and reinitialize the library.

ANR8824EI/O Error on library library name; request request id for operation operation/function to the 3494 Library Manager been lost.

Explanation: A command for the operation was issued to the Library Manager and a response was not received within the maximum timeout period.

System Action: The operation and the transaction fails.

User Response: Verify that communications with the library is operational, that it is online and ready for commands. If the problem persists, provide your service representative with the 3494 Library Manager transaction logs and the request id from the failed operation.

ANR8825E'Volume range' is not a valid volume range.

Explanation: The specified string is not a valid volume range.

System Action: The program prompts for a new volume range.

User Response: Enter the volume names in the range that is within the length constraints for the media type being labeled, and which contains only alphanumeric characters. The volume names of the begining and ending volume must be the same in length and the incrementals must be in digits.

ANR8826ENo Entry/Exit found on library library name.

Explanation: A CHECKIN LIBVOLUME SEARCH=BULK command was issued on a library that has no Entry/Exit ports.

System Action: None.

User Response: None.

ANR8827ENo Entry/Exit port is available on library library name.

Explanation: A CHECKOUT LIBVOL command was issued on a library where all its Entry/Exit Ports were found to be full.

System Action: None.

User Response: Empty all the Entry/Exit ports on the library and try the command again.

ANR8828ESlot element number of library library name is inaccessible.

Explanation: The slot in the library could not be physically accessed at this time.

System Action: None.

User Response: Verify that the Entry/Exit door is closed and the device has not logged any device errors before trying the command again.

ANR8829IRemove volume volume name from slot element number of library library name at your convenience.

Explanation: A volume has been checked out from the library and placed in a multiple entry/exit port library. The volume needs to be removed from the library, but the operation is not critical.

System Action: None.

User Response: Remove the volume from the entry/exit slot.

ANR8830EInternal Device type drive diagnostics detect excessive media failures for volume Volume name (MIM MIM Code). Access mode is now set to "read-only".

Explanation: The tape drive's microcode performed an analysis of the media during the prior mount of the volume and determined that the number of temporary errors and other indicators exceed the threshold for reliable data recording.

System Action: The volume is made read-only.

User Response: Check system error logs for entries made by the device relative to media errors. It is recommended to move the data off the volume in order to minimize the impact of future errors and further damage to the media.

ANR8831WBecause of media errors for volume Volume name, data should be removed as soon as possible.

Explanation: Errors previously encountered on the volume leave the access to the data in a questionable state. The errors may be permanent temporary media failures such as the corruption of the Volume Control Region of a Magstar drive.

System Action: None.

User Response: Move the data off the volume. This can be done with the MOVE DATA command. In some cases the tape is reusable by returning it to scratch. Check system error logs for entries made by the device relative to media errors. If the errors cannot be isolated ore resolved, contact your support representative. Return the tape to scratch or dispose of it.

ANR8832ECHECKIN LIBVOLUME for volumes in search mode in library library name failed.

Explanation: The background process for a CHECKIN LIBVOLUME command has failed.

System Action: The background process ends, but volumes have not been checked into the library.

User Response: Make sure the library and drive devices associated with this command are powered on and ready, and then reissue the command.

ANR8833ECommand: Volume volume name in library library name is currently being checked in or checked out.

Explanation: The command cannot be processed because the specified volume is being checked in or checked out of the library.

System Action: The command is not processed.

User Response: Wait until the conflicting checkin or checkout has completed, and then reissue the command.

ANR8834ELibrary volume volume name is still present in library library name drive drive name, and must be removed manually.

Explanation: Library operations cannot be performed using the drive because a volume is still mounted in it. This may be due to a prior dismount failure that occurred on the drive.

System Action: The command fails. The drive may be taken offline.

User Response: See previous error messages and the system error logs to determine the cause of the dismount failure or any other reason the volume would still be loaded in the drive. Hardware diagnostics may be required. If neccessary, remove the volume manually and place it in its storage cell. If the storage cell is unknown, place the volume in any cell and issue the AUDIT LIBRARY command. Use the QUERY DRIVE command to determine the online status of the drive. If the drive is still functioning, change the status with the UPDATE DRIVE command.

ANR8835WError returning volume volume name to scratch.

Explanation: The server external library manager sent a RELEASE request to the external agent for the named volume, but the external agent was unable comply with the request. The server, however, marked the volume scratched in its inventory; consequently, the server inventory and the external agent inventory are not consistent. This message is issued to inform the customer that the external agent inventory must be made consistent with the server inventory using the facilities of the external agent.

System Action: The server has returned the volume to scratch status.

User Response: Consult the documentation for the external agent and take the appropriate action to make the agent inventory consistent with the server inventory.

ANR8836EFunction RSM_function failed in server_function processing, return return code, call call number.

Explanation: The library function that uses the API to the Windows NT Removable Storage Manager failed with a return code from the API. The call number represents the exact API call issued in the program.

System Action: The function fails.

User Response: Use the RSM documentation to determine the source of the problem.

ANR8837ERSM Library Library Name not supported on this Windows platform.

Explanation: The libtype=RSM was used on a Windows platform that does not support RSM.

System Action: The function fails.

User Response: Use another library type to define the library.

ANR8838EI/O error on drive drive name: excessive unit attentions received from device.

Explanation: An operation to the drive failed with a device unit attention. These are normally cleared when the operation is retried, but in this case subsequent recover and retry attempts persistently fail with unit attention. This indicates a device failure.

System Action: The operation fails.

User Response: See accompanying error messages and the system error logs to determine any reason for the drive failure. Hardware diagnostics may be required. It may be necessary to manually unload the volume and mark the drive offline with the UPDATE DRIVE command.

ANR8839WDrive drive name of library library name is accessible.

Explanation: The server is now able to use the mentioned drive that was inaccessible. However, the administrator has marked the drive offline while the drive was being polled.

System Action: The drive is left offline and is not used for tape operations.

User Response: Issue the UPDATE DRIVE command to bring the drive back online.

ANR8840EUnable to open device device name with error error number.

Explanation: The library was inaccessible, thus causing a open request to fail. This will inturn cause the pending request to fail.

System Action: A drive is marked inaccessible and the server starts polling the drive to determine if the library and drive are inaccessible. In most case, the libary had a temporary failure and recovers. When the server determines that the library is available, the drive will be brought back online.

User Response: Verify the library is online. Verify cable connections between the library and the server. If the problem persists contact your service representative.

ANR8841IRemove volume from slot element number of library library name at your convenience.

Explanation: A volume has been placed in a multiple entry/exit port library because the volume should be placed back in the entry/exit port as result of the successful completion of a server command, or there was a problem during a server command. The volume needs to be removed from the library, but the operation is not critical.

System Action: None.

User Response: Remove the volume from the entry/exit slot. Examine previous messages for additional information regarding the specified volume and the command.

ANR8842EThe Device type drive detected a marginal sector and could not reallocate the sector for volume Volume name. Access mode is now set to "read-only".

Explanation: The optical drive detected a marginal sector (media error) while reading the volume. The drive read the sector successfully but could not reallocate the sector because of a previous media error.

System Action: The volume is made read-only.

User Response: Check system error logs for entries made by the device relative to media errors. It is recommended to move the data off the volume in order to minimize the impact of future errors and further damage to the media.

ANR8846EVolume volume name is assigned to a category that does not belong to library library name.

Explanation: The attempted operation on the volume cannot proceed because it is assigned to a category other than the insert, private, or scratch category used by the library.

System Action: The attempted operation is terminated.

User Response: Use the mtlib utility to query the volume's category. If the volume is not in use by another library, use mtlib to reassign the category or choose another volume that is assigned to the proper category.

ANR8847ENo device type-type drives are currently available in library library name.

Explanation: The attempted operation cannot be completed on the specified library because there are no available drives of the specified type. A drive may be unavailable because a different application has the drive opened. This message may also be issued if a CHECKIN or LABEL command is issued and no drive is available to service the operation. This can be because all the drives are mounted by other processes or sessions, or the device type was incorrectly specified.

System Action: The attempted operation is terminated.

User Response: Use the QUERY DRIVE command to check the online status of the drives. Drives that are marked "Unavailable since hh:mm yy/mm/dd" are drives taken offline by the server at the time specified because of hardware failures or the inability to open the drive. If the attempted operation is a CHECKIN or LABEL command, use the QUERY MOUNT command to determine if all the drives in the library are mounted and wait until one of these is available. If there are mounted volumes with an IDLE status, use the DISMOUNT VOLUME command to free its drive, and retry the original operation. Finally, the DEVTYPE parameter is required for CHECKIN and LABEL commands specifying 3590 volumes in a 349X library that also contains 3490 drives. This is because this library also supports 3490 volumes, and the default device type on CHECKIN and LABEL commands is CART (3490).

ANR8848WDrive drive name of library library name is inaccessible; server has begun polling drive.

Explanation: The server is unable to use the mentioned drive. This may be for the following reasons:

System Action: The drive is temporarily made offline and is not used for tape operations. The server polls the drive at one-half minute intervals to check if the condition has cleared. Once the drives is accessible again, the drive is brought online.

User Response: Determine the reason the drive is inaccessible, such as hardware errors reported in the system logs. Render any needed corrections to the drive. The drive will be brought online automatically when the polling process detects that is has become accessible.

ANR8849ECommand: There is already a request to delete drive drive name.

Explanation: The designated drive cannot be deleted or updated because there is a request to delete the drive already.

System Action: The command is not processed.

User Response: None.

ANR8850IACSLS library library name is ready for operations.

Explanation: The initialization process for the given library has completed successfully, and the library is ready for use.

System Action: The library is made ready for use.

User Response: None.

ANR8851EInitialization failed for ACSLS library library name; will retry in delay time minute(s).

Explanation: The initialization process for the given library has failed. It is retried automatically after the specified amount of time has elapsed.

System Action: The initialization will be retried later.

User Response: Ensure that the library device is powered on and ready.

ANR8852EInitialization failed for ACSLS library library name.

Explanation: The initialization process for the given library has failed and will not be retried until the next time the server needs to access the library.

System Action: The library is made temporarily unavailable.

User Response: None.

ANR8853EIncompatible options CHECKLABEL=NO and SEARCH=YES for ACSLS libraries.

Explanation: The CHECKLABEL=NO and SEARCH=YES parameters on the CHECKIN LIBVOL command are not compatible.

System Action: The command fails.

User Response: Reissue the CHECKIN LIBVOL command and specify CHECKLABEL=YES.

ANR8854EACSAPI(command name) invocation failed, status=acs status.

Explanation: The ACSLS library api invocation for the given command failed.

System Action: Depends on the server function and command, library may be unavailable.

User Response: Contact your ACS System Administrator and perform ACSLS library problem determination.

ANR8855EACSAPI(command name) response with unsuccessful status, status=acs status.

Explanation: The ACSLS library api responded with an unsuccessful status as indicated.

System Action: Depends on the server function and command, library may be unavailable.

User Response: If the status indicates STATUS_CAP_IN_USE, it might be CAP priorities not set to non-zero. It might also be CAPs are not set to automatic mode, or CAPs are in manual mode during manual checkin. If CAP mode and priorities are set correctly, contact your ACS System Administrator and perform ACSLS library problem determination.

ANR8856EACSAPI sequence(sequence number) request(request number) timed out, elapse time=hours:minutes:seconds.

Explanation: The ACSLS client has received no response from the ACSLS server for the period as indicated in the elapsed time. The ACSLS library api function with the associated sequence number is canceled if the request number is non-zero.

System Action: Depends on the server function and command, library may be unavailable.

User Response: Contact your ACS System Administrator and perform ACSLS library problem determination.

ANR8857IACS access control set to user_id - user id, status=acs status.

Explanation: The ACSLS ACCESSID structure for command and volume access control is set the user_id as indicated.

System Action: None.

User Response: Ensure the indicated user_id is the same as specified in the environment variable ACSAPI_USER_ID.

ANR8858WUnable to lock drive drive id,drive id,drive id,drive id, status=acs status.

Explanation: The ACSLS library function acs_lock_drive failed for the specified drive.

System Action: Depends on the server function and command, library drive may be unavailable. or may be temporary unavailable in a shared library environment.

User Response: Contact your ACS System Administrator and perform ACSLS library problem determination if the problem persists.

ANR8859WUnable to lock volume volume id, status=acs status.

Explanation: The ACSLS library function acs_lock_volume failed for the specified volume.

System Action: Depends on the server function and command, library volume is unavailable.

User Response: Contact your ACS System Administrator and perform ACSLS library problem determination if the problem persist.

ANR8860WVolume volume id is already locked by user id.

Explanation: The specified volume is already locked by other user or has a different lock id.

System Action: Depends on the function, the volume maybe bypassed or the process maybe terminated.

User Response: This may not be an error in a shared configuration. However, if the existing volume lock is not needed. contact your ACSLS system administrator to clear the lock the volume.

ANR8861IWait and monitor the ACSSA console message to remove volume volume id from CAP.

Explanation: The specified volume is about to put into CAP for removal. Monitor the ACSSA console and removed the volume after it has been placed into the CAP as indicated in the ACSSA message.

System Action: None.

User Response: Monitor the ACSSA console and wait.

ANR8862IUnable to access ACS volume volume id.

Explanation: The specified ACSLS volume can not be accessed in the library. The possible reasons might be the volume is in use, the user is not authorized, the volume does not exist in the library.

System Action: Depends on the server function and command, library volume is unavailable.

User Response: Contact your ACS System Administrator and perform ACSLS library problem determination if the problem persists.

ANR8863IUnlocking library library name volumes from the ACSLS server.

Explanation: The volumes of the specified library are being unlocked from the ACSLS server.

System Action: The operation continues. The process may take a while depends on the number of volumes in the library.

User Response: None.

ANR8864IACSLS library library name is being re-initialized.

Explanation: The specified ACSLS library is being re-initialized.

System Action: The operation continues. The process may take a while depends on the number of volumes in the library. All volumes in the library are being locked.

User Response: None.

ANR8865WVolume volume name bypassed for command, status=acs_status.

Explanation: The specified volume is bypassed. The volume is not in a valid status for the specified function.

System Action: The operation continues.

User Response: Determine the volume status from the ACSSA and re-issue the command if necessary.

ANR8866EIncompatible option REMOVE=BULK for ACSLS libraries.

Explanation: The REMOVE=BULK option is not supported for ACSLS libraries. The final response of ACSAPI acs_eject does not return to the application until the volume is removed from CAP.

System Action: The command fails.

User Response: Reissue the CHECKOUT LIBVOL command and specify REMOVE=YES or NO.

ANR8867IProcessing volume volume id for the command command.

Explanation: The specified volume is being processed for the specified command.

System Action: The command process continues.

User Response: None.

ANR8868EEjecting Volume volume name Failed, status = acs_status.

Explanation: The volume is failed to be ejected from the library due to the status as indicated

System Action: The operation continues.

User Response: Determine the volume status from the message and do something as needed

ANR8869ECommand: There is already a request to update drive drive name.

Explanation: The designated drive cannot be deleted because there is a request to update the drive already.

System Action: The command is not processed.

User Response: None.

ANR8901ECommand: Incompatible options STATUS=CLEANER and CHECKLABEL=YES.

Explanation: Cleaner cartridges do not have internal labels that can be checked by loading them into the drive.

System Action: The command fails.

User Response: Reissue the CHECKIN LIBVOL command and include the parameter, CHECKLABEL=BARCODE (with SEARCH=YES specified), or include the parameter CHECKLABEL=NO (with the required volume name specified in the CHECKIN command).

ANR8902WUnable to read the barcode of cleaner cartridge in slot-id Element number of slot in library library name; cleaner not checked in.

Explanation: The library barcode reader is unable to read the label of a cartridge that is checked in as a cleaner. The cartridge is found in the slot with the given element number.

System Action: The cartridge is not checked in. If the library is being searched, the checkin process continues with the next volume.

User Response: Examine the cartridge to ensure it has a barcode label and that it is compatible with the barcode reader. Not all vendors' labels are readable by all libraries. Check that the barcode reader is configured and is functioning properly. The cleaner cartridge can be checked in without use of the barcode label by issuing the CHECKIN LIBVOL command.

ANR8903ECommand: Missing CLEANINGS parameter for cleaner cartridge checkin.

Explanation: When checking in a cleaner cartridge, the CLEANINGS parameter is required.

System Action: The command fails.

User Response: Reissue the CHECKIN LIBVOL command and specify a value for the CLEANINGS parameter which is used to determine the number of times a cleaner can be mounted to clean a drive.

ANR8904ICommand: Cleaning operation for drive drive name in library library name started as process process ID.

Explanation: A command-driven process is started to clean the specified drive. The process is assigned the ID that is in the message.

System Action: In response to the CLEAN DRIVE command that is issued by an administrator, the server starts a background process to perform the operation.

User Response: To obtain status on the process, issue the QUERY PROCESS command. The process may be canceled with the CANCEL PROCESS command.

ANR8905ICLEAN DRIVE process for drive drive name in library library name is been canceled.

Explanation: A background server process is has been working to clean the specified drive and is canceled by the CANCEL PROCESS command.

System Action: The cleaning process is ended.

User Response: None.

ANR8906ICleaning drive drive name in library library name.

Explanation: In response to a QUERY PROCESS command, this message displays the status for a CLEAN DRIVE process on the server. The given volume is being checked in to the designated library.

System Action: The background process operation continues. The process may be canceled by an authorized administrator using the CANCEL PROCESS command.

User Response: None. The process may be canceled by an authorized administrator using the CANCEL PROCESS command.

ANR8907ECLEAN DRIVE for drive drive name in library library name failed.

Explanation: The background process for a CLEAN DRIVE fails.

System Action: The background process ends, but the drive is not cleaned.

User Response: Make sure the library and drive devices associated with this command are powered on and ready. Reissue the command.

ANR8908ICLEAN DRIVE for drive drive name in library library name completed successfully.

Explanation: The specified drive is successfully cleaned in the library during processing of a CLEAN DRIVE command.

System Action: The drive is available for normal library operations.

User Response: None.

ANR8909ICleaning drive drive name in library library name- CANCEL PENDING.

Explanation: In response to a QUERY PROCESS command, this message displays the status for a CLEAN DRIVE process on the server.

System Action: The background process operation is terminated.

User Response: None.

ANR8910INo cleaner, or no cleaner with cleanings left, found in library library name.

Explanation: A drive is selected to be loaded with a cleaner cartridge, but no cleaner, or cleaner with cleanings left, is found in the library's inventory.

System Action: The drive is available for normal library operations.

User Response: A cleaner should be checked in to the library by issuing the CHECKIN LIBVOL command.

ANR8911WThe cartridge in storage element slot element address in library library name is not a cleaner cartridge as was expected.

Explanation: The cartridge is listed in the library's inventory with a cleaner volume status. After loading the cartridge in the specified storage cell into a drive for cleaning, it is determined that it is not a cleaner cartridge.

System Action: The drive is available for normal library operations.

User Response: The cartridge should be checked out of the library by issuing the CHECKOUT LIBVOL command. If necessary a cleaner cartridge should be checked in to replace it.

ANR8912EUnable to verify the label of volume from slot-element element-address in library library name.

Explanation: The volume from the slot that is identified by the element address is loaded into a drive. The drive cannot be opened following the load. The label cannot be read to process the volume.

System Action: The volume is stored, and processing continues with the next available slot.

User Response: Check the system error logs for errors reported by the drive that are related to this volume. Make sure that the cartridge is not a cleaner cartridge that would have been loaded by mistake. If the cartridge is a cleaner, issue the QUERY LIBVOL command to get the correct storage slot for the cleaner and move the cleaner to that slot. If the cleaner is not in the library's inventory, use the CHECKIN LIBVOL to check the cleaner in.

ANR8913IDrive drive name in library library name is currently busy; Cleaning is scheduled.

Explanation: A background process to clean the drive is unable to acquire the drive because the drive is busy.

System Action: The background process operation completes. The drive is scheduled to be cleaned when it is unloaded.

User Response: None.

ANR8914IDrive drive name in library library name needs to be cleaned.

Explanation: The drive has returned indicating to the server that it needs to be cleaned.

System Action: The server marks the drive to be cleaned. If the drive is enabled for server-managed cleaning, and a cleaner cartridge is checked into the library, the server will load the cleaner into the drive after the current volume is dismounted. See the DEFINE DRIVE and QUERY DRIVE commands for information on enabling server-managed cleaning. See the CHECKIN LIBVOL command for checking a cleaner into the library.

User Response: None.

ANR8915ICleaning cartridge cleaner name in library library name is near end of life; has library name uses left.

Explanation: A cleaner cartridge is found and used, but its number of uses ih has left is nearly exhausted.

System Action: The cleaning operation continues.

User Response: As the cleaner is used, monitor the number of cleanings that remain with the QUERY LIBVOL command. Remove the cleaner when all cleanings are exhausted. A new cleaner may be checked in so that the library is not left without a useful cleaner when the old cleaner is exhausted.

ANR8916IDrivemapping for drive Drive name in library library name on storage service storage service name defined.

Explanation: A drivemapping has been successfully defined for the specified drive.

System Action: The drivemapping is defined and recorded in the database.

User Response: None.

ANR8917IDrivemapping for drive Drive name in library library name on storage service storage service name updated.

Explanation: An UPDATE DRIVEMAPPING request has been successfully processed for the given drive.

System Action: The server updates its information about the drivemapping.

User Response: None.

ANR8918IDrivemapping for drive Drive name in library library name on storage service storage service name deleted.

Explanation: The drivemapping for the specified storage service, library, and drive has been deleted successfully.

System Action: The drivemapping is deleted.

User Response: None.

ANR8919IInitalization and recovery has started for shared library library name.

Explanation: The shared library has started to initialize or recover to resynchronize the library manager and library client.

System Action: None.

User Response: This process should resynchronize all of the drives that are currently being used by this library client. This process might also start after a communication error or if the library client has not been able to verify drive status with the library manager.

ANR8920IInitalization and recovery has ended for shared library library name.

Explanation: Initialize or recover has ended the library manager and library client should by synchronized.

System Action: None.

User Response: The drives previously owned by the library client should now indicate they are free on the library manager. Verify this with the QUERY DRIVE command on the library manager. If ownership of the drives is still in question restart the library client and library manager.

ANR8921EUnable to start library polling thread .

Explanation: Library sharing requires that this polling thread starts. This thread keeps the library manager and library client synchronized with regards to drive ownership. These thread are started when the library is defined or when the server is first initalized.

System Action: None.

User Response: Since the polling thread did not start, the user must restart the server in order for library sharing to correctly work. Failure to restart the server and get these polling services running can cause unusual results for library clients.

ANR8922IA device class for library library name was not found.

Explanation: A library client request a mount operation to be performed by the library manager. The library manager is missing a device class definition for that library.

System Action: None.

User Response: Define a device class for the library using the DEFINE DEVCLASS command.

ANR8923IDismount failed because drive drive name in library library name is not currently owned by drive owner name.

Explanation: A library client attempted to dismount a drive that was not currently owned by the library client.

System Action: None.

User Response: None.

ANR9579W (HP-UX)Command: Unable to locate file file name.

Explanation: The specified file cannot be found. Note: PREPARE assumes that the volume formatting program (dsmfmt) is located in the same directory as the server executable file.

System Action: PREPARE uses the following default file names in the plan file:

User Response: Determine why file does not exist; create if necessary.

ANR9579W (Solaris)Command: Unable to locate file file name.

Explanation: The specified file cannot be found. Note: PREPARE assumes that the volume formatting program (dsmfmt) is located in the same directory as the server executable file.

System Action: PREPARE uses the following default file names in the plan file:

User Response: Determine why file does not exist; create if necessary.

ANR9580W (Solaris)Command: Generated replacement volume name volume name may not be a valid raw partition name. Original volume name:volume name. Stanza is stanza name.

Explanation: Appending the replacement volume name postfix to the original volume name has created a name that may not be a valid raw partition name.

System Action: Replacement volume name is used in the recovery plan stanza.

User Response: Manually update the generated recovery plan stanza with a legal replacement name. The replacement name can be another raw partition name or a regular file name.

ANR9581W (HP-UX)Command: Volume file name not found while building stanza recovery plan stanza name.

Explanation: This volume is defined to the server but does not exist. The device class associated with the volume is DISK or the device class device type is FILE.

System Action: The entry for the volume is not included in the recovery plan stanza.

User Response: Determine why file does not exist; create if necessary.

ANR9581W (Solaris)Command: Volume file name not found while building stanza recovery plan stanza name.

Explanation: This volume is defined to the server but does not exist. The device class associated with the volume is DISK or the device class device type is FILE.

System Action: The entry for the volume is not included in the recovery plan stanza.

User Response: Determine why file does not exist; create if necessary.

ANR9582E (HP-UX)Command: Generated file name too long. Length of directory or prefix 'prefix' plus 'name' exceeds maximum characters characters.

Explanation: The file name generated is too long. The maximum valid length is shown in the message.

System Action: The recovery plan file was not created.

User Response: Reissue the command specifying a valid prefix. The following commands are used to specify the prefix:

ANR9582E (Solaris)Command: Generated file name too long. Length of directory or prefix 'prefix' plus 'name' exceeds maximum characters characters.

Explanation: The file name generated is too long. The maximum valid length is shown in the message.

System Action: The recovery plan file was not created.

User Response: Reissue the command specifying a valid prefix. The following commands are used to specify the prefix:

ANR9583E (HP-UX)Command: Cannot generate fully qualified file name for 'name'.

Explanation: A failure occurred expanding the specified file name.

System Action: Recovery plan file not created.

User Response: Reissue the command specifying a valid prefix. The following commands are used to specify the prefix:

ANR9583E (Solaris)Command: Cannot generate fully qualified file name for 'name'.

Explanation: A failure occurred expanding the specified file name.

System Action: Recovery plan file not created.

User Response: Reissue the command specifying a valid prefix. The following commands are used to specify the prefix:

ANR9584E (HP-UX)Command: Cannot generate server options file name.

Explanation: A failure occurred generating the server options file name.

System Action: Recovery plan file not created.

User Response: See accompanying messages for more information.

ANR9584E (Solaris)Command: Cannot generate server options file name.

Explanation: A failure occurred generating the server options file name.

System Action: Recovery plan file not created.

User Response: See accompanying messages for more information.

ANR9585E (HP-UX)Command: Cannot generate a volume history file name.

Explanation: A failure occurred generating the volume history file name.

System Action: Recovery plan file not created.

User Response: See accompanying messages for more information.

ANR9585E (Solaris)Command: Cannot generate a volume history file name.

Explanation: A failure occurred generating the volume history file name.

System Action: Recovery plan file not created.

User Response: See accompanying messages for more information.

ANR9586E (HP-UX)Command: Cannot generate a device configuration file name.

Explanation: A failure occurred generating the device configuration file name.

System Action: Recovery plan file not created.

User Response: See accompanying messages for more information.

ANR9586E (Solaris)Command: Cannot generate a device configuration file name.

Explanation: A failure occurred generating the device configuration file name.

System Action: Recovery plan file not created.

User Response: See accompanying messages for more information.

ANR9600E (AIX)Invalid information passed to NETLS license interface.

Explanation: The server licensing functions encountered an internal error in accessing license information for the server storage capacity and number of registered clients.

System Action: Server operation continues. New licensing information is not used by the server.

User Response: Contact your service representative for assistance in resolving the error.

ANR9601E (AIX)The NETLS license interface was not initialized properly.

Explanation: The server licensing functions encountered an internal error in accessing license information for the server storage capacity and number of registered clients.

System Action: Server operation continues. New licensing information is not used by the server.

User Response: Contact your service representative for assistance in resolving the error.

ANR9602E (AIX)Invalid JOB information passed to the NETLS Interface.

Explanation: The server licensing functions encountered an internal error in accessing license information for the server storage capacity and number of registered clients.

System Action: Server operation continues. New licensing information is not used by the server.

User Response: Contact your service representative for assistance in resolving the error.

ANR9603E (AIX)The NETLS Nodelock file could not be created.

Explanation: The server was not able to create the file /usr/lib/netls/conf/nodelock which is used for storing license password information.

System Action: Server operation continues. New licensing information is not used by the server.

User Response: If the server is not running with root authority, make sure that directory authorities in the /usr/lib/netls/conf path are set so that the user ID under which the server is running can create, read, and write to the /usr/lib/netls/conf/nodelock file. If the server is running with root authority, contact your service representative for assistance in resolving this problem.

ANR9604E (AIX)The NETLS license interface encountered an internal error.

Explanation: The server licensing functions encountered an internal error in accessing license information for the server storage capacity and number of registered clients.

System Action: Server operation continues. New licensing information is not used by the server.

User Response: Contact your service representative for assistance in resolving the error.

ANR9605E (AIX)An invalid vendor ID was passed to NETLS.

Explanation: The server licensing functions encountered an internal error in accessing license information for the server storage capacity and number of registered clients.

System Action: Server operation continues. New licensing information is not used by the server.

User Response: Contact your service representative for assistance in resolving the error.

ANR9606E (AIX)NETLS failed to find socket families to contact a server.

Explanation: The server licensing functions encountered an internal error in accessing license information for the server storage capacity and number of registered clients.

System Action: Server operation continues. New licensing information is not used by the server.

User Response: Contact your service representative for assistance in resolving the error.

ANR9607E (AIX)No NETLS Servers found.

Explanation: The server licensing functions encountered an internal error in accessing license information for the server storage capacity and number of registered clients.

System Action: Server operation continues. New licensing information is not used by the server.

User Response: Contact your service representative for assistance in resolving the error.

ANR9608E (AIX)A NETLS Security Breach was encountered.

Explanation: The server licensing functions encountered an internal error in accessing license information for the server storage capacity and number of registered clients.

System Action: Server operation continues. New licensing information is not used by the server.

User Response: Contact your service representative for assistance in resolving the error.

ANR9609E (AIX)Incorrect license entered: Password entered = password Annotation entered = annotation.

Explanation: The license information entered for a REGISTER LICENSE command is not correct.

System Action: None.

User Response: Register the license again with the REGISTER LICENSE command. Be sure to correctly enter the license information.

ANR9610E (AIX)Unable to create directory: directory.

Explanation: The REGISTER LICENSE command is unable to either create or verify the specified directory structure.

System Action: None.

User Response: If the server is not running with root authority, make sure that directory authorities in the /usr/lib/netls/conf path are set so that the user ID under which the server is running can create, read, and write to the /usr/lib/netls/conf/nodelock file. If the server is running with root authority, contact your service representative for assistance in resolving this problem.

ANR9610E (Solaris)Unable to create directory: directory.

Explanation: The REGISTER LICENSE command is unable to either create or verify the specified directory structure.

System Action: None.

User Response: If the server is not running with root authority, make sure that directory authorities in the given directory path are set so that the user under which the server is running can create, read, and write to the server's license file. If the server is running with root authority, contact your service representative for assistance in resolving this problem.

ANR9611E (AIX)Unable to open NODELOCK file: file.

Explanation: The REGISTER LICENSE command is unable to either create or open the nodelock file.

System Action: None.

User Response: If the server is not running with root authority, make sure that directory authorities in the /usr/lib/netls/conf path are set so that the user ID under which the server is running can create, read, and write to the /usr/lib/netls/conf/nodelock file. If the server is running with root authority, contact your service representative for assistance in resolving this problem.

ANR9612E (AIX)Error writing to NODELOCK file.

Explanation: The REGISTER LICENSE command fails writing to the nodelock file.

System Action: None.

User Response: If the server is not running with root authority, make sure that directory authorities in the /usr/lib/netls/conf path are set so that the user ID under which the server is running can create, read, and write to the /usr/lib/netls/conf/nodelock file. If the server is running with root authority, contact your service representative for assistance in resolving this problem.

ANR9613W (AIX)Error loading modname for Licensing function.

Explanation: The server cannot load file module modname to initialize licensing functions.

System Action: Server operation continues. Default licensing values are in effect for running the server.

User Response: The dsmreg.lic module is accessed as part of the load process for licensing. It should be in the same directory as the dsmserv executable or it must be in a directory that is pointed to by the DSMSERV_DIR environment variable. The dsmreg.lic module is only installed when you purchase the product.

ANR9613W (Solaris)Error loading modname for Licensing function.

Explanation: The server cannot load file module modname to initialize licensing functions.

System Action: Server operation continues. Default licensing values are in effect for running the server.

User Response: dsmreg.lic is accessed as part of the load process for licensing. It should be in the same directory as the dsmserv executable file or it must be in a directory that is pointed to by the DSMSERV_DIR environment variable. The dsmreg.lic module is only installed when you purchase the product.

ANR9614E (AIX)Unable to open license file: file.

Explanation: The REGISTER LICENSE command is unable to create or open the server license file.

System Action: None.

User Response: Make sure that the user ID under which the server is running has the authority required to create or write, or both, to the license file in the directory in which the server is running. If this does not resolve the problem, contact your service representative for assistance.

ANR9614E (Solaris)Unable to open license file: file.

Explanation: The REGISTER LICENSE command is unable to either create or open the server license file.

System Action: None.

User Response: Make sure that the user ID under which the server is running has the authority required to create or write, or both, to the license file in the directory in which the server is running. If this does not resolve the problem, contact your service representative for assistance.

ANR9615E (AIX)Error writing to adsmserv.licenses file.

Explanation: The REGISTER LICENSE command fails writing to the server license file.

System Action: None.

User Response: Make sure that the user ID under which the server is running has the authority required to create or write, or both, to the license file in the directory in which the server is running. Also, ensure that free space is available in the file system so that the license information can be written to the file. If this does not resolve the problem, contact your service representative for assistance.

ANR9615E (Solaris)Error writing to adsmserv.licenses file.

Explanation: The REGISTER LICENSE command fails writing to the server license file.

System Action: None.

User Response: Make sure that the userid under which the server is running has the authority required to create and/or write to the license file in the directory in which the server is running. Also ensure that there is free space available in the filesystem so that the license information can be written to the file. If this does not resolve the problem contact your service representative for assistance.

ANR9616I (AIX)Invalid license record record value found in license file - it will be skipped.

Explanation: The license manager found an invalid record in the server license file (adsmserv.licenses). The record is ignored.

System Action: The invalid record is ignored.

User Response: Erase the adsmserv.licenses file and reregister your licenses.

ANR9616W (Solaris)Invalid license record record value found in license file - it will be ignored.

Explanation: The license manager found an invalid record in the server license file (adsmserv.licenses). The record is ignored.

System Action: The invalid record is ignored.

User Response: Erase the adsmserv.licenses file and reregister your licenses. Refer to the licenses provided to you to ensure that only valid licenses are specified with the REGISTER LICENSE command.

ANR9617I (AIX)Invalid license authorization: authorization string.

Explanation: The license authorization specified for a REGISTER LICENSE command is not valid.

System Action: Server operation continues; licensing terms are not changed by the REGISTER LICENSE command.

User Response: Examine the license authorization string that was entered with the REGISTER LICENSE command. Reenter the command if the license authorization was not specified correctly. If the license authorization has been specified correctly, contact your service representative.

ANR9617W (Solaris)Invalid license authorization: authorization string.

Explanation: The license authorization specified for a REGISTER LICENSE command is not valid.

System Action: Server operation continues; licensing terms are not changed by the REGISTER LICENSE command.

User Response: Examine the license authorization that was entered using the REGISTER LICENSE command. Reenter the command if the license authorization was not specified correctly. If the license authorization has been specified correctly, contact your service representative.

ANR9618E (AIX)License registration is not supported on this server.

Explanation: The REGISTER LICENSE command fails because the license authorization module cannot be found.

System Action: Server operation continues; licensing terms are not changed by the REGISTER LICENSE command.

User Response: The license authorization file is required for formal licensing for the AIX/6000 server. The file is delivered when the product is purchased, but it is not available in the product service stream or with demonstration copies of the server. If you have purchased the server, contact your service representative for assistance in resolving this problem.

ANR9618E (Solaris)License registration is not supported on this server.

Explanation: The REGISTER LICENSE command failed because the license authorization module could not be found.

System Action: Server operation continues; licensing terms are not changed by the REGISTER LICENSE command.

User Response: The license authorization file is required for formal licensing for the server. The file is delivered when the server is purchased, but is not available in the product service stream or with demonstration copies of the server. If you have purchased the server, please contact your service representation for assistance in resolving this problem.

ANR9622I (AIX)An EVALUATION LICENSE for support of Tivoli Space Management will expire on expiration date.

Explanation: The AIX/6000 server is distributed with an evaluation license for Tivoli Space Management support. If no formal license is found for the server and the evaluation period has not lapsed, this message is displayed each time the server checks the server license terms.

System Action: The Tivoli Space Management license allows clients to utilize the server for storing files migrated during space management. The server checks this license when files are migrated to the server from client nodes to ensure that the server is licensed to perform this function.

User Response: If you are interested in using the server, contact your service representative to obtain formal licenses for the server before the evaluation period has elapsed. Without formal licenses, the server will not support Tivoli Space Management after the expiration date shown.

ANR9623I (AIX)An EVALUATION LICENSE for support of Tivoli Disaster Recovery Manager will expire on expiration date.

Explanation: The AIX/6000 server is distributed with an evaluation license for Tivoli Disaster Recovery Manager support. If no formal license is found for the server and the evaluation period has not lapsed, this message is displayed each time the server checks the server license terms.

System Action: The Tivoli Disaster Recovery Manager license allows customers to store information in the server regarding machines and recovery media, allows management of offsite recovery media, collects and stores information in the server for server recovery and allows data base and storage pool backups to a device class of type server. The server checks this license when machines or recovery media are defined to the server, when PREPARE or MOVE DRMMEDIA are invoked and when a data base backup or storage pool backup to a device class of type server are performed to ensure that the server is licensed to perform this function.

User Response: If you are interested in using the server, contact your service representative to obtain formal licenses for the server before the evaluation period has elapsed. Without formal licenses, the server will not support Tivoli Disaster Recovery Manager after the expiration date shown.

ANR9624E (AIX)Unexpected error encountered in iFor/LS (SystemView License Use Management) routine license interface name status=xreported status code.

Explanation: The server encountered an unexpected error in accessing the SystemView License Use Management function specified.

System Action: The server license monitoring operation fails

User Response: The SystemView License Use Management product is installed during normal AIX server installation. Check to make sure that server was installed correctly. If the installation was successful, re-boot your AIX system and re-start the server. If this message continues to be issued, contact your service representative.

ANR9624I (HP-UX)An EVALUATION LICENSE for support of Tivoli Space Management will expire on expiration date.

Explanation: The server is distributed with an evaluation license for Tivoli Space Management support. If no formal license is found for the server and the evaluation period has not lapsed, this message is displayed each time the server checks the server license terms.

System Action: The Tivoli Space Management license allows clients to utilize the server for storing files migrated during space management. The server checks this license when files are migrated to the server from client nodes to ensure that the server is licensed to perform this function.

User Response: If you are interested in using the server, contact your service representative to obtain formal licenses for the server before the evaluation period has elapsed. Without formal licenses, the server will not support Tivoli Space Management after the expiration date shown.

ANR9624I (Solaris)An EVALUATION LICENSE for support of Tivoli Space Management will expire on expiration date.

Explanation: The server is distributed with an evaluation license for Tivoli Space Management support. If no formal license is found for the server and the evaluation period has not lapsed, this message is displayed each time the server checks the server license terms.

System Action: The Tivoli Space Management license allows clients to utilize the server for storing files migrated during space management. The server checks this license when files are migrated to the server from client nodes to ensure that the server is licensed to perform this function.

User Response: If you are interested in using the server, contact your service representative to obtain formal licenses for the server before the evaluation period has elapsed. Without formal licenses, the server will not support Tivoli Space Management after the expiration date shown.

ANR9624I (Windows NT)An EVALUATION LICENSE for support of Tivoli Space Management will expire on expiration date.

Explanation: The server is distributed with an evaluation license for Tivoli Space Management support. If no formal license is found for the server and the evaluation period has not lapsed, this message is displayed each time the server checks the server license terms.

System Action: The Tivoli Space Management license allows clients to utilize the server for storing files migrated during space management. The server checks this license when files are migrated to the server from client nodes to ensure that the server is licensed to perform this function.

User Response: If you are interested in using the server, contact your service representative to obtain formal licenses for the server before the evaluation period has elapsed. Without formal licenses, the server will not support Tivoli Space Management after the expiration date shown.

ANR9625E (AIX)Could not open file file name.

Explanation: The server could not open the license certificate file specified.

System Action: The license registration command fails.

User Response: Examine the file specification entered, including wildcard characters, to determine if it names the license certificate file(s) you intended to use. If an error is found, re-try the command with the corrected specification. If an error cannot be found, contact your service representative.

ANR9625I (HP-UX)An EVALUATION LICENSE for support of Tivoli Disaster Recovery Manager will expire on expiration date.

Explanation: The server is distributed with an evaluation license for Tivoli Disaster Recovery Manager support. If no formal license is found for the server and the evaluation period has not lapsed, this message is displayed each time the server checks the server license terms.

System Action: The Tivoli Disaster Recovery Manager license allows customers to store information in the server regarding machines and recovery media, allows management of offsite recovery media, collects and stores information in the server for server recovery and allows data base and storage pool backups to a device class of type server. The server checks this license when machines or recovery media are defined to the server, when PREPARE or MOVE DRMMEDIA are invoked and when a data base backup or storage pool backup to a device class of type server are performed to ensure that the server is licensed to perform this function.

User Response: If you are interested in using the server, contact your service representative to obtain formal licenses for the server before the evaluation period has elapsed. Without formal licenses, the server will not support Tivoli Disaster Recovery Manager after the expiration date shown.

ANR9625I (Solaris)An EVALUATION LICENSE for support of Tivoli Disaster Recovery Manager will expire on expiration date.

Explanation: The server is distributed with an evaluation license for Tivoli Disaster Recovery Manager support. If no formal license is found for the server and the evaluation period has not lapsed, this message is displayed each time the server checks the server license terms.

System Action: The Tivoli Disaster Recovery Manager license allows customers to store information in the server regarding machines and recovery media, allows management of offsite recovery media, collects and stores information in the server for server recovery and allows data base and storage pool backups to a device class of type server. The server checks this license when machines or recovery media are defined to the server, when PREPARE or MOVE DRMMEDIA are invoked and when a data base backup or storage pool backup to a device class of type server are performed to ensure that the server is licensed to perform this function.

User Response: If you are interested in using the server, contact your service representative to obtain formal licenses for the server before the evaluation period has elapsed. Without formal licenses, the server will not support Tivoli Disaster Recovery Manager after the expiration date shown.

ANR9625I (Windows NT)An EVALUATION LICENSE for support of Tivoli Disaster Recovery Manager will expire on expiration date.

Explanation: The server is distributed with an evaluation license for Tivoli Disaster Recovery Manager support. If no formal license is found for the server and the evaluation period has not lapsed, this message is displayed each time the server checks the server license terms.

System Action: The Tivoli Disaster Recovery Manager license allows customers to store information in the server regarding machines and recovery media, allows management of offsite recovery media, collects and stores information in the server for server recovery and allows data base and storage pool backups to a device class of type server. The server checks this license when machines or recovery media are defined to the server, when PREPARE or MOVE DRMMEDIA are invoked and when a data base backup or storage pool backup to a device class of type server are performed to ensure that the server is licensed to perform this function.

User Response: If you are interested in using the server, contact your service representative to obtain formal licenses for the server before the evaluation period has elapsed. Without formal licenses, the server will not support Tivoli Disaster Recovery Manager after the expiration date shown.

ANR9626E (AIX)Invalid license certificate file: file name.

Explanation: The specified file does not contain valid license certificate information.

System Action: The license registration command ignores the contents of the file.

User Response: Examine the file specification entered, including wildcard characters, to determine if it names the license certificate file(s) you intended to use. If an error is found, re-try the command with the corrected specification. If an error cannot be found, contact your service representative.

ANR9627E (AIX)Cannot access node license lock file: file name.

Explanation: The server was not able to access the specified file. The node lock file contains licensing information for the server.

System Action: The license function fails.

User Response: Examine the file specification displayed and ensure that the file attributes will allow the server to access the file. The location of the file is either in the directory from which the server is started, or in the directory specified by the DSMSERV_DIR environment variable. Re-specify the DSMSERV_DIR environment variable if this specification is in error. Also ensure that there is sufficient space on the drive specified for the file. If the problem persists after these corrections have been made, contact your service representative.

ANR9628E (Windows NT)Unexpected error encountered in iFor/LS (SystemView License Use Management) routine license interface name status=xreported status code.

Explanation: The server encountered an unexpected error in accessing the SystemView License Use Management function specified.

System Action: The server license monitoring operation fails

User Response: The SystemView License Use Management product is installed during normal server installation. Check to make sure that the product was installed correctly. If the installation was successful, re-boot your system and re-start the server. If this message continues to be issued, contact your service representative.

ANR9629E (Windows NT)Could not open file file name.

Explanation: The server could not open the license certificate file specified.

System Action: The license registration command fails.

User Response: Examine the file specification entered, including wildcard characters, to determine if it names the license certificate file(s) you intended to use. If an error is found, re-try the command with the corrected specification. If an error cannot be found, contact your service representative.

ANR9630E (Windows NT)Invalid license certificate file: file name.

Explanation: The specified file does not contain valid license certificate information.

System Action: The license registration command ignores the contents of the file.

User Response: Examine the file specification entered, including wildcard characters, to determine if it names the license certificate file(s) you intended to use. If an error is found, re-try the command with the corrected specification. If an error cannot be found, contact your service representative.

ANR9631E (Windows NT)Cannot access node license lock file: file name.

Explanation: The server was not able to access the specified file. The node lock file contains licensing information for the server.

System Action: The license function fails.

User Response: Examine the file specification displayed and ensure that the file attributes will allow the server to access the file. The location of the file is either in the directory from which the server is started, or in the directory specified by the DSMSERV_DIR environment variable. Re-specify the DSMSER-DIR environment variable if this specification is in error. Also ensure that there is sufficient space on the drive specified for the file. If the problem persists after these corrections have been made, contact your service representative.

ANR9632I (Windows NT)Cannot load licensing DLL library: DLL file name : the server will assume evaluation licensing mode.

Explanation: The server was not able to load the specified dynamic link library.

System Action: Server licensing assumes Try and Buy mode with licenses for 180 days.

User Response: The named DLL library(ies) are required for the server to support feature licensing. If you are running an evaluation copy of the server, this message should not cause concern and is normal. If the libraries are installed and this message continues to be issued, contact a support representative for assistance.

ANR9634E (AIX)command name: No license certificate files were found with the file name specification specification.

Explanation: The server did not find any license certificate file(s) with the file name specification entered.

System Action: The license registration command fails.

User Response: Examine the file specification entered, including wildcard characters, to determine if it names the license certificate file(s) you intended to use. The file name specification indicates the fully qualified file name the server was trying to read. The directory used to locate the license certificate files when no explicit path is provided is determined as follows:

If an error is found, re-try the command with the corrected specification. If an error cannot be found, contact your service representative.

ANR9634E (HP-UX)command name: No license certificate files were found with the file name specification specification.

Explanation: The server did not find any license certificate file(s) with the file name specification entered.

System Action: The license registration command fails.

User Response: Examine the file specification entered, including wildcard characters, to determine if it names the license certificate file(s) you intended to use. If an error is found, re-try the command with the corrected specification. If an error cannot be found, contact your service representative.

ANR9634E (Solaris)command name: No license certificate files were found with the file name specification specification.

Explanation: The server did not find any license certificate file(s) with the file name specification entered.

System Action: The license registration command fails.

User Response: Examine the file specification entered, including wildcard characters, to determine if it names the license certificate file(s) you intended to use. If an error is found, retry the command with the corrected specification. If an error cannot be found, contact your service representative.

ANR9634E (Windows NT)command name: No license certificate files were found with the file name specification specification.

Explanation: The server did not find any license certificate file(s) with the file name specification entered.

System Action: The license registration command fails.

User Response: Examine the file specification entered, including wildcard characters, to determine if it names the license certificate file(s) you intended to use. If an error is found, retry the command with the corrected specification. If an error cannot be found, contact your service representative.

ANR9635E (HP-UX)Invalid license certificate file: file name.

Explanation: The specified file does not contain valid license certificate information.

System Action: The license registration command ignores the contents of the file.

User Response: Examine the file specification entered, including wildcard characters, to determine if it names the license certificate file(s) you intended to use. If an error is found, retry the command with the corrected specification. If an error cannot be found, contact your service representative.

ANR9635E (Solaris)Invalid license certificate file: file name.

Explanation: The specified file does not contain valid license certificate information.

System Action: The license registration command ignores the contents of the file.

User Response: Examine the file specification entered, including wildcard characters, to determine if it names the license certificate file(s) you intended to use. If an error is found, retry the command with the corrected specification. If an error cannot be found, contact your service representative.

ANR9635E (Windows NT)Invalid license certificate file: file name.

Explanation: The specified file does not contain valid license certificate information.

System Action: The license registration command ignores the contents of the file.

User Response: Examine the file specification entered, including wildcard characters, to determine if it names the license certificate file(s) you intended to use. If an error is found, retry the command with the corrected specification. If an error cannot be found, contact your service representative.

ANR9636E (HP-UX)Could not open file file name.

Explanation: The server could not open the license certificate file specified.

System Action: The license registration command fails.

User Response: Examine the file specification entered, including wildcard characters, to determine if it names the license certificate file(s) you intended to use. If an error is found, re-try the command with the corrected specification. If an error cannot be found, contact your service representative.

ANR9636E (Solaris)Could not open file file name.

Explanation: The server could not open the license certificate file specified.

System Action: The license registration command fails.

User Response: Examine the file specification entered, including wildcard characters, to determine if it names the license certificate file(s) you intended to use. If an error is found, re-try the command with the corrected specification. If an error cannot be found, contact your service representative.

ANR9636E (Windows NT)Could not open file file name.

Explanation: The server could not open the license certificate file specified.

System Action: The license registration command fails.

User Response: Examine the file specification entered, including wildcard characters, to determine if it names the license certificate file(s) you intended to use. If an error is found, retry the command with the corrected specification. If an error cannot be found, contact your service representative.

ANR9637E (HP-UX)Cannot access node license lock file: file name.

Explanation: The server was not able to access the specified file. The node lock file contains licensing information for the server.

System Action: The license function fails.

User Response: Examine the file specification displayed and ensure that the file attributes will allow the server to access the file. The location of the file is either in the directory from which the server is started, or in the directory specified by the DSMSERV_DIR environment variable. Re-specify the DSMSERV_DIR environment variable if this specification is in error. Also ensure that there is sufficient space on the drive specified for the file. If the problem persists after these corrections have been made, contact your service representative.

ANR9637E (Solaris)Cannot access node license lock file: file name.

Explanation: The server was not able to access the specified file. The node lock file contains licensing information for the server.

System Action: The license function fails.

User Response: Examine the file specification displayed and ensure that the file attributes will allow the server to access the file. The location of the file is either in the directory from which the server is started, or in the directory specified by the DSMSERV_DIR environment variable. Re-specify the DSMSERV-DIR environment variable if this specification is in error. Also ensure that there is sufficient space on the drive specified for the file. If the problem persists after these corrections have been made, contact your service representative.

ANR9637E (Windows NT)Cannot access node license lock file: file name.

Explanation: The server was not able to access the specified file. The node lock file contains licensing information for the server.

System Action: The license function fails.

User Response: Examine the file specification displayed and ensure that the file attributes will allow the server to access the file. The location of the file is either in the directory from which the server is started, or in the directory specified by the DSMSERV_DIR environment variable. Re-specify the DSMSER-DIR environment variable if this specification is in error. Also ensure that there is sufficient space on the drive specified for the file. If the problem persists after these corrections have been made, contact your service representative.

ANR9638W (HP-UX)License registration is not supported on this server.

Explanation: The REGISTER LICENSE command fails because the license authorization module cannot be found.

System Action: Server operation continues; licensing terms are not changed by the REGISTER LICENSE command.

User Response: The license authorization file is required for formal licensing for the HP-UX server. The file is delivered when the server is purchased, but it is not available in the product service stream or with demonstration copies of the server. If you have purchased the server, contact your service representative for assistance in resolving this problem.

ANR9638W (Solaris)License registration is not supported on this server.

Explanation: The REGISTER LICENSE command fails because the license authorization module cannot be found.

System Action: Server operation continues; licensing terms are not changed by the REGISTER LICENSE command.

User Response: The license authorization file is required for formal licensing for the Sun Solaris server. The file is delivered when the server is purchased, but it is not available in the product service stream or with demonstration copies of the server. If you have purchased the server, contact your service representative for assistance in resolving this problem.

ANR9638W (Windows NT)License registration is not supported on this server.

Explanation: The REGISTER LICENSE command fails because the license authorization module cannot be found.

System Action: Server operation continues; licensing terms are not changed by the REGISTER LICENSE command.

User Response: The license authorization file is required for formal licensing for the Windows NT server. The file is delivered when the product is purchased, but it is not available in the product service stream or with demonstration copies of the server. If you have purchased the server, contact your service representative for assistance in resolving this problem.

ANR9639W (HP-UX)Unable to load shared library shared library.

Explanation: The server module is unable to load the indicated shared library.

System Action: Server operation continues, but the function that requires the shared library will be inoperative.

User Response: Ensure that the shared library is accessible. If this is an evaluation copy of the server, then this message is normal for the DSMREG library, since the library is only provided with purchased servers. The server licensing will assume "Try and Buy" mode with sample licensed options for a period of time.

ANR9639W (Solaris)Unable to load Shared License File shared library.

Explanation: The server was unable to loaded the shared library.

System Action: Server operation continues, but functions that require the shared library will be inoperative.

User Response: Make sure the shared library is accessible/readable. This message is normal for those servers in the Try and Buy mode.

ANR9640E (HP-UX)Unable to load procedure address from shared library shared library.

Explanation: The server module is unable to load the address of a routine in the indicated shared library.

System Action: Server operation continues, but the function that requires the shared library will be inoperative.

User Response: Ensure that the shared library is accessible. If the problem persists, contact your service representative.

ANR9640E (Solaris)Unable to load procedure address from shared library shared library license module.

Explanation: The server module is unable to load the address of a routine in the indicated shared library for license loading.

System Action: Server operation continues, but the function that requires the shared library will be inoperative.

User Response: Ensure that the shared library is accessible. If the problem persists, contact your customer service representative.

ANR9641W (HP-UX)One or more EVALUATION LICENSES will expire on expiration date.

Explanation: Although you are running with a purchased version of the server, there are one or more licenses registered that will expire on the date specified. This is usually the case when you have been using evaluation licenses prior to purchasing the product.

System Action: Server operation continues.

User Response: Halt the server and erase the nodelock file in the server startup directory. After restarting the server, use the REGISTER LICENSE command to define the licensed features that you have purchased with your server. These licenses should NOT have an expiration date, so this message should not appear after re-registering the proper licenses. If this message persists, contact your service representative.

ANR9641W (Solaris)One or more EVALUATION LICENSES will expire on expiration date.

System Action: Server operation continues.

User Response: Halt the server and erase the nodelock file in the server startup directory. After restarting the server, use the REGISTER LICENSE command to define the licensed features that you have purchased with your server. These licenses should NOT have an expiration date, so this message should not appear after re-registering the proper licenses. If this message persists, contact your service representative.

ANR9642E (HP-UX)The specified license authorization code (license authorization code) is invalid.

Explanation: The license authorization code which you entered using the REGISTER LICENSE command is invalid.

System Action: No additional licenses are registered. Server operation continues.

User Response: Obtain a valid license authorization code and try the command again.

ANR9678W (Windows NT)File name used for server executable. A server is currently running as a service.

Explanation: The name of the executable used when the server is running as a service cannot be used in the plan file.

System Action: PREPARE uses file name identified in the message within the plan file and generation of the plan file continues.

User Response: None.

ANR9679W (AIX)Command: Unable to locate file file name.

Explanation: The specified file cannot be found. Note: PREPARE assumes that the volume formatting program (dsmfmt), is located in the same directory as the server executable file.

System Action: PREPARE uses the following default file names in the plan file:

User Response: Determine why file does not exist; create if necessary.

ANR9679W (Windows NT)Command: Unable to locate file file name.

Explanation: The specified file cannot be found.

System Action: PREPARE uses the following default file names in the plan file:

User Response: Determine why file does not exist; create if necessary.

ANR9680W (AIX)Command: Could not obtain AIX logical volume information for volume name while building stanza recovery plan stanza name.

Explanation: This volume is defined to the server but PREPARE cannot obtain AIX logical volume information for it from the AIX Object Data Manager (ODM).

System Action: The entry for the volume is not included in the recovery plan stanza.

User Response: This message should be preceded by another error message which contains the ODM error code.

ANR9680W (HP-UX)Command: Could not obtain logical volume information for volume name while building stanza recovery plan stanza name.

Explanation: This volume is defined to the server but PREPARE cannot obtain logical volume information for it.

System Action: The entry for the volume is not included in the recovery plan stanza.

User Response: This message should be preceded by another error message which contains an error code.

ANR9680W (S/390)Command: Catalog information cannot be obtained for file 'file name'.

Explanation: Catalog information cannot be obtained for the file specified in the message. DRM does not support creation of JCL for a file that is not catalogued.

System Action: The stanzas, where JCL is created, for this file will not contain volume or unit information.

User Response: Catalog the file.

ANR9680W (Solaris)Command: Could not obtain logical volume information for volume name while building stanza recovery plan stanza name.

Explanation: This volume is defined to the server but PREPARE cannot obtain logical volume information for it.

System Action: The entry for the volume is not included in the recovery plan stanza.

User Response: This message should be preceded by another error message which contains an error code.

ANR9680W (Windows NT)Unable to locate path for component in registry.

Explanation: The path to the component could not be found in the registry.

System Action: PREPARE uses the following default path names in the plan file:

User Response: Determine why path does not exist; install components if necessary.

ANR9681W (AIX)Command: Volume file name not found while building stanza recovery plan stanza name.

Explanation: This volume is defined to the server but does not exist. The device class associated with the volume is DISK or the device class device type is FILE.

System Action: The entry for the volume is not included in the recovery plan stanza.

User Response: Determine why the file does not exist; create it if necessary.

ANR9681W (AS/400)Command: Volume file name not found while building stanza recovery plan stanza name.

Explanation: This volume is defined to the ADSM server but does not exist or has some other problem. If the file exists, the error code issued in a previous message can be checked to determine the problem. The device class associated with the volume is DISK or the device class device type is FILE.

System Action: The entry for the volume is not included in the recovery plan stanza.

User Response: Determine why file does not exist or what the problem is; create if necessary.

ANR9681W (S/390)Command: Volume file name not found while building stanza recovery plan stanza name.

Explanation: This volume is defined to the server but does not exist. The device class associated with the volume is DISK or the device class device type is FILE.

System Action: The entry for the volume is not included in the recovery plan stanza.

User Response: Determine why file does not exist; create if necessary.

ANR9681W (Windows NT)Command: Volume file name not found while building stanza recovery plan stanza name.

Explanation: This volume is defined to the server but does not exist. The device class associated with the volume is DISK or the device class device type is FILE.

System Action: The entry for the volume is not included in the recovery plan stanza.

User Response: Determine why file does not exist; create if necessary.

ANR9682E (AIX)Command: Generated file name too long. Length of directory or prefix 'prefix' plus 'name' exceeds maximum characters characters.

Explanation: The file name generated is too long. The maximum valid length is shown in the message.

System Action: The recovery plan file was not created.

User Response: Reissue the command specifying a valid prefix. The following commands are used to specify the prefix:

ANR9682E (AS/400)Command: Generated file name too long. Length of library or prefix 'prefix' plus 'name' exceeds maximum characters characters.

Explanation: The file name generated is too long. The maximum valid length is shown in the message.

System Action: The recovery plan file was not created.

User Response: Reissue the command specifying a valid prefix. The following commands are used to specify the prefix:

ANR9682E (S/390)Command: Generated file name too long. Length of directory or prefix 'prefix' plus 'name' exceeds maximum characters characters.

Explanation: The file name generated is too long. The maximum valid length is shown in the message.

System Action: The recovery plan file was not created.

User Response: Reissue the command specifying a valid prefix. The following commands are used to specify the prefix:

ANR9682E (Windows NT)Command: Generated file name too long. Length of directory or prefix 'prefix' plus 'name' exceeds maximum characters characters.

Explanation: The file name generated is too long. The maximum valid length is shown in the message.

System Action: The recovery plan file was not created.

User Response: Reissue the command specifying a valid prefix. The following commands are used to specify the prefix:

ANR9683E (AIX)Command: Cannot generate fully qualified file name for 'name'.

Explanation: A failure occurred expanding the specified file name.

System Action: Recovery plan file not created.

User Response: Reissue the command specifying a valid prefix. The following commands are used to specify the prefix:

ANR9683E (AS/400)Command: Cannot generate fully qualified file name for 'name'.

Explanation: A failure occurred expanding the specified file name.

System Action: Recovery plan file not created.

User Response: Reissue the command specifying a valid prefix. The following commands are used to specify the prefix:

ANR9683W (S/390)Command: Cannot generate fully qualified file name for 'name'. Prepare will substitute file name 'default name'.

Explanation: The fully qualified name for the volume history or device configuration file specified in the message could not be determined. Either the volume history or device configuration file specified in the plan file does not exist or some other error has occurred.

System Action: Recovery plan file was created using the substitute name.

User Response: Reissue the command after the volume history or device configuration file has been backed up.

ANR9683E (Windows NT)Command: Cannot generate fully qualified file name for 'name'.

Explanation: A failure occurred expanding the specified file name.

System Action: Recovery plan file not created.

User Response: Reissue the command specifying a valid prefix. The following commands are used to specify the prefix:

ANR9684E (AIX)Command: Cannot generate server options file name.

Explanation: A failure occurred generating the server options file name.

System Action: Recovery plan file not created.

User Response: See accompanying messages for more information.

ANR9684E (AS/400)Command: Cannot generate server options file name.

Explanation: A failure occurred generating the server options file name.

System Action: Recovery plan file not created.

User Response: See accompanying messages for more information.

ANR9684E (S/390)Command: Cannot generate fully qualified file name for 'name'.

Explanation: A failure occurred creating the specified file name.

System Action: Recovery plan file not created.

User Response: Reissue the command specifying a valid prefix. The following commands are used to specify the prefix:

ANR9684E (Windows NT)Command: Cannot generate server options file name.

Explanation: A failure occurred generating the server options file name.

System Action: Recovery plan file not created.

User Response: See accompanying messages for more information.

ANR9685E (AIX)Command: Cannot generate a volume history file name.

Explanation: A failure occurred generating the volume history file name.

System Action: Recovery plan file not created.

User Response: See accompanying messages for more information.

ANR9685E (AS/400)Command: Cannot generate a volume history file name.

Explanation: A failure occurred generating the volume history file name.

System Action: Recovery plan file not created.

User Response: See accompanying messages for more information.

ANR9685E (S/390)Command: Catalog information cannot be found for options file 'file name'.

Explanation: The options file name specified in the message is not cataloged. The options file must be cataloged.

System Action: The recovery plan file was not created.

User Response: Catalog the options file.

ANR9685E (Windows NT)Command: Cannot generate a volume history file name.

Explanation: A failure occurred generating the volume history file name.

System Action: Recovery plan file not created.

User Response: See accompanying messages for more information.

ANR9686E (AIX)Command: Cannot generate a device configuration file name.

Explanation: A failure occurred generating the device configuration file name.

System Action: Recovery plan file not created.

User Response: See accompanying messages for more information.

ANR9686E (AS/400)Command: Cannot generate a device configuration file name.

Explanation: A failure occurred generating the device configuration file name.

System Action: Recovery plan file not created.

User Response: See accompanying messages for more information.

ANR9686E (Windows NT)Command: Cannot generate a device configuration file name.

Explanation: A failure occurred generating the device configuration file name.

System Action: Recovery plan file not created.

User Response: See accompanying messages for more information.

ANR9690W (S/390)Command: Cannot obtain help file name.

Explanation: Help file name cannot be obtained. HLPAMENG will not be included in the START.SERVER stanza of the plan file.

System Action: Processing continues.

User Response: None.

ANR9691W (S/390)Command: Cannot obtain image file name.

Explanation: Image file name cannot be obtained. IMAGES will not be included in the START.SERVER stanza of the plan file.

System Action: Processing continues.

User Response: None.

ANR9710EInsufficient memory to continue operations.

Explanation: There is not enough memory to operate the label utility program.

System Action: The program is halted.

User Response: Provide more memory for the program to use.

ANR9711EUnrecognized argument 'argument'.

Explanation: The specified argument is not recognized as one that is supported by the label utility program.

System Action: The program is halted.

User Response: Retry the label utility program with the correct argument syntax.

ANR9712EArgument has invalid value 'argument'.

Explanation: The value specified for the given argument is not valid.

System Action: The program is halted.

User Response: Retry the label utility program with the correct argument syntax.

ANR9713EOnly one library can be specified.

Explanation: Only one library can be specified in the argument list for the label utility program.

System Action: The program is halted.

User Response: Retry the label utility program with the correct argument syntax.

ANR9714ENo drives were specified.

Explanation: At least one drive must be specified for use by the label utility (DSMLABEL) program.

System Action: The program is halted.

User Response: Retry the label utility program with the correct argument syntax.

ANR9715EError starting label activity for drive drive name.

Explanation: The label utility is unable to start its activity for the given drive.

System Action: The program is halted.

User Response: Increase the number of allowed threads or processes in the system, then retry the operation.

ANR9716EDevice 'library name' is not accessable, or is not recognized as a supported library type.

Explanation: The device specified for the library cannot be accessed or is not recognized as a supported device.

System Action: The program is halted.

User Response: Retry the operation, specifying a valid supported library.

ANR9717EElement address element address is not valid for drive 'drive name'.

Explanation: The specified element address does not represent a valid drive location in the associated library.

System Action: The program is halted.

User Response: Retry the operation, specifying a valid element address for the drive.

ANR9718EDevice 'drive name' is not recognized as a supported drive type.

Explanation: The device specified for the drive is not recognized as a supported device.

System Action: The program is halted.

User Response: Retry the operation, specifying a valid supported drive.

ANR9719EToo many drives were specified.

Explanation: The number of drives specified on the command line exceeds the limits of the program.

System Action: The program is halted.

User Response: Retry the operation, specifying only up to the maximum number of supported drives. The program can be invoked with the -help argument to determine this maximum value.

ANR9720IVolume 'volume name' was labeled successfully using drive 'drive name'.

Explanation: The volume is successfully labeled.

System Action: The program continues operation.

User Response: None.

ANR9721E'Volume name' is not a valid volume name.

Explanation: The specified string is not a valid volume name.

System Action: The program prompts for a new volume name.

User Response: Enter a volume name that is within the length constraints for the media type being labeled, and which contains only alphanumeric characters.

ANR9722IInsert a new volume in drive 'drive name', then enter the name (1-maximum length characters) to be used for its label; or just press ENTER to quit this program:

Explanation: The program prompts for a new volume to be mounted in the given drive so that a label can be written to it.

System Action: The program waits for the volume name to be entered.

User Response: Mount a new volume, then type a volume name for it and press ENTER; or, if you want to quit the program, press ENTER without entering a volume name.

ANR9723IInsert side A of a new volume in drive 'drive name', then enter the name (1-maximum length characters) to be used for its label; or just press ENTER to quit this program:

Explanation: The program prompts for a new volume to be mounted in the given drive so that a label can be written to it.

System Action: The program waits for the volume name to be entered.

User Response: Mount side A of a new volume, then type a volume name for it and press ENTER; or, if you want to quit the program, press ENTER without entering a volume name.

ANR9724IFlip the volume in drive 'drive name' to side B, then press ENTER.

Explanation: The program prompts for a two-sided volume to be flipped so that its second side can be labeled.

System Action: The program waits for the ENTER key to be pressed.

User Response: Flip the volume in the drive, and press ENTER.

ANR9725EThe volume in drive 'drive name' is already labeled (volume name).

Explanation: The volume in the specified drive cannot be labeled because it already contains a valid label with the given name.

System Action: The volume is not labeled.

User Response: If an overwrite of the existing label with a new label is desired, restart the DSMLABEL utility program by using the -overwrite argument.

ANR9726EI/O error writing label for volume 'volume name' in drive 'drive name'.

Explanation: An I/O error occurs while attempting to write the label for the specified volume in the given drive.

System Action: The volume is not labeled.

User Response: Ensure that the volume is not write protected, the drive is powered on and ready, and the device parameter has the correct value.

ANR9727EMedia fault detected on volume 'volume name' in drive 'drive name'.

Explanation: A media fault condition is detected for the specified volume in the given drive.

System Action: The volume is not labeled.

User Response: Remove the volume from use, since the media is questionable. If the media in question requires formatting, such as an unformatted optical disk, retry the operation by starting the program with the '-format' argument.

ANR9728EError ejecting volume from drive 'drive name'.

Explanation: An error occurs while ejecting the volume from the given drive.

System Action: All further activity on the given drive is suspended.

User Response: Ensure that the drive is in proper operating condition before resuming its use.

ANR9729EI/O error formatting volume 'volume name' in drive 'drive name'.

Explanation: An I/O error occurs while attempting to format the media for the specified volume in the given drive.

System Action: The volume is not labeled.

User Response: Ensure that the volume is not write protected, that the drive is powered on and ready, and that the media is not damaged.

ANR9730IManual intervention required for library device 'library device name'.

Explanation: The specified library device requires manual intervention before it can be accessed for normal operations.

System Action: The operation will be retried periodically until either the required action is performed or a timeout occurs.

User Response: If the library has an access door, make sure it is in the closed position. If it has a cartridge carousel, make sure the carousel is installed.

ANR9731IInsert a new volume into the entry/exit port of library 'library device name', then enter the name (1-maximum length characters) to be used for its label; or just press ENTER to quit this program:

Explanation: The program prompts for a new volume to be mounted in the entry/exit port of the given library so that a label can be written to it.

System Action: The program waits for the volume name to be entered.

User Response: Insert a new volume into the entry/exit port, then type a volume name for it and press ENTER; or, if you want to quit the program, press ENTER without entering a volume name.

ANR9732IInsert a new volume in the entry/exit port of library 'library device name' with side A facing up, then enter the name (1-maximum length characters) to be used for its label; or just press ENTER to quit this program:

Explanation: The program prompts for a new volume to be mounted in the entry/exit port of the given library so that a label can be written to it.

System Action: The program waits for the volume name to be entered.

User Response: Insert a new volume into the entry/exit port, then type a volume name for it and press ENTER; or, if you want to quit the program, press ENTER without entering a volume name.

ANR9733IInsert a new volume in drive 'drive name' of library 'library device name', then enter the name (1-maximum length characters) to be used for its label; or just press ENTER to quit this program:

Explanation: The program prompts for a new volume to be mounted in the given drive so that a label can be written to it.

System Action: The program waits for the volume name to be entered.

User Response: Mount a new volume, close the library access door, and then type a volume name for it and press ENTER; or, if you want to quit the program, press ENTER without entering a volume name.

ANR9734IInsert side A of a new volume in drive 'drive name' of library 'library device name', then enter the name (1-maximum length characters) to be used for its label; or just press ENTER to quit this program:

Explanation: The program prompts for a new volume to be mounted in the given drive so that a label can be written to it.

System Action: The program waits for the volume name to be entered.

User Response: Mount side A of a new volume, close the library access door, and then type a volume name for it and press ENTER; or, if you want to quit the program, press ENTER without entering a volume name.

ANR9735IEnter the name (1-maximum length characters) for the next volume to label in library 'library device name'; or just press ENTER to quit this program:

Explanation: The program prompts for the name of the next volume to be labeled in the given library.

System Action: The program waits for the volume name to be entered.

User Response: Type the name for the next volume to be labeled and then press ENTER; or, if you want to quit the program, press ENTER without entering a volume name.

ANR9736EAn I/O error occurred while accessing library device 'library device name'.

Explanation: An attempted I/O operation for the given library failed.

System Action: If the error is noncritical, operation continues; otherwise, the program is halted.

User Response: Ensure that the library device is powered on and ready, any access doors are closed, the device parameter has the correct value, and then retry the operation that was in progress when the error occurred.

ANR9737IRemove the volume from drive 'drive name' in library 'library device name', then press ENTER.

Explanation: All activity associated with the volume in the given drive is complete, so it should be removed.

System Action: The program waits until the ENTER key is pressed.

User Response: Remove the volume from the specified drive, then close the library access door and press ENTER.

ANR9738IRemove the volume from the entry/exit port of library 'library device name', then press ENTER.

Explanation: All activity associated with the volume in the entry/exit port is complete, so it should be removed.

System Action: The program waits until the ENTER key is pressed.

User Response: Remove the volume from the entry/exit port, and press ENTER.

ANR9739IInitializing library device 'library device name'.

Explanation: The specified library device is being initialized for use by the labeling utility program.

System Action: The library device is prepared for use.

User Response: None.

ANR9740EVolume 'volume name' is not in the INSERT category.

Explanation: The specified volume cannot be labeled because it is not in the library's "insert" category. This restriction is provided as a safeguard against labeling volumes that are in use, and possibly destroying valid data.

System Action: The volume is not labeled.

User Response: If you are sure the volume contains no valid data, it can be removed from the library and then reinserted with the library's convenience I/O station. This will cause the volume's category code to be changed to the INSERT category, and thus allow the labeling operation to work.

ANR9741EDrives 'drive name' and 'drive name' cannot use the same element address.

Explanation: The element addresses specified for the given drives are the same. This is not allowed, since the element address is the only way in which the robot can distinguish between different drives in a SCSI library.

System Action: The program is stopped.

User Response: Restart the program, providing valid and unique element addresses. Appropriate values can be determined with the worksheets in Administrator's Guide.

ANR9742EThe element address for drive 'drive name' is missing or invalid.

Explanation: The element address value for the specified drive is omitted, or an illegal value has been provided.

System Action: The program is stopped.

User Response: Restart the program, providing a valid element address. Appropriate values can be determined with the worksheets in Administrator's Guide.

ANR9743IAttempting to label volume 'volume name' using drive 'drive name'...

Explanation: The specified volume is in the process of being labeled in the given drive.

System Action: Labeling activity continues.

User Response: None.

ANR9744EVolume 'volume name' is not present in library 'library name'.

Explanation: The specified volume is not present in the given library, so it cannot be labeled.

System Action: Labeling activity continues for other volumes.

User Response: Insert the volume into the library, then retry the operation.

ANR9745EOnly one trace argument is allowed.

Explanation: More than one trace argument has been encountered, but only one is allowed.

System Action: The program is halted.

User Response: Retry the program, specifying at most one trace argument.

ANR9746EUnable to open trace file 'file name'.

Explanation: An error occurs while opening the specified file for writing trace data.

System Action: The program is halted.

User Response: Retry the program, specifying a valid file name for the trace file.

ANR9747IUnable to write to trace file.

Explanation: An error occurs while writing data to the trace file.

System Action: The program continues, but trace data may be lost.

User Response: Make sure the disk that contains the trace file is not full or defective and then retry the operation.

ANR9748IInsert a new volume into slot with element number 'slot element address' of library 'library device name', then enter the name (1-maximum length characters) to be used for its label; or just press ENTER to quit this program:

Explanation: The program prompts for a new volume to be inserted into the given slot with the specified element number so that a label can be written to it. For the slot and element number diagram of your library, refer to the documentation provided with the current ptf level or refer to the Administrator's Guide for your release and platform.

System Action: The program waits for the volume name to be entered.

User Response: Insert a new volume, close the library access door, type a volume name for it, and press ENTER; or, if you want to quit the program, press ENTER without entering a volume name.

ANR9749IInsert a new volume into slot with element number 'slot element address' of library 'library device name' with side A facing up, then enter the name (1-maximum length characters) to be used for its label; or ju st press ENTER to quit this program:

Explanation: The program prompts for a new volume to be inserted into the slot with the specified element number so that a label can be written to it. For the slot and element number diagram of your library, refer to the documentation provided with the current ptf level or refer to the Installing the Server and Administrative Client manual for your release and platform.

System Action: The program waits for the volume name to be entered.

User Response: Insert side A of a new volume, close the library access door, type a volume name for it, and press ENTER; or, if you want to quit the program, press ENTER without entering a volume name.

ANR9750IRemove the volume from slot with element number 'slot element address' in library 'library device name', then press ENTER.

Explanation: All activity associated with the volume in the given slot with the specified element number is complete, so it should be removed. For the slot and element number diagram of your library, refer to the documentation provided with the current ptf level or refer to the Administrator's Guide for your release and platform.

System Action: The program waits until the ENTER key is pressed.

User Response: Remove the volume from the specified slot, close the library access door, and press ENTER.

ANR9751EThe volume in drive 'drive name' is not compatible with the drive.

Explanation: The volume cannot be used in the drive. It is most likely an outdated media type that the drive cannot write.

System Action: The volume is not labeled.

User Response: Remove the volume; replace it with a different type known to work in the drive, or press ENTER to end the program.

ANR9752ECould not access drive 'drive name'. It may be in use by another application.

Explanation: The specified drive cannot be accessed.

System Action: The program is halted.

User Response: Ensure that the drive name is correct and the device is not in use by another application, then retry the operation.

ANR9753ESkipping slot element address 'slot element address', which has no barcode.

Explanation: The cartridge in the indicated slot will not be labeled, since it does not have a valid barcode.

System Action: The program attempts to label the next cartridge.

User Response: Examine the cartridge to see if it has a barcode. Add a barcode if required.

ANR9754IBarcode of element slot element address, 'hardware barcode string', exceeds maximum length characters in length.

Explanation: A barcode is encountered that was longer than a valid volume name.

System Action: The barcode is not considered valid and will not be used for the server process.

User Response: Replace the cartridge's barcode with one that is supported by the library and whose number of characters does not exceed the maximum length.

ANR9755EThere are no barcodes available.

Explanation: The hardware did not return any valid barcode data for any cartridge.

System Action: The program terminates without attempting to label any cartridges.

User Response: Make sure the hardware supports barcodes, or that barcode labels have been affixed to the cartridges.

ANR9756INo volumes were found.

Explanation: No volumes are found in the library. This means that in a 349x ATL, no volumes were found in the insert category (xFF00), and that in a SCSI autochanger, no cartridges were loaded into the library.

System Action: The program terminates normally.

User Response: Insert cartridges into the library. For a 349x ATL, this may involve changing the category of previously inserted cartridges to be relabeled.

ANR9757EACS drive id ACS drive id is not valid for drive 'drive name'.

Explanation: The specified ACS drive id does not represent a valid drive location in the associated library.

System Action: The program is halted.

User Response: Retry the operation, specifying a valid drive id for the drive.

ANR9758WError mounting volume 'volume name'.

Explanation: An error occurs while mounting the volume to the drive. This may not be an error since the volume or drive maybe in use or locked in a shared environment.

System Action: The specified volume is bypassed for labeling.

User Response: Ensure that the volume is not locked or in use if label is required.

ANR9759Eunsuccessful ACSAPI response, status=acs status.

Explanation: The ACSLS library api responded with an unsuccessful status as indicated.

System Action: Depends on the ACS api for labeling, the process may continue as the error may not be a problem.

User Response: If the label process terminates, contact your ACS System Administrator and perform ACSLS library problem determination.

ANR9760IWait and monitor the ACSSA console message to remove volume volume id from CAP.

Explanation: The specified volume is about to put into CAP for removal. Monitor the ACSSA console and removed the volume after it has been placed into the CAP as indicated in the ACSSA message.

System Action: None.

User Response: Monitor the ACSSA console and wait.

ANR9773EHardware configuration error in library library name: number of drives drives, number of storage slots storage slots.

Explanation: The library device retuned a count of zero for either the drives or the slots. The drives may have not yet been configured to the operating system, or to the library. The library must have at least one drive and multiple slots when properly configured in order to be defined to the server.

System Action: The operation fails.

User Response: Configure the drives to the operating system, and reinitialize the library.

ANR9774WVolume volume name should be freed of data as soon as possible.

Explanation: The server has received an indication from the 3995 that the indicated volume is out of spare sectors for re-allocation. Spare sectors are reserved to take the place of sectors that experience I/O problems. The re-allocation can take place on either a read or write.

System Action: The indicated volume is marked read-only by the server.

User Response: A MOVE DATA command should be used as soon as possible to move the data from this cartridge to other cartridges in the library. This cartridge should NOT be marked read-write again through the UPDATE VOLUME command.

ANR9775EError while writing on volume volume name (RC=internal code).

Explanation: An I/O error has occurred while writing on the specified volume.

System Action: The operation fails.

User Response: Ensure that the 3995 volume is accessible and that the media is usable. Diagnostics may have to be run on the 3995 with the specified volume. If the problem persists, contact your service representative and provide the internal code values from this message. The internal code is returned to the server from the OS/2 operating system.

ANR9776IFile file name is being erased and deleted. Data erasure may take several minutes.

Explanation: A file is being deleted from an optical library cartridge. The file is deleted when a LAN3995 device class volume is deleted. File deletion includes erasure of data. The erasure process can take several minutes to complete.

System Action: The operation continues.

User Response: None.

ANR9778EUnable to establish a communication session with either the primary library manager or the secondary library manager.

Explanation: The requested operation required that a communication session be established with with a library manager. Both library managers were found to be unavailable at this time.

System Action: None.

User Response: Verify the primary or secondary library manager is up and operational. Once the server is verified to be operational, retry the operation.

ANR9779EUnable to acquire a drive for volume volume name from the library manager.

Explanation: The library manager was unable to assign a drive to the library client. There are a couple of situations that can cause this error.

System Action: None.

User Response: Verify that a drive is available on the library manager side and the drive is currently not busy or marked offline on the library client. Set the mount retention on the device class on the library manager and the library clients to a lower value. Using a lower mount retention value can free up drives.

ANR9780EVolume volume name is not mounted in drive from the library drive name.

Explanation: A communication error occured while dismount the volume.

System Action: None.

User Response: Verify the library manager is up and operational. Verify that the library manager and library client can communicate using command routing.

ANR9781EVolser volume name was not found to be mounted on the library manager.

Explanation: According to the library manager, the requested volume is no longer mounted. The error occured if the library manager forced the volume to be dismounted because of a communication error.

System Action: None.

User Response: Verify that the volume has been dismounted.

ANR9782EPrimary Library Manager primary library manager name is NOT defined as a server.

Explanation: The primary library manager server has not be defined to this server.

System Action: None.

User Response: Define the server to this server using the DEFINE SERVER command.

ANR9783EPrimary Library Manager does not contain a valid value.

Explanation: The primary library manager server has not be defined to this server.

System Action: None.

User Response: Define the server to this server using the DEFINE SERVER command.

ANR9784ESecondary Library Manager secondary library manager name is NOT defined as a server.

Explanation: The secondary library manager server name has not be defined to this server.

System Action: None.

User Response: Define the server to this server using the DEFINE SERVER command.

ANR9785EDrive drive name, is not defined on the library manager.

Explanation: A drive is being defined that does not exist or is being managed by the library manager.

System Action: None.

User Response: Verify drive name with the library manager.

ANR9786EA communication error has occured. Operation ending.

Explanation: A communication error occured.

System Action: None.

User Response: Verify the library manager is up and operational. Verify that the library manager and library client can communicate using command routing.

ANR9787EThe owner name specified is not defined to this server.

Explanation: A command was issues specifing a ownership of a volume. The name of the owner given was not defined to this server.

System Action: None.

User Response: Define the server to this server using the DEFINE SERVER command.

ANR9788ECommand: Library library name is not defined - the primary library manager not defined.

Explanation: The designated library is not defined because the primary library manager is not defined as a server to this server.

System Action: The command is not processed.

User Response: Define the server to this server using the DEFINE SERVER command.

ANR9789ECommand: Library library name is not defined - the secondary library manager not defined.

Explanation: The designated library is not defined because the secondary library manager is not defined as a server to this server.

System Action: The command is not processed.

User Response: Define the server to this server using the DEFINE SERVER command.

ANR9790WRequest to mount volume Volume Name for library client Library Client Name failed.

Explanation: A library client requested a volume to be mount by the library manager, which inturn failed.

System Action: None.

User Response: Verify the status of all drives are currently online and not in use by other library clients or the library manager itself. Free up drive resources as needed.

ANR9791IVolume Volume Name in library Library Name ownership is changing from Current volume owner to New Volume owner.

Explanation: A library client requested a volume to be mount by the library manager, which inturn failed.

System Action: None.

User Response: Verify the status of all drives are currently online and not in use by other library clients or the library manager itself. Free up drive resources as needed.

ANR9792ELibrary Library Name on library manager Library Manager Name is currently not being shared.

Explanation: A define library command attempted to define a shared library that was not being shared by the library manager.

System Action: None.

User Response: Verify the library on the library manager is being shared. If the library is not being shared, update the library shared status to yes.

ANR9793Iprocess name in library library name- CANCEL PENDING.

Explanation: In response to a QUERY PROCESS command, this message displays the status for a process on the server. The command was started, but the process was canceled by an administrator.

System Action: The background process operation is being terminated.

User Response: None.

ANR9794EUnable to load the RSM dynamic link library dynamic link library.

Explanation: The server module is unable to load the indicated dynamic link library.

System Action: Server operation continues, but the function that requires the dynamic link library will be inoperative.

User Response: Ensure that the installed Windows version supports RSM. Ensure that the Removable Storage Manager is installed and the system DLL is accessible.

ANR9795ECommand: Invalid storage service name storage service name.

Explanation: The designated storage service name is invalid; either it contains too many characters, or some of the characters are invalid.

System Action: The command is not processed.

User Response: Reissue the command using a valid storage service name.

ANR9796ECommand: Drivemapping is already defined for drive drive name in library library name on storage service storage service name.

Explanation: The designated drivemapping cannot be defined because it has already been defined for the specified drive, library, and storage service.

System Action: The command is not processed.

User Response: If you want to define an additional drivemapping, reissue the command with a different drive name.

ANR9797ECommand: Drivemapping for drive drive name is not defined in library library name on storage service storage service name.

Explanation: The designated drivemap has not been defined for the given drive in the given library on the give storage service.

System Action: The command is not processed.

User Response: Reissue the command using a different drive name. If appropriate, define the drive before retrying the command.

ANR9798ECommand: One or more drivemappings are still defined for drive drive name in library library name.

Explanation: The designated drive cannot be deleted because there are still drivemapping defined for it.

System Action: The command is not processed.

User Response: Delete all drivemappings for the drive, and reissue the command.

ANR9799ECommand: Library Library Name is currently not being shared.

Explanation: The command attempted to perform an operation that is not allowed unless the library is allowed to be shared .

System Action: None.

User Response: Verify the library on the library manager is being shared. If the library is not being shared, update the library shared parameter to yes.

ANR9801I (Windows NT)ANR9801: Ready for operations.

Explanation: The device driver has successfully initialized and is ready to accept requests from the server.

System Action: Processing continues.

User Response: None.

ANR9803W (Windows NT)ANR9803: ERROR! Insufficient free memory to initialize driver.

Explanation: The server device driver is unable to initialize due to an inability to acquire dynamic storage.

System Action: Processing continues. The device driver is not available to process requests from the server.

User Response: For minimum storage requirements, refer to Licensed Program Specifications/2. You must have sufficient memory in your system to initialize Windows NT and the device drivers you want to use.

ANR9810I (Windows NT)ANR9810: SCSI Tape Device Driver Initializing ...

Explanation: The server SCSI tape device driver has been invoked by the system and is initializing.

System Action: Processing continues.

User Response: None.

ANR9820I (Windows NT)ANR9820: SCSI Autochanger Device Driver Initializing ...

Explanation: The server SCSI automatic changer device driver has been invoked by the system and is initializing.

System Action: Processing continues.

User Response: None.

ANR9900W (AIX)Attention -- Accounting records could not be written to the file: filespec.

Explanation: The server detects an error while trying to open the accounting file.

System Action: Server processing continues.

User Response: Ensure that there is sufficient disk space and that the accounting file is not marked as read-only.

ANR9900W (AS/400)Attention -- Accounting file could not be opened for write: filespec.

Explanation: ADSM detects an error while trying to open the accounting file.

System Action: Server processing continues.

User Response: Ensure that sufficient disk space is available and that the accounting file is not marked as read-only.

ANR9900W (HP-UX)Attention -- Accounting records could not be written to the file: file name.

Explanation: The server detects an error while trying to open the accounting file.

System Action: Server processing continues, but no accounting records are written.

User Response: Ensure that there is sufficient disk space and that the accounting file is not marked as read-only.

ANR9900W (Solaris)Attention -- Accounting records could not be written to the file: file name.

Explanation: The server detects an error while trying to open the accounting file.

System Action: Server processing continues, but no accounting records are written.

User Response: Ensure that there is sufficient disk space and that the accounting file is not marked as read-only.

ANR9900W (Windows NT)Attention -- Accounting records could not be written to the file: filespec.

Explanation: The server detects an error while trying to open the accounting file.

System Action: Server processing continues.

User Response: Ensure that there is sufficient disk space and that the accounting file is not marked as read-only.

ANR9901W (AIX)Attention -- Accounting records could not be written to the file: filespec.

Explanation: The server detects an error while trying to write an accounting record.

System Action: Server processing continues.

User Response: Ensure that there is sufficient disk space and that the accounting file is not marked as read-only.

ANR9901W (AS/400)Attention -- Accounting records could not be written to the file: filespec.

Explanation: ADSM detects an error while trying to write an accounting record.

System Action: Server processing continues.

User Response: Ensure that sufficient disk space is available and that the accounting file is not marked as read-only.

ANR9901W (HP-UX)Attention -- Accounting records could not be written to the file: file name.

Explanation: The server detects an error while trying to write an accounting record.

System Action: Server processing continues.

User Response: Ensure that there is sufficient disk space and that the accounting file is not marked as read-only.

ANR9901W (Solaris)Attention -- Accounting records could not be written to the file: file name.

Explanation: The server detects an error while trying to write an accounting record.

System Action: Server processing continues.

User Response: Ensure that there is sufficient disk space and that the accounting file is not marked as read-only.

ANR9901W (Windows NT)Attention -- Accounting records could not be written to the file: filespec.

Explanation: The server detects an error while trying to write an accounting record.

System Action: Server processing continues.

User Response: Ensure that there is sufficient disk space and that the accounting file is not marked as read-only.

ANR9902W (AIX)Attention -- Accounting records could not be written to the file: filespec.

Explanation: The server detects an error while trying to close the accounting file.

System Action: Server processing continues.

User Response: Ensure that sufficient disk space is available and that the accounting file is not marked as read-only.

ANR9902W (AS/400)Attention -- Cannot close accounting file: filespec. Records not written to file.

Explanation: ADSM detects an error while trying to close the accounting file.

System Action: Server processing continues.

User Response: Ensure that sufficient disk space is available and that the accounting file is not marked as read-only.

ANR9902W (HP-UX)Attention -- Accounting records could not be written to the file: file name.

Explanation: The server detects an error while trying to close the accounting file.

System Action: Server processing continues.

User Response: Ensure that there is sufficient disk space and that the accounting file is not marked as read-only.

ANR9902W (Solaris)Attention -- Accounting records could not be written to the file: file name.

Explanation: The server detects an error while trying to close the accounting file.

System Action: Server processing continues.

User Response: Ensure that there is sufficient disk space and that the accounting file is not marked as read-only.

ANR9902W (Windows NT)Attention -- Accounting records could not be written to the file: filespec.

Explanation: The server detects an error while trying to close the accounting file.

System Action: Server processing continues.

User Response: Ensure that there is sufficient disk space and that the accounting file is not marked as read-only.

ANR9950W (AS/400)Attention -- License option could not be written to the file: filespec.

Explanation: ADSM detects an error while trying to write to the options file.

System Action: Server processing continues.

User Response: Ensure that sufficient disk space is available and that the options file is not marked as read-only.

ANR9950W (S/390)Attention -- License option could not be written to the file: filespec.

Explanation: The server detects an error while trying to write to the options file.

System Action: Server processing continues.

User Response: Ensure that sufficient disk space is available and that the options file is not marked as read-only.

ANR9950W (Windows NT)Attention -- License option could not be written to the file: filespec.

Explanation: The server detects an error while trying to write to the options file.

System Action: Server processing continues.

User Response: Ensure that there is sufficient disk space and that the options file is not marked as read-only.

ANR9951W (S/390)Attention -- License option could not be written to the file: filespec.

Explanation: The server detects an error while trying to write to the options file.

System Action: Server processing continues.

User Response: Ensure that sufficient disk space is available and that the options file is not marked as read-only.

ANR9951W (Windows NT)Attention -- License option could not be written to the file: filespec.

Explanation: The server detects an error while trying to close the options file.

System Action: Server processing continues.

User Response: Ensure that there is sufficient disk space and that the options file is not marked as read-only.

ANR9952E (AS/400)Command: Invalid value specified for licensed storage capacity - value.

Explanation: The specified command has been issued with an invalid value.

System Action: Server operation continues, but the command is not processed.

User Response: Issue the command and specify a valid value.

ANR9952E (S/390)Command: Invalid value specified for licensed storage capacity - value.

Explanation: The specified command has been issued with an invalid value.

System Action: Server operation continues, but the command is not processed.

User Response: Reissue the command using a valid value.

ANR9952E (Windows NT)Command: Invalid value specified for licensed storage capacity - value.

Explanation: The specified command has been issued with an invalid value.

System Action: Server operation continues, but the command is not processed.

User Response: Issue the command using a valid value.

ANR9953E (AS/400)Command: Invalid value specified for number of licensed clients - value.

Explanation: The specified command has been issued with an invalid value.

System Action: Server operation continues, but the command is not processed.

User Response: Issue the command and specify a valid value.

ANR9953E (S/390)Command: Invalid value specified for number of licensed clients - value.

Explanation: The specified command has been issued with an invalid value.

System Action: Server operation continues, but the command is not processed.

User Response: Reissue the command using a valid value.

ANR9953E (Windows NT)Command: Invalid value specified for number of licensed clients - value.

Explanation: The specified command has been issued with an invalid value.

System Action: Server operation continues, but the command is not processed.

User Response: Issue the command using a valid value.

ANR9954E (AS/400)REGISTER LICENSE is not a valid command for this release.

Explanation: The REGISTER LICENSE command does not apply to the V3R1 operating system.

System Action: Server operation continues, but the command is not processed.

User Response: Add additional licenses by using the ADDLICKEY command.

ANR9954S (S/390)The server is not licensed for use on this system.

Explanation: DFSMS/MVS Feature server is not defined as licensed for this system to use in SYS1.PARMLIB member IGDDFPKG.

System Action: The server operation ends.

User Response: If you are licensed to use the server, update the IGDDFPKG member in SYS1.PARMLIB to set the correct value that enables the server. Either start task DFSMSPKG or reIPL.

ANR9955I (AS/400)An EVALUATION LICENSE for number of clients clients will expire on expiration date.

Explanation: The ADSM/400 Server is distributed with an evaluation license for client node connections. If no formal license is found for server and the evaluation period has not lapsed, this message is displayed each time the server checks the server license terms.

System Action: The number of client connections specified are used to determine if the server is in compliance with license terms.

User Response: If you are interested in using the ADSM server, please contact your service representative to obtain formal licenses for the server before the evaluation period has elapsed. Without formal licenses, clients cannot back up or archive files, and new clients cannot be defined after the expiration date shown.

ANR9955W (Windows NT)Unable to load dynamic link library dynamic link library.

Explanation: The server module is unable to load the indicated dynamic link library.

System Action: Server operation continues, but the function that requires the dynamic link library will be inoperative.

User Response: Ensure that the dynamic link library directories are accessible. If this is an evaluation copy of the server, then this message is normal for the DSMREG library, since the library is only provided with purchased NT servers. The server licensing will assume "Try and Buy" mode with sample licensed options for a period of time.

ANR9956I (AS/400)An EVALUATION LICENSE has expired.

Explanation: The ADSM/400 Server is distributed with an evaluation license. The evaluation license has expired.

System Action: Server continues with the default license terms.

User Response: If you are interested in using the ADSM server, please contact your service representative to obtain formal licenses. Without formal licenses, clients cannot back up or archive files, and new clients cannot be defined after the expiration date shown.

ANR9956E (Windows NT)Unable to load procedure address from dynamic link library dynamic link library.

Explanation: The server module is unable to load the address of a routine in the indicated dynamic link library.

System Action: Server operation continues, but the function that requires the dynamic link library will be inoperative.

User Response: Ensure that the dynamic link library directories are accessible. If the problem persists, contact you service representative.

ANR9957E (AS/400)License object validation failed.

Explanation: License object failed the validation.

System Action: Server operation continues.

User Response: Contact your service representative if you have valid formal licenses.

ANR9957W (Windows NT)One or more EVALUATION LICENSES will expire on expiration date.

Explanation: Although you are running with a purchased version of the server, there are one or more licenses registered that will expire on the date specified. This i usually the case when you have been using evaluation licenses prior to purchasing the server for NT.

System Action: Server operation continues.

User Response: Halt the server and erase the nodelock file in the server startup directory. After restarting the server, use the REGISTER LICENSE command to define the licensed features that you have purchased with your NT server. These licenses should NOT have an expiration date, so this message should not appear after re-registering the proper licenses. If this message persists, contact your service representative.

ANR9958I (AS/400)An EVALUATION LICENSE for all device features will expire on expiration date.

Explanation: The ADSM/400 Server is distributed with an evaluation license for device support modules. If no formal license is found for server and the evaluation period has not lapsed, this message is displayed each time the server checks the server license terms.

System Action: The device support module specified is used to determine if the server is in compliance with license terms with respect to the devices in use by the server.

User Response: If you are interested in using the ADSM server, please contact your service representative to obtain formal licenses for the server before the evaluation period has elapsed. Without formal licenses, certain devices will not be accessible by the ADSM server after the expiration date shown.

ANR9958W (Windows NT)Node entry node name was removed from this server's definition in Active Directory.

Explanation: In response to a REMOVE NODE command, the requested backup-archive node has been removed from this server's definition in Active Directory.

System Action: None.

User Response: None.

ANR9959I (AS/400)An EVALUATION LICENSE for support of space managed clients will expire on expiration date.

Explanation: The ADSM/400 Server is distributed with an evaluation license for space management client support. If no formal license is found for server and the evaluation period has not lapsed, this message is displayed each time the server checks the server license terms.

System Action: The server space-managed client support license allows clients to utilize the server for storing files migrated during space management. The server checks the license when files are migrated to the server from client nodes to ensure that the server is licensed to perform this function.

User Response: If you are interested in using the ADSM server, please contact your service representative to obtain formal licenses for the server before the evaluation period has elapsed. Without formal licenses, the server will not support space managed clients after the expiration date shown.

ANR9959W (Windows NT)Node entry node name was not removed from this server's definition in Active Directory.

Explanation: In response to a REMOVE NODE command, the requested backup-archive node has not been removed from this server's definition in Active Directory.

System Action: None.

User Response: To remove a node entry in the Active Directory, the option "adunregister" has to be set to "yes" in the server options file. A domain controller must also be available. The Active Directory Configuration wizard can be used to manually update the server definition.

ANR9960E (AS/400)License registration is not supported on this server.

Explanation: The REGISTER LICENSE command fails because the license authorization is not found.

System Action: Server operation continues, but the command is not processed. Licensing terms are not changed by the command.

User Response: The license authorization file is required for formal licensing for the server. If you have purchased the ADSM server, contact your service representative for assistance in resolving this problem.

ANR9960W (Windows NT)Node entry node name has been added to this server's definition in Active Directory.

Explanation: The requested backup-archive node entry has been added to this server's definition in Active Directory in response to a REGISTER NODE command.

System Action: None.

User Response: None.

ANR9961W (Windows NT)Node entry node name has not been added to this server's definition in Active Directory.

Explanation: The requested backup-archive node entry has not been added to this server's definition in Active Directory in response to a REGISTER NODE command.

System Action: None.

User Response: To register a node entry in the Active Directory, the option "adregister" has to be set to "yes" in the server options file. A domain controller must also be available. The Active Directory Configuration wizard can be used to manually update the server definition.

ANR9962W (Windows NT)Node entry node name was renamed in this server's definition in Active Directory.

Explanation: In response to a RENAME NODE command, the requested backup-archive node has been renamed to the new name shown.

System Action: None.

User Response: None.

ANR9963W (Windows NT)Node entry node name was not renamed in this server's definition in Active Directory.

Explanation: In response to a RENAME NODE command, the requested backup-archive node has not been renamed.

System Action: None.

User Response: To Rename Node in the Active Directory, the options "adregister" and "adunregister" have to be set to "yes" in the server options file. A domain controller must also be available. The Active Directory Configuration wizard can be used to manually update the server definition.

ANR9964W (Windows NT)Failed to access Active Directory. RC: return code

Explanation: Could not communicate with an Active Directory server.

System Action: Server operation continues.

User Response: Try using the option "adsetdc" in the server options file to explicitly provide the TCP/IP address of the domain controller where Active Directory is located.

ANR9965W (Windows NT)Could not create the inital node list in Active Directory for this server.

Explanation: At startup the server's registered nodes could not be added to the server definition in Active Directory

System Action: Server operation continues.

User Response: Try using the option "adsetdc" in the server options file to explicitly provide the TCP/IP address of the domain controller where Active Directory is located.

ANR9966I (Windows NT)NodeName node name.

Explanation: The NodeName is registered in Active Directory.

System Action: Server operation continues.

User Response: None.

ANR9967I (Windows NT)Server server name was defined in Active Directory.

Explanation: The server is registered in Active Directory.

System Action: None.

User Response: None.

ANR9968I (Windows NT)Success accessing Active Directory.

Explanation: Active Directory Server could be contacted.

System Action:

User Response: None.

ANR9999D(component)(code):(text)

Explanation: This message carries diagnostic text relating to a server process or algorithm. This information is intended for reporting processing exceptions and other non-standard situations that occur on the ADSM server. The (component), (code), and (text) will vary depending upon the cause of the message and the server process or algorithm that issues the message.

System Action: Server processing may or may not continue depending upon the cause of this message.

User Response: Examine error messages that may have been displayed before and/or after this message and correct any problems, if possible. If the cause of this message can not be determined or resolved, contact your support representative. If you contact your support representative, the entire text of this message should be reported.


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