Preface

This manual describes the system definitions for HiRDB Version 9, a nonstop database server program product. For details about prerequisite information that is not described in this manual, see the manual HiRDB Version 9 Description (3020-6-450).

Intended readers

This manual is intended for users who will be constructing or operating HiRDB Version 9 ("HiRDB") relational database systems.

Readers of this manual must have the following:

This manual is based on the following manuals, which we recommend that you read before reading this one:

Conventions: Diagrams

This manual uses the following conventions in diagrams:

[Figure]

Conventions: Fonts and symbols

The following table explains the text formatting conventions used in this manual:

Text formattingConvention
BoldBold characters indicate text in a window, other than the window title. Such text includes menus, menu options, buttons, radio box options, or explanatory labels. For example:
  • From the File menu, choose Open.
  • Click the Cancel button.
  • In the Enter name entry box, type your name.
ItalicItalic characters indicate a placeholder for some actual text to be provided by the user or system. For example:
  • Write the command as follows:
    copy source-file target-file
  • The following message appears:
    A file was not found. (file = file-name)
Italic characters are also used for emphasis. For example:
  • Do not delete the configuration file.
MonospaceMonospace characters indicate text that the user enters without change, or text (such as messages) output by the system. For example:
  • At the prompt, enter dir.
  • Use the send command to send mail.
  • The following message is displayed:
    The password is incorrect.

The following table explains the symbols used in this manual:

SymbolConvention
|In syntax explanations, a vertical bar separates multiple items, and has the meaning of OR. For example:
A|B|C means A, or B, or C.
{ }In syntax explanations, curly brackets indicate that only one of the enclosed items is to be selected. For example:
{A|B|C} means only one of A, or B, or C.
[ ]In syntax explanations, square brackets indicate that the enclosed item or items are optional. For example:
[A] means that you can specify A or nothing.
[B|C] means that you can specify B, or C, or nothing.
...In coding, an ellipsis (...) indicates that one or more lines of coding have been omitted.
In syntax explanations, an ellipsis indicates that the immediately preceding item can be repeated as many times as necessary. For example:
A, B, B, ... means that, after you specify A, B, you can specify B as many times as necessary.
()Parentheses indicate the range of items to which the vertical bar (|) or ellipsis (...) is applicable.
{{ }}A double pair of curly brackets encloses multiple items, all of which you can specify multiple times as a unit.
Example: {{pdbuffer -a option-name}}
This example indicates that you can specify the above multiple times as follows:
pdbuffer -a option-name
pdbuffer -a option-name
~A swung dash precedes the attributes of a user-specified value.
<< >>A double pair of angle brackets encloses the default value assumed by the system when the specification is omitted.
< >A single pair of angle brackets encloses the syntax element notation for a user-specified value.
(( ))A double pair of parentheses encloses the permitted range of values that can be specified.
[Figure][Figure]Round up the result to the next integer.
Example: The result of [Figure]34 [Figure] 3[Figure] will be 12.
[Figure][Figure]Discard digits following the decimal point.
Example: The result of [Figure]34 [Figure] 3[Figure] will be 11.
MAXSelect the largest value as the result.
Example: The result of MAX(3 [Figure] 6, 4 + 7) will be18.
MINSelect the smallest value as the result.
Example: The result of MIN(3 [Figure] 6, 4 + 7) will be 11.

Syntax element conventions

The following table explains the syntactical element symbols used in this manual:

Syntactical element symbolMeaning
<alphabetics>The alphabetic characters (A to Z and a to z) and the underscore (_)
<alphabetics and special characters>The alphabetic characters (A to Z and a to z) and the special characters #, @, and \
<alphanumerics>Alphabetic characters and the numeric digits (0 to 9)
<alphanumerics and special characters>Alphabetic characters, special characters, and numeric digits
<unsigned integer>Numeric value
<unsigned decimal>#1Numeric value (0 to 9), period (.), numeric value (0 to 9)
<hexadecimal>Numeric digits and A to F (or a to f)
<identifier>#2Alphanumeric character string beginning with an alphabetic character
<symbolic name>Alphanumeric character string beginning with an alphabetic character or a special character
<character string>Any string of characters
<path name>#3Forward slash (/), alphanumeric characters, period (.), hash mark (#), and at sign (@)
<host-name>#4Character string consisting of alphabetic characters (A to Z, a to z), numeric characters, period (.), hyphen (-), underscore (_), and at mark (@).
Note: All alphabetic characters must be single-byte characters. Alphabetic characters are case sensitive.
#1
If all the numeric characters preceding the period are zeros (0), the zeros preceding the period can be omitted. Similarly, if all the numeric characters following the period are zeros (0), the zeros following the period can be omitted.
Example 1: 0.008[Figure] .008
Example 2: 15.000[Figure] 15
#2
Specifying an RDAREA name:
[Figure]RDAREA names can include one or more alphanumeric and special characters, underscores (_), hyphens (-), and spaces. However, the first character must be an alphabetic or special character.
[Figure]When an RDAREA name includes a space, the entire name must be enclosed in double quotation marks (").
#3
Path names depend on the OS being used.
#4
Use one of the following formats to specify a host name:
[Figure]host-name
[Figure]IP-address (xxx.xxx.xxx.xxx format)
[Figure]fully-qualified-domain-name (FQDN)
However, do not use different formats to specify the same host. HiRDB regards host names specified in different formats as different hosts.
You can also specify loop-back addresses.
A host name must be registered before it can be specified in a system definition. For details, see Registering host names in the HiRDB Version 9 Installation and Design Guide.

Conventions: Version numbers

The version numbers of Hitachi program products are usually written as two sets of two digits each, separated by a hyphen. For example:

The version number might be shown on the spine of a manual as Ver. 2.00, but the same version number would be written in the program as 02-00.

Important notes on this manual

The following facilities are explained, but they are not supported:

The following products and option program products are explained, but they are not supported: