The DFSMShsm ADDVOL command adds new non-SMS-managed volumes to
the list of volumes that DFSMShsm manages or owns and defines the
attributes of those volumes. You must issue the ADDVOL command for
each non-SMS-managed volume that you want DFSMShsm to manage or own,
including those volumes defined for aggregate recovery with the DEFINE
ARPOOL command. In addition, the initialization procedure for DFSMShsm
must issue an ADDVOL command for each primary and migration level
1 volume each time you start DFSMShsm.
Attention: Do not issue simultaneous ADDVOL commands for backup volumes
from multiple systems because this may, in rare cases, create duplicate
BVR entries in DFSMShsm control data sets records.
Use the ADDVOL command for the following purposes:
Note: - In a JES3 environment, you cannot add a primary volume to DFSMShsm
after initialization.
- If you try to issue an ADDVOL command for an SMS-managed volume,
a volume whose management cannot be determined, or for a volume that
is not online, the ADDVOL command is rejected.
- The ADDVOL command must be issued on each system
in the DFSMShsm plex where this volume is to be used.
You can change attributes within each volume category, but you
cannot change the volume category. Volume categories are:
- PRIMARY
- BACKUP(DAILY)
- BACKUP(SPILL)
- MIGRATIONLEVEL1
- MIGRATIONLEVEL2
- DUMP
For example, if a volume has been added to DFSMShsm as a primary
volume, you cannot use the ADDVOL command to change it to a migration
or backup volume.
You can change any of the following space management techniques
to be used for a primary volume:
- Migrate
- Delete-by-age
- Delete-if-backed-up
Use caution when you change the attributes of a primary volume
if the volume is using migration as the space management technique.
If you change the primary volume attributes so that no volume has
the same attributes that existed when DFSMShsm first migrated the
data set from the primary volume, an undirected recall may fail. The
undirected recall
will fail if
all of the following are true:
- You are using the LIKE subparameter of the SETSYS RECALL PRIVATEVOLUME
or ANYSTORAGEVOLUME command.
- No available volume has a space management technique of MIGRATE
and a recall technique of AUTORECALL.
- Pools are not defined.
To avoid the problem, you can specify the following UNLIKE subparameters
of the SETSYS RECALL command to allow the recall to occur when the
attributes do not match:
- AUTOMIGRATION
- AUTOBACKUP
- NOAUTOMIGRATION
- NOAUTOBACKUP
- BACKUPDEVICECATEGORY