CICS Transactions CPU Usage

The CICS Transactions CPU Usage report shows the distribution of CPU usage among transactions processed by the target subsystem. The report appears when Strobe records transaction identifiers in the sample data set.

Activity within IBM-supplied modules, such as I/O service routines, compiler library routines, and SVCs, is attributed to pseudo-sections whose names begin with ".". The true name of the module appears when you expand an entry to the Section level.

Report Details

Terminal

  • Terminal shows the terminal associated with a transaction.
  • CPU% Total shows the percentage of CPU activity with or without any concurrent I/O activity for the transaction.

Click list_closed.gifnext to a Terminal to view the following specific transaction detail.

  • Transaction is the name of the active transaction. If the transaction name contains unprintable characters, the report shows it in hexadecimal notation.
  • Description briefly explains the function of the transaction. Function descriptions appear for all Strobe pseudo-entities and for transactions with descriptions supplied by the system programmer.
  • Transaction Count is the total number of times that the transaction executed during the measurement session.
  • Avg Service Time (sec) shows the average wall clock time for the transaction's duration.

Click list_closed.gif next to a Transaction to view the following additional detail:

  • Pseudo-Csect is the name of the active pseudo-entity.
  • Description briefly explains the function of the pseudo-entity. Function descriptions appear for all Strobe pseudo-entities and for transactions with descriptions supplied by the system programmer.

Click list_closed.gif next to a Pseudo-Csect to view the following additional detail:

  • Module is the name of the active module or pseudo-module.
  • Description briefly explains the function of the module. Function descriptions appear for all Strobe pseudo-entities and for transactions with descriptions supplied by the system programmer.

Click list_closed.gif next to a module to view the following additional detail:

  • Section is the name of the active control section or pseudo-section. When measurement detects activity attributable to a section as part of a module running on behalf of a transaction, you can expand this line to view the section's CPU by code block.
  • Description briefly explains the function of the section. Function descriptions appear for all Strobe pseudo-entities and for transactions with descriptions supplied by the system programmer.

Important

For all module or section names that exceed eight characters, 

 generates a token, which is an eight-byte identifier. The token comprises the first four characters of the module or section name followed by a hyphen (-) and then the last three characters of the name. Refer to the Token Long Name Cross Reference report to reconcile all tokens with their long names.

User

  • User shows the user associated with a transaction.
  • CPU% Total shows the percentage of CPU activity with or without any concurrent I/O activity for the transaction.

Click list_closed.gif next to a User to view the following specific transaction detail.

  • Transaction is the name of the active transaction. If the transaction name contains unprintable characters, the report shows it in hexadecimal notation.
  • Description briefly explains the function of the transaction. Function descriptions appear for all Strobe pseudo-entities and for transactions with descriptions supplied by the system programmer.
  • Transaction Count is the total number of times that the transaction executed during the measurement session.
  • Avg Service Time (sec) shows the average wall clock time for the transaction's duration.

Click list_closed.gifnext to a Transaction to view the following additional detail:

  • Pseudo-Csect is the name of the active pseudo-entity.
  • Description briefly explains the function of the pseudo-entity. Function descriptions appear for all Strobe pseudo-entities and for transactions with descriptions supplied by the system programmer.

Click list_closed.gif next to a Pseudo-Csect to view the following additional detail:

  • Module is the name of the active module or pseudo-module.
  • Description briefly explains the function of the module. Function descriptions appear for all Strobe pseudo-entities and for transactions with descriptions supplied by the system programmer.

Click list_closed.gifnext to a module to view the following additional detail:

  • Section is the name of the active control section or pseudo-section. When measurement detects activity attributable to a section as part of a module running on behalf of a transaction, you can expand this line to view the section's CPU by code block.
  • Description briefly explains the function of the section. Function descriptions appear for all Strobe pseudo-entities and for transactions with descriptions supplied by the system programmer.

Important

For all module or section names that exceed eight characters, 

 generates a token, which is an eight-byte identifier. The token comprises the first four characters of the module or section name followed by a hyphen (-) and then the last three characters of the name. Refer to the Token Long Name Cross Reference report to reconcile all tokens with their long names.

Tip

  • Click an underlined module name to see an expanded description and performance improvement hints.
  • If high CPU execution within a transaction or ADABAS region was caused by library routines, SVC activity, or system routines (Db2, CICS, and so on), refer to the Attribution of CPU Usage report to determine what invoked this activity.
  • If a specific module is responsible for high CPU use within a transaction, refer to the Program CPU Usage report to identify the procedures or offsets within that module that are using the CPU.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*