IF(!) you run this on a UNIX system (e.g. SAS On Demand), then the correct shortcut for your home directory is the tilde (~), not the ampersand (&).
... View more
Post the complete log of your code by copy/pasting it into a code box, from the ODS POWERPOINT statement to the ODS POWERPOINT CLOSE statement. Do not change or omit anything.
... View more
SAS Studio uses ODS to fetch output for display in your browser. By issuing your own ODS statements, you might interfere with this. That's what this NOTE tells you.
... View more
@ivarenho wrote:
I tried the code as you wrote it and It worked well except for the error regarding the CSV file:
ERROR: Physical file does not exist, S:\ \workshop\EPG1V2\data\storm_final.csv.
When you get an ERROR like this while trying to create a file, you either specified a directory path that does not exist, or where you do not have write permission.
... View more
If all your combinations of
studyid site subjid
are unique, then
first.subjid
will always be true, and the whole condition always false. Your empty result dataset proves that all combinations are unique and you have no duplicates.
Multiple entries for a given subjid are obviously contained in different studies/sites.
... View more
When reading text files, don‘t waste your time with PROC IMPORT. Write the DATA step yourself, according to the documentation of the file. You‘ll get much cleaner and easier to maintain code, and have the full flexibility if DATA step coding at your hand. The accepted solution will make it impossible to correctly read numeric values, including dates and times.
... View more
The usual mistake that causes the "physical file does not exist" message comes from trying to read a local (residing on your PC) file in the remote (running on a server) SAS session. You must upload the file to the On Demand server first (Studio can do this) and then use the path on the server in your code. You can get the complete path through the properties of the file by right-clicking on it in the file navigation tab of SAS Studio.
... View more
You can log on to the server‘s commandline and use the ps command (or the Windows equivalent) to display the process status; by filtering for your username you can find your SAS session. As admin, I provided a web page which ran such a command and displayed the top 10 processes in terms of CPU consumption, so it was easier for the SAS users to see if they had accidentally created a runaway process.
... View more
