ISchedulerJob.ExpandedPriority Property

Gets or sets the priority of the job, using the expanded range of priority values in Windows HPC Server 2008 R2.

Namespace: Microsoft.Hpc.Scheduler
Assembly: Microsoft.Hpc.Scheduler (in Microsoft.Hpc.Scheduler.dll)

Dim instance As ISchedulerJob
Dim value As Integer

value = instance.ExpandedPriority

instance.ExpandedPriority = value

int ExpandedPriority { get; set; }
/** @property */
int get_ExpandedPriority ()

/** @property */
void set_ExpandedPriority (int value)

function get ExpandedPriority () : int

function set ExpandedPriority (value : int)

Property Value

An Int32 between 0 and 4000 that indicates the priority for the job, where 0 is the lowest priority and 4000 is the highest.

Use the fields of the ExpandedPriority class to specify the numeric equivalents in Windows HPC Server 2008 R2 for named priority values such as BelowNormal and Highest. You can add or subtract values from these constants to specify an offset from the named value. For example, Normal + 500.

If you set the value of ExpandedPriority to a value less than 0 or a value greater than 4000, an exception occurs.

If you set the values of both the ExpandedPriority and Priority properties, the property that you set last determines the priority of the job. When you set the value of one of these properties, the value of the other property is automatically updated to the equivalent value.

The Default job template sets the default value to Normal.

The job template for the job determines that values the a user can set for ExpandedPriority without administrative privileges. A cluster administrator cannot submit a job with an ExpandedPriority that the job template does not allow, but when the job is in the queued or running state, the cluster administrator can set ExpandedPriority to any value between 0 and 4000, even if the job template does not allow that expanded priority.

Server resources are allocated to jobs based on job priority, except for backfill jobs. Jobs can be preempted if the CanPreempt property is true; otherwise, jobs run until they finish, fail, or are canceled.

Within a job, tasks receive resources based on the order in which they were added to the job. If a core is available, the task will run.

Platform Note: This property was introduced in Windows HPC Server 2008 R2 and is not supported in previous versions.

Any public static (Shared in Visual Basic) members of this type are thread safe. Any instance members are not guaranteed to be thread safe.

Development Platforms

Windows XP, Windows Vista, Windows 7, Windows 8, Windows Server 2003, Windows Server 2008, Windows Server 2008 R2, Windows Server 2012

Target Platforms

Windows XP, Windows Vista, Windows 7, Windows 8, Windows Server 2003, Windows Server 2003 R2, Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, with HPC Pack Client Utilities

Build Date: