LIU load module library customization

The IMS™ Library Integrity Utilities load module library (also referred to as LIU load module library) must be customized to use Integrity Checker.

The DMB verification function of Integrity Checker is triggered by IMS jobs (IMS online, application, IMS standard utility, and IMS Tools utility jobs) that access databases. Therefore, unlike other IMS Tools programs that run with JCL in which the EXEC PGM= parameter specifies the utility program name to execute, Integrity Checker must be customized to automatically start DMB verification when a database is accessed.

The DMB verification process runs as part of the DBRC authorization process. Therefore, instead of coding JCL statements, you must customize the LIU load module data set (SHPSLMD0 data set) to work with DBRC module DSPCRTR0.

Important: In IMS Library Integrity Utilities Version 2 Release 1 and earlier, alias name DSPCRTR0 was assigned for the FABLRTR0 module by default, but in IMS Library Integrity Utilities Version 2 Release 2 and later, the alias name is not assigned. You must customize the LIU load module library.

Methods for customizing the LIU load module library

Integrity Checker supports two methods for customizing the LIU load module data set. Compare the two methods and determine the best method for your environment.

Method 1: Defining alias name DSPCRTR0 for FABLRTR0 (recommended method)
Module FABLRTR0 is the program load module that is stored in the LIU load module library. Module DSPCRTR0 is the DBRC router module, which is one of the DBRC authorization modules.

If alias name DSPCRTR0 is defined for the FABLRTR0 module, and the LIU load module library precedes the IMS resident library (SDFSRESL data set) in the STEPLIB DD in JCL and procedures of IMS jobs, when a database is accessed by such jobs, instead of the DBRC module DSPCRTR0, the FABLRTR0 module starts and activates DMB verification. To apply this method, the LIU load module library must be APF-authorized.

  • Advantage: You can use the standard SMP/E methods to apply program temporary fixes (PTFs) for both IMS Library Integrity Utilities and IMS.
  • Disadvantage: You must modify the STEPLIB DD statement in JCL and procedures of all IMS jobs that access databases.
Method 2: Merging Integrity Checker load modules into the IMS resident library (SDFSRESL)
If all the Integrity Checker modules (FABL* members) in the LIU load module library are merged into the IMS SDFSRESL data set, when a database is accessed, the FABLRTR0 module, which is link-edited to the DBRC module DSPCRTR0 module, starts and activates DMB verification. Before the modules are merged, the FABLRTR0 module and DBRC module DSPCRTR0 must be link-edited to create one DSPCRTR0 module, and the module entry point must be set to FABLRTR0. Before the modules are merged, a backup of the IMS SDFSRESL data set must be created.
  • Advantage: You do not need to modify the STEPLIB DD statement in each JCL and procedure of IMS jobs that access databases.
  • Disadvantage: When you apply PTFs for IMS Library Integrity Utilities and IMS, the following additional steps are required:
    • For IMS Library Integrity Utilities, after you apply a PTF, you must merge the members again.
    • For IMS, if the PTF updates the DSPCRTR0 module, you must restore the DSPCRTR0 module before you apply the PTF. After you apply the PTF, create a backup of the SDFSRESL data set, and then link-edit FABLRTR0 and DSPCRTR0 again.

Integrity Checker supports multiple versions of IMS with one module. Therefore, with either method, if the version of IMS is supported by IMS Library Integrity Utilities, the same LIU load module data set can be used.