Possible reasons for volume selection failure

During the process of volume selection, volumes can be rejected for any one of many different reasons. Possible reasons for rejection include:

The volume is not online to MVS.
The SMS volume or storage group status is DISNEW, DISALL, or NOTCON.
The volume was not initialized as being SMS-managed.
The volume resides in a copy pool backup storage group.
The volume does not contain enough space to satisfy the primary space requested (this is determined by DADSM).
The volume control data sets (VTOC) does not contain enough space to accommodate the format 1 DSCB for the allocation request, as determined by DADSM.
The volume was selected and DADSM returned an unsuccessful return/reason code for the allocation request. When DADSM fails to allocate the data set on a volume due to insufficient space on the volume, SMS tries to allocate the data set on a different volume. Other failures in DADSM can result in allocation failures.
The volume does not meet the availability requirement specified in the storage class.
The volume does not support concurrent copy, SnapShot, or FlashCopy® and the storage class specifies accessibility continuous (Required).
The DASD controller does not support extended format and the data class specifies 'If EXT=R.'
The volume is mountable DASD when an IART of zero or blank was specified in the storage class.
The volume was listed on the provided exclude list or was not listed in the provided include list during the DFSMSdss COPY or RESTORE operations.
The volume has an incorrect unit control block (UCB) type.
The volume was not specified for a specific guaranteed space request.
The volume belongs to a storage group and the storage group does not contain enough volumes to satisfy the volume count of a guaranteed space request. All volumes in the storage group are rejected.
The volume is too fragmented to contain the primary space extent.
During extend (EOV) processing, volume selection rejects volumes whose device types do not match the device type of the volume that the data set currently resides on.
The controller was IMLed while online to MVS. This can result in the MVS device control blocks not reflecting the current state of the volume. The device or devices should be varied offline and back online to update the MVS control block status. SMS can reject the device because of incorrect MVS status. ISMF reports the correct status because ISMF queries the device/controller directly. To not affect I/O performance, SMS uses the status in the MVS device control blocks for all volumes in a storage group.
The volume is not assigned to any of the storage groups selected by the storage group ACS routine. This results in the volume not being included on the candidate volume list, which has the same effect as the volume being rejected.

Note: During the volume selection process, many volumes can be rejected because they do not possess the right attributes. With few exceptions, volume selection fails only after allocation has been attempted without success on each of the remaining volumes.