BookmarkSubscribeRSS Feed
Quartz | Level 8 LB
Quartz | Level 8

Within SAS Grid -Is there a way to name EACH job submitted to the GRID per se- I know I can name the overall job but many times I have components that I would like to get an understanding for which ones are fast/slow/failing- 



i.e. I would like to have the GRID apply the job name VDW1 vs GRID_JOB:98790 or whatever the current sequence is: 

signon VDW1 ;
rsubmit VDW1 wait=no;







Lapis Lazuli | Level 10

The JOBOPTS= option of the GRDSVC_ENABLE function has a sub-option named JOBNAME that lets you set the jobnames of submitted jobs.  You give it the name of a macro variable, and before you start a new session with SIGNON you set the value of the macro variable to the name you want to use.  If you're submitting your job with the sasgsub command, you can specify the name using the -gridjobname option .


Like so many things in grid processing, how to do this in code is poorly or obscurely documented.  I wonder if the designers were trying to increase the need for buying SAS consulting services, or if they simply realized that there was no need to bother with good documentation because SAS Viya would provide an alternative in many cases.  SAS has dropped previously supported functionality in the High Performance procs and told us to license Viya instead, so I lean towards the "no need to bother because it's going away" hypothesis.

There's some documentation at






The SAS online training probably does a better job of explaining how to use functions and statements to control grid processing.

There's an example with working code at

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 

Discussion stats
  • 1 reply
  • 2 in conversation