The batch jobs are struck as the Stay on RESWAIT - the renewable resource is not used. Using the List Resource Usage shows:
The resource is active.
1 needed by WAITFORRESOURCE.JOB_NAME
Release : 12.3
Having an Availability value of 0 effectively disables the resource. This makes it so that nothing can use the resource. You need an Availability of at least 1. If you want to make 1 available you can do this by:
If you want to make 1 available you can do this by:
Alternatively, you can use the drop resource feature to temporarily suspend it's dependency on the resource and execute the job.
grep -Po 'DM.Appl.*Alert: (<YOUR_OFF_ALERT_NAME>|<YOUR_ON_ALERT_NAME>)' tracelog*
where < and > are not included in the command and the values between those characters are replaced with your alert names.