Explanation
Cross-system coupling facility (XCF) or cross-system
extended services encountered a non-recoverable error and stopped
the system. The system also issues this wait state in response to
an operator request to stop the system. See z/OS MVS Diagnosis: Reference for
information on diagnosing sysplex problems.
The
right-most four bytes of the program status word (PSW) have the following
format:
x0rrrwww
where:
- x
- Irrelevant information.
- rrr
- A hexadecimal reason code indicating the reason for the failure.
- www
- The wait state code.
The reason code (
rrr) is one of the
following:
- 004
- The operator entered the VARY XCF,sysname,OFFLINE
command to remove the system from the sysplex.
- 008
- XCF lost signalling path connectivity between systems.
- 00C
- XCF will imply LOSS_OF_ETR_WAIT.
- 010
- XCF lost access to all couple data sets.
- 014
- During IPL, XCF removed a system from the sysplex.
- 020
- XCF removed the system from the sysplex.
One of the following
occurred:
- An I/O error was encountered by this system on either the primary
or the alternate couple data set after this system joined the sysplex
but before it could complete initialization of the couple data sets.
- An I/O error was encountered by another system in the sysplex
on either the primary or the alternate couple data set after this
system joined the sysplex but before it could complete initialization
of the couple data sets
- The operator on another system in the sysplex initiated a data
set transition by making a new alternate available via the SETXCF
COUPLE,ACOUPLE command or by replacing the primary couple data set
with the alternate couple data set via the SETXCF COUPLE,PSWITCH command.
This action was taken after the time that this system joined the
sysplex but before it could complete initialization of the couple
data sets.
- The operator replied DOWN to message IXC402D to specify that XCF
was to remove the system from the sysplex.
- 030
- An ETR failure on another system has occurred. The operator has
restarted that system. All other systems are stopped. Another system
is removing this system from the sysplex because of an external time
reference (ETR) failure. When there is an ETR failure, only one system
can remain in the sysplex. The remaining system removes all others
from the sysplex.
- 078
- The set of sysplex couple data sets in use by the sysplex was
changed while it was marking itself active.
- 07C
- System checks indicate that there are no allowable configurations
(XCF-local, monoplex, and sysplex) for this system based on current
settings.
- 08C
- XCF will not accept this system into the sysplex because a couple
data set inconsistency was detected.
- 09C
- The CFRM couple data set has been lost.
- 091
- Internal XCF error
- 104
- I/O has been prevented as a result of a system being fenced.
- 108
- The system was partitioned out of the sysplex as specified by
XCFPOLxx.
- 10C
- The system was found to be in a status update missing condition
and was partitioned out of the sysplex.
- 110
- The system experienced a signalling connectivity failure and was
partitioned out of the sysplex as specified by the Sysplex Failure
Management policy.
- 114
- This is a non-restartable wait state due to the loss of the ETR
link or the ETR itself.
- 11C
- Not enough storage to define subchannel notification vectors.
- 14C
- The wait state occurred because one of the names being declared
by the operating system was already declared via logical partition
definition at the hardware console, and the previously-declared name
does not match the name being declared by the operating system.
- 158
- The system has lost time synchronization with the Server Time
Protocol (STP) time source.
- 15A
- The system has been partitioned out of the sysplex because it
has lost time synchronization with the other systems in the sysplex.
- 160
- A member of XCF group SYSGRS, SYSMCS, or SYSXCF appeared to be
causing signaling sympathy sickness. The system was removed from the
sysplex to terminate the member.
- 164
- XES common storage control block CADS initialization failed.
- 17C
- Operator requested partitioning with the VARY XCF command and
REIPL AutoIPL option specified.
- 180
- Operator requested partitioning with the VARY XCF command and
SADMP AutoIPL option specified.
- 184
- Operator requested partitioning with the VARY XCF command and
SADMP and REIPL AutoIPL options specified.
- 188
- A coupling facility structure connector failed to provide a required
response within the time specified by the CFSTRHANGTIME interval defined
in the SFM policy (over and above the time required to determine that
the response is overdue, approximately 2 minutes). The system was
removed from the sysplex to terminate the connector.
- 18C
- A coupling facility (CF) structure connector encountered an unexpected
internal error during the processing of a CF request, structure-related
event, or other connection-related system processing. The system
was removed from the sysplex to terminate the connector in accordance
with the IXLCONN TERMLEVEL specification of the connector.
- 190
- Terminating an XCF member due to an IXCTERM request that requires
a system to be removed from the sysplex. This can occur for the
following reasons:
- The target member is running on a system that is in the early
phases of system initialization. During this time the system can not
terminate the member without terminating the system.
- The target member specified TERMLEVEL=SYSTEM when it joined its
group. The system will terminate the system on which the target member
resides.
XCF issues message IXC615I to identify the member that was the
target of the IXCTERM request. The message also identifies the system
from which the IXCTERM request was issued, and if possible, the XCF
group member that initiated the request.
- 194
- The system was removed from the sysplex to alleviate a critical
member impairment condition that could have been impacting other systems
in the sysplex. Messages IXC633I, IXC636I and IXC615I may have been
issued by the removed system to indicate which impaired XCF members
were causing the critical member impairment condition. See z/OS MVS System Messages, Vol 10 (IXC-IZP)
System action
The system enters a nonrestartable wait state
and issues message IXC220W or IXL004W.
Operator response
System programmer response
See the system programmer response
for message IXC220W.
Format the stand-alone dump with the following
IPCS subcommands:
Issue the D XCF,COUPLE command from a system currently
active in the sysplex. Check the connectivity to the volumes that
contain the couple data sets. Refer to z/OS MVS Setting Up a Sysplex for
additional information on couple data set placement for avoidance
of a single point of failure in couple data set availability.
Search
problem reporting databases for a fix for the problem. If no fix exists,
contact the IBM Support Center.
Provide the formatted stand-alone dump. Include all the reports and
the summary, detail, and exception levels for each report.
Source
Cross-system coupling facility (XCF)