Contents
The FILE statement specifies the product input file. Every control file must have a FILE statement and it must be the first statement in the file. There can be only one FILE statement in a control file.
If the input file named in the FILE statement is being used by a product when the report is run, VMRGRW will not complete processing the control file. You must wait until the product is inactive or suspend use of the product.
FILE ddt [filename [filetype]] [DSNB].
- ddt
Specifies the keyword for the predefined data definition table for the respective filename and filetype. The ddt column of the Product Data Definition Table below lists the values you can use for this parameter. - filename
Indicates the filename of the data file that VMRGRW will use as input to the report. The fn column of the Product Data Definition Table below lists the values you can use for this parameter. - filetype
Indicates the filetype of the data file that VMRGRW will use as input to the report. The ft column of the Product Data Definition Table below lists the values you can use for this parameter. - DSNB
Specifies that the report is to be generated from the TMC, retrieving information about all the data sets on the tapes. This parameter is valid only if you are using a CA VM:Tape data definition table.
Product Data Definition Table Information
The following table lists the products for which VMRGRW produces reports, their corresponding data definition table names, filenames, filetypes, and their minidisk virtual addresses.
Product | ddt | filename | filetype | Minidisk/vaddr |
CA VM:Account | VMJRAW VMJAREC3 | RAWDATA PERIODTE | $$yyddmm no default | VMACCT 1B0 VMACCT 1B0 |
CA VM:Backup | TAPEPOOL | no default | TAPEPOOL | VMBACKUP 1C0 |
CA VM:Batch | VMHAUDIT | yy-mm-dd | VMHAUDIT | The A-disk of the user ID that ran the AUDEXT command |
CA VM:Director | UDIRECT UDIRECTX VMXAUD | USER USER AUDIT | DIRECT DIRECT EXTRACT | VMDIRECT 1B0 VMDIRECT 1B0 VMDIRECT 1D0 |
CA VM:Schedule | REQUEST3 | VMSCHED | IRBDB | VMSCHED 1B0 |
CA VM:Secure | UDIRECT UDIRECTX VMXAUD | USER USER AUDIT | DIRECT DIRECT EXTRACT | VMSECURE 1B0 VMSECURE 1B0 VMSECURE 1D0 |
CA VM:Spool | VMLAUDIT VMLCATLG VMLSNAPS VMLMASTR | AUDIT no default VMLSPOOL VMLDB | EXTRACT CATALOG SNAPSHOT MASTER | The A-disk of the user ID that ran the AUDEXT command VMSPOOL 1C0 VMSPOOL 1B0 VMSPOOL 1B0 |
CA VM:Tape | TMC5 AUDIT5 | VMTAPE VMTAPE | TMC AUDIT | VMTAPE 1B0 VMTAPE 1D0 |
Product Specific Requirements
The following information is product-specific and explains any restrictions, requirements, or other information about FILE statements that you should be aware of before running your VMRGRW reports.
CA VM:Account
- If you use a FILE VMJRAW statement in your control file, you must specify the filetype of the RAWDATA file you want to use. For example:
FILE VMJRAW RAWDATA $$100708. - If you want to use costed CA VM:Account information for an accounting period before the current account period, use:
FILE VMJAREC3 PERIODTE period.
where period is the name of the accounting period you want to report on. For example, the statement might read FILE VMJAREC3 PERIODTE 01FEB10.
CA VM:Secure or CA VM:Director
To create the USER DIRECT file, you can:
- Use the VMSOURCE control file record to specify the minidisk where the USER DIRECT file should be placed
- Use the CA VM:Secure or CA VM:Director VMXBKP01 utility to create the USER DIRECT file and place it on your A-disk