the autocall and compiled features are different. * autocall means that SAS search for a macro definition reference in a set of filerefs (folders) which are the value of the option sasautos the autocall is turned on my default %put mautosource:%sysfunc(getoption(mautosource));*is boolean; %put %sysfunc(getoption(sasautos,keyword));* is character; when a macro is called SAS searched the filerefs for a file with the name of the macro and %includes it, the result of which is that the macro is compiled and stored in the work.sasmacr catalog. * compiled and stored (stored and compiled: not alphabetical, nor the sequence of events, but ...) macros have the %macro statement option "/store" and when they are submitted, or %included, then they are compiled and written not to work.sasmacr catalog but to the libref which is the value of the option sasmstore. %put mstored:%sysfunc(getoption(mstored));*is boolean; %put %sysfunc(getoption(sasmstore,keyword));*is character I kind of like the idea of copying the compiled and stored catalog to the user's work fileref but that is a solution for multiple users in multiple sessions. I think that is a lot of copying another solution is to reset the libref of sasmstore. it does not have to be 'library'. note: files with macros with the store option set ought not to be in any of the filerefs in the sasautos search list. see also: http://www.sascommunity.org/wiki/SASautos_Companion_Reusing_Macros
... View more