CA XCOM Data Transport For z/OS and TCP Stack Affinity

Document ID : KB000027680
Last Modified Date : 14/02/2018
Show Technical Document Details

Introduction:

As a general rule, both incoming and outgoing transfers from CA XCOM for z/OS will default to the IP stack specified in the SYS1.PARMLIB(BPXPRMxx) as the primary stack. If that stack is busy, CA XCOM will use the secondary stack if one is available.

Background:  

The CA-XCOM default table parameters SERVADDR and TCPSTACK affect stack affinity.

 

Instructions: 

SERVADDR

  • Use the SERVADDR= parameter to specify a single IP address from which the z/OS CA-XCOM server will accept incoming requests. If the SERVADDR parameter is specified CA XCOM will use only that stack for incoming transfers. For example, in sites with multiple stacks, only the ipaddress (stack) specified in SERVADDR will accept incoming requests.
  • When sending from a remote partner you must specify the ipaddress (stack) specify this SERVADDR address. This parameter defaults to none.

TCPSTACK

  • Use the TCPSTACK= parameter to specify the job name or started task name of the TCP/IP stack that will be used. Otherwise this parameter defaults to none. For both incoming and outgoing transfers CA XCOM will default to the IP stack specified in the SYS1.PARMLIB as the primary stack. If that stack is busy, it will use the secondary stack if one is available.
  •  If the TCPSTACK parameter is specified, CA XCOM will use that stack for both incoming and outgoing transfers.

Determining what Stack is in Use

For all platforms, you may determine what stack is used by looking at the local XCOMLOG on the server. For MVS the following message will be issued in the XCOMLOG:

XCOMM0793I TCP/IP REMOTE CONNECTION ESTABLISHED FROM IP=nnn.nnn.nnn.nnn

The IP address above shows the remote system outgoing stack address.