Explanation
A request was made to start structure
rebuild processing or to stop in progress structure rebuild processing
for all structures in one or more coupling facilities, but the request
was not successful for one or more of the structures in that coupling
facility. Structure rebuild processing type can be either rebuild
or duplexing rebuild. The request was either due to a SETXCF command
or invocation of an IXLREBLD macro.
For rebuild
one of the following was specified:
- SETXCF START/STOP REBUILD
- IXLREBLD REQUEST=START/STOP
For duplexing rebuild one of the following
was specified:
- SETXCF START/STOP,REBUILD,DUPLEX
- IXLREBLD REQUEST=STARTDUPLEX/STOPDUPLEX
In the message text:
- strname
- The name of the structure.
- cfname
- The name of the coupling facility.
- STARTED
- The request was to start structure rebuild processing.
- STOPPED
- The request was to stop structure rebuild processing.
- reason
- One of the following:
- STRUCTURE NOT DEFINED IN THE CFRM ACTIVE POLICY
- The structure is not defined in the CFRM active policy and therefore
is not allocated in any coupling facility.
- STRUCTURE NOT ALLOCATED
- The structure is not allocated in any coupling facility.
- REBUILD HAS ALREADY BEEN INITIATED FOR THE STRUCTURE
- The structure rebuild process is already in progress for the structure.
Use the DISPLAY XCF,STR command to determine the type (rebuild or
duplexing rebuild0 and method (user-managed or system-managed) of
the structure rebuild process.
- REBUILD STOP HAS ALREADY BEEN INITIATED FOR THE STRUCTURE
- Stop has already been initiated for the structure
rebuild process.
- AT LEAST ONE ACTIVE CONNECTION INDICATED THAT REBUILD IS NOT ALLOWED
- Rebuild not permitted because IXLCONN with ALLOWREBLD=NO was specified
by at least one active connection.
- COUPLE DATA SET FOR CFRM NOT AVAILABLE
- The couple data set for CFRM is not available to this system.
- NO ACTIVE CONNECTIONS TO THE STRUCTURE
- The rebuild request would have resulted in a user-managed rebuild,
but the structure has no active connectors to participate in rebuild.
- REBUILD STOP IS IN PROGRESS FOR THE STRUCTURE
- Rebuild stop is in progress for the structure.
- STRUCTURE NOT IN REBUILD PROCESS
- The structure is not in the rebuild process.
- CLEANUP HAS BEGUN, REBUILD CANNOT BE STOPPED NOW
- Rebuild has entered the cleanup phase. Rebuild cannot be stopped
now.
- XES FUNCTION NOT AVAILABLE
- XES functions are not available. This can be because the hardware
necessary to provide XES functions is not present.
- AN UNEXPECTED ERROR OCCURRED
- An unexpected error occurred during rebuild processing.
- NO ELIGIBLE STRUCTURES FOUND IN COUPLING FACILITY
- On a rebuild start request, no structures eligible for rebuild
were found in the coupling facility specified. On a rebuild stop
request, no structures eligible for rebuild stop were found in the
coupling facility specified.
- COUPLING FACILITY NOT DEFINED IN THE CFRM ACTIVE POLICY
- The coupling facility is not defined in the CFRM active policy.
- NO COUPLING FACILITY PROVIDED BETTER CONNECTIVITY
- No other facility has better connectivity than the
current one. The rebuild, which was initiated because of a loss of
connectivity, would cause a further degradation in connectivity if
accepted. The system evaluated the set of active connections that
lost connectivity to the current structure as compared with the set
of active connections that would not be able to connect to the rebuild
new structure. The system terminates structure rebuild processing
because the result of the rebuild would cause additional active connections
to lose connectivity.
- NO COUPLING FACILITY PROVIDED BETTER OR EQUIVALENT CONNECTIVITY
- No other facility has better connectivity than the current one.
The rebuild would cause a degradation in connectivity as determined
by SFM system weights, if accepted.
Note: When this
reason is received for an operator initiated rebuild by STRNAME or
CFNAME and the installation needs to rebuild the structures, a SETXCF
START,REBUILD command specifying LESSCONN=CONTINUE can be used to
force the rebuild to continue despite this condition. Because this
might cause active connections to the structure to lose connectivity
to the structure, do not use LESSCONN=CONTINUE unless you understand
the impact to the application or subsystem. Consult the application
or subsystem documentation for recommendations.
- XCF SIGNALLING STRUCTURES CANNOT BE REBUILT USING CFNAME KEYWORD
- Due to the availability constraints of XCF Signalling Structures,
these structures cannot be rebuilt using the CFNAME option. They
must be rebuilt individually using the STRNAME option.
- DUPLEXING REBUILD NOT ALLOWED FOR THE STRUCTURE
- The structure does not support duplexing rebuild
for one of the following reasons:
- DUPLEX(DISABLED) was specified or defaulted to in the CFRM active
policy for the structure.
- There are failed-persistent connections that are unavailable until
a larger CFRM couple data set is made available.
- A user-managed duplexing rebuild could not be started
because:
- User-managed duplexing rebuilds are not supported for the structure
type.
- At least one active or failed-persistent connection specified
or defaulted to IXLCONN ALLOWDUPREBLD=NO.
- A system-managed duplexing rebuild could not be started
because:
- The structure has at least one active connector, and none of the
connectors (active or failed-persistent) specified IXLCONN ALLOWAUTO=YES
when connecting.
- A system-managed duplexing rebuild is not supported when a CFRM
policy change is pending for the structure.
- TYPE OF STOP REQUEST DOES NOT MATCH TYPE OF REBUILD IN PROGRESS
- SETXCF STOP,REBUILD or IXLREBLD REQUEST=STOP was issued to stop
a duplexing rebuild OR SETXCF STOP,REBUILD,DUPLEX or IXLREBLD REQUEST=STOPDUPLEX
was requested to stop a non-duplexing rebuild.
- DUPLEXING NOT ESTABLISHED, CANNOT STOP TO KEEP NEW STRUCTURE
- SETXCF STOP,REBUILD,DUPLEX,KEEP=NEW or IXLREBLD REQUEST=STOPDUPLEX
KEEP=NEW was requested and the rebuild has not yet entered the duplex
established phase. Stop requests to switch to the new structure are
not accepted until the rebuild enters the duplex established phase.
- ALREADY STOPPING IN THE OTHER DIRECTION
- The request to stop a duplexing rebuild was not processed because
duplex rebuild stop has already been initiated for this structure
name in the other direction. Either KEEP=OLD was requested and KEEP=NEW
type of duplex rebuild stop is in progress or KEEP=NEW was requested
and KEEP=OLD type of duplex rebuild stop is in progress.
- STRUCTURE HAS FAILED
- The rebuild start request was rejected for one of the following
reasons:
- The request was to start a duplexing rebuild and the structure
has failed. Duplexing rebuild is not allowed when the structure is
in the failed state.
- The rebuild start request would result in a system-managed rebuild.
System-managed rebuild is not allowed when the structure is in the
failed state.
- NO OTHER COUPLING FACILITY FOUND IN PREFERENCE LIST
- On a rebuild start request, either LOCATION=OTHER was specified
or defaulted to for a request to start a duplexing rebuild. In addition
to avoiding the facility in which the structure is currently allocated,
when a duplexing rebuild is stopped by the operator and DUPLEX(ENABLED)
is specified in the active policy, the subsequent duplexing request
initiated due to DUPLEX(ENABLED) will avoid the coupling facility
in which the previous instance of the structure was allocated when
the duplexing rebuild was stopped.
- STRUCTURE DOES NOT SUPPORT SYSTEM-MANAGED PROCESSES
- The structure does not support system-managed processes (for example,
rebuild) for one of the following reasons:
- The structure was not allocated in a coupling facility at or above
the minimum CFLEVEL required for the current process by a system supporting
system-managed processing.
- The structure has connections that have not been reconciled into
the CFRM active policy.
- Structure cleanup is in progress for the structure.
- CONNECTORS DO NOT SUPPORT SYSTEM-MANAGED PROCESSES
- The requested system-managed process cannot be initiated
for one of the following reasons:
- The structure has at least one active connector, and at least
one of the connectors (active or failed-persistent) did not specify
IXLCONN ALLOWAUTO=YES when connecting.
- A duplexing rebuild cannot be initiated for a structure that has
only failed-persistent connectors, and at least one of the failed-persistent
connectors did not specify IXLCONN ALLOWAUTO=YES when connecting.
- NO SUITABLE COUPLING FACILITY IN PREFERENCE LIST
- The requested system-managed process cannot be initiated for one
or more of the following reasons:
- The preference list is empty.
- The preference list contains no other coupling facility at or
above the minimum CFLEVEL required for the current process.
- The structure already exists in the only suitable coupling facility.
The same coupling facility can only be selected as the target for
the system-managed process if a CFRM policy change is pending for
the structure and one of the following is true:
- The policy change does not affect the SIZE or the INITSIZE parameters.
- The policy change affects the SIZE or the INITSIZE parameter and
all of the structure connectors specified IXLCONN ALLOWALTER=YES.
- A potentially suitable coupling facility does not
permit structure allocation.
- START REASON INAPPROPRIATE FOR SYSTEM-MANAGED PROCESS
- An IXLREBLD REQUEST=START invocation would have resulted in system-managed
processing (for example, rebuild). The request specified a STARTREASON
of LOSSCONN or STRFAILURE, which are not valid reasons for the requested
process.
- AT LEAST ONE CONNECTOR HAS LOST CONNECTIVITY TO THE STRUCTURE
- The requested system-managed process (for example, rebuild) cannot
be initiated because one or more of the connectors to the target structure
has lost connectivity to the coupling facility containing the target
structure.
- CFRM COUPLE DATA SET DOES NOT SUPPORT SYSTEM-MANAGED PROCESS
- The CFRM couple data set does not support the requested
system-managed process (for example, rebuild) because the CFRM couple
data set was not formatted at or above the minimum version for the
system-managed process requested. Use the DISPLAY XCF,COUPLE,TYPE=CFRM
command to determine the format of the CFRM couple data set. To support
system-managed rebuild the CFRM couple data set should be formatted
specifying “ITEM NAME(SMREBLD) NUMBER(1)”. For system-managed duplexing
rebuild, “ITEM NAME(SMDUPLEX) NUMBER(1)” should also be specified
when formatting a CFRM couple data set. Specifying “ITEM NAME(SMDUPLEX)
NUMBER(1)” implicitly formats a CFRM couple data set that supports
both system-managed rebuild and system-managed duplexing rebuild.
- STRUCTURE WITH NO CONNECTORS HAS NEVER BEEN SYSTEM-MANAGED DUPLEXED
- A system-managed duplexing rebuild cannot be initiated because
there are no connections to the structure and the structure has not
previously been duplexed using system-managed processing.
- ALLOCATION OF REBUILD NEW STRUCTURE FOR DUPLEXING REBUILD NOT
FEASIBLE
- Allocation of the rebuild new structure instance in support of
a duplexing rebuild is not feasible. Message IXC574I will contain
additional diagnostic information.
- STRUCTURE OBJECTS IN STORAGE-CLASS MEMORY
- The duplexing rebuild could not be started because storage-class
memory is in use.
- thread
- Used to tie together messages and XCF component trace records
for a particular coupling facility rebuild process.
System action
The system does not process the request
for that structure. Requested processing continues for those structures
which had structure rebuild processing successfully started or stopped.
Operator response
Contact the system programmer
for advice and assistance in determining whether to manually move
the structures or cancel the rest of the CFNAME level rebuild. Ensure
the IXC528I messages are preserved for the system programmer to use
in determining next action.
System programmer response
Examine the IXC528I messages
for the correct next action. Note that depending on the application
using the structure, structure rebuild may not be possible. Consult
the application or subsystem documentation for recommendations.
Source
Cross System Coupling Facility (SCXCF)
Module
Routing code
Descriptor code