Page data set volumes 2-n

The recommended types of data sets for these volumes are:

Local
SMF
RMF™ reporting
STGINDEX data sets (if used)
Image-related LOGREC data set (if used)

Considerations when setting up a page data set volume are:

Where possible, each local page data set should be placed on a dedicated volume connected to a control unit that is not used for other paging volumes, and on channel paths that are not used for other paging volumes. Although paging rates to DASD might be low, given sufficient central and expanded storage, increasing workloads might eventually cause significant paging. If this happens, locating local page data sets as suggested provides the best performance. Additionally, a large number of page data sets yields better performance than a small number if there is significant paging to DASD.
IBM® does not recommend placing other data sets on the volumes used for page data sets. However, if you must place other data on local page data set volumes, choose data with the lowest frequency of reference possible to minimize contention with paging.
As one might expect, the I/O activity to SMF data sets is proportional to the amount of SMF data you record from your specified SMF parmlib member.
I/O to STGINDEX data sets is only done when a job stream does batch checkpoints to save status (to allow the job stream to be restarted) or obtains restart status; therefore, this data set has relatively low I/O. If your installation always IPLs using CVIO or CLPA (which implies CVIO), there is no reason to have a STGINDEX data set. In this case, specify VIODSN=IGNORE in IEASYSxx. For more information, see z/OS MVS Initialization and Tuning Reference.
For information on choosing the LOGREC recording medium, see "Recording Logrec Error Records" in z/OS MVS Diagnosis: Tools and Service Aids. I/O activity is typically low for the image-related LOGREC data set.
Dynamic dumps are recommended, so SVC dump data sets are not listed.