Reason:
If LXX replaces aaannnnn in the message text, CA Datacom/DB attempted to open the Log Area when opening User Requirements Tables, but found that the Log Area was not prepared for use. CA Datacom/DB may have encountered an uninitialized Log Area. See the INIT LXX in the CA Datacom/DB DBUTLTY Reference Guide.
If the I/O error occurred when accessing a record residing in a data area of a database, it is probably due to a JCL error or a hardware problem.
The following are replaced in the message text:
|
aaannnnn |
One of the following:
|
||
|
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:
Verify that the JCL points to the correct areas and revise if an error is found. If the JCL contains no errors, reinitialize the area by executing the DBUTLTY INIT function, then reload the area with the DBUTLTY LOAD function.
|
Copyright © 2014 CA.
All rights reserved.
|
|