This section contains detailed information about the format of the configuration file and the syntax of the parameters it can contain. It also contains detailed information about the valid values that you can specify for each parameter.
The configuration file has three types of sections in which you specify parameters:
These three sections of the rsm.cfg file form a hierarchy in which you can specify overriding values at each level. DB2 OLAP Server uses the settings in the RSM section unless overriding values are specified in a database or application section. When you create or start an application, DB2 OLAP Server looks for an application section in the configuration file for that application and overrides values in the RSM section with values found in that application section. When you create or start a database, DB2 OLAP Server looks for a database section in the configuration file for that database within the section for the current application and overrides values in the application section with values found in that database section.
The format for parameters in the configuration file is:
tag=value
where tag is the parameter name, and value is either a value for a variable (such as a database name, a number, or a string), or a value that you select from a list of possible values (for example, a list of isolation levels). Note that text values are not enclosed in quotes.
You can edit the configuration file using the editor of your choice.
The following series of examples shows basic and advanced sample configuration files for Windows NT, UNIX, and OS/390.
The sample in Figure 7 is a basic configuration table for Windows NT or UNIX. The system administrator set up the initial configuration file so that DB2 OLAP Server stores all table data in TSOLAP and all index data is TSOLAPX. Use a basic configuration file like this one when you want to place all your cubes in the same database and table space.
Figure 7. Basic configuration file on Windows NT or UNIX
/* Config file - system defaults */
[RSM] /* Required tag to start the main section */
RDB_NAME = OLAP /* Default to using the OLAP database */
RDB_USERID = ROLAP /* Specify the userid */
RDB_PASSWORD = xxxxxxxx /* Specify the password */
TABLESPACE = IN TSOLAP INDEX IN TSOLAPX /* All tables will go in this */
/* one tablespace */
|
Figure 8 shows a configuration file for Windows NT and UNIX in which selective parameters are overridden for OLAP applications and multidimensional databases. Use a configuration file like this one if you want to use more table spaces to accommodate a greater number of databases. In this example, payroll data is in TSPR, and the payroll table index is in TSPRX. Profit and loss data is in TSPL, and the profit and loss table index is in TSPLX. All other tables reside in TSOLAP, and their indexes reside in TSOLAPX. There are also separate fact tables and fact table indexes for each multidimensional database.
Figure 8. Advanced configuration file on Windows NT or UNIX
/* Config file - system defaults */
[RSM] /* Required tag to start the main section */
RDB_NAME = OLAP /* Default to using the OLAP database */
RDB_USERID = ROLAP /* Specify the userid */
RDB_PASSWORD = xxxxxxxx /* Specify the password */
TABLESPACE = IN TSOLAP INDEX IN TSOLAPX /* Tables go here unless */
/* overridden below */
/* Application - Accounts */
[ACCOUNTS]
RDB_NAME = ACCTS /* Application uses its own database */
/* Application - Accounts : Database - Payroll */
<Payroll>
TABLESPACE = IN TSPR INDEX IN TSPRX /* Non-fact tables have their */
/* own tablespaces */
FACTS = IN TSPRF INDEX IN TSPRFX /* Fact table has its own */
/* tablespaces */
/* Application - Accounts : Database - Profit and Loss */
<PandL>
TABLESPACE = IN TSPL INDEX IN TSPLX /* Non-fact tables have their*/
/* own tablespaces */
FACTS = IN TSPLF INDEX IN TSPLFX /* Fact table has its own */
/* tablespaces */
|
To enter a comment in the configuration file, follow these rules:
For example:
/*This is a valid comment.*/
/*This is valid.*/ TAG=VALUE /*And this is valid.*/ /*This is not valid*/
A configuration file begins with this header tag:
[RSM]
A configuration file must also contain this parameter:
RDB_NAME = databasename
where databasename is the name of the relational database where you want DB2 OLAP Server to store your OLAP applications and databases.
All of the parameters described in Configuration File Parameters are valid in the RSM section.
You can create an application section that contains parameters that override the parameters set in the RSM section.
An application section begins with a tag that indicates the name of the application. For example, if the application name is SAMPLE, you might include an application section for that application by using a [SAMPLE] tag, as shown in Figure 7.
An application section must start after the last parameter of the RSM section.
The following parameters are valid for the application section:
See Configuration File Parameters for a description of each parameter.
You can create a database section that contains parameters that override the parameters set in the application section.
A database section starts with a <database> tag. For example, if an application named SAMPLE includes a database named BASIC, you would start a database section for that database with <BASIC>.
A database section must start after the last parameter of the corresponding application section.
Only the TABLESPACE, FACTS, PARTITIONING, FINDEX, and KINDEX parameters are valid in the database section. These parameters are described in Configuration File Parameters.