[GE users] Jobs starting with a number

Ron Chen ron_chen_123 at yahoo.com
Wed Nov 2 08:31:03 GMT 2005

    [ The following text is in the "iso-8859-1" character set. ]
    [ Your display is set for the "ISO-8859-10" character set.  ]
    [ Some special characters may be displayed incorrectly. ]

Internally, SGE checks whether the job name is a digit to
determine whether it is a job id (JB_job_number) or it is a name

We discussed about it on this list before. One solution is to
qsub with "-N <name>", then SGE will happily accept your scripts
starting with a number. Another solution needs to change the
code - instead of checking whether the first letter is a number,
we should check the whole name (all letters -> job id, 1 or more
alphabets -> job name).


--- "Jeroen M. Kleijer" <jeroen.m.kleijer at philips.com> wrote:
> Hi all,
> Every now and then I get a user who claims his jobs aren't
> started and 
> usually it ammounts to them having given the job a name that
> starts with a 
> number instead of a letter. They adjust it and the jobs then
> goes as 
> expected.
> However, I'm still quite curious what the decision was on why
> a job could 
> not start with a number. One of our applications, Msc.Marc,
> breaks down a 
> job-file for mupltiple cpus and prefixes every new jobfile
> with a number. 
> This in its turn gets submitted but the fails so multi-cpu
> computing using 
> this application doesn't work.
> Is there any way to get around this?
> Met vriendelijke groeten / Kind regards
> Jeroen Kleijer
> Unix Systeembeheer
> Philips Applied Technologies

Yahoo! FareChase: Search multiple travel sites in one click.

To unsubscribe, e-mail: users-unsubscribe at gridengine.sunsource.net
For additional commands, e-mail: users-help at gridengine.sunsource.net

More information about the gridengine-users mailing list