When a job enters the system, its resource requirements are analyzed and it is placed into a job class (and a queue). A job is eligible for scheduling if its job class has been "opened" by the operator and if the number of jobs of that class already running in the system does not exceed a specified number. If these conditions aren't met, your job goes into a system scheduler queue.
Generally speaking, the more processor time and the more special resources (like tapes) you require, the better the chance it will get stuck in a queue and the longer it will take to get your job through the system.
A job is positioned in a queue according to its "priority" relative to other jobs. Priority is assigned when a job enters the system and NEVER changes; it is a function of the maximum processor time and the maximum amount of memory you request in the entire job (not just one activity).
The following list shows the job classes at Waterloo. Your job is placed into the first queue in the list which describes your job's resources.
Some of the above queues are summarized in the following table:
\ SIZE \ | 1K-30K | 30K-150K | 150K-... | TIME \ | | | | ---------------------------------------------- 1-2 | QUICK | QCORE | ---------------------------------------------- 3-9 | NORM | | -------------------------------- - 10-49 | BIG | CORE | ---------------------------------------------- 50-... | WOW | NEVER | ----------------------------------------------
Copyright © 1996, Thinkage Ltd.