Date:         Mon, 29 Nov 2004 14:04:57 -0800
Reply-To:     Jeff Voeller <Jeff.Voeller@MCI.COM>
Sender:       "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From:         Jeff Voeller <Jeff.Voeller@MCI.COM>
Subject:      Re: Smallest SAS program?
In-Reply-To:  <30vlgkF34gfpbU1@uni-berlin.de>
Content-type: text/plain; charset=us-ascii

You *can* get away with a zero-byte SAS program in z/OS:

//SYSIN    DD *
followed by nothing at all results in:

NOTE: The initialization phase used 0.11 CPU seconds and 7278K.
NOTE: The SAS session used 0.11 CPU seconds and 7278K.
NOTE: SAS Institute Inc., SAS Campus Drive, Cary, NC USA 27513-2414

-----Original Message-----
From: SAS(r) Discussion [mailto:SAS-L@LISTSERV.UGA.EDU] On Behalf Of Richard
A. DeVenezia
Sent: Sunday, November 28, 2004 8:05 PM
To: SAS-L@LISTSERV.UGA.EDU
Subject: Re: Smallest SAS program?


Bruce Erlichman wrote:
> dat;
> ru;


Here are some short SAS programs - each is one line and ends sas

dm'bye;
dm'by;
dm'by
dm'bye
endsas;
endsa;

Do any of these one liners count ?
;
*;
%*;
%put;
run;
ru;           (generates a warning)

This might be the shortest program that creates an external file
---
dat;
fil'x';
ru;
---

An interesting non-program that locks up sas is
...\sas.exe -initcmd 'bye'

If it didn't lockup, one might claim the shortest sas program is zero bytes
long.

In batch mode, the shortest is zero.  Presume zero.sas is a file with no
content.
...\sas.exe -sysin zero.sas

--
Richard A. DeVenezia
http://www.devenezia.com/