[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

131.0. "ZAP and Decwindow motif" by SSUPD::DELORENZO () Mon May 24 1993 10:26


hello,

I have a customer that want to use ZAP to stop idle window sessions ,
the environment is a Vaxstation 3100 with VMS 5.5-1 , motif 1.1 , ZAP 5.0.

I have setup ZAP in the following way :

ZAP$CONFIG.DAT
000 DEBUG       FALSE
001 ENABLE      TRUE 
002 GROUP_DW    TRUE 
003 HISTORY     TRUE 
004 IGNORE_SUSP FALSE
005 INSWAP      FALSE
006 LENIENT     TRUE 
007 SEND        9,7,5,3,1
008 SENSITIVITY 5        
009 TRACEBACK   TRUE     

ZAP$EXCEPTION.DAT
000 *      SYSTEM       [*,*]         * REMOTE  *        00:00 23:59 Y 15  STOP   
001 *      *            [1,*]         * ALL     *        00:00 23:59 N *   STOP   
002 *      *            [*,*]         * BATCH   *        00:00 23:59 N *   STOP   
003 *      *            [*,*]         * NETWORK *        00:00 23:59 N *   STOP   
004 *      *            [*,*]         * DETACH  *        00:00 23:59 N *   STOP   
005 ITPD03 DELORENZO    [600,601]     * DECWIND *        00:00 23:59 Y 5   STOP   
006 *      *            [*,*]         * ALL     *        00:00 23:59 N *   STOP   

I used UIC [600,601] to test ZAP in window environment ,
now the problem is that the processes related to this user get stopped
but the login window prompt doesn't appeare any more , so nobody could
any more login on that window terminal unless I restart decwindow.

I bypassed this situation replacing the "stop" action with a 
"user action routine" that lauches just "@sys$startup:decw$startup restart"
this seems to work.


Now what I ask you is:

1) does ZAP behaves as expected when it doesn't restart the process
   that manages the login window ??

2) Is the solution I adopted acceptable , or do you know anyone better ??


Thanks in advance,
Gian Luigi
T.RTitleUserPersonal
Name		DateLines
131.1Bug allows window process to remainZAPDEV::MACONIThe Doctor is InTue May 25 1993 19:5120
Hi,

	There appears to be a bug that allows some processes to remain after
the session manager is killed.  I believe that this problem is related to the
new version of MOTIF.  I will need to modify ZAP to track down this "lost"
process and kill it, since it appears that the session manager is not doing
it.

	When ZAP kills a windows users, it executes a command procedure

		ZAP$DIR:ZAP$RESTART_DECWINDOWS.COM

	This procedure kills the process and then creates a LOGINOUT process
to allow the user to log back in.  However, if there is still a process around
with a connection to the system, the login window can not appear - even if the
session manager has been killed.

	I will work on this and get a patch available as soon as I can.

					Keith Maconi
131.2where can I find the patch?SSUPD::DELORENZOThu Jun 17 1993 12:3810
Hi Keith,


>> RE .1, I will work on this and get a patch available as soon as I can. <<


how can I know when the patch will be available ? And where can I find
the patch ?

bye, Gian Luigi
131.3ESOA12::PILITZDThu Nov 11 1993 12:1213
     I am experiencing a similar problem as described in 0.  DECterm windows
     and the session manager are being zapped.  The mail and clock application
     remain active.  The login session window also does not appear.

     What is strange is I had this problem under 5.0 of ZAP, installed the
     field test version of 5.2 which resolved the problem, then just recently 
     installed production ZAP 5.2 kit where the problem returned.

     After the installation I did not make any changes to the configuration. 
     I'm running ZAP 5.2-2, VMS 5.5-2 and Motif 1.1.

     Any ideas on what is happening?
131.4ZAP V5.2 has a bugZAPDEV::MACONIThe Doctor is InThu Nov 11 1993 16:208
ZAP V5.2 has a bug.  There appears to have been a revision problem when it
was released and a piece of FT code was included in the released kit.  This
bug prevents ZAP from grouping DECwindows processes together.

I will attempt to correct this problem and re-release ZAP V5.2 as quickly as
possible.

					Keith Maconi
131.5ESOA12::PILITZDFri Nov 12 1993 08:494
     Thank you Kieth,  would you post a note when the new version has 
     been released?

     Dolores
131.6ZAP V5.2-3 has been releasedZAPDEV::MACONIThe Doctor is InFri Nov 12 1993 15:0428
Hello all,

	I have just submitted the corrected kit to the ASSETS group.  I need to
applogize to all who upgraded to the bad version of ZAP v5.2 as the error was
the result of an error on my part.

	I have been testing ZAP to run under AXP/VMS (it is not quite there yet)
and had accidently included the AXP field test code in the kit that I submitted
to the assets group.  I am having problems since the Motif programmers keep
changing how processes are interacting and how they pause the workstation.

	The new kit should be available shortly.  Do not install any version of
ZAP V5.2 unless the kit is dated 12-NOV-1993 14:41.  Once installed, it will
identify itself as V5.2-3.

	In addition, there are two known problems that I am currently working
on.  But I thought it was more important to get a correct kit out than to wait
until I resolve these problems.  They are:

	1.  When loging out a DECwindows user, remote processes displaying to
	    the workstation are not always disconnected (based on the version
	    of Motif that you are running).  This causes the workstation to
	    not restart windows (the login box does not appear).

	2.  ZAP can not always tell if a workstation is paused (again based
	    on the version of Motif).

					Keith Maconi