Date: Tue, 10 Dec 1996 20:32:01 GMT
Reply-To: Han Oostdijk <hoostdyk@EURONET.NL>
Sender: "SAS(r) Discussion" <SAS-L@UGA.CC.UGA.EDU>
From: Han Oostdijk <hoostdyk@EURONET.NL>
Organization: EuroNet Internet
Subject: macro debugging using log
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
If anyone could show me how to avoid this procedure I would be
1 OPTIONS PS=91 LS=80 S=72 S2=S SOURCE NODATE DQUOTE
2 NOFMTERR YEARCUTOFF=1950 SOURCE2 MPRINT;
4 %INCLUDE 'SOR012.ASD.SAS(FILT5A)' ;
NOTE: %INCLUDE (level 1) file SOR012.ASD.SAS(FILT5A) is file
5 + %INCLUDE 'SOR012.ASD.SAS(ASDSD)' ;
NOTE: %INCLUDE (level 2) file SOR012.ASD.SAS(ASDSD) is file
380 +%MACRO FILT1(SASFIN,VAL,SASFOUT,SD,COR,TYPESD,VENSTER);
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
Han Oostdijk firstname.lastname@example.org Tagline of the week:
Amstelveen, Nederland 2:500/121.6663 lies->big lies->statistics