Overview of the SAS historical reporting process
To collect performance data, SMF recording must be enabled for OMEGAMON AI for CICS. You can enable SMF recording during product customization.
Table 1 shows the steps in the SAS historical reporting process,
from OMEGAMON AI for CICS data collection to
SAS report creation.
| Stage | Description |
|---|---|
| 1 | OMEGAMON AI for CICS collects performance data using additional event monitoring points defined in the MCT and clocks and counters information defined in the GLOBAL_OPTIONS module. CICS® or OMEGAMON AI for CICS writes performance data as SMF 110 records and, optionally, clocks and counters information as SMF user records. |
| 2 | SAS creates a DETAIL data set and, using job KC2SMFJ, populates it with collected SMF data. |
| 3 | SAS uses data in the SAS DETAIL data set (through job KC2REPTJ) to generate the supplied reports and charts (KC2TRPn and KC2TCHn). |
| 4 | You can generate user-defined reports by using the supplied Generalized Report Writer job KC2GRWJ. |
| 5 | You can generate response time group definitions by using the supplied transaction group build job KC2TRXJ. |
| 6 | At the end of the day, SAS summarizes the DETAIL data set to the DAILY data set and archives the DETAIL data set to cartridge (through job KC2DLYJ) for post processing purposes. |
| 7 | SAS uses data in the SAS DAILY data set (through job KC2REPTJ) to generate the supplied reports and charts (KC2DRPn and KC2DCHn). |
| 8 | Ad hoc reports may be produced directly from the SMF data set using job KC2ADHCJ. |