Additional Profile Settings
SAS Options Settings Examples
SAS system options can be set for each connection profile. Changes to the SAS system options do not take effect until you close and restart your SAS session. See the following examples of the required formats for the supported connection profile types.
-
SAS Viya:
{
"profiles": {
"viya4": {
"endpoint": "https://example-endpoint.com",
"connectionType": "rest",
"sasOptions": ["NONEWS", "ECHOAUTO", "PAGESIZE=MAX"]
}
}
} -
SAS 9.4 (remote - IOM):
{
"profiles": {
"sas9IOM": {
"host": "host",
"username": "username",
"port": 8591,
"sasOptions": ["NONEWS", "ECHOAUTO", "PAGESIZE=MAX"],
"ConnectionType": "iom"
}
}
} -
SAS 9.4 (local):
{
"profiles": {
"sas9COM": {
"host": "localhost",
"sasOptions": ["NONEWS", "ECHOAUTO", "PAGESIZE=MAX"],
"ConnectionType": "com"
}
}
} -
SAS 9 (remote - SSH):
{
"profiles": {
"SAS9SSH": {
"host": "hostname",
"username": "username",
"port": 22,
"sasPath": "/remote/path/to/sas_u8",
"sasOptions": ["-NONEWS", "-ECHOAUTO", "-PAGESIZE MAX"],
"connectionType": "ssh"
}
}
}
SAS Autoexec Settings
For SAS Viya connection profiles, you can set up autoexec code that executes each time you start a new session. Changes to the autoexec code do not take effect until you close and restart your SAS session. The Autoexec option supports different modes for how to define the SAS lines that should run:
-
Line Mode: embed lines directly into the connection profile JSON. This mode is useful if only a few lines are needed to run on session startup. Note that standard JSON escaping rules apply.
"SAS.connectionProfiles": {
"activeProfile": "viyaServer",
"profiles": {
"viya4": {
"endpoint": "https://example-endpoint.com",
"connectionType": "rest",
"autoExec": [
{
"type": "line",
"line": "ods graphics / imagemap;"
}
]
}
}
} -
File Mode: specify a path to a file containing autoexec lines to execute. The file must be in a location that is readable by the extension. This mode is useful for complex autoexec scenarios:
"SAS.connectionProfiles": {
"activeProfile": "viyaServer",
"profiles": {
"viya4": {
"endpoint": "https://example-endpoint.com",
"connectionType": "rest",
"autoExec": [
{
"type": "file",
"filePath": "/my/local/autoexec.sas"
}
]
}
}
} -
Mixed Mode: The autoexec option supports an array of entries, so it is possible to use a combination of both embedded lines and files. The lines will be read in sequential order as they occur in the array itself.
"SAS.connectionProfiles": {
"activeProfile": "viyaServer",
"profiles": {
"viya4": {
"endpoint": "https://example-endpoint.com",
"connectionType": "rest",
"autoExec": [
{
"type": "line",
"line": "ods graphics / imagemap;"
},
{
"type": "file",
"filePath": "/my/local/autoexec.sas"
}
]
}
}
}
SAS Interop Library Settings
SAS Interop library settings can be configured for ITC-based connections ("remote - IOM" and "local" connection types). ITC-based connections have a dependency on SASInterop.dll
and SASOManInterop.dll
. The extension tries to load these libraries from the following locations (ordered by priority):
- The path specified in
interopLibraryFolderPath
. This should be an absolute path to the folder containing the files listed above. - If
interopLibraryFolderPath
is empty or invalid, the extension will attempt to resolve the path from Windows registry - If steps 1 and 2 fail, the extension will attempt to load libraries from the default Integration Technologies Client folder (
C:\Program Files\SASHome\x86\Integration Technologies
)
The following demonstrates how to setup interopLibraryFolderPath
in user settings:
-
SAS 9.4 (remote - IOM):
{
"profiles": {
"sas9IOM": {
"host": "host",
"username": "username",
"port": 8591,
"ConnectionType": "iom",
"interopLibraryFolderPath": "C:\\Program Files\\SASHome\\x86\\Integration Technologies"
}
}
} -
SAS 9.4 (local):
{
"profiles": {
"sas9COM": {
"host": "localhost",
"ConnectionType": "com",
"interopLibraryFolderPath": "C:\\Program Files\\SASHome\\x86\\Integration Technologies"
}
}
}