Opened 19 years ago

Last modified 11 years ago

#49 new defect

IZ290: handling of job names

Reported by: joga Owned by:
Priority: normal Milestone:
Component: sge Version: current
Severity: Keywords: cleanup


[Imported from gridengine issuezilla]

        Issue #:      290              Platform:     All       Reporter: joga (joga)
       Component:     gridengine          OS:        All
     Subcomponent:    cleanup          Version:      current      CC:    None defined
        Status:       NEW              Priority:     P3
      Resolution:                     Issue type:    DEFECT
                                   Target milestone: ---
      Assigned to:    ernst (ernst)
      QA Contact:     ernst
       * Summary:     handling of job names
   Status whiteboard:

     Issue 290 blocks:
   Votes for issue 290:

   Opened: Fri Jun 14 04:12:00 -0700 2002 

Job names are currently set in different locations.

For some reason qmaster rejects jobs, that have no job name set - despite the fact that there exists code in execd that will create a default job name if the job contains no name.

This should be cleaned up:
1. Is there a reason why a job has to pass a job name to qmaster? Certainly, we need one for qstat, but this could be generated in qmaster.

2. Use a central function call to create the job name from the job settings and from default rules. Currently there exist 3 different places that create jobnames: qsub code, qsh code and execd.

Change History (0)

Note: See TracTickets for help on using tickets.