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 EZAXCFnn, 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:
- DEVICE CPName MPCPTP AUTORESTART
- Device definition to communicate with TCP/IP stacks hosted by the remote VTAM.
- LINK EZAXCFnn MPCPTP CPName
- Link definition for the device, where nn is the SYSCLONE value for the remote VTAM and MVS.
- HOME IPAddress EZAXCFnn
- Associates the IP address with the dynamic XCF link.
- BSDROUTINGPARMS EZAXCFnn 55296 CostMetric SubnetMask DestIPAddress
- Defines the link characteristics for EZAXCFnn.
- START CPName
- Starts the specified device.
Notes:
- If EZAXCFnn is already defined as a link name, or the CP name is already defined as a device name, then dynamic XCF definition EZAXCFnn and the 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.