This field, if set to IIADD_INCONSISTENT, tells the DBMS Server to start even if the values of the current add_major_id and add_minor_id fields do not agree with those in use by the Ingres recovery system. Setting this field is very dangerous and must only be done in test installations.

If the add_risk_consistency field is set, the DBMS Server ignores any disagreements between the major and minor ID fields of the support processes and the system. This is very dangerous in a production environment.

The DBMS Server uses these values to ensure that all support processes know about all the data types in the system, ensuring recoverability across the installation. When a support process starts up, it checks the major and minor ID values in this block against the major and minor ID values known to the system. If the major_id values are not equal and the process' minor_id is not equal to or greater than the system's, the process not does start.

The add_major_id field represents the high order 4 bytes and the add_minor_id, the low order 4 bytes of an 8-byte value. The initial values of the major and minor IDs, representing Ingres in the original state, are 0x80000000 and 0, respectively.

To display the current values for these fields, run the lockstat utility. Look for a lock with the key SYS_CONTROL II_DATATYPE_LEVEL. This key has an 8-byte value associated with it. The high order 4 bytes of this value represent the major_id and the low order 4 bytes, the minor_id. For example, the value associated with this key for the default data type level is '8000000000000000', representing the major_id of 0x80000000 and the minor_id of 0 which is Ingres in the original state.

Increment the add_major_id field each time you add a new user-defined data type. User values for this field must be greater than 0. Minor_id must be greater than or equal to 0. Reset the add_minor_id field to 0 whenever the add_major_id is changed.

Specifies the length of the character string pointed to by add_user_string.

Pointer to a character string that is included in the system log.

4-byte integer that can be filled with a bitmask to set trace functions to be provided during system startup. There are two bits used by trace functions:

IIADD_T_LOG_MASK (1) directs the DBMS Server to place a number of trace messages in the various trace logs which exist in the system. While operating the DBMS Server, defining II_DBMS_LOG to a file causes the DBMS Server to place copies of the system error log messages in that file. If the IIADD_T_LOG_MASK bit is set, user-defined abstract data type initialization places status and error messages in this file.

IIADD_T_FAIL_MASK (2) directs the system to shut down if there are failures while initializing the user-defined data types. This is useful in test situations.

By default, the system ignores any errors encountered in processing new data type information and continues startup as if no user information was provided.

Must be set to the sum of the add_dt_cnt, add_fo_cnt, and add_fi_cnt fields.

A 4-byte integer field that must be set to the count of data types to be added.

This field must point to an array of IIADD_DT_DFN structures that define new data types. (For instructions on filling in the IIADD_DT_DFN structures, see the chapter "Defining Data Types.") If the add_dt_cnt field is zero, set add_dt_dfn to zero.

This field is a 4-byte integer that must be set to the count of functions to be added.

This field must point to an array of IIADD_FO_DFN structures that define new functions. For details, see the chapter “Defining Functions.” If the add_fo_cnt field is zero, set add_fo_dfn to zero.

This field is a 4-byte integer that must be set to the count of function instances to be added.

This field must point to an array of IIADD_FI_DFN structures that define new function instances. For details, see the chapter “Defining Function Instances.” If the add_fi_cnt field is zero, set add_fi_dfn to zero.