Creating global option modules

To activate Integrity Checker, create at least one global option module that contains the name of the LICON data set. If you want to change the default options of Integrity Checker globally, specify them when you create this module.

About this task

IBM® does not supply global option modules. You must create at least one global option module before invoking Integrity Checker.

Procedure

To create a global option module, determine the type of the global option module, then use the FABLPGEN procedure (provided in the SHPSSAMP data set) to create it. Runtime options can be defined by using the SYSIN control statements.

There are two levels of global option modules that can be categorized by their effective range: installation level and IMS subsystem level.

Installation level
To set values that will be effective at the installation level, create a global option module named LIU@INST. The values in this module apply to all the databases that are defined in the IMS environment.
IMS subsystem level
To set values that will be effective at the IMS subsystem level, create a global option module named LIU@imsid, where imsid is the 4-character ID of the IMS subsystem. The values that you set in this module apply to all the databases that are defined to that IMS subsystem. In accordance with the options assignment rule, they override the values that are set in the LIU@INST module.
Tip: If you want more than one IMS subsystems to use a set of options that are defined in a single global option module, create a global option module for the IMS subsystem level and use the linkage editor to assign an alias to that global option module.

In a database sharing environment where more than one IMS subsystem shares databases, the LICON data set and option values defined in the global option module must be the same across the IMS subsystems. Assigning an alias is beneficial in such a case as well as in XRF environments. For information about how to assign an alias name, see Setting up the global option modules.

In environments where a LICON data set is used across multiple IMS subsystems, assigning an alias name for the global option module to apply the same runtime options for all IMS IDs is a good practice. However, if you want to set runtime options for each IMS ID, instead of assigning an alias name to the global option module, you can create one global option module for each IMS ID. In such a case, except for certain control statement keywords, the keyword parameters must be the same. You can set different parameters for the following control statement keywords:
  • VERIFY=
  • MSGROUT=
  • MSGDESC=
  • VERIFYLMT=
  • RDEBUILD=
  • INITERR=

When you create global option modules, name the modules LIU@xxxx. At sign (@) is a code-page-dependent character. If you are working in an environment where you cannot use the at sign (@), name the modules LIUGxxxx. Use either format for all the global option modules consistently because maintaining both LIU@xxxx and LIUGxxxx modules can cause confusion. If Integrity Checker finds both LIU@imsid and LIUGimsid in the same effective range level, Integrity Checker ignores LIUGimsid and uses LIU@imsid.