[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference share::zap

Title:Zap Technical Conference
Notice:ZAP Version 5.3 is available. See note 1.1
Moderator:ZAPDEV::MACONI
Created:Mon Feb 24 1986
Last Modified:Mon May 05 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:170
Total number of notes:492

56.0. "ZAP info needed" by IND::MISRAHI (This page intentionally left Blank) Wed Jan 18 1989 11:10

    I have a number of questions pertaining to ZAP:
    
    1. Does it stop processes using "STOP/ID="    ?
       Is there a problem using this in conjunction with certain databases?
       I have read somewhere that this could be a problem. 
    
    2. What criteria does ZAP use to determine a 'victim process' ?
       CPU usage, CPU time, Buff I/O, .... or a combination thereof ?
       Can I control these parameters ?
    
    3. Can I set up various classes of 'victims' with different parameters
       e.g.

       	[1,*] - no ZAPPING

        [60,*] - ZAP between 18:00 and 06:00

        dialup terminals - ZAP after delta time

        batch jobs - ZAP after delta time.

	The ASSETS description is vague at best.    
        Sorry if this is in the wrong place, or has been asked elsewhere,
        but I'm in a hurry with a bad connection.

    
    Thanks
        /Jeff
T.RTitleUserPersonal
Name
DateLines
56.1AnswersMPO::MACONIMon Jan 30 1989 13:2737
    {Sorry about the delayed response}
    
    1.  ZAP uses the DELPRC system service which is the same as using
        the "$ STOP/ID=" command.  Some applications do have problems
        with this and should not be stopped by ZAP.  Each application
        should be checked.
    
    2.  Zap uses Direct I/Os, Buffered I/Os and CPU clock ticks to
        determine how much work is performed.  The ratio is
        (3 * Direct I/O ) + ( 2 * Buffered I/O ) + CPU ticks
        You can not change the formula, but you specify how many "units"
        must be performed to be considered "active".
    
    3.  Zap uses UIC, Image name, Terminal class/name to determine
        which "catagory" a user falls in to.  Each "catagory" can have
        its own time limit or be immune.  An "mini" example is below
        of the Zap data file:
    
        !UIC        Image         Terminal       Time limit     Send Message
        [1,*]       *             console        *              Nomessage
        [200,150]   monitor       any            15             Message  
        [200,*]     monitor       any            30             Message
    
        Etc.
    
    	In addition, you specify when the warning messages should be
        send and what they should look like.
    
    	ZAP V3.8 can be obtained via the ASSETS program from VTX with
        the $ VTX ASSETS_OFFICE command.
                                                            
    
                                 Thanks for your interest,
    
    						Keith Maconi