3.2.2 Operands related to maximum concurrent executions

3) pd_max_server_process = maximum-number-of-concurrently-activated-server-processes
~<unsigned integer>((50-10000))
Specifies the maximum number of processes that can be activated at the same time in the unit. The number of server processes includes the number of processes for the system server, individual servers, utilities, and the like (the system server is a server that is used internally by HiRDB).
Specification guidelines
  • Normally, omit this operand. 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 value of the following equation is assumed. Note that HiRDB automatically re-computes the value of this operand whenever you change the specification of any of the operands mentioned in the explanations below of the variables.
    Default value = a + b[Figure] (c + 30) + 70 + i + j + k + m + n + o
  • If you choose to specify this operand, use the following formula as a reference for determining the operand value. For a HiRDB parallel server configuration, determine values for all units, and use the largest of these values as a guideline.
    Recommended value = a + b[Figure] (c + d[Figure] e + f + 3) + d[Figure] g + h + i + j + k + m + n + o+ A
    VariableExplanation of variable
    aFor a HiRDB single server configuration:
    Value of pd_max_users
    For a HiRDB parallel server configuration:
    Total the values obtained using the following formulas for individual servers inside the unit.
    Back-end server: Value of pd_max_bes_process
    Dictionary server: Value of pd_max_dic_process
    For front-end servers: Value of pd_max_users
    • If the pd_max_bes_process or pd_max_dic_process operand is omitted, use the value of the pd_max_users operand.
    • If a unit contains multiple back-end servers, compute a value for each back-end server.
    • If multiple front-end servers are used, add one per front-end server.
    • For a unit to which the standby-less system switchover (effects distributed) facility is to be applied, substitute the value of the pd_ha_max_server_process operand.
    bFor a HiRDB single server configuration:
    1
    For a HiRDB parallel server configuration:
    Server count inside the unit (server count allocated to the unit by the pdstart operand of the system common definition)
    • For a unit to which the standby-less system switchover (effects distributed) facility is to be applied, add the value of the pd_ha_max_act_guest_servers operand (or the default, if this operand has been omitted).
    cConcurrently executable process count in full recovery processing (value of the pd_max_recover_process operand)
    dMaximum number of concurrently executable utilities (2 is the default value for this operand)
    eNumber of processes to be started in each server by the utility (set this variable to 10)
    fNumber of processes to be started by HiRDB for controlling the server (set this variable to 6)
    gNumber of processes to be started in each unit by the utility (set this variable to 10)
    hNumber of processes to be started by HiRDB for controlling the unit (set this variable to 50)
    iFor a HiRDB single server configuration:
    1
    For a HiRDB parallel server configuration:
    Number of back-end servers in the unit
    • For a unit to which the standby-less system switchover (effects distributed) facility is to be applied, add the value of the pd_ha_max_act_guest_servers operand.
    jFor a HiRDB single server configuration:
    Value of pd_max_ard_process operand
    For a HiRDB parallel server configuration:
    Number of back-end servers in the unit[Figure] pd_max_ard_process operand value + number of dictionary servers in the unit[Figure] pd_max_ard_process operand value
    • For a unit to which the standby-less system switchover (effects distributed) facility is to be applied, add the following value:
      Maximum value of pd_max_ard_process operand for a guest BES[Figure] pd_ha_max_act_guest_servers operand value
    kDepends on the value specified for the pd_process_terminator operand:
    • resident: 1
    • fixed (default value): pd_process_terminator_max operand value
    • nonresident: 0
    mTo execute updatable online reorganization, substitute the following values. If updatable online reorganization is not to be executed, substitute 0.
    For a HiRDB single server configuration:
    x
    For a HiRDB parallel server configuration:
    x[Figure] (y + z)
    x: pd_max_reflect_process_count operand value
    y: Number of servers in the unit
    z: pd_ha_max_act_guest_servers operand value
    For a unit to which the standby-less system switchover (effects distributed) facility is to be applied, add z. For a unit to which the standby-less system switchover (effects distributed) facility is not to be applied, the value is 0.
    nFor a HiRDB single server configuration:
    pd_dfw_awt_process operand value
    For a HiRDB parallel server configuration:
    Number of back-end servers[Figure] pd_dfw_awt_process operand value + number of dictionary servers[Figure] pd_dfw_awt_process operand value
    • For a unit to which the standby-less system switchover (effects distributed) facility is to be applied, add the following value:
      Maximum value of the pd_dfw_awt_process operand for a guest BES[Figure] pd_ha_max_act_guest_servers operand value
    oWhen using a memory database, substitute the following value:
    p + 128 + XDS count in the unit[Figure] 5 + 2
    If the unit has a system manager
    p: 64 [Figure] XDS count for system as a whole
    If the unit does not have a system manager
    p: 0
    AMaximum number of transaction recovery processes that can be started
    [Figure]pd_trn_rcvmsg_store_buflen operand value[Figure] 72[Figure]
Relationships to other operands
This operand's value limits the maximum value of the pd_process_count operand.
Notes
  • This specification value includes the number of processes for servers and utilities in the unit. If this value is too small, the following might occur:
    [Figure]Unit or server startup process results in an error
    [Figure]Transaction recovery cannot be performed
    [Figure]HiRDB planned termination cannot be performed
  • Because the number of processes that can actually be activated depends on factors such as the system resources, it might be necessary to adjust the resources or to change the locations of servers in some cases.
Effects on individual estimation formulas
If the value of the pd_max_server_process operand is changed, the following estimation formulas are affected:
HiRDB Version 9 Installation and Design Guide:
  • Estimating AIX OS parameter values
  • Calculation of required memory 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 single server configuration
  • Calculation of required memory under Estimating the memory size required for a HiRDB parallel server configuration
  • Formulas for shared memory used by a unit controller under Estimating the memory size required for a HiRDB parallel server configuration
  • Estimating HP-UX OS parameter values
  • Estimating Linux kernel parameter values
  • Estimating Solaris OS parameter values