☜	OMI - Mnemonis Space Draft MDC Standard					☞

5.3.5 Mnemonic spaces

A mnemonic space defines a set of control mnemonics and device parameters that apply to a particular device. Transactions shall contain the server’s names for mnemonic spaces.

A device may support more than 1 mnemonic space. For example:

• A video display terminal has an attached printer; the server considers them as 1 device but different parameters apply to them.
• Output goes to several windows on a video display, each with its own mnemonic space.
• A single device accepts parameters and control mnemonics from 2 standards or conventions, each with its own name.
  NOTE – the null mnemonic space, whose name is the empty string, has significance in M (see ANSI/MDC X11.1, 8.2.2).

Transactions express the mnemonic space as a <SS> whose content is a mnemonicspacename, defined by ANSI/MDC X11.1 as a string of restricted characters. When no mnemonic space is in effect – the open device request specified 0 mnemonic spaces – then the mnemonic space shall equal the empty string.

The open device transaction establishes the valid mnemonic spaces when it gains ownership of the device. Mnemonic spaces shall not be added during ownership. A mnemonic space not set error condition shall result when any request, including open device but excepting get device parameters, names a mnemonic space not included among those established by the transaction that gained ownership of the device.

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 14-Nov-2023, 21:47:55.

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