as i know, i had that problem in 2015. You should reduce the number of rules running always in LOG mode, and change more rules from LOG to PROD. because a lots of rules in LOG mode may lead to a high RQC utilization.
for solution, im increase the parameter and increase size an dataset, but my suggestion you can contact BMC first and open the ticket.
because sometimes a same problem not always have same solution.
you may reduce the number of rules running always in LOG mode
thank you for your reply. I have already chcecked out all of the rules, but all of them are in a PROD mode. This problem with RQC utilization has been always active when WTO buffer shortage or an unusual number of messages have been produced to MVS console.
This may happen, if there is a new program in some JOB or have been made some changes in processing.
Ok, I am probably going to open a ticket. Becouse, there is a mismatch in a documentation.
Thank you for your suggestion.
We had a similar issue when we implemented Cosmos due to the number of nested rules. I agree with Irvan to consult with support before making any changes.