This site will undergo a maintenance outage on Saturday, 13 September beginning at 2:30 AM Central/1 PM IST for a platform upgrade. The downtime will be ~three hours.

Transaction Report

The Transaction reports show you which transactions were responsible for most of the CPU activity. These reports are helpful when you want to do the following:

  • Identify which transactions (tasks) are responsible for a majority of the CPU consumption
  • See which modules within those transactions contributed the most to that transaction’s CPU usage.

Transaction Summary

The Transaction Summary report (Transaction Summary Report) shows the CPU usage among transactions that were active during a measurement session. For a typical CA-IDMS-DC/CV region, this report shows the following four types of transactions:

  • User-mode CA-IDMS applications, such as those written by database application developers and those supplied with the CA-IDMS system and ADS/O (ACCMNT, BYE and ADS2 shown in Transaction Summary Report are examples of these applications)
  • System service tasks, such as those created by the CA-IDMS system to render support services (*DBRC*, *FACTOT*, *HELOT*, *LDRVR*, *MSTR* shown in Transaction Summary Report are examples of these tasks)
  • External run units, such as Central Version batch jobs that issue database requests to the CA-IDMS CV for execution
  • Other transactions, such as activity in CA-IDMS TCBs that cannot be associated with a CA-IDMS task (CA-IDMS, for CPU activity in CA-IDMS main task, .IDMTSS, for CPU activity in a security system task, .RHDCTCK, for CPU activity in the CA-IDMS ticker task shown in Transaction Summary Report are examples of these transactions).

In addition to naming the transaction and defining its function, the Transaction Summary report gives TRANSACTION COUNT and AVERAGE SERVICE TIME. The TRANSACTION COUNT is the total number of times the transaction actually executed during the measurement session. The AVERAGE SERVICE TIME is the average wall clock time between transaction start and transaction end. These measurements enable you to see variances in the execution of a transaction. The CPU TIME and AVERAGE SERVICE TIME reported is based on Strobe sampling and are not directly related to the TRANSACTION COUNT.

As shown in the report, ADS/O task ADS2 using 36.31% and CA-IDMS application task ACCTMNT using 21.11% account for more than half of the total CPU usage. The reports shown in the next section Transaction Usage by Control Section Reports provide detailed accounts of the CPU activity in these tasks.

Transaction Summary Report

image2021-2-9_11-48-30.png

The TRANSACTION COUNTS and AVERAGE SERVICE TIMES are reported under the CA-IDMS supplied ERUS task named RHDCNP3S. CA-IDMS supports using a user-defined batch program name as a task to invoke the ERUS TASK program, which is named RHDCNP3S. For a user-defined ERUS task, the TRANSACTION COUNTS and AVERAGE SERVICE TIMES will be reported under the user-defined task name, as in the following figure.

Program Section Usage Summary Report Using RHDCNP3S

image2021-2-9_11-49-28.png

Transaction Usage by Control Section Reports

The Transaction Usage by Control Section reports show, for each transaction that was active during the measurement session, the CPU time spent in each control section within each active module that was invoked to process that transaction.

The following figure shows the CPU activity within the ADS/O task ADS2, the transaction under which ADS/O dialogs execute. This report details all application and system modules that executed on behalf of all ADS/O dialogs observed during the measurement session. It also includes any 3GL subroutines called by the dialogs such as ACCTINT, which is a CA-IDMS application module written in assembler that is called to calculate interest.

Transaction Usage by Control Section Report for ADS/O Tasks

image2021-2-9_11-50-39.png

The following figure details the CPU activity used by all application and system modules that executed on behalf of the application task ACCTMNT. This task was created by the user and defined in the CA-IDMS Task Definition Table (TDT). Most of its activity is in the CA-IDMS database service modules IDMSDBMS, IDMSKEEP, and IDMSDBIO, indicating that this task is database intensive. ACCTMNT also invokes two user-written CA-IDMS programs called ACCTM100 and ACCTM200. Because both of these programs request DB/DC services primarily, the CPU activity directly attributed to them is relatively low.

Transaction Usage by Control Section Report for CA-IDMS Application Tasks

image2021-2-9_11-51-46.png

If programs show high CPU usage in the Transaction Usage by Control Section reports, you can see which sections of code within those programs cause the most CPU activity by referring to the appropriate Program Usage by Procedure reports.

Transaction Usage by Control Section Report for Central Version Batch Jobs shows the CPU activity within the CA-IDMS-DC/CV region on behalf of the Central Version batch job PAYROL01. In this example, Strobe uses the batch job name as the transaction name and shows that this job invoked only CA-IDMS service modules. Because this job makes database requests to the CA-IDMS-DC/CV region, it mainly invokes CA-IDMS modules that provide database services. These batch jobs often access the same database as online tasks and can degrade performance for other online applications and CV batch jobs. Slow response time in the online applications and longer-running CV batch jobs may indicate that the same database areas and datasets are involved.

Using the AutoStrobe concurrent measurement function can assist in evaluating overall system performance. It enables you to measure jobs that are executing in different, but related address spaces. For example, you could measure the CV batch job and the CA-IDMS-DC/CV region simultaneously, and then compare their Performance Profiles and see how each of them affects the other. Using Strobe to measure a batch region is described in Interpreting-Strobe-Performance-Profile-for-Batch-Regions.

Transaction Usage by Control Section Report for Central Version Batch Jobs

image2021-2-9_11-52-36.png

The following figure details the CPU activity used by the CA-IDMS FACTOTUM task *FACTOT*. This task was created by CA-IDMS to handle system-level services such as terminal paging, as indicated by the asterisks Strobe placed around the pseudo-taskcode name. The report reflects all CPU activity caused by FACTOTUM tasks observed in the CA-IDMS system during the measurement session. Detailing these system service pseudo-tasks shows the impact that they have on CA-IDMS system modules. These service tasks are embedded in the CA-IDMS system and support many functions used by applications, but they cannot be modified to improve performance.

Transaction Usage by Control Section Report for CA-IDMS Tasks

image2021-2-9_11-53-26.png

 

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