Compatibility of HISTORY data sets

Depending on the options you have activated or set to HISTORY data sets, HISTORY data sets have several incompatibilities. This information summarizes these incompatibilities.

For details about the options and values, see OPTION control statement of DB Historical Data Analyzer.

Format (MULTIENT=YES | NO)

The usage of the key field of the HISTORY data sets depends on whether you have activated multiple entries option. The activation is controlled by specifying MULTIENT=YES or MULTIENT=NO when you update HISTORY data sets. If a user application program processes the HISTORY data sets, considerations for the key field and handling of the entries depending on the option are required.

For more information about the MULTIENT option, see OPTION control statement. For more information about the key field, see Format of the HISTORY data set records.

Record types (EXPORTABLE=YES | NO)

If exportable option is activated, a new format of history record entries will be created. The activation is controlled by specifying EXPORTABLE=YES or EXPORTABLE=NO when you update HISTORY data sets. The new format is compatible with the existing records, and it is not public. It is referred to as a non-public history record.

If a user application program processes the HISTORY data sets, it should bypass the non-public records. The non-public history record is identified by the public format flag in the record. For more information about the flag, see Format of the HISTORY data set records.

Once the non-public records are created, the records will not be deleted even if the exportable option is deactivated. To delete them, run the delete function of the FABGHIST program.

For more information about the EXPORTABLE option, see OPTION control statement.

Lock mechanism (HISTLOCK=GROUP | DATASET)

The HD Pointer Checker jobs are serialized to update a HISTORY data set by the ENQ macro. Different RNAME parameters of the ENQ macro are used depending on whether you have set the HISTORY lock option to GROUP or DATASET. The setting can be changed by specifying HISTLOCK=GROUP or HISTLOCK=DATASET when you update HISTORY data sets. If you define resources of the HISTORY data sets in Global Resource Serialization (GRS) or an equivalent product, you need to specify the correct names.

For more information about the HISTLOCK option, see OPTION control statement.

Format (MULTIIMSID=YES | NO)

The usage of the key field of the HISTORY data sets depends on whether you have enabled the Multiple-IMSID option. The status is controlled by the specification of MULTIIMSID=YES or MULTIIMSID=NO while updating HISTORY data sets. If a user application program processes the HISTORY data sets, considerations for the key field and handling of the entries depending on the option are required.

For more information about the MULTIIMSID option, see OPTION control statement. For more information about the key field, see Format of the HISTORY data set records.