S/MF
StackMF Knowledge Base • z/OS
DB2 SQL & Performance 8 min read 2026-09-27

Fixing DB2 SQLCODE -501 (Cursor Not Open) and SQLCODE -502 (Cursor Already Open) in Nested Calls

A
Reviewed by Anshu
Chief Technology Architect & Mainframe Systems SME
Verified Production Runbook
Google AI Overview & Featured Snippet Quick Answer

Quick Diagnostic Summary: What Causes Fixing DB2 SQLCODE -501 (Cursor Not Open) and SQLCODE -502 (Cursor Already Open) in Nested Calls?

DB2 SQLCODE -501 occurs when attempting to FETCH from or CLOSE a cursor that is closed. SQLCODE -502 occurs when OPENing an already open cursor. Learn how to manage cursor states across nested subprogram calls and commit boundaries.

1 Incident Symptoms: What Triggers Fixing DB2 SQLCODE -501 (Cursor Not Open) and SQLCODE -502 (Cursor Already Open) in Nested Calls?

A complex batch billing cycle terminates with:

text
DSNT408I SQLCODE = -501, ERROR:  THE CURSOR IDENTIFIED IN A FETCH OR CLOSE
         STATEMENT IS NOT OPEN. CURSOR NAME = CUST_CSR

Or in a loop:

text
DSNT408I SQLCODE = -502, ERROR:  THE CURSOR IDENTIFIED IN AN OPEN STATEMENT
         IS ALREADY OPEN. CURSOR NAME = CUST_CSR

2 Technical Root Cause & Architecture Mechanics

1. SQLCODE -501:

  • The cursor was closed automatically when an intervening COMMIT was issued without WITH HOLD.
  • The cursor hit SQLCODE = +100 (End of Table) and the application issued FETCH again.

2. SQLCODE -502:

  • An application called subprogram SUB1 multiple times without closing the cursor prior to GOBACK.
  • A loop re-executed EXEC SQL OPEN CUST_CSR END-EXEC without a prior CLOSE.

3 Step-by-Step Diagnostic & Code Resolution

# 1. Declare Cursors WITH HOLD Across Commits

If a batch program issues commits while iterating through a cursor:

cobol
EXEC SQL
           DECLARE CUST_CSR CURSOR WITH HOLD FOR
           SELECT CUST_ID, BALANCE
           FROM CUSTOMER
           WHERE REGION = :WS-REGION
       END-EXEC.

WITH HOLD keeps the cursor open and maintains its position across EXEC SQL COMMIT calls!

# 2. Defensively Manage Cursor State in Subprograms

Track cursor open status in Working-Storage:

cobol
IF WS-CSR-IS-OPEN = 'N'
           EXEC SQL OPEN CUST_CSR END-EXEC
           MOVE 'Y' TO WS-CSR-IS-OPEN
       END-IF.

       EXEC SQL FETCH CUST_CSR INTO :WS-CUST-ROW END-EXEC.

       IF SQLCODE = 100
           EXEC SQL CLOSE CUST_CSR END-EXEC
           MOVE 'N' TO WS-CSR-IS-OPEN
       END-IF.

Diagnostic Reference Matrix

Attribute Specification
Target Subsystem IBM z/OS 2.4 - 3.1 • DB2 SQL & Performance
Error Signature DB2, SQLCODE -501, SQLCODE -502
Resolution SLA < 15 Minutes via Verified StackMF Runbook
Technical Reviewer Anshu, Chief Technology Architect • StackMF Architecture Pod

Architectural Prevention & Performance Tuning Checklist

? Frequently Asked Questions

What is the root cause of Fixing DB2 SQLCODE -501 (Cursor Not Open) and SQLCODE -502 (Cursor Already Open) in Nested Calls? ↓
1. SQLCODE -501:.
How do you resolve Fixing DB2 SQLCODE -501 (Cursor Not Open) and SQLCODE -502 (Cursor Already Open) in Nested Calls in production? ↓
DB2 SQLCODE -501 occurs when attempting to FETCH from or CLOSE a cursor that is closed. SQLCODE -502 occurs when OPENing an already open cursor. Learn how to manage cursor states across nested subprogram calls and commit boundaries.
How can teams prevent Fixing DB2 SQLCODE -501 (Cursor Not Open) and SQLCODE -502 (Cursor Already Open) in Nested Calls in enterprise pipelines? ↓
Always include `WITH HOLD` on cursors that process multi-commit batch update windows.

Recommended Technical Runbooks

Authoritative Reference Documentation

Official IBM manuals, Redbooks, and vendor technical advisories:

Related Topics: DB2SQLCODE -501SQLCODE -502CursorsCOBOLStored Procedures
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%.