4.2.2 Creating HiRDB system definitions (HiRDB/Parallel Server)

Organization of this subsection
(1) Creating system common definitions (HiRDB/Parallel Server)
(2) Creating unit control information definitions (HiRDB/Single Server)
(3) Creating single server definitions
(4) Creating front-end server definitions
(5) Creating dictionary server definitions
(6) Creating back-end server definitions
(7) UAP environment definition creation (optional)
(8) Creating an SQL reserved word definition (optional)
(9) Configuring the HiRDB system definition files

(1) Creating system common definitions (HiRDB/Parallel Server)

For system common definitions, define the HiRDB configuration and common information. After you create the system common definitions, store them in the following file:

Create the same system common definitions for each server machine.

The system common definitions include the definitions of unit configuration, server configuration, and global buffer.

Note that HiRDB commands and utilities operate in conformance with the definitions in this definitions file. Consequently, grant the read privilege (r) for this definitions file to users who execute HiRDB commands or utilities (users on the OS).

(2) Creating unit control information definitions (HiRDB/Single Server)

For unit control information definitions, define the unit's execution environment. Store the unit control information definitions created in the following file:

Create the unit control information definitions for each server machine.

The unit control information definitions include the definitions of status files for units.

Note that HiRDB commands and utilities operate in conformance with the definitions in this definitions file. Consequently, grant the read privilege (r) for this definitions file to users who execute HiRDB commands or utilities (users on the OS).

(3) Creating single server definitions

For single server definitions, define the default values of the server-definition operands, which are explained in (4)-(6), below. Create the server common definitions for each server as required and store them in the following file:

The server common definitions are useful in the following cases:

The information specified in the server common definitions takes effect on all the servers defined in the corresponding server machine. If there are many definitions that are common to multiple servers, you should specify the common information in the server common definitions and the information unique to individual servers in the corresponding server definitions.

Also, since HiRDB commands and utilities operate in conformance with the definitions in this definitions file, grant the read privilege (r) for this definitions file to users who execute HiRDB commands or utilities (users on the OS).

(4) Creating front-end server definitions

For front-end server definitions, define the front-end server's execution environment. Save the front-end server definitions created in the following file:

Create the front-end server definitions in the server machine where the front-end server is defined. The following shows an example of items that can be specified in the front-end server definitions:

#: Use the server name that is specified in the -s option of the pdstart operand in the system common definitions. For example, if your specification is pdstart -s f001, then store the front-end server definitions in the following file:
  • %PDDIR%\conf\f001 file

Note that HiRDB commands and utilities operate in conformance with the definitions in this definitions file. Consequently, grant the read privilege (r) for this definitions file to users who execute HiRDB commands or utilities (users on the OS).

(5) Creating dictionary server definitions

For dictionary server definitions, define the dictionary server's execution environment. Save the dictionary server definitions created in the following file:

Create the dictionary server definitions in the dictionary server machine where the dictionary server is defined. The following shows an example of items that can be specified in the dictionary server definitions:

#: Use the server name that is specified in the -s option of the pdstart operand in the system common definitions. For example, if your specification is pdstart -s dic, then store the dictionary server definitions in the following file:
  • %PDDIR%\conf\dic file

Note that HiRDB commands and utilities operate in conformance with the definitions in this definitions file. Consequently, grant the read privilege (r) for this definitions file to users who execute HiRDB commands or utilities (users on the OS).

(6) Creating back-end server definitions

For back-end server definitions, define the back-end server's execution environment. Save the back-end server definitions created in the following file:

Create the back-end server definitions in the server machine where the back-end server is defined. The following shows an example of items that can be specified in the back-end server definitions:

#: Use the server name that is specified in the -s option of the pdstart operand in the system common definitions. For example, if your specification is pdstart -s b001, then store the back-end server definitions in the following file:
  • %PDDIR%\conf\b001 file

Note that HiRDB commands and utilities operate in conformance with the definitions in this definitions file. Consequently, grant the read privilege (r) for this definitions file to users who execute HiRDB commands or utilities (users on the OS).

(7) UAP environment definition creation (optional)

Define UAP execution environments. Create UAP environment definitions as needed, and store them in the following file:

A UAP environment definition is created at the unit with the front-end server. If there are multiple front-end servers, the UAP environment definition can be defined at any of them, as appropriate.

The HiRDB administrator must grant to the users who will use a UAP environment definition the read privilege (r) and the execute privilege (x) for the %PDDIR%\conf\pduapenv directory. Read (r) privilege must also be granted for the UAP environment definition file.

Also, since HiRDB commands and utilities operate in conformance with the definitions in this definitions file, grant the read privilege (r) for this definitions file to users who execute HiRDB commands or utilities (users on the OS).

The following are examples of the items that can be specified in a UAP environment definition:

#: The file name must begin with an alphabetic character and must not exceed 8 characters in length. File names are not case sensitive. For example, the characters A and a are treated as being identical. The file names ABC and abc are the same file name.

(8) Creating an SQL reserved word definition (optional)

To use the SQL reserved word deletion facility, you must define the reserved words to be deleted for each UAP. You create an SQL reserved word definition as needed and store it in the following file:

Create the SQL reserved word definition on the unit where the front-end server is located. In the event of multiple front-end servers, define the SQL reserved word definition on the front-end server to which the UAP environment definition is to be applied.

The HiRDB administrator must grant to a user who uses the SQL reserved word definition the read (r) and execution (x) privileges for the %PDDIR%\conf\pdrsvwd directory and the read privilege (r) for the SQL reserved word deletion file.

Also, since HiRDB commands and utilities operate in conformance with the definitions in this definitions file, grant the read privilege (r) for this definitions file to users who execute HiRDB commands or utilities (users on the OS).

#: The file name must be expressed as no more than eight alphanumeric characters beginning with an alphabetic character. The file name is not case-sensitive. For example, A is not distinguished from a, so the file names ABC and abc are regarded as the same.

(9) Configuring the HiRDB system definition files

The following figure shows an example of a configuration of HiRDB system definition files.

Figure 4-3 Configuration of HiRDB system definition files: HiRDB/Parallel Server

[Figure]