All public logs

Combined display of all available logs of Webhuis wiki. You can narrow down the view by selecting a log type, the username (case-sensitive), or the affected page (also case-sensitive).

06:13, 27 March 2026 User account Subsequentmovie talk was created
02:35, 27 March 2026 10.68.171.250 talk created page Best Customs Brokers (Created page with "Вся инфа по ссылке актуальна на текущий момент, проверено [https://www.oyeanuncios.com/profile/rrkjosef180067 https://www.oyeanuncios.com/profile/rrkjosef180067]")
02:00, 27 March 2026 User account Wholesaletyrant talk was created
20:12, 26 March 2026 User account Waggishupshot18 talk was created
04:01, 26 March 2026 AbeMartz284 talk created page User:AbeMartz284 (Created page with "Шкафы в ванную на заказ в Москве от компании МебЭстет - это практичное решение для создания удобной и функциональной системы хранения в ванной комнате с учётом индивидуальных размеров помещения и особенностей интерьера. Индивидуальное проектирование позво...")
04:01, 26 March 2026 User account AbeMartz284 talk was created
03:31, 26 March 2026 User account Headycluster90 talk was created
23:39, 25 March 2026 User account Niftyhacienda43 talk was created
22:03, 25 March 2026 User account CharisGrimes21 talk was created
16:50, 25 March 2026 Martin talk contribs created page Control flow (Created page with " = Control Flow = '''Project:''' pgcobol — Prime Numbers Application '''Version:''' 1.0 (reverse-engineered) '''Date:''' 2026-03-17 ----- == 1. Conventions == * '''PERFORM''' — synchronous paragraph call; returns to the next statement after the PERFORM. * '''CALL''' — dynamic subprogram call; passes a data block by reference; returns via EXIT PROGRAM. * '''EVALUATE TRUE''' — multi-way...")
16:49, 25 March 2026 Martin talk contribs created page IO behaviour (Created page with " = I/O Behaviour = '''Project:''' pgcobol — Prime Numbers Application '''Version:''' 1.0 (reverse-engineered) '''Date:''' 2026-03-17 ----- == 1. File I/O — primes.prt == === 1.1 File Definition (primesui.cbl) === <syntaxhighlight lang="cobol">SELECT fprinter ASSIGN TO "primes.prt" ORGANIZATION IS SEQUENTIAL FILE STATUS I...")
16:48, 25 March 2026 Martin talk contribs created page Business rules (Created page with " = Business Rules = '''Project:''' pgcobol — Prime Numbers Application '''Version:''' 1.0 (reverse-engineered) '''Date:''' 2026-03-17 ----- == 1. Primality Algorithm == === BR-ALGO-01 — Input domain === Only odd integers are tested for primality. The sieve begins at <code>test-number = 3</code> and advances in steps of 2 (<code>ADD 2 TO...")
16:47, 25 March 2026 Martin talk contribs created page Program Logic (Created page with " = Program Logic = '''Project:''' pgcobol — Prime Numbers Application '''Version:''' 1.0 (reverse-engineered) '''Date:''' 2026-03-17 ----- == 1. primesmain — Step-by-Step Logic == '''Source:''' <code>primesmain.cbl</code> '''Role:''' Entry point. Parses command-line argument, initialises UI, dispatches to processing, shuts down. <span id="procedure-division-main-i...")
16:46, 25 March 2026 Martin talk contribs created page Flow diagrams (Created page with " = Flow Diagrams = '''Project:''' pgcobol — Prime Numbers Application '''Version:''' 1.0 (reverse-engineered) '''Date:''' 2026-03-17 '''Notation:''' Mermaid flowchart / sequence diagrams ----- == 1. System-Level Call Graph == <pre class="mermaid">graph TD OS([OS / shell]) -->|command-line arg| MAIN[primesmain] MAIN -->|CALL primesui start| UI[primesui] MA...")
16:46, 25 March 2026 Martin talk contribs created page Data dictionary (Created page with " = Data Dictionary = '''Project:''' pgcobol — Prime Numbers Application '''Version:''' 1.0 (reverse-engineered) '''Date:''' 2026-03-17 ----- == 1. Conventions == {| ! Column ! Meaning |- | Name | COBOL data-name as written in source |- | Level | 01 / 03 / 05 / 07 hierarchy level |- | Picture | COBOL PICTURE clause |- | Usage | DISPLAY (default) / COMP-3 / COMP-5 |- | Source | Copybook or...")
16:44, 25 March 2026 Martin talk contribs created page Technical specifications (Created page with " = Technical Specification = '''Project:''' pgcobol — Prime Numbers Application '''Version:''' 1.0 (reverse-engineered) '''Date:''' 2026-03-17 ----- == 1. Technology Stack == {| !width="50%"| Component !width="50%"| Technology |- | Runtime | GnuCOBOL 4.0, Linux |- | SQL pre-processor | GixSQL (translates EXEC SQL … END-EXEC to GIXSQLExec calls) |- | Database server | Postgr...")
16:43, 25 March 2026 Martin talk contribs created page Business requirements (Created page with " = Business Requirements Document = '''Project:''' pgcobol — Prime Numbers Application '''Version:''' 1.0 (reverse-engineered) '''Date:''' 2026-03-17 '''Status:''' Baseline ----- == 1. Purpose == The system generates prime numbers and stores them in a relational database, and provides a printed report of all stored primes. It demonstrates a three-tier COBOL application ar...")
16:18, 25 March 2026 Martin talk contribs created page Primes programs specifications (Created page with " ```mediawiki = pgcobol Prime Numbers Application Documentation = This documentation provides a comprehensive overview of the prime numbers application developed using GnuCOBOL on Linux with PostgreSQL as the database backend. Below you will find links to various sections of the documentation. == Quick Links == * Technology Stack * Component Architecture * Business Requirements (BR) * Database Objects * [[Output File Specification]...")
15:37, 25 March 2026 Martin talk contribs created page Business Requirement Document (Created page with " = Business Requirements Document = {| !width="23%"| Field !width="76%"| Value |- | Document ID | PGCBL-BRD-001 |- | Document Type | Business Requirements Document |- | System | pgcobol — Prime Numbers Application v1.0 |- | Version | 1.0 |- | Status | Approved |- | Owner | Lead Developer |- | Author | [reverse-engineered from source artifacts] |- | Reviewers | — (pending) |- | Approved by | — (pending) |- | Created...")
15:36, 25 March 2026 Martin talk contribs created page Naming and Coding Standards (Created page with " = Naming and Coding Standard — COBOL = {| !width="23%"| Field !width="76%"| Value |- | Document ID | PGCBL-NCS-001 |- | Document Type | Naming and Coding Standard |- | System | pgcobol — Prime Numbers Application v1.0 |- | Applies to | All GnuCOBOL source files (<code>.cbl</code>) and copybooks (<code>.cpy</code>) |- | Version | 1.0 |- | Status | Approved |- | Owner | Lead Developer |- | Author | Derived from: IBM...")
15:34, 25 March 2026 Martin talk contribs created page Architecture decision records (Created page with " = Architecture Decision Records = {| !width="23%"| Field !width="76%"| Value |- | Document ID | PGCBL-ADD-001 |- | Document Type | Architecture Decision Document |- | System | pgcobol — Prime Numbers Application v1.0 |- | Version | 1.0 |- | Status | Draft — decisions marked [INFERRED] need developer confirmation |- | Owner | Lead Developer / Architect |- | Author | [reverse-engineered from source artifacts] |- | Creat...")
15:31, 25 March 2026 Martin talk contribs created page Test Traceability Matrix (Created page with " = Test Traceability Matrix = {| !width="23%"| Field !width="76%"| Value |- | Document ID | PGCBL-TTM-001 |- | Document Type | Test Traceability Matrix |- | System | pgcobol — Prime Numbers Application v1.0 |- | Version | 1.0 |- | Status | Draft — test cases not yet written; matrix is a planning skeleton |- | Owner | QA Lead / Lead Developer |- | Author | [derived from PGCBL-BRD-001 and PGCBL-NFR-001] |- | Created | 2026-03...")
15:30, 25 March 2026 Martin talk contribs created page Non-Functional Requirements (Created page with " = Non-Functional Requirements = {| !width="23%"| Field !width="76%"| Value |- | Document ID | PGCBL-NFR-001 |- | Document Type | Non-Functional Requirements |- | System | pgcobol — Prime Numbers Application v1.0 |- | Version | 1.0 |- | Status | Draft — performance and security targets require stakeholder input |- | Owner | Lead Developer / Architect |- | Author | [reverse-engineered; targets are best-practice defaults w...")
15:29, 25 March 2026 Martin talk contribs created page Assumptions and Dependencies (Created page with " = Assumptions, Dependencies, and Constraints = {| !width="23%"| Field !width="76%"| Value |- | Document ID | PGCBL-SAD-002 |- | Document Type | Assumptions, Dependencies, and Constraints Register |- | System | pgcobol — Prime Numbers Application v1.0 |- | Version | 1.0 |- | Status | Draft — requires stakeholder confirmation |- | Owner | Lead Developer |- | Author | [reverse-engineered from source artifacts]...")
15:21, 25 March 2026 Martin talk contribs created page Document Engineering (Created page with " = Document Engineering Standard = '''Document ID:''' STD-DOC-001 '''Applies to:''' All design-level and program-level specification documents in the pgcobol set '''Version:''' 1.0 '''Status:''' Approved '''Owner:''' Lead Developer / Architect ----- == 1. Purpose == This standard defines the mandatory scaffolding, metadata blocks, and governance structure that every do...")
15:00, 25 March 2026 Martin talk contribs created page Scope and applicability (Created page with " = Scope and Applicability Document = {| !width="23%"| Field !width="76%"| Value |- | Document ID | PGCBL-SAD-001 |- | Document Type | Scope and Applicability Document |- | System | pgcobol — Prime Numbers Application v1.0 |- | Version | 1.0 |- | Status | Approved |- | Owner | Lead Developer |- | Author | [reverse-engineered from source artifacts] |- | Created | 2026-03-17 |- | Last modified | 2026-03-17 |- | Classifi...")
13:26, 25 March 2026 Martin talk contribs created page Design standards (Created page with " = Document Engineering Standard = '''Document ID:''' STD-DOC-001 '''Applies to:''' All design-level and program-level specification documents in the pgcobol set '''Version:''' 1.0 '''Status:''' Approved '''Owner:''' Lead Developer / Architect ----- == 1. Purpose == This standard defines the mandatory scaffolding, metadata blocks, and governance structure that every do...")
11:28, 25 March 2026 Martin talk contribs created page Template:Ambox (Created page with "{{Ambox | type = serious | text = Serious message | style = width:70% | textstyle = color:blue; }}")
11:21, 25 March 2026 Martin talk contribs created page 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...")
11:20, 25 March 2026 Martin talk contribs created page 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...")
11:20, 25 March 2026 Martin talk contribs created page 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...")
11:19, 25 March 2026 Martin talk contribs created page 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...")
11:18, 25 March 2026 Martin talk contribs created page 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...")
11:17, 25 March 2026 Martin talk contribs created page 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...")
11:16, 25 March 2026 Martin talk contribs created page 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...")
11:14, 25 March 2026 Martin talk contribs created page 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...")
11:13, 25 March 2026 Martin talk contribs created page 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...")
11:12, 25 March 2026 Martin talk contribs created page 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...")
11:12, 25 March 2026 Martin talk contribs created page 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 *--------------------------...")
11:08, 25 March 2026 Martin talk contribs created page 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:06, 25 March 2026 Martin talk contribs created page 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...")
10:59, 25 March 2026 Martin talk contribs created page 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 #...")
22:58, 24 March 2026 Martin talk contribs created page Flow-Diagrams (Created page with " = Flow Diagrams = <blockquote>'''Document ID:''' PGCBL-FLD-001 · '''Version:''' 1.0 · '''Status:''' Approved · '''Last updated:''' 2026-03-17 '''Notation:''' Mermaid <code>flowchart TD</code> and <code>sequenceDiagram</code> </blockquote> '''← Data Dictionary''' | Home → ----- == Contents == # Top-Level Application Flow # #2-prim...")
22:41, 24 March 2026 Martin talk contribs created page Data-Dictionary (Created page with "= Data Dictionary = '''Project:''' pgcobol — Prime Numbers Application '''Version:''' 1.0 (reverse-engineered) '''Date:''' 2026-03-17 ----- == 1. Conventions == {| ! Column ! Meaning |- | Name | COBOL data-name as written in source |- | Level | 01 / 03 / 05 / 07 hierarchy level |- | Picture | COBOL PICTURE clause |- | Usage | DISPLAY (default) / COMP-3 / COMP-5 |- | Source | Copybook or program where defined |- | Description | Semantic meaning and valid values |} Condi...")
21:28, 24 March 2026 Martin talk contribs created page Technical-Specification (Created page with " = Technical Specification = <blockquote>'''Document ID:''' PGCBL-TSD-001 · '''Version:''' 1.0 · '''Status:''' Approved · '''Last updated:''' 2026-03-17 </blockquote> '''← Business Requirements''' | Data Dictionary → ----- == Contents == # System Architecture #* Three-Tier Model #* #12-inter-...")
21:24, 24 March 2026 Martin talk contribs created page Business-Requirements (Created page with " = Business Requirements = <blockquote>'''Document ID:''' PGCBL-BRD-001 · '''Version:''' 1.0 · '''Status:''' Approved · '''Last updated:''' 2026-03-17 </blockquote> '''← Home''' | Technical Specification → ----- == Contents == # Business Objective # Stakeholders # #3-functional-requirements|Functional Requirements...")
21:17, 24 March 2026 Martin talk contribs created page Primes system Design (Created page with "The Primes system was written on top of my head, aimed at creating a consistent three tier object oriented set of Cobol programs using a PostgreSQL backend. It does not serve any purpose, storing prime numbers in a database actually is a bad idea.  = pgcobol — Documentation Wiki = <blockquote>'''System:''' pgcobol — Three-Tier...")
16:53, 24 March 2026 Martin talk contribs created page Primes Software Specification (Created page with " = Software Specification — <code>Primes.cbsql</code> = <blockquote>'''Standard:''' IEEE 830 / ISO/IEC 29148 (Requirements) · IEEE 1016 (Design) · ISO/IEC 11179 (Data Dictionary) · UML 2.x Activity Diagrams '''Source:''' <code>Primes.cbsql</code> — GnuCOBOL + GixSQL preprocessed source '''Date:''' 2026-03-17 '''Status:''' Reverse-engineered </blockquote> ----- <...")
14:56, 24 March 2026 Martin talk contribs created page PrimesSQL Design (Created page with "# pgcobol Wiki > **pgcobol** — Three-tier GnuCOBOL / PostgreSQL prime-numbers application · v1.0 · reverse-engineered 2026-03-17 --- ## What is pgcobol? pgcobol is a batch COBOL application that demonstrates a clean three-tier architecture on Linux. It generates prime numbers by trial division, persists each prime in a PostgreSQL database, and produces a paginated printed report of all stored primes. There is no interactive interface; everything is driven from a...")
10:44, 23 March 2026 MaritzaConnors talk created page IPL (Created page with " Cricket in India in 2026 promises to be an exhilarating spectacle, blending the excitement of the Indian Premier League with significant international fixtures that will captivate fans across the nation. As the sport continues to evolve, 2026 stands out as a landmark year, showcasing India’s dominance and passion for cricket on multiple fronts. The Indian Premier League (IPL) remains the crown jewel of domestic cricket in India, and the 2026 season i...")

All public logs

Navigation menu

Search