You can avoid one level of exchange between two nodes by following the multi-job stream option described below. If nodes exchange the signon concurrence flag -- NCCIRIF -- in the signon records exchanged at initialization, you can eliminate the X‘90’-X‘AO’ exchange after the receiver sends back the first X‘C0’. This method of transmission is recommended for sessions over satellite links because it reduces the propagation delay.

Both systems using the signon concurrence flags for this method of transmission to work.

Systems using the signon concurrence flag can end the transmission of a job for a number of reasons, as described in the 'B0' reason codes on 3-12. The receiving node can send an R C record (RCB X'B0') in response to a request to initiate (RCB X'90'). In this instance, the transmitting node should consider the receiving node drained until it receives a receiver online request (RCB X'D0'). If the receiving node does not wish to receive an object but is in the midst of transmission, it can send a cancel transmission (RCB X'B0') with a reason control byte to explain the reason. Then the transmitting node can place that file in a HOLD state and reopen the stream to send another object.

Each job in the stream still ends with an EOF travelling from the sender node to the receiving node. To end transmission, the receiver must send an E C request (RCB X"C0"). The receiver can also send an R C (RCB X"B0") in response to the EOF. This record terminates the stream and rejects the last job sent.

Note that the sending node should notify the operator before deleting the stream from his system.

Under the MRTS protocol, the R C is treated as a cancel request for both the last job and this stream. In this case, the sending node must respond with a T C request before restarting the stream with an R I.

Under the LRTS protocol, the R C is treated as an EOF response.