Data Transformation Engine Type Tree Importers Reference Guide
Chapter 2 - Using the Importer Wizard  COBOL Copybook Importer 
Type Tree Importers Reference Guide 
16 
Warning and error messages that may occur when generating a type tree from a 
copybook file are listed in the Appendix A – Return Codes and Error Messages. 
Modifying a Copybook File 
If the copybook file does not conform to what the COBOL Copybook Importer 
Wizard expects, a type tree is not successfully generated. Before importing the 
copybook file, you may want to: 
♦  Check that the level number statements (for example, 01, 05, 10) in your 
copybook do not start before Column 8. 
♦  Check for statements not supported by the COBOL Copybook Importer. The 
importer does not expand any embedded COPY clauses. Add the data included 
in the embedded COPY clauses before you run the COBOL Copybook Importer. 
Note  If you do not modify the copybook file before running the COBOL Copybook 
Importer wizard, use the Type Designer to manually modify the generated type 
tree. See the section COBOL Features Not Supported for information. 
Modifying a Generated Type Tree 
The COBOL Copybook Importer automatically generates type trees from COBOL 
copybooks that describe the format of data. However, a copybook may contain 
certain statements or have insufficient information that result in type trees being 
generated that require some manual modification. Use the Type Designer to 
modify any type tree that is generated by the COBOL Copybook Importer so that 
the types contained in the tree accurately represent your data. The situations that 
may require type tree modifications are: 
♦  The copybook contains REDEFINES clause(s). 
♦  The copybook contains VALUES THROUGH or VALUES THRU clause(s). 
♦  The copybook contains statements that are not supported by the wizard. 
♦  The Byte-Storage Mode is used. 
REDEFINES Clause 
If a copybook contains a REDEFINES clause, the COBOL Copybook Importer adds 
a group subtype for the REDEFINES object. However, a copybook does not contain 
sufficient information for the COBOL Copybook Importer to determine how the 
redefined type is used. 
For example, REDEFINES may be used to overlay different Record subtypes. In 
this case, you may want to: 










