Migrating a Managed File Transfer for z/OS installation to the next version of the product
Follow these instructions to migrate an IBM MQ Managed File Transfer for z/OS installation to Version 9.2 of the product.
Overview
From IBM MQ Version 9.2 the install process for Managed File Transfer for z/OS (MFT) changed on z/OS.
MFT no longer has its own SMP/E install. Instead, MFT is installed at the same time as the queue manager code, using the IBM MQ for z/OS SMP/E install. For details on the install process see: Installing Managed File Transfer for z/OS.
From Version 9.2 of the product, the MFT libraries are placed into an mqft directory underneath the directory containing the IBM MQ for z/OS UNIX System Services Components. For example: /mqm/V9R2M0/mqft.
Note that the mqft directory structure is the same as before, apart from the bin directory.
In earlier versions of MFT the bin directory was a peer of the mqft directory. That is, you might have installed MFT into a /mqmfte/V9R1Mn/ directory, and that directory would have contained both an mqft and a bin directory.
From Version 9.2 of the product, the bin directory is located underneath the mqft directory; for example: /mqm/V9R2M0/mqft/bin.
Important: As part of migrating Version 9.2 of the product, we should:
- Adjust any scripts you had that are dependent on this directory structure.
- Look at any JCL which we use to launch MFT processes, and adjust the BFG_PROD and MQ_PATH variables appropriately.
For example, if you have installed IBM MQ for z/OS Unix System Services Components into /mqm/V9R2M0/ the value of MQ_PATH will be /mqm/V9R2M0/ and the value of BFG_PROD will be /mqm/V9R2M0/mqft.
Finally, the fte* commands no longer require that the LIBPATH environment variable contains the path to the IBM MQ for z/OS Java libraries.
Migration process
The process of migrating MFT to a new version is:
- Install IBM MQ for z/OS Version 9.2, including the MFT component.
- Wait until your agents are not processing any transfers, and stop them.
- Stop your loggers.
- For each agent or logger that is being administered by JCL:
- Copy the SCSQFCMD data set from the IBM MQ for z/OS Version 9.2 installation into a new data set specific to that agent or logger.
- Edit BFGCUSTM inside the copy of the data set and fill in all of the required parameters.Note: We should set the BFG_DATA variable to the same value that the agent or logger was using previously. This allows the agent or logger to pick up its existing configuration.
Make sure you set the BFG_PROD and MQ_PATH variables correctly, as described in point 2, in the overview section of this topic.
- Run BFGCUSTM inside the copy of the data set. This generates a new set of JCL that can be used to administer the agent or logger.
- Start the agent or logger again.
- For each agent or logger that is being administered from USS:
- The fte* commands used to administer the agent or logger are located in a mqft/bin directory under the IBM MQ for z/OS UNIX System Services Components install; for example: /mqm/V9R2M0/mqft/bin.
We need to adjust any scripts calling these commands, to take account of this change.
- The commands no longer require that the IBM MQ for z/OS Java lib directory, for example, /mqm/V9R2M0/java/lib is in the LIBPATH environment variable.
If you manually set the LIBPATH environment variable to contain the IBM MQ for z/OS Java lib directory, no longer do so.
This variable might also be set in a .wmqfterc file, in which case we should remove it.
- Additionally, you might need to update the STEPLIB environment variable if the queue manager has been migrated at the same time.
This variable might be set in a .wmqfterc file as described in Environment variables for MFT on z/OS.
- Finally, set the BFG_DATA environment variable to the same value as it was before, to ensure the agent or logger has access to its existing configuration.
This variable might be set in a .wmqfterc file as described in Environment variables for MFT on z/OS.
- Start the agent or logger again
Parent topic: Migrating IBM MQ for z/OS - order of tasks Parent topic: Migrating IBM MQ Managed File Transfer
Related information