Portal | Manuals | References | Downloads | Info | Programs | JCLs | Master the Mainframes
IBM Mainframe Computers Forums Index
 
Register
 
IBM Mainframe Computers Forums Index Mainframe: Search IBM Mainframe Forum: FAQ Memberlist Usergroups Profile Log in to check your private messages Log in
 

 

B37 error received but batch job did not abend

 
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> COBOL Programming
View previous topic :: :: View next topic  
Author Message
MadHadder

New User


Joined: 09 Apr 2008
Posts: 9
Location: Virginia

PostPosted: Fri Aug 20, 2010 11:23 pm    Post subject: B37 error received but batch job did not abend
Reply with quote

I've been running a cobal program fine for some time now, however it's data has increase, i know i need to correct my allocation for more DASD, my issue is that the job got a B37 but did not fail. it got a RC=00 has anyone ever had this happen?
Back to top
View user's profile Send private message

Robert Sample

Global Moderator


Joined: 06 Jun 2008
Posts: 8054
Location: East Dubuque, Illinois, USA

PostPosted: Fri Aug 20, 2010 11:43 pm    Post subject:
Reply with quote

There are products like STOP-X37 that could be installed at your site that intercept and correct space abends. There also could be a site-developed process to do the same thing. Contact your site support group to know for sure.
Back to top
View user's profile Send private message
MadHadder

New User


Joined: 09 Apr 2008
Posts: 9
Location: Virginia

PostPosted: Fri Aug 20, 2010 11:55 pm    Post subject: Reply to: B37 error received but batch job did not abend
Reply with quote

Thanks for the feedback, we actually have DIF/SRS, but the cobal program DCB is using a NOTE/POINT and DIF/SRS will not do anytype of ADDVOL to this. I just found it very weird that you can get a IEC030I B37-04,IFG0554A in the job log, but the job gets a return code 0. One would think that the job would blow up.
Back to top
View user's profile Send private message
dbzTHEdinosauer

Global Moderator


Joined: 20 Oct 2006
Posts: 6967
Location: porcelain throne

PostPosted: Sat Aug 21, 2010 2:25 am    Post subject:
Reply with quote

Quote:
One would think that the job would blow up.


has to do with the cobol program.
if you have declaratives or you are handling the file-status
and your code does not force an abend (return-code > 0),
then your job will continue to the next step.

unhandled errors normally result in abends.
improperly handled errors will result in faulty return-codes (=0).
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> COBOL Programming All times are GMT + 6 Hours
Page 1 of 1

 

Search our Forum:

Similar Topics
Topic Author Forum Replies Posted
No new posts Getting error while opening a variabl... apandey1 COBOL Programming 5 Fri May 05, 2017 12:22 pm
No new posts HLIST Utility In Batch Virendra Shambharkar TSO/ISPF 4 Fri Apr 07, 2017 3:38 pm
No new posts IDC2902I Error tzeche ABENDS & Debugging 2 Tue Mar 28, 2017 11:39 am
No new posts Batch job tuning sgandhla Testing & Performance analysis 5 Fri Mar 24, 2017 9:41 pm
No new posts MIPS/CPU consumption reduction in Batch vishwakotin DFSORT/ICETOOL 4 Sat Mar 18, 2017 5:46 pm


Facebook
Back to Top
 
Mainframe Wiki | Forum Rules | Bookmarks | Subscriptions | FAQ | Tutorials | Contact Us