Migrating a Version 5.0 broker to Version 6.0 on z/OS

Before you start
  • Ensure that you are familiar with the steps involved in creating a broker on z/OS.
  • The JCL (Job Control Language) uses the mqsimigratecomponents command to migrate a broker on z/OS. This command takes many parameters, which you must understand fully before attempting to migrate the broker.
  • Before migrating a broker, ensure that you do not have any aggregations in progress. When you migrate a broker to Version 6.0 any live data that is being stored for aggregations in progress will be lost.
  • If the broker runs in a locale that is not listed in the Locales topic, check that the code page is one of the supported code pages and that the locale is set up correctly.

To migrate a Version 5.0 broker to Version 6.0 on z/OS, complete the following steps:

  1. Stop the Version 5.0 broker.
  2. Back up the broker database tables.
  3. Create a new broker PDSE.
  4. Copy all broker JCL from the Version 6.0 installed SBIPPROC and SBIPSAMP PDSEs to the new broker PDSE and customize them all. See Customizing the broker JCL for more information.

    When you customize the new Version 6.0 JCL for this migration, do not make the ++HOME++ JCL variable the same value as the existing Version 5.0 component directory, otherwise the previous ENVFILE will be overwritten when you submit the BIPGEN job. Set the ++HOME++ variable to the Started Task user ID home directory (for example, /u/mq01brk).

    1. Customize the BIPEDIT file using values that are defined in the broker's Version 5.0 mqsicompcif file. Equivalent customization variables in mqsicompcif and BIPEDIT lists the customization variables that are used in the Version 5.0 mqsicompcif file, and the equivalent variables in the Version 6.0 BIPEDIT file.
    2. Copy any additional changes that you have made to the environment file, ENVFILE, and the ODBC initialization file, dsnaoini, to BIPBPROF and BIPDSNAO in the component data set. Submit the BIPGEN job to create the environment file ENVFILE.
    3. Customize and submit the BIPMGCMP job. This migrates the registry, queues and broker database. As part of the database migration, database tables are created, or deleted, and dropped, so you must you have the correct DB2 privileges. These privileges would be the same as those required for running the mqsicreatebroker command.
  5. Copy the started task JCL (BIPBRKP) to the procedures library. When you copy the started task, keep a second copy of the original in a safe place for backup purposes.
  6. The verification program will run when you start the Version 6.0 broker.
When you have migrated the broker, ensure that you have migrated the rest of the components: then see the post-migration tasks for information about tasks that you might want to perform after migration.
Related concepts
Brokers
Related tasks
Creating a broker on z/OS
Backing up WebSphere Business Integration Message Broker Version 5.0 resources
Creating the broker PDSE
Customizing the broker JCL
Copying the broker started task to the procedures library
Changing your locale on z/OS
Related reference
Equivalent customization variables in mqsicompcif and BIPEDIT
Sample BIPEDIT file
Installation Guide