User contributions for Martin

Jump to navigation Jump to search
Search for contributionsExpandCollapse
⧼contribs-top⧽
⧼contribs-date⧽
(newest | oldest) View ( | ) (20 | 50 | 100 | 250 | 500)

25 March 2026

  • 13:4713:47, 25 March 2026 diff hist −11‎ Template:Ambox ‎No edit summary current
  • 13:4313:43, 25 March 2026 diff hist +162‎ Template:Ambox ‎No edit summary
  • 13:4313:43, 25 March 2026 diff hist +185‎ COBOL Std 1 Purpose and Scope ‎No edit summary
  • 13:2613:26, 25 March 2026 diff hist +10,329‎ N Design standards ‎ Created page with "<span id="document-engineering-standard"></span> = Document Engineering Standard = '''Document ID:''' STD-DOC-001<br /> '''Applies to:''' All design-level and program-level specification documents in the pgcobol set<br /> '''Version:''' 1.0<br /> '''Status:''' Approved<br /> '''Owner:''' Lead Developer / Architect ----- <span id="purpose"></span> == 1. Purpose == This standard defines the mandatory scaffolding, metadata blocks, and governance structure that every do..."
  • 13:1613:16, 25 March 2026 diff hist +86‎ Cobol and PostgreSQL ‎ →‎Making sense of IT
  • 11:4511:45, 25 March 2026 diff hist −20‎ Template:Ambox ‎No edit summary
  • 11:3611:36, 25 March 2026 diff hist +29‎ Template:Ambox ‎No edit summary
  • 11:2911:29, 25 March 2026 diff hist −100‎ Template:Ambox ‎ Blanked the page Tag: Blanking
  • 11:2811:28, 25 March 2026 diff hist −64‎ COBOL Std 1 Purpose and Scope ‎No edit summary
  • 11:2811:28, 25 March 2026 diff hist +100‎ N Template:Ambox ‎ Created page with "{{Ambox | type = serious | text = Serious message | style = width:70% | textstyle = color:blue; }}"
  • 11:2111:21, 25 March 2026 diff hist +862‎ N COBOL Std Appendix A Approved Abbreviations ‎ Created page with "== Appendix A — Approved Abbreviations == {| class="wikitable" style="width:100%" ! Abbreviation !! Meaning !! Abbreviation !! Meaning |- | CTR || Counter || ERR || Error |- | MSG || Message || SEQ || Sequence |- | NUM || Number || TXT || Text |- | DT || Date || TM || Time |- | AMT || Amount || QTY || Quantity |- | ID || Identifier || CD || Code |- | NM || Name || SW || Switch / flag |- | WS || Working Storage || LS || Linkage Section |- | DB || Database || SQL || Str..." current
  • 11:2011:20, 25 March 2026 diff hist +1,603‎ N COBOL Std 12 Common Defect Patterns Lessons from pgcobol ‎ Created page with "== 12. Common Defect Patterns (Lessons from pgcobol) == The following defects were observed in the pgcobol reference project and are documented here as anti-patterns to avoid: {| class="wikitable" style="width:100%" ! ID !! Severity !! Description and Prevention |- | D-01 || High || Generate loop commented out in main program — generation mode silently does nothing. Never leave PERFORM stubs commented out without removing the WHEN branch that invokes them. |- | D-02..." current
  • 11:2011:20, 25 March 2026 diff hist +1,022‎ N COBOL Std 11 Build and Compilation ‎ Created page with "== 11. Build and Compilation == === 11.1 Recommended cobc Flags === {| class="wikitable" style="width:100%" ! Flag !! Purpose |- | <code>-Wall</code> || Enable all warnings; treat unexplained warnings as defects. |- | <code>-Wtruncate</code> || Warn on MOVE where source is wider than destination. |- | <code>-debug</code> || Enable PERFORM stack checking in test builds. |- | <code>-O2</code> || Enable optimisation in production builds. |- | <code>-free</code> || Only if..." current
  • 11:1911:19, 25 March 2026 diff hist +1,408‎ N COBOL Std 10 Configuration and Credentials ‎ Created page with "== 10. Configuration and Credentials == === 10.1 Externalise Credentials === Hard-coded database credentials in WORKING-STORAGE (pgcobol defect D-04) are prohibited in production code. Use one of the following patterns, in preference order: # Environment variables accepted via <code>ACCEPT … FROM ENVIRONMENT-VALUE</code> at runtime. # A configuration file read at startup, with path supplied via an environment variable. # A GnuCOBOL external data item shared from a c..." current
  • 11:1811:18, 25 March 2026 diff hist +2,211‎ N COBOL Std 9 Output Formatting Rules ‎ Created page with "== 9. Output Formatting Rules == === 9.1 Print File Definition === * Every print file must have an explicit LINAGE clause specifying lines-per-page, footing area, and bottom margin. * Record length must be stated explicitly in the FD; for report files, 132 characters is the baseline. * FILE STATUS must be checked after every OPEN, WRITE, and CLOSE. === 9.2 Page Layout === {| class="wikitable" style="width:100%" ! Element !! Rule |- | Page heading || Written on the fi..." current
  • 11:1711:17, 25 March 2026 diff hist +2,242‎ N COBOL Std 8 Data Definition Rules ‎ Created page with "== 8. Data Definition Rules == === 8.1 Numeric Usage === * Signed arithmetic fields must use the S prefix: <code>PIC S9(9)</code>. * Packed-decimal (COMP-3) is the preferred internal numeric type for arithmetic fields — smaller footprint and faster on most platforms. * Binary (COMP-5) for SQL Communications Area fields (SQLCODE etc.) to match GixSQL generated C types. * DISPLAY numeric only for print-output or host-variable character-format copybooks. {| class="wiki..." current
  • 11:1611:16, 25 March 2026 diff hist +2,853‎ N COBOL Std 7 Error Handling ‎ Created page with "== 7. Error Handling == === 7.1 Return-Code Standard === All programs and DAL interfaces use the following result-code scheme via <code>DAL-RESULT</code> / <code>SESSION-RESULT</code> / <code>UI-RESULT</code>: {| class="wikitable" style="width:100%" ! Code !! Meaning !! Required Action |- | <code>0</code> || Success || Continue processing. |- | <code>1</code> || Error — recoverable || Log message; set result; return to caller for decision. |- | <code>2</code> || End..." current
  • 11:1411:14, 25 March 2026 diff hist +3,797‎ N COBOL Std 6 Embedded SQL Standards GixSQL EXEC SQL ‎ Created page with "== 6. Embedded SQL Standards (GixSQL / EXEC SQL) == === 6.1 SQL Formatting Rules === * All SQL keywords in UPPER CASE. * Each SQL clause on its own line, indented 11 spaces from column 8 (Area B +3). * Host variables prefixed with colon (<code>:</code>) and matching the <code>DB-</code> prefix. * '''Never use <code>SELECT *</code>''' — always name columns explicitly. * Every EXEC SQL block must be followed immediately by SQLCODE evaluation. * Named database connectio..." current
  • 11:1311:13, 25 March 2026 diff hist +4,222‎ N COBOL Std 5 Program Structure ‎ Created page with "== 5. Program Structure == === 5.1 Division Order === Every program must contain all four divisions in this sequence: # IDENTIFICATION DIVISION — program identity and metadata. # ENVIRONMENT DIVISION — platform bindings, file assignments, special names (e.g. <code>CONSOLE IS scherm</code>). # DATA DIVISION — FILE SECTION, WORKING-STORAGE SECTION, LINKAGE SECTION (if a subprogram). # PROCEDURE DIVISION — all executable logic. === 5.2 Mandatory IDENTIFICATION D..." current
  • 11:1211:12, 25 March 2026 diff hist +3,304‎ N COBOL Std 4 Naming Conventions ‎ Created page with "== 4. Naming Conventions == === 4.1 General Rules === * Use hyphens (<code>-</code>) as word separators — never underscores or camelCase. * Maximum 30 characters for data names; 30 characters for paragraph names. * COBOL reserved words in ALL CAPS; user-defined names in ALL CAPS (consistent with GnuCOBOL case-insensitivity). * Names must reflect business purpose; avoid single-letter names and meaningless abbreviations. * Approved abbreviations are listed in #Append..." current
  • 11:1211:12, 25 March 2026 diff hist +2,142‎ N COBOL Std 3 Comment Standards ‎ Created page with "== 3. Comment Standards == === 3.1 Program Header Block === Every program must open with the following header block immediately after IDENTIFICATION DIVISION: <syntaxhighlight lang="cobol"> *================================================================ * PROGRAM : PROG-NAME * PURPOSE : One-line description of business function * AUTHOR : Developer name * DATE : YYYY-MM-DD * VERSION : 1.0 *--------------------------..." current
  • 11:1011:10, 25 March 2026 diff hist 0‎ COBOL Std 2 Source-Code Layout ‎No edit summary current
  • 11:0911:09, 25 March 2026 diff hist +1‎ COBOL Std 2 Source-Code Layout ‎No edit summary
  • 11:0911:09, 25 March 2026 diff hist 0‎ COBOL Std 2 Source-Code Layout ‎No edit summary
  • 11:0811:08, 25 March 2026 diff hist +1,850‎ N COBOL Std 2 Source-Code Layout ‎ Created page with "== 2. Source-Code Layout == === 2.1 Column Format === All programs use fixed-format COBOL unless the project explicitly adopts free-format (<code>cobc -free</code>). In fixed format: {| class="wikitable" style="width:100%" ! Columns !! Area !! Rule |- | 1–6 || Sequence || Leave blank or use numeric sequence; never use for logic. |- | 7 || Indicator || Asterisk (<code>*</code>) = full-line comment. Hyphen (<code>-</code>) = continuation. Blank = code. |- | 8–11 ||..."
  • 11:0611:06, 25 March 2026 diff hist +976‎ N COBOL Std 1 Purpose and Scope ‎ 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..."
  • 11:0311:03, 25 March 2026 diff hist +109‎ Cobol programming standards ‎No edit summary current
  • 10:5910:59, 25 March 2026 diff hist +1,270‎ N Cobol programming standards ‎ Created page with "= COBOL Programming Standard = '''Generic Baseline for GnuCOBOL + PostgreSQL Projects''' Version 1.0  |  2026  |  AI Lab Derived from: pgcobol project artefacts, GnuCOBOL Programmer's Guide, Broadcom COBOL Coding Standards, MainframeMaster best practices. ---- == Contents == # 1. Purpose and Scope # 2. Source-Code Layout # 3. Comment Standards #..."

24 March 2026

(newest | oldest) View ( | ) (20 | 50 | 100 | 250 | 500)
Retrieved from "https://wiki.webhuis.nl:443/index.php?title=Special:Contributions/Martin"