On 2013-05-01, at 10:32, Ed Jaffe wrote:
> On 5/1/2013 8:43 AM, Ed Jaffe wrote:
>> On 5/1/2013 8:24 AM, Ed Gould wrote:
>>> I am somewhat surprised that you indicate that duplicate jobnames are to be
>>> allowed. I have worked in a few shops that job naming stand is frozen and
>>> it would wreek havoc if a duplicate jobname were to be allowed running at
>>> the same time.
>>
>> Not sure what to say. This long-standing customer requirement was
>> implemented in JES2 over six years ago.
>
> Wow! Time flies when you're getting old. ;)
>
> Research suggests this feature was introduced to JES2 in OS/390 V2R6 ca. 1998!
>
And Ed G. didn't read the announcements, SHARE proceedings or DOC holds.
A scheduler can be seen as a sort of outboard hypervisor. If it's
programmable, I don't see why it shouldn't be able to support,
even as a one-off a program such as:
Run JOB A
wait for completion
Run JOB B
...
Again, as John M. notes, this much more natural in UNIX
where there's no artificial distinction between "jobs" and
other kinds of processes.
-- gil
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
