Activities for migrating a standalone application server node
after you have generated the appropriate JCL jobs using the Customization
Dialog include activities related to general preparation, transaction-log
clearance, and node migration.
This checklist is intended to provide a quick reference.
More
details can be found under Preparing to migrate a standalone application server node to Version 6.0.x.
Key
similarities with an ND configuration:
- You must still create "skeleton" CNTL/DATA data sets through the Customization
Dialog.
- You must still allocate and mount a new HFS to act as the target for the
new Version 6.0.x configuration, either manually or using BBOWMBMT.
- You must still run BBOWMG3B to perform the migration.
Key differences from an ND configuration:
- You must clear transaction logs using BBOWMG1B; you do not have to do
this for a deployment manager migration.
- You must disable PRR mode using BBOWMG2B; you do not have to do this for
a deployment manager migration.
- There is no deployment manager node to migrate.
Clear transaction logs for application server node
Check
off |
Item |
|
Stop
server in the standalone application server node. |
|
Run BBOWMG1B. Check for success. |
|
Restart the application server
to clear transaction logs. It will start and then automatically stop. |
|
Run BBOWMG2B to disable PRR mode. |
|
Migrate application server node
Check
off |
Item |
|
Ensure
that all servers are stopped, including the daemon server. |
|
Run BBOWMG3B and check for success. |
|
Start application servers. |
|