Chapter 3. Operating NetView FTP V2.2.1 MVS - IBM

When a File-Transfer Request Remains Active in the Request Queue
If the queue handler encounters an error such as abnormal termination or an I/O
error in the request queue, it requests all its servers to terminate immediately. In
this case the file transfers that are currently being processed are interrupted and
checkpoints are taken. However, the file-transfer requests cannot be updated in
the request queue. Their status remains active.
When the queue handler is started again and rebuilds the request queue, it
changes the status from active to waiting. It remains nondispatchable for 300
seconds. When this time has elapsed, the file-transfer request can be scheduled
again.
Scheduling in the Case of a Restart from Checkpoint (SNA only)
When a data set is being transferred between two NetView FTP systems and the
transfer must be restarted, any of the local servers that serve the class of the
request can obtain it and continue the transfer. Also, the local server can contact
any of the remote servers, as far as this is specified by the file-transfer request.
Automatic Logon Retry (SNA only)
Sometimes a server cannot establish a session with a server at a remote system
because:
� All the servers at the remote system are busy with other transfers.
� None of the servers at the remote system has been started.
� ACF/VTAM is temporarily unable to find a path between the two servers.
When this happens, the server at the local system automatically changes the status
of the request from active back to waiting, and goes on to process the next
request in the request queue. Later, NetView FTP V2.2.1 MVS tries again to
process the request. It keeps trying until it succeeds in establishing a session.
This is called using automatic logon retry.
The automatic logon retry facility is not controlled by a parameter in the file-transfer
request—NetView FTP V2.2.1 MVS always performs it. A server that fails to establish
a session for one of these reasons does not tell the user who originated the file
transfer request.
Appendix B. Transfer Error Recovery 193