With each version and revision, HiRDB revises the default values that are assumed when you omit from the HiRDB system definition operands, utility options, and SQL options. To handle these changes to default values, HiRDB versions 09-50 and later offer two modes for the default behavior when operands are omitted: recommended mode, which assumes the recommended default values, and compatibility mode, which uses the default values for a specific version of HiRDB. Normally, to build a more secure system, we suggest that you apply the recommended mode, which greatly reduces the number of operands that must be specified.

For details about the advantages and disadvantages of changing the default values when you upgrade from a version earlier than 09-50, see 1.4.1(8) Checking the default values of operands in the HiRDB system definition and 1.4.1(9) Checking other default values. After checking the default values, if you decide to focus on compatibility with the previous version, you can apply the compatibility mode to make the default values the same as in the previous version. However, in this case all of the operands will have the previous version's default values, so we recommend specifying the recommended values on a per-operand basis.

If you want to update to the HiRDB update version, apply the operand default behavior that is already in effect.

The behavior when operands are omitted can be selected during setup of HiRDB. The behavior can also be changed using the command pdsetenv.