15 Comments

1. 

   Paulus Mau on March 1, 2014 4:27 am

   Thanks for the belated Christmas Present :) Great workshop! Thanks for coming!
2. 

   Saurabh on December 22, 2012 11:48 am

   Divyesh, try removing that $amp and run the code.

   U will get the ans !!
3. 

   Michelle Homes on December 21, 2012 3:10 pm

   Whilst I appreciate the 3 gifts you offered my preference would be to do this in 1 procedure, proc stdize... All the code above could be replaced with the following:

   proc stdize data=miss reponly missing=0 out=missing2;
   var _numeric_;
   run;
4. 

   Christophe Z. on December 21, 2012 1:47 pm

   All this can be done with a proc stdize as well. Just 3 lines of code:

   proc stdize data=miss reponly MISSING=0 out=new_miss;
   var _numeric_;
   run;
   • 

     Charu Shankar on January 2, 2013 11:04 am

     thanks Christophe & Michelle,
     proc stdize is another great option to get the missing values converted.. I wanted to showcase the ability of proc sql to interface with the macro language in step 2--that allows users to store variables so easily & use & reuse them over and over again..
5. 

   Quentin on December 20, 2012 9:19 pm

   Hi,
   I'm confused as to why you have 2 do-loops. What is the purpose of the :
   do i=_n_ to new;
   loop? I wouldn't think it is needed.

   Thanks,
   -Q.
   • 

     Charu Shankar on January 2, 2013 11:01 am

     thanks Quentin, nice catch. that was a redundant do loop. .step 3 can easily read:
     data missing2;
     set miss;
     array miss{*} &allnumvars;
     do k=lbound(miss) to hbound(miss);
     if miss{k} = .
     then miss{k}=0;
     end;
     run;
6. 

   Divyesh Dave on December 20, 2012 12:38 pm

   I think I completely followed your code except for "amp". Where was this macro variable created? At least, we know "allnumvars" was created in Proc SQL. But I am lost on "amp"
   • 

     charu on December 21, 2012 4:22 pm

     thanks Divyesh for pointing that out.. I realized this typo problem only after all your comments.. only after the blog posted as I mentioned in my reply to Eric. so the last line in step 2 should really be
     %put &allnumvars;
     Have a great holiday season!
7. 

   Matt Psioda on December 20, 2012 12:27 pm

   In the case where you want to examine and update all numeric variables in the data set, you might consider using the _Numeric_ keyword in the array definition to include all numeric variables (currently in the program data vector) in the array.

   For example:

   data missing2;
   set miss ;
   array miss{*} _Numeric_;
   NoChange = .; /*Will be left Missing;*/

   do j=1 to dim(Miss);
   if Miss(j) = . then Miss(j) = 0;
   end;
   drop j;
   run;

   Happy Holidays!
   • 

     Dominic on December 20, 2012 6:00 pm

     You can refine that syntax still like so:

     data missing2;
     set miss;

     array x _numeric_;
     do over x;
     if x = . then x = 0;
     end;
     run;
   • 

     charu on December 21, 2012 4:20 pm

     very very nice gift Matt, thoroughly appreciate it! I just wanted to show SAS skills at being multilingual with sql, macro & datastep. I do like your gift & am so glad you posted it so others can also share.. happy holidays!
8. 

   Eric Jackson on December 20, 2012 10:34 am

   Thank for the gift! I did want to point out to slave off any confusion in the code snipits that the & that might show up in your browser display are html code for an ampersand. Took me a second to realize this until it hit me.
   • 

     Eric Jackson on December 20, 2012 10:36 am

     And in my post it converted it to an actually ampersand ... "& amp ;" no spaces is what I was referring too.
   • 

     charu on December 21, 2012 4:16 pm

     thanks Eric. Between browser and sometimes quirky blog editing tool, the ampersand took a hit. you're right step 2 should really read as
     %put &allnumvars;
     happy holidays.