OpenTP1 Version 7 Description

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

3.3.6 Message-control transactions

The following describes the processing of message-control transactions.

Organization of this subsection
(1) MCF message processed as an MHP transaction
(2) MCF message not processed as an MHP transaction

(1) MCF message processed as an MHP transaction

On receipt of an MCF message from another system, the MHP service is called and an MHP transaction begins. If the MHP that processed the message ends normally, the transaction is committed and the MHP process takes effect.

An MHP can either commit or roll back a transaction. To commit an MHP transaction, use the dc_mcf_commit function. To roll back an MHP transaction, use the dc_mcf_rollback function.

(2) MCF message not processed as an MHP transaction

You can choose not to handle a received MCF message as an MHP transaction. This makes processing more efficient, although the message cannot be recovered if an error occurs in the UAP. An MHP that does not process MCF messages as transactions is known as non-transaction attribute MHP. To use this type of MHP, specify nontrn in the trnmode operand of the application attribute definition.