Start detail trace for active transactions
You can start a detail trace on long-running transactions that are still in-flight.
The in-flight transaction trace works like a detailed application trace except:
- The only selection criteria is the task number.
- Only a single instance of the transaction is traced.
- When enough data has filled the buffer, you can view the detail trace events, without waiting for the task to end.
- If you own the BMC MainView for CICS Management solution, you can use automation to start traces against executing tasks. See Using automation to start detail traces in the MainView for CICS Customization Guide.
The following table lists the line commands that you can use on task-related views to start, stop, purge, or display the trace for in-flight transactions.
Line commands for in-flight transactions
Command | Description |
|---|---|
STR | starts a detail trace for the in-flight task without logging The trace ID name begins with the lower case characters dt followed by a unique count and the task number. |
STL | starts a logged detail trace for the in-flight task The STL command displays the Trace Log Data Set Options dialog where you can edit and confirm the trace options. The trace ID name begins with the lower case characters dt followed by a unique count and the task number. |
ZTr | stops a previously started in-flight task trace |
DTr | displays the summary trace entries listed in the STRAC view for the in-flight task trace |
PTr | purges the trace entry for an in-flight task as long as there is only one entry found If there is more than one entry, a warning message is displayed indicating there are multiple traces found for this task. |
The STL command displays the Trace Log Data Set Options dialog that allows you to override and confirm the default trace options.
Trace Log Data Set Options dialog
| COMMAND ===> SCROLL ===> CSR |
| |
| Trace ID: dt000084 Title: IN-FLIGHT TRACE FOR ASMT Target: BCVCB660 |
| |
| Specify trace log data set options: |
| Number of logs 1 |
| First log DSN _________________________________________________________ |
| Low level qualifier of DSN must be V01 |
| Blank for default: BCVWSB.BCVCB660.dt000047.mmmdd.Thhmm.V01 |
| Names without quotes will be prefixed with BCVWSB |
| |
| Overwrite logs Y (Y/N - Action when all logs used) |
| |
| Volumes (BAB303,BAB304,BAB305,BAB306,BAB307,BAB308) |
| Primary CYLS 3 SMS Storage class |
| Data DSN Suffix D SMS Data class |
| SMS Management class |
| |
| |
| ENTER to process the request |
| CANCEL to cancel the request |
| HELP to view related help |
-------------------------------------------------------------------------------
The following table lists the primary task views that support the line commands.
Primary task views that support the in-flight transaction line commands
View | Description |
|---|---|
CTASK/TASK | Displays the status of active CICS tasks |
TASKCON | Displays information about CICS connection activity |
TASKDSA | Displays information about task DSA usage |
TASKFIL | Displays information about task file usage |
TASKLCK | Displays information about CICS tasks that have outstanding lock conditions |
TASKPGM | Displays information about task program usage |
TASKSES | Displays general information about count and timing information for session activity within a conversation to a connected CICS system |
TASKTDQ | Displays general information on Transient Data (TD) Queue utilization for all tasks |
TASKTSQ | Displays general information on Temporary Storage (TS) Queue utilization for all tasks |
Detailed trace information for any active task is displayed in the CT (Current Traces) view.
The active task has its own trace ID that uses the following naming convention:
dtCnnnnn
where:
Variable | Description |
|---|---|
dt | is a lowercase acronym indicating that this is a detail trace |
C | is a numeric value from 0 through 9 that indicates the number of times the trace was started for the same task |
nnnnn | is the CICS task number |
An example of multiple traces started for the same task follows:
CT view with in-flight traces
COMMAND ===> SCROLL ===> CSR
CURR WIN ===> 1 ALT WIN ===>
>W1 =CT================BCVCW653=*========ddmmmyyyy==hh:mm:ss====MVCICS===D====1
- Current Traces
Commands: ST (Start Application Trace) HT (History Traces) JOURNAL
Line CMDs: S (Select), W (Show), M (Modify), I (Switch)
Z (Stop), P (Purge), R (Replicate), Q (Quiesce Logging)
CM Trace ID Typ User ID Trace Title Start Date Start Status Log
-- -------- --- ------- ------------------------ ---------- Time -------- Stat
dt000044 Det BOLTSM2 IN-FLIGHT TRACE FOR PFIL 08OCT2011 08:10 Active
dt000047 Det BOLTSM2 IN-FLIGHT TRACE FOR ASME 08OCT2011 08:11 Active ACTV
dt000122 Det BOLTSM2 IN-FLIGHT TRACE FOR ASMC 08OCT2011 08:11 Complete
dt100122 Det BOLTSM2 IN-FLIGHT TRACE FOR ASMC 08OCT2011 10:11 Complete
dt200122 Det BOLTSM2 IN-FLIGHT TRACE FOR ASMC 08OCT2011 12:11 Active
Usage Notes
- Only one in-flight trace can be active for a given task at one time, but you can start up to 10 traces for the same task.
You must stop the currently active trace and wait until it has a status of Complete before you can start another trace for that task. In CT view with in-flight traces, traces dt000122 and dt100122 were stopped before the third in-flight trace, dt200122, was started.
- The in-flight trace remains in an active status after the task ends, but no additional trace data will be recorded.
- You cannot modify or replicate an in-flight trace.
For more information, see CT-view.