The crosstabs template is not available in 9.1. However, check out the CROSSLIST option on the TABLES statement. It produces crosstabulation output in column format and there is an ODS template for it. ... View more

You can suppress this default title by specifying a title statement with no title: [pre]title;[/pre] ... View more

Try the asis=on style attribute. From the ODS documentation: ASIS=ON|OFF specifies how to handle leading spaces and line breaks in an HTML document. ON prints text with leading spaces and line breaks, in the same manner as the listing output. OFF trims leading spaces and ignores line breaks. Default: OFF Tip: The ASIS= attribute is valid only in MARKUP family destinations, PRINTER family destinations, and the RTF destination. http://support.sas.com/documentation/cdl/en/odsug/59523/HTML/default/a002972093.htm#a002576191 ... View more

Single quotes inhibit macro substitution. Use double-quotes. outfile = "C:\&name..txt" Also you'll need two periods in a row, the first to delimit the macro variable name and the second to actually separate species from txt. ... View more

The LS option only works with listing (monospace) output. PROC REPORT doesn't know anything about the page size of an ODS destination such as PDF or RTF. Generally the way to force a break is to use BREAK statement with the PAGE option to force a page break where you want it. You may want to add a NOPRINT column to the report so you can trigger a break based on the value of the column. For example, after every N rows. Regarding "gridlines," the SPANROWS option will cause the cell that contains a single value of a GROUP or ORDER variable to span all the rows for that value. Here's the SPANROWS doc. http://support.sas.com/documentation/cdl/en/proc/59565/HTML/default/a002473620.htm. ... View more

Try using the new SPANROWS option on the proc statement: proc report data=xyz nowd SPANROWS ...; If your output is RTF you must use the new tagsets.rtf destination. ... View more

The WIDTH option only controls the width of columns in monospace (listing, Report Window) output. To control the width of a column in PDF output (and HTML and RTF output), use the STYLE option and specify a value for the WIDTH style attribute. http://support.sas.com/documentation/cdl/en/proc/59565/HTML/default/a002473627.htm#a003072087 http://support.sas.com/documentation/cdl/en/proc/59565/HTML/default/a000146851.htm#a000531789 http://support.sas.com/documentation/cdl/en/odsug/59523/HTML/default/a002972093.htm#a002592786 ... View more

See http://support.sas.com/documentation/cdl/en/hosto390/59577/HTML/default/mvs-init-custom.htm#mvs-init-sysops for information about system options in z/OS. Here's information about SYSPARM itself: http://support.sas.com/documentation/cdl/en/mcrolref/59526/HTML/default/a000543608.htm. ... View more

Try the PRINT=NO column attribute. See the "Column Attributes" table here: http://support.sas.com/documentation/cdl/en/odsug/59523/HTML/default/a001027907.htm ... View more

How about the IFC and IFN functions? Here's the 9.1 doc for IFC: http://support.sas.com/onlinedoc/913/getDoc/en/lrdict.hlp/a002604570.htm. ... View more

Kapil, The simplest solution is to use an IF statement: [pre] IF THEN VAR1 = ; ELSE VAR1 = ; [/pre] Does this meet your needs? The data step language does not have the ?: ternary operator. ... View more

> do not know how to use the option yet. Could you > please give me an example? Thank you so mcuh! options noquotelenmax; ... View more

Use the NOQUOTELENMAX option. http://support.sas.com/documentation/cdl/en/lrdict/59540/HTML/default/a002233891.htm ... View more

I would think that any of the popular version control systems out there would suffice. CVS (http://en.wikipedia.org/wiki/Concurrent_Versions_System) has been around for a long time. Subversion (http://en.wikipedia.org/wiki/Subversion_(software)) is newer but extremely popular. Both are free, have enormous user communities, and are well-documented. ... View more

You're mixing macro code and data step code. The macro statements are executed by SAS's macro processor before PROC REPORT runs. The macro statement is not controlled by the do while statement. Here's a link to the SAS documentation about macros: http://support.sas.com/documentation/cdl/en/mcrolref/59526/HTML/default/getstart.htm ... View more