05-09-2017 10:00 AM
To answer this question, we need to know the context. (Re)Setting such automatic macro variables can and does make sense in certain situations.
So where have you encountered this statement?
05-09-2017 10:04 AM
Think of it this way.
Datastep 1 runs and fails, error code set to 1.
Datastep 2 runs and passes, but error code still 1.
Hence why you reset the error macro at the point you want.
05-09-2017 10:07 AM
Normally you see that line in code generated by PROC IMPORT. When reading from a text file PROC IMPORT is essentially an SCL program that analyzes the text file and generates a data step to read it. The generated data step will update that macro variable if there are any errors. So then the PROC can detect the updated macro variable and report the error.
05-09-2017 10:10 AM
If you're asking the question "Does one need to include a line of code like that when we manually rerun code that was produced by proc import or export?" the answer is absolutely not.
Art, CEO, AnalystFinder.com