Removing transfers in a WAITING state/status from the queue
search cancel

Removing transfers in a WAITING state/status from the queue

book

Article ID: 372396

calendar_today

Updated On:

Products

XCOM Data Transport

Issue/Introduction

Initiated a transfer from XCOM on z/OS to XCOM on Windows, which failed with message #XCOMN0322E Cannot access file server: Access denied. It was noticed that every time the transfer retried on z/OS a new TID entry was created for the transfer in the XCOM for Windows queue that would have a WAITING status/state and causing us to have to manually remove the entry from the queue. 

Environment

XCOM Data Transport for Windows r11.6 and r12.0

Cause

The new TID entry created in the XCOM for Windows queue is due to the transfer retry. As noted, their is a "#" preceding the XCOMN0322E message, that tells XCOM on z/OS that the transfer is retriable. XCOM on Windows will generate a new TID in the queue every time XCOM on z/OS retries the transfer. When that occurs you will notice that the status/state of the transfer will be in a WAITING state causing the transfer to stay in the queue.

Resolution

Review the value of parameter AGE_TIME in the %XCOM_HOME%\config\xcom.glb file and change the default value to a more reasonable value for your site. 

The AGE_TIME parameter will age and remove the transfers in the queue that do not have a "DONE" status/state. This will prevent the user from having to remove the entry manually with the "xcomqm" command.