[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

89.0. "ZAP stops ZAPPING after ZAP$MAINT runs" by GUBBE::FRYKMAN () Wed Apr 03 1991 22:25

We currently have ZAP V4.2 running on two ALL-IN-1 clusters.  Nightly ZAP$MAINT is
submitted via VAX Scheduler to ensure that Zap log files are kept to a 'readable' size.

The problem which has been occurring is that ZAP$MAINT does not appear to be stopping
the ZAP process so when it goes to restart it, there is an error stating that Process
is already present, cannot create.  What 'appears' to be happening in this instance
is that ZAP itself stops ZAPPING!

Unfortunately this has caused some concern with the ALL-IN-1 folks as they must ensure
all users are logged out of their clusters prior to their nightly maintenance.  ZAP
seemed to be the answer, but now??

Has anyone seen this occurrence before?

My fix to the problem was simply to kill the ZAP process and restart it.  As a check,
I then ran ZAP$MAINT to ensure it would work.  It did.  Is it possible that ZAP$MAINT
may be the problem?  I know there is a WAIT statement of 2 minutes in the command to
allow ZAP to be shutdown 'nicely'.  

Any thoughts or suggestions would be appreciated.

T.R Title User Personal
Name Date Lines

89.1 Possible privilege problem? CSUDEV::MACONI The Doctor is In Mon Apr 08 1991 15:55 13

T.R	Title	User	Personal Name	Date	Lines
89.1	Possible privilege problem?	CSUDEV::MACONI	The Doctor is In	`Mon Apr 08 1991 15:55`	13
	Is it possible that the zap maintenance procedure is running out of a not-privileged-enough user via VAX Scheduler? The reason I ask is that if it runs out of an account which does not have sufficient privileges to define a executive mode system logical name without enabling privileges first, the procedure will not work. Since the ZAP startup procedure enables these privileges, it would not have the same problem. Maybe you could try this, add the following line to the beginning of the ZAP$MAINT.COM procedure: $ SET PROCESS/PRIV=ALL Zap only looks at executive mode system logical names.

	Is it possible that the zap maintenance procedure is running out of a
not-privileged-enough user via VAX Scheduler?  The reason I ask is that if it
runs out of an account which does not have sufficient privileges to define a
executive mode system logical name without enabling privileges first, the
procedure will not work.

	Since the ZAP startup procedure enables these privileges, it would not
have the same problem.  Maybe you could try this, add the following line to
the beginning of the ZAP$MAINT.COM procedure:

	$ SET PROCESS/PRIV=ALL

	Zap only looks at executive mode system logical names.