Data Capture exit routines and logically related databases

Segment data passed to Data Capture exit routines is always physical data. Consequently, you must place restrictions on delete rules in logically related databases supporting Data Capture exit routines.

This topic contains Product-sensitive Programming Interface information.

The following table summarizes which delete rules you can and cannot use in logically related databases with Data Capture exit routines specified on their segments.

Table 1. Delete rule restrictions for logically related databases using Data Capture exit routines
Segment type	Virtual delete rule	Logical delete rule	Physical delete rule
Logical Children	Yes	No	No
Logical Parents	No	Yes	Yes

When a logically related database has a delete rule violation on a logical child:

The logical child cannot have a Data Capture exit routine specified.
No ancestor of the logical child can have a Data Capture exit routine specified.

When a logically related database has a delete rule violation on a logical parent, the logical parent cannot have a Data Capture exit routine specified. ACBGEN validates logical delete rule restrictions and will not allow a PSB that refers to a database that violates these restrictions to proceed.