When a Mainframe EBCDIC copybook consists of a single type records, you may still need to tweak the copybook and conversion options to make it work. EBCDIC files are NOT a standard and vary from mainframe vendor to mainframe vendor.
By using an output format such as CSV, and then opening the output file in Excel, you can easily check for 'field progression' where field data is moved one or more space to the right or left for each new record. This indicates either a mismatch between the copybook and the file, or more often, a mismatch with the vendor settings used to decode the file.
Try experimenting with the settings 'Assume adjacent COMP fields are overlapped' and 'Allow COMP-3 to be unsigned' of the most common or initial record type. Unfortunately the copybook does not tell us exactly how the data has been stored.
If the error log reports that there were extra bytes in the file that could not be matched, this indicates that
Once tested, the TextPipe filter can be run automatically or on a schedule from the command line. It can also be controlled by other software using COM.
Please drop us an email with your copybook firstname.lastname@example.org