Cynthia, I have found that the ODS RTF statments necessary to do this work "as advertised", but the same can NOT be said for the comparable statements for the ODS TAGSETS.RTF destination: in a Tech Support Track that I submitted (December 2010) regarding the headery and footery section data "command" in the ODS TAGSETS.RTF it was finally determined that there was a problem with that tagset (in Version 9.2), in that the resulting RTF file had the correct Section Data string in it to set the header and footer margin ... followed immediately by a re-setting of the headery and footery to equal the top and bottom margin. The final reply to that support track was that the support person was going to discuss the problem with development and "... expect ... to modify the tagset to change this behavior" ... and it appears to have NOT yet been fixed in Version 9.3. FYI---Here's the snippet of the "offending" tagset code (from the 9.3 TAGSETS.RTF) --- wherein you can see that the section data is put in the RTF output file, which would include the headery footery values one might have issued in the SAS ODS statement (e.g., ods tagsets.RTF options(SECT='\headery720\footery576') --- then the headery and footery is re-set afterwards to the top/bottom margins. put $sect_data; put NL; put "\headery" TOPMARGIN "\footery" BOTTOMMARGIN; ... View more

Tom, I already was using the NOPRINT in the procedures that needed that (e.g, UNIVARIATE), and the other I was using (SUMMARY) doesn't produce 'printed' results. I didn't try your suggestion of routing the LISTING to "null", since in SAS 9.3 the default ouput destination is not LISTING ... and I found David Kelley's later answer to work. Thanks for the suggestion anyway. Take care-Allen ... View more

David, Worked great, when I used your suggestion INSTEAD of closing all ODS destinations (I assume you intended that). Thanks-Allen ... View more

I addressed the issue of more than one active ODS destinations in the following code ... and it appears to work 'great' in both 9.2 and 9.3 (the 1st two statements are just to set things up for testing on both versions): ods listing; ods html; %MACRO test; /* Save all current system used in the macro for later re-setting to original state    GOPTIONS that are set in the macro are reset to the default system values only */ %let sopts= %sysfunc(getoption(missing,keyword)) %sysfunc(getoption(center)) %sysfunc(getoption(xwait)) %sysfunc(getoption(xsync)) %sysfunc(getoption(date)) %sysfunc(getoption(papersize,keyword)) %sysfunc(getoption(bottommargin,keyword)) %sysfunc(getoption(topmargin,keyword)) %sysfunc(getoption(rightmargin,keyword)) %sysfunc(getoption(leftmargin,keyword)) %sysfunc(getoption(orientation,keyword)) ; OPTIONS MPRINT; /* Following launch of PROC TEMPLATE is to 'force' SASHELP.VDEST to have observations (if SAS just    initialized it would not have any values */ proc template; run; data _null_;    set sashelp.vdest end=last;    call symput('INIT_DEST'||left(_n_),destination);    call symput('INIT_STYL'||left(_n_),style);    if last then call symput('N_DEST',LEFT(_n_));    else; run; %do I = 1 %to &N_DEST %by 1;        ODS &&INIT_DEST&I CLOSE; %end; options noxwait xsync; ods rtf file='test.rtf'; ods results off; /* PUT CODE FOR MACRO HERE ... THAT VARIOUSLY USES A VARIETY OF ODS DESTINATIONS */ ODS _ALL_ CLOSE; /* Reset system options, etc. to starting values and goptions to system default values */ OPTIONS &SOPTS; GOPTIONS reset=goptions; /* Reset ODS destinations to original values */ %do I = 1 %to &N_DEST %by 1;    ODS &&INIT_DEST&I style=&&INIT_STYL&I; %end; ODS RESULTS ON; %MEND test; %TEST ... View more

Thanks---worked perfectly!!! BTW-I'll worry about future versions of SAS when I have to cross that bridge. ... View more

David, Very useful --- but somewhat problematic to actually use in practice. When I launch a 'fresh' interactive session of SAS 9.2 or 9.3, sashelp.vdest has NO observations. So my 'workaround' to that issue (is to use the proc print to actually 'populate' VDEST) in some paired code --- the 1st part is at the beginning of my macro, and the second part is at the end: First part: ods results off; proc print data=sashelp.vdest;run; data _null_;    set sashelp.vdest;    call symput('INIT_DEST',destination);    call symput('INIT_STYL',style);    stop; run; ODS &INIT_DEST CLOSE; Second part: ODS &INIT_DEST style=&INIT_STYL; ODS RESULTS ON; The problem with this code is that it seems to work just fine with 9.3 ... but with SAS 9.2 ... I get a Listing output in the output window of the contents of SASHELP.VDEST. (It also assumes that there is only one active destination ... and it is the first one in VDEST)!!! The interesting part of this that I'm wondering about it that SAS 9.2 nor 9.3 doesn't really have the Listing or HTML output active (i.e., VDEST has no obs when SAS initialized), but only has those active after 'asking' for some output (in this case via Proc Print). So really the code above is not necessarily setting things to their initial state, but seems to be as close as I can get (with my coding skills). Any clue as to what I'm doing wrong that results in the proc print output going to the listing output window in 9.2 (seems to me the ods results off should have handled that ... and it appears to in 9.3)? Thanks-Allen ... View more

Interestingly ... after I looked into this some more myself as well as your reply --- I now realize that in 9.2 it was ignoring the KEYWORD parameter for the boolean type of system options ... and that I can get what I want by removing the KEYWORD option for those system options ... and that the code will work in both 9.2 and 9.3!!! THANKS-Allen ... View more