| I attended the DECmcc AM training for Strategic Vendors in Europe last year.
The vendors' representatives were asking the same sort of questions and it
appeared at the time that the approach would be that Digital would act as
a "registrar" for strategically identified vendors, reviewing their AMs,
cataloguing them and in some cases, absorbing them into future versions of
the main DECmcc product. This was the flavour of the response given to the
vendors.
Regarding the sales channel, I believe from some of the vendors, that they
would like to see their AMs bundled for free with DECmcc (implying that we
handle the customer requests). Other vendors have a different approach and
will sell their AMs for a nominal fee to lever a hardware sale where
sophisticated network management is required.
Regarding the concept of a "Registrar" and someone doing code level review of
the SVPs' AMs, how is this progressing? I did not pursue my intent to do
AM development, but it struck me at the time that the Registrar must be in place
already even if only to allocate global entity tokens and symbolic values.
/Chris.
|
| The Registery is in place, however we haven't really told
anybody about it (yet) other than our SVP's we're working with
currently.
We have a document that will outline exactly what the process
is to register. It is being reviewed now and should be
available shortly.
The DSTEG orgainzation, managed by Emilio Marianelli, is
responsible for the logistics. I believe that DSTEG is already
doing DECnet/OSI and DNS registeration functions.
A careful point to make is that we will be registering
DIRECTIVES and MSLs, not really AMs. The goal is to ensure
that vendors don't use directives that will clash when their
MMs come together at the enterprise or that the meanings of
directives don't change from MM to MM.
At this point in DECmcc's life, the single point for 3rd
party/SVP activities is Earl Ingalls. Contact him for
questions or suggestions.
JCE
|