Prepare to Upgrade (Migrate)

When you upgrade, you migrate data from the old region to the new region, for example, from the 12.1 region to the 12.2 region. You can also migrate data as part of a same-release migration, for example, cloning or replicating the same release of CA NetMaster from one region to another. See Install or Upgrade CA NetMaster Products for an overview of the upgrade process.
nwmscl122
When you upgrade, you migrate data from the old region to the new region, for example, from the 12.1 region to the 12.2 region. You can also migrate data as part of a same-release migration, for example, cloning or replicating the same release of CA NetMaster from one region to another. See Install or Upgrade CA NetMaster Products for an overview of the upgrade process.
Some migration tasks require actions on the region that you are migrating from. If you plan to reuse resources, ensure that you perform the following tasks before you shut down your existing region for the last time. These resources can include the access control block (ACB) name and started task name.
 Do not migrate or re-use content from CC2DPLD, CC2DMAPO, CnnnnEXEC, MODSDIS, or PANLDIS datasets from older product releases.
 
 
2
 
2
 
 
Meet the Prerequisites
Before you complete this section, verify that you have performed all tasks in Prepare to Install, including completing your installation worksheets and verifying the installation prerequisites.  
Migrate Parameter Group Values by Migrating Your Initialization File
If you want to migrate your previous parameter group values to your new product region, generate an INI file now if you do not already have one.
The process of migrating your initialization file consists of the following steps. Details follow for each step.
  1. If you have not already generated your INI file, generate the initialization file in the previous region.
  2. Configure the initialization file for the new region.
  3. Start the new region using your initialization file.
Generate the Initialization File
Perform these tasks to configure a region from an initialization file. If you are deploying multiple regions, each region must be configured for its local environment. When you have configured your first region, you can build an initialization file from that region. You can then configure it for use with your other regions. This process removes the need to customize each region with Customizer.
The initialization file is produced from a running region for your product.
 
Complete the following steps:
 
  1. From the Primary Menu, enter 
    /CUSTOM
    .
    The Customizer panel appears.
  2. Select the option G - Generate INI Procedure.
    The Generate INI Procedure panel appears.
  3. Enter the data set name and the member name of the file in the Generate INI File Details section.
    The data set must be in the commands concatenation of the RUNSYSIN member for the region in which it is used.
  4. Ensure that the member name and data set name are correct. Enter 
    YES
     in the Replace Member? field if you are replacing an existing member.
  5. Press F6 (Action).
    The initialization file is generated.
  6. Make a note of the data set and member names and press F6 (Confirm).
    The details are saved.
Configure the Initialization File
The initialization file must be configured before it can be used for other regions. You can perform this configuration as follows:
  • Configure an individual initialization file for each region.
  • Configure a common initialization file for multiple regions.
You can use system variables and static system variables with both of these methods. The variables substitute for the initialization parameters in the INI file.
You can delete the configuration section for a whole parameter group to let the new regions use the defaults.
 Review and update the file if necessary. Verify that names such as ACBs, data sets, and interfaces are suitable for the new region. After you start the region, you can review the parameter values and can regenerate the initialization file if necessary. Generation of the INI file replaces custom code, such as code that includes MVS system symbols, with the actual values. If you regenerate the file, reapply the custom code.
 During the region initialization, the initialization file passes all parameter values to the INI file procedure and the procedure overwrites the parameter group values. If you do 
not
 want to overwrite some settings, comment out or delete the corresponding statements in the initialization file.
Configure Individual Initialization Files
You can customize an initialization file from one region so that it can be used for another region, as follows:
 
  1. Open the initialization file in edit mode using your TSO editing tool.
  2. Substitute the parameters in the initialization file with 
    one 
    of the following values:
    • Hard-coded data set names for the region in which the file is used
    • System variables
    These substitutions enable the initialization file to work in regions with different data sets than the region in which it was generated.
  3. Save the changes to the initialization file.
  4. Copy the initialization file to the region TESTEXEC or 
    one
     of the other libraries in the COMMANDS concatenation.
  5. Repeat steps 1 through 4 for each initialization file needed.
 To facilitate this procedure, ensure that the source region and the destination regions have the same product sets.
Configure a Common Initialization File
You can customize an initialization file using variables so that it can be used for multiple regions, as follows:
  1. Create a data set that is available to every region to be initialized from the common initialization file, for example, PROD.INIFILES.
  2. Add the newly created data set to the COMMANDS concatenation of the RUNSYSIN member to every region to be initialized from the common initialization file.
    RUNSYSIN is located in TESTEXEC.
  3. Copy the generated initialization file into the new INIFILES data set.
  4. Open the initialization file in edit mode using your TSO editing tool.
  5. Replace the relevant generated variables in the initialization file with the following system variables:
    •  
      &ZDSNQLCL
      The local VSAM data set qualifier.
    •  
      &ZDSNQSHR
      The shared VSAM data set qualifier.
    •  
      &ZACBNAME
      The primary VTAM ACB name that the region uses.
    •  
      &ZDSNQLNV
      The local non-VSAM data set qualifier.
    •  
      &ZDSNQSNV
      The shared non-VSAM data set qualifier.
    •  
      &ZNMDID
      The domain identifier.
    •  
      &ZNMSUP
      The system user prefix.
  6. Replace the relevant generated variables in the initialization file with the z/OS static system symbols as follows:
    •  
      &SYSCLONE
      The short name for the system.
    •  
      &SYSNAME
      The name of the system.
    •  
      &SYSPLEX
      The name of the sysplex.
    •  
      &SYSR1
      The IPL VOLSER.
  7. Save the changes to the initialization file.
Configure Your Region to Start From the Initialization File
The INIFILE parameter in the RUNSYSIN member specifies the name of the initialization file.
Updating your RUNSYSIN member causes your region to set its initialization parameters from the initialization file. All Customizer parameter settings are overwritten. If you update a parameter group online and you want to keep the changes for subsequent region startups, regenerate the initialization file.
 
Follow these steps:
 
  1. Open your RUNSYSIN member using a text editor.
  2. Insert the line PPREF='INIFILE=
    membername
    ' into your RUNSYSIN member.
  3. Save the member.
Prepare to Migrate Knowledge Base
If you want to migrate your knowledge base, consider the following:
  • To keep a copy of an old distributed ResourceView template (for example, you might have modified it), copy this template to a new template image version above 0009. You can copy a template image from the Template System Image List panel (/RADMIN.T.I).
  • To keep a copy of an old distributed EventView rule set (for example, you might have modified it), make a copy of this rule set under a different name. (If the rule set is associated with a system image, update the association accordingly.) You can copy a rule set from the Ruleset List panel (/EADMIN.R.R).
Prepare for Multi-system Network Migration
You cannot link and synchronize a new region with a region running an earlier release of the product.
You can use migration mode to help in the migration of an existing multisystem network.
Migration mode gives to the new product region the same level of visibility as normal synchronization, but a slightly reduced command capability. The main difference between migration mode and normal synchronization is that the databases are 
not
 synchronized. Maintaining the database at a single point is 
not
 possible in migration mode.
If you are upgrading multiple synchronized regions to this release, perform the following steps to plan for it:
  1. Ensure that your existing multi-system network has at least two focal regions. If you have only one focal region, unlink a subordinate region and relink it as a focal region.
  2. Choose a focal region, and unlink it from the multi-system network.
  3. Upgrade the focal region, and perform migration tasks.
  4. After you have completed all of the steps in this guide, link your new focal region in migration mode to an existing focal region.
    After the new region is linked back, you can monitor all resources for all linked regions from the new region.
  5. Select the next product region that you want to upgrade, and unlink it.
  6. Upgrade this product region, and then synchronize it to the focal region that you upgraded in Step 3.
  7. Continue until all regions are upgraded.
Each region can be migrated as required without losing the benefits of multi-system monitoring.
 
Notes:
 
  • You only perform knowledge base migration for the first region because the focal knowledge base contains details of all linked regions.
  • You only link the first new focal region in migration mode.