Open a track with SAS technical support. But since the return of FOPTNUM, FOPTNAME and FINFO is OS-dependent, this might be a fault in Windows itself.
... View more
Run PROC CONTENTS on both datasets, then take appropriate action so that the append dataset's variable attributes matches those of the base dataset.
... View more
@sassy_seb wrote:
Both datsets do have the variable I am merging by in common. The only discrepancy seems to be the length in one of the datasets but I am not sure if it has something to do with the SAS code or the csv where I am pulling the data from.
Read the log. You merge by PID only, but the complaint is about PID_INI and VIT_DTH_SP. One usually does not want a situation where there are variables not included in the BY in both datasets. It is quite hard to predict which values will end up in the result if there's not a strict 1:1 relationship.
It would help a lot if you post examples for the datasets and the expected result.
... View more
The syntax checker in Studio is not 100% complete, it will miss some elements. The real check happens when you run your code; look at the log.
... View more
First, I would define a file reference with FILENAME URL. Then I would use that reference in a DATA step in the INFILE statement with the GZIP option. This should perform the download and uncompress in one action.
... View more
@Ronein wrote:
I found the solution!~
options dlcreatedir;
libname PanelOsh "/usr/local/SAS/SASUsers/LabRet/Credit_Scoring_Users/";
Is it necessary to write options dlcreatedir?? Why?>
Maxim 1: Read the Documentation.
On Windows and UNIX, the default is NODLCREATEDIR.
... View more
With system option DLCREATEDIR set, the directory will be created when the LIBNAME statement is issued. You must, of course, have the necessary permissions in the filesystem.
... View more
These numbers are the raw values of Excel datetimes. Add '30dec1899'd (a SAS date literal) to them, then multiply by 86400 to get a raw SAS datetime value.
Or save the data to a text (csv) file and read that with a DATA step; create a suitable informat to deal with special values (those which caused PROC IMPORT to go wrong).
... View more
It means that you have different values in at least one of your ID variables (consider that statement to be like a BY).
If there are numeric values that look identical, you may have small differences far down in the fractional part, caused by the usual numeric imprecision.
CRITERION does not influence the working of ID.
... View more
