[Imported from gridengine issuezilla ​http://gridengine.sunsource.net/issues/show_bug.cgi?id=111]

        Issue #:      111              Platform:     All           Reporter: svdavidson (svdavidson)
       Component:     gridengine          OS:        All
     Subcomponent:    doc              Version:      5.3beta2         CC:    None defined
        Status:       NEW              Priority:     P3
      Resolution:                     Issue type:    ENHANCEMENT
                                   Target milestone: ---
      Assigned to:    markob (markob)
      QA Contact:     skonta
          URL:
       * Summary:     qconf man page updated with new -clearusage option
   Status whiteboard:
      Attachments:

     Issue 111 blocks:
   Votes for issue 111:


   Opened: Wed Dec 5 06:55:00 -0700 2001 
------------------------


The qconf man page has been updated. Please update the reference manual.

   ------- Additional comments from andreas Thu Oct 21 07:22:00 -0700 2004 -------
Assign Admin/User/Install guide related issues to Mark O'Brien.

   ------- Additional comments from surajp Mon Mar 23 01:23:09 -0700 2009 -------
Reassigning to Sandra.

[Imported from gridengine issuezilla ​http://gridengine.sunsource.net/issues/show_bug.cgi?id=114]

        Issue #:      114              Platform:     All           Reporter: ernst (ernst)
       Component:     gridengine          OS:        All
     Subcomponent:    doc              Version:      current          CC:    None defined
        Status:       NEW              Priority:     P3
      Resolution:                     Issue type:    ENHANCEMENT
                                   Target milestone: ---
      Assigned to:    markob (markob)
      QA Contact:     skonta
          URL:
       * Summary:     Two new cluster configuration parameters (max_aj_instances, max_aj_tasks)
   Status whiteboard:
      Attachments:

     Issue 114 blocks:
   Votes for issue 114:


   Opened: Wed Dec 19 06:23:00 -0700 2001 
------------------------


sge_conf:

max_aj_instances
   This parameter defines the maximum amount of array task instances
   within an array job.
   An instance of an array task will be created within the master
   daemeon when it gets a start order from the scheduler. The instance
   will be destroyed when the array task finishes.
   'max_aj_instances' gives the possibility to limit the number of tasks
   which may be started at the same time. Therefore it gives the
   administrator the possibility to directly influence the qmaster's
   memory consumption behavior.
   Default for this parameter is 2000. The value 0 will deactivate this
   limit.

max_aj_tasks
   This parameter defines the maximum number of array tasks within an
   array job. Qmaster will reject all submittion requests for jobs
   which should have more than 'max_aj_tasks'.
   Default for this parameter is 75000. The value 0 will deactivate this
   limit.

   ------- Additional comments from ernst Wed Mar 6 04:59:46 -0700 2002 -------
manpages change, documentation still has to be done

   ------- Additional comments from andreas Thu Oct 21 07:44:32 -0700 2004 -------
Assign Admin/User/Install guide related issues to Mark O'Brien.

   ------- Additional comments from surajp Mon Mar 23 01:26:25 -0700 2009 -------
Reassigning issue to Sandra.

[Imported from gridengine issuezilla ​http://gridengine.sunsource.net/issues/show_bug.cgi?id=178]

        Issue #:      178              Platform:     All           Reporter: ernst (ernst)
       Component:     gridengine          OS:        All
     Subcomponent:    doc              Version:      6.0              CC:    None defined
        Status:       NEW              Priority:     P4
      Resolution:                     Issue type:    ENHANCEMENT
                                   Target milestone: ---
      Assigned to:    andreas (andreas)
      QA Contact:     skonta
          URL:
       * Summary:     New cluster configuration parameter "max_jobs"
   Status whiteboard:
      Attachments:

     Issue 178 blocks:
   Votes for issue 178:


   Opened: Wed Mar 6 05:12:00 -0700 2002 
------------------------


A new cluster configuration parameter will be available in the
next main release. It won't be available in 5.3.

I changed the manpage. Documentation still has to be done.

sge_conf(5):
...
max_jobs
       The number of active (not  finished)  jobs  simultaneously
       allowed  in xxQS_NAMExx.  is controlled by this parameter.
       A value greater than 0 defines  the  limit.   The  default
       value  0  means  "unlimited".  If  the  max_jobs  limit is
       exceeded by a job submission then the  submission  command
       exits  with  exit  status 25 and an appropriate error mes
       sage.

       Changing max_jobs will take immediate effect.

       This value is a global configuration  parameter  only.  It
       cannot be overwritten by the execution host local configu
       ration.
...

   ------- Additional comments from andreas Thu Oct 21 08:37:20 -0700 2004 -------
Assign User/Admin/Install issues to Mark O'Brien.

   ------- Additional comments from surajp Mon Mar 23 01:30:59 -0700 2009 -------
Reassigning issue to Sandra.