| 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 realize this notesfile is for technical questions, but the other MCC
notesfile seems to be moribund, so I'm cross posting this. It seems likely
that some of the people who follow this notesfile could provide a quick
answer, having investigated the question for their own purposes.)
<<< NAC::DISK$WORK17:[NOTES$LIBRARY]MCC.NOTE;2 >>>
-< MCC Technical Forum >-
================================================================================
Note 29.0 packaging question No replies
MOSAIC::PRAETORIUS "VAX: Architecture For The 80's" 8 lines 14-FEB-1990 13:10
--------------------------------------------------------------------------------
Will the MCC skeleton be shipped as part of VMS (so that a layered product
could write and ship their own A, F and/or PMs) or will it only be available
along with the A, F and PMs that are parts of products with MCC in the name?
Or will other layered products with generic management needs be able to
incorporate it?
curious,
Robt. P.
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 53.1 | It can be done..... | TOOK::STRUTT | Colin Strutt | Thu Feb 15 1990 02:15 | 9 |
While no specific decisions or commitments have been made, it is
technically feasible to ship an MCC skeleton (which we call the kernel)
with VMS and for the MMs to be added by layered products.
Right now, noone has expressed a desire to do this in a specific
timeframe. Please contact Peter Savage at your convenience if you
have such a need. We'd be happy to work with you.
Colin
| |||||
| 53.2 | still open for discussion | ENUF::GASSMAN | Sat Feb 17 1990 07:23 | 15 | |
Packaging has been the subject of many meetings, and while final
choices appear to be far from decided, some basic beliefs are coming
out. There will be a very basic package, a replacement for NCP if you
will. There will be a package of DEC LAN AM's, which speaks DEC's
proprietary protocols such as MOP and RBMS to handle FDDI, Bridges, and
terminal servers. There will be (over time as modules are available)
packages of FM's to replace function in current DECmcc/SMS and EMS
packages (current products). The goal is to reduce the number of part
numbers, since that is a hassle for both product managers and sales
people. Field input is still welcome, and should be placed here, or
mentioned to the product manager (hakim dhilla). Right now, the basic
kernel is not looked at as an option for the first release or two, but
does sound like a good idea....
bill
| |||||