topic Re: Including modules and programs in SAS Programming

Including modules and programs

jan_t_lagen — Thu, 15 Mar 2018 09:58:19 GMT

I'm new to SAS EG and also new to IML. I have two similar problems that i have encountered.

1. %include does not seem to work as it did in sas base. There i would just give it the location of the sas file and it worked. How do i include a sas file in SAS EG?

2. Is there a way to import/include a module that is not defined inside the same proc iml; statement? I'd rather not define all my modules inside my "main" program.

Thanks!

Re: Including modules and programs

gamotte — Thu, 15 Mar 2018 10:54:15 GMT

Hello,

1. There is no difference between SAS base and EG regarding include statements.

Maybe your SEG is configured to run program on a remote server. So you have either

to deploy the programs you wish to include on the server or execute your programs

locally. Check the menu Tools->Connexions->Servers

I don't understand your second question.

Re: Including modules and programs

jan_t_lagen — Thu, 15 Mar 2018 11:05:00 GMT

1. Okay, Thanks!

2. I would like to do something like this:

this part would optimally be in another file

/*******/

proc iml;

start func1(x);

finish;

;quit;

/*******/

This is in the main file:

/*******/

proc iml;

y = func1(x);

;quit;

/*******/

Re: Including modules and programs

gamotte — Thu, 15 Mar 2018 11:19:18 GMT

File c:\temp\func.sas

----------------

start func1(x);

finish;

---------------

File main.sas

-------------------------

proc iml;

%include "c:\temp\func.sas";

y = func1(x);

;quit;

--------------------------

Re: Including modules and programs

Ksharp — Thu, 15 Mar 2018 12:46:12 GMT

Calling @Rick_SAS

Re: Including modules and programs

Rick_SAS — Thu, 15 Mar 2018 12:54:40 GMT

There are three common ways to store/load or %INCLUDE modules. You can choose whichever one appeals to you.

My favorite is to use the STORE statement to store the modules to a library, then use the LOAD statement to load them when needed. That way, the modules are parsed once and stored in compiled form. When they are loaded, they do not need to be re-parsed or re-compiled.

If you have a lot of modules, you can use the _ALL_ keyword to store and load them all, thus saving some typing.