CDC Guide for z/OS

10.4.1
- 10.5.8
- 10.5.6
- 10.5.5
- 10.5.4
- 10.5.3
- 10.5.2
- 10.5.1
- 10.5
- 10.4.0 HotFix 1
- 10.4.0

Back Next

Detecting Matching SR2 and SR3 Records for ECCR Capture of Relocated Records

For the IDMS log-based ECCR to capture changes made to a relocated SR3 record, it must find the matching SR2 that contains the original record ID. The ECCR uses this record ID to determine if the changes are of CDC interest. To enable the ECCR to find the SR2 record, run the DTLUCSR2 utility. The utility records the pairs of matching SR2 and SR3 records in an internal table. The ECCR can then perform a lookup on the table with an SR3 database key to find the matching SR2 record that contains the original record ID.

Run the DTLUCSR2 utility before you start the ECCR for the first time and after events that tend to relocate records. For example, run the utility after the following events:

An IDMS REORG operation

An IDMS dictionary migration utility (RHDCMIG1 and RHDCMIG2) run

An alter table operation that adds one or more columns, or any other schema change that can increase the record size

The following PowerExchange program logic errors, which are issued for an after image (AFTR) or before image (BFOR):

PWX-00999 Program logic error. Prog="program". Line=line_number. P1="UOW - SR3 AFTR hex_SR3_database_key, not found in hash table". P2=1

PWX-00999 Program logic error. Prog="program". Line=line_number. P1="UOW - SR3 BFOR hex_SR3_database_key, not found in hash table". P2=1

After you run the utility, restart the ECCR so that it can detect the SR2 and SR3 pairs that the utility recorded.

Rename Saved Search

Table of Contents

CDC Guide for z/OS

CDC Guide for z/OS

Detecting Matching SR2 and SR3 Records for ECCR Capture of Relocated Records

Detecting Matching SR2 and SR3 Records for ECCR Capture of Relocated Records