Depending on the import type selected in the
Import FD From field of the Importer, there are a number of restrictions.
The following restrictions and problems exist in the extraction process when using the
RM/COBOL Source File using RST Schema Extractor (.cbl -> .rst) option:
- Empty groups generate a syntax error and the entire COBOL source is not imported into the catalog.
- All relational-operators for the VALUE clause are not supported. Condition items with these relational operators generate
a syntax error and the entire COBOL source is not imported into the catalog. For more information, see
Relation Condition in Chapter 5 and
VALUE Clause, Format 2 in Chapter 4 of the
RM/COBOL Language Reference Manual.
- Data items with a USAGE Clause of Pointer are not supported. They will result in a syntax error and prevent the COBOL source
from being imported into the catalog.
- The source format extensions introduced in RM/COBOL 11, including longer source lines and changing of the right margin, are
not supported, will result in syntax errors, and prevent the COBOL source from being imported into the catalog.
The following restrictions and problems exist in the extraction process for when using the
RM/COBOL Object File (*.cob) option:
- Object files must have been compiled with the Y (or Y=1) compiler option.
- Empty groups are ignored and are not imported into the catalog.
- The following relational-operators for the VALUE clause are not supported: GREATER THAN, >, LESS THAN, <, GREATER THAN OR
EQUAL TO, >=, LESS THAN OR EQUAL TO, <=, and LIKE, and their NOT variations. Condition items with these relational operators
are ignored and not imported into the catalog. For more information, see
Relation Condition in Chapter 5 and
VALUE Clause, Format 2 in Chapter 4 of the
RM/COBOL Language Reference Manual.
- Data items with USAGE Clause of Pointer generate an import error and the entire COBOL source is not imported into the catalog.
- RM/COBOL object programs do not contain the original level numbers for data items defined in a record description. Therefore,
level numbers are generated during import in increments of 5. The generated level numbers are stored in the catalog during
import and cannot be changed.