Overview of UDS/SQL programs

The UDS/SQL (BS2000) system in its entirety incorporates a series of programs required for creating, maintaining and communicating with the database

The functions of these programs are described in brief below:

Creating the database	Preparing the program run	Loading or unloading the database	Monitoring the session	Working with the database	Testing DML functions
BCREATE DDL SSL BGSIA BFORMAT BGSSIA BPRIVACY OPRIVACY	BCALLSI	BINILOAD BOUTLOAD	UDSMON	IQS (not part of the UDS/SQL delivery package)	DMLTEST
D a t a b a s e   m a i n t e n a n c e
Information output	Reorganizing the database	Restructuring the database/Renaming database objects	Recovering the database	Checking the database	Database conversion
BPSIA BPSQLSIA BSTATUS BPRECORD	BREORG BMODTT ONLUTIL	BCHANGE BRENAME BALTER	BMEND	BCHECK	BPGSIZE BTRANS24
D a t a b a s e   o p e r a t i o n
		Administer UDS/SQL
		UDSADM

Table 8: Program overview

Creating the database

BCREATE	formats the DBDIR and the DBCOM.
DDL	DDL compiler compiles the Schema DDL and the Subschema DDL, and sets up DBCOM and COSSD.
SSL	SSL compiler compiles the SSL and modifies data in DBCOM.
BGSIA	sets up the schema information area (SIA) and stores it in the DBDIR.
BFORMAT	formats the user realms of the database and modifies the SIA.
BGSSIA	sets up the subschema information area (SSIA) and stores it in the DBDIR
BPRIVACY or OPRIVACY	enters the user access rights in the DBDIR.

Preparing for the program run

BCALLSI

only needed in conjunction with CALL DML. BCALLSI makes subschema information available to CALL DML users.

Loading the database

BINILOAD

rapidly loads large volumes of data of the same record type into the database.

Unloading the database

BOUTLOAD

copies, deletes or unloads record types from a database.

Monitoring the session

UDSMON

outputs the UDS/SQL operating values during database operation.

Testing DML functions

DMLTEST

tests individual DML functions in interactive mode and in procedures.

Outputting information on the database

BPSIA	prints a summary of the chief information from the schema or a given subschema of the database
BPSQLSIA	prints the relational schema information of an existing UDS/SQL subschema defined in accordance with the CODASYL model. The relational schema information serves as a programming aid for the SQL user.
BSTATUS	generates statistics on storage occupancy in the database realms.
BPRECORD	outputs the contents of database realms.

Reorganizing the database

BREORG	increases and reduces the size of database realms, increases and reduces the permissible number of records of a record type and reorganizes tables and hash areas
BMODTT	controls the reuse of database key values that have been released and the search for free space by the DBH.
ONLUTIL	relocates records in a database and modifies settings to a database.

Restructuring/renaming the database

BCHANGE	prepares DBDIR, DBCOM and COSSD for restructuring
BRENAME	prepares DBDIR, DBCOM and COSSD for renaming.
BALTER	executes the restructuring/renaming of the existing database in accordance with the new schema description.

Recovering the database

BMEND

creates ALOG files and offers functions for recovering a destroyed database and outputting information on the status of realms to be updated and ALOG files.

Checking the database

BCHECK

checks whether the physical structures of a database are correct; can be used in conjunction with data security so that inconsistencies in the database can be detected and eliminated at an early stage.

Converting the database

BPGSIZE	defines a new page format for the database (database conversion). During conversion, BPGSIZE can optionally create a copy of the database with the larger page length. a copy of the database with the unaltered page length. Note that the realms of the converted database usually require less storage space.
BTRANS24	converts databases of UDS/SQL V2.0 to V2.3 for use in UDS/SQL V2.4 and higher.

UDS/SQL administration

UDSADM

The UDSADM program can be used to administer a UDS/SQL configuration.

Some utility programs that access UDS/SQL databases have to be run in conjunction with the DBH: such programs load the linked-in DBH using default values for the load parameters, and they all work with only one database.

The following table shows which programs load the linked-in DBH dynamically and which require files from the compiler database during the program run:

UDS/SQL program	Loads linked-in DBH dynamically	Access to
		DBDIR	DBCOM	COSSD
BALTER	-	X	X	-
BCALLSI	-	-	-	X
BCHANGE	-	X	X	X
BCHECK	-	X	-	-
BCREATE	-	X	X	-
BFORMAT	-	X	-	-
BGSIA	X	X	X	-
BGSSIA	X	X	X	-
BINILOAD	-	X	X1	-
BMEND	-	X	X	-
BMODTT	-	X	-	-
BOUTLOAD	-	X	X2	-
BPGSIZE	-	X	X	X
BPRECORD	-	X	-	-
BPRIVACY	X	X	X3	-
BPSIA	-	X	-	-
BPSQLSIA	-	X	-	X
BRENAME	-	X	X	X
BREORG	-	X	-	-
BSTATUS	-	X	-	-
BTRANS24	-	X	X	-
COBOL compiler	-	-	-	X
DDL compiler	X	X	X	X
DMLTEST	X4	X	-	-
ONLINE- PRIVACY	-	X	X3	-
ONLINE-UTILITY	X4	X	-	-
SSL compiler	X	X	X	-
UDSADM	-	-	-	-
UDSMON	-	-	-	-

Table 9: Overview of programs in the UDS/SQL database system

¹ DBCOM is used when input file is in CSV format or record type contains a variable field

² DBCOM is used when  CSV-OUTPUT = *YES is specified. 

³ The DBCOM is not read, but it must be present

⁴ Optional