Operands related to troubleshooting information

30) 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.

Operand default: When this operand is omitted, the specification of the same operand in the server common definition, the unit control information definition, or the system common definition, in that order, is assumed. When the same operand is also omitted in the server common definition, the unit control information definition, and the system common definition, the default is 126.

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)

31) 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.

Operand default: When this operand is omitted, the specification of the same operand in the server common definition, the unit control information definition, or the system common definition, in that order, is assumed. When the same operand is also omitted in the server common definition, the unit control information definition, and the system common definition, the default is 0.

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 might decline.

32) pd_pth_trace_max = maximum-number-of-stored-communication-traces

~<unsigned integer>((1024-8388608))

Specifies the maximum number of communication trace records to be used as troubleshooting information.

Specification guidelines: Normally, there is no need to specify this operand. If a maintenance engineer asks you to specify this operand for a reasons such as performance checking, follow the maintenance engineer's instructions.

Operand default: When this operand is omitted, the specification of the same operand in the server common definition, the unit control information definitions, or the system common definition, in that order, is assumed. When the same operand is also omitted in the server common definition, the unit control information definition, and the system common definition, the default is 1024.

Notes: Increasing the value of this operand increases the amount of process private memory secured by HiRDB processes.; Process private memory for communication traces is calculated based on this operand's value rounded up to the power of two. For details about memory requirements, see Calculation of required memory in the HiRDB Version 9 Installation and Design Guide.

Effects on individual estimation formulas

If the value of the pd_pth_trace_max operand is changed, the following estimation formula is affected:

HiRDB Version 9 Installation and Design Guide:

Calculation of required memory under Estimating the memory size required for a HiRDB/Single Server

5.2.10 Operands related to troubleshooting information