Using modules from the MVS link pack area

You must follow these steps to use the CICS® modules installed in the MVS link pack area from the hlq.SDFHLOAD library.

  • Copy the modules into a CICS LPA library. That is, you do not have to remove them from the hlq.SDFHLOAD library.
  • Specify the system initialization parameter LPA=YES. CICS then uses the following search order:
    1. MVS link pack area
    2. DFHRPL DD concatenation
  • For a non-nucleus CICS module or user application program, specify USELPACOPY(YES) on the associated PROGRAM resource definition. These modules are identified in the CICS-supplied USERMODs by this statement:
    /* Not loaded from LPA unless USELPACOPY is set to Y in the CSD  */
    For each CICS-supplied LPA-eligible module that requires USELPACOPY(YES) specified in its associated PROGRAM resource definition, you must create your own resource definition with USELPACOPY(YES) specified, and use it instead of the CICS-supplied resource definition, because you cannot modify the CICS-supplied resource definitions. For example, you can use the DFHCSDUP utility program for these purposes:
    1. Copy the CICS-supplied resource groups that contain the module definitions to new resource groups.
    2. For each module that requires USELPACOPY(YES), change the PROGRAM resource definition in the new resource groups to specify USELPACOPY(YES).
    3. Add your new resource groups to a new group list; that is, at the start of the list.
    4. Append the CICS-supplied group list DFHLIST, or your own equivalent of that group list, to your group list. Alternatively, include DFHLIST on the GRPLIST system initialization parameter as well as your group list.
    5. Remove the CICS-supplied groups that you have copied.
    When the program definitions have been changed on the CSD, perform the following steps:
    • Reinitialize the CICS catalogs if you have been using modules not in the MVS link pack area, and now want to use those modules from the MVS link pack area
    • Specify your new group list (and DFHLIST if your group list does not include the list of resource groups provided in DFHLIST) on the GRPLIST system initialization parameter.

    A sample DFHCSDUP job for all CICS LPA-eligible jobs is in Sample DFHCSDUP job to specify USELPACOPY(YES).

    In the above example, instead of steps 3 and 4, you can use the CEDA transaction for these tasks:
    • Copy your group list to create a new group list.
    • Add the new (USELPACOPY(YES)) groups to the new group list in the same place as the original, CICS-supplied, groups.
  • CICS uses eligible modules installed in the MVS link pack area, if the following criteria are met:
    • You have not specified the name of the module on the CICS system initialization parameter PRVMOD.
    • The module has not already been loaded from the DFHRPL concatenation.
  • If CICS cannot find an eligible module in the MVS link pack area, it loads the private (non-shared) version into the CICS address space from the DFHRPL concatenation, after issuing the message DFHLD0109I to warn you that the module is not in the MVS link pack area. See topic Handling the module-not-found warning message, DFHLD0109I for more information about this message.
  • CICS assumes that the PL/I modules, IBMBPSLA and IBMBPSMA, are installed in the MVS link pack area and issues message DFHLD0109I if it fails to find them there. If you want your PL/I application programs to run with the PL/I shared library, ensure that the modules IBMBPSLA and IBMBPSMA are installed in the MVS link pack area, in the hlq.SDFHLOAD library or in another library in the CICS DFHRPL library concatenation.
  • You must place program list tables (PLTs) must be placed in the DFHRPL concatenation. However, before PROGRAM resource definitions for phase one PLTPI programs and PLTSD programs are installed (for example, early in CICS initialization) CICS scans the MVS link pack area for those programs and issues message DFHLD0109I if it cannot find such a program there.
  • Similarly, before PROGRAM resource definitions for global and task-related user exit programs are installed (for example, early in CICS initialization) CICS scans the MVS link pack area for those programs, and issues message DFHLD0109I if it cannot find such a program there.

Specifying USELPACOPY(YES)

For every non-nucleus CICS module or user application program that you have moved to the MVS link pack area, that is, have removed from the DFHRPL concatenation, ensure that you have specified USELPACOPY(YES) on the associated PROGRAM resource definition. Otherwise, CICS cannot find the module and might fail to start successfully. See Sample DFHCSDUP job to specify USELPACOPY(YES) for a sample job to specify USELPACOPY(YES).



dfha1c2.html | Timestamp icon Last updated: Sunday, 4 June 2017