BookmarkSubscribeRSS Feed
IU
Fluorite | Level 6 IU
Fluorite | Level 6

I am using SASGSUB in MS Windows batch files to submit SAS code to the SAS Grid.

The batch script code for SAS 9.2 is shown below. The customized config file, sasgsub92.cfg, is located in  C:\Users\%username%\SASGrid.

The default SAS WORK data library location assigned to a SAS session created by this submit is WORK= C:\Users\%username%\<_TD…..>

What option should be used to change the default SAS WORK data library location (C:\Users\%username%)  to another path?  

SET RunSAS="C:\Program Files\SAS\SASFoundation\9.2\sasgsub.exe" -gridconfig "C:\Users\%username%\SASGrid\sasgsub92.cfg" -metauser %username%
%RunSAS% -gridsubmitpgm "%mypath%%pgm%" -gridsasopts " -log '%mylog%.log' -print '%mylst%.lst'"

 

 Thanks,

IU

4 REPLIES 4
owagner
Calcite | Level 5
You can use a libname statement like
libname work "<pathname>";

But don't forget: then the work library is permanent!

Regstes, Olaf
https://www.youracclaim.com/user/olaf-wagner
LinusH
Tourmaline | Level 20
-work
Data never sleeps
IU
Fluorite | Level 6 IU
Fluorite | Level 6

Yes, LinusH:

 "-work" is the option I am trying to use.

But it does not work in the sasgsub config file (sasgsub92.cfg in my example):  

-GRIDSASOPTS  "-work \\servername\...."

It works in the sasgsub.exe command line:

-gridsasopts " -work \\servername\...<other SAS options>."  

Is there any way to tell the sasgsub.exe  command to use the "-work" option from the sasgsub config file?

 

Thanks,

-IU

Ksharp
Super User

Add option at the top of your code.

 

options user='c:\temp\';

suga badge.PNGThe SAS Users Group for Administrators (SUGA) is open to all SAS administrators and architects who install, update, manage or maintain a SAS deployment. 

Join SUGA 

Get Started with SAS Information Catalog in SAS Viya

SAS technical trainer Erin Winters shows you how to explore assets, create new data discovery agents, schedule data discovery agents, and much more.

Find more tutorials on the SAS Users YouTube channel.

Discussion stats
  • 4 replies
  • 2043 views
  • 0 likes
  • 4 in conversation