Date: Wed, 16 Apr 2008 11:11:54 -0400
Reply-To: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE>
Sender: "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE>
Subject: Re: what system options can you use to debug a SAS program
... it's a secret option! It still works but does the same thing as MPRINT.
On Wed, 16 Apr 2008 03:29:49 -0700, RolandRB <rolandberry@HOTMAIL.COM>
>On Apr 16, 10:01 am, gerhard.hellrie...@T-ONLINE.DE (Gerhard
>> You should not do all in one step. First level should be the macro. To
>> sure that the macro produces what you want, use the MPRINT (or MACROGEN)
>MACROGEN is out of date now. You won't find it in the sas
>documentation. They expect you to use MPRINT instead.
>> option. With that you see what the macro produces (or not).
>> Second thing, if you assume that the right code is produces, but the
>> contents of macro variables are not that what you expect, use SYMBOLGEN.
>> If that is ok, the logic might be not ok: MLOGIC. Do NOT use all that
>> options together! Your log is full and you won't find what you're
>> There are some others, look in the docu for that.
>> Second is a data-step and 7 or procs.
>> Options source source2 (to see includes) notes. Some others like
>> for example, all are for more or less informations in the log.
>> For the datastep there is a real debugger available:
>> data test / debug;
>> you can then step through the code, watch variable contents and follow
>> logic of the program flow. That might be the last thing, if pure
>> and code review does not help.
>> On Tue, 15 Apr 2008 13:47:12 -0400, Jayakumar Ramachandra
>> <jayakumarre...@GMAIL.COM> wrote:
>> >what system options can you use to debug a SAS program?
>> >debugging here is debugging in sas datastep, sas proc and sas macros.-
Hide quoted text -
>> - Show quoted text -