Hello @PamG,   Try the TITLE statement with a HEIGHT= option.   Example: title1 height=5 "Data : aaa"; title2 height=4 "Years of study: xxx"; title3 height=3 "Outcomes: BBB"; proc print data=sashelp.class; run; title; The values 5, 4, 3 are relative sizes, but you can specify absolute values like 24pt as well. ... View more

Hello @jlf,   That problem and possible solutions are described in this Knowledge Base article: Troubleshooting issues related to SAS® file-type association in a Windows operating environment. ... View more

Hello @Hlm2019,   Minor correction: SYMGET is not a CALL routine, but a function.   Example (for @Roberto_BM): data _null_; set sashelp.class; mvar='age'||put(age,2.); if not symexist(mvar) then call symputx(mvar,name); else call symputx(mvar,catx(' ',symget(mvar),name)); run; %put &=age11; %put &=age12; %put &=age13; ... ... View more

Alternatively, you could follow Example 2: Clustering a Grouped Scatter Plot from the documentation: data want; set forest_data; series=1; a=a1; lowa=lowa1; uppera=uppera1; output; series=2; a=a2; lowa=lowa2; uppera=uppera2; output; drop a1--uppera2; run; proc sgplot data=want; scatter x=XValue y=a / yerrorlower=lowa yerrorupper=uppera group=series groupdisplay=cluster clusterwidth=0.15; yaxis label="Odds Ratio" ; run; ... View more

@alepage wrote: I have 14 datasets to check, using proc contents.  For future checks like this (especially if more datasets are involved) you may want to consider querying DICTIONARY.COLUMNS rather than reviewing a lot of PROC CONTENTS output: /* List all TRX.PRM_TRX_... datasets not containing variable driverType */ proc sql; select memname from dictionary.columns where libname='TRX' & memname eqt 'PRM_TRX_' group by 1 having max(upcase(name)='DRIVERTYPE')=0; quit; ... View more

Hi @ssll,   You could avoid the %IF-%THEN/%ELSE statements like this: %let m=NNEEEERRREEE; %let N=no report will be generated; %let R=quarter to date comparison report; %let E=not in Q3 and not in Jan or Feb; %let c=%substr(&m,&current_month_num,1); %put &&&c;   However, I suspect that you actually want to execute some reporting statements if &c=R. In this case you could at least avoid the nesting: %let m=NNEEEERRREEE; %let N=no report will be generated; %let E=not in Q3 and not in Jan or Feb; %let c=%substr(&m,&current_month_num,1); %if &c=R %then %do; %inc 'C:\Temp\myQtoDreport.sas' / source; %end; %else %do; %put &&&c; %end; ... View more

Alternatively, you could store the exact value of max(of result1-result16) in variable SummaryResult (and thus have more information available) and define a format to display 100 as "UNKNOWN", 200 as "NO", etc. proc format; value sumres .='MISSING' 100='UNKNOWN' 200='NO' 300-high='YES' other='STRANGE' ; run; data want; set have; if n(of result:) then SummaryResult=max(of result:); format SummaryResult sumres.; run; This formatted variable could be used in CLASS statements (e.g. in PROC MEANS), as a group variable in PROC REPORT, for creating frequency tables (with PROC FREQ), etc. However, it would be slightly less convenient than a character variable if you had to retrieve the formatted values very often (as in if vvalue(SummaryResult)='YES' then ...). ... View more

@shoin wrote: My apologies Chris, I clicked on the wrong accept as solution ... Hello @shoin, It's easy to correct this: Select Chris's post as the solution after clicking "Not the Solution" in the option menu (see icon below) of the current solution. ... View more

Hello @RJY9,   Glad to see that Tom's solution worked for you. Then it would be fair and help later readers if you marked his helpful reply as the accepted solution, not your own "thank you" post. Could you please change that? It's very easy: Select his post as the solution after clicking "Not the Solution" in the option menu (see icon below) of the current solution.   ... View more

Hi @hellohere, @hellohere wrote: I prefer in SAS/SQL. Then try this:   proc sql; create table want as select a.*, max(b.x1) as x1_running_max from temp a, temp b where a.byvar=b.byvar & b.ind<=a.ind group by 1,2,3,4; quit;     ... View more

Hi @SamSays,   @SamSays wrote: I've tried one of those picture formats (low-high) but it doesn't work because I also want it to round. Picture formats do round if you use the ROUND option: proc format; picture pctfmt (round) 0-high='0009.9%'; run; As demonstrated below, this picture format displays non-negative values x<999.95 exactly like the PERCENT8.1 format displays x/100. 247 data chk; 248 do n=0 to 999949; 249 x=n/1000; 250 p1=put(x, pctfmt.); 251 p2=put(x/100, percent8.1); 252 if p1 ne p2 then output; 253 end; 254 run; NOTE: The data set WORK.CHK has 0 observations and 4 variables. However, the PERCENT8.1 format adds an unnecessary trailing blank, so that variable p2 has length 8, whereas p1 has length 7, which is the default length of the format. Unlike PERCENT8.1, the picture format would also display larger values up to 9999.949... correctly. ... View more

Courier is a proportional  font, i.e., narrow characters like "i" occupy less space than wide characters like "m." This variability makes it virtually impossible to achieve perfect alignment by using space characters such as '20'x or 'A0'x because the exact amount of horizontal space required is most likely not an integer multiple of the width of a space character.   This problem does not occur with non-proportional fonts (where all characters have the same width) such as Courier New, Cumberland AMT or Lucida Console. I had suggested the latter because, like Courier, it is essentially a sans-serif font. See the example text below (created by TEXT statements of PROC SGPLOT) where the digit strings help counting characters.   One proportional and three fixed-width fonts. ... View more

Fully agree with Tom. I would expect that those values would be judged unequal even within Teradata, i.e., the transfer to SAS has not caused the difference. Note that the same sort of numeric precision issues can easily occur in SAS, too. Tom's solution would be the remedy here as well.   Example: 288 data _null_; 289 total_amount=7+0.11+0.27; 290 mean_amount =7+0.27+0.11; 291 if total_amount > mean_amount then flag=1; 292 else flag=0; 293 rflag=(round(total_amount,1e-9) > round(mean_amount,1e-9)); 294 put (_all_) (=best32.); 295 put (_all_) (hex16. /); 296 run; total_amount=7.38 mean_amount=7.38 flag=1 rflag=0 401D851EB851EB86 401D851EB851EB85 3FF0000000000000 0000000000000000 Note that even the BEST32. format conceals the tiny difference (of 2**-50=8.881...E-16) between total_amount and mean_amount, which arose from just adding three numbers in different orders and which is reliably revealed by the HEX16. format. ... View more

@MingC wrote: @FreelanceReinh , thank you very much for your quick and detailed response. I was wondering if I there is a proc template options could fix the alignment, which bothered me in the past couple of weeks. After I tried your idea to add 'A0A0A0A0A0'x to the end of shorter label value, I can left-align the label now. You're welcome. There doesn't seem to be a PROC TEMPLATE option to control that alignment. Glad to hear that the 'A0'x trick worked for you. (The minor imperfection in the alignment shown in your screenshot is due to the proportional font you are using.)   Another approach would be SG annotation. Continuing the example from the previous post: %sganno; data anno; %sgtext(reset=all, id="xtlabel", label="EDU", textcolor="GraphData1:contrastcolor", textsize=9, textweight="bold", x1=0, x1space="layoutpixel", y1=69, y1space="layoutpixel", anchor="left"); %sgtext(label="CONSUMER", textcolor="GraphData2:contrastcolor", width=90, y1=55); run; proc template; define statgraph axistable; begingraph; entrytitle "Average Product Sales By Division and Country"; layout overlay / cycleattrs=true pad=(left=18px) yaxisopts=(offsetmax=0.15 label="Sales By Country"); innermargin / align=bottom opaque=true backgroundcolor=cxf5f5f5; axistable x=product value=actual / name="division" stat=mean display=(values) headerlabel="Sales By Division" headerlabelattrs=GraphLabelText valueattrs=(size=9pt weight=bold) colorgroup=division class=division; endinnermargin; barchart category=product y=actual / name="country" barlabel=true barlabelformat=dollar5.0 stat=mean group=country groupdisplay=cluster; discretelegend "country" / title="Country:" location=inside valign=top; annotate / ID="xtlabel"; endlayout; endgraph; end; run; proc sgrender data=have template=axistable sganno=anno; run; The display=(values) option in the AXISTABLE statement suppresses the original labels, which are then replaced by the labels (here: hard-coded) in the annotation dataset ANNO. The new pad= option of the LAYOUT statement provides the space on the left needed for those labels. Their vertical positioning (i.e., determining the y1 coordinates) is cumbersome.   Result: Using SG annotation ... View more