ARC0800 An open error occurred on file %s- %s

Archive/Recovery (ARC Prefix) Messages

prodname
Teradata Tools and Utilities
vrm_release
15.10
category
Programming Reference
featnum
B035-1096-151K

ARC0800 An open error occurred on file %s- %s

Explanation:

An attempt to open the specified file was not successful.

For Whom:

User

Notes:

Reason codes for ARC08XX series messages. 1 I/O request type invalid2 DDname unknown3 Open request - dataset already open I/O request - dataset not yet open4 Read request - not open for input Write request- not open for output or archive dataset not positioned properly for write5 Rewrite request invalid for archive dataset8 Device not magnetic tape nor DASD10 DCB open unsuccessful12 Buffer length invalid13 Segment error16 Block length error on read21 Argument length error22 Offset value error30 Disposition request not for either dataset DDname31 Read JFCB not successfully completed32 Dataset disp = new33 Dataset disp = mod34 Dataset disp = shr35 Dataset disp = old200 Invalid archive labeldef for relative positioning. TRWFAH1170 I/O request type invalid1171 DDname unknown1172 Open request - dataset already open I/O request - dataset not yet open1173 Read request - not open for input Write request- not open for output or archive dataset not positioned properly for write1174 Rewrite request invalid for archive dataset1179 Device not magnetic tape nor DASD or not DASD device1181 DCB open unsuccessful1183 Buffer length invalid1184 Archive datasets open - disp request DDname not for either dataset DDname1185 Read JFCB not successfully completed1186 Dataset disp = new1187 Dataset disp = mod1188 Dataset disp = shr1189 Dataset disp = old1190 Segment error1191 Argument length error1192 Offset value error1193 Request not yet supported1194 Block length error on read1195 HUTIO internal force write occurred1198 I/O err on archive dataset1199 Disp incompatible with options

Remedy:

If the file was an archive, check the statement on which the error occurred to insure the name of the file on the statement is the same as the system control language. If the file is the DBCLog, then check to make sure the DBCLog is properly defined for access.