LOADLPA
The LOADLPA (LOA) service lets you add modules or SVCs in LPA without needing to re-IPL.
This service also lets you delete modules that are added by this service.
Syntax
The parameters are defined as follows:
Parameter | Description |
|---|---|
LIST | lists information for all active modules A module is considered active if it was loaded by the ADD function and has not been deleted. The LIST function is the default. |
ADD | loads a module and all of its aliases; it also places the module on the active LPA queue Modules are loaded from the load library with a DD name of USERLIB, unless a data set name is specified as the third parameter. If you specify a module that was previously loaded by the ADD function, the module is loaded at a new location because the entry point changes. The previously loaded copy is deleted (see the description of the DEL function). |
modname | name of the module that is to be added, deleted, or freed |
dsname | name of the data set where modname resides LOADLPA dynamically allocates the data set specified before loading modname into LPA. If no data set name is specified, LOADLPA tries to find modname in the DD concatenation USERLIB. Note that USERLIB must have been previously allocated to the same address space where SYSPROG Services is currently executing. (When SYSPROG Services is running under MainView for z/OS from the SYSPROG Services menu, this address space is PAS.) |
DEL | deletes a module and its aliases loaded by the ADD function All saved entry-point addresses are restored, and the module is removed from the active LPA queue. The module’s storage is freed if the module’s use count is zero and if the module does not contain an SVC entry point. If you specify ALL, LOADLPA deletes all modules and aliases previously loaded by the ADD function. |
Example 1
To add the USERMOD module, which is found in LGS1.LOADLIB, type
LOADLPA ADD USERMOD LGS1.LOADLIB
AMTL5HI NAME=USERMOD, EP=00B41000, CDE=F47AD0, TIME=17:13
[5] [6]
AMTL5JI LA=00BA4100, LEN=0022CE
AMTL5KI ALIAS=USEREP1, EP=00BA4140, CDE=F47B00 [7]
AMTL5KI ALIAS=USEREP2, EP=00BA4440, CDE=F47B30 [7]
AMTL5LI LOADLPA ADD FUNCTION COMPLETED
Legend:
- name of module loaded
- address of module entry point
- address of the contents directory entry (CDE) created for this module
- time module was loaded
- address of module
- length of module
name, entry point address, and CDE address for all aliases found in the specified module for this module
Example 2
To delete the USERMOD module from LPA, type
LOADLPA DEL USERMOD
AMTL5PI LOADLPA DELETE FUNCTION COMPLETED
Usage notes
- Entry points of some operating system routines are maintained in system control blocks. The entry points that are used for specific modules and control blocks depend on the operating system, release level, and maintenance level. The LPA active queue is the only control block that LOADLPA updates. Therefore, programs that do not use LINK, LOAD, ATTACH, or XCTL to access the module are unaffected by LOADLPA.
- LOADLPA can delete only the module and aliases that LOADLPA has loaded.
- The SVC table is updated with an entry point address for any module name (true name or alias) that conforms to SVC naming conventions. If necessary, you can use the ZAP service to update the SVC table to change the locks. All types of extended SVCs are supported. In all cases, the old entry point address is saved and then restored when the module is deleted by the LOADLPA delete function. Use the ZAP service to reset the locks. See SVCFIND and ZAP for more information.
Using LOADLPA, you can either add to or delete from LPA the SVC names that end with X'C0' (such as type 4 SVC 250) by substituting a left brace ({) for the last characters of the module name; for example:
LOADLPA ADD IGC0025{
- When you add an extended SVC with the LOADLPA service, the entry point address in the Extended SVC Router (ESR) table is updated. However, the flags in the second word of the ESR table entry are not changed. Use the ZAP service to reset flags, if required.
- Modules loaded by the LOADLPA service are logically added to the LPA but physically reside in CSA storage.
Related topic