search cancel

XCOMU0297E & XCOMU0436E sending from upgraded Unix server

book

Article ID: 242415

calendar_today

Updated On:

Products

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

Issue/Introduction

I have upgraded one of our test XCOM Solaris servers from r11.6 13012 SP00 (32 bit) to r11.6 21112 SP01 64bit and the upgrade is successful.
On the upgraded server when trying to send a test file to another legacy r11.6 13012 SP00 (32 bit) Solaris server receive error XCOMU0297E and see error XCOMU0436E on remote server:

# xcomtcp -c1 -f ./xcom.cnf LOCAL_FILE=/var/tmp/test1/testfile.txt REMOTE_FILE=/var/tmp/testfile.txt

# xcomqm -La
root      000006 - DONE       LOCAL   FAILED       XCOMU0297E Error requesting header confirmation: Txpi  227: Socket received 0 bytes: partner closed socket. Last error: 0

# xcomqm -D000006
         ===== CA XCOM Data Transport transfer record =====
  Transfer ID..................: 000006
  Start time...................: Mon May 23 11:16:05 2022
  Transfer type................: Send file
  Local file...................: /var/tmp/test1/testfile.txt
  Remote file..................: /var/tmp/testfile.txt
  Initiated by.................: LOCAL  site
  Remote System................: xxx.xxx.xxx.xxx
  End time.....................: Mon May 23 11:16:05 2022
  Owned by user................: root from group root
  Current Condition............: DONE
  Current Status...............: FAILED
  Current TP state.............: XCOMU0127I TP_DONE
  Password Encryption Cipher...: XCOM
  Message......................: XCOMU0297E Error requesting header confirmation: Txpi  227: Socket received 0 bytes: partner closed socket. Last error: 0

Here is the error at the receiver server:

# xcomqm -D000010
         ===== CA XCOM Data Transport transfer record =====
  Transfer ID..................: 000010
  Remote TID...................: 000006
  Remote group.................: IP0AE6D351
  Start time...................: Mon May 23 11:16:05 2022
  Transfer type................: Receive file
  Local file...................: /var/tmp/testfile.txt
  Remote file..................: /var/tmp/test1/testfile.txt
  Initiated by.................: REMOTE site
  Remote System................: yyy.yyy.yyy.yyy
  End time.....................: Mon May 23 11:16:07 2022
  TP pid.......................: 28041
  Owned by user................: root from group root
  Current Condition............: DONE
  Current Status...............: ABENDED
  Current TP state.............: XCOMU0167I SET_REMOTE_USER_ID
  Message......................: XCOMU0436E TP ended abnormally.

Environment

Release : 11.6

Component : XCOM Data Transport for Sun Solaris Operating System

Resolution

This type of error often means there is a problem with the file /etc/inetd.conf (or file /etc/xinetd.conf) on the receiving side which stores the configuration for listening for new remote transfers (XCOM Data Transport for UNIX/Linux 11.6.1 > Reference > Operating Environment > Remote Session Control Parameters)
However in this scenario the problem occurred when sending a file from the upgraded r11.6 21112 SP01 64bit server to the existing r11.6 13012 SP00 (32-bit) legacy server i.e. the legacy server is the receive side and thus /etc/inetd.conf should not have had anything changed.

It was determined that the root cause was that eTrust Antivirus software had blocked the XCOM file transfer traffic and there was no actual problem with XCOM itself.

Additional Information

Related KB article when sending files TO a newly upgraded server: XCOMU0297E Error requesting header confirmation: Txpi 227 ...