User Tools

Site Tools


jobnames

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision
Previous revision
jobnames [2015/03/20 15:07]
meesters created
jobnames [2015/04/14 13:51]
meesters
Line 3: Line 3:
 Job names are important for the LSF scheduler (when searching for particular jobs, working with job dependencies,​ etc.). We therefore ask to specify meaningful and preferably unique job names. Job names are important for the LSF scheduler (when searching for particular jobs, working with job dependencies,​ etc.). We therefore ask to specify meaningful and preferably unique job names.
  
-In addition we adjust ​job names as of March, 24th, 2015:+In addition we will adjust ​jobnames in the near future:
  
 Our policy is: Our policy is:
-  * Missing jobnames ​or insanly long ones are converted ​to the first part of the command lineif the command line is too long, with a maximum of 40 Characters +  * Job names should not contain whitespace ​or semicolons. In this case the job name will be truncated ​to the first part of the original job nametaking whitespace and semicolons as delimiters. 
-  * HERE-doc like submission without ​jobnames ​fulfilling the criterion named above get a jobname ​consiting ​of ''​$USER_$RANDOMSTRING''​. Here, ''​$RANDOMSTRING'',​ obviously will be a random string, 20 characters long+  * Missing ​jobnames ​or insanly long ones get a jobname ​consisting ​of ''​$USER_$RANDOMSTRING''​. Here, ''​$RANDOMSTRING'',​ obviously will be a random string, 20 characters long.
  
jobnames.txt · Last modified: 2015/04/14 13:51 by meesters