CA XCOM for z/OS Continuously Tries to Connect After the Transfer Fails

Document ID : KB000026457
Last Modified Date : 14/02/2018
Show Technical Document Details

Problem: 

 

CA XCOM for z/OS Continuously Tries to Connect After the Transfer Fails

 

Cause: 

 

There are retry parameters that can be set. If these parameters are set to a high number, it may appear that CA XCOM is looping.

Resolution:

XCOM retries failed transfers unless they are considered fatal errors. If the error is considered "retryable", CA XCOM will precede the message number with a # sign, such as #XCOMM0780E.

There are several retry parameters in the CA XCOM default table of Config Member that may be configured. You may specify a total number of retries; a total number of retries in a number of categories and the number of minutes between attempted retries. These parameters may also be specified as PARM parameters when starting the CA XCOM server.

These are the retry parameters that may be specified:

FERLFile access retry limit. This defaults to 255 times per transfer.
SERLSNA session establishment retry limit. This defaults to 255 times per transfer.
VERLSNA or TPC/IP connection attempts (after a network error). This defaults to 255 times per transfer.
TERLTotal number of all types of retries per transfer. This defaults to 32767 times per transfer.
ERRINTVThe number of minutes between retries. This defaults to 7 minutes.

Setting a parameter to 0 turns off retries for that category.

Additional Information:

Refer to the CA XCOM Data Transport for z/OS - 12.0 Adminstrating for more information on each of these parameters.