Usage Note 20241: Using an autoexec.sas file with SAS® Data Integration Studio
If you need to use an autoexec.sas file to set up global parameters and automatic libnames for the SAS Data Integration Studio client, follow these steps.
- Add the -AUTOEXEC option to the
configuration path, so that it is used via the
invocation of the given SAS Workspace Server.
- Once it has been added, restart the SAS object spawner service.
Some things to keep in mind about the SAS Workspace Server and how it works:
- The SAS Workspace Server is defined in the SAS
Management Console under the SAS Object Spawner with
the associated servers, which lists the servers that
the spawner is permitted to start.
- The servers in the list run on the machine with
which the spawner is associated. This was
specified in the Associated Machine field in the
SAS Object Spawner Options window.
- You will not see the bat file under:
C:\SAS\<configdir>\Lev1\SASMain\WorkspaceServer
The SAS Workspace Server does not have a .bat
file, so it cannot work without the SAS object spawner.
- Files associated with the Workspace Server include:
- sasv9.cfg - C:\SAS\<configdir>\Lev1\SASMain\
This file calls !sasroot\sasv9.cfg (the default location is
C:\Program Files\SAS\SAS 9.1\.
- *.log - C:\SAS\<configdir>\Lev1\SASMain\ WorkspaceServer\logs
Workspace server logging is not enabled by default.
Logging should be enabled only through
SAS® Management Console, not directly in sasv9.cfg
as this file is used by the other SAS® Foundation Servers.
You will not see a service for the SAS Workspace Server.
Operating System and Release Information
SAS System | SAS Data Integration Studio | Microsoft Windows XP Professional | 3.2 | | 9.1 TS1M3 SP4 | |
Microsoft Windows XP 64-bit Edition | 3.2 | | 9.1 TS1M3 SP4 | |
Microsoft Windows NT Workstation | 3.2 | | 9.1 TS1M3 SP4 | |
Microsoft® Windows® for 64-Bit Itanium-based Systems | 3.2 | | 9.1 TS1M3 SP4 | |
Microsoft Windows Server 2003 Enterprise Edition | 3.2 | | 9.1 TS1M3 SP4 | |
Microsoft Windows Server 2003 Standard Edition | 3.2 | | 9.1 TS1M3 SP4 | |
Microsoft Windows 2000 Professional | 3.2 | | 9.1 TS1M3 SP4 | |
Microsoft Windows Server 2003 Datacenter Edition | 3.2 | | 9.1 TS1M3 SP4 | |
Microsoft Windows 2000 Server | 3.2 | | 9.1 TS1M3 SP4 | |
Microsoft Windows 2000 Datacenter Server | 3.2 | | 9.1 TS1M3 SP4 | |
64-bit Enabled Solaris | 3.2 | | 9.1 TS1M3 SP4 | |
Solaris for x64 | 3.2 | | 9.1 TS1M3 SP4 | |
Microsoft Windows 2000 Advanced Server | 3.2 | | 9.1 TS1M3 SP4 | |
Linux on Itanium | 3.2 | | 9.1 TS1M3 SP4 | |
Linux | 3.2 | | 9.1 TS1M3 SP4 | |
HP-UX IPF | 3.2 | | 9.1 TS1M3 SP4 | |
64-bit Enabled HP-UX | 3.2 | | 9.1 TS1M3 SP4 | |
Tru64 UNIX | 3.2 | | 9.1 TS1M3 SP4 | |
OpenVMS Alpha | 3.2 | | 9.1 TS1M3 SP4 | |
64-bit Enabled AIX | 3.2 | | 9.1 TS1M3 SP4 | |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.
Date Modified: | 2009-04-24 14:26:27 |
Date Created: | 2007-05-21 13:25:38 |