Modify the system APS value (bmod)

About this task

The absolute scheduling priority for a newly submitted job is dynamic. Job priority is calculated and updated based on formula specified by APS_PRIORITY in the absolute priority queue.

You must be an administrator to modify the calculated APS value.

Procedure

  1. Run bmod job_ID to manually override the calculated APS value.
  2. Run bmod -apsn job_ID to undo the previous bmod -aps setting.
Parent topic: Absolute job priority scheduling

Assign a static system priority and ADMIN factor value

Procedure

Run bmod -aps "system=value" to assign a static job priority for a pending job.

The value cannot be zero.

In this case, job's absolute priority is not calculated. The system APS priority is guaranteed to be higher than any calculated APS priority value. Jobs with higher system APS settings have priority over jobs with lower system APS settings.

The system APS value set by bmod -aps is preserved after mbatchd reconfiguration or mbatchd restart.

Use the ADMIN factor to adjust the APS value

Procedure

use bmod -aps "admin=value" to change the calculated APS value for a pending job.

The ADMIN factor is added to the calculated APS value to change the factor value. The absolute priority of the job is recalculated. The value cannot be zero .

A bmod -aps command always overrides the last bmod -aps commands

The ADMIN APS value set by bmod -aps is preserved after mbatchd reconfiguration or mbatchd restart.

Example bmod output

The following commands change the APS values for jobs 313 and 314:
bmod -aps "system=10" 313
Parameters of job <313> are being changed
bmod -aps "admin=10.00" 314
Parameters of job <314> are being changed

View modified APS values

Procedure

  1. Run bjobs -aps to see the effect of the changes: 
    bjobs -aps
JOBID   USER   STAT   QUEUE  FROM_HOST EXEC_HOST   JOB_NAME   SUBMIT_TIME    APS
313    user1   PEND   owners hostA                    myjob  Feb 12 01:09    (10)
321    user1   PEND   owners hostA                    myjob  Feb 12 01:09      -
314    user1   PEND   normal hostA                    myjob  Feb 12 01:08 109.00
312    user1   PEND   normal hostA                    myjob  Feb 12 01:08  99.00
315    user1   PEND   normal hostA                    myjob  Feb 12 01:08  99.00
316    user1   PEND   normal hostA                    myjob  Feb 12 01:08  99.00
  2. Run bjobs -l to show APS values modified by the administrator: 
    bjobs -l
Job <313>, User <user1>, Project <default>, Service Class <SLASamples>, Status <RUN>, 
Queue <normal>, Command <myjob>, System Absolute Priority <10> ...
Job <314>, User <user1>, Project <default>, Status <PEND>, Queue <normal>, 
Command <myjob>, Admin factor value <10> ...
  3. Use bhist -l to see historical information about administrator changes to APS values.

    For example, after running these commands:

    1. bmod -aps "system=10" 108

    2. bmod -aps "admin=20" 108

    3. bmod -apsn 108

    bhist -l shows the sequence changes to job 108:
    bhist -l
Job <108>, User <user1>, Project <default>, Command <sleep 10000>
Tue Feb 23 15:15:26 2010: Submitted from host <HostB>, to 
Queue <normal>, CWD </scratch/user1>;
Tue Feb 23 15:15:40 2010: Parameters of Job are changed:
   Absolute Priority Scheduling factor string changed to : system=10;
Tue Feb 23 15:15:48 2010: Parameters of Job are changed:
   Absolute Priority Scheduling factor string changed to : admin=20;
Tue Feb 23 15:15:58 2010: Parameters of Job are changed:
   Absolute Priority Scheduling factor string deleted;
Summary of time in seconds spent in various states by  Tue Feb 23 15:16:02 2010
  PEND    PSUSP    RUN    USUSP    SSUSP    UNKWN    TOTAL
   36       0       0       0        0        0        36
...