LISTSERV at the University of Georgia
Menubar Imagemap
Home Browse Manage Request Manuals Register
Previous messageNext messagePrevious in topicNext in topicPrevious by same authorNext by same authorPrevious page (January 2012, week 4)Back to main SAS-L pageJoin or leave SAS-L (or change settings)ReplyPost a new messageSearchProportional fontNon-proportional font
Date:   Wed, 25 Jan 2012 12:15:47 -0600
Reply-To:   "Data _null_;" <iebupdte@GMAIL.COM>
Sender:   "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From:   "Data _null_;" <iebupdte@GMAIL.COM>
Subject:   Re: non-SAS-killing ABORT for interactive mode, is there one?
Comments:   To: Bolotin Yevgeniy <YBolotin@schools.nyc.gov>
In-Reply-To:   <01384B2401936142AF5F65E3D12402780BDDA67A@EX3VS1.nyced.org>
Content-Type:   text/plain; charset=ISO-8859-1

You could put SAS into syntax check, obs=0 mode based on some condition. You will need to check the exact options that need to be set.

On 1/25/12, Bolotin Yevgeniy <YBolotin@schools.nyc.gov> wrote: > This has probably been asked before but I can't seem to find what I > want... > > Is there a simple command I can write in code to force SAS to abort the > currently submitted code (i.e. equivalent to Cancel Submitted Statements > from the Break menu), that DOESN'T actually shut down SAS in the process > like ABORT does? > Even if the abort cannot be made conditional, this can work wonders for > debugging (i.e. insert as a breakpoint) > > > I've seem some interesting approaches to doing this with macros > injecting comment delimiters (i.e. /* ) but this is both way too > complicated for what I'm doing and requires way too much work to > implement on existing projects > > > > Using SAS 9.2 on WinXP (32 bit) >


Back to: Top of message | Previous page | Main SAS-L page