Ed,
Duplicate jobnames are allowed or not allowed at the discretion of the customer. There is now a parameter to allow duplicate jobnames' running simultaneously. Those shops that do not want havoc can opt not to use the new parameter. All shops are not identical. Bill Fairchild Franklin, TN ----- Original Message ----- From: "Ed Gould" <[email protected]> To: [email protected] Sent: Wednesday, May 1, 2013 10:24:03 AM Subject: Re: Check whether job still running Ed: 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. Ed On May 1, 2013, at 12:07 AM, Ed Jaffe wrote: > On 4/30/2013 8:25 PM, Robert A. Rosenberg wrote: >> If you can live with JOB1 and JOB2 having the same jobname and you >> use JES2, that will handle the wait since JES2 will not allow JOB2 >> to be initiated so long as JOB1 is executing. > > This is true only with JOBDEF DUPL_JOB=DELAY. More and more JES2 > shops these days are implementing JOBDEF DUPL_JOB=NODELAY to > provide function similar to JES3 DUPJOBNM=YES functionality. > > -- > Edward E Jaffe > Phoenix Software International, Inc > 831 Parkview Drive North > El Segundo, CA 90245 > http://www.phoenixsoftware.com/ > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
