search cancel

Recommended method to perform XCOM port health check pings

book

Article ID: 258038

calendar_today

Updated On:

Products

XCOM Data Transport XCOM Data Transport - Linux PC XCOM Data Transport - Windows XCOM Data Transport - z/OS

Issue/Introduction

For XCOM running on distributed OS platforms when health check pings are sent to the XCOM ports unwanted messages may appear in the xcom.log.

1. If a ping is made to the non-secure XCOM listener port (default 8044) these connection messages are seen:
2023/01/18 17:37:48 TID=REMOTE PRG=xcomtcp PID=8864 IP=xxx.xxx.xxx.xxx
    XCOMU0793I Remote TCP/IP Connection Established.

2023/01/18 17:37:50 TID= PRG=xcomtcp PID=8864 IP=
    XCOMU0805I TCP/IP Connection Ended.    
    
2. If a ping is made to the non-secure XCOM listener port (default 8045) equivalent connection messages plus an extra error are seen:
2023/01/18 17:37:57 TID=REMOTE PRG=xcomtcp PID=8872 IP=xxx.xxx.xxx.xxx
    XCOMU0812I Remote Secure TCP/IP Connection Requested.

2023/01/18 17:37:59 TID=REMOTE PRG=xcomtcp PID=8872 IP=xxx.xxx.xxx.xxx
    XCOMU0780E XCOMU0780E TcpIp  507: TXPI function failed with no error code.:

2023/01/18 17:37:59 TID= PRG=xcomtcp PID=8872 IP=
    XCOMU0818I Secure TCP/IP Connection Ended.

Environment

Release : Any

Resolution

If LOG_CONNECT_MSG has been set to NO in the xcom.glb file the connection messages will not be displayed i.e. for a ping to the non-secure port nothing will be displayed and for a ping to the secure port the XCOMU0780E message will still be displayed.

XCOMU0780E is a valid error when targeting the XCOM secure port without a certificate. Compared to a non-secure port, connection requests on the secure port first perform an SSL handshake and then proceed for regular XCOM conversation over the SSL channel.

The recommended way to perform health checks is via XCOM ping requests ("xcomtcp -ping ...") which will eliminate the XCOMU0780E messages. This requires XCOM to be installed on the server which initiates the health checks so it may not be feasible to do that for some environments: XCOM Data Transport for UNIX/Linux 11.6.1 > Using > Sending a Ping Request

Examples:
xcomtcp -ping REMOTE_SYSTEM=hostname PORT=8044 SECURE_SOCKET=NO TRNENCRL_CIPHER=ALL
The xcom.log will contain just the non-secure connection messages i.e.

2023/01/18 17:57:35 TID=REMOTE PRG=xcomtcp PID=10186 IP=xxx.xxx.xxx.xxx
    XCOMU0793I Remote TCP/IP Connection Established.

2023/01/18 17:57:35 TID= PRG=xcomtcp PID=10186 IP=
    XCOMU0805I TCP/IP Connection Ended.

xcomtcp -ping REMOTE_SYSTEM=hostname PORT=8045 SECURE_SOCKET=YES TRNENCRL_CIPHER=ALL
The xcom.log will contain just the secure connection messages:

2023/01/18 17:57:28 TID=REMOTE PRG=xcomtcp PID=10159 IP=10.252.108.55
    XCOMU0812I Remote Secure TCP/IP Connection Requested.

2023/01/18 17:57:29 TID= PRG=xcomtcp PID=10159 IP=
    XCOMU0818I Secure TCP/IP Connection Ended.