[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

97.0. "ZAP problem from another conference" by 3574::ROHNERT (Awesome ASSETS) Mon Aug 26 1991 18:16

         <<< BUFFER::EVENT$PAGE:[NOTES$LIBRARY]ASSETS_PROGRAM.NOTE;1 >>>
                              -< ASSETS_PROGRAM >-
================================================================================
Note 164.0                        Bug in ZAP ?                        No replies
IJSAPL::BROUWERS                                     19 lines  26-AUG-1991 04:51
--------------------------------------------------------------------------------
    Hi,
    
    I have problems with ZAP. A customer uses TEAMDATA under All-In-1. 
    After invoking the data, the TEAMDATA server works a while with this
    data and the subprocess in which TEAMDATA runs is idle.
    When the ZAP time limit is over, the sub- and oa$main process are
    deleted.
    ZAP-maintainer, can this be fixed ?
    
    	To build a workaround, i placed the TEAMDATA image in the ZAP
    exceptions file.
    But the subprocess was still deleted.
    Is it true that the exceptions file will be compared to the main
    process?
    If so, can the ZAP asset be modified in that way, that the images from
    the exceptions file are also compared to the subprocess image ?
    
    regards, Gerard Brouwers EIS Holland.
T.RTitleUserPersonal
Name		DateLines
97.1ZAP needs new feature ZAPDEV::MACONIThe Doctor is InTue Sep 03 1991 11:1413
Hello,

	I believe you have found a place where ZAP can be improved.  It is
apparent that you are using the TRACEBACK function with ALLIN1 to allow ZAP
to monitor all of the subprocesses and treat them as one process.  You have
also correctly concluded that when ZAP is in this mode it ONLY looks at the
root (main) process (all other subprocesses are ignored EXCEPT for utilization).

	It appears that ZAP needs the ability to use the most lenient rule when
dealing with TRACEBACKed processes.  This ability will be introduced with the
next version currently being developed.

						Keith Maconi
97.2Quick solution ?IJSAPL::BROUWERSMon Sep 09 1991 10:368
    hi,
    
    thanks Keith. When will the next version be available ? I have a
    customer with a lot of problems because off this ZAP behaviour. Is it
    possible to build a "quick solution" ?
    
    Gerard Brouwers, EIS Holland.
97.3ZAP V4.3 real soon now...ZAPDEV::MACONIThe Doctor is InTue Sep 10 1991 00:1722
Hi,

	Unfortunately, I do not believe that a 'quick' solution based on V4.2
will be possible for this problem.  V4.3 is a major re-write of the code to
allow future support for some new features.  The problem that we have talked
of has already been incorporated into the basic design of the next release.

	I believe that this release may be ready for Field Test by the end of
the month.  Depending on how well things go, it should include most or all of
the planned features.  Working through the Network ASSETS program, you may be
able to get a pre-release UNSUPPORTED version for this customer.

	Until then, the best I can suggest is to disable traceback and make your
sensitive sub-processes immune (be sure to specify terminal type 'all').  This
will cause ZAP to kill from the bottom up, instead of from the top down.

	NOTE: Doing this will cause ZAP to kill 'idle' subprocesses that it had
previously left alone because of other 'non-idle' subprocesses/parent process.

				Sorry that I can't be of more immediate help,

							Keith