Files Aren't Imported After Implementing 'RecordDeterminerExtension'

Problem

Not all files are imported after implementing ‘RecordDeterminerExtension’, resulting in a smaller cobol import than expected.

Cause

If you implement 'RecordDeterminerExtension' and it can't determine the byte-size of a cobol record, the rest of the cobol record file is dropped and no more records from that file are imported. The byte-size can't be determined if there are changes to a copybook file that result in new record types in your incoming files which aren't accounted for in the extension.

Solution

Contact the person who implemented RecordDeterminerExtension and add more cases to the extension point based on the changes to the copybook.