Dealing with DB2 z/OS Hang/Wait situations:
APAR II13538: DEALING WITH HUNG COUPLING FACILITY CONNECTIONS IXLCONN REASON CODE 02010C27 0C27 02010C09 APAR status
When a DB2 member abnormally terminates, its connections to the coupling facility structures are put into a FAILING state by cross-system extended services for z/OS (XES). The FAILING DB2 member remains in this state until all surviving members of the group have responded to the XES Disconnected/Failed Connection (DiscFailConn) event for each structure. XES sends this event to each surviving member of the group so that the necessary recovery actions can be taken in response to the failed member.
For this reason it is important to preform the actions described in this informational APAR to recover from hung CF structure connections.
Other important informational APARs in this area are:
APAR II14016: DB2 RA10 R910 R810 HANG WAIT SUSPEND LOOP PROBLEM SUMMARY and for HANG or WAIT problems in DB2 DISTRIBUTED asid also see II08215 + II11164.