System status values

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

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.

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

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.

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.

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.

The system is running in monoplex mode which prevents any other systems from joining this sysplex. The sysplex is using couple data sets.

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.

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.

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.

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.

XCF is in the process of removing a system from the sysplex.

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

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.

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.

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.