Button for 1977 Button for 1984 Button for 1990 Button for 1995 Button for MDC Button for notes Button for examples
Left Hand Pointer

OMI - Transactions

1995 Version of ANSI (Equivalent to Current ISO Version) of Standard

Right Hand Pointer

4.3.3 Transactions

An agent shall originate each transaction with exactly one request message. The server shall attempt the requested operation and shall reply with exactly one response message, which may indicate failure to perform the operation.

Note – In anticipation of future versions of the protocol, which may permit many requests and responses in a transaction, messages include sequence numbers and request identifiers.

Only the agent shall initiate a transaction. If the server has something to tell the agent, for example "shutting down," the server shall indicate in its next response message that the agent should request the server's status.

Transactions are isolated. The server need not retain information about completed transactions.

Nonetheless, both server and agent shall retain the parameters of the session including, for example, agent's and server's names, and negotiated maximum lengths of gvns, values, and messages.

All OMI transactions shall have the same priority or the same class. That is, there are no out-of-band messages. Protocol management transactions such as capability negotiation, status updates, or startup and shutdown shall be handled in the same manner as database transactions.

Button for 1977 Button for 1984 Button for 1990 Button for 1995 Button for MDC Button for notes Button for examples

Copyright © Standard Documents; 1977-2018 MUMPS Development Committee;
Copyright © Examples: 1995-2018 Ed de Moel;
Copyright © Annotations: 2003-2008 Jacquard Systems Research
Copyright © Annotations: 2008-2018 Ed de Moel.

This page most recently updated on 13-Sep-2014, 14:13:51 .

For comments, contact Ed de Moel (demoel@jacquardsystems.com)