Home
Migrating to HCL Z Asset Optimizer Version 2.2
When you migrate to the latest version of HCL Z Asset Optimizer from an earlier version, you must convert existing data to be compatible with your new environment.
Migrating from IBM Z Software Asset Management version 8.2 to HCL Z Asset Optimizer version 2.2
If you wish to port data from IBM Z Software Asset Management version 8.2 to HCL Z Asset Optimizer version 2.2, you need to unload data from the version 8.2 repository and reload the unloaded data into a new version 2.2 repository.

Migrating to HCL Z Asset Optimizer Version 2.2
When you migrate to the latest version of HCL Z Asset Optimizer from an earlier version, you must convert existing data to be compatible with your new environment.
- Migrating from version 1.1 to HCL Z Asset Optimizer version 2.2 (Db2® database)
  When you upgrade to HCL Z Asset Optimizer version 2.2 for Db2 database, there is no porting of data within the Repository database. New Db2 objects are defined to the Repository. The existing version 1.1 GKB database is dropped and re-created with the same database name for version 2.2.
- Migrating from version 1.1 to HCL Z Asset Optimizer version 2.2 (SQLite database)
  When you upgrade to HCL Z Asset Optimizer version 2.2 for SQLite database, there is some porting of data within the Repository database. New SQLite objects are defined and obsolete objects dropped from the Repository. The existing version 1.1 GKB database is dropped and re-created with the same database name for version 2.2.
- Migrating from IBM Tivoli Asset Discovery for z/OS version 8.1 to HCL Z Asset Optimizer version 2.2
  If you wish to port data from IBM Tivoli Asset Discovery for z/OS version 8.1 to HCL Z Asset Optimizer version 2.2, you need to unload data from the version 8.1 repository and reload the unloaded data into a new version 2.2 repository.
- Migrating from IBM Z Software Asset Management version 8.2 to HCL Z Asset Optimizer version 2.2
  If you wish to port data from IBM Z Software Asset Management version 8.2 to HCL Z Asset Optimizer version 2.2, you need to unload data from the version 8.2 repository and reload the unloaded data into a new version 2.2 repository.
- Post migration errors
  If migration from version 1.1 to version 2.2 is incomplete, or if a wrong combination of files, jobs, or PARMLIB members are used between the two versions, then you might get the following errors.

Migrating from IBM Z Software Asset Management version 8.2 to HCL Z Asset Optimizer version 2.2

If you wish to port data from IBM Z Software Asset Management version 8.2 to HCL Z Asset Optimizer version 2.2, you need to unload data from the version 8.2 repository and reload the unloaded data into a new version 2.2 repository.

About this task

The HCL Z Asset Optimizer version 2.2 repository can be either a Db2® database or a SQLite database.

To perform the migration, run the following migration jobs:

Procedure

HSISUN82 – Run this job to unload the IBM Z Software Asset Management version 8.2 repository. Ensure that all groups are unloaded, including group 3.
HZASCUST – Run this customization job to create a new set of JCLLIB/PARMLIB members for HCL Z Asset Optimizer version 2.2.
HZASDB01:
Db2 - Run this job to create new storage groups.

SQLite – Run this job to create a new zFS file.
HZASDB03 – Run this job to create a new version 2.2 repository
HZASMI87 – Run this job to load data into the newly created version 2.2 repository, using the input file generated from step (a).
Note: LKB/LKU data are not ported in this migration. LKB/LKU must be re-created in version 2.2.

What to do next

See Chapter 3 for information about running jobs in a newly created repository.