Db2 default DDL attributes not generated within RC/Migrator
search cancel

Db2 default DDL attributes not generated within RC/Migrator


Article ID: 6406


Updated On:


RC/Migrator for DB2 for z/OS RC/Query for DB2 for z/OS RC Compare for DB2 for z/OS


Currently it seems that when using RC/Migrator for Db2 for z/OS (RCM ) to generate DDL for a given object such as a table,
RCM 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.
Would like to see all options punched even if they can default if not specified.


The default Db2 attributes are not generated because they do not 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 is 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 may be very large already.

Additional Information

The RC/Update for Db2 for z/OS, DDL and HDDL line commands do however generate all the DDL including the default options when DDL is generated.