More jobs are executing than the DQM limit allows
Document ID : KB000091859
Last Modified Date : 01/02/2019
 Show Technical Document Details
Issue:
The DQM job limit is used to limit the number of jobs executing in parallel.
In some cases, the number of job executions in parallel exceeds the set limit, for example 2 executions instead of 1. 

Another symptom is that the counters displayed for JobExe and JobPend are wrong ( displaying -1 for JobExe).

If this is the case, the number of executions in UVC> Monitoring > Batch Queue Status, in the column "Pending" displays 1 instead of 0 when no Jobs are queued.

IMPORTANT: When no jobs are executing in the queue, the number in the column "Running" shows -1 (minus one) . 
Or, in the command line the command "uxlstque or uxshwque queue=<queue_name> full" show -1 in the column JOBEXE.

Example:
In the command line uxshwque, we can observe the issue ( counter -1): 

user@server:/automic/DUAS/node/bin#./uxshwque queue=SYS_BATCH
Queue SYS_BATCH
      JobLim 150
      JobQue 0 , JobExe -1 , JobHld 0 , JobPend 1

user@server:/automic/DUAS/node/bin#./uxlstque queue=SYS_BATCH

QUEUE NAME                      TYPE STA  JOBLIM  JOBQUE  JOBEXE  JOBHLD JOBPEND
--------------------------------------------------------------------------------
SYS_BATCH                       PHYS ON      150       0      -1       0       1

In UVC - Batch Queues Status, the counter Pending displays 1:
UVC - Batch Queues Status

In UVC - Queued Jobs, no Pending Jobs are displayed :
UVC - Queued Jobs

Another symptom is that the counter JobPend displays a wrong (higher) value.
 
Environment:
Dollar Universe 6 node using DQM Job Limits.
Cause:
A problem has been fixed where DQM queue counters are wrong (executing is -1 or pending wrongly high) if job terminations and job submissions occur at the same time.
Resolution:
As a workaround, reinitialize the affected DQM queue/s. 

1. In the command line execute the following command after having loaded the Dollar Universe environment:
uxresetque queue=<queue_name> 


In order to avoid the issue from happening again, increase the "DQM send cycle" value on the node where the Logical queue resides: 
Node Settings - DQM Settings:

DQM send cycle  ->  120 -> increase to 360

Save and restart the node to take into account the modifications.


Solution: Update to a fix version listed below or a newer version if available.

Fix version(s): 
Component: Application.Server
Dollar Universe 6.10.01 - Should be available around May 2019