Table 17-52 shows how the method execution history that was accumulated in the JDBC driver memory before establishment of the first HiRDB connection is transferred if the system properties and client environment definition settings are different.

Table 17-52 Transfer of the method execution history accumulated in the JDBC driver memory

Item	Relationship between system properties and client environment definition	Transfer operation
Number of information items to be acquired in memory	HiRDB_for_Java_OnMemNUM < PDJDBONMEMNUM	The JDBC driver re-allocates memory for accumulation of the method execution history based on the PDJDBONMEMNUM specification, and then copies the execution history accumulated up to that point to the re-allocated area. However, if the PDJDBTRACELEVEL specification is 0, memory is not re-allocated.
	HiRDB_for_Java_OnMemNUM > PDJDBONMEMNUM	The JDBC driver re-allocates memory for accumulation of the method execution history based on the PDJDBONMEMNUM specification. The driver then destroys any accumulated execution history information that cannot be stored in the re-allocated area, and copies the remaining information to the re-allocated area. However, if the PDJDBTRACELEVEL specification is 0, memory is not re-allocated.
Trace acquisition level	HiRDB_for_Java_TraceLevel < PDJDBTRACELEVEL	The driver simply transfers the execution history that was accumulated up to that point.
	HiRDB_for_Java_TraceLevel > PDJDBTRACELEVEL	If the PDJDBTRACELEVEL specification is 1 or greater, the JDBC driver simply transfers the execution history accumulated up to that point. The driver also transfers the execution history of methods that are not targeted by the trace acquisition level specified by PDJDBTRACELEVEL. If the PDJDBTRACELEVEL specification is 0, the JDBC driver destroys the accumulated execution history for each accumulation memory.

The first time the Exception trace log is output to a file after the Java Virtual Machine is started, the log is output to the file with the older update date and time. If the date and time are the same for both files, the log is output to pdexc1.trc.

If the same file output destination is specified when Exception trace logs are being acquired from multiple processes, trace information for the different processes is output to the same file. To acquire a trace for each process, specify a different file output destination for each process.

The JDBC driver uses the facilities of the Java Virtual Machine to create log files in the file system provided by the OS. Therefore, the following items depend on the Java Virtual Machine and file system being used:

• Prefix for the absolute path name
• Path delimiter character
• Maximum number of characters for the output destination file (absolute path)
• Size per file

Information is not output to the Exception trace log when file creation or output fails. An error message may be returned to the UAP and file output may be retried.

The Exception trace log is output with the default conversion character set of the Java Virtual Machine being used.