Nasuh, I think that the answer to your question was hidden within the several responses.
There has never been a guarantee that with all things being equal, a JES2 initiator will select jobs from the Input Queue in the order they were submitted. This is because they go through CONVERSION first, and I'm think I'm right to say that with all else being equal they will be selected from the input queue in the order that they completed CONVERSION. Selection from the Input queue is not influenced by the Job number at all. You mention below that you have two CONVERTERS defined to JES2 (CNVTNUM=2) so when you submit the jobs it is likely that each one will be converted concurrently, and the converters will complete asynchronously. If the 2nd job completes conversion first then it is first on the input queue and the initiator will take it first. David Andrews suggested earlier that you reduce to CNVTNUM=1 so that conversion is single threaded, and your problem will be resolved. Ron > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On > Behalf Of Nasuh KARAHALLI > Sent: Tuesday, 25 October 2005 5:07 PM > To: [email protected] > Subject: Re: JES2 input queue priority > > Many thanks to ones who responded, > > This is the first case I have have ever see such kind issue, so yesterday > or other past days no problem was available. Anyway, we have MAS and > PCEDEF CNVTNUM=2, (2 Converter PCEs). If you assign two or more jobs > only > one init class, I think no matter how many CPUs, PCEs you have and so on. > > Regards. > ---------------------------------------------------------------------- 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
