Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

Is there an easier way to set the RUSH_JOBID environment variable?

easier Environment
0
Posted

Is there an easier way to set the RUSH_JOBID environment variable?

0

You can use eval `submit` to automatically set it, or a simple alias to set it manually. However, cutting and pasting the ‘setenv’ command is not so hard. Some people like to use this alias to make it easy to set new jobid variables: # Put this in your .cshrc alias jid ‘setenv RUSH_JOBID “\!*”‘ Then you can use it on the command line to set one or more jobids: erco@tahoe % jid tahoe.932 tahoe.933 If you want to have the RUSH_JOBID variable set automatically in your shell whenever you invoke your submit script, then use ‘eval’: erco@tahoe % eval `my_submit_script` …the shell automatically parses the ‘setenv RUSH_JOBID’ command rush prints on stdout when a job is successfully submitted. Error messages are not affected by ‘eval’, so you don’t have to worry about losing error messages when using this technique.

Related Questions

What is your question?

*Sadly, we had to bring back ads too. Hopefully more targeted.

Experts123