Users can construct tables of descriptive statistics, analysis variables, and
keywords for statistics. Tables can have up to three dimensions: column; row
and column; or page, row and column.

PROC REPORT

Ad hoc report generator included with base SAS software. Combines features
from the PRINT, MEANS, and TABULATE procedures along with elements of the DATA
step to provide a powerful report writing tool.

Building batch reports to be run over and over and distributed to a wide
audience. Can also be used to build reports interactively through pull-down
menus.

Question: How can a duplicate copy of a data set be
created within the same library without copying the data set to an intermediate
location, renaming it, and copying it back?

Answer: The most efficient way to do this is to use the APPEND
procedure. Also, unlike the DATA step, indexes are copied as well. If the data
set supplied on the BASE= option does not exist, then it's created with the
contents of the data set supplied with the DATA= option. Here is an example of
creating a duplicate data set with a different name in the same library using
PROC APPEND.

Have you ever found yourself with a SAS data step which runs, but not quite
as you want it to? The SAS Data Step debugger can help you find logic errors in
your program by allowing you to step through your code, examine data, and even
temporarily modify data values. The full text of this tip appears in the 1997
Q1 edition of SAS Communications.

To invoke the data step debugger, add the DEBUG option in
the DATA statement. For example:

data temp/debug;
do i=1 to 10;
x=i*2;
output;
end;
run;

When you submit this code you will see two new windows on your workstation
screen, the DEBUGGER LOG window and the
DEBUGGER SOURCE window. In the DEBUGGER LOG
window you can type commands to examine variable values, set breakpoints, and
change values. The results of these commands are shown as well. The DEBUGGER
SOURCE window contains the source code for the DATA
step you are debugging.

To end the debugger session, type QUIT on the command line in
the DEBUGGER LOG window.

Setting Break Points

To set a breakpoint for examining data, use the break
command. For example, instead of processing all the observations through the
DATA step until you reach patient 3 (in the following example), set a breakpoint
by typing