ADSM V3R1 Messages

Chapter 9. Storage Services (1300-1499)



ANR1300I VARY ONLINE command initiated for disk volume volume name.
Explanation: A VARY ONLINE command has caused a vary-on process to be started for the volume specified.
System Action: The volume is varied online.
User Response: None.


ANR1301I VARY OFFLINE command initiated for disk volume volume name.
Explanation: A VARY OFFLINE command has caused a vary-off process to be started for the volume specified.
System Action: The volume is varied offline.
User Response: None.


ANR1302E Disk volume volume name is already online.
Explanation: A VARY ONLINE command specified a volume that was already online.
System Action: None.
User Response: None.


ANR1303E Disk volume volume name is already offline.
Explanation: A VARY OFFLINE command specified a volume that was already offline.
System Action: None.
User Response: None.


ANR1304E Disk volume volume name is currently in use.
Explanation: A VARY OFFLINE command specified a volume that is currently in use and cannot be varied offline at this time.
System Action: None.
User Response: Try the command again at a later time, or attempt to determine how it is currently being used and free it.


ANR1305I Disk volume volume name varied online.
Explanation: The specified volume has been varied online as the result of a VARY ONLINE command.
System Action: None.
User Response: None.


ANR1306I Disk volume volume name varied online (read-only).
Explanation: The specified volume has been varied online in read-only mode as the result of a VARY ONLINE command.
System Action: None.
User Response: None.


ANR1307I Disk volume volume name varied offline.
Explanation: The specified volume has been varied offline as the result of a VARY OFFLINE command.
System Action: None.
User Response: None.


ANR1310E Vary-on failed for disk volume volume name - insufficient memory.
Explanation: A VARY ONLINE command has been issued for the disk volume specified, but sufficient memory is not available to process the command.
System Action: The volume is not varied online.
User Response: Reissue the command at a later time, or make more memory available to the server.


ANR1311E Vary-on failed for disk volume volume name - unable to access disk device.
Explanation: A VARY ONLINE command has been issued for the disk volume specified, but the server is unable to access the disk.
System Action: The volume is not varied online.
User Response: Attempt to determine the cause of the inability to access the volume and correct the problem.


ANR1312E Vary-on failed for disk volume volume name - error reading disk.
Explanation: A VARY ONLINE command has been issued for the disk volume specified but the server encounters an error reading the disk.
System Action: The volume is not varied online.
User Response: Attempt to determine the cause of the read error and correct the problem.


ANR1313E Vary-on failed for disk volume volume name - unsupported block size (block size).
Explanation: A VARY ONLINE command has been issued for the disk volume specified, but the volume is formatted with a block size that cannot be used.
System Action: The volume is not varied online.
User Response: Reformat the disk with a block size that is an evenly divisible by 4096.


ANR1314E Vary-on failed for disk volume volume name - reduced capacity (was count blocks, now count blocks.
Explanation: A VARY ONLINE command has been issued for the disk volume specified, but the size of the volume does not match the size expected.
System Action: The volume is not varied online.
User Response: Restore the volume or otherwise correct the disk volume size, and reissue the command.


ANR1315E Vary-on failed for disk volume volume name - invalid label block.
Explanation: A VARY ONLINE command has been issued for the disk volume specified, but the label block of the volume is invalid or cannot be read.
System Action: The volume is not varied online.
User Response: Restore or reformat the disk volume.


ANR1316E Vary-on failed for disk volume volume name - internal error detected.
Explanation: A VARY ONLINE command has been issued for the disk volume specified, but fails due to an internal server error.
System Action: The volume is not varied online.
User Response: Contact your service representative.


ANR1320W Vary-on not possible for disk volume volume name - access state is "unavailable".
Explanation: A VARY ONLINE command has been issued for the disk volume specified, but the status of the volume is unavailable.
System Action: The volume is not varied online.
User Response: If necessary, use the UPDATE VOLUME command to change the status of the volume, and reissue the command.


ANR1321W Vary-on not possible for disk volume volume name - access state is "destroyed".
Explanation: A VARY ONLINE command has been issued for the disk volume specified, but the status of the volume is destroyed.
System Action: The volume is not varied online.
User Response: If necessary, use the UPDATE VOLUME command to change the status of the volume, and reissue the command.


ANR1340I Scratch volume volume name is now defined in storage pool storage pool name.
Explanation: The scratch volume specified has been added to the storage pool shown.
System Action: None.
User Response: None.


ANR1341I Scratch volume volume name has been deleted from storage pool storage pool name.
Explanation: The scratch volume specified is no longer in use and has been removed from the indicated storage pool.
System Action: None.
User Response: None.


ANR1342I Scratch volume volume name is now pending - volume will be deleted from storage pool storage pool name after the reuse delay period for this storage pool has elapsed.
Explanation: All files have been deleted from the indicated scratch volume. The volume will not be removed from the storage pool until the reuse delay time period for the indicated storage pool has elapsed.
System Action: None.
User Response: None.


ANR1343I Unable to delete scratch volume volume name.
Explanation: A scratch volume cannot be deleted from ADSM and returned to scratch at this time because all the locks have not be released. A number a retries have been attempted.
System Action: None
User Response: The scratch volume will be automatically deleted when the ADSM server is restarted. Or, you may manually delete this volume later, using the DELETE VOLUME command.


ANR1360I Output volume volume name opened (sequence number sequence number).
Explanation: During a sequential data operation, the volume specified has been opened for output as the volume number shown.
System Action: None.
User Response: None.


ANR1361I Output volume volume name closed.
Explanation: During a sequential data operation, the volume specified has been closed because the export or dump is complete.
System Action: None.
User Response: None.


ANR1362I Output volume volume name closed (full).
Explanation: During a sequential data operation, the volume specified has been closed because the volume is full.
System Action: None.
User Response: None.


ANR1363I Input volume volume name opened (sequence number sequence number).
Explanation: Because of a sequential data operation, the volume specified has been opened for input as the volume number shown.
System Action: None.
User Response: None.


ANR1364I Input volume volume name closed.
Explanation: During a sequential data operation, the volume specified has been closed because the operation is complete.
System Action: None.
User Response: None.


ANR1365I Volume volume name closed (end reached).
Explanation: During a sequential data operation, the volume specified has been closed because processing of the volume is complete.
System Action: None.
User Response: None.


ANR1366W Input volume volume name contains an invalid identifier.
Explanation: During a sequential data operation, the volume specified has been mounted but contains an invalid identifier.
System Action: The volume is not used.
User Response: Make sure you specified the correct volume for the operation.

If a LOADDB operation was being performed on MVS, the command syntax may be specified by using a ddname or by specifying a device class name. You must use the same method that was used when the data base was originally dumped. If you did not, this error message will be displayed. Try loading the data base by using the other method of syntax (ddname).


ANR1367W Import volume volume name was written by a different export process.
Explanation: During an IMPORT operation, the volume specified has been mounted but contains an export identifier that does not match the import process.
System Action: The volume is not used.
User Response: Supply a volume created by the proper export process.


ANR1368W Input volume volume name contains sequence number sequence number; volume sequence number sequence number is required.
Explanation: During a sequential data operation, the volume specified has been mounted but contains the wrong volume sequence number.
System Action: The volume is not used.
User Response: Supply the volume with the proper sequence number. The volume history file can help you choose the correct volume.


ANR1369E Input volume volume name contains Version 1 dump.
Explanation: During a sequential data operation, the volume specified has been mounted but appears to contain a version 1 data base dump.
System Action: The volume is not used. The operation is terminated.
User Response: Make sure you specified the correct volume for the operation.

A Version 1 database dump may not be loaded into a Version 2 server. The Version 1 database dump must only be loaded into a Version 1 server.


ANR1370E Insufficient number of mount points available in device class device class name.
Explanation: During IMPORT or EXPORT processing, the server cannot allocate sufficient mount points for the device class specified. The device class associated with the EXPORT or IMPORT drive only has a mount limit of one. The operation needs to read or write file data from or to the same device class because file data is being imported or exported.
System Action: The IMPORT or EXPORT command is ended and server operation continues.
User Response: Make more mount points available.


ANR1400W Mount request denied for volume volume name - mount canceled.
Explanation: The volume shown cannot be mounted because the mount request has been canceled.
System Action: The volume is not mounted.
User Response: None.


ANR1401W Mount request denied for volume volume name - mount failed.
Explanation: The volume shown cannot be mounted because the mount request cannot be completed successfully. Possible reasons include, an error in device specifications to the server or the mount request timed out.
System Action: The volume is not mounted.
User Response: If the device specifications (DEFINE DEVCLASS and so forth) are in error, correct them and reissue the command that requested the volume to be mounted.


ANR1402W Mount request denied for volume volume name - volume unavailable.
Explanation: The volume shown cannot be mounted because it is not available.
System Action: The volume is not mounted.
User Response: None.


ANR1403W Scratch volume mount request denied - mount canceled.
Explanation: A scratch volume cannot be mounted because the mount request has been canceled.
System Action: The scratch volume is not mounted.
User Response: None.


ANR1404W Scratch volume mount request denied - mount failed.
Explanation: A scratch volume cannot be mounted because the mount request cannot be completed successfully. Possible reasons include, an error in device specifications to the server or the mount request timed out.
System Action: The scratch volume is not mounted.
User Response: If the device specifications (for example, DEFINE DEVCLASS) are in error, correct them and reissue the command that requested the volume to be mounted.
System Action: The scratch volume is not mounted.
User Response: None.


ANR1405W Scratch volume mount request denied - no scratch volume available.
Explanation: A scratch volume cannot be mounted because no scratch volume is available.
System Action: The scratch volume is not mounted.
User Response: None.


ANR1409W Volume command already in use - skipped.
Explanation: During an export or database backup, a volume cannot be used because it is already defined in a storage pool, or has been previously used by an export or database backup operation (as recorded in the volume history) or is in use by another process.
System Action: The operation continues and the volume is skipped.
User Response: Use the QUERY VOLUME command to display the names of volumes that are defined to server storage pools. Use the QUERY VOLHISTORY command to display the names of volumes that have been used for export or database backup operations.


ANR1410W Access mode for volume volume name now set to "unavailable".
Explanation: The status of the volume shown has been set to unavailable.
System Action: None.
User Response: None.


ANR1411W Access mode for volume volume name now set to "read-only" due to write error.
Explanation: Because of an unrecoverable write error on the volume shown, the status of the volume has been set to read-only.
System Action: None.
User Response: None.


ANR1412W Volume volume name access mode is "unavailable".
Explanation: At server startup, the status of the indicated volume is unavailable.
System Action: None.
User Response: None.


ANR1413W Volume volume name access mode is "read-only".
Explanation: At server startup, the status of the indicated volume is read-only.
System Action: None.
User Response: None.


ANR1414W Volume volume name access mode is "read-only" due to previous write error.
Explanation: At server startup, the status of the indicated volume is read-only due to an unrecoverable write error, or because an administrator used the UPDATE VOLUME command to set the volume access mode to read-only.
System Action: None.
User Response: None.


ANR1415W Volume volume name access mode is "destroyed".
Explanation: At server startup, the status of the indicated volume is destroyed.
System Action: None.
User Response: None.


ANR1416W Volume volume name access mode is "offsite".
Explanation: At server startup, the status of the indicated volume is offsite.
System Action: None.
User Response: None.


ANR1417W Access mode for volume volume name now set to "read-only" due to excessive read error.
Explanation: Because of an numerous read errors on the volume shown, the status of the volume has been set to read-only.
System Action: None.
User Response: Use QUERY VOLUME FORMAT=DETAILED for the volume to view the access mode and number of read errors. You may want to use the MOVE DATA command to move the retrievable data from this volume to another volume. For the damaged files, use the RESTORE VOLUME command to restore a readable copy of the file to the storage pool.


ANR1420W Read access denied for volume volume name - volume access mode = "unavailable".
Explanation: An attempt to access the named volume for reading fails because the volume status is unavailable.
System Action: The volume is not used for read access.
User Response: None.


ANR1421W Read access denied for volume volume name - volume offline.
Explanation: An attempt to access the named volume for reading failed because the volume is offline.
System Action: The volume is not used.
User Response: None.


ANR1422W Read access denied for volume volume name - volume access mode = "offsite".
Explanation: An attempt to access the named volume for reading failed because the volume status is offsite.
System Action: The volume is not used for read access.
User Response: None.


ANR1423W Scratch volume volume name is empty but will not be deleted - volume access mode is "offsite".
Explanation: The named scratch volume is empty but will not be deleted at this time because the access mode is offsite.
System Action: The volume is not deleted.
User Response: After bringing the volume onsite, change the access mode to read-only so the volume will be deleted.


ANR1424W Read access denied for volume volume name - volume access mode = "destroyed".
Explanation: An attempt to access the named volume for reading failed because the volume status is destroyed.
System Action: The volume is not used for read access.
User Response: None.


ANR1430W Retrieval request denied for storage pool storage pool name - access mode = "unavailable".
Explanation: An attempt was made to retrieve a file from the storage pool shown, but the access mode of the storage pool is unavailable.
System Action: The file is not retrieved from this storage pool. If possible, the file is retrieved from another storage pool.
User Response: Consider changing the access mode for the storage pool.


ANR1431E An error occurred while writing to side A of volume volume name. An attempt will be made to write to side B of this volume.
Explanation: An error occurred while writing to side A of a two-sided volume.
System Action: No additional data will be written to side A of this volume. Any remaining space on side A will not be used. An attempt will be made to use the reverse side (side B) of the volume.
User Response: None required if the side B can be used successfully. However, the administrator should investigate the cause of the error and may want to move data from this volume.


ANR1432I Updating device configuration information to defined files.
Explanation: The server is updating device configuration information for the files or data sets specified with the DEVCONFIG option in the server options file.
System Action: Server operation continues.
User Response: None.


ANR1433I Device configuration information successfully written to file name.
Explanation: Device configuration information was successfully written to the file specified.
System Action: Server operation continues.
User Response: None.


ANR1434W No files have been identified for automatically storing device configuration information.
Explanation: The server is unable to automatically update device configuration file. No files were identified using the DEVCONFIG option in the server options file.
System Action: Server operation continues.
User Response: If you would like to have the server automatically record device configuration information to assist in server recovery, use the DEVCONFIG option in the server options file to specify where device configuration information should be written. If you update the options file, halt and then restart the server so the changes can take effect.


ANR1435E Server could not write device configuration information to devconfig file name.
Explanation: While attempting to write device configuration information to defined files, the server cannot write to the file name specified.
System Action: The server cannot write device configuration information to the specified file.
User Response: Examine error messages that may have been displayed prior to this message and correct any problems, if possible. Make sure that the server has proper authority to write to the file indicated and that there is sufficient space in the file system for the file. On MVS, make sure that the data set has been allocated and that the server has authority to write to the data set. After the problem has been corrected, use the BACKUP DEVCONFIG command to write device configuration information to the file.


ANR1436E Device configuration file devconfig file name cannot be opened.
Explanation: While attempting to write device configuration information to device configuration files, the server cannot open the file name specified.
System Action: The server does not write device configuration information to the file specified.
User Response: Examine error messages that may have been displayed prior to this message and correct any problems, if possible. Make sure that the server has proper authority to write to the file indicated and that there is sufficient space in the file system for the file. On MVS, make sure that the data set has been allocated and that the server has authority to write to the data set. After the problem has been corrected, use the BACKUP DEVCONFIG command to write device configuration information to the file.


ANR1437E No device configuration files could be used.
Explanation: The server attempts to read device configuration information from defined files and cannot open any of the files.
System Action: The operation is ended.
User Response: Examine error messages that may have been displayed prior to this message and correct any problems, if possible. Ensure that the defined device configuration files have been created. If you can start the server, you can create the files by using the BACKUP DEVCONFIG command. If you cannot start the server, you will need to create a device configuration file by editing the file and adding the appropriate DEFINE commands for the device class, drive, and library definitions. The contents and requirements for this file are described in the ADSM Administrator's Guide. Make sure that the server has proper authority to read from the defined device configuration files.


ANR1438W Skipping device configuration file: devconfig file name.
Explanation: While attempting to read device configuration information from a defined device configuration file, the server encounters problems in processing the definitions included in the file.
System Action: The specified file is skipped, and the next one specified in the server options file will be used.
User Response: Examine error messages that may have been displayed prior to this message to understand why the file could not be used. When you can start the server again, you can refresh this file by using the BACKUP DEVCONFIG command.


ANR1439E Allocate prohibited - transaction failed.
Explanation: While attempting to preallocate storage on a storage pool, the ADSM server detected that the transaction for this operation has previously failed. This error may occur when a large file is selected for backup and the client did not properly estimate the file size. There may not be enough space in the storage pool for the file.
System Action: An internal error is reported by the ADSM server and the operation being performed is ended.
User Response: Examine error messages that may have been displayed prior to this message for more information.


ANR1440I All drives in use. Process process number being preempted by higher priority operation.
Explanation: When a high priority operation attempted to find an available drive, all the drives were in use. To make a drive available for this operation, the indicated process is being cancelled by the system.
System Action: The lower priority process is cancelled to make a mount point (drive) available.
User Response: When a drive again becomes available, restart the process that was cancelled. If the process was a migration or reclamation process, it will be automatically restarted when needed. If this message appears frequently, you may want to increase the number of drives available. See the MOUNTLIMIT parameter on the UPDATE DEVCLASS command.


ANR1441I Volume volume name is in use. Process process number being preempted by higher priority operation.
Explanation: When a high priority operation attempted to use a volume, it was in use. To make a volume available for this operation, the indicated process is being canceled by the system.
System Action: The lower priority process is cancelled to the volume available.
User Response: Restart the process that was canceled. It will wait until the higher priority process is finished with the volume. If the canceled process was a migration or reclamation process, it will be automatically restarted when needed.

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