Report command
You can request the Transaction Profiling report in the dialog either:
- From a Report Set. Select the Transaction Profiling report in the Performance Reports category.
- Independently of Report Set. Select Profiling on the Primary Option Menu.
To request the Transaction Profiling report in batch, you use the PROFILING operand.
CICSPA PROFILING(REPORT(SMF|hdbname)),
PROFILING(BASELINE(SMF|hdbname))
You must specify two PROFILING operands for each Transaction Profiling report:
- One with a REPORT suboperand that defines the source of the report data
- One with a BASELINE suboperand that defines the source of the baseline data
For example, REPORT(SMF) defines the source of the report data as the SMF files identified by either the most recent INPUT operand, if specified, or the DDname SMFIN, if no INPUT operand is specified. BASELINE(hdbname) defines the source of the baseline data as the List or Summary Performance historical database named hdbname that is defined in the Repository identified by the DDname CPAHDBRG.
To tailor the report, you can specify report options as follows:
CICSPA PROFILING([ID(profile#)],REPORT(SMF|hdbname),
[SUFACTOR(ddname|hdbname(nnnnn.nnn)),]
[SMFSTART(date,time),]
[SMFSTOP(date,time),]
[SELECT(PERFORMANCE(INCLUDE|EXCLUDE(field1(values1),...),...)),]
[SELECT2(PERFORMANCE(INCLUDE|EXCLUDE(field1(values1),...),...)),]
[FIELDS(field1[(options)],...),]
[INTERVAL(hh:mm:ss),]
[PRINT(REPORT,BASELINE,DELTA,CHANGE,
FULL|EXCEPTIONSONLY,NOBLANKLINES|BLANKLINES),]
[THRESHOLD(%abovebaseline,%belowbaseline),]
[OUTPUT(ddname),]
[EXTERNAL(ddname),]
[NOTOTALS|TOTALS(n),]
[LINECount(nnn),]
[TITLE1('...1st 64 characters of title... '),]
[TITLE2('...2nd 64 characters of title... '),])
PROFILING([ID(profile#)],BASELINE(SMF|hdbname),
[SUFACTOR(ddname|hdbname(nnnnn.nnn)),]
[SMFSTART(date,time),]
[SMFSTOP(date,time),]
[SELECT(PERFORMANCE(INCLUDE|EXCLUDE(field1(values1),...),...)),]
[SELECT2(PERFORMANCE(INCLUDE|EXCLUDE(field1(values1),...),...)),]
[FIELDS(field1[(options)],...),]
[INTERVAL(hh:mm:ss)])
To understand how the Transaction Profiling report compares two sets of data, it is useful to think of the Transaction Profiling report as a comparison of two Performance Summary reports:
- One for the report data, as specified by the PROFILING(REPORT(...)...) operand
- One for the baseline data, as specified by the PROFILING(BASELINE(...)...) operand
- Group and sort input records by key field values
- Summarize the values of non-key fields in each group of records (for example, as an average or a total)
The Transaction Profiling report consolidates the two sets of summarized data by finding a row of summarized baseline data whose key fields match a row of summarized report data. The Transaction Profiling report then compares the values of the non-key fields in the two matched rows. Rows of summarized baseline data whose key field values do not match any rows of summarized report data are discarded.
When designing a Transaction Profiling report, you might find it useful to first run the two Performance Summary reports. This enables you to review the two sets of summarized data separately, before using the Transaction Profiling report to consolidate and compare them. Note that the Report Form and the Baseline Form both affect how the Transaction Profiling report summarizes baseline data. The Transaction Profiling report summarizes baseline data according to the order of the fields in the Report Form, and using only those fields that occur in both the Baseline Form and the Report Form.
If a CICSĀ® system (APPLID/Image) is specified and a VRM can be derived from the MCT load library or SDFHLOAD library, then that VRM is used. If a VRM cannot be derived from the system definition then the VRM value specified in this panel is used.
If the Profiling report includes field CPUSU in either the Form or HDB Template, you can specify the CPU Service Unit conversion factor for specific Images, SMF files, or HDBs, or use the current system conversion factor. For information about specifying the appropriate conversion factors see the section on CPU service unit conversion factors in the CICS Performance Analyzer for z/OSĀ® User's Guide.