Frank Swarbrick wrote: > I have a complaint (shocking, I know). What is the reasoning behind MVS not > allowing more than one job with the same name to run at the same time? For > instance just now I wanted to do an IDCAMS PRINT on two files. I do this > often on VSE with a job I have set up that has this: > PRINT INFILE(FILE1) - > DUMP > > I simply change FILE1 to whatever the name is and submit it. Then if I have > another one I change it again to the second file and submit it. These are > large files so it makes sense to have them both run at the same time, rather > than one after the other. But unless I change the job name on the JOB card > on z/OS the second one won't run until the first is done. Annoying! Why on > earth is this restriction present? Does it actually *help* some situations, > or is it simply one of those annoying things that has existed forever and > will probably never be changed? > > Thanks (really!), > Frank > > As you correctly surmised the default to delay duplicate jobnames is due to the way it's always worked. I assume that it was used as a very simple job scheduling mechanism.
Under more recent levels of JES2 the default can be changed via a parameter in the JOBDEF statement, DUPL_JOB=DELAY/NODELAY for a global change or it can be set on a jobclass basis on the JOBCLASS(x) statement. -- Mark Jacobs Time Customer Service Tampa, FL ---- "Guitar groups are on the way out", "The Beatles have no future in show business" Decca Records rejection of The Beatles - 1962 ---------------------------------------------------------------------- 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
