The Faucets Scheduler commands

Job Submission:

• Commands ufrun, frun-mpi, and frun run a jobs interactively. Command ufrun submits single processor interactive jobs and frun-mpi submits interactive MPI jobs. Command frun is the generic command to submit jobs and it takes job type as an argument. By default frun runs a charm job.

  frun [program_name] [options] [arguments]

  ufrun [program_name] [options] [arguments]

  frun-mpi [program_name] [options] [arguments]

  These commands interactively run the jobs on the parallel machine

  program_name is the name of your compiled executable or script,

  you should NOT provide an mpirun or a charmrun

  Options

  • -I : For interactive debugging jobs. It opens up an xterm and sets the nodelist to the nodes allocated by the scheduler. You can then run anything you wish from the shell. Primarily useful for long compilation sessions or porting work best kept off the head node. For multiprocessor jobs consult the .nodelist file written by Faucets for your node allocation. Note that this only works for frun and frun-mpi.
  • -stdout [filename]: The Std. Output file of the job (default frun terminal)
  • -stderr [filename]: The Std. Error file of the job (default frun terminal)
  • -stdin [filename]: The Std. Input file of the job (default frun terminal)
  • -type [mpi/charm/mcharm/uni]: The type of the job (default charm)
  • -time [hh:mm:ss] : time requested for the job (4 hours by default)
  • -pwd [directory name]: Process Working Directory, (default current directory)
  • -name [name]: Name that will be reported by fjobs, no spaces allowed (default executable name)

  • +n : Number of nodes requested for the job
  • +ppn : Number of processors per node to use
  • +p : Alternative to +n<> and +ppn<>. Number of processors requested for the job, assumes that all processors on a node will be used

    If a processor range needs to be provided for the job

  • -minnode : minimum number of nodes used by the job
  • -maxnode : maximum number of nodes used by the job
  • -minpe : minimum number of processors used by the job
  • -maxpe : maximum number of processors used by the job

    #Processors allocated to the job varies between these bounds

  • ++notify-start, to send email when job starts
  • ++notify-end, to send email when job finishes

    default email address used is userid@localhost.cs.uiuc.edu

  • -email [address], to send email to address, also sets notify-end by default
  • ++debug, to enable charm++ programs to be debugged, SHOULD HAVE DISPLAY set

  For Example :

  frun +n2 +ppn2 ./hello -time 1:0:0

  runs the charm program hello interactively on 2 nodes and 4 processors for 1 hour.

  ufrun /bin/ls,

  runs /bin/ls on one processor. For single processor jobs ufrun should be used.

  frun-mpi +n2 +ppn2 ./hello_mpi -time 1:0:0

  runs the mpi program hello_mpi interactively on 2 nodes and 4 processors for 1 hour.

• ufsub, fsub and fsub-mpi submit jobs to the queuing system as a batch job. ufsub and fsub-mpi submit batch single processor and mpi jobs.

  ufsub [program_name] [options] [arguments]

  fsub [program_name] [options] [arguments]

  fsub-mpi [program_name] [options] [arguments]

  program_name is the name of your compiled executable or script,

  you should NOT provide an mpirun or a charmrun

  Options

  • -stdout [filename]: The Std. Output file of the job (default /dev/null)
  • -stderr [filename]: The Std. Error file of the job (default /dev/null)
  • -stdin [filename]: The Std. Input file of the job (default /dev/null)
  • -type [mpi/charm/mcharm/uni]: The type of the job (default charm)
  • -time [hh:mm:ss] : time requested for the job (4 hours by default)
  • -pwd [directory name]: Process Working Directory, (default current directory)
  • -name [name]: Name that will be reported by fjobs, no spaces allowed (default executable name)

  • +n : Number of nodes requested for the job
  • +ppn : Number of processors per node to use
  • +p : Alternative to +n<> and +ppn<>. Number of processors requested for the job, assumes that all processors on a node will be used

    If a processor range needs to be provided for the job

  • -minnode : minimum number of nodes used by the job
  • -maxnode : maximum number of nodes used by the job
  • -minpe : minimum number of processors used by the job
  • -maxpe : maximum number of processors used by the job

    #Processors allocated to the job varies between these bounds

  • ++notify-start, to send email when job starts
  • ++notify-end, to send email when job finishes

    default email address used is userid@localhost.cs.uiuc.edu

  • -email [address], to send email to address, also sets notify-end by default
  • ++debug, to enable charm++ programs to be debugged, SHOULD HAVE DISPLAY set

  For Example :

  fsub +n2 +ppn2 ./hello -time 1:0:0

  submits the charm program hello to be run on 2 nodes and 4 processors for 1 hour.

  ufsub /bin/ls,

  submits /bin/ls on one processor.

  ufsub +n2 +ppn2 ./hello_uni -time 1:0:0

  submits the single processor program to be run on 2 nodes and 4 processors for 1 hour.

  fsub-mpi +n2 +ppn2 ./hello_mpi -time 1:0:0

  submits the mpi program hello_mpi to run on 2 nodes and 4 processors for 1 hour.

  Job Management:

• fkill, kills the job

  fkill [job_id1, job_id2, job_id3....] All the job_ids will get killed.

  fkill -u [user] kills all jobs by that user.

• fjobs [options] reports the status of all the running and queued jobs. Options
  • -full: prints out all information about jobs
  • -user [uname]: reports information for jobs owned by the user 'uname'
  • [id]: reports information only for job with ID 'id'