OpenTP1 Version 7 Operation
If an error occurs in a message queue file, an error message is output.
Errors are handled as appropriate to the error messages, as described below.
OpenTP1 must be terminated normally once, and the size of the physical file for the message queue must be increased with the queinit command (-r option specified). OpenTP1 can then be started.
OpenTP1 must be terminated normally once. Then, the physical file for the message queue must be deleted with the querm command, and a new physical file for the message queue must be allocated with the queinit command. OpenTP1 can then be started.
If the disk queue cannot be used for some reason during MCF startup and fallback operation with a memory queue was specified in the extended reservation definition of the MCF manager definitions, processing will resume using the memory queue. When the memory queue is used, messages cannot be recovered during full recovery.
If the disk queue becomes unusable during online operation, it cannot be replaced with the memory queue.
The KFCA11065-W or KFCA11066-W message is output when the fallback operation with a memory queue begins. Whenever either of these messages is output, you must perform recovery from the fallback operation.
The most common cause of a fallback operation is a definition information mismatch. The following are examples of definition information mismatches:
In such cases, use the following procedure to recover from the fall-back operation:
If an error occurs in a message queue file, the messages in the queue cannot be recovered. For received messages, the messages that were to be stored in the input queue can be checked by collecting the IJ. For sent messages, the messages that were to be stored in the output queue can be checked by collecting the OJ. Whether or not the IJ and OJ are to be collected is specified in the application attributes definition.
All Rights Reserved. Copyright (C) 2006, 2010, Hitachi, Ltd.