@astha8882000 Read through what @Tom wrote. He's covering pretty much the possible root causes of why that's not working for you.   For testing: Instead of redirecting the log why don't you just first try with a simple filename statement writing "something" to the desired location. If that works then redirecting the log to such a location should work as well. ... View more

I don't find any issue with the code, it works fine with my sample data. Make sure that the data types you defined are same in the source tables.   prodcd - Is this a character variable, if its numeric then you might need to give proccd=. (period) for numeric missing value. data table1; set sashelp.class(keep=name height); run; data table2; set sashelp.class(keep=name weight); opendt='01JAN2018'd; prodcd = ' '; run; proc sql; create table abc as select a.name, a.height, b.opendt, case when today()-b.opendt>200 then b.opendt end as date_opened from table1 a left join table2 b on a.name=b.name where (a.height>50 and b.prodcd = ' '); quit;   ... View more

I made the changes like you suggested, and I think it works. I'm going to try on another code which is a huge list of proc sqls and data _null statements and see if it works for that too. Thank you so much for your help!! ... View more

That's expected behavior.  It's how a many-to-many merge is supposed to work. You must be seeing an additional note in the log about more than one data set having multiple observations for the BY variable.    If you want to eliminate "Vendor1" as a possible match, you have to get rid of it on purpose:   merge vendor (in=a) clue (in=b where=(Name_Vendor='Vendor')); by mail_name; drop name_vendor;   If your macro contains a macro variable that indicates the value of Name_Vendor you are working with, use double quotes when referring to it:   merge vendor (in=a) clue (in=b where=(Name_Vendor="&vendor")); by mail_name; drop name_vendor;       ... View more

Is the DMR option set? The macro could be failing because the macro parser checks that option before attempting the %SYSRPUT statement.   You would also have to have an active connection to a remote host if I read the documentation correctly. Is one active? ... View more

thank you! Quick question though, what are these folders called? when i open it up it just has logs. how do I run this folder code/ contents? ... View more

select * into : test //does a refer to the global macro variable created above?    Yep. It's a global macro variable on the remote host. The %global statement makes it available outside the macro.   what is the purpose of this statement?   A proc SQL request to store the calculated value of MAX(height) from profile_table in the macro variable TEST.    %sysrput test = &test //value of remote test (which is in the select statement) gets transferred into global macro variable test defined at the very top??   Nope. it's a request to copy the value of the macro variable TEST on the remote host into macro variable TEST on your local host, so that you could use it in the local session after the SAS/Connect session is over.    Also, why is it written test. in some places and test in other places(with and without the period)?   A period after a macro variable reference tells SAS to dereference only the part between the ampersand and the period. After the variable is resolved, the period is ignored.Thus, if the value of macro variable TEST is 100, the reference &TEST._SMTH will result in 100_SMTH. Without the period, i.e. &TEST_SMTH, SAS would think that this is a reference to a macro variable whose name is TEST_SMTH. If it exists, you may get a wrong result; if it doesn't, SAS will tell you that it cannot be resolved.   Note that only the first period immediately following the macro variable name is treated in this manner; any subsequent period is just text. Thus, if a macro variable LIB contains value SASHELP and a macro variable DSN contains value CLASS and you wanted to get SASHELP.CLASS, you'd code &LIB..&CLASS since the first period after &LIB would be ignored after &LIB is resolved but the second will stay.   Some people have the habit of coding a period after a macro variable reference no matter whether's is needed (as in the example above) or not (as in your code sample) as some sort of "safety measure". Personally, I agree with Ian Whitlock that coding something that serves no purpose is wrong practice and code a period after a macro variable name only if what follows it can be interpreted as that name's continuation.   Paul D.                         ... View more

You are right, the statement below is giving the error as you mentioned: 1. Instead of abc="mv -f /original path" || strip (_infile_) || "/new path"; it should be abc=mv -f "/original path" || strip (_infile_) || "/new path"; The statement: abc=mv -f "/original path" || strip (_infile_) || "/new path"; would have a syntax error as it would first attempt to subtract the value of a numeric variable f from a numeric variable mv (not a problem unless you actually have those variables) but without an operation the "/original path" will generate an error like: ERROR 22-322: Syntax error, expecting one of the following: !, !!, &, (, *, **, +, -, /, <, <=, <>, =, >, ><, >=, AND, EQ, GE, GT, LE, LT, MAX, MIN, NE, NG, NL, OR, [, ^=, {, |, ||, ~=. What should be the correct syntax for this line of code? ... View more

You wrote- "I really am not sure what made it work, will continue my R&D on that later".    I like that.    This is just a heads up to give you an idea what's purpose of hash object to begin with. The hash object stores data as key::value pairs in a so called virtual table or you can call it look up table. Basically, we try to match the key with a key in another table and fetch the associated data with key, very similar to a join so to speak. With this understanding your further reading will be more comprehensible.  ... View more

Your original data step is using a subsetting IF statement. So it is only keeping the observations where the phone number is found. So this part of the WHERE clause implements that condition.   AND phoneno in (select phoneno from ds1) ... View more

You wrote- "I really am not sure what made it work, will continue my R&D on that later".    I like that.    This is just a heads up to give you an idea what's purpose of hash object to begin with. The hash object stores data as key::value pairs in a so called virtual table or you can call it look up table. Basically, we try to match the key with a key in another table and fetch the associated data with key, very similar to a join so to speak. With this understanding your further reading will be more comprehensible.  ... View more

I actually ended up working around it by getting that exact server location rather than getting into all this and reading the data in there. Still not sure how to get sysrput to work, but maybe another time. Thanks everyone for your help! ... View more

I tried doing that too, that didn't help either: %let abc_unix = &sd_exports. rsubmit; %sysrput abc_unix = &abc_unix.; endrsubmit; LIBNAME abc "&abc_unix."; I get the following error: ERROR: The text expression &abc_UNIX. contains a recursive reference to the macro variable abc_UNIX. The macro variable will be assigned the null value. ... View more

I tried doing this: %let abc_unix = &sd_exports.; %nrstr(%sysrput abc_unix = &abc_unix.); LIBNAME abc "&abc_unix."; that gave me the error: Statement is not valid or it is used out of proper order. ... View more