Running License Verification Import

To run the License Verification Import, follow the steps outlined in this section.

About this task

ZLVLICI is a batch job that imports your license data into the TLICENSE table. The file to be imported is the uploaded CSV file on the host. The CSV file is created using the Extract Product Information report. See Creating the CSV file and Uploading the CSV file to the host.

Each CSV file contains license data from only a single repository. You can import only a single CSV file at a time.

Following is a scenario where CSV files from multiple repositories are to be imported.

Consider there are four repositories – REP1, REP2, REP3, REP4, that are defined in the same Db2® subsystem (DB2A) and ZLV is implemented in REP1. CSV files created from REP1 to REP4 are separately collected. Job ZLVLICI needs to be run four times to import these CSV files separately.

Note: If in another Db2® subsystem (DB2B), a repository with an identical name (REP3) is used, then a different ZLV must be implemented in a repository defined to DB2B. The CSV file collected from REP3 can then be imported into a repository belonging to DB2B.

Procedure

  1. To run the License Verification Import, use job ZLVLICI. You need to customize this job before submission.
  2. When the batch job is submitted the //SYSPRINT displays any problems with the importing of the data.
  3. Correct any errors and then re-import them until you are satisfied.
  4. Both ZLVLICI and ZLVLICV jobs can be run only after you have loaded the Inquisitor data into the Repository.