Controlling the use of modules from the LPA

You can control whether CICS® uses modules from the LPA, either by specifying the LPA and PRVMOD CICS system initialization parameters , or by including or excluding the SYS1.CICSTS53.CPSM.SEYULPA library (defined to MVS™ as an LPA library) in the STEPLIB or DFHRPL concatenations.

  1. A module that is link-edited with the RMODE(ANY) attribute is loaded into the ELPA.
  2. It is important to remember that the LPA-resident version of a module that is usually loaded from STEPLIB is not used from the LPA if it is left in the STEPLIB DD concatenation of libraries. If a module is found in the STEPLIB concatenation, it is loaded into the private area of the address space, and the LPA version ignored. You can avoid this situation by moving the LPA-eligible modules into an LPA library, as described in Installing CICSPlex SM modules into the LPA.
For further information about controlling the use of LPA-eligible modules, see Installing CICSPlex SM modules in the MVS link pack area, taking particular note of information concerning:
  • The module-not-found warning message DFHLD0109I
  • CICS system initialization parameters related to LPA modules