From experience I've found the "core" parts SAS Base, SAS GRAPH, OR, ETS etc are very stable. other parts we have had issues with in the past - Stored processes

From experience I've found the "core" parts SAS Base, SAS GRAPH, OR, ETS etc are very stable. other parts we have had issues with in the past - Stored processes, LSF for scheduled jobs. SAS tech support have been pretty good though I believe my workplace pays a lot for the privilege of being able to contact them direct. One thing I have found is you can usually throw something together in a pretty "hackish" manner but typically there is a better and more optimal method of doing it which will be much more stable. Sometimes it doesn't hurt to ask tech support "What is the recommended method for doing..." Code which abuses the SAS macro language is especially notorious and a good candiate for asking this. A quick google tells me first class JSON support is pretty new (dec 2016). http://blogs.sas.com/content/sasdummy/2016/12/02/json-libname-engine-sas/ http://blogs.sas.com/content/sasdummy/2016/12/02/json-libnam... I don't know much about this all the A2A messaging is XML based in my org.