Migrating a Version
5.0 broker to Version 6.0 on z/OS
To migrate a Version
5.0 broker to Version 6.0 on z/OS,
complete the following steps:
Stop the Version
5.0 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.
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).
Customize the BIPEDIT file using values that are defined in the broker's Version
5.0mqsicompcif 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.
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 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 (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.
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: