Explanation
In the message,
text is:
SYSTEM sysname DATA
INTERVAL OPNOTIFY MAXMSG CLEANUP RETRY CLASSLEN
interval opnotify maxmsg cleanup retry classlen
SSUM ACTION SSUM INTERVAL SSUM LIMIT WEIGHT MEMSTALLTIME
action sfminterval ssumlimit weight memstalltime
CFSTRHANGTIME
cfstrhangtime
ufdisrc USER INTERVAL: uuuuu
DERIVED SPIN INTERVAL: sssss
uonisrc USER OPNOTIFY: [+]ooooo
MAX SUPPORTED CFLEVEL: maxcflevel
MAX SUPPORTED SYSTEM-MANAGED PROCESS LEVEL: maxprocesslevel
[SYNC/ASYNC CONVERSION THRESHOLDS NOT APPLICABLE]
SYNC/ASYNC CONVERSION THRESHOLD -SOURCE- DEFAULT
SIMPLEX SYNC/ASYNC THRESHOLD: thresh [source defthresh]
DUPLEX SYNC/ASYNC THRESHOLD: thresh [source defthresh]
SIMPLEX LOCK SYNC/ASYNC THRESHOLD: thresh [source defthresh]
DUPLEX LOCK SYNC/ASYNC THRESHOLD: thresh [source defthresh]
SIMPLEX SYNC/ASYNC THRESHOLD: thresh1
DUPLEX SYNC/ASYNC THRESHOLD: thresh2
SIMPLEX LOCK SYNC/ASYNC THRESHOLD: thresh3
DUPLEX LOCK SYNC/ASYNC THRESHOLD: thresh4
CF REQUEST TIME ORDERING FUNCTION: {NOT-INSTALLED | INSTALLED}
COUPLING THIN INTERRUPTS: {ENABLED | NOT-ENABLED | NOT-INSTALLED}
SYSTEM STATUS DETECTION PARTITIONING PROTOCOL ELIGIBILITY:
SYSTEM {CAN | CANNOT} TARGET OTHER SYSTEMS.
[REASON: targetotherrsn]
SYSTEM {IS | IS NOT} ELIGIBLE TO BE TARGETED BY OTHER SYSTEMS.
[REASON: othertargetrsn]
SYSTEM NODE DESCRIPTOR: type.mfg.plant.sequence
PARTITION: partition side CPCID: cpcid
SYSTEM IDENTIFIER: sysid
NETWORK ADDRESS: netid.nau
PARTITION IMAGE NAME: image
IPL TOKEN: ipltoken
COUPLEXX PARMLIB MEMBER USED AT IPL: COUPLExx
OPTIONAL FUNCTION STATUS:
FUNCTION NAME STATUS DEFAULT
funname {ENABLED|DISABLED} {ENABLED|DISABLED}
A
DISPLAY XCF,COUPLE command was entered to display the following information:
- Information about the primary and alternate data sets
- Information about sysplex failure management (SFM)
- Information about the system parameters set by the COUPLE statement
in the COUPLExx parmlib member
- Information related to the system status detection partitioning
protocol
- Status of optional functions
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.
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 (such as 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, but functional couple
data sets may be accessed only infrequently. For example, some types
of functional couple data sets are only accessed when a new policy
is started.
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.
- sysname
- The name of the system that issued the command
- interval
- The system failure detection interval in seconds. This interval
is the time XCF lets elapse without a status update before assuming
that the system failed.
- opnotify
- The time, in seconds, XCF waits before notifying the operator
of a potential system problem.
- maxmsg
- The default value for the maximum amount, in kilobytes, of message
buffer space. This default value is used when MAXMSG is not specified
on SETXCF START commands.
- cleanup
- The time, in seconds, XCF waits for cleanup of members.
- retry
- The default value for the retry limit. This value is used when
the RETRY keyword is not specified on SETXCF START commands.
- classlen
- The default length, in bytes, of messages allowed for a transport
class. This value is used when CLASSLEN is not specified on the SETXCF
START CLASSDEF command.
- action
- Define action. action can be one of the following:
- ISOLATE
- DEACTIVATE
- RESET
- PROMPT
- N/A
- sfminterval
- The SSUM interval as specified in the current SFM policy. This
interval is the time elapsed after a system has become status update
missing before the SSUM action is attempted.
- ssumlimit
- The SSUMLIMIT value from the SFM active policy.
The value of
ssumlimit can
be one of the following values:
- seconds
- When a system detects SSUM but XCF signal traffic is produced
by this system, seconds elapse before the SSUM
ACTION is automatically attempted. Message IXC446I will be issued
to indicate the action will be taken to remove the SSUM system that
is producing XCF signal traffic.
- NONE
- This value indicates that message IXC426D will prompt the operator
to remove a system that is producing XCF signal traffic. Automatic
action is not taken when message IXC426D (and IXC427A) is issued.
- N/A
- This value indicates that either an SFM policy is not active or
an SSUM ACTION of PROMPT is used.
- weight
- The SSUM weight as specified in the current SFM policy. This
weight is used in sysplex reconfigurations after a signalling connectivity
failure.
- memstalltime
- The MEMSTALLTIME value as specified in the current SFM policy,
which determines whether and when SFM is to take action against a
stalled XCF group member that is causing sympathy sickness on other
systems in the sysplex.
- NO indicates SFM will not take action.
- N/A indicates that an SFM policy is not active, in which case
the system behaves as if NO is specified.
- An integer value indicates the number of seconds that SFM is
to wait before taking action to alleviate a sympathy sickness condition
caused by a stalled member. SFM actions could include terminating
the stalled member or removing a system from the sysplex.
- cfstrhangtime
- The CFSTRHANGTIME value as specified in the current SFM policy,
which determines whether and when the system is to take action against
a coupling facility structure connector that has not provided an expected
response to an event associated with an on-going structure-related
activity, such as rebuild. The value and meaning are as follows:
- NO indicates that the system will not take action.
- N/A indicates that an SFM policy is not active on the system from
which the DISPLAY command is issued, in which case the system behaves
as if NO is specified.
- An integer value indicates the number of seconds that the system
is to permit the response to remain outstanding after a hang has been
reported by message IXL040E or IXL041E. If the response is still
outstanding when the specified interval elapses, the system will initiate
corrective actions to alleviate the hang. These may include stopping
a rebuild, or terminating the task, address space, or system associated
with the unresponsive connector.
- ufdisrc
- The source of the INTERVAL value being used by the system:
- SETXCF
- The value is set by the SETXCF COUPLE,INTERVAL command.
- PARMLIB
- The value is explicitly set in the COUPLExx parmlib member during
IPL.
- DEFAULT
- The default value that is derived from the excessive spin parameters
that are currently defined for the system. This value changes dynamically
in response to the SET EXS command.
- CLUSTER
- The value is set by cluster management instrumentation software.
- uuuuu
- The user-specified INTERVAL value, whether explicitly or by default.
- sssss
- The INTERVAL derived from the spin loop recovery specifications.
This value equals (N+1)*SpinTime+5 where N is the
number of excessive spin recovery actions, +1 indicates the implicit
SPIN action, and SpinTime is the excessive spin loop
timeout interval.
- uonisrc
- The source of the OPNOTIFY value used by the system:
- SETXCF
- The value is set by the SETXCF COUPLE,OPNOTIFY command.
- PARMLIB
- The value is explicitly set in the COUPLExx parmlib member during
IPL.
- DEFAULT
- The default OPNOTIFY value is a relative value of three seconds.
Thus the effective OPNOTIFY value used for this system is three seconds
more than the effective failure detection interval value (INTERVAL),
but not more than the maximum value of 86400.
- [+]ooooo
- The OPNOTIFY value specified by the user, whether explicitly or
by default. The value is displayed as +ooooo for
a relative OPNOTIFY value, ooooo for an absolute
OPNOTIFY value.
- maxcflevel
- The maximum CFLEVEL supported by this system.
- maxprocesslevel
- The maximum level of system-managed process, if any, supported
by the system. For a system to participate in system-managed processing
(for example, rebuild) against a structure, this value must be greater
than or equal to the level required by that structure as reported
(for allocated structures) by IXC360I in response to a D XCF,STR command.
This
value is meaningful only if the CFRM couple data set is formatted
to support system-managed processes.
- SYNC/ASYNC CONVERSION THRESHOLDS NOT APPLICABLE
- The system configuration does not support processing of coupling
facility requests.
- thresh
- The synchronous to asynchronous conversion threshold, in microseconds,
for the specified request type.
For these thresholds, when the system
observes actual CF request service times for the indicated types of
CF requests that exceed the indicated thresholds, it might start to
convert requests from CPU-synchronous execution to asynchronous execution,
to avoid using excessive amounts of processor time that would otherwise
be needed to perform the CF accesses in a CPU-synchronous manner.
- source
- One of the following:
- SYSTEM
- The indicated threshold was determined by the system.
- SETXCF
- The indicated threshold was set in response to a SETXCF MODIFY,SYNCASYNC
command.
- PARMLIB
- The indicated threshold was set in response to parameters specified
in the COUPLExx parmlib member used to IPL the system.
- *REPAIR
- The indicated threshold was set as the result of repairs made
to corrupted system data. If the value is not the current system
default, it will be reset to the system default. If the system default
is not appropriate for use, issue the SETXCF MODIFY,SYNCASYNC command
to set an appropriate value.
- defthresh
- The default sync/async conversion threshold value that would have
been used if the system-determined default value was in effect. The
value is expressed in microseconds. The text "IN USE" appears if
the indicated threshold value is being set in accordance with the
system determined default.
- thresh1
- The synchronous to asynchronous conversion threshold, in microseconds,
for simplex non-locking CF requests.
- thresh2
- The synchronous to asynchronous conversion threshold, in microseconds,
for duplexed non-locking CF requests.
- thresh3
- The synchronous to asynchronous conversion threshold, in microseconds,
for simplex locking CF requests.
- thresh4
- The synchronous to asynchronous conversion threshold, in microseconds,
for duplexed locking CF requests.
For these thresholds,
when the system observes actual CF request service times for the indicated
types of CF requests that exceed the indicated thresholds, it might
start to convert requests from CPU-synchronous execution to asynchronous
execution, to avoid using excessive amounts of processor time that
would otherwise be needed to perform the CF accesses in a CPU-synchronous
manner.
- CF REQUEST TIME ORDERING FUNCTION: NOT-INSTALLED
- The CF request time ordering function is not installed on this
machine. Operations to the CF may not request time ordering.
- CF REQUEST TIME ORDERING FUNCTION: INSTALLED
- The CF request time ordering function is installed on this machine.
Operations to the CF may request time ordering.
- COUPLING THIN INTERRUPTS: ENABLED
- Support for processing coupling thin interrupts is installed on
the central processor complex (CPC) and enabled on this LPAR.
- COUPLING THIN INTERRUPTS: NOT-ENABLED
- Support for processing coupling thin interrupts is installed on
the CPC but not enabled on this LPAR. See message IXL163I for diagnostic
information.
- COUPLING THIN INTERRUPTS: NOT-INSTALLED
- Support for processing coupling thin interrupts is not installed
on the CPC.
- SYSTEM {CAN | CANNOT} TARGET OTHER SYSTEMS
- Whether this system can employ the system status detection partitioning
protocol when removing other systems from the sysplex.
If
the system status detection partitioning protocol is not enabled,
and enablement is needed, refer to the description for message IXC104I,
which lists the required action to correct the limiting factor.
- targetotherrsn
- The reason that this system cannot use the system status detection
partitioning protocol to aid in removing other systems from the sysplex:
- SYSPLEX COUPLE DATA SET NOT FORMATTED TO SUPPORT PROTOCOL
- The primary sysplex couple data set was not formatted to support
the larger records required by the protocol.
- NOT ENABLED BY INSTALLATION
- The installation has not enabled the protocol by specifying ENABLE(SYSSTATUSDETECT)
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 exploit the protocol are not available.
- BCPII SERVICES NOT AVAILABLE
- BCPii services are not available. The system status detection
protocol requires BCPii services to determine the status of other
systems in the sysplex. When BCPii services are not available, the
local system is not connected to any remote CPC images in the sysplex.
- SYSTEM OR HARDWARE ERROR
- A system or hardware error prevented this system from communicating
its IPL token, obtaining its network address, or connecting to the
BCPii hardware management interface.
- INSUFFICIENT SAF RESOURCE ACCESS AUTHORITY
- The local system has insufficient authorization to access SAF-protected
resources associated with BCPii callable services.
- UNEXPECTED SYSTEM SERVICE ERROR
- An unexpected return code was received on a system service preventing
this system from communicating its IPL token, obtaining its network
address or image name, or connecting to the BCPii hardware nanagement
interface.
Message IXC112I is issued when a BCPii callable service
returns a failing return code while the local system is attempting
to connect to the BCPii hardware management interface (HWI) and collect
the necessary information to publish the local CPC network address
and image name for other systems in the sysplex to use. See message
IXC112I for diagnostic information to help correct the problem causing
the failure.
- SYSTEM {IS | IS NOT} ELIGIBLE TO BE TARGETED BY OTHER SYSTEMS
- Whether other systems can employ the system status detection partitioning
protocol when removing this system from the sysplex.
If
the system status detection partitioning protocol is not enabled,
and enablement is needed, refer to the description for message IXC104I,
which lists the required action to correct the limiting factor.
- othertargetrsn
- The reason that other systems cannot use the system status detection
partitioning protocol to aid in removing this system from the sysplex:
- SYSPLEX COUPLE DATA SET NOT FORMATTED TO SUPPORT PROTOCOL
- The primary sysplex couple data set was not formatted to support
the larger records required by the protocol.
- NOT ENABLED BY INSTALLATION
- The installation has not enabled the protocol by specifying ENABLE(SYSSTATUSDETECT)
either in the COUPLExx parmlib member FUNCTIONS statement or on a
SETXCF FUNCTIONS command.
- 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.
- 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 exploit the protocol are not available.
- SYSTEM OR HARDWARE ERROR
- A system or hardware error prevented this system from communicating
its IPL token, obtaining its network address, or connecting to the
BCPii hardware management interface.
- BCPII SERVICES NOT AVAILABLE
- For the local system to be an eligible target of the system status
detection partition protocol, the system status detection protocol
requires BCPii services to be available on the local system to collect
necessary information to publish the local IPL token, CPC network
address, and image name needed by other systems.
- INSUFFICIENT SAF RESOURCE ACCESS AUTHORITY
- The local system has insufficient authorization to access SAF-protected
resources associated with BCPii callable services.
- UNEXPECTED SYSTEM SERVICE ERROR
- An unexpected return code was received on a system service preventing
this system from communicating its IPL token, obtaining its network
address or image name, or connecting to the BCPii hardware management
interface.
Message IXC112I is issued when a BCPii callable service
returns a failing return code while the local system is attempting
to connect to the BCPii hardware management interface (HWI) and collect
the necessary information to publish the local CPC network address
and image name for other systems in the sysplex to use. See message
IXC112I for diagnostic information to help correct the problem causing
the failure.
- 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 SIDE 1 of a partitionable
CPC.
- blank - The coupling facility is in a non-partitionable CPC.
- cpcid
- Node Central Processor Complex (CPC) ID. (see ndecpcid in IXLYNDE.)
- sysid
- The system identifier used to identify the system at the sender
end of a CF link.
- netid.nau
- The network address uniquely identifying the CPC on which this
system resides, as a node on the LAN.
netid.nau is
available when the local system was able to obtain its netid.nau using
BCPii APIs.
N/A indicates the information is not currently available
because of limiting environmental conditions on the local system.
See message IXC104I for information about limiting environmental conditions
associated with using BCPii APIs and the system status detection partitioning
protocol.
- image
- The image name associated with the logical partition (LPAR) in
which the local system is loaded.
image is available
when the local system was able to obtain its image name using BCPii
APIs.
N/A indicates the information is not currently available
because of limiting environmental conditions on the local system.
See message IXC104I for information about limiting environmental conditions
associated with using BCPii APIs and the system status detection partitioning
protocol.
- ipltoken
- The IPL token associated with this system instance and the LPAR
in which it resides.
ipltoken is available when
the local system was able to obtain its IPL token using BCPii APIs.
N/A
indicates the information is not currently available because of limiting
environmental conditions on the local system. See message IXC104I
for information about limiting environmental conditions associated
with using BCPii APIs and the system status detection partitioning
protocol.
- xx
- COUPLExx parmlib member xx value used for the
current IPL.
- STATUS
- The current status of the named function on the system from which
the display command was issued.
- DEFAULT
- The default status of the named function.
- funname
- Name of XCF/XES optional function. See z/OS MVS Setting Up a Sysplex for
descriptions of the listed function names. funname is
one of the following values:
- DUPLEXCF16
- SYSSTATDETECT
- USERINTERVAL
- CRITICALPAGING
- DUPLEXCFDIAG
- CFLCRMGMT
- COUPLINGTHININT
- ENABLED
- The system will exploit the named function, subject to the establishment
of any other prerequisites that may be required for its use.
- DISABLED
- The system will not exploit the named function.
System action
The system continues processing.
Operator response
If the display indicates that the sysplex
needs a larger maximum number of groups or members, or a larger maximum
number of members possible in a group, then notify the system programmer.
System programmer response
Do one of the following:
- If the sysplex needs a larger maximum number of members possible
in a group, format a new, larger sysplex couple data set. Then ask
the operator to make the new sysplex couple data set the alternate
using the SETXCF COUPLE,ACOUPLE command, and perform a data set switch
with the SETXCF COUPLE,PSWITCH command. If more groups are also desired,
allocate more space to the data set.
- If the peak number of groups, peakgrp, is close
to the value of MAXGROUPS, a larger sysplex couple data set might
be needed to contain growth.
- If the peak number of members, peakmem, is
close to the value of MAXMEMBERS, a larger sysplex couple data set
might be needed to contain growth.
Source
Cross System Coupling Facility (SCXCF)
Module
Routing code
Descriptor code