Explanation
A request to rebuild a structure used for signalling
was not successful.
In the message text:
- strname
- The name of the XES list structure that was to be rebuilt.
- STOP IS REQUESTED
- A stop path command was initiated for the signalling path by either
the operator or XCF. All processing for the rebuild request is ended.
- 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 rebuild request
is ended.
- UNEXPECTED ERROR
- An unexpected failure occurred while processing the command.
- NO CONNECTIVITY TO COUPLING FACILITY
- The system processing the rebuild command does not have connectivity
to the coupling facility containing the rebuilt structure. This situation
could be due to operator commands such as VARY PATH OFFLINE or 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
all the connections are not in use.
- UNEXPECTED HARDWARE ERROR
- The signalling path could not be rebuilt 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.
- 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 in the CFRM
active policy determines which coupling facilities are allowed to
contain 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
rebuild request.
- DELAYED UNTIL STOP COMPLETES
- A system initiated rebuild request 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.
- STRUCTURE FAILURE
- The structure failed.
- 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 rebuilt structure was created with a disposition that allows
it to persist (remain allocated) when there are no defined connections.
Since the system that processed the rebuild request does not use persistent
structures, the structure is being used in ways that are not compatible
with its protocols.
- STRUCTURE'S LIST ENTRY SIZE TOO SMALL
- The rebuilt structure 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 rebuild 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.
- STRUCTURE DOES NOT USE ADJUNCT DATA
- The rebuilt structure does not use adjunct data. Since the system
that processed the rebuild request uses adjunct data for its list
entries, the structure is being used in ways that are not compatible
with its protocols.
- 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
- One or more of the connectors to the rebuilt structure 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.
Message IXC452I is issued to identify the non-XCF connectors.
- STRUCTURE IN USE BY ANOTHER SYSPLEX
- The rebuilt structure appears to be in use by systems in a different
sysplex. Signalling paths are only permitted between systems participating
in the same sysplex.
- TOO FEW LISTS IN STRUCTURE
- The structure does not have enough lists available.
The rebuilt
structure was not allocated with the minimum number of lists required
for XCF to make use of the structure for signalling. It could be that
the structure was allocated by a non-XCF connector, or that there
was not enough space available to allocate the structure with the
desired number of lists.
- NOT ENOUGH FREE SPACE IN STRUCTURE FOR SIGNALLING
- There is not enough space available in the rebuilt 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.
- UNEXPECTED ERROR
- An unexpected failure occurred while processing the command.
- IXLREBLD REQUEST(START) FAILED
- XCF attempted to initiate a structure rebuild by invoking the
IXLREBLD macro but the START rebuild request failed.
- REBUILD WAS STOPPED AND ORIGINAL UNUSABLE
- Rebuild processing was stopped, so the rebuilt structure will
not be used. The original structure is not usable by this system,
so the system will stop using the original structure.
- REBUILT NOT USABLE, NEED ORIGINAL FOR SIGNAL CONNECTIVITY
- This system is not able to use the rebuilt structure, so it considered
disconnecting from the structure so that other systems could proceed
with using the rebuilt structure. Since disconnecting from the original
structure would lead to a loss of signalling connectivity, the rebuild
is stopped.
- STOP REBUILD, WOULD LOSE SIGNAL CONNECTIVITY
- The rebuild is stopped since this system would lose signalling
connectivity with one or more systems if it were to use the rebuilt
structure.
- REBUILT NOT USABLE, ORIGINAL NOT USABLE
- Neither the original structure nor the rebuilt structure can be
used by this system.
- STOP REBUILD, WOULD LOSE SPACE
- A rebuild was requested in order to increase the amount of usable
space in the structure. The rebuild is stopped since the rebuilt structure
did not resolve the space problem.
- STOP REBUILD, WOULD LOSE LISTS
- A rebuild was requested in order to increase the number of lists
in the structure. The rebuild is stopped since the rebuilt structure
did not resolve the problem with the number of lists.
- REBUILT NOT USABLE
- This system cannot use the rebuilt structure.
- DIAG073=n n n n n
- Diagnostic data that is provided to assist IBM® service personnel with problem determination.
System action
If possible, the system reverts to using the original
structure. If the original structure is not usable, the system initiates
stop path processing.
Operator response
If stop path processing was performed for
the structure, enter a SETXCF START path command to try to start the
structure again.
If the system reverts to using the original
structure, resolve any hardware, definitional, or capacity problems.
Then enter a SETXCF START,REBUILD command to try rebuilding the structure
again.
If the problem persists, do the following:
- Record the name of the signalling path, the text explaining why
the rebuild 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.
- Enter the display commands that are relevant to the problem. Record
the results of the display commands to assist with problem determination.
- Contact hardware support as needed.
- Contact the system programmer as needed.
The following commands are useful for investigating unsuccessful
rebuild requests for structures. In some cases, it may be helpful
to enter these commands on systems in the sysplex other than the one
that was processing the rebuild 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:
- 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.
- 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 rebuild 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).
- DELAYED UNTIL STRUCTURE DUMP COMPLETES
- 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.
System programmer response
Do the following:
- Examine the information provided by the operator.
- Ensure that the hardware is correctly configured, defined to the
system, and operational.
- Perform the actions suggested below for the indicated message
text.
- Examine logrec error records for I/O errors or other hardware
problems related to the signalling path.
- Examine the system log for other messages related to the signalling
path. Messages IXC452I, IXC457I, and IXC463I are especially relevant.
- 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 the problem 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.
- XES component trace tables. Obtain both the global trace buffer
and the connection related trace buffer.
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 rebuild 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:
- NO CONNECTION AVAILABLE FOR XCF
- 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.
- 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 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.
- 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
Routing code
Descriptor code