Start of change

DSNT305I   SUBSYSTEM FAILURE DURING command-name DATABASE COMMAND PROCESSING. RC = return-code, REASON = reason-code

Explanation

An error occurred while processing a DB2® command.

command-name
The name of the command that was being processed when the failure occurred. command-name can have one of the following values:
DISPLAY
DISPLAY DATABASE command
START
START DATABASE command
STOP
STOP DATABASE command
return-code and reason-code
The reason for the error.

return-code is a 4-byte return code.

reason-code is a 4-byte reason code.

The values of return-code and reason-code depend on which control section (CSECT) issued the message, as follows:

CSECT DSNTDCST:
  • For relational data system (RDS) subcomponent errors:
    • return-code is 8.
    • reason-code is abend code 00E30085.
  • For data manager (DM) subcomponent errors:
    • return-code consists of a 2-byte return code and a 2-byte reason code that is returned by the data manager function that is invoked by DSNTDCST.
    • reason-code is abend code 00E30086.

A record is written to SYS1.LOGREC, and an SVC dump is requested before the execution unit is abended.

CSECT DSNTDDIS:
  • return-code is 12.
  • reason-code is abend code 00E30089.

The request is abended.

CSECTs DSNTDMUL or DSNTDMSG:
  • return-code is a return code that is returned by the message generator.
  • reason-code is abend code 00E30084.

The request is abended.

CSECT DSNTDSTP:
  • return-code is 00000074.
  • reason-code is internal reason code 00E30064.

The STOP DATABASE command has failed.

This internal reason code indicates that an unexpected error occurred during DB2 catalog lookup for the STOP DATABASE command. Review the current messages in the DB2 MSTR address space and retry the command after any related error conditions have been corrected.

System action

The actions are described in the explanation for each CSECT.

System programmer response

Refer to the information for the particular abend reason code that was issued.

Problem determination

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 that spans the failure.
  • Dynamic dump, taken to SYS1.DUMPxx data set, by DB2 (04E and 04F abends).
  • Listing of SYS1.LOGREC data set, obtained by executing IFCEREP1.
  • Source listing of the failing application program.
End of change