This topic applies only on the z/OS operating system.

Customization Dialog walk-through for migrating a standalone application server node

Walk through using the migration option within the Customization Dialog to generate the JCL jobs (CNTL and DATA data sets) for migrating a standalone application server node. You must create these jobs before you can begin the actual migration.

Before you begin

Default values can be accepted for all fields and settings except for those that are explicitly identified in the following steps.

Procedure

  1. Invoke the WebSphere Application Server for Version 6.0.x Customization Dialog.
    ex 'product_hlq.SBBOCLIB(BBOWSTRT)' 'options'
    • Example product_hlq: WAS601.WAS
    • Example options: appl(az)

    _________________________________________________________________

  2. From the first menu page, select option 4: Migrate V5.x Nodes to V6 Nodes.

    _________________________________________________________________

  3. On the next panel, select option 1: Migrate a V5.x standalone application server node to V6.

    _________________________________________________________________

  4. Allocate partitioned data sets that you will use to store the generated migration jobs and supporting data. On the "V5.x standalone Application Server Migration" menu, select option 1: Allocate target data sets.

    _________________________________________________________________

  5. On the "Allocate Target Data Sets" panel, specify your high-level qualifier, and then press Enter to proceed to the next panel. Accept the defaults on the next two panels that specify the parameters for the .CNTL and .DATA data sets.

    _________________________________________________________________

  6. Back on the "V5.x standalone Application Server Migration" menu, select option 2: Define variables. In the following panels, the migration data collection process begins.

    _________________________________________________________________

  7. On the "Define Variables to migrate a V5.x standalone Application Server Node" menu, select option 1: System Locations (directories, HLQs, etc.).

    _________________________________________________________________

  8. The System Locations (1 of 2) panel collects information about your Version 6.0.x installation libraries, and whether you intend to place the load modules in STEPLIB. Correctly specifying STEPLIB is essential to a successful migration. It is likely that your Version 5.x modules are currently in LPA/LNKLST, and that you will begin with your Version 6.0.x libraries being defined in STEPLIB. Specify whether to put your Version 6.0.x modules in STEPLIB and continue to the next panel.
    Example:
    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)                                  

    _________________________________________________________________

  9. On the "System Locations (2 of 2)" panel, specify your Version 6.0.x WebSphere Application Server SMP/E home directory (/usr/lpp/zWebSphere/V6R0 for example). After specifying your Version 6.0.x home directory, press Enter to proceed.

    You will be taken back to the "Define Variables to migrate a V5.x standalone Application Server Node" menu.

    _________________________________________________________________

  10. Back on the "Define Variables to migrate a V5.x Standalone Application Server node" menu, option 1 is marked as completed. Now select option 2: System Environment Customization.

    _________________________________________________________________

  11. The System Environment Customization panel is where you specify the Version 6.0.x configuration root HFS, which is where the configuration for the node being migrated is physically stored. You can choose to use an existing Version 6.0.x HFS if you already have an appropriate HFS on the node being migrated. If you choose to use an existing Version 6.0.x HFS, you need to ensure that the mount point you specify here is present before running the migration utilities (BBOWMG1B, BBOWMG2B, and so on) that are created through these dialogs. If you choose to create a new Version 6.0.x HFS on the node being migrated, the actual creation of the new HFS will not occur until you run the BBOWMBMT job during the migration process, after you complete this walk-through (see Migrating a standalone application server node for more information). Specify either an existing mount point or a new mount point and press Enter to proceed.
    Example:
                                                                       
    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

    _________________________________________________________________

  12. Back on the "Define Variables to migrate a V5.x Standalone Application Server node" menu, options 1 and 2 are marked as completed. Select option 3: Server Customization.

    _________________________________________________________________

  13. On the Server Customization (1 of 2) panel, specify the source node that you are migrating under "V5.x WebSphere Application Server home directory." 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, /myTemp/migrate/47002/base_backup for example. The five-digit number (47002 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/47002 (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.

    Example:
    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/47002/base_backup         
         User Specified Backup Directory:                                  
    

    _________________________________________________________________

  14. On the Server Customization (2 of 2) panel, specify the High Availability Manager Host, a feature in Version 6.0.1 that has no previous value from Version 5.x. The value you enter here is the IP address of the LPAR you are migrating. This value must resolve to a single IP address, and you can use a dotted decimal address.

    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.

    Specify values or accept defaults and press Enter to proceed.

    Example:
    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                            
                                                                                                                 

    Note: The "High Availability Manager Host" field was removed from the dialog in WebSphere Application Server for z/OS Version 6.0.2.

    _________________________________________________________________

  15. After completing the Standalone Server Customization (2 of 2) panel, you will be returned to the "Define Variables to migrate a V5.x standalone application server node" menu. Press PF3 to return to the "V5.x standalone Application Server Migration" menu.

    _________________________________________________________________

  16. On the "V5.x Standalone Application Server Migration" menu, select option 3: Generate customization jobs.

    _________________________________________________________________

  17. On the Generate Customization Jobs panel, you can see the names of the .CNTL and .DATA data sets that have been customized based on your previous input.

    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.

    Example:
    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                 
    //*                                                                     
    //*                                                                     
    //*                                                                     
    

    _________________________________________________________________

  18. A list of JCL jobs that have been generated for your migration is displayed. When processing has completed, press Enter to proceed.
    Example:
    Processing for data set 'hlq.CNTL' ... 
    Member BBOWMG1B successfully created.                
    Member BBOWMG2B successfully created.                
    Member BBOWMG3B successfully created.                
    Member BBOWMBMT successfully created.                
    Member BBOMBCR successfully created.                 
    Member BBOMBCRZ successfully created.                
    Member BBOMBDN successfully created.                 
    Member BBOMBDNZ successfully created.                
    Member BBOMBSR successfully created.                 
    Member BBOMBSRZ successfully created.                
    Member BBOMBCP successfully created.                 
    Member BBOMBINS successfully created.                
                                                         
    Processing for data set 'hlq.DATA' ... 
    Member BBOWBMPT successfully created.                
    Member BBOWMBRF successfully created.                
    ***                                                                                                   

    _________________________________________________________________

  19. You are now back on the "V5.x standalone Application Server Migration" menu. You should now save your configuration variables for future reference by selecting option S: Save Customization Variables.

    _________________________________________________________________

  20. You have now completed the job generation process and are ready to begin the process of migration. See instructions for performing the migration by selecting option 4: View instructions. Also, proceed to the article Migrating a standalone application server node for instructions on performing the migration.

    _________________________________________________________________




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.

Task topic    

Terms of Use | Feedback

Last updated: Sep 20, 2010 11:08:29 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=vela&product=was-nd-mp&topic=tinsappcdwalkthru
File name: tins_appcdwalkthru.html