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

Later, after the not-before time has passed, this request is again eligible for
scheduling (dispatchable). The server that then obtains the request might be
different from the one that obtained it last.
3. The local server sends information about the file-transfer request to the remote
server. The local and remote servers then determine which is the sending
server and which is the receiving server. This depends on the direction of the
file transfer (to or from the remote location). The transfer direction is specified
in the request and is independent of which server initiated the conversation.
4. The sending server passes control to the pre-transfer user-exit routine at its
location. You can modify this routine so that it checks the parameters of the
request, changes some of their values, or performs any other pre-transfer processing.
This routine is described in the NetView FTP Customization guide.
5. If appropriate, the server uses values specified in the request to establish a
security environment, which it uses to open the sending file.
6. Unless job allocation is to be used for the sending file, the sending server
dynamically allocates it. If job allocation is to be used, the file is allocated in
the JCL used to start the server. Dynamic allocation and job allocation are
described in the NetView FTP V2 MVS User’s Guide.
7. The sending server opens the sending file, extracts information about the
sending file, and sends that information to the receiving server.
8. The receiving server passes control to the pre-transfer user-exit routine at its
location where the part of the request that specifies parameters for the remote
location can be modified.
9. If appropriate, the server uses values specified in the request to establish a
security environment, which it uses to open the receiving file.
10. Unless job allocation is to be used for the receiving file, the receiving server
dynamically allocates it. If the receiving file does not already exist, the
receiving server creates it before allocating it. If job allocation is to be used,
the file is allocated in the JCL used to start the server.
11. The receiving server opens the receiving file, extracts information about the
receiving file, and sends that information to the sending server.
12. The local server asks the queue handler to update the file-transfer request in
the request queue. The transfer start time is set.
13. The sending server accesses the sending file.
14. The sending server uses a component called a file handler to read records
from the sending file. If specified in the file-transfer request, the sending server
uses a user-written file handler. User-written file handlers are described in the
NetView FTP Customization guide.
15. The sending server compresses the data to be transferred, using the type of
compression specified in the request.
16. The sending server encrypts the data if data encryption is specified in the
request. The encryption labels in the request must be matching at both the
local and remote locations. For information on encryption, refer to the OS/VS1
and OS/VS2 MVS Programmed Cryptographic Facility: Installation Reference
Manual.
Chapter 1. What NetView File Transfer Program for MVS Is and Does 9