[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

65.0. "Does it also work with SNA?" by KYOA::CHANG () Thu Jul 06 1989 13:19

    I have an ALL-IN-1 customer who also has SNA software on the
    system.  They are having a problem with people who log in from
    ALL-IN-1 and go to SNA as well as the reverse.  The users do
    not log off of the system and housekeeping procedures are not
    able to continue.  We are looking at ZAP to see if this will
    be able to kill these processes.  It would seem that it can
    kill ALL-IN-1 users, but how about people coming from SNA?
    
    Anyone have any experience with this or any suggestions?
    
    Thanks

T.R Title User Personal
Name Date Lines

65.1 Depends on application type WOODS::MACONI The Doctor is In Mon Jul 10 1989 10:11 26

T.R	Title	User	Personal Name	Date	Lines
65.1	Depends on application type	WOODS::MACONI	The Doctor is In	`Mon Jul 10 1989 10:11`	26
	We do not use SNA at this site, nor has it ZAP been tested with it. However, here is some info which may help: Zap monitors processes for cpu time (in hundreths), direct i/o's and buffered i/o's. When a process starts a program (such as ALLIN1), it will do some of the above, which causes ZAP to make the process "not idle". Applications which perform work in subprocesses, such as ALLIN1, must have the TRACEBACK option enabled (TRUE) so that the work that these subprocesses does is billed to the parent process. Applications, such as ACMS, which perform the work in detached processes are a problem. As they can not be readily identified as doing work for a particular process (hopefully it performs work for many different processes), the work done there can not be billed. Due to this, applications which use a detached server can not be monitored by ZAP as the process may be killed while waiting for a response from the server. Depending on which of the above two types of applications SNA is, ZAP may be able to handle the situation. I would appreciate if you would post your findings here for others. Thanks, Keith Maconi ZAP support

    We do not use SNA at this site, nor has it ZAP been tested with it.
    However, here is some info which may help:
    
    Zap monitors processes for cpu time (in hundreths), direct i/o's and
    buffered i/o's.  When a process starts a program (such as ALLIN1), it
    will do some of the above, which causes ZAP to make the process
    "not idle".  Applications which perform work in subprocesses, such as
    ALLIN1, must have the TRACEBACK option enabled (TRUE) so that the work
    that these subprocesses does is billed to the parent process.
    
    Applications, such as ACMS, which perform the work in detached
    processes are a problem.  As they can not be readily identified as
    doing work for a particular process (hopefully it performs work for
    many different processes), the work done there can not be billed.  Due
    to this, applications which use a detached server can not be monitored
    by ZAP as the process may be killed while waiting for a response from
    the server.
    
    Depending on which of the above two types of applications SNA is, ZAP
    may be able to handle the situation.  I would appreciate if you would
    post your findings here for others.
    
    					Thanks,
    
    						Keith Maconi
    						ZAP support