ADSM V3R1 Messages

Chapter 17. Disaster Recovery Manager (6500-7000)

ANR6600E command: 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.

ANR6601E command: 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.

ANR6602E command: 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.

ANR6603E command: 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.

ANR6604E command: 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.

ANR6605E command: 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.

ANR6606E command: 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.

ANR6607E command: 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.

ANR6608E command: A machine containing an ADSM 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 an ADSM 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.

ANR6609I Machine machine name defined.
Explanation: A DEFINE MACHINE command has added the requested machine to the server.
System Action: None.
User Response: None.

ANR6610E command: 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.

ANR6611E command: 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.

ANR6612I Machine machine name updated.
Explanation: An UPDATE MACHINE command has updated one or more attributes of a machine.
System Action: None.
User Response: None.

ANR6613I Machine machine name deleted.
Explanation: A DELETE MACHINE command has deleted the requested machine from the server.
System Action: None.
User Response: None.

ANR6614E command: 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.

ANR6615E command: 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 ADSM server.

ANR6616E command: 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.

ANR6617W command: 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.

ANR6618E command: 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.

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

ANR6620E command: 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.

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

ANR6622E command: 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.

ANR6623W command: 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.

ANR6624E command: 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.

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

ANR6626E command: 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.

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

ANR6628E command: 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.

ANR6629E command: 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.

ANR6630E command: 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.

ANR6631E command: 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.

ANR6632I Recovery media recovery media name defined.
Explanation: A DEFINE RECOVERYMEDIA command has defined the recovery media to the server.
System Action: None.
User Response: None.

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

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

ANR6635E command: 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.

ANR6636E command: 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.

ANR6637E command: 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.

ANR6638E command: 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.

ANR6639E command: 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.

ANR6640E command: 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.

ANR6641E command: 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.

ANR6642E command: 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.

ANR6643E command: 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.

ANR6644E command: 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.

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

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

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

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

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

ANR6650I audit 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. �

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

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

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

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

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

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

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

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

ANR6659I audit command: Invalid ADSM server value encountered for machine machine name.
Explanation: A database audit process encounters an invalid ADSM server value for the machine indicated.
System Action: Audit processing continues.
User Response: Issue the command again and specify FIX=YES to correct the ADSM server value. Or, issue an UPDATE MACHINE command and specify a new ADSM server value.

ANR6660I audit command: Invalid ADSM server value encountered for machine machine name - the default value will be set.
Explanation: A database audit process encounters an invalid ADSM server value for the machine indicated. Because FIX=YES has been specified, the audit function sets the machine ADSM 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.

ANR6661I audit command: Multiple machines are indicated as ADSM servers. Only one machine should have the ADSM server indicator set to YES.
Explanation: A database audit process encounters more than one machine with the ADSM server indicator set to YES.
System Action: Audit processing continues.
User Response: For a list of machines with the ADSM server indicator set to YES, issue a QUERY MACHINE ADSMSERVER=YES command. Issue an UPDATE MACHINE command for each machine that is not an ADSM server.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

ANR6683I command: 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.

ANR6684I command: Volume volume name was deleted.
Explanation: The MOVE DRMEDIA * WHERESTATE=COURIERRETRIEVE command displays the message. Volume volume name is deleted from the ADSM 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 ADSM database.
User Response: Issue the CHECKIN LIBVOLUME command for each volume returned onsite if the volume is reused by ADSM.

ANR6685E command: 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.

ANR6686E command: 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.

ANR6690E command: 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.

ANR6691E command: 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.

ANR6694E command: 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.

ANR6695E command: 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.

ANR6696I command: 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.

ANR6697I command: 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.

ANR6698E command: 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.

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

ANR6700I command command completed successfully.
Explanation: The indicated command completed successfully.
System Action: None.
User Response: None.

ANR6701E command: 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.

ANR6702E command: Invalid DB backup series expiration period - days value.
Explanation: The indicated command has been entered that specifies an invalid days value for expiring the database backup series.
System Action: The server does not process the command.
User Response: Reissue the command with a valid days value for expiring the database backup series.

ANR6703E command: 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.

ANR6704E command: 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.

ANR6705E command: 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.

ANR6706E command: 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

ANR6733E command: 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".

ANR6734E command: 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

ANR6749I command: 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.

ANR6750E Disaster 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. Clients can perform any action except backup, archive, space-managed file migration, or disaster recovery manager DEFINE MACHINE, DEFINE RECOVERYMEDIA, PREPARE or MOVE DRMMEDIA commands.
User Response: Issue a QUERY LICENSE command to determine which license terms are not in compliance.

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

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

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

ANR6754I Machine machine name characteristics deleted.
Explanation: A DELETE MACHINE command has deleted the requested characteristics from the server.
System Action: None.
User Response: None.

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

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

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

ANR6758E command: 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.

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

ANR6760E command: Executable command line exceeds maximum length characters for volume volume name.
Explanation: While writing to a command file, one of the following conditions occurred:

The length of the command specified with the CMD parameter exceeds the maximum length of allowable characters (255).
The length of the command line written to the command file exceeds the LRECL specified for MVS or exceeds the default length for the command line written (255).
The length of the command created after replacing the substitution variables &VOL, &VOLDSN, &NL, and &LOC exceeds the ADSM allowable command line length (1500).

System Action: The server stops processing the command.
User Response: Issue the command again and specify a valid executable command with the CMD parameter.

If this message is issued by a MOVE or QUERY DRMEDIA command and the volume record has been deleted from the ADSM 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.

ANR6761E command: 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.

ANR6762E command: 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.

ANR6763I command: 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.

ANR6764E command: 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.

ANR6765E command: 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.

ANR6766E command: 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.

ANR6767E command: 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.

ANR6768E command: 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.

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

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

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

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

ANR6773E command: 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.

ANR6774E command: 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.

ANR6775E command: 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.

ANR6776E command: 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.

ANR6777E command: 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 ADSM in the following order:

The file name specified on the indicated command.
The file name specified on the SET command.
The file name generated by ADSM (AIX only).

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.

ANR6778E command: 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.

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

ANR6900I command: The recovery plan file file name was created.
Explanation: The recovery plan file was created.
System Action: None.
User Response: None.

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

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

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

ANR6912W command: The database was not backed up.
Explanation: No backups have been made of the ADSM data base.
System Action: Stanzas in the recovery plan do not include database recovery information.
User Response: Backup the ADSM server data base by issuing the BACKUP DB command.

ANR6913W command: 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.

ANR6915W command: Storage pool storage pool name storage pool type is not defined to the ADSM server.
Explanation: A storage pool that is not defined to the ADSM 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 ADSM server.

ANR6916W command: No copy storage pools are defined.
Explanation: The ADSM 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 ADSM server.

ANR6918W command: 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.

ANR6920W command: Generated replacement volume name volume name is not valid for ADSM 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 ADSM 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 ADSM Administrator's Reference for your particular platform.

ANR6921W command: Cannot locate server options file 'file name'.
Explanation: The Prepare command cannot open the specified ADSM Server options file.
System Action: VOLHISTORY and DEVCONFIG options are added to the recovery plan file stanza DSMSERV.OPT.FILE.
User Response: None.

ANR6922W command: No machine information was defined for the machine that contains ADSM server server name.
Explanation: The machine information has not been saved in the ADSM 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 ADSM data base and reissue the PREPARE command.

ANR6923W command: 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 ADSM Administrator's Reference for your particular platform.

ANR6924W command: 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 ADSM Administrator's Reference for your particular platform.

ANR6925W command: 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 ADSM Administrator's Reference for your particular platform.

ANR6926W command: There is at least one invalid generated volume name associated with storage pool storage pool ADSM 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 ADSM 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 ADSM Administrator's Reference for your particular platform.

ANR6950E command: 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.

ANR6951E command: 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.

ANR6952E command: 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.

ANR6953E command: 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.

ANR6954E command: 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.

ANR6959E command: 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.

ANR6960E command: 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.

ANR6962E command: Query database failed.
Explanation: An ADSM 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.

ANR6963E command: Query log failed.
Explanation: An ADSM 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.

ANR6964E command: Query storage pool failed.
Explanation: An ADSM 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.

ANR6965E command: Query volume failed.
Explanation: An ADSM 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.

ANR6966E command: Query database volume failed.
Explanation: An ADSM 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.

ANR6967E command: Query log volume failed.
Explanation: An ADSM 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.

ANR6968E command: Query volume history failed.
Explanation: An ADSM 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.

ANR6969E command: Query device class failed.
Explanation: An ADSM 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.

ANR6970E command: 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.

ANR6971E command: 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.

ANR6972E command: Query machine failed.
Explanation: An ADSM/DRM 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.

ANR6973E command: Query recovery media failed.
Explanation: An ADSM/DRM 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.

ANR6980E command: 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.

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