DSNU086I csect-name ttttt I/O ERRORS ON SPACE= dddddddd. DATA SET NUMBER= nnn. I/O ERROR PAGE RANGE= aaaaaa, bbbbbb.
Explanation
- I/O errors were detected on the named object. ttttt is either 'READ' or 'WRITE'. nnn; is the data set number. aaaaaa is the first damaged page and bbbbbb is the last damaged page of the data set.
- A broken page was detected.
- A page parity error was detected for a 'must complete' agent.
- A read or write I/O error was detected. A LPL recovery might be in progress so the page is added to the WEPR instead of the LPL.
System action
Processing continues, but the pages within the error range are no longer accessible.
This message is non-scrollable. It remains highlighted on the console until you take the appropriate action.
System programmer response
Determine the appropriate level of recovery, and invoke the recovery utility. If user-defined data sets are being used and full data set or table space RECOVER is to be used, then, prior to invoking the RECOVER utility, the table space must be stopped, new data set(s) defined, and the table space restarted. If the data set is part of a ROSHARE READ database, determine whether it was a link or DASD failure. It there was a link failure, then fix the link, and issue a -START DATABASE with the ACCESS(FORCE) parameter. If the error was caused by a DASD failure, then correct the problem from the system on which the database was defined as ROSHARE OWNER.
Problem determination
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. for a discussion of database recovery procedures.
An IOS (I/O subsystem) message might be included on the MVS console SYSLOG indicating the type of I/O error that occurred. If an IOS message was issued, follow the Problem Determination directions for the message.
Severity
0 (informational)