That link has great tips. Also, I like ctrl-alt-plus and ctrl-alt-minus for expanding and collapsing code blocks. (I'm using Enterprise Guide). I built that into a recorded macro I mapped to ctrl-alt-F3. I call the macro "Super Run". The macro collapses the section of code I'm in, goes to the start of the line and selects that line of code. After that, I can just hit F3 to run the selected code block. I like the record macro feature for other things. I have some macro programs in my autoexec file that compile on opening a SAS session. I have the actual typing out the "%macro_name(<parameter>)" where paramater is a value copied on my clipboard. So the keyboard shortcut writes that out, pastes in the value on my clipboard into the parameter, then selects the line of code. So the execution becomes "keyboard shortcut to run macro" then F3 to run. So, not only am I not typing out the actual code that's running, since it is a precompiled macro, I'm not even typing out the name of the macro to get it set up so I can run it. Hope these ideas are helpful. Good luck! ... View more

After your output of class_means, can you create a macro variable for the mean you want to compare it to. Then create a format with proc format using that macro variable as a cutoff in your value statement. Similar to the pattern on page 9-10 of this https://support.sas.com/resources/papers/proceedings13/366-2013.pdf.  ... View more

I think it all depends on how this referenced table is structured. Can you turn that data into macro variables that can be used to subset the data in a data step? %let cnt=8; /*number of datasets you need to combine. Assuming 1 row per table in reference table, should equal row count of reference table*/ %macro dataset_append(); %do i=1 %to &cnt.; /*Create variables to be used to go table by table and subset according to criteria*/ data _null_; set reference_table (firstobs=&i. obs=&i); call symputx('table_name',variable_with_table_name); call symputx('criteria1', variable_with_criteria1); call symputx('criteria2', variable_with_criteria2); run; /*create temp "want" table that is single month table subsetted based on criteria from reference table*/ data want; set &table_name.; where var1=&criteria1. and var2=&criteria2.; run; /*append to your combined dataset*/ proc append base=my_combined_dataset data=want; run; %end; %mend; /*Run Loop*/ %dataset_append() This will loop through one table at a time, subset it first based on criteria in the reference dataset, then append it to a combined dataset. Hope this helps get going in the right direction. ... View more

proc sql; create table want as select * from sample1 where claim_id in (select distinct claim_id from sample1 where proc_cd in ('23','35')) ; quit; ... View more

Here's an alternative using by group processing, which, if you are new to SAS, I'd learn it since it comes in handy for stuff like this. We have to sort it by your group first. Then retain your sum value variable and a temporary variable I'm using to indicate whether it found proc_cd = 23 in that group. I use that to control whether it outputs that group to the output dataset.  proc sort data=sample1; by claim_id; run; data want (drop=has_proc_cd_23); set sample1; by claim_id; retain sum_value has_proc_cd_23; sum_value+value; if proc_cd = '23' then has_proc_cd_23=1; if last.claim_id then do; if has_proc_cd_23=1 then output; sum_value=.; has_proc_cd_23=.; end; run; ... View more

I might need to see what your "want" dataset looks like - does that need to also contain all rows for claim_id = 3 along with the sum value duplicated on each row? Below is what I put together using proc sql;   proc sql; create table want as select claim_id, sum(value) as total_value from sample1 where claim_id in (select distinct claim_id from sample1 where proc_cd = '23') and claim_id = 3 group by claim_id; quit; ... View more

I'm guessing you are wanting to use the types (ID) to pass into some sort of where clause where the condition is then applied. If I'm guessing right, then you'd take your dataset with your ID & condition text, then use data _null_ with call symputx to create macro variables for each type, that would hold the conditional text string. Then you use the macro variable to refer to the condition in later where statements or SQL clauses. Is this what you're trying to do?  data cars; set sashelp.cars; run; data Dictionary; input ID : $6. Condition & $211.; datalines; TYPE_A upcase(Type) IN('SUV', 'SPORTS', 'WAGON') and upcase(Origin) = 'ASIA' AND Horsepower > 150 TYPE_B Horsepower >= 220 and upcase(Origin)='EUROPE' TYPE_C Type='SUV' and Horsepower > 300 and Cylinders > 6 ; data _null_; set dictionary; call symputx(id,condition); run; data want; set sashelp.cars; where &TYPE_A.; run; ... View more

Listen to @Reeza , especially the first sentence. This was the key for me to understanding the macro facility as a beginner. The entire macro facility is a text replacement function. You aren't writing actual SAS programming in macros. You should already have the program written. Once you start wrapping that in a macro, you need to understand which values are going to change (the macro variables) and the best way to insert them into your already written code. This doesn't help answer your specific question, but as a beginner, I wanted you to know what concept really helped me and made the macro facility really click. But Reeza is also right that a lot of people think they need a macro when they don't. So thinking of it as a text replacement tool helped me understand when I need to use it and when I don't.  ... View more