data x; x='x';y=1;a=1.2;b=1.2; run; proc sgplot data=x; vbarparm category=x response=y ; scatter x=x y=a/ discreteoffset=-0.4 markerattrs=(symbol=X size=14); scatter x=x y=b/ discreteoffset=0.4 markerattrs=(symbol=square size=14); run; ... View more

Hi: Without code, it's hard to speculate. It will make a difference about how you do it, depending on what your destination is and what initial style you're using. You have 2 approaches -- using a TEXTDECORATION style override or changing the bordertop... or borderbottom... style overrides. HEADLINE and HEADSKIP are LISTING only options, so they would NOT be giving your anything in ODS output. Your output looks like JOURNAL style, which has RULES=GROUPS turned on that might put the bottom line under the column headers.   This forum posting https://communities.sas.com/t5/ODS-and-Base-Reporting/How-to-write-ods-latex-template/m-p/471278#M21087 showed the use of border controls with PROC REPORT and ODS RTF to put an extra line into spanning headers. That person was using ACROSS items, so your use case might be different. Cynthia ... View more

What about a TEXT statement? Instead of scatterplot? ... View more

data test; /*create two value*/ c1=104; c2=2; /*use right alignment*/ s1=right(put(c1,8.))||" (99.00)"; s2=right(put(c2,8.))||" (99.00)"; output; /*create another row*/ c1=2; c2=104; s1=right(put(c1,8.))||" (99.00)"; s2=right(put(c2,8.))||" (99.00)"; output; put _ALL_; run;   Output: ... View more

Just an FYI...The three separate scatter statements cause different y-offsets due to size of markers and text.  As you increase marker size or text size), offsets increase, causing the alignment problems in different containers (Layout Overlays).  Each container with separate axes will have separate offsets based on their individual contents.    One way to overcome this is to set fixed offsets on all containers (yaxisopts=(offsetmin=0.05 offsetmax=0.05).  Or, use common row axes to force all offsets to be the same.  This will also happen with TEXT plot or AXISTABLE.  One way to avoid this is to use only ONE Layout Overlay, and put the axis tables in the INNERMARGIN.   Your use case may be simple enough that you can use SGPLOT with a YAXISTABLE of two columns on the right side.  GTL may not be required.  See example here:  https://blogs.sas.com/content/graphicallyspeaking/2016/05/30/ctspedia-clinical-graphs-subgrouped-forest-plot/.  Note the use of two yAxisTables on the left and one yAxisTable on the right with 3 variables.   ... View more

Thanks for the input, everyone!   First, the code belongs to my client and I'm not able to share a lot of detail--just the overall logic. Second, this isn't even my project; I just jumped in to help and now my curiousity has gotten the best of me. 😉    The output is 6 pages.  Page 1 is a waterfall all 5 values of VAR, each a different color: VAR = 1 then red VAR = 2 then blue VAR = 3 then yellow VAR-= 4 then green VAR = 5 then purple   Pages 2 through 6 are 1 VAR each, and we want the colors to match what is on page 1; so page 2 (VAR = 1) will be red, page 3 (VAR = 2) will be blue, etc.   It seems that the overall issue is how the macros are set up: A proc template is called to create the style "STYLEX", using "replace GraphData1" etc. to set the 5 colors for page 1. A proc template is called to create the format for the page 1 waterfall Proc sgrender creates page 1 from the dataset A macro is created to subset the dataset by value of VAR (if VAR = &val) A proc template (still within the macro) is called to create the format for the pages 2-6 waterfalls Proc sgrender (still within the macro) creates the page Macro is called 5 times, once for each value of VAR Another macro combines all 6 pages into one output--and this macro calls STYLEX.  Since pages 2 through 6 only have one value of VAR, each one gets treated like VAR = 1 and is assigned red.   I think what we might need to do is find a way to alter that final macro so that we can create each page in a different style, THEN combine them. ... View more