Reducing the amount of captured data

If the internal area of the changed data log record is not large enough to hold all of the data, the ERROR_LOG flag is set in the log record to indicate that the data is not complete. You can specify CASCADE,KEY,NODATA,NOPATH in the EXIT= parameter in the DBDGEN if cascade is required.

The changed data log record can contain a large amount of data for cascade deletes, especially when path data is requested. The data is staged in an internal area prior to logging. If this internal area is not large enough to hold all of the data, the ERROR_LOG flag is set in the log record to indicate that the data is not complete, although, the IMS data is committed and the call completes normally.

To avoid large amounts of data being written to the log and possible incomplete log records, specify CASCADE,KEY,NODATA,NOPATH in the EXIT= parameter in the DBDGEN if cascade is required. This specification results in just the concatenated key being written to the log during DLET operations, which significantly reduces the amount of data that is captured during a cascade delete. For data propagation to Db2 for z/OS® where the primary key is derived from the concatenated key, the segment data is not required for the delete in Db2 for z/OS.