SYSDUMP component trace
Before using this component trace, ensure that you have read:
SDUMP component trace is described by the following attributes:
- Trace buffers reside in 64-bit common storage area. Size is controlled by the TRACE CT operator command.
- Tracing is activated during DUMPSRV address space initialization.
- SDUMP CTRACE is captured at the end of the SDUMP capture phase and dumped at the end of the dump. If the trace data is needed at other times, you must request a new dump to collect the SDUMP CTRACE.
- The MVS™ component trace (CTRACE) external writer can also capture SDUMP CTRACE.
- Trace options revert to minimal event tracing when the operator turns the trace off.
The following table summarizes the information required to request a SYSDUMP component trace for SDUMP.
| Information | For SYSDUMP: |
|---|---|
| Parmlib member | CTIDMPxx; Default member: CTIDMP00 |
| Default tracing | Yes; full tracing |
| Trace request OPTIONS parameter | In CTIDMPxx and REPLY for TRACE CT command |
| Buffer |
|
| Trace records location | 64-bit Common Storage Area; trace data sets |
| Externalizing trace data | Included in every SDUMP; can also use external writer to write data to a trace data set |
| Trace formatting by IPCS | CTRACE COMP(SYSDUMP) |
| IPCS trace format OPTIONS parameter | None |
| Maximum trace entry size | 4050 bytes |