This appendix provides an overview of what is specified in each of the HiRDB system definition operands. Note that the operands for the following definitions are not described in this appendix.
Operand explanation | Operand name |
---|---|
Specifies a HiRDB identifier. | pd_system_id |
Specifies a HiRDB port number. | pd_name_port |
Specifies the first HiRDB file in the master directory RDAREA. | pd_master_file_name |
Allocates a unit to a host. | pdunit |
Allocates a server to a host. | pdstart |
Specifies a unit identifier. | pd_unit_id |
Specifies a standard host name. | pd_hostname |
Operand explanation | Operand name |
---|---|
Specifies the maximum number of concurrent connections. | pd_max_users |
Specifies the maximum number of server processes that can be activated concurrently within a single unit. | pd_max_server_process |
Specifies the maximum number of tables that can be accessed concurrently by a transaction. | pd_max_access_tables |
Modifies the maximum number of utilities that can be executed concurrently. | pd_utl_exec_mode |
Specifies the maximum number of pdreclaim commands (with the -p option specified) that can be executed concurrently. | pd_max_commit_write_reclaim_no |
Operand explanation | Operand name |
---|---|
Specifies the maximum number of processes that can be activated in any back-end server. | pd_max_bes_process |
Specifies the maximum number of processes that can be activated in any dictionary server. | pd_max_dic_process |
Specifies the number of resident processes that can be activated at server startup. | pd_process_count |
Specifies in minutes the interval checking for nonresident server processes in HiRDB that are to be stopped. This facility is applied when the number of executing server processes exceeds the number of processes that can be made resident (value specified by the pd_process_count operand). | pd_server_cleanup_interval |
Specifies the number of processes necessary for asynchronous READ operations when using the asynchronous READ facility. For a HiRDB/Parallel Server, this operand specifies the number of processes per server (back-end server or dictionary server). | pd_max_ard_process |
Specifies the number of processes to be processed in parallel when the facility for parallel writes in deferred write processing is used. | pd_dfw_awt_process |
Operand explanation | Operand name |
---|---|
Specifies the method of allocating buffers for creating work tables for temporary storage of information during SQL execution. | pd_work_buff_mode |
Specifies the size of the work table buffer to be used for SQL execution. | pd_work_buff_size |
Specifies the upper limit for expanding the work table buffer when the space in this buffer becomes insufficient. | pd_work_buff_expand_limit |
Specifies the names of HiRDB file system areas for work table files. | pdwork |
Operand explanation | Operand name |
---|---|
Specifies the HiRDB system startup method. | pd_mode_conf |
Specifies the amount of time to wait for completion of the pdstart command execution. | pd_system_complete_wait_time |
Specifies the maximum amount of time to wait for completion of HiRDB start preparation. | pd_start_time_out |
Operand explanation | Operand name |
---|---|
Specifies whether or not reduced activation is to be used. | pd_start_level |
Specifies the amount of time to wait for receipt of a notice of reduced activation startup. | pd_reduced_check_time |
Specifies the names of units that need not be started because of errors, etc., during HiRDB startup. | pd_start_skip_unit |
Operand explanation | Operand name |
---|---|
Specifies the timing for committing database changes to a file. | pd_dbsync_point |
Specifies the timing for committing to file updates in the following types of RDAREAs:
| pd_system_dbsync_point |
When an update buffer reference request is issued during synchronization point acquisition processing, the transaction process that issued the reference request handles the writing of the update buffer contents into the database. This operand specifies whether or not the handling of this write processing is to be skipped. | pd_dbsync_altwrite_skip |
Specifies whether or not errors are to be suppressed during operation. | pd_overflow_suppress |
Specifies whether to start the post-processing process, which executes post-processing when a HiRDB process is abnormally terminated, when starting HiRDB. | pd_process_terminator |
Specifies the number of post-processing processes to be started when starting HiRDB. | pd_process_terminator_max |
Specifies a space conversion level when the space configuration facility is used. | pd_space_level |
Specifies whether or not the facility for conversion to a DECIMAL signed normalized number is to be used. | pd_dec_sign_normalize |
If contention occurs in the HiRDB server process during concurrent execution of UAPs, processing requests may sometimes be temporarily queued. This operand specifies what HiRDB must do in this case. | pd_server_entry_queue |
Specifies the type of sleep function (for waiting for a specified amount of time) to be used when acquiring a lock between threads. | pd_thdlock_sleep_func |
Specifies a thread lock release notification method. | pd_thdlock_wakeup_lock |
Specifies in microseconds the interval at which to check for thread lock release. | pd_thdlock_pipe_retry_interval |
Specifies in microseconds the thread lock sleep time. | pd_thdlock_retry_time |
Specifies a spin count for thread spin lock. | pd_thdspnlk_spn_count |
Specifies the page access mode to be used for database retrieval. | pd_pageaccess_mode |
Specifies the method to be used for checking for RDAREA hold. | pd_cmdhold_precheck |
Specifies the processing to be performed by HiRDB when an input/output error occurs in an RDAREA (excluding the master directory RDAREA). | pd_db_io_error_action |
Specifies whether to hide the error cause in the message that is output when a connection attempt fails. | pd_connect_errmsg_hide |
Specifies whether or not the error messages output when a server process is terminated forcibly are to be changed. | pd_cancel_down_msgchange |
Operand explanation | Operand name |
---|---|
Specifies the number of processes to be recovered during full recovery processing. For a HiRDB/Parallel Server, this operand specifies the number of processes to be recovered per server (dictionary server or back-end server). | pd_max_recover_process |
Specifies whether to output to a database the pages updated after a synchronization point during full recovery processing. | pd_redo_allpage_put |
Operand explanation | Operand name |
---|---|
Specifies whether or not an undecided transaction that has branched from a transaction is to be decided automatically when a unit is restarted. An undecided transaction occurs when a unit terminates abnormally while the latter transaction's first phase of COMMIT is incomplete. | pd_trn_rerun_branch_auto_decide |
Specifies the interval (in seconds) for sending an automatic decision instruction to a branched transaction when the previous send operation has failed for some reason. | pd_trn_send_decision_intval_sec |
Specifies the interval (in minutes) for sending an automatic decision instruction to a branched transaction when the previous send operation has failed for some reason. | pd_trn_send_decision_interval |
Specifies the maximum amount of time to wait for a decision completion notice to be returned after an automatic decision instruction has been sent to a branched transaction. | pd_trn_send_decision_retry_time |
Specifies the maximum amount of time to wait for receiving communication (prepare, commit instruction, or response) between transaction branches during transaction synchronization point processing executed in the HiRDB server process. | pd_trn_watch_time |
Specifies whether to use one-phase commit in a HiRDB/Parallel Server's commitment control. | pd_trn_commit_optimize |
Operand explanation | Operand name |
---|---|
Specifies SQL optimization options. | pd_optimize_level |
Specifies SQL extension optimizing options. | pd_additional_optimize_level |
Specifies the hashing method to be used when hash join, subquery hash execution is specified for the SQL extension optimizing option. | pd_hashjoin_hashing_mode |
Specifies the size of the hash table to be used when "application of hash-execution of a hash join or a subquery" is specified as an SQL optimization option. | pd_hash_table_size |
Specifies one of the following HiRDB processing methods to be used for executing an SQL statement that uses a work table:
| pd_work_table_option |
Specifies back-end servers that can be used as floating servers. | pd_floatable_bes |
Specifies back-end servers that are not to be used as floating servers. | pd_non_floatable_bes |
Operand explanation | Operand name |
---|---|
Specifies whether to use the facility for output of extended SQL error information. | pd_uap_exerror_log_use |
Specifies the directory in which to store SQL error report files. | pd_uap_exerror_log_dir |
Specifies the maximum size of an SQL error report file. | pd_uap_exerror_log_size |
Specifies the maximum data size for the parameter information to be output to an error log file and an SQL error report file. | pd_uap_exerror_log_param_size |
Operand explanation | Operand name |
---|---|
Specifies the name of an SQL reserved word deletion file when the SQL reserved word deletion facility is used. | pd_delete_reserved_word_file |
Operand explanation | Operand name |
---|---|
Specifies the maximum number of users who can own lists concurrently. | pd_max_list_users |
Specifies the maximum number of lists that one user can create. | pd_max_list_count |
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. | pd_list_initialize_timing |
Operand explanation | Operand name |
---|---|
Specifies the monitoring time (units: minutes) for monitoring the execution time of the following utilities:
| pd_utl_exec_time |
Specifies a maximum execution time for SQLs that are executed in a HiRDB server process. If execution of an SQL statement is not completed within the specified amount of time, execution of that SQL statement is terminated. | pd_watch_time |
If messages cannot be extracted from the message queue within the time specified by this operand, a warning message (KFPS00888-W or KFPS00889-E) is output (the message queue monitoring facility). | pd_queue_watch_time |
Specifies the processing to be performed by HiRDB when messages cannot be extracted from the message queue within the time specified by the pd_queue_watch_time operand. | pd_queue_watch_timeover_action |
If abnormal terminations of server processes exceed the value specified in this operand, HiRDB (applicable unit for a HiRDB/Parallel Server) is abnormally terminated (the facility for monitoring abnormal process terminations). | pd_down_watch_proc |
Specifies the interval at which the other host's operation status is to be checked. | pd_host_watch_interval |
Specifies the maximum amount of time to wait for the next request from a HiRDB client after the HiRDB server returns a response to a request from a Windows-compatible HiRDB client. | pd_watch_pc_client_time |
Specifies the number of successive synchronization point dumps that can be skipped (number of skips in a single transaction). | pd_spd_syncpoint_skip_limit |
Specifies the maximum number of times synchronization point dumps can be skipped (number of skips per transaction) when synchronization point dump acquisition is delayed by deferred write processing. | pd_dfw_syncpoint_skip_limit |
Specifies whether or not a warning message related to resource usage is to be issued. | pd_watch_resource |
Specifies whether to output the warning message when the number of concurrent connections reaches or exceeds the specified percentage of the maximum value specified by the pd_max_users operand. | pd_max_users_wrn_pnt |
Specifies whether or not a warning message related to the number of concurrently accessible base tables specified by the pd_max_access_tables operand is to be issued. | pd_max_access_tables_wrn_pnt |
Specifies whether to output the warning message when the number of RDAREAs reaches or exceeds the specified percentage of the maximum value specified by the pd_max_rdarea_no operand. | pd_max_rdarea_no_wrn_pnt |
Specifies whether to output the warning message when the number of HiRDB files comprising an RDAREA reaches or exceeds the specified percentage of the maximum value specified by the pd_max_file_no operand. | pd_max_file_no_wrn_pnt |
Specifies whether or not a warning message related to the HiRDB file system areas for work table files specified by the pdwork operand is to be issued. | pdwork_wrn_pnt |
Specifies as a percentage of the number of users who can create lists (as specified by the pd_max_list_users operand) the point at which the number of users actually using lists is to cause a warning message to be issued. | pd_max_list_users_wrn_pnt |
Specifies as a percentage of the number of lists that can be created per user (as specified by the pd_max_list_count operand) the point at which the number of lists created by a user is to cause a warning message to be issued. | pd_max_list_count_wrn_pnt |
Specifies as a percentage of the number of lists that can be created at a server the point at which a warning message is to be issued. | pd_rdarea_list_no_wrn_pnt |
Operand explanation | Operand name |
---|---|
Specifies whether or not deadlock information is to be output. | pd_lck_deadlock_info |
Specifies the maximum amount of time for monitoring lock wait time. | pd_lck_wait_timeout |
Specifies the method by which HiRDB is to detect lock release. | pd_lck_release_detect |
Specifies the interval at which HiRDB is to reference the lock management area. | pd_lck_release_detect_interval |
Specifies the processing method to be used when WITHOUT LOCK NOWAIT search is executed. | pd_nowait_scan_option |
Specifies the number of users who must be waiting for lock release in order for a warning message to be issued. | pd_lck_queue_limit |
Specifies whether or not deadlock priorities are to be used. | pd_deadlock_priority_use |
Specifies the deadlock priority value of a command. | pd_command_deadlock_priority |
Specifies the method for creating a locked resource for an index key value. | pd_key_resource_type |
Specifies the amount of lock pool space to be used by a server. | pd_lck_pool_size |
Specifies the amount of lock pool to be used by a front-end server. | pd_fes_lck_pool_size |
Specifies the number of resources to be locked for the tables and RDAREAs that are to be held across transactions. | pd_lck_until_disconnect_cnt |
Specifies the maximum number of holdable cursors that can be concurrently open for each transaction when holdable cursors are used for a table for which a LOCK statement with UNTIL DISCONNECT specification is not executed. | pd_max_open_holdable_cursors |
Specifies the number of hash table entries to be used in the lock pool. | pd_lck_hash_entry |
Specifies the locking method for a B-tree index (whether or not "index key value no lock" is to be executed). | pd_indexlock_mode |
Specifies an interval for unlocking global buffers when global buffer locking occurs during synchronization point processing. | pd_dbsync_lck_release_count |
Operand explanation | Operand name |
---|---|
Specifies the size of the buffer area in which SQL objects are to be placed. | pd_sql_object_cache_size |
Specifies the size of the buffer for table definition information. | pd_table_def_cache_size |
Specifies whether the control areas for the buffers for table definition information, buffers for view analysis information, buffers for user-defined type information, and buffers for routine definition information are to be allocated in a single batch at the time of HiRDB activation or in a single batch at the time of transaction activation. | pd_def_buf_control_area_assign |
Specifies the maximum stack size to be used by one thread. | pd_thred_max_stack_size |
Specifies the size of the buffer for user privilege information. | pd_auth_cache_size |
Specifies the size of the buffer for view analysis information. | pd_view_def_cache_size |
Specifies the size of the buffer for user-defined type information. | pd_type_def_cache_size |
Specifies the size of the buffer for routine definition information. | pd_routine_def_cache_size |
Specifies the size of a buffer to be used to store registry information. | pd_registry_cache_size |
Operand explanation | Operand name |
---|---|
Specifies the size of the shared memory to be used by a single server. | pd_sds_shmpool_size |
Specifies the size of the shared memory to be used by the dictionary server. | pd_dic_shmpool_size |
Specifies the size of the shared memory to be used by a back-end server. | pd_bes_shmpool_size |
Specifies the upper limit of the segment size for the shared memory for the global buffer pool. | SHMMAX |
Operand explanation | Operand name |
---|---|
Specifies the maximum number of RDAREAs allowed. | pd_max_rdarea_no |
Specifies the maximum number of HiRDB files that comprise an RDAREA. | pd_max_file_no |
Specifies the trigger for issuing a warning message (KFPH00211-I or KFPA12300-I) about the segment usage ratio. | pd_rdarea_warning_point |
Specifies whether to use the DEFER or SCHEDULE attribute as the RDAREA opening trigger. | pd_rdarea_open_attribute _use |
Specifies the standard value for the RDAREA opening trigger attribute. | pd_rdarea_open_attribute |
Specifies whether to use a shared RDAREA. | pd_shared_rdarea_use |
Operand explanation | Operand name |
---|---|
Specifies the LRU management method for the global buffer. | pd_dbbuff_lru_option |
Specifies whether to dynamically modify the global buffer. | pd_dbbuff_modify |
Specifies the method of detecting lock release of the global buffer. | pd_dbbuff_lock_release_detect |
Specifies the number of spins during lock acquisition wait processing for the global buffer. | pd_dbbuff_lock_spn_count |
Specifies the interval during lock acquisition wait processing for the global buffer. | pd_dbbuff_lock_interval |
Specifies the interval at which to check the global buffer occupation state. | pd_dbbuff_wait_interval |
Specifies the maximum number of spin loops for global buffer occupation state checking. | pd_dbbuff_wait_spn_count |
Specifies the deferred write trigger event as a percentage of the updated buffers. | pd_dbbuff_rate_updpage |
Defines the RDAREAs to be allocated to a global buffer. | pdbuffer |
Specifies the maximum number of global buffers for dynamic addition. | pd_max_add_dbbuff_no |
Specifies the maximum number of shared memory segments for dynamic addition. | pd_max_add_dbbuff_shm_no |
Operand explanation | Operand name |
---|---|
Specifies the minimum guaranteed value for the table reservation count. | pd_assurance_table_no |
Specifies the guaranteed minimum number of indexes. | pd_assurance_index_no |
Operand explanation | Operand name |
---|---|
Specifies whether to specify a constraint name definition before or after constraint definition in a referential constraint or check constraint. | pd_constraint_name |
Specified when a referential constraint or check constraint is used. | pd_check_pending |
Operand explanation | Operand name |
---|---|
Specifies whether or not to use a HiRDB file system area with a size of 2048 MB or greater. | pd_large_file_use |
Specifies whether or not to use the no-cache access method to access HiRDB file system areas. | pd_ntfs_cache_disable |
Operand explanation | Operand name |
---|---|
Specifies whether or not dual system log files are to be used. | pd_log_dual |
Specifies the processing to be performed by HiRDB when the available space in the system log file falls below the warning level (the facility for monitoring the free area for the system log file). | pd_log_remain_space_check |
Specifies as absolute pathnames the unload file output directories or HiRDB file system areas when the automatic log unloading facility is to be used for the system log. | pd_log_auto_unload_path |
Specifies whether or not single operation of the system log files is to be used. | pd_log_singleoperation |
Specifies whether or not a reserved file is to be used when none of the opened files can be used for swapping. | pd_log_rerun_reserved_file _open |
Specifies whether or not system log files are to be swapped during a restart. | pd_log_rerun_swap |
Specifies a wait time for swapping of system log files to be completed. | pd_log_swap_timeout |
Specifies whether or not the unload status of system log files is to be checked. If unload status checking is not performed, system log information is not available for database recovery. | pd_log_unload_check |
Specifies the size of the buffer to be used for system log input/output. | pd_log_max_data_size |
Specifies the number of buffer sectors to be used for system log output. | pd_log_write_buff_count |
Specifies the system log file record length. | pd_log_rec_leng |
Specifies the name of a file group for system log files. | pdlogadfg -d sys |
Specifies the name of the system log file to be allocated to a file group. | pdlogadpf -d sys |
Operand explanation | Operand name |
---|---|
Specifies whether to use dual synchronization point dump files. | pd_spd_dual |
Specifies whether or not a message is to be output when a synchronization point dump is completed. | pd_spd_assurance_msg |
Specifies the number of guaranteed valid generations. | pd_spd_assurance_count |
Specifies whether or not the reduced mode of operation is to be used. | pd_spd_reduced_mode |
Specifies whether or not a reserved file is to be opened automatically. | pd_spd_reserved_file_auto _open |
Specifies the size of the buffer to be used for synchronization point dump input/output. | pd_spd_max_data_size |
Specifies the synchronization point dump collection interval. | pd_log_sdinterval |
Specifies the name of a file group for a synchronization point dump file. | pdlogadfg -d spd |
Specifies the name of a synchronization point dump file to be allocated to a file group. | pdlogadpf -d spd |
Operand explanation | Operand name | |
---|---|---|
Unit status files | Specify the names of unit status files. | pd_syssts_file_name_1-7 |
Specifies the action to be taken when an error is detected in a unit status file during unit startup. | pd_syssts_initial_error | |
Specifies whether or not single operation of unit status files is to be used. | pd_syssts_singleoperation | |
Specifies the name of the unit status file to be used as the current file. | pd_syssts_last_active_file | |
During a restart, specifies the unit status file that was normal during the previous operation. | pd_syssts_last_active_side | |
Server status files | Specify the names of server status files. | pd_sts_file_name_1-7 |
Specifies the action to be taken when an error is detected in a server status file during server startup. | pd_sts_initial_error | |
Specifies whether or not single operation of server status files is to be used. | pd_sts_singleoperation | |
Specifies the name of the server status file to be used as the current file. | pd_sts_last_active_file | |
During a restart, specifies the server status file that was normal during the previous operation. | pd_sts_last_active_side |
Operand explanation | Operand name |
---|---|
Specifies a message log output destination unit. | pd_mlg_msg_log_unit |
Specifies the maximum size of the message log file. | pd_mlg_file_size |
Operand explanation | Operand name |
---|---|
Specifies whether or not collection of statistical information is to begin at the time of HiRDB startup. | pd_statistics |
Specifies the maximum size of the statistics log file. | pd_stj_file_size |
Specifies the statistics log buffer size. | pd_stj_buff_size |
Specifies the statistical information that is to be output, beginning at the time of HiRDB startup. | pdstbegin |
Specifies that collection of statistical information related to CONNECT and DISCONNECT is to begin at the time of HiRDB startup. | pdhibegin |
Operand explanation | Operand name |
---|---|
Specifies whether or not RPC trace information is to be collected. | pd_rpc_trace |
Specifies the name of the file in which RPC trace information is to be collected. | pd_rpc_trace_name |
Specifies the size of the file in which RPC trace information is to be collected. | pd_rpc_trace_size |
Operand explanation | Operand name |
---|---|
Specifies whether to output troubleshooting information. | pd_cancel_dump |
Specifies whether to collect the following types of troubleshooting information when the client maximum wait time (value of the PDCWAITTIME operand in the client environment definition) is exceeded during transaction execution. | pd_client_waittime_over_abort |
Specifies the amount of time during which to suppress re-outputting the troubleshooting information. | pd_dump_suppress_watch_time |
Specifies whether or not the network information portion of troubleshooting information is to be collected when a HiRDB process or HiRDB (unit) terminates abnormally. | pd_debug_info_netstat |
Specifies the interval at which to delete the troubleshooting information files (files under %PDDIR%\spool) and the temporary work files (files under %PDDIR%\tmp) that are output by HiRDB. | pd_spool_cleanup_interval |
Specifies the files to be deleted by the pd_spool_cleanup_interval operand. | pd_spool_cleanup_interval_level |
Specifies whether to delete during the startup of HiRDB the troubleshooting information files (files under %PDDIR%\spool) that are output by HiRDB. | pd_spool_cleanup |
Specifies the troubleshooting information files to be deleted by the pd_spool_cleanup operand. | pd_spool_cleanup_level |
Specifies the maximum number of module trace records to be stored. | pd_module_trace_max |
Specifies how to acquire the time to be output in module traces. | pd_module_trace_timer_level |
Operand explanation | Operand name |
---|---|
Specifies whether to use the BES connection holding facility. | pd_bes_connection_hold |
Specifies the BES connection holding period. | pd_bes_conn_hold_trn_interval |
Operand explanation | Operand name |
---|---|
Specifies whether to use the facility for predicting reorganization time. | pd_rorg_predict |
Operand explanation | Operand name |
---|---|
Specifies whether to begin collecting an audit trail when HiRDB (a unit for a HiRDB/Parallel Server) is started. | pd_audit |
Specifies an absolute path name for the name of the HiRDB file system area for an audit trail file. | pd_aud_file_name |
Specifies the maximum size (units: MB) for audit trail files. | pd_aud_max_generation_size |
Specifies the maximum number of (number of generations of) audit trail files to be created inside the HiRDB file system area for audit trail files. | pd_aud_max_generation_num |
Specifies the process to be performed by HiRDB when no swappable audit trail file is available. | pd_aud_no_standby_file_opr |
Specifies the size (units: bytes) of the buffer to be used for asynchronously outputting an audit trail. | pd_aud_async_buff_size |
Specifies the number of buffer sectors to be used for asynchronously outputting an audit trail. | pd_aud_async_buff_count |
Specifies the retry interval for monitoring for a buffer to be used for asynchronous output of an audit trail in order to acquire an audit trail when all buffers are in use. | pd_aud_async_buff_retry_intvl |
When the number of unswappable audit trail files reaches or exceeds the warning value, a warning message is issued. For this operand, specify the warning value as a percentage of the maximum audit trail file count specified in the pd_aud_max_generation_num operand. | pd_aud_file_wrn_pnt |
Specifies the buffer size to be used to store information for the security audit facility. | pd_audit_def_buffer_size |
Operand explanation | Operand name |
---|---|
Specifies whether or not the system switchover facility is to be used. | pd_ha |
Specifies whether or not IP addresses are to be inherited when the system switchover facility is used. | pd_ha_ipaddr_inherit |
Specifies that the system switchover facility is not to be applied to the unit. | pd_ha_unit |
Specifies whether to run the system switchover facility in the monitor mode or server mode. | pd_ha_acttype |
Specifies whether to use user server hot standby. | pd_ha_server_process_standby |
Specifies whether to use the rapid system switchover facility, standby-less system switchover (1:1) facility, or standby-less system switchover (effects distributed) facility. | pd_ha_agent |
Specifies the maximum number of guest BESs that operate as running systems inside the unit when the standby-less system switchover (effects distributed) facility is used. | pd_ha_max_act_guest_servers |
Specifies the maximum number of user server processes to be started inside a unit when the standby-less system switchover (effects distributed) facility is used. | pd_ha_max_server_process |
Specifies the combined total of the number of host BESs inside the unit and the number of resident processes for the guest BESs after these guest BESs have been accepted when the standby-less system switchover (effects distributed) facility is used. | pd_ha_process_count |
When the standby-less system switchover (effects distributed) facility is used, this operand specifies a maximum amount of time to wait until the running server's resources are activated at the time of unit startup. | pd_ha_resource_act_wait_time |
Specifies whether to use the transaction queuing facility. Also specifies the processing that takes place when the number of connections to the HiRDB server exceeds the maximum number of concurrent connections (value specified by the pd_max_users operand) during system switchover. | pd_ha_transaction |
Specifies the transaction queuing wait time when the transaction queuing facility is used. | pd_ha_trn_queuing_wait_time |
Specifies the upper limit for retrying transaction start requests after system switchover occurs and before the standby unit restarts. | pd_ha_trn_restart_retry_time |
Specifies whether to switch the system without waiting for internal termination processing of HiRDB when internal termination processing of HiRDB (or a unit for a HiRDB/Parallel Server) during system switchover has exceeded the server failure monitoring time. | pd_ha_switch_timeout |
Specifies whether to wait for the completion of start processing of other units before switching the system for the system manager unit. | pd_ha_mgr_rerun |
Defines an HA group. | pdhagroup |
Specifies that the system switchover facility is not to be applied to the unit. | pdunit |
Specifies the server machine to be used for executing the servers that comprise a HiRDB system and how each server machine is to be used. | pdstart |
Specifies the name of the standard host of the primary system. | pd_hostname |
Operand explanation | Operand name |
---|---|
Specifies whether or not the HiRDB Datareplicator linkage facility is to used from the time of HiRDB startup. | pd_rpl_init_start |
When the HiRDB Datareplicator linkage facility is used, this operand specifies the unit for applying transactions. | pd_rpl_reflect_mode |
Specifies the action to be taken when a swap request is received when not all of the system log files can be created at the swapping destination because system log extraction by HiRDB Datareplicator using the HiRDB Datareplicator linkage facility has not been completed. | pd_log_rpl_no_standby_file_opr |
Specifies the extracted side HiRDB Datareplicator directory when the HiRDB Datareplicator linkage facility is used. | pd_rpl_hdepath |
Operand explanation | Operand name |
---|---|
Specifies whether or not HiRDB events are to be registered into JP1. | pd_jp1_use |
Specifies the HiRDB event types that are to be registered into JP1. | pd_jp1_event_level |
Specifies whether to register message-outputting events into JP1. | pd_jp1_event_msg_out |
Operand explanation | Operand name |
---|---|
Specifies that the Directory Server linkage facility is to be used. | pd_directory_server |
Operand explanation | Operand name |
---|---|
Specifies the maximum number of foreign servers that can be connected. | pd_max_foreign_server |
Specifies the path name for a foreign server client library. | pd_foreign_server_libpath |
Specifies the foreign server to which the Hub optimization information definition is applied. | pdhubopt |
Defines the execution environment for the HiRDB External Data Access facility. | Foreign server information definition |
Defines whether to use a foreign server to execute each syntax of the input query. Also defines the values of the parameters necessary for cost expression computation. | Hub optimization information definition |
Operand explanation | Operand name |
---|---|
Specifies whether to use the holdable cursor facility in a UAP under the OLTP environment. | pd_oltp_holdcr |
Operand explanation | Operand name |
---|---|
Specifies the time zone. | TZ |
Operand explanation | Operand name |
---|---|
Controls whether to allow HiRDB to output messages in the event log. | pdmlgput |
Operand explanation | Operand name |
---|---|
Specifies the number of users who are guaranteed connection when the connection frame guarantee facility for a client group is used. | pdcltgrp |
Operand explanation | Operand name |
---|---|
Specifies the name of a plug-in to be used. | pdplugin |
Specifies the size of the shared memory to be used by a plug-in. | pdplgprm |
Specifies the directory in which the index information file is to be created when delayed batch creation of plug-in indexes is to be performed. | pd_plugin_ixmk_dir |
Operand explanation | Operand name |
---|---|
Specifies whether or not the pdvrup command for executing HiRDB version upgrading is to be started automatically. | pd_auto_vrup |
Specifies whether to keep the default values of the system definition operands of HiRDB Version 6 or earlier. | pd_sysdef_default_option |
Operand explanation | Operand name |
---|---|
Specifies a port number unique within the host when using a client that uses the high-speed connection facility. | pd_service_port |
Specifies the network to be used by the HiRDB server to communicate with HiRDB clients. | pd_change_clt_ipaddr |
Specifies the range of port numbers to be used for communication by the HiRDB server. | pd_registered_port |
Specifies whether or not checking is to be performed for overlapping port numbers in the ranges of port numbers specified in the pd_registered_port operand and in the port numbers registered in %windir%\system32\drivers\etc\services. | pd_registered_port_check |
Specifies a target range for the HiRDB reserved port facility. | pd_registered_port_level |
Specifies the number of times process-to-process communication can be attempted. | pd_ipc_send_retrycount |
Specifies the sleep time between process-to-process send retries. | pd_ipc_send_retrysleeptime |
Specifies the number of times server-to-server send can be performed before send is terminated. | pd_ipc_send_count |
Specifies the number of times server-to-server receive can be performed before receive is terminated. | pd_ipc_recv_count |
Specifies whether to establish connection in the non-block mode for HiRDB server-to-server communication (communication between units). | pd_ipc_conn_nblock |
Specifies whether or not connection is to be established in the non-block mode for HiRDB server-to-server communication (communication between units). | pd_ipc_conn_nblock_time |
Specifies the retry interval for establishing connection for sending data. | pd_ipc_conn_interval |
Specifies the number of retries for establishing connection for sending data. | pd_ipc_conn_count |
Specifies the maximum size for the send/receive buffer to be used for unit-to-unit communication within a server (TCP INET domain). | pd_ipc_inet_bufsize |
Specifies the maximum size for the send/receive buffer to be used for communication with a HiRDB client connected from outside the host where the HiRDB server resides (TCP INET domain). | pd_tcp_inet_bufsize |
Specifies the size of the communication buffer used by utility processes. | pd_utl_buff_size |
Specifies the size of the communication buffer used for transferring retrieved data among HiRDB servers. | pd_sql_send_buff_size |
Operand explanation | Operand name |
---|---|
Specifies Java virtual option startup options. | pd_java_option |
Specifies in bytes the stack size to be used by a Java routine. | pd_java_routine_stack_size |
Specifies the name of the directory for storing JAR files used by Java stored procedures or Java stored functions. | pd_java_archive_directory |
Specifies the class path to be used by a Java virtual machine. | pd_java_classpath |
Specifies the root directory of the Java Runtime Environment as an absolute pathname. | pd_java_runtimepath |
Specifies the directory that stores the library of the Java virtual machine as a relative pathname to the Java Runtime Environment root directory. | pd_java_libpath |
Specifies the file to which the standard output and standard error output are to be output in a Java virtual machine. | pd_java_stdout_file |
Operand explanation | Operand name |
---|---|
Specifies the condition for outputting SQL runtime warning information. | pd_cwaittime_wrn_pnt |
Specifies the output destination directory for the SQL runtime warning information file. | pd_cwaittime_report_dir |
Specifies the maximum size for the SQL runtime warning information file. | pd_cwaittime_report_size |
Operand explanation | Operand name |
---|---|
Specifies the action to be taken by the UAP when the RDAREA or index to be accessed using a local buffer is being used by another user. | pd_uap_wait |
Specifies the local buffer used by a UAP. | pdlbuffer |
Operand explanation | Operand name |
---|---|
Specifies the maximum number of bytes to be used to represent a single character. | pd_substr_length |