SAS should be passing the return code straight back to the script, and you can test in same way as the return code from any other command.

e.g. see <http://tldp.org/LDP/abs/html/exit-status.html> and <http://tldp.org/LDP/abs/html/filearchiv.html#FILECOMP> ('# Test exit status of "cmp" command.')

Cheers

On 2010-06-10, at 05:29, Scott Bennett wrote:

> When running SAS from UNIX command line, I need to capture the exact value > SAS has returned or abended with. > > If in SAS we have the following: > > DATA _NULL_; > ABORT ABEND 2000; > RUN; > > I need the UNIX script that started the SAS session to know SAS abended > with the 2000 code. > > Also if SAS had the following: > > DATA _NULL_; > ABORT RETURN 1; > RUN; > > I need to know the SAS returned a 1 because of the code, and not because of > a SAS warning. > > The reason for this is I need to have SAS previously running on MVS produce > the same results on UNIX. On MVS a SAS warning would result in a job step > RC of 4, so a value of 1 from the developer is meaningful. > > Thanks!!