Bill Fairchild wrote:
A long time ago IBM wanted to do this, took a user survey, and found that a
large number of JES2 shops were relying on JES2's "feature" (really a
restriction since day one of HASP) of not letting more than one job with the same
jobname start executing. Users were using this restriction as a home-grown way
of enqueing on a resource at the job level. IBM then announced it was no
longer interested in supporting multiple jobs running with the same name.
There are other ways to provide job-level enqueuing, some of which are used
by JES3. The JES2 users would have to change lots of production JCL to use
some new technique. Thus the resistance.
I suspect the same JES2 user resistance is still there.
Resistance or no resistance, both JES2 and JES3 allow multiple jobs with
the same name to execute simultaneously. The feature is optional -- an
acknowledgment of "old school" shops that actually depend on duplicate
job name queuing as a primitive form of serialization. We run multiple
jobs with the same name all the time!
--
.-----------------------------------------------------------------.
| Edward E. Jaffe | |
| Mgr, Research & Development | [EMAIL PROTECTED] |
| Phoenix Software International | Tel: (310) 338-0400 x318 |
| 5200 W Century Blvd, Suite 800 | Fax: (310) 338-0801 |
| Los Angeles, CA 90045 | http://www.phoenixsoftware.com |
'-----------------------------------------------------------------'
----------------------------------------------------------------------
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
