The compiler database (see section "Files and realms of a UDS/SQL database") consists of the following realms:
DBDIR | database directory |
DBCOM | database compiler realm |
the file:
COSSD | COBOL subschema directory |
These files and realms have to be set up and their size specified using the BS2000 command CREATE-FILE.
Setting up DBDIR and DBCOM
|
dbname
Database name; max. 17 characters in length. dbname is used as a partial qualifier in almost all file names for database files and has to conform to the following rules:
dbname must be the same for all files in the database.
dbname must not contain special characters or blanks, and its first character must be a letter.
:catid:$userid.dbname.realmname.copyname may be at most 54 characters in length.
With UDS-D:
dbname must be unique network-wide.
SPACE
Specification of storage space (see section “Maximum size of UDS/SQL files" in chapter "Files and realms of a UDS/SQL database").
PRIMARY-ALLOCATION=primary
Primary allocation;
In order to format the DBCOM and DBDIR with the BCREATE utility routine, the following minimum values are required for the primary allocation (see section "Formatting the compiler database with BCREATE"):
DBDIR | DBCOM | |
2-Kbyte format | 52 | 100 |
4-Kbyte format | 79 | 424 |
8-Kbyte format | 127 | 607 |
In the case of databases with large schemas, a correspondingly higher allocation is required, or automatic extensibility must be enable by a secondary allocation > 0.
The BREORG utility routine can be used later to reduce the amount of unused space (see the "Recovery, Information and Reorganization" manual, BREORG).
SECONDARY-ALLOCATION=secondary
Secondary allocation.
secondary=0
This setting suppresses the option of automatic realm extensibility and of online realm extensibility.
secondary>0
Prerequisite for automatic realm extensibility and online realm extensibility and prerequisite for activating online extensibility of the DBDIR using the ACT INCR command.
In the case of secondary>0, online realm extensibility is already activated for the realm concerned when the database is created.
When online realm extensibility is activated in this way, the default values NR-PAGES=64 and MIN-PAGES=0 are entered for NR-PAGES and MIN-PAGES (see Activating online extensibility when creating databases and DAL command ACT INCR in the "Database Operation" manual).
VOLUME
DEVICE-TYPE
if DBDIR and DBCOM are stored on private disk (PRIVATE VOLUME), the following must be specified:
priv-vsn
Volume serial number
device
Device type of private disk
LINK-NAME
The database directory should be linked to the database via the file link name DATABASE.
Setting up COSSD
|
SPACE
Specification of storage space (see section “Maximum size of UDS/SQL files in chapter "Files and realms of a UDS/SQL database").
PRIMARY-ALLOCATION=primary
Primary allocation;
the storage space requirement of the COSSD is directly dependent on the size of the compiled subschemas.
In order to ensure that additional compiled subschemas can be added too the COSSD at a later stage if required, it is advisable to create the COSSD with a primary and secondary allocation (see below) of 100 2K units (BS2000 half pages) each.
SECONDARY-ALLOCATION=secondary
Secondary allocation;
depending on how the operating system has been generated, there may be limits on the extent to which COSSD can be dynamically extended.
A value of 100 2K units (BS2000 half pages) is recommended.
VOLUME
DEVICE-TYPE
If you store COSSD on private disk (PRIVATE VOLUME), the following must be specified:
priv-vsn
Volume serial number
device
Device type of private disk.