IXC430E

Explanation
The indicated system has one or more members of
an XCF group that are not processing their XCF work in a timely manner.
The XCF work to be performed by a group member includes such things
as processing of messages by a message user exit routine, or processing
of group events by a group user exit routine.
A member is declared
stalled if there is any one work item that is not being processed
in a timely manner. A stalled member could be processing all its other
XCF work in a timely manner. See the explanation of message IXC431I
for a description of situations that could make a member appear stalled.
Note: It is very unlikely that the delays are caused by a
problem in XCF.
It may not be possible to determine the impact
to the sysplex, system, or relevant application without understanding
the type and nature of the work item(s) experiencing the delay. The
impact may not be limited to the stalled member if it provides services
to other applications or subsystems  the sysplex. Failure to process
this work in a timely manner could  account for delays or performance
problems elsewhere in the sysplex.
This message is not necessarily
issued if the stalled member happens to be an internal XCF member.
In
the message text: sysname
The name of the system on which the stalled members reside.

System action
XCF continues to monitor the situation. The message
is deleted when  no member stalled conditions exist on the indicated
system.
Messages IXC431I and IXC432I may be issued periodically
to the log to provide information about the current state of the stall
for a particular group member. XCF may issue abend x00C reason x020F0006
to initiate internal XCF self verification and other actions to address
the stall. The abend does not directly impact the stalled application.
 If an internal XCF problem is discovered, a dump will be taken. An
entry in logrec is made to document the situation even if no dump
is taken.                                                        

Operator response
Monitor the situation. If there does not seem
to be any detrimental impact, no further action may be needed. On
many occasions the system will successfully resolve the situation
during the course of normal processing. Issue DISPLAY XCF commands
on the indicated system to get more  information about the stalled
group members.Use DISPLAY XCF,GROUP to determine which groups have a stalled
member on the system. Message IXC331I lists the names of the groups
and indicates which ones have stalled members.
Use DISPLAY XCF,GROUP,grpname to determine
which members of group grpname are stalled. Message
IXC332I lists the names of the members and indicates which ones are
considered stalled by XCF.
Use DISPLAY XCF,GROUP,grpname,membername to
get detailed information about the member membername of
 group grpname. Message IXC333I provides status
information about the member and indicates what work appears to be
stalled.    

There may be other commands provided by the stalled application/subsystem
that will allow you to determine its status and/or alleviate the problem.
At the direction of the system programmer, you may need to obtain
dumps for problem diagnosis and/or terminate the indicated application. If multiple members appear to be stalled, or if other
indicators suggest work is not being processed, check the status of
the system because there may be an underlying problem affecting them
all.
The DISPLAY XCF,PATHOUT and DISPLAY XCF,PATHIN commands
may be issued to obtain detailed path status information to see if
a member  with a signaling stall appears to be impacting message delivery.

System programmer response
Check the status of the stalled application/subsystem.
On many occasions the system will successfully resolve the situation
 during the course of normal processing, in which case no further
action is warranted. Take appropriate action to correct the situation
or cancel/terminate the application. Before terminating the application,
issue the DISPLAY XCF,GROUP grpname,ALL command
as well as any application specific display commands that may be helpful in ascertaining status. Then collect the following
diagnostic information: system log, application log, and an appropriate
dump. In addition to application  specific diagnostic data, the dump
should include XCF data (SDATA=COUPLE). Then using its normal shut
down procedure, terminate  the application.

Source
Cross System Coupling Facility (SCXCF)

Module
IXCS1DCM

Routing code
2, 10

Descriptor code
11