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
 

 

DB2 Abnormal Termination.

 
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> DB2
View previous topic :: :: View next topic  
Author Message
Manshadi

New User


Joined: 31 Aug 2005
Posts: 82

PostPosted: Tue Jun 29, 2010 7:20 pm    Post subject: DB2 Abnormal Termination.
Reply with quote

Hi,

Suddenly one of our DB2 system on test system is crashed and I couldn't find any useful message to find out the cause of termination.

The only messages during termination I found is as follow :

*DSNV086E -DSNP DB2 ABNORMAL TERMINATION REASON=00E50702
IEA043I SVC DUMP REACHED MAXSPACE LIMIT - MAXSPACE=00000500 MEG
IEA989I SLIP TRAP ID=X058 MATCHED. JOBNAME=DSNPDBM1, ASID=00F0.
IEA989I SLIP TRAP ID=X058 MATCHED. JOBNAME=DSNPDBM1, ASID=00F0.
IEA794I SVC DUMP HAS CAPTURED: 155
DUMPID=146 REQUESTED BY JOB (DSNPDBM1)
DUMP TITLE=DSNP,ABND=04E-00E20013,U=SYSOPR ,C=XYR00.710.BMC -D
SNB5CMA,M=DSNTFRCV,LOC=DSNSLD1 .DSNSGMN +0558
IEA848I NO DUMP WAS PRODUCED FOR THIS ABEND, DUE TO SYSTEM OR INSTALLATI
ON REQUEST
IEA848I NO DUMP WAS PRODUCED FOR THIS ABEND, DUE TO SYSTEM OR INSTALLATI
ON REQUEST
IEA989I SLIP TRAP ID=X13E MATCHED. JOBNAME=DSNPDBM1, ASID=00F0.
IEA989I SLIP TRAP ID=X13E MATCHED. JOBNAME=DSNPDBM1, ASID=00F0.
IEA989I SLIP TRAP ID=X13E MATCHED. JOBNAME=DSNPDBM1, ASID=00F0.

Any suggestion or experience??

Note: At that time one of our CICS transaction was on loop and operator canceled it and reorg online utility was running on two tablespaces.

Thanks
Manshadi
Back to top
View user's profile Send private message

enrico-sorichetti

Global Moderator


Joined: 14 Mar 2007
Posts: 10256
Location: italy

PostPosted: Tue Jun 29, 2010 7:41 pm    Post subject: Reply to: DB2 Abnormal Termination.
Reply with quote

the manuals will tell all You might want to know about the

00E50702 reason code
and
04E abend and 00E20013 reason code

a simple google with 00E50702 and 04E-00E20013 will return the links to the relevant manual pages
Back to top
View user's profile Send private message
Manshadi

New User


Joined: 31 Aug 2005
Posts: 82

PostPosted: Wed Jun 30, 2010 10:47 am    Post subject:
Reply with quote

Enrico your suggestion is very funny. Thanks
Back to top
View user's profile Send private message
enrico-sorichetti

Global Moderator


Joined: 14 Mar 2007
Posts: 10256
Location: italy

PostPosted: Wed Jun 30, 2010 11:08 am    Post subject: Reply to: DB2 Abnormal Termination.
Reply with quote

Quote:
Enrico your suggestion is very funny


simple and effective YES, funny certainly NOT. I seldom joke on IT issues

its part of Your job to search and read the manuals about the abend and reason codes

I read them for You and the suggestions given were not worth rewriting
so I decided to let You have the pleasure to read the manuals Yourself

this is a help forum, not a read the manuals for me

read the manuals if You do not understand something post quoting the unclear sentence and somebody will be glad to help You understand!

but, since I am in a very good mood, to save You some of Your precious time
I went again ove the path followed and here are the relevant pages of the manuals

Quote:
00E50702
Explanation
An error occurred while processing in SRB mode which could not be recovered.

System action
The DB2® subsystem abnormally terminates with this reason code.

Operator response
Notify the system programmer and restart DB2.

System programmer response
Scan the SYS1.LOGREC entries looking for one or more DB2 abends immediately prior to the subsystem termination. If you suspect an error in DB2, refer to Part 2 of Utility Guide and Reference for information on identifying and reporting the problem.

Problem determination
A DB2 dump of the original failure was requested by the recovery routine for DSNVEUS2 and a record written to SYS1.LOGREC. Refer to the appropriate CICS® documentation for information about X'04F' and X'04E' abend completion codes.


Quote:
00E20013
Explanation
The get tracked storage from GETMAIN function was unable to obtain sufficient storage in private area to satisfy an unconditional request.

System action
The agent is abended.

Operator response
Notify the system programmer.

System programmer response
Increase region size.

Problem determination
Diagnostic information is recorded in SYS1.LOGREC, and a DB2® dump is requested. Register 2 contains the ASID, in hexadecimal, of the private area to be printed. The trace information has the address of the parameter list.

Collect the following diagnostic items:
Console output from the system on which the job was run, and a listing of the SYSLOG data set for the period of time spanning the failure.
Dynamic dump, taken to SYS1.DUMPxx data set, by DB2 (04E and 04F abends).
SVC dump (or system dump), taken to SYS1.DUMPxx data set, as result of an operator-initiated dump command or SLIP trap exit.
Listing of SYS1.LOGREC data set, obtained by executing IFCEREP1.


as said in my previous post I simply googled for the two reason code strings as You could have done that Yourself

I have the manuals bookmarked, but it takes a bit of habit to find the relevant info
I always test before replying and usually give the easiest to follow path
in this case googling was the fastest and easiest one

there is nothing that can be done from a forum, You should , as said in the messages, contact Your support

the suggestion to increase the region size is not a permanent fix,
the situation is generally transient and might happen also after a region increase
so an analisys is needed to see what was going on at the time of the abend
and Your support must do it
Back to top
View user's profile Send private message
Manshadi

New User


Joined: 31 Aug 2005
Posts: 82

PostPosted: Wed Jun 30, 2010 11:46 am    Post subject:
Reply with quote

Thanks again for your useful manual.

"this is a help forum, not a read the manuals for me"
Yes ofcourse this is help forum I agree with you, but believe me before putting this topic to forum I tried to find the problem anywhere 'google,yahoo,IBM books and ..... but I couldn't find anything to help me find out what happened?

Thank you again.

With best regards
Manshadi
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 -> DB2 All times are GMT + 6 Hours
Page 1 of 1

 

Search our Forum:

Similar Topics
Topic Author Forum Replies Posted
No new posts SORT(DFSORT) behaving abnormal chandracdac DFSORT/ICETOOL 8 Thu Dec 10, 2015 3:58 am
No new posts Loop Termination with CLIST PROC akhi007 CLIST & REXX 6 Wed Nov 23, 2011 1:22 am
No new posts File not deleted after abnormal termi... sureshmurali JCL & VSAM 9 Fri Mar 04, 2011 9:36 pm
No new posts Clarification in cics abnormal termin... cvishu CICS 1 Thu Jan 06, 2011 12:23 pm
No new posts Lock termination with RR isolation Level Manojtyagi1979 DB2 1 Mon Dec 13, 2010 8:56 pm


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