End of support This version of the product has reached end of support. The documentation is available for your convenience. However, you must be logged in to access it. You will not be able to leave comments.

AUTOADDV function—Add volume to storage group

The AUTOADDV function is used to select a candidate volume and a skeleton JCL member to be used when adding a volume to a storage group.

Skeleton JCL is used to reinitialize the candidate volume to a new target volser value appropriate for the storage group. For more information, see Adding-a-volume-to-a-storage-group.

The AUTOADDV function runs device addresses (volumes) from the candidate pool one at a time through the FLST/RLST statements. The first device that matches an RLST SET statement is added to the requested storage group. If all devices are run through FLST/RLST and no match is produced, the request fails and a volume is not added to the group. The LAST_VOL keyword can be used to ensure that a volume is selected before the request is failed. See an example of the LAST_VOL usage in AUTOADDV-filter-and-rule-list-parameters.

Candidate volumes can be selected based on device geometry, device vendor, RAID device type, and other volume characteristics. For a list of filter parameters, see AUTOADDV-filter-and-rule-list-parameters.

A skeleton JCL member is used to initialize the candidate device. The JCL can contain any number of job steps that are necessary to initialize the device in your environment. For more information, see Adding-a-volume-to-a-storage-group.

If you are using the ICKDSF utility to initialize the candidate volume, you might consider specifying the VERIFY keyword with the &CANDVOL variable and a PARM of NOREPLYU to avoid operator intervention. This requirement is discussed in Adding-a-volume-to-a-storage-group. You can see an example in the SRMJOB09 and SRMJOB10 sample BBSLIB members.

For more information, see:

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*