For operation identifiers 1 through 3, the
For operation identifiers 4 through 8, the
For operation identifier 9, the
Note: See “Usage Notes” for a summary of the
Length of operation-specific information
INPUT; BINARY(4) Indicates the length (in bytes) of the
Allow operation
OUTPUT; BINARY(4) Indicates whether the operation should be accepted or rejected. The valid values are as follows:
vThis operation identifier is to be unconditionally rejected for the remainder of the current session.
vThe exit program will not be called again for this operation identifier.
0Reject the operation
1Allow the operation
2Always allow this operation identifier.
v This operation identifier is to be allowed unconditionally for the remainder of the current session.
vThe exit program will not be called again with this operation identifier.
Usage Notes
For FTP, if the returned Allow operation output parameter is not valid, the FTP application will not allow the operation and the message “Data from exit program for exit point &1; is missing or not valid” will be issued to the job log.
For FTP, if any exception is encountered when calling the exit program, the FTP application will issue the message: Exception encountered for FTP exit program &1; in library &2; for exit point &3;
Two different exit points are provided for the FTP application. Exit point QIBM_QTMF_CLIENT_REQ is used to validate requests processed by the FTP client program. Exit point QIBM_QTMF_SERVER_REQ is used to validate requests processed by the FTP server program. If desired, the same exit program can be used to validate requests from both of these exit points.
Table 10 on page 88 summarizes the
Appendix B. TCP/IP Application Exit Points and Programs 87