ALERT! Warning: your browser isn't supported. Please install a modern one, like Firefox, Opera, Safari, Chrome or the latest Internet Explorer. Thank you!
Startseite » ... » Zentrale Einrichtungen  » ZIH  » Wiki
phone prefix: +49 351 463.....

HPC Support

Operation Status

Ulf Markwardt: 33640
Claudia Schmidt: 39833

Login and project application

Phone: 40000
Fax: 42328

You are here: Compendium » BatchSystems

Batch Systems

Applications on an HPC system can not be run on the login node. They have to be submitted to compute nodes with dedicated resources for user jobs. Normally a job can be submitted with these data:
  • number of CPU cores,
  • requested CPU cores have to belong on one node (OpenMP programs) or can distributed (MPI),
  • memory per process,
  • maximum wall clock time (after reaching this limit the process is killed automatically),
  • files for redirection of output and error messages,
  • executable and command line parameters.

Depending on the batch system the syntax differs slightly:

If you are confused by the different batch systems, you may want to enjoy this batch system commands translation table.


Please keep in mind that for a large runtime a computation may not reach its end. Try to create shorter runs (4...8 hours) and use checkpointing. Here is an extreme example from literature for the waste of large computing resources due to missing checkpoints:

Earth was a supercomputer constructed to find the question to the answer to the Life, the Universe, and Everything by a race of hyper-intelligent pan-dimensional beings. Unfortunately 10 million years later, and five minutes before the program had run to completion, the Earth was destroyed by Vogons. (Adams, D. The Hitchhikers Guide Through the Galaxy)

Exclusive Reservation of Hardware

If you need for some special reasons, e.g., for benchmarking, a project or paper deadline, parts of our machines exclusively, we offer the opportunity to request and reserve these parts for your project.

Please send your request 7 working days before the reservation should start (as that's our maximum time limit for jobs and it is therefore not guaranteed that resources are available on shorter notice) with the following information to the HPC support:
  • Project: <Which project will be credited for the reservation?>
  • Reservation owner: <Who should be able to run jobs on the reservation? I.e., name of an individual user or a group of users within the specified project.>
  • System: <Which machine should be used?>
  • Hardware requirements: <How many nodes and cores do you need? Do you have special requirements, e.g., minimum on main memory, equipped with a graphic card, special placement within the network topology?>
  • Time window: <Begin and end of the reservation in the form [year:]month:day:hour:minute>
  • Reason: <Reason for the reservation.>

Please note that your project CPU hour budget will be credited for the reserved hardware even if you don't use it.