I'm working on a macro function to append a record to a SAS data set every time a specific function is called, and I need to include information on the context from which it was called.  Is there a way to programmatically access the 'breadcrumb' trail that appears in the log when mprintnest or mlogicnest options are enabled?   With the 'mlogicnest' option enabled in the log excerpt below, it's clear that I've called the 'send_message' macro function which in turn calls the 'test_macro' macro function.  Using 'put _all_;' from that inner function shows me (among many others) macro variables available in the 'send_message' scope, and the automatic macro variable 'sysmacroname' shows that the current macro function is named 'test_macro'.   Is there another place to look for the whole breadcrumb trail? or do I have to construct it as I traverse the nested macro function tree?   Thank you! David   86 %send_message( MLOGIC(SEND_MESSAGE): Beginning execution. 87 message_dest = WORK.message_log, 88 message_type = exception, 89 message_user = david 90 ) MLOGIC(SEND_MESSAGE): Parameter MESSAGE_DEST has value WORK.message_log MLOGIC(SEND_MESSAGE): Parameter MESSAGE_TYPE has value exception MLOGIC(SEND_MESSAGE): Parameter MESSAGE_USER has value david MLOGIC(SEND_MESSAGE): Parameter MESSAGE_SRC has value unknown MLOGIC(SEND_MESSAGE): Parameter MESSAGE_TEXT has value MPRINT(SEND_MESSAGE): data WORK.new_message; MPRINT(SEND_MESSAGE): format message_timestamp_utc E8601LX.; MPRINT(SEND_MESSAGE): length message_type $32 message_src $128 message_user $32 message_text $256 message_exception_detail $1024; MPRINT(SEND_MESSAGE): message_timestamp_utc = tzones2u(datetime()); MPRINT(SEND_MESSAGE): message_type = symget('message_type'); MPRINT(SEND_MESSAGE): message_src=symget('message_src'); MPRINT(SEND_MESSAGE): message_user = symget('message_user'); MPRINT(SEND_MESSAGE): message_text = symget('message_text'); ... MLOGIC(SEND_MESSAGE.TEST_MACRO): Beginning execution. MLOGIC(SEND_MESSAGE.TEST_MACRO): This macro was compiled from the autocall file .../macros/test_macro.sas ... MLOGIC(SEND_MESSAGE.TEST_MACRO): %PUT _all_ SEND_MESSAGE MESSAGE_DEST WORK.message_log SEND_MESSAGE MESSAGE_SRC unknown SEND_MESSAGE MESSAGE_TEXT SEND_MESSAGE MESSAGE_TYPE exception SEND_MESSAGE MESSAGE_USER david ... AUTOMATIC SYSMACRONAME TEST_MACRO ... MLOGIC(SEND_MESSAGE.TEST_MACRO): Ending execution. MLOGIC(SEND_MESSAGE): Ending execution.   ... View more

I'm trying to do something similar to another post, but the accepted answer didn't meet my requirements.   We're working on a SAS macro to produce control chart data tables using PROC SHEWHART.  We need to capture exceptions/errors, take appropriate action, and then continue with subsequent data steps/procedures.  In the example I've included below, we're simply changing from a p-Chart to a c-Chart when something causes the p-Chart to fail.  This specific example is where the denominator value is larger than the numerator; that is one known failure mode, but we don't know what other p-Charts rules could be violated.  Pre-testing for a specific failure mode, or failure modes, is not a desirable solution.   As expected, an exception, caught while the SYNTAXCHECK option is set, causes SAS to enter the special syntax check mode, and subsequent procedure calls within the macro fail due to empty data sets.   I have a workaround where I temporarily set the NOSYNTAXCHECK system option immediately before the error-prone procedure call, and then set SYNTAXCHECK immediately following the exception handling code.  In our environment we are supposed to keep the SYNTAXCHECK option active for the duration of the SAS session, so this is also an undesirable solution.   Is it possible to recover from "syntax check mode" after an error has occured with the SYNTAXCHECK system option set?   I would rather include a few lines of "reset" code within my exception-handling block and continue on.  I have set the OBS and REPLACE system options in my exception-handling block, but that doesn't appear to completely reverse the syntax check mode changes to the environment.   options mprint mprintnest mlogic mlogicnest symbolgen spool syntaxcheck; options msglevel=i notes source serror fullstimer errorcheck=normal; %put NOTE: obs option : %sysfunc(getoption(obs,keyword)); %put NOTE: replace option : %sysfunc(getoption(replace)); %put NOTE: syntaxcheck option : %sysfunc(getoption(syntaxcheck)); data WORK.shewhart_data; input interval_month mmddyy10. numerator denominator; datalines; 07/01/2018 5 11 08/01/2018 14 9 09/01/2018 12 24 10/01/2018 19 27 11/01/2018 15 13 12/01/2018 20 34 01/01/2019 25 15 02/01/2019 22 31 03/01/2019 34 28 ; %macro test_shewhart( in_data=, out_data= ); proc shewhart data=&in_data; pchart numerator*interval_month / subgroupn=denominator sigmas=3 nochart outtable=&out_data; run; %if &syserr ne 0 %then %do; options obs=max replace; run; quit; %put NOTE: obs option : %sysfunc(getoption(obs,keyword)); %put NOTE: replace option : %sysfunc(getoption(replace)); %put NOTE: syntaxcheck option : %sysfunc(getoption(syntaxcheck)); proc shewhart data=&in_data; cchart numerator*interval_month / sigmas=3 nochart outtable=&out_data; run; %end; %mend test_shewhart; %test_shewhart( in_data = WORK.shewhart_data, out_data = WORK.chart_data ) I've also attached the log with this code run from a brand new SAS session.   Thanks, David ... View more

As noted in the SAS 9.4 Intelligence Platform Desktop Application Administration Guide, "When you upgrade to a new release of the SAS Add-In for Microsoft Office, you need to manually replace all non-default roles and capabilities."   In the SAS Add-In 7.13 for Microsoft Office, one new capability was added, "Create or Modify SAS Programs."  Our validated deployment is SAS 9.4m3 which included AMO 7.11; some of our users have updated the client to 7.14.   How do we add that new 'capability' to metadata to control access to the new feature of the Add-In?   Thanks! David         ... View more