XCOM for z/OS continuously tries to connect after a transfer fails
Article ID: 26457
Updated On:
Products
Issue/Introduction
It is noticed that XCOM for z/OS continuously tries to connect after a transfer fails
Environment
Release : 12.0
Component : XCOM Data Transport for z/OS
Cause
XCOM retries failed transfers unless they are considered fatal errors. If the error is considered "retryable", XCOM will precede the message number with a # sign, such as #XCOMM0780E.
Resolution
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 for type=SCHEDULE transfers either in the dest members or config members:
| FERL | File access retry limit. This defaults to 255 times per transfer. |
| SERL | SNA session establishment retry limit. This defaults to 255 times per transfer. |
| VERL | SNA or TPC/IP connection attempts (after a network error). This defaults to 255 times per transfer. |
| TERL | Total number of all types of retries per transfer. This defaults to 32767 times per transfer. |
| ERRINTV | The number of minutes between retries. This defaults to 7 minutes. |
NOTE: Setting a parameter to 0 turns off retries for that category.
Additional Information
How the parameters are set depends a lot on the environment, but realistically they could be set to 3 (except ERRINTV). If they don't recover within that range, they probably aren't going to. ERRINTV is probably at a good value.
Choose what works for the environment. Setting them in the dest members would be a lot of work and it would not provide any value.
If these parameters are set to a high number, it may appear that XCOM is looping.
Feedback
