| Date: | Tue, 26 Jan 1999 22:13:28 GMT |
| Reply-To: | jsuebersax@my-dejanews.com |
| Sender: | "SAS(r) Discussion" <SAS-L@UGA.CC.UGA.EDU> |
| From: | Shiling Zhang <shiling@MATH.WAYNE.EDU> |
| Organization: | Deja News - The Leader in Internet Discussion |
| Subject: | Re: Batch SAS under Windows: SYSPARM? |
|---|
John,
As far as I can tell, the sysparm option DOES work with batch SAS under
Windows 95. However, arguments in command line is wrong. Here is an example
of good one.
D:\SAS611\SAS.EXE -config d:\sas611\config.sas -sysparm testing.sas -sysin
d:\temp\testing.sas -icon
the log goes to d:\sas611\testing.log
Hope this helps.
In article <78kmhh$t74$1@nnrp1.dejanews.com>,
jsuebersax@my-dejanews.com wrote:
> I'm running SAS 6.12 in batch mode under Windows 95. Is there a way
> to supply information from the command execution statement? I.e.,
> with, say VMS, you can say:
>
> sas -sysparm=labs prog.sas
>
> and a macro variable, &sysparm, with a value of "labs" is
> supplied to the program. As far as I can tell, the sysparm option
> doesn't work with batch SAS under Windows 95.
>
> Is there another way to supply a macro variable from the
> program execution statement? Thanks in advance.
>
> --
> John Uebersax
> Quintiles (Contractor)
> Lenexa, KS
> jsuebersax@yahoo.com
>
> -----------== Posted via Deja News, The Discussion Network ==----------
> http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own
>
-----------== Posted via Deja News, The Discussion Network ==----------
http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own
|