Usage: globus-job-run [-help|-usage] print usage and exit [-version] print version and exit Usage: globus-job-run [-dumprsl] output RSL, don't run job [-dryrun] verify RSL, don't run job [-verify] perform dryrun, then run job [-file file] read rest of arguments from file [-stdin [-l|-s] file] global input default [-stdout [-l|-s] file] global output default [-stderr [-l|-s] file] global error output default [-env name=value]... global environment default [-args [jobarg]...] job-wide arguments [ host-clause | job description -: host-clause...] subjob description (multi-req) host-clause syntax: { contact string only the hostname is required. [-np N] number of processing elements [-count N] same as -np [-host-count nodes] number of SMP nodes (IBM SP) [-m[axtime] minutes] time to allocate for the job [-p[roject] projectID] scheduling/accounting project ID [-q[ueue] queueID] scheduling/accounting queue ID [-d[ir] directory] working directory [-env name=value]... environment binding [-stdin [-l|-s] file] input [-stdout [-l|-s] file] output [-stderr [-l|-s] file] error output [-x rsl-clause] RSL extension capability [-l|-s] executable [args...] executable and clause arguments Job stdin defaults to /dev/null. Job stdout/stderr default to stdout/stdout of globus-job-run. The file modifiers -l and -s specify different filespaces: -l[ocal] file is relative to working directory of job (DEFAULT) -s[tage] file relative to job request is staged to job host The working directory of the submitted job defaults to $HOME. Valid forms of the contact string are: hostname hostname:port hostname:port/service hostname/service hostname:/service hostname::subject hostname:port:subject hostname/service:subject hostname:/service:subject hostname:port/service:subject More than one host-clause can be specified, in which case the job runs on all of the hosts simultaneously. The host clause begins with '-:' for a multi-request, and the contact string of the remote resource for a single request. It allows any of the specified options in any order. The first unrecognized (non-flagged) term is treated as the executable, with arguments following immediately after. In the multi-request case, arguments may be specified specifically for each host-clause by appending them after the name of the executable, or job-wide with the -args flag. In either case, arguments continue until the end of the command-line or until the next '-:' flag signifying a new host-clause. Two '-:' flags in a row are interpreted as an escaped '-:' and the host- clause continues until the next unpaired '-:' flag or end of input. If more than one setting is defined (such as two -stdin definitions), the setting defined last on the command line will be used.