Problem solved. $DJOBCLASS,DUPL_JOB identified one errant class and $TJOBCLASS(x),DUPL_JOB=DELAY fixed it.
Now to find out how one class got that setting..... Thanks Lizette. Bob -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Lizette Koehler Sent: Monday, June 06, 2016 9:04 AM To: [email protected] Subject: Re: Duplicate jobs running concurrently even with DUPL_JOB=DELAY What level of z/OS are you running? Next, can you post the following output of the commands $DJOBDEF $DJOBCLASS(x) where X is the class where you are seeing this issue? If you specify DUPL_JOB=DELAY on the JOBDEF statement or DUPL_JOB=DELAY is the default, no two batch jobs with the same name will execute at the same time in the MAS, except when DUPL_JOB=NODELAY is specified on the JOBCLASS(x) statement. If you specify DUPL_JOB=NODELAY on the JOBDEF statement, jobs with the same name can run at the same time, no matter what DUPL_JOB= is specified on the JOBCLASS(x) statement. Lizette > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] > On Behalf Of Richards, Robert B. > Sent: Monday, June 06, 2016 5:36 AM > To: [email protected] > Subject: Duplicate jobs running concurrently even with DUPL_JOB=DELAY > > I am experiencing a strange event at the moment and was wondering if > this has happened to others. > > Just this morning, jobs with duplicate names have been running > concurrently even though we are running with DUPL_JOB=DELAY > > Has anyone else seen this recently? > > Bob ---------------------------------------------------------------------- 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
