/tmp Storage used for joining and sorting

[shrikantpwc]

Hi Team,

Few of my jobs are getting failed due to insufficient storage, my work file location having sufficient space. /tmp/ getting utilised by job for sorting and joining. 

my question is can we change the location of this sorting and joining location permentalty.

Thanks

-shrikant Suvarnkar

[yabwon]

HI,

I think you could use the USER library idea:

libname USER ("%sysfunc(pathname(work))" "/temp/");

It allow you to write codes like:

data OUTPUT;
  set sashelp.class;
run;

and the OUTPUT dataset will be stored in the USER library, so you don't have to change your code to much if you' were using "single name dataset"(i.e. without work. before dataset name)  to store data in WORK.

But you have to remember that you have to clean USER up yourself after SAS session ends.

All the best

Bart

[shrikantpwc]

Thanks,

Can we perform this in SAS DI. By default Sort and join operation area is /tmp, and I want it to change to any other directory location.

[Kurt_Bremser]

You need to set UTILLOC in the sasv9_usermods.cfg file of the server context that DI uses (e.g. in the SASApp directory, not in SASApp/WorkspaceServer).

[yabwon]

Other approach would be to change the UTILLOC= System Option, see: https://documentation.sas.com/?docsetId=lesysoptsref&docsetTarget=p1texr4rxo0ipyn1ovajj11raccx.htm&d...

But it is Configuration file/SAS invocation option so

 -you will need admin help if you work with EG or

 -if you could work with command line interface you could do it yourself.

Bart

[AhmedAl_Attar]

The default setting for the WORK library on Linux is /tmp. You can double check that setting by running the following statement in Code Editor from within SAS Data Integration Studio. Tools --> Code Editor

%put %sysfunc(pathname(work));

The result will be placed in the log tab.

To get around this issue, there are few options

1. Ask your SAS Administrator to redirect/change the -WORK setting to point to a different more sizable directory/file-system, by modifying the <SASHome>/SASFoundation/9.4/sasv9_local.cfg file
2. Create your own custom sasv9.cfg file and save it in your own $HOME directory on the Linux Compute Server(s)

Hope this helps,

Ahmed  

[TomKari · Accepted solution]

SAS DI is meant to be a managed environment for running production jobs. If you're having storage issues, you should discuss it with your SAS administrators to ensure changes are made to the environment to prevent these problems from happening.

Tom