| 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 have a customer who is running ZAP V4.2 in a 2 node cluster running VMS 5.4-2. Occasionally, the ZAP process stops logging out inactive processes. The ZAP process will run for weeks correctly and the last log the customer showed me had a pass = 13020, stack=71, stopped-473, error=0. When he stops the zap process and restarts ZAP, it continues to work for weeks. Anyone know if there are limitations to the amount of time the ZAP process can be running. Any help appreciated. Dave Coughlan
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 120.1 | Please upgrade to ZAP V5.0 | ZAPDEV::MACONI | The Doctor is In | Tue Oct 20 1992 16:58 | 13 |
The behavior that you describe has been reported before with versions of ZAP prior to V5.0. It can "forget" what it is doing or just "forget" about one or more specific processes. My belief is that some event causes the internal database to "unlink" process records. Due to this behavior, version 5.0 includes a completely new design for the internal database which does not allow processes to become disconnected from the database (as long as VMS remembers they exist and they are not in RWxxx states). Please upgrade to ZAP V5.0, which should correct this behavior. Keith Maconi | |||||