SYSXES component trace

Before Using This component trace

This topic assumes you have read:

The following summarizes information for requesting a SYSXES component trace for cross-system extended services (XES).

Information	For SYSXES:
Parmlib member	CTnXESxx; default member: CTIXES00 specified in COUPLE00 member
Default tracing	Yes; minimal; unexpected events
Trace request OPTIONS parameter	In CTnXESxx or REPLY for TRACE command
Buffer	Default: 336KB for connector-related SUB trace buffers. There are multiple instances of these trace buffers in use on the system 16M for the GLOBAL SUB trace buffer Range: 16KB - 16MB for connector-related SUB trace buffers The size for the GLOBAL SUB trace buffer cannot be changed. Size set by: CTnXESxx member or TRACE CT command Change size after IPL: Yes Location: Data space. In the REPLY for the DUMP command, specify SDATA=XESDATA and DSPNAME=(`asid`.IXLCTCAD) where `asid` is the ASID for address space XCFAS
Trace records location	Data-space buffer, trace data set
Request of SVC dump	By DUMP or SLIP command
Trace formatting by IPCS	CTRACE COMP(SYSXES)
Trace format OPTIONS parameter	Yes

SYSXES supports sublevel tracing. Tracing options are inherited through a hierarchy of trace levels. If you set trace options without specifying a sublevel, the options apply at the highest level, or head, of the hierarchy. A sublevel inherits its trace options from the next higher level, unless options are specified explicitly for the sublevel. If you set trace options for a sublevel, the options are inherited by any sublevels lower in the hierarchy. Figure 1 shows the hierarchical structure of SYSXES traces.

Figure 1. SYSXES SUB Trace Structure

                  ┌─────────────────┐
                  │SYSXES head      │
        ┌─────────┤    options      ├─────────┐
        │         └─────────────────┘         │
        ↓                                     ↓
┌────────────────┐               ┌──────────────────────┐
│                │               │                      │
│     GLOBAL     │        ┌──────┤      STRUCTURE       │
│   sublevel     │        │      │      sublevel        │
│                │        │      │                      │
└────────────────┘        │      └────────────┬─────────┘
        |                 │                   │
        |                 ↓                   ↓
        |            ┌─────────┐    ┌──────────────────────┐
        |            │         │    │                      │
        |            │ ADDRESS │    │   ADDRESS SPACE      │
        |            │  SPACE  │    │      sublevel        ├──────────┐
        |            │         │    │                      │          │
        |            └────┬────┘    └───────────┬──────────┘          │
        |                 │                     │                     │
        |                 ↓                     ↓                     ↓
        |           ┌───────────┐     ┌────────────────────┐    ┌───────────┐
        |           │           │     │                    │    │           │
        |           │ Connector │     │     Connection     │    │ Connector │
        |           │           │     │     sublevel       │    │           │
        |           │           │     │                    │    │           │
        |           └───────────┘     └────────────────────┘    └───────────┘
        |                                      |
        |                                      |
        |                                      |
  Non-connection                          Connection
     tracing                               tracing

Two classes of sublevel traces inherit the head trace options:

The global sublevel trace has its own trace buffer and controls tracing that is not related to any particular connection. Request GLOBAL tracing by specifying SUB=(GLOBAL).
Connection sublevels control tracing for a particular connection. Each connection has its own trace buffer. Connection sublevels are filtered hierarchically based on:
1. Structure name (STRNAME) of the coupling facility structure to which the system is connected
2. Address space identifier (ASID) of the address space from which the connection was made
3. Connection name (CONNAME) of the particular connector for which tracing is requested
Therefore, options specified for a particular structure name are inherited only by address spaces connected to that structure. Options specified for a particular address space are inherited only by connections that are connected through that address space.
Specify SUB=(strname), SUB=(strname.asid), or SUB=(strname.asid.conname), depending on the degree of specificity you need. Do not specify conname without specifying asid. Also, do not specify asid without specifying strname. When specifying a structure name or connector name on the SUB option, if the name contains special characters, it must be in quotation marks. If it is in quotation marks, upper and lower case characters are not the same. Therefore the case information is important and must identically match the name used by the system. Once the name is enclosed in quotation marks it becomes case sensitive.