6.3.8 Operands related to RPC trace information

20) pd_rpc_trace = Y | N
Specifies whether or not RPC trace information is to be collected. HiRDB maintenance information is output in the RPC trace information.
Normally, this operand should be omitted.
Y: Collect RPC trace information.
N: Do not collect RPC trace information.
Note
Specifying Y for this operand degrades communication performance.
21) pd_rpc_trace_name = "name-of-RPC-trace-collection-file"
[Figure]<pathname of up to 254 characters>
Specifies an absolute pathname for the filename for the RPC trace files. Three RPC trace files are created, with 1, 2, and l suffixed to the specified file name.
Note
Files with a maximum size of pd_rpc_trace_size value [Figure]2 are created under the directory specified by this operand. Attention should be paid to the file capacity.
22) pd_rpc_trace_size = RPC-trace-collection-file-size
[Figure]<unsigned integer>((1024-2147483648)) (Bytes)
Specifies in bytes the size of the RPC trace files.
The value specified by this operand determines the size of both RPC trace file 1 and RPC trace file 2.
Specification guidelines
An RPC trace collects in a single file in time order the information on the communications among all processes. If the volume of this information exceeds the specified value, trace data output is switched to the other file, which means that older trace information will be overwritten. When this happens, the amount of trace information that is available may be inadequate, making troubleshooting difficult. For this reason, at least 1,000,000 should be specified for this operand.
Note
The value specified by this operand does not apply to RPC trace file l, because its size is fixed at 0 bytes.