Scalable Database Server, HiRDB Version 8 System Definition

[Contents][Index][Back][Next]

1.2.2 HiRDB system definition creation procedure

The HiRDB administrator uses one of the following tools to create HiRDB system definitions:

The created HiRDB system definitions should be stored in the files listed in Table 1-5. These files are referred to collectively as HiRDB system definition files.

Table 1-5 Storage files for HiRDB system definitions (HiRDB/Parallel Server)

Definition type Storage file name
System common definition $PDDIR/conf/pdsys
Unit control information definition $PDDIR/conf/pdutsys
Server common definition $PDDIR/conf/pdsvrc
Front-end server definition $PDDIR/conf/server-name1, 2
Dictionary server definition $PDDIR/conf/server-name1, 3
Back-end server definition $PDDIR/conf/server-name1, 4
UAP environment definition $PDDIR/conf/pduapenv/arbitrary-name5
SQL reserved word definition $PDDIR/conf/pdrsvwd/arbitrary-name5
foreign server information definition $PDDIR/conf/foreign-server-name
Hub optimization information definition $PDDIR/conf/arbitrary-name

1 A server name specified by the -s option of the pdstart operand of the system common definition is specified here.

2 When the system generator is used to create the HiRDB system definitions, the file names are f001-fxxx, where xxx is a serial number in the range 1-999.

3 When the system generator is used to create the HiRDB system definitions, the file name is dic.

4 When the system generator is used to create the HiRDB system definitions, the file names are b001-bxxx, where xxx is a serial number in the range 1-999.

5
  • A file name must be an alphanumeric character string (a maximum of 8 characters) that begins with a letter.
  • Assign to the users who will use the UAP environment definition or SQL reserved word definition the reading privilege (r) and execution privilege (x) for the directory in which each file is stored. Also assign the reading privilege (r) for the file.
    Note
    Set and maintain the HiRDB system definition file permissions in such a manner that only the file owner (HiRDB administrator) has read and write permissions.
Organization of this subsection
(1) Using the simple setup tool
(2) Using the system generator (pdgen command)
(3) Using an OS text editor

(1) Using the simple setup tool

When the simple setup tool is employed to create HiRDB system definitions, the simple setup tool itself sets up the HiRDB environment. The HiRDB system definitions are created automatically on the basis of information specified with the simple setup tool and are stored in the files listed in Table 1-5. If necessary, the HiRDB administrator can use the simple setup tool to modify the definition contents (operand specification values).

Note that the following definitions cannot be created using the simple setup tool:

(2) Using the system generator (pdgen command)

When the system generator is employed to create HiRDB system definitions, the system generator itself sets up the HiRDB environment. The HiRDB system definitions are created automatically on the basis of information specified with the system generator and are stored in the files listed in Table 1-5. If necessary, the HiRDB administrator can use the OS text editor to modify the definition contents (operand specification values). For details about the operands created by the pdgen command, see G. Operands Created by the pdgen Command.

Note that the following definitions cannot be created using the system generator:

(3) Using an OS text editor

When an OS text editor is employed to create HiRDB system definitions, commands are used to set up the HiRDB environment. HiRDB system definition operands are specified as appropriate to the HiRDB execution environment.

Once the HiRDB system definitions have been created, use the pdconfchk command to check the integrity of the HiRDB system definition operands; see F. Operands Checked by the pdconfchk Command for the operands that are checked.