CA Mainframe VM Product Manager - 1.2 : DASD Utility Basics

Contents

This section summarizes the DASD utilities, explains how to run them using EXECs, and provides recommendations, requirements, and restrictions for running them.

DASD Utilities Summary

This section summarizes the DASD utilities, explains how to run them using EXECs, and provides recommendations, requirements, and restrictions for running them.

  • VMRMDS
    (Minidisk Scanning)
    Gathers empirical data used by the VMRMUA, VMRSDA, and VMRMCA utilities.
  • VMRMUA
    (Minidisk Utilization Analysis)
    Provides statistical snapshots of CMS minidisk utilization. Produces reports describing different aspects of your DASD system. Makes recommendations based on those reports.
  • VMRSDA
    (System DASD Analysis)
    Maps your VM DASD system, including all CP-reserved areas, and identifies potential problems. Validates your DASD (for example, checks for sufficient expansion area for your CP nucleus and alerts you to any overlaps).
  • VMRMCA
    (Minidisk Cost Analysis)
    Reports on costs incurred by CMS minidisks.
  • VMRCMQ
    (Component Minidisk Query)
    Reports on component minidisk utilization. Reports indicate when a component minidisk exceeds its threshold value.

How to Use EXECs to Run Utilities

If you have many minidisks to analyze, you might want to use EXECs to run the utilities. The following example runs the VMRMDS utility and then the VMRMUA utility, and sends the results to your virtual printer:

/* Sample MYVMRMUA EXEC  -  REXX Program */
address 'COMMAND'
'EXEC VMRMDS'
'EXEC VMRMUA (PRINT'
'CP MSG * CHECK TO SEE IF THE USEID IS LOGGED ON'
if rc=57 then push 'CP LOGOFF'
exit

You can use CA VM:Schedule to schedule the EXEC. For example, to run a request named MUAJOB, using the MYVMRMUA EXEC, every Friday night at 11:00 PM, enter the following CA VM:Schedule command:

vmsched schedule muajob myvmrmua (at 23:00:00 on fri again weekly

Recommendations, Requirements, and Restrictions

The DASD utilities are resource-intensive. You should run them during off-peak hours.

We recommend that you run all of the utilities from the VMANAGER user ID. VMANAGER has the appropriate authorizations, privilege classes, and virtual storage to run the utilities. If you use a user ID other than VMANAGER to run the utilities, the user ID must have CP privilege classes B and E. You must link and access the VMANAGER 193 and 195 minidisks. The access mode Z and virtual address 1F1 are reserved for use by the utilities. Additional requirements are provided on a utility-by-utility basis in the corresponding utility section.