Just a run-through on why not to use compiler option AWO.
AWO applies to all QSAM VB In the program, including input files.
What this means for the input files (since the WRITE part obviously does not apply) is that the record is moved from the buffer to a record-area which is pointed-to by the FD.
The is no advantage for you in this.
Although this allows for sloppy coding, like using the FD before the file is open, after the file is closed or after end-of-file, as soon as you recompile without AWO, or go to another site which does not use AWO, your sloppy code will fail (in the case of the first two) and may fail in the case of the latter.
With no advantage, you are left with the disadvantage of each input record being moved, and the additional processing time that that takes. MVCL is a "slow" instruction, and that is what will be used.
APPLY WRITE ONLY is good to use on all your QSAM VB output files. Spell it out for each of them and don't use (unless forced to by site standards) compiler option AWO.