An authorized user creates the database's catalog space with the utility statement CREATE CATALOG.
System administrators grant the right to execute the utility statement CREATE CATALOG to a specific system user ID by making this user ID known to the appropriate SESAM/SQL DBH with the DBH option ADMINISTRATOR, or with the administration statement MODIFY-ADMINISTRATION (see the “Database Operation” manual).
The catalog space can be created either on the DBH user ID or on a DB user ID, see the section “Database files and job variables on foreign user IDs”.
The catalog space can be up to 4 TB in size on pubsets with “large files”. Otherwise it can be up to 64 GB in size.
The catalog space is where the database's metadata is stored. SESAM/SQL initializes the empty metadata by entering the information specified in connection with CREATE CATALOG, together with other administrative information (e.g. the views of the information schema). From the point of view of the operating system, the catalog space is an ordinary BS2000 file. The database also always has to be initialized with CREATE CATALOG. The catalog space's BS2000 file name is
:catid:user_id.catalog.CATALOG
The BS2000 user ID for the database
All the files in a SESAM/SQL database with the exception of logging and error files have to be cataloged on the same BS2000 user ID. SESAM/SQL enters the user ID for the database in the DBH's SQL database catalog (see the “Database Operation” manual).
The following is important in connection with the databases that are not located on the DBH user ID:
SESAM backup copies on magnetic tape cartridges can only be created with HSMS. For this to be possible, the DBH ID must be defined as a co-owner of the DB files in the DB user ID. Repair or reset from a SESAM backup copy on tape is also only possible using HSMS.
SESAM/SQL can only execute the SQL statement CREATE SPACE if the preparations have been made for creating the catalog space, see the section “Database files and job variables on foreign user IDs”.
If logging files (CAT-LOG files, DA-LOG files) are to be stored on the DB user ID, preparations must have been made for creating the logging files, see the section “Database files and job variables on foreign user IDs”.
If it is not possible to create logging files on the DB user ID, SESAM/SQL will create them on the DBH user ID.During repairs, SESAM/SQL first searches for the log files on the DB user ID and then on the DBH user ID.