Date:         Thu, 5 Jun 2008 08:06:26 -0700
Reply-To:     =?KOI8-R?B?SsVucyBNwXJ0aW4gU2NobMF0dMVy?=
              <KmoEfrUewEbx@SPAMMOTEL.COM>
Sender:       "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From:         =?KOI8-R?B?SsVucyBNwXJ0aW4gU2NobMF0dMVy?=
              <KmoEfrUewEbx@SPAMMOTEL.COM>
Organization: http://groups.google.com
Subject:      Re: raise an error if libname fails?
Comments: To: sas-l@uga.edu
Content-Type: text/plain; charset=ISO-8859-1

On 5 Jun., 14:07, sa...@DATASAVANTCONSULTING.COM (Gregg Snell) wrote:
> Perhaps use the ABORT statement?http://support.sas.com/onlinedoc/913/getDoc/en/lrdict.hlp/a0002302100851856

The abort statement is only valid in a data step.
Of course I could construct a data step to use the abort stmt but this
is not very elegant.

I have found what I need:
OPTIONS ERRORCHECK=STRICT

places the SAS job into syntax-check mode when an error occurs in a
LIBNAME or FILENAME statement, or in a LOCK statement in SAS/SHARE
software. In addition, the job or session abends when a %INCLUDE
statement fails due to a non-existent file.