If your site has been using NSP Release 2.0, then you can migrate some of your existing data from NSP Release 2.0 and continue to use your current NSP Release 2.0 interface. At the same time, you will also have access to the new ISM Release 3.0 environment. ISM's migration feature allows you to convert your existing mainframe router definitions, router configuration data, and system setup information from NSP Release 2.0, so that this information is ready for use from within ISM Release 3.0.
This chapter provides detailed instructions on migrating from ISM Release 2.0 on the mainframe, which is stage three of the ISM installation process. This stage is optional. This chapter includes the following sections:
For the MVS systems programmer responsible for installing ISM Release 3.0 on the mainframe, complete the following tasks before you continue to migrate data from NSP Release 2.0:
- Read the "Preparing to Install ISM" chapter.
- Perform the installation stage two tasks described in the "Installing ISM" chapter.
If after you have migrated the NSP Release 2.0 data to ISM Release 3.0 and you decide that you no longer want to maintain the previous release of NSP on your mainframe, you can remove the NSP Release 2.0 version from the host. For more information about removing NSP Release 2.0, see the "Deinstalling NSP Release 2.0" chapter.
You can benefit in the following ways when you choose to migrate your NSP Release 2.0 data to ISM Release 3.0:
- The ISM router configuration data and definitions, ISM setup, and operator profiles are available to you from within ISM Release 3.0.
- You can continue to use the NSP Release 2.0 interface while you gain familiarity with ISM Release 3.0.
Though you can continue to use your NSP Release 2.0 interface, once you try ISM's new features and use its improved interface, you will probably choose to perform all of your router management functions within the enhanced environment of ISM Release 3.0.
Note The NSP Release 2.0 user interface runs from within the ISM Release 3.0 environment after ISM Release 3.0 has been installed and configured. When the ISMMGR task is running, you can access the NSP user interface using the nsp command from NetView, but you are not actually running the NSP software installation. You cannot run the NSPMGR task at the same time that you are running the ISMMGR task.
Migrating your NSP Release 2.0 router definitions and configuration data allows you to convert a copy of your existing NSP Release 2.0 data files so that they are compatible with ISM Release 3.0. The original NSP Release 2.0 data files remain intact.
When you migrate your NSP Release 2.0 installation, you convert a copy of your existing NSP Release 2.0 data files to the new VSAM key structures and new VSAM data sets that are supported in ISM Release 3.0. After you have installed ISM Release 3.0 and converted the NSP Release 2.0 file structure, you can access either the NSP user interface or the new ISM user interface. The ISM Release 3.0 data is stored in two distinct groups of databases depending on whether you are running the nsp command or the ism command from NetView.
Data that you migrate can be seen from within the ISM Release 3.0 user interface, but any new data that you may collect while running the older NSP user interface can only be seen when you run the nsp command.
Note Data gathered when running the
nsp command after the initial migration has been performed cannot be migrated again.
If you set up NetView to automatically initialize the ISM tasks in the previous release of ISM (NSPMGR, NSPMGRA, and NSPMGRB), be sure that you have updated the NetView production CLIST to specify the new ISM Release 3.0 autotask members.
To verify that you have completed this task, see the "Setting Up NetView to Initialize ISM" section in the "Installing ISM" chapter.
Once you have installed ISM Release 3.0, you are ready to convert your NSP Release 2.0 files. The following two NetView CLISTs are provided with the ISM installation to automatically perform the conversion functions:
- NSPCONV--Converts the archived router configuration files. These files are updated for year-2000 compatibility.
- NSPCONVR--Copies the NSP Release 2.0 system setup, operator profiles, and router definitions for compatibility with ISM Release 3.0.
To convert the NSP Release 2.0 files complete the following tasks:
Step 1 Verify that NSP Release 2.0 (NSPMGR) or ISM Release 3.0 (ISMMGR) is not currently started.
- To stop NSPMGR, type the nspinit reset command at the NetView command prompt and press Enter.
- To stop ISMMGR, type the isminit reset command at the NetView command prompt and press Enter.
Step 2 From a NetView command prompt, type the nspconv command and press Enter. Verify that the output displayed is similar to the following output and that you receive the "NSP to ISM Configuration Conversion complete" message:
C CNM01 NSP1095I No data found in ISMDSx data base for XXXXXXX NSPDISCU
C CNM01 NSP1095I No data found in ISMDSx data base for ATLANTAX NSPDISCU
C CNM01 NSP1095I No data found in ISMDSx data base for COLOMAXX NSPDISCU
C CNM01 NSP1095I No data found in ISMDSx data base for CORGW1XX NSPDISCU
C CNM01 NSP1095I No data found in ISMDSx data base for CWBC01XX NSPDISCU
C CNM01 NSP1095I No data found in ISMDSx data base for CWBC01XX NSPDISCU
C CNM01 NSP1095I No data found in ISMDSx data base for CWBC02XX NSPDISCU
C CNM01 CONVERSION DONE FOR CWBC03XX NLINES=127
C CNM01 CONVERSION DONE FOR CWBC04XX NLINES=250
C CNM01 NSP1095I No data found in ISMDSx data base for CWBC05XX NSPDISCU
C CNM01 NSP1095I No data found in ISMDSx data base for CWBC06XX NSPDISCU
C CNM01 NSP1095I No data found in ISMDSx data base for CWBC07XX NSPDISCU
C CNM01 NSP1095I No data found in ISMDSx data base for CWBC08XX NSPDISCU
C CNM01 CONVERSION DONE FOR CWBC09XX NLINES=124
>> This is the message that occurs when a configuration file is converted.
C CNM01 NSP1095I No data found in ISMDSx data base for CWBC10XX NSPDISCU
>>> Statements deleted for documentation purposes.
C CNM01 NSP1095I No data found in ISMDSx data base for XYARMXXX NSPDISCU
C CNM01 NSPCONVR 170 Records Converted
.. This means that 170 routers were checked for configuration files.
C CNM01 NSPCONVR NSP to ISM Configuration Conversion complete
Step 3 Once the NSPCONV CLIST has executed, type the nspconvr command and press Enter. Verify that the output displayed is similar to the following output and that you receive the "NSP to ISM Conversion complete" message:
* CNM01 NSPCONVR
C CNM01 NSPCONVR 170 Records Converted
>>This means that 170 routers were migrated.
C CNM01 NSP1052I Record added/updated. NSPCONVS
C CNM01 NSPCONVS System Setup Converted
.. This means that the Setup Member was converted from NSP to ISM
C CNM01 NSPCONVU 70 ISM USER Records Converted
>> This means that 70 user profiles were converted.
C CNM01 NSPCONVR NSP to ISM Conversion Complete
Once you have migrated your NSP Release 2.0 data to ISM Release 3.0, you need to configure the ISM setup options. For more information about setting up ISM, see the "Configuring ISM" chapter.
After you have migrated your NSP Release 2.0 data to ISM Release 3.0 and decide that you no longer want to maintain the previous release on your mainframe, you can remove NSP Release 2.0 from the mainframe. For more information about removing NSP Release 2.0, see the "Deinstalling NSP Release 2.0" chapter.
