This article answers several frequently asked questions about the WebSphere Application Server for z/OS migration process.
Can I simply point to the new Version 6.0.x data sets and restart my servers?
No. WebSphere Application Server for z/OS Version 6.0.x requires that you migrate your Version 5.x configuration up to the Version 6.0.x level.
What is the basic migration process?
Install the SMP/E code for WebSphere Application Server for z/OS Version 6.0.x. Use the Customization Dialog walk-throughs to create the migration utilities that you need to perform the migration. When you run these jobs a new configuration is created—separate from your existing Version 5.x configuration—that is an exact copy in every way except that it will be at the Version 6.0.x level.
Is migration a node-by-node activity?
Yes. The process of migrating the configuration involves running the supplied utilities against each node in your configuration.
With a standalone application server you have only one node, but that node needs to be migrated. The steps are essentially the same as you would perform for any other node, except you do not have to have a deployment manager up and running. See Checklist of migration activities for standalone application server node for a checklist of activities for migrating a standalone application server node.
What do the migration utilities do?
The migration utilities serve the following purposes:
Utility | Purpose |
BBOWMG1B (standalone application server migrations) | Enables all servers on the node being migrated
to be configured to start in PRR processing mode. After this job completes,
you must start all servers on the node being migrated and wait for them to
terminate. PRR processing mode resolves any outstanding transactions, clears
the transaction logs, and terminates the server. This job is not needed for
a deployment manager migration, and it is optional for configurations that
do not use XA connectors. This job is required only if you are using XA adapters and you need to migrate the XA logs. Check your resource providers in the Version 5.x administrative console by going to Resources > JDBC providers and checking to see if you have chosen any XA providers such as DB2, Cloudscape, and so on. |
BBOWMG1F (federated node migrations) | |
BBOWMG2B (standalone application server migrations) | Disables PRR mode and returns
all servers to normal operating state. There is no need to start all servers
after this job completes. This job is not needed for a deployment manager
migration, and it is optional for configurations that do not use XA connectors. This job is required only if you are using XA adapters and you need to migrate the XA logs. Check your resource providers in the Version 5.x administrative console by going to Resources > JDBC providers and checking to see if you have chosen any XA providers such as DB2, Cloudscape, and so on. |
BBOWMG2F (federated node migrations) | |
BBOWMBMT (standalone application server migrations) | Optional: Creates an HFS and mount point for the Version 6.0.x configuration root. If you want to use an existing HFS to contain the Version 6.0.x configuration, you must manually create the mount point specified in the Customization Dialog rather than run this job. In either case, the HFS and mount point must be created before proceeding with the migration. |
BBOWMDMT (deployment manager migrations) | |
BBOWMMMT (federated node migrations) | |
BBOWMG3B (standalone application server migrations) | Performs the migration of the node from Version 5.x to Version 6.0.x. |
BBOWMG3D (deployment manager migrations) | |
BBOWMG3F (federated node migrations) | |
BBOMBCP (standalone application server migrations) | Copies the generated JCL procedures to start the servers to the specified procedure library. If you choose to have your Version 6.0.x configuration make use of different JCL start procedure names, this utility will update the new Version 6.0.x configuration, substituting your new JCL names in place of the names that existed in your original Version 5.x configuration. |
BBOMDCP (deployment manager migrations) | |
BBOMMCP (federated node migrations) |
Where should the migration jobs be run?
Run the jobs on the same system on which the node being migrated resides.
What happens when a node is migrated?
The migration utilities will copy the contents of your present Version 5.x configuration HFS into a new, separate configuration HFS, changing them along the way as needed to support Version 6.0.x:
Will my existing configuration be lost during migration?
During the migration the original Version 5.x configuration tree is unaffected. If for some reason the migration fails before completing, your previous configuration still exists.
If my node has multiple application servers, will all of them be migrated?
Yes. The utility will detect all servers and migrate all, including the Node Agent. One invocation of the migration utilities against the node will take care of all the servers in the node.
Do the servers in a node have to be stopped to perform the migration?
Is it possible to have a cell operating with only some of the nodes migrated and others not?
Yes, that is possible. Version 5.1 can coexist with Version 6.0.x in the same cell and on the same LPAR. When migrating from Version 5.0.x, however, you need to migrate the deployment manager node and other application server nodes on that same MVS image one right after the other — or essentially at the same time. Version 5.0.x and Version 6.0.x nodes cannot exist in the same cell on the same LPAR.
Can my newly-migrated Version 6.0.x deployment manager still "talk" to Version 5.x nodes?
Is there a sequence to performing a multinode migration?
Is it possible to have cells at Version 6.0.x coexist with other cells at Version 5.x?