COBOL Std 1 Purpose and Scope: Difference between revisions
Jump to navigation
Jump to search
(Created page with "== 1. Purpose and Scope == This document defines the baseline coding standard for COBOL programs targeting GnuCOBOL 4.x on Linux, with optional GixSQL pre-processing for embedded PostgreSQL access. It applies to all newly written programs, to programs undergoing significant modification, and to reverse-engineering or migration work. The standard covers four concerns: * Source-code layout and formatting * Naming conventions for data items, paragraphs, copybooks, and fi...") |
Tag: Undo |
||
| (4 intermediate revisions by the same user not shown) | |||
| Line 11: | Line 11: | ||
{{Ambox |
{{Ambox |
||
name = COBOL Std 1 Purpose and Scope{{subst:void|Don't change anything on this line. It will change itself when you save.}} |
|||
| ⚫ | |||
subst = <includeonly>{{subst:substcheck}}</includeonly> |
|||
| ⚫ | |||
| ⚫ | |||
| ⚫ | |||
}} |
}} |
||
---- |
|||
---- |
|||
''[[COBOL Programming Standard|← Back to index]]'' |
|||
<hr/> |
<hr/> |
||
[[Cobol programming standards]] | [[Cobol and PostgreSQL]] |
[[Cobol programming standards]] | [[Cobol and PostgreSQL]] |
||
Latest revision as of 16:42, 25 March 2026
1. Purpose and Scope[edit]
This document defines the baseline coding standard for COBOL programs targeting GnuCOBOL 4.x on Linux, with optional GixSQL pre-processing for embedded PostgreSQL access. It applies to all newly written programs, to programs undergoing significant modification, and to reverse-engineering or migration work.
The standard covers four concerns:
- Source-code layout and formatting
- Naming conventions for data items, paragraphs, copybooks, and files
- Structural and architectural patterns (divisions, tiers, method-dispatch)
- Error handling, embedded SQL, and output formatting rules
{{Ambox name = COBOL Std 1 Purpose and Scope{{subst:void|Don't change anything on this line. It will change itself when you save.}} subst = type = notice text = Compliance note — Existing programs may deviate from this standard. Any modification touching more than 20 % of a program's statements must bring the changed portions into conformance. }}