Hypothetical Case Study—Migrating from Tivoli NetView › The Migration Plan

The Migration Plan

The team produces a migration plan, to include the following broad tasks.

Note: Everyone migrating from NCCF faces the same typical tasks.

1. Identify and Prepare

   Identify what procedures really need to be migrated. Prepare them for migration. Make sure that the procedures work before migrating them. (A little time spent on this at the start can save a lot of unnecessary effort later.)

2. Familiarize

   Examine and experiment with the standard diagnosis and monitoring functions of CA NetMaster. The team may be able to use some of these to replace functions that are currently implemented by NetView REXX.

3. Analyze

   Analyze the NetView REXX procedures that need to be migrated. The team uses the NetMaster REXX analysis program to report on which REXX procedures need changing, and why.

   This program compares the NetView REXX commands, pipe stages, and functions in use with those provided by the CA NetMaster NetView REXX emulation environment. This provides an initial broad survey of the effort required for the next steps.

4. Migrate

   Update and test until the procedures work correctly. This is an iterative process. Where you start and where you go next is guided by the output of the REXX Analysis report, run during the analysis step.

   1. Update procedures—Make code changes to the NetView REXX procedures to enable them to run successfully under CA NetMaster. For any individual procedure, code changes might range from none to extensive.
   2. Test all procedures—Test the NetView REXX procedures under the Tivoli NetView Emulation environment. If they do not work, correct them.
5. Verify

   Bring everything together. Test and verify the migrated REXX procedures and any new NCL procedures against the production network.