Date:         Wed, 17 Jul 1996 22:29:29 +1000
Reply-To:     "David H. Johnson" <djohnson@WERPLE.NET.AU>
Sender:       "SAS(r) Discussion" <SAS-L@UGA.CC.UGA.EDU>
From:         "David H. Johnson" <djohnson@WERPLE.NET.AU>
Subject:      Re: omiting "proc" from a procedure
Comments: To: Julian S Visch <math5jsv@MATH.CANTERBURY.AC.NZ>

Caution here, this mail machine doesn't run SAS, so I may place one toe
after another in my mouth, but if so, so be it.
 
GOPTIONS is a System option and decodes as such, as well as a proc under
SAS/GRAPH.
 
SAS/GRAPH like PROC CATALOGS and a number of others have runtime code. So
issuing parts of the Graph code, immediately after issuing the first full
invocation of SAS Graph will work until you issue QUIT. See the following;
 
PROC CATALOG;
     CONTENTS DATA=FRED.STUFF NOPRINT OUT=MORSTUF;
RUN;
 
     CONTENTS DATA=WORK.MORSTUF;
RUN;
QUIT;
 
Only the final QUIT shuts down CATALOG. If I were to issue the CONTENTS
statement after a DATA or PROC step (other than CATALOG), it wouldn't work!
Graph is the same. And that is different to your describing a situation
where CATALOG, or GRAPH anytime in the session keeps the Procedure current
and allows issuing partial code ANYTIME thereafter. I don't think so.
 
Regards
>I have come to notice that sometimes one does not need to include "proc"
>at the beginning of a procedure e.g goptions.
>In other cases like the print procedure, it will not work.
>But in cases like gchart, as long as I have already included
>proc gchart at sometime on my current SAS window, it won't require
>"proc" there after. Has anyone made a list of when you can or can't
>leave out proc?
>
>thanks
>Julian
>
>
/*---------------------------------------------------------------------------
  David Johnson   Strategy & Research   TAC  +61 3 9664 6492
     Senior Research Analyst ... not company spokesman!!!
---------------------------------------------------------------------------*/