| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 5982.1 | Incorrect assumption | SCCA::dave | Ahh, but fortunately, I have the key to escape reality. | Tue May 10 1994 18:07 | 3 |
| Your assumption is incorrect. There will not be a new version of
MCC "very soon".
|
| 5982.2 | | WELTM1::CRIDDLE | Graham Criddle, MCS Tech Consultant, 853-4015 | Wed May 25 1994 10:45 | 12 |
| Hi...
Is there any reason why the message store Management Specification as
provided by the product cannot be added to the MCC dictionary?
(it may not be in the right form, but the data should be there)
If this were possible, is anything else necessary to make it work?
Rgds,
Graham
|
| 5982.3 | Shortest path between 2 offices: around the world | AZUR::ANTEUNIS | There's no software like declared dead software | Fri May 27 1994 08:52 | 17 |
| MCC uses a private MSL syntax as opposed to the standard one promoted by ???? and
used by NCL and others.
The DSSR group manages all these MSL files and makes sure that the identifiers that
are contained in them are unique. This is a necessary condition for being included in
a dictionary. The DSSR group then makes the unique MSL file public or sends it back
to You if You wish to keep it private. (DSSR contact DSSR::LUND)
Unfortunately You need more to access the Message Store: You will have to program an
agent that understands a language spoken by an access module that gets linked to MCC.
One way of getting rid of the access module is making the agent CMIP or SNMP
compiant. That way You can use a standard access module.
Hops this is the right answer,
Dirk
|
| 5982.4 | | WELTM1::CRIDDLE | Graham Criddle, MCS Tech Consultant, 853-4015 | Mon Jun 06 1994 06:10 | 12 |
| Hi, Dirk.
Thanks for the reply (I have been out for a week or so, so haven't
responded earlier)
It was not clear from point .2 but the MEssage Store is a module
under the NODE entity, so is manageable via CMIP. Does this
mean that all I need is the MSL included in some form into the MCC
dictionary?
Rgds,
Graham
|