Date: Tue, 2 Sep 2003 12:24:32 -0700
Sender: "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From: Jeff Voeller <c-jeff.voeller@MCI.COM>
Subject: Re: NOERRORABEND option ON OS390 (MVS)
Content-type: text/plain; charset=iso-8859-1
Hmmmm...I don't think I've ever worked anywhere where ERRORABEND was the
Are you sure that SAS continues processing normally if a disk file runs
out of space? I think it enters "syntax check" mode and runs the rest
of the code but with OBS=0 (or something much like that). The job ends
with a return code of 8, so you're definitely given warning that
_something_ went wrong. NOERRORABEND does not in and of itself cause a
return code of 0 in the presence of critical errors, it simply controls
whether the job immediately terminates.
There are definitely situations where I want to override our
NOERRORABEND default (e.g., the job creates a new GDG or other dataset
which I don't wish to catalog in the event of an error), but I've never
found a situation where something meaningful has been overlooked because
> -----Original Message-----
> From: SAS(r) Discussion [mailto:SAS-L@LISTSERV.UGA.EDU]On Behalf Of
> Jerry Prarat
> Sent: Tuesday, September 02, 2003 11:59 AM
> To: SAS-L@LISTSERV.UGA.EDU
> Subject: NOERRORABEND option ON OS390 (MVS)
> I am curious to know if any MVS sites are using the SAS
> default option
> of NOERRORABEND. From what I have found so far, all (or
> almost all)
> MVS sites change this option to ERRORABEND.
> I AM ALSO TRYING TO DETERMINE WHAT KIND OF SERIOUS ERRORS
> MIGHT BE IGNORED
> WHEN NOERRORABEND IS IN EFFECT.
> For example, I know that when I run a batch job that writes to a disk
> output file, and the file runs out of space, SAS will continue
> processing like nothing happened IF NOERRORABEND is specified.
> If you know of other situations on MVS where NOERRORABEND can cause
> critical errors to go unnoticed, please let me know.