reason code 00E50705

Nagaraj Pudukotai

reason code 00E50705
Hi Joe

This is what I got for the reason code
00E50705

Explanation: A subsystem termination was requested for one of the
following reasons:

1. An agent was flagged as executing in 'must complete' mode,
2. An execution unit holds a latch,
3. An agent is marked as being on a latch waiter queue, when none of
these conditions should be true. Additionally, the subsystem
termination may have been preceded by an abend with this reason code.

This termination reason code is issued by the following CSECTs:


DSNVEOT1 DSNVEUS2 DSNVEUS3


System Action: The DB2 subsystem is abended.

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 Section 3 of Diagnosis Guide and
Reference for information on identifying and reporting the problem.

The recovery routine for the CSECT issuing this reason code records
information in the variable recording area (VRA).

Problem Determination: DB2 diagnostic information may be obtained through
SYS1.LOGREC and SVC dump materials generated at the time of the original
error. Refer to the accompanying abend code to determine the failure while
in 'must complete' state. Refer to "DB2 Abend Completion Codes (X'04E' and
X'04F)" in topic4 for information about X'04F' and X'04E' abend
completion codes.

If subsystem termination was requested by module DSNVEUS2, a standard MVS
SVC dump will be generated.

The 'must complete' indicator is bit ACEMC. Latch-held indicators are in
field EBLTCHLD. Latch waiter status information is in field EBLWSI.

Usually these conditions occur as the result of a prior failure where the
associated recovery routine did not perform correct resource cleanup. The
condition may also occur if a resource manager function does not release
all latches and/or reset the 'must complete' bit before returning control
to either DSNVEUS2 or DSNVEUS3.

Hope this can be of some help to you

Thanks

Nagaraj

Hi
Everybody I can find the reason code.The message = DSNV086E and Reason =
00E50705
I run on DB2/OS390 Version 5.I sent this message to IBM in THAILAND but
nothing feed back yet.
Thanks
JOE



----------
> From: Lourdes Kishi <[login to unmask email]>
> To: [login to unmask email]
> Subject: Re: DSNV086E
> Date: 17 ¡ØÁÀҾѹ¸ì 2543 18:57
>
> Hello Joe,
>
> We received this message too! What I can tell you... is that you
> are really in trouble :-) as we are, cause it is not solved yet!.
> It started after we applied some PSP's to SHARK Disk.
> Could you tell us about your enviroment?
>
> It seens like that it happens when DB2 needs create another extent
> and there is no space in the same volume.
>
> The messages are :
> 16.17.01 STC06534 DSNB225I # DSNB5COM - BUFFER MANAGER
> I/O ERROR DURING WRITE
> DBNAME=FXDB0001
> SPACENAME=FXI37400
> DATA SET NUMBER=1
> MM ERROR CODES=X'00301114'
> DB2 REASON CODE=X'00C200C0'
> 16.17.01 STC06534 DSNB225I # DSNB5COM - BUFFER MANAGER
> I/O ERROR DURING WRITE
> DBNAME=FXDB0001
> SPACENAME=FXI40302
> DATA SET NUMBER=1
> MM ERROR CODES=X'00301114'
> DB2 REASON CODE=X'00C200C0'
> 16.17.01 STC06534 DSNB225I # DSNB5COM - BUFFER MANAGER
> I/O ERROR DURING WRITE
> DBNAME=GPDB0001
> SPACENAME=GPTSGP02
> DATA SET NUMBER=1
> MM ERROR CODES=X'00301114'
> DB2 REASON CODE=X'00C200C0'
> 16.17.01 STC06534 DSNB225I # DSNB5COM - BUFFER MANAGER
> I/O ERROR DURING WRITE
> DBNAME=EDDB0002
> DATA SET NUMBER=1
> MM ERROR CODES=X'00301114'
> DB2 REASON CODE=X'00C200C0'
>
>
> 2000017 16:17:01.32 STC06534 00000090 DSNB225I # DSNB5COM - BUFFER
MANAGER
> 414
> 414 00000090 I/O ERROR DURING WRITE
> 414 00000090 DBNAME=FXDB0001
> 414 00000090 SPACENAME=FXI37400
> 414 00000090 DATA SET NUMBER=1
> 414 00000090 MM ERROR
CODES=X'00301114'
> 414 00000090 DB2 REASON
> CODE=X'00C200C0'
> 2000017 16:17:01.33 STC06534 00000090 DSNB225I # DSNB5COM - BUFFER
MANAGER
> 415
> 415 00000090 I/O ERROR DURING WRITE
> 415 00000090 DBNAME=FXDB0001
> 415 00000090 DBNAME=FXDB0001
> 415 00000090 SPACENAME=FXI40302
> 415 00000090 DATA SET NUMBER=1
> 415 00000090 MM ERROR
CODES=X'00301114'
> 415 00000090 DB2 REASON
> CODE=X'00C200C0'
> 2000017 16:17:01.35 00000294 IEA989I SLIP TRAP ID=X13E MATCHED.
> JOBNA
> 2000017 16:17:01.35 STC06537 00000090 *DSNV086E # DB2 ABNORMAL
TERMINATION
> REASO
> 2000017 16:17:01.34 STC06534 00000090 DSNB225I # DSNB5COM - BUFFER
MANAGER
> 416
> 416 00000090 I/O ERROR DURING WRITE
> 416 00000090 DBNAME=GPDB0001
> 416 00000090 SPACENAME=GPTSGP02
> 416 00000090 DATA SET NUMBER=1
> 416 00000090 MM ERROR
CODES=X'00301114'
> 416 00000090 DB2 REASON
> CODE=X'00C200C0'
> 2000017 16:17:01.39 00000294 IEA989I SLIP TRAP ID=X13E MATCHED.
> JOBNA
> 2000017 16:17:01.39 00000294 IEA989I SLIP TRAP ID=X13E MATCHED.
> JOBNA
> 2000017 16:17:01.40 00000294 IEA989I SLIP TRAP ID=X13E MATCHED.
> JOBNA
> 2000017 16:17:01.41 00000294 IEA989I SLIP TRAP ID=X13E MATCHED.
> JOBNA
> 2000017 16:17:01.44 00000294 IEA989I SLIP TRAP ID=X13E MATCHED.
> JOBNA
>
>
> visit