View previous topic :: View next topic
|
Author |
Message |
arnab
New User
Joined: 13 Mar 2006 Posts: 59 Location: UK
|
|
|
|
Hi,
Can anyone help me to resolve this abend ? There is no Dump formatter to format the SYUDUMP that I am getting. We have IPCS but for this abend only SYSUDUMP gets produced so IPCS would not be of musch help.
From the DB2MSTR job the following message can be ssen:
14.39.43 STC14768 DSN3201I <DB2P ABNORMAL EOT IN PROGRESS FOR 820
820 USER=MQP1APP CONNECTION-ID=PROD CORRELATION-ID=0060JIEV
820 JOBNAME=MRPRODF ASID=00B9 TCB=008E2228
The SYSUDUMP shows:
0COMPLETION CODE SYSTEM = 04E REASON CODE = 00E70007
PSW AT ENTRY TO ABEND 077C1001 93293FD4 ILC 02 INTC 000D
0PSW ADDRESS 13293FD4 AT TIME OF ERROR DOES NOT POINT TO AN ACTIVE MODULE
Could you please let me know the probable causes for this kind of an abend.? This seems to be an internal DB2 error but not sure what statement is causing it as it happens quite frequently.
Please help. |
|
Back to top |
|
|
anv2005
New User
Joined: 14 Jul 2005 Posts: 44 Location: US
|
|
|
|
DB2 Messages and Codes manual reads: "00E70007
Explanation: A bad application-supplied address was encountered while trying to copy SQLCA back to the application program."
See the complete message text at:
00E70007
Take a look at SYMPTOM DUMP and SYSUDUMP (you may want to get SVC dump or SYSABEND dump at least) to diagnose the actual problem.
What DB2 attachment do you use? Locate application SQLCA. It could be a memory overlay related issue.
Alex. |
|
Back to top |
|
|
CICS Guy
Senior Member
Joined: 18 Jul 2007 Posts: 2146 Location: At my coffee table
|
|
Back to top |
|
|
anv2005
New User
Joined: 14 Jul 2005 Posts: 44 Location: US
|
|
|
|
DB2 terminates abnormally a thread within the client TCB's using ABEND code 04E upon many error conditions. It is VERY important to look at the exact reason code associated with the ABEND code 04E.
The current reason code is 00E70007. Hence, it's necessary to look at the exact explanation for this reason code.
Regards,
Alex. |
|
Back to top |
|
|
arnab
New User
Joined: 13 Mar 2006 Posts: 59 Location: UK
|
|
|
|
Many thanks to everyone.. |
|
Back to top |
|
|
arnab
New User
Joined: 13 Mar 2006 Posts: 59 Location: UK
|
|
|
|
Hi Again,
I traced the programs and recreated the i/p in TEST environment. This is working fine in my test environment but failing in Acceptance Test and prod environment. I tried recompiling in A/T environment, but it is still failing with same error.
Could you please help me regarding this ? |
|
Back to top |
|
|
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007 Posts: 10872 Location: italy
|
|
|
|
very little we can do from here...
Work with Your support group to
find the differences between the test and the acceptance/prod environment
and modify things accordingly
it' a mission of support to provide similar/same environment setup
in order to avoid the issue You are just facing |
|
Back to top |
|
|
arnab
New User
Joined: 13 Mar 2006 Posts: 59 Location: UK
|
|
|
|
Hiya,
Thanks to everyone for their help on this issue. I finally managed to find the root cause of this issue and resolved it.
The problem was with a module referencing outside the array bounds. Since the SSRANGE option was not on, this was not being handled causing the program to fail at some other point with a S04E.
The search for SQLCA from the SYSUDUMP gave a lot of information about the input string , so I could recreate the same in my test environment and finally find the RC.
Thanks again to everyone for their help and support..!
Cheers,
Arnab |
|
Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006 Posts: 19244 Location: Inside the Matrix
|
|
|
|
Hello Arnab,
Good to hear it is resolved - thanks for lettng us know
d |
|
Back to top |
|
|
|