Specifies whether the job scheduler should ensure that no other job runs on the same nodes as this job while this job runs.

A non-zero value or $true indicates that the job scheduler should ensure that no other job runs on the same nodes as this job while this job runs.

A value of 0 or $false indicates that this job can share compute nodes with other jobs.

Specifies whether the job scheduler should stop the job and fail the entire job immediately when a task in the job fails.

A non-zero value or $true indicates that the job scheduler should stop the job and fail the entire job immediately when a task in the job fails.

A value of 0 or $false indicates that the job scheduler should continue running the rest of the tasks in the job after any task in the job fails.

Specifies an HpcJob object that represents an existing job that you want to copy when you create the new job. Use the Get-HpcJob cmdlet to get an HpcJob object for an existing job. You cannot specify both the Job and the JobFile parameters.

Specifies the environment variables that you want to set in the context of the job and the values that you want to set for the environment variables. Specify the environment variables and values as a list of strings that have a format of environment_variable_name=value; for example, "MyVariable1=yes","MyVariable2=no". To unset an environment variable in the context of a job, leave out the value part of the string; for example, "MyVariable3=".

If you set or unset an environment variable for a job, that environment variable is also set or unset for each task in the job unless you override that environment variable setting for the task by specifying a new setting with the Env parameter when you call the Add-HpcTask cmdlet.

This parameter is supported only for Windows HPC Server 2008 R2.

Specifies the file name and path for a job XML file that contains settings to use for the job that you want to create. You cannot specify both the JobFile parameter and the Job parameters.

Specifies a list of features for which the job requires licenses, and the number of licenses required for each. Use a format of license_name1:number1,license_name2:number2,license_name3:number3,... for this list, for example, License1:10,License2:20,License3:12. The list has a maximum length of 160 characters.

Specifies the maximum number of cores that a node can have for the job scheduler to consider the node as a candidate node on which to run the job. The job will not run on a node that has more cores than the value that this parameter specifies. If all of the nodes in the cluster have more cores than the value you specify for this parameter, an error occurs when you submit the job.

Specifies the maximum amount of memory in megabytes (MB) that a node can have for the job scheduler to consider the node as a candidate node on which to run the job. The job will not run on a node that has more memory than the value that this parameter specifies. If all of the nodes in the cluster have more memory than the amount you specify for this parameter, an error occurs when you submit the job.

Specifies the minimum number of cores that a node can have for the job scheduler to consider the node as a candidate node on which to run the job. The job will not run on a node that has fewer cores than the value that this parameter specifies. If all of the nodes in the cluster have fewer cores than the value you specify for this parameter, an error occurs when you submit the job.

Specifies the minimum amount of memory in megabytes (MB) that a node can have for the job scheduler to consider the node as a candidate node on which to run the job. The job will not run on a node that has less memory than the value that this parameter specifies. If all of the nodes in the cluster have less memory than the amount you specify for this parameter, an error occurs when you submit the job.

Specifies a name to use for this job in command output and in the user interface. The maximum length for the name is 80 characters.

Specifies the list of node groups on which this job can run. The job scheduler only allocates resources to the job from nodes that belong to all of the node groups in the list.

If you specify values for the both NodeGroups and RequestedNodes parameters, the job runs only on the nodes in the list of nodes for the RequestedNodes parameter that also belong to all of the node groups in the list of node groups for the NodeGroups parameter.

Specifies whether the HPC Job Scheduler Service should send an email notification when the job ends. A nonzero value or $true indicates that the HPC Job Scheduler Service should send an email notification when then job ends. A value of 0 or $false indicates that the HPC Job Scheduler Service should not send an email notification when the job ends. A job ends and the notification is sent when the state of the job changes to Finished, Failed, or Canceled.

A cluster administrator must configure notification for the HPC cluster before you can receive an email notification about a job.

This parameter is supported only for Windows HPC Server 2008 R2.

Specifies whether the HPC Job Scheduler Service should send an email notification when then job starts. A nonzero value or $true indicates that the HPC Job Scheduler Service should send an email notification when then job starts. A value of 0 or $false indicates that the HPC Job Scheduler Service should not send an email notification when then job starts.

A cluster administrator must configure notification for the HPC cluster before you can receive an email notification about a job.

This parameter is supported only for Windows HPC Server 2008 R2.

Specifies the overall number of cores across the HPC cluster that the job requires, in the format [minimum-]maximum. The job runs on at least the minimum number of cores and on no more than the maximum. If you specify only one value, this cmdlet sets both the minimum and maximum number of cores to that value. If you specify a minimum value that exceeds the total number of cores available across the cluster, an error occurs when you submit the job.

The minimum and maximum values can only be positive integers or an asterisk (*). If you specify the minimum or maximum value as an asterisk, the scheduler automatically calculates the minimum or maximum number of cores at run time, based on the minimum and maximum number of cores for the tasks in the job.

You cannot specify the NumCores parameter if you also specify the NumNodes or NumSockets parameter.

Specifies the overall number of nodes across the HPC cluster that the job requires, in the format [minimum-]maximum. The job runs on at least the minimum number of nodes and on no more than the maximum. If you specify only one value, this cmdlet sets the minimum and maximum number of nodes to that value. If you specify a minimum value that exceeds the total number of nodes available across the cluster, an error occurs when you submit the job.

The minimum and maximum values can only be positive integers or an asterisk (*). If you specify the minimum or maximum value as an asterisk, the scheduler automatically calculates the minimum or maximum number of nodes at run time, based on the minimum and maximum number of nodes for the tasks in the job.

You cannot specify the NumNodes parameter if you also specify the NumCores or NumSockets parameter.

Specifies the overall number of sockets across the HPC cluster that the job requires, in the format [minimum-]maximum. The job runs on at least the minimum number of sockets and on no more than the maximum. If you specify only one value, this cmdlet sets the minimum and maximum number of sockets to that value. If you specify a minimum value that exceeds the total number of sockets available across the cluster, an error occurs when you submit the job.

The minimum and maximum values can only be positive integers or an asterisk (*). If you specify the minimum or maximum value as an asterisk, the scheduler automatically calculates the minimum or maximum number of socket at run time, based on the minimum and maximum number of sockets for the tasks in the job.

You cannot specify the NumSockets parameter if you also specify the NumCores or NumNodes parameter.

Specifies the order that the job scheduler should use to allocate nodes to the job, in the format primary_order[,secondary_order]. The primary_order and secondary_order portions of the value can be one of the following values:

* Memory

The job scheduler sorts the nodes by the amount of memory that they have available, and then first allocates the job to nodes with more memory.

* -Memory

The job scheduler sorts the nodes by the amount of memory that they have available, and then first allocates the job to nodes with less memory.

* Cores

The job scheduler sorts the nodes by the number of cores that they have available, and then first allocates the job to nodes with more cores.

* -Cores

The job scheduler sorts the nodes by the number of cores that they have available, and then first allocates the job to nodes with fewer cores.

When you specify a secondary order, the job scheduler sorts the nodes according to the primary order first. For subsets of nodes that have the same amount of the resource that the primary order specifies, the job scheduler then sorts the nodes within the subset by using the secondary sort order. For example, if you specify memory,-cores, the job scheduler sorts the nodes from the highest amount of memory to the lowest. For subsets of nodes that have the same amount of memory, the job scheduler uses the number of cores to specify the order, and it sorts the nodes that have the same amount of memory from the fewest number of cores to the most.

The primary order and secondary order must refer to different types of resources. For example, memory,-cores is a valid combination of primary and secondary sort orders. Combinations such as memory,-memory and -cores,-cores are not valid.

Specifies the priority for scheduling the job on a scale from 0 to 4000, with 0 as the lowest priority and 4000 as the highest. In addition to specifying the priority as a number between 0 and 4000, you can specify one of the following named priority values: Highest, AboveNormal, Normal, BelowNormal, and Lowest. These named priority values correspond to numeric priorities of 4000, 3000, 2000, 1000, and 0, respectively. You can also specify the priority as <named_value>+<offset> or <named_value>-<offset>. However, the priority value that results when the numeric equivalent of the <named_value> is substituted for the <named_value> still must be a value between 0 and 4000.

The job template that the job uses specifies permissions that affect who can specify elevated priorities.

The job scheduler places jobs with the same priority into the job queue in the order that users submit the jobs, unless a user requeues a job. If a user requeues a job, the job scheduler places that job first among the jobs with the same priority.

The values that are valid for this parameter have changed since Windows HPC Server 2008.

Specifies the percentage of the job that is complete. This value must be between 0 and 100.

If you do not set the value of this property, the HPC Job Scheduler Service calculates the progress based on the percentage of tasks that are complete for the job. When you set this property for a job, the HPC Job Scheduler Service does not continue to update this property, so you must continue to update the property.

This parameter is supported only for Windows HPC Server 2008 R2.

Specifies a custom status message that you want to display for the job. The maximum length for this string is 80 characters.

This parameter is supported only for Windows HPC Server 2008 R2.

Specifies a project name for the job that you can use for tracking jobs. The maximum length for the project name is 80 characters.

Specifies an array of names for the nodes on which the job can run. These nodes are candidates for the job, but not all of the nodes will necessarily run the job if the available resources on these nodes exceed the resources that the job requires. The job scheduler allocates the top nodes according to the value of the Orderby parameter until the allocated nodes meet the value that you specified with the NumCores, NumSockets, or NumNodes parameter.

If you do not specify the RequestedNodes parameter, the job scheduler considers all nodes as candidates that the job scheduler can allocate to the job.

If you specify values for both the RequestedNodes and NodeGroups parameters, the job runs only on the nodes in the list of nodes for the RequestedNodes parameter that also belong to all of the node groups in the list of node groups for the NodeGroups parameter.

Specifies the maximum amount of time the job should run. After the job runs for this amount of time, the job scheduler cancels the job.

You specify the amount of time in a format of [[days:]hours:]minutes. You can also specify "infinite" to indicate that the job can run for an unlimited amount of time.

If you specify only one part of the days:hours:minutes format, the cmdlet interprets the specified value as the number of minutes. For example, 12 indicates 12 minutes. If you specify two parts of the format, the command interprets the left part as hours and the right part as minutes. For example, 10:30 indicates 10 hours and 30 minutes.

You can use one or more digits for each part of the format. The maximum value for each part is 2,147,483,647.

Specifies whether the job continues to run and hold resources until the run-time limit expires or someone cancels the job.

A non-zero or $true value indicates that the job continues to run and hold resources until the run-time limit expires or someone cancels the job. If you specify a non-zero or $true value, you must specify minimum and maximum values for the NumCores, NumNodes, or NumSockets parameter, or an error occurs when you submit the job.

A value of 0 or false indicates that the job should stop and release its resources when all of the tasks in the job are complete.

Specifies the host name or IP address of the head node for the cluster on which you want to create the job. The value must be a valid computer name or IP address. If you do not specify the Scheduler parameter, this cmdlet uses the scheduler on the head node that the CCP_SCHEDULER environment variable specifies. To set this environment variable, run the following cmdlet:

Set-Content Env:CCP_SCHEDULER <head_node_name>

Specifies the name of the default template to use for the job. The maximum length for the name of a job template is 80 characters.

This cmdlet supports the common parameters: -Verbose, -Debug, -ErrorAction, -ErrorVariable, -OutBuffer, and -OutVariable. For more information, see about_CommonParameters

Creates a new job by using the settings in the job file at C:\JobFiles\SampleJob1.xml.

	Copy Code
New-HpcJob -JobFile "C:\JobFiles\SampleJob1.xml"

Creates a new job named Sample Job by using the default job template. This job has a run-time limit of 30 minutes.

	Copy Code
New-HpcJob -Name "Sample Job" -Template "Default" -Project "Cluster Testing" -RunTime 0:0:30

Creates a new job that is a copy of the job with an identifier of 47, but sets the priority of the new job to 3015 and specifies that the HPC Job Scheduler Service should send an email notification when the job starts and when the job ends.

	Copy Code
Get-HpcJob -id 47 | New-HpcJob -Priority "AboveNormal+15" -NotifyOnStart $true -NotifyOnCompletion $true

Creates a new job for which an environment variable named MyVariable1 is set to yes and the environment variable named MyVariable2 is unset within the context of the job. It also sets the progress percentage for the job to 15 and sets a status message for the job.

	Copy Code
New-HpcJob -JobEnv "MyVariable1=yes","MyVariable2=" -Progress 15 -ProgressMessage "Making management believe that we have done more than we really have."