Hi
No you can change it, the view only tells you the max number of process that has been launched. It allows you to check if the process parameter is set too low. In your case it seems to be ok as max used did not reach the number of process you defined.
Make sure that parameter rsts/enqueue/enabled is not set (1724201 - Background jobs remain in the status "ready")
Are the failing jobs defined to run on a specific server or server group ?
Have look to note 1057255 - Jobs remain in status 'ready' bit i do not think this will help...
And to note 394677 - Jobs do not run on certain servers
The time scheduler runs periodically at short intervals on every background server. The event scheduler can start jobs only on the server on which it is running.
There is no point in several time schedulers running on the same server simultaneously. To avoid this situation, a server-specific semaphore is used.
From a technical perspective, for Basis releases lower than Release 7.10, this semaphore is an enqueue lock of the form
Table = BTCREMTCLN Argument = <SERVER NAME>
If you cannot delete this lock after the time scheduler has run due to an external error, the time scheduler no longer runs on this server, and almost no jobs can be started on this server as a result.
Perform also the additional test (/goto/additional test) in SM65 for all your servers.
Regards