| Title: | DECmcc user notes file. Does not replace IPMT. |
| Notice: | Use IPMT for problems. Newsletter location in note 6187 |
| Moderator: | TAEC::BEROUD |
| Created: | Mon Aug 21 1989 |
| Last Modified: | Wed Jun 04 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 6497 |
| Total number of notes: | 27359 |
I'm running V1.3 SSB DECmcc BMS on a V4.3 ULTRIX system with V5.1 DECnet/OSI. The system is a DECstation 5000/240 with 128MB of memory. When I attempt to create notification events for entity NODE *, the event is created and enabled w/o problems. As soon as I turn on a remote systems EVENT DISPATCHER OUTBOUND STREAM to connect to this system, dozens and dozens of windows are displayed, each one on top of the other indicating "notification request # for domain .... encountered an exception". So many of these windows are created that the workstation hangs until I can login from another system and kill the mcc_iconic_map process. vmstat 3 shows that memory is being used up very rapidly and idle cpu = 0. I did increase the system parameters as identified in the installation manual and rebuilt the kernal. dbx was used to verify that the new values have taken. I'm new enough to ULTRIX to know that I've hit my window of expertise.....the above system information was obtained with the help of the CSC. Don't know where to look next...... Any help greatly appreciated. Al
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 4862.1 | NODE * ANY EVENT alert | CTHQ::WOODCOCK | Mon Apr 12 1993 17:59 | 15 | |
Hi Al, I can't help with the exception messages but I can tell you what your 'next' problem is going to be :). Once you get by the exception problem with the help of someone in the know, if you NOTIFY DOMAIN x NODE * ANY EVENT I'll be real interested to see what happens to your CPU. When we did this the CPU went straight to 100% (back in V1.2) because it seems to constantly check for all the events of the entire entity model (hundreds maybe??). Maybe MCC has changed something for V1.3 to alleviate this but I've yet to try it with this version, but if not be careful when using "*" and "ANY EVENT". cheers, brad... | |||||