Date: Mon, 10 Apr 2006 16:12:09 +0000
Reply-To: toby dunn <tobydunn@HOTMAIL.COM>
Sender: "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From: toby dunn <tobydunn@HOTMAIL.COM>
Subject: Re: annoying error message in sas log
Content-Type: text/plain; format=flowed
>>I have one more question. Even if i eliminate the following steps in the
>>program Iam able to see the output .csv file. The following steps are
>>mandatory or not
No they are not. But were neccessary to match your original code.
>>call symput( '_efierr_' , put ( 0 , 8. ) ) ;
>>call symput( '_efirec_' , put ( 0 , 8. ) ) ;
Initializes the macro variables in the Global symbol table and gives them a
starting value of 0.
>>if 0 then set New ;
Sets the attributes in the PDV so that the input data and thus the outptu to
the CSV file conforms to it.
>>_efierr_ ++ _error_ ;
Increments the detection of an error by one.
>>call symput( '_efierr_' , put( ^^_efierr_ , 8. ) ) ;
>>call symput( '_efirec_' , put( _n_ , 8. ) ) ;
If an error occures in the code load those values into a global macro
The whole exercise of error logging in this way seems illy to me unless one
wants to make programming choices automatice based on the presence of an
error or not. Since you are not these peices really arent tha crucial to
the production an output file. The best advice I can give anyone righth now
is quit looking at the specifics of examples the first thing out of the box
and look at the concepts. Once you have that down then go back see if the
example is exactly or very similar to your needs and if so then look and
break down the example. Since no one person can concieve and write up
examples for every possible problem, learning the concepts of programming
and concepts of a programming language will lead you out of the darkness of
confusion faster and more reliably than programming by specific examples.
Hey your on the right track you are making sure that certain code in an
example does not affect the concept of what you want to do.