The nontransaction attribute MHPs can use message exchange functions like MHPs which work as transactions, but the following differences are involved:

• A message output sequence number can be specified, but it is not eligible for error recovery.
• The nontransaction attribute MHPs cannot use synchronization point processing functions (dc_mcf_commit() and dc_mcf_rollback()) and cannot call the message resend function (dc_mcf_resend()). If one of these functions is called, it returns with an error.

(a) Available message queue

The nontransaction attribute MHPs can use memory queues, but cannot use disk queues. Specify the memory queue in the quekind operand that is the -g option to the mcfaalcap operand for the application attribute definition in the MCF application definition.

(b) Transaction attribute of MHPs

For the nontransaction attribute MHPs, specify nontrn in the trnmode operand for the application attribute definition in the MCF application definition. The MHP is not treated as a transaction even if atomic_update=Y is specified in the user service definition.

(c) Time monitoring

Time monitoring of the nontransaction attribute MHPs is specified by the -v option to the mcfaalcap operand for the application attribute definition in the MCF application definition. When the specified time comes, the nontransaction attribute MHP terminates abnormally. If 0 is specified in this definition, time monitoring is not in effect.

If a synchronous message exchange request is used from a nontransaction attribute MHP, the processing time for this message exchange is not included in the time monitored. If a nontransaction attribute MHP requests a service to an SPP, the SPP processing time is also included in the time monitored (if the SPP processes a synchronous message, the processing time is included in the time monitored).

The MHP for handling MCF event ERREVT2 or ERREVT3 is activated depending on the specification in the MCF application definition. If the nontransaction attribute MHP is requesting an SPP for service, nothing is done on the SPP process.

If temporary-stored data cannot be actually updated during processing in continuous inquiry response mode, the processing in continuous inquiry response mode is terminated regardless of the error event definition. If the processing in continuous inquiry response mode cannot be terminated because of an internal error or other condition, a message log is output to prompt the execution of the command for force termination of continuous inquiry response (mcftendct -f). Execute this command to terminate processing in continuous inquiry response mode.