Previous topic |
Next topic |
Contents |
Contact z/OS |
Library |
PDF
Selecting output volumes z/OS DFSMSdss Storage Administration SC23-6868-01 |
|
Specifying output volumes is required for the COPY DATASET command in a non-SMS-managed environment. (For a discussion of SMS considerations for moving data, see Moving SMS-managed data sets.) You can specify multiple target volumes with the OUTDDNAME or OUTDYNAM keywords. This allows you to specify spill volumes. These spill volumes are used if the data sets you are moving require more space than is available on your first choice of volume. If the output volume has unexpired data sets, you can either not process the data sets or write over them. DFSMSdss now distinguishes between non-SMS and SMS volumes specified in the OUTDDNAME or OUTDYNAM keywords. For non-SMS allocations, only the volumes that are non-SMS are considered for allocation. Similarly, only SMS volumes are considered for SMS allocations. The distinction between SMS and non-SMS is also used when determining the volume count for a multivolume allocation. Where volume count is determined from the number of specified volumes, only those volumes eligible for the type of allocation (SMS volume for SMS allocation or non-SMS volume for non-SMS allocation), processing proceeds with a null volume list. There are several reasons for distinguishing between SMS and non-SMS volumes:
For non-SMS output volume selection, DFSMSdss selects volumes based on size of the allocation necessary. The first volume that has enough space will be used for the allocation. When moving data sets with the extended attributes variable DS1EATTR set in the VTOC, the system selects non-SMS output volumes as follows:
Preferring EAVs means that all volumes that are EAVs will be evaluated before any non-EAVs are even considered. If the EAVs in the list of output volumes cannot satisfy the allocation request, all of the output volumes will then be evaluated to accommodate the allocation request. Note: The BPV is derived, in the following order,
from the Storage Group attribute, the IGDSMSxx parmlib member, and
the system default of 10 cylinders. The BPV can be changed dynamically
in the storage group definition or changed with the SETSMS BPV operator
command to override the IGDSMSxx parmlib member. However, for non-SMS
volume selection, there will be no Storage Group attribute to evaluate.
|
Copyright IBM Corporation 1990, 2014
|