What data to gather for sysplex services problems

Now that you know what area of sysplex services your problem pertains to, the next table indicates what information you will need in a dump. Some of the information pertains only to SVC dumps, and some is for either an SVC dump or a stand-alone dump.

Note: The couple data sets are not dumped for an SVC dump or a stand-alone dump. A separate job must be run to dump this information. See the information about ADRDSSU output in Table 1.

Certain information is needed for every sysplex services problem, but they are included in the table for completeness. A quick guide to the areas that should always be dumped follows:

XCFAS (XCF address space)
All XCF data spaces
SDATA options
- XESDATA
- COUPLE
- RGN
- CSA
- SQA
- NUC
- LSQA
- TRT
- SUM

Table 1. Data to gather for sysplex services problem
Problem Area─> Data to Gather ║ ║ V	Connection Services IXLCONN IXLDISC IXLEERSP	Rebuild Processing	Mainline Services¹	Coupling Facility Interface	Couple Dataset Services	CFRM	XCF Signaling	SFM	ARM	XCF Client/Server	XCF Note Pad
	XES				XCF
SDUMP DATA
ASID=
Connector's address space (issued IXLCONN)	X	X	X	X		X
XCFAS	X	X	X	X	X	X	X	X	X	X	X
DSPNAME=
All related to issuer of IXLCONN	X	X	X	X		X
All XCFAS	X	X	X	X	X	X	X	X	X	X	X
SDATA=
XESDATA	X	X	X	X	X	X	X⁶	X		X⁶	X
COUPLE	X	X	X	X	X	X	X	X	X	X	X
RGN	X	X	X	X	X	X	X	X	X	X	X
CSA	X	X	X	X	X	X	X	X	X	X	X
SQA	X	X	X	X	X	X	X	X	X	X	X
NUC	X	X	X	X	X	X	X	X	X	X	X
LSQA	X	X	X	X	X	X	X	X	X	X	X
TRT	X	X	X	X	X	X	X	X	X	X	X
SUM	X	X	X	X	X	X	X	X	X	X	X
ADRDSSU Output for (Note ⁴)
ARM couple data sets									X
CFRM couple data sets	X	X			X	X	X			X	X
SFM couple data sets					X			X
Sysplex couple data sets	X	X			X	X	X			X	X
Component Trace Options for comp=SYSXCF
ARM									X
CFRM	X	X				X	X⁶			X⁶	X
GROUP
GRPNAME=
NOTEPAD											X
SERIAL					X	X
SERVER										X	X
SFM								X
SIGNAL							Note ³			X	X
STATUS								X
STORAGE
Component Trace Options for comp=SYSXES
ALL
CONFIG				X		X
CONNECT	X	X				X	X⁶			X⁶	X
HWLAYER	M	M	X	X		X	X⁶			X⁶	X
LOCKMGR			X
RECOVERY	X	X	X
REQUEST			X
SIGNAL	M	M	M
STORAGE
Output from IPCS Subcommand COUPLE
ARM									X
GROUP
SERIAL					X	X
SIGNAL							X			X	X
STORAGE
SYSPLEX								X
XCFSTACK					X	X	X	X
CFRM	X	X				X
Output from IPCS Subcommand XESDATA
CACHE			X
CONNECTION	X	X	X			X	X⁶				X
FACILITY			X	X		X
LIST			X				X⁶				X
LOCKMGR			X
LOCKRESOURCE			X
XESSTACK	X	X	X	X
Other IPCS Subcommands
CTRACE SYSXES	X	X	X	X		X	X⁶			X⁶	X
CTRACE SYSXCF	X	X			X	X	X	X	X	X	X
OTHER DATA
CTRACE output from external writer for SYSXCF or SYSXES	X	X	X	X	X	X	X	X	X	X	X
SYSLOG OUTPUT	X	X		X	X	X	X	X	X	X	X
LOGREC DATASET	X			X	X			X	X	X	X
IODF					Note ⁵
Note: LEGEND: X=definitely trace, M=might need to be traced, use other information to determine if this is a possible problem area. Mainline Services include: IXLLIST IXLCACHE IXLFCOMP IXLVECTR IXLLOCK IXLSYNCH IXLRT IXLUSYNC. For signaling path and connectivity problems, historical information is vital. Therefore, the system should execute using only default XCF tracing. Do NOT explicitly request the SIGNAL option for CTRACE for SYSXCF. For message traffic, message delivery and I/O, detail SIGNAL tracing is required and should be specified. Use the ADRDSSU utility to dump the contents of a couple dataset. Just taking an SVC dump or stand-alone dump will not give you the contents of the couple data sets. The following sample JCL indicates how to invoke the ADRDSSU utility: `//DUMP JOB MSGLEVEL=(1,1) //STEP1 EXEC PGM=ADRDSSU,REGION=4M //SYSPRINT DD SYSOUT=* //DD1 DD DISP=SHR,VOL=SER=SHR001,UNIT=3380 //SYSIN DD * PRINT DATASET(SYS1.PRIMARY) INDDNAME(DD1) /*` See z/OS® Data Facility Data Set Services Reference, SC26-4389, for more information on the ADRDSSU utility. The IODF that is defined for the coupling facility hardware might assist you in determining if connectivity problems exist due to an incorrect specification under HCD. Valid if signal structures are used for XCF signaling.