SAS documents its return codes in platform-specific "companion" documentation. Log errors, warnings, and other messages may produce non-zero exit status codes.

You can determine these empirically by writing test programs to generate error and warning messages, and testing the return code.

You'll have to use some arbitrarily high exit status to find jobs which actually ran into serious problems. The other line of though is to treat *any* non-zero exit status as a bug and fix it -- as you should.

On Wed, Dec 29, 1999 at 04:18:35PM +0000, jamartine@ARMSTRONG.COM wrote: > I'm running SAS batch processes on NT using Maestro. I'm trying to > get > SAS to terminate with a non '0' return code when a critical error > occurs. I also want to be sure to return a 0 if no critical errors > occur so that Maestro does not think the SAS process ended abnormally. > > I've tried using errorabend but get non-0 return codes when there are > warnings generated by SAS. > > Thanks for any help you can give me. > > John Martine > Armstrong World Industries > > > Sent via Deja.com http://www.deja.com/ > Before you buy. > > ------------------------------

-- Karsten M. Self (kmself@ix.netcom.com) What part of "Gestalt" don't you understand?

SAS for Linux: http://www.netcom.com/~kmself/SAS/SAS4Linux.html Mailing list: "subscribe sas-linux" to mailto:majordomo@cranfield.ac.uk