Since it is not part of the base SAS installation, ask your admin where he/she put it. ... View more

Use the COUNTW function with a ',' delimiter to determine the number of occurences in a line. Then run a do loop for 1 to (result of COUNTW), use the SCAN function with delimiter ',' to get the nth value group, split that with another use of the SCAN function with default delimiter ' ', and output. KEEP only the wanted variables. ... View more

This looks like an appliaction for a dow loop: data want (keep=id1 st1 enddate rename=(id1=id st1=startdate)); format id1 st1 enddate; /* just to keep the vars in order */ do until ((startdate - lastdate >= 28) or finish);   lastdate = startdate;   set have end=finish;   by id;   if first.id then lastdate = startdate; end; if startdate - lastdate >= 28 then do;   do until (lastdate = st1 and id = id1); /* read to the first record */     set have (rename=(id=id1 startdate=st1));   end;   output;   do until (startdate = st1 and id = id1); /* read to the second record */     set have (rename=(id=id1 startdate=st1));   end;   output; end; run; ... View more

PS do not despair. I was in your shoes some 10 years ago. I have the luxury of running SAS on a _real_ server OS (AIX), though .... ... View more

In this case, you can either make sure that the windows server has access to the excel file via AD, or use the ftp transfer as in the example I gave you. But to use ftp you first have to modify the default behaviour of the SAS workspace server that does all the work for your Enterprise Guide. By default, no shell escapes are allowed in workspace server sessions right out of the box. I hope this works for you (did that quite some time ago, SAS 9.2): Start Management Console and log in as sasadm when connecting to the metadata server. Search for your workspace server definition: Plug-Ins - Server Manager - SASApp (the name you see as server in EG) - Logical Workspace Server - Workspace Server Right Click on Workspace Server, select Properties and then Options, you will see the script that is used to start the server instance. Click on Advanced Options (or whatever it is called, it is "Erweiterte Optionen" in German). In Startup Properties you need to activate "allow XCMD") To put this into effect, you then have to restart the Object Spawner on this machine, you can do this via the MC ... View more

If you want to just check the behaviour of the data step with a few records, look at the (obs=...) data set option. ... View more

I just suspect that reading a file byte-wise may be slow as drying paint ... View more

begin with: data _null_; file 'C:\temp\ftp.script'; put "open ftp.mycompany.com"; put "username"; /* supply the username in plain text here */ put "password"; /* supply the password in plain text here */ put "cd /somepath/path"; put "lcd where-you-want-the-file-to-end-up"; /* (eg c:\temp) */ put "bin"; put "get test.xlsx"; put "quit"; run; x "ftp -s c:\temp\ftp.script"; x "del c:\temp\ftp.script"; the script file is necessary because it's (next to) impossible (AFAIK) to pipe the commands into the windows ftp.exe now you can run the proc import on c:\temp\test.xlsx edit: had to change how user and password are supplied, added "bin" ... View more

On which platform are you using SAS? Windows ftp does have its quirks compared to "standard" ftp on a UNIX platform. ... View more

Your workspace server runs on UNIX, so you have to make the include visible to it. - UNIX knows NO backslash in Filepaths, instead it uses the forward slash. (actually it's the other way round, some bespectacled lawschool dropout decided to use the \ when he imported the idea of a hierarchical filesystem from UNIX into a new version of CP/M 86, which he later named DOS) - if your UNIX server can see the PC network (Novell or AD), ask the admin what the name of the network mount is - if your server cannot see the network drives, copy the files via ftp/sftp to your home directory there, or a publicly accessible location if other users should also be able to use the include - start your filename with a / (or something like $HOME), so that it is interpreted as an absolute path. Without a leading slash, the working path of the workspace server is always prepended (the /some/unix/path/ that you saw). ... View more