2.3.5 Operands related to HiRDB processing

15) pd_dbsync_point = sync | commit
Specifies the timing for committing database updates to the file.
sync:
Commit database updates to the file at each synchronization point. This option enhances performance when a large number of transactions that update the same page occur between synchronization points. Because update information is not committed to the file when a COMMIT statement is issued, the input/output workload is reduced. Note that full recovery processing is slower than when commit is specified.
commit:
Commit database updates to the file when a COMMIT statement is issued. Because the database contents are guaranteed when the transaction is completed, there is no need to recover transaction processing from a synchronization point, thus reducing the time required for a full recovery. However, if a large number of transactions that update the same page occur between synchronization points, this option is slower than when the sync option is specified.
Remarks
A LOB RDAREA is not affected by this operand. Directories are updated when the COMMIT statement is issued. Whether or not data is updated depends on whether a LOB global buffer has been allocated. If no LOB global buffer has been allocated, data is instantly updated when an update request is issued. If a LOB global buffer has been allocated, data is updated when the COMMIT statement is issued. However, if the global buffer becomes full, data is updated at that time.
Relationship to other operands
This operand is related to the pd_system_dbsync_point operand.
16) pd_system_dbsync_point = sync | commit
Specifies the timing for committing to file updates in the following types of RDAREAs:
  • Master directory RDAREA
  • Data directory RDAREA
  • Data dictionary RDAREAs
  • Data dictionary LOB RDAREAs
  • Registry RDAREAs
  • Registry LOB RDAREAs
sync:
Commit RDAREA updates to the file at each synchronization point. Because update information is not committed to the file when a COMMIT statement is issued, the processing performance of a definition SQL is slightly better than when the commit option is specified. However, full recovery processing is slower than when the commit option is specified.
commit:
Commit to file updates to the indicated types of RDAREAs when a COMMIT statement is issued. Because the contents of updates to the indicated types of RDAREAs are guaranteed when the transaction is completed, there is no need to recover these types of RDAREAs from a synchronization point, thus reducing the time required for a full recovery. However, the processing performance of a definition SQL is slightly lower than when sync is specified.
Relationship to other operands
This operand is related to the pd_dbsync_point operand. The following table shows the relationship to the pd_dbsync_point operand:
pd_dbsync_point specificationpd_system_dbsync_point specification
synccommit (default)
sync (default)Commits updates to all RDAREAs at a synchronization point.Commits updates to the indicated types of RDAREAs when a COMMIT statement is issued. Commits updates to other types of RDAREAs at a synchronization point.
commitCommits updates to all RDAREAs when a COMMIT statement is issued.
17) pd_dbsync_altwrite_skip = Y | N
Specifies the handling of the write processing when an update buffer reference request is issued during synchronization point acquisition processing. Normally, such write processing of the update buffer contents into the database is handled by the transaction process that issues the reference request. This operand specifies whether or not the handling of this write processing is to be skipped.
The following compares the values of this operand.
Comparison itempd_dbsync_altwrite_skip operand value
YN (default value)
Database writing method when an update buffer reference request is issued during synchronization point acquisition processingThe transaction process that issued the reference request does not handle the writing of the update buffer contents into the database (the handling is skipped).The transaction process that issued the reference request handles the writing of the update buffer contents into the database (the handling is not skipped).
AdvantageBecause the transaction process does not handle the write processing, the performance of the referencing transaction is stable during synchronization point acquisition processing.The amount of time required for synchronization point acquisition processing is reduced because some of the workload is distributed to the referencing transaction.
DisadvantageThe amount of time required for synchronization point acquisition processing increases because none of the workload is distributed to the referencing transaction.There may be adverse effects on the referencing transaction during synchronization point acquisition processing.
Specification guidelines
You can execute the statistics analysis utility to obtain statistical information on the global buffer pool in order to check the database write processing take-over count (ALTRW) due to reference request hits during synchronization point processing. If this value is large, performance of a referencing transaction is not stable during synchronization point acquisition processing. To achieve stable performance, specify Y. Note that when Y is specified, more time is required for synchronization point acquisition processing; if necessary, you can use the facility for parallel writes in deferred write processing to distribute the write processing workload.
18) pd_overflow_suppress = Y | N
Specifies whether or not error suppression is to be implemented during computations. The following types of errors can be suppressed:
  • Overflow in the middle of a computation
  • Division by 0 errors
Y:
If an applicable error occurs in a computation during SQL execution, convert the computation result to the null value and continue the processing.
N:
If an applicable error occurs in a computation during SQL execution, cancel the process with an error.
19) pd_process_terminator = resident | fixed | nonresident
If a HiRDB process is abnormally terminated, HiRDB starts a process that executes post-processing. This operand specifies whether the post-processing process is activated when HiRDB is started.
resident:
This option starts a single post-processing process when starting HiRDB. For a HiRDB/Parallel Server, a post-processing process is started in each unit.
If multiple processes are abnormally terminated at the same time, post-processing processes up to the number specified by HiRDB are started and executed in parallel. If a new post-processing process cannot be started due to memory shortage, for example, post-processing is sequentially performed using the post-processing processes that are already active.
fixed:
When starting HiRDB, this option starts the number of post-processing processes specified by the pd_process_terminator_max operand. For a HiRDB/Parallel Server, the number of post-processing processes specified by the pd_process_terminator_max operand are started in each unit. If post-processing processes cannot be started due to memory shortage, for example, HiRDB (or the applicable unit for a HiRDB/Parallel Server) is not started.
If a number of processes exceeding the value specified in the pd_process_terminator_max operand are abnormally terminated at the same time, no additional post-processing processes are started. In this case, post-processing is sequentially performed using the post-processing processes that are already active.
nonresident:
This option does not start any post-processing process when starting HiRDB. A post-processing process is started whenever a process is abnormally terminated.
If multiple processes are abnormally terminated at the same time, post-processing processes are simultaneously started and executed in parallel. If post-processing processes cannot be started due to memory shortage, for example, HiRDB (or the applicable unit for a HiRDB/Parallel Server) may be abnormally terminated in some cases.
Specification guidelines
  • To improve reliability, specify resident or fixed. Although fixed provides higher post-processing performance than resident, fixed requires more memory.
  • When nonresident is specified, post-processing processes are started on demand. Consequently, post-processing processes cannot be started if memory shortage occurs. Furthermore, if multiple processes are abnormally terminated at the same time, multiple post-processing processes are started, resulting in performance degradation.
Note
You must be careful when changing the specification value to fixed. Because this option starts post-processing processes when starting HiRDB, it requires more memory. If memory shortage, for example, prevents post-processing processes from being started, HiRDB (or the applicable unit for a HiRDB/Parallel Server) cannot start.
20) pd_process_terminator_max = maximum-number-of-resident-post-processing-processes
[Figure]<unsigned-integer>((1-100)) << (3, [Figure](value of pd_max_users/100[Figure])>>
Specify this operand if you have omitted the pd_process_terminator operand or specified fixed or it. Specify for the pd_process_terminator_max operand the number of post-processing processes to be started when starting HiRDB. If memory shortage, for example, prevents the specified number of post-processing processes from being started, HiRDB (or the applicable unit for a HiRDB/Parallel Server) cannot start.
Specification guidelines
The number of post-processing processes needed is proportional to the value of pd_max_users. Take this into consideration when determining a value for the pd_process_terminator_max operand.
Relationship to other operands
If v6compatible or v7compatible is specified in the pd_sysdef_default_option operand, the default value for this operand is as follows:
[Figure]value of pd_max_users/100[Figure]
21) pd_space_level = 0 | 1 | 3
Specifies the applicable space conversion level when the space configuration facility is used. For details about the space conversion facility, see the HiRDB Version 8 System Operation Guide.
0: Use space conversion level 0.
1: Use space conversion level 1.
3: Use space conversion level 3.
The following table explains the space conversion levels.
LevelExplanation
Level 0No space conversion.
Level 1Converts spaces in literals, embedded variables, and ? parameter data in a data
manipulation SQL as follows:
  • If a character string literal is considered a national character string literal, two single-byte spaces are converted into a double-byte space. If a single-byte space appears by itself, it is not converted.
  • If a character string literal is considered a mixed character string literal, a double-byte space is converted into two single-byte spaces.
  • When data is being stored into a national character string-type string or is being compared with a national character string-type value expression, two single-byte spaces in an embedded variable or ? parameter are converted into a double-byte space. If a single-byte space appears by itself, it is not converted.
  • When data is being stored into a mixed character string-type string or is being compared with a mixed character string-type value expression, a double-byte space in an embedded variable or ? parameter is converted into two single-byte spaces.
Level 3The following processing is performed, in addition to the processing in Level 1:
  • When data of a national character string-type value expression is being retrieved, a double-byte space is converted into two single-byte spaces.
Notes
  • When the space conversion level is changed, there may be differences in UAP results before and after the change. To ensure that UAP results remain the same, the space conversion level should not be changed.
  • When sorting is performed with the space conversion level set to 3, HiRDB performs space conversion on the sorting results, which may produce unexpected results.
  • When data is being stored in a cluster key string, space conversion may cause a uniqueness error. In such a case, either store the data without space conversion or use the database reorganization utility to standardize the spaces in the existing database.
  • Spaces in a national character string are converted in units of two characters from the beginning of the string.
  • The following should be noted when 1 or 3 is specified for the space conversion level:
    When a storage RDAREA is determined in the case of a UAP that uses a hash function for table partitioning from a hash-partitioned table, it is necessary to specify a space conversion level in the argument of the hash function for table partitioning. If no level is specified, the result of the hash function for table partitioning may be incorrect.
    When a UAP is used to execute key range partitioning on a table that has been key range-partitioned (partitioning key is national character data or mixed character data), the partitioning key must be converted with the space conversion function. Otherwise, the result of key range partitioning may be incorrect.
    For details about the hash functions for table partitioning and the space conversion function, see the HiRDB Version 8 UAP Development Guide.
Relationship to client environment definition
The value of this operand can be different for each client. To change the operand for a client, specify the PDSPACELVL operand in the client environment definition.
For details about the PDSPACELVL operand, see the HiRDB Version 8 UAP Development Guide.
22) pd_dec_sign_normalize = Y | N
Specifies whether or not the sign of signed packed data transferred from a UAP is to be normalized (i.e., specifies whether or not the facility for conversion to a DECIMAL signed normalized number is to be used).Normalizing the sign means converting the sign A-F of signed packed data to C or D. For details about the facility for conversion to a DECIMAL signed normalized number, see the HiRDB Version 8 System Operation Guide.
Y:
Use the facility for conversion to a DECIMAL signed normalized number. The sign of signed packed data is normalized. A-F are considered to be DECIMAL data signs.
N:
Do not use the facility for conversion to a DECIMAL signed normalized number. The sign of signed packed data is not normalized. C, D, and F are considered to be DECIMAL data signs.
Notes
The following must be noted when Y is specified (i.e., when the facility for conversion to a DECIMAL signed normalized number is to be used):
  • For determining the storage RDAREA for a hash-partitioned table in the case of a UAP that uses the hash function for table partitioning, it is necessary to specify "Use the facility for conversion to a DECIMAL signed normalized number" as an argument of the hash function for table partitioning. If this is not specified, the result of the hash function for table partitioning may be corrupted.
  • When a UAP is used to execute key range partitioning for a key range-partitioned table (for data whose partitioning key is DECIMAL), the partitioning key value must be converted using the facility for conversion to a DECIMAL signed normalized number. Otherwise, the result of the key range partitioning may be corrupted.
For details about the hash functions for table partitioning and the facility for conversion to a DECIMAL signed normalized number, see the HiRDB Version 8 UAP Development Guide.
23) pd_server_entry_queue = spnfifo | fifo | loop
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. Note that process contention in this case means that multiple processes are simultaneously trying to lock internal resources, such as tables and RDAREAs, when transactions are running on the HiRDB server process. Only a single process is allowed to lock internal resources at any point in time. Spin, referred to in the following explanation means a process for acquiring the right to execute a lock. When another process releases the right to execute a lock, a process that is spinning has a higher probability of acquiring the right to execute a lock.
spnfifo:
A processing request that occurs first is given higher priority. However, because the process is spun a certain number of times before being registered in a queue, the priority order is not perfect. This method is used in Version 06-00 and older versions.
fifo:
A processing request that occurs first is given higher priority than when spnfifo is specified. Because no spinning occurs before a process is registered in a queue, the priority order is maintained better than when spnfifo is specified. This method also reduces the CPU load.
loop:
All processing requests are given the same priority. When processes are registered in a queue, they are spun at high speed. Specifying loop may improve the response during concurrent execution of UAPs. However, this method places a greater load on the CPU than other methods.
Specification guidelines
Normally, you need not specify this operand.
Change the specification value if the processing performance during concurrent execution of UAPs does not improve. Doing so may improve the performance.
24) pd_thdlock_sleep_func = 0 | 1
Specifies the type of sleep function (for waiting for a specified amount of time) to be used when acquiring a lock on shared resources, such as shared memory. The following table shows the relationship between the value specified by this operand and the characteristics of the function issued by HiRDB.
pd_thdlock_sleep_func
operand value
Characteristics of the function issued by HiRDB
Process switchover rateCPU usage
0LowLow
1HighHigh
Specification guidelines
  • Normally, you need not specify this operand.
  • Change the specification value of this operand if the concurrent execution performance of UAPs is significantly worse than stand-alone performance. Doing so may improve the performance.
  • Whether 0 or 1 produces better performance depends on the OS type, machine performance, disk performance, UAP details, and the number of UAPs being concurrently executed. However, specifying 0 usually produces relatively stable performance.
Notes
If you change the specification value of this operand from 0 to 1, the CPU usage may increase, resulting in performance degradation in some cases.
Relationship to other operands
Specification of this operand is invalid if a value greater than 10,000 is specified for the pd_thdlock_retry_time operand.
25) pd_thdlock_wakeup_lock = Y | N
Specifies a thread lock release notification method.
Y:
When issuing a thread lock release notification, a new separate lock is temporarily obtained. Because this temporary lock is obtained, reliable transmission of the release notification is guaranteed.
N:
When issuing a thread lock release notification, no new separate lock is temporarily obtained. When no temporary lock is obtained, a transaction may occur that has a longer execution time than other transactions. How much longer is determined by the value specified for the pd_thdlock_pipe_retry_interval operand.
Specification guideline
  1. The following table shows the effects of multiplexed transaction execution:
    Comparison itempd_thdlock_wakeup_lock operand value
    YN
    Difference in transaction execution timeReduces the difference.Increases the difference.
    Time required for the completion of all transactionsLengthensShortens
  2. The following table shows the recommended values of this operand:
    ConditionRecommended value
    When a new HiRDB is usedY
    When HiRDB is already being usedWhen the execution times of all transactions must be the same during multiplexed transaction executionY
    When some differences in the execution times of all transactions are allowed during multiplexed transaction executionN
Relationship to other operands
If you specify N in this operand or you omit this operand, evaluate the specification of the pd_thdlock_pipe_retry_interval operand.
26) pd_thdlock_pipe_retry_interval = thread-lock-release-check-interval
[Figure]<unsigned integer>((0-2147483647))<<100000>>(microseconds)
Specifies the interval in microseconds at which to check for thread lock release. Specify this operand if pd_thdlock_wakeup_lock = N (default value) is specified. In all other cases, there is no need to specify this operand.
If multiple transactions are executed concurrently, differences occur in their execution times. The value specified for this operand provides an estimate for the maximum execution time difference (this value is not exact).
Specification guidelines
  • If this operand is to be specified, specify 1000 for it.
  • If the specification of 1000 increases the CPU usage rate too much, specify a greater value.
  • Even if you specify a value less than 1000, performance does not improve over a case in which 1000 is specified.
Note
If 0 is specified for this operand, release check is repeated within short intervals and may result in an extremely high CPU usage rate.
27) pd_thdlock_retry_time = thread-lock-sleep-time
[Figure]<unsigned integer>((1-1000000))<<10000>>(microseconds)
Specifies the thread lock sleep time in microseconds. If this operand is specified when all the conditions listed below are satisfied, the CPU usage rate may decrease. Otherwise, there is no need to specify this operand.
  • The CPU usage rate is very high.
  • Reducing the CPU usage rate is necessary even if it results in a reduction in performance.
  • 0 is specified for the pd_thdlock_sleep_func operand.
The following describes the HiRDB processing based on the combination of the pd_thdlock_sleep_func and the pd_thdlock_retry_time operand values:
pd_thdlock_sleep_func operand valuepd_thdlock_retry_time operand value
1 to 1000010001 to 1000000​
0Each process stands by for the thread lock sleep time specified by select() or Sleep().
1The OS determines process allocation using sched_yield() or SwitchToThread() (the pd_thdlock_retry_time operand value is ignored).Each process stands by for the thread lock sleep time specified by select() or Sleep().
Specification guidelines
  • If this operand is to be specified, begin specify 10000 for it.
  • If the specification of 10000 increases the CPU usage rate too much, specify a greater value.
  • If there is an ample margin in the CPU usage rate, specify a value less than 10000.
Notes
  • Reducing the value may not change the performance.
  • Specifying 1000 or a greater value may have an adverse effect on performance.
Relationship to other operands
If v6compatible is v7compatible is specified in the pd_sysdef_default_option operand, the default value for this operand is 10000.
28) pd_thdspnlk_spn_count = thread-spin-lock-spin-count
[Figure]<unsigned integer>((0-2147483647))<<512>>
Specifies a spin count for thread spin lock. Specifying this operand when all of the following conditions are satisfied may improve the system performance. Otherwise, there is no need to specify this operand.
  • An ample margin exists in the CPU usage rate.
  • You want to improve performance, even if the CPU usage rate must be increased.
Specification guidelines
  • If this operand is to be specified, specify a value that is greater than the default value (512).
  • Because the specification value depends on the OS type, the processor type, the machine performance, the disk performance, the UAP content, and the number of UAPs concurrently being executed, there is no clear guideline. Determine an appropriate value by varying the specification value and measuring the performance.
Notes
  • If the value of this operand is too large, the CPU usage rate may increase, causing problems such as slower OS operation. In this case, decrease the operand value.
  • Increasing the value of this operand may not always improve performance.
29) pd_pageaccess_mode = SNAPSHOT | NORMAL
Specifies the page access mode to be used for database search.
SNAPSHOT:
Uses a snapshot mode for page access. When the global buffer is accessed for the first time, rows that match the search condition are copied to the process private memory. During the second search request, a search result is returned by referencing the process private memory. For details on the snapshot mode, see the HiRDB Version 8 Installation and Design Guide.
NORMAL:
Uses a normal mode for page access. The global buffer is accessed for each search request.
Specification guidelines
If facilities for improving performance, such as the rapid grouping facility, cannot be used, consider using the snapshot mode. In normal search-SQL, the global buffer is accessed roughly the same number of times as the number of rows that match the specified search condition. Consequently, if search-SQLs are concurrently executed, accesses to the global buffer become concentrated, and as a result, the expected performance may not be obtained. In this case, using the snapshot mode can reduce the number of accesses by search-SQLs to the global buffer, and thus may improve the performance. However, using the snapshot mode increases the size of the process private memory used by HiRDB. For the method of computing the size of process private memory when using the snapshot mode, see the HiRDB Version 8 Installation and Design Guide.
30) pd_cmdhold_precheck = Y | N
Specifies whether to check for RDAREA hold before locking the RDAREA.
Y:
Checks for RDAREA hold before locking the RDAREA.
N:
Does not check for RDAREA hold before locking the RDAREA. Checking is performed after locking.
The following hold types are checked:
  • Command hold
  • Reference-possible hold
  • Reference-possible backup hold
Specification guidelines
Normally, omit this operand or specify Y. The following table describes the differences between Y and N specifications.
ItemY specifiedN specified
Processing by HiRDBDuring UAP or command* execution, HiRDB checks the hold statuses of all RDAREAs that store the access target tables before locking the RDAREAs. For example, when accessing a table that is row-partitioned into RDAREAs 1 through 4, HiRDB checks the hold statuses of all these RDAREAs.During UAP or command* execution, HiRDB first locks RDAREAs and then checks the hold statuses of the access target RDAREA. For example, suppose that a table that is row-partitioned into RDAREAs 1 through 4 is to be accessed. If the target RDAREAs are narrowed using an index and if RDAREA 1 is to be accessed, HiRDB checks the hold status of RDAREA 1 only. This mode is used in HiRDB Version 5.0 and older versions.
When a UAP accesses an RDAREA that is on holdBecause a hold check is performed before locking the RDAREA, the fact that the RDAREA is on hold can be detected more quickly than when N is specified.Because a hold check is performed after locking the RDAREA, the locked RDAREA may cause a timeout error (KFPA11770-E) if a UAP accesses the RDAREA that is on hold.
Additionally, if the access target RDAREA is on hold because data is being loaded or because it is being reorganized, the UAP may cause a hold error (KFPA11920-E).
When using a non-row partitioning index to narrow the access target RDAREAsYou must be careful when a table is row-partitioned but the index is not. When using a non-row partitioning index to narrow the access target RDAREAs. a hold error (KFPA11920-E) occurs, even when a non-access target RDAREA is on hold. In the example given for processing by HiRDB, the UAP causes a hold error (KFPA11920-E) if any of RDAREAs 1 through 4 is on hold.When using a non-row partitioning index to narrow the access target RDAREAs, the UAP or command can be executed even if a non-access target RDAREA is on hold. In the example given for processing by HiRDB, the UAP can be executed even if RDAREAs 2 through 4 are on hold.
* Refers to UAPs and commands that cannot be executed if RDAREAs are on hold.
31) pd_db_io_error_action = dbhold | unitdown
Specifies the processing to be performed by HiRDB when an input/output error occurs in an RDAREA (excluding the master directory RDAREA). If an input/output error occurs in the master directory RDAREA, HiRDB (or a unit for a HiRDB/Parallel Server) is always abnormally terminated regardless of the specification in this operand. For the actions to be taken when an RDAREA input/output error occurs, see the HiRDB Version 8 System Operation Guide.
An input/output error in this case refers to an error that occurs when a file manipulation attempt by HiRDB fails due to a cause that cannot be determined by HiRDB. When such an error occurs, -1544 is output as the error code returned in response to a HiRDB file system access request.
dbhold:
When an input/output error occurs in an RDAREA, the RDAREA is placed in an error shutdown state.
unitdown:
If an input/output error occurs in an RDAREA, HiRDB (or a unit for a HiRDB/Parallel Server) is abnormally terminated. However, if an input/output error occurs again following abnormal termination, the RDAREA is placed in an error shutdown state. To enable the specification of unitdown again, take one of the following actions:
  • Start HiRDB normally.
  • Execute the system reconfiguration command (pdchgconf command).
Specification guidelines
To determine the specification value for this operand, see Actions to be taken when an RDAREA input/output error occurs in the HiRDB Version 8 System Operation Guide.
Notes
  • When an input/output error occurs when unitdown is specified, HiRDB is abnormally terminated. Consequently, if a UAP or utility is being executed in the pre-update log acquisition mode or no-log mode, the processing target RDAREA may go into an error shutdown state.
  • If an input/output error occurs during the startup or termination process, HiRDB is not abnormally terminated even if unitdown is specified.
32) pd_connect_errmsg_hide = Y | N
Specifies whether to hide the error cause in the message that is output when a connection attempt fails.
Y: Hides the error cause when a connection attempt fails.
N: Does not hide the error cause when a connection attempt fails.
Depending on the value specified for this operand, the message that is output when a connection attempt fails may vary. The following table shows the details:
Error causeOutput message
pd_connect_errmsg
_hide = Y
pd_connect_errmsg
_hide = N (default value)
Invalid authorization identifier (the specified user does not exist)KFPA19632-EKFPA11561-E
Invalid password (the specified password is invalid)KFPA19632-EKFPA11560-E
33) pd_cancel_down_msgchange = Y | N
Specifies whether or not the error messages output when a server process is terminated forcibly are to be changed.
Y:
Changes the error messages to warning messages. The facility for changing error messages is called the facility for changing a process down message when cancelling a transaction.
N:
Does not change the error messages.
The following shows the relationship between the value of this operand and the error messages that are output:
ConditionMessages that are output
When Y (default value) is specifiedWhen N is specified
Server process is terminated forcibly for one of the following reasons:#
  • Intentional forced termination by the user
  • Forced termination caused by a timeout
  • Forced termination due to a failure at the client
  • KFPS01852-W
  • KFPO00115-W
  • KFPS01820-E
  • KFPO00105-E
Server process is terminated forcibly for some other reason
  • KFPS01820-E
  • KFPO00105-E
HiRDB cannot identify the cause of the forced termination of the server process
#
There are other causes that change the messages. For details, see Facility for changing a process down message when cancelling a transaction in the HiRDB Version 8 System Operation Guide.
Advantages
By specifying Y in this operand, you change the messages that are displayed for identifying the cause of forced termination of a server process.
Remarks
When the KFPS01820-E and KFPO00105-E messages are displayed, it is not possible to use the message IDs to distinguish between errors detected by HiRDB and errors resulting from an intentional user operation. To identify the cause, you must compare the process IDs that are displayed in the individual messages.
If JP1 is used to monitor messages, handling based on the KFPS01820-E and KFPO00105-E messages may be complicated because information about multiple messages cannot be compared. Specifying Y in this operand makes it easier to handle such messages because the output messages are classified by error cause. For this reason, it is recommended that you specify Y in this operand when you use JP1 to monitor messages.
Relationship to other operands
If v6compatible or v7compatible is specified in the pd_sysdef_default_option operand, the default value for this operand is N.