How to restrict certain users’ ability to delete queued jobs in Lawson job scheduler

, ,

Follow the steps below to learn how to restrict certain users’ ability to delete queued jobs in Lawson job scheduler.

  1. Create a new role named ‘BatchRestrictedRole’ using the Lawson RM Administrator tool.
  2. Next, in the Lawson Security Administrator (LSA), generate a new Security Class for the GEN profile and name it ‘BatchRestricted.’
  3. Within LSA, associate the ‘BatchRestricted’ Security Class with the ‘BatchRestrictedRole.’
  1. Now, let’s establish the rules for the Batch Restricted security class:
    1. Online: CAT UN
      • Grant All Access
    2. Data sources: GEN
      • Grant All Access
    3. Files: JOB, JOBSTEP
      • Grant All Access
    4. Elements: UserName
      • Grant All Access
    5. Files: QUEUEDJOB
      • Unconditional Access for Action Add (A) and Action Inquiry (I)
    6. More Security context:
      • Action Add (A) enables ability to add batch jobs
      • Action Inquiry (I) enables ability to view and run queued jobs
      • Action Delete (D) enables ability to kill running jobs
      • Action Update (M) enables ability to remove completed jobs
  1. Assign the newly created ‘BatchRestrictedRole’ to users. Ensure that these users do not possess any existing roles that grant full access to QUEUEDJOB. You can verify this by running a user security report for the GEN profile and searching for QUEUEDJOB.
  1. Please take note that, depending on your specific security requirements, you may opt to impose further restrictions on other objects within the security class.
  1. Keep in mind that while users will still see the option to delete a job, they will receive messages such as ‘User does not have access to queued job’ or ‘User Does Not Have Security Access To Delete This Job Log’ when attempting to delete jobs.
0 replies

Leave a Reply

Want to join the discussion?
Feel free to contribute!

Leave a Reply

Your email address will not be published. Required fields are marked *