I should have added, If JES2 then it is working as designed. Users are allowed to submit as many as the same job name as they like. The only difference is whether they run concurrently or one at a time.
I am not sure why you want to prevent a user from submitting any number of jobs with the same job name. What is the problem? Are TSO Users or Batch jobs doing the submitting? Can you determine who/what is submitting the jobs and correct that process? The only way I can think of restricting is an exit in JES2. Or if this is a TSO User you may wish to look at IKJEFT10 exit. If you are JES3 I am not sure what might work. Lizette -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Lizette Koehler Sent: Tuesday, May 07, 2013 1:54 AM To: [email protected] Subject: Re: Duplicate Batch Job Jake, What level of z/OS and JES are you running? Are the jobs running concurrently or just waiting execution? Lizette -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Jake anderson Sent: Tuesday, May 07, 2013 1:36 AM To: [email protected] Subject: Duplicate Batch Job Hello, In one of our education system. We find Same Job being Submitted Multiple Times(8 Times). Apology for my ignorance, Are there any way to restrict the Duplicate Job Submission when Original One is in Running State ? Any Suggestions Or help is much Appreciated. /Jake ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
