Hi, I don't have any issue when running your code on my computer. Is there any message in the log? Can you share a picture of the result you get? Have you tried to split the statement into several lines? It could be that the width of your screen editor is too short. Make sure ls=max too. Best Regards, ... View more

Thanks @DanH_sas    So to make sure I properly understand the statement "Basic bar charts (HBARBASIC and VBARBASIC) do not support uniform axis scaling. However, they do support group uniformity"   1/ "group uniformity" would mean that values of the variable listed in the group= option can be harmonized across graphs generated with the by statement i.e. the legend can be common to all graphs when using uniform=group, xscalegroup or yscalegroup.   The harmonizsation of the values of the category variable is not foreseen with those options. However in my test, uniform=xscalegroup harmonizes the values of the category variable when displayed on the x-axis (vbarbasic) and uniform=yscalegroup harmonizes the values of the category variable displayed on the y-axis (hbarbasic) but uniform=group does not harmonize the values of the category variable. By default, the legend is specific to each graph. According to the SAS Online Documentation uniform=all by default. But when I use it, the y-axis gets truncated. (I tried all the values listed in the documentation).   2/ "do not support uniform axis scaling" means that uniform=scale, xscale, yscale, all would have no effect when using vbarbasic or hbarbasic. However, when there is no group variable in the statement, I could see in my test that xscale/yscale and xscalegroup/yscale affects the order of the values of the category variable.   Only uniform=group does not affect the order of the values of the category variables (as in the default setting). The other values (all, scale) would truncate the response axis.   ----- So if group= is used, we should consider using uniform=group to harmonize the legend but should prefer another method to set the order of the values of the category variable. We should not use the default group=all explicitely to avoid response axis truncation.   If no group= is used, we should not use the uniform= option and we should use another method to set the order of the values of the category variable. Correct? ... View more

Hi, The issue is not on the proc means but on the proc sgplot. ... View more

Thanks. I forgot about the *. For those reading this post, notice that with ods output, the sparse option is not needed. ... View more

@tomy Actually I was not expecting any difference between ods output statement and the output statement. I'm really surprise that both label and format are added to output datasets by default without any possibility to avoid them upfront. I don't see as beneficially to have to go back to old syntax because of that or add additional steps. ... View more

@Ksharp Actually no. Here is an example showing that using the global option is not helping: options nolabel; ods exclude all; ods output summary=test; proc means data=sashelp.class ; class sex; var height; attrib _all_ label=' '; run; ods exclude none; options label; proc sql; select name, format, label from dictionary.columns where upcase(libname)='WORK' and upcase(memname)='TEST'; quit; proc print data=test label noobs; run; ... View more

no variable label in the dataset as given in the example. ... View more

statistics with no label. ... View more

Using a ifn fonction may be easier for people to interpret the code. For original numeric variables, the code would have to be updated to avoid messages in the log e.g. chk=ifn(vvalue(sex)=put(sex,best12.),1,0); ... View more