KEMBAR78
zOS 5 | PDF | Software Development | System Software
0% found this document useful (0 votes)
52 views23 pages

zOS 5

The document provides an overview of Link Pack Area (LPA), Linked List (LNKLST), and Authorized Program Facility (APF) libraries, detailing their functionalities, structures, and management processes. It explains how modules are loaded, the significance of various LPA sub-areas, and the procedures for dynamic updates to LPA and LNKLST. Additionally, it covers the importance of APF in securing access to sensitive system functions and the management of authorized libraries.

Uploaded by

Sagar Salake
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
52 views23 pages

zOS 5

The document provides an overview of Link Pack Area (LPA), Linked List (LNKLST), and Authorized Program Facility (APF) libraries, detailing their functionalities, structures, and management processes. It explains how modules are loaded, the significance of various LPA sub-areas, and the procedures for dynamic updates to LPA and LNKLST. Additionally, it covers the importance of APF in securing access to sensitive system functions and the management of authorized libraries.

Uploaded by

Sagar Salake
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 23

LPA, LNKLST & APF Libraries

Link Pack Area (LPA)


Link Pack Area (LPA) – (Cont.)
• Link pack area (LPA) modules are loaded in common storage,
shared by all address spaces in the system. Modules found in
LPA do not need to be brought into virtual storage because
they are already in virtual storage.

• Modules placed anywhere in LPA are always in virtual


storage, and modules placed in FLPA are also always in
central storage.

• LPA pages are only stolen, and never paged out, because
there are copies of all LPA pages in the LPA page data set.

• Modules can also be loaded into CSA by authorized


programs. When modules are loaded into CSA and shared by
multiple address spaces, the performance considerations are
similar to those for modules placed in LPA.
LPA Sub Areas
• Each component of the LPA has a counterpart in the extended
common area (that is above the 16 megabyte line) as follows:
– FLPA The FLPA exists only for the duration of an IPL. Therefore, if an
FLPA is desired, the modules in the FLPA must be specified for each IPL
(including quick-start and warm-start IPLs).
– PLPA During initialization, both primary and secondary (or duplexed)
PLPAs are established. The PLPA is established initially from the LPALST
concatenation. On the PLPA page data set, ASM maintains records that
have pointers to the PLPA and extended PLPA pages. During quick start
and warm start IPLs, the system uses the pointers to locate the PLPA
and extended PLPA pages. The system then rebuilds the PLPA.
– MLPA This area may be used to contain reenterable routines from APF-
authorized libraries that are to be part of the pageable extension to
the link pack area during the current IPL. 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 can be used at IPL time to temporarily modify or
update the PLPA with new or replacement modules.
LPA Parmlib Definition
LPA Parmlib Definition (Cont.)
Specifying LPA parameters in Parmlib
• The two characters (A through Z, 0 through 9, @, #, or $)
represented by aa (or bb and so forth) in Figure, are
appended to LPALST to form the name of the LPALSTxx
parmlib members.

• If the L option is specified, the system displays the contents


of the LPALSTxx parmlib members at the operator's console
as the system processes the members.

• The LPA parameter is only effective during cold starts. The


LPA parameter does not apply to modules requested
through the MLPA option.
Coding a LPALSTxx Member
Coding a LPALSTxx Member (Cont.)
Some important syntax rules for the creation of
LPALSTxx are:
• On each record, place a string of data set names
separated by commas.
• If a data set is not cataloged in the system master
catalog, but is cataloged in a user catalog, specify in
parentheses immediately following the data set name
the one to six character VOLSER of the pack on which
the data set resides.
• Indicate continuation by placing a comma followed by
at least one blank after the last data set name on a
record.
Dynamic LPA Functions
Dynamic LPA Functions (Cont.)
How to perform dynamic LPA functions
• The PROGxx parmlib member includes the LPA
statements, which are used to define what modules
can be added to or deleted from LPA after the IPL.
You use the SET command to validate the PROGxx
parmlib member; for example, SET PROG=xx.
• The SETPROG LPA command may be used to initiate a
change (add or delete) to the LPA.
• The DISPLAY PROG,LPA command may be used to
display information about modules that have been
added to LPA.
• The CSVDYLPA macro allows an authorized program
to initiate dynamic LPA services.
Linked List (LNKLST)
Linked List (LNKLST) – (Cont.)
The LNKLST begins with these system data sets:
• SYS1.LINKLIB
• SYS1.MIGLIB
• SYS1.CSSLIB
• All LNKLST-managed libraries must be cataloged.
The benefits of LNKLST apply only to modules that
are retrieved through the following macros: LINK,
LINKX, LOAD, ATTACH, ATTACHX, XCTL, and XCTLX.
Dynamic LNKLST Functions
Dynamic LNKLST Functions (Cont.)
How to perform dynamic LPA functions
• You can create a PROGxx parmlib member with the
new changes to the LNKLST set, then issue the SET
PROG=xx operator command to activate the changes.
• You can simply use the SETPROG LNKLST operator
command to update the LNKLST directly.
• You can also use the D PROG,LNKLST command to
display information about the LNKLST set.
• Finally, you can use CSVDYNL macro programming
service in an authorized program to change the
LNKLST concatenation for associated jobs and
address spaces.
Compressing LLA libraries
Compressing LLA libraries (Cont.)
How to compress LLA-managed libraries
1. Compress the library.
There are two ways of compressing a data set:
– You can issue the line command Z against the data set
you want to compress from the ISPF panel.
– You can submit a job to compress the data set using
the utility IEBCOPY as shown in the following sample
JCL.
Authorized Libraries
Authorized Libraries (Cont.)
• z/OS offers a mechanism called the authorized program
facility (APF) to restrict the access to sensitive system
functions or user programs. APF was designed to avoid
integrity exposures. The installation identifies what libraries
contain those special functions or programs. Those libraries
are then called APF (authorized program facility) libraries.
• The modified link pack area (MLPA) may be used to contain
reenterable routines from APF-authorized libraries that are
to be part of the pageable extension to the link pack area
during the current IPL.
• 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).
Authorized Libraries (Cont.)
• APF-authorized programs must reside in one of
the following authorized libraries:
• SYS1.LINKLIB
• SYS1.SVCLIB
• SYS1.LPALIB
• An authorized library specified by your installation
Dynamic APF Functions
Dynamic APF Functions (Cont.)
Managing dynamic APF
• Use PROGxx Parmlib member which includes the
appropriate APF statement to define the change.
• The SETPROG AFP™ operator can also initiate a
change to the APF table.
• The DISPLAY AFP command can be used to display
the list of libraries authorized by APF.
Questions Please!!!
THANK YOU!!!

You might also like