IXC305I
{SETXCF START|START} dir REQUEST FOR pathname WAS NOT SUCCESSFUL: text

Explanation

The request to start an XCF signalling path was not successful.

During XCF initialization, message IXC305I may or may not be displayed on an operator console when a CTC device cannot be started as a signalling path.
  • The message is not displayed on an operator console the first time XCF initialization runs during an IPL.
  • If XCF initialization is to be restarted for an issue not related to signalling connectivity problems, the message is not displayed on an operator console.
  • If XCF initialization is to be restarted for an issue related to signalling connectivity, message IXC207A prompts the operator to respecify the COUPLExx parmlib member. The response to message IXC207A determines whether message IXC305I is displayed on an operator console. If the same COUPLExx parmlib member is specified, message IXC305I will be displayed. If a different COUPLExx parmlib member is specified, message IXC305I will not be displayed on the operator console, but IXC305I will always be displayed on the hardcopy log.
In the message text:
SETXCF START
An operator entered a SETXCF START path command.
START
The system initiated a start path request in response to some event or circumstance. System initiated start requests do not cause paths to become defined to XCF for signalling, but are otherwise functionally equivalent to SETXCF START path commands entered by an operator.
dir
The path direction specified for the unsuccessful start request. An inbound signalling path is used to receive signals from another system in the sysplex. An outbound signalling path is used to send signals to another system in the sysplex.
PATHIN
Indicates the path was to be started for inbound signal traffic.
PATHOUT
Indicates the path was to be started for outbound signal traffic.
PATH
Indicates the path direction was not specified or could not be determined. For system initiated requests, the existing XCF path definition was to be used to determine the direction(s) in which to start the path.
pathname
The name of the signalling path.
DEVICE dev
Indicates the CTC device with device number dev.
STRUCTURE strname
Indicates the XES list structure whose name is strname. A list structure can contain one or more individual list signalling paths.
STRUCTURE strname LIST num TO COMMUNICATE WITH SYSTEM sysname
Indicates the list signalling path using list number num within the XES list structure named strname to communicate with the system named sysname. The list number is zero if the path was not yet assigned a list within the structure, or if the initiator of the request could not determine which list was assigned for the path.
UNABLE TO ALLOCATE DEVICE
XCF was unable to allocate a device, probably because it is allocated to another component, such as global resource serialization, JES3, or Virtual Telecommunications Access Method (VTAM®). XCF will not use a device that is already allocated.
INVALID DEVICE NUMBER
The device number in the message text is not defined to the system.
DEVICE IS NOT A CTC ADAPTER
The unit type for the device is not a channel to channel (CTC) adapter. The unit type must be a CTC adapter in order for XCF to use the device as a signalling path.
STOP IS REQUESTED
A stop path command was initiated for the signalling path by either the operator or XCF. All processing for the start request is ended.
CHANNEL PATH VERIFICATION FAILED
An unrecoverable error interrupted XCF's verification process for the device.
I/O TIMEOUT DURING CHANNEL PATH VERIFICATION
The command failed during verification for the device's channel paths because of an I/O timeout.
NO CHANNEL PATHS LOGICALLY DEFINED FOR DEVICE
The command failed because the device has no logical channel paths leading to it.
NO CHANNEL PATHS PHYSICALLY DEFINED TO DEVICE
The command failed because the device has no usable physical channel paths leading to it.
DEVICE IS IN A PERMANENT ERROR STATE
The command failed because the device is in a permanent error state.
DEVICE NOT CONNECTED TO ANY SUBCHANNEL
The command failed because the device is not connected to a subchannel.
DEVICE IS NOT ONLINE
The device must be online if it is to be used by XCF for signalling. Start path processing was unable to vary the device online. If the device is varied online, XCF automatically attempts to start the signalling path.
SENSE ID CHANNEL PROGRAM FAILED
A request for sense data from the device failed. XCF must have the sense data to operate the CTC adapter correctly.
UNSUPPORTED CTC DEVICE TYPE
The device is not a CTC adapter type supported by XCF.
PATH UNCONDITIONALLY STOPPED
A stop command with UNCOND=YES was entered for the signalling path. The unconditional stop path request was initiated by either the operator or the system. All processing for the start command is ended.
UNEXPECTED ERROR
An unexpected failure occurred while processing the command.
NO CONNECTIVITY TO COUPLING FACILITY
The system processing the start command does not have connectivity to the coupling facility containing the specified structure. This situation could be due to operator commands such as VARY PATH OFFLINE, CONFIG CHP OFFLINE or hardware errors such as facility or path failures.
NO CONNECTION AVAILABLE FOR XCF
XCF was unable to connect to the structure. There was no connection available for XCF to use. Possible explanations include:
  • The maximum number of connectors to a structure has been reached for the CFRM active policy.
  • The model dependent limit on the maximum number of connectors to a list structure has been reached for the coupling facility that contains the list structure.
  • Some non-XCF connector is connected to the structure. A non-XCF connector can prevent XCF from connecting to a structure even though not all the connections are in use.
IXLCONN SERVICE COULD NOT CONNECT
An unexpected return and reason code was returned by the IXLCONN service when XCF attempted to connect to the structure.
DELAYED UNTIL STOP COMPLETES
A system initiated start command is delayed until stop path processing completes. The system will automatically start the path upon successful completion of the stop, provided the path remains defined to XCF for signalling.
UNABLE TO ALLOCATE A LIST FOR A SIGNALLING PATH
An unexpected error occurred while attempting to allocate a specific list within the structure for the list signalling path to use.
REMOTE SYSTEM NO LONGER USING STRUCTURE
The system to which the list path was to establish signalling connectivity is no longer using the structure for signalling.
STRUCTURE FAILURE
The structure failed.
SYSTEMS NO LONGER USING STRUCTURE IN OPPOSITE DIRECTIONS
The system with which the list path was to establish signalling connectivity is no longer using the structure for signalling in the opposite direction. List paths are established between those pairs of systems for which the structure has been defined for outbound use on one system and inbound use on the other system.
TOO FEW LISTS IN STRUCTURE
A list could not be allocated for the list path. Either the list structure was not allocated with enough lists for all the desired list paths or there is a list path in the midst of stop processing that has not yet deallocated its list.
LIST NOTIFICATION VECTOR TOO SMALL
The list notification vector for the list structure is not large enough for all the lists that need to be monitored for list transitions. There was not enough storage available in the Hardware System Area (HSA) for a larger vector.
REMOTE SYSTEM STOPPED USING LIST
The system to which the list path was to establish signalling connectivity is stopping its side of the list path.
DELAYED UNTIL STRUCTURE UNQUIESCED
The system processing the start command has quiesced all I/O operations to the structure. The start of the list path is delayed until I/O to the structure is again permitted.
UNEXPECTED HARDWARE ERROR
The signalling path could not be started due to an unexpected hardware error.
STRUCTURE NOT DEFINED IN ACTIVE POLICY
The indicated structure name is not defined in the CFRM active policy. The structure must be defined in the active policy in order to connect to the structure.
NEW CONNECTIONS TO STRUCTURE BEING PREVENTED
New connections to the requested structure are being prevented at this time for one of the following reasons:
  • All active connectors have confirmed the rebuild quiesce event. New connections will not be permitted until the rebuild or rebuild stop is completed
  • The structure is allocated in a coupling facility that is failed. New connections will not be permitted until the structure is rebuilt, or all connections disconnect causing the structure to be deallocated.
  • The coupling facility containing the structure is not available for use because policy reconciliation is in progress. New connections will not be permitted until policy reconciliation is complete.
  • New structure allocations for this structure name are not permitted because there is a pending policy change for this structure. New connections will not be permitted until the change is complete.
UNABLE TO DEFINE LOCAL LIST NOTIFICATION VECTOR
The list notification vector used to monitor list transitions could not be defined. The situation is most likely caused by a lack of storage in the Hardware System Area (HSA).
OTHER SYSTEMS USING STRUCTURE INCOMPATIBLY
Some other system is using the structure in ways that are not compatible with the protocols used by the system that processed the start command. The signalling path is stopped to avoid interfering with those systems.
COUPLE DATA SET FOR CFRM NOT AVAILABLE
The couple data set for CFRM is not available to this system. In order to connect to structures, the couple data set for CFRM must be available.

For a system that is IPLing into an existing sysplex, this failure also arises when the indicated structure is not defined in the CFRM active policy.

DELAYED UNTIL STRUCTURE DUMP COMPLETES
The connect to the structure could not complete because SVC Dump holds serialization on the structure.
STRUCTURE'S DISPOSITION IS KEEP
The structure already exists but was created with a disposition that allows it to persist (remain allocated) when there are no defined connections. Since the system that processed the start command does not use persistent structures, the structure is being used in ways that are not compatible with its protocols. The signalling path is stopped to avoid interfering with the other systems using the structure.
STRUCTURE'S LIST ENTRY SIZE TOO SMALL
The structure already exists but was created with a maximum size list entry that is not large enough to contain 65536 bytes of data. Since the system that processed the start command creates list entries containing up to 65536 bytes of data, the structure is being used in ways that are not compatible with its protocols. The signalling path is stopped to avoid interfering with the other systems using the structure.
STRUCTURE DOES NOT USE ADJUNCT DATA
The structure already exists but does not use adjunct data. Since the system that processed the start command uses adjunct data for its list entries, the structure is being used in ways that are not compatible with its protocols. The signalling path is stopped to avoid interfering with the other systems using the structure.
STRUCTURE DOES NOT USE DATA ELEMENTS
The structure already exists but does not use data elements. Since the system that processed the start command uses list entries containing data elements, the structure is being used in ways that are not compatible with its protocols. The signalling path is stopped to avoid interfering with the other systems using the structure.
STRUCTURE DOES NOT COUNT LIST ENTRIES
The structure already exists but does maintain list counts on a list entry basis. Since the system that processed the start command uses list entry counts, the structure is being used in ways that are not compatible with its protocols. The signalling path is stopped to avoid interfering with the other systems using the structure.
IPLING SYSTEM UNABLE TO WRITE STRUCTURE
XCF connected to the structure before the IPLing system became active in the sysplex. It is not possible to make any updates to the structure until after the system becomes active in the sysplex. However, once the IPLing system became active in the sysplex, it still could not make updates.
XES FUNCTION NOT AVAILABLE
XES functions are not available. This situation can arise when the hardware necessary to provide XES functions is not present.
STRUCTURE IN USE BY A NON-XCF CONNECTOR
The structure already exists, but one or more of the connectors is not XCF. Since it appears that the structure is in use by some other application, XCF disconnects from the structure to avoid interfering with that application. Structures to be used by XCF for signalling should be dedicated exclusively to XCF in order to ensure correct operation of the signalling service. Message IXC452I is issued to identify the non-XCF connectors.
DELAYED UNTIL REBUILD COMPLETES
The structure already exists, but there is a rebuild in progress. The system processing the start command elected not to participate in the rebuild.
DELAYED UNTIL AN ACTIVE SYSTEM ALLOCATES STRUCTURE
An system cannot allocate a structure for signalling until after the system is active in the sysplex and XES services are available. Systems attempting to IPL into a sysplex may be able to connect to an existing structure in use by XCF for signalling, but cannot create such a structure. The indicated structure does not yet exist.
USER SYNC POINT SET
The structure already exists, but there is a user sync point set. Sync points are set during rebuild processing, but are otherwise unexpected. If there is a rebuild in progress,'the start is delayed until the rebuild completes. If there is no rebuild in progress, an unexpected error has occurred. The error could be caused by a non-XCF connector using the structure.
STRUCTURE IN USE BY ANOTHER SYSPLEX
The structure already exists, but appears to be in use by systems in a different sysplex. Signalling paths are only permitted between systems participating in the same sysplex.
NOT ENOUGH FREE SPACE IN STRUCTURE FOR SIGNALLING
There is not enough space available in the structure for XCF to use it for signalling. After connecting to the structure, XCF verifies that there is enough space available to manage the structure and to be able to send at least one signal of the maximum supported message length. If the size of the structure is greater than or equal to the maximum structure size defined in the CFRM active policy, the size specified in the policy must be increased so that a larger structure can be allocated. If the allocated structure size is less than the size defined in the policy for the structure, the coupling facility containing the structure did not have enough space available to allocate the structure as large as the policy allowed. Either more space needs to be made available in the coupling facility, or the structure needs to be allocated in a coupling facility that can accommodate it.
UNABLE TO ALLOCATE STRUCTURE
Structure could not be allocated. Message IXC463I is written to the system log to explain why the allocation failed in each of the coupling facilities that was tried. The preference list and exclusion list in the CFRM active policy determines which coupling facilities are allowed to contain the structure.
DIAG073=n n n n n
Diagnostic data that is provided to assist IBM® service personnel with problem determination.
RC=n, RSN=n
Diagnostic data that is provided to assist IBM service personnel with problem determination.

System action

The signalling path remains defined to XCF as a signalling path (provided the system has not processed a SETXCF STOP path operator command). The signalling path is considered to be in an INOPERATIVE state' If the problems that prevent the path from starting are resolved, a new start command can be entered. In many cases, the system is able to detect circumstances for which the problems may have been resolved and automatically initiates a new start request. In the case of a list structure, the system may attempt to rebuild the structure.

Operator response

If the path was specified incorrectly, enter a SETXCF STOP path command so that the path is no longer defined to XCF for signalling. The stop prevents the system from using resources to manage the path definition and prevents attempts to start a path that is not intended to be used for signalling. Then enter a SETXCF START path command with the path specified correctly.

For a path that was correctly specified, any hardware, definitional, or capacity problems must be resolved before the path can be used for signalling. In some cases these problems are resolved automatically by the system. For other cases, manual intervention is required. The type of manual intervention needed varies according to the message text. After the problem is resolved, it is often the case that no further action is necessary as the system automatically starts the path again. If needed or desired, enter a SETXCF START path command to manually reinitiate start processing for the path' If the problem persists, do the following:
  1. Record the name of the signalling path, the text explaining why the start was not successful, and any diagnostic data presented with this message. The system programmer will need this information if it becomes necessary to contact IBM service for problem resolution.
  2. Enter the display commands appropriate to the particular type of signalling path' Record the results of the display commands to assist with problem determination.
  3. Contact hardware support as needed.
  4. Contact the system programmer as needed.
The following commands are useful for investigating unsuccessful start path requests for devices:
  • DISPLAY U,CTC,ALLOC,dev to display the allocation information for a CTC device with device number dev.
  • DISPLAY U,CTC,,dev to display the status of the device.
  • Enter a DISPLAY M=DEV(dev) to display the state of the channel paths to the device with device number dev.
The following commands are useful for investigating unsuccessful start path requests for structures and list paths. In some cases, it may be helpful to enter these commands on systems in the sysplex other than the one that was processing the start path request.
  • DISPLAY XCF,PATHOUT,STRNAME=strname to display detailed information about the use of the structure for signalling, including the state of the outbound list paths that have been started.
  • DISPLAY XCF,PATHIN,STRNAME=strname to display detailed information about the use of the structure for signalling, including the state of the inbound list paths that have been started.
  • DISPLAY XCF,STRUCTURE to display summary information about the structures defined in this sysplex.
  • DISPLAY XCF,STRUCTURE,STRNAME=strname to display detailed information about the indicated structure.
  • DISPLAY XCF,CF to display summary information about the coupling facilities defined in this sysplex.
  • DISPLAY XCF,CF,CFNAME=cfname to display detailed information about the indicated coupling facility as defined to the sysplex.
  • DISPLAY CF to display summary hardware information about the coupling facilities connected to a system.
  • DISPLAY CF,CFNAME=cfname to display detailed hardware information about the indicated coupling facility connected to a system.
  • DISPLAY M=CHP(chp) to display the state of the channel paths connecting a system to a coupling facility.
Depending on the message text, do the following manual intervention:
UNABLE TO ALLOCATE DEVICE
Display the allocation information for the device by entering the DISPLAY U,CTC,ALLOC,dev command. If appropriate, deallocate the device from the indicated user.

If the device is used by global resource serialization and is to be made available to XCF, deallocate it by entering the VARY dev,OFFLINE,FORCE command. Enter the command from both systems attached to that device.

NO CHANNEL PATHS PHYSICALLY DEFINED TO DEVICE
Enter the VARY command to make sure there are channel paths online for this device.
DEVICE IS NOT ONLINE
Enter the VARY command to vary the device online.
NO CONNECTIVITY TO COUPLING FACILITY
Enter a DISPLAY XCF,STRUCTURE,STRNAME=strname for information about which coupling facility contains the indicated structure. Enter a DISPLAY CF,CFNAME=cfname command to display the status of that coupling facility and the channel paths that connect the system to it, (cfname is the name of the coupling facility that contains the structure).

Enter a CONFIG CHP command to configure channel paths to the coupling facility, if needed. Enter a VARY PATH command to vary the channel paths online to the system, if needed.

NO CONNECTION AVAILABLE FOR XCF
Enter a DISPLAY XCF,STRUCTURE,STRNAME=strname command for information about the connectors to the structure. Enter a DISPLAY XCF,POLICY,TYPE=CFRM command for information about the CFRM active policy. Consult the system programmer as needed to determine whether to:
  • Perform the steps needed to activate a CFRM policy that has been formatted to support more connectors.
  • Enter a SETXCF START,REBUILD command to rebuild the structure in a coupling facility that supports more connectors.
  • Perform the steps needed to cause the non-XCF connector to disconnect from the structure.
LIST NOTIFICATION VECTOR TOO SMALL
UNABLE TO DEFINE LOCAL LIST NOTIFICATION
VECTOR
Enter a DISPLAY XCF,STR command to determine which structures are in use' For each structure that is in use, enter a DISPLAY,XCF,STR,STRNAME=inusestr, where inusestr is the name of an in use structure, to determine which applications are connected to the structure from this system. Consult the system programmer as needed to determine whether to reduce the number of connectors connected to structures from the system that processed the start command, or to modify the way in which the connectors are using the structure, or to perform the steps needed to increase the amount of storage in the Hardware System Area (HSA).
STRUCTURE NOT DEFINED IN ACTIVE POLICY
Consult the system programmer as needed to determine which CFRM policy should be made active. Enter a SETXCF START,POLICY,TYPE=CFRM,POLNAME=polname to activate the policy named polname which defines the structure.
COUPLE DATA SET FOR CFRM NOT AVAILABLE
Enter a DISPLAY XCF,COUPLE,TYPE=CFRM command to list the couple data set in use for CFRM. Consult the system programmer as needed to determine which coupling data set should be made available for CFRM. As needed, enter a SETXCF COUPLE command for a couple data set to be used for CFRM.
DELAYED UNTIL STRUCTURE DUMP COMPLETES
The system automatically starts the path again when the dump completes. However, if the dump does not complete within a reasonable time, enter a DISPLAY,XCF,STRNAME=strname command for information about the structure dump. To force the dump serialization to be released, enter a SETXCF FORCE,STRDUMPSERIAL command. Note however, that the requested structure dump may then fail to contain the data needed for problem determination.
DELAYED UNTIL REBUILD COMPLETES
The system automatically starts the path again when rebuild completes. However, if the rebuild does not complete within a reasonable time, enter a DISPLAY,XCF,STRNAME=strname command for information about the state of the structure and rebuild processing. One possible source of rebuild delay is a connector failing to respond to a rebuild event. Ensure that all connectors are operational and that there is signalling connectivity between all the systems in the sysplex so that responses can be processed. It may be necessary to force a connector to disconnect, which causes an implicit response to be made. Use the SETXCF STOP path command for each applicable direction to force XCF to disconnect from the structure on the system that processes the stop path command.
DELAYED UNTIL AN ACTIVE SYSTEM ALLOCATES STRUCTURE
Usually, no action is needed since the system automatically starts the path again once the system becomes active in the sysplex and XES services become available. So if an IPLing system is able to establish signalling connectivity with the other systems in the sysplex, no action is needed.

If an IPLing system is not able to establish signalling connectivity with the other systems in the sysplex, action may be needed on one or more of the systems already active in the sysplex before the IPL can proceed. Message IXC454I lists the systems for which signalling connectivity cannot be established. Consult the system programmer as needed to determine which of the these systems are to use the indicated structure to establish signalling connectivity with the IPLing system. The structure must be started as an XCF signalling path on those systems. If the active systems are themselves IPLing, the indicated structure will be started as a consequence of being defined as a signalling path in the COUPLExx parmlib member. If not, enter a SETXCF START path command on the active systems as needed to start the structure for signalling in the appropriate directions. Message IXC306I is issued when the structure is successfully started for signalling. After the active systems successfully start the structure for signalling, respond to message IXC455D on the IPLing system that needs to establish signalling connectivity.

System programmer response

Do the following:
  1. Examine the information provided by the operator.
  2. Ensure that the signalling path is correctly defined to XCF.
  3. Ensure that the hardware is correctly configured, defined to the system, and operational.
  4. Perform the actions suggested below for the indicated message text.
  5. Examine logrec error records for I/O errors or other hardware problems related to the signalling path.
  6. Examine the system log for other messages related to the signalling path. In the case of a list structure, messages IXC452I, IXC457I, and IXC463I are especially relevant.
  7. Obtain the following additional diagnostic information as appropriate for problem determination:
    • The XCF component trace table. The trace table must be obtained within 30 seconds of completion of the command if XCF detail tracing is enabled, and within a few minutes if just XCF default tracing is in effect. Default tracing is sufficient to resolve this problem.
    • For list structures, the XES component trace tables. Obtain both the global trace buffer and the connection related trace buffer.
    • A GTF I/O trace of the device.

If the problem persists, search problem reporting data bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Supply any diagnostic data presented as part of the start failed message, any output from the DISPLAY commands issued while investigating the problem, the system log(s), and any of the traces that were obtained.

Depending on the message text, the following actions are appropriate:
ALL CONNECTIONS TO STRUCTURE ARE IN USE
If the maximum number of connectors to a structure has been reached for the CFRM active policy, use the XCF couple data set format utility to create a new couple data set that supports more connectors. Run the XCF Administrative Data Utility to recreate the CFRM policy in the new couple data set. Have the operator make this couple data set available to the sysplex.

If the model dependent limit on the maximum number of connectors to a list structure has been reached for the coupling facility that contains the list structure, have the operator rebuild the structure into some other coupling facility that can support the required number of connectors. If so, consider modifying the preference list in the CFRM policy so that the structure is allocated in coupling facilities that can support the required number of connectors. If no suitable coupling facility is available, consider defining more list structures for signalling so that each list structures provides signalling connectivity for a subset of systems in the sysplex. The structures together can provide for full signalling connectivity but the number of connectors need not exceed the model dependent limits on the number of connectors.

If some non-XCF connector is connected to the structure, take whatever steps are needed to force that connector to disconnect.

LIST NOTIFICATION VECTOR TOO SMALL
UNABLE TO DEFINE LOCAL LIST NOTIFICATION VECTOR
There was not enough storage available in the Hardware System Area (HSA) of the system that processed the start command to allow a list notification vector of the required length to be defined. Either reduce the amount of storage being used in the HSA, or increase the amount of storage available in the HSA for creating list notification vectors. Reduce the amount of HSA storage being used by decreasing the number of connectors or changing the way connectors make use of their structure. For example, the size of the list notification vector required by the XCF signalling service is determined by the number of inbound list paths to be started. As another example, changing the number of buffers associated with a XES cache structure changes the amount of HSA storage required by the connector.
STRUCTURE NOT DEFINED IN ACTIVE POLICY
A CFRM policy containing a definition for the structure must be made active' As needed, run the XCF Administrative Data Utility to define the structure in a policy. Have the operator enter a SETXCF START,POLICY command to activate a policy that defines the structure.
COUPLE DATA SET FOR CFRM NOT AVAILABLE
Use the XCF format utility program to format a couple data set for CFRM. Ensure that the couple data set formatted for CFRM is available to the system.
NOT ENOUGH FREE SPACE IN STRUCTURE FOR SIGNALLING
If the size of the structure is greater than or equal to the maximum structure size defined in the CFRM active policy, use the XCF Administrative Data Utility to increase the structure size specified in a policy. Have the operator activate the updated policy.

If the allocated structure size is less than the size defined in the policy for the structure, the coupling facility containing the structure did not have enough space available to allocate the structure as large as the policy allowed. Either more space needs to be made available in the coupling facility, or the structure needs to be allocated in a coupling facility that can accommodate it. More space can be made available in a coupling facility by causing structures to be deallocated from that facility, or by decreasing the amount of space reserved for structure dumps. It may be necessary to modify the preference list or the exclusion list defined in the CFRM policy to allow the structure to be allocated in a more suitable coupling facility. Alternatively, it may be necessary to make a new coupling facility available for the sysplex to use.

UNABLE TO ALLOCATE STRUCTURE
Examine the system log for instances of message IXC463I for explanations of why the structure could not be allocated. Message IXC463I is issued for each coupling facility that was considered. Resolve the problems indicated by message IXC463I or make a suitable coupling facility available for use.

Source

Cross System Coupling Facility (SCXCF)

Module

IXCT1FSR, IXCT1FSS, IXCT1ISS, IXCT1PCC

Routing code

1,2

Descriptor code

5,12.

Parent topic: IXC messages