4.2.1 HiRDB system construction procedure when system generator is used

The system generator constructs a HiRDB system automatically on the basis of information entered in response to queries that are displayed on the system generator's menu screens.

To set up the environment for a HiRDB/Parallel Server using the system generator:

  1. On the HiRDB/Parallel Server License selection menu screen, specify your HiRDB model.
  2. On the Master menu screen, specify the minimum settings required for system construction, such as HiRDB directory and port number.
  3. On the Detail option setting menu screen, specify the detailed functions related to HiRDB system definitions such as buffer sizes.
  4. On the Log option setting menu screen, set up an environment for the system log files.
  5. On the HiRDB unit initialization menu screen, set up and initialize units.
  6. On the Create new rdarea menu screen, add user RDAREAs and user LOB RDAREAs.
  7. On the Plugin Setup menu screen, set up an environment for plug-ins. Do this step only if you have installed a plug-in.

The following explains each menu of the system generator:

Organization of this subsection
(1) HiRDB/Parallel Server License selection menu
(2) Master menu
(3) Detail option setting menu
(4) Log option setting menu
(5) HiRDB unit initialization
(6) Create new rdarea menu
(7) Plug-in Setup menu

(1) HiRDB/Parallel Server License selection menu

[Figure]

Explanation:
On this screen, there is no query regarding the HiRDB environment setup. Specify the HiRDB's license type only.

(2) Master menu

[Figure]

Explanation:
  1. These inquiries relate to the HiRDB system definitions.
  2. This inquiry is for specifying the unit on which the dictionary server is to be created.
  3. This inquiry is for specifying the number of back-end servers to be created per unit.
  4. These inquiries relate to system files. Whether the HiRDB file system area for system files is to be created in a character special file or in a regular file is specified here. A character special file is usually specified, but a regular file can be used instead. If creation of a highly reliable system is a top priority, a character special file should be specified.
  5. This inquiry relates to RDAREAs. Whether the HiRDB file system area for RDAREAs is to be created in a character special file or in a regular file is specified here. A character special file is usually specified, but a regular file can be used instead. If creation of a highly reliable system is a top priority, a character special file should be specified.

(3) Detail option setting menu

[Figure]

[Figure]

Explanation:
This menu contains inquiries related to HiRDB system definitions.
When the system generator is executed, the parameters for HiRDB system definitions (operand values) are created under $PDDIR/conf. They should be referred to when HiRDB system definitions are modified.

(4) Log option setting menu

[Figure]

Explanation:
This menu lets you set up an environment for the system log files.

(5) HiRDB unit initialization

[Figure]

Explanation:
  1. This inquiry is for specifying a unit that is to be initialized.
  2. These inquiries relate to system files. HiRDB use a character special file or a regular file, whichever type is specified here, as explained as follows:
    Initializes the specified type of file (character special file or regular file) as a HiRDB file system area for system files.
    Creates system files in this HiRDB file system area.
  3. These inquiries relate to RDAREAs. HiRDB uses a character special file or a regular file, whichever type is specified here, as explained as follows:
    Initializes the specified type of file (character special file or regular file) as a HiRDB file system area for RDAREAs.
    If the dictionary server is to be created on this unit, HiRDB creates system RDAREAs in this HiRDB file system area.
(a) Number of times HiRDB unit initialization is executed

HiRDB unit initialization is executed as many times as there are units.

(b) Notes on specifying information in response to queries about system files
  1. Normally, character special files are specified, but regular files are also permissible. If you desire to create a high-reliability system, you should use character special files.
  2. Character special files and regular files should not be located on the same hard disk.
  3. If only one character special file or regular file is provided, system reliability is compromised because it will not be possible to collect dual system log files. Dual system log files can be used only when two or more files are provided; three files are better than two files in terms of system reliability. For details about dual system log files, see 10.3.1 Designing system log files.
  4. The configuration of the system files to be created depends on the number of provided character special files or regular files.
  5. The contents of the system files that are created by the system generator are shown in Table 4-3.

    Table 4-3 Contents of system files created by the system generator (HiRDB/Parallel Server)

    System file typeContents of each file
    Unit status file200 kilobytes
    Server status fileFront-end server260 kilobytes
    Back-end server or dictionary server3480 kilobytes
    Synchronization point dump fileFront-end server120 + (40 [Figure] maximum-number-of-users) kilobytes
    Back-end server or dictionary server380 + (80 [Figure] maximum-number-of-users) kilobytes
    System log fileFront-end server1 megabyte
    Dictionary server2 megabytes
    Back-end serverThis is the size (in megabytes) specified on the Log Options Menu screen, 3: Size of log files.
    If omitted, this is [Figure] (database-update-size + 1) [Figure] 1.5 [Figure] megabytes. The database update size is the size specified on the Main Menu screen, 5: Database update size per day.
Three character special files provided
If three files are specified, HiRDB creates system files in the configuration shown in Figure 4-4.

Figure 4-4 Configuration of system files created by HiRDB with three files specified

[Figure]
Explanation:
This is the structure when system log files and synchronization point dump files are duplexed:
  • Six generations are created for each system log file.
    The size of one system log file is equivalent to the amount of information collected for one day. This means that three days of system log files can be retained.
  • Three generations are created for each synchronization point dump file.
  • Three generations are created for each status file.
Two character special files provided
If two files are specified, HiRDB creates system files in the configuration shown in Figure 4-5.

Figure 4-5 Configuration of system files created by HiRDB with two files specified

[Figure]
Explanation:
This is the structure when system log files and synchronization point dump files are duplexed:
  • Six generations are created for each system log file.
    The size of one system log file is equivalent to the amount of information collected for one day. This means that three days of system log files can be retained.
  • Three generations are created for each synchronization point dump file.
  • Two generations are created for each status file.
One character special file provided
If one file is specified, HiRDB creates system files in the configuration shown in Figure 4-6.

Figure 4-6 Configuration of system files created by HiRDB with one file specified

[Figure]
Explanation:
Because there is only one HiRDB file system area, the system log files and synchronization point dump files are not duplexed:
  • Six generations are created for each system log file.
    The size of one system log file is equivalent to the amount of information collected for one day. This means that three days of system log files can be retained.
  • Three generations are created for each synchronization point dump file.
  • Two generations are created for each status file.
(c) Notes about specifying information in response to queries about RDAREAs

When the system generator is executed, the parameters for RDAREA area creation (operands of the database initialization utility) are created under $PDDIR/conf.

(6) Create new rdarea menu

[Figure]

Explanation:
Specify information about an RDAREA that is to be added. You can add the following types of RDAREAs on this screen:
  • User RDAREA
  • User LOB RDAREA
  • RDAREA for lists
When the system generator is executed, the parameters for RDAREA creation (database initialization utility (pdinit) operands) are created under $PDDIR/conf.
(a) Number of times Create new rdarea menu is to be executed

The Create new rdarea menu is executed as many times as there are RDAREAs to be added.

(b) Notes on adding RDAREAs to the unit on which the dictionary server has been created

An RDAREA added from the Create new rdarea menu is stored in the HiRDB file system area for RDAREAs that was initialized from the HiRDB unit initialization menu. This means that on the unit where the dictionary server is created, both system RDAREAs and user RDAREAs (and user LOB RDAREAs) are stored in the same HiRDB file system area.

To store system RDAREAs and user RDAREAs (and user LOB RDAREAs) in separate HiRDB file system areas, the Create new rdarea menu cannot be used. Instead, the pdfmkfs command must be used to initialize another HiRDB file system area, and then the database structure modification utility (pdmod command) must be used to add RDAREAs.

(7) Plug-in Setup menu

This menu is used to install a plug-in after HiRDB system creation has been completed.

When this menu is used, the plug-in is registered as MASTER without creating a schema for the user executing pdgen.

[Figure]

Explanation:
This menu lets you specify information about a plug-in.
Note
If plug-in setup or registration fails, the cause of the failure must be investigated, then HiRDB must be terminated (if it is active) by specifying t on the Master menu. If HiRDB is already engaged in termination processing, also terminate the system generator. When the system generator has terminated, pdsetup -d can be used to cancel the registration in the OS, and then pdsetup can be re-executed.