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

17. The sending server passes the data to ACF/VTAM, which controls its transport
to the receiving location.
18. The receiving server receives the data from ACF/VTAM, decrypts and decompresses
it, and, if specified in the request, converts and pads the data before it
is written to the receiving file.
19. The receiving server uses a file handler to write the data to the receiving file. If
specified in the file-transfer request, the receiving server uses a user-written file
handler. User-written file handlers are described in the NetView FTP
Customization guide.
20. Steps 14 through 19 are repeated until the entire contents of the sending file
are written to the receiving file.
Periodically during the file transfer the receiving server records how many
records have been transferred successfully. This is called taking checkpoints.
The checkpoint interval is described in “Specifying Values for the Server Initialization
Parameters” on page 113.
21. When the transfer of data is finished, both the sending and the receiving
servers close their files.
22. Both the sending and receiving servers call their post-transfer user-exit routines,
deallocate the files sent and received, and remove their established security
environments. The post-transfer user-exit routines can record statistics or
perform any post-transfer processing. For further information on the posttransfer
user-exit routine, refer to the NetView FTP Customization guide.
23. One of the two servers terminates the ACF/VTAM conversation.
24. The requesting server calls the post-conversation user-exit routine.
25. Each server sends a file-transfer report file and file-transfer completion
message to the user specified in the request.
26. Each server sends transfer end messages to the operator console.
27. The requesting server adds information about the outcome of the file transfer to
the request.
28. The requesting server asks the queue handler to put the updated request back
into the queue and to change its status to finished. Depending on the
outcome of the file transfer, the request is marked as being successfully or
unsuccessfully finished. Unsuccessfully finished requests remain on the
request queue and can be restarted.
29. If the requesting server was started in continuous mode, it tells the queue
handler to get a new file-transfer request, and the process begins again from
step 1. If the server was started in single mode, it stops automatically. The
server running modes (continuous and single) are described in “Specifying
Values for the Server Initialization Parameters” on page 113.
Note: The preceding discussion considers only one local-request handler on
one server. In practice, up to 99 local servers can be started, with each server
having up to 32 local-request handlers.
10 NetView FTP V2 MVS Installation, Operation, and Administration