DB2 V8 - abnormal termination - Reason code : 00D30014

Senthilkumar K

DB2 V8 - abnormal termination - Reason code : 00D30014
Hi All ,

DB2 V8 subsystem was abnormally terminated because of DIST address space
was abnormally terminated with reason code : 00D30014

Actually the above error was happened in DB2 V8 on Z/OS V1R7 but it is
working fine with Z/OS V1R6 .

Message log of DBY8DIST

10.10.04 STC02102 $HASP373 DBY8DIST STARTED
10.10.04 STC02102 IEF403I DBY8DIST - STARTED - TIME=10.10.04
10.10.07 STC02102 *DSNV086E -DBY8 DB2 ABNORMAL TERMINATION REASON=00D30014

10.10.10 STC02102 IEF450I DBY8DIST DBY8DIST - ABEND=S04E U0000
REASON=00D30014
025 TIME=10.10.10
10.10.10 STC02102 IEF404I DBY8DIST - ENDED - TIME=10.10.10
10.10.10 STC02102 $HASP395 DBY8DIST ENDED
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Message log of DBY8MSTR

S DBY8DBM1
S DBY8DIST
IEA794I SVC DUMP HAS CAPTURED: 866
DUMPID=002 REQUESTED BY JOB (DBY8DIST)
DUMP TITLE=DBY8,ABND=04E-00D30014,U=SYSOPR ,M=(?),C=810.IPC -D
SNYSIRM,M=DSNYECTE,LOC=DSNLDTML.DSNLSSRB+0426
IEF450I DBY8MSTR DBY8MSTR - ABEND=S04F U0000 REASON=00000000 032
TIME=10.10.11
IEF404I DBY8MSTR - ENDED - TIME=10.10.11
$HASP395 DBY8MSTR ENDED
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
PTF Applied for DB2

PTF UK15967 and their pre requisites , UK14489 ,UK11312 were applied .
But still error persists .

These are our environment details .

DB2 V8 Product details:

VERSION
DB2V8
PUT LEVEL
PUT0607
RSU LEVEL
RSU0609
Date of Purchase
23/07/2006

Z/OS Details

VERSION
ZOS V1R7
PUT LEVEL
PUT0511
RSU LEVEL
RSU0512

Could you please anyone pass some light on this .

Thanks and Regards
Senthil Kumar K

ForwardSourceID:NT0001A28E
ForwardSourceID:NT0001A41E
=====-----=====-----=====
Notice: The information contained in this e-mail
message and/or attachments to it may contain
confidential or privileged information. If you are
not the intended recipient, any dissemination, use,
review, distribution, printing or copying of the
information contained in this e-mail message
and/or attachments to it are strictly prohibited. If
you have received this communication in error,
please notify us by reply e-mail or telephone and
immediately and permanently delete the message
and any attachments. Thank you



---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm

Lizette Koehler

Re: Fw: DB2 V8 - abnormal termination - Reason code : 00D30014
(in response to Senthilkumar K)
According to the message (D030014) response:



Determine which sites the abending agent was connected to by examining the
DSNL027 and DSNL028 SYSLOG console messages at the site of the DB2 abend.
Obtain copies of the SYS1.LOGREC and SYSLOG data sets from each connected
site, the SVC dump at the site of the DB2 failure, and any related dumps
from each connected site. Refer to Part 2 of DB2 Diagnosis Guide and
Reference for information on identifying and reporting the problem.

What do those messages show?



If you have the maint on, perhaps you should contact the IBM support center?



Lizette


---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm