Concepts › Audit Phase › Set Disconnection Processing › Verifying Pointers

Verifying Pointers

When a record is to be audited for set disconnections, each pointer is verified by finding the indicated record. For example, if there are 24,000 GREPORT records with next, prior, and owner pointers in the STUDENT-GREPORT set, then CA IDMS/DB Audit verifies each pointer (72,000 pointers) by finding 72,000 records.

Two disconnected records are illustrated in Figure 2.39. If all of the pointers of a record are null, the record is fully disconnected. If all of the pointers of a record are a combination of invalid and null pointers, the record is partially disconnected. Because all of the pointers of the Joan Brown record are null (indicated by -1), it is fully disconnected. The David Lee record is partially disconnected, because its only pointer that is not null does not point into a set.

Note: Because of the large number of I/Os and calls to DBIO,DISCONNECT can increase processing time significantly. You can, however, reduce processing time through QuickCheck. QuickCheck DISCONNECT looks for fully disconnected records only. QuickCheck USERSETS looks for partially disconnected records only.