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

When you upgrade to IBM Z Software Asset Management 8.3.1 for SQLite 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.

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. 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 SQLite 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 SQLITE.
    2. Set HSIINST to the same value as the one defined for the existing 8.3 system. As stated in the section, “Before you begin”, it is imperative that you either 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 REPZSCHM parameter to the same value that is defined for your 8.3 Repository database.
    5. Set the value of the GKBZSCHM parameter to the same value that is defined for your 8.3 GKB database.
    6. Set the value of the SQLTZFS parameter to the same value that is defined for your 8.3 zFS linear VSAM data set.
    7. Set the value of the SQLTPATH parameter to same value that is defined for your 8.3 path of the z/OS UNIX for Systems Services directory.
  2. Submit the HSISCUST job. The JCLLIB/PARMLIB datasets created use the same names as those created in 8.3. The same dataset names for JCLLIB/PARMLIB must be used in 8.3.1 because of the relationships between the high level qualifier HSIINST parameter and the SQLTZFS/SQLTPATH parameters.

    1. SQLTZFS = '&HSIINST..&SYS..ZFS'

    2. SQLTPATH = '/u/tadz/&SQLTZFS

  3. Edit and update jobs in the JCLLIB library and parameters in the PARMLIB library if there are special site requirements.
  4. HSISGKBL– Submit this job 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.
  5. Backup 8.3.1
    1. HSISUT01– run the 8.3.1 job to backup the SQLite database.
  6. Recovery
    1. If failures occur during the migration, and a recovery is required, run the 8.3 job, HSISUT02 to recover using the backup copy created just before the start of migration.

What to do next

See section "What to do next", from topic "Migrating from IBM Z Software Asset Management 8.3 to IBM Z Software Asset Management 8.3.1 (DB2 database)".