3.2.22 Operands related to communication processing

67) pd_service_port = scheduler-process-port-number
~<unsigned integer>((5001-65535))
Specifies the port number for the scheduler process under the following circumstances:
  • A high-speed connection facility is used
For details about high-speed connection facilities, see the HiRDB Version 9 Installation and Design Guide.
  • A firewall or NAT is installed on the HiRDB server
    For details about setting the HiRDB environment when a firewall or NAT is installed on the HiRDB server, see the HiRDB Version 9 Installation and Design Guide.
Specification guidelines
  • Use this operand for a HiRDB single server configuration or when there is a firewall between the HiRDB client and HiRDB server.
  • Use this operand in systems connected via a broadband LAN to reduce the number of communications when connecting to a server.
Operand default
When this operand is omitted, the specification of the same operand in the system common definition is assumed.
Notes
  • If there are multiple units in a single server machine, such as in a mutual system switchover configuration, always specify this operand in the unit control information definition. Specify a different port number for each unit. If a port number is duplicated, system switchover will fail in one of the units during a switching attempt.
  • When this operand is specified in both the unit control information definition and the system common definition, the specification in the unit control information definition is effective.
  • If the HiRDB port number (the port number specified with the pd_name_port operand or the -p option of the pdunit operand) is specified, the specification of this operand will be ignored, which will prevent operation using the high-speed connection facility or when a firewall or NAT is set up at the HiRDB server. The KFPS00860-W message will be issued when this happens.
  • If the high-speed connection facility is used to issue concurrently more connection requests than the value set in the pd_max_users operand, a shortage will occur in the number of active front-end servers and single servers for extracting connection requests from the message queue. Consequently, some connection requests will not be extracted from the message queue, and the message queue monitoring facility could stop the unit. You must ensure that the number of concurrent connection requests generated does not exceed the value specified in the pd_max_users operand. For details about the message queue monitoring facility, see the HiRDB Version 9 System Operation Guide.
  • 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.
  • In the case of a parallel server that has multiple front-end servers, the front-end servers to be connected are fixed and load sharing will no longer be possible. For this reason, consider carefully the balance among the front-end servers to be connected.
Relationship to other operands
This operand is related to the following operands:
  • pd_scd_port
  • pdunit -s
68) pd_change_clt_ipaddr = 0 | 1
Specifies the network to be used by the HiRDB server to communicate with HiRDB clients. Normally, you need not specify this operand.
0:
Communication from the HiRDB server to HiRDB clients uses the network in which the IP address specified in the PDCLTRCVADDR operand of the client environment definition is located. If the PDCLTRCVADDR operand is omitted, the IP address of the standard host is assumed.
1:
For communication from the HiRDB server to HiRDB clients, the network used for communication from HiRDB clients to the HiRDB server is used.
Operand default
When this operand is omitted, the specification of the same operand in the system common definition is assumed. When the same operand is also omitted in the system common definition, the default is 1.
69) pd_registered_port ="port-number-reservation-range" [,"port-number-reservation-range"]...
~<character string>
When the HiRDB reserved port facility is used, this operand specifies ranges of port numbers to be used for communication by HiRDB.
The HiRDB reserved port facility is enabled for server-to-server communication and server-to-client communications. For details, see the description of the pd_registered_port_level operand. This facility does not need to be used if the number of ports to be used is small.
Operand specification method
This example provides the following 35,000 port numbers: 6000 to 8999, 12500 to 29999, and 30500 to 44999:
set pd_registered_port = "6000:8999","12500:29999","30500:44999"
Advantages
The port numbers to be used for communication between a HiRDB server and HiRDB clients or between HiRDB servers are assigned automatically by the OS. If the communication volume increases significantly, a shortage of port numbers might cause an interruption of processing or might adversely affect the communication processing by other programs. Use this operand to specify a range of port numbers to be used exclusively by HiRDB to prevent such problems.
Specification guidelines
  • The range of port numbers that can be specified is from 5001 through 49151.
  • For the number of ports used by HiRDB, see the HiRDB Version 9 Installation and Design Guide.
  • Do not register the port number specified in this operand in /etc/services (for NIS or DNS environments, the locations defined therein). A duplication check is performed for /etc/services when Y, C, or W is specified in the pd_registered_port_check operand.
Operand default
When this operand is omitted, the specification of the same operand in the system common definition is assumed.
Specification value tuning method
As a guideline, the value obtained from the following formula is the total number of ports that will be needed:
a + b + 100
a: Number of HiRDB reserved ports that are being used (# OF REGISTERED PORTS)
b: Number of ports being used that were assigned automatically by the OS because all HiRDB reserved ports were in use (# OF ASSIGNED PORTS)
These values can be determined from the statistical information related to system operation obtained by executing the statistics analysis utility.
Operand rules
  • Up to 10 ranges of port numbers can be specified.
  • If more than one range is specified, ensure that there is no overlap in the port numbers included in the various ranges.
  • An ending port number must be greater than the paired starting port number.
Notes
  • When there are multiple units in a single server machine, such as in a mutual system switchover configuration, this operand must be specified in the unit control information definition. Be sure to specify a different port number for each unit. If a port number is duplicated, system switchover will fail in one of the units during a switching attempt.
  • Specification of a port number that is not supported by the HiRDB reserved port facility is ignored. For the scope of the HiRDB reserved port facility, see the pd_registered_port_level operand.
  • For details about how to specify port numbers when the HiRDB reserved port facility is used and for notes about duplication of other port numbers, see the HiRDB Version 9 Installation and Design Guide.
  • When this operand is specified in both the unit control information definition and the system common definition, the specification in the unit control information definition is effective.
Effects on individual estimation formulas
If the value of the pd_registered_port operand is changed, the following estimation formulas are affected:
HiRDB Version 9 Installation and Design Guide:
  • Formulas for shared memory used by a unit controller under Estimating the memory size required for a HiRDB single server configuration
  • Formulas for shared memory used by a unit controller under Estimating the memory size required for a HiRDB parallel server configuration
70) pd_registered_port_check = Y | N | C | W
Specifies whether checking is to be performed for overlapping port numbers in the ranges of port numbers specified in the pd_registered_port operand and in the port numbers registered in /etc/services (definition location in an NIS or DNS environment).
Y:
Check for overlap. If an overlap is found, the KFPS00348-E message is output and HiRDB activation is canceled.
N:
Do not check for overlap.
C:
Check for overlap. The HiRDB reserved port facility is not applied to any overlapping port number.
W:
Check for overlap. If an overlap is found, the KFPS00354-W message is output. The HiRDB reserved port facility is not applied to any overlapping port number.
Condition
The pd_registered_port operand must be specified.
Specification guidelines
  • If an overlap in port numbers is detected, HiRDB communication might be adversely affected, resulting, for example, in the receipt of wrong messages or message send failures.
  • If Y, C, or W is specified, process server process activation in an NIS or DNS environment might slow down.
Operand default
When this operand is omitted, the specification of the same operand in the system common definition is assumed. When the same operand is also omitted in the system common definition, the default is Y.
71) pd_ipc_send_retrycount = process-to-process-send-retries-count
~<unsigned integer>((1-32767))
Specifies the number of times process-to-process communication can be attempted. This operand is related to the pd_ipc_send_retrysleeptime operand.
Examples
  • pd_ipc_send_retrycount = 500
  • pd_ipc_send_retrysleeptime = 2
When the operands are specified in this way, send is attempted up to 500 times and a 2-second sleep occurs between attempts.
Specification guidelines
  • Normally, this operand need not be specified.
  • Specifying too large a value for this operand increases the CPU lock rate.
Operand default
When this operand is omitted, the specification of the same operand in the system common definition is assumed. When the same operand is also omitted in the system common definition, the default is 200.
72) pd_ipc_send_retrysleeptime = process-to-process-send-retry-sleep-time
~<unsigned integer>((0-60)) (seconds)
Specifies the sleep time between process-to-process send retries.
This operand is related to the pd_ipc_send_retrycount operand.
Examples
  • pd_ipc_send_retrycount = 500
  • pd_ipc_send_retrysleeptime = 2
When the operands are specified in this way, send is attempted up to 500 times and a 2-second sleep occurs between attempts.
Specification guidelines
  • Normally, this operand need not be specified.
  • Specifying too large a value for this operand increases communication completion time.
Operand default
When this operand is omitted, the specification of the same operand in the system common definition is assumed. When the same operand is also omitted in the system common definition, the default is 0.
73) pd_ipc_send_count = server-to-server-send-retries-count
~<unsigned integer>((1-32767))
Specifies the number of times a server-to-server send can be performed before the send is completed. A send occurs for up to 5 seconds at each retry. With the default value, send will be performed for up to 60 [Figure] 5 seconds = 300 seconds.
Specification guideline
Normally, this operand need not be specified. If transmission timeouts occur frequently, increase this operand's value.
Operand default
When this operand is omitted, the specification of the same operand in the system common definition is assumed. When the same operand is also omitted in the system common definition, the default is 60.
74) pd_ipc_recv_count = server-to-server-receive-retries-count
~<unsigned integer>((1-32767))
Specifies the number of times a server-to-server receive can be performed before receive is completed. Receive occurs for up to 5 seconds at each retry. With the default value, receive is performed for up to 120 [Figure] 5 seconds = 10 minutes.
Specification guideline
Normally, this operand need not be specified.
Operand default
When this operand is omitted, the specification of the same operand in the system common definition is assumed. When the same operand is also omitted in the system common definition, the default is 120.