Skip to main content
Modernization Hub

COND Parameter - Multi-Step Job Control

Interview Question

"We have a critical overnight batch job processing $15 billion in daily trades. The job has 12 steps:

  • Steps 1-3: Data extraction and validation
  • Steps 4-8: Transaction processing
  • Steps 9-10: Reconciliation
  • Steps 11-12: Audit logging and notifications

Step 4 (data validation) can fail with RC=8 (warnings) or RC=12 (critical errors). Business rules:

  • If RC=8: Skip processing (steps 5-8) but MUST run reconciliation with previous day's data
  • If RC=12: Skip everything except audit logging and notifications
  • If RC=0: Run everything normally

Design the COND parameter logic for this job. The batch window is 6 hours and we cannot miss it."

What This Tests

  • Complex conditional logic in production environments
  • Understanding of return code evaluation
  • Risk management and business continuity thinking
  • Ability to design fault-tolerant batch processes

Good Answer Should Include

1. COND parameter syntax on EXEC statements for steps 5-12

2. Multiple condition checking (COND=(8,LE,STEP4) vs COND=(12,LE,STEP4))

3. Discussion of why certain steps MUST run (audit, notifications)

4. Alternative: IF/THEN/ELSE/ENDIF for clearer logic in modern JCL

5. Mention of restart considerations if job fails mid-processing

Red Flags

  • ❌ Only knows "COND=(0,NE)" generic example
  • ❌ Doesn't understand business impact of skipping steps
  • ❌ Can't explain when condition evaluates to TRUE
  • ❌ Doesn't mention audit trail requirements

Follow-Up Questions

  • "What if Step 6 needs data from Step 5? How do you handle the dependency?"
  • "How would you test this logic without running production data?"
  • "If we want Step 10 to run different logic based on whether Step 4 was skipped, how do you pass that information?"

Difficulty Level

Senior

Relevant Roles

System Programmer, Batch Lead, Technical Architect