The libraries that contain APF-authorized programs must be defined
in an APF list. The APF list contains the following information for
each library:
- The library name
- An identifier for the volume that contains the library (or "SMS",
if the library is SMS-managed).
Note: The system considers all modules in the link
pack area (pageable LPA, modified LPA, fixed LPA, dynamic LPA) as
having come from an authorized library whether or not the library
is defined in the APF list).
The system automatically places SYS1.LINKLIB and SYS1.SVCLIB in
the first two APF list entries. Your installation can create the remaining
entries in the APF list.
Note: When LNKAUTH=APFTAB is specified, the
system considers SYS1.MIGLIB, SYS1.CSSLIB,SYS1.SIEALNKE and SYS1.SIEAMIGE to
be APF-authorized when they are accessed as part of the concatenation
(even when they are not included in the APF list).
Defining Aliases in the APF List: Do not
define aliases in the APF list because data management services of IBM® (for example, OPEN processing)
map an alias to its actual library name and query the APF list by
the actual library name. An alias in the APF list thus does not actually
authorize anything.
You can specify a dynamic format for the APF list, which allows
you to:
- Update the APF list without having to reIPL the system, and
- Specify as many APF-authorized libraries as you need; there is
no system-imposed maximum number.
You can also specify a static format for the APF list, which has
the following limitations:
- You can define the static APF list only at IPL, using the IEAAPFxx
or PROGxx parmlib member
- You can only specify a maximum of only 253 libraries in the static
APF list (255 entries are allowed, but SYS1.LINKLIB and SYS1.SVCLIB
occupy two entries in the list).
Because of the limitations associated with a static APF list, IBM recommends that you maintain
a dynamic APF list.
Requesting APF list services (CSVAPF macro)explains how to create, update, and change
the format and contents of the APF list.