View previous topic :: View next topic
|
Author |
Message |
ashek15
New User
Joined: 20 Oct 2015 Posts: 48 Location: USA
|
|
|
|
Hi All
For one of our job, we received S0C4-X'11' issue - page translation exception. Pls advise what might be the root cause of this abend..as I don't think it's DBA issue. Seems like storage issue to me
Thanks |
|
Back to top |
|
|
dneufarth
Active User
Joined: 27 Apr 2005 Posts: 418 Location: Inside the SPEW (Southwest Ohio, USA)
|
|
|
|
AMODE RMODE?
Programming language? Utility?
Page Dataset issue?
Show JCL. |
|
Back to top |
|
|
Robert Sample
Global Moderator
Joined: 06 Jun 2008 Posts: 8696 Location: Dubuque, Iowa, USA
|
|
|
|
The root cause of this ABEND is that a program attempted to access storage that is not available to it. Why is the storage not available? It could be due to storage being freed before the access, or it could be an invalid address (I've seen this abend when there was a 24-bit program being passed 31-bit addresses). Although your topic title mentions page translation exception, that is NOT the only cause of this particular ABEND. Since such an ABEND often requires using IPCS to figure out the problem, you have to get your site support group involved since they work at your site and can use IPCS on the dump and we don't work at your site and hence cannot access the dump. |
|
Back to top |
|
|
ashek15
New User
Joined: 20 Oct 2015 Posts: 48 Location: USA
|
|
|
|
I found below more details from fault analyzer if it can help
Abend Code. . . . . . . . . : S0C4-X'11'
Program-Interruption Code . : 0011 (Page-Translation Exception)
A page-translation exception occurred due to one
of the following:
- The page-table entry indicated by the page-index
portion of a virtual address was outside the
page table.
- The page-invalid bit was one.
AMODE = 31, RMODE = 24
Programming language? Utility = AEXEMAIN |
|
Back to top |
|
|
steve-myers
Active Member
Joined: 30 Nov 2013 Posts: 917 Location: The Universe
|
|
|
|
99%+ of the time S0C4 ABENDs (whether they are -04, -10, or -11) represent an error in your program. In more than 50 years I have never once encountered an S0C4 that was not my program error, even when it was encountered in system code because my program gave the system a bad address. It is not a "storage" issue, whatever you think you mean by that.
Mr. Sample and dneufarth talked about AMODE and RMODE because mixing them up can potentially case this error and is something you should investigate. dneufarth's suggestion about a page data set issue is right in there with a system error: very unlikely.
You need to
- Determine the failing program (which evidently you have not yet done). This is usually (though not always) fairly easy.
- Determine where in the failing program the error occurred.
- If the failing program is in a compiled language like Cobol determine what the program was trying to do when it failed. The same is true in an Assembler program.
You or your support structure must complete the three bullets. Crying about it in these forums will just waste your time. |
|
Back to top |
|
|
Willy Jensen
Active Member
Joined: 01 Sep 2015 Posts: 712 Location: Denmark
|
|
|
|
Talk to your system support people and ask for an EREP report for the period a few minutes before the time of your abend. Locate the relevant information using the jobname info. Then contact whoever is responsible for the failing program. As prevoulsly mentioned, this is a programming error. Even if the error is indirectly caused by the data, i.e. reading record larger than expected causing storage overlay, should be handled by the program. |
|
Back to top |
|
|
PeterHolland
Global Moderator
Joined: 27 Oct 2009 Posts: 2481 Location: Netherlands, Amstelveen
|
|
|
|
Quote: |
Utility = AEXEMAIN |
That looks like a BMC DB2 utility. According to your profile you are a DB2 DBA, so its best to contact BMC. |
|
Back to top |
|
|
ashek15
New User
Joined: 20 Oct 2015 Posts: 48 Location: USA
|
|
|
|
Hi Steve
As I mentioned earlier the failing programs/module is BMC utility AEXEMAIN only. While am following up with BMC on the same, I just needed to understand the reason for this sudden/un-expected failure as our jobs have been running successfully until now. Moreover, there have been no changes to this utility since long.
Regards |
|
Back to top |
|
|
Robert Sample
Global Moderator
Joined: 06 Jun 2008 Posts: 8696 Location: Dubuque, Iowa, USA
|
|
|
|
Quote: |
I just needed to understand the reason for this sudden/un-expected failure as our jobs have been running successfully until now. Moreover, there have been no changes to this utility since long. |
The reason is something that only the vendor can tell you -- we have no way of knowing. There could have been a system-related change that affected the program or perhaps multiple programs in the application. One thing about storage-related issues is that the abending program (the victim) sometimes had nothing to do with the storage issue (it just uncovered the issue) and the problem was caused by a very different program (the perpetrator). |
|
Back to top |
|
|
Deepa Cola
New User
Joined: 29 Nov 2018 Posts: 2 Location: Sweden
|
|
|
|
Hi,
Was this issue resolved? |
|
Back to top |
|
|
Nic Clouston
Global Moderator
Joined: 10 May 2007 Posts: 2455 Location: Hampshire, UK
|
|
|
|
One would think so as it was 8 months ago. If you have a similar problem but cannot resolve it from the informtion posted then please start a new topic, preferably under COBOL. |
|
Back to top |
|
|
|