Migrating from IBM Z Software Asset Management 8.3 to IBM Z Software Asset Management 8.3.1 (Db2® database)

When you upgrade to IBM Z Software Asset Management 8.3.1 for Db2® database, no porting of data within the Repository database is required, as there are no changes to database objects. The 8.3 and 8.3.1 GKB databases are identical, so no changes are required. To use the new REST API feature, see REST API.

Before you begin

Make a backup of your 8.3 Repository database by running job HSISUT01 from your 8.3 JCLLIB, or equivalent in-house backup job.

Make a backup or rename your JCLLIB and PARMLIB data sets.

Migration planning and consideration:

  1. If your existing 8.3 Repository database (including LKB/LKU) and GKB use different schema names, then you need to modify the migration jobs to suit your site requirements.

  2. If you have multiple 8.3 repositories sharing the same 8.3 GKB database, you can continue to use the 8.3 GKB database after migration to 8.3.1.
  3. Continue to run your 8.3 Usage Monitor job/started task (HSISUMON/HSIJMON), but stop the Analyzer, and do not run any 8.3 operational jobs during the migration.

About this task

Perform these migration tasks for every Db2® Repository in your IBM Z Software Asset Management environment.

Procedure

  1. In 8.3.1, make a copy of the HSISCUST member in the hsi.SHSISAMP data set and modify the following parameters:
    1. Set the value of the DBTYPE parameter to DB2.
    2. Set HSIINST to a different value to the one defined for the existing 8.3 system. This will ensure that the JCLLIB/PARMLIB datasets are created with different names. As stated in the section, “Before you begin”, backup or rename copies of 8.3 JCLLIB/PARMLIB datasets.
    3. Set the value of the SYS parameter to the same system that is defined for your existing 8.3 Repository database.
    4. Set the value of the DB parameter to the same value that is defined for your existing 8.3 Repository database.
    5. Set the value of the DBGKB parameter to the same value that is defined for your existing 8.3 Global Knowledge Base (GKB) database.
    6. Set the value of the REPZSCHM parameter to the same value that is defined for your 8.3 Repository database.
    7. Set the value of the GKBZSCHM parameter to the same value that is defined for your 8.3 GKB database.
    8. Set values of the remaining Db2® parameters (e.g. DBSSID, LOC) to the same values that are defined for your 8.3 Repository database.
    9. The default value for the BPIX parameter is set to BP8K0 and must be activated before usage. Compressed indexes require Bufferpools to be defined with BP8K0-BP8K9, BP16K0-BP16K9, or BP32K-BP32K9. It cannot be BP0-BP49.
  2. Submit the HSISCUST job. DO NOT share members of JCLLIB/PARMLIB between 8.3 and 8.3.1. Some member names may be the same, but the contents differ.
  3. Edit and update jobs in the JCLLIB library and parameters in the PARMLIB library if there are special site requirements.
  4. Submit job HSISGKBL to populate the 8.3.1 GKB database.
    A GKB level is shipped with this migration. To download the latest GKB level, see "Updating the Global Knowledge Base".

What to do next

After migration, use the following approach to manage the implementation to the latest version:
  1. You must apply the latest GKB update. This will ensure that all product identifications are up to date when you run the Inquisitor Import job, HSISIQIM. For each repository, run HSISIQIM for all LPARs before you run any Usage Import (HSISUIMP) jobs. You can continue to use existing 8.3 Inquisitor fully-scanned files as inputs for the 8.3.1 HSISIQIM Inquisitor Import job.
  2. For each repository, run the HSISIQIM job for every LPAR with setting of FULLREMATCH=Y. For performance reasons, exclude the Aggregator job step, except for the last HSISIQIM job. Please read the comments in the "Performance consideration" section of job HSISIQIM before you proceed.
  3. For the last HSISIQIM job, update the Aggregator jobstep with COUNTUSAGEFULL=Y. For example: 
    //AGGR EXEC HSIJSQLE,PROG=HSICTLAG,TPARAM=HSISAGP1
//USERPARM DD *
COUNTUSAGEFULL=Y
    Run the last HSISIQIM job with COUNTUSAGEFULL=Y for the Aggregator jobstep.
  4. After running the last HSISIQIM job, in the Aggregator jobstep, set COUNTUSAGEFULL=N (the default setting).
  5. Repeat steps 1 to 4 for the next repository.
  6. Before you run any Usage Import job, HSISUIMP, you must run the Inquisitor Import job, HSISIQIM, for all LPARS (as described in step 1). Failure to complete running the Inquisitor Import job (HSISIQIM) for all LPARs before you start running Usage Import (HSISUIMP) could result in errors during the Aggregator jobstep due to the product identifications not being up-to-date.
    1. For each repository, run the HSISUIMP job for every LPAR. For performance reasons, exclude the Aggregator jobstep, except for the last HSISUIMP job. Please read the comments in the "Performance consideration" section of job HSISUIMP before you proceed.
    2. For the last HSISUIMP job, update the Aggregator jobstep with COUNTUSAGEFULL=Y. For example: 
      //AGGR EXEC HSIJSQLE,PROG=HSICTLAG,TPARAM=HSISAGP1
//USERPARM DD *
COUNTUSAGEFULL=Y
      Run the last HSISUIMP job with COUNTUSAGEFULL=Y for the Aggregator jobstep.
    3. After running the last HSISUIMP job in the Aggregator jobstep, set COUNTUSAGEFULL=N (the default setting).
    4. Repeat steps 6a through 6c for the next repository.
  7. Configure APF authorization for the 8.3.1 hsi.SHSIMOD1 load library.
  8. You can run 8.3.1 operational jobs and discontinue 8.3 tasks once the 8.3.1 Inquisitor scans and Usage Monitors are ready for use.
    1. Review the settings in the Inquisitor scan jobs, before submissions: 
      HSISINQU – PACK=1 (default)
HSISINQZ – PACK=1 (default)
    2. Before starting HSISUMON, review parameters:
      PARMLIB member HSISMNPM – different parameters and default values.
    3. HSISZCAT – different parameters and default values: 
      Parameters 'JNM=Y,UID=Y,JAC=Y' are now the default.
    4. HSISIQIM – parameter COUNTUSAGE = N is now the default.