Common Causes of Conversion Errors

Listed below are some causes for ConverterPro conversion errors. Errors can occur when:

  • Converting DBMS-specific macros, options, procedures, or functions that can be present in a source data field that are not supported or used by the target DBMS.
  • Converting default functions from DBMS to DBMS and going from instance to instance (for example, an optional module has been installed in the source DBMS and not in the target).
  • Converting data from version to version (deprecated features are no longer supported in the current version of ConverterPro and/or new features have been added).
  • Converting from Brand X to Brand Y DBMS'. Database-specific functions, options, procedures, and macros cannot be converted to work in a different database brand since these objects rely on SQL and programming languages native to the database.
  • Using Data Generation to populate a Target file/table if the data layout has been derived from another file/table. When layouts are reused in this manner, ConverterPro may assign a value to the "MaxSize" property for one or more fields if the layout dictates. The data truncation occurs when the data length generated by the tool exceeds this "MaxSize" property value. To resolve this issue, perform the following steps:
    1. Open the conversion specification within ConverterPro.
    2. Within the Tree View, under "Data Targets", right-click on the data layout name and select "View/Edit Record Layout".
    3. Select the desired field name. Within the "Properties" list on the left-hand side, verify whether the value assigned to property "MaxSize" for the field is valid. Adjust as needed.

  • A database table is converted to an ASCII flat file. Typically, Date/Timestamp, and Number (either Float or Integer) data types are stored as Binary in the database. If you don't change those data types to Strings before sending them to the ASCII flat file, ConverterPro will write the data just as the database stores it. To convert Date/Timestamp and Number data types before sending them to the ASCII flat file, select "View/Edit Record Layout" for your target ASCII flat file and change all of the data types to String. Close the Record Layout Editor, go to the Mapping Editor, and then re-map your fields.

    Important

    Before you re-map the fields, there are now Validation errors next to all of the fields that were previously Date/Timestamp or Number data types. The Validation Tab says that ConverterPro "can't promote <data type> and Qstring for operator =." Remapping will remove these errors. After remapping and clicking the "Validate Syntax" button, notice that the Validation errors have disappeared and that all of the Date and Number fields from the source are now inside <data type>2STR() functions. Your conversion should now run successfully and output all of the data in ASCII format.

  • The error "End of file found before read" while attempting to access a flat file (along with a COBOL copybook layout). This may be caused when the data layout and copybook do not match in terms of record length. Review the two files and ensure that they are compatible.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*