Currently it seems that when we use RC/Migrator to generate DDL for a given object such as a table, RC/Migrator does not actually generate any attribute that is a DB2 default. An example of this is the AUDIT option of table definition. AUDIT can be AUDIT(ALL) or AUDIT(NONE). AUDIT(NONE) is the default if AUDIT is not specified at table create time. We would like to see all options punched even if they can default if not specified.
The default DB2 attributes are not generated because they don't need to be when the attribute would be created with the default value. If the object uses a value that is not the default then it is generated.
By design, RC/Migrator will not incorporate AUDIT (NONE) due to the fact that it's the default value for AUDIT. Since it is implicate you will not see this statement in the generated DDL from the source. If however the value is not the default such as AUDIT(Changes) or (ALL) then it will be generated in the DDL. This is done in order to reduce the amount of DDL generated and to keep it efficient since some strategy analysis outputs are very large already.