1.3 Coding format of HiRDB system definitions
(1) Operand specification format
HiRDB system definition operands are specified in the following three formats:
- set format
- set is used to set a value in an operand; for example,
- set pd_max_users=15
- Command format
- Options and command arguments are set in an operand; for example,
pdlogadfg -d sys -g loggrp01 ONL
- pdlogadfg
- Command name
- -d sys -g loggrp01
- Options (an option is a character string that begins with a hyphen)
- Flag arguments are not specified in Format 1; flag arguments are specified in Format 2:
- Format 1: option-flag
- Format 2: option-flag flag-argument
option-flag: An alphabetic character that follows the hyphen.
Values are case sensitive.
flag-argument: Operation target for the option flag.
- ONL
- A command argument (argument that begins with anything other than a hyphen).
- putenv format
- putenv is used to set in an operand an environment variable and value for the environment variable; for example,
- putenv SHMMAX 16
(2) Comments
A comment can be entered for any operand. A comment must begin with the number sign (#). When the number sign is encountered, the remainder of the line is assumed to be a comment. When the number sign is entered at the beginning of a line, the entire line is handled as a comment line.
- Example
- set pd_max_users=15 # maximum number of concurrent connections
- pdlogadfg -d sys -g loggrp01 ONL
- # Defines a file group for system log files
(3) Line continuation
The maximum number of characters per line of definition is 80. If a definition requires more than 80 characters, additional lines can be used by specifying the backslash (\) as a continuation symbol before the end of each line that is to be continued.
- Example
- pdbuffer -a buffer ABC -n 160 -r rdareaA,rdareaB,..... \
- rdareaZ
A line in which a comment is specified cannot be continued. When the number sign (#) is encountered, the entire remainder of the line is handled as a comment line, so even if the backslash is specified subsequently on the line, it will be regarded as part of the comment rather than as the line continuation symbol.
(4) Duplicate operand specification
When multiple operands are specified in a single definition statement (single file), HiRDB uses the following rules for processing these operands:
- When the operands are in the set or putenv format, the value of the operand that was specified last takes precedence.
- When the operands are in the command format, priority depends on the operands. Refer to the explanations of the individual operands.
(5) Notes
- Do not use a file extension such as .txt for a HiRDB system definition file.
- When specifying an absolute pathname, be sure to include the drive name.
Example: C:\hirdb_s\spool\tmp
- Enclose in double quotation marks (" ") any path name specified in the HiRDB system definition file that includes a space.
Example:
pdinit -d "C:\Program Files\hitachi\hirdb_s\conf\mkinit"