|
|
|
|
|
|
|
| ☜ | OMI - ProgramsDraft MDC Standard | ☞ | ||||
A strictly conforming program shall use only the constructs specified in this standard, shall not exceed the limits and restrictions specified and shall not depend on extensions of an implementation.
A strictly conforming <National Body> program is a strictly conforming program, except that any limits and restrictions are replaced by those specified by the <National Body> and other extensions required by the <National Body> may be used.
A conforming program is one that is acceptable to a conforming implementation.
Table A.1 – Conformance
| Clause | Feature | Option / Value |
|---|---|---|
| Hardware Name | ||
| Hardware Version | ||
| Operating System Name | ||
| Operating System Version | ||
| Special configuration requirements | ||
| 4.2 | OSI level 4 services required | |
| 4.3 | Client? | |
| 4.3 | Server? | |
| 4.3.1 | Maximum number of client sessions | |
| 4.3.1 | Maximum number of server sessions | |
| 4.3.2 | Agent provided? | |
| 4.4 | Alternative character sets provided | |
| 4.5.5 | Translation mechanism for user ID and group ID | |
| 4.6 | Replication supported? | |
| 4.7 | Environment mapping facility | |
| 4.9 | OMI versions supported | |
| 4.10.1 | Deferred write error handling | |
| 4.10.4 | Virtual circuit error handling | |
| 4.11 | Minimum and maximum sizes of the following: | |
| gvn | ||
| gvn value | ||
| nref | ||
| messages containing the above | ||
| 4.12 | Extension numbers | |
| 5.3.7 | Server requires which parameter styles? | |
| 5.3.8 | String forms permitted by the server | |
| 5.4.28 | Does the server ever return status items that the agent has not requested? | |
| 5.4.1.f | Implementation identifier | |
|
|
|
|
|
|
|
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, 16:23:59.
For comments, contact Ed de Moel (demoel@jacquardsystems.com)