Solved - Restrict on ability to access periodic jobs

There have been a number of discussions about "normal" user's ability to execute a report in the background and thereby schedule it to execute periodically and not just once. It is sometimes a big mess to clean up afterwards when hundreds or even thousands of jobs are running under end user ID's and they leave the company (or system), at which time the user ID should be disabled (restrict validity of user and roles, lock... etc).

If one could restrict this, then users would be forced to contact a batch job administrator to have the job scheduled as a recurring one under a SYSTEM ID.

Reference: Restrict periodic scheduling in SM37