OPEN with no FILE STATUS for the file, and no DECLARATIVES for the file, will get a U4038 if it fails, a Language Environment abend.
Yes, having defined a FILE STATUS it should *always* be checked. The consequences of not checking far outweigh any "saving". FILE STATUS cannot prevent/identify the "file full" stuff. Without system software to "deal" with an X37, that's just the X37 abend. You can code an LE Abend Handler to identify the X37s (and lots of other things). On Tuesday, 12 July 2016 15:51:17 UTC+2, Clark Morris wrote: > That depends on whether a status code field is defined for the file. > If no status code is defined for a file, a failed OPEN will cause an > abend of some type. Note that if a status code is defined for a file, > it must be checked after ALL I-O statements for the file. Otherwise > interesting problems could occur such as ignoring B37 and D37 type > failures on output. One client's programs actually only checked the > OPEN statements. Without the status code I-O failures such as READ > past end of file and B37/D37 conditions will cause abends. > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
