glite-ce-job-suspend

Section: User Commands (1)
Index

NAME

glite-ce-job-suspend - Suspends one or more jobs running or idle on CREAM based CEs.

SYNOPSIS

glite-ce-job-suspend [options] <jobId1> <jobId2> ... <jobIdn>

DESCRIPTION

The command glite-ce-job-suspend suspends jobs running or idle on CREAM based CEs.

glite-ce-job-suspend can suspend one or more jobs: the jobs to be suspended are identified by their job identifiers (job Ids returned by the glite-ce-job-submit command) provided as arguments to the command and separated by a blank space.

It has to be remarked that a job can be suspended only by his/her owner (i.e. the user who submitted it). Only the ``super-users'' can suspend jobs submitted by other persons.

Before actually suspending the specified jobs, the command prompts the user for confirmation.

Only jobs in RUNNING, REALLY-RUNNING or IDLE status can be suspended even if some other constraints can be imposed by the underlying resource manager system (e.g. PBS doesn't allow suspending running jobs). For all the other job states the suspend request will result in a failure. An error message is of course printed also if a specified jobId doesn't exist.

If the --all option is specified, all the jobs submitted to the interested CREAM CE (whose endpoint must be specified with the --endpoint option, which is mandatory in this case), owned by the user issuing the command, are requested to be suspended. When the command is launched with the --all option, neither can a jobId be specified nor can the --input option be used.

The --input option permits to specify a file (file_name) that contains the jobIds to be suspended. This file must be the one generated with the --output option of the glite-ce-job-submit or glite-ce-job-list commands. When using this option the user is interrogated for choosing among all, one or a subset of the listed job identifiers. If the file file_name does not represent an absolute path the file will be searched in the current working directory.

When a glite-ce-job-suspend request is issued, the host name and the port number to be used to contact the CREAM service(s) are retrieved from the specified jobIds (which encompass this information) unless the --endpoint option is used. As stated before, the --endpoint option is mandatory if the --all option is used.

OPTIONS

--help, -h

Displays command usage.

--conf file_name, -c file_name

Specifies the user specific configuration file.

--all, -a

Suspends all known jobs in the specified (with the --endpoint option, which is mandatory in this case) CREAM CE, owned by the user issuing the command. This option can't be used either if one or more jobIds have been specified or if the --input option has been specified.

--endpoint host[:port], -e host[:port]

Selects the endpoint of the CREAM CE to send the suspend request to. If this option is not specified, the endpoint will be extracted from the JobID strings. The endpoint must have the format <host>:<port> or <host>.

--donot-verify-ac-sign, -A

Allows the execution of the command even if the VO voms server certificate is not installed.

--input file_name, -i file_name

Suspends jobs whose Ids are contained in the file file_name. This option can't be used if the --all option has been specified as well.

--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

When this option is specified, any warning or info message is suppressed.

--debug, -d

When this option is specified, debugging information is displayed on the standard output and written also into the file glite-ce-job-suspend_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-suspend exits with a value of 0 if the suspend operation succeeds, >0 if errors occurred.

EXAMPLES

1. > glite-ce-job-suspend https://grid005.pd.infn.it:8443/CREAM116j9457d
requests to suspend the specified job. After a while the job status will become HELD:

> glite-ce-job-status -L 0 https://grid005.pd.infn.it:8443/CREAM116j9457d
**** JobID=[https://grid005.pd.infn.it:8443/CREAM116j9457d]

Status=[HELD]

2.If it is requested to suspend a job which is not running or idle, an error message will be returned, as in the following example:

> glite-ce-job-suspend https://grid005.pd.infn.it:8443/CREAM216h94452d
Are you sure you want to suspend specified job(s) [y/n]: y

20050902 10:46:29 - FAULT: FAULT: - SOAP-ENV:Server.generalException - MethodName=[jobSuspend] - FaultCause=[Invalid job ID list] - Description=[The following jobs have a status not compatible with the jobSuspend command: https://grid005.pd.infn.it:8443/CREAM216h94452d] - ErrorCode=[1]

3. > glite-ce-job-suspend --endpoint grid005.pd.infn.it:8443 --all --noint
requests to suspend all jobs, submitted to the specified CREAM CE, owned by the user issuing the command.