TaskType enumeration

Defines how to run the command for a task.

Syntax

typedef enum  { 
  TaskType_Basic            = 0,
  TaskType_ParametricSweep  = 1,
  TaskType_NodePrep         = 2,
  TaskType_NodeRelease      = 3,
  TaskType_Service          = 4
} TaskType;

Constants

• TaskType_Basic
  Runs a single instance of a serial application or a Message Passing Interface (MPI) application. An MPI application typically runs concurrently on multiple cores, and it can span multiple nodes. This task type is the default.

• TaskType_ParametricSweep
  Runs a command a specified number of times as indicated by the start, end, and increment values, generally across indexed input and output files. The steps of the sweep may or may not run in parallel, depending on the resources that are available on the HPC cluster when the task is running.

• TaskType_NodePrep
  Runs a command or script on each compute node as it is allocated to the job. The Node Prep task runs on a node before any other task in the job. If the Node Prep task fails to run on a node, then that node is not added to the job.

• TaskType_NodeRelease
  Runs a command or script on each compute node as it is released from the job. Node Release tasks run when the job is canceled by the user or by graceful preemption. Node Release tasks do not run when the job is canceled by immediate preemption.

• TaskType_Service
  Runs a command or service on all resources that are assigned to the job. New instances of the command start when new resources are added to the job, or if a previously running instance exits and the resource that the previously running instance was running on is still allocated to the job. A service task continues to start new instances until the task is canceled, the maximum run time expires, or the maximum number of instances is reached. A service task can create up to 1,000,000 subtasks. Tasks that you submit through a service-oriented architecture (SOA) client run as Service tasks. You cannot add a Basic task or a Parametric Sweep task to a job that contains a Service task.

Remarks

The following properties do not apply to tasks that you start on a per-resource basis, and thus you cannot set these properties if you set the ISchedulerTask::Type property to NodePrep, NodeRelease, or Service:

• MaximumNumberOfNodes

• MinimumNumberOfNodes

• MaximumNumberOfCores

• MinimumNumberOfCores

• MaximumNumberOfSockets

• MinimumNumberOfSockets

• RequiredNodes

• IsExclusive

• IsRerunnable

• DependsOn

• EndValue

• IncrementValue

• IsParametric

• StartValue

You cannot add a Basic task or a Parametric Sweep task to a job that contains a Service task.

Requirements

See also

ISchedulerTask::Type