Conference azur::mcc

	Just a few more instructions:

	The newsgroup/mailing list posted in .0 is a PUBLIC mailing list. 
Proprietary DEC info should terefore not go out on this list.  I don't own
this newsgroup/mailing list, it is owned by Bob Boyd 
(decwrl::"[email protected]", Unisys/EPA) located at Research Triangle 
Park, NC.

	To sign up for it via e-mail, send mail to 
decwrl::"[email protected]" with the subject line blank and one line
of text in it containing:

subscribe decmcc YourFirstName YourLastName (Optional Additional Comments)

	To receive info for it via e-mail, send mail to 
decwrl::"[email protected]" with the subject line blank and one line
of text in it containing:

help

	To send info to it via e-mail, send mail to 
decwrl::"[email protected]" and write a normal subject line and text
as you would any other note.

	To join the news group:

From:	FLASHY::kennedy "MaryEllen Kennedy"  6-NOV-1991 19:41:02.66
To:	Carl Silva - Telecom Engineering - 828-5339  06-Nov-1991 1036    <[email protected]>
CC:	flashy::kennedy
Subj:	Re: MCC newsgroup? 

Carl,

Well, I'm using mxrn on ULTRIX.  I think there are also news readers
available on VMS - let me know if you need help with this part.

Then, assuming you've got a newsreader - I'm currently using
usenet.pa.dec.com as my server (I'm using IP as a transport) - it also
is DECnet node usenet.
The name of the newsgroup is vmsnet.networks.management.decmcc.

Here's a (fairly current) list of news servers within DEC.  You may
want to try one close to you to see if they carry this group.  This
information comes from the UPSAR::News-Backbone conference - which also
has information on where to get software, etc.

        LOC   NODE    NUMB  EASYnet       TCP/IP

        abo  decabo  17348  16.964
        buo  deceds  26647  26.23
        cxn  shodha   8912   8.720      16.63.96.2	(shodha.cxn.dec.com)
        dco  decuac  36915  36.51       16.67.32.1	(decuac.dec.com)
        fac  lemans  34949  34.133	16.75.32.9	(lemans.det.dec.com)
        jit  tkou02  60156  58.764
        lkg  nntpd   56696  55.376	16.20.0.162	(nntp.lkg.dec.com)
        ltn  sousa   29872  29.176      16.120.0.31	(sousa.ltn.dec.com)
        mko  e2big   32752  31.1008     16.126.16.1	(e2big.mko.dec.com)
        mro  ryn     21662  21.158      16.25.0.1	(ryn.mro4.dec.com)
        nyo  datum   33325  32.557      16.69.128.12	(datum.nyo.dec.com)
        pko  engage  24729  24.153      16.124.0.254	(engage.pko.dec.com)
        reo  hollie  43211  42.203      16.36.80.4	(hollie.rdg.dec.com)
        soo  loke    51624  50.424
    	uco  usenet  10392  10.352	16.1.16.73	(usenet.pa.dec.com)
        unt  cssec4  50844  49.668      16.185.96.113	(cssec4.unt.dec.com)
        uvo  decuk   41990  41.6        16.182.128.1	(decuk.uvo.dec.com)
        vbo  uninet  52631  51.407
    	wfo  sniff   18608  18.176	16.129.128.2	(sniff.wfo.dec.com)
        wro  oct17   30779  30.59       16.60.160.4	(oct17.dfe.dec.com)
        zso  rust    10416  10.176	16.64.0.1	(rust.zso.dec.com)

Regards,
_Mek

    This news group has been around for a few months now.  Bob Boyd
    introduced himself at Interop - and is happy to be sponsoring this
    group.  Question:  Should all entrys be posted to one note, or should
    each topic generate a new one in this conference, or should those
    interested get on the news group and handle things as they see fit?
    I've seen this news group become a sort of unofficial support channel,
    but sometimes that's the 'right thing to do'.  It's also a good way to
    get out news about MCC.
    
    bill

>    I've seen this news group become a sort of unofficial support channel,
>    but sometimes that's the 'right thing to do'.  It's also a good way to
>    get out news about MCC.

Since there is a delay between posting news and its availability for reading,
we need to decide WHO is going to post support type answers.  The newsgroup
is public,  with worldwide distribution, and it would not look good
for DEC to be posting speculations (possibly conflicting) from many different
people at the same time.

Also, as I understand it, commercial announcements are not permitted
in the newsgroups, so we have to be careful about what we post.

	RE: .3,

>Since there is a delay between posting news and its availability for reading,
>we need to decide WHO is going to post support type answers.  The newsgroup
>is public,  with worldwide distribution, and it would not look good
>for DEC to be posting speculations (possibly conflicting) from many different
>people at the same time.
>
>Also, as I understand it, commercial announcements are not permitted
>in the newsgroups, so we have to be careful about what we post.

	I agree with .3, there are always problems with public mailing lists. 
Just be careful what gets sent to it.

	Carl

    
    If someone will reply to this question from the USENET, I'll
    consolidate the answers and reply.  thanks... bill
    
From:	DECWRL::"[email protected]" 19-NOV-1991 09:29:21.88
To:	enuf::gassman
CC:	
Subj:	New user questions

I've just installed DECmcc SMS (via CSLG, i.e. free but no support) and I'm
still slogging through the documentation.  However, I've got a couple of
questions that puzzle me:


1. MCC> dir station *

   STATION *
   AT 13-NOV-1991 20:04:32

   The requested operation cannot be completed
                    MCC Routine Error = %MCC-E-NOATTRIB, no such DNS attribute

The messages manual says that this is an error inside DECmcc.  Is this a known
bug?  Or have I done something wrong?


2. The DCL command procedure to register nodes from the NCP database want to
put them in  the .dna_node hierarchy.  I'd rather put them at the root, as the
examples are in the book.  Any problems with this?

3. The DCL command procedure to register stations from the Ethernim database
insists on sticking a leading underscore to the names.  Is there a reason for
this?  Again, I'd rather put them at the root.

4. We're looking into network monitors; Technically Elite Concepts has a DECmcc
Access Module for their Network Professor.  Has anybody used this?

Thanks,
-Bruce
--
Bruce Tanner        (213) 860-2451 x 596    [email protected]
Cerritos College    Norwalk, CA             cerritos!tanner

% ====== Internet headers and postmarks (see DECWRL::GATEWAY.DOC) ======
% Received: by enet-gw.pa.dec.com; id AA26191; Tue, 19 Nov 91 06:29:45 -0800
% Received: from  (localhost) by ralph.rtpnc.epa.gov (5.65c/1.34) id AA02487; Tue, 19 Nov 1991 09:29:41 -050
% Date: Tue, 19 Nov 1991 09:29:41 -0500
% Message-Id: <[email protected]>
% Comment:  Discussion group for DECmcc related topics
% Originator: [email protected]
% Errors-To: [email protected]
% Reply-To: <[email protected]>
% Sender: [email protected]
% Version: 5.3 -- Copyright (c) 1991, Anastasios Kotsikonas
% From: [email protected]
% To: enuf::gassman
% Subject: New user questions

Here's a few of the answers...

>1. MCC> dir station *
>
>  STATION *
>  AT 13-NOV-1991 20:04:32
>
>  The requested operation cannot be completed
>                MCC Routine Error = %MCC-E-NOATTRIB, no such DNS attribute
>
> The messages manual says that this is an error inside DECmcc.  Is this a
> known bug?  Or have I done something wrong?

This looks like something that would happen if no STATIONs are registered.
Are any registered?

> 3. The DCL command procedure to register stations from the Ethernim database
> insists on sticking a leading underscore to the names.  Is there a reason for
> this?  Again, I'd rather put them at the root.

Putting a leading underscore in the name has nothing to do with which
DNS directory the name gets filed under.

Fullnames in DECmcc must (currently) be unique. This means that you couldn't,
for example, have a Node4 and Station (or Bridge) entity both named ".Fred".
Since the NMCC/VAX ETHERnim database used the Node4 name (where applicable)
to identify its entities, odds are good that autoregistering Stations (if done
first) would prevent Node4s from registering. To get around this problem,
we prepend an underscore to the name.

BTW, Feel free to edit the .COM file generated before running it.

>
> 4. We're looking into network monitors; Technically Elite Concepts has a
> DECmcc Access Module for their Network Professor.  Has anybody used this?

I thought TECs AM was a prototype (maybe Kathy Jo can answer this).