So many autoexecs; three tips for BI administrators

BASE SAS users are already familiar with the autoexec file. This is a .sas file that typically resides in the installation folder of the SAS executable. Instructions for setting it up in UNIX, Windows, and other environments is readily available on the SAS website. In SAS BI configurations there are as well as SAS programs scattered throughout but which one(s) should be edited? Three tips:

  1. Avoid future conflicts: SAS recommends that no matter where they are located, you should edit the "" version to avoid conflicts in installing future upgrades/updates.
  2. Where do you need the information: You can preassign SAS libraries, set default options, point to macro and format locations, or create global macro variables with these autoexec files, just choose wisely where you need the information available.
  3. Precedence is important: There is also a main file for the entire SAS installation at: C:\\Program Files\\SASHome\\SASFoundation\\9.3\\ This is the granddaddy file that drives everything else. Of course an option here could then be overwritten by an option down the stream in another file. So understand the order of precedence.




Affects all servers within the application server context \\SASApp
The SAS Schedule Server can execute jobs on the BatchServer. Changes to this file only affect the BatchServer jobs. \\SASApp\\BatchServer
Only the Connect Server \\SASApp\\ConnectServer
Only the OLAP Server \\SASApp\\OLAPServer
Only the Pooled Workspace Server \\SASApp\\PooledWorkspaceServer
Only the Stored Process Server \\SASApp\\StoredProcessServer
Only the Workspace Server \\SASApp\\WorkspaceServer
Affects all services within the SASMeta application server context (recommended for use by SAS Administrators managing SAS applications) \\SASMeta
SASMeta - Batch Server only \\SASMeta\\BatchServer
SASMeta - Workspace Server only \\SASMeta\\WorkspaceServer
Scheduling Server \\SchedulingServer
Share Server \\ShareServer
tags: Administration

2 Trackbacks

  1. By Demystifying SAS autoexec files - SAS Users Groups on November 28, 2012 at 8:02 am

    [...] her recent blog post So many autoexecs; three tips for BI administrators,  Angela Hall dispels some of the mystery around finding and understanding autoexec files in a [...]

  2. [...] proc metalib code to update all the libraries the user has access to change, and place this in the workspace server autoexec (SAS Config Included is a sample to loop [...]

Post a Comment

Your email is never published nor shared. Required fields are marked *


You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>