RE: Why do people set up their batch submission defaults to run multiple batch jobs at the same time?

Most of our production job queues allow 15 or more jobs to run simultaneously...

Jobs submitted 'on demand' by users go to the user's "personal" job queue-- which is single threaded. This prevents a single user from flooding the system.

We also 'rotate' our job queues-- a routing program inspects the log of the job just starting and finds out which job queue the job started from. It then changes the subsystem description, giving that job queue the next highest sequence number. The sequence number is held in a data area; when we get over 9000 a batch job renumbers the queues starting at a low number.

This rotating of job queues prevents a user with a queue that has a low sequence number from filling the queue and blocking all other users from running jobs until hit queue is empty.

==Paul E Musselman
PaulMmn@xxxxxxxxxxxxxxxxxxxx