S/MF
StackMF Knowledge Base • z/OS
DevOps & Automation 11 min read 2026-09-27

Setting up Remote COBOL/PL/I Debug Sessions in IBM Developer for z/OS (IDz) using Debug Tool

A
Reviewed by Anshu
Chief Technology Architect & Mainframe Systems SME
Enterprise Modernization Advisory
Google AI Overview & Featured Snippet Quick Answer

Executive Summary: Setting up Remote COBOL/PL/I Debug Sessions in IBM Developer for z/OS (IDz) using Debug Tool

Step-by-step guide to configuring interactive source-level debugging for batch and CICS COBOL applications inside IBM Developer for z/OS (IDz). Discover how to configure TEST compiler options, establish TCP/IP daemon connections, and trigger breakpoints dynamically.

1 Problem Statement & Architecture Context: Setting up Remote COBOL/PL/I Debug Sessions in IBM Developer for z/OS (IDz) using Debug Tool

Developers spend days inserting temporary DISPLAY statements into 5,000-line COBOL programs to trace elusive logic bugs. Re-compiling and promoting code just to inspect variables burns immense CPU and delays incident turnaround.

2 Technical Root Cause & Architecture Mechanics

IBM Developer for z/OS (IDz) pairs with the IBM z/OS Debugger backend.

When properly configured:

  • The mainframe program executes under control of Language Environment's TEST runtime parameter.
  • It opens a reverse TCP/IP connection to the developer's workstation running the IDz Debug Daemon (typically on port 8001).
  • The developer steps through live COBOL code, sets breakpoints, and inspects variables in real-time within the IDz GUI.

3 Implementation Guide & Modernization Strategy

# 1. Compile COBOL with the TEST Option

Ensure the compile step generates DWARF debugging information:

jcl
//COBSTEP EXEC PGM=IGYCRCTL,
//  PARM='TEST(SOURCE,SEPARATE),OPT(0),ARCH(14)'
//SYSDEBUG DD DSN=DEV.USER.SYSDEBUG(ACCNTREC),DISP=SHR

Using TEST(SEPARATE) stores debug tables in a separate side-file (SYSDEBUG), keeping production load module sizes minimal.

# 2. Start the IDz Debug Daemon on Your Workstation

In IDz:

1. Open the Debug perspective.

2. Ensure the daemon icon in the toolbar indicates Debug Daemon Listening on port 8001.

3. Note your workstation IP address (e.g., 10.14.20.105).

# 3. Pass TEST Runtime Options in Batch JCL

Add the CEEOPTS DD statement to your execution JCL:

jcl
//RUNSTEP  EXEC PGM=ACCNTREC
//STEPLIB  DD DSN=DEV.USER.LOADLIB,DISP=SHR
//         DD DSN=EQAW.SEQAMOD,DISP=SHR
//CEEOPTS  DD *
  TEST(ALL,*,PROMPT,TCPIP&10.14.20.105%8001:)
/*

# 4. Interactive Debugging in IDz

Upon launching the batch job, execution immediately suspends at statement 1:

  • IDz opens the COBOL source automatically.
  • Press F5 to step into, F6 to step over.
  • Hover over any variable to inspect or modify its value in memory!

Technical Specifications Matrix

Attribute Specification
Target Environment IBM z/OS • DevOps & Automation
Key Technologies IDz, COBOL, Remote Debug
Delivery SLA Accelerated Sprint Delivery via StackMF Pods
Technical Reviewer Anshu, Chief Technology Architect • StackMF Architecture Pod

Production Readiness & Verification Checklist

? Frequently Asked Questions

What is the root cause of Setting up Remote COBOL/PL/I Debug Sessions in IBM Developer for z/OS (IDz) using Debug Tool? ↓
IBM Developer for z/OS (IDz) pairs with the IBM z/OS Debugger backend.
How do you resolve Setting up Remote COBOL/PL/I Debug Sessions in IBM Developer for z/OS (IDz) using Debug Tool in production? ↓
Step-by-step guide to configuring interactive source-level debugging for batch and CICS COBOL applications inside IBM Developer for z/OS (IDz). Discover how to configure TEST compiler options, establish TCP/IP daemon connections, and trigger breakpoints dynamically.
How can teams prevent Setting up Remote COBOL/PL/I Debug Sessions in IBM Developer for z/OS (IDz) using Debug Tool in enterprise pipelines? ↓
Use `TEST(NOHOOK,SEPARATE)` for production modules to enable on-demand diagnostics without performance penalties.

Recommended Technical Runbooks

Authoritative Reference Documentation

Official IBM manuals, Redbooks, and vendor technical advisories:

Related Topics: IDzCOBOLRemote DebugDebug ToolEclipsez/OS Debugger
Diagnostic Runbook Notice & Nominative Fair Use Disclaimer

This diagnostic runbook is published by StackMF Technologies LLP for educational and architectural reference only. All code snippets, JCL, and procedures are provided "AS IS" without warranty of any kind. Always test changes thoroughly in non-production sysplex environments prior to production rollout.

IBM, z/OS, CICS, Db2, IMS, RACF, and IDz are registered trademarks of International Business Machines Corporation. Broadcom, CA-7, and Endevor are trademarks of Broadcom Inc. All other trademarks belong to their respective owners and are referenced under the Nominative Fair Use Doctrine (US Lanham Act 15 U.S.C. ยง 1125 / Section 30 of the Indian Trade Marks Act, 1999) solely for technology compatibility and diagnostic identification. StackMF Technologies LLP is an independent consulting entity not affiliated with or endorsed by these vendors. View Full Legal & IP Policy →

Enterprise Advisory

Struggling with Critical Mainframe Incidents or Vendor Renewal Pressure?

StackMF deploys certified Senior Mainframe Engineers fluent in both z/OS legacy internals (COBOL, DB2, CICS, VSAM, CA-7, Endevor) and modern cloud stacks (React, Kafka, AWS, Git). Onboard dedicated pods in 48 hours or cut Broadcom licensing by 60%.