Global TCP/IP SOURCEIP
Global TCP/IP SOURCEIP for Stand Alone Servers
The IBM Connect:Direct Server binds a local socket for out-bound processes and the default is to bind to the HOST IP as returned by BPX1HST (gethostid/gethostname) function. The HOST name is used for SMF reporting in the SESSION.HIGHWATER.SMF record. The HOST IP will become the local IP for the node.
- NETMAP SOURCEIP parameter
- TCP.SOURCEIP INITPARM
Global TCP/IP SOURCEIP for CD/PLEX Servers
Since CD/PLEX servers can run on multiple LPARs, each with its own TCP/IP stack, a different approach must be used for a global source IP. Normal defaults will assign a different HOST IP for the manager and each server based on the local TCP/IP stack. The TCP.SOURCEIP initialization parameter override this TCP/IP restriction.
However, IBM TCP/IP provides a feature called Distributed DVIPA that allows a single Dynamic VIPA address to be shared across TCP stacks and LPARs in a Sysplex. Please refer to “z/OS Communication Server: IP Configuration Guide” for information about Distributed DVIPA. With Distributed DVIPA configured for all TCP/IP stacks in a Sysplex and the Distributed DVIPA address included in TCP.LISTEN, TCP.API.LISTEN and TCP.SOURCEIP, the CD/PLEX manager and servers can use the same IP for primary and backups (Extended Recovery) and can be moved to any LPAR in the Sysplex as needed.