RE: End user job scheduling in a multi-tenet environment

I'm assuming you mean multi-tenant, as in many companies... or maybe letting many users control their own jobs.

We create a single-threaded JOBQ for every user. This is created automatically when we create a user profile. This prevents a user from flooding a jobq with dozens of jobs. Yes, they would!

We also 'rotate' our JOBQs in the batch subsystem. When a user job starts, the routing entry moves the jobq that the job started from to the next-highest sequential numbered jobq in the subsystem. We keep a data area with the next number. When the number gets over a threshold (9000?), we-resequence the job queue numbers starting at 200 or so. This is necessary because the system processes jobs in the order the queues are listed in the subsystem. Once again, a user could flood the system, and no other job with a higher sequential number would get through until that user got tired of submitting jobs.

Users can submit jobs from the applications they have authority to use. These may go to various job queues-- their own personal queue, a queue for the application, or a queue for their location (ie physical plant scattered across the country).

We don't allow users to cancel jobs. They have a bad habit of cancelling a job that's already running.

Users can see any job they submit. The WRKSBMJOB command can show jobs submitted by user, workstation, or job (ie on-line session). A short 'wrapper' program, or a validity checking program could restrict users to just their own user profile.

Validity checking programs around the internal scheduler commands could do the same thing for those jobs.

We use the ROBOT/Help Systems job scheduler. It can be restricted so users can't schedule jobs themselves (our users can't). We've reserved this scheduler for system administrators and operators only.

Paul E Musselman
PaulMmn@xxxxxxxxxxxxx

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Charles Wilt
Sent: Tuesday, April 24, 2018 5:07 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: End user job scheduling in a multi-tenet environment

All,

Just curious how other out there handle allowing end-users to automate the
running of jobs in a multi-tenet environment?

As we see it two main requirements
- we define templates for what jobs can be scheduled
- end users should only be able to see their own jobs

Did you build or buy your solution?

We use the standard job scheduler internally...
I suppose we could build our own interface around the
List Job Schedule Entries (QWCLSCDE) API
and XXXJOBSCHDE commands...

Thanks!
Charles