Thanks Jeff.    I was wrong when I said that SAS would continue running.
It does set  OBS=0  and do syntax checking.
I guess that my main contention is that the output file is not deleted,
and if some lazy programmer does not see RC=0008   or does not check their
SASLOG,  they could assume that everything is OK.   They may read the
incomplete file in another job or step  and never know that it is
incomplete.
I have been advised by SAS tech support that their documentation only
mentions this issue in a 'Tip'   for ERRORABEND.   The tip says that
production batch jobs should always use  OPTIONS=ERRORABEND;
When I asked the support person for her personal opinion,  she said she
would  'Strongly'  recommend using ERRORABEND  at every MVS site for all
batch.

So,  from your comments,  you seem to have no problem with NOERRORABEND
for MVS batch.   I would guess that your production standards always
recommend (or require)  condition code checking.   This makes sense.

I am still curious to find out what other abend-level scenarios  are
effected by using   NOERRORABEND.