So you have only one class defined in one INIT and it is active. You have 2 jobs come into the system with different names. Job 1 runs in this init for (example) 5 hours. It is a test job. Then Job 2 comes in and cannot run because the INIT is busy with JOB 1. Is that correct?
If so, add a second INIT with the same class. So long as DELAY_SUB is set in JES2 to only run one duplicate job at a time, then you can setup multiple INITs with the same class and have more work run Most shops do this. So in JES2 you might have INIT 1 CLASS A INIT 2 CLASS A and B INIT 3 CLASS B and A So if two jobs enter and use CLASS A, then INIT 1 and 2 would allow A to run before B, but INIT 3 would run Class B over Class A Does that make sense? What restrictions are in your shop that you would NOT be able to do this? The inits can be idle waiting for work with little over head. And JES2 (I presumed you are JES2) will handle the work load Or you can look at WLM and see how a JES2 WLM Managed INIT would work. Most shops have day time inits and night time inits. So during the day you might have 6 CLASS A inits to handle test work load. At night you switch the inits to have only ONE Class A init to allow minimal TEST and more PROD work. You would make sure any TEST job uses CLASS A, and Production would only use CLASS B. that way you can restrict how much of Class A or Class B runs at a particular time in the day. Lizette -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Jake anderson Sent: Tuesday, May 07, 2013 2:06 AM To: [email protected] Subject: Re: Duplicate Batch Job Hello, The problem is that same Job is submitted multiple times and which Leads to unavailability of Initiator to other Genuine Jobs. Lizette, We are having JES2. /Jake On Tue, May 7, 2013 at 2:32 PM, Vernooij, CP - SPLXM <[email protected]>wrote: > Can you explain what the problem is with the second job waiting for > execution? > > Regards, > Kees. > > > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] > On Behalf Of Jake anderson > Sent: Tuesday, May 07, 2013 11:00 > To: [email protected] > Subject: Re: Duplicate Batch Job > > Hello Lizette, > > We are at Z/OS 1.8. The first Job is in Execution status(Active) and > the other Same Job too in Execution but they are waiting for the Execution. > > /Jake > > > On Tue, May 7, 2013 at 2:24 PM, Lizette Koehler > <[email protected]>wrote: > > > 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
