IXC336I

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.
sysname
The system being displayed.
type
The type of the system being displayed.
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.
mm/dd/yyyy hh:.mm:.ss 
 The last time stamp recorded for status monitoring on this system.
status
One of the following: :BEING REMOVED
XCF is removing the system from the sysplex. This can mean that:A VARY XCF command was entered to remove the system from the sysplex.
The system lost signalling connectivity to the other systems in
the sysplex.
The system lost access to the common clock being used by the sysplex.

msysname is the system name of the system
that is monitoring the removal of system msysnamefrom
the sysplex. If the monitoring system cannot be determined, msysname appears
as N/A
MONITOR-DETECTED STOP
The system has not updated its status on the couple data set within
the time interval specified on that COUPLExx parmlib member of the
system. This can mean that: The system is issuing an SVC dump.
The system is going through reconfiguration.
A spin loop is occurring.
The operator pressed stop.
The system is in a restartable wait state.
The system lost access to the couple data set.

XCF-LOCAL MODE
The system is running in XCF-local mode.  No other systems can
join a sysplex in XCF-local mode.  The sysplex is not using couple
data sets.
XCF-LOCAL MODE TM=SIMETR
The system is running in XCF-local mode.  No other systems can
join a sysplex in XCF-local mode.  The sysplex is not using couple
data sets. The TOD clock of this system is synchronized by simulated
ETR.
XCF-LOCAL MODE TM=ETR
The system is running in XCF-local mode.  No other systems can
join a sysplex in XCF-local mode.  The sysplex is not using couple
data sets.  The TOD clock of this system is synchronized by stepping
to the ETR Sysplex Timer.
XCF-LOCAL MODE TM=STP
The system is running in XCF-local mode.  No other systems can
join a sysplex in XCF-local mode.  The sysplex is not using couple
data sets.  The TOD clock of this system is synchronized by steering
to the ETR Sysplex Timer or
to the STP Facility.
XCF-LOCAL MODE TM=LOCAL
The system is running in XCF-local mode.  No other systems can
join a sysplex in XCF-local mode.  The sysplex is not using couple
data sets.  The TOD clock of this system is not synchronized to any
external time source.
MONOPLEX MODE
The system is running in monoplex mode which prevents any other
systems from joining this sysplex.  The sysplex is using couple data
sets.
MONOPLEX MODE  TM=SIMETR
The system is running in monoplex mode which prevents any other
systems from joining this sysplex.  The sysplex is using couple data
sets.  The TOD clock of this system is synchronized by simulated ETR.
MONOPLEX MODE  TM=ETR
The system is running in monoplex mode which prevents any other
systems from joining this sysplex.  The sysplex is using couple data
sets.  The TOD clock of this system is synchronized by stepping to
the ETR Sysplex Timer.
MONOPLEX MODE  TM=STP
The system is running in monoplex mode which prevents any other
systems from joining this sysplex.  The sysplex is using couple data
sets.  The TOD clock of this system is synchronized by steering to
the ETR Sysplex Timer or
to the STP Facility.
MONOPLEX MODE  TM=LOCAL
The system is running in monoplex mode which prevents any other
systems from joining this sysplex.  The sysplex is using couple data
sets.  The TOD clock of this system is not synchronized to any external
time source.
PARTITIONING CLEANUP
XCF is in the process of removing a system from the sysplex.
ACTIVE
The system is running and has updated its status on the couple
data set within the last time interval as defined in the system's
COUPLExx parmlib member.
ACTIVE         TM=ETR
The system is running and has updated its status on the couple
data set within the last time interval as defined in the system's
COUPLExx parmlib member.  The TOD clock of this system is synchronized
by stepping to the ETR Sysplex
Timer.
ACTIVE         TM=SIMETR
The system is running and has updated its status on the couple
data set within the last time interval as defined in the system's
COUPLExx parmlib member.  The TOD clock of this system is synchronized
by simulated ETR.
ACTIVE         TM=STP
The system is running and has updated its status on the couple
data set within the last time interval as defined in the system's
COUPLExx parmlib member.  The TOD clock of this system is synchronized
by steering to the ETR Sysplex
Timer or to the STP Facility.
ACTIVE          TM=LOCAL
The system is running and has updated its status on the couple
data set within the last time interval as defined in the system's
COUPLExx parmlib member.  The TOD clock of this systemk is not synchronized
to any external time source.

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.
N/A

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 bcpiiservice 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