Walk through using the Customization Dialog to generate the JCL jobs (CNTL and DATA data sets) for migrating a managed application server node. You must create these jobs before you can begin the actual migration.
Default values can be accepted for all fields and settings except for those that are explicitly identified in the following steps.
ex 'product_hlq.SBBOCLIB(BBOWSTRT)' 'options'
_________________________________________________________________
_________________________________________________________________
_________________________________________________________________
_________________________________________________________________
_________________________________________________________________
_________________________________________________________________
In the following panels, the migration data collection process begins.
_________________________________________________________________
_________________________________________________________________
System Locations (1 of 2) Specify the following V6.0.2 information, then press ENTER to continue. For some data sets, specify "Y" if they are in STEPLIB. Full Names of Data Sets PROCLIB.: SYS1.PROCLIB Run WebSphere Application Server from STEPLIB (Y/N)? Y SBBOLPA.: WAS601.WAS.SBBOLPA SBBOLOAD: WAS601.WAS.SBBOLOAD SBBOLD2.: WAS601.WAS.SBBOLD2 Use STEPLIB? SCEERUN.: CEE.SCEERUN Y SCEERUN2: CEE.SCEERUN2 Y SGSKLOAD: SYS1.GSK.SGSKLOAD Y (leave SGSKLOAD blank if all systems are at z/OS 1.6 or above)
_________________________________________________________________
_________________________________________________________________
_________________________________________________________________
System Environment Customization Specify the following to customize your system environment, then press Enter to continue. WebSphere Application Server for z/OS HFS Information Mount point....: /WebSphere/V6R0 Name...........: OMVS.WAS.CONFIG.HFS Volume, or '*' for SMS.: * Primary allocation in cylinders...: 250 Secondary allocation in cylinders.: 100
_________________________________________________________________
_________________________________________________________________
Also, specify the home location of the profile that will contain your Version 6.0.x migrated node under "V6 WebSphere Application Server home directory."
On this panel, you can also choose to enable tracing on your migration utilities, which will then remain enabled throughout the entire migration process. Enabling tracing generates a lot of output, and is generally intended for use only when directed by service support.
During migration, a backup copy of the Version 5.x configuration is required. The default location of this backup is already specified, though you can override if needed. You might need to specify a location other than the default if the /tmp HFS does not have adequate space to store the backup configuration. If you choose to override the default location of the backup copy, the best practice is to keep the same naming convention and just replace the /tmp portion with another path, /myTempmigrate/57638/fed_backup for example. The five-digit number (57638 in this example) is generated uniquely each time you create the migration jobs.
The migration output messages, which you will need to monitor throughout the migration process, are stored in tmp/migrate/57638 (after migration, the job output in this directory is NOT automatically deleted). The migration output messages are also appended to the JCL sysout messages, which can be viewed in SDSF.
After you have specified all values or left the defaults, press Enter to proceed to the next panel.
Server Customization (1 of 2) Specify the following to customize your migration, then press Enter to continue. V5.x WebSphere Application Server home directory: /WebSphere/V5R1M0 / AppServer V6 WebSphere Application Server home directory: /WebSphere/V6R0 / AppServer Migration Options Enable z/OS Migration Tracing: N Enable WASProfile Tracing....: N Enable WASPreUpgrade Tracing.: N Enable WASPostUpgrade Tracing: N Default Backup Directory: /tmp/migrate/57638/fed_backup User Specified Backup Directory:
_________________________________________________________________
The procedure names used to start the Version 6.0.x servers are also specified on this panel; new procedure names are required for Version 6.0.x. You can keep the defaults or change them if needed. The Customization Dialog creates new Version 6.0.x JCL using the procedure names specified here.
Because some of the migration jobs require running under a WebSphere Administrator ID, you need to supply a valid administrator ID and password here as well.
Specify values or accept defaults and press Enter to proceed.
Server Customization (2 of 2) Specify the following to customize your migration, then press Enter to continue. High Availability manager Host: The High Availability Manager Host MUST resolve to a single IP address. It can not be a multihomed host. Daemon Procedure name.........: BBO6DMN Controller Procedure name.....: BBO6ACR Servant Procedure name........: BBO6ASR Some migration tasks require running under the WebSphere Administrators account: WebSphere Administrator User ID.: XXXXXXX WebSphere Administrator Password: XXXXXXXX
Note: The "High Availability Manager Host" field was removed from the dialog in WebSphere Application Server for z/OS Version 6.0.2.
_________________________________________________________________
_________________________________________________________________
_________________________________________________________________
Now you need to provide a job card customized to your environment-specific requirements.
When you have entered your job card, press Enter. The generation process runs, and presents you with a list of job streams and files that have been created to perform the migration to Version 6.0.x. These jobs do not require any editing; they are to be submitted "as-is" during the migration process.
Enter an appropriate job card, and press Enter to proceed.
Generate Customization Jobs This portion of the Customization Dialog generates the jobs you must run after you complete this dialog process. You must complete the customization process before you generate the jobs with this step. If you have not done this, please return to that step. Jobs and data files will get generated into data sets: 'hlq.CNTL' 'hlq.DATA' If you wish to generate customization jobs using other data sets, then exit from this panel and select the "Allocate target data sets" option. All the jobs that will be tailored for you will need a job card. Please enter a valid job card for your installation below. The file tailoring process will update the job name for you in all the generated jobs, so you need not be concerned with that portion of the job cards below. If continuations are needed, replace the comment cards with continuations. Specify the job cards, then press Enter to continue. //jobname JOB (ACCTNO,ROOM),'IBMUSER',CLASS=A,REGION=0M //* //* //*
_________________________________________________________________
Processing for data set 'hlq.CNTL' ... Member BBOWMG1F successfully created. Member BBOWMG2F successfully created. Member BBOWMG3F successfully created. Member BBOWMMMT successfully created. Member BBOMMCR successfully created. Member BBOMMCRZ successfully created. Member BBOMMDN successfully created. Member BBOMMDNZ successfully created. Member BBOMMSR successfully created. Member BBOMMSRZ successfully created. Member BBOMMCP successfully created. Member BBOMMINS successfully created. Processing for data set 'hlq.DATA' ... Member BBOWBMPT successfully created. Member BBOWMMRF successfully created. ***
_________________________________________________________________
_________________________________________________________________
_________________________________________________________________
In this information ...Related tasks
| 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. |