Request Scheduling

When scheduling a request for processing by a transmission initiator, the following requirements should be satisfied:

An INMC link to the remote region is specified as the transmission destination.
Transmissions are enabled for the destination.
A transmission initiator is available for the destination.
The request must be of a request class serviced by that initiator.
The inbound file limit has not been reached at the destination.

When these requirements are satisfied, the request is removed from the request queue and scheduled for processing by the appropriate initiator.

Concepts Behind the Control of Transmissions

The issuing of transmission requests and supervision of active requests is controlled from the region from which the requests are transmitted. The region that is receiving transmissions can only monitor the progress of inbound requests, acknowledge completed requests, and limit the number of concurrent transmissions that are to be received.

If a request fails for any reason, the restart of that request is always accomplished by the operator at the sending host. This means that even if the cause of the failure was rectified at the receiving host, the operator at the sending host must be informed that a restart should be attempted.

Error Recovery and Transmission Restarts

If a transmission request is scheduled but fails for a reason classified as unrecoverable, the request is requeued and suspended, pending clearance from an operator for it to be rescheduled. Such failures include data set errors, out-of-space conditions, invalid request parameters, operator interruption, and so on.

Requests that fail because of loss-of-contact conditions are rescheduled automatically when the link to the destination is restored, unless the AUTO-RESTART option is NO in the transmission definition. For most types of transmission, CA SOLVE:FTS checkpoints the progress of individual transmissions independently at both the transmitting and receiving regions, enabling a mutually acceptable restart point to be found when the request is rescheduled. If automatic restart is not permitted on a transmission, the request is placed in HELD status if it is interrupted by a loss-of-contact condition and is not restarted until released by operator intervention.

Note: Restart is not supported when the transmission is sent directly to spool (SYSOUT), or when either the input or output data set is a member of a partitioned data set.