Error Message :
N/A

When using multiple single run jobs with a Before Change Q condition to switch to a given queue, an issue can occur where jobs become stuck in a QUEUE WAIT status.

When a specific queue reaches its maximum job value, no further jobs will be able to go into a RUNNING status.  

All newly submitted jobs to the specific queue go to a QUEUE WAIT status.

To resume processing on the queue the RmiServer process must be restarted.

The issue has been identified as known issue in Application Manager 9.1.1 and Application Manager 8.0.17.

Reference

Cause type:
Defect
Root Cause: Jobs would become stuck in Queue Wait and the Queue had reached its thread limit. This would occur when using multiple single run jobs with Before Change Q conditions to switch to a given queue.

Release: AAMOS499000-8.0-Automic Applications Manager-OS400 Agent
Component:

This field was added on 30/03/2017. This article has not been updated yet. Refer to the "Description" or "Workaround" sections for solution information.

Fix Status: Released

Fix Version(s):
Applications Manager 9.1.2 - Available
Applications Manager 8.0 - Will not be fixed

Workaround :
Stop and restart the RmiServer process to resume processing. This can be done from the command line as following.1) Log into the Application Manager Master server as the OS user.2) Navigate to $AW_HOME/site and invoke the sosite environment.3) Next issue the "stopso rmi" command.4) Wait for the stop script to complete.5) Next issue the "startso rmi" command.6) Wait for the start script to complete.7) Log into the GUI and confirm processing on the Queue has resumed.