☜	OMI - Connect 1995 Version of ANSI (Equivalent to Current ISO Version) of Standard					☞

5.4.1 Connect

(Operation type 1) The fields of the connect request and their sequence shall be:

1. Major version: <SI> the major version of the OMI protocol supported by the agent. This International Standard defines major version 1. If the agent supports multiple versions, it shall send connect requests for each until the server accepts a major version.
2. Minor version: <SI> the minor version of the OMI protocol supported by the agent. This International Standard defines minor version 1. The agent should send the highest minor version it supports.
3. Min/max values: <LI> The next 10 fields are 5 pairs of minimum and maximum lengths for global values, individual subscripts, global references, total message length, and limit on requests outstanding. These values represent the minimum acceptable to the agent and the maximum that can be processed by the agent.
   The server shall compare these values with its own limits and shall return either the largest value possible or, if the agent’s lengths are not within its bounds, an error condition.
   Agents shall send minimum values that accommodate the portability requirements of ANSI/MDC X11.1. Maximum values may be as high as the agent can support. For example, an agent that supports global value lengths of 510 bytes would send min = 255 and max = 510. A server with maximum global value length of 255 would respond with a maximum of 255. The agent should thereafter return a maximum length error to any client that sets global values longer than 255.
   Minimum and maximum values for the limit on requests outstanding shall both equal 1. Larger values allow for higher performance in extensions and future versions of the protocol.
4. 8 bit: <SI> The 8 bit flag indicates whether the agent supports 8 bit bytes for global values and subscripts. 0 means that only 7 bit values are valid; 1 means that all 8 bit values are valid.
   Note – This flag does not affect the overall protocol, which shall transmit 8 bit characters.
5. Character translation: <SI> The character translation flag indicates whether the agent wishes to send characters in an untranslated form. 1 means do not translate; 0 means translate to the standard character set. See 4.4.
6. Implementation identification: <SS> identifies the implementation of MUMPS or other software that is running on the agent. This field is for information only and does not affect the operation of the protocol. Implementers shall register their implementation identifiers with the MUMPS Development Committee, the sponsor of ANSI/MDC X11.2, to avoid duplication. Implementers who do not wish to register an identification may use an empty string.
7. Agent name: <SS> the OMI node name assigned to the agent’s node, used along with the agent’s password to authenticate that the agent is not an impersonator.
8. Agent password: <SS> a password assigned by the network manager, used by the server for authentication.
9. Server name: <SS> the OMI node name assigned to the server’s node with which the agent wishes to establish a session. This name may or may not relate to the names used to establish the circuit in the underlying protocol.
10. Extension count: <SI> the count of extension numbers that follow.
11. Extension number(s): 0 or more fields contain extension numbers that the agent proposes to use in this session. These extension numbers are assigned by the MUMPS Development Committee and need not relate directly to operation classes. See 4.11.

Figure 5 – Connect request

The fields of the connect response and their sequence shall be:

1. Major version: <SI> the major version of the OMI protocol supported by the server.
2. Minor version: <SI> the minor version of the OMI protocol supported by the server. The server shall send the highest minor version it supports that is not greater than the agent’s minor version.
3. Max values: <LI> The next 5 fields are the maximum lengths for global values, individual subscripts, global references, total message length, and limit on requests outstanding. These values shall equal the largest acceptable to the server but shall not exceed the maxima proposed by the agent in the connect request. If the server cannot satisfy this constraint, then it shall return an error condition.
   Note – When the agent requests minima that meet the portability requirements of ANSI/MDC X11.1, the server should be able to accept those values. Failure to agree means that one of the parties does not conform to the OMI protocol.
   The limit on requests outstanding shall equal 1. Larger values allow for higher performance in extensions and future versions of the protocol.
4. 8 bit: <SI> The 8 bit flag indicates whether the server agrees to use 8 bit bytes for global values and subscripts. 0 means that only 7 bit values are valid; 1 means that all 8 bit values are valid.
5. Character translation: <SI> The character translation flag indicates whether the server agrees to send characters in an untranslated form. 1 means do not translate; 0 means translate to the standard character set. See 4.4.
6. Implementation identifier: <SS> identifies the implementation of MUMPS or other software that is running on the server. See the corresponding field in the connect request.
7. Server name: <SS> the OMI node name assigned to this server’s node.
8. Server password: <SS> a password assigned by the network manager, used by the agent for authentication.
9. Extension count: <SI> the count of extension numbers that follow.
10. Extension number(s): <LI> 0 or more fields contain extension numbers that the server agrees to use in this session. Only extensions proposed by the agent shall be returned. These extension numbers are assigned by the MUMPS Development Committee and need not relate directly to operation classes. See 4.11.

Figure 6 – Connect 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.

This page most recently updated on 14-Nov-2023, 21:48:39.

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