Configuration autoexec files in order of precedence

Reference: Configuration Files for SAS Servers

Introduction to the Configuration File Reference

This section provides tables that show the name, location, and purpose of the various server configuration files that are used in the SAS Intelligence Platform. Each table in this appendix contains the following columns:

Order of Precedence

The numbers in this column indicate the order in which the options in the files are applied. Option settings in files with higher orders of precedence override the settings in files with lower orders of precedence.

"Not applicable" means that the option settings in the file do not affect, and are not affected by, option settings that are specified in other files.

Path and Filename

All paths that begin with Lev1 are located in the SAS configuration directory (see About the Configuration Directory). Within the pathnames, the following variables are used:

• server-context, which indicates the name of an application server grouping (for example, SASApp, SASMeta, or SASMain)
• server-name, which indicates the name of the logical server or server that the configuration file applies to

Purpose

This column describes the purpose of the configuration file, indicates that certain configuration files are not to be modified by users, and provides references to detailed documentation.

Configuration Files for the Metadata Server

The following table shows the configuration files that affect the metadata server. For an explanation of each columns' contents, see Introduction to the Configuration File Reference.

Order of Precedence	Path and Filename	Purpose
1	Windows: \Lev1\SASMeta\MetadataServer\sasv9.cfg UNIX and z/OS: /Lev1/SASMeta/MetadataServer/sasv9.cfg	Specifies server startup options for the metadata server and contains calls to the other files that are listed in the table. Do not modify this file. If you need to make changes, modify the sasv9_usermods.cfg file that is in the same directory.
2	Windows: SAS-install-directory\SASFoundation\9.2\sasv9.cfg UNIX: SAS-install-directory/SAS-install-directory/SASFoundation/9.2/sasv9.cfg z/OS: Not applicable	Specifies system options that apply to all SAS sessions on the host machine.
3	Windows: SAS-install-directory\SASFoundation\9.2\locale\sasv9.cfg UNIX: SAS-install-directory/SASFoundation/9.2/locale/sasv9.cfg z/OS: <HLQ>.V92D8ddd.CNTLDSN(BATlocaleW0)	Specifies system options that apply to all SAS sessions on the host machine in the specified locale.
4	Windows:\Lev1\SASMeta\MetadataServer\sasv9_usermods.cfg UNIX and z/OS:/Lev1/SASMeta/MetadataServer/sasv9_usermods.cfg	Contains site-specific modifications to the metadata server start-up options. Use this file to change the options that are specified in the sasv9.cfg file in the same directory. SeeOptions for the Metadata Server Invocation Command.
Not applicable	Windows: \Lev1\SASMeta\MetadataServer\omaconfig.xml UNIX and z/OS:/Lev1/SASMeta/MetadataServer/omaconfig.xml	Specifies options for the metadata server and metadata repositories. See Reference Information for omaconfig.xml.
Not applicable	Windows: \Lev1\SASMeta\MetadataServer\logconfig.xml UNIX and z/OS:/Lev1/SASMeta/MetadataServer/logconfig.xml	Specifies the logging configuration for the server. SeeAdministering Logging for SAS Servers.
Not applicable	Windows: \Lev1\SASMeta\MetadataServer\adminUsers.txt UNIX and z/OS:/Lev1/SASMeta/MetadataServer/adminUsers.txt	Defines your system's initial unrestricted user. See Metadata Server: Unrestricted Role.
Not applicable	Windows:\Lev1\SASMeta\MetadataServer\trustedUsers.txt UNIX and z/OS:/Lev1/SASMeta/MetadataServer/trustedUsers.txt	Conveys privileged status to a service account to enable that account to act on behalf of other users. See About the Initial User Accounts.
Not applicable	Windows:\Lev1\SASMeta\MetadataServer\trustedPeers.xml UNIX and z/OS:/Lev1/SASMeta/MetadataServer/trustedPeers.xml	Can be used to limit the scope of trust for connections from SAS sessions to the metadata server. Initially, the scope is not limited. See the SAS Intelligence Platform: Security Administration Guide.
Not applicable	Windows: Not applicable UNIX and z/OS:/Lev1/SASMeta/MetadataServer/MetadataServer.srv	On UNIX and z/OS, contains information that is used by generate_boot_scripts.sh to regenerate the sas.servers script.

In z/OS environments, the following additional configuration files affect the metadata server:

Order of Precedence	Path and Filename	Purpose
1	z/OS: <HLQ>.TKMVSENV(TKMVSENV)	Contains name/value pairs (environment variables) that apply to all SAS sessions on the machine.
2	z/OS: /Lev1/SASMeta/MetadataServer/tkmvsenv.cfg	Contains name/value pairs (environment variables) that apply to the metadata server. Do not modify this file. If you need to make changes, modify the tkmvsenv_usermods.cfg file that is in the same directory.
3	z/OS:/Lev1/SASMeta/MetadataServer/tkmvsenv_usermods.cfg	Contains site-specific modifications to the name/value pairs (environment variables) for the metadata server. Use this file to change the options that are specified in the tkmvsenv.cfg file in the same directory. See the Configuration Guide for SAS 9.2 Foundation for z/OS.

Configuration Files for Components of SAS Application Servers

The following table shows the configuration files that affect servers that are components of a SAS Application Server. These servers include OLAP servers, workspace servers, pooled workspace servers, stored process servers, and SAS/CONNECT servers. For an explanation of each columns' contents, seeIntroduction to the Configuration File Reference.

Order of Precedence	Path and Filename	Purpose
1	Windows: \Lev1\server-context\server-name\sasv9.cfg UNIX and z/OS: /Lev1/server-context/server-name/sasv9.cfg	Specifies start-up options for the server and contains calls to the other files that are listed in this table. Do not modify this file. If you need to make changes, modify the sasv9_usermods.cfg file that is in the same directory.
2	Windows: \Lev1\server-context\sasv9.cfg UNIX and z/OS: /Lev1/server-context/sasv9.cfg	Specifies start-up options that apply to all components of the application server. Do not modify this file. If you need to make changes, modify the sasv9_usermods.cfg file that is in the same directory. See System Options for SAS Application Server Components in the SAS Intelligence Platform: Application Server Administration Guide.
3	Windows: SAS-install-directory\SASFoundation\9.2\sasv9.cfg UNIX: SAS-install-directory/SASFoundation/9.2/sasv9.cfg z/OS: Not applicable	Specifies system options that apply to all SAS sessions on the host machine.
4	Windows: SAS-install-directory\\SASFoundation\9.2\locale\sasv9.cfg UNIX: SAS-install-directory/SASFoundation/9.2/locale/sasv9.cfg z/OS: <HLQ>.V92D8ddd.CNTLDSN(BATlocaleW0)	Specifies system options that apply to all SAS sessions on the host machine in the specified locale.
5	Windows: \Lev1\server-context\sasv9_usermods.cfg UNIX and z/OS: /Lev1/server-context/sasv9_usermods.cfg	Contains site-specific modifications to the server-startup options that apply to all application server components. Use this file to change the options that are specified in the sasv9.cfg file in the same directory. See System Options for SAS Application Server Componentsin the SAS Intelligence Platform: Application Server Administration Guide.
6	Windows: \Lev1\server-context\autoexec.sas UNIX and z/OS: /Lev1/server-context/autoexec.sas	Contains SAS statements that are executed immediately after SAS initializes on all components of the application server. Do not modify this file. If you need to make changes, modify the autoexec_usermods.sas file that is in the same directory.
7	Windows: \Lev1\server-context\autoexec_usermods.sas UNIX and z/OS: /Lev1/server-context/autoexec_usermods.sas	Contains site-specific modifications to the autoexec.sas file that is located in the same directory.
8	Windows: \Lev1\server-context\server-name\sasv9_usermods.cfg UNIX and z/OS: /Lev1/server-context/server-name/sasv9_usermods.cfg	Contains site-specific modifications to the server's startup options. Use this file to change the options that are specified in the sasv9.cfg file in the same directory. See System Options for SAS Application Server Components in the SAS Intelligence Platform: Application Server Administration Guide.
9	Windows: \Lev1\server-context\server-name\autoexec.sas UNIX and z/OS: /Lev1/server-context/server-name/autoexec.sas	Contains SAS statements that are executed immediately after SAS initializes on the server. Do not modify this file. If you need to make changes, modify the autoexec_usermods.sas file that is in the same directory.
10	Windows: \Lev1\server-context\server-name\autoexec_usermods.sas UNIX and z/OS: /Lev1/server-context/server-name/autoexec_usermods.sas	Contains site-specific modifications to the autoexec.sas file that is located in the same directory.
Not applicable	Windows: \Lev1\server-context\server-name\logconfig.xml UNIX and z/OS: /Lev1/server-context/server-name/logconfig.xml	Specifies the logging configuration for the server. SeeAdministering Logging for SAS Servers.
Not applicable	Windows: \Lev1\sasv9_meta.cfg UNIX and z/OS: /Lev1/sasv9_meta.cfg	Specifies metadata server connection information for the SAS OLAP Server, SAS/SHARE server, and SAS Table Server.
Not applicable	Windows: Not applicable UNIX and z/OS: /Lev1/server-context/server-name/server-name.srv	On UNIX and z/OS, contains information that is used by generate_boot_scripts.sh to regenerate the sas.servers script.

In z/OS environments, the following additional configuration files affect components of a SAS Application Server:

Order of Precedence	Path and Filename	Purpose
1	z/OS: <HLQ>.TKMVSENV(TKMVSENV)	Contains name/value pairs (environment variables) that apply to all SAS sessions on the machine.
2	z/OS: /Lev1/server-context/server-name/tkmvsenv.cfg	Contains name/value pairs (environment variables) that apply to this server. Do not modify this file. If you need to make changes, modify the tkmvsenv_usermods.cfg file that is in the same directory.
3	z/OS: /Lev1/server-context/tkmvsenv.cfg	Contains name/value pairs (environment variables) that apply to all components of the application server. Do not modify this file. If you need to make changes, modify the tkmvsenv_usermods.cfg file that is in the same directory.
4	z/OS: /Lev1/server-context/tkmvsenv_usermods.cfg	Contains site-specific name/value pairs (environment variables) that apply to all application server components. Use this file to change the options that are specified in the tkmvsenv.cfg file in the same directory. See the Configuration Guide for SAS 9.2 Foundation for z/OS.
5	z/OS: /Lev1/server-context/server-name/tkmvsenv_usermods.cfg	Contains site-specific modifications to the server's name/value pairs (environment variables). Use this file to change the options that are specified in the tkmvsenv.cfg file in the same directory. See the Configuration Guide for SAS 9.2 Foundation for z/OS.

Configuration Files for SAS/SHARE Servers and SAS Table Servers

The following table shows the configuration files that affect SAS/SHARE servers and SAS Table Servers. For an explanation of each columns' contents, seeIntroduction to the Configuration File Reference.

Order of Precedence	Path and Filename	Purpose
1	Windows: \Lev1\server-name\sasv9.cfg UNIX and z/OS: /Lev1/server-name/sasv9.cfg	Specifies start-up options for the server and contains calls to the other files that are listed in this table. Do not modify this file. If you need to make changes, modify the sasv9_usermods.cfg file that is in the same directory.
2	Windows: \SAS-install-directory\SASFoundation\9.2\sasv9.cfg UNIX: /SAS-install-directory/SASFoundation/9.2/sasv9.cfg z/OS: Not applicable	Specifies system options that apply to all SAS sessions on the host machine.
3	Windows: \SAS-install-directory\SASFoundation\9.2\locale\sasv9.cfg UNIX: /SAS-install-directory/SASFoundation/9.2/locale/sasv9.cfg z/OS: <HLQ>.V92D8ddd.CNTLDSN(BATlocaleW0)	Specifies system options that apply to all SAS sessions on the host machine in the specified locale.
4	Windows: \Lev1\server-name\sasv9_usermods.cfg UNIX and z/OS: /Lev1/server-name/sasv9_usermods.cfg	Contains site-specific modifications to the server's startup options. Use this file to change the options that are specified in the sasv9.cfg file in the same directory. See theSAS/SHARE User's Guide.
5	Windows: \Lev1\server-name\autoexec.sas UNIX and z/OS: /Lev1/server-name/autoexec.sas	Contains SAS statements that are executed immediately after SAS initializes on the server. Do not modify this file. If you need to make changes, modify the autoexec_usermods.sas file that is in the same directory.
6	Windows: \Lev1\server-name\autoexec_usermods.sas UNIX and z/OS: /Lev1/server-name/autoexec_usermods.sas	Contains site-specific modifications to the autoexec.sas file that is located in the same directory.
Not applicable	Windows: \Lev1\sasv9_meta.cfg UNIX and z/OS: /Lev1/sasv9_meta.cfg	Specifies metadata server connection information for the SAS OLAP Server, SAS/SHARE server, and SAS Table Server.
Not applicable	Windows: \Lev1\server-name\logconfig.xml UNIX and z/OS: /Lev1/server-name/logconfig.xml	Specifies the logging configuration for the server. SeeAdministering Logging for SAS Servers.
Not applicable	Windows: Not applicable UNIX and z/OS: /Lev1/server-name/server-name.srv	On UNIX and z/OS, contains information that is used by generate_boot_scripts.sh to regenerate the sas.servers script.

In z/OS environments, the following additional configuration files affect SAS/SHARE servers and SAS Table Servers:

Order of Precedence	Path and Filename	Purpose
1	z/OS: <HLQ>.TKMVSENV(TKMVSENV)	Contains name/value pairs (environment variables) that apply to all SAS sessions on the machine.
2	z/OS: /Lev1/server-name/tkmvsenv.cfg	Contains name/value pairs (environment variables) for the server. Do not modify this file. If you need to make changes, modify the tkmvsenv_usermods.cfg file that is in the same directory.
3	z/OS: /Lev1/server-name/tkmvsenv_usermods.cfg	Contains site-specific modifications to the server's name/value pairs (environment variables). Use this file to change the options that are specified in the tkmvsenv.cfg file in the same directory. See the Configuration Guide for SAS 9.2 Foundation for z/OS.

Configuration Files for SAS Object Spawners and SAS/CONNECT Spawners

The following table shows the configuration files that affect SAS object spawners and SAS/CONNECT spawners. For an explanation of each columns' contents, see Introduction to the Configuration File Reference.

Order of Precedence	Path and Filename	Purpose
Not applicable	Windows: \Lev1\spawner-name\metaConfig.xml UNIX and z/OS: /Lev1/spawner-name/metaConfig.xml	Specifies metadata server connection information. The spawner must be stopped and restarted to pick up changes to this file.
Not applicable	Windows: \Lev1\ConnectSpawner\ConnectSpawner.bat UNIX: /Lev1/ConnectSpawner/ConnectSpawner.sh z/OS: Not applicable	Contains start-up options for the SAS/CONNECT spawner. See Communications Access Methods for SAS/CONNECT and SAS/SHARE.
Not applicable	Windows: \Lev1\ObjectSpawner\ObjectSpawner.bat UNIX: /Lev1/ObjectSpawner/ObjectSpawner.sh z/OS: Not applicable	Contains start-up options for the object spawner. See Spawner Invocation Options in the SAS Intelligence Platform: Application Server Administration Guide.
Not applicable	Windows: \Lev1\spawner-name\logconfig.xml UNIX and z/OS: /Lev1/spawner-name/logconfig.xml	Specifies the logging configuration for the spawner. SeeAdministering Logging for SAS Servers.
Not applicable	Windows: Not applicable UNIX and z/OS: /Lev1/server-name/server-name.srv	On UNIX and z/OS, contains information that is used by generate_boot_scripts.sh to regenerate the sas.servers script.

_____________________________________________________________________

Dan Strickland - SAS Platform Adminstrator -512.666.4546_IF/Reg1__________
Texas Parks and Wildlife Department, 3407 S Chadbourne, San Angelo, TX 76903 danwstrickland@gmail.com 

EG 5.1 project migration issue

Here is a hotfix for the issue I am having moving my EG 4.3 projects to EG 5.1.

http://support.sas.com/kb/46/192.html

_____________________________________________________________________

Dan Strickland - SAS Platform Adminstrator -512.666.4546_IF/Reg1__________
Texas Parks and Wildlife Department, 3407 S Chadbourne, San Angelo, TX 76903 danwstrickland@gmail.com 

Task Scheduler Issues

I found out that with the new security policy on Windows 7 users can't schedule task thru the task scheduler without getting admin rights first.  (As well as not being able to access their computer thru Remote Desktop Connection.)

I also found when running a scheduled task manually a taskeng.exe window pops up.  To prevent this from happening right click on the task in the task scheduler, select properties, click the actions tab, click edit, and in the "Add arguments" window insert "/NOCONSOLE" before the existing text.  You need to do this for each scheduled task and will need admin rights.

http://social.msdn.microsoft.com/Forums/en-US/isv/thread/3cf1f1c2-d839-46d7-831a-ab4fc6731774

_____________________________________________________________________

Dan Strickland - SAS Platform Adminstrator -512.666.4546_IF/Reg1__________
Texas Parks and Wildlife Department, 3407 S Chadbourne, San Angelo, TX 76903 danwstrickland@gmail.com 

Computing distances between coordiantes in SAS

http://www.sascommunity.org/wiki/Driving_Distances_and_Drive_Times_using_SAS_and_Google_Maps

Calculating the last day of the month one year forward from a date

FYI -- Here's some code that calculates the Expiration dates for the

Year-from-date license (which expires the last day of the month, one
year forward from date of purchase), as well as the rest of the
licenses:

case
when t1.ITEM = 237 then intnx('month', (t1.Date_of_purchase + 365), 0,
'e')
else mdy(8,31,2012)
end

*************************************************************************************

Updated.  Realized that the inside intnx sends it to the end of the month, but for years before a leap year, that's Feb 28^th, so I needed to wrap everything in another intnx to force it to go to the 29^th in the case of a leap year.

The innermost intnx takes the license date and sends it to the end of the current month. The next intnx then updates the year by 1.  The outermost intnx pushes it to the final day of the current month, and is only useful during February of a leap year.

data test;

input date_of_purchase mmddyy10.;

datalines;

02-01-2003

;

run;

data new;

set test;

format date_of_purchase mmddyy10. lic_end mmddyy10.;

lic_end=intnx('month',(intnx('year',(intnx('month', (Date_of_purchase), 0, 'e')),1,'s')),0,'e');

run;

SAS Add-ins 4.3 Turning on the log

To turn on the SAS Add-in for Microsoft Office logging facility:

http://support.sas.com/kb/31217. Install the attached file in C:\Program
Files\SAS\Add-InForMicrosoftOffice\4.3

Open Excel and replicate the problem, the log text file is generated.

_____________________________________________________________________

Dan Strickland - SAS Platform Adminstrator -512.666.4546_IF/Reg1__________
Texas Parks and Wildlife Department, 3407 S Chadbourne, San Angelo, TX 76903 danwstrickland@gmail.com 

Enterprise Guide Installation 32 and 64 bit note

http://support.sas.com/kb/41/277.html

IMPORTANT NOTE: If you need to install both a SAS 9.3 32-bit and a SAS 9.3 x64 order on the same machine; make sure you install the x64 order first. For more details, see Installation Note 44168.

The opposite is true for a SAS 9.2 installation; you need to install the 32-bit order first and then the x64 order.

_____________________________________________________________________

Dan Strickland - SAS Platform Adminstrator -512.666.4546_IF/Reg1__________
Texas Parks and Wildlife Department, 3407 S Chadbourne, San Angelo, TX 76903 danwstrickland@gmail.com