If you have an initiator set to CLASS=AP, JES2 will select the highest
priority, non-held CLASS=A job for execution. Only when the CLASS=A
queue is empty will JES2 then start looking for the highest priority
non-held
job in the CLASS=P queue.
/jack
----- Original Message -----
From: "John Mattson" <[EMAIL PROTECTED]>
Newsgroups: bit.listserv.ibm-main
To: <[email protected]>
Sent: Monday, December 08, 2008 2:14 PM
Subject: Re: /*PRIORITY change without JCL change
Page 99 of zOS V1R9.0 JES2 Initialization and Tuning
Guide-has2a360.pdf Has the following text:
"During execution, the initiator selects nonheld jobs in priority order
within their class, and the nonheld classes in the order specified for
that initiator. That is, the JES2 initiator selects the lowest priority
job in the first nonempty class ahead of the highest priority job of the
next class."
Is it correct that "nonempty" means input job class which for
which jobs are waiting for initiators and there is an unused initiator?
Would someone explain what is meant by "first nonempty class" and
"next class"? What is the "order" to which they refer?
Does it mean from lowest, A to Z and 0 to 9? IF this is so it
would mean that jobs on the Input class "A" would ALWAYS be selected
BEFORE jobs in any other input queue even if the /*PRIORITY was very LOW
for the class A job, and Very High for class "P" for example. Is this what
the manual is saying?
----------------------------------------------------------------------
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
----------------------------------------------------------------------
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
