z/OS Communications Server: IP Messages Volume 2 (EZB, EZD)
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


EZD1177I

z/OS Communications Server: IP Messages Volume 2 (EZB, EZD)
SC27-3655-01

EZD1177I
tcpstackname SYSPLEX PROFILE DEFINITIONS ARE IGNORED BECAUSE THE STACK IS NO LONGER A MEMBER OF A TCP/IP SYSPLEX GROUP

Explanation

The sysplex profile definitions in the data set referenced by the VARY TCPIP,,OBEYFILE command were ignored because the stack is no longer a member of a TCP/IP sysplex group. Sysplex profile definitions cannot be applied if the stack is not a member of a TCP/IP sysplex group.

The stack left the TCP/IP sysplex group because one of the following occurred:
  • A VARY TCPIP,,SYSPLEX,LEAVEGROUP command was issued, causing the stack to leave the TCP/IP sysplex group.
  • A problem was detected that caused the stack to leave the TCP/IP sysplex group.

tcpstackname is the name of the TCP/IP stack.

System action

TCP/IP continues.

Operator response

If a VARY TCPIP,,SYSPLEX,LEAVEGROUP command was issued, then issue a VARY TCPIP,,SYSPLEX,JOINGROUP command to cause the stack to rejoin the TCP/IP sysplex group. If a problem was detected, prior eventual action messages explain why the stack is not a member. The problem that caused the stack to leave the TCP/IP sysplex group should be identified and corrected so that the stack can rejoin the TCP/IP sysplex group. See the information about sysplex problem detection and recovery in z/OS Communications Server: IP Configuration Guide for more information. If the problem cannot be corrected, contact the system programmer. When the stack has rejoined the TCP/IP sysplex group, the sysplex profile definitions can be reapplied.

System programmer response

If the problem causing the stack to leave the TCP/IP sysplex group cannot be corrected, contact IBM® software support services.

Module

EZBXFDYN

Procedure name

EZBXFDYN

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014