Nonstop Database, HiRDB Version 9 System Operation Guide

[Contents][Index][Back][Next]

8.10 Monitoring the execution time of UAPs and utilities (reducing the effects of nonresponding programs)

This section explains how to minimize adverse effects when an error occurs that causes a UAP, utility, or operation command to stop responding.

When an error (such as a communications error, an intermittent failure such as a power flicker, or a disk error) occurs during the execution of an overnight batch job or other process and a UAP, a utility, or an operation command stops responding, the execution of other UAPs, utilities, and operation commands might be affected adversely or even stopped. In the worst case, the effects might extend to online operations on the following business day. You can specify the following operands to minimize adverse effects when UAPs, utilities, or operation commands stop responding:

If a UAP, utility, or operation command does not terminate once the time specified in this operand or option has elapsed, that UAP, utility, or operation command is terminated forcibly. This minimizes adverse effects on other UAPs, utilities, or operation commands. We recommend that you specify a time that assumes a high probability of such errors occurring in these operands or options.

For details about the PDCWAITTIME operand of the client environment definitions, see the HiRDB Version 9 UAP Development Guide.

For pd_utl_exec_time and pd_cmd_exec_time in the system common definition, specify whichever of these operands is appropriate, because there are differences in the operation commands and utilities whose execution time they monitor. For details about the operation commands and utilities that can be monitored, see the description of each operand in the manual HiRDB Version 9 System Definition.

For details about the options of the individual operation commands and utilities and about the operands of each utility, see the manual HiRDB Version 9 Command Reference.