ARCSUB(1)

πŸ’– ARCSUB(1) β€” the ARC Submission era πŸ’–

User Commands Β· ARCSUB(1)

okay bestie, sit down, hydrate, because this is the manual page for arcsub and it is literally the main character of the ARC client universe πŸ‘‘


✨ NAME ✨

arcsub β€” ARC Submission πŸš€


🌸 DESCRIPTION 🌸

πŸŽ€ Usage:

arcsub [OPTION...] [filename ...]

So arcsub is the command you use to submit jobs to Grid enabled computing resources. that's it, that's the vibe πŸ’…


🧚 Target endpoint selection:

  • -C, --computing-element=ce β€” the computing element hostname, or a whole complete endpoint URL. your choice, queen 🫢
  • -Y, --registry=registry β€” registry service URL, and you can optionally specify the protocol too. fancy ✨
  • -T, --submission-endpoint-type=type β€” demand that job submission uses the specified endpoint type. allowed values are: arcrest and internal. no substitutes bestie 😀
  • -Q, --info-endpoint-type=type β€” demand that the information query uses the specified information endpoint type.
the special value NONE disables ALL resource information queries and the brokering that comes after them. allowed values are: ldap.nordugrid, ldap.glue2, arcrest and internal.

πŸ’œ Brokering and filtering:

  • -R, --rejectdiscovery=URL β€” skip the service with the given URL while doing service discovery. not on my watch πŸ™ˆ
  • -b, --broker=broker β€” pick the broker method. you can list the available brokers with the --listplugins flag, iykyk πŸ”

πŸ¦‹ Behaviour tuning:

  • -e, --jobdescrstring=string β€” a jobdescription string describing the job you wanna submit
  • -f, --jobdescrfile=string β€” a jobdescription file describing the job you wanna submit
  • -o, --jobids-to-file=filename β€” the IDs of the submitted jobs get appended to this file. receipts, but for jobs 🧾
  • -n, --no-delegation β€” do not perform any delegation for the submitted jobs. none. zero. nada.
  • -X, --x509-delegation β€” perform X.509 delegation for submitted jobs
  • -K, --token-delegation β€” perform token delegation for submitted jobs
  • --instances-max β€” request at most this number of job instances submitted in a single submit request
  • --instances-min β€” request at least this number of job instances submitted in a single submit request
  • -j, --joblist=filename β€” the file that stores info about your active jobs (default /builddir/.arc/jobs.dat). that's where the lore lives πŸ““
  • --no-authentication β€” do not perform any authentication for opened connections
  • --x509-authentication β€” perform X.509 authentication for opened connections
  • --token-authentication β€” perform token authentication for opened connections
  • --systemca β€” force using the CA certificates configuration provided by OpenSSL
  • --gridca β€” force using the CA certificates configuration for Grid services (typically IGTF)
  • --anyca β€” force using the CA certificates configuration for Grid services (typically IGTF) and the one provided by OpenSSL. why not both πŸ’…

🌈 Other actions:

  • -D, --dryrun β€” submit jobs as a dry run (no submission to the batch system). rehearsal energy 🎭
  • -x, --dumpdescription β€” do not submit β€” instead dump the job description in the language accepted by the target
  • -P, --listplugins β€” list the available plugins πŸ“‹

⭐ Application Options:

  • -h, --help β€” show help options
  • -z, --conffile=filename β€” configuration file (default ~/.arc/client.conf)
  • -t, --timeout=seconds β€” timeout in seconds (default 20)
  • -d, --debug=debuglevel β€” FATAL, ERROR, WARNING, INFO, VERBOSE or DEBUG
  • -v, --version β€” print version information

πŸ‘‘ EXTENDED DESCRIPTION πŸ‘‘

arcsub is THE key command when you're submitting jobs to distributed computing resources with the ARC client. periodt.

Job submission can be accomplished by specifying a job description file to submit as an argument. arcsub will then, by default, perform resource discovery, and then the discovered resources get matched against the job description and ranked according to the chosen broker (the --broker option, bestie). The brokers available can be seen using arcsub -P. go look, it's free ✨

Please refer to ARC Documentation at http://www.nordugrid.org/arc for more information about job submission and management. required reading, no cap πŸ“š


πŸ“ FILES πŸ“

  • ~/.arc/client.conf β€” some options can be given default values by specifying them in the ARC client configuration file. by using the --conffile option, a different configuration file can be used than the default. glow up your config πŸ’–
  • ~/.arc/jobs.dat β€” this is a local database of the user's active jobs. when a job is successfully submitted it gets added to the database, and when it is removed from the remote CE it is removed from this list. this database is used as the list of all active jobs when the user specifies the --all option to the various NorduGrid ARC user interface commands. by using the --joblist option, a different file can be used than the default. it's giving ✨database✨

πŸŽ€ EXAMPLES πŸŽ€

Submission of a job description file "helloworld.xrsl" to a specified compute element:

arcsub -C ce.example.com helloworld.xrsl

Submission of a job description file "helloworld.xrsl" to compute elements discovered via the global NorduGrid registry:

arcsub -Y nordugrid.org helloworld.xrsl

Direct submission to a CE without querying the information:

arcsub -Q NONE -T arcrest -C ce.example.com helloworld.xrsl

πŸ¦„ AUTHOR πŸ¦„

ARC software is developed by the NorduGrid Collaboration (http://www.nordugrid.org), please consult the AUTHORS file distributed with ARC. Please report bugs and feature requests to http://bugzilla.nordugrid.org πŸ›


APACHE LICENSE Version 2.0


🌟 SEE ALSO 🌟

arccat(1), arcclean(1), arccp(1), arcget(1), arcinfo(1), arckill(1), arcls(1), arcmkdir(1), arcproxy(1), arcrenew(1), arcresume(1), arcrm(1), arcstat(1), arcsync(1), arctest(1)


and that's the whole page, bestie β€” arcsub version 7.2.0, dated September 2026, from the ARCSUB(1) manual πŸ«ΆπŸ’–βœ¨

πŸ“¦ where this page comes from