I can see this is getting too complex, and that MLOGIC might not be enough to paint the right picture.  Here's some more detail. Macro programming statements such as %IF %THEN are never part of a DATA step.  Your program generates this code instead: %if &MOD = N %then %let M1 = N; /* As Tom points out, &MOD has the value of the letters MOD */ %else %if %EVAL(&MOD in 6 8 9) %then %let M1 = Y; %else %let M1 = N; /* Always assigned as N, and never changed during the DATA step */ data TEST1; infile datalines; input ID $ MOD $; length PRODUCT $ 10; if &ID = "0001" and "&M1" = "Y" then PRODUCT = "SCOOTER"; else if &ID = "0001" then PRODUCT = "BIKE"; else if &ID = "0002" then PRODUCT = "SKATEBOARD"; datalines; 0001 N 0001 0 0001 6 0002 8 ; run; The %IF %THEN statements execute just once, before the DATA step even begins to run.  The DATA step does contain the DATA step programming statements such as IF THEN that generates PRODUCT.  But the macro %IF %THEN statements run just once, before the DATA step begins to execute.  Use DATA step programming statements to change the values of DATA step variables as the DATA step executes. ... View more

Since you have gotten this far, I would suggest you would learn more by solving this one yourself. Add this statement at the beginning:   options MLOGIC;   That will show you what macro language is trying to do at each step of the way. ... View more

It seems you often look for ways to shorten your code.  This type of code is a good candidate: if B not in (0, .) then C = A / B; It can be shortened to: if B then C = A / B; When SAS interprets logical expressions as true or false, 0 and missing values are false and all other values (including negative numbers) are true. ... View more

A simple solution for the simplest form that the problem might take on: data want; set have end=done; output; if done; value = 0; if month < 12 then do month = month + 1 to 12; output; end; run; If more is required, let us know why. ... View more

As you can see, this has the possibility of being a complex problem.  At the cost of some processing time, let me show you how to turn it into an easy problem, one that most junior programmers would use and maintain. %macro RRR; %local month. %do YYMM=2306 %to 2403 ; %let month = %substr(&YYMM, 3, 2); %if &month > 0 and &month < 13 %then %do; Data ttt; set Mon_tbl&YYMM.; run; proc append data=ttt base=want force;quit; %end; %end; %mend; %RRR So you go through 100 iterations of a %DO loop, and only process the values that represent a valid month.   ... View more

What would you like for this abbreviated version of your data? Data have; input CustID status; datalines; 123 202401 0 123 202402 0 123 202403 1 123 202404 1 123 202405 0 ; ... View more

Show the context in which <> is being used. SQL interprets it differently than a DATA step. ... View more

Instead of printing the table, put the output into a data set.  Do not bother with subsets or percentages, just keep the original counts.  If it's easier for you, just use PROC SUMMARY to get the counts into an output data set.   Then use a DATA step to remove the missing categories from that output data set.   Then feed the remaining subset with no missing values back into a new PROC TABULATE to print your table.  Since you already have totals, you may need to switch to the SUM statistic (and pctSUM) instead of N (and pctN).   You are 100% correct about PROC TABULATE removing observations where even one class variable has a missing value. ... View more

The best starting point to learn "brief" codes is to learn more about SAS procedures.  These are routines that are already written, already debugged, and well documented.  They often replace dozens of lines of code if you were to try to write something from scratch. Take some common procedures:  FREQ, MEANS, FORMAT, even PRINT.  Read about them and play with them until you know more than twice as much as what you know now.  Procedures embody expert decisions about what functionality is important, and would be useful to have put into a shortened, easier-to-use form. Just my two cents. ... View more

Not invalid, just incorrect. R_Seizure_1--R_Seizure_4 actually is equivalent to R_Seizure_1+R_Seizure_4 ... View more

Here's a variation on Tom's program: data wide; update have(obs=0 keep=id) have(keep=id vaccine_1-vaccine_4 vaccine_sequence) ; by id; run; It gives you a wide form to the data, with all the useful information.  Its not the form that you asked for, but it does contain everything you might need. ... View more

@Ksharp , Of course you're right about that.  And other cases as well:  if the first RECEPTION record comes after a non-RECEPTION record. My real point:  since the poster doesn't say what's really in the data, and it makes such a difference in the complexity of the solution, shouldn't somebody have asked?  The original poster probably doesn't see that the question is important, so let me ask:   For a FILE, does the first record have to be RECEPTION or could it be something else?   If it is something else, should that record be ignored? ... View more

We don't have your data to test with, but here is a push in the right direction.  PROC SUMMARY will compute the values you are asking for, and the MAXID option on the OUTPUT statement.  Bare bones (untested, incomplete program)could look like this: proc summary data=have nway; var salary; class pnr year; output out=want max(sakary) = maxsal maxid.........; run; You'll need to read about maxid, and play with it to get the final program. ... View more