Illegal schema modifications in the renaming cycle

To enable violations of the renaming rules to be corrected quickly, a current version of the old schema should be created using the BPSIA utility routine before the renaming cycle begins. In the renaming cycle you should also use the DISPLAY statement in the BGSIA utility routine. In some cases BGSIA already recognizes that contradictory declarations are contained in the new schema when renaming takes place.

In the renaming cycle the BALTER output concerning illegal differences between the old and new schemas largely relates to the corresponding information in the output of BPSIA and BGSIA. BALTER also outputs the differences in individual items in record types.

When corrections are made, first of all the information relating to the record types should be observed because messages about illegal modifications in SIA_CONTROL, the sets and keys are very often due to illegal declarations in items of the record types.

Illegal schema modifications are checked for in five phases.

In phase one BALTER checks SIA-CONTROL. Modifications in SIA-CONTROL always indicate illegal modifications. The following illegal modifications can occur (message text: DIFFERENCE IN sia-content):

Message (sia-content)	Meaning
NR_AREAS	The highest realm number assigned (area reference) is different in the old and new schemas.
NR_RECORDS	The highest record type number assigned (REC-REF) is different in the old and new schemas.
NR_SETS	The highest set number assigned (SET-REF) is different in the old and new schemas.
NR_KEYS	The highest key number assigned (KEY-REF) is different in the old and new schemas.
SCHEMA_NAME	The old and new schema names are not the same.
IMPL_RESULT_SET	There are differences in the IMPLICIT_RESULT_SET of the schema.
SINGULAR_SET	There are differences in the first SYSTEM set of the schema.
DYNAMIC_SET	There are differences in the first dynamic set of the schema.
MAX_REC_LENGTH	The length of the largest record type is different in the old and new schemas.
MAX_ENTRY_LENGTH	The length of the longest key is different in the old and new schemas.
MAX_MEMBERSHIPS	The largest number of sets in which Member is a record type is different in the old and new schemas.
MAX_SPLIT_PARAMETER	The maximum number of pages in the SSL which is defined in the REORGANIZATION parameter is different.
LENGTH_KEY_BIT	The check information for the MODIFY information is different in the old and new schemas.
BLOCK_LENGTH	The length of the database pages is different in the old and new schemas.

In phase two the individual areas are checked for illegal modifications. The following illegal modifications can occur (message text: DIFFERENCE IN area-content):

Message (area-content)	Meaning
AREA_REF	The reference of the realm is different in the old and new schemas.
AREA_PROPERTIES	The central properties of the realm are different in the old and new schemas (TEMP, D/T).
NR_WITHIN_RECORDS	The number of record types which can be stored in the realm is different in the old and new schemas.
RECORD_LIST	In the old and new schemas there are differences between the references of the record types which can be stored in the realm.

The DIFFERENT USE OF AREA-REF message indicates that the assignment of this realm reference is so different in the new and old schemas that a more detailed differentiated analysis does not make sense.

The AREA RENAMING WITH ALOG message indicates that the renaming of areas is allowed only if After Image Logging is deactivated. If the database is operated with After Image Logging you must deactivate it before the renaming cycle is started.

In phase three the

• various record types are checked for illegal modifications.

• keys at record type level are checked for changes to the SIA data.

• key information which is only later stored in the SSIA is checked.

• renaming of items is checked.

The following illegal modifications can occur when the various record types are modified (message text: DIFFERENCE IN record-content):

Message (record-content)	Meaning
REC_REF	The reference of the record type is different in the old and new schemas.
LOCATION_MODE	There are differences with regard to the location of the DBKEY or DBKEY-LONG item which is used for LOCATION MODE DIRECT.
REC_PROPERTIES	The central properties of the record type are different in the old and new schemas.
IMPLICIT_SET	There are differences in the implicit set of the record type.
OWNER_CHAIN	There are differences in the first set in which the record type is Owner.
MEMBER_CHAIN	There are differences in the first set in which the record type is Member.
RECORD_LENGTH	The length of the record is different in the old and new schemas.
SYSTEM_INFO	The length of the set connection data is different in the old and new schemas.
PHYSICAL_CALC_INFO	The location of the CALC buckets is different in the old and new schemas.
DBTT_ENTRY_LENGTH	The length of the DBTT entries is different in the old and new schemas.
LOCATION_VIA	The type of location mode is different in the old and new schemas.

The DIFFERENT USE OF REC-REF message indicates that the assignment of this record reference is so different in the new and old schemas that a more detailed differentiated analysis does not make sense.

The following illegal modifications in the SIA data can occur when a key in a set is modified:

Message (record-content)	Meaning
KEY_LENGTH	The key length is different in the old and new schemas.
HASH	The reference to the hash routine is different in the old and new schemas.
DBTT_COLUMN	The DBTT entry corresponding to the key is different in the old and new schemas.
KEY_PROPERTIES	The properties of the key are different in the old and new schemas.

The following illegal modifications can occur in the key information which is only later entered in the SSIA (message text: DIFFERENCE IN key-content):

Message (key-content)	Meaning
KEY_LTH	The key length is different in the old and new schemas.
DBTT_COL_NR	The DBTT entry corresponding to the key is different in the old and new schemas.
INDEX_AREA_REF	The reference of the realm is different in the old and new schemas.
CALC_PROCEDURE_NAME	The name of the CALC routine is different in the old and new schemas.
CALC_PROCEDURE_NR	The number of the CALC routine is different in the old and new schemas.
KEY_BITS	The properties of the key are different in the old and new schemas.
KEY_REF_NR	The (internal) reference number is different in the old and new schemas.
NR_BUCKETS	The size of the CALC area is different in the old and new schemas.
USER_KEY_TYPE	The item type of the key is different in the old and new schemas.
KEY_INDICATOR	The properties of the key are different in the old and new schemas.
KEY_ITEM_DISPL	A key item has a different displacement in the old and new schemas.
KEY_ITEM_CONCAT	The grouping of key items in the new schema does not match the key items in the old schema.
KEY_ITEM_SPLIT	The splitting of key items in the new schema does not match the item fields in the old schema.

The DIFFERENT USE OF KEY-REF message indicates that the assignment of this key reference is so different in the new and old schemas that a more detailed differentiated analysis does not make sense.

The following illegal modifications can occur when items are renamed:

Message	Meaning
ITEM BOUNDARIES UNSUITABLE	Grouping or splitting items leads to overlapping.
CONCATENATION TO NON CHAR TYPE	Items were grouped but the grouped item in the new schema is not of the type CHAR.
SPLIT OF NON CHAR TYPE	An item is split but the item in the old schema is not of the type CHAR.
FORM GROUP FROM NON CHAR TYPE	Items were combined to form a group but not all items in the new schema are of the type CHAR.
SPLIT GROUP TO NON CHAR TYPE	A group was split into one or more items but not all items in the new schema are of the type CHAR.
LENGTH DIFFERENCE OF TYPE VARIABLE	The maximum length of a variable item at the end of the record type was modified illegally.
LENGTH DIFFERENCE OF LAST OLD ITEM	The length of the last item in the old schema indicates illegal renaming.
LENGTH DIFFERENCE OF LAST NEW ITEM	The length of the last item in the new schema indicates illegal renaming.
DIFFERENCE IN COMPRESSED RECORD	Illegal modifications have been made in a compressed record type.
DIFFERENCE IN ITEM TYPE	Indicates an illegal type change in the item
TYPE CHANGE OF NON CHAR TYPE	An illegal type change was detected.
VECTOR CHANGE OF NON CHAR TYPE	An illegal type change was detected when a vector was changed.

In phase four the

• various sets are checked for illegal modifications.

• keys at set level are checked for modifications in the SIA data. The same illegal modifications can occur as in phase three (see "Illegal schema modifications in the renaming cycle").

As the keys have no explicit names, corresponding internal numbers are output for various keys or an unambiguous name is output for the key type in the case of record types and sets. Differences in the keys for record types or sets result from illegal modifications to the related data items from which the keys are formed. In order to eradicate these differences, the renaming errors must be corrected.

• key information which is only later stored in the SSIA is checked. The same keys with the corresponding number are output as in the schema’s BPSIA report. The same illegal modifications can occur as in phase three (see "Illegal schema modifications in the renaming cycle").

The following illegal modifications can occur when the various sets are modified (message text: DIFFERENCE IN set-content):

Message (set-content)	Meaning
SET_REF	The reference of the set is different in the old and new schemas.
SET_PROPERTIES	The properties of the set are different in the old and new schemas.
SET_MODE	The set mode is different in the old and new schemas.
SET_ORDER	The sort sequence is different in the old and new schemas.
OWNER_OF_SET	The owner reference is different in the old and new schemas.
MEMBER_OF_SET	The member reference is different in the old and new schemas.
OWNER_CHAIN	Owner chaining is different in the old and new schemas.
MEMBER_CHAIN	Member chaining is different in the old and new schemas.
SINGULAR_SET_CHAIN	Chaining of the SYSTEM set is different in the old and new schemas.
DYNAMIC_SET_CHAIN	Chaining of the dynamic sets is different in the old and new schemas.
KEY_CHAIN	Chaining of the set is different in the old and new schemas.
SET_MEMBERSHIP	The POPULATION / INCREASE clause is different in the old and new schemas.
SET_CONNECTION	There are differences in the set connection data.
ANCHOR_DBKEY	The database key of the anchor of a singular set is different in the old and new schemas.

The DIFFERENT USE OF SET-REF message indicates that the assignment of this set reference is so different in the new and old schemas that a more detailed differentiated analysis does not make sense.

In the fifth phase the physical order of all keys of the SIA which are connected to the record types or sets is checked. The physical order of the keys must be unchanged as they are assigned an implicit numbering which the database uses. Illegal modifications can occur again here (see "Illegal schema modifications in the renaming cycle").