Page 1 of 1

handling VSAM status code 35 that is VSAM empty

Posted: Sat Jan 03, 2015 12:37 pm
by neeti
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?

Posted: Mon Jan 05, 2015 5:18 pm
by William Collins
What's your problem with checking for 35?

Topic deleted by Admin

Posted: Thu Jan 21, 2016 11:17 am
by academyindia4
<< Content deleted By Admin >>