Moving an MFT agent to a new z/OS LPAR

It is sometimes necessary to move an IBM MQ Managed File Transfer for z/OS agent from one LPAR to another, while keeping the agent in the same IBM MQ Managed File Transfer topology with the same coordination and command queue managers. The steps needed to do this depend on how the agent being migrated was originally created.


Move the IBM MQ Managed File Transfer for z/OS agent in one of the following ways:

  • If the agent was originally created using a customized version of the SCSQFCMD library, use the library to recreate it on a new LPAR.
  • If the agent was originally created by running USS commands, use the commands to recreate it on a new LPAR.

Note:

Scheduled transfers and transfer templates are stored on the coordination queue manager for an IBM MQ Managed File Transfer topology. This task assumes that the coordination queue manager is not part of the movement work. In this case, any scheduled transfers and transfer templates associated with the agent being moved remain on the existing coordination queue manager after the move is completed.


Procedure

  • Move an agent created using a customized version of the SCSQFCMD library. If the agent was created using a customized version of the SCSQFCMD library, we can use that library to recreate the IBM MQ Managed File Transfer for z/OS environment, and the agent configuration on the new LPAR. To do this, complete the following steps:
    1. Copy the customized version of the library from the original LPAR to the new LPAR.
    2. Edit the BFGCUSTM member in the customized version of the library on the new LPAR, and make sure that the parameter values are still valid.
    3. Run the BFGCUSTM member on the new LPAR, to create all of the JCL needed to configure the environment and create the agent.
    4. Run the BFGCFCR member to define the coordination queue manager to be used by the agent on the new LPAR, and create the directory structure needed to store the IBM MQ Managed File Transfer configuration.
    5. Next, run the BFGCMCR member, to define the command queue manager to be used by the agent on the new LPAR.
    6. Run the BFGAGCR member to recreate the agent and its configuration.
    7. Ensure that the system queues used by the agent exist on the queue manager for that agent.

    If the agent being moved has resource monitors associated with it, we need to recreate the monitors on the new agent. To do this, complete the following steps:

    1. On the original LPAR, run the BFGMNLI member to export the definitions for the resource monitor associated with the original agent to XML files.
    2. Copy the XML files containing the resource monitor definitions to the new LPAR.
    3. Use the BFGMNCRS member in the SCSQFCMD library on the new LPAR to import the resource monitor definitions stored in the XML files. This results in the monitors being created on the new agent.

  • Move an agent created by running commands in USS. If the agent was originally created by running USS commands, we can use commands to recreate the agent on a new LPAR. To do this, complete the following steps:
    1. Run the fteSetupCoordination command on the new LPAR, to define the coordination queue manager to be used by the agent, and create the directory structure needed to store the IBM MQ Managed File Transfer configuration.
    2. Run the fteSetupCommands command to define the command queue manager to be used by the agent on the new LPAR.
    3. Run the fteCreateAgent command to recreate the agent and its configuration.
    4. Ensure that the system queues used by the agent exist on the queue manager for that agent.

    If the agent being moved has resource monitors associated with it, we need to recreate the monitors on the new agent. To do this, complete the following steps:

    1. On the original LPAR, run the fteListMonitors command, specifying the -ox parameter, to export the definitions for the resource monitor, associated with the original agent, to XML files.
    2. Copy the XML files containing the resource monitor definitions to the new LPAR.
    3. Run the fteCreateMonitor command on the new LPAR, specifying the -ix parameter, to import the resource monitor definitions stored in the XML files. This results in the monitors being created on the new agent.

Parent topic: Configure Managed File Transfer for z/OS