Previous Topic: About Cross-Process Transaction TracesNext Topic: Enable Cross-Process Transaction Tracing


How to Trace Cross-Process Transactions

As a system administrator, your responsibilities often include monitoring systems, addressing known issues, and then triaging these issues. You trace these systems issues using CA Introscope to find the components that caused them. To find these components, you construct filter criteria on the Transaction Trace screen. You then analyze the results to determine the problem.

Use this scenario to guide you through the process:

The illustration shows how to select filter criteria and analyze trace results.

  1. Enable cross-process transaction tracing.
  2. Select the event duration and type filters.
  3. Select the CICS or IMS filters.
  4. Select the trace duration and agent filters, and start trace.
  5. Narrow the trace by excluding front-end elements.
  6. Analyze trace results

Important! Running a transaction trace can have a negative impact on the performance of the monitored application.

Completing this process lets you understand which filters criteria to select to find the problematic components and how to analyze the results.