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

This section explains how to minimize the effects when an error occurs that causes a UAP or utility 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 execution of an overnight batch job or other process, causing a UAP or a utility to stop responding, execution of other UAPs and utilities may be affected adversely or even stopped. In the worst case, the effects may extend to online operations on the following business day. To minimize the adverse effects of UAPs or utilities that are not responding, you can specify the following operands:

The PDCWAITTIME operand is used to monitor UAP execution time. If a UAP or utility does not terminate once the time specified in this operand has elapsed, that UAP or utility is terminated forcibly. This minimizes adverse effects on other UAPs or utilities. In these operands, we recommend you specify a time that assumes a high probability of such errors occurring.

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