IBM Support

Central Site Distribution (DSLO) Media

Troubleshooting


Problem

Central Site Distribution (DSLO) is the process of creating install media from a currently installed system to install or upgrade another system.

Resolving The Problem

One of the methods to upgrade a system or partition is to use Central Site Distribution (DSLO) media. The biggest advantage in using this method is that the distribution media already contains the applied PTFs. This will eliminate the PTF installation step during the upgrade process.
  • - PTFs Needed on Source System Before Creating Media



    Note: Licensed Internal Code PTFs must be permanently applied on the source system before creating the distribution media:

     
    V5R3
    PTF=SI65184 APAR = SE60533

    V5R4
    PTF= MF44916 (8305) APAR= MA36754 PROD= 5722999 R540 SUPERSEDED BY: MF45579 (9321)
    PTF= MF44933 (9104) APAR= MA36754 PROD= 5722999 R545 SUPERSEDED BY: MF45585 (9321)
    PTF= SI31481 (8183) APAR= SE33093 PROD= 5722SS1 R540 SUPERSEDED BY: SI36434 (1000)
    PTF= SI31476 (8183) APAR= SE31738 PROD= 5722SS1 R540 SUPERSEDED BY: SI36434 (1000)
    PTF= SI31118 (8183) APAR= SE32731 PROD= 5722SS1 R540 SUPERSEDED BY: SI43589 (1000)
    PTF= SI27493 (7226) APAR= SE28702 PROD= 5722SS1 R540 SUPERSEDED BY: SI43272 (1000)
    PTF= SI31722 (8183) APAR= SE33442 PROD= 5722SS1 R540 SUPERSEDED BY: SI43272 (1000)
    PTF= SI27686 (8057) APAR= SE29045 PROD= 5722SS1 R540 SUPERSEDED BY: SI43589 (1000)
    PTF= SI27054 (7226) APAR= SE28330 PROD= 5722SS1 R540 SUPERSEDED BY: SI43589 (1000)
    PTF= SI31265 (0117) APAR= SE32902 PROD= 5722DG1 R540 SUPERSEDED BY: SI43312 (1000)
    PTF= SI31332 (8183) APAR= SE32979 PROD= 5722DG1 R540 SUPERSEDED BY: SI41519 (1000)
    PTF= SI22394 (7002) APAR= SE24115 PROD= 5722DG1 R540 SUPERSEDED BY: SI41519 (1000)
    PTF= SI22447 (7002) APAR= SE24177 PROD= 5722DG1 R540 SUPERSEDED BY: SI43312 (1000)
    PTF= SI22402 (7002) APAR= SE24127 PROD= 5722DG1 R540 SUPERSEDED BY: SI41519 (1000)
    PTF= SI27055 (7226) APAR= SE28331 PROD= 5722DG1 R540 SUPERSEDED BY: SI43312 (1000)

    V6R1
    PTF= SI31485 (8190) APAR= SE33155 PROD= 5761SS1 R610
    PTF= SI31486 (8190) APAR= SE33156 PROD= 5761SS1 R610 SUPERSEDED BY: SI41912 (1102)
    PTF= SI31234 (8288) APAR= SE32862 PROD= 5761SS1 R610 SUPERSEDED BY: SI41912 (1102)
    PTF= SI30159 (8127) APAR= SE31525 PROD= 5761SS1 R610 SUPERSEDED BY: SI32452 (8365)

    V7R1
    PTF = SI38823 (1000) APAR = SE42078 PROD= 5770999 R710
    V7R2
    PTF = SI65184 (1000) APAR  = SE67568 PROD = 5722IP1 R530
    PTF = SI80960 (1000) APAR = SE77059 PROD = 5770SS1 R720

    V7R3
    PTF = SI65184 (1000) APAR  = SE67568 PROD = 5722IP1 R530
    PTF = SI80961 (1000) APAR = SE77059 PROD = 5770SS1 R730
    V7R4
    PTF = SI65184 (1000) APAR  = SE67568 PROD = 5722IP1 R530
    PTF = SI80768 (1000) APAR = SE77059 PROD = 5770SS1 R740
    PTF = SI71876 (0121) APAR = SE72666 PROD = 5770BR1 R740 SUPERSEDED BY SI80272
    V7R5
    PTF = SI65184 (1000) APAR  = SE67568 PROD = 5722IP1 R530
    PTF = SI78522 (1000) APAR = SE77059 PROD = 5770SS1 R750
    For R730, R740 and R750, create the DSLO media without service program NEWNAV object in library QUSRSYS. On the system where the DSLO media is created, save the NEWNAV service program to a save file in library QUSRSYS. Then delete the service program before creating DSLO media. Fix to prevent issue is expected to be included in the latest HTTP group.
  • - Creating a Custom Installation Profile (Optional)



    A custom installation profile is only needed if you wish to deviate from the default installation profiles which are already provided by IBM.

    1. GO LICPGM, press Enter, select Option 41, and press Enter to start the process for creating an Installation Profile:

    GO LICPGM Option 41

    2. 1=Create and enter the Installation Profile name and the blank line:

    create installation profile

    3. Choose your type of install: 1=Upgrade or reinstall, 2=New install, 3=Change primary language:

    Create Profile Details
    4. Choose your restore options: 1=Restore from this creation media, 2=Keep values that are on the target system, 3=Keep values from target system unless they do not exist, then restore from this creation media:

    Change Restore Options
    5. Set Major System Options. Setting Enable automatic configuration to Y will automatically create device descriptions for the resources. This is usually set to Y for a new system and N for an existing system. The other two parameters are rarely changed from their defaults.

    Create Major System Options
    6. Select your licensed program installation options:

    Installation options:
    1=Reinstall or upgrade only the currently installed products on the target system.
    2=Reinstall or upgrade all of the products on the target system.
    3=Only install the products that do not already exist on the target system.
    4=If the product option exists on the target system, you should reinstall or upgrade the product option (same as option 1). If the product option does not exist on the target system, that option will be restored from media (same as Option 2).

    Notes:
    1. Dependent on Replace if current value. If Replace if current is set to Y=Yes, that licensed program option can be reinstalled regardless if it is already at the current release. If the Replace if current is set to N=No, that licensed program option will not be reinstalled.
    2. Option 4 does not apply to QGPL, QUSRSYS, Option 1, Option 2, or Option 3 of the base operating system.
    3. If the licensed programs do not appear in the GO LICPGM Option 11 list, they may need to be independently installed on the target system using the RSTLICPGM command.

    Create Licensed Program Options
    7. Your newly created profile should now show in the Installation profile list:

    Created Install Profile shows in list

  • - Creating Central Site Distribution (DSLO) Media



    The steps are shown below for creating distribution media. The screenshots included are an example of creating media to upgrade a target system.

    1. GO LICPGM, press Enter, select Option 40, and press Enter to start the creation process:

    GO LICPGM option 40
    2. A screen will show you what this option will do. Press Enter to confirm:

    Create a Distribution Media
    3. Enter your device and command defaults:

    Specify Command Defaults
    4. Press Enter to end all Subsystems:

    ENDSBS
    5a. Enter an installation profile which will determine what licensed programs are saved and how the target system should be installed. A Custom Installation profile can be created using GO LICPGM Option 41. This example uses the QIBMRPLRLS installation profile which is generally used for upgrading a target system:

    Specify Installation Profile
    5b. Pressing F4 on the Installation profile will show the pre-created profiles which you can select by typing 1 next to the desired profile and pressing Enter:

    Select an Installation Profile
    6. The SAVSYS will save your Licensed Internal Code, Base Operating System, User profiles, and Configuration objects. If you are using a tape or optical library, enter the volume ID of the media. If you are using a tape drive or optical drive, ensure that the volume is mounted in the drive:

    SAVSYS
    7. Because QGPL licensed program is really just a library, the SAVLIB command is used to save QGPL:

    SAVLIB LIB(QGPL)
    8. QUSRSYS licensed program is also just a library, so SAVLIB is performed to save QUSRSYS:

    SAVLIB LIB(QUSRSYS)
    9. Select the licensed programs you wish to upgrade on the target system. If you want to upgrade all of the licensed programs on your target system and you use and installation profile that is set up to upgrade the Installed Products, such as QIBMRPLRLS installation profile, you can select all of the licensed programs to be saved:

    Select Licensed Programs to save
    10a. Choose the device where you want to save your licensed programs and if the software agreements should already be accepted:

    Save Licensed Program Options
    10b. The next screen is just an example after you press enter on the Save Options screen. There will be a message at the bottom for which licensed program is being saved at that time:

    Licensed Programs saving
    11. After all of the licensed programs are installed, you can start your subsystems back up by pressing Enter on the STRSBS command:

    STRSBS
    12. You will then be taken back to the Work with Licensed Programs screen, and a message at the bottom will indicate if the process was successful or if it failed:

    Save completed successfully

 
  • - Secondary Language Installation (Optional)



    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. Because there is no automatic installation of secondary languages, they need to be saved later on the media as documented in the redistribution 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).





This is a high-level overview of the steps that need to be followed to create the media. Please see the information contained in the Information Center for complete instructions. Do the following to create the media:
1. Make sure the appropriate PTFs listed above are currently applied to the central system.
2. Verify the system objects using the menu option under the GO LICPGM option 5 menu.
3. When adding an image catalog entry to an image catalog, specify the size of the first image as *DVD4700. This image has to be large enough to hold all of the Licensed Internal Code with it's PTFs.
4. Ensure that QUSRSYS licensed program does not span to a separate volume.
5. Be sure to add enough catalog entries to hold all of the LPPs and their PTFs.
6. When using Option 40 of the GO LICPGM menu, it is suggested that you use either the QRPLRELLVL or QIBMRPLRS user profile or a profile that was created by using a copy of one of these two profiles.
7. Be aware that the installation of the LPPs will take longer than a standard installation, as the PTFs are part of the code that is being restored.
8. When option 40 completes, move the images or physical media to the target system or partition. If using physical media, ensure that the tape or optical device is the alternate restart device and perform a D Normal IPL from a PWRDWNSYS command. If using an image catalog for the upgrade, on the PWRDWNSYS command specify *IMGCLG for the IPL source and specify the image catalog to upgrade from. Also ensure that you have completed the pre-upgrade steps on the system that will be upgraded prior to starting the upgrade from DSLO media.
Additional Documentation

[{"Type":"MASTER","Line of Business":{"code":"LOB57","label":"Power"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SWG60","label":"IBM i"},"ARM Category":[{"code":"a8m0z0000000C4BAAU","label":"IBM i"}],"ARM Case Number":"TS010635765","Platform":[{"code":"PF012","label":"IBM i"}],"Version":"All Versions"}]

Historical Number

559882536

Document Information

Modified date:
16 September 2022

UID

nas8N1012298