<wsdl:documentation>
This operation submits a job. The JDL description of the job provided by the client is validated by the service, registered to the LB and finally passed to the Workload Manager. The unique identifier assigned to the job is returned to the client.
This operation assumes that all the work preparatory to the job (e.g. input sandbox upload, registration of input data to the Data Management service etc.) has been completed by the client. Usage of this operation (instead of jobRegister + jobStart) is indeed recommended when the job identifier is not needed prior to its submission (e.g. jobs without input sandbox or with a sandbox entirely available on a GridFTP server managed by the client).
The service supports submission of simple jobs, parametric jobs, partitionable jobs, DAGs and collections of jobs; the description is always provided through a single JDL description (see "GLite JDL Attributes" document for details).
When a clients requests for submission of a complex object, i.e. parametric and partitionable jobs, DAGs and collections of jobs (all those requests represent in fact a set of jobs), the operations returns a structure containing the main identifier of the complex object and the identifiers of all related sub jobs.
Input: string containing the job jdl representation.
Input: string containing the Id of the delegated proxy associated to the job.
Output: no output.
Faults:
AuthenticationFault: a generic authentication problem occured.
AuthorizationFault: client is not authorized to perform this operation.
InvalidArgumentFault: the provided job JDL expression is not valid.
GenericFault: another problem occured.
</wsdl:documentation>