Completing Migration › Migrate NSCNTL File

Migrate NSCNTL File

If you have not made any changes to your back-level file, you can use the r12 NSCNTL file and omit this step. If you made changes to your file, you should 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.

   Note: 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.

   Note: 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.

   Note: 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.

   Note: If you have changed any of the following Cat 004 Process-ID definitions in your old NSCNTL file for CA NetMaster NA, these changes are no longer required:

   • 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.