| 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 |
Are there any plans to improve the handling of phase V events, so that
fields beyond the first line can be checked ?
I am specifically thinking about "adjacency state change"-events, where
the up/down status information is placed in the second line of the
event and can currently only be checked manually by parsing the event
text with an alarm fired procedure.
Are there any plans to improve the targeting mechanism, so that targeting
can be done on entities in other domains ?
The lack of this possibility is a big drawback to an otherwise very
useful feature.
More generally speaking; is there ANY developement going on for Decmcc,
or will we have to live with it AS IT IS for the next ?? years, until
it's successor can provide a reasonable amount of it's functionality ?
Will there be an updated kit including all the fixes produced for V1.3,
or will the seperate pieces only be available individually on request ?
Erik B. Christensen
MCS-COMMS
Copenhagen
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 5771.1 | TOOK::GUERTIN | I am never worng | Tue Dec 07 1993 09:05 | 11 | |
Well, I know that I am writing code for DECmcc. But the French Telecom
group (CBS) will be getting it for their product, called TeMIP. Which
layers on top of MCC. This new version of MCC may not be released to
the general public, but I would guess there would have to be some sort
of maintenence release. We have several bug fixes in our CMS libraries
with no place to go.
There should be more information about DECmcc in January, if you can
wait a few more weeks.
-Matt.
| |||||
| 5771.2 | Glad to see somebody is there. | COPCLU::EBC | Wed Dec 08 1993 05:01 | 3 | |
I guess, I will HAVE to wait, but thankyou for replying.
Erik
| |||||