
#==========================================================================
# JM Job Manager    - Copyright 1992, Steve Koren
#
# (JM is freely distributable under conditions given in the documentation.
#  It is not wise to try to understand JM by browsing this file.  The
#  documentation is there for a reason).
#
# This file is read by JM upon invocation.  It should be named ".jmrc",
# and may reside in either the current directory or "S:" (preferred).
# Also, make sure JM-Handler resides in "L:".
#
# Do not delete these comment lines - they are read fast.  Arguments
# to options can be quoted to contain spaces.  Use spaces, but no tabs.
# Inter-field spacing is ignored.  '#' in the first column of a line is
# a comment line.  If a non-repeating option is repeated, later definitions
# will override previous ones.
#==========================================================================

# This option controls whether JM will keep a log of task activity.
# Permitted values are "off" and "on".

LOGSWITCH       off


#--------------------------------------------------------------------------
# This is the name of the log file, when used.  The log file should be on
# fast device, not a floppy.  Permitted values are valid file names.

LOGFILE         "ram:JM.log"


#--------------------------------------------------------------------------
# This is the time in seconds between updates of the task CPU percentage
# fields.  The larger this number, the longer the CPU weighted average will
# take to converge to the current value.  Permitted values are 1 to 10,
# inclusive.

PS_CPU_TIME      5


#--------------------------------------------------------------------------
# This switch controls whether JM will manage unequal allocation of
# cycles to CPU bound tasks.  See the "MANAGE" options below.  Permitted
# values are "on" or "off".

MANAGESWITCH     off


#--------------------------------------------------------------------------
# This switch controls whether JM will watch new tasks and modify their
# priority according to the "TASKPRI" defaults given in this file.
# Permitted values are "on" or "off".

WATCHSWITCH      on


#--------------------------------------------------------------------------
# This option controls the length of one quantum when JM is managing
# unequal allocation of cycles to CPU bound tasks.  This number is the
# number of 10ths of a second in one quantum.  Small values produce
# smoother results, but have a (slightly) higher overhead.  Permitted
# values are 1 (one 10th of a second) to 50 (5 seconds).  Faster machines
# can use smaller values with less overhead.

QUANTUM          5


#--------------------------------------------------------------------------
# These two parameters control the priority of "active" and "inactive"
# managed tasks.  JM will allocate CPU resources unequally by changing
# task priorities over time.  These are the two priorities it uses.
# The MIN value must be less than MAX.  Permitted values are -128 to -1.

MIN_MANAGE_PRI   -26
MAX_MANAGE_pri   -25


#--------------------------------------------------------------------------
# JM can watch tasks which start up, and change their priorities to a
# default based on the task name.  Up to 64 watched task names may be
# present.  Case is not significant, and pathnames are ignored.  The
# second field is the task name, and the third is the priority to give
# the task upon startup.  The minimum allowable priority is -128, and
# the maximum is 127.  Values greater than 5 should be used with caution.

TASKPRI          "mg"              2
TASKPRI          "MEmacs"          2
TASKPRI          "calendar"        5
TASKPRI          "calculator"      1


#--------------------------------------------------------------------------
# JM can manage unequal allocation of CPU resources to CPU bound tasks,
# something not before possible on the Amiga.  These lines control this
# behavior.  The second field is the task name.  The third is the number
# of quantum (see QUANTUM above) which will go to this task before control
# is given to another task.  For example, if "task_1" is set to 3, and
# "task_2" is set to "11", there will be 14 total quantum, "task_1" will
# get 3/14 of this time, and "task_2" will get 11/14 of this time.
# These tasks should be CPU bound tasks only.  An editor or IFF viewer
# would not be a good candidate, nor would a task which needs continous
# un-interrupted use of the CPU, such as a terminal program.  The minimum
# permitted quantum count is 1, and the maximum is 100.

MANAGE           "SceneryAnimator"     12
MANAGE           "MandelPAUG"          8
MANAGE           "longpi"              1

# *** LINES AFTER THIS POINT ARE NEW TO JM 1.1 ****************************

#--------------------------------------------------------------------------
# Some methods of starting background commands (the AmigaDos RUN command,
# for example) do not install the process name immediately upon invocation.
# Instead, the process name is "run" or some other non-descript string
# temporarily.  This will confuse JM, which normally looks for the name
# immediately upon startup.  This parameter will tell JM to delay checking
# the task name for N 10ths of a second after the task first appears.  This
# should be made as small as possible.  A value of 5 to 10 should be fine
# for most accelerated hard disk systems.  You may need to tweak this value
# for slower machines.  Permitted values are 0 to 50.  Use high values only
# as a last resort.

INSTALL_DELAY    5


#--------------------------------------------------------------------------
# This switch turns the JM ARexx port on or off.  Permitted values are "on"
# or "off".  Default is "on".

AREXX_PORT       on
