Developer track · Core · 4 days · prerequisite: CS105 or CS110
From the 3270 datastream to a working pseudo-conversational application: BMS maps, COMMAREA design, file access, paging — the way online systems are actually written.
Cohort / corporate first self-paced release follows recording
Every session ends in a lab on your own environment. Labs are machine-checked against expected outputs — you and your L&D team always know exactly where you stand.
Transactions, tasks and programs; regions; resource definition; how a transaction actually starts. The supplied transactions you will live in: CEMT, CECI, CEDF.
LAB Drive an existing transaction and watch it under CEDF.
EXEC CICS, translation and program preparation, the EIB, and RESP handling discipline instead of HANDLE spaghetti.
LAB First command-level program.
The 3270 datastream and attribute bytes; DFHMSD/DFHMDI/DFHMDF; physical versus symbolic maps; SEND MAP and RECEIVE MAP; MDTs.
LAB Build the account-inquiry screen.
Why conversational dies at scale; COMMAREA, RETURN TRANSID, and the standard skeleton every shop recognizes.
LAB Convert the inquiry to pseudo-conversational.
Input editing patterns, cursor positioning, error lines; debugging with CEDF for real.
LAB Bulletproof the screen against hostile input.
READ, WRITE, REWRITE, DELETE; browsing with STARTBR/READNEXT/READPREV/ENDBR; the paging patterns for list screens.
LAB A scrolling account list over VSAM.
LINK, XCTL and COBOL CALL; channels and containers past the 32K COMMAREA; TS queues for paging state; TD queues and ATI in brief.
LAB Split presentation from business logic across programs.
ASKTIME/FORMATTIME/START, SYNCPOINT, abend handling, storage commands — and a look at exposing a transaction as a JSON service.
LAB Capstone: the maintenance transaction, maker-checker pattern included.
Your seat is a private, full z/OS-compatible environment with a CICS-class transaction monitor and BMS in the browser — nothing to install, snapshot and reset per exercise. By the end of the course the lab harness will have verified: a working inquiry + maintenance transaction pair per student.