- TCP/IP detects another instance of TCP/IP in the sysplex
- The images are on the same CPC
- HiperSockets™ connectivity
between the two images exists
- The host processor supports HiperSockets and z/OS® Communications Server is properly
configured
- No link exists with the name IQDIOLNKnnnnnnnn (where nnnnnnnn is
the hexadecimal representation of the IP address specified on the
IPCONFIG DYNAMICXCF statement)
This scenario creates internal definitions equivalent to the following
definitions:
- DEVICE IUTIQDIO MPCIPA AUTORESTART
- Device definition to communicate with TCP/IP stacks hosted by
the remote VTAM®.
- LINK IQDIOLNKnnnnnnnn IPAQIDIO IUTIQDIO
- Link definition for the device, where nnnnnnnn is
the hexadecimal representation of the IP address specified on the
IPCONFIG DYNAMICXCF statement (that is, IPAddress).
- HOME IPAddress IQDIOLNKnnnnnnnn
- Associates the IP address with the dynamic XCF link.
- BSDROUTINGPARMS IQDIOLNKnnnnnnnn 57344
CostMetric SubnetMask DestIPAddress
- Defines the link characteristics for IQDIOLNKnnnnnnnn.
- START IUTIQDIO
- Starts the specified device.
Notes: - If IQDIOLNKnnnnnnnn is already defined
as a link name, or IUTIQDxx (where xx is
the CHPID of the HiperSockets LAN
that is defined or specified by default on the VTAM start option IQDCHPID) is already defined
as a device name, dynamic XCF IQDIOLNKnnnnnnnn and
IUTIQDIO definitions are not generated for discovery of another stack
in the same CPC.
- 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.