4

I've been using a macro library so that I can use macros without compiling them first. The problem is that when I change the macro and save it, then refresh my filename for the macro lib, this is not enough to update and use the new macro?

Anyone have any ideas why it is still using and compiling the old macro before it was saved?

78282219
  • 593
  • 5
  • 21

2 Answers2

4

The first time a macro is called, if it hasn't already been defined, SAS will check your autocall path and iterate through those locations trying to find it.

When it finds the macro in your autocall library it compiles it and saves the compiled version to your work folder. Subsequent calls to the macro will result in SAS using the compiled version of the macro.

In order for it to be refreshed (if you have made changes since it was compiled) you need to open the code to the macro and submit it again. That will redefine/recompile it for you.

Alternatively, you could also find the catalog in your work folder that contains the compiled versions of the macros and delete it from there (typically work.sasmacr).

Robert Penridge
  • 8,424
  • 2
  • 34
  • 55
2

Robert explains why you see the behavior.

I use the following to easily reinclude a changed macro. This assumes you have a FILENAME called MACROREF defined to the folder in question.

%include MACROREF(my_macro);

Obviously change the my_macro to the macro you need to be compiled.

filename macroref "c:\temp";

%include MACROREF(MacroOne);

If you have a folder full of macros (as stated in the comments) you can include the whole folder.

%include "%sysfunc(pathname(MACROREF))/*.sas";

This will recompile the whole folder. Just don't have any non-macro sas files in that folder, otherwise you are running them too.

DomPazz
  • 12,415
  • 17
  • 23