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.
Availability: 0
MaximumAvailability: 1
Used: 0
Reserved: 0
Needed: 1
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.
If you are using the javascript method "resetResourceProperty", the following tools will not help determine what is using that resource:
If you're using an Alert -> Javascript to execute the resetResourceProperty then you can track down which applications use that alert using a command similar to the following:
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.