| 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 |
I'm sure this is probably a feature and not a bug, but in our
application it is sort of annoying.
Before initiating backups, we run a home grown COM procedure
called SUSPENDER. This goes out and suspends any interactive users
that have not logged out as per the backup warning messages. This
was put in place to allow anyone performing lengthy interactive
jobs to continue, undisturbed, after the completion of backups.
It seems that ZAP does not take into account if a process is
in the suspended state and kills it anyway (ie if its in a suspended
state, it was probably set like that for a reason.)
Is there any help for this situation?
Thanks,
Charlie
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 66.1 | Suspend ZAP | WOODS::MACONI | The Doctor is In | Fri Jul 21 1989 16:46 | 8 |
As you are suspending ALL interactive users, the best solution would be
to suspend ZAP too. Zap does not monitor a processes state (except for
its swap state).
I will try to add code in that will treat a suspended process as a
swapped process.
Keith
| |||||
| 66.2 | ZAP$KILL_SUSPEND = "TRUE" | POLAR::SYSTEM | Mon Jul 24 1989 09:55 | 7 | |
Yes I guess that is the only solution for now. I was wondering
though; in some cases, it might be advantageous to have
control of how suspended processes are dealt with. Perhaps
a logical definition?
Charlie
| |||||
| 66.3 | Suspending ZAP has no effect! | DEBUG::GALLO | No time for JIVE from 9 to 5! | Wed Aug 30 1989 17:07 | 15 |
re .1, Keith, I have tried to suspend the ZAP process, even using "SET PROCESS/SUSPEND=KERNEL" with no apparent change to the behavior of ZAP. A "SHO SYS" reveals the ZAP process is in HIBernate state, yet it continues to run every minute and even ZAP idle processes as usual! I would really like to find a way to "suspend" the ZAP process between 8 and 5 daily. I have written a simple procedure that runs in batch to do this, however, it requires shutting down ZAP, and re-starting it 9 hours later. ZAP by design always creates a new ZAP.LOG file. I would prefer not to create new log files daily, so do I have any other alternatives for now? Thanks for your help, Paul Gallo | |||||