LISTSERV at the University of Georgia
Menubar Imagemap
Home Browse Manage Request Manuals Register
Previous messageNext messagePrevious in topicNext in topicPrevious by same authorNext by same authorPrevious page (March 2004, week 2)Back to main SAS-L pageJoin or leave SAS-L (or change settings)ReplyPost a new messageSearchProportional fontNon-proportional font
Date:         Mon, 15 Mar 2004 04:25:48 GMT
Reply-To:     Stuart Luppescu <s-luppescu@UCHICAGO.EDU>
Sender:       "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From:         Stuart Luppescu <s-luppescu@UCHICAGO.EDU>
Organization: SBC http://yahoo.sbc.com
Subject:      Re: I don't get %sysexec
Content-Type: text/plain; charset=ISO-8859-1

On Sun, 14 Mar 2004 22:44:18 -0500, Richard A. DeVenezia wrote:

> Stuart Luppescu wrote: >> I'm having terrible trouble getting %sysexec to work. >> I have these lines of code (SAS 8.2 on SunOS 5.9): >> %if &passed=no %then %do; >> %put =-=-=-= School &&schl Failed Inclusion Criterion =-=-=-=-= ; >> %sysexec /usr/bin/cp -f &pspath/&themeas.csys.ps.gz >> &pspath/&&schl/&themeas.c&&schl..ps.gz; run; >> %put =-=-=-= File copied &pspath/&themeas.csys.ps.gz to >> &pspath/&&schl/&themeas.c&&schl..ps.gz; %end; >> >> The log shows this (slightly edited for brevity): >> > snip >> anyone >> have any idea what's happening? >> >> Thanks. > > I dont like the &&schl. > && is typically used in context such as &&foo&i > &&& is for multiple indirect (value of macro var named in macro var)

I think I used &&schl because schl is a macro parameter in a surrounding macro. I don't know if it's necessary or not, but it doesn't hurt.

> For debugging purposes, perhaps preevaluate the source and destination > %let source =... > %let dest =... > %sysexec cp ... &src &dest

Good suggestion, but it doesn't change anything. The src and dest paths are fine. -- s-luppescu .at. uchicago.edu


Back to: Top of message | Previous page | Main SAS-L page