| 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 |
We have been evaluating various Idle Process Killers and feel that ZAP fits our needs, because it is very flexable to customize. However, when I make a change to the ZAP.DAT file, the User Guide says that I cna change the value of the ZAP$RUN_STATUS logical name from "Continue" to "Start", and ZAP will re-initialize itself to take on the new information. I can't seem to get this to work. I have to STOP/ID= on the process and run SYS$STARTUP:ZAP$START.COM. I have tried the following flavors of redefining the logical name: $ DEFINE/SYSTEM/EXEC ZAP$RUN_STATUS "Start" $ DEFINE/SYSTEM/EXEC ZAP$RUN_STATUS START Any help will be appreciated. Alan
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 81.1 | Check for [SUPER] mode logical name | CSUDEV::MACONI | The Doctor is In | Thu Sep 13 1990 12:36 | 21 |
One of the possible problems that I can think of is that the logical is not being defined in executive mode. When you issue the command: $ define/sys/exec zap$run_status start VMS will not issue a warning message if you do not have the proper privileges to define this logical in EXEC mode. When you show the logical name, it will always show it as START and it will not change back to CONTINUE. Try the following command: $ show logical zap*/system If you see two definitions for ZAP$RUN_STATUS, one in [SUPER] mode and one in [EXEC] mode, then this is probably your problem. Unfortunately, this will also cause Zap to repeatedly re-initialize as Zap only changes the value of the EXEC mode logical name. If this is not the problem, then I will be glad to help you futher investigate the problem so that it can be properly corrected. Keith Maconi | |||||