z/OS MVS Initialization and Tuning Guide
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


Modified link pack area (MLPA/Extended MLPA)

z/OS MVS Initialization and Tuning Guide
SA23-1379-02

This area may be used to contain reenterable routines from either APF-authorized or non-APF-authorized libraries that are to be part of the pageable extension to the link pack area during the current IPL. Any module in the modified link pack area will be treated by the system as though it came from an APF-authorized library. Ensure that you have properly protected any library named in IEALPAxx to avoid system security and integrity exposures, just as you would protect any APF-authorized library.

The MLPA exists only for the duration of an IPL. Therefore, if an MLPA is desired, the modules in the MLPA must be specified for each IPL (including quick start and warm start IPLs).

The MLPA is allocated just below the FLPA (or the PLPA, if there is no FLPA); the extended MLPA is allocated above the extended FLPA (or the extended PLPA if there is no extended FLPA). When the system searches for a routine, the MLPA is searched before the PLPA.

Note: Loading a large number of modules in the MLPA can increase fetch time for modules that are not loaded in the LPA. This could affect system performance.

The MLPA can be used at IPL time to temporarily modify or update the PLPA with new or replacement modules. No actual modification is made to the quick start PLPA stored in the system's paging data sets. The MLPA is read-only, unless NOPROT is specified on the MLPA system parameter.

Specified by:
  • Including a module list as an IEALPAxx member of SYS1.PARMLIB; where xx is the specific list.
  • Including the MLPA system parameter in IEASYSxx or specifying MLPA from the operator's console during system initialization.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014