DFS3252I DATA EXISTS ON yyy LOG THAT DOES NOT EXIST ON zzz LOG.

Explanation

During the processing of the Log Recovery utility in CLS mode, DFSULG20 found that data existed on one input log but did not exist on the other log. Also, when DFSFDLW0 was called to copy log records from the WADS, all the records already existed on one of the input logs. This scenario can happen, for instance, if there is a write error on one of the OLDSs. This is not necessarily an error condition because the Log Archive utility also detects this inconsistency and creates SLDS or RLDS from the OLDS that has all of the data.

In the message text, the values of yyy and zzz can be either PRIMARY and SECONDARY or vice versa, depending upon which is appropriate in which spot.

System action

The utility dumps the error block, which might be the end-of-file marker if a write error was encountered, and continues processing in CLS mode. Neither OLDS is flagged as being in error in DBRC.

User response

No response is necessary. This message is put out as informational to make you aware that one OLDS does not contain all of the data that it is supposed to. You might have already known before running the Log Recovery utility that the OLDS encountered a problem such as a write error.

Problem determination

To determine which blocks are on one OLDS and not on the other, you can use a tool such as IMS Problem Investigator for z/OS® or DFSERA10 to check type 4800 log records. There is one type 4800 log record per block and it contains fields such as the block sequence number.