A system is trying to join a sysplex, but has not yet established signalling connectivity with all the systems in the sysplex. Message IXC454I identifies the systems without signalling connectivity to the IPLing system.
Initialization processing stops until the operator replies to the message or re-IPLs the system.
Each time this response is chosen, stopped signalling paths on the IPLing system are started again since the circumstances which caused the path failure may have been resolved, thereby allowing the path to establish signalling connectivity. In some cases, the system will unconditionally stop paths that are in the midst of stop processing so that a new start request can be initiated for the path.
System initialization proceeds as soon as signalling connectivity is established. If connectivity is not established within nnn seconds, the system reissues message IXC455D to reprompt the operator. The maximum allowable value of nnn is 999 seconds.
Choose this response to stop and then start the signalling paths all over again (specify the same COUPLExx parmlib member when prompted). This action sometimes allows signalling connectivity to be established when the system does not seem to be making progress despite repeated use of the INTERVAL=nnn response.
The system issues message IXC207A to prompt the operator to specify a new COUPLExx member. All signalling paths are stopped, and the system starts the signalling paths identified in the new COUPLExx parmlib member.
If an incorrect reply is entered, the system issues message IXC208I to notify the operator of the error. The system then reissues message IXC455D.
Repeatedly specifying INTERVAL=nnn and/or repeatedly respecifying the COUPLExx parmlib member may cause a signalling path on another system to be stopped because the path exceeds its retry limit. In such cases the operator may need to enter a SETXCF START path command on that system to manually start the signalling path again. This situation is more likely to occur when the other system is running a release of MVS/ESA prior to SP510.
If the COUPLExx parmlib member is not correctly identified, request reinitialization of XCF (reply R) with the correct parmlib member. If the sysplex couple data set is not correctly identified, request reinitialization of XCF (reply R) with the correct couple data set. The COUPLExx parmlib member identifies the sysplex couple data set(s) to be used by this system.
Check the systems named in message IXC454I. If any of these systems is non-operational, use the VARY XCF command from an active system to remove the non-operational systems from the sysplex. When all non-operational systems have been removed from the sysplex, reply INTERVAL=nnn to request that the IPLing system continue to check for full signalling connectivity.
If there is no active system in the sysplex from which to issue the VARY XCF command, ensure that the systems named in message IXC454I actually are non-operational. Then, reply R to reinitialize XCF. If message IXC405D appears, reply I to complete the removal of all the systems from the sysplex and continue the initialization process.
Use the configuration chart to verify that the required signalling paths are correctly defined in the current COUPLExx parmlib member. If the signalling path definitions do not agree, you must either specify a different COUPLExx member or modify the current one. See the system programmer.
From an active system console, issue DISPLAY XCF,PATHOUT and DISPLAY XCF,PATHIN commands to obtain detailed information about the status of the signalling paths on each of the systems listed in message IXC454I. The DISPLAY command issues message IXC356I which identifies the status of the requested signalling paths. If the status of a path needed for signalling connectivity is STARTING, RESTARTING, LINKING, REBUILDING, QUIESCING, or QUIESCED, allow additional time for XCF to establish signalling connectivity (reply INTERVAL=nnn). If the signalling path is not established after several attempts, enter a SETXCF STOP path command to stop the path and then enter a SETXCF START command to start the path again.
Note particularly that additional time may be needed when a list structure is used for signalling. Signalling paths cannot be established through a list structure until an active system allocates the structure and initializes it for use by the XCF signalling service. If a list structure is the only means of establishing connectivity between a set of systems in the sysplex (not recommended since it represents a single point of failure), the first system in the set to become active in the sysplex will be the only system capable of allocating the structure. The remaining systems in the set cannot allocate the structure because they are not active in the sysplex, and they cannot become active in the sysplex until they establish signalling connectivity. Initialization of the remaining systems will be delayed until the first system in the set successfully starts the structure for signalling. Message IXC306I is issued when the structure is started successfully.
If a needed signalling path is not displayed, enter SETXCF START path command to start the path needed to establish signalling connectivity.
After resolving these path problems, reply INTERVAL=nnn on the IPLing system to allow XCF additional time to establish connectivity.
Examine the system logs from all systems for any additional data, especially messages about stopped paths or paths that failed to be started. If these messages originate from the IPLing system, and the paths needed for connectivity are either stopped or have not been successfully started, reinitialize XCF with the COUPLExx parmlib member that corresponds to the configuration. As a last resort, take a stand-alone dump from the IPLing system. View the dump with the Interactive Problem Control System (IPCS). Use the VERBX MTRACE command to view messages issued to the system log during the IPL.
Provide a configuration chart for the operator which describes the signalling paths used to establish signalling connectivity between every pair of systems in the sysplex. Ensure that the COUPLExx parmlib member correctly defines the signalling paths needed to establish signalling connectivity. Ensure that the necessary signalling paths are defined to systems already active in the sysplex. Ensure that the underlying hardware (devices, coupling facilities, coupling data sets) are operational and available to the appropriate systems. For list structures, ensure that the appropriate CFRM policy is active. Examine the system logs to determine why signalling connectivity could not be established. Messages IXC305I, IXC307I, and IXC467I identify path problems. Message IXC466I indicates when a signalling path is established.
Cross System Coupling Facility (SCXCF)
IXCT1CON
1, 2
2