Operands related to troubleshooting information

27) pd_cancel_dump = put | noput

This operand is designed to reduce the amount of troubleshooting information to be output.

Specifies whether or not troubleshooting information is to be collected in the following cases:

When a UAP does not terminate within the monitoring time specified by the PDCWAITTIME operands in the client environment definition
When a UAP being executed is canceled by the pdcancel command

For details about the troubleshooting information to be collected, see the HiRDB Version 8 System Operation Guide.

put:

Troubleshooting information is collected. Because the troubleshooting information is output to files under %PDDIR%\spool, a space shortage may occur in the file system.

Note that the troubleshooting information that has been collected is automatically deleted by HiRDB at the following timings.

Every 24 hours while HiRDB is running (the deletion interval can be changed using the pd_spool_cleanup_interval operand).
When HiRDB is started (whether to delete the troubleshooting information can be changed using the pd_spool_cleanup operand).

If the HiRDB administrator is to delete the troubleshooting information, the pdcspool command must be executed.

noput:: Do not collect troubleshooting information. Because no troubleshooting information will be collected, the load on the file system is reduced. Specify this option if UAP cancellation occurs frequently during normal operation and there is no need to investigate the causes.

For details about the error information that is displayed in the event of abnormal termination, see Table 2-1 Error information that is displayed in the event of abnormal termination in the section on the pd_dump_suppress_watch_time operand.

Notes: If a UAP is canceled by the pdcancel command with the -d option specified, troubleshooting information is collected regardless of the option specified for this operand.

28) pd_dump_suppress_watch_time = troubleshooting-information-output-suppression-time

<unsigned integer>((0-3600)) (Seconds)

This operand is designed to reduce the amount of troubleshooting information to be output.

This operand specifies the amount of time (in seconds) during which to suppress outputting again the troubleshooting information (files under %PDDIR%\spool) that is output when any of the following situations occurs.

The time specified in PDCWAITTIME is exceeded.
The UAP being executed is cancelled by the pdcancel command (except when the -d option is specified).
A process is abnormally terminated.

Once troubleshooting information is output, no troubleshooting information is output again until the time specified by this operand has elapsed. For example, if 60 is specified for this operand, no troubleshooting information is output again until 60 seconds have passed because troubleshooting information was previously output.

Note that if 0 is specified for this operand, outputting of troubleshooting information is not suppressed.

Advantage: If there are multiple HiRDB server processes, they may be abnormally terminated continuously because of timeout, for example. When abnormal terminations of server processes occur continuously, troubleshooting information, such as core and simple dump, is repeatedly collected, thus causing a space shortage in the disk in which the HiRDB directory is located. If such a shortage occurs, HiRDB may be abnormally terminated. Therefore, specify this operand to make sure that no disk space shortage occurs.

For details about the error information that is displayed in the event of abnormal termination, see Table 2-1 Error information that is displayed in the event of abnormal termination in the section on the pd_dump_suppress_watch_time operand.

Notes: If the -d option is specified for the pdcancel command, if abnormal termination is caused by an internal conflict, or if a signal is received from outside, troubleshooting information is collected regardless of the value specified for this operand.

29) pd_spool_cleanup_interval = troubleshooting-information-deletion-interval

<unsigned integer>((0-744)) (Times)

This operand is used for deleting the troubleshooting information and temporary work files that have been output. If these items are not deleted, they may cause a space shortage in the disk in which the HiRDB directory is located. If such a shortage occurs, HiRDB may be abnormally terminated. Therefore, HiRDB regularly deletes the following files:

Troubleshooting information file (files in %PDDIR%\spool)
Temporary work files (files in %PDDIR%\tmp)

This operand specifies the deletion interval (hours). For example, if 48 is specified for this operand, these files are deleted every 48 hours. Normally, (if this operand is omitted) files are deleted every 24 hours.

Note that time counting begins when HiRDB is normally started. When HiRDB is normally terminated, time counting also stops. Then, the count returns to 0 during the next normal startup.

Specify the files to be deleted using the pd_spool_cleanup_interval_level operand explained as follows.

Operand rule: If 0 is specified, files are not deleted.

Specification guidelines: If 24, 48, 72, and so on are specified for this operand, files are deleted at the predetermined time. Specify the time so that files are deleted during the time period that does not overload the system.

Notes

Even while HiRDB is stopped because of planned termination, forced termination, or abnormal termination, time counting continues. However, if the deletion time arrives while HiRDB is stopped, files are not deleted. Files are not deleted until the next deletion time. To restart HiRDB after deleting the files, execute the pdcspool command.
If the TMP environment variable is specified, the temporary work files used by a command or utility are not output to %PDDIR%\tmp, but to the directory specified by the TMP environment variable. The temporary work files that are output to the directory specified by the TMP environment variable are not subject to regular deletion. Therefore, use Explorer, for example, to delete them.

Remarks

The difference between the pd_spool_cleanup_interval and pd_spool_cleanup operands is as follows:

The pd_spool_cleanup_interval operand is related to regular deletion of troubleshooting information.
The pd_spool_cleanup operand is related to the deletion of troubleshooting information during HiRDB startup.

Therefore, if you plan to run HiRDB continuously for 24 hours, consider specifying the pd_spool_cleanup_interval operand. If you plan to terminate HiRDB every day, consider specifying the pd_spool_cleanup operand.

30) pd_spool_cleanup_interval_level = number-of-days [, deletion-type]

This operand is used for deleting the troubleshooting information and temporary work files that have been output, and specifies the condition for regularly deleting the troubleshooting information and temporary work files.

number-of-days: <unsigned integer>((1-24855)) (days): Troubleshooting information files that are older than the number of days specified here are deleted. For example, if 3 is specified, all troubleshooting information files, except for those created within the last 3 days (or 3 days 24 hours = 72 hours), are deleted.

deletion-type: <character string>

Specifies the type of troubleshooting information file to be deleted.

all: All files are to be deleted.

dump: Only the files internally acquired by HiRDB are to be deleted.

The following are the types of troubleshooting information files that are deleted.

Troubleshooting information file type	Directory name	all	dump	Remarks
Deadlock and timeout information	pdlckinf	Y	N	Output when an error occurs during locking.
Access path information	pdsqldump	Y	N	Output when the access path display utility is used.
Save core file, etc.	save	Y	Y	Output when a process is abnormally terminated.
Shared memory dump file	pdshmdump	Y	Y	Output when a process or unit is abnormally terminated.
Simple dump files	pdsysdump	Y	Y	None
	pdsdsdump	Y	Y	Nonexistent in a HiRDB/Parallel Server
	pdfesdump pddicdump pdbesdump	Y	Y	Nonexistent in a HiRDB/Single Server
System log file status information file	pdjnlinf	Y	N	Files under \pdjnlinf\errinf are not deleted.

Y: File is deleted.

N: File is not deleted.

Note: Directory names under %PDDIR%\spool are shown.

All temporary work files, except for those listed as follows, are deleted regardless of the deletion type specification. Parentheses indicate directory names under %PDDIR%\tmp.

Current working directory (home) of the process in which HiRDB is to start
Shared memory information file (pdommenv)
Differential information files of the pdbufls command (files with names that begin with CMb)

Condition: A value other than 0 must be specified for the pd_spool_cleanup_interval operand.

Specification guidelines: Specify a value that is longer than the execution time of commands (including utilities). For example, if the execution of the pdcopy command, which collects backup data, requires 24 hours (1 day), specify at least 2 for the number of days. If you do not specify a value that is longer than the execution time of the command, the temporary work files being used by the command are deleted, and thus the command may not run correctly.

Operand rule: If you specify a deletion type, you must also specify a number of days.

Remarks

The difference between the pd_spool_cleanup_interval_level and pd_spool_cleanup_level operands is as follows:

The pd_spool_cleanup_interval_level operand is related to regular deletion of troubleshooting information.
The pd_spool_cleanup_level operand is related to the deletion of troubleshooting information during HiRDB startup.

Therefore, if you plan to run HiRDB continuously for 24 hours, consider specifying the pd_spool_cleanup_interval_level operand. If you plan to terminate HiRDB every day, consider specifying the pd_spool_cleanup_level operand.

31) pd_spool_cleanup = normal | force | no

This operand is used for deleting the troubleshooting information that has been output.

Specifies whether or not troubleshooting information files (files under %PDDIR%\spool) that were output previously by HiRDB are to be deleted when HiRDB is started. This operand is related to the pd_spool_cleanup_level operand described below.

normal:: Delete the files when HiRDB is started normally or is restarted following a planned termination.

force:: Delete the files whenever HiRDB is started, regardless of the HiRDB activation mode.

no:: Do not delete the files.

Specification guidelines: If troubleshooting information files take up too much disk space, specify normal or force.

Remarks

The difference between the pd_spool_cleanup_interval and pd_spool_cleanup operands is as follows:

The pd_spool_cleanup_interval operand is related to regular deletion of troubleshooting information.
The pd_spool_cleanup operand is related to the deletion of troubleshooting information during HiRDB startup.

32) pd_spool_cleanup_level = number-of-days [, deletion-type]

This operand is used for deleting the troubleshooting information that has been output, and specifies the condition for deleting the troubleshooting information files during HiRDB startup.

number-of-days: <unsigned integer>((0-24855)) (days): Specifies a number of days when troubleshooting information that is older than the specified number of days is to be deleted. For example, if 3 is specified, all troubleshooting information will be deleted except for the information that is fewer than 3 days old (3 days 24 hours = 72 hours).; If 0 is specified, all troubleshooting information files are deleted.

deletion-type: <character string>: Specifies the type of troubleshooting information to be deleted.; all: Delete all file types.; dump: Delete only files collected internally by HiRDB.

The following are the types of troubleshooting information files that are deleted:

Troubleshooting information file type	Directory name	all	dump	Remarks
Deadlock and timeout information	pdlckinf	Y	N	Output when an error occurs during locking.
Access path information	pdsqldump	Y	N	Output when the access path display utility is used.
Save core file, etc.	save	Y	Y	Output when a process is abnormally terminated.
Shared memory dump file	pdshmdump	Y	Y	Output when a process or unit is abnormally terminated.
Simple dump files	pdsysdump	Y	Y	None
	pdsdsdump	Y	Y	Nonexistent in a HiRDB/Parallel Server
	pdfesdump pddicdump pdbesdump	Y	Y	Nonexistent in a HiRDB/Single Server
System log file status information file	pdjnlinf	Y	N	Files under \pdjnlinf\errinf are not deleted.

Y: File is deleted.

N: File is not deleted.

Note: Directory names under %PDDIR%\spool are shown.

Condition: normal or force (default value) must be specified for the pd_spool_cleanup operand.

Operand rule: A number of days and a deletion type must both be specified.

Remarks

The difference between the pd_spool_cleanup_interval_level and pd_spool_cleanup_level operands is as follows:

The pd_spool_cleanup_interval_level operand is related to regular deletion of troubleshooting information.
The pd_spool_cleanup_level operand is related to the deletion of troubleshooting information during HiRDB startup.

33) 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 pd_module_trace_max operand value (bytes); In the 64-bit mode: 64 + 64 pd_module_trace_max operand value (bytes)

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

3.3.11 Operands related to troubleshooting information