Skip to content

Latest commit

 

History

History
42 lines (33 loc) · 2.17 KB

File metadata and controls

42 lines (33 loc) · 2.17 KB

zOS Integration

Mainframe connector framework (TN3270 TLS, JCL submission, DB2 unloads)

  • ETL automation (DuckDB → Postgres)
  • Snapshot/diff engine
  • API framework
  • CI/CD GitOps pipelines
  • Onboarding scripts and templates
  • “One-button” agency onboarding playbooks

“We designed this platform so that onboarding is standardized and automated. Even if we execute the rollout ourselves as a small LTOD team, the workload scales predictably because each agency follows the same connector → extract → snapshot → ETL → API flow. With a team of 7–8 engineers, we can onboard 20–30 agencies per year without needing dozens of field engineers, because the automation does the work, not the people.”

“Most federal data originates on z/OS mainframes—usually DB2, VSAM, or IMS. They’re the systems of record for critical services, but they weren’t built to share data across agencies. Our solution brings modern DevSecOps and API-driven architectures to mainframe data without changing the mainframes themselves. We automate secure extraction, snapshot changes, transform the data in a modern environment, and publish standardized APIs that any agency can use. This gives the government a cross-agency data layer while respecting the reliability, security, and operational constraints of existing mainframes.”

“If DoD implementation engineers are unavailable, we can execute the rollout internally using a Limited Tour of Duty (LTOD) engineering team. LTOD talent is uniquely suited for this because LTOD engineers are modern, mission-driven technologists who can rapidly deliver cross-agency modernization with a startup-like velocity. Our platform is intentionally built to be self-contained, automated, and repeatable. This allows a small, high-skill LTOD team to onboard agencies in a predictable and scalable manner without requiring hundreds of field engineers.”

/docker
   /mainframe-emulator
      Dockerfile
      startup.sh
      hercules.cnf
      mvs/
   /mainframe-connector
      Dockerfile
      connect.sh
      submit_jcl.py

/src
   hello.cpp
   hello.jcl

/.github/workflows
   mainframe-ci.yml

/docs
   architecture.md
   pipeline-flow.md
   whitepaper.md