|
View previous topic :: View next topic
|
| Author |
Message |
Manshadi
New User
.jpg)
Joined: 31 Aug 2005
Posts: 82
|
|
|
|
Hi,
During a display command on one of our database on DB2 subsystem the following messages appears :
-DIS DB(U5BANCS) SPACE(*) LIMIT(*)
********************************* Top of Data **********************************
DSNT305I -DS81 SUBSYSTEM FAILURE DURING DISPLAY DATABASE COMMAND
PROCESSING. RC=0000000C, REASON=00E30089
DSN9023I -DS81 DSNTDDIS 'DISPLAY DATABASE' ABNORMAL COMPLETION
******************************** Bottom of Data ********************************
Please let me know if you have any idea about that.
Best regards
Manshadi |
|
| Back to top |
|
 |
expat
Global Moderator
Joined: 14 Mar 2007
Posts: 8797
Location: Welsh Wales
|
|
|
|
| Does it not say anything meaningful in the messages and codes manauals. |
|
| Back to top |
|
|
Manshadi
New User
Joined: 31 Aug 2005
Posts: 82
|
|
|
|
No,
Nothing more message. not in MSTR, IRLM or DBM! or DIST
There is no more message. |
|
| Back to top |
|
|
GuyC
Senior Member
Joined: 11 Aug 2009
Posts: 1281
Location: Belgium
|
|
|
|
| Quote: |
00E30089
Explanation: This code is used in the REASON parameter of the DSNT305I
database command message to inform the requester that the execution unit
supporting the database command processor has terminated. Other entries in
the SYS1.LOGREC identify the source of the error.
This abend reason code is issued by the following CSECT: DSNTDMSG
System Action: A DSNT305I message appears on the console of the
requester, with an RC parameter of 12 and a REASON parameter of
X'00E30089'. This is probably a DB2 subsystem error. No SVC dump is
requested because a prior dump of the failing subcomponent is expected.
Operator Response: Notify the system programmer.
System Programmer Response: See the SYS1.LOGREC for prior failure. |
|
|
| Back to top |
|
|
Manshadi
New User
Joined: 31 Aug 2005
Posts: 82
|
|
|
|
I don't have any SVC dump.
Is there any way to find what happened? |
|
| Back to top |
|
|
dbzTHEdinosauer
Global Moderator
Joined: 20 Oct 2006
Posts: 6966
Location: porcelain throne
|
|
|
|
| maybe SYS1.LOGREC |
|
| Back to top |
|
|
Manshadi
New User
Joined: 31 Aug 2005
Posts: 82
|
|
|
|
| There is no SYS1.LOGREC on system. |
|
| Back to top |
|
|
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007
Posts: 10872
Location: italy
|
|
| Back to top |
|
|
Anuj Dhawan
Superior Member
Joined: 22 Apr 2006
Posts: 6250
Location: Mumbai, India
|
|
|
|
| Manshadi wrote: |
| There is no SYS1.LOGREC on system. |
You did not mean to say that "it's empty"? |
|
| Back to top |
|
|
Manshadi
New User
Joined: 31 Aug 2005
Posts: 82
|
|
|
|
/D logrec
RESPONSE=CPAC
IFB090I 20.29.35 LOGREC DISPLAY 797
CURRENT MEDIUM = IGNORE
because this is test lpar. |
|
| Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix
|
|
|
|
Hello,
| Quote: |
| There is no SYS1.LOGREC on system. |
Suggest you speak with the system support people. . . |
|
| Back to top |
|
|
dbzTHEdinosauer
Global Moderator
Joined: 20 Oct 2006
Posts: 6966
Location: porcelain throne
|
|
|
|
according to the display the TS provided,
it seems as if the system support people deemed it appropriate to disable logging on the test lpar.
the TS should go to his manager and explain that the current situation
does not allow for complete error handling and resolution.
the sys1.logrec could be depleted on a 3 week basis (only contain last 3 weeks),
which would relieve the systems support people of dealing with large logs. |
|
| Back to top |
|
|
|
|
