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.

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, you might need to report the problem. For information about identifying and reporting the problem, see Collecting diagnostic data.

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) 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.