Server Startup Command

• on the server startup command-line
• in the sasCommand attribute of the metadata server definition.

Note: Server parameters that are specified on the command line override parameters that are specified in the server metadata.

In the server command, you can provide the following information:

• SAS configuration file (required). To initialize SAS options, you must specify a SAS configuration file using the -config option on the server command line. For example,

  C:\Program Files\SAS\SAS 9.1\sas.exe 
     -config "C:\Program Files\SAS\SAS 9.1\sasv9.cfg"
  

  The SAS Configuration file contains SAS options that are automatically executed when the SAS System is invoked. The default configuration is located in the SAS install directory; you can also create your own configuration file.

• SAS Autoexec File (optional). To preassign server settings, specify a SAS autoexec file using the -autoexec option on the server command line. For example,

  C:\Program Files\SAS\SAS 9.1\sas.exe 
     -autoexec "C:\Program Files\SAS\SAS 9.1\autoexec.sas"
  

  A SAS autoexec file contains SAS statements that are executed as part of the SAS invocation. SAS autoexec files are particularly useful for pre-assigning librefs, filerefs, and macros. When multiple workspaces are used on the same server, each workspace inherits the server properties that are set by the autoexec file. Individual workspaces can override the properties that are inherited from the server by specifying new LIBNAME, FILENAME, or macro statements--however, these changes only affect the workspace where the new statements are submitted.

  Note:Workspaces do not inherit the server WORK library that is used during autoexec processing.

  To use a single autoexec file for both SAS sessions and IOM servers, you can set up conditional statements in your autoexec file. For example,

  %macro autsetup;
  %if %sysfunc(getoption(objectserver))=OBJECTSERVER
   %then
    %do;
        <IOM server autoexec statements>
    %end;
  %else
   %do;
       <SAS session autoexec statements>
   %end;
  %mend autsetup;
  %autsetup;
  

  Important: For some SAS 9.1 hosts, IOM servers process a SAS autoexec file implicitly if the file is stored in the default location. This might cause compatibility issues for existing configurations because IOM servers did not process autoexec files in previous versions of SAS. You can suppress this behavior by specifying -noautoexec in the server command.

  For more information about the -AUTOEXEC system option, see the SAS documentation for your operating environment.

• Logging Options (optional). To diagnose server problems, specify the -log and -logparm logging options on the server command line. You specify the logging options in the Command field or Object Server Parameters field of the server definition.

  For details about object server parameters, see Object Server Parameters. When you specify the logging options, you can also configure the server to create a different log for each process, or switch logs during execution.

  The following command (specified in the Command field creates a unique log file (in the server user's home directory) for each instance of this server definition.

  C:\Program Files\SAS\SAS 9.1\sas.exe  -log "test%v.log" 
     -logparm "rollover=session"
  

  For example, when the spawner starts the first server, a log named test1.log is created; when the spawner starts the second server, a log named test2.log is created.

  For information about system logging options, see SAS Language Reference: Dictionary.

  Note: Specifying logging options can cause performance degradation in your server; therefore, you should only specify logging options to diagnose problems with your server connections.

  Note: If you specify a log destination in the configuration metadata rather than the startup command, you might miss some messages that are generated before the log destination is set.