How cicsdev/cics-genapp works
Project type and purpose
• This repository is a sample “General Insurance Application” (GenApp) for IBM CICS Transaction Server on z/OS.
• It is a monolithic, COBOL-based transaction processing system driven by 3270 “green-screen” terminals, using IBM Db2 as its data store.
• It demonstrates how to modernize a legacy CICS TS application, exercising various CICS functions (event processing, REXX execs, JCL scripts, WSIM simulation).
File structure
• Top-level files: README.md, Changes.md, license and maintainer info.
• “base/” directory contains the core GenApp code and support artifacts:
• base/src/ : COBOL programs (.cbl/.cpy) implementing policy insert/query/delete and setup logic.
• base/cntl/ : JCL job control language scripts to build, bind, delete DB2 packages, install CICS bundles.
• base/data/ : sample data files for load into Db2 tables.
• base/event-bindings/ : CICS event binding definitions (.evbind).
• base/exec/ : REXX exec scripts used in batch or CICS environments.
• base/wsim/ : IBM WSIM definition files (to simulate CICS regions for offline testing).
• base/bin/install.sh : UNIX shell wrapper to orchestrate build and install steps.
• There are README.md files in subdirectories explaining configuration, installation, testing, architecture.
README for additional insights
• The root README calls out the purpose: drive a legacy COBOL app through CICS TS, modernize to new features.
• It lists prerequisites: CICS TS, Db2.
• It directs you to base/README.md for detailed instructions on installation, building, testing, architecture.
Main components
a. User Interface
• 3270 terminals (green-screen) or a WSIM simulator connecting via TN3270 emulator to CICS TS.
b. CICS Transaction Server (z/OS region)
• Hosts COBOL transaction programs (base/src/*.cbl, .cpy).
• Executes REXX execs from base/exec/.
• Loads event bindings from base/event-bindings/*.evbind.
c. Db2 Database
• Stores insurance policy tables loaded from base/data/*.txt.
• Db2 packages are bound via JCL in base/cntl/*.jcl.
d. Build & Deployment Pipeline
• UNIX/CLI driver: base/bin/install.sh
• JCL scripts in base/cntl to compile, link, bind programs/packages.
e. WSIM Simulation
• WSIM definition files (base/wsim/*.txt) to simulate CICS API calls offline.
Relationships and interactions
• 3270 terminal → CICS TS: TN3270 (“start transaction,” display screens).
• CICS TS → COBOL programs: dispatch transaction ID to load the correct module.
• COBOL programs → Db2: SQL calls for INSERT/SELECT/DELETE policy records.
• CICS TS → REXX execs: invoked for environment setup or batch-style operations.
• JCL (batch) → MVS: compiles and links COBOL, binds Db2 packages, loads modules into CICS load library.
• WSIM → COBOL programs: simulates CICS APIs for offline testing.
Architectural patterns and design principles
• Monolithic transaction processing architecture (all business logic in COBOL under CICS).
• Clear separation of concerns:
• Transaction logic (COBOL)
• Data definitions (DB2 tables, copybooks)
• Control scripts (JCL, REXX)
• Use of standard IBM mainframe tooling for build/deploy (JCL → MVS batch, CICS bundle install, Db2 package binding).
• Event-Driven: CICS event bindings allow external triggers.
Technologies, frameworks, libraries
• IBM CICS Transaction Server for z/OS
• IBM Db2 for z/OS
• COBOL (Micro Focus/EFU)
• JCL (Job Control Language)
• REXX scripting
• IBM WSIM (CICS simulator)
Detail level
• Major components without overcrowding:
• 3270 emulator / WSIM node
• CICS TS (with labels for program library, event binding, exec library)
• Db2 (with sample policy tables)
• Build/deploy pipeline (script → JCL → load library)
• Call out important scripts and directories alongside each component.