BALTER checks the renaming in a predefined sequence.
BALTER begins by checking fundamental structures of the schemas ("SIA_CONTROL"). These include the internal numbers of realms, record types, sets and keys in the old and the new schemas. It is not permissible that these numbers have changed.
The area declarations are then checked. Only renaming of user realms is permitted.
The declarations of the record types are subsequently checked. The renaming of items, grouping of items and the splitting of items are checked here. A check is also made to see whether the declarations of the CALC key match.
Finally the set declarations and consequently also the logically associated key declarations are checked to see whether they match. Only sets may be renamed here.
The BALTER run finishes with any renaming of realms being implemented by recataloging the realms concerned. This is the only case in which user realms need to be opened and modified in a renaming cycle.
All renaming actions and actions for splitting and grouping items are documented in REPORT IS YES. The number of realms, record types (records) and sets which are unchanged is also output.
Modifications in the schema which conflict with pure renaming lead to error messages and to the recycling cycle being aborted. An error can result in multiple error messages as it can lead to related modifications at several places in the SIA. The analysis is not terminated after the first error which is detected but only after multiple errors have occurred.