ERROR: "XCOMM0780E Txpi 215: Socket send error return value = 1127"
Article ID: 27866
Updated On:
Products
Issue/Introduction
This document explains the meaning of these messages and how to troubleshoot them:
XCOMM0780E Txpi 215: Socket send error return value = 1127
XCOMM0783E FLUSH REQUEST ENDED DUE TO TCP/IP ERROR
XCOMM0780E Txpi 215: Socket send error return value = 1124
Environment
- XCOM™ Data Transport® for z/OS
- XCOM™ Data Transport® for Windows
- XCOM™ Data Transport® for UNIX/Linux PC
Cause
These are TCP/IP errors and XCOM is just displaying the error codes it is receiving from TCP/IP.
Resolution
The Txpi 215 error indicates the general category of TCP/IP error.
The return value/code that follows indicates the meaning of the Txpi 215: Socket send error.
The return codes may be found in dataset CEE.SCEEH.H(ERRNO). NOTE: The high level qualifier may vary across sites.
Alternatively please see IBM documentation : IBM Return Codes (errnos)
For example:
1124 0464 ENOTCONN The socket is not connected.
1127 0467 ETIMEDOUT Connection timed out.
TCP/IP cannot make the connection so as long as XCOM services are started this is not normally an XCOM related problem.
In practice, other users have indicated that when these error messages were received, the problem was resolved by one of the following:
- Applying IBM maintenance to TCP/IP.
- Problem resolved after IPL.
- Firewall denying the connection; permit the connection.
- Remote XCOM service or XCOM TCP/IP listener down e.g.
UNIX/Linux - uses the separate inetd/xinetd daemon service as the listener.
Windows - when the XCOM service starts it launches a separate listener process caxcgsvr.exe. - Remote server down - restart.
- Wrong IP address specified - correct IP address.
Feedback
