Scenario number 2
- TCP/IP detects another instance of TCP/IP in the sysplex
- No device with the name of the CPName of the remote VTAM® exists
- No HiperSockets™ connectivity between the two images exists
- No link exists with the name EZ6XCFnn, where nn is the value of the MVS™ system symbol (SYSCLONE) for the MVS hosting the VTAM with the device name
This scenario creates internal definitions equivalent to the following definitions:
- INTERFACE EZ6XCFnn DEFINE MPCPTP6 TRLENAME CPName IPADDR IP6Address
- Interface definition, where nn is the SYSCLONE value for the remote VTAM and MVS.
- START EZ6XCFnn
- Starts the specified interface.
Notes:
- If EZ6XCFnn is already defined as a link name, or the CP name is already defined as a device name, then dynamic XCF definition EZ6XCFnn and CP name are not generated for discovery of another stack in the same sysplex.
- The DestIPAddress is always zero.
For details about XCF-related statements, see z/OS Communications Server: IP Configuration Reference. For information about changes to Netstat displays of dynamic XCF settings, see z/OS Communications Server: IP System Administrator's Commands.