To note, as per previous posts I have made here, your code is very sloppy, and hence you are getting problems: data cork; input tree$1-3 north east south west; datalines;  T1 72 66 76 77  T2 60 53 66 63  T3 56 57 64 58  T4 41 29 36 38    <--- Where is the semicolon to finish this?  It may not be entirely necessary, but its bad coding! run;   The question is Then, suppose you submit the following code. %RandomOrder(cork, 5, 0, outData)       <--- again, where is the semicolon to finish this line, this looks like the cause of your issue as this line runs into the next.   what would happen in we printed this out? Proc print data=outData1;       Run; Proc print data=outData2;   <-- Why is this on the same line as the run; from the previous code, are you trying to hide code?   You can also make sure the macro itself exists at the time its called, i.e. somewhre before the call off %RandomOrder(), you need to have defined the macro with %macro RandomOrder;   Of course, also bear in mind the other advice given here in that the process itself isnt good, don't duplicate data just to have a different sort - its wastes disk space and is inefficient coding.  Assign flag variables which can then be used in sorts. ... View more

To note, as per previous posts I have made here, your code is very sloppy, and hence you are getting problems: data cork; input tree$1-3 north east south west; datalines;  T1 72 66 76 77  T2 60 53 66 63  T3 56 57 64 58  T4 41 29 36 38    <--- Where is the semicolon to finish this?  It may not be entirely necessary, but its bad coding! run;   The question is Then, suppose you submit the following code. %RandomOrder(cork, 5, 0, outData)       <--- again, where is the semicolon to finish this line, this looks like the cause of your issue as this line runs into the next.   what would happen in we printed this out? Proc print data=outData1;       Run; Proc print data=outData2;   <-- Why is this on the same line as the run; from the previous code, are you trying to hide code?   You can also make sure the macro itself exists at the time its called, i.e. somewhre before the call off %RandomOrder(), you need to have defined the macro with %macro RandomOrder;   Of course, also bear in mind the other advice given here in that the process itself isnt good, don't duplicate data just to have a different sort - its wastes disk space and is inefficient coding.  Assign flag variables which can then be used in sorts. ... View more

To note, as per previous posts I have made here, your code is very sloppy, and hence you are getting problems: data cork; input tree$1-3 north east south west; datalines;  T1 72 66 76 77  T2 60 53 66 63  T3 56 57 64 58  T4 41 29 36 38    <--- Where is the semicolon to finish this?  It may not be entirely necessary, but its bad coding! run;   The question is Then, suppose you submit the following code. %RandomOrder(cork, 5, 0, outData)       <--- again, where is the semicolon to finish this line, this looks like the cause of your issue as this line runs into the next.   what would happen in we printed this out? Proc print data=outData1;       Run; Proc print data=outData2;   <-- Why is this on the same line as the run; from the previous code, are you trying to hide code?   You can also make sure the macro itself exists at the time its called, i.e. somewhre before the call off %RandomOrder(), you need to have defined the macro with %macro RandomOrder;   Of course, also bear in mind the other advice given here in that the process itself isnt good, don't duplicate data just to have a different sort - its wastes disk space and is inefficient coding.  Assign flag variables which can then be used in sorts. ... View more

I would suggest a slightly different strategy.  Since you need a DATA step to create a macro variable, let the DATA step compute the average value as well.  Here is the idea:   data _null_; set have (keep=quantity) end=nomore; where quantity > .; tot_quantity + quantity; if nomore then do;    * Divide TOT_QUANTITY by number of observations;    * Transfer the result to a macro variable AVG; end; run;   The details are up to you. ... View more

Try below code.  proc sql; create table want as select a.subj , a.height , a.Weight , b.salary from left a inner join right b on a.subj = b.subj; quit; Try changing key inner join to left join or right join to get desired result.  Link shared by @Reeza must read to understand the concept.   ... View more

Another approach to the interleave is MERGE by flavor which would look like:   data want;     merge duncan betty;     by flavor; run;   However you need to 1) have each of those sets sorted using the BY variable mentioned and 2) Other variables with the same name from Betty will replace the value from Duncan, so you need to rename them.   BUT any combination of data sets you should specify what the result looks like be starting to combine them. MANY approaches will lose the information of which set the values come from if not careful. ... View more

Here's a test you can run, so you can possibly figure this out for yourself.   Input @1 curr_test1 3.   @1 curr_test2 3.1   @1 curr_test3 3;   Then print the results and compare them to the original data. ... View more

Duncan Hines and Betty Crocker are two brands of cake mix in the US. MK ... View more

I suspect that we are missing part of the puzzle hear. Is the original text file supposed to be used for data interchange or was it something that was printed or formatted in a different manner and possibly pasted into another application (Excel perhaps) that has now removed some of the formatting information? Almost every data interchange format would have some way of identifying the end of a field especially one that has embedded blanks. Typically the methods would be a delimiter such as tab or comma, fixed column widths and or quotes around the text that contains spaces.   The irregular number of variables appearing on the example lines is another indicator of something "odd" having possibly been done with this file somewhere in its history. ... View more