set format

set jnl_objservername="applicable-system-service-name"
[set jnl_max_datasize=checkpoint-dump-buffer-length]
[set assurance_count=guaranteed-generation-count]
[set jnl_reduced_mode=fall-back-operation-option]
[set jnl_reserved_file_auto_open=Y|N]
[set jnl_dual=Y|N]
[set jnl_singleoperation=Y|N]
[set watch_time=maximum-response-waiting-time]

command format

{{{{jnladdfg [-j srf] -g file-group-name [ONL]}}
  {{jnladdpf [-j srf] -g file-group-name -a physical-file-name
             [-b physical-file-name]}}}}

The checkpoint dump service definition defines the execution environment to collect a checkpoint dump in the checkpoint dump file. Always define the execution environment for the transaction service. For other services, define only when the service is to be used.

jnl_objservername="applicable-system-service-name"~<1-8 character identifier>

Specify the name of the applicable system service.

For a MCF service, specify the name as specified with the dcsvstart -m command of the system service configuration definition. For a transaction service, specify as _tjl.

For an MQA service, specify as _mqa.

jnl_max_datasize=checkpoint-dump-buffer-length~<unsigned integer> ((32000-4000000)) <<32768>> (Unit: bytes)

Specify the size of the buffer to read or write the checkpoint dump information from and to the checkpoint dump file.

The number of read and write operations from and to the checkpoint dump file can be controlled. The larger the buffer specification, the smaller will be the number of operations.

assurance_count=guaranteed-generation-count~<unsigned integer> ((1-2)) <<1>>

Specify the number of generations of a checkpoint dump file to be saved on-line as a contingency against input errors and other damage to the said file during a system recovery.

Files of the specified number of generations cannot be re-written. Should an error occur in the newest generation file, recovery can proceed with a remaining guaranteed file, thus improving system reliability.

File groups in a number equal to this (guaranteed generation count + 1) are required to collect a checkpoint dump file.

In specifying several guaranteed generations, the number of non-rewritable journals increases. This can cause a deficiency of files for the next journal collection. To prevent this, the number of journal file blocks should be computed and set as follows:

Journal file block count = Journal block count set as the interval for a checkpoint dump collection x (guaranteed generation count + 1).

jnl_reduced_mode=fall-back-operation-option~<unsigned integer> ((0-2)) <<0>>

Specify whether the checkpoint dump fall-back function is to be used.

When a file error causes fewer files than necessary for online operation or restart operation, the processing continues if at least two files are available.

0

The fall-back function is not used.

1

The fall-back function is used.

2

The fall-back function is used and a warning message is output whenever the chance for collecting a checkpoint dump occurs in the fall-back state.

jnl_reserved_file_auto_open=Y|N~<<N>>

Specify whether an unused (reserved) file is to be automatically opened to continue the processing when a file error causes fewer files than necessary for online operation.

Y

The reserved file is automatically opened.

N

The reserved file is not automatically opened.

This specification takes precedence over the fall-back operation option.

jnl_dual=Y|N~<<N>>

Specify whether the checkpoint dump file is to be duplicated. If duplicated, specify the two physical files (systems A and B) to one file group.

Y

The checkpoint dump file is duplicated.

N

The checkpoint dump file is not duplicated.

jnl_singleoperation=Y|N~<<N>>

When the checkpoint dump file is duplicated, specify whether to assign the physical file as an overwritable file group if either of the dual systems becomes overwritable.

Y

When the physical file of only one system is overwritable, it is assigned as an overwritable file group (one-system operation available).

N

When the physical file of only one system is overwritable, it is not assigned as an overwritable file group (one-system operation unavailable). The file group is placed in the reserved status.

watch_time=maximum-response-waiting-time~<unsigned integer> ((0-65535)) (Unit: seconds)

Specify the maximum waiting time between sending a service request and receipt of a response when communicating between processes by RPC.

OpenTP1 may suspend termination processing for the length of time specified in this operand. Therefore, if you specify a large value, the termination processing of OpenTP1 may take some time.

If no response is received within the specified time, RPC returns a transmission timeout error.

Specify 0 if the system is to wait for a response. When you specify 0, OpenTP1 may not terminate.

If this operand is omitted, the value specified with the watch_time operand of the system common definition is assumed.

Use the default of the watch_time operand of the system common definition for this operand.

We recommend that you do not change the operand unless special tuning is necessary.

If a value that is much greater or smaller than the default of the watch_time operand of the system common definition is specified, a failure may occur causing OpenTP1 to go down.

Described on the following pages.