SYSBHI component trace

Before using this component trace

This topic assumes you have read:

Basic HyperSwap® socket support component trace is described by the following attributes:

Trace buffers reside in 64-bit common ECSA. Size is controlled by the TRACE CT operator command.
Minimal and unexpected event tracing is activated during Basic HyperSwap management address space initialization.
Component trace buffers externalized through:
- DUMP or SLIP operator command when the Basic HyperSwap management address space or a BHIHSRV address space is requested to be dumped.
- SVC dumps issued by Basic HyperSwap management address space or the BHIHSRV address space.
- MVS™ component trace (CTRACE) external writer.
Trace options revert to minimal event and exception tracing when the operator turns the trace off.

The following summarizes information for requesting a SYSBHI component trace for Basic HyperSwap.

Information	For SYSBHI:
Parmlib member	CTIBHIxx; Default member: CTIBHI00 (IBM® provides a sample in SYS1.SAMPLIB)
Default tracing	Yes; error; error events
Trace request OPTIONS parameter	In CTIBHIxx and REPLY for TRACE command
Buffer	Default: 4MB Range: 4MB - 64MB Size set by: CTIBHIxx parmlib member or REPLY to TRACE CT command Change size after IPL: Yes Location: 64-bit Common Storage Area (ECSA)
Trace records location	Address-space buffer; trace data sets
Request of SVC dump	By DUMP or SLIP command when dumping the HyperSwap Management address space or one of the BHIHSRV address spaces
Trace formatting by IPCS	CTRACE COMP(SYSBHI)
Trace format OPTIONS parameter	Yes