We have an issue with some transfers with XCOM from NonStop to Windows. Error is the following:
Enter Request # 32460
REQUEST # : 032460 TRANSFER ID : TANDEM
TYPE : LOCAL SEND FILE
STATUS : I ERROR : 297
LOCAL ID :
REMOTE ID :
LOCAL FILE : $xxxxxx.xxxxxxx.xxxxxx
REMOTE FILE : \\server\dir1\dir2\dir3\file.TXT
XCOM LOGIN : xxxxx
XCOM CREATOR : xxxxx
NOTIFIY USER :
TRANSFER STARTED : 2021/01/28, 18:00:24
TRANSFER TIME : 0
BLOCKS TRANSFERRED : 0
BYTES TRANSFERRED : 0
COMPRESSED BYTES TRANSFERRED : 0
Some jobs fail in an random time with the error, but when you re-run the transfer, it completes normally.
Version of XCOM in Windows is 11.6.1709.0, version on NonStop is also 11.
Release : 11.1
Component : CA XCOM Data Transport for Hp NonStop
Based on the traces received and reviewed, the following messages were received:
On Tandem:
"Txpi 226: Select timed out with no data available"
On Windows:
"XCOMN0780E TcpIp 506: Partner ended TCPIP connection unexpectedly."
In this case the connection was ended in 40 seconds per the Tandem trace. On the Windows side the transfer took a little longer to reply back to Tandem with the Header confirmation and could not since the connection had already ended.
It has been suggested that parameter TCP_TIMEOUT= be specified in the XCOMCNF file on Tandem. This should help with allowing the connection to be available a little longer in slow response time scenarios.
Also there are problems with the AV software on the Windows system that are causing problems. No details available on that.