OpenTP1 Version 7 Operation

[Contents][Index][Back][Next]

10.6.2 OpenTP1 cannot be terminated

Organization of this subsection
(1) UAP processing continues for a long time, or UAP cannot be terminated due to an error
(2) Messages accumulated in output queue are not output during normal termination due to a communication error, etc.
(3) OpenTP1 at archive-journal target node does not terminate because connected journal service fails to terminate
(4) OpenTP1 at archive-journal source node does not terminate because of failure to release connection from global archive journal service

(1) UAP processing continues for a long time, or UAP cannot be terminated due to an error

The status of a UAP can be checked with the prcls or scdls command or with the OS's ps command.

If UAP processing does not terminate, either the user can wait for UAP termination or the UAP can be terminated forcibly.

(2) Messages accumulated in output queue are not output during normal termination due to a communication error, etc.

An MCF event that reports the discarding of an unprocessed message (ERREVTA) is activated after a specified period of time (the unprocessed send message accumulation time specified in the MCF communication configuration definition), and OpenTP1 terminates normally. All unsent messages in the output queue are discarded.

To retain the unsent messages, OpenTP1 must be terminated forcibly before the unprocessed send message accumulation time elapses. The unsent messages can be inherited by then restarting OpenTP1.

(3) OpenTP1 at archive-journal target node does not terminate because connected journal service fails to terminate

Normal or planned termination of OpenTP1 at an archive-journal target node requires that the connections to all journal service be released. To this end, the user must execute the dcndls command to check the status of the archive-journal source node being connected and take the following action as may be appropriate:

(a) Archive-journal source node terminated abnormally or forcedly

Execute the jnlardis command to forcedly release the connection. Or else, restart OpenTP1 at the archive-journal source node and then perform normal or planned termination.

(b) Archive-journal source node terminated normally or as planned

Execute the jnlardis command to forcedly release the connection.

(c) Archive-journal source node in the online mode

Terminate OpenTP1 at the archive-journal source node.

(4) OpenTP1 at archive-journal source node does not terminate because of failure to release connection from global archive journal service

If OpenTP1 at the archive-journal target node is not online, the journal service at the archive-journal source node cannot be released from the connection to the global archive journal service. The user must execute the dcndls command to check the status of the archive-journal target node and take the following action as may be appropriate:

(a) Archive-journal target node terminated

Restart OpenTP1 at the archive-journal target node.

(b) Archive-journal target node in online mode

Forcedly terminate OpenTP1 at the archive-journal source node.