| 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 |
Problem with ZAP...
Does ZAP work with DSM processes? A user instructed me that a
ZAP killed process will cause database corruption if the process,
that was 'Zapped' was in a database? How is the process stopped?
STOP/ID?
Thanks
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 92.1 | $DELPRC used to kill users | ZAPDEV::MACONI | The Doctor is In | Mon May 20 1991 12:24 | 10 |
ZAP uses the $DELPRC system service to stop users on the system. This is the equivilent of using the STOP/ID= command at DCL level. Data corruption is a function of the program and the language it is written in. Being stopped by ZAP is the same as being disconnected from the system. If a rundown procedure has been specified in the program, it should be executed. An example of this is that in most languages, if you type ^Y all of your files are automatically closed. I do not know about the particular program you mentioned, but it is possible. | |||||
| 92.2 | Is a routine available? | LARVAE::BEALE | Security is a Thumb and a Blanket... | Fri Nov 06 1992 11:24 | 6 |
18 months later can I re-open this query.
Has anyone provided a User routine to run down DSM (Digital Standard
MUMPS) processes when they are identified as idle by ZAP.
Location of such would save us some work. Any offers???
| |||||