INSTALL FOR NON-PRIVILEGED RSX11M USERS 
                    =======================================

             Possibility of install for  non-privileged  user  makes  it
        possible  to  replace complicated, super-overlaied tasks by com-
        municating group of simpler tasks, and benefit from the most  of
        executive  directives.   The Pool load due to installed tasks is
        not too large, if there is possibility to remove them as soon as
        possible.   (There  are  many  other  ways  to  exhaust  POOL by
        non-privileged user).

             There is a simple patch in INSBLD.CMD, which makes INS com-
        mand  non-privileged.   But  making REMove unprivileged would be
        very dangerous - I don't reccomend it.  After some experience  I
        suggest following solution (all for the non-privileged user):
         
         - allow install under following conditions:
        	- non-privileged task
        	- limit priority up to 50.
        	- force the taskname to xxxTnn (xxxVnn)
         
         - allow remove under following conditions:
        	- non-privileged task
        	- not-fixed
        	- priority 50. or less
        	- taskname xxxTnn (xxxVnn)
         
         - modify the BYE to remove ALL the non-priv. installed tasks
           (recognition based on the name xxxTn, priority, prv-tsk).
         
         - modify MCRMU to first search for xxxTnn (xxxVnn) and then for
           ...xxx. This will allow non-privileged user also to redefine
           installed tasks (...PIP) to his own. 
         
        With the exception of the last item (not  yet  implemented)  the
        whole thing works O.K.  Example for TT4:
         
        >INS OWNPRG/PRI=220	will install task OWNT4 at PRI=50.
        INS -- non-privileged, taskname reduced to three letters
        >TAL OWN		will display OWNT4 status
        >OWN command		will schedule OWNT4 passing command to it
        >ABO OWN		will abort OWNT4
        >REM OWN		will remove OWNT4 (the same will do BYE)

             Currently I try to merge the whole thing together with  the
        KMS  Enhancement  Kit  and  latest Autopatch available, since my
        modified INS recognizes the /PRM switch, but not other  KMS  RUN
        privileges.
         
         
        					Ing.Martin Brunecky
        					Drobneho 28a
        				60000 	BRNO
        					Czechoslovakia
         

                                                                  PAGE 2