Historical data maintained in LICON data sets
Integrity Checker stores historical copies of RDEs in the LICON data sets. RDEs record database access logs for database update, load, and unload applications.
Historical copies of DBD definition
Integrity Checker maintains historical copies of RDEs. Each of these copies contains a part of the database description (DBD) that is used in DMB verifications. Whenever a DBD is changed, Integrity Checker creates a new RDE that contains the latest DMB information. The historical copies of RDEs can be used to track the changes made to DBDs.
The content of the current RDE and historical copies of RDEs can be printed in reports. You can use the reports to examine the information in DBDs, review the changes made to DBDs, or to compare the difference between the current DBD and the DBDs used in the past.
To print the content of an RDE in a report, use the LIST.DB command of the LICON utility. For more information, see the following topics:
- To print a report, see the topic "LIST.DB command" in the IMS Library Integrity Utilities User's Guide.
- For report field descriptions, see the topic "Output from Integrity Checker" in the IMS Library Integrity Utilities User's Guide.
Database access recording option
Integrity Checker records the time stamp of the last database access that is made by update, load, and unload applications in the RDE together with the IMS subsystem name. Such information can be printed in a report, which can be used as evidence in database auditing.
To record database accesses, make the specifications in the RDE by using the global option module or the LICON utility. To use the database access recording option, specify the option for each of the following database access types:
| Database access | Access type identified by Integrity Checker |
|---|---|
| Load utility | Load access |
| Reorganization utility | Load access |
| Unload utility | Unload access |
| Recovery utility | Update access |
| Utility or application program with the PCB processing option (PROCOPT) of A, I, R, or D | Update access |
- To set the options in the global option module, see Global option module generation macro.
- To update the options in RDEs, see the topic "INIT.DB command" in the IMS Library Integrity Utilities User's Guide.
When Integrity Checker is activated in an IMS online environment, Integrity Checker records access information only for the first database authorization request, and the recorded time is not updated while the IMS online environment is active. To have the recorded information updated while the IMS online environment is active, the ACCESS parameter of the DATABASE macro statement must specify UP or EX (during the system definition stage), or the parameter for the /START DB ACCESS= command must specify UP or EX.
- This option is not effective for online reorganization functions or online reorganization utilities that are provided by IMS or IMS Tools.
- For a database access through the High-Speed DEDB Direct Reorganization utility, Integrity Checker identifies the database access type as a database update.
- Database access for load or unload operations is recorded only when the operations are done by IMS standard utilities or IMS Tools utilities.
- If a utility or an application program ends with an error after the Integrity Checker DMB verification process ends successfully, the database access information that is recorded in the RDE is updated in the same way as when the utility or the application program ended successfully, even though the utility or application program ended with an error.
- For index databases or secondary index databases that have no PCBs, Integrity Checker does not record database access information in the RDEs except when the database operation is done by IMS Database Reorganization Expert.