After you generate Job Control Language (JCL) jobs for migrating a standalone application server node to WebSphere® Application Server Version 7.0, 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 BBOMBINS members of the CNTL dataset that was used to generate your jobs. Follow these customized instructions to complete the process of migrating your standalone application server to Version 7.0.
The BBOWMG3B and BBOWBPRO jobs referenced in these instructions must be submitted by a user ID that has control over the file system.
All other jobs must be submitted by a user ID that has control over the file system.
For help, read Troubleshooting migration.
Before you perform the migration, Version 7.0 requires a file system to be present for your new configuration. You can run the BBOMBHFS or BBOMBZFS job to create and mount a new configuration file system, or you can mount one manually. Either way, you must have a file system for your Version 7.0 configuration created and mounted before you proceed. This configuration file system is the target of the migration; your Version 5.1.x or Version 6.x configuration file system is the source.
The BBOMBHFS or BBOMBZFS job 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 your migration jobs.
Ensure that you allocated, created, and mounted your configuration file system datasets either manually or using the BBOMBHFS or BBOMBZFS job 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 BBOMBCP copies the generated JCL procedures used to start the servers to the specified procedure library. Your Version 7.0 configuration must use different JCL procedures from those used by your Version 5.1.x or Version 6.x configuration. This utility will update the new Version 7.0 configuration, substituting your new JCL names in place of the names that existed in your original Version 5.1.x or Version 6.x configuration.
Submit the BBOMBCP job, and verify a return code of 0.
new controller same identity used in JCL name V5.1.x or V6.x configuration | | RDEFINE STARTED AZ6ACR.* STDATA(USER(AZACRU) GROUP(AZCFG) TRACE(YES))
The BBOWMG1B job enables all servers on the application server node being migrated to start in Peer Restart and Recovery (PRR) processing mode. PRR processing mode resolves any outstanding transactions, clears the transaction logs, and stops the server. The BBOWMG2B job disables PRR mode and returns all servers to normal operating state.
The daemon must be at the highest version level of any of the servers that it manages on the same LPAR. It will be at the Version 7.0 level when the server is started.
You must stop the Version 5.1.x or Version 6.x application server before proceeding.
Perform this step only if you previously configured the transaction XA partner log or compensation log on the Version 5.1.x or Version 6.x server to use a log stream.
You can use the BBOLOGSD and BBOLOGSA jobs that were created during Version 5.1.x or Version 6.x customization if you configured the server initially to use the log stream.
//RLSP1A JOB 'xxxx,yyy,?','USERID',MSGCLASS=H, // CLASS=J,MSGLEVEL=(1,1),REGION=4M,NOTIFY=&SYSUID //STEP1 EXEC PGM=IXCMIAPU //STEPLIB DD DSN=SYS1.MIGLIB,DISP=SHR //SYSPRINT DD SYSOUT=* //SYSIN DD * DATA TYPE(LOGR) REPORT(YES) /* Default to show output of job */ DELETE LOGSTREAM NAME(P1ACEL6A.W51ASA2.D) DEFINE LOGSTREAM NAME(P1ACEL6A.W51ASA2.D) LOWOFFLOAD(20) HIGHOFFLOAD(79) STG_DUPLEX(YES) DUPLEXMODE(UNCOND) STG_DATACLAS(OPERLOG) STG_SIZE(5000) HLQ(Q10RRS) LS_SIZE(5000) LS_DATACLAS(OPERLOG) STRUCTNAME(WAS_LOGRLS) /*
The BBOWMG3B job performs the physical migration of the Version 5.1.x or Version 6.x node to Version 7.0 based on the information that you supplied when you generated your migration jobs. Submit the BBOWMG3B job, verify that you are getting return codes of 0, and review the log files in the migration temporary directory on the 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.
BBOWBPRO creates the Websphere Application Server home and default profile.
BBOWBPRE runs the migration pre-upgrade process.
BBOWBPOS runs the migration post-upgrade and finish-up (change file permission) processes.
Use the existing commands that you would use to start a Version 5.1.x or Version 6.x application server, but replace the RACF STARTED procedure name with the value that you entered for the controller procedure name when you generated your migration jobs. This command starts the Version 7.0 application server. Wait until the server is finished initializing before proceeding.
BBOO0019I INITIALIZATION COMPLETE FOR WEBSPHERE FOR z/OS CONTROL PROCESS BBOS001At this point, your migration to Version 7.0 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. |