> From: Collin Elliot > Sent: Friday, February 19, 2010 6:08 PM > Subject: Issue with filename pipe and SAS shortcut. > > I'm not sure if this is for someone with expertise in filename pipe or > systems architecture, but I'm hoping that among the geniuses on this > listserv there is someone who can help me. > > One of my practices is to create a SAS shortcut in the folders for my > more > significant projects. I change the properties to have these shortcut > point > to an autoexec file that establishes the libnames, etc. One part of the > autoexec includes a filename pipe that gets me a listing of all my code > files that then feeds into a macro that creates file shortcuts for me. > > I have never had issues with this practice until this week when I began > to > work on a new server with Windows Server 2008 R2 Standard. > > I created the shortcut, which worked fine in terms of starting SAS and > running the autoexec file, but when it got to the filename pipe, I get > the > following in the log: > > LOG CONTENTS START: > > NOTE: AUTOEXEC processing completed. > > 1 > 2 filename ral pipe 'dir /S "O:\SCE\CSI_ImpactEval"'; > 3 > 4 data setup; > 5 infile ral truncover; > 6 input contents $150.; > 7 run; > > NOTE: The infile RAL is: > Unnamed Pipe Access Device, > PROCESS=dir /S "O:\SCE\CSI_ImpactEval",RECFM=V, > LRECL=256 > > Stderr output: > There is not enough space on the disk. > NOTE: 0 records were read from the infile RAL. > NOTE: The data set WORK.SETUP has 0 observations and 1 variables. > NOTE: DATA statement used (Total process time): > real time 1.01 seconds > cpu time 0.03 seconds > > LOG CONTENTS END. > > If I try to run this code from the SAS session that the shortcut > launched, I > get the same result, so it does not seem that it's because the code is > in > the autoexec. > > > However, here is the curious (and frustrating) part. When I start SAS > via > the shortcut in the START menu and then run the same code, it does what > is > supposed to do. > > LOG CONTENTS START: > > NOTE: This session is executing on the W32_SRV08 platform. > > NOTE: SAS initialization used: > real time 2.06 seconds > cpu time 0.99 seconds > > 1 > 2 filename ral pipe 'dir /S "O:\SCE\CSI_ImpactEval"'; > 3 > 4 data setup; > 5 infile ral truncover; > 6 input contents $150.; > 7 run; > > NOTE: The infile RAL is: > Unnamed Pipe Access Device, > PROCESS=dir /S "O:\SCE\CSI_ImpactEval",RECFM=V, > LRECL=256 > > NOTE: 16840 records were read from the infile RAL. > The minimum record length was 0. > The maximum record length was 209. > NOTE: The data set WORK.SETUP has 16840 observations and 1 variables. > NOTE: DATA statement used (Total process time): > real time 6:18.16 > cpu time 0.21 seconds > > LOG CONTENTS END. > > I cannot even begin to understand why launching SAS from a different > shortcut would have an effect on how the code would run, but if anyone > here > has any insights or, even better, solutions, I will be very > appreciative. > And yes, I know I could just use the default icon and then run my code > manually, but I find it very convenient and efficient to do so via an > autoexec,particularly when I've never had issues with this before. > > Thank you very much in advance.

tricky!

examine your HostName to see which computer -- and which disk is running out of space -- is actually accepting the submission of your job.

%Put note2: HostName= %sysget(computername);

if your Windows does not have this environment variable then check all your system macro variables:

%Put _automatic_;

Ron Fehd the macro maven CDC Atlanta GA USA RJF2 at cdc dot gov