The road to SAS Global Forum: A training Q&A series

Many of us here at SAS are hustling to prepare for SAS Global Forum set to begin April 18 in Las Vegas. This year’s agenda is shaping up to be a “can’t-miss” event. Monday, before SAS Global Forum begins, there are two SAS Certification testing events. Then after the conference […]

The post The road to SAS Global Forum: A training Q&A series appeared first on SAS Learning Post.

In case of error in SAS program, send email and stop

Any automated program should check for errors and unexpected conditions, such as inability to access a resource and presence of invalid values. Unlike traditional programming languages such as Python and C# that stop processing when an error occurs, SAS barrels ahead through the rest of the program. Therefore, carelessly-written SAS programs can create unwanted side effects, such as overwriting an output data set with bad data.

Previously I wrote about a robust solution for checking SAS error codes which wraps the entire program in a macro and invokes %GOTO EXIT in case an error. This is still the ideal solution when some part of the program must continue, but it comes at a cost: wrapping SAS code in a macro disables syntax highlighting in the SAS Enhanced Editor (though not in SAS Studio). Also, it can be awkward to work with the large code block delimited by the macro, so this post focuses on two alternatives.

Read more »

For more posts like this, see Heuristic Andrew.

Linking analytics outcomes to return on investment

In my SAS Press book Business Statistics Made Easy in SAS® I place a strong focus on the skill of extrapolating analytics/statistical outcomes to key business implications (similar techniques can be used to link statistics to other key societal outcomes). Unfortunately, business analytics often stops short of defining the impact […]

The post Linking analytics outcomes to return on investment appeared first on SAS Learning Post.