Operations Fundamentals
Console Diagnostics Sprint
Tight two-week sprint on interpreting messages, tracing failures, and coordinating with application owners.
- Duration
- 2 weeks · virtual live
- Format
- Virtual live
- Skill level
- Intermediate
- Certification path
- Incident readiness
- Team access
- Single seat
- Cohort start
- 2026-10-14
Tuition reference
₩265,000
Informational only — no checkout here. Discuss invoicing, cohort packaging, or summit bundles via Contact.
Course lead
Evelyn Cho
Coordinates summit content and keeps sprint scenarios aligned with current z/OS maintenance streams.
Description
Operators who already navigate ISPF still freeze when a flood of messages arrives mid-shift. This sprint compresses real incidents from transportation, retail, and public-sector labs into ninety-minute blocks. You learn to triage by severity, capture evidence before recycling address spaces, and communicate with application teams without jargon overload. Every scenario includes a facilitator debrief that links symptoms back to subsystem design so the pattern sticks beyond the classroom.
What is included
- Six scripted incidents with increasing ambiguity
- Message handbook you can adapt to your own enterprise taxonomy
- Role-played bridge calls with strict timeboxes
- Evidence packet layout external reviewers accepted in past audits
- SMF excerpt reading without building a full analytics pipeline
- Checklist for when to engage hardware support versus software support
Outcomes
- Produce a concise incident timeline within ten minutes of detection.
- Select the correct diagnostic command set for three common failure classes.
- Escalate with enough context that the next tier avoids duplicate work.
Participant questions
Experience notes
“The bridge-call simulation felt awkward at first, but it fixed our habit of over-explaining to app teams.”