Planning for Managed File Transfer - hardware and software requirements on z/OS
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:
- Java, for example, in directory /java/java80_bit64_GA/J8.0_64/
- IBM® MQ 9.4.0, for example, in directory /mqm/V9R3M0
- 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
The IBM MQ for z/OS Program Directory states the DASD and zFS storage requirements for Managed File Transfer. For download links for the Program Directory for IBM MQ for z/OS, see IBM MQ 9.4 PDF files for product documentation and Program Directories.