Transfer to Windows in hung state and timed out "XCOMM0780E Txpi 226"

Products

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

Issue/Introduction

1. XCOM z/OS to Windows transfer hangs and eventually timed out with these messages in the log file.
*****
XCOMM0780E Txpi  226: Select timed out with no data available         
XCOMM0783E CONFIRM  REQUEST ENDED DUE TO TCP/IP ERROR                  
*****

On the receive side Windows server the xcom.log file only shows the initial connection message and initial transfer message:
*****
2026/01/15 12:12:33 TID=REMOTE PRG=xcomtcp PID=1812 IP=##.##.#.#:8642

    XCOMN0793I Remote TCP/IP Connection Established.

2026/01/15 12:12:37 TID=000010 [P52084.XCOM.TEST at ##.##.#.#:8642 --> \\server1\test\XCOM_TEST_FILE]

    XCOMN0026I Remotely initiated first try.
*****

2. Test another remotely initiated transfer from a different (Windows) server to the same receive side Windows server.
The Windows server xcom.log again shows the same messages:
*****
2026/01/21 04:10:02 TID=REMOTE PRG=xcomtcp PID=8780 IP=##.##.#.#:50398
    XCOMN0793I Remote TCP/IP Connection Established.

2026/01/21 04:10:03 TID=000087 [C:\Users\Administrator\Documents\file1.txt at ##.##.#.#:50398 --> C:\Users\Administrator\Documents\file2.txt]
    XCOMN0026I Remotely initiated first try.
*****

Taking the TID number and using command xcomqm -D<TID> shows the transfer is in PREALLOCATION_STATE:
*****
C:\Program Files\CA\XCOM>xcomqm -D000087
Copyright (c) 2022 Broadcom. All rights reserved. The term "Broadcom" refers to Broadcom Inc. and/or its subsidiaries.
xcomqm working with shared memory -- 000026
         ===== XCOM Data Transport transfer record =====
  Transfer ID..................: 000087
  Remote TID...................: 000139
  Remote group.................: IP5D6508
  Start time...................: Wed Jan 21 04:10:02 2026
  Transfer type................: Receive file
  Local file...................: C:\Users\Administrator\Documents\file2.txt
  Remote file..................: C:\Users\Administrator\Documents\file1.txt
  Initiated by.................: REMOTE site
  Remote System................: ##.##.#.#:50398
  TP pid.......................: 8780
  Owned by user................: xcomuser
  Current Condition............: ACTIVE
  Current Status...............:
  Current TP state.............: XCOMN0174I PREALLOCATION_STATE
  Message......................: XCOMN0026I Remotely initiated first try.
xcomqm displayed a total of 1 record(s) for command line option 1
xcomqm ended -- 1 command line option(s) were processed
*****

3. Test a locally initiated loopback command line transfer (QUEUE=NO) on the receive side Windows server itself.
It shows an unexpected message  "Press any key to continue . . .":
*****
    XCOMN0029I Locally initiated transfer started.

Press any key to continue . . .


*****

Environment

XCOM™ Data Transport® for z/OS
XCOM™ Data Transport® for Windows
XCOM™ Data Transport® for UNIX/Linux

Cause

Typically txpi errors can indicate a TCP/IP layer network issue but the above symptoms do not confirm with that.
Instead the transfer state of PREALLOCATION_STATE indicates some issue with the Preallocation Script exit on the receive side Windows server.

The optional parameter XPRECMD had been enabled in the %XCOM_HOME%\xcom.glb file to invoke the pre-allocation exit %XCOM_HOME%\xcompre.bat. The XPRECMD is invoked for both locally initiated and remotely initiated transfers.

A copy of the default version of xcompre.bat had been made and customized but a "pause" statement had inadvertently been left in the file.
That resulted in the the hung PREALLOCATION_STATE for the remotely initiated transfer and the visible message "Press any key to continue . . ." for the locally initiated loopback transfer.

Resolution

Correct the coding of the %XCOM_HOME%\xcompre.bat file to remove the "pause" statement.