Problem conclusion

This DBD version check was removed in V10.1 because repeated
detections of a mismatch resulted in many messages being
issued, followed by an out-of-memory condition (V10.1 APAR
PM62789). Removal of the DBD version check has been
backported to V9.5.
With this change applied, users are now responsible for
managing the change process and its impact on change data
capture processing. If the contents of a segment being
captured are reordered, results are unpredictable.
In the case where the IMS agent goes into recovery, it is
recommended that users verify that the DBD version in a data
capture log matches the DBD version referenced by the
correlation service.