z/OS DFSMS Implementing System-Managed Storage
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


Determining the Management Classes

z/OS DFSMS Implementing System-Managed Storage
SC23-6849-00

After you identify the filters to intercept the allocations and redirect them to DASD, determine the proper management class attributes, such as residency time on primary and migration level 1 storage. Consider the amount of space required to store the data set on primary or migration level 1 storage versus the number of mounts required to recall the data. The volume mount analyzer produces a report ranking all of the management classes by number of migration level 2 mounts, number of recalls, and additional tracks needed for the migration and recall activity for that management class.

The Management Class Report is sorted in descending order by L2-MOUNTS, RECALLS, and TOT TRKS. The most important value to keep low is the L2-MOUNTS, because it represents specific mounts. All other tape mount management mounts are scratch mounts. When you select a management class, you should rerun the Estimate Report with that management class.

The following control statements generate a Management Class Report for all data sets created by PGM=IDCAMS, but not those on 3420 tapes:

PGM(INC(IDCAMS))
UNIT(EXC(3420))
REP(MC)

Table 1 shows the five top-ranked management classes for the sample installation's tape mount management data sets generated by IDCAMS.

Table 1. Management Class Report for IDCAMS Data. L0AGE is the number of days that the data set resides on primary storage before migration. L1AGE shows the number of days that the data set resides on migration level 1.
ORDER L0AGE L1AGE L2-MNTS RECALLS TOT TRKS L0-TRKS L1-TRKS L2-MB
1 1 1 451 451 3191 3191 0 3
2 0 1 451 451 7 0 7 0
3 0 0 451 451 0 0 0 8
4 1 2 99 451 3192 3191 1 0
5 0 2 99 451 8 0 8 0

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014