How Are REDEFINES Clauses Handled? - trillium_discovery - trillium_quality - 17.1

Trillium DQ Repository Administrator Guide

Product type
Software
Portfolio
Verify
Product family
Trillium
Product
Trillium > Trillium Discovery
Trillium > Trillium Quality
Version
17.1
Language
English
Product name
Trillium Quality and Discovery
Title
Trillium DQ Repository Administrator Guide
Topic type
Overview
Administration
Configuration
Installation
Reference
How Do I
First publish date
2008

When creating entities described by COBOL copybooks that contain REDEFINES clauses, you have two options:

  • Ignore all REDEFINES clauses in your COBOL copybooks, or

  • Represent all data redefinitions (including nested REDEFINES).

Note: You do not have the option to “pick and choose” REDEFINES clauses during an import. If you have a copybook where only a few of the REDEFINES clauses are required, manually modify the copybook to remove the unnecessary REDEFINES clauses prior to importing the data into Trillium. Make sure that you maintain the original record length if some REDEFINES blocks of the same fields are of different sizes.

To ignore all REDEFINES clauses in a copybook

In the Create Entity Wizard, select the option Redefines: First.

When Trillium encounters a REDEFINES clause, it ignores the REDEFINES clause and retains only the first representation of the data in the copybook.

Example—Results of the Option Redefines First

 

To represent all REDEFINES clauses in a copybook

In the Create Entity Wizard, select the option Redefines: All.

When Trillium encounters a REDEFINES clause, it removes the REDEFINES clause and keeps both representations of the data in the copybook. The data file is then populated to match the copybook.

Example—Results of the Option Redefines All

The corresponding data file is modified by Trillium to match the copybook. In this example, Trillium will add seven bytes of data to the file to account for the redefinition.