[CF LOSSCONN RECOVERY MANAGEMENT IS IN PROGRESS]
[LARGER COUPLE DATA SET FOR CFRM REQUIRED.
FORMAT A NEW COUPLE DATA SET FOR CFRM
USING AT LEAST THE FOLLOWING:
  ITEM NAME(STR) NUMBER(str#)
  ITEM NAME(CONNECT) NUMBER(conn#)]

[THE COUPLE DATA SET
FOR CFRM SUPPORTS THE MAXIMUM NUMBER OF STR
RECORDS.  totalstr
STRUCTURE(S) MUST BE DELETED FROM THE POLICY TO
ACCOMMODATE STRUCTURES ALLOCATED IN THE COUPLING FACILITY.]

[totalstr STRUCTURE(S) MUST ALSO
BE DELETED FROM THE POLICY TO
ACCOMMODATE STRUCTURES ALLOCATED IN THE
COUPLING FACILITY.]

[THE REALLOCATE PROCESS IS IN PROGRESS.]

[THE REALLOCATE PROCESS IS STOPPING.]STRNAME: strname
STATUS:                   status
EVENT MANAGEMENT:         strem
TYPE:                     strtype
POLICY INFORMATION:
 POLICY SIZE:             policysize u
 POLICY INITSIZE:         policyinitsize u
 POLICY MINSIZE:          policyminsize u
 [SCMMAXSIZE:              policyscmmaxsize u]
 [SCMALGORITHM:            scmalgorithm]
 FULLTHRESHOLD:           fullthreshold
 ALLOWAUTOALT:            allowautoalt
 REBUILD PERCENT:         rebuildpercent
 DUPLEX:                  duplexstatus
 ALLOWREALLOCATE:         allowrealloc
 PREFERENCE LIST:         pref-cf pref-cf pref-cf pref-cf pref-cf
 ENFORCEORDER:            enforceorder
 EXCLUSION LIST:          excl-str excl-str excl-str
[POLICY RECPRTY:          recprty]
[SUBNOTIFYDELAY:           subnotifydelay]
[PENDING POLICY INFORMATION:]
  
  [header]

[  REASON PENDING : pendrsn ]
[  REASON IN TRANSITION: CONNECT OR DISCONNECT IN PROGRESS]
[  STRUCTURE DUMP EXISTS WITH STRUCTURE DUMP ID dumpid]
[  STRUCTURE FAILED] 

ALLOCATION TIME:   mm/dd/yyyy hh:mm:ss
CFNAME:     cfname  [NO SYSTEMS CONNECTED TO COUPLING FACILITY]
COUPLING FACILITY:      type.mfg.plant.sequence
                        PARTITION: partition side  CPCID: cpcid

[STORAGE CONFIGURATION NOT AVAILABLE]
 STORAGE CONFIGURATION    ALLOCATED         MAXIMUM      %
  ACTUAL SIZE:            actualsize u         maxsize u  pct
 [AUGMENTED SPACE:           iuaugspc u      emxaugspc u  pct]
 [STORAGE-CLASS MEMORY:         iuscm u         maxscm u  pct]
  [ENTRIES:                    scment        emxscment    pct]
  [ELEMENTS:                  scmelem       emxscmelem    pct]
For list, serialized list, and lock structures with record data:
   SPACE USAGE      IN-USE        TOTAL     %
 ENTRIES:          iuent       totent   iupct
[ELEMENTS:       iuelem     totelem   iupct]
[EMCS:            iuemc       totemc   iupct]
[LOCKS:                     totlock]

For lock structures without record data:
   SPACE USAGE                  TOTAL
    LOCKS:                     totlock

For cache structures:
   SPACE USAGE      IN-USE         TOTAL     %      CHANGED       %
    ENTRIES:         iuent       totent    iupct     chgdent   chgdpct
    ELEMENTS:      iuelem      totelem    iupct   chgdelem   chgdpct
 [ACTUAL SUBNOTIFYDELAY:   actualsubnotifydelay]
LOGICAL VERSION:         logicalver1 logicalver2
PHYSICAL VERSION:        physicalver1 physicalver2
SYSTEM-MANAGED PROCESS LEVEL:  processlevel
XCF GRPNAME:             xcfgrpname
DISPOSITION:             disp
ACCESS TIME:             accesstime
NUMBER OF RECORD DATA LISTS PER CONNECTION:   rdatalistspercon
MAX CONNECTIONS:         maxconns
# CONNECTIONS:           conns
STR ALTER STATE:         alterstate   [ALTER SYSTEM NAME: altersys]
STR ALLOW RATIO:         strratio
STR MINENTRY:            strminentry
STR MINELEMENT:          strminelement
STR MINEMC:              strminemc
COMPLETED USYNC          usynccompleted
EVENT:
COMPLETED USYNC          completedcode
COMPCODE:
COMPLETED USYNC          completedinfo
STATE :
NEXT USYNC EVENT:        usyncnext
NEXT USYNC               nextcompcode
COMPCODE :
NEXT USYNC STATE:        usyncnextinfo
SYSTEM RECPRTY:  sysrecprty
* ASTERISK DENOTES  asterisk
& AMPERSAND DENOTES CONNECTOR WHO LOST CONNECTIVITY TO STRUCTURE

CONNECTION NAME ID   VERSION   SYSNAME   JOBNAME   ASID STATE
----------------------------------------------------------------
connection-name id   version   sysname   jobname   asid constate 
CONNECTION NAME:   connection-name
ID:                id
VERSION:           version
CONNECT DATA:      condata
DISCONNECT DATA:   discdata
SYSNAME:           connsysname
JOBNAME:           jobname
ASID:              asid
STATE:             constate
CONNECTOR HAS LOST PHYSICAL CONNECTIVITY additionalinfo
moreinfo
CONNECTION ID(S) OWING A RESPONSE FOR THIS CONNECTION
                   connectionids
REBUILD WAIT:      rebldwait
CONNECT LEVEL      connect-level1 connect-level2
INFO LEVEL:        info-level
CFLEVEL REQ:       cflevel
NONVOLATILE REQ:   nonvolrequest
CONDISP:           condisp
ALLOW REBUILD:     allowrebld
ALLOW DUPREBUILD:  allowduprebld
ALLOW AUTO:        allowauto
   SUSPEND:        autosuspend
TERMLEVEL:         termlevel
CRITICAL:          critical
ALLOW ALTER:       allowalter
   USER ALLOW RATION: userratio
   USERMINENTRY:      userminentry
   UNSERMINELEMENT:   userminelement
   UNSERMINEMC:       userminemc
USYNCH WAIT:       usyncwait
[NUMUSERS numusers]
[MAXCONN({USER | DEFAULT}): maxconn]
[THE CFRM ACTIVE POLICY IS EMPTY]
[NO STRUCTURES MATCH THE SPECIFIED CRITERIA]
[STRUCTURE NAMES REQUESTED BUT NOT SHOWN ARE NOT DEFINED]

[CONNECTION NAMES REQUESTED BUT NOT SHOWN ARE NOT DEFINED]
[SYSTEM-MANAGED PROCESS STATE INFORMATION NOT AVAILABLE FOR THIS SYSTEM]

SYSTEM NAME   SYSTEM TOKEN  SYSTEM-MANAGED PROCESS STATE  COPY ID
------------  ------------  ----------------------------  -------
sysname       systoken      processstate                  processcopyid
[ENABLED FOR EXPEDITED DUPLEX COMPLETION PROTOCOL]
[DIAGNOSTIC INFORMATION:  STRNUM: strnum  STRSEQ: strseq]

[            MANAGER SYSTEM ID: mgrsysid] 

[NAME/MGR     #QUEUED  1STQESN  LASTQESN  CMPESN  NOTIFYESN]
------------  -------  -------  --------  ------  ---------
sysnameormgr  #queued  hESN     tESN      dESN    nESN

EVENT MANAGEMENT: evtmgmt 
[MANAGEMENT LEVEL: msgbasedlevel]

hh.mm.ss

The time in hours (00-23), minutes (00-59), and seconds (00-59) for the DISPLAY XCF command.

CF LOSSCONN RECOVERY MANAGEMENT IS IN PROGRESS

A loss of connectivity to a coupling facility occurred that required connector recovery.

str#

The STR number to be used in reformatting the CFRM Couple Data Set. If the current number is adequate, then this line will not be displayed.

conn#

The CONNECT number to be used in reformatting the CFRM Couple Data Set. If the current number is adequate, then this line will not be displayed.

totalstr

The total number of structures that should be deleted from the CFRM active policy.

THE REALLOCATE PROCESS IS IN PROGRESS.

The REALLOCATE process is initiated by the SETXCF START,REALLOCATE operator command. Once started, the REALLOCATE process examines each allocated structure to determine whether the location of any instance needs to be adjusted and/or a pending policy activated. The evaluation process uses the XCF allocation algorithm which factors in the CFRM active policy information and current set of active connections to make the determination.

THE REALLOCATE PROCESS IS STOPPING.

The REALLOCATE process is stopped by the SETXCF STOP,REALLOCATE operator command. Once stopped, the structure, which is the current target of the REALLOCATE process, will complete the relocation steps prior to ending the REALLOCATE process.

structure-name

The name of a structure.

status

One or more of the following:

ALLOCATED

The structure is allocated in a coupling facility.

NOT ALLOCATED

The structure is not allocated.

REASON SPECIFIED WITH REBUILD START:

Possible reasons structure rebuild has been initiated are:

STRUCTURE FAILURE

The user who initiated the rebuild has indicated that the structure should be rebuilt because structure failure has occurred. Note that structure failure might or might not have occurred. Rebuild processing does NOT verify the reason indicated by the user.

CONNECTIVITY LOST TO STRUCTURE

The user who initiated the rebuild has indicated that the structure should be rebuilt because loss of connectivity has occurred. Note that loss of connectivity might or might not have occurred. Rebuild processing does NOT verify the reason indicated by the user. If rebuild was initiated by the system based on the CFRM administrative policy, the following additional text also appears:

• REBUILD LOSSCONN PERCENTAGE: pctlossconn - where pctlossconn is the percentage loss of connectivity which caused the system to initiate a rebuild for the structure.

OPERATOR INITIATED

The user who initiated the rebuild or rebuild stop has indicated that he is the operator. Note that the user who initiated the rebuild / rebuild stop might or might not be the operator. Rebuild processing does NOT verify the reason indicated by the user.

POLICY-INITIATED

A duplexing rebuild has been initiated by the system based on the contents of the CFRM administrative policy.

CONNECTOR REASON: user reason

A connector-initiated rebuild, and supplied reason user reason.

REASON SPECIFIED WITH REBUILD STOP:

Possible reasons structure rebuild has been stopped are:

OLD STRUCTURE FAILURE

The user who initiated the rebuild stop has indicated that the rebuild should be stopped because the old structure has failed. Note that the old structure may or may not have failed. Rebuild processing does NOT verify the reason indicated by the user.

CONNECTIVITY LOST TO OLD STRUCTURE

The user who initiated the rebuild stop has indicated that the rebuild should be stopped because connectivity to the old structure has been lost. Note that loss of connectivity may or may not have occurred. Rebuild processing does NOT verify the reason indicated by the user.

CONNECTIVITY LOST TO NEW STRUCTURE

The user who initiated the rebuild stop has indicated that the rebuild should be stopped because connectivity to the new structure has been lost. Note that loss of connectivity may or may not have occurred. Rebuild processing does NOT verify the reason indicated by the user.

CONNECTIVITY LOST TO STRUCTURE

The duplexing rebuild is being stopped because one or more connectors lost connectivity to a coupling facility containing the structure. Structure rebuild may have been stopped by the system or a user. Note that loss of connectivity may or may not have occurred when a user initiated the rebuild stop. Rebuild processing does NOT verify the reason indicated by the user.

OPERATOR INITIATED

The user who initiated the rebuild or rebuild stop has indicated that he is the operator. Note that the user who initiated the rebuild / rebuild stop may or may not be the operator. Rebuild processing does NOT verify the reason indicated by the user.

CONNECTOR REASON: user reason

A connector initiated rebuild stop, and supplied reason user reason.

CONNECTIVITY LOST TO STRUCTURE

The duplexing rebuild is being stopped because one or more connectors lost connectivity to a coupling facility containing the structure. Structure rebuild may have been stopped by the system or a user. Note that loss of connectivity may or may not have occurred when a user initiated the rebuild stop. Rebuild processing does NOT verify the reason indicated by the user.

XES INITIATED REBUILD STOP:

XES has stopped the structure rebuild for the following reason:

NEW STRUCTURE FAILED

The new structure has failed.

NO COUPLING FACILITY PROVIDED BETTER CONNECTIVITY

No other coupling facility has better connectivity than the current one. The rebuild, which was initiated due to a loss of connectivity, would cause a further degradation in connectivity if accepted.

NO COUPLING FACILITY PROVIDED BETTER OR EQUIVALENT CONNECTIVITY

No other coupling facility has better or equivalent connectivity than the current one. The rebuild would cause a degradation in connectivity as determined by SFM system weights, if accepted.

INSUFFICIENT CONNECTIVITY DUE TO CHANGE IN THE SET OF CONNECTORS

A duplexing rebuild was stopped because a connector did not have connectivity to the new structure instance.

POLICY-INITIATED

A duplexing rebuild has been stopped by the system based on the contents of the CFRM administrative policy.

FAILURE OF A SYSTEM-MANAGED PROCESS PHASE

During a system-managed process, a phase was unsuccessful. When the system-managed process was stopped, message IXC522I was issued and supplied a SYSTEM CODE. The SYSTEM CODE is an internal value indicating the reason for the stop, and is diagnostic data provided to help IBM® service personnel with problem determination. Message IXC573I may have been issued to the hardcopy log to provide additional information.

DUMP SERIALIZATION HELD ON STRUCTURE

During a system-managed process, dump serialization prevented access to either the old or the new instance of the structure.

FAILURE OF A DUPLEXED REQUEST

During a system-managed duplexing rebuild, a duplexed request failed. When the system-managed process was stopped, message IXC522I was issued and supplied a SYSTEM CODE. The SYSTEM CODE is an internal value indicating the reason for the stop, and is diagnostic data provided to help IBM personnel with problem determination.

DETECTION OF A DUPLEX OUT OF SYNCH CONDITION

During a system-managed duplexing rebuild, a duplex out of synch condition was detected. The condition is detected by a duplexed request issued during the duplex established phase of a system-managed duplexing rebuild. When the system-managed process was stopped, message IXC522I was issued and supplied a SYSTEM CODE. The SYSTEM CODE is an internal value indicating the reason for the stop, and is diagnostic data provided to help IBM personnel with problem determination.

CONNECTOR HANG

The system is stopping the rebuild to try to alleviate a hang of a structure-related process caused by failure of a connector to provide an expected response.

NO AVAILABLE CONIDS

The system is stopping the duplexing rebuild because a structure instance did not have any available connection identifiers.

USER DID NOT ALLOW USER LIMIT CHANGES

The system is stopping the duplexing rebuild because the structure instances had different facility user-id limits, and a connector did not specify MAXCONN on the IXLCONN invocation.

POLICY CHANGE PENDING — CHANGE

There is an administrative policy change pending for this structure. The pending change is to change the policy definition for the structure. Each policy item that has a different value in the pending policy compared to the active policy will be highlighted in the PENDING POLICY INFORMATION section of the display. Note that there is a period of time during a structure rebuild process where the pending policy information has already been copied over into the active policy, and yet the structure is still marked as policy change pending. In such cases, the PENDING POLICY INFORMATION section of the display will not be provided, since no policy items differ between the active and pending policies at that time.

POLICY CHANGE PENDING - DELETE

There is an administrative policy change pending. The pending policy change is to delete the policy definition for the structure.

STRUCTURE NOT DEFINED IN POLICY

The structure is not defined in the active policy and therefore cannot be connected to. This scenario can only occur when all instances of the structure are either deallocation pending or in transition.

FAILED-PERSISTENT CONNECTIONS UNAVAILABLE DUE TO LARGER CFRM COUPLE DATA SET REQUIRED

The CFRM Couple Data Set must be reformatted to correct this unavailability.

{ALTER IN PROGRESS | ALTER STOP IN PROGRESS}

Structure alter has been initiated and is in progress or stopping. The message text indicates how the alter was initiated:

startsrc [ALTER, STOP REQUESTED stopsrc]

startsrc

One of the following:

OPERATOR INITIATED

The operator has initiated structure alter via a SETXCF START,ALTER command.

PROGRAM INITIATED

A program initiated structure alter via an IXLALTER REQUEST=START invocation.

SYSTEM INITIATED

The system initiated structure alter. A system-initiated alter (automatic alter) for an eligible structure will begin when structure full monitoring determines that a structure contains monitored objects that are at or above the structure full threshold specified in the policy by FULLTHRESHOLD. ALLOWAUTOALT(YES) is specified in the policy.

CF INITIATED

The coupling facility initiated reapportionment.

stopsrc

One of the following:

BY OPERATOR

The operator requested alter stop via a SETXCF STOP,ALTER command.

BY PROGRAM

A program requested alter stop via an IXLALTER REQUEST=STOP invocation.

BY SYSTEM

The system requested alter stop.

FOR REBUILD

The system requested alter stop because a structure rebuild was started.

The message text indicates the target values specified when the alter was initiated.

TARGET SIZE: targetsize u

The target size for the structure alter. The size was specified either by a program or by the operator, or by the system. This size is expressed in u.

u

The integer size unit specification. One of the following:

• K (kilobytes)
• M (megabytes)
• G (gigabytes)
• T (terabytes)

Note: In the message output, the size unit displayed may be converted to the largest size unit that can be used to represent the size and avoids any rounding.

TARGET RATIO: targetratio

The target ratio in form entry:element when the entry-to-element ratio is changing. The ratio was specified by a program or by the system.

TARGET EMC STORAGE PERCENT: targetEMCpct

The EMC storage target as a percentage of total structure storage when the EMC storage percent is changing. The percentage was specified by a program or by the system.

POPULATECF REBUILD PENDING FOR cfname

The structure is pending rebuild for the current PopulateCF rebuild. cfname is the name of the coupling facility specified for the PopulateCF rebuild request.

POPULATECF REBUILD IN PROGRESS FOR cfname

The structure is being rebuilt for the current PopulateCF rebuild. cfname is the name of the coupling facility specified for the PopulateCF rebuild request.

STRUCTURE CLEANUP IN PROGRESS

A lock structure is being cleared of residual information.

REALLOCATE EVALUATION PENDING

The allocated structure is pending evaluation of its current location. The REALLOCATE process initiated by the SETXCF START,REALLOCATE operator command examines each allocated structure to determine whether the location of any of the instance(s) needs to be adjusted and/or a pending policy activated. The evaluation process uses the XCF allocation algorithm, which factors in the CFRM active policy information and current set of connections, to make the determination.

TARGET OF REALLOCATE PROCESS

The structure was selected by the REALLOCATE process to have its location adjusted and/or pending policy activated. The REALLOCATE process was initiated by the SETXCF START,REALLOCATE operator command. Once marked as the target of the REALLOCATE process, the structure remains the target until one of the following occurs:

• The REALLOCATE process evaluates the next structure or completes.
• The structure is reduplexed, deallocated, or forced.

REBUILDING

The structure rebuild process type is rebuild.

REBUILD STOPPING

The structure rebuild process type is rebuild. The process is being stopped.

DUPLEXING REBUILD

The structure rebuild process type is duplexing rebuild.

DUPLEXING REBUILD STOPPING

The structure rebuild process type is duplexing rebuild. The process is being stopped to fall back to the old structure.

DUPLEXING REBUILD SWITCHING

The structure rebuild process type is duplexing rebuild. The process is being stopped to switch to the new structure.

METHOD: method

The method used to manage the current process (for example, rebuilding, rebuild stopping, or duplexing rebuild) is one of the following:

SYSTEM-MANAGED

The system is managing the process.

AUTO VERSION: procid1 procid2

The version number of the system-managed process. Used to correlate messages and XCF component trace records associated with the current system-managed process. procid1 is the first half of the auto version and procid2 is the second half.

USER-MANAGED

The connected users are managing the process.

PHASE: phase

The phase of the current process (for example, rebuilding, rebuild stopping, or duplexing rebuild) is one of the following:

WAITING FOR QUIESCE

The structure rebuild process is in the quiesce phase.

WAITING FOR COMPLETE

The structure rebuild process is in the complete phase.

WAITING FOR CLEANUP

The structure rebuild process is in the cleanup phase.

DUPLEX STARTUP

The structure rebuild process is in the startup phase.

DUPLEX ESTABLISHED

The structure rebuild process is in the duplex established phase.

DUPLEX SWITCHING

The structure rebuild process is in the duplex switching phase.

STARTUP

The structure rebuild process is in the startup phase.

ALLOCATE

The structure rebuild process is in the allocate phase.

ATTACH

The structure rebuild process is in the attach phase.

COPY

The structure rebuild process is in the copy phase. This line is followed by additional text:

COPY SUBPHASE: subphase

where subphase is one of the following:

INITIALIZATION

Phase initialization.

ATTACH

Connection of users to the new instance of the structure.

EXIT

Phase completion

CASTOUT CLASS

Copying cache structure directory entries.

WRITE WITH CASTOUT

Copying cache structure directory entries.

STORAGE CLASS REGISTRATION

Copying cache structure storage class directory entry registration information.

STORAGE CLASS COUNTERS

Copying cache structure storage class statistical information.

LIST

Copying list or lock structure data.

LOCK

Copying lock data for a list or lock structure.

LOCK CLEANUP

Copying lock data for a list or lock structure.

EVENT QUEUE

Copying list structure event and monitoring event queue data.

NOT AVAILABLE

Subphase information not available.

UNKNOWN

Unknown subphase.

COPY STOP

The structure rebuild process is in the copy stop phase.

QUIESCE FOR STOP

The structure rebuild process is in the quiesce for stop phase.

STOP

The structure rebuild process is in the stop phase.

START ALTER NOT PERMITTED

CF structure alter processing has been disabled; start alter is not permitted.

EVENT MANAGEMENT:

The CFRM event management protocol according to the CFRM active policy. Except for XCF signaling structures, message-based processing can be used for any allocated structure. When the CFRM event management protocol is message-based, message-based processing is enabled for an allocated structure during event processing. When the CFRM event management protocol is policy-based, event processing is policy-based for all allocated structures.

strem

One of the following:

POLICY-BASED

Event management for an allocated structure is controlled on each system having a structure connection and the CFRM active policy is accessed to obtain event data.

After the message-based protocol is selected for CFRM as a whole, an individual structure may continue to use policy-based processing until in flight events are completely processed. strem will continue to show structure using the policy-based protocol until the next event occurs for that structure, which may be quite some time. So even if the sysplex is using message-based protocols, a particular structure could be using either protocol. A structure used for XCF Signalling always uses policy-based protocols.

MESSAGE-BASED

Event management for the allocated structure is controlled by an event manager system using messages sent by XCF to provide event data and to communicate among the system(s). The manager system updates the CFRM active policy once all participant system(s) distribute the event to active connections.

TYPE:

When the allocated instance displayed is ACTIVE, REBUILD OLD/NEW, or DUPLEXING REBUILD OLD/NEW, the structure type is from the CFRM active policy.

strtype

One of the following:

LOCK

The structure type is a lock.

SERIALIZED LIST

The structure type is a serialized list.

LIST

The structure type is a list.

CACHE

The structure type is cache.

policysize u

The size of the structure as specified in the active policy. This size is expressed in u.

u

The integer size unit specification. One of the following:

• K (kilobytes)
• M (megabytes)
• G (gigabytes)
• T (terabytes)

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, a policysize of 1048576K may be converted to policysize of 1G for the purpose of messages; a policysize of 120000K will not cause the displayed size to be converted because it is not an even multiple of megabytes, gigabytes, or terabytes.

policyinitsize u

The INITSIZE for the structure as specified in the policy. This size is expressed in u. If no INITSIZE was specified in the policy, N/A will be displayed.

policyminsize u

The MINSIZE for the structure as specified or defaulted to in the policy. This size is expressed in u.

policyscmmaxsize u

The SCMMAXSIZE for the structure as specified or defaulted to in the policy. This size is expressed in u. This message line appears only if the policy specifies SCMMAXSIZE.

scmalgorithm

The SCMALGORITHM for the structure as specified or defaulted to in the policy. This message line appears only if the policy specifies SCMMAXSIZE.

fullthreshold

The FULLTHRESHOLD for the structure as specified or defaulted to in the policy, expressed as a percentage.

allowautoalt

One of the following:

YES

System-initiated alter (automatic alter) of the structure is allowed. For structure alter processing to be started for the structure, connections must also allow alter.

NO

System-initiated alter (automatic alter) of the structure is not allowed.

rebuildpercent

The REBUILDPERCENT for the structure as specified in the policy. If no REBUILDPERCENT was specified in the policy, then N/A will be displayed.

recprty

The RECPRTY for the structure as specified in the policy. If no RECPRTY was specified in the policy, then the line will not be displayed.

sysrecprty

The RECPRTY for the structure determined by the system. Value of 0 implies RECPRTY is not supported for the structure and it will not participate in lossconn recovery management. For more information about lossconn recovery management see .

duplexstatus

One of the following:

ENABLED

The CFRM administrative policy specifies DUPLEX(ENABLED) for this structure.

ALLOWED

The CFRM administrative policy specifies DUPLEX(ALLOWED) for this structure.

DISABLED

The CFRM administrative policy specifies or defaults to DUPLEX(DISABLED) for this structure.

allowrealloc

One of the following:

YES

REALLOCATE processing is allowed for the structure.

NO

REALLOCATE processing is not allowed for the structure. REALLOCATE processing will evaluate the structure but will not start a rebuild when the evaluation indicates that a rebuild is needed. REALLOCATE processing starts a duplexing rebuild when the structure is not duplexed but DUPLEX(ENABLED) is specified.

pref-cf

The name of a coupling facility in the preference list. The coupling facility names are listed in order of preference (most preferred first). Additional lines may be used to list more names. If the list is empty, the message PREFERENCE LIST IS EMPTY will be displayed instead.

enforceorder

One of the following:

YES

The order of the preference list is to be enforced.

NO

The system may reorder the preference list.

EXCLUSION LISTexcl-str

The name of a structure in the exclusion list. Additional lines may be used to list more names. If the list is empty, the message EXCLUSION LIST IS EMPTY will be displayed instead.

SUBNOTIFYDELAY subnotifydelay

The SUBNOTIFYDELAY value for the structure as specified in the policy, expressed in microseconds.

Header

One of the following:

ACTIVE STRUCTURE

The structure is active.

REBUILD NEW STRUCTURE

The structure is being rebuilt. This is the rebuild new structure.

REBUILD OLD STRUCTURE

The structure is being rebuilt. This is the rebuild old structure.

STRUCTURE PENDING DEALLOCATION

Deallocation is pending for this structure. The structure deallocation may remain pending if the coupling facility containing the structure is not connected to any system. Use the DISPLAY XCF,CF or DISPLAY CF command to show the connectivity status of the coupling facility.

STRUCTURE IN TRANSITION

The structure is either being allocated in a coupling facility or deallocated from a coupling facility. The structure deallocation may remain pending if the coupling facility containing the structure is not connected to any system. Use the DISPLAY XCF,CF or DISPLAY CF command to show the connectivity status of the coupling facility.

DUPLEXING REBUILD NEW STRUCTURE

The structure is undergoing a duplexing rebuild. This is the rebuild new structure.

DUPLEXING REBUILD OLD STRUCTURE

The structure is undergoing a duplexing rebuild. This is the rebuild old structure.

pendrsn

One of the following:

DEALLOCATING SYSTEM LOST CONNECTIVITY

Deallocation is pending for this structure and cannot complete due to a loss of connectivity.

STRUCTURE DUMP EXISTS WITH STRUCTURE DUMP ID nnnn

Deallocation is pending for this structure and cannot complete due to the existence of a structure dump. The structure dump id nnnn is given for use in the SETXCF FORCE,STRDUMP command.

REASON IN TRANSITION: CONNECT OR DISCONNECT IN PROGRESS

The structure is either being allocated in a coupling facility or being deallocated in a coupling facility.

STRUCTURE DUMP EXISTS WITH STRUCTURE DUMP ID

There is a structure dump associated with this structure, and the structure dump ID is given for use in the SETXCF FORCE,STRDUMP command.

dumpid

There is a structure dump associated with this structure, and the structure dump id is given for use in the SETXCF FORCE,STRDUMP command.

STRUCTURE FAILED

The structure has failed.

mm/dd/yyyy

The date when the structure was allocated. The date is in months (01-12), days (01-31), and years. If the structure is not allocated, dashes are displayed instead.

hh:mm:ss

The time when the structure was allocated. The time is in hours (00-23), minutes (00-59), and seconds (00-59). This is used to guarantee structure uniqueness. If the structure is not allocated, dashes are displayed instead.

cfname

Name of coupling facility in which the structure is allocated in. This name is from the CFRM active policy. If the structure is not allocated, this line is not displayed.

NO SYSTEMS CONNECTED TO COUPLING FACILITY

No systems have connectivity to this coupling facility.

COUPLING FACILITY:

The coupling facility which this system is able to use is identified by the node descriptor. See mapping IXLYNDE. The format xxxxxx.xxx.xx.xxxxxxxxxxxx gives the type, manufacture ID, manufacture plant ID, and sequence number.

type

Node type (See ndetype in IXLYNDE).

mfg

Node manufacturer ID (See ndemfg in IXLYNDE).

plant

Node manufacturer plant ID (See ndeplant in IXLYNDE).

sequence

Node sequence number (See ndesequence in IXLYNDE).

partition

Node LPAR partition number (See ndepartition in IXLYNDE).

side

The node PP/SI mode indicator and configuration code from the IXLYNDE are used to determine the value for side. Side is one of the following:

• SIDE: 0 - The coupling facility is on SIDE 0 of a partitionable CPC.
• SIDE: 1 - The coupling facility is on SIDE 1 of a partitionable CPC.
• blank means the coupling facility is in a non-partitionable CPC.

cpcid

Node Central Processor Complex (CPC) ID.

actualsize u

The actual size of the structure, if available. This size is expressed in u.

u

The integer size unit specification. One of the following:

• K (kilobytes)
• M (megabytes)
• G (gigabytes)
• T (terabytes)

Note: In the message output, the size unit displayed may be converted to the largest size unit that can be used to represent the size and avoids any rounding.

maxsize u

The maximum size of the structure, expressed in u.

pct

The percentage of the maximum value (allocated / maximum).

iuaugspc u

The amount of augmented space currently in use to support the use of storage-class memory by this structure. The value is expressed in u. This message line appears only if the structure is allocated with support for storage-class memory.

emxaugspc u

The estimated maximum amount of augmented space required to support the use of storage-class memory by this structure. The value is expressed in u.

iuscm u

The amount of storage-class memory currently in use by the structure. The value is expressed in u. This message line appears only if the structure is allocated with support for storage-class memory.

maxscm u

The maximum amount of storage-class memory that can be used by the structure.

iuscment

The number of entries currently stored in the storage-class memory associated with this structure. This message line appears only if the structure is allocated with support for storage-class memory.

emxscment

Estimated maximum number of entries that can be stored in the storage-class memory associated with this structure.

iuscmelem

The number of elements currently stored in the storage-class memory associated with this structure. This message line appears only if the structure is allocated with support for storage-class memory.

emxscmelem

Estimated maximum number of elements that can be stored in the storage-class memory associated with this structure.

iuent

The number of in-use entries residing in CF real storage (i.e., not including entries residing in storage-class memory). For cache structures, this includes both changed and unchanged entries.

totent

The total number of entries allocated in CF real storage.

iupct

The percentage of objects that are in-use relative to the total count (in-use/total).

iuelem

The number of in-use elements residing in CF real storage (i.e., not including elements residing in storage-class memory). For cache structures, this includes both changed and unchanged elements.

totelem

The total number of elements allocated in CF real storage.

iuemc

The number of in-use EMCs.

totemc

The total number of EMCs.

totlock

The total number of lock entries.

chgdent

The number of changed entries.

chgdelem

The number of changed elements.

chgdpct

The percentage full value for changed entries or elements (changed/total).

ACTUAL SUBNOTIFYDELAY actualsubnotifydelay

The actual SUBNOTIFYDELAY value, expressed in microseconds, for the structure as returned from the CF where the structure is allocated. In most cases the actual and the policy SUBNOTIFYDELAY value will be the same. They may differ if the DISPLAY XCF command is issued after a policy change has processed but before the system has updated the SUBNOTIFYDELAY value in the CF.

While a structure is duplexed, the actual SUBNOTIFYDELAY value that applies to the duplexed structure is the value associated with the old (primary) structure instance. The value associated with the new (secondary) structure instance is not used to determine the structure's sublist notification delay until/unless that structure instance becomes the old (primary) or simplex instance of the structure.

LOGICAL VERSION

Logical structure version number that is used for diagnostic purposes.

logicalver1

First half of the logical structure version number.

logicalver2

Second half of the logical structure version number.

PHYSICAL VERSION

Physical version for the structure. Changes when a new instance of the structure is allocate, as in a user-managed or system-managed rebuild, and there is at least one active connector to observe the allocation.

physicalver1

First half of the physical structure version number.

physicalver2

Second half of the physical structure version number.

processlevel

The level of support required by this structure in order to participate in a system-managed process (for example, rebuild). Certain phases of system-managed processes (for example, allocation and copy processing) can only occur on systems that support a system-managed process level greater than or equal to the level specified here. The DISPLAY XCF,COUPLE command (message IXC357I) displays the level of support provided by a given system.

processlevel will appear as NOT APPLICABLE if any of the following are true:

• The structure resides in a coupling facility of CFLEVEL less than 8. The CFLEVEL can be determined by issuing the DISPLAY CF command for the coupling facility named on the CFNAME line.
• The structure is a list structure used for XCF signalling.
• The structure is a list structure or a lock structure with record data, and was allowed by a system at a release that does not support system-managed processes.

processlevel will appear as NOT AVAILABLE if the system is unable to access the necessary information.

xcfgrpname

The XCF groupname associated with a serialized list or lock structure.

disp

One of the following:

KEEP

The structure disposition is Keep.

DELETE

The structure disposition is Delete.

accesstime

The length of time that the connector can tolerate not having access to the structure. Access will be denied to connectors when SVC Dump obtains serialization in order to dump data in the structure. The access time is defined by the connector which allocates the structure, and will either be in decimal tenths of seconds, or will be NOLIMIT (indicating that serialization may be held for as long as is required to capture all data requested).

NUMBER OF RECORD DATA LISTS PER CONNECTION

The number of lists per connection for a lock structure with record data. This line is displayed only for a lock structure with record data, which was allocated to support more than one record data list per connection.

rdatalistspercon

The number of lists per connection for this structure.

maxconns

The maximum number of connections for this structure.

conns

The current number of connections for this structure.

strratio

STR ALLOW RATIO will only be displayed when structure alter is in progress. strratio is one of the following:

YES

The current set of connectors have indicated that they will permit changes to the entry-to-element ratio.

NO

The current set of connectors have indicated that they will not permit changes to the entry-to-element ratio.

alterstate

One of the following:

IN PROGRESS

This instance of the structure is currently being altered.

DEFERRED

The alter of this instance of the duplexed structure is deferred, waiting for the alter of the other instance to complete.

STOPPING

Alter is stopping for this instance of the structure.

SCM OR AUS IN USE

The alter of this instance of the duplexed structure is in progress but cannot complete until all structure objects for the structure instance have been migrated from storage-class memory back into coupling facility real storage and all associated augmented space has been released.

MONITORING

The alter was initiated by the CF and the system is monitoring for completion.

altersys

The name of the system responsible for structure alter processing.

strminentry

Maximum for all connections of the connector-specified percentage of currently in-use list or currently in-use-and-changed cache entries that must be available for use at the end of structure alter processing. STR MINENTRY will only be displayed when structure alter is in progress.

strminelement

Maximum for all connections of the connector-specified percentage of currently in-use list or currently in-use-and-changed cache elements that must be available for use at the end of structure alter processing. STR MINELEMENT will only be displayed when structure alter is in progress.

strminemc

Maximum for all connections of the connector-specified percentage of structure storage to be used as Event Monitor Controls that must be available for use at the end of structure alter processing. STR MINEMC will only be displayed when structure alter is in progress.

usynccompleted

Completed user synch point event. Will only be displayed if USYNC processing has been invoked for this structure and has completed.

completedcode

Completed user synch point completion code. Will only be displayed if USYNC processing has been invoked for this structure and has completed.

completedinfo

Completed user synch point user state information. Will only be displayed if USYNC processing has been invoked for this structure and has completed.

usyncnext

Next user synch point event. Will only be displayed if USYNC has been invoked for this structure.

nextcompcode

Next user synch point completion code. Will only be displayed if USYNC processing has been invoked for this structure and has completed.

usyncnextinfo

Next user synch point user state information. Will only be displayed if USYNC processing has been invoked for this structure.

connectionids

Connection ID(s) of users who have not yet provided an event exit response (confirmation) for this disconnecting or failing connector. This connector will remain in the disconnecting or failing state until such responses are received from all connectors that owe them.

asterisk

One of the following:

CONNECTOR WITH OUTSTANDING REBUILD RESPONSE

Rebuild processing is waiting for a response from this connector.

OUTSTANDING REBUILD PROCESSING FOR CONNECTOR

A system-managed rebuild is waiting for a response from the system on behalf of the connector.

connection-name

The name of a connection. The system will repeat the connection message text to report all connections. If there are no connections, then no connection table will be displayed.

id

The connection identifier.

version

The connection version number.

connsysname

The name of the system owning the connection.

jobname

The name of the job owning the connection.

asid

The identifier of the address space owning the connection.

constate

One of the following:

FAILED-PERSISTENT

The connection is in the failed-persistent state.

DISCONNECTING

The connection is in the process of disconnecting.

FAILING

The connection is in the process of abnormally ending.

ACTIVE

This connection is in the active state.

ACTIVE &

This connection is in the active state but this connector has physically lost connectivity to the structure.

ACTIVE OLD

The structure is being rebuilt. This connector is connected to the old structure.

ACTIVE &OLD

The structure is being rebuilt. This connector has connected to the old structure but has physically lost connectivity to the structure.

ACTIVE NEW,OLD

The structure is being rebuilt. This connector is connected to both the old structure and the new structure.

ACTIVE NEW,&OLD

The structure is being rebuilt. This connector has connected to both the old structure and the new structure but has physically lost connectivity to the old structure.

ACTIVE &NEW,OLD

The structure is being rebuilt. This connector has connected to both the old structure and the new structure but has physically lost connectivity to the new structure.

ACTIVE &NEW,&OLD

The structure is being rebuilt. This connector has connected to both the old structure and the new structure but has physically lost connectivity to both structures.

REBUILD ACTIVE OLD

The structure is being rebuilt. This connector is connected to the rebuild old structure.

REBUILD ACTIVE NEW

The structure is being rebuilt. This connector is connected to the rebuild new structure.

DUPLEX REBUILD ACTIVE OLD

The structure is in a duplexing rebuild. This connector is connected to the duplexing rebuild old structure.

DUPLEX REBUILD ACTIVE NEW

The structure is in a duplexing rebuild. This connector is connected to the rebuild new structure.

condata

Data that is specified by the connector and is provided to the connection's exits.

discdata

Data that is specified by the connector and is provided to the connection's exits.

additionalinfo

One of the following:

TO STRUCTURE

The connector has lost physical connectivity to the structure.

TO NEW STRUCTURE

The connector has lost physical connectivity to the rebuild new structure.

TO OLD STRUCTURE

The connector has lost physical connectivity to the rebuild old structure.

moreinfo

One of the following:

FAILURE ISOLATED FROM CF

The system from which this user has connected is failure isolated from this structure.

NOT FAILURE ISOLATED FROM CF

The system from which this user has connected is not failure isolated from this structure.

rebldwait

REBUILD WAIT will only be displayed when structure rebuild is in progress. rebldwait is one of the following:

YES - USER

Rebuild processing is waiting on this connector for a response.

NO

This connector has already responded to the current rebuild event.

YES - SYSTEM

Rebuild processing is waiting for the system to respond on behalf of this connector.

connect-level1

First half of user-specified connection version/release level.

connect-level2

Second half of user-specified connection version/release level.

info-level

Level of information returned for the connection.

cflevel

Requested coupling facility level.

nonvolrequest

One of the following:

YES

User connected with NONVOLREQ=YES.

NO

User connected with NONVOLREQ=NO.

condisp

One of the following:

KEEP

User connected with CONDISP=KEEP.

DELETE

User connected with CONDISP=DELETE.

allowrebld

One of the following:

YES

Connector specified or defaulted to ALLOWREBUILD=YES

NO

Connector specified ALLOWREBUILD=NO

allowduprebld

One of the following:

YES

Connector specified ALLOWDUPREBLD=YES.

NO

Connector specified or defaulted to ALLOWDUPREBLD=NO.

allowauto

One of the following:

YES

Connector specified ALLOWAUTO=YES.

NO

Connector specified or defaulted to ALLOWAUTO=NO.

autosuspend

One of the following:

YES

User connected with ALLOWAUTO=YES and SUSPEND=YES.

NO

User connected with ALLOWAUTO=YES and SUSPEND=NO.

FAIL

User connected with ALLOWAUTO=YES and SUSPEND=FAIL.

termlevel

The first level at which the system is to take action if it becomes necessary to terminate the connector. One of the following:

TASK

The system will terminate the task from which the connector connected.

ADDRSPACE

The system will terminate the connector's home address space.

SYSTEM

The connector's system will partition itself from the sysplex.

XCFSIG

The system will take a sequence of actions specific to XCF signaling connectors, stopping at the first successful action:

• Stop signaling paths through the affected structure
• Force a disconnect
• Partition itself from the sysplex

Note: Depending on the nature of the problem, the system might take other actions not listed here before attempting to terminate the connector.

critical

One of the following:

YES

Connector has indicated that it considers itself a critical connector.

NO

Connector does not consider itself a critical connector.

allowalter

One of the following:

YES

Connector has indicated that it can support structure alter being initiated against this structure.

NO

Connector has indicated that it cannot support structure alter being initiated against this structure.

userratio

USER ALLOW RATIO will only be displayed when the connector permits structure alter. userratio is one of the following:

YES

Connector has indicated that it permits changes to the entry-to-element ratio.

NO

Connector has indicated that it does NOT permit changes to the entry-to-element ratio.

userminentry

Connector-specified percentage of currently in-use list or currently in-use-and-changed cache entries that must be available for use at the end of structure alter processing. USER MINENTRY will only be displayed when the connector permits structure alter.

userminelement

Connector-specified percentage of currently in-use list or currently in-use-and-changed cache elements that must be available for use at the end of structure alter processing. USER MINELEMENT will only be displayed when the connector permits structure alter.

userminemc

Connector-specified percentage of currently in-use event monitor control storage that must be available for use at the end of structure alter processing. USER MINEMC will only be displayed when the connector permits structure alter.

usyncwait

USYNC WAIT will only be displayed when USYNC is in progress. usyncwait is one of the following:

YES

USYNC processing is waiting on this connector for a response.

NO

This connector has already responded to the current USYNC event.

evtmgmt

The CFRM event management protocol according to the CFRM active policy. Except for XCF signaling structures, message-based processing can be used for any allocated structure. When the CFRM event management protocol is message-based, message-based processing is enabled for an allocated structure during event processing. When the CFRM event management protocol is policy-based, event processing is policy-based for all allocated structures.

POLICY-BASED

For the sysplex, event management for an allocated structure is controlled on each system having a structure connection and the CFRM active policy is accessed to obtain event data.

MESSAGE-BASED MANAGER SYSTEM NAME: mgrsysname

For the sysplex, allocated structures enabled for message-based processing have event processing managed by an event manager system using message sent by XCF signaling for communication with the participant system(s). The manager system updates the CFRM active policy once all participant system(s) distribute the event to active connections.

The event manager system is identified by mgrsysname.

MESSAGE-BASED TRANSITIONING TO NEW MANAGER

For the sysplex, allocated structures enabled for message-based processing have event processing managed by an event manager system but the sysplex is transitioning to a new manager system. Once the new manager system is assigned, the name of the event manager system can be displayed. The sysplex changes to a new manager system as the result of removing the prior manager system from the sysplex.

msgbasedlevel

The level of message-based event processing being used by CFRM. Message-based processing can be restarted by the system if a system in the sysplex does not support this level. Message-based processing can also be restarted by the system to increase this level.

maxconns

The maximum number of connections for this structure.

numusers

Number of users specified by the connection.

MAXCONN({USER | DEFAULT})

USER indicates that MAXCONN was specified by the connector on the IXLCONN invocation. DEFAULT indicates that MAXCONN was not specified by the connector on the IXLCONN invocation.

maxconn

Number of users specified or defaulted to by the connection.

mgrsysname

When event processing is policy-based, no system name is displayed. When event processing is message-based, the message-based manager system name (mgrsysname) is displayed. When transitioning to a new manager system, no system name is displayed.

msgbasedlevel.

The level of message-based event processing that is being used by CFRM. Message-based processing can be restarted by the system if a system in the sysplex does not support this level. Message-based processing can also be restarted by the system to increase this level

SYSTEM-MANAGED PROCESS STATE

The specified structure is undergoing a system-managed process (for example, rebuild). The current process phase is being coordinated by the listed systems on behalf of the connected users.

sysname

The name of the system participating in the system-managed process.

systoken

The token of the system participating in the system-managed process.

processstate

One of the following:

ALLOCATING

The system is in the process of allocating the new structure during the allocate phase of a system-managed process (for example, rebuild).

ATTACHING

The system is in the process of attaching connectors to the new structure during the attach phase of a system-managed process (for example, rebuild).

ATTACHED

The system has successfully attached connectors to the new structure during the attach phase of a system-managed process (for example, rebuild).

COPY WORKING

The system is participating in the copy phase of a system-managed process (for example, rebuild).

COPY WAITING

The system is waiting for working systems to complete the copy phase of a system-managed process (for example, rebuild).

COPY FAILED

The system was participating in the copy phase of a system-managed process (for example, rebuild), but has failed.

COPY STOPPING

The system is waiting for working systems to complete the copy phase of a system-managed process (for example, rebuild), but is now stopping.

COPY STOPPED

The system was participating in the copy phase of a system-managed process (for example, rebuild), but has stopped.

processcopyid

Identifier assigned to this system while participating in the copy phase of a system-managed process. Applicable only when the phase is COPY or COPY STOP.

DIAGNOSTIC INFORMATION

The diagnostic data is provided to help IBM service personnel with problem determination.

strnum

The number associated with the structure in the CFRM active policy.

strseq

The sequence number for the allocated structure from the CFRM active policy.

mgrsysid

The system slot and sequence number of the event manager system as viewed by this system only. A value of zero indicates that this system is using policy-based event management.

sysnameormgr

The name of the system for participant data or "MGR SYS" indicating event manager data. Data is only displayed for allocated structures. "MGR SYS" data is only displayed when the command is issued on the event manager system.

#queued

The number of events queued. It is a substantially correct count of current number of events on the queue.

hESN

Event sequence number of first event on the queue.

tESN

Event sequence number of last event on the queue.

dESN

Discard event sequence number.

nESN

Notify event sequence number.

ENABLED FOR EXPEDITED DUPLEX COMPLETION PROTOCOL

This text is displayed when the structure being duplexed through system-managed duplexing protocols is enabled for the expedited duplex completion protocol. This text is not displayed if the statement does not apply or if this system is not able to access the necessary information.