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
 

 

ILBOABN0-Mainframe job takes a dead lock but does not abend

 
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> ABENDS & Debugging
View previous topic :: :: View next topic  
Author Message
Nishith

New User


Joined: 02 Apr 2007
Posts: 3
Location: London

PostPosted: Mon Apr 02, 2007 4:37 pm    Post subject: ILBOABN0-Mainframe job takes a dead lock but does not abend
Reply with quote

Here is teh sysout

* PROGRAM EISP040 ENDED ABNORMALLY *
* DUE TO INVALID DB2 SQL RETURN CODE. *
*********************************************
* SQLCODE: -911
* PARA # : 02-2000
* MESSAGE:
CEE3250C The system or user abend U 000 R=00000000 was issued.
From compile unit EISP040 at entry point EISP040 at compile unit offset
at address 17B29EDE.

*********************************************

It does not return a bad return code to the job. I've never used this abend routine before but I think the problem is that the ABEND-CODE is not set to 12.

*********************************************
I came across this on net fro the abend utility ILBOABN0 whci I am using.
OS/VS COBOL programs that use a CALL to ILBOABN0 can continue to CALL
ILBOABN0 when compiled with IBM COBOL. However, it is recommended that
you use the Language Environment CEE3ABD callable service instead.
Back to top
View user's profile Send private message

dick scherrer

Site Director


Joined: 23 Nov 2006
Posts: 19270
Location: Inside the Matrix

PostPosted: Mon Apr 02, 2007 7:20 pm    Post subject:
Reply with quote

Hello,

There has been no system "abend" so the code continues.

If the code detects the -911 and wants to abend, the code can cause a user abend (the code could cause an 0c7 or ocb, but those are misleading - a documented user abend will serve better). While the transaction that received the -911 did not successfully process, it is up to the code to do whatever is appropriate (rc=nn, abend, whatever. . .).
Back to top
View user's profile Send private message
Nishith

New User


Joined: 02 Apr 2007
Posts: 3
Location: London

PostPosted: Mon Apr 02, 2007 8:53 pm    Post subject:
Reply with quote

dick scherrer wrote:
Hello,

There has been no system "abend" so the code continues.

If the code detects the -911 and wants to abend, the code can cause a user abend (the code could cause an 0c7 or ocb, but those are misleading - a documented user abend will serve better). While the transaction that received the -911 did not successfully process, it is up to the code to do whatever is appropriate (rc=nn, abend, whatever. . .).


DOES THAT MEAN THE PROBELM IS THE UTILITY ?
Back to top
View user's profile Send private message
dick scherrer

Site Director


Joined: 23 Nov 2006
Posts: 19270
Location: Inside the Matrix

PostPosted: Mon Apr 02, 2007 9:14 pm    Post subject:
Reply with quote

Hello,

Probably No.

The problem is most likely that there are (at least) two processes in conflict. If you run the problem process "by itself" it will most likely work. A single process should not deadlock itself.

Most often a deadlock or "fatal embrace" occurs when multiple processes lock rows in the same tables, but in different orders.
Back to top
View user's profile Send private message
Nishith

New User


Joined: 02 Apr 2007
Posts: 3
Location: London

PostPosted: Mon Apr 02, 2007 9:29 pm    Post subject:
Reply with quote

dick scherrer wrote:
Hello,

Probably No.

The problem is most likely that there are (at least) two processes in conflict. If you run the problem process "by itself" it will most likely work. A single process should not deadlock itself.

Most often a deadlock or "fatal embrace" occurs when multiple processes lock rows in the same tables, but in different orders.


Agreed, But what I understand is that the abend utility should have abended the COBOL Program once the abend routine was called which did not happen.i.e. is the utility failing or the COBOL code?

One more thing....Has this anything to do with the older utility(ILBOABN0) being used instead of the CEE3ABD callable service ?

ANy guidance will be very helpful.
Back to top
View user's profile Send private message
William Thompson

Global Moderator


Joined: 18 Nov 2006
Posts: 3158
Location: Tucson AZ

PostPosted: Mon Apr 02, 2007 10:04 pm    Post subject:
Reply with quote

I'd guess that the call to ILBOABN0 wass called without giving it a rc....
I have no idea where to find an old enough manual.....
Back to top
View user's profile Send private message
dick scherrer

Site Director


Joined: 23 Nov 2006
Posts: 19270
Location: Inside the Matrix

PostPosted: Mon Apr 02, 2007 11:29 pm    Post subject:
Reply with quote

Hello,

You could try calling CEE3ABD instead.

From IBM:
Quote:
OS/VS COBOL programs that use a CALL to ILBOABN0 can continue to call ILBOABN0 when compiled with Enterprise COBOL. However, it is recommended that you use the Language Environment CEE3ABD callable service instead.
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 -> ABENDS & Debugging All times are GMT + 6 Hours
Page 1 of 1

 

Search our Forum:

Similar Topics
Topic Author Forum Replies Posted
No new posts SNMP trap from Mainframe bipinpeter Compuware & Other Tools 6 Wed Apr 26, 2017 3:05 pm
This topic is locked: you cannot edit posts or make replies. Mainframe Opening in Allianz India- T... Rajesh Gopinathan Mainframe Jobs 0 Wed Apr 19, 2017 11:33 am
No new posts FTP from Mainframe to Unix - with CRLF vasanthz All Other Mainframe Topics 7 Thu Mar 23, 2017 5:12 am
No new posts Want to pull the job log into a Mainf... Jishu Mukherjee Compuware & Other Tools 9 Tue Mar 21, 2017 4:48 pm
No new posts Innovations in Your Mainframe Sort Arun Raj PC Guides & IT News 4 Wed Mar 15, 2017 10:38 pm


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