IXC358I
hh.mm.ss DISPLAY XCF text

Explanation

In the message, text is: 
SYSPLEX COUPLE DATA SETS
PRIMARY DSN: dsname
    VOLSER: prisysvol     DEVN: prisysdev
    FORMAT TOD            MAXSYSTEMMAXGROUP(PEAK)   MAXMEMBER(PEAK)
    mm/dd/yyy hh:mm:ss    maxsys  maxgroup(peakgrp) maxmember(peakmem)
    ADDITIONAL INFORMATION:
     sysplexfunction

ALTERNATE DSN: dsname
          VOLSER: altsysvol  DEVN: altsysdev
          FORMAT TOD         MAXSYSTEM  MAXGROUP        MAXMEMBER
          mm/dd/yyy hh:mm:ss maxsys     maxgroup        maxmember
          ADDITIONAL INFORMATION:
            sysplexfunction

cdstype COUPLE DATA SETS
PRIMARY   DSN: dsname
          VOLSER: privol  DEVN: pridev
          FORMAT TOD       MAXSYSTEM
          mm/dd/yyy hh:mm:ss maxsys
          ADDITIONAL INFORMATION:
            typeinfo

         [DATA SET BEING REMOVED]

ALTERNATE DSN: dsname
          VOLSER: altvol    DEVN: altdev
          FORMAT TOD         MAXSYSTEM
          mm/dd/yyy hh:mm:ss maxsys
          ADDITIONAL INFORMATION:
            typeinfo


   [SYNCHRONIZATION WITH PRIMARY IN PROGRESS]

   [DATA SET BEING REMOVED]
[cdstype IN USE BY ALL SYSTEMS]

[SYSTEMS USING cdstype:
  sysname sysname sysname sysname sysname sysname sysname]

[SYSTEMS NOT USING cdstype:
  sysname sysname sysname sysname sysname sysname sysname]

[SYSTEMS processtype FOR cdstype:
   sysname2 sysname2 sysname2 sysname2 sysname2 sysname2]

[THERE ARE NO COUPLE DATA SETS DEFINED TO THE SYSPLEX]

[THE FOLLOWING REQUESTED TYPES
ARE NOT DEFINED TO THE SYSPLEX:
  ndeftype ndeftype ndeftype ndeftype ndeftype ndeftype ndeftype]

[cdstype NOT IN USE BY ANY SYSTEM]

A DISPLAY XCF,COUPLE command was entered to display detailed information about couple data sets. Information about the primary and alternate data sets is displayed.

The DATA SET BEING REMOVED message may appear for the primary couple data set because of an error with the data set or because the SETXCF command with the PSWITCH keyword was entered by the operator, causing the alternate couple data set to become the primary couple data set. The message may appear for the alternate couple data set because of an error with the data set or because the SETXCF command with the ACOUPLE keyword was entered by the operator, causing the alternate couple data set to be replaced.

If one or more types are used by ALL systems, the list of all systems in the sysplex may be displayed by issuing the DISPLAY XCF,SYSPLEX command.

The presence of couple data set information in the display output does not necessarily imply that the system can access the couple data set. A couple data set may be physically inaccessible (no paths to it available from the displaying system), but the system does not become aware of the problem until an attempt is made to perform I/O to the data set. The frequency of I/O varies with couple data set type. The sysplex couple data set is updated every few seconds. Functional couple data sets, on the other hand, may be accessed only infrequently (for example, when a new policy is started), so the system attempts to drive I/O to them approximately once per minute to verify their continued accessibility.

In the message text:
hh.mm.ss
The time in hours (00-23), minutes (00-59), and seconds (00-59) for the DISPLAY XCF command.
dsname
The name of the couple data set. The primary sysplex couple data set must be defined to XCF via the COUPLExx parmlib member. All other couple data sets can be defined via the COUPLExx parmlib member or the SETXCF command.
prisysvol
The volume on which the primary sysplex couple couple data set resides.
prisysdev
The device address of the device on which the primary sysplex couple data set resides.
mm/dd/yyyy
The date when the primary couple data set was formatted. The date is in months (01-12), days (01-31), and years.
hh:mm:ss
The time when the primary couple data set was formatted. The time is in hours (00-23), minutes (00-59), and seconds (00-59). This is used to guarantee data set uniqueness.
maxsys
The maximum number of systems that the couple data set can support.
maxgroup
The maximum number of groups that the couple data set can support.
peakgrp
The peak number of groups ever in use in the sysplex.
maxmember
The maximum number of members per group that the primary couple data set can support in one group.
peakmem
The greatest number of members ever in use in the largest group in the sysplex.
ADDITIONAL INFORMATION:
The lines following this header are supplied by the component owning the couple data set.
sysplexfunction
The level of function for which the couple data set is formatted. sysplexfunction has the following format:
  • One of the following two statements appears:
    SYSPLEX-ONLY COUPLE DATA SET SUPPORTED
    The couple data set supports only the use of the sysplex couple data set itself.
    ALL TYPES OF COUPLE DATA SETS ARE SUPPORTED
    The couple data set supports the use of additional couple data sets such as CFRM, SFM, etc.
  • One or more of the following lines may also appear:
    GRS STAR MODE IS SUPPORTED
    The couple data set supports GRS star mode operations.
    CLUSTER RESOURCE MANAGEMENT IS SUPPORTED
    The couple data set supports cluster resource management operations.
    SYSTEM STATUS DETECTION PROTOCOL IS SUPPORTED
    The couple data set supports the system status detection partitioning protocol.
altsysvol
The volume on which the alternate sysplex couple data set resides.
altsysdev
The device address of the device on which the alternate sysplex couple data set resides.
cdstype
The type name associated with the couple data sets.
privol
The volume on which the primary couple data set resides.
pridev
The device address of the device on which the primary couple data set resides. A value of ‘N/A’ means that the device address is not available on the displaying system, either because the function is not active on that system, or because the data set is being removed due to PSWITCH or an I/O error.
altvol
The volume on which the alternate couple data set resides.
altdev
The device address of the device on which the alternate couple data set resides. A value of ‘N/A’ means that the device address is not available on the displaying system because the function is not active on that system.
typeinfo
Additional information provided by the component owning the couple data set. It may describe, for example, the level of specialized function for which the couple data set is formatted.
  • typeinfo displays the following for any cdstype :
    NOT PROVIDED
    The component that owns the couple data set did not supply additional information, or the system is not using the couple data set.
    Component-supplied information
    Information supplied by the component that owns the couple data set. See the documentation associated with the owning component for an explanation.
  • If cdstype is ARM, typeinfo has the following format:
     FORMAT DATA
VERSION version, formatlvl
POLICY(policy) MAXELEM(maxelem) 
TOTELEM(totelem)
    version
    Indicates the version of the couple data set.
    formatlvl
    One of the following:
    HBB5520 SYMBOL TABLE SUPPORT
    This is the initial or base ARM couple data set format level and is created when the ARM couple data set is formatted using a version of IXCL1DSU prior to z/OS® V1R4.
    HBB7707 SYMBOL TABLE SUPPORT
    This format level is created when the ARM couple data set is formatted using a version of IXCL1DSU at z/OS V1R4 or higher.
    POLICY(policy) MAXELEM(maxelem) TOTELEM(totelem)
    This line represents the IXCL1DSU control statements that were used to format the couple data set.
  • If cdstype is BPXMCDS, typeinfo has the following format: 
    ADDITIONAL INFORMATION:
FORMAT DATA
VERSION(version)
MOUNTS(mounts) AMTRULES(amtrules)
    The typeinfo lines display the CDS version, the MOUNT parameter value, and the AMTRULES parameter value found in the BPXMCDS couple data set.
  • If cdstype is CFRM, typeinfo has the following format:
    FORMAT DATA
 POLICY(n)  CF(n)  STR(n)   CONNECT(n)
 [SMREBLD(1) [SMDUPLEX(1) [MSGBASED(1)]]]
    The FORMAT DATA lines represent the IXCL1DSU control statements that would be required to format a couple data set equivalent to the one described.
  • If cdstype is LOGR, typeinfo has the following format: 
    LOGR COUPLE DATA SET FORMAT LEVEL: formatlvl
LSR(lsrnum) LSTRR(lstrrnum) DSEXTENT(dsextentnum)
SMDUPLEX(smduplexnum)
    The typeinfo lines indicate the format level, the type, and the number of records found in the LOGR couple data set, where:
    formatlvl
    Indicates the format level of this couple data set. HBB5220 indicates this LOGR CDS was formatted at a release level prior to HBB6603. HBB6603 indicates this LOGR CDS was formatted at release HBB6603 or higher. HBB7705 indicates this LOGR CDS was formatted at release HBB7705 or higher.
    lsrnum
    Indicates the number of LSR type records formatted in this LOGR couple data set.
    lstrrnum
    Indicates the number of LSTRR type records formatted in this LOGR couple data set.
    dsextentnum
    Indicates the number of DSEXTENT type records formatted in this LOGR couple data set. This type of record is supported with a LOGR CDS format level of at least HBB6603.
    smduplexnum
    Specifies whether Logger should support XES system-managed structure duplexing:
    • 0 indicates Logger will not support system-managed structure duplexing. Results in LOGR CDS format level of HBB6603.
    • 1 indicates Logger will support system-managed structure duplexing. Results in LOGR CDS format level of HBB7705.
  • If cdstype is SFM, typeinfo has the following format: 
     FORMAT DATA
  POLICY(policy) SYSTEM(system) RECONFIG(reconfig)
    The POLICY(policy) SYSTEM(system) RECONFIG(reconfig) line represents the IXCL1DSU control statements that were used to format the couple data set.
sysname
The name of the system using, or not using, a type. If a type is used by all systems, or by no systems, then this line is not displayed. Instead, the preceding line will be replaced by cdstype IN USE BY ALL SYSTEMS or by cdstype NOT IN USE BY ANY SYSTEM, whichever is appropriate.
processtype
One of the following:
REMAINING IN PERMANENT ERROR
A permanent error process (removal of one or both couple data sets) is in progress for the named couple data set type. The named systems have not yet reported their participation in the process.
PARTICIPATING IN ACOUPLE
An ACOUPLE is in progress for the named couple data set type. The named systems are participating in the process.
sysname2
The name of a system participating or expected to participate in the permanent error or ACOUPLE process.
ndeftype
Name of a requested type which is not defined to the sysplex.

System action

The system continues processing.

Operator response

Not applicable.

System programmer response

Not applicable.

Source

Cross System Coupling Facility (SCXCF)

Module

IXCO1DCP

Routing code

#

Descriptor code

5,8,9

Parent topic: IXC messages