(a) Normal termination

One OpenTP1 node can terminate all OpenTP1 nodes configuring multinode areas or subareas in normal termination mode. All journals at the OpenTP1 node that configures a multinode area or subarea are archived.

OpenTP1 nodes will be started in normal termination mode next time. Journals following the last archive file when OpenTP1 terminated will not be archived.

(b) Planned termination

One OpenTP1 node can terminate all other OpenTP1 nodes configuring multinode areas or subareas in normal termination mode or planned termination mode. All journals at the OpenTP1 node configuring a multinode area or subarea are archived.

OpenTP1 will be started in restart mode next time. Journals will be archived following the last archive journal file when OpenTP1 terminated.

(c) Forced termination

One OpenTP1 node can terminate all other OpenTP1 nodes configuring multinode areas or subareas in forced termination mode.

OpenTP1 will be started in restart mode next time. Journals will be archived following the last archive journal file when OpenTP1 terminated.

(d) Abnormal termination

If an error occurs, one OpenTP1 node will terminate OpenTP1 nodes configuring multinode areas or subareas in abnormal termination mode.

OpenTP1 will be started in restart mode next time. Journals will be archived following the last archive journal file when OpenTP1 terminated.

The dcmstop command enables one OpenTP1 command to terminate more than one OpenTP1 node that configures multinode areas or subareas. Executing this command terminates the following OpenTP1 nodes:

• All OpenTP1 nodes that configure multinode areas to which the OpenTP1 node corresponding to the command input environment variable DCDIR belongs
• All OpenTP1 nodes that configure the specified multinode subareas
• OpenTP1 nodes with the specified node identifiers

The termination modes and the operation commands used for termination are:

Normal termination

dcmstop

Planned termination

dcmstop -a or dcmstop -b

Forced termination

dcmstop -f

The dcstop command is used to terminate individual OpenTP1 nodes. The termination modes and the operation commands used for termination are:

Normal termination

dcstop

Forced normal termination

dcstop -n

Planned termination

dcstop -a or dcstop -b

Forced termination

dcstop -f

Under the global archive journal facility, the archive-journal target node terminates with the dcstop or dcmstop command as with other nodes. In this case, however, the archive-journal target node must be terminated concurrently with or after any other nodes. If the dcstop or dcmstop command is executed before the other nodes, the archive-journal target node awaits for the other nodes to terminate. The maximum waiting time (timeout value) must be specified in jnl_arc_terminate_timeout of the global archive journal service definition. For details, see the manual OpenTP1 System Definition.

The archive-journal target node can terminate normally only when all other nodes have terminated normally. The user is recommended to specify a termination mode for the archive-journal target node after verifying that all other nodes have terminated normally.

The archive-journal target node remains connected in the following cases:

• The OpenTP1 dcstop command (termination command) is executed in the archive-journal source node before that node is connected with the archive-journal target node (message KFCA04130-I is not output).
• The jnl_arc_terminate_timeout operand (timeout with the global archive journal service) is set for the archive-journal source node and a timeout occurs when the archive-journal source node is terminated (message KFCA04148-W is output).

To release the connection, execute the jnlardis command from the archive-journal target node.