(a) Executing the pdsetup command

The superuser executes the pdsetup command to register HiRDB into the OS. The pdsetup command copies the directories and files from the installation directory to the HiRDB directory. For a HiRDB parallel server configuration, execute the pdsetup command for each server machine.

To perform registration into the OS:

1. Execute the pdsetup command.
2. Check the termination status.
   If the termination status of the pdsetup command is not 0, an error may have occurred. See the message output to the syslog file, eliminate the cause of the error, and then re-register HiRDB into the OS.
   

For details about the pdsetup command, see the manual HiRDB Version 9 Command Reference.

Notes

• The pdsetup command is located in the bin directory under the HiRDB installation directory.
• If you execute the pdsetup command, the Inittab directory is automatically created in the conf directory under the HiRDB installation directory. This directory is used to back up the /etc/inittab file. If the /etc/inittab file is damaged during or after the execution of the pdsetup command, use this backup file to start the operating system.
• After you execute the pdsetup command, do not delete files or directories created under the HiRDB directory, and do not change owners or access permissions. Doing so can prevent HiRDB from starting.
• The pdsetup command copies or overwrites the installed HiRDB load modules to the specified HiRDB directory. To prevent loss of other program or user data, specify either of the following in the HiRDB directory:
  A directory created exclusively for HiRDB
  A HiRDB installation directory (for a HiRDB single server configuration, /opt/HiRDB_S; for a HiRDB parallel server configuration, /opt/HiRDB_P)
  

(b) Default operand behavior selected by the pdsetup command

The -v option of the pdsetup command can be used to choose the default behavior when operands are omitted. After you have executed the pdsetup command to register HiRDB in the OS, if you want to change the operand default behavior, execute the pdsetenv command. To check the mode being used to apply the default operand behavior, execute the command pdadmvr, or check message KFPS01826-I, which is output when HiRDB starts.

Rules

• In a system switchover configuration, the default behavior when operands are omitted must be the same in the primary and secondary systems.
• In a HiRDB parallel server configuration, the default behavior when operands are omitted must be the same for all units.

(c) Specifying the character encoding by using the pdsetup command

Specifying at the server

Use the -c option of the pdsetup command to specify the character encoding to be used in with HiRDB. The following table shows the character encodings that can be used with HiRDB.

Table 2-4 Character encoding supported by HiRDB

Character encoding	OS
	HP-UX	Solaris	AIX	Linux
Shift JIS Kanji Code	Default	Usable	Default	Usable
EUC Chinese Kanji Code	Usable	Usable	Usable	Usable
Chinese Character Code (GB18030)	Usable	Usable	Usable	Usable
Single-byte character encoding	Usable	Usable	Usable	Usable
EUC Japanese Kanji Code	Usable	Default	Usable	Default
Unicode (UTF-8)	Usable	Usable	Usable	Usable
Unicode (IVS-supported UTF-8)	Usable	Not usable	Usable	Usable

Default: Usable character encoding (the default character encoding when the pdsetup command -c option is omitted)

Usable: Usable character encoding

Not usable: Not a usable character encoding

Use the pdadmvr -c command to check which character encoding is in use.

Specifying at the client

On the client side, specify the character encoding with the LANG or PDCLTLANG operand in the client environment definition as appropriate to the server's character encoding. The client environment definition is referenced during UAP creation or execution. For the client environment variables supported based on the server's available character encoding, see the HiRDB Version 9 UAP Development Guide.

(d) Specifying the pdsetup command when using the POSIX library version

If you are using the POSIX library version, specify the -l option in the pdsetup command. You need the POSIX library version to use the following facilities:

• Java stored procedures and Java stored functions^#

For details about Java stored procedures and Java stored functions, see the HiRDB Version 9 UAP Development Guide.

The Linux version supports Java stored procedures and Java stored functions without requiring any special setup.

#: The following versions of HiRDB support Java stored procedures and Java stored functions:

• HP-UX version (32-bit mode POSIX library version) and HP-UX (IPF version)
• Solaris version (32-bit mode POSIX library version)
• AIX version (32-bit mode POSIX library version)
• Linux version (32-bit mode) and Linux version (EM64T)

To install option program products, use the pdopsetup command to register them in the OS.

When using a HiRDB parallel server configuration

Execute the pdopsetup command on each machine to make sure the option program product is registered in all units.

When using the system switchover facility

• When you register the option program product on the primary system, register the same product on the secondary system (execute the pdopsetup command on the secondary system also).
• If two or more HiRDB systems are registered to the OS on a single server machine, such as in a system switchover configuration, execute the pdopsetup command on each HiRDB system (or each unit in the case of a HiRDB parallel server configuration). For example, in a mutual system switchover configuration, if two HiRDB systems (primary and secondary) exist on one server machine, the pdopsetup command must be executed twice on the server machine (once on the primary HiRDB system and once on the secondary HiRDB system).

When using Real Time SAN Replication

If you register an option program product on the main site, register the same product on the remote site (execute the pdopsetup command on the remote site also).