Developer track · Core · 3 days · prerequisite: CS100
Jobs, steps and datasets; condition codes and restarts; procedures, GDGs and the utility toolbox — the plumbing every estate runs on.
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.
Statement syntax that actually matters: classes, MSGCLASS, parameters, instream data, SYSOUT.
LAB Build a job from a blank member.
DSN and DISP in depth — NEW/OLD/SHR/MOD and both dispositions — SPACE, DCB, temporary datasets and referbacks.
LAB A multi-step job passing datasets forward.
COND and IF/THEN/ELSE/ENDIF, return-code propagation, abends versus RCs, and restart thinking.
LAB Conditional chains that skip and resume correctly.
Instream and cataloged procedures, symbolic parameters, overrides.
LAB Parameterize the nightly job.
Generation data groups: defining, (+1) and (0), models, cycles.
LAB A daily extract with GDG rotation.
IEFBR14, IEBGENER, SORT and ICETOOL (COPY, SORT FIELDS, INCLUDE/OMIT, SUM), IDCAMS in batch, IEBCOPY.
LAB Utility drills over real files.
A miniature nightly chain — extract, sort, report, GDG archive — restartable at any step.
LAB Break it, restart it, prove it.
Your seat is a private, full z/OS-compatible environment with JES2, utilities and GDGs in the browser — nothing to install, snapshot and reset per exercise. By the end of the course the lab harness will have verified: at least 10 job streams per student, including a restartable multi-step chain.