We noticed this behavior when we send an event:
sendevent -E FORCE_STARTJOB -J DUMMY
Job DUMMY uses a resource definition such as :
If at same time the resource is used by another job, the job cannot run even if a FORCE_STARTJOB event is sent
Job will remain in RW status. (Resource Wait)
This is working as designed.
If you send a FORCE_STARTJOB event to a job that has a status of RESWAIT, the FORCE_STARTJOB event is ignored and the job remains in the RESWAIT status.
You can remove or alter the resource requirements of the job so the job is no longer in RESWAIT and can be started.