[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

148.0. "user-written comfile is invoked each minute" by UTRTSC::WDEBAKKER (I'm not home right now) Tue Mar 29 1994 08:41

    Hello,
    
    A customer who's using ZAP V5.0 reported a problem with the use of
    user-written actionroutines. When using exit or stop as the action to
    be taken after idle_limit all's well, but when specifying a
    user-written commandprocedure instead, this procedure is not invoked
    after idle_limit, but by each pass of ZAP, i.e. each minute.
    Is this a known problem? 
    I saw that V5.2 is already available. Is this version also for external
    use, or is it just for internal use only?
    
    Thanks for any help.
    Regards,
    Willem de Bakker
T.RTitleUserPersonal
Name		DateLines
148.1Coming soon to an SSB near you!SOLVIT::ROHNERTTue Mar 29 1994 12:027
    ZAP 5.2 is currently being transferred to ESSB and should be available
    soon for customer use.  However there is a bug that Keith is fixing now
    (a previous note).
    SSB will have the new kit for the Americas area soon after it is fixed.
    
    Dick
148.2And the problem in .0 ? Also solved in V5.2?UTRTSC::WDEBAKKEREach man has his price, BobThu Mar 31 1994 06:2714
Hello,

Does V5.2 provide a solution for the problem in .0?
According to the Reference Guide (3.1.13):
 The USERXXX parameter is used to indicate the name of a
 user-written action routine. These routines may be selected
 in the exception file to be executed when a process reaches its
 idle time limit.
But, according to the customer, these routines are executed each time ZAP
is scanning, so they are executed each minute.

Regards,
Willem
148.3V5.2 should fix thatZAPDEV::MACONIThe Doctor is InThu Mar 31 1994 18:2024
Hi,

	In version V5.0, when a process reached it's idle time limit, the
specified action is taken.  Under normal conditions, that will result in the
termination of the process before the next pass of ZAP (one minute later).  If,
however, the action does not result in the termination of the process (or in it
becoming active), then the action is repeated each minute because the process is
still at its idle time limit.

	In version V5.2, when an action is taken the entire process record is
cleared in ZAPs internal database.  This means that if the process should remain
after the action is taken, the process will accumulate idle time from 0 again.
This prevents repeated actions on processes, especially when user written action
routines are used.

	I suspect that the user written action routine that your customer is
referring to either (1) does not actually kill the process or (2) does not kill
it before the next pass of ZAP.  If you check the log files and find that it
is just taking too long, then V5.2 will fix the problem.  If this does not appear
to be the case, then there may be another problem that needs to be checked.

	I hope that this answers your question.

					Keith Maconi