06-20-2012 03:10 PM
When we run a long SAS code, errors maybe happen.and the error information would be push into SAS log.
My question is if an error happened how we can stop running the rest program immediately and have the error information recorded in a macro variable for the future reference?
06-21-2012 12:25 PM
Once upon a time I did something similar. The general idea was to write a macro that would check the status after each datastep/ procedure boundary.
I would recommend that instead of saving to a macro variable alone to write it to a permanent dataset with some information.
There may be some operating system dependencies, so which OS? Also is this a batch job or interactive? Macros or running in a macro?
My approach had been that the macro was called at each boundary that provided some information as the last datastep/ proc in the program. Then the system date and time were queried.
If the %SYSERR was greater than a cutoff, 4 if I remember, then the the message was retrieved from the SYSERRORTEXT system variable. All of this was appended to a log dataset. Then used the %ABORT statement to end the program. Mine was batch job running overnight so I used the ABEND option.
06-22-2012 06:52 AM
Have you ever look at the SAS code gnerated by DI Studio? It uses macros to record the results of procs and data steps. Maybe that will help.
Between steps it generates code such as
Maybe this idea could be expanded for your needs.
06-24-2012 10:03 PM
"an error happened how we can stop running the rest program immediately "
Check some system options such as abend ...
"and have the error information recorded in a macro variable for the future reference?"
The &SYSERRORTEXT automatic macro variable contains the text of the last
error message formatted for display on the SAS log.