How to Trace and Analyze Events › How to Trace Cross-Process Transactions › Analyze Trace Results › About Transaction Trace View › Tree View

Tree View

The Tree View is a hierarchical view of the components of the currently selected transaction trace. Each component represents a Java method or mainframe timing that the transaction completed. A component shows its duration and a percent of the total transaction lifetime that that duration represents.

The front-end traces that are generated from an instrumented Java application have the usual components that represent methods in the Java call stack. To drill down to the methods that invoked the back-end applications on the mainframe, expand the call stack in the tree.

Note: For the back-end traces generated by the Cross-Enterprise APM agent on z/OS, the tree view does not represent an actual Java call stack. Instead, it is a set of nested timings that are taken during processing of a CICS or IMS transaction.

The hierarchical structure of the transaction traces generated when processing a CICS or an IMS transaction are as follows.

The Transaction traces consist of a series of CICS and IMS components.

CICS Transaction Traces

Provides information about how time was spent in CICS transactions. Tracing a CICS transaction produces a CICS Suspend trace. If the transaction invokes DB2 queries, you also get a CICS DB2 trace.

The following property in the Cross-Enterprise_APM_Dynamic.properties file controls the generation of the CICS DB2 trace:

SYSVIEW.CICS.Transaction.Trace.DB2

The CICS Suspend trace has the following hierarchy of components as identified by their paths:

CICS Regions|region|transaction_name|task_number|Suspend|Transaction Lifetime

	Dispatch Time

		Program Load Time

	Suspend Time

		<Optional suspend time components>

The CICS DB2 trace has the following hierarchy of components as identified by their paths:

CICS Regions|region|transaction_name|task_number|DB2|Transaction Lifetime

Program program_name|SSID ssid|statement type Stmt# statement number

The CICS transaction traces have the following components:

Transaction Lifetime

Is the total time or transaction lifetime that equals the sum of input, processing, and output time.

Note: For more information, see CICS Transaction Lifetime Component Properties.

Dispatch Time

Is a child of Transaction Lifetime and represents time spent dispatched and doing work. The CPU time is the portion of dispatch time when the task is using processor cycles.

Note: For more information, see CICS Dispatch Time Component Properties.

Program Load Time

Is a child of dispatch time that shows how long the program took to load.

Suspend Time

Accompanies Dispatch Time and it represents time that is wasted in waiting for system resources.

Suspend time has extra child components representing nonoverlapping timings.

Suspend Time also includes various overlapping timings that cannot be represented as a hierarchy. These timings are represented as properties in the lower pane of the Trace View tab.

Note: High suspend times on a running transaction indicates an issue.

Note: Zero duration timing properties and components are not presented.

Note: For more information, see CICS Suspend Time Component Properties.

Program program_name |SSID ssid|statement type Stmt# statement number

Specifies the CICS DB2 statement component which provides the timings for the DB2 queries that the identified program invokes. The statement runs on the subsystem that is identified by ssid. The path contains the standard DB2 statement type such as SELECT, DELETE, FETCH, and INSERT. If CA-SYSVIEW is configured to generate statement numbers, then one is added to the path. The statement number indicates the line of the program which invoked the statement.

Note: For more information, see CICS DB2 Statement Component Properties.

IMS Transaction Trace

Specifies the information about how time was spent in an IMS transaction. Tracing an IMS transaction produces a single trace.

The IMS trace has the following hierarchy of components identified by their paths:

IMS Subsystems|subsystem name|Transaction|transaction name|Transaction Lifetime
		Input Queue Time
		Process Time
			optional components
		Output Queue Time	

The IMS transaction trace has the following components:

Transaction Lifetime

The total time or transaction lifetime equals the sum of input, processing, and output time which are its child components.

Note: For more information, see IMS Transaction Lifetime Component Properties.

Input Queue Time

The amount of time the input transaction waited in the message queue before being scheduled.

Process Time

Process Time has extra child components representing nonoverlapping timing events. These optional components are IMS Monitor type events such as, IWAITs, DL/1, and External Subsystem calls that occur during the transaction lifetime.

A single optional child component that contains properties for Event Count and Maximum Event Time represent multiple events. The Event Count property indicates the number of events. The Maximum Event Time property has the duration of the slowest instance of the event.

Output Queue Time

The amount of time the transaction output waited in the output message queue before being forwarded to its destination.