Upgrade (Migrate) Your Product

To migrate the CA NetMaster products, perform the tasks on this page, beginning with the prerequisite tasks. Typically, you perform these tasks as part of completing an upgrade that you started in Prepare to Upgrade. You can also perform these tasks 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
To migrate the CA NetMaster products, perform the tasks on this page, beginning with the prerequisite tasks. Typically, you perform these tasks as part of completing an upgrade that you started in Prepare to Upgrade. You can also perform these tasks 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.
The contents of the following files are migrated during the Region Setup process: IPFILE, MSDB, NEWSFIL, NTSLOG, PSPOOL, UAMS, VFS, and SSIDB.
Unless noted otherwise, each section applies to all CA NetMaster products, including 
CA SOLVE:FTS
.
 
 
2
 
2
 
 
After you completed the tasks on this page, perform the tasks on the following child pages, if applicable:
Prerequisite Tasks
Before you complete this section, perform these tasks:
  • Verify that you have performed the tasks in Prepare to Install and Prepare to Upgrade 
  • Verify that you have installed and configured the CA NetMaster 12.2 products, using either the CA CSM or Pax file methods
  • Start your region if you have not already done so.
Migrate the Knowledge Base
This section applies to all CA NetMaster products except 
CA SOLVE:FTS
.
The knowledge base is where you store your resource definitions. System images, in which you define the resources a region manages, are part of the knowledge base.
For more information about the knowledge base, see Reference.
As part of region setup, a knowledge base is created, comprising the following data sets:
  • RAMDB
  • ICOPANL
Migrate any existing data that you want to keep to this knowledge base.
Do not use the IDCAMS REPRO command to manage the definitions in the knowledge base.
In r11.5, Graphical Monitor support was added to this product. If you are migrating from a prior release, and have created your own resource groups, ensure that they do not use the following names:
ASMON
CSM
IPNDE
ROUTR
VIPA
CIP
EE
NCPMN
STACK
CIPRT
FT
OSA
TCPIP
Migrate Your Existing Knowledge Base
If you are migrating multiple synchronized regions, you only perform this task for the first focal region. You do not have to perform this task when migrating subsequent regions because when you link the regions, the knowledge base is synchronized.
Keep the old knowledge base until your new product regions are performing correctly.
 
To migrate your existing knowledge base to a new product region, complete the following steps:
 
  1. Shut down the region using your existing knowledge base.
  2. From the new product region, enter 
    /RAMUTIL.M
    .
    The RAMDB Migration Utility panel appears.
  3. Perform the following steps:
    1. Specify the data set name for your existing RAMDB in the Old RAMDB Data Set Name field.
      The data set name is 
      dsnpref.rname
      .RAMDB.
    2. Specify 
      NO
       in the Selective Migration field to migrate all definitions.
      The utility migrates only customized definitions from the old knowledge base to the knowledge base in the new product region. Definitions that are not migrated are listed for further action.
    3. Press F6 (Action) to display the Migration Statistics panel.
  4. After migration has completed, perform the following steps:
    1. Look for the components that have a non-zero value in the Not Copied column. (The utility does not copy a component if the component exists in the new knowledge base.)
      You might have customized some of these components and want to copy them.
    2. Enter 
      R
       next to the components that you want to copy, and copy the records.
      The copying options depend on whether a component contains multiple objects, such as a system image, or is the object itself, such as a user profile definition.
  5. After you have copied the components, exit the migration utility.
 If you do not want to move directly from your established regions to the new product regions, you can run the two releases in parallel.
How to Copy Multi-Object Components
The products use template images $TEMPLAT 0001 through 0009 for the distribution of new and updated template definitions. Do not overwrite or replace them in the knowledge base.
If a component contains multiple objects, you operate on the component as a whole. You can perform the following actions:
  • Merge the component in the old knowledge base into the component in this knowledge base. Only objects that do not exist in this knowledge base are migrated. Existing objects are unchanged.
  • Overwrite the existing objects in this knowledge base with the objects in the old knowledge base. This operation does not affect any objects that are not in the old knowledge base.
  • Replace the component in this knowledge base with the component in the old knowledge base.
To migrate specific objects, see the activity log and use the RMMUAD05 messages to determine which objects have not been copied. You can then delete the appropriate objects and redo the migration by merging (to list only the RMMUAD05 messages in the log, enter 
TEXT RMMUAD05
).
How to Copy Single-Object Components
For a component that is the object, do 
one
 of the following:
  • Rename the component to create a copy of the component in this knowledge base using a different name.
  • Overwrite the existing component in this knowledge base with the component in the old knowledge base.
Apply Updated Templates
After you have migrated your knowledge base, review the distributed templates. For information about changes to the distributed knowledge base, see the
 Release Notes
 for your product.
 
Follow these steps:
 
  1. Review the distributed templates. Determine whether they are suitable for your requirements:
    1. Enter 
      /RADMIN.T
      .
      The Template Definition menu appears.
    2. Select the option that lists the definitions you want to review.
  2. If you use any template image other than the default (as specified in the OPSYSIDS parameter group), copy the required definitions to your working template images.
    When you copy definitions from the distributed to your working images, you can replace your working definition with a distributed definition of the same name. If you want to retain your working definition, make a copy of the definition beforehand.
    If you want to copy all the new definitions, follow these steps:
    1. Enter 
      /RADMIN.T.I
      .
    2. Enter 
      C
       next to the distributed image.
    3. Update the Database Version field with your working image version, and press F3 (File).
      This step starts the process to merge the distributed template image with the target image. The Confirm System Image Merge panel appears.
    4. Specify 
      YES
       in the Enter 'YES' to OVERLAY Like-named Components field.
    If you want to copy changed definitions, copy them one by one.
  3. If you want to apply a template, perform the following steps. The template is applied to all the resource definitions (in one or more system images) that use it.
    a. Enter R next to the parent template image.
    b. Enter AP next to the resource template that you want to apply.
    c.To ensure that the template is applied in full, specify RESET and REPLACE.
    If you want to retain an old definition, make a copy of the definition before you apply the template.
Migrate Custom MODS Files and Entries, if Applicable
If you have not created your own MODS file, or added entities to the default MODSUSR file, skip the steps described in this section.
Perform one of the following tasks, whichever applies to your environment:
  • Copy All Entries in Your MODS File
  • Copy Individual MODS Definitions
Copy All Entries in Your MODS File
To keep using all user-defined entities in your MODS file, use the IDCAMS REPRO command to copy the contents of your MODS file to the file for the new region.
Copy Individual MODS Definitions
To keep using some but not all user-defined entities in your MODS file, use the /MODSADE, as explained in this section.
You can copy the following entities from your MODS file:
  • Application definitions
  • Command definitions
  • Criteria definitions
  • Help definitions
  • List definitions
  • Menu definitions
  • Message definitions
  • Print Services definitions
  • Report definitions
  • Table definitions
Complete the following steps:
  1. Allocate the old MODS file by updating the MODSFILES parameter group in Customizer.
    For information about how to update the parameter group, enter 
    /PARMS
     on any panel, select $NM MODSFILES, and press F1 (Help).
  2. Enter 
    /MODSADE
     from any panel.
    The Entity Administration Menu appears.
  3. Specify the source and target files. (For example, copy your entities from the MODSUSR data set used by the old region to the MODSUSR data set used by this region.) Select 
    C - Copy Definitions
    .
    The Entity List panel appears.
  4. Select the entities that you want to copy, and press Enter.
  5. De-allocate the old MODS file by updating the MODSFILES parameter group in Customizer.
Migrate Custom Panel Files, If Applicable
You can copy some or all custom panel files, as follows: 
  • Copy All Custom Panel Files
  • Copy Individual Custom Panel Definitions
  • If you have not created your own PANL file or added entities to the default PANLUSR file, do not perform this step.
  • You do not need to migrate installation-defined icon panels in the ICOPANL file. These panels are recreated during the knowledge base migration.
  • The PANELLIBS parameter group in Customizer controls the allocation of panels data sets. For more information, enter 
    /PARMS
     from any panel, select $NM PANELLIBS, and press F1 (Help).
Copy All Custom Panel Files
To keep using all custom panel files, use the IDCAMS REPRO command to copy the contents of your PANELS file to the file for the new region.
Copy Individual Panel Files
To keep using some but not all custom panel entities, follow these steps:
  1. Allocate the old PANELS file by updating the PANELLIBS parameter group in Customizer.
  2. Enter
     /PANELS
     on any panel.
    The Panel Maintenance Menu appears.
  3. Specify the source and target files. (For example, copy your panels from the PANLUSR data set used by the old region to the PANLUSR data set used by this region.) Select 
    M -
     
    Move/Copy Panels Between Libraries
    .
    The Panel Copy List appears.
  4. Select the entities that you want to copy, and press Enter.
  5. De-allocate the old PANELS file by updating the PANELLIBS parameter group in Customizer.
Migrate IPLOG Records, if Applicable (
CA NetMaster NM for TCP/IP
 Only)
If you want to use the IPLOG records from a previous release such as 12.0 or 12.1, use IDCAMS REPRO to migrate them to Release 12.2
Migrate NSCNTL Data (If Necessary, for 
CA NetMaster NM for SNA
 Only)
If you have not made any changes to your back-level file, you can use the Release 12.2 NSCNTL file and omit this step. If you made changes to your file, execute the NSCNTL file migration utility to identify your changes.
 
To migrate your NSCNTL file using the $SNNSCNV utility procedure
 
  1. Start the region, using the latest distributed NSCNTL file.
  2. Enter 
    =O
     at a command prompt. The Operator Console Services (OCS) panel appears.
  3. Enter 
    $SNNSCNV DSN=
     
    datasetname
     at the ==> prompt. The procedure reads the old NSCNTL file, produces a report, and displays it.
    datasetname
     is the DSN
     
    name of the back-level NSCNTL file.
  4. Scroll through the migration report, reading the explanatory text and observing categories that are highlighted to indicate a change.
    To print the migration report for easy reference, press F11 (Print).
  5. To migrate your old NSCNTL file to the current release, press F6 (Migrate). The NSCNTL : Record Migration List panel appears. 
    F6 (Migrate) appears only if both of the following apply:
    • The target NSCNTL file, that is the file allocated to this region, with the current product release, has update access. The Migration Summary section of the report instructs you how to enable migration if the file is read-only.
    • There are records (SNAMS focal points and entry points or CNM code points) that qualify for migration.
    If you have changed any of the following Cat 004 Process-ID definitions in your old NSCNTL file for CA NetMaster NA, you do not need to reapply them:
    AL0001, AL0002, AL0003, AL0010 EV0001, EV0002, EV0003, EV0004
  6. Type 
    C
     beside each record that you want to copy to your new NSCNTL file and press Enter. The migration utility updates the Status column to show the effect of this action. The new status shown for each record is as follows:
    •  
      Copied
       - if the record did not already exist in the new file
    •  
      Replaced
       - if the record already existed in the new file
    For further information, see the comments contained within the migration utility.
How to Run Your Old Region in Parallel with the New Region
If your existing region uses global mode AUTOMATED to perform desired state management, you can ease your new product regions into production as described in this section.
If you do not want to move directly from your existing regions to the new regions, you can do the following:
  1. Create an equivalent region for each of your existing regions, so that you have a mirrored pair on each system.
  2. Initially, have the existing region performing automation, and the new region running in the global mode of MANUAL (that is, merely monitoring) but using the same data.
  3. Gradually, reverse the global mode of operation between the mirrored pairs until the new regions are performing automation.
This suggested scenario provides you with a hot backup, letting you instantly swap from a new region to the established region if you experience any problems. You can then correct the problem before swapping back to try the new region again.