DSXchange

According to the Ops Console's Workload Management tab, by default there are 3 batch queues for jobs (Low, Medium, and High), and dedicated queues for ISD, IA, and DataClick.

Today we have deployed a new ISD application that is based on a DataStage job, and instead of running, it was Queued in the ISD queue. This seems to have happened because several IA tasks were already running and CPU usage was too high, and there was a very long wait for IA tasks to finish and reduce CPU to below the global threshold of 80%.

Are there any options to give ISD priority over IA, or over anything else for that matter?

Basically by tweaking (balancing) the CPU and memory limits for each of the queues. Allow ISD queue to start jobs even though CPU/memory might be 100%, but don't allow this for the other queues.
You may also be able to fiddle with the maximum jobs setting.

There are a lot of sites who recognize the unique pattern and needs of ISD Jobs vis-a-vis regular batch Jobs, and they deploy a whole separate engine for ISD Jobs.

Ernie

Thank you both for sharing! We will look into both options.

By default, the IA queue and the ISD queue are each set to Medium priority and 100 maximum running jobs.

The ISD queue is locked down from making any changes, however the IA queue allowed some changes to made and saved.