Codes, embedded within the comment section of the original IMAGE schema indicate special processing to occur during the translation to SQL. These include:

• De-concatination of composite fields
• Type conversion (J2 to NUMERIC(9,2) or X8 to DATE)
• Don't automatically expand array fields (the default is to auto-expand)

All IMAGE datatypes are supported and converted to the appropriate native type. VARCHAR support is also available.

Indexes (Unique or non-unique, as appropriate) are created for search and sort items. Primary and Foreign Key relationships are also indicated.

The DDL statements use appropriate EXTENT/STORAGE qualifiers based on the CAPACITY statement.

Scripts for routine maintenance are also created (UPDATE STATISICS and COMPUTE STATISTICS).

Configuration files can indicate fragmentation policy for large tables.

To the degree possible, any differences between the existing table structure and that dictated by the IMAGE schema are output as ALTER TABLE statements. This greatly eases the update process.

Automatic masters can be removed from the database and simulated in the DBFIND/DBGET calls. This solves issues with using third-party tools that aren't aware of Automatic masters.