ECACCE...-SUBMIT(1p)

📦
version 6.3.1 · 2 versions
, in ubuntu resolute, ubuntu stonking

💖 ECACCE...-SUBMIT(1p) — bestie, it's the job submitter 💖

okay so this is ecaccess-job-submit, and it lives in the User Contributed Perl Documentation manual section, and no cap it is THE glow-up for getting your script onto ECaccess. one job, one script, infinite main character energy. let's go 🦋

✨ NAME ✨

ecaccess-job-submit — Submit a new ECaccess Job 👑

🌸 SYNOPSIS 🌸

ecaccess-job-submit -version|-help|-manual

ecaccess-job-submit [-debug] [-distant] [-bufsize length]
[-scheduledDate date] [-noDirectives] [-gateway name] [-remote location]
[-transferOutput] [-transferError] [-transferInput] [-keep] [-eventIds
list] [-sterr2Stdout] [-noRenew] [-mailTo email] [-onStart] [-onSuccess]
[-onFailure] [-onRetry] [-jobName name] [-manPage content] [-lifeTime
days] [-retryCount number] [-retryFrequency frequency] [-queueName name]
source

💅 DESCRIPTION 💅

So basically, this lets you submit the source script to either the default ECaccess batch queue or whichever ECaccess batch queue you picked with the -queueName option. and how do you find a queue name, you ask? bestie, run ecaccess-queue-list — and heads up, the default queue is just the first one in that list. periodt. ✨

there's also a whole special service (peep the -eventIds option 👀) that lets you automatically submit jobs to run when certain points in the daily ECMWF operational forecast suite have been reached. the main purpose? making sure certain data is actually there before, like, you go submit a MARS request. rude to ask for data that doesn't exist yet, honestly. these events correspond to the different stages when the ECMWF operational activity has produced certain data or products, and you can grab the list of events with the ecaccess-event-list command. 🌈

and here's the cute part: to make migrating from the old ECtools (ecjreq/ecjput commands) easier, the equivalent options can be set using their old names too — like -at for -scheduledDate. this should limit the script modifications you have to make for job submissions, so your old scripts don't have to go through a whole rebrand. 💖

🎀 ARGUMENTS 🎀

  • source — the name of the file which contains the job input script. and depending on the -distant option, this file is either at ECMWF or local to your workstation. choose your fighter. 💫

👑 OPTIONS 👑

one bullet per option, and yes, every single one is here because we don't skip. slay.

  • -distant — by default the source is specifying a file which is local to your workstation. using this option lets you submit a script which is already at ECMWF. no upload required, we're already there. ✨
  • -bufsize length — specify the length of the buffer (in bytes) which is used to upload the file. the larger the buffer, the smaller the number of http/s requests. by default a buffer of 524288 bytes (512KB) is used. note that this option only applies for local scripts (so not with -distant). 📦
  • -at, -scheduledDate date — lets you specify the start date for the Job. by default the job will start as soon as possible. the format for the date is 'yyyy-MM-dd HH:mm'. ⏰
  • -nd, -noDirectives — lets you submit a job with no scheduler directives. some default directives will be added to your input script to allow processing the job. 🚫
  • -tg, -gateway name — this is the name of the target ECaccess Gateway for the transfers. it's by default the Gateway you are connected to. to get the name of your current Gateway you can use the ecaccess-gateway-name command. when using the commands at ECMWF the default Gateway is always "boaccess.ecmwf.int". 🌉
  • -tr, -remote location — defines the target ECtrans location in the format association-name[@protocol]. 📍
  • -to, -transferOutput — request the transfer of the job standard output to the gateway and remote location defined in the -gateway and -remote options. 📤
  • -te, -transferError — request the transfer of the job error output to the gateway and remote location defined in the -gateway and -remote options. 😭
  • -ti, -transferInput — request the transfer of the job input to the gateway and remote location defined in the -gateway and -remote options. 📥
  • -tk, -keep — lets you keep the transfers requests in the spool. don't throw it away, bestie. 🫶
  • -ni, -eventIds list — lets you give a list of event-identifiers to subscribe to with the Job. the list should be separated by ';' or ','. only one job will be launched when all the events in the list have been reached. and to submit the same job to multiple events, you'll need to submit the job to each event separately — no bundling, sorry. 🦋
  • -eo, -sterr2Stdout — force redirection of the job standard error output (stderr) to the job standard output (stdout). merging the vibes. 🔀
  • -ro, -noRenew — the job subscriptions to events will not be renewed. 🚫🔄
  • -mu, -mailTo email — defines the target email address (default: current ECMWF user identifier). 📧
  • -mb, -onStart — lets you send a mail when the execution/transfer begins. 🏁
  • -me, -onSuccess — lets you send a mail when the execution/transfer ends. ✅
  • -mf, -onFailure — lets you send a mail when the execution/transfer fails. 💀
  • -mr, -onRetry — lets you send a mail when the execution/transfer retries. 🔁
  • -queueName name — the name of the ECaccess batch queue to submit the job to. 🎯
  • -jn, -jobName name — lets you specify a name for the new Job (other than the Job Identifier). if no name is specified then the name of the input script is used. ✍️
  • -mp, -manPage content — lets you give the man page content which will be displayed to the ECMWF operators in case of problems with your Job (e.g. what to do or who to contact). leave them a lil note 💌
  • -lt, -lifeTime days — lets you specify the job input/output life time in days. the default is 7 days. ⌛
  • -rc, -retryCount number — defines the number of retries. the default is 0. 🔂
  • -rf, -retryFrequency frequency — defines the frequency of retries in seconds. the default is 600 seconds. ⏱️
  • -version — display version number and exits. 👋
  • -help — print a brief help message and exits. 🙋
  • -manual — prints the manual page and exits. 📖
  • -retry count — number of SSL connection retries per 5s to ECMWF. this parameter only applies to the initial SSL connection initiated by the command to the ECMWF server. it does not apply to all the subsequent requests made afterward, as it is mainly targeting errors that can happen from time to time during the SSL handshake. default is no retry. 🤝
  • -debug — display the SOAP and SSL messages exchanged. peek behind the curtain, bestie 🫣

🌟 EXAMPLES 🌟

ecaccess-job-submit -noDirectives ./test.txt

transfer the local file test.txt to your ECMWF spool and submit the job to the default ECaccess batch queue. the source does not have any directives. iconic, honestly. 🔥

🔗 SEE ALSO 🔗

ecaccess-queue-list, ecaccess-event-list, ecaccess-job-delete, ecaccess-job-get, ecaccess-job-list ecaccess-job-restart and ecaccess.

and that's the whole page, bestie 💜 this one's brought to you by perl v5.40.1, dated 2025-10-22, filed under ECACCE...-SUBMIT(1p). go submit something legendary. mwah 🎀✨

📦 where this page comes from