You can create a picture format with the round option and use that in the respective table definition. An example is given in this document: http://www2.sas.com/proceedings/sugi30/243-30.pdf (search for "round") ... View more

You could use proc means without a variable and take the _freq_ output value. proc sort data=readin; by y x; run; proc means data=readin; by y x; output out=want; run; ... View more

You're misunderstanding what the macro processor does, and when it does it. If we feed var=xy and num=3 to your macro, it will do the following: &var&var_num will evaluate to xy1 xy2 xy3 respectively All these are clearly not 0, so therefore the macro processor will supply the lines perc_xy1 = xy1 / total; perc_xy2 = xy2 / total; perc_xy3 = xy3 / total; to the SAS interpreter. Anytime total equates to zero, you get a warning. The macro processor is invoked BEFORE any data step runs, and does its work without any knowledge about what happens during data step execution. It is only there to generate program text. Repeat the last sentence three times. You most probably want this in your %do loop: if total ne 0 then perc_&var&var_num = &var&var_num / total; else perc_&var&var_num = 0; This piece of code is then repeatedly supplied vor every var_num to the data step code. ... View more

a) Get the fastest storage infrastructure available. If possible, try to cobble together a bunch of SSD's to form big enough volumes. b) Set up a separate (big enough) volume to assign UTILLOC to. That way the temporary files during sorting are not created on the physical disks that your data already resides on. This reduces contention and the risk of out of space conditions. c) For MERGEs, try to allocate separate physical volumes for the respective sources and target data sets. This may be less important when using SSD's, because they have less latency d) Use the DATA step instead of PROC SQL. ... View more