If a connection error occurs, the cause of the error must be eliminated, as appropriate to the reason code displayed with the error message. Connection can then be reestablished with the mcftactcn command.

For details of the error handling procedures, see the applicable protocol manual.

If a LAN error occurs, an error message is output, and the client UAP results in an error during process-to-process communication by the RPCs at both computers.

The cause of the error must be eliminated, as appropriate to the OS and hardware error handling procedures. OpenTP1 can then be restarted.

If a communication error occurs between the global archive journal service and the journal service at an archive-journal source node, an error message is displayed. The user must eliminate the cause of the error according to the information contained in the message.

While the communication error remains, the journal at the archive-journal source node is not archived. When there is no swap-in file for the system journal file at the archive-journal source node, the OpenTP1 at the node terminates. The user must unload files individually.

When communication is restored, archiving begins with an untransferred journal even if files are unloaded individually. If journals that must be archived by individual unloading and swapping have been lost, archiving for applicable subsequent nodes is suspended. The user must unload files individually after recovery of communication.