Nonstop Database, HiRDB Version 9 System Definition

[Contents][Index][Back][Next]

2.2.44 Operands related to unit structure

236) pdunit -x host-name
-u unit-identifier
[-d "HiRDB-directory-name"]
[-c host-name]
[-p HiRDB-port-number]
[-s scheduler-process-port-number]
[-t transaction-server-process-port-number]
[-m message-log-server-process-port-number]
[-a unit-monitoring-process-port-number]
Remarks
You can change the -x and -c option values when HiRDB is restarted following a planned termination. For the other options, change their values after HiRDB is started normally.

HiRDB/Single Server
Defines the unit structure of a HiRDB/Single Server.
Specification guidelines
  • You can omit this operand for a HiRDB/Single Server.
    However, it cannot be omitted if a system switchover facility that does not inherit IP addresses is used.
  • When a system switchover facility is used, the definitions must be the same for the primary system and the secondary system.
  • For a mutual system switchover configuration, in which a multi-HiRDB configuration is used (two HiRDB/Single Servers coexisting in a single server machine), the same system definition cannot be used for both HiRDB/Single Servers.
  • Specify different names for the hosts specified in the -x and -c options of all pdunit operands that are specified.
-x host-name
~<host name>((1-32 characters))
Specifies the host name of the server machine that defines the HiRDB/Single Server.
This operand can be specified as an IP address or in FQDN format. A loopback address can also be specified. However, the same specification format must be used consistently within a server machine. For example, once a host is specified in host name format, a host must not be specified as an IP address on the same server machine.
For specification examples, see Settings for a DNS server to manage IP addresses in the HiRDB Version 9 Installation and Design Guide.
Caution about specifying in host name format
  • Specify the host name displayed when the hostname command is executed.
  • Host names are case sensitive.
  • You cannot specify an alias for a host name.
Relationship to other operands
The following table shows the relationships between the host names specified in the -x and -c options of the pdunit operand and in the pd_hostname operand:
System configuration condition pdunit operand pd_hostname operand specification
-x option specification -c option specification
Not using switchover facility
  • Specify host name#1
  • Omit pdunit operand
 Need not be specified
  • Omit pd_hostname operand
  • Specify standard host name#1
  • Specify same host name as in -x option#1
Specify loopback address #2, #4 Need not be specified
  • Omit pd_hostname operand
  • Specify loopback address
Using switchover facility Monitor mode (IP addresses inherited)#6 Specify relocatable IP address, host name with a relocatable IP address, or FQDN Need not be specified
  • Omit pd_hostname operand
  • Specify primary system's standard host name#1
  • Specify same host name as in -x option#1
Specify loopback address#2, #3, #4, #5 Need not be specified
  • Omit pd_hostname operand
  • Specify loopback address
IP addresses not inherited Specify primary system's host name#1 Specify secondary system's host name#1 Specify primary system's standard host name#1

Notes:
  • A host name specified here must be registered in the hosts file, DNS, or similar, and the name must be resolved.
  • If a host is specified in FQDN format, it must have been defined in FQDN format.
  • In HiRDB, localhost is normally treated as a host name, so when used as a loopback address, the name must be resolved.
  • When the pdunit operand is omitted, it is assumed that the standard host name has been specified with the -x option. In such a case, a standard host name must be applied following the rules described in Syntax element conventions in the Preface.
  • When the pdunit operand is omitted, the standard host name is assumed, so a standard host name must be registered in the hosts file, DNS, or similar, and the name must be resolved.

#1
The specification format can be a host name, IP address, or FQDN format.

#2
If a loopback address is specified, it is not necessary to register the host name in the hosts file, DNS, or similar.

#3
In this case, it is not necessary to set up cluster software IP address inheritance.

#4
In this case, HiRDB clients on other machines cannot connect to the HiRDB server. To connect to the HiRDB server, use the multi-connection address facility or the high-speed connection facility.

#5
When using the multi-connection address facility, specify in the -m option of the pdstart operand (the option that specifies the host name to which the HiRDB client connects) a host name with a relocatable IP address that can be inherited at switchover.

#6
Specify the virtual network name to be registered in the MSCS or MSFC resource (network name). For details about virtual network name registration, see the HiRDB Version 9 System Operation Guide.
-u unit-identifier
~<identifier>((4 characters))
Specifies a unit identifier. The unit identifier specified here is also specified in the pd_unit_id operand in the unit control information definition.
-d "HiRDB-directory-name"
~<path name of up to 200 characters><<value of environment variable PDDIR>>
Specifies the name of the HiRDB directory.
The HiRDB directory name is not case sensitive. C:\hirdb_x is treated as the same as C:\HIRDB_X.
When the pdunit operand is omitted, the installation directory is assumed.
-c host-name
~<host name>((1-32 characters))
Specifies the secondary system's host name in one of the formats listed below. You specify this option for system switchover in which IP addresses are not inherited.
Use this option to specify the secondary system's host name. This option can be specified as an IP address or in FQDN format. However, the same specification format must be used consistently within a server machine. For example, once a host is specified in host name format, a host must not be specified as an IP address on the same server machine.
Caution about specifying in host name format
  • Host names are case sensitive.
  • You cannot specify an alias for a host name.
-p HiRDB-port-number
~<unsigned integer>((5001-65535))
Do not specify this option for a HiRDB/Single Server.
-s scheduler-process-port-number
~<unsigned integer>((5001-65535))
Specifies the port number for the scheduler process.
Notes
  • Normally, this operand need not be specified.
  • When a single server machine has multiple units, as in a mutual switchover configuration, specify a different port number for each unit.
  • For details about how to specify a scheduler process port number and for notes about duplication of other port numbers, see the HiRDB Version 9 Installation and Design Guide.
Relationship to other operands
This operand is related to the following operands:
  • pd_service_port
  • pd_scd_port
-t transaction-server-process-port-number
~<unsigned integer>((5001-65535))
Specifies the port number for the transaction server process.
Notes
  • Normally, this operand need not be specified.
  • When a single server machine has multiple units, as in a mutual switchover configuration, specify a different port number for each unit.
  • For details about how to specify a transaction server process port number and for notes about duplication of other port numbers, see the HiRDB Version 9 Installation and Design Guide.
Relationship to other operands
This operand is related to the pd_trn_port operand.
-m message-log-server-process-port-number
~<unsigned integer>((5001-65535))
Specifies the port number of the message log server process.
Notes
  • Normally, this operand need not be specified.
  • When a single server machine has multiple units, as in a mutual switchover configuration, specify a different port number for each unit.
  • For details about how to specify a message log server process port number and for notes about duplication of other port numbers, see the HiRDB Version 9 Installation and Design Guide.
Relationship to other operands
This operand is related to the pd_mlg_port operand.

HiRDB/Parallel Server
Defines the unit structure of a HiRDB/Parallel Server.
Specification guidelines
  • Information on all units that comprise the HiRDB/Parallel Server must be defined with this operand. For example, if there are three units, three pdunit operands are required.
  • This operand cannot be omitted when a system switchover facility is used.
  • When a system switchover facility is used, the definitions must be the same for the primary system and the secondary system.
  • For a mutual system switchover configuration, in which a multi-HiRDB configuration is used (two units coexisting in a single host), the same definition cannot be used for the two separate units.
  • Specify different names for the hosts specified in the -x and -c options of all pdunit operands that are specified.
  • If the HiRDB/Parallel Server consists of a single unit, this operand can be omitted. In this case, the installation directory is assumed as the HiRDB directory.
-x host-name
~<host name>((1-32 characters))
Specifies the host name of the server machine that defines the server of the HiRDB/Parallel Server. This operand can be specified as an IP address or in FQDN format. However, the same specification format must be used consistently within a server machine. For example, once a host is specified in host name format, a host must not be specified as an IP address on the same server machine.
For specification examples, see Settings for a DNS server to manage IP addresses in the HiRDB Version 9 Installation and Design Guide.
Caution about specifying in host name format
  • Specify the host name displayed when the hostname command is executed.
  • Host names are case sensitive.
  • You cannot specify an alias for a host name.
Relationship to other operands
  • The following table shows the relationships between the host names specified in the -x and -c options of the pdunit operand and in the pd_hostname operand:
    System configuration condition pdunit operand pd_hostname operand specification
    -x option specification -c option specification
    Not using switchover facility Specify host name.#1 Does not need to be specified.
    • Omit pd_hostname operand.
    • Specify standard host name.#1
    Using switchover facility IP addresses inherited#3 Specify relocatable IP address, host name with a relocatable IP address, or an FQDN. Does not need to be specified. Specify primary system's standard host name.#1
    IP addresses not inherited Specify primary system's host name.#1 Specify secondary system's host name.#1, #2 Specify primary system's standard host name.#1

Note:
  • A host name specified here must be registered in the hosts file, DNS, or similar, and the name must be resolved.
  • If a host is specified in FQDN format, it must have been defined in FQDN format.

#1
The specification format can be a host name, IP address, or FQDN format.

#2
The same host name cannot be specified more than once in the -x and -c options of the pdunit operand. The following shows examples of valid and invalid specifications:
Valid examples
pdunit -x hostA ... -c hostAA
pdunit -x hostB ... -c hostBB
Invalid examples
pdunit -x hostA ... -c hostB
pdunit -x hostB ... -c hostA
For an example of a HiRDB system definition that uses system switchover and in which IP addresses are not inherited, see B.4 HiRDB/Parallel Server: when the standby system switchover facility is used.

#3
Specify the virtual network name to be registered in the MSCS or MSFC resource (network name). For details about virtual network name registration, see the HiRDB Version 9 System Operation Guide.
-u unit-identifier
~<identifier>((4 characters))
Specifies a unit identifier. The unit identifier specified here is also specified in the pd_unit_id operand in the unit control information definition of each unit.
-d "HiRDB-directory-name"
~<path name of up to 200 characters><<value of environment variable PDDIR>>
Specifies the name of the HiRDB directory for this unit.
The HiRDB directory name is not case sensitive. C:\hirdb_x is treated as the same as C:\HIRDB_X.
Notes
  • When using the standby-less system switchover (1:1) facility
    Specify the same HiRDB directory name in the normal and back-end server units.
  • When using the standby-less system switchover (effects distributed) facility
    Specify the same HiRDB directory name in all units belonging to the same HA group.
  • The environment variable PDDIR is set to the environment variable that is set in the unit that executed the pdstart -q command. If you omit the -d option for a system composed of multiple units, specify the same HiRDB directory name for all units.
-c host-name
~<host name>((1-32 characters))
Specifies the secondary system's host name in one of the formats listed below. You specify this option for system switchover in which IP addresses are not inherited.
Use this option to specify the secondary system's host name. This option can be specified as an IP address or in FQDN format. However, the same specification format must be used consistently within a server machine. For example, once a host is specified in host name format, a host must not be specified as an IP address on the same server machine.
This option cannot be specified for the units described below. If it is specified, HiRDB cannot start (message KFPS01896-E is output).
  • Unit to which the standby-less system switchover (1:1) facility is applied. (IP address inheriting does not occur.)
  • Unit to which the standby-less system switchover (effects distributed) facility is applied. (IP address inheriting does not occur.)
Caution about specifying in host name format
  • Host names are case sensitive.
  • You cannot specify an alias for a host name.
-p HiRDB-port-number
~<unsigned integer>((5001-65535))
Specifies the HiRDB port number for the unit. When this option is omitted, the value specified in the pd_name_port operand is assumed.
Notes
  • When a single server machine has multiple units, as in a mutual switchover configuration, specify a different port number for each unit.
  • When using the standby-less system switchover (1:1) facility, specify the same port number for the normal BES unit and the alternate BES unit.
  • When using the standby-less system switchover (effects distributed) facility, specify the same port number for all units belonging to the same HA group.
  • For details about how to specify a HiRDB port number and for notes about duplication of other port numbers, see the HiRDB Version 9 Installation and Design Guide.
Relationship to other operands
This operand is related to the pd_name_port operand.
-s scheduler-process-port-number
~<unsigned integer>((5001-65535))
When Y is specified in the pd_name_fixed_port_lookup operand, specifies the port number for the scheduler process for the unit.
Notes
  • When a single server machine has multiple units, as in a mutual switchover configuration, specify a different port number for each unit.
  • When using the standby-less system switchover (1:1) facility, specify the same port number for the normal BES unit and the alternate BES unit.
  • When using the standby-less system switchover (effects distributed) facility, specify the same port number for all units belonging to the same HA group.
  • For details about how to specify a scheduler process port name and for notes about duplication of other port numbers, see the HiRDB Version 9 Installation and Design Guide.
Relationship to other operands
  • Y must be specified in the pd_name_fixed_port_lookup operand.
  • This operand is related to the following operands:
    [Figure] pd_service_port
    [Figure] pd_scd_port
-t transaction-server-process-port-number
~<unsigned integer>((5001-65535))
When Y is specified in the pd_name_fixed_port_lookup operand, specifies the port number for the transaction server process for the unit.
Notes
  • When a single server machine has multiple units, as in a mutual switchover configuration, specify a different port number for each unit.
  • When using the standby-less system switchover (1:1) facility, specify the same port number for the normal BES unit and the alternate BES unit.
  • When using the standby-less system switchover (effects distributed) facility, specify the same port number for all units belonging to the same HA group.
  • For details about how to specify a transaction server process port number and for notes about duplication of other port numbers, see the HiRDB Version 9 Installation and Design Guide.
Relationship to other operands
  • Y must be specified in the pd_name_fixed_port_lookup operand.
  • This operand is related to the pd_trn_port operand.
-m message-log-server-process-port-number
~<unsigned integer>((5001-65535))
When Y is specified in the pd_name_fixed_port_lookup operand, specifies the port number of the message log server process for the unit.
Notes
  • When a single server machine has multiple units, as in a mutual switchover configuration, specify a different port number for each unit.
  • When using the standby-less system switchover (1:1) facility, specify the same port number for the normal BES unit and the alternate BES unit.
  • When using the standby-less system switchover (effects distributed) facility, specify the same port number for all units belonging to the same HA group.
  • In the case of a unit on which no message log server process is running, a port number cannot be used, even if one is specified. However, such a defined port number is checked to ensure it does not duplicate any other port number. A unit on which no message log server process is running is a unit without a system manager when a HiRDB/Parallel Server is configured of at least two units and manager is specified in pd_mlg_msg_log_unit.
  • For details about how to specify a message log server process port number and for notes about duplication of other port numbers, see the HiRDB Version 9 Installation and Design Guide.
Relationship to other operands
  • Y must be specified in the pd_name_fixed_port_lookup operand.
  • This operand is related to the pd_mlg_port operand.
-a unit-monitoring-process-port-number
~<unsigned integer>((5001-65535))
When Y is specified in the pd_name_fixed_port_lookup operand, specifies the port number of the unit monitoring process for the unit.
Notes
  • When a single server machine has multiple units, as in a mutual switchover configuration, specify a different port number for each unit.
  • When using the standby-less system switchover (1:1) facility, specify the same port number for the normal BES unit and the alternate BES unit.
  • When using the standby-less system switchover (effects distributed) facility, specify the same port number for all units belonging to the same HA group.
  • In the case of a unit on which no unit monitoring process is running, a port number cannot be used, even if one is specified. However, such a defined port number is checked to ensure that it does not duplicate any other port number. A unit monitoring process does not run on any unit other than a unit with a system manager when a HiRDB/Parallel Servers consists of at least two units.
  • For details about how to specify a unit monitoring process port number and for notes about duplication of other port numbers, see the HiRDB Version 9 Installation and Design Guide.
Relationship to other operands
  • Y must be specified in the pd_name_fixed_port_lookup operand.
  • This operand is related to the pd_alv_port operand.

[Contents][Back][Next]

[Trademarks]

All Rights Reserved. Copyright (C) 2014, Hitachi, Ltd.