[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

5.0. "ZAP vs SPIRIT vs Global Buffering" by JOET::JOET (Joe Tomkowitz) Wed Feb 26 1986 10:43

    We've been using SPIRIT to do what I guess is the same function. A
    problem with it, however, is that if global buffering is turned on, a
    process terminated by SPIRIT can cause output which the process thought
    it had written, to be lost.  This is quite a bummer with a system
    running an application as critical, complex, and fragile as MAXCIM. 
    
    Does (or can) ZAP waste processes more gently than SPIRIT?  (The
    topic was discussed in some incarnation or another of VMSNOTES,
    but I don't think that it was resolved.)
    
    -joet
T.RTitleUserPersonal
Name
DateLines
5.1Not quite the same functionMRMFG1::K_MACONIThe DoctorWed Feb 26 1986 12:0828
        The procedure that Zap uses to kill off a process on the system
    is the SYS$DELPRC system call.  This is, as I recall, the same method
    that SPIRIT uses to kill of processes.  So, in that respect, Zap
    and SPIRIT are similar.
    
        The question that you should be asking yourself is, do I really
    want to stop a user when they are running MAXCIM?  Since MAXCIM
    is a system which uses RMS to perform its updates on multiple files,
    the act of killing a user can cause you some serious problems with
    files becoming out of sync.
    
        One of the problems with SPIRIT is that it does not enable you
    to turn it off under various conditions.  It is either on for the
    entire system, with specified uic's immune, or its off.  When you
    have an application on your system that uses DBMS or is as complicated
    and critical as MAXCIM, you may not want users in these applications
    to be killed.
    
        Zap, on the other hand, can be set up to have different idle
    time limits based on such factors as UIC, image name, and terminal
    type.  This means that if you have a critical application on your
    system, say MAXCIM, you can make that application immune from Zap.
    
    	If, however, you actually do want to kill off users in MAXCIM,
    then any idle process deletion utility (SPIRIT, ZAP, etc) will do.
    
    				Keith Maconi