4.1.1 Introduction to the system generator

If you enter information in response to queries that are displayed on the system generator's menu screens, the system generator constructs a HiRDB/Single Server's environment.

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

  1. On the HiRDB/Single 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 Create new rdarea menu screen, add user RDAREAs and user LOB RDAREAs.
  6. 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/Single Server License selection menu
(2) Master menu
(3) Detail option setting menu
(4) Log option setting menu
(5) Create new rdarea menu
(6) Plugin Setup menu

(1) HiRDB/Single 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. These inquiries relate to system files. HiRDB uses a character special file or a regular file, whichever type is specified here, explained as follows:
    HiRDB initializes the specified type of file (character special file or regular file) as a HiRDB file system area for system files.
    HiRDB 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, explained as follows:
    HiRDB initializes the specified type of file (character special file or regular file) as a HiRDB file system area for RDAREAs.
    HiRDB stores the RDAREAs that are created with the system generator in this HiRDB file system area.
(a) Notes about specifying information in response to queries about system files
  1. 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.
  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 9.3.1 Designing system log files.
  4. The configuration of the system files to be created depends on the number of character special files or regular files provided.
  5. The contents of the system files that are created by the system generator are shown in Table 4-1.

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

    System file typeContents of each individual file
    Unit status file80 kilobytes
    Server status file3480 kilobytes
    Synchronization point dump file104 + (4 [Figure] maximum-number-of-users) kilobytes
    System log fileThis 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-1.

Figure 4-1 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-2.

Figure 4-2 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-3.

Figure 4-3 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.
(b) Notes about specifying information in response to queries about RDAREAs
  1. A character special file area 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.
  2. When you execute the system generator, the parameters for RDAREA creation (operands of the database initialization utility [pdinit]) are created under $PDDIR/conf.

(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) 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 you execute the system generator, the parameters for RDAREA creation (operands of the database initialization utility [pdinit]) are created under $PDDIR/conf.
Note
To create a user RDAREA (or user LOB RDAREA or RDAREA for lists) in a different HiRDB file system area from the one used for system RDAREAs, do not use the Create new rdarea menu. Instead, use the pdfmkfs command to initialize another HiRDB file system area, and then use the database structure modification utility (pdmod) to add RDAREAs.

(6) Plugin 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 is used to specify information about a plug-in that is to be set up and registered after HiRDB system creation has been completed.
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 reexecuted.