VMRMDS scans the CP object directory to find out which minidisks are defined.
VMRMDS establishes links and loop through the minidisks by:
- Linking to each minidisk as 1F1
- Looking at each minidisk and determining:
- The size of the minidisk
- How much of the minidisk is in use
- The date when the minidisk was last updated
VMRMDS does the following:
- Determines device types and models (sizes).
- Reads CP ALLOCATION records.
- Locates and determines the size of the CP nucleus.
The length of time this process takes depends on the number of minidisks in your system. To keep you informed, VMRMDS displays information about the minidisks it has scanned in a running commentary screen. VMRMDS updates this screen with its progress for each new volume.
After completing its minidisk allocation analysis, VMRMDS summarizes your disk space, providing:
- Number of CMS minidisks
- Number of files
- Number of kilobytes in use
- Number of kilobytes allocated
- Average percent (%) full
- Number of "other" minidisks
Requirements
VMRMDS must be able to LINK to any minidisk, even those without passwords. An OPTION LNKNOPAS statement is usually required to enable this access. If you have CA VM:Secure, CA VM:Director, or another security product that intercepts the CP LINK command, you must give VMANAGER authorization to link with or without supplying passwords.
If VMRMDS cannot link and exceeds its link error threshold, it will produce a VMRFIL ERROR file listing the failed links. It will not produce the output files needed for the VMRMUA, VMRSDA, and VMRMCA utilities.
To determine whether VMANAGER has sufficient virtual storage to run VMRMDS, add 1000 to the number of minidisks on your system and round up to the next thousand. The result is an estimate of the amount of virtual storage, in kilobytes, needed to run VMRMDS. For example, if your system has 2755 minidisks, you would need about 4000 kilobytes (4 megabytes) of virtual storage. If the virtual storage for VMANAGER is insufficient, increase the amount before proceeding.
Certain display terminals, such as the 3278 model 5, can cause the VMRMDS screen display to appear distorted. To correct this, rename the VMRDSP MODULE, located on the VMANAGER 195 minidisk, to VMRDSP XMODULE. This causes all screen I/O to display in line mode.