After you generate JCL jobs for migrating a deployment manager to WebSphere Application Server for z/OS Version 6.1, you can perform the actual migration by running those jobs. When you generated your custom migration jobs, you also created customized instructions for preparing and running the migration jobs in the BBOMDINS members of the CNTL data set that was used to generate your jobs. Follow these customized instructions to complete the process of migrating your deployment manager to Version 6.1.
All other jobs must be submitted by a user ID that has control over the file system.
Migrating a deployment manager from Version 5.x to Version 6.1.x redeploys all application binaries when the deployment manager is restarted. This action results in the deployment manager recycling all the applications across the sysplex. This can cause an outage in a sysplex that is set up for high availability if the synchronization settings are not disabled.
For help in troubleshooting problems when migrating, see Troubleshooting migration.
Before you perform the migration, Version 6.1.x requires a configuration file system to be present for your new configuration. You can run BBOMDHFS or BBOMDZFS to create and mount a new configuration file system, or you can mount one manually. Either way, you must have a configuration file system for your Version 6.1.x configuration created and mounted before you proceed. This configuration file system is the target of the migration; your Version 5.x or 6.0.x configuration file system is the source.
BBOMDHFS or BBOMDZFS creates a mount point directory, allocates the configuration's file system, and mounts the file system at whatever value you specified for the mount point when you generated you migrations jobs.
Ensure that you have allocated, created, and mounted your configuration file system data sets either manually or using BBOMDHFS or BBOMDZFS before you proceed. The mount point should be owned by the WebSphere Admin ID, and have permissions of at least 755. The new configuration file system structures should be included in BPXPARM so that they will be mounted at the next IPL.
The migration utility BBOMDCP copies the generated JCL procedures to start the servers to the specified procedure library. Your Version 6.1.x configuration must use different JCL procedures from those used by your Version 5.x or 6.0.x configuration. This utility will update the new Version 6.1.x configuration, substituting your new JCL names in place of the names that existed in your original Version 5.x or 6.0.x configuration.
Submit BBOMDCP, and verify a return code of 0.
new controller same identity used in JCL name V5.x or 6.0.x configuration | | RDEFINE STARTED AZ1DCR.* STDATA(USER(AZDCRU) GROUP(AZCFG) TRACE(YES))
A deployment manager migration does not require bringing the node into and out of PRR mode as standalone application server and federated node migrations do. There are two less jobs to submit for a deployment manager migration, therefore, and you are ready to perform the physical migration.
BBOWMG3D is the job that performs the physical migration of the Version 5.x or 6.0.x deployment manager to Version 6.1.x based on the information that you supplied when you generated your migration jobs. Submit BBOWMG3D. Verify that you are getting return codes of 0, and review the log files in the migration temp directory on the configuration file system. The migration temporary directory is temporary_directory_location/nnnnn, where temporary_directory_location is the directory specified for the temporary directory location (/tmp/migrate by default) and nnnnn is the numeric value generated for the migration identifier when you generated your migration jobs.
Ensure that all nodes on the deployment manager's LPAR in the same cell are shut down.
WebSphere Application Server for z/OS Version 6.1.x requires that the daemon process be at the highest level of code of any of the servers that it manages on the same LPAR. It will be at the Version 6.1.x level when the deployment manager is started. If the deployment manager manages nodes on the same LPAR in a mixed-cell environment, the daemon started JCL procedure for both the deployment manager and the down-level nodes must have both the Version 6.1.x libraries and those of the highest level of the down-level nodes in STEPLIB.
If you are migrating from Version 5.1 and you have an application server node on the same LPAR as the deployment manager, for example, add the following to both your Version 6.1.x and Version 5.1 daemon JCL procedure's "Z" member ("Z=BBO5DMNZ" ) using your library names:
//*STEPLIB Setup //* //STEPLIB DD DSN=hlq61.SBBOLD2,DISP=SHR // DD DSN=hlq61.SBBOLOAD,DISP=SHR // DD DSN=hlq61.SBBOLPA,DISP=SHR // DD DSN=hlq51.SBBOLD2,DISP=SHR // DD DSN=hlq51.SBBOLPA,DISP=SHR //*
After you migrate all nodes to Version 6.1.x and before you remove the previous version's libraries from the system, you must update the daemon JCL procedure and remove the previous version's libraries from the STEPLIB concatenation. Failure to do so will result in a failure of the daemon to start.
Use the existing commands that you would use to start a Version 5.x or 6.0.x application server, but replace the RACF STARTED procedure name with the value that you entered in the deployment manager panel for the controller procedure name when you generated your migration jobs. This command starts the Version 6.1.x deployment manager. Wait until the server is finished initializing before proceeding.
BBOO0019I INITIALIZATION COMPLETE FOR WEBSPHERE FOR z/OS CONTROL PROCESS BBODMGRAt this point, your migration to Version 6.1.x is complete.
In this information ... | IBM Redbooks, demos, education, and more(Index) Use IBM Suggests to retrieve related content from ibm.com and beyond, identified for your convenience. This feature requires Internet access. Most of the following links will take you to information that is not part of the formal product documentation and is provided "as is." Some of these links go to non-IBM Web sites and are provided for your convenience only and do not in any manner serve as an endorsement by IBM of those Web sites, the material thereon, or the owner thereof. |