In a recent note, Ted MacNEIL said:
> Date: Mon, 29 Aug 2005 00:00:00 GMT
> Reply-To: IBM Mainframe Discussion List <[log in to unmask]>
> Sender: IBM Mainframe Discussion List <[log in to unmask]>
> From: Ted MacNEIL <[log in to unmask]>
> Subject: Re: Future ISPF directions (was: Re: How Was Share?)
> Content-type: text/plain
>
> >I suspect the same JES2 user resistance is still there.
> ...
>
> If you're resistant, don't turn on the option.
>
Such options should, by good design, be available with
the smallest possible scope. In this case, it should be
a job-by-job option: I want my job "FRED" to run
concurrently with other jobs named "FRED", but my job "JOE"
to wait until all other jobs named "JOE" to complete before
running. No user should be subject to the tyranny of the
majority, nor to the autocratic whim of the system
administrator.
Even as DISP={SHR|OLD} is not somewhere in PARMLIB, but on
each DD statement, JOBNAME={SHR|EXCL} should be an option
on each JOB card, with only the default coming from PARMLIB.
> You can do it for TSO and Batch separately.
>
Does this mean, IOW, that an installation can preserve
uniqueness for Batch jobs, but allow concurrency for
TSO jobs?
-- gil
--
StorageTek
INFORMATION made POWERFUL
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
