RCALPROC=XCOMRCAL, transfer not retrying

book

Article ID: 111557

calendar_today

Updated On:

Products

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

Issue/Introduction

XCOMRCAL=XCOMRCAL is working fine for locally initiated transfers requiring a tape/dataset recall, but if a remotely initiated transfer to the mainframe, requires a tape/dataset recall, XCOM starts the XCOMRCAL proc, but the transfer ends immediately with a network error: 

XCOMM0793I TCP/IP REMOTE CONNECTION ESTABLISHED FROM IP=xx.xxx.xxx.xx 
XCOMM0128I FOLLOWING FMH7 SENT TO CONVERSATION PARTNER
#XCOMM0770I SUBMITTING XCOMRCAL FOR ASYNCHRONOUS RECALL OF "dataset name"
XCOMM0805I TCP/IP CONNECTION ENDED WITH IP=xx.xxx.xxx.xx

Environment

XCOM r12.0 for z/OS 
XCOM r11.0 for iSeries(AS/400)

Resolution

Explained that they need to specify ENQ=YES for their AS/400 transfers to make the transfer retriable.

When the RCALPROC=XCOMRCAL parameter is specified in the CONFIG member and if a dataset/tape needs to be recalled, message  "#XCOMM0770I SUBMITTING XCOMRCAL FOR ASYNCHRONOUS RECALL OF dataset" will be produced. The message is a retriable message, hence the "#" before the message number.