BookmarkSubscribeRSS Feed
Jovian
Obsidian | Level 7

Hi everyone, 

 

I am currently trying to setup a queue in SAS Viya 4 where these rules are followed 

 

  • From 10 AM - 2 PM no jobs should be executed by the user "demo1"
  • From 6PM - 11:59AM jobs from user "demo1" takes priority.

 

Currently I have only a single compute node, so the host type does not matter.

 

I have attached below the screenshots with the queue and the rules i have created. 

Default time based setting in my queue

Jovian_0-1763115169523.png

time override named business 

Jovian_2-1763115319186.png

and its rules

 

Jovian_1-1763115287053.png

 

time override named no-execute

Jovian_4-1763120791147.png

and its rules

Jovian_3-1763120773062.png

I have also added the queues in EVM -> context 

Jovian_5-1763120880895.png

 

If there is any updated documentation, link or videos, it will be mighty helpful. 

My viya 4 is LTS 2025.03

 

Thanks everyone.

1 REPLY 1
gwootton
SAS Super FREQ
The configuration shown in these screen shots is:
1. Queue has a default configuration (i.e. when no time-based configuration is valid) such that it is only accessible to use demo1 who is also an administrator of the queue, and it is the default queue. The job priority for the queue is 10.
2. Queue has a time-based configuration "no-execute" effective from 15:30 - 15:50 where the priority is set to 50 but maximum jobs is set to 0, so no jobs would be accepted. An override is set to override the default users configuration but the setting is the same as the default (demo1). The queue is not the default queue at this time.
3. Queue has a time-based configuration "business" effective from 16:30 - 16:35 that adds a maximum job limit of 10 total, and 3 jobs per user, and the priority is adjusted to 30. It is set to override the default values for users and administrators but these values are the same (demo1). The queue is the default queue a this time.
4. The Job Execution compute context has been configured to use a queue named "business" (it is not clear from the screenshots that the name of the queue you are modifying is "business").

Your requirement description has a time overlap from 10 AM to 11:59 AM where jobs both take priority and cannot be executed:

From 10 AM - 2 PM no jobs should be executed by the user "demo1"
From 6PM - 11:59AM jobs from user "demo1" takes priority.

There can only be one default queue, and that is the queue where all jobs without a queue specified in the request will be sent.

You can configure launcher and compute contexts to specify a queue to override the default.

So, I think on the SWO side you want to create a separate queue from default for demo1, and in contexts define a context for demo1 to make use of that queue and perhaps disallow them from using any other context using authorization rules, as they could otherwise select a context without a queue defined and not have the applied configuration in place.

Then, I think your queue definition should be:

Default: Priorty 10, Users: demo1
No-Execute: Start: 0 10 * * * / End: 0 14 * * *, Maximum jobs: 0
Priority: Start: 0 18 * * * / End: 59 23 * * *, Priority: 20
--
Greg Wootton | Principal Systems Technical Support Engineer

sas-innovate-2026-white.png



April 27 – 30 | Gaylord Texan | Grapevine, Texas

Registration is open

Walk in ready to learn. Walk out ready to deliver. This is the data and AI conference you can't afford to miss.
Register now and lock in 2025 pricing—just $495!

Register now

Discussion stats
  • 1 reply
  • 315 views
  • 0 likes
  • 2 in conversation