Hi: When you have a local copy of SAS and do a %INCLUDE, you can include code snippets, or whole programs from your computer's drive or from a shared drive. When you run a stored process, first your stored process does NOT run on your local machine. It runs on a Stored Process Server or a Workspace Server. So when you have a stored process which contains a %INCLUDE, the Platform configuration process has some directories that are recommended down in the Lev1/SASEnvironment folder -- one directory is for autocall macros, another directory is for format libraries and a third directory is for SASCode, such as you might %INCLUDE. In your local session, you, as a programmer can write a program which will include code from any machine that your SAS session can get to. However in a stored process you don't, technically, have a "session" under your personal control, you request a stored process to execute and in the metadata, the appropriate server session is started up, but you really don't have a chance to see anything going on in the session. If your stored process has a%INCLUDE, it cannot use code on your local C drive. It must do the %INCLUDE from a location that is known to the server where the stored process will be running. The Platform config provides you this location. Conceptually, %INCLUDE will include code in both scenarios. Where SAS is running will make a difference in how you build the %INCLUDE reference. cynthia
... View more
