topic Re: sasv9 config parameter in Administration and Deployment

sasv9 config parameter

freshstarter — Tue, 10 Dec 2024 18:40:10 GMT

Hello,

We have defined datestyle setting as 'MDY' in sasv9_usermods.cfg under /sas/config/Lev1/SASApp. We do have two server i.e. Workspace server and Batch server under the SASApp directory

/sas/config/Lev1/SASApp/WorkspaceServer

/sas/config/Lev1/SASApp/BatchServer

My understanding is that datestyle setting defined in the top level config file (/sas/config/Lev1/SASApp/sasv9_usermods.cfg) will automatically drilled down to Workspace server and Batch server. But I see different results in both.

I have launced workspace server session and trigerred

proc options option=datestyle value;run;

From the log, I got as below

SAS(r) Proprietary Software Release 9.4 TS1M7

Option Value Information for SAS Option DATESTYLE

Value : MDY

Scope : SAS Session

How option Value Set : Config Value

Config File name : /sas/config/Lev1/SASApp/sasv9_usermods.cfg

I have launced Batch server session and trigerred

proc options option=datestyle value;run;

From the log, I got as below

SAS(r) Proprietary Software Release 9.4 TS1M7

Option Value Information for SAS Option DATESTYLE

Value : DMY

Scope : Default

How option Value Set : Locale

I assume datestyle option on the batch server is considered from the locale setting of the linux server ( where we installed SAS ). I cross verfied all the config file under Batch server and dont see anywhere we have defined this datestyle option. So not sure why it is considered from locale.

Please do let me know if you have answer. Thanks.

Re: sasv9 config parameter

gwootton — Wed, 11 Dec 2024 21:10:28 GMT

I wasn't able to reproduce this in my M7 environment. Is the config file /sas/config/Lev1/SASApp/sasv9_usermods.cfg present in your config path in the batch server?
%put %sysget(SASCFGPATH);
proc option option=config; run;

Re: sasv9 config parameter

freshstarter — Thu, 12 Dec 2024 09:08:25 GMT

Thank you @gwootton for your response.

The output of the code from the batch server didnot give me this path and the workspace server does.

/sas/config/Lev1/SASApp/sasv9_usermods.cfg

Thats the reason I think thats the difference in proc option output.

I have to edit my sasbatch.sh script to include in path under SASCFGPATH variable.

Thank you so much.

Re: sasv9 config parameter

Kurt_Bremser — Thu, 12 Dec 2024 11:12:30 GMT

Tips from a seasoned SAS 9.4 admin:

do not use SASApp for your server context, create a new one and adapt it to your needs; keep SASApp as the original blueprint for future reference
never make edits to sasbatch.sh or similar scripts/configs; always make your edits in the respecive "usermods" extension files. The usermods files will not be overwritten during updates, the main files will be.

Re: sasv9 config parameter

freshstarter — Thu, 12 Dec 2024 14:08:16 GMT

Thank you

Re: sasv9 config parameter

gwootton — Mon, 16 Dec 2024 14:17:01 GMT

The sasbatch.sh script should have the path present, so I would suspect it was edited in the past and this was removed. The below output is from my environment's BatchServer directory:

$ grep SASCFGPATH sasbatch.sh
SASCFGPATH="/opt/sas/config/Lev1/SASApp/sasv9.cfg, /opt/sas/config/Lev1/SASApp/sasv9_usermods.cfg, /opt/sas/config/Lev1/SASApp/BatchServer/sasv9.cfg, /opt/sas/config/Lev1/SASApp/BatchServer/sasv9_usermods.cfg"
export SASCFGPATH