EZZ9678E

Explanation
 Sysplex problem detection has determined that
OMPROUTE was not responsive. 
 tcpstackname is
the name of the TCP/IP stack. 
 timevalue is
the number of seconds OMPROUTE was not responsive.  This value is
 determined by the GLOBALCONFIG SYSPLEXMONITOR timersecs parameter
in the TCP/IP  profile.  See the z/OS Communications Server: IP Configuration
Guide and the z/OS Communications Server: IP Configuration
Reference for more information about the timersecs parameter
 and how it is used to detect OMPROUTE unresponsiveness. 

System action
 TCP/IP continues.  If the GLOBALCONFIG  SYSPLEXMONITOR  RECOVERY option is active
and this stack is not the only member of its TCP/IP sysplex  group,
the following RECOVERY actions will occur:  This stack will leave the TCP/IP sysplex group.  
This stack will no longer participate in sysplex distribution
(as a distributor or target) or act as an owner or a backup for DVIPAs.
 All DVIPAs defined on this stack will be deactivated; however, the
DVIPA definitions will be saved.   
If the problem is corrected, this operator message will be deleted;
if the GLOBALCONFIG SYSPLEXMONITOR AUTOREJOIN option is active, the
stack will process the DVIPA definitions and rejoin the TCP/IP sysplex
group.

If the GLOBALCONFIG  SYSPLEXMONITOR  NORECOVERY option is active,
no action  will be taken.  If the problem is corrected, this operator
message will be deleted.
If the operator did not stop OMPROUTE, TCP/IP sysplex problem
detection will assume there is a problem with OMPROUTE and will issue
an ABEND with system code 4C5,  reason code TcpLostOMPROUTE ('0404'x)
and capture an SVC dump of both the TCP/IP and the OMPROUTE address
spaces.  

 See  Sysplex problem detection and
recovery in z/OS Communications Server: IP Configuration
Guide for more information.
 See  GLOBALCONFIG statement in z/OS Communications Server: IP Configuration
Reference for the definition of the SYSPLEXMONITOR
parameters.

Operator response
 If RECOVERY is active, and no 4C5 abend occurred,
start the OMPROUTE procedure for this stack.  
 If OMPROUTE
successfully starts, this operator message will be deleted. If RECOVERY and NOAUTOREJOIN are active, then issue theVARY TCPIP,,SYSPLEX,JOINGROUP
command to cause the DVIPA definitions to be processed, and the stack
to rejoin the TCP/IP sysplex group.
If RECOVERY and AUTOREJOIN are active, no further actions are
needed.  The stack will process the DVIPA definitions and rejoin the
TCP/IP sysplex group.
If NORECOVERY is active, no further actions are needed. 

 If an abend occurred, save this documentation and contact
the system programmer.

System programmer response
 If this message is displayed, but
OMPROUTE is active, then it might not be  getting enough CPU cycles
to complete the task; OMPROUTE should run under the  WLM service class
SYSSTC (the default service class for started tasks).  It might  be
necessary to run OMPROUTE as non-swappable.  See the network design considerations with z/OS® Communications Server information
in z/OS Communications Server: IP Configuration
Guide for more information about improving OMPROUTE
performance.  If the  OMPROUTE performance problem cannot be determined,
contact the IBM® support  center
 with any supporting ABEND documentation.

Module
 EZBXFPDM

Procedure name
  EZBXFPDM