2.2.10 Operands related to narrowed searches
- 44) pd_max_list_users = number-of-users-who-can-perform-operations-on-lists
- ~<unsigned integer>((0-32767)) <<0>>
- Specifies the number of all users who perform operations on lists.
- Relationship to other operands
- When this operand is specified, the pd_max_list_count operand must also be specified.
- Notes
- Do not specify an unnecessarily large value for this operand. Increasing the specification value of this operand increases the size of the shared memory used by HiRDB. For details about the shared memory used by servers, see the HiRDB Version 9 Installation and Design Guide.
- If you specify the maximum value (32767) for both this operand and the pd_max_list_count operand, the size of the shared memory might exceed the upper limit of the size that can be allocated by the OS.
- Effects on individual estimation formulas
- If the value of the pd_max_list_users operand is changed, the following estimation formulas are affected:
- HiRDB Version 9 Installation and Design Guide:
- Formula 1 under Formulas for shared memory used by a single server
- Formula 1 under Formulas for the size of the shared memory used by a dictionary server
- Formula 1 under Formulas for the size of the shared memory used by a back-end server
- 45) pd_max_list_count = number-of-lists-created-per-user
- ~<unsigned integer>((0-32767)) <<0>>
- Specifies the maximum number of lists that one user can create.
- Relationship to other operands
- When this operand is specified, the pd_max_list_users operand must also be specified.
- Notes
- Do not specify an unnecessarily large value for this operand. Increasing the specification value of this operand increases the size of the shared memory used by HiRDB. For details about the shared memory used by servers, see the HiRDB Version 9 Installation and Design Guide.
- If you specify the maximum value (32767) for both this operand and the pd_max_list_users operand, the size of the shared memory might exceed the upper limit of the size that can be allocated by the OS.
- Effects on individual estimation formulas
- If the value of the pd_max_list_count operand is changed, the following estimation formulas are affected:
- HiRDB Version 9 Installation and Design Guide:
- Formula 1 under Formulas for shared memory used by a single server
- Formula 1 under Formulas for the size of the shared memory used by a dictionary server
- Formula 1 under Formulas for the size of the shared memory used by a back-end server
- 46) pd_list_initialize_timing = INITIAL | DEFER | STANDBY
- Specifies the list initialization (deletion) timing. Normally, lists are initialized when HiRDB is started (including restart). You can use this operand to change the initialization timing. If you create a large number of lists, you might want to consider changing the specification value of this operand.
- For details about changing the list initialization timing, see the HiRDB Version 9 System Operation Guide.
- INITIAL:
- Lists are initialized during HiRDB startup. HiRDB is started only after all lists have been initialized.
- DEFER:
- Lists are not initialized during HiRDB startup. They are initialized when the ASSIGN LIST statement is executed. Consequently, there is some overhead associated with the execution of the ASSIGN LIST statement. Consider specifying DEFER in the following cases:
- You want to shorten the HiRDB startup time.
- You want to shorten the system switchover time (when user server hot standby or the rapid system switchover facility is being used).
- STANDBY:
- This specification becomes valid when the rapid system switchover facility is used. Even if STANDBY is specified when the rapid system switchover facility is not being used, INITIAL is used as the default.
- Lists are initialized when starting the standby HiRDB. They are not initialized during a system switchover. Lists are not initialized when the ASSIGN LIST statement is executed following a system switchover, either. Note that you must create the same lists for both the running system and the standby system.