Multiple trace capture modes
Events inside the CICS internal trace are captured by the C\Prof collection task (collector). Run C\Prof as a collection server servicing requests from either the ISPF dialog or the C\Prof Web UI, or submit ad hoc batch requests using JCL.
C\Prof has the following trace capture modes:
Profiling provides an application perspective of the trace. The C\Prof collector reads the internal trace to keep detailed information about transactions whilst the user interface provides near real-time access to the transaction information.
Reveal more about your CICS regions with the following capabilities:
Sift through thousands of transactions to quickly identify problems.
See response time broken down into processing parts. Move across program links, including regions using multiregion operation (MRO).
View a timeline of application calls. See EXEC CICS, DB2, MQ, IMS and Java statements together with the call's elapsed time, response code, and command text.
Display the trace events behind the transaction to quickly determine the root cause of a delay or problem.
Snap peeks back in time to capture what has recently happened in CICS. It does this by taking a point-in-time copy of the CICS internal trace and writes it to an auxiliary trace data set. Snap has no dependence on the CICS auxiliary trace facility. As such, it is very fast and has almost no impact on CICS.
To demonstrate, observe the following snap statistics for a snapshot of three CICS regions with a combined internal trace size of 200 MB:
- Job steps: 1
- Elapsed time: 1 second
- CPU time: 0.2 seconds
- Output: 3 auxiliary trace data sets totaling 275 DASD cylinders
- Impact on CICS: None
Once the auxiliary trace data sets have been written, you can analyze them using C\Prof, or using the CICS trace utility program.
Record to auxiliary trace data sets (ISPF)
Recording to auxiliary trace data sets provides a similar functionality to the CICS auxiliary trace facility but with far less overhead. Recording does not involve or require any changes to CICS.
Record for transaction profiling
Profiling provides an application perspective of the trace. C\Prof uses the CICS internal trace to keep detailed information about transaction behavior while the user interface provides near real-time access to the archived collection data. Transactions can be traced across multiple CICS regions while the regions themselves remain unaffected by the process.
Viewing a timeline of application calls made by a transaction (Web UI)
The C\Prof user interfaces are powered by the transaction information collected and stored in C\Prof archive data sets. Collection settings and storage attributes are defined by a simple configuration file.
A list of transactions collected by C\Prof (ISPF)
A list of transactions collected by C\Prof (Web UI)
Snap the CICS internal trace
The CICS internal trace is a circular buffer in which the oldest trace entries are continuously being overwritten with new entries due to ongoing activity in CICS. If a problem occurs in CICS, trace events relating to recent problems in CICS will persist inside the CICS internal trace for a period before they are eventually overwritten by newer entries. If we are fast enough, we can capture those trace events by taking a copy of the trace table. In C\Prof, this process is called a "snapshot".
Collecting from the trace: C\Prof snap versus the CICS auxiliary trace facility
Snap is very lightweight and typically completes within a few seconds, depending on the size of the trace. View the resulting auxiliary trace data set with the CICS trace utility print program, the C\Prof trace viewer, or import it into the C\Prof transaction profiler as required.
Record to CICS auxiliary trace data sets
A C\Prof recording to an auxiliary trace data set produces output identical to the CICS auxiliary trace facility but with a much lower processing burden. Configure and manage collection from the C\Prof ISPF dialog, use the C\Prof trace viewer to view the results, import data into the profiler, and share data quickly and easily with the C\Prof configuration file.
C\Prof trace events viewer