Here is how I did it. Might be useful to others. I used proc options option=encoding; run; to find my current encoding. It was indeed WLATIN1. Then I followed the instructions here to change the encoding of my local SAS session to UTF-8. The "problem" disappeared!
... View more
I used proc contents to check the encoding of my target dataset on WRDS. The encoding is utf-8 Unicode (UTF-8). How do I make sure that it is compatible?
... View more
I use SAS PC Connect to extract a large database from the WRDS server using PROC DOWNLOAD. In the process, I kept getting warning messages "an error occurred translating a data set variable's value". This really bothers me, since the downloading takes 20+ hours. Why do we have these messages, and is there a good solution?
... View more
Thanks! Perhaps the way I use these macros is wrong. Here is how I tried to compile them: %include "&dir\Code\nwords.sas";
%include "&dir\Code\winsorize.sas";
%winsorize(inset = have, outset = want, sortvar = region, vars = number, perc1 = 2.5, trim = 0); Now the messages are: ### START. ### Winsorization ### Number of Variables: 1 ### List of Variables: number ### Sorting... ERROR: A character operand was found in the %EVAL function or %IF condition where a numeric operand is required. The condition was: 100-2.5 ERROR: The macro WINSORIZE will stop executing.
... View more
I am trying to winsorize a variable using the winsorization macro provided by WRDS, which can be seen here: https://gist.github.com/mgao6767/736968d5b3a6b9c11df76624c98e5d50 I call the macro with %include "&dir\Code\winsorize.sas";
%winsorize(inset = have, outset = want, sortvar = region, vars = number, perc1 = 2.5, trim = 0); and get error messages: WARNING: Apparent invocation of macro NWORDS not resolved. ### START. ### Winsorization WARNING: Apparent invocation of macro NWORDS not resolved. ### Number of Variables: %nwords(flow) ### List of Variables: flow ### Sorting... ERROR: A character operand was found in the %EVAL function or %IF condition where a numeric operand is required. The condition was: 100-2.5 ERROR: The macro WINSORIZE will stop executing.
... View more
I am using data want;
infile "&in_path\data.csv" delimiter = ',' dsd missover lrecl = 32767 firstobs = 2;
informat variables 15.2;
format variables;
input variables;
run; All other variables are read correctly, except for ones that have thousand separators.
... View more
I opened it in Atom. The values look like the following: "1,972,909.44","1,771,118.01","1,710,921.05","1,604,967.14","1,655,117.54","1,638,147.95"
... View more
This is working now. The data step has 2000 lines though. The only issue I am having is that my numeric values have a comma as the thousand separator, and SAS gets confused.
... View more
This makes sense. The only issue with using the data step to import csv format is that the file has hundreds of columns with the same prefix, each followed by a different date. I am still trying to find a way to avoid typing all these columns in the informat command.
... View more
Indeed some of the variables are char and others are numeric. This is caused by the import process from excel. When all values of a column are missing, the procedure determines the variable to be char instead of numeric.
... View more
Why should we use "and" in the where clause, instead of "or" ? My goal is to find all obs in set1 that does not have any match in set2 in terms of a pair of x and y.
... View more
