6.0.6 Upgrade Concern: Diable or Hide the JRS Schedule Screen From All AT&T Users To Protect Server Performance

For the TDP-JRS application we desire to have the ability to block or hide the presentation of the JRS Scheduling screen to all users. This IBM feature 6.0.6 Upgrade Feature, that based on our conversations, we believe allows users to schedule an unlimited number of reports (though not concurrently) to execute at any time, is out-of-the-box and will come to us on 11/15/18 with the 6.0.6 Upgrade. AT&T did not request it

Adverse Impacts: The JRS Report Scheduler's processes are very simplex. In summary, it does not have any of the features that one would expect to come with a Scheduler:
1) Ability limit users in how much demand they place on our CPU or disk space utilization (but we do understand we can limit the number of concurrent users)
2) Ability to turn off or hide the new JRS scheduler
3) Ability to automatically delete, or age off, old report data
4) Ability limit its use to specific individuals
5) Mandate that it is used during off peak hours.

To us this means that the database that holds the data from report executions could get filled up, or CPU utilization go so high that system performance degrades. Over use of CPU could actually bring one or many TDP servers down.
Specific Risks:
Risk 1: JRS Scheduling could cause over utilization of disk space on one or more of our servers due to scheduled reports using up our disk capacity. Having a data base get filled up would likely mean no more reports could be successfully executed.
Risk 2: JRS Scheduling could potentially absorb all of our CPU capacity on one or more servers. This could cause our servers to slow down, or one or more servers could come down.

We desire the ability to hide or block the JRS Scheduler.