Additional TCP processes have been added and the plan is to use them for the XCOM for HP NonStop application being set up.
After looking at the XCOM setup, choosing the new TCP process for outbound XCOM seems pretty straightforward- all it needs is a new parameter in the XCOM startup script.
Release : 11.1
Component : XCOM Data Transport for HP NonStop
For incoming transfers, XCOM relies on the NonStop LISTNER process (via definitions defined in the PORTCONF file) to start and pass the socket to the XCOM62 process when a request is received. It is possible to configure a LISTNER process per TCP stack with each listening on different ports and IP addresses:
+++
== Start TCP/IP LISTNERs LSN0 and LNS1
DELETE DEFINE =TCPIP^PROCESS^NAME
CLEAR ALL
ADD DEFINE =TCPIP^PROCESS^NAME,CLASS MAP,FILE $ZTC0
PARAM TCPIP^PROCESS^NAME $ZTC0
PARAM ZTNT^TRANSPORT^PROCESS^NAME $ZTC0
WARNING - $ZTN0.#PTYSZAL: TRUNCATION OCCURRING
LISTNER /CPU 1,TERM $ZHOME,NAME $LSN1,PRI 150,NOWAIT,IN $ZHOME,OUT $ZHOME/0 $SYSTEM.ZTCPIP.PORTCOF
DELETE DEFINE =TCPIP^PROCESS^NAME
CLEAR ALL
ADD DEFINE =TCPIP^PROCESS^NAME,CLASS MAP,FILE $ZTC1
PARAM TCPIP^PROCESS^NAME $ZTC1
PARAM ZTNT^TRANSPORT^PROCESS^NAME $ZTC1
LISTNER /CPU 0,TERM $ZHOME,NAME $LSN0,PRI 150,NOWAIT,IN $ZHOME,OUT $ZHOME/1 $SYSTEM.ZTCPIP.PORTCON2
+++
More detailed configuration examples are available in the attached Word document TCPIP_STARTUP.docx i.e. OBEY files used to start multiple TCP stacks with each pointing to and starting a unique LISTNER and PORTCONF ports.