EZD1212E

Explanation
 The TCP/IP stack delayed joining a sysplex group
and delayed processing sysplex  definitions in the profile (VIPADYNAMIC
and IPCONFIG/IPCONFIG6 DYNAMICXCF  statements). 
 In the message
text:
 tcpstackname
The name of the TCP/IP stack.

System action
 TCP/IP continues.

Operator response
 If you want the TCP/IP stack to immediately
join a sysplex group rather than wait for dynamic routes over monitored
interfaces to be found, issue the  VARY TCPIP,,OBEYFILE command with
the GLOBALCONFIG SYSPLEXMONITOR NOMONINTERFACE option or  the NODYNROUTE
option specified. See the information about the GLOBALCONFIG statement in z/OS Communications Server: IP Configuration
Reference for information about the MONINTERFACE and
DYNROUTE keywords.
 When at least one dynamic route over monitored
interfaces is found, TCP/IP joins a sysplex group and finishes processing
the sysplex definitions. 
 If OMPROUTE is active, and the expected
dynamic routes over the monitored interfaces are not being generated,
contact the system programmer.

System programmer response
 Issue the Netstat DEvlinks/-d command
to determine which interfaces are being monitored. If the first hop
routers were stopped for maintenance, this might be the reason why
dynamic routes are not being generated. If you cannot determine why
the routes are not being created, see the information about  diagnosing OMPROUTE problems in z/OS Communications Server: IP Diagnosis Guide.

User response
 Not applicable.

Problem determination
 Not applicable.

Module
 EZBXFDYN

Example
  None.