VMRMCA requires only the CMSDISKS file and the CA VM:Account CUSTOMER ACCTLIST files to execute. However, without access to the cost data provided by the MDISK COSTABLE file, the output reports are not as valuable. Additional input files can be used to customize the VMRMCA output report information to fit your requirements.
Contents
VMANAGER CMSDISKS File
The VMANAGER CMSDISKS file contains CMS minidisk allocation information; it provides VMRMCA with the raw data required for its analyses. This file is created by the VMRMDS utility. The accuracy and completeness of its data is only as good as its timeliness. Therefore, you should run VMRMDS immediately before running VMRMCA to ensure accurate and complete information.
CUSTOMER ACCTLIST File
The CA VM:Account CUSTOMER ACCTLIST file associates each VM directory account code with a CA VM:Account customer. Before using this file, you should ensure that every account code has been associated with a CA VM:Account customer.
MDISK COSTABLE File
The CA VM:Account MDISK COSTABLE file contains minidisk charge information. Check this file to ensure that all device types are included, that the costs for each device type are correct, and that all CA VM:Account customers are included.
CUSTOMER MASTER File
The CA VM:Account CUSTOMER MASTER file associates a billing address with each CA VM:Account customer. Ensure that every CA VM:Account customer has a billing address and that each address is up to date.
PROJECTS ACCTLIST File
The CA VM:Account PROJECTS ACCTLIST file associates each VM directory account code with a CA VM:Account project. Check that every account code has been associated with a project.
PROJECTS MASTER File
The CA VM:Account PROJECTS MASTER file associates a CA VM:Account project name with a CA VM:Account customer ID. Ensure that every CA VM:Account project has an associated customer.
VMRMCA EXCLUDE File
The VMRMCA EXCLUDE file allows you to specify group members to be excluded from analysis. To create this file, use XEDIT, specifying a filename of VMRMCA and a filetype of EXCLUDE. The first field of each record must be a groupname and can be followed by a list of group members to be excluded. For example:
VOLUME VMZ0* USERID BERT CALVIN LUCY 191
ACCTCODE 134* 88888
MANAGER SMITH
- In the VOLUME record, masking has been used to specify that all volumes beginning with VMZ0 are excluded from analysis.
- In the USERID record, all of BERT's and CALVIN's minidisks are excluded from analysis, while only LUCY's 191 minidisk is excluded.
- In the ACCTCODE record, account code 88888 has been excluded from analysis, and masking has been used to specify that any account codes beginning with 134 should be excluded from analysis.
- In the MANAGER record, only manager SMITH is excluded from analysis.
An EXCLUDE file can be overridden by the NOEXCLUDE option on the command line.
VMRMCA INCLUDE File
The VMRMCA INCLUDE file lists group names and group members to be included in the analysis. Use XEDIT to create the INCLUDE file by specifying a filename of VMRMCA and a filetype of INCLUDE. The structure of the INCLUDE file is the same as that of an EXCLUDE file. An INCLUDE file takes precedence over an EXCLUDE file.
groupname THRESHLD File
The groupname THRESHLD file provides group level configurability by setting exception thresholds for individual group members. The filename is groupname and the filetype is THRESHLD.
A threshold lets you decide what minidisks you and your users should be aware of. For example, if you wanted to know which minidisks had not been updated for the last three months, you would change the Last Update column value to 90. The columns in a THRESHLD file are described in the file itself. The original values in each column are the default values.
There are three levels of detail available in a THRESHLD file:
- NORMAL
Uses the exception thresholds defined in the THRESHLD file. Any minidisks that satisfy any of the exceptions in columns 3 through 9 are included in the report. NORMAL is the default detail level. - ALL
Produces a report in which all of the minidisks owned by the group member are included. Minidisks that exceed any of the exceptions in the THRESHLD file are flagged with an exception code and EXTREME level minidisks are overprinted. - EXTREME
Produces a list of minidisks satisfying a set of globally defined extreme exception conditions. These conditions are defined in the program. A minidisk is identified as an EXTREME if it meets one or more of the following conditions:- It has not been updated in the last 365 days.
- It is less than or equal to 10 percent full.
- It has no files on it.
You can create a THRESHLD file for any group (except DISTCODE) by issuing this command:
- VMRMCA ( SETUP groupname
- groupname
groupname is the group for which you want to create a threshold file, and will be the filename of the file created.
VMRMCA uses a THRESHLD file for a group whenever the groupname is specified on the command line. If no group name is specified, VMRMCA looks for a CUSTOMER THRESHLD file. If more than one group is specified on the command line and there is a THRESHLD file for each group, VMRMCA uses the THRESHLD file for the first group only. For example, if the command line was:
VMRMCA ( BYGROUP MANAGER CUSTOMER USER01
VMRMCA would use the MANAGER THRESHLD file only.
If you want to exclude certain minidisks from the report, modify values in the THRESHLD file. - groupname
VMSECURE MANAGER File
The VMSECURE MANAGER file associates a list of CA VM:Secure managers with user IDs. This file must be accessed if:
- groupname MANAGER is specified on the command line
- groupname MANAGER is used in any other input file
- You want to create a MANAGER THRESHLD file
- You want to use the DISTRIB option with VM:Secure managers
To create the VMSECURE MANAGER file, follow these steps:
- Link to and access the CA VM:Secure DRCT (1B0) minidisk. You may see messages warning you that you are linked to this disk.
Enter this command, in which x is the minidisk access mode:
listfile * * x (exec
- Release and detach the disk.
- Use the XEDIT command to edit the CMS EXEC file.
Enter this XEDIT command:
shift left 7 *
- Set filename to VMSECURE and filetype to MANAGER.
- Enter the FILE command.
VMDIRECT MANAGER File
The VMDIRECT MANAGER file associates a list of CA VM:Director managers with user IDs. This file must be accessed if:
- groupname MANAGER is specified on the command line
- groupname MANAGER is used in any other input file
- You want to create a MANAGER THRESHLD file
- You want to use the DISTRIB option with CA VM:Director managers
To create the VMDIRECT MANAGER file, follow these steps:
- Link to and access the CA VM:Director DRCT (1B0) minidisk. You may see messages warning you that you are linked to this disk.
Enter this command, in which x is the minidisk access mode:
listfile * * x (exec
- Release and detach the disk.
- Use the XEDIT command to edit the CMS EXEC file.
Enter this XEDIT command:
shift left 7 *
- Set filename to VMDIRECT and filetype to MANAGER.
- Enter the FILE command.
groupname USERID File
The groupname USERID file associates a group name with user IDs. It is used with the DISTRIB command line option to spool print files to group members.
A groupname USERID file is automatically created for the group name specified on the following command line (used to create a THRESHLD file):
VMRMCA ( SETUP groupname
The USERID file will be an empty shell in which you will need to manually enter the user IDs. You can also use XEDIT to create a file with a filename of groupname and the filetype USERID, and enter records, where the first field is the group name and the second field is the group member.
Note: The VMSECURE MANAGER or VMDIRECT MANAGER file performs the same functions as a USERID file for the MANAGER group. Therefore, a MANAGER USERID file is not needed for the MANAGER group and is not automatically created with a MANAGER THRESHLD file. A USERID file is also not created when you create a USERID THRESHLD file.
groupname USRNOTES File
The groupname USRNOTES file is used to append notes to a specified group member to his report.
Use XEDIT to create a file with the filename of groupname and a filetype of USRNOTES. Each record in the file must begin with the group member's user ID to whose report you want the note appended.