Maintaining BMC Software Administrative Products
BMC Software, Inc., Confidential and Proprietary Information
Chapter 3 Performing Additional Installation Tasks 3-33
using DASD
MANAGER PLUS
5.4.04
1. Migrate the DB2 catalog.
2. Modify the ASUDB26E worklist
member in the
HLQ
.JCL library.
3. Execute the worklist using a modified
copy of the $I40INST job that the JCL
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 toleration
mode.
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
6.1
1. Migrate the DB2 catalog.
2. Run
HLQ
.CNTL(UPGRD5#6).
Then, you will be operating in exploitation
mode.
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 catalog
indirection and
ALTER, CHANGE
MANAGER,
PATROL DB-Alter,
or PATROL
DB-Change
Manager in
toleration mode
1. Perform a Full installation of ALTER or
CHANGE MANAGER 6.2E. Then, you
will be operating in exploitation mode.
2. Reinstall catalog indirection.
1. Provided that the previous indirection
still exists, remove the indirect copy or
view in exploitation mode.
2. Provided that ALTER, CHANGE
MANAGER, PATROL DB-Alter, or
PATROL DB-Change Manager still
exists in toleration mode, use the
fallback procedures described for
toleration mode to remove the product
in exploitation mode.
3. Rebind all indirect packages and
plans for the previous version by using
prdssid
Z (bind packages) and
prdssid
B (bind plans) (where
ssid
is
the subsystem ID).
using catalog
indirection and
CATALOG
MANAGER 6.1 or
later
Reinstall catalog indirection. 1. Provided that the previous indirection
still exists, remove the indirect copy or
view in exploitation mode.
2. Provided that CATALOG MANAGER
still exists in toleration mode, use the
fallback procedures described for
toleration mode to remove the product
in exploitation mode.
3. Rebind all indirect packages and
plans for the previous version by using
prdssid
Z (bind packages) (where
ssid
is the subsystem ID).
Table 3-15 Migrating DB2 Version 5 to Version 6 (Part 4 of 4)
If You Are Then To Fall Back Then
