Configuring a migrated broker on z/OS

Before you start

This task is part of the larger tasks: See either of the larger tasks to understand the context of this task and what you must do before you start this task.
To configure a migrated broker on z/OS, do the following:
  1. Create a new PDSE for the migrated broker. Allocate the PDSE with the same data set characteristics as those of the original broker PDSE. For detailed instructions on how to perform this task, see Creating the broker PDSE.
  2. Create a new directory for the migrated broker. For detailed instructions on how to perform this task, see Creating the broker directory on z/OS.
  3. Issue the mqsicreatebroker command as if you were creating a new broker. For more information about issuing this command and checking the output, see Customizing the broker. The command creates a Customization Input File (mqsicompcif) and a shell script called mqsicustomize, and stores them in the migrated broker's directory.
  4. Edit the Customization Input File. Note the following:
    • The DB2_BUFFER_POOL and DISTHUB_PATH keys are new to WebSphere Business Integration Message Broker.
    • You must replace the pattern ++JAVAHOME++ with the fully qualified path name of the directory where Java 1.4 is installed.
    • You must replace the pattern ++COMPONENT_PDS++ with the name of the migrated broker's PDSE.
    • Many of the remaining values, particularly those that refer to Hierarchical File System (HFS) directories, might already be correct for your installation. You can replace those that are not correct by copying the correct values from the Customization Input File of the original broker.

    For more information about performing this task, see Editing the Customization Input File (mqsicompcif) for a broker.

  5. Issue the mqsicustomize command. For more information about issuing this command and checking the output, see Customizing the broker. The command generates the members of the migrated broker's PDSE and populates the migrated broker's directory.
  6. Migrate the broker database tables. Follow the instructions in Migrating a broker's database tables on z/OS.
  7. Submit the job BIP$MQ01 to create the broker queues as if you were creating a new broker. Check that the job is completed successfully. The job is a member of the migrated broker's PDSE.
  8. Copy and compare the broker started task procedure:
    1. Save a copy of the started task procedure of the original broker.
    2. Submit the job BIP$UT01 to copy the started task procedure from the migrated broker's PDSE to your procedure library. The job is a member of the migrated broker's PDSE. The procedure library supplied by IBM is called SYS1.PROCLIB, but your installation might be using one with a different name. For more information about running this job, see Copying the broker started task procedure.
    3. Compare the started task procedure of the migrated broker with that of the original broker and make any necessary changes.
  9. Submit the job BIP$JCVP to run the Customization Verification Program (CVP). The job is a member of the migrated broker's PDSE. For more information about running this job and checking the output, see Running the Customization Verification Program (CVP).
  10. In the migrated broker's directory, compare the contents of environment file, ENVFILE, and ODBC initialization file, dsnaoini, with the contents of the corresponding files of the original broker. Incorporate into the migrated broker's files any changes you made to the original broker's files.
  11. In the directory migrated broker's directory/registry/broker name, do the following:
    1. Copy the file BrokerUUID from the corresponding directory of the original broker.
    2. Compare the contents of the directory, both the files and their contents, with the contents of the corresponding directory of the original broker. Note the following:
      • The file StatisticsMajorInterval is new to WebSphere Business Integration Message Broker.
      • If you have installed WebSphere Business Integration Message Broker in a different directory to where you installed WebSphere MQ Integrator Broker or WebSphere MQ Integrator, the contents of the files LilPath and FilePath will be different to the contents of the corresponding files of the original broker .
      • Because the migrated broker is using a different directory to that of the original broker, the contents of the file WorkPath will be different to the contents of the corresponding file of the original broker.

      The contents of the remaining files will be identical to the contents of the corresponding files of the original broker unless you have changed any of the original broker's files. If you have made changes, incorporate the changes into the migrated broker's files.

      Copy into the directory any files you have added to the corresponding directory of the original broker.

Related tasks
Migrating from WebSphere MQ Integrator Broker Version 2.1 to WebSphere Business Integration Message Broker Version 5.0
Migrating a Version 2.1 broker to Version 5.0
Creating the broker PDSE
Creating the broker directory on z/OS
Creating the broker runtime environment on z/OS
Editing the Customization Input File (mqsicompcif) for a broker
Customizing the broker
Migrating a broker's database tables on z/OS
Creating the broker queues
Copying the broker started task procedure
Running the Customization Verification Program (CVP)
Related reference
mqsicreatebroker command