[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference azur::mcc

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

539.0. "HELP! I don't get it to work properly after installation" by STKHLM::AMARTENSSON (smooth as ice) Mon Dec 10 1990 19:30

I can't get my DECmcc EFT v1.1 to run properly, but I can't find out what 
I've done wrong. If I try to create a domain I get the following errormessage:

MCC> create domain democenter
%MCC-E-INVALIDIDENT, invalid entity identifier
MCC>
MCC>

If I try to create an entity I get the same message:

MCC>
MCC> create node4 .svanen syno=svanen
%MCC-E-INVALIDIDENT, invalid entity identifier
MCC>

---

If I activate the windows-interface most selections on the pulldown-menu
are grey, f.i. new domain and toolbox.


------------------------------------------------------------------------

The IVP's runs OK, but I found the following in the installation-log:


The MCC_STARTUP_DIR startup procedure for DECmcc T1.1.0 is now running.
.
.
.
If the DNS directory .MCC has not been created, both
the deregister and the register commands will fail.

DECmcc (T1.1.0)

%MCC-E-INVALIDIDENT, invalid entity identifier
DECmcc (T1.1.0)

%MCC-E-INVALIDIDENT, invalid entity identifier

   Completing DECmcc DIRECTOR Postinstallation Procedure ...

   Beginning DECmcc BMS Postinstallation Procedure ...



The MCC_STARTUP_BMS startup procedure for DECmcc T1.1.0 is now running.

DECmcc (T1.1.0)

%MCC-W-ARGUNKNOWN, unknown argument RULE
%MCC-E-ATTRNOTALLOW, no attribute or argument allowed


The MCC_STARTUP_BMS startup procedure for DECmcc T1.1.0 is now ending.



-------------------------------------------------------------------------------



The DNS-server runs on another node but a DNS-clerk is
up and running on the DECmcc-node. I have run 
    SYS$COMMON:[MCC]MCC_DNS_BASIC_SETUP.COM;1
    SYS$COMMON:[MCC]MCC_DNS_SETUP.COM;1

---

The accesscontrol in DNS seems OK, read+write+test+delete on all mcc-directories
but I do anyhow suspect there is something wrong with the communication with 
the DNS-server. If I do:

MCC>  set mcc 0 responsible person="decmcc"

MCC 0
AT 10-DEC-1990 22:19:15 References

The requested operation cannot be completed
                      MCC Routine Error = %MCC-E-INV_ENTITY, invalid entity
                                          structure




SO, does anyone has any suggestions on what to look at or shall I do the
installation all over again?

Thanks in advance

Anna-Lena
T.RTitleUserPersonal
Name
DateLines
539.1can you supply some more info?TOOK::DITMARSPeteWed Dec 12 1990 12:1935
Looks like an interesting problem (read: I have no idea what's wrong).

The %MCC-E-INVALIDIDENT error is returned by the parser when an entity
identifier fails a validity check.  The entity identifiers you're entering
look fine to me.

What versions of VMS and DNS are you running?

Does anything at all work in MCC?  (post some results)

Was this a clean, from scratch installation?  If not, what previous version of
MCC had you been running?

Are there any old dictionary/parse tables laying around that could be getting
in the way?

Can you run the following tests for us:

What are the values of the logicals MCC_SYSTEM, MCC_SPECIFIC and MCC_COMMON?

$ SHO LOG/FULL MCC_SYSTEM, MCC_SPECIFIC, MCC_COMMON

What are the timestamps/sizes/protections of the ditionary and parse tables?

$ DIR/DATE/SIZE/PROT MCC_SYSTEM:*.DAT, MCC_SYSTEM:*.BPT

Try running the following commands in MCC and posting the results:

show mcc 0 all attr
show mcc 0 alarms rule * all attr
show mcc 0 FCL all attr
show domain * member * all attr
show domain * rule * all attr
show node4 0 all attr
show node4 anchor all attr
539.2Do you have any MCC Symbols defined?TOOK::GUERTINI have an in_e, you have an out_eWed Dec 12 1990 13:3513
    The last time I saw something like this, the user had defined an MCC
    symbol (like "MCC") to be something else, and they did it in the
    MCC initialization file.  Please post the results of the DISPLAY
    command:
    
    MCC> Display
    
    If this is the problem, then the solution is not to define that symbol.
    As a long term solution the FCL should display an informational message
    whenever a user defines a symbol, much like the Debugger displays an
    informational message when you redefine a key.
    
    -Matt.
539.3symbols: good guessTOOK::DITMARSPeteWed Dec 12 1990 14:1218
Good idea Matt.  Symbols may well be the problem here.

>    As a long term solution the FCL should display an informational message
>    whenever a user defines a symbol, much like the Debugger displays an
>    informational message when you redefine a key.

And then FCL will be getting QAR'd because folks won't want to see a whole
screenful of garbage messages go by every time they start up FCL, so we'd add
something to make the display of confirmation messages for local FCL commands
to be optional, and the NCL folks would QAR us for more non-NCL-conformant
stuff....

p.s.

DBG> define key xxx xxx /NOLOG

will get those annoying messages from DBG to go away when you're defining
keys.  :^)
539.4Here are my answers to both .1 and .2STKHLM::AMARTENSSONsmooth as iceWed Dec 12 1990 14:35279
The product versions are:
VMS v 5.4 and DNS v 1.1

It was a scratch installation. I have now done the installation all over again
with new kits - both DECMCC and DNS (now placed on the same node as DECMCC)
and I still get the same kind of error. I can hardly do anything at all
in DECmcc, if I try to create an alarm it doesn't like the argument RULE,
if I try to create a domain or add a new node it gives the message
'Unknown entity identifier'.

Here follows the requested information:

------------------------------------------------------------------------------

$ SHO LOG/FULL MCC_SYSTEM, MCC_SPECIFIC, MCC_COMMON

           "MCC_SYSTEM" [exec] = "MCC_SPECIFIC" (LNM$SYSTEM_TABLE)
                = "MCC_COMMON"
        1  "MCC_SPECIFIC" [exec] = "SYS$SPECIFIC:[MCC]" (LNM$SYSTEM_TABLE)
        1  "MCC_COMMON" [exec] = "KNIPAN$DUA2:[MCC]" (LNM$SYSTEM_TABLE)



           "MCC_SPECIFIC" [exec] = "SYS$SPECIFIC:[MCC]" (LNM$SYSTEM_TABLE)

           "MCC_COMMON" [exec] = "KNIPAN$DUA2:[MCC]" (LNM$SYSTEM_TABLE)

-------------------------------------------------------------------------------

$ DIR/DATE/SIZE/PROT MCC_SYSTEM:*.DAT, MCC_SYSTEM:*.BPT

Directory KNIPAN$DUA2:[MCC]

MCC_ALARMS_ATTRIBUTE_MIR.DAT;1
                         81   3-DEC-1990 11:40:41.97  (RWED,RWED,RWED,RE)
MCC_ALARMS_INSTANCE_MIR.DAT;1
                         66   3-DEC-1990 11:40:40.21  (RWED,RWED,RWED,RE)
MCC_BRIDGE_ICON.DAT;4
                          3   6-APR-1990 16:57:21.23  (RWED,RWED,RWED,RE)
MCC_BRIDGE_LANBRIDGE_100_ICON.DAT;4
                          4   1-MAY-1990 13:15:23.00  (RWED,RWED,RWED,RE)
MCC_BRIDGE_LANBRIDGE_150_ICON.DAT;4
                          4   1-MAY-1990 13:15:24.00  (RWED,RWED,RWED,RE)
MCC_BRIDGE_LANBRIDGE_200_ICON.DAT;4
                          4   1-MAY-1990 13:15:26.00  (RWED,RWED,RWED,RE)
MCC_DEFINITION.DAT;5
                      14103  13-NOV-1990 20:56:17.33  (RWED,RWED,RWED,R)
MCC_DICTIONARY.DAT;5
                      23742  13-NOV-1990 20:56:16.16  (RWED,RWED,RWED,R)
MCC_DISPATCH_TABLE.DAT;1
                        450  12-DEC-1990 13:32:05.33  (RWED,RWED,RWED,R)
MCC_DOMAIN_DELNI_ICON.DAT;4
                          4   1-MAY-1990 13:53:17.00  (RWED,RWED,RWED,RE)
MCC_DOMAIN_DEMPR_ICON.DAT;4
                          4   1-MAY-1990 13:55:44.00  (RWED,RWED,RWED,RE)
MCC_DOMAIN_DESPR_ICON.DAT;4
                          4   1-MAY-1990 13:56:03.00  (RWED,RWED,RWED,RE)
MCC_DOMAIN_ICON.DAT;4
                          3   5-APR-1990 12:19:37.29  (RWED,RWED,RWED,RE)
MCC_MCC_ICON.DAT;4        3   5-APR-1990 12:19:47.45  (RWED,RWED,RWED,RE)
MCC_META_DEFINITION.DAT;5
                          4  14-NOV-1990 13:54:18.63  (RWED,RWED,RWED,R)
MCC_META_DICTIONARY.DAT;5
                          1  18-JUN-1990 16:26:09.38  (RWED,RWED,RWED,R)
MCC_MIR_ATTRIBUTE.DAT;5
                         81  12-DEC-1990 13:20:19.75  (RWED,RWED,RWED,R)
MCC_MIR_DIRECTORY.DAT;5
                         66  12-DEC-1990 13:20:16.02  (RWED,RWED,RWED,R)
MCC_NODE4_DECNET_HOST_ICON.DAT;4
                          4   1-MAY-1990 13:15:00.00  (RWED,RWED,RWED,RE)
MCC_NODE4_DECNET_OSI_HOST_ICON.DAT;4
                          4   1-MAY-1990 13:15:02.00  (RWED,RWED,RWED,RE)
MCC_NODE4_DECROUTER_1_ICON.DAT;4
                          4  20-MAY-1990 10:10:56.00  (RWED,RWED,RWED,RE)
MCC_NODE4_DECROUTER_2_ICON.DAT;4
                          4  20-MAY-1990 10:11:12.00  (RWED,RWED,RWED,RE)
MCC_NODE4_DECSTATION_ICON.DAT;4
                          4   1-MAY-1990 13:55:15.00  (RWED,RWED,RWED,RE)
MCC_NODE4_DECSTA_ULTRIX_DECNET_ICON.DAT;4
                          5   8-MAY-1990 13:54:56.00  (RWED,RWED,RWED,RE)
MCC_NODE4_ICON.DAT;4
                          3   6-APR-1990 16:44:33.63  (RWED,RWED,RWED,RE)
MCC_NODE4_L1_ICON.DAT;4
                          3   6-APR-1990 16:48:41.33  (RWED,RWED,RWED,RE)
MCC_NODE4_L2_ICON.DAT;4
                          3   6-APR-1990 16:55:27.81  (RWED,RWED,RWED,RE)
MCC_NODE4_LAVC_ICON.DAT;4
                          4   1-MAY-1990 13:15:27.00  (RWED,RWED,RWED,RE)
MCC_NODE4_PRINT_SERVER_ICON.DAT;4
                          4   1-MAY-1990 13:15:31.00  (RWED,RWED,RWED,RE)
MCC_NODE4_VAXSTA_VMS_DECNET_ICON.DAT;4
                          5   8-MAY-1990 13:56:55.00  (RWED,RWED,RWED,RE)
MCC_NODE4_VAX_HOST_ICON.DAT;4
                          4   1-MAY-1990 13:15:37.00  (RWED,RWED,RWED,RE)
MCC_NODE4_WS_VAX_ICON.DAT;4
                          4   1-MAY-1990 13:15:48.00  (RWED,RWED,RWED,RE)
MCC_NODE_ICON.DAT;4
                          3   6-APR-1990 16:41:34.24  (RWED,RWED,RWED,RE)
MCC_PTB_PARSER.DAT;2
                       1013   4-DEC-1990 09:52:49.91  (RWED,RWED,RWED,RE)

MCC_PTB_PARSER.DAT;1
                        996   3-DEC-1990 12:11:44.99  (RWED,RWED,RWED,RE)
MCC_SAMPLE_ICON.DAT;4
                          3   6-APR-1990 16:58:25.30  (RWED,RWED,RWED,RE)
MCC_SNMP_ICON.DAT;4
                          3   8-JUN-1990 08:11:10.00  (RWED,RWED,RWED,RE)
MCC_SNMP_TCP_IP_HOST_ICON.DAT;4
                          4   1-MAY-1990 13:15:34.00  (RWED,RWED,RWED,RE)
MCC_SNMP_WS_ULTRIX_IP_ICON.DAT;4
                          4  18-SEP-1990 15:16:05.00  (RWED,RWED,RWED,RE)
MCC_STATION_ICON.DAT;4
                          3  19-APR-1990 13:43:51.68  (RWED,RWED,RWED,RE)
MCC_UNITED_STATES.DAT;4
                        105  20-JUN-1990 15:28:40.73  (RWED,RWED,RWED,RE)
MCC_WESTERN_EUROPE.DAT;4
                         46  31-OCT-1990 13:38:12.80  (RWED,RWED,RWED,RE)
MCC_WORLD.DAT;4         336  20-JUN-1990 15:28:20.16  (RWED,RWED,RWED,RE)

Total of 43 files, 41198 blocks.

Directory KNIPAN$DUA2:[MCC]

MCC_PTB_PARSER.BPT;7
                       1467  19-NOV-1990 17:09:44.78  (RWED,RWED,RWED,R)

Total of 1 file, 1467 blocks.

Grand total of 2 directories, 44 files, 42665 blocks.
DECmcc (T1.1.0)

---------------------------------------------------------------------------
$
$ manage/enter
MCC> show mcc 0 all attr

MCC 0
AT 12-DEC-1990 16:50:10 All Attributes

                         Component Name =
%FULLNAME_ERROR, error in Full Name value
               Component Identification = "DECmcc"
                      Component Version = T1.1.0

MCC>show mcc 0 alarms rule * all attr

MCC 0 ALARMS RULE
AT 12-DEC-1990 16:50:40 All Attributes

No rules have been created.

MCC> show mcc 0 FCL all attr

MCC 0 FCL
AT 12-DEC-1990 16:50:50 All Attributes

               Component Identification = "DECmcc Forms and Command Line PM"
                      Component Version = "T1.1.0"

MCC> show domain * member * all attr

The requested operation cannot be completed
                      MCC Routine Error = %INVALIDFUNCTION, Specified function
                                          code is invalid

MCC> show domain * rule * all attr

The requested operation cannot be completed
                      MCC Routine Error = %INVALIDFUNCTION, Specified function
                                          code is invalid

MCC> show node4 0 all attr

Node4 62.404
AT 12-DEC-1990 16:51:15 All Attributes

                                Address = 62.404
                                   Name = KNIPAN
                       Physical Address = AA-00-04-00-94-F9
                                  State = On
                       Aged Packet Loss = 0 Packets
                      Connects Received = 42 Connects
                          Connects Sent = 42 Connects
                  Counter Creation Time = 11-DEC-1990 22:39:01.68
           Maximum Logical Links Active = 9 Links
          Node Out-of-Range Packet Loss = 0 Packets
           Node Unreachable Packet Loss = 0 Packets
                  Oversized Packet Loss = 0 Packets
                    Packet Format Error = 0
            Partial Routing Update Loss = 0
       Received Connect Resource Errors = 0
                      Response Timeouts = 0 Timeouts
              Seconds Since Last Zeroed = >65535 Seconds
                Total Messages Received = 568 Messages
                    Total Messages Sent = 610 Messages
                    User Bytes Received = 40726 Bytes
                        User Bytes Sent = 40600 Bytes
                    Verification Reject = 0
                    Alias Maximum Links = 32
                Broadcast Routing Timer = 180 Seconds
                            Buffer Size = 576 Bytes
                         Default Access = Both
                           Delay Factor = 80
                           Delay Weight = 5
                         Identification = "DECnet-VAX V5.4,  VMS V5.4    "
                       Inactivity Timer = 60 Seconds
                         Incoming Proxy = Enable
                         Incoming Timer = 45 Seconds
                     Management Version = V4.0.0
                        Maximum Address = 1023
                           Maximum Area = 63
                      Maximum Area Cost = 1022
                      Maximum Area Hops = 30
           Maximum Broadcast NonRouters = 64
              Maximum Broadcast Routers = 32
                        Maximum Buffers = 100
                       Maximum Circuits = 16
                           Maximum Cost = 1022
                           Maximum Hops = 30
                          Maximum Links = 32 Links
                    Maximum Path Splits = 1
                         Maximum Visits = 63
                     NonPrivileged User = "DECNET"
                            NSP Version = V4.1.0
                         Outgoing Proxy = Enable
                         Outgoing Timer = 60 Seconds
                         Pipeline Quota = 10000
                      Retransmit Factor = 10
                          Routing Timer = 600 Seconds
                        Routing Version = V2.0.0
                                   Type = EndNodeIV
                        Initial Address = 62.404
             Initial Management Version = V4.0.0
                Initial Maximum Address = 1023
                           Initial Name = KNIPAN
         Initial NonPrivileged Password = "no access rights"
             Initial NonPrivileged User = "DECNET"
                          Initial State = On
                           Initial Type = EndNodeIV

MCC> show node4 anchor all attr

Node4 anchor
AT 12-DEC-1990 16:51:36 All Attributes

Node does not exist or is not known to local Node.
                         Default Entity =
                      Default Qualifier =
                      Default Qualifier =
                                 Prompt = MCC>
                            Indentation = 42

------------------------------------------------------------------------------


Re .2

MCC> Display

No symbols exist in the symbol table
No notify requests are currently in progress
Command procedure verification is OFF
Logging is OFF, Logging file is MCC.LOG











 



539.5dns doesn't seem to be talking with mccGOSTE::CALLANDERWed Dec 12 1990 14:5714
    
    Did you run the two dns setup procedures?
    
    You see you can get at node4 stuff without haveing to register it,
    as long as you don't try to access it via a full name, or register
    it. Domains as well as MCC itself all require DNS for even the simplist
    operation. It sure doesn't look your MCC and DNS are
    intercommunicating.
    
    First you should check the install guide and see if you did all
    of the dns_setup steps, and then second you can try using dns control
    to check out a few things yourself (see note 538 for instructions).
    
    
539.6Answer to .5STKHLM::AMARTENSSONsmooth as iceWed Dec 12 1990 15:2225
I agree at what you say about MCC and DNS not intercommunicating
but I must say I can't figure out why.

I did run the MCC_DNS_SETUP at installation-time and the directories are 
there as I think they should be.

DNS> sh dire . kno child

 Child ______ DNA_BACKTRANSLATION
 Child ______ DNA_NODE
 Child ______ DNA_NODESYNONYM
 Child ______ mcc
 Child ______ MCC_BRIDGE_BACKTRANSLATION
 Child ______ MCC_STATION_BACKTRANSLATION
 Child ______ MCC_UID


There is also a child (%X49) in DNA_BACKTRANSLATION and it 
has a lot of children.


Confused greetings

Anna-Lena
539.7DNS V1.1 != DNS on VMS V5.3/V5.4TOOK::DITMARSPeteWed Dec 12 1990 17:5321
>The product versions are:
>VMS v 5.4 and DNS v 1.1
>It was a scratch installation. I have now done the installation all over again
>with new kits - both DECMCC and DNS (now placed on the same node as DECMCC)

Hmmm... these aren't the same symptoms, but there have been problems in the
past when folks have deleted DNS .EXEs and then re-installed DNS using
the V1.1 kit.

Is there any chance that DNS was "partially" de-installed at any point in
the past?  The DNS V1.1 kit will install certain parts of the clerk if they
are not already on the VMS system.  These parts of the clerk that are on
the DNS V1.1 kit are outdated and won't work the way the DNS that comes
with VMS V5.3 (and later) works.

See notes 369.9 and 378.3 in this conference and notes 413 and 415 in 
the TOOK::DNS conference.

Check your DNS .EXE files against those of a system that is running the
same version of VMS as your system.  If you're out of synch, copy their
DNS .EXE files over to your system.
539.8Just a suggestion : running PTB never does any harmTENERE::LAVILLATThu Dec 13 1990 06:229
Try :

mana/tool/parse in mcc_specific directory

It will do no harm and sometimes has good effects...

(Especially when you upgrade from IFT1.1 to EFT1.1 which is not your case !)

Pierre.
539.9'no communication with DNS$BACK'STKHLM::AMARTENSSONsmooth as iceThu Dec 13 1990 13:3916
I copied the suggested files from a working DECMCC/DNS system and then got
the message:

...
$ DNSCP START NAMESERVER ALL
%DNS-E-CANTSTARTBACK, Cannot communicate with DNS$BACK process

So I suppose I ran into the same problem as mentioned in the TOOK::DNS
conferens - note 415.2.

Does anyone know what files that are involved in the communication with 
DNS$BACK?ex
 

Anna-Lena
539.10a few commentsDSTEG2::HUGHESThu Dec 13 1990 15:5713
    Did you get this error while starting the server? In order for the new
    files to take effect you would have had to stop the client and server
    then start them again. I have experienced times when I stop both
    client and server when not all the dns processes go away. There are 3
    dns* processes, make sure they go away before restarting.
    
    Can you see the DNS$BACK process when you do a show system? I would
    start by taking a close look at that process. I think I have experienced 
    most DNS errors! I have had problems with processes starting up, They 
    start then go away right away. 
    
    I hope this helps, Good Luck
    Linda
539.11Clerk/Server versions mismatch can cause th this...HERON::MORALESDEC:.VBO.EIS.Telecom.DTN828-5383Thu Dec 13 1990 18:0414
    
    I have just finished helping people on a similar problem...after copying
    the good dns executables (client,adver,solicit...) from another system,
    it works !!
    Everyone should be very careful before touching any DNS files. 
    
    rep .9
    
    Anna-Lena, 
    if you have copied dns files from another system, you may have a 
    protection problem on one of these files.
    
    	Manuel.
    
539.12I think I move on to the DNS-notesfile (but, you can see my results in this note)STKHLM::AMARTENSSONsmooth as iceThu Dec 13 1990 18:3326
I extracted all DNS-files from a VMSv5.4-kit and placed them in the right
places with the right protection. All other DNS-files were deleted
including the files in <DNS$SERVER>.

I reinstalled DNS v1.1 and got the following message in the end of 
the installation:


   =========================================================================
                     Starting VAX Distributed Name Service
   =========================================================================

Creating clearinghouse, please wait ...

Clearinghouse filename _____________ SYS$SYSROOT:[DNS$SERVER]knipan_ch.DNS

%DCL-I-TABEXIST, DNS$SYSTEM_TABLE already exists - not superseded
%RUN-S-PROC_ID, identification of created process is 20200142

%DNS-E-CANTSTARTBACK, Cannot communicate with DNS$BACK process
%VMSINSTAL-E-INSFAIL, The installation of DNS V1.1 has failed.


        VMSINSTAL procedure done at 21:17