Start of change

Migrating a Version 5.0 broker's database tables on z/OS

Before you start

This task is part of the larger task, Migrating a Version 5.0 broker to Version 6.0 on z/OS. See the larger task to understand the context of this task and what you must do before you start this task.

To migrate a Version 5.0 broker's database tables, submit the DB2 jobs shown in the following table. Submit the jobs in the order specified and check that each job completes successfully before submitting the next. A job completes successfully if each step, other than the step BAD, has a return code of 00 and the step BAD has a return code of FLUSH.

You need the following authorities to run the DB2 jobs:
  • SYSADM or SYSCTRL DB2 authority
  • ALTER access to the migrated broker's PDSE (for jobs BIP$DBM1)
  • READ and WRITE access to the migrated broker's directory and all its subdirectories (for job BIP$DBM2)
  • EXECUTE access to the directory, and all its subdirectories, where WebSphere Business Integration Message Broker is installed (for job BIP$DBM2)

The job BIP$DBM1 issues the SQL statements in the member BIPDBMG of the migrated broker's PDSE. These statements alter existing table spaces and create new table spaces. You might want to review and change the statements before submitting the job.

[INFO IN PARA ABOVE IS CHANGING, CHECK WITH MATT L OR DAVE G WHEN INFO AVAILABLE]

The job BIP$DB05 issues the SQL statement in the member BIPDBGR of the migrated broker's PDSE. As generated, this statement grants all users unlimited access to the broker database tables. You might want to review and change the statement before submitting the job.

[MIGHT BE ABLE TO REMOVE PARA ABOVE, CHECK WITH DAVE G. BIP$DB05 DOESN'T EXIST IN V6]

Order of submission DB2 job Description
1 BIP$DBM1 Alters existing table spaces and creates new table spaces
2 BIP$DBM2 Migrates existing broker database tables and creates new broker database tables
Related tasks
Migrating a Version 5.0 broker to Version 6.0 on z/OS


End of change