Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
A Comprehensive Guide to CAN CSA Z243.183-89 (2004): The Canadian Standard for COBOL Programming Language
Understanding the Scope, Technical Requirements, and Compliance Framework for the COBOL Language in Canada
Scope and Purpose of CAN CSA Z243.183-89 (2004)
CAN CSA Z243.183-89 (2004) is the Canadian national standard for the COBOL (COmmon Business-Oriented Language) programming language. Originally published in 1989 and reaffirmed in 2004, this standard adopts the syntax and semantics defined in ANSI X3.23-1985 (COBOL-85) as the authoritative specification for COBOL implementations within Canada. It belongs to the CSA Z243 series of information processing standards, which align with international and U.S. standards to ensure compatibility and portability of COBOL applications in business, government, and industrial data processing environments.
The scope of this standard encompasses the complete definition of the COBOL language, including:
- Source program format and character set.
- Four main divisions: Identification, Environment, Data, and Procedure.
- Data description entries, picture character strings, and levels.
- Statements and control flow, including arithmetic, conditional, input/output, and string operations.
- File organization and processing (sequential, relative, indexed).
- Classification of language elements into required, optional, and reserved categories.
Tip: While CAN CSA Z243.183-89 (2004) is based on COBOL-85, many Canadian organizations still rely on legacy COBOL systems. Understanding this standard is essential for maintaining and auditing existing code bases.
Technical Requirements and Language Features
Language Architecture
The standard defines a highly structured language organized into four mandatory divisions. The following table summarises the core data types and their usage as specified in the standard:
| Data Category | Picture Symbol(s) | Usage Clause | Typical Size (Bytes) |
|---|---|---|---|
| Alphanumeric | X(n) | DISPLAY | 1–65535 |
| Numeric Display | 9(n), S9(n) | DISPLAY | 1–18 digits |
| Computational (Binary) | 9(n), S9(n) | COMP (BINARY) | 2–8 bytes |
| Computational-3 (Packed Decimal) | 9(n), S9(n) | COMP-3 (PACKED-DECIMAL) | 1–10 bytes (n+1/2) |
| Floating Point (optional) | – | COMP-1 (short), COMP-2 (long) | 4 / 8 bytes |
| Alpha‑numeric Edited | A, X, B, 0, / | DISPLAY | As defined |
Core Requirements for Conforming Implementations
- Reserved words: A fixed list of approximately 300 reserved words that cannot be used as user-defined names.
- Level numbers: 01, 02…49, 77, 88, and special RENAMES (66). The standard enforces proper hierarchical structuring.
- Conditional statements:
IFwith optionalELSE, nested conditions, andEVALUATE(the case construct) was added in COBOL-85 and is fully specified. - Inline statements: End-of-statement markers (period) and explicit scope terminators such as
END-IF,END-PERFORM,END-READ. - File processing: Sequential, relative, and indexed file organizations; each with defined I/O statements (
READ,WRITE,REWRITE,DELETE,START). - Library and COPY: Copying source text from a library is specified to facilitate code reuse.
Warning: The standard allows three distinct levels of language subset—Standard COBOL, Intermediate COBOL, and High-Level COBOL—each with different feature sets. Implementers must clearly document the level supported. Applications written assuming the highest level may not run on compilers claiming only a lower level.
Implementation and Conformance
Conformance Requirements
CAN CSA Z243.183-89 (2004) defines conformance conditions for both implementations and programs.
- Conforming implementation: Must accept and process any source program that abides by the language specification, report any violations as errors, and provide documentation for any extensions, restrictions, or deviations.
- Conforming program: Must use only features defined in the standard, avoid implementation‑dependent items except when documented, and not rely on unspecified effects.
- Elementary and high-level subsets: The standard categorises features into required (NUCLEUS, TABLE HANDLING, SEQUENTIAL I-O) and optional modules (INTERPROGRAM COMMUNICATION, SEGMENTATION, etc.).
Implementation Highlights
The 2004 reaffirmation confirmed the 1989 text without technical changes, ensuring backward compatibility for Canadian implementations. Key points:
- Compatibility with ANSI X3.23-1985: No deviations were introduced, so code conforming to the US standard automatically conforms to this Canadian standard.
- International alignment: The standard is technically identical to ISO 1989:1985, which served as the basis for COBOL-85.
- Obsolete features: The standard retains features marked as obsolescent (e.g.,
GO TODEPENDING,DISPLAYUPON,ACCEPTFROM) to allow gradual migration; compilers may issue warnings but still must accept them.
Compliance Success: A program that strictly adheres to CAN CSA Z243.183-89 (2004) will compile without errors on any conforming compiler, provided it uses only the language subset claimed by the compiler. This level of portability is critical for large, long-lived transaction systems.
Compliance Notes and Legacy Relevance
Declaring Conformance
Suppliers of COBOL systems in Canada should clearly state conformance to CAN CSA Z243.183-89 (2004) in their documentation, specifying the level (Standard, Intermediate, High) and any modules implemented. Users should verify that their application’s required features are fully supported.
Relation to Subsequent Standards
Since 2004, the international COBOL standard has evolved. ISO/IEC 1989:2002 (and later amendments) introduced object-oriented COBOL, XML, and improved interoperability. CAN CSA Z243.183-89 (2004) was eventually superseded by later editions of the ISO/IEC standard, but it remains a stable reference for legacy systems. Many Canadian government and banking core systems continue to depend on COBOL-85 compilers that implement this very standard.
Important: For new developments, it is recommended to target a more recent standard (e.g., COBOL 2002 or COBOL 2014) to gain modern features and better tool support. CAN CSA Z243.183-89 (2004) should be used primarily for verification and maintenance of existing COBOL-85 applications.
Frequently Asked Questions
Q: Is CAN CSA Z243.183-89 (2004) still active?
A: The CSA reaffirmed this standard in 2004, meaning it was confirmed as a current standard at that date. However, the COBOL language has since been revised internationally. In practice, few compilers now certify against this specific version, but many legacy systems were built to conform to it. It is considered a historical baseline for COBOL-85 in Canada.
A: The CSA reaffirmed this standard in 2004, meaning it was confirmed as a current standard at that date. However, the COBOL language has since been revised internationally. In practice, few compilers now certify against this specific version, but many legacy systems were built to conform to it. It is considered a historical baseline for COBOL-85 in Canada.
Q: How does this standard differ from ANSI X3.23-1985?
A: CAN CSA Z243.183-89 (2004) is an adoption of ANSI X3.23-1985 without any substantive changes. The Canadian standard includes a foreword and possibly minor editorial adaptations to meet CSA formatting requirements. Therefore, the technical content is identical.
A: CAN CSA Z243.183-89 (2004) is an adoption of ANSI X3.23-1985 without any substantive changes. The Canadian standard includes a foreword and possibly minor editorial adaptations to meet CSA formatting requirements. Therefore, the technical content is identical.
Q: Does the standard cover the COBOL 2002 object‑oriented extensions?
A: No. CAN CSA Z243.183-89 (2004) is based solely on COBOL-85, which does not include object‑oriented features. For object‑oriented COBOL, the relevant standard would be ISO/IEC 1989:2002 or later adoptions by CSA.
A: No. CAN CSA Z243.183-89 (2004) is based solely on COBOL-85, which does not include object‑oriented features. For object‑oriented COBOL, the relevant standard would be ISO/IEC 1989:2002 or later adoptions by CSA.
Q: Can modern COBOL compilers support this standard?
A: Most modern COBOL compilers offer a ‘COBOL-85 compatibility mode’ that conforms closely to this standard. They may also accept syntax not present in the Canadian standard, so careful separation of legacy code from new features is advised.
A: Most modern COBOL compilers offer a ‘COBOL-85 compatibility mode’ that conforms closely to this standard. They may also accept syntax not present in the Canadian standard, so careful separation of legacy code from new features is advised.
Article prepared according to the CAN CSA Z243.183-89 (2004) specification and related technical documentation. Year of last review: 2026.