The CTRACE command provides analysis of the CONTROLLER trace table.
Syntax
── CTRACE ─┬─────────────────────────────┬─────────────────────────────┤
├─ JOB ──<job number>─────────┤
└─ QUEUE ──<job queue number>─┘Explanation
The CONTROLLER portion of the MCP can be directed to capture certain trace information via the ODT command CO + TRACE. The trace table can be subsequently analyzed when captured in a memory dump through the use of the CTRACE command.
The initial implementation of the CONTROLLER tracing facility is limited to activity related to jobs and job queues.
When using this command in its simplest form, the entire trace table is analyzed.
Irrespective of the form of the CTRACE command selected, the contents of the table are presented in reverse chronological order, with the most recent entry presented first and the oldest entry presented at the end of the analysis.
Trace table entries may be selectively chosen by using either the JOB or the QUEUE modifiers. The description for these modifiers is as follows:
| Note: | Either JOB or QUEUE modifiers may be used in this command, but the presence of both is not allowed, and will be flagged as an error. |
JOB <job number>
Selects only those trace table entries that affect the <job number> provided following the JOB modifier.
QUEUE <job queue number>
Selects only those trace table entries that affect the provided <job queue number> following the QUEUE modifier.
<job number>
<job queue number>
The values for <job number> and <job queue number> are by convention decimal numbers. Use of the DEC <number>, or HEX <hexadecimal number> numeric forms are not acceptable. Use of the CTRACE command is limited to the analysis of memory dumps only, and cannot be used when analyzing program dumps.
The trace table is cyclical in nature, and thus the oldest table entries are lost as new entries are captured. Therefore it is possible that data for a selected <job number> or <job queue number> no longer exists within the trace table.
