3.2 Operands whose specification values can be changed

The values of some of the unit control information 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_unit_id[Figure]Y[Figure][Figure][Figure][Figure][Figure]NN
2pd_hostname[Figure]Y[Figure][Figure][Figure][Figure][Figure]NN
3pd_max_server_processYY[Figure][Figure][Figure][Figure][Figure]YY
4pd_server_entry_queueYY[Figure][Figure][Figure][Figure][Figure]YY
5pd_thdlock_wakeup_lockYY[Figure][Figure][Figure][Figure][Figure]YY
6pd_thdlock_pipe_retry_intervalYY[Figure][Figure][Figure][Figure][Figure]YY
7pd_thdlock_retry_timeYY[Figure][Figure][Figure][Figure][Figure]YY
8pd_thdspnlk_spn_countYY[Figure][Figure][Figure][Figure][Figure]YY
9pd_db_io_error_actionYY[Figure][Figure][Figure][Figure][Figure]YY
10pd_max_recover_processYY[Figure][Figure][Figure][Figure][Figure]YY
11pd_watch_timeYY[Figure][Figure][Figure][Figure][Figure]YY
12pd_down_watch_procYY[Figure][Figure][Figure][Figure][Figure]YY
13pd_cwaittime_report_dirYY[Figure][Figure][Figure][Figure][Figure]YY
14pd_cwaittime_report_sizeYY[Figure][Figure][Figure][Figure][Figure]YY
15pd_uap_exerror_log_dirYY[Figure][Figure][Figure][Figure][Figure]YY
16pd_uap_exerror_log_sizeYY[Figure][Figure][Figure][Figure][Figure]YY
17pd_uap_exerror_log_param_size4YY[Figure][Figure][Figure][Figure][Figure]YY
18pd_lck_wait_timeoutYY[Figure][Figure][Figure][Figure][Figure]YY
19pd_lck_release_detectYY[Figure][Figure][Figure][Figure][Figure]YY
20pd_lck_release_detect_intervalYY[Figure][Figure][Figure][Figure][Figure]YY
21pd_lck_deadlock_infoYY[Figure][Figure][Figure][Figure][Figure]YY
22pd_stj_file_sizeYY[Figure][Figure][Figure][Figure][Figure]Y3Y
23pd_stj_buff_sizeYY[Figure][Figure][Figure][Figure][Figure]Y3Y
24pd_rpc_traceYYYYYYYYY
25pd_rpc_trace_nameYYYYYYYYY
26pd_rpc_trace_sizeYYYYYYYYY
27pd_cancel_dumpYY[Figure][Figure][Figure][Figure][Figure]YY
28pd_dump_suppress_watch_timeYY[Figure][Figure][Figure][Figure][Figure]YY
29pd_spool_cleanup_intervalYY[Figure][Figure][Figure][Figure][Figure]YY
30pd_spool_cleanup_interval_levelYY[Figure][Figure][Figure][Figure][Figure]YY
31pd_spool_cleanupYY[Figure][Figure][Figure][Figure][Figure]YY
32pd_spool_cleanup_levelYY[Figure][Figure][Figure][Figure][Figure]YY
33pd_module_trace_maxYYYYYYYYY
34pd_module_trace_timer_levelYYYYYYYYY
35pd_dbbuff_wait_intervalYY[Figure][Figure][Figure][Figure][Figure]YY
36pd_dbbuff_wait_spn_countYY[Figure][Figure][Figure][Figure][Figure]YY
37pd_syssts_file_name_1[Figure]7[Figure]Y[Figure][Figure][Figure][Figure][Figure]Y1Y1
38pd_syssts_initial_error[Figure]Y[Figure][Figure][Figure][Figure][Figure]YY
39pd_syssts_singleoperation[Figure]Y[Figure][Figure][Figure][Figure][Figure]YY
40pd_syssts_last_active_file[Figure]Y[Figure][Figure][Figure][Figure][Figure]YY
41pd_syssts_last_active_side[Figure]Y[Figure][Figure][Figure][Figure][Figure]YY
42pd_auditYY[Figure][Figure][Figure][Figure][Figure]NN
43pd_aud_file_nameYY[Figure][Figure][Figure][Figure][Figure]YY
44pd_aud_max_generation_sizeYY[Figure][Figure][Figure][Figure][Figure]YY
45pd_aud_max_generation_numYY[Figure][Figure][Figure][Figure][Figure]YY
46pd_aud_async_buff_sizeYY[Figure][Figure][Figure][Figure][Figure]YY
47pd_aud_async_buff_countYY[Figure][Figure][Figure][Figure][Figure]YY
48pd_aud_async_buff_retry_intvlYY[Figure][Figure][Figure][Figure][Figure]YY
49pd_ha_acttype[Figure]Y[Figure][Figure][Figure][Figure][Figure]NN
50pd_ha_unit[Figure]Y[Figure][Figure][Figure][Figure][Figure]NN
51pd_ha_switch_timeoutYY[Figure][Figure][Figure][Figure][Figure]YY
52pd_ha_server_process_standby[Figure]Y[Figure][Figure][Figure][Figure][Figure]NN
53pd_ha_agent[Figure]Y[Figure][Figure][Figure][Figure][Figure]NN
54pd_ha_max_act_guest_servers[Figure]Y[Figure][Figure][Figure][Figure][Figure]NN
55pd_ha_max_server_process[Figure]Y[Figure][Figure][Figure][Figure][Figure]NY2
56pd_ha_process_count[Figure]Y[Figure][Figure][Figure][Figure][Figure]YY
57pd_ha_resource_act_wait_timeYY[Figure][Figure][Figure][Figure][Figure]YY
58pd_ha_ipaddr_inheritYY[Figure][Figure][Figure][Figure][Figure]NN
59pd_rpl_hdepath[Figure]Y[Figure][Figure][Figure][Figure][Figure]NN
60pd_service_portYY[Figure][Figure][Figure][Figure][Figure]YY
61pd_change_clt_ipaddrYY[Figure][Figure][Figure][Figure][Figure]YY
62pd_registered_portYY[Figure][Figure][Figure][Figure][Figure]NY
63pd_registered_port_checkYY[Figure][Figure][Figure][Figure][Figure]NY
64pd_registered_port_levelYY[Figure][Figure][Figure][Figure][Figure]NY
65pd_ipc_send_retrycountYY[Figure][Figure][Figure][Figure][Figure]YY
66pd_ipc_send_retrysleeptimeYY[Figure][Figure][Figure][Figure][Figure]YY
67pd_ipc_send_countYY[Figure][Figure][Figure][Figure][Figure]YY
68pd_ipc_recv_countYY[Figure][Figure][Figure][Figure][Figure]YY
69pd_ipc_inet_bufsizeYY[Figure][Figure][Figure][Figure][Figure]YY
70pd_tcp_inet_bufsizeYY[Figure][Figure][Figure][Figure][Figure]YY
71pd_java_archive_directoryYY[Figure][Figure][Figure][Figure][Figure]YY
72pd_java_classpathYY[Figure][Figure][Figure][Figure][Figure]YY
73pd_java_runtimepathYY[Figure][Figure][Figure][Figure][Figure]YY
74pd_java_libpathYY[Figure][Figure][Figure][Figure][Figure]YY
75pd_java_stdout_fileYYYYYYYYY
76SHMMAXYY[Figure][Figure][Figure][Figure][Figure]YY

Y: Yes, specification value can be modified.

N: No, specification valued 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 Operands may be added, but not 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 value of the following HiRDB system definition operand can be changed for each client in its client environment definition. To change values for a client, you must specify the applicable operand in its client environment definition. For details about the client environment definition, see the HiRDB Version 8 UAP Development Guide.

HiRDB system definition
operand
Client environment definition
operand
pd_uap_exerror_log_param_sizePDUAPEXERLOGPRMSZ