IGD301I DATA SET ALLOCATION REQUEST FAILED - DATA SET dsname IS NOT ELIGIBLE FOR ALLOCATION ON SMS-MANAGED VOLUME volser
Explanation
You specified an SMS-managed volume, but the system was unable to derive a storage class for your data set. A storage class must be specified to allocate a data set on an SMS-managed volume.
Possible
causes for this include:
- The data set is a type that cannot be SMS-managed.
- The storage class ACS routine over-rode the storage class that you specified.
- A logic error in the storage class ACS routine prevented it from assigning a storage class to your data set.
In the message text:
- volser
- The volume serial number.
- dsname
- The data set name.
System action
The allocation fails.
Programmer response
If the data set does not need to be SMS-managed, specify a non-SMS managed volume and resubmit the allocation request.
If the data set is to be SMS-managed, either modify the data set type so that the data set can be managed by by SMS, or determine an appropriate storage class and resubmit the allocation request. If the storage class selection routine should have selected a storage class for this data set allocation, it may need to be corrected. Contact your storage administrator for assistance.
If the data set is not eligible
to be SMS-managed, specify a non-SMS managed volume, do not code STORCLAS
and resubmit the allocation request. Not all data sets can be
SMS-managed. The following data sets do NOT qualify:
- Unmovable data sets
- Data sets with absolute track allocations
- Tape data sets, except tape data sets on mountable volumes contained in an automated tape library (ATL) dataserver.
The operating system no longer supports the following
types of request for any volume:
- ISAM (indexed sequential) data sets. See z/OS DFSMS Using Data Sets for conversion information.
- CVOLs. Use an ICF catalog instead. See z/OS DFSMS Managing Catalogs.
Source
DFSMSdfp
Routing code
2
Descriptor code
4