DB00801W

Processing, DBUTLTY and SQL Messages › CA Datacom/DB Processing Messages (DB0xxxxc) › DB00801W

DB00801W

I/O ERR - NO RECORD FOUND - aaannnnn xxxxx-yy-zzz type

Reason:

Due to either a JCL error or a hardware problem, no physical block was found in the identified area in the identified database. The following are replaced in the message text:


aaannnnn	One of the following: CXX, the Directory DATACOM-NAME of a data area and the DBID of the database FXX, the Force Area IXX or Inn of an index area, where nnnnn is the database ID LXX, the Log Area
xxxxx	Count-Key-Data Disk Type: physical cylinder	FBA Device Disk Type: logical block number in the area
yy	head
zzz	Count-Key-Data Disk Type: record on which the error occurred	FBA Device Disk Type: number of blocks in the I/O
type	I/O type, where type is either READ or WRITE

Action:

If an error in the JCL is responsible for this message, correct the error and resubmit the job. If the JCL contains no error, recovery procedures depend on aaannnnn as follows:

If aaannnnn is a data area, restore the named area from a backup, attempt to spill the LXX and, whether the spill succeeds or fails, initialize the Log Area with the DBUTLTY function INIT AREA=LXX.
If aaannnnn is CXX, a particular database definition might need to be restored from a CXX backup.
If aaannnnn is FXX, then all work needs to be allowed to end and the MUF set to EOJ. When it is down, the FXX should be set to INIT to rebuild it.
If aaannnnn is IXX or Inn, where Inn is an index, that area might need to be initialized and areas subject to RETIX, if they have a table with a key in this index.