4.2 Operands whose specification values can be changed

The values of some of the server common definition operands can be changed in the individual server definitions. These operands are indicated below. After a planned termination, forced termination, or abnormal termination of HiRDB, some HiRDB system definition operands can be modified while others cannot be modified. The operands that can be modified are indicated below.

No.OperandDefinition nameModifiable after forced or abnormal termination?Modifiable after planned termination?
SYSUNTSVRSDSFESDSBES
1pd_max_bes_process[Figure][Figure]Y[Figure][Figure][Figure]YNY1
2pd_max_dic_process[Figure][Figure]Y[Figure][Figure]Y[Figure]NY1
3pd_process_count[Figure][Figure]YYYYYY1Y1
4pd_server_cleanup_interval[Figure][Figure]YY[Figure]YYYY
5pd_max_ard_process[Figure][Figure]YY[Figure]YYYY
6pd_dfw_awt_process[Figure][Figure]YY[Figure]YYYY
7pd_work_buff_mode[Figure][Figure]YY[Figure]YYYY
8pd_work_buff_size[Figure][Figure]YY[Figure]YYYY
9pd_work_buff_expand_limit[Figure][Figure]YY[Figure]YYYY
10pd_watch_pc_client_time3[Figure][Figure]YYY[Figure][Figure]YY
11pd_spd_syncpoint_skip_limit[Figure][Figure]YYYYYYY
12pd_dfw_syncpoint_skip_limit[Figure][Figure]YY[Figure]YYYY
13pd_lck_pool_size[Figure][Figure]YY[Figure]YYY1Y
14pd_fes_lck_pool_size[Figure][Figure]Y[Figure]Y[Figure][Figure]YY
15pd_lck_until_disconnect_cnt[Figure][Figure]YY[Figure]YYNY
16pd_max_open_holdable_cursors[Figure][Figure]YY[Figure]YYNN
17pd_lck_hash_entry[Figure][Figure]YYYYYYY
18pd_dbsync_lck_release_count[Figure][Figure]YY[Figure]YYYY
19pd_sql_object_cache_sizeY[Figure]YYYYYNY
20pd_table_def_cache_size[Figure][Figure]YYY[Figure][Figure]Y1,2Y1
21pd_auth_cache_size[Figure][Figure]YYY[Figure][Figure]Y1,2Y1
22pd_view_def_cache_size[Figure][Figure]YYY[Figure][Figure]Y1,2Y1
23pd_type_def_cache_size[Figure][Figure]YYY[Figure][Figure]YY
24pd_routine_def_cache_size[Figure][Figure]YYY[Figure][Figure]YY
25pd_registry_cache_size[Figure][Figure]YYY[Figure][Figure]YY
26pd_sds_shmpool_size[Figure][Figure]YY[Figure][Figure][Figure]Y1Y1
27pd_dic_shmpool_size[Figure][Figure]Y[Figure][Figure]Y[Figure]Y1Y1
28pd_bes_shmpool_size[Figure][Figure]Y[Figure][Figure][Figure]YY1Y1
29pd_rpc_traceYYYYYYYYY
30pd_rpc_trace_nameYYYYYYYYY
31pd_rpc_trace_sizeYYYYYYYYY
32pd_module_trace_maxYYYYYYYYY
33pd_module_trace_timer_levelYYYYYYYYY
34pd_max_add_dbbuff_no[Figure][Figure]YY[Figure]YYNY
35pd_max_add_dbbuff_shm_no[Figure][Figure]YY[Figure]YYNY
36pd_audit_def_buffer_size[Figure][Figure]YYY[Figure][Figure]YY
37pd_java_stdout_fileYYYYYYYYY
38pd_log_dual[Figure][Figure]YYYYYNN
39pd_log_remain_space_check[Figure][Figure]YYYYYYY
40pd_log_singleoperation[Figure][Figure]YYYYYNN
41pd_log_rerun_reserved_file_open[Figure][Figure]YYYYYYY
42pd_log_rerun_swap[Figure][Figure]YYYYYYY
43pd_log_swap_timeout[Figure][Figure]YYYYYYY
44pd_log_unload_check[Figure][Figure]YYYYYYY
45pd_log_max_data_size[Figure][Figure]YYYYYY1,2Y1
46pd_log_write_buff_count[Figure][Figure]YYYYYY2Y
47pd_log_rec_leng[Figure][Figure]YYYYYYY
48pd_spd_dual[Figure][Figure]YYYYYNN
49pd_spd_assurance_msg[Figure][Figure]YYYYYYY
50pd_spd_assurance_count[Figure][Figure]YYYYYNN
51pd_spd_reduced_mode[Figure][Figure]YYYYYNY
52pd_spd_reserved_file_auto_open[Figure][Figure]YYYYYNY
53pd_spd_max_data_size[Figure][Figure]YYYYYNN
54pd_log_sdinterval[Figure][Figure]YYYYYYY
55pd_sts_initial_error[Figure][Figure]YYYYYYY
56pd_sts_singleoperation[Figure][Figure]YYYYYYY
57pd_bes_connection_hold[Figure][Figure]Y[Figure][Figure][Figure]YYY
58pd_bes_conn_hold_trn_interval[Figure][Figure]Y[Figure][Figure][Figure]YYY

Y: Yes, specification value can be modified.

N: No, specification value cannot be modified.

[Figure]: Specification value cannot be modified because the operand is not applicable.

SYS: System common definition

UNT: Unit control information definition

SVR: Server common definition

SDS: Single server definition

FES: Front-end server definition

DS: Dictionary server definition

BES: Back-end server definition

1 If the specified value is too small, it may not be possible to restart HiRDB. When this is the case, restore the value to what it was before the change and then restart HiRDB.

2 If the specified value is too large, it may not be possible to restart HiRDB. When this is the case, restore the value to what it was before the change and then restart HiRDB.

3 The value for this operand can be different for each client. To change the value for a client, specify the PDSWATCHTIME operand in the client environment definition. For details about the PDSWATCHTIME operand, see the HiRDB Version 8 UAP Development Guide.