ADSM V3R1 Messages

Chapter 15. Server Sequential History Information (4500-4699)



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


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


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


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


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


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


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


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


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


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


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


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


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


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


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


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


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


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


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


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


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


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


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


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


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


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


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


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


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


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


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


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


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


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


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


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


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


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


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


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


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


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


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


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


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


ANR4612E Unable to restore database and roll forward updates - no volume history available.
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 backup series is not available. This process is possible only when no full backup is taken after setting the recovery log mode to ROLLFORWARD with a SET LOGMODE command.
System Action: The server does not process the command.
User Response: Reissue the command and specify a point in time (TODATE/TOTIME) for restore.


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


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


ANR4630I Starting 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).


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


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


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


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


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


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


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


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


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


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


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


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


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


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


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


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


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


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


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


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


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


ANR4660I Connected to SNMP subagent at adsm snmp subagent address on port port number.
Explanation: The ADSM server has successfully connected to the ADSM SNMP subagent at the indicated address and port.
System Action: The ADSM server will now register with the subagent.
User Response: None.


ANR4661E SNMP communication with the subagent failed because a thread resource was not available.
Explanation: The server could not continue with SNMP communication to the ADSM 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".


ANR4662W Failure sending message to SNMP subagent.
Explanation: The ADSM server experienced an error return code from TCP/IP while sending to 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 ADSM 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.


ANR4663W Failure receiving message from SNMP subagent.
Explanation: The ADSM 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 ADSM 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.


ANR4664W Failure in registering with SNMP subagent.
Explanation: The ADSM 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.


ANR4665W Failure re-trying registration with SNMP subagent.
Explanation: The ADSM 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.


ANR4666W Failure sending heartbeat message to SNMP subagent.
Explanation: The ADSM 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.


ANR4667W Failure re-trying heartbeat message to SNMP subagent.
Explanation: The ADSM 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.


ANR4668I Connection successfully re-established with SNMP subagent.
Explanation: The ADSM 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.


ANR4669W Heartbeat message was not accepted by SNMP subagent.
Explanation: The ADSM 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.


ANR4670W Failure in opening session with SNMP subagent.
Explanation: The ADSM 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 ADSM server.


ANR4671W SNMP subagent did not accept registration of this server.
Explanation: The ADSM 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. The stop the ADSM server and re-start it if heartbeat and message forwarding functions are required.


ANR4672W SNMP 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 ADSM 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".


ANR4673E Insufficient memory for subagent initialization. (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 additional storage to the subagent.


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


ANR4675E Server/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.


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


ANR4677I Session established with ADSM 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.


ANR4678I Session closed with ADSM 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.


ANR4679W Messages are no longer being forwarded to the SNMP subagent.
Explanation: The ADSM 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.


ANR4680I DPI subagent (the subagent name): "connected" or "reconnected", ready to receive requests.
Explanation: The ADSM subagent has successfully connected or reconnected to the SNMP agent.
System Action: The subagent is ready to receive request from ADSM servers.
User Response: None.


ANR4681W Connect to SNMP agent failed, will keep trying.
Explanation: The ADSM 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.


ANR4682W A SNMP agent connection error occurred. Attempting to re-establish connection.
Explanation: An error has occurred in the communication between the ADSM 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.


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


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


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


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


ANR4687E Server/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.


ANR4688E Server/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.


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


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


ANR4691I DPI subagent (the subagent name): connected, ready to receive requests.
Explanation: The ADSM subagent has successfully connected to the SNMP agent.
System Action: The subagent is ready to receive request from ADSM servers.
User Response: None.


ANR4692I DPI subagent (the subagent name): reconnected, ready to receive requests.
Explanation: The ADSM subagent has successfully reconnected to the SNMP agent.
System Action: The subagent is ready to receive request from ADSM servers.
User Response: None.


ANR4693I Interface Driver information will be loaded in quiet mode: Only warning and error messages will be displayed.
Explanation: The ADSM 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.

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