The submitted jobs do not cause the interactive job to stop or pause.
They are, once submitted, independent of the mother ship.
As for the requirement that JobA finish before JobB runs, the usual way
to do that is to be sure that they are both submitted to the same job
queue that allows only one job to run at a time. Another way to insure
this, regardless of job queue settings, is to have JobA submit JobB as
its last step, rather than having the interactive job do it.
This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact