Date: Wed, 11 Dec 1996 02:09:18 -0800
Reply-To: FRS--LiteWate <faith@FRSA.COM>
Sender: "SAS(r) Discussion" <SAS-L@UGA.CC.UGA.EDU>
From: FRS--LiteWate <faith@FRSA.COM>
Subject: Re: macro debugging using log
Content-Type: text/plain; charset="us-ascii"
At 08:32 PM 12/10/96 GMT, Han Oostdijk wrote:
>I hope someone is willing to help me with the following problem.
>When using macro's I don't know how to use the information in
>the log when there are warnings or errors.
>
>In the example below (in MVS-batch 6.08) I call a macro which is
>contained in an included member. Every error or warning message
>seems to occur on line 552 (the line in the log on which the macro
>is called). What does column mean in this situation?
>Are there any debug options helping to link these column-numbers
>to the generated code I see if I use MPRINT?
>
>In this particular case my helpdesk gave the advice to extract
>the generated code from the log and run the program again without
>the macro's but with the code. When I did this the line:column
>pointed (more clearly) to the problem area and I could solve
>the problem.
>
>If anyone could show me how to avoid this procedure I would be
>very grateful.
>
>1 OPTIONS PS=91 LS=80 S=72 S2=S SOURCE NODATE DQUOTE
>2 NOFMTERR YEARCUTOFF=1950 SOURCE2 MPRINT;
>
>3
>
>4 %INCLUDE 'SOR012.ASD.SAS(FILT5A)' ;
>
>NOTE: %INCLUDE (level 1) file SOR012.ASD.SAS(FILT5A) is file
>
> SOR012.ASD.SAS(FILT5A).
>
>5 + %INCLUDE 'SOR012.ASD.SAS(ASDSD)' ;
>
>NOTE: %INCLUDE (level 2) file SOR012.ASD.SAS(ASDSD) is file
>
> SOR012.ASD.SAS(ASDSD).
>
>--cut--
>380 +%MACRO FILT1(SASFIN,VAL,SASFOUT,SD,COR,TYPESD,VENSTER);
>--cut--
>552 %FILT1(ASSETD1.BEFCMY,BEF,TEST.BEFCMY,6,YES,MED,25);
>--cut--
>NOTE: Missing values were generated as a result of performing an
> operation on missing values.
>
> Each place is given by: (Number of times) at (Line):(Column).
>
> 646 at 552:148 646 at 552:210 632 at 552:148 632 at 552:210
>
> 632 at 552:148 632 at 552:210
>
Hans, this is not a macro thing. it's a datastep informative message. it's
actually saying that it attempted to perform an operation on missing values
in your dataset 646 times at line 552 in your log (see your line 552 above)
in column 148 and 248 of the statement on line 552. most likely the values
are missing, thus the informative note.
run a freq on your data values and look for missing values. i betcha have
646 missing values for 2 of your parameters and 632 missing values for 3 of
your parameters. OR the parameters don't actually have missing values but
the expression you're trying to evaluate WITH your parameters may be missing.
best...
>Han Oostdijk hoostdyk@euronet.nl Tagline of the week:
>Amstelveen, Nederland 2:500/121.6663 lies->big lies->statistics
>
>
--
Faith Renee Sloan (FRS ASSOCIATES) - WEB Site Design and Interactive
Programming/SAS and Internet Training - A SAS Institute Quality Partner
http://www.frsa.com (world-wide-web home base)
http://www.frsa.com/sas - SAS for the Masses
http://www.frsa.com/bbpage.shtml BodyBuilding Page
a Pointgrrl for San Francisco Webgrrls
sanfran@webgrrls.com -- http://www.webgrrls.com/sf
faith@frsa.com
| 
