Operands related to troubleshooting information

21) pd_module_trace_max = maximum-number-of-module-traces-that-can-be-stored

<unsigned integer>((126-16383))

A HiRDB process records the history of the executed functions and macros inside the process private memory. This history is called a module trace. This operand specifies the number of module trace records. The content of this history is loaded into the core file and is output when a process error occurs.

Specification guidelines: Normally, there is no need to specify this operand. If a maintenance engineer asks you to specify this operand for a performance check purpose or the like, follow the maintenance engineer's instructions.

Note: Process private memory of the following size is allocated to each process:; In the 32-bit mode: 64 + 48 value of pd_module_trace_max operand (bytes); In the 64-bit mode: 64 + 64 value of pd_module_trace_max operand (bytes)

22) pd_module_trace_timer_level = 0 | 10 | 20

Specifies how to acquire the time to be output in module traces. The following table explains the meaning of the value specified for this operand.

Specified value	Time acquisition method
0	Time is output in seconds at every module trace output location.
10	Time is output in microseconds only at performance-critical module trace output locations, such as those before and after input/output processing, and time is output in seconds at other locations.
20	Time is output in microseconds at every module trace output location.

Specification guidelines: Normally, there is no need to specify this operand. If a maintenance engineer asks you to specify this operand for a performance check purpose or the like, follow the maintenance engineer's instructions.

Note: If you specify a value other than 0 for this operand, a function for acquiring time in microseconds is issued, and as a result, system performance may decline.

7.3.8 Operands related to troubleshooting information