7. PARAMETERS › 7.2 Record Selection Parameters and JCL › 7.2.3 Record Identifiers and JCL - VM Monitor Data
7.2.3 Record Identifiers and JCL - VM Monitor Data
When you press the PF4 key (Create/Edit Select File) from the
Monitor Data Parameters panel, the MONXA SELECT file is
displayed. Figure 7-4e is a sample of the XEDIT panel of the
MONXA SELECT file showing the distributed defaults.
+----------------------------------------------------------------------------+
| |
| VM Monitor Data Select File Edit |
| |
| * * * Top of File * * * |
| * |
| * VM MONITOR SELECT/EXCLUDE OVERRIDE TABLE |
| * |
| * FORMAT: |
| * MODE D/RC D/RC .... |
| * |
| * WHERE: |
| * MODE = SELECT OR EXCLUDE |
| * D = MONITOR DOMAIN |
| * RC = RECORD CODE |
| * |
| * EXAMPLE: |
| * SELECT * |
| * EXCLUDE 2/* 7/* |
| * |
| * IN THIS EXAMPLE RECORD 1 CAUSES ALL RECORD TYPES TO BE INCLUDED, |
| * RECORD 2 CAUSES ALL SCHEDULE AND SEEK DATA TO BE EXCLUDED |
| * |
| * NOTE: THE '*' INDICATES ALL. WHEN ALL CLASSES ARE INDICATED IN |
| * A SELECT OR INCLUDE, THE RECORD CODE IS NOT NECESSARY. |
| * |
| * NOTE: BLANK LINES ARE IGNORED. |
| * COMMENT LINES BEGIN WITH AN ASTERISK FOLLOWED BY A BLANK. |
| * COMMENTS MAY BE CODED ON A RECORD BY CODING AN EXCLAMATION |
| * MARK FOLLOWED BY A BLANK. |
| * |
| INCLUDE * ! ZAP THE ENTIRE TABLE |
| EXCLUDE 2/* 7/* 10/* ! DROP SCHEDULE, SEEKS, APPLDATA |
| UNKNOWN EXCLUDE ! IGNORE UNKNOWN RECORD TYPES |
| * * * End of File * * * |
| PF1: Help PF4: Syntax Check File |
+----------------------------------------------------------------------------+
Figure 7-4e. VM Monitor Data Select File Edit Panel
Record identifiers for MONXA data are a maximum of four
characters long. The record identifier consists of two
parts, the VM domain and the VM record, separated by a slash
(/).
To specify all VM Monitor records, code an asterisk (*) as
the domain identifier. To specify all records within a VM
domain, code an asterisk as the record code. Figure 3-3, the
VM Monitor Data Selection Report, lists the available domains
and records.
NOTE: Do not exclude domain 1 VM Monitor records from
transmission due to requirements in the CA MICS VM and
CMS Analyzer.
EXAMPLE: Retain only system-wide data, configuration data,
processor data, and device data.
EXCLUDE * ! drop all records (except those
* required by CA MICS VMC)
INCLUDE 0/* 1/* 5/* ! send SYSTEM, MONITOR, PROCESSOR,
INCLUDE 6/* ! and I/O DOMAIN data
UNKNOWN EXCLUDE ! drop all custom records
When you use the PF5 key to Create/Edit the JCL from the VM
Monitor Data Parameters panel, the following screen is
displayed.
+-----------------------------------------------------------------------------+
| |
| VM Monitor Data Transfer JCL Edit |
| |
| Press PF1 for HELP |
| |
| * * * Top of File * * * |
| //* |
| //* VM MONITOR DATA TRANSMISSION VIA SPOOL |
| //* |
| //MONXA EXEC PGM=VMTRCV,REGION=1024K |
| //STEPLIB DD DISP=SHR,DSN=sharedprefix.MICS.LOAD |
| //PRINT DD SYSOUT=*,DCB=(LRECL=81,BLKSIZE=6075) |
| //SYSUDUMP DD SYSOUT=* |
| //OUTPUT DD DISP=(MOD,CATLG),SPACE=(CYL,(15,15),RLSE), |
| // UNIT=SYSINT,DSN=prefix.VMESA.MONITOR.DATA, |
| // DCB=(BLKSIZE=23440,RECFM=VB) |
| //INPUT DD DATA,DLM='++' |
| ++ |
| // |
| * * * End of File * * * |
| |
+-----------------------------------------------------------------------------+
Figure 7-4f. VM Monitor Data JCL Edit Panel
