Your Browser is not longer supported

Please use Google Chrome, Mozilla Firefox or Microsoft Edge to view the page correctly
Loading...

{{viewport.spaceProperty.prod}}

Generating a new SIA and entering it in the DBDIR with BGSIA

Once the Schema DDL and the SSL (optional) have been successfully compiled, the SIA of the new schema must be generated and entered in the DBDIR using the BGSIA utility routine.

The saved SIA of the old schema remains in the DBDIR so that, after the BGSIA run, DBDIR contains the SIAs of both the old and the new schemas. BALTER requires both to check and execute the planned renaming.

The BGSIA run corresponds to the run carried out for the creation of the database (see section "Setting up the Schema Information Area (SIA) with BGSIA"). After the BGSIA run, the module UDSHASH generated by BGSIA must be stored in the HASHLIB.

To ensure that BGSIA recognizes realms, record types and sets which remain the same in the renaming cycle despite the name change and leaves the existing references unchanged, name changes for realms, record types and sets must be specified in full in additional statements. The names in the DDL/SSL source are affected by this. The additional statements of BGSIA do not change any names in these sources.

Dynamic sets can be renamed in precisely the same way. The names of the dynamic sets required for using IQS are predefined and may not be changed. However, this is not checked. Implicit sets do not need to be specified explicitly. They are renamed automatically in accordance with the renamed record type (SYS_recordname) as soon as a search key is defined.

If you work with your own hash routines, you must also store these in the HASHLIB with the attributes RMODE=ANY and AMODE=ANY at the latest before BALTER is started.

If, when the SIA is generated, it is recognized that not just purely renaming is involved, a message is issued that the renaming cycle is being aborted because the references do not match. This message can be used for correcting the source. A precise analysis only takes place with BALTER. Illegal type changes and illegal splitting or grouping of items are examples of changes which conflict with pure renaming.

Generating SIA and entering it in DBDIR

01  /ADD-FILE-LINK LINK-NAME=DATABASE,FILE-NAME=dbname.DBDIR

02  /SELECT-PRODUCT-VERSION PRODUCT-NAME=UDS-SQL,VERSION=version,SCOPE=*TASK

03  /DELETE-SYSTEM-FILE FILE-NAME=*OMF

04  /START-UDS-BGSIA

05  GENERATE SCHEMA schema-name

06  [DISPLAY[ SCHEMA schema-name]]

07  END

Entering the module UDSHASH in the HASHLIB

01 /START-LMS

02 //OPEN-LIB LIB=dbname.HASHLIB,MODE=*UPDATE

03 //ADD-ELEMENT FROM-FILE=*OMF,TO-ELEMENT=*LIBRARY-ELEMENT(TYPE=R)

04 //END