BMC Software, Inc., Confidential and Proprietary Information
3-36 Administrative Products for DB2 Installation Guide
Maintaining BMC Software Administrative Products
using ALTER or
CHANGE
MANAGER 6.1C or
later installed on
DB2 Version 4
1. Migrate the DB2 catalog.
2. If the Distributed Data Facility (DDF) is
installed for CHANGE MANAGER,
drop the current synonyms to the old
communication database tables.
Then, recreate the synonyms by using
the same synonym names, but with
the new catalog table names. For an
example, refer to the ALUINIT5 or
ACMINIT5 member in the
HLQ
.JCL
library.
3. Rebind all ALTER (ALU) or CHANGE
MANAGER (ACM) packages and
plans by using
prdssid
P (bind
packages) and
prdssid
B (bind plans)
(where
prd
is the product code and
ssid
is the subsystem ID).
Then, you will be operating in toleration
mode.
1. Check your synonyms to make sure
that they point to the correct table
names.
2. If the synonyms do not point to the
correct names, drop the current
synonyms. Then, recreate the
synonyms by using the same
synonym names, but with the correct
table names.
3. Rebind all ALTER (ALU) or CHANGE
MANAGER (ACM) packages and
plans by using
prdssid
P (bind
packages) and
prdssid
B (bind plans)
(where
prd
is the product code and
ssid
is the subsystem ID).
As an alternative, you can perform a Full
installation of ALTER or CHANGE
MANAGER 6.2D. Then, you will be
operating in exploitation mode.
Provided that ALTER or CHANGE
MANAGER still exists in toleration mode,
use the fallback procedures described for
toleration mode and remove the product
in exploitation mode. Any data that you
added while you were in exploitation
mode will not be available in toleration
mode.
using CATALOG
MANAGER 5.3 or
5.4
1. Migrate the DB2 catalog.
2. Modify the ACTDB25E worklist
member in the
HLQ
.JCL library.
3. Execute the worklist using a modified
copy of the $I40INST job that the
INSTALL job dialog generated.
4. Rebind all CATALOG MANAGER
packages and plans by using
ACT
ssid
P (bind packages) and
ACT
ssid
B (bind plans) (where
ssid
is
the subsystem ID).
Then, you will be operating in exploitation
mode.
1. Check your synonyms to make sure
that they point to the correct table
names.
2. If the synonyms do not point to the
correct names, drop the current
synonyms. Then, recreate the
synonyms by using the same
synonym names, but with the correct
table names.
3. Rebind all CATALOG MANAGER
packages and plans by using
ACT
ssid
P (bind packages) and
ACT
ssid
B (bind plans) (where
ssid
is
the subsystem ID).
Table 3-17 Migrating DB2 Version 4 to Version 5 (Part 2 of 5)
If You Are Then To Fall Back Then
