[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

80.0. "ZAP and 3270 TE, 3270 DS and INGRES ?" by IJSAPL::HUIJTS (F2CS+5.6m�+4..7Bft=Fun) Wed Sep 05 1990 12:00

Howdy,

I have two questions concerning ZAP :

- my customer is running INGRES on their systems. He wants to kill users 
  (that is : a front-end process within INGRES) who are doing nothing
  for half an hour.
  Is this possible using ZAP ?
  How does this influence the database integrity ?

- this customer is also using 3270 TE and 3270 DS terminal emulation and
  file transfer to an IBM system.
  When the user has a connection to the IBM, is this connection closed
  when he is ZAPped ?

Thanx & best Regards,

Mark Huijts
Digital Utrecht
The Netherlands
DTN 7838-2528

T.R Title User Personal
Name Date Lines

80.1 Should work fine CSUDEV::MACONI The Doctor is In Wed Sep 05 1990 18:38 21

T.R	Title	User	Personal Name	Date	Lines
80.1	Should work fine	CSUDEV::MACONI	The Doctor is In	`Wed Sep 05 1990 18:38`	21
	ZAP is able to monitor any individual process and issue, basically, a STOP/ID= on the process when it becomes inactive. The database should be able to recover any transactions in progress should a partial transaction be terminated. ZAP, to the best of my knowlege, has not yet been tested with INGRES specifically, but there should not be any problems. Terminal emulators, when disconnected, will automatically drop any links that they may have, be it hard wired lines or DECnet links, etc. The only issue would be similar to the problem with ACMS type products: 1. User is running an interface program. All work is actually performed by a database server process. 2. User requests a large database inquiry, such as a comprehensive report which may take some time to generate. 3. The user becomes inactive and is ZAPped, even though they were doing work, since their process was actually just hibernating until the server completed.

ZAP is able to monitor any individual process and issue, basically, a STOP/ID=
on the process when it becomes inactive.  The database should be able to
recover any transactions in progress should a partial transaction be terminated.

ZAP, to the best of my knowlege, has not yet been tested with INGRES
specifically, but there should not be any problems.

Terminal emulators, when disconnected, will automatically drop any links that
they may have, be it hard wired lines or DECnet links, etc.

The only issue would be similar to the problem with ACMS type products:

	1. User is running an interface program.  All work is actually
	   performed by a database server process.

	2. User requests a large database inquiry, such as a comprehensive
	   report which may take some time to generate.

	3. The user becomes inactive and is ZAPped, even though they were doing
	   work, since their process was actually just hibernating until the
	   server completed.