set format

 
[set prf_file_size=JNL-performance-verification-trace-information-file-size]
[set prf_file_count= number-of-generations-for-JNL-performance-verification-trace-information-files]
[set prf_trace_backup=Y|N]
 

Command format

None

The JNL performance verification trace definition defines the execution environment for acquiring JNL performance verification trace information.

prf_file_size=JNL-performance-verification-trace-information-file-size

~<unsigned integer> ((1024-1048576))<<1024>> (units: kilobytes)

Specify the size of a JNL performance verification trace information file.

Normally, the trace information is output to regular files in OpenTP1. The number of generations of this file is specified by the prf_file_count operand in the JNL performance verification trace definition. When all generations have been used, the oldest file is overwritten with new trace information. Accordingly, old trace information is lost as time passes. You can increase the interval at which the oldest file is overwritten by increasing the value of this operand.

You can use the following formulas to calculate the size of one trace file (units: bytes):

• When 00000001 is specified in the jnl_prf_event_trace_level operand of the system common definition
  Size of one file = 128 x a + 128 x b
  
• When 00000002 is specified in the jnl_prf_event_trace_level operand of the system common definition
  
  • When the OS is UNIX
    Size of one file = 512 x a + 128 x b + 256 x c
    
  • When the OS is Windows
    Size of one file = 576 x a + 128 x b + 256 x c
    

Where:

a: Number of journal write processes that occur inside one transaction

b: Number of buffer waits that occur inside one transaction

c: Number of journal records acquired in one transaction

prf_file_count=number-of-generations-for-JNL-performance-verification-trace-information-files

~<unsigned integer>((3-256)) <<3>>

Specify the number of generations for the JNL performance verification trace information file.

prf_trace_backup=Y|N

~<<Y>>

Specify whether to back up the JNL performance verification trace files when OpenTP1 terminates.

Y

The JNL performance verification trace information files are backed up.

N

The JNL performance verification trace information files are not backed up.

The backup files, when collected, are created in $DCDIR/spool/save.

The following table lists the files that are backed up when Y is specified.

Trace file name	File name	Backup file name#1
JNL performance verification trace information file	_jl_nnn#2	_jl_nnn.bk1 and _jl_nnn.bk2

#1

nnn: A value that corresponds to the name of a trace file.

#2

nnn: A value that begins with 001. The maximum of the value is specified by the prf_file_count operand in the JNL performance verification trace definition.

For details about the JNL performance verification trace information file, see the manual OpenTP1 Description.

The JNL performance verification trace information file provides information useful for troubleshooting. If no backup is collected when a problem occurs, no information is available for troubleshooting and problem resolution may take a long time. If you do not plan to collect backups, consider the possibility of expanding the prf_file_size and prf_file_count operands.

You can also specify this operand in the performance verification trace definition. The priority of the specified values is (1.>2.):

1. JNL performance verification trace definition
2. Performance verification trace definition

None

Use this definition only when TP1/Extension 1 is installed. If TP1/Extension 1 is not installed, the definition might not work correctly.