CLASS-WEIGHT
Designates the urgency of the jobs waiting in a job class as compared to another class (important only after system saturation occurs).
Value range <integer 1..9>; 1 is the lowest urgency, 9 is the highest urgency.
JOB-PRIORITY
Defines the importance (priority) of the waiting jobs within a job class.
Value range <integer 1..9>; 1 is the highest priority, 9 is the lowest priority.
CPU-LIMIT
Determines the CPU time which a job in this job class may use.
The parameter NO-CPU-LIMIT=*YES has the same effect as the entry PRIVILEGE=*NO-CPU-LIMIT in the user catalog.
START
Specifies the possible start times (*SOON, *WITHIN,...).
The additional condition ALLOWED=*IMMEDIATE has the same effect as the entry PRIVILEGE=*START-IMMEDIATE in the user catalog. This means that a job may be started immediately, even if the job class limit has already been reached.
If, in an XCS network, the HOST=*ANY operand is specified in /ENTER-JOB or /ENTER-PROCEDURE, the jobs are automatically distributed to the individual computers in the network (for details, see the "HIPLEX MSCF" manual [12 (Related publications)]).
To select the target system, the criteria are considered in the following order:
Status of the job class
The desired job class must be defined and active (it must not have been suspended by means of /HOLD-JOB-CLASS, for example).
The system must not be in a state of saturation.
Utilization of the job class
As long as the job class limit (CLASS-LIMIT) has not been reached, for jobs that are to be executed immediately the difference between the job class optimum (CLASS-OPTIMUM) and the number of jobs already started is taken.
If the job class limit has been reached or exceeded, the difference between the job class limit and the number of accepted (i.e. already started and pending) jobs is taken.