If this stack is not the only member of the TCP/IP sysplex group and it is advertising DVIPAs (owns a DVIPA or is the primary routing node for a Distributed DVIPA), the following resource checks are made by the monitor:
If the VTAM address space is not currently active and the elapsed time since VTAM was last detected as active has exceeded the TIMERSECS value, message EZZ9671E is issued.
If there are no routes available to all partners, given the configured method chosen for forwarding data (VIPAROUTE statement or dynamic XCF interfaces), there are at least two other MVS™ systems in the sysplex, and the elapsed time since an active route was detected has exceeded the TIMERSECS value, message EZZ9673E or EZD1172E is issued.
If OMPROUTE was successfully initialized, it periodically sends a heartbeat to the stack, so the monitor can always make the following resource checks:
If the network monitoring function is enabled, at least one monitored interface is configured, the TCP/IP stack is not the only member of this sysplex group, and the TCP/IP stack participates in sysplex distribution (as a distributor or target) or acts as an owner or a backup for DVIPAs, the following network connectivity checks are made by the monitor:
If the MONINTERFACE option is specified on the SYSPLEXMONITOR parameter of the GLOBALCONFIG statement, all monitored interfaces become inactive, and the elapsed time since at least one active monitored interface was detected has exceeded the TIMERSECS value, message EZD1209E is issued.
If the MONINTERFACE or MONINTERFACE DYNROUTE option is specified on the SYSPLEXMONITOR parameter of the GLOBALCONFIG statement, there are no available dynamic routes found over any of the monitored interfaces, and the elapsed time since at least one dynamic route over the monitored interfaces was detected has exceeded the TIMERSECS value, message EZD1210E is issued.
Ensure that the WLM policy for the OMPROUTE address space receives sufficient priority in relationship to other work managed by WLM on the system, so that OMPROUTE receives the CPU cycles necessary for this task. For more information on this topic, see Sysplex autonomics.
If this stack is advertising DVIPAs or is a sysplex distributor target, the following checks are made:
Note, however, that if all DVIPAs on this stack have a status of MOVING and the stack is not a DVIPA target, these checks are not made.
In addition to the sysplex monitor, when the stack joins the TCP/IP sysplex group it requests that XCF monitor the TCP/IP sysplex component on the local stack. The XCF component performs this function by monitoring a status field updated by the TCP/IP sysplex component. If XCF detects that the sysplex functions have not been responsive for the TIMERSECS value, it schedules a TCP/IP routine that issues message EZZ9674E.
If TCP/IP encounters a nonrecoverable sysplex error, it issues the eventual action message EZZ9670E.
If five TCP/IP abends occur in less than 1 minute, eventual action message EZD1973E is issued.
All of these messages are eventual action messages. If the detected problem condition is corrected (for example, VTAM is started), the eventual action message is cleared. For more information about these eventual action messages, see z/OS Communications Server: IP Messages Volume 2 (EZB, EZD) and z/OS Communications Server: IP Messages Volume 4 (EZZ, SNM).