LISTSERV at the University of Georgia
Menubar Imagemap
Home Browse Manage Request Manuals Register
Previous messageNext messagePrevious in topicNext in topicPrevious by same authorNext by same authorPrevious page (August 2008, week 5)Back to main SAS-L pageJoin or leave SAS-L (or change settings)ReplyPost a new messageSearchProportional fontNon-proportional font
Date:   Sun, 31 Aug 2008 11:25:44 -0700
Reply-To:   Jack Hamilton <jfh@STANFORDALUMNI.ORG>
Sender:   "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From:   Jack Hamilton <jfh@STANFORDALUMNI.ORG>
Subject:   Re: Compiled Macros
Comments:   To: Alan Churchill <savian001@GMAIL.COM>
In-Reply-To:   <011301c90b7a$e8ed9610$bac8c230$@com>
Content-Type:   text/plain; charset=US-ASCII; format=flowed; delsp=yes

There has been a lot of discussion about this. My recollection of the conclusion is that there's no way to protect your macro against a determined programmer in 9.2, when the SECURE macro option is introduced.

The most recent thread was entitled "read only macro code", June 20-21 of this year. This was a short thread (I think everyone was tired of the topic), but Ron Fehd gave a pointer to one of his papers: <http://www2.sas.com/proceedings/sugi30/267-30.pdf >.

You're probably giving this macro to someone who's still running 9.1.3 or earlier, so you're out of luck. Can you put the essential code into a compiled data step?

-- Jack Hamilton jfh@alumni.stanford.org videtis illam spirare libertatis auram

On Aug 31, 2008, at 8:04 am, Alan Churchill wrote:

> Everyone, > > > > Is there a way to lock a macro so its code and its execution cannot > be seen? > I thought this had been discussed before but having trouble finding > it. > > > > Thanks, > > Alan > > > > Alan Churchill > Savian > www.savian.net <http://www.savian.net/>


Back to: Top of message | Previous page | Main SAS-L page