Migrating from IBM Z Software Asset Management 8.2 to IBM Z Software Asset Management 8.3 (optional)

If you wish to port data from IBM Z Software Asset Management 8.2 to IBM Z Software Asset Management 8.3, you need to unload data from the 8.2 repository and reload the unloaded data into a new IBM Z Software Asset Management 8.3 repository. Note: This migration path is recommended for porting only a small 8.2 repository from one system/site to another. Please read the description in job HSISVS29 before considering this migration path.

Before you begin

The IBM Z Software Asset Management 8.3 repository can be either a Db2® database or an SQLite database. To perform the migration, run the following migration jobs:

About this task

Procedure

  1. HSISUN82– Run this job to unload the 8.2 repository. Ensure that all groups are unloaded, including group 3. To accomplish this, you need to comment the // NULL statement just before the //UNLOAD3 EXEC statement in order for jobsteps UNLOAD3, UNLOAD4, and UNLOAD5 to run. Otherwise, data from tables, TJOBDATA, TMODULE, AND TUSEMTD will not be selected for unload.
  2. HSISCUST– Run this customization job to create a new set of JCLLIB/PARMLIB members for IBM Z Software Asset Management. Before you decide where to define your 8.3 repository, read the comments in step 5, below.
  3. HSISDB01:
    1. Db2® - Run this job to create new storage groups.
    2. SQLite – Run this job to create a new zFS file.
  4. HSISDB02 – Run this job to create a new 8.3 GKB database.
  5. HSISDB03 – Run this job to create the new 8.3 repository database and database objects. LKB/LKU database objects are also created in this job, but note that LKB/LKU data are not unloaded in the 8.2 job, HSISUN82.
    1. Db2:If the same Db2 subsystem is used by the 8.2 and 8.3 repositories, you must define different database and schema names for the 8.3 Repository. Having identical database and schema names in the same Db2 system will result in Db2 errors.
    2. SQLite: You can use the same 8.2 database name and schema names for the 8.3 Repository, as long as the 8.3 Repository is defined in a different ZFS file system.
  6. HSISGKBL – Run this job to populate the GKB database. Always use the latest GKB version which can be found in the latest GKB PTF.
  7. HSISVS28 – Run this job to load data into the newly created 8.3 Repository, using the input file generated from step 1.
  8. Verify the loaded V8.3 Repository
    1. To verify that Group 3 data has been loaded, run the following SQL statements (replace REPZSCHM with the schema name of the V8.3 Repository). 
      SELECT COUNT(*) FROM REPZSCHM.TUSEMTD ;
SELECT COUNT(*) FROM REPZSCHM.TMODULE ;

      Expected result: The number of rows from these two tables must be identical to the number of rows unloaded from the V8.2 job, HSISUN82.

      Note: LKB/LKU data are not ported in this migration. LKB/LKU must be re-created in IBM Z Software Asset Management 8.3.

What to do next

After the successful completion of job HSISVS29, you must perform the following tasks to bring your V8.3 repository up to speed:
  1. HSISIQIM - Run IQ Imports with a setting of FULLREMATCH=Y for ALL LPARs that are defined in the repository. This will ensure that vendors and products are re-identified.

  2. //AGGR - Run at least one Aggregator jobstep (//AGGR) with a setting of COUNTUSAGEFULL=Y. This will ensure that vendors and products are populated with the latest information for the new V8.3 tables and columns.

    Jobstep //AGGR is included as part of job, HSISIQIM.

  3. To verify that vendor names have successfully been re-identified and populated in the above steps (1) and (2), run the following SQL statements (replace REPZSCHM with the schema name of the V8.3 Repository): 
    SELECT FVENDORNAME, FALTVENDORNAME 
 FROM REPZSCHM.TVENDOR ; 
SELECT VENDOR_NAME, ALT_VENDOR_NAME 
 FROM REPZSCHM.PRODUCT ;
    Expected result: Columns FALTVENDORNAME and ALT_VENDOR_NAME must display non-blank values.
  4. Lastly, run other operational jobs such as: HSISZCAT, HSISUIMP, HSISUMON, HSISANLO (Analyzer), and so forth.