|Date: ||Thu, 14 Aug 1997 13:16:26 -0400|
|Reply-To: ||"Zuckier, Gerald" <Zuckier@CHIME.ORG>|
|Sender: ||"SAS(r) Discussion" <SAS-L@UGA.CC.UGA.EDU>|
|From: ||"Zuckier, Gerald" <Zuckier@CHIME.ORG>|
|Subject: ||Re: How do you test?|
|Content-Type: ||text/plain; charset="us-ascii"|
>Interesting approach. Might I suggest, macroizing the IF _N_ EQ 9 THEN
STOP statement at the top of the code, then just calling the macro
wherever needed. Then when everything is fixed, you just have to kill
the statement one time in the macro rather than search and destroy.
>From: Tim Berryhill 3rd time[SMTP:TWB2%Rates%FAR@BANGATE.PGE.COM]
>Sent: Thursday, August 14, 1997 12:54 PM
>Subject: Re: How do you test?
>Rather than discard obs after number 10 (IF _N_ LE 10;), I usually stop
>ninth ob (IF _N_ EQ 9 THEN STOP;). This avoids reading and discarding
>999,991 obs. I preceed this statement with a comment (*DEBUG;), and I
>for *DEBUG; when I finish. For sorting, I will use a view to select a
>Tim Berryhill - Contract Programmer and General Wizard
>TWB2@PGE.COM or http://www.aartwolf.com/twb.html
>Frequently at Pacific Gas & Electric Co., San Francisco
>The correlation coefficient between their views and
>my postings is slightly less than 0
>----------------------[Reply - Original Message]----------------------
>Sent by:Lynn Nonnemaker <LNonnemaker@PRIASSOC.COM>
> How do people test SAS programs, particularly those who never use
>SASinteractively? To test programs on only a few observations,
>simplest way Iknow is to use an options obs=10(or whatever) statement.
>notwork, however, when you have where statements in the program;
>bombs at the first where statement.