Comprehensive Guide to ISO/IEC 11756: Standard for the MUMPS Programming Language (CAN/CSA-ISO/IEC 11756-02)

ISO/IEC 11756 (adopted as CAN/CSA-ISO/IEC 11756-02 in Canada) is the international standard that defines the syntax, semantics, and runtime behavior of the MUMPS programming language—often simply called M. Originally designed for healthcare information systems, MUMPS has evolved into a general-purpose language with unique features for hierarchical data management and multi‑user transaction processing. This article examines the standard’s scope, key technical requirements, implementation highlights, and compliance guidelines.

Scope and Application

The standard formally known as ISO/IEC 11756:1999 and its Canadian adoption CAN/CSA-ISO/IEC 11756-02 specify the form and content of a MUMPS program, the data types supported, the rules for variable scope and persistence, and the behavior of built‑in functions and commands. It is intended for implementers of MUMPS interpreters, compilers, and runtime environments, as well as for developers writing portable MUMPS applications.

The scope covers:

• Full lexical and syntactic grammar of MUMPS.
• Core commands (e.g., SET, WRITE, READ, DO, GOTO, FOR, IF, ELSE) and operators.
• Intrinsic special variables (e.g., $HOROLOG, $JOB, $IO, $ZVERSION).
• Intrinsic functions (e.g., $PIECE, $EXTRACT, $ORDER, $DATA, $FIND).
• The hierarchical persistent array model (global variables).
• Transaction processing primitives (TLOCK, TCOMMIT, TROLLBACK).
• I/O device handling and error trapping.

Implementations claiming conformance must support all mandatory elements described in the standard and document any extensions or deviations.

Technical Requirements

Syntax and Data Types

MUMPS uses an extremely compact syntax where whitespace is significant. Statements are composed of a line label (optional), a command, and arguments separated by spaces. The standard defines a single data type – a string – but numeric interpretation is allowed in arithmetic contexts. Empty strings are valid and can represent logical false.

Key data elements include:

• Local variables (process‑specific, erased on process termination).
• Global variables (persistent, hierarchical arrays stored on disk or shared memory).
• Intrinsic variables (system‑provided, e.g., $HOROLOG for date/time).

Hierarchical Data Structures

A defining characteristic of MUMPS is its global array model. A global is a sparse, tree‑structured persistent map of strings to strings, indexed by subscripts of any number of levels. For example:

 SET ^Patient("12345","Name")="John Doe"

The standard prescribes the exact semantics for ordering, subscript evaluation, and the operations $ORDER, $QUERY, $DATA, and KILL. This model enables applications to dynamically create and query nested data without a schema.

Transaction Processing and Concurrency

Multi‑user environments rely on the MUMPS transaction model. The standard defines TLOCK (acquire/release locks), TSTART, TCOMMIT, and TROLLBACK to ensure atomicity and consistency. Lock granularity is per variable (global or local). The standard requires that updates to globals within a transaction be atomic and recoverable in case of a system crash.

Implementation Highlights

To produce a conforming implementation, developers must address the following:

• Compilation vs. Interpretation: The standard allows either. Most legacy systems use interpreted byte code, but modern implementations (e.g., GT.M, Caché ObjectScript) compile to native or p‑code.
• String handling performance: Since there is only one data type, string operations must be optimized. Many implementers use a string pool and reference counting.
• Global storage engine: The underlying storage of globals can be a B‑tree, hash table, or custom journaling system. The standard requires that $ORDER traversal returns subscripts in collating order.
• Compatibility with ANSI X11.1: ISO/IEC 11756 closely follows the earlier ANSI MUMPS standard (X11.1). Implementations should document which edition they supersede for seamless migration.

The table below summarises the main compliance levels defined by the standard:

Compliance and Certification

Conformance to ISO/IEC 11756 is generally demonstrated through a self‑declaration, although third‑party test suites exist (e.g., the MUMPS Validation Suite developed by the MDC). The Canadian Standard CAN/CSA-ISO/IEC 11756-02 includes a normative annex that lists recognized deviations and corrigenda. Adopters should:

1. Verify that all mandatory syntax and semantics are implemented.
2. Document any extensions (e.g., object‑oriented features, Unicode support) as non‑standard.
3. Ensure that global arrays conform to the standard’s ordering and persistence requirements.

For organizations upgrading from older MUMPS dialects, the standard provides a migration guide (Informative Annex B) that highlights differences from pre‑1999 implementations.

Frequently Asked Questions

Revision note: This article references ISO/IEC 11756:1999 and CAN/CSA-ISO/IEC 11756-02. All comments regarding conformance refer specifically to the 1999 edition and its Canadian adoption. Check with your standards body for the latest amendments. — Published 2026.