Information
Newer version of documentation BMC provides a newer version of the documentation for this version of the product. As a result, BMC no longer accepts comments in this space.BMC recommends upgrading to the latest version of the product. To see documentation for that version, see bao8301.

Implementing the exit program FTPOSTPR


BMC AMI Ops Automation

 ships an IBM FTP exit, FTPOSTPR, that generates a message when the FTP Server finishes a file transfer to or from the host.

By implementing this exit, you can create a MSG-initiated Rule that is triggered by the message and automate an action when the file transfer completes.

Note: The BMC AMI Ops Automation for z/OS option is required for this solution to operate and a valid password must be installed. See Installation System for information about obtaining and applying passwords.

To implement the exit program

  1. Copy the FTPOSTPX load module from hilivel.BBLINK to a catalogued ,APF-authorized data set.
  2. Rename FTPOSTPX to FTPOSTPR.
  3. Ensure that the newly defined data set is accessible to the FTP Server as defined in the IBM publication z/OS Communication Server: IP Configuration Reference.In general, the data set must be specified in any one of the following ways where the data set:

    • appears in the STEPLIB statement for the address space
    • is listed within the linklist concatenation
    • is loaded to the Link Pack Area (LPA) module

    When these steps are completed, the FTP Server can access the FTPOSTPR exit immediately and begins to use it. You do not need to restart the FTP Server to activate the exit.

    Warning

    Note

    The BMC AMI OpsA FTPOSTPR exist must precede all other FTPOSTPR modules that might be listed in the loadlib search order (STEPLIB, linklist, and LPA). Only one FTPOSTPR can be active at a time.


 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

BMC AMI Ops Automation 8.3