|Tool Name||COBOL Copybook File|
|Tool Web Site||http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=51416|
|Supported Methodology||[File System] Data Store (Physical Data Model, Logical Data Model) via Cobol Copybook File|
|Remote Repository Browsing for Model Selection|
Import tool: ISO COBOL Copybook File 1985 (http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=51416)
Import interface: [File System] Data Store (Physical Data Model, Logical Data Model) via Cobol Copybook File from COBOL Copybook File
Import bridge: 'CobolCopybook' 10.1.0
The COBOL bridge imports copybook by two ways.
The 'Physical hierarchical model' way represents a Copybook as a Hierarchical file.
The 'Logical data model' way creates both a very different logical and physical models that are based upon the one COBOL itself uses in FD and WS sections.
- The logical model reflects the hierarchical 'layer' that COBOL imposes on what is effectively a flat structure.
- The physical model reflects the truly flat, byte-position defined, record structure.
- the logical model has an entity for each 'group level' (e.g., an 05 name that contains one or more 10 level names) and subtype relationships to reflect the hierarchy. In this way, OCCURS are not expanded into multiple attributes.
- the physical model has all the physical elements required to define a flat record, which is ONE table with all the elements (including multiple columns for OCCURS elements when the proper bridge parameter is set).
The bridge does not currently support the COPY verb, and reports a parsing error at the line and position at which the COPY statement begins. To import Copybooks with the Copy Statement, create an expanded Copybook file with the included sections already in place (replacing the COPY verb). Most COBOL compilers have the option to output only the preprocessed Copybooks with the COPY and REPLACE statements expanded.
FREQUENTLY ASKED QUESTIONS:
Q: Why is the default start column '6' (six) and the default end column '72' (seventy-two)?
A: The bridge parser counts columns starting at 0 (zero), rather than 1 (one). Thus, the defaults leave the standard first six columns for line numbers, next column for comment indicators, and last 8 columns (out of 80) for additional line comment information.
|File||Bridge reads metadata from the COBOL copybook file or COBOL File Description (CFD).||FILE||
|Encoding||Specify the encoding of the text in the COBOL file.||ENUMERATED||
|Import model as||Specifies how to import the model.
'Physical hierarchical model' - represent a Copybook as a Hierarchical file. This is the default.
'Logical data model' - represent a Copybook as a data modeling.
|Physical hierarchical model|
|Run COBOL copybook parser in verbose mode||Run COBOL copybook parser in verbose mode if there are parsing problems arrise. This setting will help to identify causes of the warnings and errors reported by the bridge.||BOOLEAN||
|Expand multiply occuring records||Expand multiply occuring records into multiple attributes.
For example record:
30 OCCURS-TEST PIC X OCCURS 3 TIMES.
will be represented as list of attributes with names like:
Occurence within occurence:
30 OCCURS-GROUP OCCURS 3 TIMES.
40 OCCURS-TEST PIC X OCCURS 2 TIMES.
is represented as:
|Import fillers||Specifies whether filler field names should be imported.
'True' - Filler field names are imported.
'False' - Filler field names are ignored. This is the default value.
|Miscellaneous||Specify miscellaneous options identified with a -letter and value.
For example, -m 4G -s 6 -e 72
-m the maximum Java memory size whole number (e.g. -m 4G or -m 2500M ).
-s start column index in the COBOL copybook file for the parser.
-e end column index in the COBOL copybook file for the parser.
|Meta Integration Repository (MIR)
(based on the OMG CWM standard)
|"COBOL Copybook File"
|Attribute||Record||Records that do not have any sub-record.|
|Position||Caclucated based on the record offsets and lengths|
|BaseType||Picture||Cacluated from picture. See DerivedType.|
|Class||Record||Record that has sub-records.|
|ClassDiagram||All records are included into default diagram automatically.|
|DesignPackage||Record||Created for records that have sub-records to display hierarchy.|
|FileDirectory||COBOL Copybook file|
|Generalization||Record||Created for records that have sub-records and parentrecord.|
|StoreModel||COBOL Copybook file|