Chuakp, Try this: %macro macrovariables; %do i=1 %to 3; %let mv = macrovariable;     data _null_;     set codes;     where number = &i.;     call symput("macrovariable&i.",trim(left(dxcode)));     run; %end; %mend macrovariables; 180  %macro macrovariables; 181 182  %do i=1 %to 3; 183  %let mv = macrovariable; 184      data _null_; 185      set codes; 186      where number = &i.; 187      call symput("macrovariable&i.",trim(left(dxcode))); 188      run; 189  %put "macrovariable&i. = &&&mv.&i."; 190  %end; 191 192  %mend macrovariables; 193 194  %macrovariables; NOTE: There were 1 observations read from the data set WORK.CODES.       WHERE number=1; NOTE: DATA statement used (Total process time):       real time           0.00 seconds       cpu time            0.00 seconds "macrovariable1 = 78060" NOTE: There were 1 observations read from the data set WORK.CODES.       WHERE number=2; NOTE: DATA statement used (Total process time):       real time           0.00 seconds       cpu time            0.00 seconds "macrovariable2 = 7784" NOTE: There were 1 observations read from the data set WORK.CODES.       WHERE number=3; NOTE: DATA statement used (Total process time):       real time           0.00 seconds       cpu time            0.00 seconds "macrovariable3 = 09989" ... View more

Hi Aman4SAS. Intriguing question.  You're coding style is not like mine so I am reading your code to learn a style that is different than my own.  You have at least 3 implied "If this condition is true, continue, else return to the next row".  My suggestion is to fully expand these statements to "If  *** then do;   else ***; end:" statements and place "Put _all_" statements in strategic locations to find out which of the three "continue this data steps processing" is causing nothing to be written.  My first observation is that you do not have any data that does meet all three conditions.  Also, SAS has "rules" for handling the reading of multiple datasets; and the two datasets are not the same size; and the end of file condition is met on one of the files sooner than you expect.  At this point, if this were my problem, and I knew I had data that should be output,  I would be going to ' "Combining SAS Data Sets: Basic Concepts" in Chapter 21 of SAS Language Reference: Concepts'.   The quoted portion is from the description of the SET statement in the Dictionary of SAS Statements in the book 'SAS 9.3 Statements Reference'.  I am reading the books because I am intrigued and fascinated by your style and I want to learn more about it..  if LocationType="M";   if SOC in (113021 119041 119111 119121 151111 151121 151122 151131 151132 151133 151134 151141 ); if SOC NE 0 and SOC/1000 NE round(SOC/1000,1); ... View more

  My programming instructor always told me "It's your data, not your code".  When I read DX codes from an EXCEL spreadsheet I would frequently receive errors where "E" DX codes followed by an number were interpreted by EXCEL as numbers in scientific notation. First, Please check your data source for any scientific notation. Second, Please make the format values as character numbers '1', '2','3','4'.   Lastly, Please change the if statements to place quotes around the numbers. Let me know what happens then.  Once the E codes are processing, we can address which rows go to which output file and how many rows you actually want written.  One of the threads suggest to me that you only want one row for a DX code written to an output table as opposed to my suggestion that writes every DX match row to and output table. proc format; value $ dxcodes '78060' = '1' '7784'  = '2' '4659'  = '3' '07999' = '4' '46611' = '5' '77989' = '6' '5990' = '7' '53081' = '8' '27651' = '9' '77189' = '10' '46619' = '11' '79982' = '12' '77931' = '13' '7746' = '14' 'V290' = '15' '77182' = 16 '7755' = '17' 'V070' = '18' '6910' = '19' '78791' = '20' other = '99'; run;   if put(dx(i), $dxcodes.)= '1' then output want1;   if put(dx(i), $dxcodes.)= '2' then output want2;   if put(dx(i), $dxcodes.)= '3' then output want3;   if put(dx(i), $dxcodes.)= '4' then output want4;   if put(dx(i), $dxcodes.)= '5' then output want5;   if put(dx(i), $dxcodes.)= '6' then output want6;   if put(dx(i), $dxcodes.)= '7' then output want7;   if put(dx(i), $dxcodes.)= '8' then output want8;   if put(dx(i), $dxcodes.)= '9' then output want9;   if put(dx(i), $dxcodes.)= '10' then output want10;   if put(dx(i), $dxcodes.)= '11' then output want11;   if put(dx(i), $dxcodes.)= '12' then output want12;   if put(dx(i), $dxcodes.)= '13' then output want13;   if put(dx(i), $dxcodes.)= '14' then output want14;   if put(dx(i), $dxcodes.)= '15' then output want15;   if put(dx(i), $dxcodes.)= '16' then output want16;   if put(dx(i), $dxcodes.)= '17' then output want17;   if put(dx(i), $dxcodes.)= '18' then output want18;   if put(dx(i), $dxcodes.)= '19' then output want19;   if put(dx(i), $dxcodes.)= '20' then output want20; ... View more

Hi chuakp;   The issue with the 'Enn' dx code appears to be caused by the Array variable being defined as numeric variables.  (SAS Dictionary; Array statement syntax; page 24; SAS 9.3 Statements Reference).  Try the array statement change I made and then tell me what your log says. proc format; value $ dxcodes '78060' = 1 '7784'  = 2 '4659'  = 3 '07999' = 4 '46611' = 5 '77989' = 6 '5990' = 7 '53081' = 8 '27651' = 9 '77189' = 10 '46619' = 11 '79982' = 12 '77931' = 13 '7746' = 14 'V290' = 15 '77182' = 16 '7755' = 17 'V070' = 18 '6910' = 19 '78791' = 20 other = 99; run; data want1 want2 want3 want4 want5      want6 want7 want8 want9 want10      want11 want12 want13 want14 want15      want16 want17 want18 want19 want20; set main; array dx $ dx_code1-dx_code41;        /***  arrays default to numeric variable values if not defined previously or not defined as character ***/ flag=0; do i=1 to dim(dx);   if put(dx(i), $dxcodes.)= 1 then flag=1; end; if flag>0 then output;      /*** What stops every matching row from being written to every output dataset?                                                 Where are non-matching rows written to? ***/                             /*** I understood that you want:                                  if put(dx(i), $dxcodes.)= 1 then output want1;                                  if put(dx(i), $dxcodes.)= ... then output want...;                                  if put(dx(i), $dxcodes.)= 20 then output want20;                              ***/ drop i flag; run; ... View more

Hi chuakp, I've encountered your issue in the past.  I'll see if I can dig up the code I wrote.  The problem I had was that SAS was interpreting the 'read from' input diagnosis code variable as numeric.  I was reading from EXCEL and the first 10 diagnosis positions were numeric so SAS said all the values in the EXCEL column were numeric.  The format statement should handle the E19 code if you code all the values in quotes.  If you can post  the error portion of your log or the proc contents output of your input dataset, I will be better able to advise you. ... View more

Hi Kurt, Thank you for providing your suggestion!  My style suggestion is based on the "Comparisons" paragraph in the definition of the SELECT statement of the Dictionary of SAS statements in the SAS 9.3 Statements Reference book.  Page 343.  My style has become habit and I traditionally work with smaller datasets. ... View more