SAS Model Manager compute server sessions can run with the current working directory set to the user's home directory. For example, exporting a model or obtaining the DS2 scoring code for a model can create files in the user's home directory. The user directory might have files named similar to the following:

• ds2cd.sas
• ds2pkg.sas
• Formats.txt
• Generic.txt
• XML.txt

If the user is running concurrent SAS Model Manager requests or using SAS^® Event Stream Manager to run a SAS^® Event Stream Processing project with multiple analytical models, incorrect results might be returned.

The SAS Model Manager compute server sessions should create and use a working directory unique to the compute server session. When a tenant is onboarded, the /opt/sas/spre/home/bin/tenant_setup_launcher.sh script does not set the correct access control list for the /opt/sas/<tenant_id>/config/var/run directory. A setfacl command is missing for the /opt/sas/<tenant_id>/config/var/run directory. 

To circumvent this issue, run the setfacl command to add the tenant users group to the /opt/sas/<tenant_id>/config/var/run directory:

In the code above, tenant_users_group and sas_tenant are the values from the <tenantID>_vars.yml file that was used when the tenant was onboarded.