z/OS DFSMS Using the Volume Mount Analyzer
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


The Estimate Report—Statistical Mount Savings Breakdown

z/OS DFSMS Using the Volume Mount Analyzer
SC23-6859-00

The Estimate Report includes three breakdown reports to supplement the Savings/Cost Summary ( Figure 1). The Statistical Mount Savings Breakdown provides the details for the Statistical Mount Savings reported in the Savings/Cost Summary. The total number of current statistical mounts is arranged by tape mount management data set category, and savings are attributed to the particular management class that would have been assigned based on the specified values for L0AGE and L1AGE.

The first breakdown report is the Statistical Mount Savings Breakdown Report shown in Figure 1.

Figure 1. Estimate Report—Statistical Mount Savings Breakdown

 1  In this example, the current statistical mounts value (CURR STAT MOUNTS) for active data sets is 2088.5. The target statistical mounts (TARG STAT MOUNTS) is set to the HSM - LEVEL 2 TARG MNT# for the ACTIVE, ACTV GDG, and BACKUP categories, and the numbers in these columns are the same.

The estimated target statistical mounts value will be 9.9 if you use DFSMS to manage tape data sets. This reduction results from managing tape data sets in the storage hierarchy using 3490E tape hardware. The reduction from 2088.5 to 9.9 is significant because the data sets representing 1483.1 of the mounts are residing on primary DASD, and the data sets representing the remaining 605.4 mounts are on migration level 2 tape. Because of 3490E and, optionally, DFSMShsm compaction, these mounts are reduced to 9.9 target mounts.

See Statistical Mounts for more information.

 2  For ACTV GDG data sets, the values in the HSM - LEVEL 2 TARG MNT# column in Figure 1 are equal to the values in the HSM - LEVEL 2 TARG VOL# column in Figure 1 because when the ACTV GDG volumes are mounted, all the data sets are written to these volumes during one output operation. Thus, full volumes are written.

 3  GFTAVMA models large data sets (greater than the LARGE keyword default of 600MB) as going directly to migration level 2 tape. Therefore, DFSMS would not manage them, and they would never reside in the storage hierarchy. The mount reduction from 4050.0 to 2380.2 is based on modelling to the 3490E with the Enhanced Capacity Cartridge System Tape (TAPEDEV of 3490E and TAPELEN of 2), which has a much larger capacity.

 4  The target mounts incurred for migration level 2 recalls are reported in the MGMTCLAS row.

 5  In this example, the volume mount analyzer simulates an environment where DFSMShsm bypasses migration level 1 processing. Therefore, the columns for migration level 1 contain zeros. The data sets are modelled as going directly from primary DASD to migration level 2 tape, bypassing migration level 1 DASD because the LEVEL0AGE and the LEVEL1AGE keywords defaulted to one.

 6  The target HSM migration level 2 mounts for ACTIVE, ACTV GDG, and BACKUP represent the mounts needed to create migration level 2 tape volumes.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014