LISTSERV at the University of Georgia
Menubar Imagemap
Home Browse Manage Request Manuals Register
Previous (more recent) messageNext (less recent) messagePrevious (more recent) in topicNext (less recent) in topicPrevious (more recent) by same authorNext (less recent) by same authorPrevious page (September 1996, week 3)Back to main SAS-L pageJoin or leave SAS-L (or change settings)ReplyPost a new messageSearchProportional fontNon-proportional font
Date:         Fri, 20 Sep 1996 09:32:54 -0700
Reply-To:     Bruce Rogers <gxx18300@GGR.CO.UK>
Sender:       "SAS(r) Discussion" <SAS-L@UGA.CC.UGA.EDU>
From:         Bruce Rogers <gxx18300@GGR.CO.UK>
Organization: Glaxo Wellcome
Subject:      Re: adding lable
Comments: To: TWB2%Rates%FAR@GO50.COMP.PGE.COM

TWB2%Rates%FAR@GO50.COMP.PGE.COM wrote: > > If the data is on tape, you will have to pass the file once anyway, so you can > add the labels with LABEL or ATTRIB statements. If the data is on disk and you > use 6.06-6.08, you can use: > PROC DATASETS LIBRARY=yourdisk; > MODIFY dataset; > LABEL somevar='some label' > nother='something else'; > RUN; > QUIT; > > Note, the RUN statement has little effect. For some reason some of the new > PROC's use QUIT to mean RUN and RUN to mean something completely new and > different. Many people would have chosen to use RUN to mean RUN and chosen some > completely different symbol, like QUIT, to mean something completely different, > but changing the meaning of RUN from PROC to PROC makes SAS more exciting. >


I'm surprised at your comments on the RUN and QUIT statements. In several procs, including datasets, the use of a RUN statement will cause the current command (in this case the Modify) to execute. This can then be followed by another command without re-entering the PROC statement. So the use of the 'new' QUIT statement simply tells SAS to end the procedure.

If anything, the use of RUN to terminate a step is something of an oddity, although, of course, those of us who've been using SAS for years have grown accustomed to it. The current usage is more consistent, not less, as we use RUN to do just that - cause something to run, and QUIT to terminate a step where this is not implicit in the act of running it (as it is in a data step etc.) .

In some cases, of course, statements are automatically executed (is this just in SQL? ), so it is the RUN statement which is redundant therein, and _only_ the QUIT statement has any effect.


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