No support for parametric jobs. Also known as array jobs. GT4 Currently
supports: single, multi, mpi and condor. The enhancement would submit one job
which represents N sub-jobs, also known as tasks or steps. This would invoke the
same executable with different input parameters, each sub-job is passed a
number: 0 to N-1 along with its arguments (future enhancements could extend this
to be multiple ranges each with different start, end, and increment/decrement).
Each job is not complete until all sub-jobs complete.

We have added the new job type “parametric” value in RSL’s job_description.xsd
for SimpleType JobTypeEnumeration to allow <jobType>parametric<jobType>. We have
used the <count> element to represent the number of sub jobs to be submitted for
aggregate job. Note: LSF/Symphony allows a comma-separated index-list of
start[-end[:step]] where end defaults to 1000, and step to 1, but we do not need
this level of detail initially. We added a stanza in each globus-job-scheduler
script to decode job type and then use count to create a parametric job.

Note there has been some previous discussion and a bugzilla entries for this
such as 3384 and 3569.

We have locally modified GT4.0.0 to accomplish this and would like to discuss
the potential if this could be integrated back into the main-line code base.