Some reports allow you to specify selection criteria to filter records based on their field values before they are passed on to report processing. This enables you to tailor your reports to include only the information that you are interested in. For example, you can specify selection criteria to restrict reports to:
There are several types of Selection Criteria, to support the various types of record processed by CICS PA:
Type of Selection Criteria | Filters these types of record… | For these reports… | Global? |
---|---|---|---|
Performance | CMF performance (SMF 110) | All Performance Reports, Transaction Resource
Usage Reports, Performance Graphs Some Extracts: Cross-System Work, Record Selection |
Yes |
DB2® accounting (SMF 101) | DB2 reports (in the Subsystem Reports category) | Yes | |
WebSphere® MQ accounting (SMF 116) | WebSphere MQ reports (in the Subsystem Reports category) | Yes | |
OMEGAMON® XE for CICS® (SMF 112) | OMEGAMON reports
(in the Subsystem Reports category) Record Selection extract (in the Extracts category) |
Yes | |
Transaction Resource Usage | CMF performance (SMF 110, class 5) | Transaction Resource Usage Reports | Yes |
Exception | CMF exception (SMF 110) | All Exception Reports Record Selection extract (in the Extracts category) |
Yes |
Logger | System logger (SMF 88) | Logger report (in the System Reports category) Logger extract and Report Selection (in the Extracts category) |
No |
You can specify Performance, Transaction Resource Usage, and Exception Selection Criteria in your Report Set in two places:
You specify Logger Selection Criteria individually for each System Report/Extract in your Report Set.
You can also specify Performance Selection Criteria in a Report Form. If Selection Criteria are specified in both the Report and the Report Form it uses, records must satisfy both criteria to be selected for the report. For details, see Selection Criteria in Report Forms.
For each record, the Select Statements are checked one at a time until the record is either included in or excluded from report processing.
Specifying multiple Select Statements provides you with a powerful facility to enhance your reporting capability. For example, suppose that you have two application systems, FINANCE and STOCK. Each system has its own performance thresholds that must be met. FINANCE transactions, prefixed by FI, must have a response time less than or equal to 100 milliseconds during peak period. STOCK transactions, prefixed by ST, must have a response time less than or equal to 200 milliseconds during peak period.
In this case, you would specify two Select Statements, one for each application:
Selection Criteria | Select Statement | Conditions |
---|---|---|
Global or Report | FINANCE | TRAN=FI* |
STOCK | TRAN=ST* |
Each CMF Performance record is checked against the Select Statements. The first Select Statement for the FINANCE system is checked first. If its conditions are met, then the record is passed to report processing with no further checking. Otherwise, the second Select Statement for the STOCK system is checked next. If its conditions are met, then the record is passed to report processing with no further checking. CMF records failing both Select Statements bypass report processing.
For a detailed discussion and examples, see Using SELECT statements.
When you select Selection Criteria for the first time, you are taken directly to specify a Select Statement. When you have specified at least one, a list is displayed. You can then select (edit), delete, or include/exclude any Statements in the list, or add new ones.
Thus the panel flow is: