glite-ce-job-submit

Section: User Commands (1)
Index
 

NAME

glite-ce-job-submit - Allows the user to submit a job for execution on a CREAM based CE  

SYNOPSIS

glite-ce-job-submit --resource CEId [options] <jdl_file>  

DESCRIPTION

glite-ce-job-submit is the command for submitting jobs to CREAM based Computing Elements. glite-ce-job-submit requires as mandatory inputs:

o the identifier of the CREAM CE, specified using the option --resource (-r), where the job has to be submitted;

o a job description (JDL) file in which job characteristics and requirements have been specified via a CREAM JDL expression.

The job description file given in input to this command is syntactically checked and default values are assigned to the not provided mandatory attributes in order to create a meaningful class-ad. The resulting ad is then sent to the CREAM CE.

Upon successful submission, this command returns to the user the submitted CREAM job identifier (jobId), a string that identifies unambiguously the job, that can be later used as a handle to perform monitor and control operations on the job.

The format of the CREAM jobId is as follows:

https://<CREAM_full_hostname>:<port>/CREAM<unique_string&gt;

It is possible to redirect the returned jobId to an output file using the --output (-o) option. If the file already exists, the user is asked if she wants to overwrite the file, or if she prefers to abort the operation.

The --resource (-r) directive must be used to target the job submission to a specific CREAM CE, identified by its identifier CEId. The CREAM CE identifier is a string that unambiguously identifies a CE CREAM service belonging to the Grid. The standard format for a CREAM CEId is:

<full-hostname>:<port-number>/cream-<service>-<queue-name>

where <service> identifies the underlying resource management system (e.g. lsf, pbs, etc.).

The submitted job is given the delegated credentials of the user who submitted the job: these credentials can then be used when operations requiring security support (e.g. gridftp file transfers) has to be performed by the job. It is possible to rely on credentials previously delegated with the glite-ce-delegate-proxy command or it is possible to ask the ``automatic'' delegation of the same credentials used during the submission operation. In the former case the --delegationId (-D) option must be specified, while in the latter case the --autm-delegation (-a) option must be used. Please note that one (and only one) among these two options must be specified.

 

OPTIONS

--help, -h
Displays command usage.

--conf file_name, -c file_name
Specifies the user specific configuration file.

--resource ce_id, -r ce_id
Specifies that the job has to be submitted to the CREAM CE identified by the specified ce_id. Standard format for the CREAM CEId is:

<full hostname>:<port number>/cream-<service>-<queue name>

where <service> specifies the underlying local resource management system (e.g. lsf, pbs, etc.)

--autm-delegation, -a
Specifies that the proxy credentials that have to be delegated are the ones used for this job submission.

--delegationId ID, -D ID
Forces the submitted job to use previously delegated (via the command glite-ce-delegate-proxy) user credentials, identified with the specified ID.

--donot-verify-ac-sign, -A
Allows the execution of the command even if the VO voms server certificate is not installed.

--vo VO_name, -V VO_name
Specifies the Virtual Organisation the user belongs to. This option is ignored if the user issued the command using a VOMS proxy: in this case in fact the VO to be considered is the one specified in the VOMS proxy.

--output file_name, -o file_name
Writes the generated jobId assigned to the submitted job in the file specified by file_name. file_name can be either a simple name or an absolute path on the submitting machine. In the former case the file file_name is considered in the current working directory.

--noint, -N
If this option is specified every interactive question to the user is skipped, and default values (yes; all: consider all jobs of the given list) will be considered.

--nomsg, -n
This option makes the command print on the standard output only the jobId generated for the job if submission was successful (or error messages in case of failure). Therefore any warning or info message is suppressed if this option is used.

--debug, -d
When this option is specified, debugging information is displayed on the standard output and written also into the file glite-ce-job-submit_CREAM_<username>_<date>_<time>.log file under (by default) the /tmp/glite_cream_cli_logs directory.

--logfile file_name, -l file_name
When this option is specified, a command log file (whose pathname is file_name) is created.

--version, -v
Displays the version of the CREAM CLI software.

 

EXIT STATUS

glite-ce-job-submit exits with a status value of 0 (zero) upon success, and >0 (greater than zero) upon failure.

 

EXAMPLES

glite-ce-job-submit -a -r grid005.pd.infn.it:8443/cream-lsf-grid02 myjob1.jdl

where myjob1.jdl is e.g. as follows:

[
  JobType = "Normal";
  Executable = "sum.exe";
  StdOutput="out.out";
  StdError="err.err";
  Environment={"CMSVER=321"};
  InputSandbox={"file:///home/user/sum.exe", "otherfile"};
  InputSandboxBaseUri="gsiftp://se1.pd.infn.it/cmssw";
  OutputSandbox={"out.out", "err.err", ``hist.out''};
  OutputSandboxBaseDestUri="gsiftp://se2.pd.infn.it/myfiles";
 ]

 

SEE ALSO

glite-ce-delegate-proxy


 

Index

NAME
SYNOPSIS
DESCRIPTION
OPTIONS
EXIT STATUS
EXAMPLES
SEE ALSO

This document was created by man2html, using the manual pages.
Time: 10:51:41 GMT, April 29, 2011 -- MassimoSgaravatto - 2011-04-29


This topic: CREAM > WebHome > UserDocumentation > UserGuide > GliteCeJobSubmitMan
Topic revision: r1 - 2011-04-29 - MassimoSgaravatto
 
This site is powered by the TWiki collaboration platformCopyright © 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback