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 DBDIR so that, after the BGSIA run, DBDIR contains the SIAs of both the old and the new schemas. BALTER needs both in order to adapt the stored data to the modified schema.

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 entered in the HASHLIB.

If hash routines written by the DB administrator are used, these must also be entered in the HASHLIB with the attributes RMODE=ANY and AMODE=ANY before BALTER is started by means of EXECUTION IS YES.

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