<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="FeedCreator 1.8" -->
<?xml-stylesheet href="https://docs-archive.hpc.udel.edu/lib/exe/css.php?s=feed" type="text/css"?>
<rss version="2.0">
    <channel xmlns:g="http://base.google.com/ns/1.0">
        <title>hpc documentation - abstract:farber:runjobs</title>
        <description></description>
        <link>https://docs-archive.hpc.udel.edu/</link>
        <lastBuildDate>Wed, 15 Apr 2026 20:46:31 +0000</lastBuildDate>
        <generator>FeedCreator 1.8</generator>
        <image>
            <url>https://docs-archive.hpc.udel.edu/_media/wiki/dokuwiki.svg</url>
            <title>hpc documentation</title>
            <link>https://docs-archive.hpc.udel.edu/</link>
        </image>
        <item>
            <title>job_status</title>
            <link>https://docs-archive.hpc.udel.edu/abstract/farber/runjobs/job_status</link>
            <description>Managing Jobs on Farber

Once a user has been able to submit jobs to the queue -- interactive or batch -- the user will from time to time want to know what those jobs are doing.  Is the job waiting in a queue for resources to become available, or is it executing?  How long has the job been executing?  How much CPU time or memory has the job consumed?  Users can query Grid Engine for job information using the</description>
            <author>anonymous@undisclosed.example.com (Anonymous)</author>
            <pubDate>Wed, 13 Oct 2021 20:49:24 +0000</pubDate>
        </item>
        <item>
            <title>queues</title>
            <link>https://docs-archive.hpc.udel.edu/abstract/farber/runjobs/queues</link>
            <description>The job queues on Farber

Each investing-entity on a cluster an owner queue that exclusively use the investing-entity&#039;s compute nodes. (They do not use any nodes belonging to others.) Grid Engine allows those queues to be selected only by members of the investing-entity&#039;s group.</description>
            <author>anonymous@undisclosed.example.com (Anonymous)</author>
            <pubDate>Mon, 08 Oct 2018 20:01:57 +0000</pubDate>
        </item>
        <item>
            <title>runjobs</title>
            <link>https://docs-archive.hpc.udel.edu/abstract/farber/runjobs/runjobs</link>
            <description>Running applications on Farber

Introduction

The Grid Engine job scheduling system is used to manage and control the resources available to computational tasks.  The job scheduler considers each job&#039;s resource requests (memory, disk space, processor cores) and executes it as those resources become available.  The order in which jobs are submitted and a &lt;span style=&quot;color:#ffffff;background-color:#2fa4e7;padding:3px 7px !important;border-radius:4px;&quot;&gt;sidebar&lt;/span&gt;</description>
            <author>anonymous@undisclosed.example.com (Anonymous)</author>
            <pubDate>Thu, 09 Aug 2018 19:01:49 +0000</pubDate>
        </item>
        <item>
            <title>schedule_jobs</title>
            <link>https://docs-archive.hpc.udel.edu/abstract/farber/runjobs/schedule_jobs</link>
            <description>Scheduling Jobs on Farber

In order to schedule any job (interactively or batch) on a cluster, you must set your workgroup to define your cluster group or investing-entity compute nodes.

Interactive jobs (qlogin)

As discussed, an interactive job allows a user to enter a sequence of commands manually.  The following qualify as being interactive jobs:</description>
            <author>anonymous@undisclosed.example.com (Anonymous)</author>
            <pubDate>Tue, 27 Apr 2021 20:21:09 +0000</pubDate>
        </item>
        <item>
            <title>sidebar</title>
            <link>https://docs-archive.hpc.udel.edu/abstract/farber/runjobs/sidebar</link>
            <description>*  Home
	*  Caviness
	*  DARWIN
	*  Farber
				*  Request Account
				*  Connecting
				*  Storage
				*  Transfer Files
				*  Application Development
				*  Install Software
				*  Run Jobs
					*  Queues
					*  Schedule Jobs 
					*  Managing Jobs

				*  System Status

	*  Mills (Retired)
	*  Software
	*  Training
	*  Technical</description>
            <author>anonymous@undisclosed.example.com (Anonymous)</author>
            <pubDate>Thu, 15 Jul 2021 18:22:24 +0000</pubDate>
        </item>
    </channel>
</rss>
