[z/OS]

Planning for Managed File Transfer - hardware and software requirements

Use this topic as guidance on how you need to set up hardware and software requirements on your system to run Managed File Transfer (MFT) on z/OS®.

Software requirements

Managed File Transfer is written in Java, with some shell scripts and JCL to configure and operate the program.

Important: You must be familiar with z/OS UNIX system services (z/OS UNIX) in order to configure Managed File Transfer. For example:
  • The file directory structure, with names such as /u/userID/myfile.txt
  • z/OS UNIX commands, for example:
    • cd ( change directory)
    • ls (list)
    • chmod ( change the file permissions)
    • chown (change file ownership or groups which can access the file or directory)
You require the following products in z/OS UNIX to be able to configure and run MFT:
  1. Java, for example, in directory /java/java80_bit64_GA/J8.0_64/
  2. IBM® MQ 9.1.0, for example, in directory /mqm/V9R2M0
  3. If you want to use Db2® for status and history, you need to install Db2 JDBC libraries, for example, in directory /db2/db2v10/jdbc/libs.

Product registration

At startup Managed File Transfer checks the registration in sys1.parmlib(IFAPRDxx) concatenation. The following code is an example of how you register MFT: 

PRODUCT OWNER('IBM CORP')
NAME('WS MQ FILE TRANS')
ID(5655-MFT)
VERSION(*) RELEASE(*) MOD(*)
FEATURENAME('WS MQ FILE TRANS')
STATE(ENABLED)

Disk space

[UNIX]You need 100 MB of DASD for PDSEs and a minimum of 50 MB in z/OS UNIX. If you used trace to diagnose problems, you need additional disk space in z/OS UNIX, for example 50 MB.