☜	OMI - Definitions Draft MDC Standard					☞

3 Definitions

3.1 M or MUMPS: alternate names of the programming language defined by ANSI/MDC X11.1.

3.2 OMI: an acronym for Open MUMPS Interconnect.

3.3 OSI: the Open Systems Interconnect model of computer communication protocols.

3.4 message: a string of 8-bit characters, allowing all character codes from 0 to 255. A request message contains 1 or more requests, and a response message contains the related responses, exactly 1 response for each request.

3.5 circuit: an error-free, sequence-preserving path for messages. The virtual circuit provided by an OSI level 4 service.

3.6 client: a process that originates requests to be transmitted to a server. Most OMI clients are M[UMPS] application processes, but a network manager utility program or a non-M[UMPS] application program could be a client.

3.7 server: a process that responds to clients’ requests by performing database functions on their behalf and returning responses.

3.8 transaction: 1 request and the related response. An OMI transaction is not the same as a transaction processing transaction.

3.9 agent: a process that manages transactions on behalf of 1 or more clients.

3.10 session: a connection between exactly 1 agent and exactly 1 server. When establishing a session, the 2 processes authenticate each other and negotiate the parameters of transactions to follow.

3.11 user: the human being for whom a client process runs.

3.12 user ID: a number identifying a user for authorization purposes.

3.13 group ID: a number identifying a group of users for authorization purposes.

3.14 OMI node: Usually a node is a computer, but 2 or more independent implementations might share a computer without sharing their databases, and thus be separate nodes. Conversely, an implementation might occupy several computers connected by a non-OMI method, and thus be 1 OMI node. Specifically, an OMI node is a set of 1 or more environments that are accessible without use of the OMI network. That is, a program can refer to an environment in its own node without using OMI.

3.15 device: an I/O device, file, data set, or other object supporting the M[UMPS] OPEN, USE, WRITE, and CLOSE commands.

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 16-Nov-2023, 16:56:17.

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