Date:         Wed, 16 Dec 2009 18:29:41 -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: Bug? Inadvertent execution of x command
Comments: To: Arthur Tabachneck <art297@netscape.net>
In-Reply-To:  <200912162359.nBGIQOCa007175@malibu.cc.uga.edu>
Content-Type: text/plain; charset=ISO-8859-1

Expected, response.  X is similar to FILENAME, TITLE or other GLOBAL
statement.  If "associated" with a PROC or DATA step it is executed
before the PROC or DATA step executes.

On 12/16/09, Arthur Tabachneck <art297@netscape.net> wrote:
> In testing a response to a post a few minutes ago, I inadvertently left off
> a tables statement in proc freq statement (while I use 'do over' in the
> following code, it is NOT the issue):
>
> data have;
>  input x y z;
>  cards;
> 1 -5 2
> -3 4 2
> -5 -3 7
> 1 2 3
> 2 . 4
> ;
>
> proc format;
>  invalue missed
>  -3 = .M
>  -5 = .S
> ;
> run;
>
> data want;
>  set have;
>  array numbers _numeric_;
>  do over numbers;
>    numbers=input(numbers, missed.);
>  end;
> run;
>
> proc freq data=want;
>  x y z;
> run;
>
> What was fascinating was that the code ran but, in the process, also
> executed the system command ('x') in my Window's server environment.
>
> Is that a bug or a feature?
>
> Art
>