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

Migrate a broker to use the enhanced facilities available in a Version 6.0 broker domain.

Before you start
  • Ensure that you are familiar with the steps involved in creating a broker on z/OS®.
  • The JCL (Job Control Language) migration job file uses the mqsimigratecomponents command to migrate a broker on z/OS. This command takes many parameters, which you must understand fully before you attempt to migrate the 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 are 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 WebSphere® Message Broker Version 5.0 broker to Version 6.0 on z/OS:

  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 jobs 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.

    You must take a backup copy of your Version 5.0 ENVFILE, which is stored in the directory referenced by the ++HOME++ JCL variable, before you submit BIPGEN from the Version 6.0 component data set. Subsequently, if you want to migrate back to Version 5.0, restore ENVFILE, either from the backup file location, or by submitting BIPGEN from the Version 5.0 component data set, before you start the Version 5.0 broker.

    1. Customize the BIPEDIT file with values that are defined in the mqsicompcif file for the Version 5.0 broker. See Equivalent z/OS customization variables in mqsicompcif and BIPEDIT for details of the customization variables.
    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 job migrates the registry, queues, and broker database. As part of the database migration, database tables are created, or deleted, and dropped, therefore you must you have the correct DB2® privileges. These privileges are the same as those required for running the mqsicreatebroker command.
  5. Copy the started task job 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 runs when you start the Version 6.0 broker.
When you have migrated the broker, migrate the rest of the components:

When you have completed these tasks, 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 z/OS customization variables in mqsicompcif and BIPEDIT
Sample BIPEDIT file
Installation Guide
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2009Copyright IBM Corporation 1999, 2009.
Last updated : 2009-01-07 15:22:08

ah23835_