LISTSERV at the University of Georgia
Menubar Imagemap
Home Browse Manage Request Manuals Register
Previous (more recent) messageNext (less recent) messagePrevious (more recent) in topicNext (less recent) in topicPrevious (more recent) by same authorNext (less recent) by same authorPrevious page (January 2006, week 2)Back to main SAS-L pageJoin or leave SAS-L (or change settings)ReplyPost a new messageSearchProportional fontNon-proportional font
Date:   Thu, 12 Jan 2006 06:35:30 -0800
Reply-To:   Joep <jsteeman@BUSINESSDECISION.COM>
Sender:   "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From:   Joep <jsteeman@BUSINESSDECISION.COM>
Organization:   http://groups.google.com
Subject:   Re: Using the Autocall library in SAS for storing usermade macros
Comments:   To: sas-l@uga.edu
In-Reply-To:   <dq5mgo$ocl$1@gryps6.uni-greifswald.de>
Content-Type:   text/plain; charset="iso-8859-1"

Rune,

you can use stored macro as Dietrich suggested, but then you have to point out where the library can be found: options sasmstore='library';

Then you have to compile your macros:

%macro test / store; statements %mend;

In order to use the autocall library there are 2 restrictions: 1 you can only use macros which are compiled on startup. New and altered macros will not get in effect until the next startup. 2 the name of the macro must be the same as the name of the file which contains the macro code.

Furthermore as you stated, the autocall library must be concatenated to the existing autocall libraries at startup, f.i. in the autoexec file. The files you listed contain the source code of the standard SAS autocall macros. You could try to alter your autoexec in the way that you do not concatenate your autocall library but instead replace the existing with yours. You will not be able to use the standard autocall macros.

Regards, Joep


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