XESDATA subcommand — format cross system extended services data

Use the XESDATA subcommand to request formatting of information related to cross system extended services. The information is available in three levels:

The summary and detail levels provide diagnostic, configuration, and resource information about a particular area of cross system extended services.
The exception level provides an automated way of detecting incorrect data areas and unusual system conditions that may be helpful in problem determination. When an error is detected in control block chains or data content, the report contains information for the IBM® Support Center.

Note: If the dump is not caused by an error in the cross system extended services component, the system issues the following message:

IXL0200I XESDATA XESSTACK report cannot be run with the current dump.
         Reason: The dump did not result from an XES module failure.

In this case, if you know the address of the stack, and if the storage is in the dump, enter a CBFORMAT STRUCTURE(XESSTACK) subcommand.

Data selection and report type parameters limit the scope and extent of the information that appears in a report.

Syntax

    XESDATA

               { DETAIL     }
               { EXCEPTION  }
               { SUMMARY    }

-------- Report Type Parameters --------

               [ CACHE        ]
               [ CONNECTION   ]
               [ FACILITY     ]
               [ LIST         ]
               [ LOCK         ]   
               [ LOCKMGR      ]
               [ LOCKRESOURCE ] 
               [ XESSTACK     ]

-------- Additional Data Selection Parameters --------

                 [ ASID(asidlist)       ]
                 [ CFNAME(cfname)       ]
                 [ CONNAME(conname)     ] 
                 [ HASHVALUE(hashvalue) ]
                 [ JOBNAME(jobname)     ] 
                 [ LISTNUM(listnum)     ]  
                 [ LOCKMGRCONID(conid)  ]
                 [ LTENTRY(ltentry)     ] 
                 [ REQID(reqid)         ]  
                 [ REQUESTORCONID(conid)]
                 [ RNAME(rname)         ]
                 [ SOURCENAME(conname)  ]
                 [ STRNAME(strname)     ]
                 [ SYSNAME(sysname)     ] 
                 [ TARGETNAME(conname)  ]

-------- SETDEF-Defined Parameters -------------------------
Note: You can override the following SETDEF parameters.
See SETDEF subcommand — set defaults.

                [ ACTIVE | MAIN | STORAGE          ]
                [ DSNAME(dsname) | DATASET(dsname) ]
                [ FILE(ddname) | DDNAME(ddname)    ]
                [ PATH(path-name)     ]
                [ FLAG(severity) ]
                [ PRINT | NOPRINT ]
                [ TERMINAL | NOTERMINAL ]
                [ TEST | NOTEST ]

Data Selection Parameters
Use these parameters to select the level of information in the report. If you omit these parameters, the default is SUMMARY.
DETAIL
Requests a report showing detailed information for each of the specified objects or processes. An example is:
```
COMMAND ===>  XESDATA DETAIL
```
EXCEPTION
Requests a list of exceptional or unusual conditions for the specified objects or processes.
```
COMMAND ===>  XESDATA EXCEPTION
```
SUMMARY
Requests summary information for the specified objects or processes. SUMMARY is the default.
```
COMMAND ===>  XESDATA SUMMARY
```
Report Type Parameters
Use these parameters to select the type of report. If you specify more than one report type parameter, IPCS produces a report for each parameter. If you omit a report type parameter, the default is all report types.
CACHE
Requests information about outstanding cache requests for this system. Information is included for both the request as a whole, and operation-level information for the operation to each of the duplexed structure instances. The report output is:
- XESDATA (CROSS-SYSTEM EXTENDED SERVICES) REPORT
- CACHE SUMMARY REPORT
The output fields for each connection are:
Number of requests

Requests passing filters
An example is:
COMMAND ===> XESDATA CACHE
CONNECTION
Requests information about connectors to structures in the coupling facility. The report output is:
- XESDATA (CROSS-SYSTEM EXTENDED SERVICES) REPORT
- CONNECTION SUMMARY REPORT
The output fields for each connection specified are:
Structure type

Structure name

Connect token

Connect name

Recovery status

Diagnostic data

Status of a pending response for an event that was delivered to the event exit.

An indication of the user-managed or system-managed state of a rebuild process (both rebuild and duplexing rebuild).
Note that for duplexed structure instances, the report information will be split into sections that deal with the duplexed structure as a whole, and that deal with each of the allocated structure instances.
An example is:
COMMAND ===> XESDATA CONNECTION
FACILITY
Requests information about the coupling facilities and coupling facility structures known to the system. The report output is:
- XESDATA (CROSS-SYSTEM EXTENDED SERVICES) REPORT
- FACILITY SUMMARY REPORT
The output fields for each coupling facility are:
Name

Node descriptor

Facility ID

Control unit

Authority

Total space

Max structure ID

Connected indicator

Policy indicator

Pathing information
Paths valid

Paths online

Paths miscabled

Paths not operational

Remotely-connected coupling facilities, identified by their remote CF node descriptor (ND) and system identifier (SYID)
The output fields for each structure are:
Name

Facility

Structure ID

Type

Structure version

Relationship between duplexed structure instances
An example is:
COMMAND ===> XESDATA FACILITY
LIST
Requests information about outstanding list requests for this system. Information is included for both the request as a whole, and operation-level information for the operation to each of the duplexed structure instances. The report output is:
- XESDATA (CROSS-SYSTEM EXTENDED SERVICES) REPORT
- LIST SUMMARY REPORT
The output fields for each connection are:
Number of list headers

Number of lock entries

For each outstanding lock request in the serialized list:
Lock entry number

Lock ownership status

Lock data, if applicable

Queued request count

Requests passing filters

Number of requests
An example is:
COMMAND ===> XESDATA LIST
LOCK
Requests information about outstanding asynchronous coupling facility lock requests. Both simplex and duplex request data is included in the status information. An example is:
```
COMMAND ===>  XESDATA LOCK
```
LOCKMGR
Requests information about lock resources managed globally by the system. The report output is:
- XESDATA (CROSS-SYSTEM EXTENDED SERVICES) REPORT
- LOCKMGR SUMMARY REPORT
The output fields for each globally managed resource for each connection are:
Lock structure entry number

Resource name

Hash value

Diagnostic data

Indication of whether there is an outstanding asynchronous coupling facility request
An example is:
COMMAND ===> XESDATA LOCKMGR
LOCKRESOURCE
Requests information about the lock resources owned or requested by the system. The report output is:
- XESDATA (CROSS-SYSTEM EXTENDED SERVICES) REPORT
- LOCKRESOURCE SUMMARY REPORT
The output fields for each resource are:
Number of lock entries

Lock structure entry number

Connector this entry is managed by

Number of exclusive holders

Number of shared holders

Resource name

Hash value

Requested status

Requested event

Diagnostic data

Indication of whether there is an outstanding asynchronous coupling facility request
An example is:
COMMAND ===> XESDATA LOCKRESOURCE
XESSTACK
Requests information about cross system extended services execution flow. This report contains diagnostic data for the IBM Support Center. The report output is:
- XESDATA (CROSS-SYSTEM EXTENDED SERVICES) REPORT
- XESSTACK SUMMARY REPORT
The output fields contain diagnostic data.
An example is:
COMMAND ===> XESDATA XESSTACK

Additional Data Selection Parameters

The table shows the additional data selection parameters that apply to each report type.

Data Selection Parameter	Report Types
Data Selection Parameter	CACHE	CONNECTION	FACILITY	LIST	LOCK MGR	LOCK RESOURCE	XESSTACK	LOCK
ASID	X	X		X	X	X		X
CFNAME	X	X	X	X	X	X		X
CONNAME	X	X	X	X	X	X		X
HASHVALUE				X	X
JOBNAME	X	X		X	X	X		X
LISTNUM				X
LOCKMGRCONID						X
LTENTRY		X		X	X	X
REQID	X			X
REQUESTORCONID				X	X
RNAME		X			X	X
SOURCENAME		X
STRNAME	X	X	X	X	X	X		X
SYSNAME		X
TARGETNAME		X

ASID(asidlist)

Requests that only information about the address spaces for the listed ASIDs be included in the report.

The asidlist can be a single ASID, a range of ASIDs, or a list of noncontiguous ASIDs. When you specify a range, separate the first and last ASIDs in the range with a colon. When you specify a list, separate the list members with commas.

The ASID can be 1 through 65535. An ASID can be expressed in the notation X'nnn' or nnn for a decimal number.

An example is:

COMMAND ===>  XESDATA ASID(X'001A') LIST DETAIL

CFNAME(cfname)

Requests that only information about the specified coupling facility be included in the report.

The cfname can be a single coupling facility name or a list of names. Use commas to separate names in the list; do not enclose the names in apostrophes; and do not specify a range of names. To designate coupling facility names that begin with the same characters, use an asterisk (*) as a suffix. The asterisk denotes zero or more characters, up to the maximum length of the string.

An example is:

COMMAND ===>  XESDATA CFNAME(TESTCF)

CONNAME(conname)

Requests that only information about the connectors with the listed connector names be included in the report.

The conname can be a single connector name or a list of names. Use commas to separate names in the list; do not enclose the names in apostrophes; and do not specify a range of names. To designate connector names that begin with the same characters, use an asterisk (*) as a suffix. The asterisk denotes zero or more characters, up to the maximum length of the string.

An example is:

COMMAND ===>  XESDATA CONNAME(MYCONNAME1) LIST DETAIL

HASHVALUE(hashvalue)

Requests that only information about the listed hash values be included in the report. The hash value is derived from the resource name on the IXLLOCK macro and is used to determine what entry in the lock table is used. If you do not know the hash value, specify the resource name in the RNAME parameter.

The hashvalue can be a single value, a range of values, or a list of noncontiguous values. When you specify a range, separate the first and last values in the range with a colon. When you specify a list, separate the list members with commas.

An example is:

COMMAND ===>  XESDATA CONNECTION HASHVALUE(00000001) DETAIL

JOBNAME(joblist)

Requests that only information about the address spaces associated with the listed job names be included in the report.

The joblist can be a single job name or a list of job names. Use commas to separate job names in the list; do not enclose job names in apostrophes; and do not specify a range of job names. To designate job names that begin with the same characters, use an asterisk (*) as a suffix. The asterisk denotes zero or more characters, up to the maximum length of the string.

An example is:

COMMAND ===>  XESDATA JOBNAME(MAINASID) LIST DETAIL

LISTNUM(listnum)

Requests that only information about requests affecting the specified list header number or its entry be included in the report.

The listnum can be a single list header number or a list of numbers. Use commas to separate numbers in the list; do not enclose the numbers in apostrophes; and do not specify a range of numbers.

An example is:

COMMAND ===>  XESDATA LIST LISTNUM(1) DETAIL

LOCKMGRCONID(conid)

Requests that only information about resources managed by the specified connection identifier be included in the report.

The conid can be a single connection identifier or a list of identifiers. Use commas to separate identifiers in the list; do not enclose the identifiers in apostrophes; and do not specify a range of identifiers.

An example is:

COMMAND ===>  XESDATA LOCKRESOURCE LOCKMGRCONID(01)

LTENTRY(ltentry)

Requests that only information about the listed lock table entries be included in the report. The ltentry can be a single entry or a list of entries. When you specify a list, separate the entries with commas.

An example is:

COMMAND ===>  XESDATA LOCKMGR LTENTRY(20)

REQID(reqid)

Requests that only information about requests with the specified identifier be included in the report.

The reqid can be a single request identifier or a list of identifiers. Use commas to separate identifiers in the list; do not enclose the identifiers in apostrophes; and do not specify a range of identifiers. The identifiers can be expressed in the notation X'nnn' or nnn for decimal. To designate request identifiers that begin with the same numbers, use an asterisk (*) as a suffix. The asterisk denotes zero or more numbers, up to the maximum length of the string.

An example is:

COMMAND ===>  XESDATA LIST REQID(01)

REQUESTORCONID(conid)

Requests that only information about resources requested by the specified connection identifier be included in the report. The conid can be a single connection identifier or a list of identifiers. Use commas to separate identifiers in the list; do not enclose the identifiers in apostrophes; and do not specify a range of identifiers.

An example is:

COMMAND ===>  XESDATA LIST REQUESTORCONID(01)

RNAME(rname)

Requests that only information about the resources with the listed resource names be included in the report. The rname can be a single resource or a list of resources. When you specify a list, separate the list members with commas.

The resource can be expressed in the notation X'nnn' or nnn for a decimal number or characters. To designate resources names that begin with the same characters or numbers, use an asterisk (*) as a suffix. The asterisk denotes zero or more characters or numbers, up to the maximum length of the string.

An example is:

COMMAND ===>  XESDATA RNAME(MYLIST01) LIST DETAIL

SOURCENAME(conname)

Requests that only information about the connectors with the listed connector names from which signals are received be included in the report.

An example is:

COMMAND ===>  XESDATA CONNECTION SOURCENAME(MYCONNAME1)

STRNAME(strname)

Requests that only information about the specified coupling facility structure be included in the report. The strname can be a single coupling facility structure or a list of structures. Use commas to separate structures in the list; do not enclose the structures in apostrophes; and do not specify a range of structures. To designate structures that begin with the same characters, use an asterisk (*) as a suffix. The asterisk denotes zero or more characters, up to the maximum length of the string.

An example is:

COMMAND ===>  XESDATA STRNAME(LIST01)

SYSNAME(sysname)

Requests that only information about the specified system be included in the report. The sysname can be a single system name or a list of names. Use commas to separate names in the list; do not enclose the names in apostrophes; and do not specify a range of names. To designate system names that begin with the same characters, use an asterisk (*) as a suffix. The asterisk denotes zero or more characters, up to the maximum length of the string.

An example is:

COMMAND ===>  XESDATA CONNECTION SYSNAME(D13ID04)

TARGETNAME(conname)

Requests that only information about the connectors with the listed connector names to which signals are sent be included in the report. The conname can be a single connector name or a list of names. Use commas to separate names in the list; do not enclose the names in apostrophes; and do not specify a range of names. To designate connector names that begin with the same characters, use an asterisk (*) as a suffix. The asterisk denotes zero or more characters, up to the maximum length of the string.

An example is:

COMMAND ===>  XESDATA CONNECTION TARGETNAME(MYCONNAME1)

Example
For an example of XESDATA output, see the XES component in z/OS MVS Diagnosis: Reference.