QALZAL0001 in library QUSRSYS is a duplicate

This document describes what can be done when the pre-upgrade verification tool (PRUV tool) finds QALZAL0001 in library QUSRSYS to be a duplicate.

1. Get all of the keys currently residing in QUSRSYS/QALZALIC into a separate file:
DSPLICKEY SERIAL(*ALL) OUTPUT(*LICKEYFILE) LICKEYFILE(MYLIB/TEMPLICKEY)

2. Delete QUSRSYS/QALZALIC

3. Rename QUSRSYS/QALZAL0001 to QUSRSYS/QALZALIC

4. Add the license keys from the key file created in Step 1:
ADDLICKEY LICKEYINP(*LICKEYFILE) SERIAL(*ALL) LICKEYFILE(MYLIB/TEMPLICKEY)
Any keys that were not in both files before will be after this ADDLICKEY.

5. Verify that all the keys are correct:
DSPLICKEY SERIAL(*ALL)

Download any new keys from the ESS site: https://www-05.ibm.com/servers/eserver/ess/OpenServlet.wss

Backing up the original files (QUSRSYS/QALZALIC and QUSRSYS/QALZAL0001) is fine just to be safe; however, it is most likely not necessary.

Note: It is normal for old keys to reside in the license key repository. License keys which are added to the repository are not removed automatically. If the repository is saved off of one system and restored on another system (as the system is migrated/upgraded, and so on), all the keys which were in the file when it was saved are in the file when it is restored. If you want to get rid of the keys for the old system, you can issue the RMVLICKEY command as follows:
RMVLICKEY LICKEYINP(*PROMPT) PRDID(*ALL) LICTRM(*ALL) FEATURE(*ALL) SERIAL(xxxxxxx)

where xxxxxxx equals the Type and SN of the old system

Having all those old keys in the repository is not a problem, nor is it indicative of a problem.