DSXchange: DataStage and IBM Websphere Data Integration Forum
View next topic
View previous topic
Add To Favorites
Author Message
ray.wurlod

Premium Poster
Participant

Group memberships:
Premium Members, Inner Circle, Australia Usergroup, Server to Parallel Transition Group

Joined: 23 Oct 2002
Posts: 54546
Location: Sydney, Australia
Points: 295766

Post Posted: Mon Dec 15, 2014 6:50 pm Reply with quote    Back to top    

Workload management queues (version 9.1 and later) are defined globally in an Information Server engine. Anyone submitting a DataStage job run request may request that the job be submitted to any queue on the system. A project may have a default queue defined, but that does not submit a canny user from learning that a high priority queue exists.

To that end, I would like to see a three-pronged approach to controlling who can use queues.

(1) an administrator can block a queue - no more jobs can be submitted to this queue (except by an administrator) - this can give an over-used queue the chance to drain

(2) only the queues mentioned in a project can be used by jobs submitted for that project

(3) a mechanism (probably role-driven) be implemented to specify in the queue definition who is permitted to submit jobs to it

_________________
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
ray.wurlod

Premium Poster
Participant

Group memberships:
Premium Members, Inner Circle, Australia Usergroup, Server to Parallel Transition Group

Joined: 23 Oct 2002
Posts: 54546
Location: Sydney, Australia
Points: 295766

Post Posted: Mon Dec 15, 2014 7:05 pm Reply with quote    Back to top    

I have submitted a formal request for enhancement.

Did you know that there is a new mechanism for this - you don't need to open a support case?

_________________
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Rate this response:  
Not yet rated
qt_ky



Group memberships:
Premium Members

Joined: 03 Aug 2011
Posts: 2878
Location: USA
Points: 21847

Post Posted: Mon Dec 15, 2014 10:58 pm Reply with quote    Back to top    

I voted for it. I also added a comment on that site, but something went wrong and I lost the first part about "circumventing the WLM at the queue level."

"Administrators need control over which queues are accessible and visible for various projects/users/groups to select when running jobs from the GUIs or the command line."

As far as blocking a queue, I think it may be nice to have. An admin should already be able to move jobs from one queue to another to clean out a given queue. A sequence calling hundreds of jobs could continue to drop those in the same queue. If that queue were blocked in the midst of such a run, then add the remaining jobs to the default queue?

_________________
Choose a job you love, and you will never have to work a day in your life. - Confucius
Rate this response:  
Not yet rated
Display posts from previous:       

Add To Favorites
View next topic
View previous topic
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum



Powered by phpBB © 2001, 2002 phpBB Group
Theme & Graphics by Daz :: Portal by Smartor
All times are GMT - 6 Hours