☜	OMI - Network Management Draft MDC Standard					☞

B.2 Network management

This standard requires some items whose provision is outside the scope of the standard, for example names and passwords appearing in its messages. The designers expect a network manager to coordinate these items and provide them to OMI implementations in a cooperative, "friendly" collection of nodes. Another network protocol could, in principle, perform these functions as well.

Different implementations have different names for objects; OMI consistently uses the servers’ names. The designers expect implementations to allow the network manager to enter servers’ names into clients’ nodes, where clients’ names for objects are translated into servers’ names.

Items that may need translation:

•  User identifier: identifies the user in each request header (4.5.5, 5.3.1).
•  Group identifier: identifies the user’s group in each request header (4.5.5, 5.3.1).
•  Environment: part of a global reference (5.3.3) denotes the namespace in which the accompanying gvn or nref appears. A client’s environment should be translated into a server’s name and environment (4.7, 5.3.3).

In addition, the agent and server exchange their names and passwords in the connect transaction (5.4.1). Their administration is the network manager’s responsibility.

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:57:31.

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