Do not delete the transfer's own queue entry in Transfer End Processing

Products

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

Issue/Introduction

This Document explains why you should not delete the transfer's own queue entry in Transfer End Processing.

Environment

Release: XCOM..01300-11.6-XCOM Data Transport-for AIX
Component:

Resolution

Do not delete queue entry in Transfer End Processing.

Take care when using xcomend.bat or xcompp.bat.

There are two batch files/scripts which can optionally be invoked (xcom.glb) after XCOM ended the data transfer:

• xcompp is invoked after an incoming data transfer ended succesfully.
• xcomend is invoked after every transfer is finished, whether succesful or not.

They can be used for various purposes after a transfer ended. But remember that, for xcom, the transfer itself is still not ended and the queue entry belonging to it is still used. Therefore it is strongly suggested NOT to delete that queue entry from within these batches/scripts. This can cause unpredictable results.

To shorten the time that entries are held in the queue, you can use a smaller value for EXPIRATION_TIME in xcom.glb.