Sometimes, the data has a longer record length than the length described by a COBOL copybook or schema. Since this is a common issue, Trillium loads the data source and does not reject any data that does not match. Instead, Trillium represents the data just as the copybook or schema describes it with the addition of a field named Overflow.
Note: If your data source uses line feeds or carriage returns as delimiters and you omit
that specification when you create the
entity, the entity will contain an Overflow attribute.
Check for Overflow attributes
To check for Overflow attributes
- From the Navigation View, click the Entities tab on the Discover bar.
- Expand each entity.
- Look for any attribute with the name Overflow.
- Make note of which entity or entities have an Overflow attribute and then investigate the causes of the overflow.
Locate overflow rows
To locate overflow rows
- From the Navigation View, click the Entities tab.
- From the expanded entities list, find the COBOL-based entities that you identified as problematic.
- Right-click the entity and select Drill down toMetadata. The Entity List View opens.
-
Double-click the metadata labeled Rows and try to identify the following:
- Which row has a value in the column labeled Overflow?
- What value displays in the column labeled Overflow?
- Does the copybook accommodate for these values? If not, correct the copybook and create the entity again.
Locate Overflow rows when there are no visible values in the Overflow columns
To locate Overflow rows when there are no visible values in the Overflow columns
- Double-click the attribute labeled Overflow.
- Double-click Values.
- Highlight the values in the List View.
- Right-click and select Drill down to Matching Rows.
-
Examine the rows to determine the problem:
- What values are common in the last column of that entity (column left of Overflow)?
- Does the copybook have enough space allocated for each attribute (field)? For example, does a PIC X(10) contain data that is 13 characters long? If not, correct the copybook and try to create the Entity again.