Previous topic |
Next topic |
Contents |
Contact z/OS |
Library |
PDF
Data Set Stacking Using Volume Serial z/OS DFSMS Implementing System-Managed Storage SC23-6849-00 |
|
With the enhancements, the system is now aware of data set stacking when requested with volume serial (either with the VOL=SER parameter or obtained from the catalog) within a job step. Recommendation: Use
VOL=REF for data set stacking across jobs or steps. If you use VOL=SER
to stack data sets across steps or jobs, the system cannot detect
data set stacking. In these cases, you can do one of the following:
If the ACS routines initially directed the stacked allocations
to different device categories, the system detects this and re-invokes
the ACS routines, passing them additional information. The ACS routines
can then take one of the following actions:
Figure 1 and Figure 2 show examples of ACS routine fragments to assign the referencing data set to a consistent device category as the referenced data set. Figure 1. Storage Class
ACS Routine Fragment to Assign Consistent Device Category
Figure 2. Storage Group
ACS Routine Fragment to Assign Consistent Device Category
The system re-invokes the ACS routines only when all of the following
conditions are true:
Since data set stacking might cause a second or third invocation of the ACS routines, you might want to take special care when using WRITE statements to avoid duplicates in the job log. Additionally, existing SMS-managed data sets are not checked by the system for inclusion in a data set collection. For SMS-managed data sets that are cataloged, the system cannot assume that the volume information in the catalog represents the original intended volume for the data set. For example, the data set might have been redirected, in which case if the system uses the volume information in the catalog to allocate the data set, the data set might be incorrectly placed in the wrong data set collection. |
Copyright IBM Corporation 1990, 2014
|