From CC 0008 to CC 0000 — debugging enterprise JCL on IBM z/OS so production never stops.

Imagine you have a giant, ultra-reliable computer — so powerful it runs the banking systems, airline reservations, and healthcare networks that billions of people depend on every single day. That computer is an IBM Mainframe, and the language used to tell it what jobs to run and what files to use is called JCL (Job Control Language).

This project is about finding and fixing a bug in a JCL program on a real IBM mainframe (z/OS). The broken program was supposed to combine three data files — guitar nicknames, brand names, and artist names — into one neat report called "Legendary Guitars." But it was missing a critical file instruction, causing it to crash with an error code.

I found the bug, wrote the fix, and got the job running perfectly — from CC 0008 (error) to CC 0000 (success). ✅

 ┌─────────────────────────────────────────────────────┐
 │              IBM Mainframe (z/OS)                   │
 │                                                     │
 │  📂 ZXP.PUBLIC.SOURCE                               │
 │     ├── NICKNAME  ──┐                               │
 │     ├── BRAND    ───┼──► COMBINE Program ──► 🎸 GUITAR Report
 │     └── ARTIST   ──┘  (IRXJCL + REXX)              │
 │                                                     │
 │  JES2 Job Scheduler runs everything                 │
 └─────────────────────────────────────────────────────┘

flowchart TD
    A([🧑‍💻 Developer in VS Code]) --> B[Copy JES2JOB1 from Public Library]
    B --> C[Paste into Personal JCL Dataset]
    C --> D[Review the JCL Code]
    D --> E[Submit Job to JES2 Scheduler]
    E --> F{Check Condition Code}
    F -->|CC 0008 — Something is wrong| G[Read JESYSMSG Error Log]
    G --> H[Discover: Missing ARTIST DD Statement]
    H --> I[Add the Missing Line of JCL]
    I --> J[Save Changes and Resubmit]
    J --> K{Check Condition Code Again}
    K -->|CC 0000 — All good!| L[🎸 GUITAR Report Generated]
    K -->|Still failing| I
    L --> M([✅ Challenge Complete!])

    style A fill:#1565C0,color:#fff,stroke:#0D47A1
    style M fill:#2E7D32,color:#fff,stroke:#1B5E20
    style F fill:#E65100,color:#fff,stroke:#BF360C
    style K fill:#E65100,color:#fff,stroke:#BF360C
    style H fill:#B71C1C,color:#fff,stroke:#7F0000
    style L fill:#1565C0,color:#fff,stroke:#0D47A1

flowchart LR
    A[Submit Job] --> B[CC 0008 Error]
    B --> C[Open JESYSMSG Log]
    C --> D[Error: IRX0670E
EXECIO GET/PUT Failure]
    D --> E{What is missing?}
    E --> F[REXX COMBINE script
needs 3 inputs]
    F --> G[JCL only has 2:
NICKNAME + BRAND]
    G --> H[Missing: ARTIST DD Statement]
    H --> I[Add ARTIST DD Statement]
    I --> J[Resubmit]
    J --> K[CC 0000 ✅ Success]

    style B fill:#c62828,color:#fff
    style K fill:#2e7d32,color:#fff
    style H fill:#f57f17,color:#fff
    style D fill:#6a1b9a,color:#fff

Navigate to ZXP.PUBLIC.JCL and locate the member JES2JOB1. Right-click and select Copy.

Paste the member into your personal JCL dataset so you can edit it without affecting the shared library.

Open the member and read through the code. It looks like it runs IRXJCL with a COMBINE parameter — but something critical is missing.

Right-click your copy of JES2JOB1 and select Submit Job. Note the job number that appears in the bottom-right corner.

Go to the JOBS section in VS Code. You'll see the job completed with CC 0008 — that's an error code. Something broke.

🚨 CC 0008 = Error. The job ran but something went wrong. Time to investigate.

Expand the job output and look at JESYSMSG. There is one very clear clue buried in the output.

🔎 The error is: IRX0670E EXECIO error while trying to GET or PUT a record This means the REXX script tried to read a file that wasn't defined in the JCL.

Go back to your JCL and add the missing //ARTIST DD statement. Copy the pattern from the BRAND line and change the DD name and dataset member.

✅ The fix is one line: //ARTIST DD DSN=ZXP.PUBLIC.SOURCE(ARTIST),DISP=SHR

Always save before resubmitting. If you forget to save, it will run the old broken version again. Right-click → Submit Job.

Check the JOBS section again. This time you should see CC 0000 — no errors. The GUITAR report has been written to your OUTPUT dataset.

//JES2JOB1 JOB
//COMBINE  EXEC PGM=IRXJCL,PARM='COMBINE'
//SYSEXEC  DD DSN=ZXP.PUBLIC.EXEC,DISP=SHR
//SYSTSPRT DD DSN=&SYSUID..OUTPUT(GUITAR),DISP=SHR
//SYSTSIN  DD DUMMY
//NICKNAME DD DSN=ZXP.PUBLIC.SOURCE(NICKNAME),DISP=SHR
//BRAND    DD DSN=ZXP.PUBLIC.SOURCE(BRAND),DISP=SHR

🚨 The ARTIST data file is missing! The COMBINE program expects three inputs but only two are provided.

//JES2JOB1 JOB
//COMBINE  EXEC PGM=IRXJCL,PARM='COMBINE'
//SYSEXEC  DD DSN=ZXP.PUBLIC.EXEC,DISP=SHR
//SYSTSPRT DD DSN=&SYSUID..OUTPUT(GUITAR),DISP=SHR
//SYSTSIN  DD DUMMY
//NICKNAME DD DSN=ZXP.PUBLIC.SOURCE(NICKNAME),DISP=SHR
//BRAND    DD DSN=ZXP.PUBLIC.SOURCE(BRAND),DISP=SHR
//ARTIST   DD DSN=ZXP.PUBLIC.SOURCE(ARTIST),DISP=SHR   ← Added this line

✅ One line. That's all it took. The ARTIST DD statement tells the job where to find the artist names.

DD = Data Definition — it's how you tell the mainframe "here's a file the program needs"

Think of Condition Codes like the check engine light in your car:

graph TD
    subgraph VSCode["💻 VS Code + IBM Z Open Editor"]
        dev[Developer Workspace]
        zowe[Zowe Explorer Extension]
    end

    subgraph zOS["🖥️ IBM z/OS Mainframe"]
        jes2[JES2 Job Scheduler]
        irxjcl[IRXJCL — REXX Interpreter]
        rexx[COMBINE REXX Script]

        subgraph datasets["📂 Datasets"]
            exec[ZXP.PUBLIC.EXEC]
            nick[SOURCE: NICKNAME]
            brand[SOURCE: BRAND]
            artist[SOURCE: ARTIST]
            output[OUTPUT: GUITAR]
        end
    end

    dev --> zowe
    zowe -->|Submit JCL Job| jes2
    jes2 --> irxjcl
    irxjcl --> rexx
    exec --> rexx
    nick --> rexx
    brand --> rexx
    artist --> rexx
    rexx --> output

    style VSCode fill:#1a1a2e,color:#fff,stroke:#4a4a8a
    style zOS fill:#0d2137,color:#fff,stroke:#1565C0
    style datasets fill:#0a3d62,color:#fff,stroke:#1565C0

💡 Every DISP=SHR in this project ensures source files are read-only — no accidental overwrites possible.

mindmap
  root((JCL2 Project))
    IBM Mainframe
      z/OS Operating System
      JES2 Scheduler
      IRXJCL Interpreter
      REXX Scripting
    Development Tools
      VS Code
      IBM Z Open Editor
      Zowe Explorer
    Concepts Mastered
      JCL Syntax
      DD Statements
      Dataset Management
      Error Code Analysis
      Batch Job Debugging
    Output
      GUITAR Dataset
      Legendary Guitars Report

IRX0670E EXECIO error while trying to GET or PUT a record

╔══════════════════════════════════════════════════════╗
║          IBM Z Xplore — Advanced Badge               ║
║                                                      ║
║  Challenge: JCL2 — Fix JCL and Get That Job Running  ║
║  Level:     Advanced                                 ║
║  Status:    ✅ Completed (CC 0000)                    ║
║  Platform:  IBM z/OS                                 ║
╚══════════════════════════════════════════════════════╝

ibm-zos-jcl-debugger/
│
├── README.md                      ← You are here
├── JCL/
│   ├── JES2JOB1_broken.jcl        ← Original broken JCL (CC 0008)
│   └── JES2JOB1_fixed.jcl         ← Fixed JCL with ARTIST DD (CC 0000)
├── OUTPUT/
│   └── GUITAR.txt                 ← Final Legendary Guitars report
└── docs/
    ├── JCL2_assignment.pdf        ← Original IBM Z Xplore challenge brief
    └── images/
        ├── ibm_z_hero.png
        ├── step1_copy_dataset.png
        ├── step2_paste_menu.png
        ├── step3_jcl_code.png
        ├── step4_submit_job_list.png
        ├── step5_jobs_cc0008.png
        ├── step6_jesysmsg_error.png
        ├── step7_jcl_fix.png
        ├── step8_submit_fixed.png
        └── step9_guitar_output.png

If your team works with mainframes, cloud infrastructure, or backend systems — and you need an engineer who can own a problem from error log to fix — I'd love to talk.