In a message dated 8/29/2005 10:35:21 A.M. Central Daylight Time, [EMAIL PROTECTED] writes:
>IBM could easily support multiple >sessions with the same name and allow ASID on the CANCEL command 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. Bill Fairchild ---------------------------------------------------------------------- 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
