Central Site Distribution (DSLO) - Secondary Language Installation/Upgrade

Resolving The Problem

Central Site Distribution (commonly known as DSLO or re-distribution) does not install secondary languages. The default on the SAVLICPGM is set for *PRIMARY instead of *ALL, which means that it also will not save the secondary languages. Any of the LPPs saved using GO LICPGM option 40 (Create distribution media) will only save their primary languages. Since there is no automatic installation of secondary languages, they need to be saved later on the media as documented in the re-distribution guide (SC41-5308). If all languages were saved at the same time with the licensed program products, it would interrupt the installation process of the objects. In addition, SAVLICPGM does not support 57xxSS1 *BASE secondary language. This means it can only be transferred to the target system using SAVLIB/RSTLIB of the QSYS29xx libraries. When a true installation of a secondary language 57xxSS1 *BASE is performed, the exit programs get called and they would delete the DB files, so that the new ones restore properly. RSTLIB does not have this same concept, so the DLTLICPGM of 57xxSS1 *BASE and all of its options for that secondary language are needed to ensure those DB files get removed.

Here are the proper steps for saving/restoring secondary languages using redistribution media:

Source system:
1. After using GO LICPGM option 40 to create the distribution media.
2. SAVLIB of QSYS29xx
3. SAVLICPGM LICPGM(xxxxxx) OPTION(xx) LNG(*ALL) – Perform for each licensed program.

Target system:
1. GO LICPGM option 22 to delete any existing secondary languages.
2. RSTLIB QSYS29xx as documented in the Redistribution manual (using four values instead of *ALL for ALWOBJDIF) (There may be some files that will not restore; however, that is fine because those files will be properly handled during the upcoming RSTLICPGM of the individual products).
3. RSTLICPGM of each Licensed Program Product secondary language as documented in the redistribution manual.

Note: A CL program can be written to perform the above steps automatically. The user could make use of the QLPUSER CL program (Licensed Program calls this after a successful upgrade). There is no command or API interface for GO LICPGM option 22, so the CL would need to replace that step with DLTLICPGM LICPGM(xxxxxxxx) LNG(29xx) for each secondary language. (When the LNG parameter is specified, it will delete the secondary language for the product and its options; however, it will not delete the program objects. There is no way to just delete 57xxSS1 *BASE secondary language).