topic Re: How to compile Macro into a perm location with encryption/unreadable?! in SAS Programming

How to compile Macro into a perm location with encryption/unreadable?!

hellohere — Sat, 16 Jul 2022 13:38:10 GMT

How to compile Macro into a physical directory? Whenever SAS is open, the macro is there to run?!

Also to encrypt it; to make it "unreadable" even with OPION MPRINT...

Thanks

Re: How to compile Macro into a perm location with encryption/unreadable?!

ballardw — Sat, 16 Jul 2022 14:55:01 GMT

When compiling a macro you can add the option SECURE on the %MACRO statement. Documentation indicates you should not store passwords or code segments, use for entire Proc or Data step. The STORE option lets you specify a specific library and catalog location for the compiled result. Use the system option SASMSTORE= to specify a permanent location. You will need to have the system option MSTORED to use the macro. Read the options of the %MACRO statement in the documentation.

Caveat: code compiled in a macro code is specific to OS and version. Catalogs created in SAS 9.3 are not usable by 9.4 and may have issues with the incremental releases.

Do not lose track of the source code or you will not be able to recover the code. We have had that question asked a few times on the forum.

Re: How to compile Macro into a perm location with encryption/unreadable?!

hellohere — Sat, 16 Jul 2022 20:44:17 GMT

Thanks.

I run the SAS DOC codes below. It is fine.

But one quest: options mstored sasmstore=mylib; tells SAS to find Macro in mylib; DOES that mean work.sasmacr is not working then?!

options mstored sasmstore=mylib;
libname mylib "C:\Users\24891\sas";
%macro secure/store secure; /* This macro is encrypted */
data _null_;
x=1;
put "This data step was generated from a secure macro.";
run;
%mend secure;
%secure;

filename maccat catalog 'mylib.sasmacr.secure.macro';
data _null_;
infile maccat;
input;
list;
run;

Re: How to compile Macro into a perm location with encryption/unreadable?!

SASKiwi — Sat, 16 Jul 2022 23:12:26 GMT

I suggest you read the documentation on this subject. Once the SASMSTORE option is set. All macros compiled afterwards will be stored in that location. If you already have macros in WORK.SASMACR then those should continue to work.