Cohort bootcamps that take new hires from zero to productive on real estate work — with unlimited concurrent seats, no MIPS bill, and a private environment per student that snapshots and resets between exercises.
If your business manufactures mainframe or IBM i developers for clients, your bottleneck is environment access and proof of progress. Both are solved here: seats exist on demand, and because every lab is machine-checked, your L&D team receives exercise-level telemetry per trainee — not attendance sheets. The market benchmark for a developer bootcamp is 15 COBOL programs, 12 job streams and 100+ SQL exercises per student; our counters print from the lab harness, so the claim is verifiable per cohort.
| Bootcamp | Composition | Duration | Exit criteria (machine-checked) |
|---|---|---|---|
| Mainframe Developer Zero-to-Billable | CS100 + CS110 + CS120 + CS130 + CS140 (+ CS150) | 4–5 weeks | ≥15 COBOL programs, ≥12 job streams, ≥60 SQL exercises per student |
| IBM i Developer | CS100 (adapted) + CS200 deep | 2 weeks | subfile application + CL batch chain shipped |
| Seam Intensive | CS300 | 1 week | all five defect labs diagnosed; fix-the-drift capstone green |
| Payments / ISO 20022 | CS310 (+ byte primer) | 1 week | conformance report produced and defended |
| Operations track | CS400/410/420/430/440 selection | 1–2 weeks | scenario drills incl. scheduler chains and abend triage |
| DevOps enablement | CS450 + your pipeline | 1 week | PR-gated compile + test + golden-run gate running on your repos |
| Custom estate curriculum | course estate mirroring your client's stack | scoped | defined with your delivery leads |
Every bootcamp above is a starting point, not a fixed package. We accept full course and bootcamp customization for corporate training: mix and reorder modules, set the duration and depth to your intake, drop what your shop doesn't use and add what it does (your subsystems, your scheduler, your language mix), and swap the training estate for one that mirrors the stack your people will actually work on. Your L&D or delivery leads define the exit criteria with us; the lab graders are then written to check exactly those. Send us a target role profile and we return a proposed syllabus with per-module exit checks before you commit to anything.
Developer hiring gets the attention; operations attrition takes the systems down. These run as corporate cohorts, scenario-first — your operators drill the failure, not the slideshow.
| CS400 Mainframe Operations | 3 days | Console and SDSF fluency: queues, classes, held output, purge/requeue; abend triage from the messages; syslog literacy; the escalation call made with the right facts in hand. |
| CS410 Scheduling Operations | 2 days | CA-7-style and Control-M-style side by side: trigger chains, calendars, conditions, demand/order, late-job handling. Drills run real definition decks on a live cycle runner — a missed dependency here costs a lab point, not a settlement window. |
| CS420 CICS Administration | 2 days | Resource definition (CEDA-style), regions, transactions/programs/files, TS/TD queues, MQ trigger wiring, and the tuning concepts that matter before anyone touches a production SIT. |
| CS430 z/OS SysProg Foundations | 3 days | RACF administration with a real audit trail, catalogs and dataset management, JES2 configuration concepts. IPL and SMP/E are taught as theory and labeled as such — we don't pretend a lab can do what only your iron can. |
| CS440 IBM i Operations | 2 days | Jobs and subsystems, WRKJOBSCDE scheduling, outqueues and spool, user profiles and object authority, save/restore concepts — the daily craft of keeping a midrange estate healthy. |
| CS450 Mainframe & IBM i DevOps | 3 days | Git workflows for COBOL/RPG, pull-request-gated compiles, unit tests with statement coverage, golden-run regression gates. Ends with a working pipeline on your repos, not a demo on ours. |
| CS460 MQ Fundamentals & Admin | 2 days | Queue managers, queues and channels conceptually; MQI programs; triggering into CICS; CSQUTIL-style administration drills. |
| CS470 DB2 for DBAs | 2 days | The utility suite — LOAD, UNLOAD, REORG, RUNSTATS — binds and packages, EXPLAIN reading, and staged locking scenarios your DBAs can break safely. |
Every ops course runs on the same environments as the developer track — which means your operators can break things properly. Snapshots make courage cheap.
Give us your standards manual and an artifact pack, and the cohort trains in a system that looks like home: your dataset naming, your job-card conventions and compile PROCs, your security model, your scheduler calendars — and lab graders that enforce your coding standards, so a student who violates the house style fails the exercise before a reviewer ever would. Day one on the job stops being week three.
We build one golden "shop image", snapshot it, and clone it per seat — every student starts in your shop and resets to it between exercises. Cohort two costs almost nothing; your standards updates roll through as versioned releases.
| Your standard | How it lands in the environment |
|---|---|
| Dataset naming | catalog seeded with your HLQ and qualifier scheme — SRCLIB/COPYLIB/JCLLIB/LOADLIB trees named your way |
| JCL standards | your job-card conventions, CLASS/MSGCLASS scheme, and standard compile/link PROCs installed in a PROCLIB shaped like yours; students inherit the house style from the first SUBMIT |
| Security model | your group tree and dataset-profile conventions mirrored (with synthetic users) from a standard security-database export |
| Scheduler standards | your CA-7-style or Control-M-style definitions imported as-is — training cycles run on your chain shapes and calendars |
| Online conventions | transaction and mapset naming to your standard; region resources defined your way |
| IBM i standards | library lists, object naming, authority model and CL conventions on the i-compatible side |
| Coding standards | lab graders written to your rules — exercises are checked against your conventions, not generic ones |
Your standards, JCL, copybooks and scheduler exports are your IP, ingested under NDA — this never touches anyone's licensed software. Honest limit: we mirror your conventions and platform semantics, not third-party licensed tools your shop may use; students get our equivalents (editor, debugger, file tools).