• Control‑M can periodically trigger a file transfer from the MVS system to the other system. This technique can be used to pass data to the other system. In some cases, the transferred data can trigger a process in the target system.
• All File Transfer products can be interfaced using batch and/or TSO. Control‑M can submit a job that interfaces with the File Transfer product by invoking the appropriate program under batch or by operating TSO Batch and invoking the File Transfer product’s TSO interface.
• The CMEM facility can be used to acknowledge the receipt of a file from another system and, for instance, to order a job to handle that file (or add a prerequisite condition indicating that the file arrived). CMEM can only acknowledge the receipt of files under the following conditions:
  • The file is received by a started task (STC) or job. Most File Transfer products use an STC for this functions. However, TSO RECEIVE and TRANSMIT operate under TSO.
  • The File Transfer product uses regular MVS ALLOCATION/ DEALLOCATION facilities (that is, SVC 99) to create the new file.

  CMEM can acknowledge the receipt of files. However, it cannot determine whether the file transfer process was successful or not.

If the File Transfer product provides appropriate exits, these exits can be used to inform Control‑M of events occurring within the File Transfer product.

For example, if the other system has a "File Receipt" exit, utility IOACND can be called by this exit to add a prerequisite condition that informs Control‑M that a file has been received.

Some products provide the option to submit a job after the file transfer process has finished. Such a job can invoke utility IOACND to add a prerequisite condition to the IOA Conditions file.

For information about the built-in Control‑M interface to CONNECT DIRECT, see CONNECT DIRECT Support (Formerly NDM Support).