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

9. The post-conversation user exit is called on abnormal termination of the server
except when:
a. The abnormal termination occurred in either the pre-transfer or the posttransfer
user-exit routine of the server, or within the post-conversation user
exit itself.
b. The server has been canceled by the operator.
10. If the abnormal termination did not obviously occur in the pre-transfer and posttransfer
user-exit routines, the post-transfer user-exit routine is called.
11. If necessary, the input or output data set is deallocated.
12. If necessary, the temporary SAF environment is reset.
13. The buffers needed for checkpoint data-set handling are freed.
14. If necessary, the session with the remote server is terminated.
15. If no SNAP dump can be issued, then either a system dump with the
DUMP=YES option of the SETRP macroinstruction is requested, or no system
dump is requested.
The abnormal termination of a subtask in the server leads to a termination of the
whole server if the reason for the abend is one of the following:
� NetView FTP V2.2.1 MVS issued an SVC 13. These user abends are coded to
indicate program logic error events.
� A program check occurred.
� An SVC was issued by a locked or SRB routine.
Recovery of an OSI Server
In the case of an abnormal termination of an OSI server, any file transfers that
have been passed to OSI/File Services by that server are not affected if the
abnormal termination did not affect OSI/File Services. Only a request that is currently
active in the OSI server is affected by the abnormal termination.
The data structures necessary to complete the transfer request and to inform the
user of the result of the transfer are destroyed. Therefore, the minimum amount of
information to continue processing after abnormal termination of the OSI server (the
contents of the Local Request Table) is written to a recovery file after each significant
change.
If more than one OSI server is used, each server sends its own server name to the
queue handler together with NOTIFY ACTIVE so that each server can be identified.
Every request that has not been given a specific server name by the requester is
given the name of the server that has been selected by the queue handler for the
transfer. This means, each request is associated with one particular server and is
requeued on this server at recovery time. For more information about restarting
OSI file transfer requests, see “Automatic Restart of an OSI File Transfer” on
page 191.
160 NetView FTP V2 MVS Installation, Operation, and Administration