| 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 |
It is tempting to describe callable MCC as an "MCC where the application developer controls the user interface". But I wonder. In particular, can an application built against callable MCC have calls made through MCC_CALL dispatched through the two level function-then-access mechanism that happens in the director? Or in other words, can our management application use a directive that is provided by one of our FMs? If so, would it be accurate to characterize the results of using callable MCC as an "MCC Director with a custom user-interface"? If there any capability provided below the PMs that the MCC director can do that a management application written against callable MCC cannot access (assuming it knows how)? Events? Thanks.
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 1497.1 | TOOK::SWIST | Jim Swist LKG2-2/T2 DTN 226-7102 | Thu Sep 12 1991 18:19 | 7 | |
We've confused people with our description of callable MCC. You
are right - it's just getting to mcc_call from a program other than
one of our PMs.
Our PMs use no interfaces other than mcc_call_function for
communicating with AMs/FMs. In theory you could duplicate either
of our PMs using only the info in the SRM and MRMs.
| |||||