Date: Mon, 22 Nov 1999 10:21:18 -0500
Reply-To: WHITLOI1 <WHITLOI1@WESTAT.COM>
Sender: "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From: WHITLOI1 <WHITLOI1@WESTAT.COM>
Subject: Re: I'll take SAS History for 200, Alex.
Content-Type: text/plain; charset=US-ASCII
Bob,
The thread was what statements are step boundaries? I am not sure that ending
the data flow after the step boundary CARDS should qualify, but many have
interpreted it that way.
If so didn't PARMCARDS also end some procedures? Are any still around?
RUN and QUIT are the only statements which cause step boundaries for procedures
without starting a new step or ending the program. I don't know of any
procedure that accepts both, but many of the newer procedures (e.g. SQL and
DATASETS) with an interactive flavor require QUIT, since RUN is used to indicate
execute without ending the step. In the case of SQL you actually get a warning
not to use the RUN statement since SQL statements are
executed when the statement is completed.
Ian Whitlock <whitloi1@westat.com>
____________________Reply Separator____________________
Subject: Re: I'll take SAS History for 200, Alex.
Author: Schechter Robert RS <robert.schecter@PHWILM.ZENECA.COM>
Date: 11/22/1999 9:19 AM
I, too, think we've lost the original objective.
As I remember it, the objective was to define what ended the input stream
following a CARDS statement.
The answer was any SAS line that had a semicolon, not just a step boundary.
Therefore a QUIT; statement qualifies as a CARDS delimiter, I'm not sure
it's a real step boundary. That definition needs revising in light of the
addition of the QUIT statement, IMHO.
Bob Schechter,
PhilaSUG EC Member, Philadelphia area SAS Users Group,
http://members.aol.com/PhilaSUG1
Legacy 2000 Highlander Convention, http://www.LegacyCon.org
Systems Engineer,
Pharmaceutical Information Services,
AstraZeneca Pharmaceuticals
(302) 886-5561 Voice, 886-7525 FAX
FOC-CW3-30
mailto:robert.schechter@phwilm.zeneca.com
> ----------
> From: Peter Crawford[SMTP:peter.crawford@DB.COM]
> Sent: Monday, November 22, 1999 9:04 AM
> To: SAS-L@LISTSERV.UGA.EDU
> Subject: Re: I'll take SAS History for 200, Alex.
>
> As run; doesn't close the step, but terminates a run-group of proc
> gchart and
> gplot etc does that stop it being a step boundary?
> It is in such a complex proc or proc sql that quit becomes a step
> boundary.
> So surely QUITqualifies as a step boundary.
> or are we defining different categories of step boundary ?
> what are the rules
>
> (who started this anyway, what is the objective point,,,,,,)
>
>
>
>
> Datum: 22.11.99 14:57
> An: SAS-L@listserv.uga.edu
>
>
>
>
> Antwort an: rjf2@cdc.gov
>
> Betreff: Re: I'll take SAS History for 200, Alex.
> Nachrichtentext:
>
>
>
> From: William W. Viergever [mailto:wwvierg@IBM.NET]
> Careful now, Ian's on a (Fryeday) roll! (rotflmao)
> At 03:38 PM 11/19/1999 -0500, WHITLOI1 wrote:
> >Ron,
> >
> >QUIT while your ahead.
>
> Monday morning, this thread is still unwinding?!? LOL
>
> What is QUIT anyway?
> At least in my bible: SAS Language Reference, v6 1e, it is not listed as a
> statement.
> Yes, yes, it is in the help, but it seems to be particular to a bushel of
> procedures.
> ending a procedure doesn't mean that we always get a step boundary.
> neither options nor title generate step boundaries,
> so IMHO QUIT is not a step boundary.
>
> Ron Fehd 'just the facts' maven CDC Atlanta GA
>
| 
