IIRC, JES2 runs the number of INTRDR processors (tasks) specifien on the INTRDR init statement. Not sure what happens when more SYSOUT=(*,INTRDR) than INTRDR PCEs are trying to submit jobs. I guess that the OPEN will just wait for an INTRDR PCE to become available to handle the request.
No matter, INTRDRs don't start the batch jobs (and it's only batch jobs, so STCINRDR is out of scope), they only write the JCL to the JES2 spool queueing then on the conversion queue. Some time later the conversion PCEs will pick up the JCLs and place the converted JCL onto the spool queueing the jobs on the execution queue. Again some time later, those jobs will eventually be picked by an initiator that *is already running* when using JES managed initiators. No new address spaces are being created. If using WLM managed initiators, WLM decides it more of them shall be started depending on current system load. We often have burst of batch jobs submitted from our scheduler when day end processing is scheduled on our test system. The execution queue has some 150+ jobs waiting to be executed but this does not slow down the system in any special manner. -- Peter Hunkeler CREDIT SUISSE ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
