ERROR: "XCOMN1004E CA XCOM TCP/IPV4 listener failed to start"
search cancel

ERROR: "XCOMN1004E CA XCOM TCP/IPV4 listener failed to start"

book

Article ID: 136053

calendar_today

Updated On:

Products

XCOM Data Transport XCOM Data Transport - Windows XCOM - SUPPORT XCOM Data Transport - z/OS

Issue/Introduction

We are unable to XCOM files and are experiencing the Socket closed errors again.

XCOMM0811I STARTING SECURE TCP/IP CONNECTION TO PORT=08045, IP=<ipadress>
XCOMM0813I SECURE TCP/IP CONNECTION REQUESTED WITH DEST=**NONE**, PORT=<portnumber>, IP=<ipadress>
XCOMM1510E System SSL Function gsk_secure_socket_init: RC = 420: Reason = Socket  closed by remote partner
XCOMM0093E ERROR ACTIVATING SESSION - SESSION NOT ESTABLISHED
XCOMM1168I PLEXQ LISTENER TASK STOPPING
XCOMM0071I XCOMJOB NOW TERMINATING
XCOMM0897I TOTAL ELIGIBLE zIIP TIME = 0 MICROSECONDS
XCOMM0897I TOTAL ACTUAL   zIIP TIME = 0 MICROSECONDS

In the xcom.log from the Windows side you can find message: 

XCOMN1004E CA XCOM TCP/IPV4 listener failed to start on port 8044

Environment

  • XCOM™ Data Transport® for z/OS
  • XCOM™ Data Transport® for Windows

Resolution

I had the user capture an xcomd trace on Windows:

XCOMd PRG=xcomd PID=14908; XCOMN0088I The XCOMD CA XCOM Data Transport Scheduler Service started....
XCOMd service 404: InitService routine
XCOMd service 591: Event CAXCOMTERMINATIONEVENT already exists. Resetting event state.
XCOMd service 623: Event CAXCOMSUSPENDEVENT already exists. Resetting event state.
XCOMd service 655: Event CAXCOMRESUMEEVENT already exists. Resetting event state.
XCOMd service 1176: PostServiceInit routine

After reviewing the service trace provided I had them reboot the server. This resolved the problem.

Additional Information

Taking an xcomd trace for us to to review:

  1. Go to the GUI Global Parameters, Trace section, set the trace level to 10.
  2. In that same section, please turn on the trace for each Component
  3. Click Update button after selecting the Turn On radio button for each component.
  4. Stop xcomd
  5. Go to the C prompt and change directory to %XCOM_HOME% and issue command: card3.bat on
  6. Start xcomd
  7. Reproduce the problem by starting a remote transfer
  8. Stop xcomd
  9. From C prompt issue command: card3.bat off
  10. Go to the %xcom_home%\trace directory and send us the traces.
Powered by Wolken Software