Before you start- Ensure that you are familiar with the steps that are involved in creating a broker on z/OS.
- The JCL 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 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.
- Stop the Version 2.1 broker.
- Back up the broker database tables.
- Create a new broker PDSE.
- Copy all broker JCL from the Version 6.0 installed
SBIPPROC and SBIPSAMP PDSEs to the new broker PDSE and customize them
all.
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 2.1 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).
- Customize the BIPEDIT file using values that are defined in the broker's Version 2.1 mqsicompcif file.
Equivalent customization variables in mqsicompcif and BIPEDIT lists the customization
variables that are used in the Version 2.1 mqsicompcif
file, and the equivalent variables in the Version 6.0 BIPEDIT
file.
- 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.
- Customize and submit the JCL BIPMGTB job. This creates LOB tablespaces.
The broker database on z/OS introduced
the use of LOB tablespaces in Version 5.0. They
were not used in Version 2.1, so they need to
be created at this point.
- 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.
- Copy the started task JCL to the procedures library. When
you copy the started task, keep a second copy of the original in a safe place
for backup purposes.
- The verification program runs when you start the Version 6.0 broker.