In our case, we use Connect:Direct between LPARs and one of the functions people use is the RUN TASK to tell CA7 to release a job on the receiving end. Since they are calling the same job name (CDC7NDMT) that is run to tell CA7 this, along with the job details, if there a whole bunch of transfers taking place, all wanting to run that same job name (CDC7NDMT) the release of the final processing job can get held up.
On Thu, Sep 14, 2017 at 9:50 AM Lizette Koehler <[email protected]> wrote: > There is. It is documented in the JES2 INIT and TUNING. Go to > www.ibm.com and search on JES2 DUPLICATE JOBS > > > > However, what problem are you trying to solve? > > When you switch this on - it will be an way of running that JES2 supports > but it is not normal for JES2. It was setup with serial processing. > > If you run duplicate job names, you will probably hit resource > contention. Everyone wanting the same dataset, for example. > > If you specify DUPL_JOB=NODELAY, jobs with the same job name may run > concurrently with adverse effects. Make certain that this serialization > mechanism is not being used in your environment before changing this > parameter. > > > Lizette > > > -----Original Message----- > > From: IBM Mainframe Discussion List [mailto:[email protected]] On > > Behalf Of Mark Regan > > Sent: Thursday, September 14, 2017 6:29 AM > > To: [email protected] > > Subject: Can you run multiple jobs with the same job name at the same > time on > > JES2? > > > > Just asking if there is a way. > > > > -- > > > > Regards, > > > > Mark T. Regan > > > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > -- Regards, Mark T. Regan ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
