On 2020-09-19 12:17 AM, Peter wrote:
if LPA and MLPA are same
LPA covers PLPA, MLPA, FLPA and DLPA.
PLPA is built when CLPA is specified at IPL time.
MLPA and FLPA are built every IPL time when required - they may have
zero size if no modules are loaded there - the modules to be load in
MLPA and FLPA are specified by locally customized system parameters.
DLPA is for LPA modules that are dynamically loaded by programs issuing
CSVDYLPA macros or by system SETPROG LPA commands, after IPL and after
the storage address ranges of the various address space parts have been
determined. In terms of these address space parts of virtual storage,
DLPA modules physically reside in CSA and not in PLPA, MLPA or FLPA, the
latter 3 being optimized to use the minimum storage to hold the required
modules and so have no "spare" space to add additional modules after IPL.
I believe DLPA is the way to go if you want a program object (as opposed
to a load module) made resident in LPA.
DLPA was introduced in OS/390 in the 1990s so it's older than this
century. Do some reading to find out all you need.
If you want to track program usage including the data set name of the
libraries from which they were originally fetched, the IBM product
called Tivoli Asset Discovery for z/OS (how many products still have
Tivoli in their name?) does a good job of tracking application program
use including application programs residing in any type of LPA.
Cheers,
Greg
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
