 
 
 
+                             QUEUE MONITOR
 +                             Andy Gosselin
i-                           September 4, 1985
 .                           Northeastern Univ.
*                               Boston, MA
,                             (617) 437-4430
 0H Queue Monitor User's Guide                                      Page 2
 
 
 1  PURPOSE
 
H      The queue monitoring program is  designed  to  provide  automated
H management of the batch queues.  Based on a configuration specified at
H the start of the program, the queue monitor acts as  an  operator  who
H pauses or starts queues.  The current number of interactive users will
H allow it to make such operator decisions.  This utility  was  designed
H based  on  a need to prioritize time slices for the interactive users,
H verses for  batch  jobs.   It  is  related  somewhat  to  managing  an
H overnight-holiday  queue.   A  future  release  will  be  based  o the
H percentage of idle cpu time as this  is  clearly  more  indicative  of
H system  load.   The  present  incarnation  still  fills  the void as a
 stop-gap.
o 
 
 
 2  INSTALLATION
  
H      In order to help install the monitor on your system there  exists
H a  command  file  called  'INSTALL.COM'.   Its function is to take the
H source files from a directory indicated by the  user  and  produce  an
H executable image.  It also makes an entry into the system logical name
H table  pointing  to  that  directory.   The  logical  name   used   is
H QUEMON$LIBRARY.   Once  installed the program can be run as a detached
H process by executing the command file called 'START.COM'.  A data file
H for  the  queue  configurations is built during the first part of this
H procedure.  The  later  part  involves  the  creation  of  a  detached
H process.   For  input formats read the next paragraphs.  All input and
H output, plus all code is to be found in  the  directory  indicated  by
H QUEMON$LIBRARY.    START.COM   is   AUTOMATICALLY   invoked   by   the
 installation procedure.
S 
H      The monitor can be a process that is automatically started up  by
H the  system  by  placing  a  couple  of  lines  in  the system startup
 procedure.  These lines are:
 
G         $ ASSIGN/SYS name_of_the_queue_monitor_library QUEMON$LIBRARY
          $ @QUE_MONITOR
 
H Where 'QUEMONITOR.COM' creates a detached  process.   It  assumes  the
0 data file 'CONFIG.DAT' has already been built.
 
 
 
 3  DESIGN METHODOLOGY
  
H      Upon  starting  the  queue  monitor,  the  program  will  request
H configuration  specifications.  Currently these specifications include
H three things, the name of the target queue, the time slice or interval
H in  which  the  monitor  returns to make a check on the queue, and the
H critical number of users which can be supported before  the  queue  is
H stopped.   Up  to  256  configurations can be specified, however it is
H suggested that not more than one configuration  be  entered  for  each
H queue.  Since the specifications are entered sequentially in the order
- mentioned above.  The input format follows:
  nH Queue Monitor User's Guide                                      Page 3
 
 
          Queue Name:
 
H          1.  Maximum of 31 characters indicating a  queue  name  which
6              can be found in the SHOW QUEUE command.
 
H          2.  The end of file or Z will indicate  that  no  more  queue
1              configurations wish to be entered.
l 
 
          Time Slice:
 
H          1.  The time slice should be entered in a time  format  based
/              on military time, (hh:mm:ss.cc).
u 
@          2.  The maximum slice is slightly less than 24 hours.
 
H          3.  Parts of the time can be defaulted to the current time by
H              their  elimination, (eg.  12:00:. defaults to the current
@              number of seconds and miliseconds plus 12 hours).
 
 
          Critical Load:
. 
H          1.  An integer  representing  the  tolerance  level  for  the
H              number of interactive users.  The target queue is stopped
2              once the tolerance has been broken.
 
 
 
H      Once the configurations have been  entered,  the  driver  program
H calls  the  monitor  routine.  The monitor runs indefinitely from that
H point on, simply surviving on the interrupts that  check  the  queues.
H For  this reason it is suggested that the program be run as a detached
H process, with an  input  file  being  used  to  describe  the  queues'
 configurations.
m 
H      There are two output files that are created by the queue monitor.
H The  first one is created as the configurations are read in.  Its name
H is 'CONFIG.DEF'.  It  is  closed  before  the  monitoring  routine  is
H called.   The  second  file  is  a  log  file  which  contains entries
H indicating  when  a  queue  operation   was   made.    Its   name   is
H 'QUEMONIT.LOG'.   Both  of  these files are created anew each time the
 queue monitor is started.
