P101847: SUPPORT THE LIMITATION FOR NUMBER OF DISPATCH JOBS PER QUEUE AND/OR PER USER IN SPECIFIED SCHEDULING SESSIONS

APAR status

• Closed as program error.

Error description

• This solution allow cluster administrator to set the max number
  of dispatch jobs in a specified number of scheduling sessions.
  It introduced a new plug-in, dispatch limit plug-in (The library
   file is schmod_dispatch-limit.so) and a new configuration file
  lsb.dispatch_limit under
  $LSF_ENVDIR/lsbatch/<cluster_name>/configdir directory.  Cluster
   administrator can define dispatch limitation in
  lsb.dispatch_limit configuration file.
  If there is anything incorrect in the lsb.dispatch_limit file,
  the warning or error messages about the configuration will be
  logged into /tmp/lsb.dispatchlimit.log file while running badmin
  reconfig or badmin mbdrestart command.
  ?
  The log messages while scheduling will be logged into mbschd log
  as same as other standard plug-ins.When a job is blocked
  dispatching by dispatch limitation, it will output a piece of
  LOG_INFO level log message in mbsched's log. In the end of each
  schedule session, it will output the whole table of dispatch
  jobs vs dispatch limitation for all users on all queues/cluster
  wide which sets the dispatch limitation in in mbsched's log
  file.  The log level is LOG_DEBUG with log class
  LC_TRACE|LC_SCHED.
  

Local fix

• n/a
  

Problem summary

•    This fix allows the cluster administrator to specify the
  maximum number of jobs that can be dispatched in a specified
  number of scheduling sessions.
  

Problem conclusion

•  Will deliver a patch later.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  LSF STD LEGACY

• Fixed component ID

  5725G8206

Applicable component levels

• R913 PSY

     UP