Hi:
PROC REPORT options like OL and SKIP are only designed for the LISTING destination and, as you have seen, have no impact on HTML, RTF, PDF or TAGSETS.EXCELXP destinations.
However, to put the equivalent of a skip between groups, if NUM is your GROUP or ORDER item, you can do this:
[pre]
compute after num;
line ' ';
endcomp;
[/pre]
And the LINE statement will put the equivalent of a skipped line between each unique value of NUM.
Also, you should probably change the usage of NUM to ORDER or else change the usage of JOB_CLASS to either ORDER or GROUP, so you can avoid this message in the log:
[pre]
NOTE: Groups are not created because the usage of job_class is DISPLAY. To avoid this note,
change all GROUP variables to ORDER variables.
[/pre]
As far as changing the interior table lines, the JOURNAL style, normally, does not have any interior table lines. So the concept of re-creating the overline (OL) at the break is not something that is easily done in the Excel XML.
For HTML, the "workaround" to simulate an overline is shown in this Tech Support set of examples:
http://support.sas.com/rnd/base/ods/templateFAQ/report1.html
But Excel does not respect the HTMLSTYLE method. So that leaves you with fiddling with the border top/border bottom style elements. The style element that controls the LINE output is the NoteContent style element. In the program below, I modify the NoteContent style element to have a border top of solid black and to have a background and foreground color of pink. These may not be the colors you want, but you can see what gets changed. That change is done in the style template, to show the type of change you can make at the template level for the LINE output.
Without the SUMMARIZE option, you do not get any summary numbers -- so in my program the WEIGHT variable is a DISPLAY usage, so it is not summarized, while the HEIGHT variable is a SUM usage, so it will be summarized. The style of the SUMMARY line is changed in a style override to alter the bordertopstyle and bordertopwidth, etc.
Between these 2 techniques, you should be able to simulate the OL and the SKIP for TAGSETS.EXCELXP output. This worked for me in SAS 9.2 with Excel 2010.
cynthia
[pre]
ods path work.tmp(update)
sasuser.templat(update)
sashelp.tmplmst(read);
proc template;
define style styles.myjour;
parent=styles.journal;
class NoteContent /
foreground=pink
background=pink
bordertopstyle=solid
bordertopcolor=black
bordertopwidth=2;
end;
run;
ods tagsets.excelxp file="C:\temp\LA_Training.xls"
style=styles.myjour
options(doc='Help');
options missing='0';
ods listing close;
proc report data=sashelp.class nowd contents="Claims"
out=test
style(summary)=Header{foreground=purple background=cxeeeeee
bordertopwidth=2 borderbottomwidth=0
bordertopcolor=cyan borderbottomcolor=_undef_
bordertopstyle=solid borderbottomstyle=_undef_};
column age sex name weight height;
define age / order 'ID' style(column)={just=l};
define sex / display 'Job' style(column)={just=l};
define name / display 'Date';
define weight / display 'Class/Injury';
define height /sum;
break after age / summarize ;
compute sex;
if sex eq 'F' then
call define(_row_,"style","style=[background=yellow]");
endcomp;
compute after age;
line ' ';
endcomp;
run;
ods tagsets.excelxp close;
[/pre]