COBOLSTACK.COM
//ENV     EXEC PGM=PROVISION,PARM='FIVE.MINUTES'

A mainframe in the browser in five minutes

Full z/OS-compatible environments — EBCDIC datasets, JCL and JES2, COBOL, HLASM, PL/I, REXX, Natural, Easytrieve and SAS-language engines, VSAM, DB2-class SQL, Adabas-class and IDMS-class databases, IMS DL/I, CICS-class transactions with BMS 3270 — and an IBM i-compatible companion with RPG IV, CL, DDS, 5250 and subfiles. No LPAR queue, no MIPS bill, no IBM licence audit.

//SHAPES  DD DSN=ENV.SHAPES,DISP=SHR

Every shape an estate team needs

//* every environment: browser 3270 + Studio workbench, snapshot/restore,
//* admin API, per-instance isolation. Hosted by us, on your cloud (BYOC),
//* or on hardware we set up on your premises.
ShapeForStatus
Training seatscohorts and self-paced learners; snapshot/reset per exercise; lab telemetryAvailable
Development environmentsdeveloper seats with the Studio workbench: editor, debugger, unit tests with coverage, SQL viewsAvailable
Project test environmentsintegration and UAT sandboxes per project, loaded with masked or synthetic data, resettable per test cycleAvailable
Dedicated instance
("your own LPAR")
a single-tenant environment for your team — hosted, BYOC on your cloud account, or installed on-premises; release/upgrade path includedAvailable
Demo / POC estatespre-built synthetic estates (banking, cards, insurance, payroll, utilities, payment switch…) for demos, tenders and proofs of conceptAvailable
Modernization rehearsala mirror of your estate's shape where the migration team rehearses changes and replays cycles before touching real ironAvailable
Shop-standard imagea golden environment built to your enterprise standards — dataset naming, PROCs and job cards, security model, scheduler calendars, coding-standard graders — snapshotted and cloned per seat or per project; versioned with your standards updatesAvailable
Conformance benchthe ISO 20022 rehearsal rig: synthetic core generating authentic traffic against your mappingAvailable
CI runnerscompile + run + unit-test COBOL/RPG on every pull request from GitHub/GitLabDeferred
Archive estatesa wound-down application kept queryable and re-runnable instead of paying licence rentFuture

Any shape can be built as a shop-standard image: give us your standards manual and artifact pack and the environment follows your conventions — see how that works for cohorts, or ask for the same for project teams.

Modern enterprise server cabinet in a machine room
//SPEC    DD DSN=TECH.FACT.SHEET

Technical fact sheet

Written for the engineer doing the evaluation. Ask us for anything not listed; if we don't support it, we'll say so in writing.

BatchJCL with JOB/EXEC/DD, DISP semantics, COND and IF/THEN/ELSE, in-stream and cataloged PROCs with symbolics/overrides, referbacks, GDGs with model DSCBs, JES2-style spool with classes and held output. Utilities: IEFBR14, IEBGENER, IEBCOPY, IDCAMS, SORT/ICETOOL (INCLUDE/OMIT/SUM/OUTREC and friends).
LanguagesCOBOL (full compile/link/run pipeline, copybooks, subprograms, intrinsic functions), HLASM-class assembler, PL/I, REXX and CLIST with ISPF dialogs and edit macros, Natural-class 4GL (maps, DDMs, Adabas direct calls), ADS-class dialogs (IDMS side), Easytrieve-class reporting (field definitions, overlays, REPORT), SAS-language engine (data steps + the core PROCs). IBM i side: RPG IV free-form and fixed-form, CL, DDS.
DataEBCDIC (CP037) datasets — PS/PDS/VSAM (KSDS/ESDS/RRDS/LDS with AIX/PATH), byte-true COMP-3/zoned storage; DB2-class SQL engine with SPUFI, embedded SQL, cursors, BIND-style prep; IMS DL/I-class database with PSB/DBD semantics and Boolean SSAs; Adabas-class database behind the Natural engine (direct calls, DDMs); IDMS-class CODASYL database (navigational DML, schema/subschema, sets); live SQL views over datasets, reachable from standard Postgres-protocol clients.
OnlineCICS-class transaction monitor: BMS mapsets (DFHMSD/MDI/MDF), pseudo-conversational COMMAREA patterns, channels/containers, TS/TD queues, supplied-transaction equivalents (CEMT/CECI/CEDF-style), JSON service exposure. IMS TM-class message processing. MQ-class queue manager with triggering into CICS.
IBM i sideA full midrange companion environment — libraries/objects/members, RPG IV, CL, DDS, 5250, SQL, journaling, spool. Detailed in its own table below.
Security & opsRACF-class users/groups/resources with audit trail, scheduler with CA-7-style and Control-M-style definition import and cycle runner, syslog, operator console, FTP server, TN3270E.
Developer surfaceBrowser 3270 + the Studio workbench: editor with syntax awareness, source-level debugger with breakpoints and storage inspection, unit-test runner with statement coverage, golden-run capture/compare, BMS screen gallery, SQL grid.
AutomationREST admin API (~100 operations, generated OpenAPI spec, scoped tokens), instance lifecycle API, snapshot/restore, audit log, metrics endpoint. Everything the UI does, the API does. For existing clients, the same surface is available to AI agents as governed MCP tools — see the MCP page.
DeploymentHosted by us; BYOC agent on your AWS/Azure account; or on-premises install on hardware we set up. Single-tenant per instance. Release/upgrade path with rollback.
//IBMI    DD DSN=AS400.FACT.SHEET

The IBM i side, in full

The midrange half is a first-class environment, not a footnote — every row below is backed by shipped, test-suited engine code. Try it live: SteelFrame X ↗.

LanguagesRPG IV free-form and fixed-form, including subprocedures, nested programs and embedded SQL (SQLRPGLE-style); CL programs with parameters, MONMSG, OVRDBF and '+' continuation handling; REXX via STRREXPRC; DDS as the definition language for physical, logical, display and printer files.
DatabasePhysical and logical files with keys and record formats; self-describing layouts via DSPFFD; SQL with interactive STRSQL and RUNSQLSTM DDL scripts; journaling (CRTJRN, STRJRNPF); a DRDA server speaking the DB2 wire protocol plus the classic database host server — standard DB2 clients connect.
5250 & screensThe 5250 workstation protocol with browser sign-on and TN5250 for real emulators; DDS display files with the full subfile pattern — load-all and page-at-a-time, SFLPAG/SFLSIZ, position-to, function keys; system panels incl. WRKMBRPDM-style member management.
Output & spoolDDS printer files rendered faithfully — EDTCDE edit codes, O-specs, overflow indicators; output queues with WRKOUTQ, CPYSPLF and spool download.
APIs & queuesQCMDEXC command execution from programs; data queues (QSNDDTAQ/QRCVDTAQ); message APIs (QMHSNDPM) — the integration idioms real RPG shops use.
OperationsJobs and subsystems (WRKACTJOB), batch via SBMJOB, the job scheduler (WRKJOBSCDE), user profiles and object authority, save/restore (SAVLIB/RSTLIB).
ConnectivityBrowser 5250, TN5250, FTP, host servers (signon, database, server mapper), DRDA. Same admin API, snapshot and instance machinery as the z/OS side.

Pricing

Pricing depends on cores, environments and seats — every quote is sized to your estate and team.

Every environment is licensed, not sold: a licence fee plus annual support & maintenance, with fixes and upgrades included while support is active. What the licence covers, the support response targets and how fees are structured are set out on licensing & support.

//TERMS   DD DSN=EMULATOR.VS.ENVIRONMENT

Searching for a "mainframe emulator" or "AS400 simulator"?

What you'll find elsewhere splits in two: hobbyist emulators that require operating-system images you may not have the right to run, and vendor dev/test products that require IBM entitlement and per-seat licences in the thousands of dollars. CobolStack is a third thing — a clean-room compatible environment: independently implemented from published specifications, licensed for you to use, running in the browser in minutes. If "mainframe practice environment", "z/OS sandbox", "TSO/ISPF practice", or "AS400 practice online" is what you meant — this is that, with the honest limits stated below.

//TRUTH   DD DSN=IS.AND.IS.NOT

What it is — and is not

Valid on CobolStack environments

  • Record layouts, EBCDIC and packed-decimal encodings, file formats
  • COBOL/RPG arithmetic and program behavior; JCL and CL semantics; control flow
  • Batch chains, scheduling semantics, spool and return codes
  • Throughput of our own engine; error paths defined by published specification

Not valid — by design

  • Real-system timing, locking and contention minutiae
  • Abend behavior beyond documented semantics; performance of licensed iron
  • Anything only your licensed system can prove — your system remains the sole conformance authority

Independent clean-room implementation. Specification-conformant, never "identical" — and we put that in writing on every proposal.