Before you start

Managed File Transfer (MFT) configuration uses files in UNIX System Services (USS) and PDSE data sets.

Most of the configuration and operation is done using JCL from a PDSE and you need to be familiar with working in an USS environment.

We can access OMVS from ISPF or we can use a Telnet type session using commands on your workstation, for example, Telnet Putty or SSH.

If we use OMVS from ISPF we can use the standard ISPF editor and browse commands oedit and obrowse.

You need to be familiar with the following USS commands
Table 1. Common UNIX System services commands
Command Function
ls -ltr path Lists information about the files in path
ls -ltrd directory Lists information about the specified directory rather than the files in the directory.
find path -name xxx Search for file named xxxx in the path directory. xxx is case sensitive and can be like *zzz
chmod xxx path Change files access permissions
df -k path Reports how much free space remains in the files system. -k reports the free space in KB.
du -kt path Reports the sizes of directories under path. Size reported in KB
oedit filename Edit a file in OMVS
obrowse filename Browse the file name
Review the items in the following table and complete the table with the appropriate entries for your enterprise. You need these values when you edit member BFGCUSTM.
Table 2. Parameters needed for member BFGCUSTM
Name Example data Comments
BFG_JAVA_HOME /java/java71_bit64_GA/J7.1_64/  
BFG_GROUP_NAME MQM  
LIBRARY SCEN.FTE.JCL Name of the MFT PDSE. You need a copy for each agent or logger task.
TMPDIR /tmp Read and write accessible USS path for temporary files.
SERVICE_TYPE AGENT or LOGGER  
NAME AGENT1  
BFG_PROD /var/ibm/wmqmft  
BFG_DATA   Complete as necessary
BFG_JVM_PROPERTIES   Complete as necessary
QMGR MQPV  
MQ_PATH /mqm/V8R0M0  
MQ_LANG E  
Db2®_HLQ SYS2.Db2.V10  
FTE_CONFIG   Used in migration
CREDENTIAL_PATH   Used in migration
DB_PROPS_PATH   Used in migration
BFG_WTO YES To get an MFT message on the syslog.
ADMIN_JOB1   Job card. All jobs are generated with the same JCL card.
OUTPUT_CLASS *  
JOBCARD1   This is the job card for the long running tasks, agents and loggers.
PATH bin:/usr/bin:/usr/sbin  
armELEMTYPE If ARM is being used, use the ARM ELEMTYPE specified in the ARM policy. For example, armELEMTYPE=SYSBFGAG for an agent or armELEMTYPE=SYSBFGLG for a logger. If ARM is not being used, set this parameter to blank; for example, armELEMTYPE=  
armELEMENT If ARM is being used, use the ARM ELEMENT value specified in the ARM policy for this agent or logger. If ARM is not being used, set this parameter to blank; for example, armELEMENT=  
coordinationQMgr MQPV Mandatory configuration
In addition you must review the following variables and supply values where necessary:

  • coordinationQMgrHost=
  • coordinationQMgrPort=
  • coordinationQMgrChannel=
  • connectionQMgr=
  • connectionQMgrHost=
  • connectionQMgrPort=
  • connectionQMgrChannel=
These properties are common to the AGENT or LOGGER. Note: Host, Port, and Channel are required for client connection but should be left blank for a bindings connection on the local machine.