☜	OMI - Message Form Draft MDC Standard					☞

5.3 Message form

The requests and responses of all transactions except connect shall be collected into request messages and response messages respectively. These messages shall be very long strings comprising the following fields:

1. Request count or response count: <LI> the number of requests or responses that follow, not less than 1.
2. Request(s) or response(s): <VS> 1 or more requests or responses, in the order of their sequence numbers.

Requests and responses are themselves very long strings so that their boundaries can be clearly distinguished. Both comprise a header followed by 0 or more of the fields described in 5.2, but the forms of their headers differ.

Connect requests and responses shall not be placed inside messages, but shall be transmitted in the forms shown for requests and responses. These are the forms of OMI Version 1, retained in Version 2 to allow negotiation of the version during session establishment.

All other requests and responses shall be placed inside messages.

The total number of bytes in a message shall not exceed 65 535.

Figure 1 – Request message

Figure 2 – Response message

Figure 3 – Form of a request

Figure 4 – Form of a response

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

Some specifications are "approved for inclusion in a future standard". Note that the MUMPS Development Committee cannot guarantee that such future standards will indeed be published.

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

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