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 |
Specifies an expansion unit name. | pd_system_expand_unit |
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 |
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 maximum amount of memory space that can be used by a server process. If the amount of memory being used by a server process exceeds the value specified here, that server process is terminated. | pd_svr_castoff_size |
Specifies the maximum number of files and pipes accessed by HiRDB processes. | pd_max_open_fds |
Specifies the number of processes necessary for asynchronous READ operations when using the asynchronous READ facility. For a HiRDB parallel server configuration, 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 |
Specifies the maximum number of times that abnormal termination can occur when HiRDB restart processing fails. | pd_term_watch_count |
Operand explanation | Operand name |
---|---|
Specifies whether 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 or other problems 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 |
Specifies whether, when HiRDB is started, to activate the post-processing process, which executes post-processing when a HiRDB process terminates abnormally. | pd_process_terminator |
Specifies the number of post-processing processes to be started when starting HiRDB. | pd_process_terminator_max |
Specifies a thread lock release notification method. | pd_thdlock_wakeup_lock |
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 the error messages output when a server process is forcibly terminated are to be changed. | pd_cancel_down_msgchange |
Operand explanation | Operand name |
---|---|
Specifies the number of processes to be recovered (REDO processes) during full recovery processing. For a HiRDB parallel server configuration, this operand specifies the number of processes to be recovered (REDO processes) 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 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 the transaction recovery message queue size. | pd_trn_rcvmsg_store_buflen |
Specifies whether to use one-phase commit in a HiRDB parallel server configuration's commitment control. | pd_trn_commit_optimize |
Specifies the maximum amount of time for the front-end server to wait to receive a rollback completion response from a transaction branch. This operand also specifies the period of time during which the resending of rollback instruction is to be repeated in the event of a communication error. | pd_trn_rollback_watch_time |
Operand explanation | Operand name |
---|---|
Specifies whether errors are to be suppressed during operation. | pd_overflow_suppress |
Specifies a space conversion level when the space configuration facility is used. | pd_space_level |
Specifies whether the facility for conversion to a DECIMAL signed normalized number is to be used. | pd_dec_sign_normalize |
Specifies the maximum precision for the operation result in the case of a DECIMAL type operation result of no more than 29 digits. | pd_sql_dec_op_maxprec |
Specifies whether to allow the set operator MINUS in SQL statements. | pd_sql_mode |
Operand explanation | Operand name |
---|---|
Specifies SQL optimization options. | pd_optimize_level |
Specifies SQL extension optimizing options. | pd_additional_optimize_level |
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 a client error log file or 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 authorization identifiers that can use the SQL CALL COMMAND statement to execute commands and utilities. | pd_sql_command_exec_users |
Operand explanation | Operand name |
---|---|
Specifies whether to output detailed SQLSTATE values. | pd_standard_sqlstate |
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 (in minutes) for monitoring the execution time of the following utilities:
| pd_utl_exec_time |
Specifies the monitoring time (in minutes) for monitoring the execution time of operation commands and utilities. This operand can monitor more commands and utilities than those monitored by the pd_utl_exec_time operand. | pd_cmd_exec_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 |
Specifies the process allocation wait time during execution of operation commands and utilities. | pd_cmd_process_conwaittime |
If abnormal terminations of server processes exceed the value specified in this operand, HiRDB (applicable unit for a HiRDB parallel server configuration) terminates abnormally (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 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 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 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 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 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 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 lock pool partitions that are to be used per server for distributing lock processing. | pd_lck_pool_partition |
Specifies the number of lock pool partitions that are to be used per front-end server for distributing lock processing. | pd_fes_lck_pool_partition |
Specifies the number of tables and RDAREAs to be held across transactions and the number of resources to be locked for inner replica configuration management and replica group configuration management. | 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 index key value no lock is to be executed). | pd_indexlock_mode |
Specifies the lock release wait control mode for uncommitted delete data. | pd_lock_uncommited_delete_data |
Specifies whether row identifiers are to be reused when row data is inserted. | pd_dbreuse_remaining_entries |
Specifies whether to check for deadlocks. | pd_lck_deadlock_check |
Specifies the interval between checks for deadlocks. | pd_lck_deadlock_check_interval |
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 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_thread_max_stack_size |
Specifies the stack extension size per thread. | pd_thread_stack_expand_size |
Specifies the size of the buffer for table definition information. | pd_table_def_cache_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 whether the shared memory to be used by the HiRDB is to be fixed in the memory. | pd_shmpool_attribute |
Specifies the control method for shared memory used by HiRDB. | pd_shmpool_control |
Specifies whether the shared memory to be used by the global buffer is to be fixed in the real memory. | pd_dbbuff_attribute |
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 triggers for issuing a warning message (KFPH00211-I or KFPA12300-I) about RDAREA segment usage or about area usage by a HiRDB file that is being extended (KFPH22037-W). | pd_rdarea_warning_point |
Specifies whether to issue an RDAREA segment usage warning message (KFPH00211-I or KFPA12300-I). | pd_rdarea_warning_point_msgout |
Specifies when to automatically extend an RDAREA (the trigger) when the RDAREA auto-extension facility is being used. | pd_rdarea_extension_timing |
Specifies whether to initialize the extended area when an RDAREA is extended automatically. | pd_rdarea_expand_format |
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 |
Specifies the action when a file access error occurs while accessing an RDAREA. | pd_db_access_error_action |
Specifies the action to be taken when a physical error (input/output error or file open error) occurs while accessing an RDAREA. | pd_db_hold_action |
Operand explanation | Operand name |
---|---|
Specifies the LRU management method for the global buffer. | pd_dbbuff_lru_option |
Specifies whether to use LRU management for global buffers when executing a UAP that accesses a column for which BINARY type was specified. | pd_dbbuff_binary_data_lru |
Specifies whether to dynamically modify the global buffer. | pd_dbbuff_modify |
Specifies the deferred write trigger event as a percentage of the updated buffers. | pd_dbbuff_rate_updpage |
Specifies the acquisition level for database buffer control information traces. | pd_dbbuff_trace_level |
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 maximum number of in-memory RDAREAs. | pd_max_resident_rdarea_no |
Specifies the maximum number of shared memory segments used by an in-memory data buffer. | pd_max_resident_rdarea_shm_no |
Operand explanation | Operand name |
---|---|
Specifies the number of tables that can use the free space reusage facility. | pd_assurance_table_no |
Specifies the number of indexes that can be used. | 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 the maximum number of temporary tables and temporary table indexes that can be used at any one time for each server. | pd_max_temporary_object_no |
Specifies to change when temporary table RDAREAs are initialized to a time other than when HiRDB starts. | pd_tmp_table_initialize_timing |
Operand explanation | Operand name |
---|---|
Specifies whether dual system log files are to be used. | pd_log_dual |
Specifies whether to use the facility for parallel output of system logs. | pd_log_dual_write_method |
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 path names 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 the automatic log unloading facility is to be restarted when the system log files are swapped following the issuance of s message indicating that the automatic log unloading facility stopped due to an error (message KFPS01150-E). | pd_log_auto_unload_restart |
Specifies whether single operation of the system log files is to be used. | pd_log_singleoperation |
Specifies whether 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 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 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 number of buffer sectors to be used for system log output. | pd_log_write_buff_count |
Specifies the number of records to be added to a system log file each time extension is triggered and an upper limit for extending the file size. | pd_log_auto_expand_size |
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 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 the reduced mode of operation is to be used. | pd_spd_reduced_mode |
Specifies whether 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 |
Specifies a group name for synchronization point dump files for log application processing. | pdlogadfg -d ssp |
Specifies a synchronization point dump file for log application processing that is to be allocated to a file group. | pdlogadpf -d ssp |
Operand explanation | Operand name |
---|---|
Specify the names of unit status files. | pd_syssts_file_name_1-7 |
Specify the names of unit duplicate status file. | pd_syssts_subfile_name_1-7 |
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 |
Specifies the name of the unit duplicate status file to be used as the current file. | pd_syssts_last_active_subfile |
During a restart, specifies the unit duplicate status file that was normal during the previous operation. | pd_syssts_last_active_side_sub |
Specify the names of server status files. | pd_sts_file_name_1-7 |
Specify the names of server duplicate status file. | pd_sts_subfile_name_1-7 |
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 |
Specifies the name of the server duplicate status file to be used as the current file. | pd_sts_last_active_subfile |
During a restart, specifies the server duplicate status file that was normal during the previous operation. | pd_sts_last_active_side_sub |
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 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 timing for collecting statistics on an SQL object buffer. | pd_sqlobject_stat_timing |
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 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 performance trace information is to be collected. | pd_prf_trace |
Specifies the performance trace information collection level. | pd_prf_level |
Specifies the number of performance trace information file generations. | pd_prf_file_count |
Specifies the size of each performance trace information file. | pd_prf_file_size |
Specifies the directory to which performance traces are output. | pd_prf_output_directory |
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 whether to limit the units for which a shared memory dump can be output. This is the dump that is output during transaction execution when the client's maximum wait time (the value of the PDCWAITTIME operand in the client environment definition) is exceeded. | pd_clt_waittime_over_dump_level |
Specifies the amount of time during which to suppress re-outputting the troubleshooting information. | pd_dump_suppress_watch_time |
Specifies whether 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 |
Specifies the maximum number of communication traces to be stored. | pd_pth_trace_max |
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 configuration) 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 (in megabytes) 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 (in 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 |
Specifies the size in bytes of SQL statement output to the audit trail when the security audit facility is being used. | pd_aud_sql_source_size |
Specifies the size in bytes of SQL data output to the audit trail when the security audit facility is being used. | pd_aud_sql_data_size |
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 whether the facility for automatically loading audit trail table data is to be used. | pd_aud_auto_loading |
Defines environment information for the database creation utility (pdload) activated by the facility for automatically loading audit trail table data. | pdaudload |
Specifies the buffer size to be used to store information for the security audit facility. | pd_audit_def_buffer_size |
Specifies all host names used on the network that constitutes the HiRDB server. | pd_security_host_group |
Operand explanation | Operand name |
---|---|
Specifies whether the system switchover facility is to be used. | pd_ha |
Specifies whether 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 the absolute path name of the command to be executed when HiRDB restart fails. | pd_ha_restart_failure |
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 |
Specifies a maximum amount of time to wait until the running server's resources are activated at the time of unit startup when the standby-less system switchover (effects distributed) facility is used. | 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 configuration) during system switchover has exceeded the server failure monitoring time. | pd_ha_switch_timeout |
When the server-mode system switchover facility is used, this operand specifies whether system switchover processing is to be placed on hold until all server processes subject to switchover have terminated. | pd_ha_prc_cleanup_check |
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 the HiRDB Datareplicator linkage facility is to used from the time of HiRDB startup. | pd_rpl_init_start |
Specifies the unit for applying transactions when the HiRDB Datareplicator linkage facility is used. | 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 |
Specifies the facility to be run by the source HiRDB when the HiRDB Datareplicator linkage facility is used. | pd_rpl_func_control |
Operand explanation | Operand name |
---|---|
Specifies whether 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 whether to use Real Time SAN Replication. | pd_rise_use |
Selects a Real Time SAN Replication processing method. | pd_rise_pairvolume_combination |
Specifies whether to maintain data matching by establishing synchronization between the main site and the remote site when the hybrid method is selected for the Real Time SAN Replication processing method. | pd_rise_disaster_mode |
Specifies the action to be taken when an attempt to update a volume located at a remote site by synchronously copying data fails because of an error when the synchronous method or the hybrid method is selected for the Real Time SAN Replication processing method. | pd_rise_fence_level |
Specifies the instance number of the RAID Manager that defines the pair logical volume to be used by HiRDB. | HORCMINST |
Operand explanation | Operand name |
---|---|
Specifies the maximum number of inner replica groups. | pd_inner_replica_control |
Specifies whether to permit concurrent execution of a UAP and commands when the inner replica facility is used. | pd_inner_replica_lock_shift |
Specifies whether to use the mirror facility of Logical Volume Manager (LVM) to run the replica RDAREA. | pd_lv_mirror_use |
Specifies whether replica RDAREAs with the DEFER or SCHEDULE attribute are to be placed on command hold when HiRDB starts normally. | pd_inner_replica_hold_status |
Specifies the number of processes to be used for reflection processing. | pd_max_reflect_process_count |
Specifies whether to change the status of the system log file for which reflection processing has been completed. | pd_log_org_reflected_logpoint |
Specifies the processing for HiRDB when system log file swapping occurs while all system log files are in the overwriting denied status for online reorganization. | pd_log_org_no_standby_file_opr |
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 |
---|---|
Specifies whether to enable the facility for simple authentication of OS login users. | pd_os_authenticate |
Operand explanation | Operand name |
---|---|
Controls output, suppresses output, or changes the priority of messages that HiRDB outputs to syslogfile. | pdmlgput |
Operand explanation | Operand name |
---|---|
Specifies the name of the directory that is to be shared when sharing of HiRDB system definition files is in effect. | PDCONFPATH |
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 the pdvrup command for executing HiRDB version upgrading is to be started automatically. | pd_auto_vrup |
Operand explanation | Operand name |
---|---|
Specifies the port number for the scheduler process. | pd_service_port |
Specifies how addresses are to be resolved in communication between units that is handled by the system server. | pd_name_fixed_port_lookup |
Specifies the port number of the scheduler process when Y is specified in the pd_name_fixed_port_lookup operand. | pd_scd_port |
Specifies the port number of the transaction server process when Y is specified in the pd_name_fixed_port_lookup operand. | pd_trn_port |
Specifies the port number of the message log server process when Y is specified in the pd_name_fixed_port_lookup operand. | pd_mlg_port |
Specifies the port number of the unit monitoring process when Y is specified in the pd_name_fixed_port_lookup operand. | pd_alv_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 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 /etc/services. | pd_registered_port_check |
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 connections in the non-block mode for HiRDB server-to-server communication (communication between units). | pd_ipc_conn_nblock |
Specifies the retry interval and monitoring time when establishing a connection in the non-block mode for HiRDB server-to-server communication (communication between units). | pd_ipc_conn_nblock_time |
Specifies the retry interval when establishing a connection for sending data between HiRDB servers. | pd_ipc_conn_interval |
Specifies the number of retries when establishing a connection for sending data between HiRDB servers. | pd_ipc_conn_count |
Specifies whether to establish connections in the non-block mode for communication with HiRDB clients. | pd_ipc_clt_conn_nblock |
Specifies the monitoring interval when establishing a connection with a HiRDB client in the non-block mode. | pd_ipc_clt_conn_nblock_time |
Operand explanation | Operand name |
---|---|
Specifies Java virtual option startup options. | pd_java_option |
Specifies in bytes the stack size to be used by an external 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 path name. | pd_java_runtimepath |
Specifies the directory that stores the library of the Java virtual machine as a relative path name 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 |
Specifies whether to shut down the process that started the Java Virtual Machine at particular triggers. | pd_java_castoff |
Operand explanation | Operand name |
---|---|
Specifies the directory that stores the C library files used by external C stored routines. | pd_c_library_directory |
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 |
Operand explanation | Operand name |
---|---|
Specifies the target directory to which HiRDB is to output work files. | pd_tmp_directory |