[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

87.0. "exclude DECwindows users from Zap" by DEBUG::GALLO (Fast/Cheap/Good... limit 2 only!) Thu Oct 25 1990 00:34

Zap does not play well with DECwindows!  CSU has been asked about in 
this conference, but no reply has been given.  What is CSU?  Is it a
new Zap that has more DECwindows support??

My problem is the following...

   I would like to be able to set up ZAP.DAT to exclude Windows 
   terminals from being Zapped.  Here is some lines from my Zap V4.1
   exception file, ZAP.DAT...

!
/sensitivity=5
/traceback=true
/debug=false
/send=0
/inswap=false
/ignore_suspended=true
!
! System services
[001,*]		*		all		*		nomessage
!
! Batch jobs
[*,*]		*		batch		*		nomessage
!
! Network jobs
[*,*]		*		network		*		nomessage
!
! Detached jobs
[*,*]		*		detach		*		nomessage
!
! Window Terminals		
[*,*]		*		_TWA*:		*		nomessage
!
! Window Servers
[*,*]		*		_WSA*:		*		nomessage
!
! Window Images
[*,*]	 DECW*.EXE		all		*		nomessage
[*,*]	  VUE*.EXE		all		*		nomessage
!
! Global for all other users (must be done AFTER excluding individual users)
[*,*]		*		all		90		message

   Unfortunately, the Windows jobs ALL get Zapped, EXCEPT the processes
   running the image DECW$SESSION.EXE from BATCH.  I think the key here
   is "BATCH" mode, since ALL Batch jobs are excluded.  Any ideas?

   Thanks in advance,    Paul Gallo
T.RTitleUserPersonal
Name		DateLines
87.1Work around for DECwindows...CSUDEV::MACONIThe Doctor is InFri Oct 26 1990 14:4724
If you need to run ZAP on the workstation due to people connecting to it via
LAT, then I would suggest the following work-around:


	1. Zap ONLY lat terminals
	2. Exclude ALL others

Example:

!
! Uic		Image		Terminal	Time		Message
!
[*,*]		*		lat		30		message
!
[*,*]		*		all		*		nomessage

This will cause only processes connected to LTAxxx: to be zapped.  This should
fix the problem until proper DECwindows support is available.

Please post how this works.

						Thanks,

								Keith Maconi
87.2I wish it was that simple...DEBUG::GALLOFast/Cheap/Good... limit 2 only!Fri Oct 26 1990 16:2134
Let me re-state the problem.  I DO NOT want to ZAP windows users.
Our windows users pause their sessions regularly (securing them),
and do not wish to have ZAP kill them.

Here is a typical "snapshot" of two DECwindows users.
Note, they are not LAT terminals, but rather TWA* , MBA* and even WSA*
type terminals.

VTA77:   GALLO           GALLO         4       27.04 LEF   00000625 MAIL
VTA78:   _VTA78:         GALLO         4       29.43 CUR   00000627 WHO051
TWA38:   BATCH_34        GALLO         3        8.40 LEF   00000682 DECW$SESSI
MBA2737  GALLO_SM1       GALLO         4        3.17 LEF   00000683 DECW$CLOCK
TWA20:   BATCH_778       OLSON         3        4.99 LEF   00000484 DECW$SESSI
TWA21:   _TWA21:         OLSON         4       19.55 LEF   00000488 (idle)
TWA22:   OLSON           OLSON         4        9.53 LEF   00000489 MAIL
TWA39:   _TWA39:         GALLO         4        4.00 LEF   0000068B (idle)
TWA40:   _TWA40:         GALLO         4        1.72 LEF   0000068C (idle)

I have tried doing this in ZAP.DAT, but it doesn't work...

!	Window Terminals		
[*,*]		*		_WSA*:		*		nomessage
[*,*]		*		_TWA*:		*		nomessage
[*,*]		*		_MBA*:		*		nomessage
!
!	Window Images
[*,*]	 DECW*.EXE		all		*		nomessage
[*,*]	  VUE*.EXE		all		*		nomessage
!
! Global for all other users (must be done AFTER excluding individual users)
[*,*]		*		all		90		message
!

Thanks for any other ideas.   Paul Gallo
87.3Where do users come from?CSUDEV::MACONIThe Doctor is InMon Oct 29 1990 15:531
How do the users you DO want to ZAP connect to the system?
87.4we're getting close!DEBUG::GALLOFast/Cheap/Good... limit 2 only!Mon Oct 29 1990 17:2116
The typical users I wish to ZAP are...

	VTA* terminals (LAT users)
	RTA* terminals (remote DECnet users)
	OPA0 terminal  (Operator Console)

and, hmm... does that cover it?  maybe dialup or local terminals 
should also be ZAP'd.

I believe I see where you are going with this.  Instead of telling
ZAP which terminals to "ignore", tell it which ones to "zap"!
Seems like a more difficult way to do it, but if it works...

Could you give me a better example of how ZAP.DAT should then look?

Thanks again...   Paul
87.5ZAP.DATCSUDEV::MACONIThe Doctor is InTue Nov 06 1990 09:5422
Sorry about the delay, I've been out with the flu for a little while...


! ZAP.DAT
!
! System services
[1,*]		*		all		*		nomessage
!
! Operators console: Opa
[*,*]		*		console		15		message
!
! Remote users: Rta
[*,*]		*		remote		15		message
!
! Lat terminals: Lta
[*,*]		*		lat		15		message
!
! Virtual terminals: Vta
[*,*]		*		virtual		15		message
!
! All other users: Batch, detached, dialup, local, network
[*,*]		*		all		*		nomessage
87.6new ZAP.DAT does the trickDEBUG::GALLOFast/Cheap/Good... limit 2 only!Sun Feb 03 1991 01:298
Sorry for such a late response :^( ...

I have just created a new ZAP.DAT file in the format suggested in 
the last reply.  It looks like this approach solves all our problems!

Many thanks for your assistance Keith.

Paul Gallo