Transformation Guide

Back Next

Troubleshooting Normalizer Transformations

I cannot edit the ports in my Normalizer transformation when using a relational source.

When you create ports manually, add them on the Normalizer tab in the transformation, not the Ports tab.

Importing a COBOL file failed with numberrors. What should I do?

Verify that the COBOL program follows the COBOL standard, including spaces, tabs, and end of line characters. The COBOL file headings should be similar to the following text:

identification division.
            program-id. mead.
environment division.
        select file-one assign to "fname".
data division.
file section.
fd FILE-ONE.

The Designer does not read hidden characters in the COBOL program. Use a text-only editor to make changes to the COBOL file. Do not use Word or Wordpad. Remove extra spaces.

A session that reads binary data completed, but the information in the target table is incorrect.

Edit the session in the Workflow Manager and verify that the source file format is set correctly. The file format might be EBCDIC or ASCII. The number of bytes to skip between records must be set to 0.

I have a COBOL field description that uses a non-IBM COMP type. How should I import the source?

In the source definition, clear the IBM COMP option.

In my mapping, I use one Expression transformation and one Lookup transformation to modify two output ports from the Normalizer transformation. The mapping concatenates them into a single transformation. All the ports are under the same level. When I check the data loaded in the target, it is incorrect. Why is that?

Rename Saved Search

Table of Contents

Transformation Guide

Transformation Guide

Troubleshooting Normalizer Transformations

Troubleshooting Normalizer Transformations