You can request the Transaction Profiling report in the dialog either:
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:
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:
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:
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.