6.2 Operands whose specification values can be changed

The values of some of the front-end server definition operands can be changed in the system common definition, unit control information definition, and server common definition. 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?
SYSUNTSVRFESDSBES
1pd_process_count[Figure][Figure]YYYYY2Y2
2pd_server_cleanup_interval[Figure][Figure]YYYYYY
3pd_optimize_level4Y[Figure][Figure]Y[Figure][Figure]YY
4pd_additional_optimize_level4Y[Figure][Figure]Y[Figure][Figure]YY
5pd_floatable_bes[Figure][Figure][Figure]Y[Figure][Figure]YY
6pd_non_floatable_bes[Figure][Figure][Figure]Y[Figure][Figure]YY
7pd_watch_pc_client_time4[Figure][Figure]YY[Figure][Figure]YY
8pd_spd_syncpoint_skip_limit[Figure][Figure]YYYYYY
9pd_cwaittime_wrn_pnt4Y[Figure][Figure]Y[Figure][Figure]YY
10pd_uap_exerror_log_use4Y[Figure][Figure]Y[Figure][Figure]YY
11pd_fes_lck_pool_size[Figure][Figure]YY[Figure][Figure]YY
12pd_lck_hash_entry[Figure][Figure]YYYYYY
13pd_sql_object_cache_sizeY[Figure]YYYYNY
14pd_table_def_cache_size[Figure][Figure]YY[Figure][Figure]Y2,3Y2
15pd_auth_cache_size[Figure][Figure]YY[Figure][Figure]Y2,3Y2
16pd_view_def_cache_size[Figure][Figure]YY[Figure][Figure]Y2,3Y2
17pd_type_def_cache_size[Figure][Figure]YY[Figure][Figure]YY
18pd_routine_def_cache_size[Figure][Figure]YY[Figure][Figure]YY
19pd_registry_cache_size[Figure][Figure]YY[Figure][Figure]YY
20pd_rpc_traceYYYYYYYY
21pd_rpc_trace_nameYYYYYYYY
22pd_rpc_trace_sizeYYYYYYYY
23pd_module_trace_maxYYYYYYYY
24pd_module_trace_timer_levelYYYYYYYY
25pd_audit_def_buffer_size[Figure][Figure]YY[Figure]YYY
26pd_java_stdout_fileYYYYYYYY
27pd_log_dual[Figure][Figure]YYYYNN
28pd_log_remain_space_check[Figure][Figure]YYYYYY
29pd_log_auto_unload_path[Figure][Figure][Figure]YYYNN
30pd_log_singleoperation[Figure][Figure]YYYYNN
31pd_log_rerun_reserved_file_open[Figure][Figure]YYYYYY
32pd_log_rerun_swap[Figure][Figure]YYYYYY
33pd_log_swap_timeout[Figure][Figure]YYYYYY
34pd_log_unload_check[Figure][Figure]YYYYYY
35pd_log_max_data_size[Figure][Figure]YYYYY2,3Y2
36pd_log_write_buff_count[Figure][Figure]YYYYY3Y
37pd_log_rec_leng[Figure][Figure]YYYYYY
38pd_spd_dual[Figure][Figure]YYYYNN
39pd_spd_assurance_msg[Figure][Figure]YYYYYY
40pd_spd_assurance_count[Figure][Figure]YYYYNN
41pd_spd_reduced_mode[Figure][Figure]YYYYNY
42pd_spd_reserved_file_auto_open[Figure][Figure]YYYYNY
43pd_spd_max_data_size[Figure][Figure]YYYYNN
44pd_log_sdinterval[Figure][Figure]YYYYYY
45pd_sts_file_name_1-7[Figure][Figure][Figure]YYYY1Y1
46pd_sts_initial_error[Figure][Figure]YYYYYY
47pd_sts_singleoperation[Figure][Figure]YYYYYY
48pd_sts_last_active_file[Figure][Figure][Figure]YYYYY
49pd_sts_last_active_side[Figure][Figure][Figure]YYYYY
50pdlogadfg -d sys[Figure][Figure][Figure]YYYY1Y1
51pdlogadpf -d sys[Figure][Figure][Figure]YYYY1Y1
52pdlogadfg -d spd[Figure][Figure][Figure]YYYY1Y1
53pdlogadpf -d spd[Figure][Figure][Figure]YYYY1Y1
54pdplgprm[Figure][Figure][Figure]YYYYY
55pdhubopt[Figure][Figure][Figure]Y[Figure][Figure]NY

Y: Yes, specification value can be modified.

N: No, specification value cannot be modified.

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

SYS: System common definition

UNT: Unit control information definition

SVR: Server common definition

FES: Front-end server definition

DS: Dictionary server definition

BES: Back-end server definition

1 Operand that can be added only; it cannot be deleted or modified.

2 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.

3 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.

4 The following values for the HiRDB system definition operands can be different for each client. To change a value for a client, specify the operand in the client environment definition. For details about the client environment definition, see the HiRDB Version 8 UAP Development Guide.

HiRDB system definition operandClient environment definition operand
pd_optimize_levelPDSQLOPTLVL
pd_additional_optimize_levelPDADDITIONALOPTLVL
pd_watch_pc_client_timePDSWATCHTIME
pd_cwaittime_wrn_pntPDCWAITTIMEWRNPNT
pd_uap_exerror_log_usePDUAPEXERLOGUSE