Maintaining BMC Software Administrative Products
BMC Software, Inc., Confidential and Proprietary Information
Chapter 3 Performing Additional Installation Tasks 3-37
using CATALOG
MANAGER 6.1 or
later
1. Migrate the DB2 catalog.
2. Run
HLQ
.CNTL(UPGRD4#5).
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).
using DASD
MANAGER PLUS
5.2.04
1. Migrate the DB2 catalog.
2. If the Distributed Data Facility (DDF) is
installed, 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 ASUINIT5
member in the
HLQ
.JCL library.
3. Rebind all DASD MANAGER PLUS
packages and plans by using
ASU
ssid
P (bind packages) and
ASU
ssid
B (bind plans) (where
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 DASD MANAGER PLUS
packages and plans by using
ASU
ssid
P (bind packages) and
ASU
ssid
B (bind plans) (where
ssid
is
the subsystem ID).
using DASD
MANAGER PLUS
5.3 or 5.4
1. Migrate the DB2 catalog.
2. Modify the ASUDB25E 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 DASD MANAGER PLUS
packages and plans by using
ASU
ssid
P (bind packages) and
ASU
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. Recreate the synonyms by
using the same synonym names, but
with the correct table names.
3. Rebind all DASD MANAGER PLUS
packages and plans by using
ASU
ssid
P (bind packages) and
ASU
ssid
B (bind plans) (where
ssid
is
the subsystem ID).
Table 3-17 Migrating DB2 Version 4 to Version 5 (Part 3 of 5)
If You Are Then To Fall Back Then
