Explanation
An ADDVOL command has been processed for the type
of volume volser specified in the message. If the
volume record is successfully created or updated, the return code
will be zero.
The values for
return-code are:
- Retcode
- Meaning
- 0
- Volume added or updated successfully.
- 2
- Tape migration level 2 volume already exists with valid data on
it.
- 4
- Volume entry not found for the backup cycle volume record (BVR)
update.
- 8
- Error in reading the BVR record.
- 11
- Error in writing the BVR record during internal ADDVOL command
processing of a tape volume during recycle.
- 12
- Error in writing the BVR record.
- 16
- BVR record in use by another processor.
- 20
- Invalid days have been specified for data set deletion. The day
must be between 0 and 999 inclusive.
- 22
- Invalid days have been specified on the MIGRATE subparameter.
The only valid values are 0-999.
- 25
- A read or write error has occurred for the BVR or backup control
data set backup volume record (MCT) during internal processing of
an ADDVOL command and type change of a tape volume (for example, unassigned
to SPILL). The error and record type are defined in a preceding ARC0184I
message.
- 28
- There has been a read or write error on a migration control data
set volume record (MCV) or MCT record. See message ARC0184I for details.
- 30
- The specified density is not supported by the specified unit name.
- 31
- A nonempty CAPACITYMODE(EXTENDED) ML2 or backup tape cannot be
re-ADDVOLed to a unit that is not capable of reading the tape. To
be capable of reading in CAPACITYMODE(EXTENDED), the unit must be
an esoteric and contain only CAPACITYMODE switchable drives.
- 32
- Invalid density specified. Valid for dump volumes only, density
must be 2, 3, or 4.
Note: The DENSITY parameter is no longer supported
for tape backup or ML2 volumes. However, the DENSITY parameter is
still supported for dump volumes and for existing volumes already
defined to DFSMShsm.
- 36
- The MCV, MCT or dump volume record (DVL) is not found when read.
Whichever record is being searched for, the other types are read to
make sure the volume has not already been defined as another type
of record than specified on the ADDVOL command. When reading another
type of record, an error occurs in the read.
- 37
- There has been an error writing a new DVL record or reading or
updating an existing DVL record. See message ARC0184I for details
on the particular record that has caused the error.
- 38
- An attempt has been made to add a primary volume by using the
ADDVOL command. The addition is not made because the ADDVOL command
has specified more than 5 dump classes or 1 dump class has been specified
more than once. Five dump classes are the maximum that can be specified
in the ADDVOL of a primary volume and a given class can be specified
only once.
- 39
- There has been an error reading an existing DCL record. While
adding a primary or dump volume with the ADDVOL command, the dump
class records associated with the volume are read to confirm that
the classes exist and are not disabled. See message ARC0184I for details
on the particular record that caused the error.
- 40
- For a primary volume, the high threshold has been given, but no
low threshold has been specified. Specify either the high threshold
and low threshold or neither.
- 41
- The track-managed threshold (TRACKMANAGEDTHRESHOLD) optional keyword
has been specified either for a BACKUP or DUMP or MIGRATION volume
or for PRIMARY volume that has less than 65520 cylinders (a non-Extended
Address Volume). Specify the track-managed threshold optional keyword
only for primary Extended Address Volumes.
- 44
- The creation of the tape table of contents record (TTOC) has failed.
- 46
- An internal ADDVOL command for a tape backup volume has failed
because the volume already contains valid DFSMShsm data.
- 48
- The deletion of the TTOC record has failed.
- 52
- The read for update of the MCT record has failed.
- 56
- Internal error in module ARCCPADV.
- 58
- DRAIN and NODRAIN parameters are valid only for DASD migration
volumes.
- 61
- An internal ADDVOL command has failed. See reason-code for
additional information.
- 70
- The dump volume has not been added because it is currently in
use.
- 72
- A specified dump class has been disabled as the result of a DEFINE
DUMPCLASS DISABLE command. No further dumps are processed to this
class and no dump volumes can be added to this class with the ADDVOL
command. During the process of adding a primary volume with the ADDVOL
command, if the AUTODUMP(class,...) parameter has
not been specified, the MCV record is checked for dump classes specified
on a previous ADDVOL command. If DUMPCLASS(class)
has not been specified while adding a dump volume with the ADDVOL
command, then the DVL record is checked for the dump class specified
on a previous volume added with the ADDVOL command. If a dump class
specified while adding a previous volume with the ADDVOL command is
now disabled, this return code is issued and the ADDVOL command fails.
- 80
- The volume is SMS managed or is in SMS-managed initial status.
SMS-managed volumes cannot be explicitly added to DFSMShsm, but are only added
internally by DFSMShsm when
needed.
- 82
- An error has occurred on OBTAIN while determining if the volume
is SMS managed.
- 98
- Internal ADDVOL command has failed. The number of tape volumes
allocated under the current allocation exceeds the limit of 254 volumes.
The following reason codes
reason-code apply
only to return codes 44, 48, and 52:
- 4
- The deletion of the BVR record has also failed. An error in reading
the BVR record has caused the failure of the BVR record deletion.
- 8
- The deletion of the BVR record has also failed. An error in writing
the BVR record has caused the failure of the BVR record deletion.
- 12
- The deletion of the BVR record has also failed. The BVR record
has been in use by another processor causing the failure of the BVR
record deletion.
The following reason codes apply only to return
code 61:
- 4
- Error in creating the MCV record.
- 8
- Error in deleting the MCV record.
- 12
- Error in reading the MCV record.
- 16
- Error in writing the MCV record.
- 20
- Error in creating the MCT record.
- 22
- Error in creating the DVL record.
- 24
- Error in deleting the MCT record.
- 26
- Error in deleting the DVL record.
- 28
- Error in reading the MCT record.
- 30
- Error in reading the DVL record.
- 32
- Error in writing the MCT record.
- 34
- Error in updating the DVL record.
- 36
- Error in creating the TTOC record.
- 38
- Error in reading a dump class record (DCL).
- 40
- Error in reading the TTOC record.
- 44
- Error in writing the TTOC record.
- 48
- Error in changing the key of a TTOC record.
- 52
- Error in deleting a BVR volume entry.
- 56
- Error in creating a BVR volume entry.
- 60
- Error in updating a BVR volume entry.
- 64
- Tape volume contains valid DFSMShsm data. The file sequence number
in the MCV or MCT record is nonzero.
- 68
- The tape volume is RACF-protected, but does not appear in DFSMShsm’s RACF® tape volume set. Also, the
tape volume is not in DFSMShsm’s inventory of backup or
migration volumes.
- 72
- The tape volume is RACF-protected, but does not appear in DFSMShsm’s RACF tape volume set. Also, the
tape volume has been in DFSMShsm’s inventory of backup or
migration volumes. The DFSMShsm control data set record (MCV or
MCT) indicates the tape volume is empty (the file sequence number
is zero). The tape volume is being removed from DFSMShsm’s inventory of
backup or migration volumes. For additional information, see the explanation
of message ARC0357I.
- 76
- The tape volume is RACF-protected, but does not appear in DFSMShsm’s RACF tape volume set. Also, the
tape volume is in DFSMShsm’s
inventory of backup or migration volumes. The DFSMShsm control data set record
(MCV or MCT) indicates the tape volume is not empty (the file sequence
number is nonzero). The tape volume is being marked full in the necessary
control data set records to prevent its further use by DFSMShsm.
For additional information, see the explanation of message ARC0360I.
- 80
- An error has occurred when DFSMShsm attempted to add the tape volume
to its RACF tape volume set
named either HSMHSM or DFHSMx.
- 84
- An error has occurred when DFSMShsm attempted to delete the tape volume
from its RACF tape volume set
named either HSMHSM or DFHSMx.
- 97
- Internal error in module ARCTEOV.
- 108
- Error in reading the previous volume’s MCV record.
The following reason codes apply only to return
code 82 and are the return codes from the OBTAIN:
- 4
- Volume is not mounted.
- 12
- An I/O error or invalid volume VTOC entry.
- 16
- Invalid work area pointer.
System action
ADDVOL processing ends if the return code is
not 0. DFSMShsm processing
continues.
System programmer response
Programmer response
Notify the storage administrator or system
programmer for return codes 4, 8, 11, 12, 16, 25, 28, 36, 37, 39,
44, 48, 52, or 61.
- For return code 20, reissue the ADDVOL command with a DELETEBYAGE(days)
parameter between 0 and 999 inclusive.
- For return code 22, reissue the ADDVOL command with the MIGRATE(days)
subparameter, with a day value between 0 and 999 inclusive.
- For return codes 30 and 32, reissue the ADDVOL command, specifying
the correct tape density. Specify a tape density of 2, 3, or 4 only
for valid dump volumes.
- For return code 38, reissue the ADDVOL command with no more than
5 dump classes specified.
- For return code 40, reissue the ADDVOL command specifying both
high thresholds and low thresholds or neither.
- For return code 41, reissue the ADDVOL command without
the optional TRACKMANAGEDTHRESHOLD keyword.
- For return code 56, search problem reporting databases for a fix
for the problem. If no fix exists, contact the IBM® Support Center.
- For return code 72, reissue the ADDVOL command with a dump class
that has not been disabled. If the dump class is needed again, use
the DEFINE command to redefine it. After the dump class is redefined,
reissue the ADDVOL command.
- For return code 80, remove the ADDVOL command from the startup
member if the command is being issued during startup.
- For return code 82, determine the cause of the error from the
reason code, correct the problem, and reenter the ADDVOL command.