<div dir="ltr"><div>You can check the sarchive tool.</div><div><br></div><a href="https://archive.fosdem.org/2020/schedule/event/job_script_archival/">https://archive.fosdem.org/2020/schedule/event/job_script_archival/</a><div><a href="https://github.com/itkovian/sarchive">https://github.com/itkovian/sarchive</a><br></div><div><br></div><div>Regards,</div><div>Pablo.</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Jul 16, 2021 at 8:29 PM Paul Edmon <<a href="mailto:pedmon@cfa.harvard.edu">pedmon@cfa.harvard.edu</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Not in the current version of Slurm.  In the next major version long <br>
term storage of job scripts will be available.<br>
<br>
-Paul Edmon-<br>
<br>
On 7/16/2021 2:16 PM, David Henkemeyer wrote:<br>
> If I execute a bunch of sbatch commands, can I use sacct (or something <br>
> else) to show me the original sbatch command line for a given job ID?<br>
><br>
> Thanks<br>
> David<br>
<br>
</blockquote></div>