PK96176: BF 7.1.x.x - Runtime started when jobs are still waiting in the Server queue, due to the Server 'Max Jobs' being set.

APAR status

• Closed as Permanent restriction.

Error description

• BF 7.1.x.x  - Runtime started when jobs are still waiting in the
  Server queue, due to the Server 'Max Jobs' being set.
  

Local fix

Problem summary

• BF 7.1.x.x  - Runtime started when jobs are still waiting in
  the Server queue, due to the Sysparam "Run Queue Size" being
  set.
  

Problem conclusion

• This is working as designed.
  
  This isn't a result of "Max Jobs" being set to 1 and then
  being ignored; its a result of "Run Queue Size" being set to
  3 and being obeyed.
  
  The "running" status is an Engine status, not an Agent
  status.
  
  If one were to launch Project 1 one time, and Project 2 (the
  "echo" step) ten times after, the result would be 3 jobs
  having the "running" status and the rest having the
  "waiting".  If "Run Queue Size" in the
  Administration-?System menu were changed to "1", you'd see
  one running project and nine waiting; if it were changed to
  "10", all ten would be in the running state.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels