This document will explain the full procedure for setting up and using the View Metrics function.
Notes: This document replaces knowledge document TEC436475 ("What needs to be done to run Metrics in ISPF/TSO?").
The same steps below are applicable for all releases of View 2.0 and higher (including 12.2).
- If using ISPF/TSO as the interface for the Metrics:
- Add the SARSMPT program name to the TSO Authorization Table, found in the IKJTSOxx member of SYS1.PARMLIB. The SARSMFT program name must be added to the AUTHTSF section.
- Run SARINIT, with SMFTYPE=nnn (where nnn is from 128 to 255), to designate a SMF record type that is not currently used elsewhere, which View will use to create its SMF records.
- Identify the current SMF dump file in use on the system where the Metrics program will be running.
Use the following JCL to create a SMF file to be input to the Metrics program (SARMET01):
//XXXXXXXX JOB ...
//IEFPROC EXEC PGM=IFASMFDP,REGION=4M
//SYSPRINT DD SYSOUT=*
//INDD1 DD DISP=SHR,DSN=SYS1.MAN1
- To run the Metrics process, use JCL similar to the following:
//XXXXXXXX JOB ...
//SORT EXEC PGM=SARMET01
//STEPLIB DD DISP=SHR,DSN=VIEW.CVDELOAD
For the control cards:
- nnn is the SMFTYPE (128 to 255) as defined in the SARINIT parameters. yyddd is a Julian date, used in a range
- The control card with RPT=FILE, used in conjunction with the JCL statement "//USERSMF DD ...", specifies the File that contains the View Metrics SMF records output.
- The control cards with RPT=ACCS, RPT=CHNG, RPT=DELE, and RPT=USER, will generate Access, Change, Delete, and User reports, respectively.
- The control card with ELAP=nn (00-99) is used for the Load report, where nn indicates the elapsed time (in days) from the time of a disk delete of a report to the reload of the report to the disk layer.
For more detailed information, including the contents of the SMF records, and for samples of the different reports that are created, please see the"Metrics" chapter, in the CA View Reference Guide.