topic Re: How to call macros without using %INCLUDE Statement in SAS Programming

How to call macros without using %INCLUDE Statement

SangramjitPanda — Fri, 12 Jan 2018 20:11:44 GMT

Hi All,

I have some concern on using macros in other sas program files but without using %INCLUDE statement.

Requirement:

I have a sas macro named SendMail.sas which is used to sent out email notification, As of now I am using %INCLUDE statement to call this file in other SAS Program files.

Is there any way I can directly use the macro without mentioning the %INCLUDE statements all the time.

Thanks,

Sangramjit

Re: How to call macros without using %INCLUDE Statement

novinosrin — Fri, 12 Jan 2018 20:16:27 GMT

IMHO, the use of auto call macros works well for me

http://documentation.sas.com/?docsetId=mcrolref&docsetTarget=n1o5fkxq0gqdpcn1xs3ksdks69tf.htm&docsetVersion=9.4&locale=en

Re: How to call macros without using %INCLUDE Statement

Reeza — Fri, 12 Jan 2018 20:28:02 GMT

Or do the %include within the autoexec so it's loaded when you start SAS.

However, this would be a production type usage, others who use your program may not know where the files are stored so I'd document it somehow within your programs. There are often questions on here about someone trying to find a former colleagues old macro definitions....

@SangramjitPanda wrote:

Hi All,

I have some concern on using macros in other sas program files but without using %INCLUDE statement.

Requirement:

I have a sas macro named SendMail.sas which is used to sent out email notification, As of now I am using %INCLUDE statement to call this file in other SAS Program files.

Is there any way I can directly use the macro without mentioning the %INCLUDE statements all the time.

Thanks,

Sangramjit

Re: How to call macros without using %INCLUDE Statement

SangramjitPanda — Fri, 19 Jan 2018 20:42:33 GMT

Thanks Rezza, this idea worked.

Re: How to call macros without using %INCLUDE Statement

SangramjitPanda — Fri, 19 Jan 2018 20:44:45 GMT

Thanks novinosrin, I tested the autocall library approach by storing the macros at the ~/sasautos path. It worked fine.