Best Practices and How-to for Administration of SLC Servers on Linux - Part 4 of 5
Results from Autoexec Processing
Using the example AUTOEXEC.sas we configured, we get:
NOTE: Copyright 2002-2025 World Programming, an Altair Company NOTE: Altair SLC 2026 EA1 (05.26.00.01.000433)Licensed to AltairNOTE: This session is executing on the LINUX platform and is running in 64 bit modeNOTE: AUTOEXEC processing beginning; file is/opt/slc_autocall/autoexec.sasNOTE: ================================================================NOTE: SLC Custom Configuration Loaded SuccessfullyNOTE: ================================================================NOTE: User: trbNOTE: Date: 24AUG2025 NOTE: Time: 10:57:14NOTE: Session:24AUG2025:10:57:14NOTE: Current Directory: /home/trb NOTE:NOTE: Environment Configuration:NOTE:PROJECT_ROOT = /home/trb/projects NOTE:LOG_DIR = /var/log/slcNOTE:CONFIG_DIR = /etc/slc/authd NOTE:NOTE: Autocall Library: /opt/slc_autocall NOTE:â BigQuery connection macro available NOTE:â Hello welcome macro availableNOTE: ================================================================NOTE: ================================================================NOTE: Welcome to SLC, trb!NOTE: Current directory: /home/trbNOTE: Available custom macros in /opt/slc_autocallNOTE: ================================================================NOTE: BigQuery Connection Examples:NOTE:NOTE: Positional parameter:NOTE:%slc_connect_to_bq_libname(/home/trb/.gcp/bigquery-service- account.json)NOTE: Named parameter:NOTE:%slc_connect_to_bq_libname(credpath=/home/trb/.gcp/bigquery- service-account.json)NOTE: Environment variable (set BIGQUERY_OAUTH_TOKEN first): NOTE:%slc_connect_to_bq_libname()
Autoexec Processing Validation
Test AUTOEXEC processing is error-free by executing the following program in an SLC session:
/* In SLC, run this to verify the autoexec is configured */ proc options option=autoexec;run;
In our case, this returns:
20proc options option=sasautos;21run;SASAUTOS=("/opt/slc_autocall" sasautos) Search list for autocall macros
Look for your custom AUTOEXEC messages in the SAS log when starting SLC. Verify file exists in expected location, for example, in your home directory
ls -la ~/autoexec.sas
For batch processing, the SLC command-line command option -autoexec is used to ensure autoexec processing is performed. For example:
wps -sysin run_slc.sas -autoexec /opt/slc_autocall/autoexec.sas
Return the location of the AUTOEXEC.sas file location on the file system by executing the following SLC program:
/* In SLC, run this to verify the autoexec file location // Return the current autoexec.sas file path */%put AUTOEXEC: %sysfunc(getoption(autoexec));
For debugging autoexec processing, you can use the %INCLUDE statement, like:
/* Run autoexec code manually to find errors */%include "~/autoexec.sas";
Autoexec Processing Summary:
User vs System autoexec:
- User autoexec: ~/autoexec.sas (recommended for individual customization)
- System autoexec: /etc/slc/autoexec.sas (for organization-wide settings)
