Contents

Report Fields

All of the VMRMUA reports have numbered columns to assist you in identifying the report fields. Some of the fields shared by the reports are identified below.

These fields are:

ColumnFieldContent
1UseridUser ID
2VaddrMinidisk's virtual address
3VolserVolume serial number
4DevtypeDASD device
5Last UpdatedLast day the minidisk was updated
6Days AgoNumber of days since the minidisk was last updated
7FilesNumber of files on the minidisk
8BsizeBlock size
91K Blocks UsedNumber of 1024 byte blocks used on the minidisk
101K Blocks LeftNumber of unused 1024 byte blocks left on the minidisk
11Total 1K BlocksSum of used and unused blocks on the minidisk
12%FullPercentage of used space on the minidisk

13
AllocationAmount of space allocated on the DASD device for the minidisk

Other fields are unique to each of the reports. These include:

  • Comments
  • Recommendations for resizing minidisks
  • The amount of space saved by resizing minidisks

VMRMUA Analysis Preface

The VMRMUA report file begins with the VMRMUA Analysis Preface. It provides the selection criteria used to create the reports, summary information about your DASD system, and a list of the reports created.

Report 1 Minidisks With Questionable Status

Report 1 is a list of minidisks with unusual characteristics. These include:

  • A last update date in the future. This can occur when the system is restarted, using the IPL command, with an incorrect date.
  • Minidisks that are more than 5 percent full, yet containing no files. These are usually very small minidisks.
  • Minidisks smaller than 10 Kilobyte.
  • Minidisks that seem to be larger than the disk pack.

Report 2 Minidisks Not Updated Last nnn Days

Report 2 is a list of minidisks that have not been changed over time. This can help you identify unused minidisks. The number of days is defined by the OLDDISK record in the VMRMUA CONFIG file. The default is six months.

CMS does not collect information about how often a minidisk is accessed, so remember that a frequently accessed but unaltered minidisk could appear in this report.

The last update date is read from the CMS minidisk DIRECTOR record, which describes the minidisk and points to the location of files on the minidisk. The minidisk last update date is not necessarily synonymous with the date of the most recently updated file on that minidisk. In addition to being updated when a file is written, the minidisk is also updated when a file is erased, copied, received, or released while accessed read-write.

Report 3 Percentile Rankings By Minidisk Size

Report 3 is a table that ranks minidisks by size. Report 3 cannot be sorted by editing the SORT record in the VMRMUA CONFIG file.

VMRMUA uses the percentile boundaries shown here to define medium-size and large-size minidisks in the reports that follow. These are set by the MEDSIZE and BIGSIZE records in the VMRMUA CONFIG file.

Report 4 MEDIUM Size Flagged Minidisks

Report 4 is a list of underutilized medium-size minidisks. A medium sized minidisk is defined by the MEDSIZE record in the VMRMUA CONFIG file. This value appears on the first line of the report. The other selection thresholds values, Update and Utilization, are determined by the MEDUPD and MEDUTIL records in the VMRMUA CONFIG file. This report also has recommendations for reducing the size of these minidisks and shows you the disk space you could recover by making the recommended changes.

Report 5 LARGE Size Flagged Minidisks

Report 5 is a list of underutilized large-size minidisks. The report contains information about the current sizes of the minidisks and recommends smaller sizes for them. The report also shows you the disk space you could recover by making the recommended changes. As with Report 4, the selection criteria are displayed. The BIGSIZE, BIGUPD, and BIGUTIL records in the VMRMUA CONFIG file govern the content of this report.

Report 6 Smallest Minidisks

Report 6 is a list of minidisks occupying very small amounts of space. These are minidisks that are smaller than 95 percent of all minidisks. Report 8, Frequency Distribution of Minidisk Utilization, graphically shows you how many minidisks fit this criterion. You can eliminate or consolidate these minidisks to save DASD.

Report 7 Largest Minidisks

Report 7 is a list of minidisks occupying very large amounts of space. VMRMUA selects minidisks that are larger than 95 percent of all minidisks. Report 8, Frequency Distribution of Minidisk Utilization, graphically shows you how many minidisks fit this criteria.

Report 8 Frequency Distribution of Minidisk Utilization

Report 8 contains a histogram that groups minidisks by utilization. The first column in the histogram is the percentage of utilization. The second column is the number of minidisks at that utilization level and the percentage of minidisks on your system that this number represents. The third column is the cumulative number and percentage of minidisks that are below the utilization level shown in the first column. For example, if the first column is 0-4 and the third column is 565 (29 percent), then 565 minidisks are less than 4 percent full and represent 29 percent of the minidisks on your system.

The right-hand side of Report 8 graphically depicts the number of minidisks at each utilization level.

Report 9 Least Full Minidisks

Report 9 is a list of minidisks of medium or greater size that are less than 5 percent full. Minidisks that are 0 percent full are highlighted in column 12 (%Full) of this report. This report is affected by the MEDSIZE, MEDUPD, and MEDUTIL records in the VMRMUA CONFIG file.

Report 10 Most Full Minidisks

Report 10 lists minidisks of medium or greater size that are more than 95 percent full. These minidisks are in imminent danger of a disk-full condition. If a minidisk is 98 percent full or more, VMRMUA highlights the value in bold type in Column 12 (%Full). This report is affected by the MEDSIZE, MEDUPD, and MEDUTIL records in the VMRMUA CONFIG file.

Report 11 Minidisks With at Least nnn Files

Report 11 lists minidisks containing many files. VMRMUA calculates percentiles based on a file count per minidisk and includes those minidisks in the 95th percentile. In the sample report, 5 percent of all minidisks on the system contain 475 or more files. Use this report to identify minidisks that could be split up to reduce access time.

Report 12 Minidisks With n CMS Files or Fewer

Report 12 lists minidisks with very few files. VMRMUA highlights the value in Column 7 (Files) for minidisks that contain no files. Use this report to identify obsolete and infrequently used minidisks.

Column 6 (Days Ago) shows how long it has been since the minidisk was last updated. VMRMUA highlights the value in this column if the minidisk has not been updated for 30 days or 7 times the medium update value (as calculated by the MEDUPD record in the VMRMUA CONFIG file), whichever comes first.

The value n (5 in the sample report) is set by the MAXFILES record in the VMRMUA CONFIG file.

Report 13 Minidisks Blocked at 800 Bytes

This report does not produce output because CDF (800-byte blocked) minidisks are no longer supported on VM.

Report 14 CMS Volume Level Summary Statistics

Report 14 shows utilization statistics for each CMS-formatted DASD volume on your system.

Report 15 Excepted Userids/Vaddrs

Report 15 is a list of minidisks excluded from the analysis. It is produced only if you modify the XLIST and XUSERIDS records in the VMRMUA CONFIG file.

Report 16 Minidisks on Excepted Pack(s)

Report 16 is a list of minidisks located on disk packs excluded from the analysis. It is produced only if you modify the XLIST and XPACKS records in the VMRMUA CONFIG file.