LISTSERV at the University of Georgia
Menubar Imagemap
Home Browse Manage Request Manuals Register
Previous messageNext messagePrevious in topicNext in topicPrevious by same authorNext by same authorPrevious page (April 2008, week 3)Back to main SAS-L pageJoin or leave SAS-L (or change settings)ReplyPost a new messageSearchProportional fontNon-proportional font
Date:         Tue, 15 Apr 2008 14:53:09 -0400
Reply-To:     "Richard A. DeVenezia" <rdevenezia@WILDBLUE.NET>
Sender:       "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From:         "Richard A. DeVenezia" <rdevenezia@WILDBLUE.NET>
Subject:      Re: what system options can you use to debug a SAS program
Comments: To: Jayakumar Ramachandra <jayakumarreddy@GMAIL.COM>
Content-Type: text/plain; charset="iso-8859-15"

Jayakumar Ramachandra wrote: > what system options can you use to debug a SAS program? > debugging here is debugging in sas datastep, sas proc and sas macros.

A SAS program is comprised of one or more steps.

A DATA Step is a sequence of statements that can be debugged interactively using the / DEBUG option. See the online documentation for greater detail.

data NEW / debug; set sashelp.class; product1 = age * height; product2 = age * weight; product3 = height * weight; run;

A PROC Step is a sequence of statements and options associated with a specific procedure. Generally you can not 'step through' a proc as it is running. The proc may have options for outputting diagnostic information to the log or a table.

SAS macros generate text that is then passed to the active executor / parser. There is not a debugger for walking through a macros execution step by step. The generated text can be captured by using the MFILE and MPRINT options.

-- Richard A. DeVenezia http://www.devenezia.com


Back to: Top of message | Previous page | Main SAS-L page