FOR LSA (not LAUA) accounts we did the following: To remove the ability to perform the Delete function on a Waiting, Active or Needs Recovery job, for the majority of users, we modified the existing ‘Batch’ Security Class in the GEN Profile, by writing an Unconditional Access for Action rule on the QUEUEDJOB file that prohibits job deletion by giving access only to the following functions:
1. A - Add and Submit a job
2. I - View a queued job
3. M - Delete a Completed Job
Then we created a new Security Class called ‘BatchWithDelete’ in the GEN Profile, which inherited all of the security of the ‘Batch’ Security Class, but granted ALL ACCESS to the QUEUEDJOBS table. The ‘BatchWithDelete’ Security Class was then assigned to a new role ‘BatchWithDeleteRole’. That new role was then be assigned to the specific user accounts who were identified as needing the ability to delete Active, Waiting or Needs Recovery jobs.