puzzled two ways: why not use the numeric jobid,
I don't know the job id before the actual job submission. Hence I would like to
get some kind of place holder, and `scommit` the job later with the actual
resource requirements as comments in an usual jobscript.
OK, in that case, you can make
> Am 07.05.2019 um 16:00 schrieb Mark Hahn :
>
>> Some cluster sites need the creation of a workspace for the job in a
>> scratch area before the actual job submission, and on the other hand they
>> don't accept all characters as name of the workspace. Hence the plain job
>> name often can't be
On Tue, May 7, 2019 at 10:03 AM Mark Hahn wrote:
>
> > Some cluster sites need the creation of a workspace for the job in a
> >scratch area before the actual job submission, and on the other hand they
> >don't accept all characters as name of the workspace. Hence the plain job
> >name often can't
Some cluster sites need the creation of a workspace for the job in a
scratch area before the actual job submission, and on the other hand they
don't accept all characters as name of the workspace. Hence the plain job
name often can't be used here.
puzzled two ways: why not use the numeric jobid,
Hi,
Some cluster sites need the creation of a workspace for the job in a scratch
area before the actual job submission, and on the other hand they don't accept
all characters as name of the workspace. Hence the plain job name often can't
be used here.
sblank (with possible array size give) wil
