User`s guide

Program Communicating Jobs for a Generic Scheduler
8-7
Program Communicating Jobs for a Generic Scheduler
In this section...
“Introduction” on page 8-7
“Code in the Client” on page 8-7
Introduction
This section discusses programming communicating jobs using the generic scheduler
interface. This interface lets you execute jobs on your cluster with any scheduler you
might have.
The principles of using the generic scheduler interface for communicating jobs are the
same as those for independent jobs. The overview of the concepts and details of submit
and decode functions for independent jobs are discussed fully in “Program Independent
Jobs for a Generic Scheduler”.
The basic steps follow.
Code in the Client
Configure the Scheduler Object
Coding a communicating job for a generic scheduler involves the same procedure as
coding an independent job.
1
Create an object representing your cluster with parcluster.
2
Set the appropriate properties on the cluster object if they are not defined in the
profile. Because the scheduler itself is often common to many users and applications,
it is probably best to use a profile for programming these properties. See “Clusters
and Cluster Profiles” on page 6-14.
Among the properties required for a communicating job is
CommunicatingSubmitFcn. You can write your own communicating submit and
decode functions, or use those come with the product for various schedulers and
platforms; see the following section, “Supplied Submit and Decode Functions” on
page 8-8.