Required: Allocating additional space for Licensed Internal Code

The V5R4 Licensed Internal Code requires more storage space than in previous releases.

Note: If your system has V5R3M5 Licensed Internal Code currently installed, you have enough storage space and can skip this topic.

The exact amount of this additional storage depends on which release is currently installed and which release is to be installed. If your server or logical partition does not have the additional space, the upgrade will stop during the installation of the Licensed Internal Code.

Use the Allocate Licensed Internal Code Space API (QLPALCSP) to find out if enough reserved storage is available, to allocate the additional space when necessary, and to correct any other possible errors. Enter the following text (where VxRxMx refers to the version, release, and modification of the Licensed Internal Code to which you are planning to upgrade).

CALL PGM(QLPALCSP) PARM('VxRxMx' 's')

The valid values for s are 0 or 1:

For the value 0, an indicator is set for the Licensed Internal Code to allocate all of the additional space required for the specified release during the next IPL. This value also causes the Licensed Internal Code to stop any space allocation requests due to a previous call to QLPALCSP with the Start space allocation parameter set to 1. You do not need to perform the IPL at this time, but you must do this before you begin to upgrade.
For the value 1, preparation for the allocation is done immediately by moving data off the load-source disk unit to ensure that the space can be allocated more quickly during the next IPL. This option is recommended to minimize the length of time that the next IPL will take to complete the operation.

If you do not use the IPL required parameter of this API, review the joblog after the API is called. If you see the following information message, you do not need to perform an IPL. You have the required space necessary.

CPI3DBF - Allocating additional space is not necessary

If you receive message CPF3DF7, you are directed to Checklist 11: Upgrade load-source disk unit with device parity protection . Otherwise contact your authorized service provider for assistance.

For more information on the QLPALCSP API, refer to the Allocate Licensed Internal Code space (QLPALCSP) API topic .