00C

Reason Codes:

Explanation
Cross-system coupling facility (XCF) encountered
an error. See z/OS MVS Diagnosis: Reference for
more information on diagnosing sysplex problems.
The
reason code in register 15 is: Code
Explanation
00000004
A group member abended another group member using the IXCTERM
macro.
0000004C
Data Space IXCDSCBE cannot be created or accessed.
00000040
A group member abended another group member using the IXCTERM
macro.
00000044
Data space IXCDSMEM cannot be created or accessed.
00000048
Data space IXCDSCBD cannot be created or accessed.
0000005C
Either the system encountered an error while loading an XCF module
or an XCF module is missing from the nucleus.
00000100
Data Space IXCDSLO1 cannot be created or accessed.
00000104
Data Space IXCDSLK1 cannot be created or accessed.
00000108
Data Space IXCAP1DS cannot be created or accessed.
00000160
A member of an XCF group appeared to be causing signalling sympathy
sickness and was terminated. Message IXC615I is issued to indicate
which member was selected for termination.
02070000
A non-retryable error occurred and the function is considered
complete. If the message exit was not called, the signal has been preserved
and will be presented later.
If the message exit was called, the exit returned before the error
occurred, so the signal was delivered successfully.
XCF percolates to the task to which the member is associated.
 The task can retry in its recovery routine.  The system issues a
LOGREC data set error record and an SVC dump.  If the ABEND occurred
while XCF was in control, the system issues an SVC dump.

02070001
A non-retryable error occurred and the signal data might not have
been delivered to a member message exit. If the message exit routine was called, the failure occurred before
the exit could successfully return to XCF.
If the message exit was not called, XCF discarded the message,
in which case a signal was lost.
XCF percolates to the task to which the member is associated.
 The task can retry in its recovery routine.  The system issues a
LOGREC data set error record.  If the ABEND occurred while XCF was
in control, the system issues an SVC dump.

020F0006
 A member of an XCF group appears to be stalled.  XCF periodically
monitors each active member of an XCF group to determine whether the
member is processing its XCF work in a timely fashion.  The monitor
considers a member to be stalled if any of the following are true: A user group exit routine has not returned control to XCF in a
timely fashion
A user message exit routine has not returned control to XCF in
a timely fashion
A user message notify exit routine has not returned control to
XCF in a timely fashion
 An SRB scheduled to the member address space to perform internal
XCF processing has not returned control in a timely fashion
Events queued for processing by the user group exit routine have
not been processed in a timely fashion
Signals queued for processing by the user message exit routine
have not been processed in a timely fashion 
Signals queued for processing by the user message notify exit
routine have not been processed in a timely fashion
XCF work items queued for processing in the member address space
have not been processed in a timely fashion
"Timely" is generally defined as 30 seconds.  A member is
considered stalled if any of the listed conditions is true, even though
it may be processing other XCF work in a timely fashion.
The
DISPLAY XCF,GROUP command identifies stalled groups and members with
an asterisk (provided the stalled member is active on the system where
the command is executed).  Message IXC431I is issued to document a
stall condition that persists for more than 180 seconds.  ABEND 00C
reason 020F0006 is issued if the stall condition persists for more
than 195 seconds.  The ABEND does not impact the processing of the
stalled member as it is issued by the monitor while running under
a separate work unit in the XCF address space.  Message IXC430E is
issued if the stall condition persists for more than 300 seconds.
The
stall could be due to a user error, an internal XCF error, a system
error (such as storage overlay or lost SRB), or could be normal behavior
from which the system will recover. The system issues this ABEND to
initiate recovery actions to document the problem, and to verify/repair
internal XCF control blocks.  For signalling related stalls, the system
may provide replacement member message delivery cell(s) in hopes that
signal delivery can resume. If signal delivery does not resume, signalling
resources (for example, MMDCs or SIOCBs) may be consumed/lost for
the life of the member.  This consumption of signalling resources
could surface itself in many ways, such as: common storage growth,
degradation of signal delivery (possible to the point where no signals
can be delivered), rejected message-out requests, or repeated path
restarts.

020F000C
A member of an XCF group appears to be causing signaling sympathy
sickness.The DISPLAY XCF,GROUP command identifies stalled group
and member causing signaling sympathy sickness with an exclamation
point (in addition to the asterisk, since any member causing signaling
sympathy sickness has to be stalled as well).

020F000D
A member of an XCF group appears to be causing signaling sympathy
sickness and is about to be terminated.  When the MEMSTALLTIME interval
expires, XCF determines which member is most responsible for causing
the problem and initiates an SVC dump. Message IXC615I indicates which
member was selected for termination.
05070000
An error occurred while XCF was processing a Status Exit. XCF
continues processing the Status Exit. XCF tries to end the task
that owns the Status Exit.  The system writes a LOGREC data set error
record.  If the ABEND occurred while XCF was in control, the system
issues an SVC dump.

05070000
An error occurred while XCF was processing a Status Exit. XCF
continues processing the Status Exit. XCF tries to end the task
that owns the Status Exit.  The system writes a LOGREC data set error
record.  If the ABEND occurred while XCF was in control, the system
issues an SVC dump.

06010001
Internal error.
060B0001
An error occurred while XCF was processing a Group Exit. Some
group event information may have been lost. XCF tries to end the
task that owns the Group Exit.  Some group event information may have
been lost.  The system writes a LOGREC data set error record.  If
the ABEND occurred while XCF was in control, the system issues an
SVC dump.

060C0000
A non-retryable error has occurred on the first invocation of
the users Group Exit for this event. The exit will be rescheduled
and presented with the same event.
060C0001
Group information may have been lost due to either a non-recoverable
error in XCF or the users Group Exit has ABENDed two consecutive times.
 This code indicates the user may want to issue a IXCQUERY macro to
see what may have been lost.
081C0001
XCF forcibly ended processing of a SETXCF STOP command that was
stopping a signalling path.  This can happen when an operator specifies
UNCOND=YES on a SETXCF STOP command. The XCF signalling service
may have lost some messages as a result of this ABEND.  There may
be unpredictable results for the XCF groups whose messages got lost.

081CFF01
Unconditional stop processing is terminating the task that is
currently processing a signalling path START, STOP, or RESTART request.
08960002
Internal error.
0A1x0001 (x=4,5,6)
A couple data set has been taken over by another sysplex. The
data set is removed from service in the sysplex of which the issuing
system is a member. The system does not take a dump, but records the
error in LOGREC.
0A1x0070 (x=4,5,6)
I/O interrupt occurred with an invalid CCW address.
0A1x0074 (x=4,5,6)
XCF detected an I/O error while reading or writing to a couple
data set.  This may be a hardware error. If XCF cannot recover
from the I/O error, it may end one or more groups or members using
the couple data set, or else stop using the couple data set.  XCF
writes a LOGREC data set error record.

0A1x0078 (x=4,5,6)
Failure of a previous write to the couple data set was detected.
11050040
Data space IXCDSMEX cannot be created or accessed.
11050041
Data space IXCDSMEX cannot be created or accessed.
13C00851
System REXX exec
IXCL2XPU is missing from the System REXX library.
13C008xx
The system encountered an error executing System REXX exec IXCL2XPU.
16140003
Internal error.
1701xxxx
Internal error.
17090001
The system encountered an error executing System REXX exec IXCRXCDS,
or System REXX exec
IXCRXCDS is missing from the System REXX library.
1801xxxx
Internal error.
1803xxxx
Internal error.
1805xxxx
Internal error.
1808xxxx
Internal error.

System action
The system might issue a LOGREC
data set error record or an SVC dump.  Messages explaining the error
might precede this ABEND.  Depending on the reason code, the system
also does the following: Code
Explanation
00000004
XCF ends the group member.
08960002
The system initiates two MVS™ dumps.
1701xxxx
The system might issue a LOGREC data set error record or an SVC
dump.
1801xxxx
The system might issue a LOGREC data set error record or an SVC
dump.
1803xxxx
The system might issue a LOGREC data set error record or an SVC
dump.
1805xxxx
The system might issue a LOGREC data set error record or an SVC
dump.
1808xxxx
The system might issue a LOGREC data set error record or an SVC
dump.
Others
XCF tries to end a member of a group in the sysplex.  The system
may issue a LOGREC data set error record or an SVC dump.  Messages
explaining the error might precede this ABEND.

Operator response
Depending on the reason code, do the following: Code
Explanation
08960002
Contact your system programmer.
0A1x0074 (x=4,5,6)
Determine the cause of the I/O error.  If the error is caused
by a hardware problem, contact hardware support.
Others
See the operator response for the preceding messages. Obtain the
LOGREC data set and SVC dump, if one is issued. Notify the system
programmer.

The following reason codes represent errors
internal to the XCF component. Search problem reporting databases
for a fix for the problem. If no fix exists, contact the IBM® Support Center. Provide the LOGREC data set
and SVC dump, if one is issued.Reason Codes:
00000050 00000054 00000058 00000060 00000064 
00000068 0000006C 00000070 00000080 0000008C 
00000120 00000124 00000134 

02030001 02030002 02030003 02070002 020F0001 
020F0002 020F0003 020F0005 020F0007 020F0008 
020F0009 020F000A 02130001 02140001 02140002 
02140003 02140005 02160001 02160002 02160003 
02160005 02170001 02170002 02170003 02170004 
02170006 02170007 02170008 021A0001 02220001 
02220002 02220003 02220004 02220005 02220006 
022D0002 02330001 02330002 02380002 02430001 

0416xxxx 041Axxxx 041Dxxxx

05010084 05030088 05050090 

08030001 08030002 08040001 08060002 08080001 
08080002 080A0001 080C0001 08201002 08201003 
0820100C 08221001 08221007 08240001 08300001 
08300002 08321001 08340001 085A1006 08600001 
08600002 08690001 08691001 086B0001 08750001 
08750002 08750003 08780001 08780002 08781001 
087A1001 087E1002 08801004 08891001 088E0001 
08960001 08960002 08FB0100 08FD0001 08FF0001 
08FF0224 

09030001 09031001 09050001 09080001 09080002 
09080003 09080004 090A0001 090A0002 090E0001 
09110001 091C0001 

0F01008C 0F07006E 0F080060 0F08006C 0F0F008C 

12B10001 12B10002 

16030001 16050010 16090010 16090030 16090050 
16090070 160B0010 160B0030 160D0001 160F0001 
160F0002 160F0003 160F0004 160F0005 16100001 
16120001 16140001 16140002 16160001 16160002 
16160003 16160004 16160005 16160006 161E0002 
161E0003 161E0004 161E0005 161E0006 161E0007 
161E0008 16200001 16200002 16240030 16280001 
16280002 16280003 162A0001 162A0002 162A0003 
162A0004 162A0005 162A0006 162A0007 162A0008 
162A0009 162A000A 162A000B 162A000C 162A000D 
162A000E 162C0010 162C0030 16320001 16320002 
163C0001 163C0002 163E0001 163E0002 16400010 
16400020 16400030 16420001 16440010 16440030 
16440050 16440070 16440090 164400B0 164E0001 
164E0002 164E0003 164E0004 164E0005 16500001 
16500003 16500004 16500005 16500006 16560001 
16560002 16560003 16560004 165B0001 

1701xxxx 1801xxxx 1803xxxx 1805xxxx 1808xxxx

xxxx1008 xxxx100C

Note: 
For reason code 08960002,
the system initiates two MVS dumps.
Search problem reporting databases for a fix for the problem. If no
fix exists, contact the IBM Support
Center. In this case, both dumps should be gathered before contacting
the IBM Support Center.

System programmer response
Depending on the reason code, do the
following: Code
Explanation
02070001
Make sure that the program that owns the message exit has recovery
established for missing messages.  The recovery routine might do one
of the following: Send a request to other active group members requesting that they
resend the message.
Back up to a previous point in the program and continue processing
from there.
End the task if the function cannot tolerate any missing messages.

060B0001
Determine which program owned the Group Exit.  Make sure that
the program that owns the Group Exit has recovery established to handle
missing group event information.  The recovery routine should do one
of the following: Issue the IXCQUERY macro to determine whether group event information
was lost.
Back up to a previous point in the program and continue processing
from there.
End the task if the function cannot tolerate missing information.

08960002
Contact your system programmer.
1701xxxx
Contact your system programmer.
1801xxxx
Contact your system programmer.
1803xxxx
Contact your system programmer.
1805xxxx
Contact your system programmer.
1808xxxx
Contact your system programmer.

Programmer response
Depending on the reason code, do the following: Code
Explanation
08960002
Search problem reporting databases for a fix for the problem.
If no fix exists, contact the IBM Support
Center. Provide both MVS dumps
issued by the system.
Other internal reason codes
Search problem reporting databases for a fix for the problem.
If no fix exists, contact the IBM Support
Center. Provide the LOGREC data set and SVC dump, if one is issued.
Non-internal reason codes
See the system programmer response for the messages preceding
this abend.
If the problem persists, do the following: Format the SVC dump with the IPCS COUPLE subcommand.  Include
all the reports and the summary, detail, and exception levels for
each report.
Format the SVC dump with the IPCS CTRACE COMP(SYSXCF) subcommand
to obtain XCF component trace data.
Search problem reporting data bases for a fix for the problem.
 If no fix exists, contact the IBM Support
Center.  Provide the formatted SVC dump.

Source
Cross-system coupling facility (XCF)