A structure rebuild process is being stopped.

In the message text:

rebuildtype

One of the following:

REBUILD

A structure rebuild process is being stopped. The type of process is either rebuild or duplexing rebuild and the method is user-managed.

SYSTEM-MANAGED REBUILD

A system-managed rebuild is being stopped.

PENDING REBUILD

A pending rebuild from a POPULATECF rebuild request is being stopped.

SYSTEM-MANAGED DUPLEXING REBUILD

A system-managed duplexing rebuild is being stopped.

strname

Name of the structure for which information is recorded.

action

The action that is taken when the rebuild process is stopped. action is one of the following:

TO FALL BACK TO THE OLD STRUCTURE

The rebuild process is stopping to fall back to the old structure.

TO SWITCH TO THE NEW STRUCTURE

The rebuild process is stopping to switch to the new structure.

blank

The rebuild process is stopping because the target structure is being deallocated, due to disconnect of the last connector.

reason

One of the following:

LOSS OF CONNECTIVITY TO THE OLD STRUCTURE

The reason specified for stopping the rebuild process was lost connectivity to the coupling facility where the old structure was located.

LOSS OF CONNECTIVITY TO THE NEW STRUCTURE

The reason specified for stopping the rebuild process was lost connectivity to the coupling facility where the new structure was located.

FAILURE OF THE OLD STRUCTURE

The reason specified for stopping the rebuild process was structure failure of the old structure.

FAILURE OF THE NEW STRUCTURE

The reason specified for stopping the rebuild process was structure failure of the new structure.

CONNECTOR SPECIFIC REASON

The reason specified for stopping the rebuild process was provided by the issuer of IXLREBLD. IXLREBLD is the programming interface for structure rebuild processing.

REQUEST FROM AN OPERATOR

The reason specified for stopping the rebuild process was the operator issuing the SETXCF STOP,REBUILD command.

NO COUPLING FACILITY PROVIDING 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 PROVIDING 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.

THE SPECIFIED POPULATECF IS LESS SUITABLE

The specified PopulateCF is less suitable than the coupling facility where the structure is currently allocated.

A CHANGE IN THE CFRM ACTIVE POLICY FOR THE STRUCTURE

The reason specified for stopping the rebuild process was a change in either the CFRM active policy DUPLEX specification for the structure or a change in the structure preference list such that the facility in which either the old or new structure is allocated is no longer in the preference list. When the CFRM active policy DUPLEX specification for a structure is changed to DUPLEX(DISABLED) for a change policy request, duplexing rebuild is stopped by MVS™ when the change is processed. Duplexing rebuild is also stopped when the facility in which the old or new structure is allocated is removed from the preference list.

LOSS OF CONNECTIVITY TO THE STRUCTURE

The reason specified for stopping the rebuild process was lost connectivity to either the coupling facility where the old structure was allocated or the coupling facility where the new structure was allocated.

FAILURE OF THE STRUCTURE

The reason specified for stopping the rebuild process was structure failure of either the new or the old structure.

INSUFFICIENT CONNECTIVITY DUE TO CHANGE IN THE SET OF CONNECTORS

The reason specified for stopping the rebuild process was insufficient connectivity due to a change in the set of connectors.

FAILURE OF A SYSTEM-MANAGED PROCESS PHASE

A phase of a system-managed process was unsuccessful. Message IXC573I may have been issued to provide additional information.

CONNECTOR DISCONNECTED FROM STRUCTURE

The rebuild was stopped in response to a connection disconnecting from the structure. A user-managed rebuild cannot continue after the last connector disconnects, even if the structure persists.

DEALLOCATION OF THE STRUCTURE

The rebuild was stopped because the structure was deallocated (for example, the last connector disconnected from a non-persistent structure).

DUMP SERIALIZATION HELD ON STRUCTURE

The rebuild was stopped because dump serialization prevented access to either the old or the new structure instance.

UNEXPECTED ERROR

The rebuild was stopped due to an unexpected error condition.

FAILURE OF A DUPLEXED REQUEST

The system-managed duplexing rebuild was stopped due to the failure of a duplexed request.

INABILITY TO PRESERVE DUPLEXING

The system-managed duplexing rebuild was stopped to allow the first connection to the structure after a total loss of connectivity to a coupling facility containing an instance of the duplexed pair or after a sysplex failure. To preserve duplexing, both instances of the duplexed pair must be accessible to the system where the first connection to the structure is running.

DETECTION OF A DUPLEX OUT OF SYNCH CONDITION

The system-managed duplexing rebuild was stopped due to the detection of an out of synch condition. The condition is detected by a duplexed request issued during the duplex established phase of a system-managed duplexing rebuild. Both structure instances are no longer usable and are failed by the system.

CONNECTOR HANG

The rebuild was stopped in an attempt to relieve a connector hang during the processing of a rebuild-related event. The system has issued message IXL040E or IXL041E to report the failure of the connector to provide an expected response to the event. The SFM policy specifies a value of CFSTRHANGTIME that permits the system to take automatic action to relieve connector hangs.

STRUCTURE INSTANCE DID NOT HAVE ANY AVAILABLE CONIDS

The duplexing rebuild was stopped because a structure instance did not have any available connection identifiers.

CONNECTOR DID NOT ALLOW USER LIMIT CHANGES

The duplexing rebuild was stopped because a connector connected and did not specify MAXCONN on the IXLCONN invocation.

STRUCTURE OBJECTS IN STORAGE-CLASS MEMORY

The duplexing rebuild was stopped because of usage of storage-class memory.

STRUCTURE FULL

The rebuild was stopped because the new structure instance is full. This may happen when copying structure objects to the new structure instance requires SCM-related resources that cannot be allocated. Rebuild the structure after updating the structure sizing in the CFRM policy to accommodate more structure objects.

codetype

One of the following:

USER CODE:

The stop code was specified by a user.

SYSTEM CODE:

The stop code was specified by the system.

stopcode

When the rebuild is stopped due to CONNECTOR SPECIFIC REASON, this is the USERCODE specified by the issuer of the IXLREBLD STOP request. Consult the documentation for the application that initiated the the rebuild for the meaning of this value.

When the rebuild was stopped due to FAILURE OF A SYSTEM-MANAGED PROCESS PHASE, FAILURE OF A DUPLEXED REQUEST, DETECTION OF A DUPLEX OUT OF SYNC CONDITION, or CONNECTOR HANG, this is an internal value indicating the reason for the rebuild stop, and is diagnostic data provided to help IBM® service personnel with problem determination.