PDS Structure

A PDS file begins with the keyword job (a synonym for Service) and ends with the keyword end. Supply a name after job to identify the Service. Two types of elements can occur in between job and end: parameter declarations, which assign values to variables, and blocks, which describe features or statements of the Service. The options, schedule, and discriminator blocks describe various facets of the Service, such as when to run it and which Engines can accept its tasks. The other five blocks describe statements to be executed at different phases of the Service. All blocks are optional except for the task block. Multiple job blocks are also defined in a single PDS file, and they run sequentially by default. You can also run the pdriver command with the -parallel flag to run multiple jobs in one PDS file in parallel.

Structure of a PDS file

 

Details of the structure of a PDS file:

job jobname
options
    onerror ( fail | retry | ignore )        
    maxFailedTaskRetries = val (default: 3)
    enableBlacklisting = true|false
    jobPriority = <val> (default: 5)
    autoCancelMode = "always" | "never" | "libloadfailure"
    jobOption "key" "val"
    jobDescription "key" "val"
end 
<variable assignment>
schedule
    properties
    [email = "address"]
end
discriminator
    [ affects
        properties
      end ]
    properties
end
prejob
    statements
end
pretask
    statements
end
task taskcount
    statements
end
posttask
    statements
end
postjob
    statements
end
end