5.2.9 Operands related to RPC trace information
- 28) pd_rpc_trace = Y | N
- Specifies whether RPC trace information is to be collected. HiRDB maintenance information is output in the RPC trace information.
- Normally, omit this operand.
- Y: Collect RPC trace information.
- N: Do not collect RPC trace information.
- Note
- Specifying Y for this operand degrades communication performance.
- Operand default value
- If this operand is omitted, the value specified for the same operand in the server common definition, the unit control information definition, or the system common definition takes effect, in that order. If the same operand is also omitted from the server common definition, the unit control information definition, and the system common definition, N is assumed.
- 29) pd_rpc_trace_name = "name-of-RPC-trace-collection-file"
- ~<path name of up to 254 characters>
- Specifies an absolute path name for the file name 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
2 are created under the directory specified by this operand. Pay attention to the file size.
- Operand default value
- If this operand is omitted, the value specified for the same operand in the server common definition, the unit control information definition, or the system common definition takes effect, in that order. If the same operand is also omitted from the server common definition, the unit control information definition, and the system common definition, the following value is assumed:
- $PDDIR/spool/rpctr
- 30) pd_rpc_trace_size = RPC-trace-collection-file-size
- ~<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, there might not be enough trace information available, making troubleshooting difficult. For this reason, specify at least 1000000 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.
- Operand default value
- If this operand is omitted, the value specified for the same operand in the server common definition, the unit control information definition, or the system common definition takes effect, in that order. If the same operand is also omitted from the server common definition, the unit control information definition, and the system common definition, 4096 is assumed.