Jobs waiting for "conversion" are queued for conversion by the number of JCL card images. When two jobs are in the conversion queue, and the two jobs have vastly different numbers of JCL card images (similar numbers of card images tend to get the same JES2 priority), JES2 will select the job with fewer card images for conversion first. This affects subsequent processing because the job which ends conversion first will usually be selected for execution first.
So, my contribution to the discussion is that your JOB2 had many fewer card image lines which have // in the first two characters as compared to your JOB1, and thus JOB2 completed conversion first. http://bama.ua.edu/cgi-bin/wa?A2=ind0502&L=ibm-main&P=R27040 Brian On Mon, 24 Oct 2005 09:28:58 -0500, Nasuh KARAHALLI <[EMAIL PROTECTED]> wrote: >Hi Dear Listers, > >As I try to submit two different jobs JOB1 and JOB2 (both jobs with the >same init class 1 in their jobcards, and init class 1 is the only one in >the system) in a single JCL with like below : > >//SYSPRINT DD SYSOUT=* >//SYSTSIN DD * > SUBMIT 'SYS2.PROD.JOBLIB(JOB1)' > SUBMIT 'SYS2.PROD.JOBLIB(JOB2)' > >the system give them a job the number say JOB22540 to JOB1 and let's say >JOB22541 to JOB2 respectively. > >As both get submitted, first they both wait for a couple of minutes so that >a resouce used by another user become available to them. As long as this >resource becomes available, JOB1 and JOB2 start in turn, but JOB2 first, >not JOB1. > >Does anybody out there have any idea about why this could be happened ? > >Many thanks in advance. > >Regards. >Nasuh KARAHALLI. > ---------------------------------------------------------------------- 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
