qdel

      qsub -t 1-7 array.sh

meaning that the array.sh program will run in seven issues, and the SGE_TASK_ID will have the value of 1, 2, ..., 7 in every running issue. The qstat -f shows how the block tasks are split:

     ---------------------------------------------------------------------------------
      parallel.q@cn30                       BIP   0/0/24         0    linux-x64   

     ---------------------------------------------------------------------------------

      test.q@cn32                        BIP   0/7/24       7.15     linux-x64
         907 1.00000 PI_ARRAY_T stefan       r     06/04/2011 10:34:14     1 1
         907 0.50000 PI_ARRAY_T stefan       t     06/04/2011 10:34:14     1 2
         907 0.33333 PI_ARRAY_T stefan       t     06/04/2011 10:34:14     1 3
         907 0.25000 PI_ARRAY_T stefan       t     06/04/2011 10:34:14     1 4
         907 0.20000 PI_ARRAY_T stefan       t     06/04/2011 10:34:14     1 5
         907 0.16667 PI_ARRAY_T stefan       t     06/04/2011 10:34:14     1 6
         907 0.14286 PI_ARRAY_T stefan       t     06/04/2011 10:34:14     1 7    

It is clear, that behind the tasks there are their array index with which we can refer to the components to the task. For example, in the case of block tasks, there is a possibility to delete particular parts of the block. If we want to delete the subtasks from 5-7 of the previous task, the command

      qdel -f 907.5-7 

will delete chosen components, but leaves the tasks 907.1-4 intact.

The result of the running is seven individual files, with seven different running solutions:

It can happen; that the task placed in the queue won’t start. This case the:

      qstat -j job_id

command will show the detailed scheduling information, containing which running parameters are unfulfilled by the task.

The priority of the different tasks only means the gradiation listed in the pending jobs. The scheduler will analyze the tasks in this order. Since it requires the reservation of resources, it is not sure, that the tasks will run exactly the same order.

If we wonder why a certain job won’t start, here’s how you can get information:

      qalter -w v job_id

One possible outcome

      Job 53505 cannot run in queue "parallel.q" because it is not contained in its hard queue list (-q)
      Job 53505 (-l NONE) cannot run in queue "cn30.budapest.hpc.niif.hu" because exclusive resource (exclusive) is already in use
      Job 53505 (-l NONE) cannot run in queue "cn31.budapest.hpc.niif.hu" because exclusive resource (exclusive) is already in use
      Job 53505 cannot run in PE "mpi" because it only offers 0 slots
      verification: no suitable queues

You can check with this command where the jobs are running:

   qhost -j -q

HOSTNAME                ARCH         NCPU  LOAD  MEMTOT  MEMUSE  SWAPTO  SWAPUS
-------------------------------------------------------------------------------
global                  -               -     -       -       -       -       -
cn01                    linux-x64      24 24.43  62.9G    3.0G     0.0     0.0
   serial.q             BI    0/42/48       
    120087 0.15501 run.sh     roczei      r     09/23/2012 14:25:51 MASTER 22
    120087 0.15501 run.sh     roczei      r     09/23/2012 15:02:21 MASTER 78
    120087 0.15501 run.sh     roczei      r     10/01/2012 07:58:21 MASTER 143
    120087 0.15501 run.sh     roczei      r     10/01/2012 08:28:51 MASTER 144
    120087 0.15501 run.sh     roczei      r     10/04/2012 17:41:51 MASTER 158
    120340 0.13970 pwhg.sh    roczei   r     09/24/2012 23:24:51 MASTER 3
    120340 0.13970 pwhg.sh    roczei   r     09/24/2012 23:24:51 MASTER 5
    120340 0.13970 pwhg.sh    roczei   r     09/24/2012 23:24:51 MASTER 19
    120340 0.13970 pwhg.sh    roczei   r     09/24/2012 23:24:51 MASTER 23
    120340 0.13970 pwhg.sh    roczei   r     09/24/2012 23:24:51 MASTER 31
    120340 0.13970 pwhg.sh    roczei   r     09/24/2012 23:24:51 MASTER 33
    120340 0.13970 pwhg.sh    roczei   r     09/26/2012 13:42:51 MASTER 113
    120340 0.13970 pwhg.sh    roczei   r     10/01/2012 07:43:06 MASTER 186
    120340 0.13970 pwhg.sh    roczei   r     10/01/2012 07:58:36 MASTER 187
    ...

Getting information on the waiting line’s status:

qstat -g c

CUSTER QUEUE         CQLOAD   USED    RES  AVAIL  TOTAL aoACDS  cdsuE  
--------------------------------------------------------------------------------
parallel.q                       0.52    368       0     280       648        0       0 
serial.q                          0.05       5       0     91         96        0       0 
test.q                            0.00       0       0     24        24         0       0