| 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 |
ZAP V5.0 on 7000 class machine.
Customer has many nodes (assorted boxes) running ZAP. Recently though
they shutdown and rebooted their 7000 series box. Boot went as normal
but 8-10hrs. later operator noticed OPCOM not running. Upon starting
OPCOM, VCS terminal appeared hung. Users could not CONNECT to 7000 node
nor would SET HOST or anything else work!.
Upon rebooting machine, OPCOM fired up but then later in startup
sequence VCS reporting OPCOM not running. At this point, on every boot
sequence the events were the same.
After going down the garden path ZAP startup sequence was edited out.
System rebooted with no issues.
At one point, during test boot sequence, MCR SYSMAN was edited and local
startup sequence activiated interactively with $SHOW SYSTEM between
commands. OPCOM was running until ZAP started. Then OPCOM was
blown away as was the ZAP process!
Ideas anybody?
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 143.1 | What version of VMS? | ZAPDEV::MACONI | The Doctor is In | Wed Feb 16 1994 18:56 | 11 |
Hi, What version of VMS was the system running? I have never heard of ZAP causing any problems with OPCOM on any version of VMS (until now). ZAP only uses OPCOM via the $BRKTHRU system service to send the warning messages to each user. Keith Maconi [Sorry about the delay, I was out on vacation...] | |||||
| 143.2 | VMS Version # as requested | CGOOA::HUNKA | Tue Feb 22 1994 22:52 | 9 | |
And I'm out at another site.
This system is running V5.5-2. Customer has ordered latest version of
ZAP.
Their system (since narrowing the problem to ZAP and commenting out
startup procedure) has been "rock-solid".
| |||||