Explanation
In the message,
information is:
SYSTEM {CAN | CANNOT} TARGET OTHER SYSTEMS.
[REASON: targetotherrsn]
SYSTEM {IS | IS NOT} ELIGIBLE TO BE TARGETED
BY OTHER SYSTEMS.
[REASON: othertargetrsn]
The message indicates whether the status detection partitioning
protocol is enabled on this system, and to what degree.
In
the message text:
- SYSTEM {CAN | CANNOT} TARGET OTHER SYSTEMS
- Whether this system can employ the system status detection partitioning
protocol when removing other systems from the sysplex.
- targetotherrsn
- The reason that this system cannot use the system status detection
partitioning protocol to aid in removing other systems from the sysplex.
One of the following reasons apply:
- 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 local system has not enabled the 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 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 obtaining
and communicating its IPL token, network address, or image name, 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 from a BCPii callable service,
preventing this system from obtaining its IPL token, network address
or image name, or connecting to the BCPii hardware management interface.
- 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 environment, 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 environment, and has no need
for using the system status detection partitioning protocol.
- 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.
- othertargetrsn
- The reason that other systems cannot use the system status detection
partitioning protocol when removing this system from the sysplex.
One of the following reasons apply:
- 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 local system has not enabled the protocol by
specifying ENABLE(SYSSTATDETECT) either in the COUPLExx parmlib member
FUNCTIONS statement or on a SETXCF FUNCTIONS command.
- NOT SUPPORTED BY HARDWARE
- The hardware on which this system resides does not support the
functions necessary for this system to identify itself within the
context of the protocol.
- OPERATING AS VM GUEST
- This system is operating as a second-level guest under the VM
operating system. In this environment, the system cannot uniquely
identify itself within the context of the protocol.
- SYSTEM OR HARDWARE ERROR
- A system or hardware error prevented this system from establishing
its unique identity within the context of the protocol.
- BCPII SERVICES NOT AVAILABLE
- BCPii services are 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 from a BCPii callable service,
preventing this system from obtaining its IPL token, network address
or image name, or connecting to the BCPii hardware management interface.
- 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 environment, 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 environment, and has no need
for using the system status detection partitioning protocol.
System action
The system continues processing.
If the system status detection partitioning protocol cannot be used,
the system processes partitioning requests using a partitioning protocol
based on the sysplex failure management (SFM) policy or default indeterminate
status behavior. This message will be re-issued if any factors affecting
the protocol eligibility change.
Operator response
System programmer response
If the system status detection partitioning
protocol is not enabled, and enablement is required, correct the limiting
factor identified in the message as follows:
- SYSPLEX COUPLE DATA SET NOT FORMATTED TO SUPPORT PROTOCOL
- Format primary and alternate sysplex couple data
sets by specifying the following parameters in the input to the IXCL1DSU
format utility:
ITEM NAME(SSTATDET) NUMBER(1)
Bring
the new couple data sets into service with the appropriate sequence
of SETXCF COUPLE commands.See z/OS MVS Setting Up a Sysplex for
information about the syntax of the IXCL1DSU format utility record
and the proper sequence of SETXCF COUPLE commands to use to bring
a new couple data set into service.
- NOT ENABLED BY INSTALLATION
- Issue the SETXCF FUNCTIONS,ENABLE=SYSSTADETECT command.
Update the COUPLExx parmlib member to specify FUNCTIONS ENABLE(SYSSTADETECT) to
preserve the setting for the next IPL.
- BCPII SERVICES NOT AVAILABLE
- See z/OS MVS Programming: Callable Services for High-Level Languages for
information about making BCPii services available on the system.
- INSUFFICIENT SAF RESOURCE ACCESS AUTHORITY
- See topic "Assigning the RACF® TRUSTED attribute" in z/OS MVS Initialization and Tuning Reference for
information about using RACF to
assign the TRUSTED attribute to the XCF address space. Also see topic
"BCPii Setup and Installation" in z/OS MVS Programming: Callable Services for High-Level Languages for
detailed information about defining a community name in SAF for each
CPC that the local system is communicating with.
- UNEXPECTED SYSTEM SERVICE ERROR
- Message IXC112I is issued when a BCPii callable service returns
a failing return code while the local system is attempting to establish
a virtual connection to the local CPC and image via BCPii. See message
IXC112I for diagnostic information to help correct the problem.
- SYSTEM OR HARDWARE ERROR
- XCF issues an abend x00C reason x041Dyyyy to initiate internal
XCF self verification and other actions to address the situation and
capture diagnostic data. If an internal XCF problem is discovered,
a dump is taken. An entry in logrec is made to document the situation
even if no dump is taken. Search problem reporting data bases for
a fix for the problem. If no fix exists, contact the IBM® Support Center.
Other factors reported by the message cannot be
corrected by the system programmer.
Source
Cross System Coupling Facility (SCXCF)
Module
Routing code
Descriptor code