IXC337I
hh.mm.ss DISPLAY XCF

SYSPLEX sysplex-name      MODE: plex_mode
SYSTEM system-name      STATUS: system-status
                                   system-status
                                   BEING REMOVED -  monitorsystem

                          TIMING: system-timing
                                STATUS TIME: activetime
                       JOIN TIME: jointime
                 SYSTEM NUMBER: system-number
             SYSTEM IDENTIFIER: system-identifier1  system-identifier2
                    SYSTEM TYPE: system-type  SERIAL: system-serial  LPAR: lpar
        NODE DESCRIPTOR: type.mfg.plant.sequence
                    PARTITION: partition side  CPCID: cpcid
                    RELEASE: nam ver.rel.mod

SYSTEM STATUS DETECTION PARTITIONING PROTOCOL CONNECTION EXCEPTIONS:
[local_limit | NONE]
[SYSTEM EXCEPTION conn_sys  con_exception]

            [DIAG INFO: bcpiiservice    faileddatetime     RC=retcode  diagdata]
            [SYSTEM ABEND CODE: abendcode]  [ABEND REASON CODE: abendrsncode]
            [TIME OF FAILURE:  abenddatetime]

SYSPLEX INITIALIZATION TIME: time

Explanation

In response to a DISPLAY XCF command, this message displays sysplex data for a specific system or all systems.

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.
sysplex-name
The sysplex being displayed.
plex_mode
The mode that the sysplex is running. plex_mode is one of the following:
XCF-LOCAL
The sysplex is running in XCF-LOCAL mode.
MONOPLEX
The sysplex is running in MONOPLEX mode.
MULTISYSTEM-CAPABLE
The sysplex is running in MULTISYSTEM-CAPABLE mode.
system-name
The system being displayed.
system-status
The status of the system being displayed.
monitorsysname
The system name of the system that is monitoring'the removal of the system being removed.
system-timing
The sysplex timing method on the system.
activetime
The date and time when the system saved status.
jointime
TThe date and time when the system became active in the sysplex.
system-number
System number used to identify the system in a sysplex.
system-identifier1
system-identifier2
System identifier used to identify a system in the sysplex.
system-type
The system type being displayed.
system-serial
The last four hexadecimal digits of the machine serial number of the machine on which the system being displayed is running
lpar
The LPAR number of the system being displayed N/A if the system is not an LPAR PR/SM™ system or is running under VM.
NODE DESCRIPTOR
The displaying of NODE DESCRIPTOR information is dependent on the availability of that information for a system in the sysplex couple data set. When available, extended NODE DESCRIPTOR information will be displayed.
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 system is on SIDE 0 of a partitionable CPC.
SIDE: 1
The system is on SIDE 1 of a partitionable CPC.
The system is in a non-partitionable CPC.
cpcid
Node Central Processor Complex (CPC) ID (see ndecpcid in IXLYNDE).
RELEASE
The displaying of RELEASE information is dependent on the availability of that information for a system in the sysplex couple data set. When available, extended RELEASE information will be displayed. N/A indicates that the information is not available for system-name.
nam
Product name (see ecvtpnam in IHAECVT).
ver
Product version (see ecvtpver in IHAECVT).
rel
Product release (see ecvtprel in IHAECVT).
mod
Product mod level (see ecvtpmod in IHAECVT).
local_limit
The reason the local system cannot establish connection to any CPC images in the sysplex through BCPii callable services. local_limit is one of the following:
SYSPLEX COUPLE DATA SET NOT FORMATTED FOR THE SSD PROTOCOL
The primary sysplex couple data set was not formatted to support the larger records required by the system status detection partitioning protocol.
SSD NOT ENABLED BY LOCAL SYSTEM INSTALLATION
The local system installation has not enabled the system status detection partitioning protocol by specifying ENABLE(SYSSTATDETECT) either in the COUPLExx parmlib member FUNCTIONS statement or on a SETXCF FUNCTIONS command.
OPERATING AS VM GUEST
This system is operating as a second-level guest under the VM operating system. In this environment, the system services necessary to make the connections are not available.
BCPII SERVICES NOT AVAILABLE
The BCPii service is not available. The system requires BCPii services to connect to any image.
PROTOCOL NOT APPLICABLE IN MONOPLEX MODE
The local system is running in MONOPLEX mode. A system in MONOPLEX mode is restricted to a single system sysplex, and has no need for using the system status detection partitioning protocol.
PROTOCOL NOT APPLICABLE IN XCF-LOCAL MODE
The local system is running in XCF-LOCAL mode. A system in XCF-LOCAL mode is restricted to a single system, and has no need for using the system status detection partitioning protocol.
NONE
The local system is connected to one or more target systems through the BCPii callable services.
conn_sys
The name of the system to which the local image failed to connect.
conn_exception
The reason the local system cannot establish a connection to the target CPC image through BCPii callable services. conn_exception is one of the following:
NOT SUPPORTED BY OPERATING SYSTEM RELEASE
The target system is at a system level earlier than z/OS V1R11. A system at these earlier z/OS release levels does not publish its network information required for another system to connect to it.
SSD NOT ENABLED BY REMOTE SYSTEM INSTALLATION
The remote system installation has not enabled the system status detection partitioning protocol by specifying ENABLE(SYSSTATDETECT) either in the COUPLExx parmlib member FUNCTIONS statement or on a SETXCF FUNCTIONS command.
INSUFFICIENT SAF RESOURCE ACCESS AUTHORITY
The local system has insufficient authorization to access SAF-protected resources associated with BCPii callable services.
REMOTE SYSTEM NETWORK INFORMATION NOT AVAILABLE
The target system never published its network identification information required for the local system to establish a connection. The required information includes the IPL token, image name, and network address. Possible reasons the target system fails to publish this information include:
  • The CPC on which this system resides does not support the functions necessary for the target system to communicate its IPL token.
  • The BCPii callable services are not available on the target system.
UNEXPECTED SYSTEM SERVICE ERROR
An unexpected return code was received from a BCPii callable service preventing the local system from connecting to the target system.
CONNECTION IN PROGRESS
The local image is attempting to connect to the target system, but a connection has not been established yet.
BCPII SERVICES NOT AVAILABLE
BCPii services are not available. The system status detection partition protocol requires BCPii services to be available on the local system to connect to the target system and to collect necessary information to publish the local IPL Token, CPC network address and image name.
NOT SUPPORTED BY HARDWARE
The CPC on which this system resides does not support the functions necessary for this system to communicate its IPL token.
SYSTEM OR HARDWARE ERROR
A system or hardware error prevented this system from obtaining and communicating its IPL token, network address, or image name; or connecting to the BCPii Hardware Management Interface.
bcpiiservice
The name of the BCPii callable service that failed. bcpiiservice is one of the following services:
  • HwiConn
  • HwiList
  • HwiQuery
  • HwiEvent
  • HwiCmd
  • HwiDisc
faileddatetime
The date and time when the failed BCPii callable service was invoked (mm/dd/yyyy hh:ss:dddddd).
retcode
The return code from the BCPii callable service that failed. This is diagnostic data that might be of use to IBM.
diagdata
Diagnostic data that was returned by bcpii service to help determine the cause of the service failure.
abendcode
The system abend code that occurred when attempting to connect to system conn_sys.
abendrsncode
The abend reason code associated with the abendcode.
abenddatetime
The time and date when the system abend occurred in mm/dd/yyyy hh:mm:ss:dddddd format.
time
The date and time that the sysplex was initialized.

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