End user job scheduling in a multi-tenet environment -- MIDRANGE-L

Subject: End user job scheduling in a multi-tenet environment
From: Charles Wilt <charles.wilt@xxxxxxxxx>
Date: Tue, 24 Apr 2018 15:06:57 -0600
List-archive: <https://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

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

Follow-Ups:

Re: End user job scheduling in a multi-tenet environment , Mark S Waterbury
RE: End user job scheduling in a multi-tenet environment , Musselman, Paul

This mailing list archive is Copyright 1997-2026 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.