Configuring HD Pointer Checker to use with IMS Database Recovery Facility

You can run the HD Pointer Checker HASH Check function in IMS Database Recovery Facility jobs.

About this task

IMS Database Recovery Facility can call the HD Pointer Checker HASH Check function. To run HD Pointer Checker in IMS Database Recovery Facility jobs, you must tailor HD Pointer Checker for IMS Database Recovery Facility.

Related reading: For additional information to run the HASH Check function in IMS Database Recovery Facility, see the IMS Recovery Solution Pack IMS Database Recovery Facility User's Guide and Reference.

Procedure

Complete the following steps to tailor HD Pointer Checker for IMS Database Recovery Facility:

  1. APF-authorize the IMS HP Pointer Checker load module library (SHPSLMD0).

    In the IMS Database Recovery Facility environment, the HD Pointer Checker program runs as an authorized program facility (APF) program.

  2. Modify the FABPATH0 procedure, the FABPATHZ procedure, or both procedures.

    IMS HP Pointer Checker provides two procedures; FABPATH0 and FABPATHZ. These procedures build environmental setting for the HASH pointer checking. See FABPATH0 and FABPATHZ procedures for more information about the procedures and the JCL requirements for modifying the procedures.

  3. Add the procedure to one of the libraries in the SYS1.PROCLIB concatenation.
  4. Set up security for the HD Pointer Checker subordinate address space.
    When IMS Database Recovery Facility calls the HD Pointer Checker HASH Check function, IMS HP Pointer Checker starts the procedure, which initiates HD Pointer Checker subordinate address space. To initiate the subordinate address space under a security system, you must authorize the subordinate address space. To do so, define the STARTED class profiles that correspond to the procedure names and refresh the STARTED class. You can use the following commands. If a different procedure name is used to start the HD Pointer Checker subordinate address space, replace the procedure name in the RDEFINE command.
    RDEFINE STARTED FABPATH0.* STDATA(USER(userid))
    RDEFINE STARTED FABPATHZ.* STDATA(USER(userid))
    SETROPTS RACLIST(STARTED) REFRESH
    You can also use the started procedures table ICHRIN03 to associate started procedures with user IDs instead of using the RDEFINE STARTED command.
    The user ID (userid) that is associated with the started task job requires the READ access authority to the following data sets:
    • The library that contains the IMS HP Pointer Checker load modules
    • The IMS RESLIB
    • The library that contains the HALDB partition selection exit routine if you process a HALDB and the HALDB uses a HALDB partition selection exit routine
    • The library that contains the DBD load modules
    • The RECON data sets