Modifying Configuration Files or SAS Start Commands for Application Servers

There are several ways to customize the environment where the code generated by SAS Data Integration Studio runs. When you submit a SAS Data Integration Studio job for execution, it is submitted to a SAS Workspace Server component of the relevant SAS Application Server. The relevant SAS Application Server is one of the following:
  • the default server that is specified on the SAS Server tab in the Options window
  • the SAS Application Server to which a job is deployed with the Deploy for Scheduling option
To set SAS invocation options for all SAS Data Integration Studio jobs that are executed by a particular SAS server, specify the options in the configuration files for the relevant SAS Workspace Servers, batch or scheduling servers, and grid servers. (You do not set these options on SAS Metadata Servers or SAS Stored Process Servers.) Examples of these options include UTILLOC, NOWORKINIT, or ETLS_DEBUG.
To specify SAS system options or startup options for all jobs that are executed on a particular SAS Workspace Server, modify one of the following for the server:
  • config.sas file
  • autoexec.sas file
  • SAS start command
For example, your SAS logs have become too large and you want to suppress the MPRINT option in your production environment. Perform the following steps to invoke the ETLS_DEBUG option in the autoexec.sas:
  1. Open the autoexec.sas file.
  2. Add the following code to the autoexec.sas file for your production run:
    %let etls_debug=0;
  3. Save and close the file.
Note: If the condition etls_debug=0 is true, then the logic in the deployed job prevents execution of the OPTIONS MPRINT; statement. To turn on the MPRINT option again, remove %let etls_debug=0; from the autoexec.sas file.
CAUTION:
It is strongly recommended that you do not turn off MPRINT in a development environment.
Last updated: January 16, 2018