IXL015I strtype ALLOCATION INFORMATION FOR STRUCTURE structure-name CONNECTOR NAME connector-nameCONNECTIVITY=connectivityCFNAME ALLOCATION STATUS/FAILURE REASON------ --------------------------------cfname text [diag]

Explanation

A program attempted to connect to a coupling facility structure. The IXLCONN returned allocation information to the program in the IXLYCONA. This information is recorded in the hardcopy log for debugging if the results are unexpected. The actual disposition of the IXLCONN invocation can be found by examining message IXL013I (for IXLCONN failures) or message IXL014I (for successful IXLCONN connects).

In the message text:
strtype
One of the following:
  • STRUCTURE
  • REBUILD NEW STRUCTURE
structure-name
Name of the structure for which information is recorded.
connector-name
Connection name specified by the application issuing the IXLCONN or generated by XES, if applicable.
connectivity
Describes how the eligibility queue is sorted with regards to sysplex connectivity and SFM weight. connectivity can be one of the following:
  • BESTGLOBAL

    The connector specified CONNECTIVITY=BESTGLOBAL. When the coupling facilities are being ordered for allocation, the eligibility queue is primarily sorted by SFM weight. Note that all systems are considered to have equal SFM weight if no SFM policy is active.

  • DEFAULT

    The connector specified CONNECTIVITY=DEFAULT or did not specify CONNECTIVITY. When the coupling facilities are being ordered for allocation, the eligibility queue is primarily sorted by attribute weight.

  • SYSPLEX

    The connector specified CONNECTIVITY=SYSPLEX. When the coupling facilities are being ordered for allocation, any coupling facility that does not have connectivity to every system in the sysplex is removed from the eligibility queue.

cfname
Name of the coupling facility for which information is recorded.
text
Describes the status of the structure or the reason for the allocation failure. text can be one of the following:
STRUCTURE ALLOCATED
Structure is successfully allocated in the coupling facility. (Text corresponds to IXLCONN reason code CONARSNSUCCESS.)
NO CONNECTIVITY
The active CFRM policy indicates that this system does not have connectivity to the coupling facility. You must re-establish physical connectivity to the coupling facility and then reissue the connect request. (Text corresponds to IXLCONN reason code CONARSNNOCONNPOLICY.) See message IXC518I for possible reasons why the system does not have connectivity to the coupling facility.
FACILITY NOT IN ACTIVE POLICY
The coupling facility is not defined in the active CFRM policy. Verify that the set of coupling facilities currently in use in the sysplex is correct and matches the CFRM administrative policy most recently activated. (Text corresponds to IXLCONN reason code CONARSNFACILITYNOTINPOLICY.)
CONNECTIVITY LOST
Connectivity to the coupling facility has been lost. Reestablish physical connectivity to the coupling facility and then reissue the connect request. (Text corresponds to IXLCONN reason code CONARSNNOCONN.)
FACILITY FAILURE
The coupling facility has failed. (Text corresponds to IXLCONN reason code CONARSNFACILITYFAILURE.)
STRUCTURE FAILURE
The structure failed during the allocate process. (Text corresponds to IXLCONN reason code CONARSNSTRFAILURE.)
PARAMETER ERROR
The structure attributes are inconsistent with the model-dependent attributes of the coupling facility. Change the attributes of the structure based on the model-dependent limits returned for each coupling facility. (Text corresponds to IXLCONN reason code CONAPARAMETERERROR.)
INVALID STRUCTURE SIZE: invalidsize uinitsizesource MUST BE AT LEAST: initsize u
The structure size invalidsize used for the initial allocation was too small to allocate the structure with the attributes specified. The integer size unit u specification is K (kilobytes), M (megabytes), G (gigabytes), or T (terabytes). The minimum storage required to allocate the structure in this coupling facility with the requested attributes is initsize.
initsizesource
The source from which the initial allocation was determined. It can be one of the following:
INITSIZE
The initial allocation size was determined using the INITSIZE (or SIZE if not specified) specified in the CFRM policy. To fix the problem, increase the INITSIZE in the CFRM policy.
STRSIZE
The initial allocation size was determined using the STRSIZE specified on the IXLCONN invocation. See message IXL013I for more details on the failing application.
Note: The size unit displayed may be converted to the largest size unit that can be used to represent the size and avoids any rounding. For example, an initsize of 1048576K may be converted to an initsize of 1G for the purpose of messages. An initsize of 120000K will not cause the displayed size to be converted because it is not an even multiple of megabytes, gigabytes, or terabytes.

Ensure that you do not define SIZE substantially larger than INITSIZE. The amount of storage needed for the structure includes both control areas required by coupling facility control code and data areas used by the application. When allocating the structure initially, the system attempts to build all control structures that are required to support the maximum size of the structure.

The amount of storage required by the structure also increases as a function of the CFRM policy SCMMAXSIZE specification. Requesting a large amount of storage-class memory can significantly increase the minimum structure size.

Several factors determine how much storage is needed for control structures. Those factors include CFRM policy specification, application program specification on the IXLCONN service, coupling facility storage constraints, coupling facility storage increment and coupling facility level. See 'Requesting Structure Size' in 'Setting Up a Sysplex' for a complete discussion of structure allocation.

You can use the Coupling Facility sizer for help in determining structure SIZE, INITSIZE, and SCMMAXSIZE attributes.
INSUFFICIENT SPACE FOR space u
There was not sufficient space in the coupling facility to allocate the structure. The integer size unit u specification is K (kilobytes), M (megabytes), G (gigabytes), or T (terabytes).

There may be enough space in the coupling facility to allocate the structure, but the allocated structure size would be smaller than MINSIZE as specified or defaulted to in the CFRM policy. Check the size attributes (such as CONAFACILITYMINREQSIZE) returned to indicate the storage required to allocate the structure in this coupling facility with the requested attributes. When the policy specifies SCMMAXSIZE for the affected structure, space will also include an additional component representing the amount of storage necessary to support storage-class memory. Make sure there is a coupling facility in the preference list with sufficient space. (Text corresponds to IXLCONN reason code CONARSNINSUFFICIENTSPACE.)

ALLOCATION NOT PERMITTED
New structures cannot be allocated the coupling facility according to the active CFRM policy. (Text corresponds to IXLCONN reason code CONARSNALLOCNOTPERMITTED.)
When the coupling facility status is ALLOCATION NOT PERMITTED, one or more of the following subreason lines appear:
COUPLING FACILITY IS BEING REMOVED
The coupling facility is being removed from the active policy.
CFRM INDICATES COUPLING FACILITY FAILURE
The coupling facility has failed.
COUPLING FACILITY BEING RECONCILED
The coupling facility is in the policy reconciliation process.
COUPLING FACILITY IS IN MAINTENANCE MODE
The coupling facility is in maintenance mode.
XCF COMPONENT ERROR
An XCF component error has occurred. Call IBM® Service. (Text corresponds to IXLCONN reason code CONARSNXCFCOMPERROR.)
UNKNOWN HARDWARE ERROR
An unknown hardware error has occurred. Call IBM Service. (Text corresponds to IXLCONN reason code CONARSNUNKNOWN.)
RESTRICTED BY REBUILD OTHER
LOCATION=OTHER was specified on the rebuild request. Since the original structure was allocated in this coupling facility, the system did not use this coupling facility when trying to allocate the new structure for rebuild. If the structure allocation failed, make sure there is another suitable coupling facility in the structure's preference list. (Text corresponds to IXLCONN reason code CONARSNREBLDOTHER.)
RESTRICTED BY SAMESITEONLY
SAMESITEONLY was specified for the DUPLEX parameter on the structure definition. This allocation is for a duplexing rebuild and the CF is NOT defined as being at the same site as the CF containing the structure.
RESTRICTED BY REBUILD USERS
The system did not select the coupling facility for a rebuild connect request because the coupling facility does not support a number of users greater than or equal to the highest connection ID for the original structure. (Text corresponds to IXLCONN reason code CONARSNREBLDUSERSTOOSMALL.)
INSUFFICIENT CONNECTIVITY
The system did not select the coupling facility because the coupling facility id not provide the required connectivity, as specified by the CONNECTIVITY= specification. (Text corresponds to IXLCONN reason code CONARSNINSUFFCONNECTIVITY.)

The text is followed by eight characters of hexadecimal data, which is additional diagnostic information for “INSUFFICIENT CONNECTIVITY”.

PREFERRED CF ALREADY SELECTED
The system did not select the coupling facility because a more preferable coupling facility was already selected. (Text corresponds to IXLCONN reason code CONARSNPREFERREDCFSELECTED.)
When the coupling facility status is PREFERRED CF ALREADY SELECTED, the message displays one of the following lines that gives the primary reason why this coupling facility was placed lower than the previous one in the eligibility queue. Because of how different requirements are weighted, this information does not imply that all coupling facilities higher in the eligibility queue meet the requirement:
CONNECTIVITY REQUIREMENT MET BY PREFERRED CF
At least one connector to the current (old) structure does not have connectivity to this coupling facility, and there is at least one coupling facility or the reporting system does not have connectivity, and there is at least one coupling facility to which all connectors do have connectivity.
CFLEVEL REQUIREMENT MET BY PREFERRED CF
Another coupling facility was found with a more appropriate CF level.
FAILURE ISOLATION FOR DUPLEXING MET BY PREFERRED CF
This coupling facility is not failure isolated for duplexing, this is a duplexing rebuild, and at least one coupling facility exists that is failure-isolated for duplexing.
SPACE AVAILABLE FOR REQUESTED SIZE IN PREFERRED CF
This coupling facility does not have enough free space to meet the requested structure size, and at least one coupling facility exists that does have enough free space to allocate the structure at the requested size.
SPACE AVAILABLE FOR MINIMUM SIZE IN PREFERRED CF
This coupling facility does not have enough free space to meet the minimum required structure size to allocate the new structure instance based on the current object counts, and at least one coupling facility exists that does have enough free space to allocate the structure at the minimum size.
SPACE AVAILABLE FOR CHANGED DATA IN PREFERRED CF
This coupling facility does not have enough free space to meet the minimum required structure size to allocate the new structure instance based on the current in-use and changed object counts, and at least one coupling facility exists that does have enough free space to allocate the structure but with changed data only.
MORE SPACE AVAILABLE IN PREFERRED CF
This coupling facility does not have enough free space to allocate the structure at the requested size, and at least one coupling facility exists that also does not have enough free space but does have more space than this one.
STORAGE-CLASS MEMORY REQUIREMENT MET BY PREFERRED CF
This coupling facility does not have enough free storage-class memory to allocate the structure based on the current object counts, and there is at least one coupling facility that does have sufficient storage-class memory. Note that storage-class memory is not considered to be available if the coupling facility cannot accommodate the specified SCMALGORITHM.
SCMMAXSIZE REQUIREMENT MET BY PREFERRED CF
This coupling facility does not have enough total storage-class memory to accommodate the CFRM policy SCMMAXSIZE specification for this structure, and there is another coupling facility which does. Note that storage-class memory is not considered to be available if the coupling facility cannot accommodate the specified SCMALGORITHM.
MORE STORAGE-CLASS MEMORY AVAILABLE IN PREFERRED CF
This coupling facility does not have enough storage-class memory to allocate the structure with the amount specified by the CFRM policy and there is another coupling facility that also does not have enough storage-class memory but has more than this one. Note that storage-class memory is not considered to be available if the coupling facility cannot accommodate the specified SCMALGORITHM.
MORE STORAGE-CLASS MEMORY CONFIGURED IN PREFERRED CF
This coupling facility does not have enough total storage-class memory to accommodate the CFRM policy SCMMAXSIZE specification for this structure, and there is another coupling facility that also does not have enough total storage-class memory but has more than this one. Note that storage-class memory is not considered to be available if the coupling facility cannot accommodate the specified SCMALGORITHM.
NON-VOLATILITY REQUIREMENT MET BY PREFERRED CF
This coupling facility is volatile, non-volatility was requested, and there is at least one coupling facility that is non-volatile.
FAILURE ISOLATION REQUIREMENT MET BY PREFERRED CF
This coupling facility is not failure-isolated from all connectors, non-volatility was requested, and at least one coupling facility exists that is failure-isolated from all connectors.
STAND-ALONE REQUIREMENT MET BY PREFERRED CF
This coupling facility is not stand-alone, non-volatility was requested, and at least one coupling facility exists that is stand-alone.
EXCLLIST REQUIREMENT FULLY MET BY PREFERRED CF
This coupling facility contains a structure from the EXCLLIST, and at least one coupling facility exists that does not contain any structures from the EXCLLIST.
EXCLLIST REQUIREMENT MET BY PREFERRED CF
This coupling facility contains a simplex structure from the EXCLLIST, and at least one coupling facility exists that contains only old or new structure instances from the EXCLLIST.
SPACE REQUIREMENT MET BY PREFERRED CF
The following conditions exist:
  • System-managed duplexing rebuild is a possibility for the structure.
  • The coupling facility is not connected by CF-to-CF links to any other coupling facilities in the PREFLIST that have adequate space to allocate the structure if a duplexing rebuild is to be started.
  • At least one coupling facility exists that is connected by CF-to-CF links to a coupling facility that does have adequate space to allocate the structure.
REMOTE FACILITY REQUIREMENT MET BY PREFERRED CF
The following conditions exist:
  • System-managed duplexing rebuild is a possibility for the structure.
  • This coupling facility is not connected by CF-to-CF links to any other coupling facilities in the PREFLIST,
  • At least one coupling facility exists that is connected by CF-to-CF links to a remote facility, but the remote facility does not have adequate space to allocate the structure if a duplexing rebuild is to be started.
PREFERRED CF HIGHER IN PREFLIST
This coupling facility is lower in the PREFLIST than another coupling facility that is suitable for allocation.
ENFORCEORDER(YES) AND PREFERRED CF HIGHER IN PREFLIST
This coupling facility is lower in the PREFLIST than another coupling facility that is suitable for allocation; because ENFORCEORDER(YES) was also specified for the structure in the CFRM policy, XCF did not re-order the PREFLIST.
GREATER SFM WEIGHT CALCULATED FOR PREFERRED CF
This coupling facility has a lower SFM weight than another coupling facility that is suitable for allocation. For a structure without any active connectors, the SFM weight of each coupling facility is the sum of the SFM weights of all systems connected to that coupling facility. For a structure with active connectors, only systems with active connectors are used to determine the SFM weight of the coupling facility. Note that all systems are considered to have equal SFM weight if no SFM policy is active.
RESTRICTED BY OPERATOR STOP OF DUPLEXING REBUILD
The system did not select the coupling facility because the operator had previously stopped the duplexing rebuild and the structure that was not kept was allocated in this coupling facility. (Text corresponds to IXLCONN reason code CONARSNREBLDDUPLEXOTHER.)
POPULATECF NOT SUITABLE
Facility was not selected because it was not as suitable a location for the structure as its current location.
INSUFFICIENT CFLEVEL FOR CONNECTOR EXPLOITATION
The coupling facility CFLEVEL was not at or above the minimum required for an original connector or for the current set of active and failed-persistent connectors.
CROSSSITE DUPLEXING PREFERENCE MET BY PREFERRED CF
This coupling facility does not satisfy the CROSSSITE DUPLEX preference according to the CFRM active policy, and at least one coupling facility exists that does satisfy the CROSSSITE DUPLEX preference.
SAMESITE DUPLEXING PREFERENCE MET BY PREFERRED CF
This coupling facility does not satisfy the SAMESITE DUPLEX preference according to the CFRM active policy, and at least one coupling facility exists that does satisfy the SAMESITE DUPLEX preference.
CFLEVEL FOR POTENTIAL DUPLEXING MET BY PREFERRED CF
Duplexing rebuild is a possibility for the structure, and another CF was found with a potential duplex target which has a more appropriate CF level for a duplexing rebuild.
diag
Additional diagnostic information from ConaDiag4 that can be used when a nonzero value is returned that can be used by IBM Service Personnel in evaluating structure allocation processing. For example, this data could be helpful in determining why a particular coupling facility was selected rather than another. For more information, see the message text explanation of the data2 field in the documentation for message IXC574I.

System action

The system continues normal processing.

Source

Cross System Extended Services (XES)

Module

IXLC1CON

Routing code

1,2

Descriptor code

Note 26