handling VSAM status code 35 that is VSAM empty

In this Mainframe Forum - You can post your queries on JCL,VSAM,COBOL,DB2,IMS Abend codes , solutions etc..

Moderator: Moderator Group

Post Reply
Posts: 1
Joined: Sat Jan 03, 2015 12:14 pm

handling VSAM status code 35 that is VSAM empty

Post by neeti » Sat Jan 03, 2015 12:37 pm

My cobol program reads a VSAM file that may or may not be empty. Is there a way by which we can handle 35 without having to check status 35. Something if can do with the mode in which the file is opened or can we handle it in JCL itself?

William Collins
Active Member
Posts: 732
Joined: Thu May 24, 2012 4:07 am

Post by William Collins » Mon Jan 05, 2015 5:18 pm

What's your problem with checking for 35?


Topic deleted by Admin

Post by academyindia4 » Thu Jan 21, 2016 11:17 am

<< Content deleted By Admin >>

Post Reply


Free tutorials from mainframegurukul
  • JCL Tutorial
    Covers all important JCL concepts.
  • Cobol Tutorial
    This tutorials covers all Cobol Topics from STRING to COMP-3.
  • DB2 Tutorial
    DB2 Tutorial focuses on DB2 COBOL Programming.
  • SORT Tutorial
    This Tutorial covers all important aspects of DFSORT with examples
  • CICS Tutorial
    This CICS tutorial covers CICS concepts and CICS Basics, CICS COBOL Programming.
Mainframe Interview questions

Other References
Mainframe Tools and others