RTM: hosts unreachable for scheduling constraints

when an exec server is not eligible for a scheduling constrainte ("just starting a job recently" for ex), there nothing to monitor that situation.

the only way is to detect that situation is to do a bjobs -lp on a pending job pending for that reason,

Another way, to monitor number od hosts, is to perform a complex and hazardous mysql request in RTM DB:
SELECT CASE WHEN ( pendreasons LIKE '%Just started a job recently: %' ) THEN
MIN(CONVERT(SUBSTRING_INDEX(SUBSTRING(pendreasons, INSTR(pendreasons, 'Just started a job recently: ') + 29, 10), ' ', 1),UNSIGNED)) ELSE 0 END AS MinHosts,
CASE WHEN ( pendreasons LIKE '%Just started a job recently: %' ) THEN
ROUND(AVG(CONVERT(SUBSTRING_INDEX(SUBSTRING(pendreasons, INSTR(pendreasons, 'Just started a job recently: ') + 29, 10), ' ', 1),UNSIGNED))) ELSE 0 END AS AvgHosts,
CASE WHEN ( pendreasons LIKE '%Just started a job recently: %' ) THEN
MAX(CONVERT(SUBSTRING_INDEX(SUBSTRING(pendreasons, INSTR(pendreasons, 'Just started a job recently: ') + 29, 10), ' ', 1),UNSIGNED)) ELSE 0 END AS MaxHosts
FROM grid_jobs AS gj
JOIN grid_jobs_pendreasons AS gjp ON ( gj.clusterid = gjp.clusterid AND gj.jobid = gjp.jobid AND gj.indexid = gjp.indexid )
WHERE gjp.end_time = 0 AND reason = '1314' AND pendreasons LIKE '%Just started a job recently: %' " . $clusterid_sql . "
");

But nothing, LSF nor RTM, to have a clear and reliable view of which and how many hosts not reachable for this kind of reason.

reasons can be mem, swap, tmp, run queues, etc ... limits set for scheduling at host(group)s level.