View previous topic :: View next topic
|
Author |
Message |
Nishith
New User
Joined: 02 Apr 2007 Posts: 3 Location: London
|
|
|
|
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 |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006 Posts: 19244 Location: Inside the Matrix
|
|
|
|
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 |
|
|
Nishith
New User
Joined: 02 Apr 2007 Posts: 3 Location: London
|
|
|
|
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 |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006 Posts: 19244 Location: Inside the Matrix
|
|
|
|
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 |
|
|
Nishith
New User
Joined: 02 Apr 2007 Posts: 3 Location: London
|
|
|
|
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 |
|
|
William Thompson
Global Moderator
Joined: 18 Nov 2006 Posts: 3156 Location: Tucson AZ
|
|
|
|
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 |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006 Posts: 19244 Location: Inside the Matrix
|
|
|
|
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 |
|
|
|