thanks tom for the solution instead of punching down a newbie and mocking in code language. wasn't able to run the code possibly due to the glitch in sas studio. it is now fixed and running smoothly.
... View more
hello
thanks to your advices I managed to optimise very much.
I have a column "send date" in the big table so I added a criteria inside the inner join expression to limite the rows that are > of begining of the month.
many thanks.
Nasser
... View more
BTW, if there is a prior error in your program, your DATA step creating the macro variables won't execute, so your macro variables wont be created. You might want to check that possibility.
... View more
Note that the ARRAY is not needed for this solution since you only need the list of variables once you can just place the list into the function call directly.
select (max(of result1-result5));
... View more
I know this thread only got "reanimated" because of a SPAM message, but this post is a perfect example of why you should (almost) never be using the ancient MISSOVER infile option.
@zekeT_sasaholic wrote:
First.
This process looks strange to me. The reading of input criteria as card statements.
I wont judge as maybe you are using that as a mock up.
but try this...
data layout;
infile cards missover;
input a $1-500 ;
cards;
/** your card stuff **/
;
run;
hth
zeke torres
www.wcsug.com
Using the MISSOVER option will prevent the input statement from moving to the next line when the current line does not have 500 remaining characters.
But it will also discard any line that has less than 500 characters (actually less than 481 since in-line data lines are always padded with spaces to the next multiple of 80 bytes).
Instead use the newer TRUNCOVER option (I think it is only 30 years old).
... View more
@ballardw
I hadn't thought about what a use could be for code like "N=%left(&sam)", but if you are right, or if you are wrong, I think there is probably a better way to handle it.
It is a constant struggle to get people to explain the big picture of what they are trying to do, they only want to talk about the specific coding problem they have, they don't want to get into the big picture. This particular request seems like it is an instance of the XY Problem.
... View more
If the tables are already sorted by Custid, use @Kurt_Bremsers suggestion. Otherwise SQL FULL JOIN is a simple query.
proc sql; create table want as select coalesce(aa.CustId, bb.Custid) as CustId, coalesce(aa.Y, bb.Y) as Y from aa full join bb on aa.CustId = bb.CustId ; quit;
... View more
