6.3.3 Operands related to system monitoring
- 7) pd_watch_pc_client_time = maximum-client-request-wait-time
<unsigned integer>((0-65535)) (Seconds)- Specifies in seconds the maximum amount of time for a server 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.
- If no request comes from the HiRDB client within the specified amount of time, it will be assumed that an error occurred at the client and the connection between the server and the client will be terminated forcibly. No notice of disconnection is sent to the HiRDB client in such a case.
- The time that is monitored is the period between CONNECT and DISCONNECT (i.e., the non-transaction status time), excluding the period between SQL execution startup and COMMIT or ROLLBACK.
- Notes
- When 0 is specified, the server waits indefinitely for the next request from the HiRDB client.
- If a small value (e.g., up to 600) is specified for this operand, the HiRDB client may detect server down during SQL execution and may be terminated incorrectly.
- For a UNIX version of a HiRDB client (including a Linux version of a HiRDB client), time is not monitored regardless of the value specified for this operand. To monitor time for a UNIX version of a HiRDB client, specify the PDSWATCHTIME client environment definition of the HiRDB client.
- Relationship to client environment definition
- The value of this operand can be modified for each client. To do so, the PDSWATCHTIME operand must be specified in the client environment definition. For details about the PDSWATCHTIME operand, see the HiRDB Version 8 UAP Development Guide.
- 8) pd_spd_syncpoint_skip_limit = maximum-number-of-skipped-synchronization-point-dumps
<unsigned integer>((0, 2-100000))- If an event such as an endless loop occurs in a UAP, acquisition of synchronization point dumps may be skipped. If several synchronization point dumps are not acquired (instead, they are skipped), there will be an increase in the number of overwrite-disabled system log files, which may result in a shortage of system log file capacity and ultimately in abnormal termination of the unit.
- This operand specifies the maximum number of times synchronization point dumps can be skipped (number of skips per transaction). When the number of skipped synchronization point dumps reaches the specified operand value, the target transaction is cancelled forcibly and rolled back. This is called the skipped effective synchronization point dump monitoring facility.
- For details on this facility, see the HiRDB Version 8 System Operation Guide.
- Advantage
- Specifying this operand provides a means of dealing with endless loops in UAPs.
- Specification guideline
- Normally, specify 0 for this operand. When 0 is specified, HiRDB computes the upper limit for the skip count. If the specification of 0 causes a problem, change the value of this operand. For the method of estimating the specification value, see the HiRDB Version 8 System Operation Guide.
- Notes
- The monitoring provided for by the specification of this operand begins the first time a synchronization point dump is collected after HiRDB is started (including a restart).
- When this operand is specified, UAPs that are being executed in the no-log mode are also monitored. If the processing of a UAP being executed in the no-log mode is cancelled, the database cannot be automatically recovered, and thus RDAREAs are placed in the error shutdown state. Therefore, when specifying the upper limit, account also for the size of the system logs that are output from other transactions inside the server during the processing of UAPs that are executed in the no-log mode.
- The pdload, pdmod, pdrorg, pdexp, pddbst, pdgetcst, pdrbal, and pdvrup commands are not monitored by this facility.