How File Allocation Retry Processing Works

File Allocation Retry (FAR) processing allows Connect:Direct Server Adapter to retry a Copy operation when one of a set of certain file allocation errors occurs in combination with a non-zero return code. This is most useful when Connect:Direct Server Adapter initiates a file transfer with a remote Sterling Connect:Direct® for z/OS® system. FAR processing only affects locally initiated (PNODE) sessions that use the Connect:Direct Server CopyTo service or CopyFrom service.

When you enable FAR processing and Connect:Direct Server Adapter receives one of a set of certain file allocation error messages and a non-zero return code from the remote Sterling Connect:Direct server during a copy operation, Connect:Direct Server Adapter retries the Copy operation subject to the existing short-term and long-term retry settings. If the condition that caused the FAR processing persists, retries are performed up to a maximum of the configured short-term and long-term retries only. The retry counters are not reset after a successful connection when triggered by FAR processing.

If the retry counts are exhausted, the CopyTo or CopyFrom service fails and returns an error to the Business Process that invoked it.

The set of FAR error messages, which include the commonly occurring Sterling Connect:Direct for z/OS retry-able file allocation errors, is pre-configured in the Sterling B2B Integrator installation.