Modify limits and weight of job classes
Component: | BS2000 |
Functional area: | Job processing |
Domain: | ERROR-LOGGING |
Privileges: | TSOS |
Routing code: | J |
Function
The MODIFY-JOB-CLASS command allows systems support to alter the limits and weights of job classes. The job limits and weight of job classes are defined by means of the JMU statement DEFINE-JOB-CLASS. The modifications, which are valid until the next MODIFY-JOB-CLASS command or until the end of the session, apply only to those jobs that have not yet been released for starting.
CLASS-LIMIT=0 should only be declared briefly, if at all, after startup in order to prevent any jobs being started that could hinder the activation of the job schedulers at this stage.
A message is output on the console if the command is executed successfully.
The modified values can be displayed using the SHOW-SYSTEM-STATUS command.
The default value *UNCHANGED in the corresponding operands means that the previously valid definition still applies.
Format
MODIFY-JOB-CLASS | Alias: MDJCL |
CLASS-NAME = <name 1..8> ,CLASS-LIMIT = *UNCHANGED / <integer 0..4095> ,CLASS-WEIGHT = *UNCHANGED / <integer 1..9> ,CLASS-OPTIMUM = *UNCHANGED / <integer 0..4095> |
Operands
CLASS-NAME = <name 1..8>
Name of the job class whose attributes are to be modified.
CLASS-LIMIT = *UNCHANGED / <integer 0..4095>
Defines the maximum number of jobs which may run at any given time in the specified job class.
A job transferred to the class scheduler for starting will be rejected if the CLASS-LIMIT has already been reached.
As soon as the value has fallen below the CLASS-LIMIT again, the scheduler managing the job classes is informed of this.
The only exceptions to this are express jobs, which can be started even when the class limit is reached.
CLASS-WEIGHT = *UNCHANGED / <integer 1..9>
Defines the weight of the job classes relative to each other.
This operand affects the selection of the job class from which a job is to be started. The higher the value for CLASS-WEIGHT, the greater is the weight and the urgency to start a job from the selected class.
CLASS-OPTIMUM = *UNCHANGED / <integer 0..4095>
Defines the number of jobs, which should ideally run within job class in order to reach a certain job mix.
Return codes
(SC2) | SC1 | Maincode | Meaning |
---|---|---|---|
0 | CMD0001 | No error | |
1 | CMD0202 | Syntax error | |
32 | CMD0221 | System error | |
64 | JMS0630 | Semantic error | |
64 | JMS0640 | Command cannot be executed |
Example
/show-job-class jcb00050
%NAME..........:JCB00050 %CLASS LIMIT...:20 %CLASS OPTIMUM.:0 %WEIGHT........:6 %JOB PRIORITY..:DEFAULT=9 MAXIMUM= 9 %JOB ATTRIBUTES:JOBTYPE=BATCH ST-ATTR= BATCH %BATCH ALLOWED.:YES %DIALOG ALLOWED:NO %TP ALLOWED....:YES %RUN PRIORITY..:DEFAULT=210 MAXIMUM= 209 %NO CPU LIMIT..:NO %CPU LIMIT.....:DEFAULT=50 MAXIMUM= 50 %SYSLST LIMIT..:DEFAULT=NO-LIMIT MAXIMUM= NO-LIMIT %SYSOPT LIMIT..:DEFAULT=NO-LIMIT MAXIMUM= NO-LIMIT %START.........:DEFAULT=SOON ALLOWED= SOON EARLY AT LATE IN STUP %REPEAT JOB....:DEFAULT=NO ALLOWED= NO STUP DAILY WEEKLY PERIOD %JOB PARAMETER.:UNDEFINED JCB00050 IS AVAILABLE TO: ALL USERS
/mod-job-class jcb00050,class-limit=100,class-weight=5
% JMS0022 '/MODIFY-JOB-CLASS' COMMAND PROCESSED
/show-job-class jcd00050
%NAME..........:JCB00050 %CLASS LIMIT...:100 %CLASS OPTIMUM.:0 %WEIGHT........:5 %JOB PRIORITY..:DEFAULT=9 MAXIMUM= 9 %JOB ATTRIBUTES:JOBTYPE=BATCH ST-ATTR= BATCH %BATCH ALLOWED.:YES %DIALOG ALLOWED:NO %TP ALLOWED....:YES %RUN PRIORITY..:DEFAULT=210 MAXIMUM= 209 %NO CPU LIMIT..:NO %CPU LIMIT.....:DEFAULT=50 MAXIMUM= 50 %SYSLST LIMIT..:DEFAULT=NO-LIMIT MAXIMUM= NO-LIMIT %SYSOPT LIMIT..:DEFAULT=NO-LIMIT MAXIMUM= NO-LIMIT %START.........:DEFAULT=SOON ALLOWED= SOON EARLY AT LATE IN STUP %REPEAT JOB....:DEFAULT=NO ALLOWED= NO STUP DAILY WEEKLY PERIOD %JOB PARAMETER.:UNDEFINED JCB00050 IS AVAILABLE TO: ALL USERS