WebSphere Message Broker, Version 8.0.0.7 Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS

See information about the latest product version

Performing in-place broker migration for a Version 6.1 broker on z/OS

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

Before you start:
  • Back up your broker resources by following the instructions in Backing up WebSphere Message Broker Version 6.1 resources.
  • For the latest details of all supported levels of hardware and software, visit the WebSphere Message Broker Requirements website.
  • You must migrate your queue managers to a supported version of WebSphere MQ before you can migrate your brokers.
  • Optional: If your applications use publish/subscribe functions, and you have message flows that include one or more Publication nodes, you must migrate your subscriptions to a supported version of WebSphere MQ before you migrate the broker; for more information, see Migrating publish/subscribe information to WebSphere MQ.
  • Ensure that you are familiar with the steps involved in Creating a broker on z/OS.
  • Ensure that you are familiar with the mqsimigratecomponents command, which the JCL (Job Control Language) file uses to migrate a broker.
  • Check that you have no aggregations in progress. When you migrate a broker to Version 8.0, any live data that is being stored for aggregations in progress is lost.
  • If the broker runs in a locale that is not listed in Locales, 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 6.1 broker to Version 8.0 on z/OS®, complete the following steps.

  1. Stop the Version 6.1 broker and the Version 6.1 Configuration Manager.
  2. Create a new broker PDSE.
  3. Copy all broker JCL files from the Version 8.0 installed SBIPPROC and SBIPSAMP PDSEs to the new broker PDSE. You can then customize these files. Some customization is required for migration, as described in the following substeps. You can update these and other files at a later date, if required. For more information, see Customizing the broker JCL.

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

    1. Customize the BIPEDIT file by using the values that are defined in the Version 6.1 BIPEDIT file where appropriate.
    2. Copy all additional changes that you have made to the Version 6.1 version of the BIPBPROF and BIPDSNAO files to these files in the Version 8.0 component data set. Submit the BIPGEN job to create the environment file ENVFILE.
    3. Customize and submit the BIPMGCMP (mqsimigratecomponents) job. This job migrates the registry, queue, and broker database; connection to the broker database of the previous broker is required to complete this action.

      After migration, all information in the broker database is stored in an internal repository in Version 8.0; the Version 8.0 broker does not require a database.

  4. Copy the renamed started task JCL file 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.
  5. Start the Version 8.0 broker. The verification program checks the configuration of the broker.

When you have completed migration, see Perform post-migration tasks for information about tasks that you might want to perform after migration.

Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2016Copyright IBM Corporation 1999, 2016.

        
        Last updated:
        
        Last updated: 2016-05-23 14:48:09


Task topicTask topic | Version 8.0.0.7 | bh23470_