DSNB225I   csect-name- BUFFER MANAGER I/O ERROR DURING function, DSNAME = data-set-name , MM ERROR CODES=X'aaaaaaaa' DB2 REASON CODE=X'reason-code'

Explanation

DB2® encountered an I/O error.

csect-name
The name of the control section that issued the message.
function
The function that was being performed when the error occurred. Possible values are READ, WRITE, CASTOUT, or FORMAT.
data-set-name
The name of the data set on which the I/O operation was being performed.
aaaaaaaa
Error information that is returned by the media manager at the time of the failure. This information used for error analysis by IBM® Software Support.
reason-code
The DB2 reason code value that indicates the reason for the failure. For explanations of reason codes, see DB2 reason codes.

System action

Except for a castout error, the application terminates with abend X'04E' and reason code 00C200A4 or 00C200C0. If an error occurs during a castout operation, processing continues.

Operator response

Notify the system programmer.

See the information for the given reason code and take the specified action.

System programmer response

If you suspect an error in DB2, see the information about collecting data.

Problem determination

Check the MVS™ console log for an IOS (I/O subsystem) error message that indicates the type of I/O error that occurred. If an IOS message was issued, follow the problem determination directions for that message.

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.
  • IDCAMS LISTCAT output for the ICF (VSAM) catalog that contains the DB2 subsystem catalog that defined the failing index or table.
  • VTOC listing of the disk volume on which the failing operation occurred.
.