• Even after a system switchover, you do not need to change the host name or unit identifier specified in an operation command or utility. The -x option of the pdunit operand specifies the host name, which is the host name of the primary system.
• Specify a unit identifier for as many units as possible, which will reduce the need to be concerned with host names.
• For a HiRDB single server configuration, we recommend that you omit host names to avoid problems that might occur during operation. Specify host names only when you are performing operations on a utility special unit.
• In some cases, the host name of the primary system might be displayed in the processing results of operation commands.

In some cases, the primary system's host name might be displayed in messages.

For details about how statistical information is collected after a system switchover, see 26.7.1(4)(b) Process for collecting statistical information after a system switchover.

(a) HiRDB single server configuration

When only the host name of the primary system is specified in the PDHOST operand, you must perform the procedure explained in this subsection. This procedure is not necessary in a configuration in which IP addresses are inherited or when the host names of the primary system and secondary system are both specified in the PDHOST operand of the client environment definition. For details, see 26.2.3 Handling of host names depending on whether IP addresses are inherited.

Because the host name of the HiRDB to be connected is specified in the PDHOST operand, after a system switchover the host name of the running system must be specified in the PDHOST operand. Therefore, after a system switchover, the HiRDB administrator must notify all client users that the host name of HiRDB has changed. Client users must change the host name specified in the PDHOST operand to this new host name, and then re-execute the UAPs. Note that UAPs cannot be executed until the host name specified in the PDHOST operand is changed. For details about the PDHOST operand, see the HiRDB Version 9 UAP Development Guide.

(b) HiRDB parallel server configuration

When only the host name of the primary system is specified in the operands listed below, you must perform the procedure explained in this subsection. This procedure is not necessary when the host names of the primary system and secondary system are both specified in the operands listed below, in a configuration in which IP addresses are inherited. For details, see 26.2.3 Handling of host names depending on whether IP addresses are inherited.

• PDHOST
• PDFESHOST (applicable when multiple front-end servers are being used)

Because the host name of the HiRDB to be connected is specified in one of these operands, after a system switchover the host name of the running system must be specified in the applicable operand (the host name of the system manager is specified in the PDHOST operand and the host name of a front-end server is specified in the PDFESHOST operand). Therefore, after a system switchover, the HiRDB administrator must notify all client users that the host name of HiRDB has changed. Client users must change the host name specified in the applicable operand to this new host name, and then re-execute the UAPs. Note that UAPs cannot be executed until the host name specified in the applicable operand is changed. For details about the PDHOST operand and the PDFESHOST operand, see the HiRDB Version 9 UAP Development Guide.

Remarks

• The host name specified in the PDHOST operand needs to be changed only when a system switchover occurs on the system manager unit.
• The host name specified in the PDFESHOST operand needs to be changed only when a system switchover occurs on a front-end server unit.
• There is no need to change the PDHOST or PDFESHOST operand specification when a system switchover occurs for a unit where no system manager or front-end server is defined.