4.2.1 Creating HiRDB system definitions (HiRDB/Single Server)

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

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

For system common definitions, define the HiRDB configuration and common information. Store the system common definitions created in the following file:

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:

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 single server's execution environment. Store the created single server definitions in the following file:

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).

The following shows an example of items that can be specified in the single 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 sds1, then store the single server definitions in the following file:
  • %PDDIR%\conf\sds1 file

(4) UAP environment definition creation (optional)

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

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.

(5) 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:

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.

(6) Configuring the HiRDB system definition files

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

Figure 4-2 Configuration of HiRDB system definition files: HiRDB/Single Server

[Figure]