Perhaps we all should consider a better use of our time than worrying about
inconsequential things such as duplicate jobs being submitted? (8-{]}
I, for one, do not understand what the problem is. (8-{[}
-
Ted MacNEIL
eamacn...@yahoo.ca
Twitter: @TedMacNEIL
-----Original Message-----
From: DASDBILL2 <dasdbi...@comcast.net>
Sender: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU>
Date: Wed, 8 May 2013 22:19:02
To: <IBM-MAIN@LISTSERV.UA.EDU>
Reply-To: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU>
Subject: Re: Duplicate Batch Job
Space in the JESx checkpoint area is also a finite resource even if the job
never runs. Each job submitted requires a small amount of DASD space in the
checkpoint area. Perhaps you should also consider preventing any given user
from submitting an infinite number of valid, authorized, uniquely-named jobs.
Bill Fairchild
Franklin, TN
----- Original Message -----
From: "Kirk Talman" <rkueb...@tsys.com>
To: IBM-MAIN@LISTSERV.UA.EDU
Sent: Wednesday, May 8, 2013 2:50:32 PM
Subject: Re: Duplicate Batch Job
IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> wrote on
05/08/2013 11:55:37 AM:
> From: Paul Gilmartin <paulgboul...@aim.com>
>
> On Wed, 8 May 2013 08:37:12 -0700, Ed Jaffe wrote:
> >
> A plausible motivation is that they want all jobs submitted via
> their scheduler.
I agree that one should control resources. We have written a mechanism to
replace SUBMIT which, based on an authorization scheme, a job runs with
authority other than one's own. And all actions are logged. And noone
has the authority to approve one's own job.
The approval scheme is granular enough that each person has one or more
demographics of "group". Each approver has a list of groups they can
approve.
It has a number of usability features involving symbolic replacement and
running lists of jobs. One can also specify the lpar to run on, but
unfortunately not the plex.
Written in Rexx & assembler w/reports in cobol.
-----------------------------------------
The information contained in this communication (including any
attachments hereto) is confidential and is intended solely for the
personal and confidential use of the individual or entity to whom
it is addressed. If the reader of this message is not the intended
recipient or an agent responsible for delivering it to the intended
recipient, you are hereby notified that you have received this
communication in error and that any review, dissemination, copying,
or unauthorized use of this information, or the taking of any
action in reliance on the contents of this information is strictly
prohibited. If you have received this communication in error,
please notify us immediately by e-mail, and delete the original
message. Thank you
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
