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 (July 2006, week 1)Back to main SAS-L pageJoin or leave SAS-L (or change settings)ReplyPost a new messageSearchProportional fontNon-proportional font
Date:         Mon, 3 Jul 2006 09:14:53 -0400
Reply-To:     "Howard Schreier <hs AT dc-sug DOT org>" <nospam@HOWLES.COM>
Sender:       "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From:         "Howard Schreier <hs AT dc-sug DOT org>" <nospam@HOWLES.COM>
Subject:      Re: run; quits; and other questions

On Sun, 2 Jul 2006 21:10:49 -0700, Sierra Information Services <sfbay0001@AOL.COM> wrote:

>My understanding is that the words RUN and QUIT are explicit step >boundaries between data and procedure steps in the SAS Sysetm, while >the words DATA and PROC are implied step boundaries.

Except that some PROCs (eg, PROC DATASETS) use RUN at a lower level, to terminate statement groups *within* the step. Thus only QUIT can explicitly end a PROC DATASETS step.

> >Hope this helps. > >Andrew Karp >Sierra Infrmation Services >www.SierraInformation.com > > >Alan Churchill wrote: >> Toby, >> >> That answers my question exactly. I need to identify code segments and how >> to parse them properly and using the step boundaries is that answer. >> >> Thanks, >> Alan >> >> Alan Churchill >> Savian "Bridging SAS and Microsoft Technologies" >> www.savian.net >> >> -----Original Message----- >> From: SAS(r) Discussion [mailto:SAS-L@LISTSERV.UGA.EDU] On Behalf Of toby >> dunn >> Sent: Sunday, July 02, 2006 2:56 PM >> To: SAS-L@LISTSERV.UGA.EDU >> Subject: Re: run; quits; and other questions >> >> Alan , >> >> As far as I know you cant run a Data Step or Proc without a step boundary. >> I tried running your code in interactive mode and it didnt not produce >> anything. I have had no problem in tha past running Dat aStep or procs >> without a step boundary so long as I am running in batch mode. In these >> cases SAS knows that there cannot be any more code to compile and run and >> will execute the code. >> >> >> >> Toby Dunn >> >> >> >> >> >> From: Alan Churchill <SASL001@SAVIAN.NET> >> Reply-To: Alan Churchill <SASL001@SAVIAN.NET> >> To: SAS-L@LISTSERV.UGA.EDU >> Subject: run; quits; and other questions >> Date: Sun, 2 Jul 2006 12:56:03 -0600 >> >> I have a question for the listserv that is obscure but important. >> >> >> >> I know I can do this horrible, horrible construct: >> >> >> >> data test ; >> >> set sashelp.class; >> >> >> >> .and it will run without a run; statement. >> >> >> >> However, I can't seem to run a proc without a run statement. A macro >> ,likewise, isn't recognized unless the prior data step is closed off with a >> run statement. >> >> >> >> My question is what constructs are out there such as the data step without a >> run statement where SAS implicitly adds in a statement? I am only asking >> about the major constructs such as procs and data step. So far, from my >> testing, it appears that only a data step can take an implied run; whereas >> other statements require closure. Is this a valid assumption? Does this also >> apply to macros requiring a %mend in all cases? >> >> >> >> Alan >> >> >> >> Alan Churchill >> >> Savian "Bridging SAS and Microsoft Technologies" >> >> www.savian.net


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