Considerations for activating Integrity Checker

Before you activate Integrity Checker, review these considerations.

Cases where DMB verification is not done

DMB verification is not done in certain environments or for certain application jobs.

For more information, see Restrictions: Cases where DMB verification is not done.

Size of the LICON data sets

Before creating LICON data sets, you can estimate the required storage for the LICON data sets.

For more information, see Estimating the size of the LICON data set.

LICON data set serialization consideration

If you want more than one MVS™ system to access the LICON data set, you must serialize the LICON data set. To access the LICON data set from more than one MVS system, Global Resource Serialization (GRS) or a similar global enqueue product must be installed.

For more information, see Serializing the LICON data set.

RACF® security considerations

If you want to protect the LICON data sets with RACF or if you plan to use Integrity Checker in IMS Database Recovery Facility jobs, you must modify RACF security.

For more information, see Setting up RACF security.

Considerations when you alter the definition of an online HALDB or an online DEDB

When you alter the definition of an online HALDB database or an online DEDB database with the following IMS command or IMS utility, you must temporarily stop the DMB verification process.

Use the INITIATE OLREORG command (with the ALTER option) and the online change (OLC) function to alter the definition of an online HALDB database.
Use the DEDB Alter utility (DBFUDA00) to alter the definition of an online DEDB database.

After you alter the definition, restart the DMB verification process with new RDEs. Without these steps, the DMB verification process uses the old definitions to verify the DMBs. Therefore, the DMB verification process might deny database authorization requests that use correct IMS control blocks.

For detailed instructions, see the following topics:

Consideration when you change the maximum size of OSAM data sets for a HALDB

When you change the maximum size of OSAM data sets for a HALDB from 4 GB to 8 GB or 8 GB to 4 GB, you must use the LICON utility and manually create RDEs to reflect the change for the DMB verification process.

For more information, see Changing the maximum OSAM data set size for a DMB verification-enabled HALDB.