This type of configuration file groups the configuration parameters for several components into a single file, e.g. all the DBHs, SESDCNs and DBCONs for a configuration. The appropriate framework must have been put in place when SESAM/SQL was installed (see the “Database Operation” manual).
The parameters for each component are grouped into blocks in the file. Each parameter block is introduced by a one-line entry CONFIGURATION-LINK=component. component identifies the component to which the parameter block applies. You assign the file to the component for which the file contains parameters with the command CONNECT-SESAM-CONFIGURATION (see the “Database Operation” manual).
The rules applying to configuration files for individual SESAM/SQL components such as the utility monitor or SESDCN also apply to the use of the different parameters in the global configuration file.
The particularities relating to the entry of start parameters for SESDCN, DBCON and the utility monitor are described in the section "The configuration file for DBH start parameters ".
Example of a global configuration file
//REMARK LOAD OPTIONS FOR THE DBH ********************************* CONFIGURATION-LINK=SESDBB1 //SET-DBH-OPTIONS- // DBH-IDENTIFICATION=*PARAMETERS(- // CONFIGURATION-NAME=Z- // ,DBH-NAME=X- // )- // ,ADMINISTRATION=*PARAMETERS(- // ACCOUNTING=*PARAMETERS(- . . . //REMARK K_2_DBH_NEW_1 ******************************************** //ADD-SQL-DATABASE-CATALOG-LIST- // ENTRY-1=*CATALOG(- // CATALOG-NAME=AUFTRAGKUNDEN- // ,USER-ID=KENN1- // )- . . . //REMARK LOAD OPTIONS FOR USER PROGRAMS *********************** CONFIGURATION-LINK=SESDBB2 REMARK CONFIGURATION DATA **************************************** CNF=Z NAM=X SQLOPT-PREFERRED-JOIN-METHOD=SORT-MERGE PUF=64000 TOTAL-USERS=00128 REMARK A DB PROCESS IS ASSIGNED EXACTLY ONE UTM PROCESS ****** UTMVG=JA
Start parameters for SESDCN
Here you define the distribution rules and access paths for the current SESDCN session.
The individual SESDCN start parameters' syntax and meanings are described in section “SESDCN control statements and options”. Information on the entry in the configuration file and a detailed description of SESDCN start parameters are provided in the “Database Operation” manual.
Alongside a global configuration file, you can also use a specific configuration file as the start parameter input file for SESDCN. This type of configuration file then contains only SESDCN control statements and options.
Start parameters for DBCON and the utility monitor
You can assign start parameters for the connection module (DBCON) of an ESQL or CALL DML application, or for the utility monitor via a global configuration file or via a specific configuration file. This type of configuration file can contain parameters for the utility monitor, for DBCON or both.
Attention should be paid to the following when entering parameters in configuration files of this type:
Only one parameter must be entered per line or record.
The parameter must begin in column 1 and must not contain blanks.
Each parameter must only occur once in the file.
Parameters can be entered in any order.
A DBCON or the utility monitor only ever evaluates its own specific parameters. To make it possible to differentiate, utility monitor parameters begin with the prefix “SEE”; DBCON start parameters have no prefix. In addition to the parameters flagged with "SEE", the utility monitor also reads the DBH name and the configuration name (connection module parameter NAM or CNF).
DBCON parameters
The DBH name and the configuration name are important DBCON parameters (connection module parameters). These two parameters assign the application to which the connection module is linked to a DBH and to a configuration (see section “Connection module parameters”).
Only applications that work with an independent DBH, not linked-in applications, have a configuration file containing connection module parameters. With linked-in applications, the key parameters (the DBH name and the configuration name) are contained in the linked-in DBH's configuration file as DBH options.
In TIAM and DCAM operations, users must assign the connection module parameters via the configuration file before starting the application, unless they wish to use the preset default parameters. CALL DML application users can also pass certain connection module parameters via special CALL DML calls (see the “CALL-DM Applications” manual). However, the configuration file offers an advantage in terms of flexibility because it allows the application program to be assigned to a different DBH or configuration if necessary, without needing to change the source code or re-link the application. Configuration parameters for a number of components can be combined in a single global configuration file.
The same configuration file can be used for TIAM applications, UTM applications and DCAM applications. If the configuration file for a TIAM application contains DCAM-specific or UTM-specific connection module parameters, these are ignored. The same applies to DCAM or UTM applications
The SQL notes for TIAM and DCAM applications are listed with their respective syntax and meanings starting.
Utility monitor parameters
The utility monitor parameters (the so-called configuration data) control how the utility monitor executes.
The authorization key for working with the utility monitor or the authorization key for administration is a mandatory parameter and has to be specified by users via the CALL interface. There are also various optional parameters that can be specified.
If users do not specify a configuration file, they must supply the configuration data (or at least their authorization to use the utility monitor) when the monitor executes.
You should enter the DBH name and the configuration name (connection module parameter NAM or CNF) in the configuration file since these specifications are displayed in the CNF - CONFIGURATION screen even though they cannot be edited there. If you do not enter the DBH name, the configuration name and the CCS name (connection module parameter CCSN) in the configuration file, the utility monitor is started with the defaults for the DBH name and configuration name (see the “Database Operation” manual).
The utility monitor's most important configuration data is listed below. For a full description of the configuration data, see the “Utility Monitor” manual.
SEE-AUTHID=authorization
Authorization key for working with utility monitor.
This parameter is mandatory.
SEE-INST-LOGGING={ON | OFF}
Enables/disables logging in the statement file.
Default: OFF
SEE-EXECUTE={ON|OFF}
Causes/prevents the execution of logged statements.
Default: ON
SEE-ERROR={ON|OFF}
Specifies the reaction to DBH error messages output while the statement file is being processed (abort or continue).
Default: ON
SEE-COPY={ON|OFF}
Enables/disables the automatic backup of database objects.
Default: ON
SEE-ADMIN=password
Administration password or password for the SESADM administration program.This is a mandatory parameter for administration via the CALL DML interface.