A system is trying to join a sysplex, but there are not enough paths available to establish signalling connectivity between this system and the sysplex.
The COUPLExx parmlib member must provide path definitions so that there will be at least one inbound and one outbound signalling path for every other active system in the sysplex. Either the definition for these signalling paths is missing from the COUPLExx parmlib member, or a failure kept the system from establishing the paths that were defined, or more time is needed to establish the signalling paths.
If the system is not yet active in the sysplex, XCF stops using the COUPLExx parmlib member and message IXC207A is issued. System initialization stops until the operator respecifies the COUPLExx parmlib member.
If the system is active in the sysplex, message IXC455D is issued. System initialization stops until the operator specifies how much longer the system should wait for signalling connectivity to be established. Alternatively, the operator must re-IPL the system.
If a failure prevented the signalling paths from functioning, the IPL-ing system and/or the system to which the signalling path is connected issue messages to explain the failure. Look especially for messages IXC305I and IXC307I which explain why start path processing failed or why the path was stopped.
Respond to message IXC455D or IXC207A as appropriate. Notify the system programmer if the problem persists.
If a failure kept the system from establishing valid signalling paths, see the operator response for the message issued to explain the signalling path failure.
Correct the COUPLExx specifications if signalling path definitions are missing.
If a failure kept the system from establishing valid signalling paths, see the system programmer response for the message issued to explain the signalling path failure.
Cross System Coupling Facility (SCXCF)
IXCT1CON
1, 2
12