[index (frame version)]       [index (text version)]

                 Connect:Queue - A batch job scheduling tool

Connect:Queue is a batch job queuing tool which allows you to submit jobs from your terminal or workstation to be processed on the system and you can continue working at your terminal without interruption while it is being processed or logout.

This batch facility must be used when a process (job) requires more than 13 meg of memory and/or more than 10 minutes of cpu.

If a process(job) exceeds the above limits and is not submitted through the batch facilty, the system will detect the process, terminate it and send appropriate mail message to the user.

The table below gives the configuration of the existing batch queues.

--------------------------------------------------------------
|  Queue                                                      |
|  Name   Cpu limit    Memory limit Total # of concurrent jobs|
|                                                             |
|-------------------------------------------------------------|
|                                                             |
|    b1   60 minutes   15 MB          5                       |
|    b2   2 hours      50 MB          5                       |
|    b2a  48 hours     100 MB         2                       |
|    b3   6.5 days     256 MB         1                       |
|                                                             |
--------------------------------------------------------------

          ************************************************
          *   Submitting a job to the queue -  "qsub"    *
          ************************************************

1.   Create a script file containing the commands you give when you run ajob interactively.
    Example:  To submit a sas program  plot.sas to the batch queue b1
    Create a script file "sasbat"  with the following statements.
-------------------------------------------------
  #
  #Script file to submit plot.sas to batch queue
  # print the log and listing files
 sas plot
 print plot.log
 print plot.lst
-------------------------------------------------
 
 Note: Statements beginning with # are comments and are not executed

2.   Make sure the file "sasbat"  has read,write and executable permissions
         chmod 700 sasbat

3.   Submit a batch request with the script file "sasbat" to the default queue
        qsub  -x sasbat
 
     To submit to a specific queue b2, give the command:
        qsub -x sasbat -q  b2
     The system will respond:
 
     Request 1501.server submitted to queue: b2
 
4.   Connect:Queue uses the script filename (sasbat) and the request-id number (1501) to form the names of the standard output (sasbat.o1501) and standard error (sasbat.e1501) files.
 
The output information that is normally sent to the screen in the interactive session will be written to sasbat.o1501.
 
The error messages from executing the script file will written to sasbat.e1501.

Note:  For more information on the "qsub" command, give the command man qsub and for a hardcopy give the command man -t qsub

          ************************************************
          *      Checking on your request  - "qstat"     *
          ************************************************

To check the status of your request, give the command:  qstat

For example , the system may respond

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

CONNECT:Queue for UNIX Scheduling 2.4b(SGI resource): REQUESTS on server

 REQUEST     NAME     OWNER    QUEUE  PRI NICE CPU    MEM    STATE

 10.server.u sasbat    joe      b1     5   30  900    unlim  running
 11.server.u abaqus    snow     b3     15  36  172800 unlim  queued

-----------------------------------------------------------------------------
 For more information give the command   man qstat

          ************************************************
          *        Deleting a request -  "qdel"          *
          ************************************************

The command "qdel"  can be used to delete a request that is not in a  "running" state.

Give the qstat command to fine the request id and the state of the job.
 
If the state is not running, then give the command:  qdel request.id  to delete the job from the queue.
 
       Example: qdel 11
 
The system will respond Request 11 has been deleted

If the state is running and you still want to delete the request, give the command:  qdel -k request.id
 
       Example: qdel -k 10
 
The system will respond Request 10 is running, and has been signalled.

[index (frame version)]       [index (text version)]