[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

2230.0. "T1.2.4 Internal error in DECnet Phase IV AM" by FLYROC::GOYETTE () Thu Jan 30 1992 15:21


	Hi,

	I'm attempting to register a bunch of NODE 4 entities but I keep
	getting the following error message:

MCC> REGISTER NODE4 GUFFAW SYNONYM GUFFAW

Node4 FLYROC_NS:.GUFFAW
AT 30-JAN-1992 11:49:55

Partial registration success. Please retry later to complete the registration.
        Reason for Partial Registration = Internal error in DECnet Phase IV AM.
MCC> DEREGISTER NODE4 GUFFAW

Node4 GUFFAW
AT 30-JAN-1992 11:50:16

The entity Node4 GUFFAW  is not registered
                  Not Registered Entity = Node4 GUFFAW
MCC>


	I only get this error some of the time....that is, I can successfully
	register some NODE 4 entities...

	Any help would be appreciated...

	Thanks,

	Joe 8*)
T.RTitleUserPersonal
Name
DateLines
2230.1What is node4 GUFFAW?TOOK::TANEd TanThu Jan 30 1992 18:2345
    First of all, during REGISTRATION, the very first thing that happens is
    the namespace fullname is put in the namespace. In your case, the
    fullname is FLYROC_NS:.GUFFAW. Then REGISTRATION FM calls the DECnet
    Phase IV AM's REGISTER entry point, and then the SHOW ALL IDENTIFIERS
    entry point for the node's identifiers. If something fails during this
    call, the fullname is still in the namespace, and REGISTRATION FM will
    mark this entity as partially registered and return the error returned
    by the AM. In your case, the AM returns
    
    	Internal error in DECnet Phase IV AM.
    
    
    You should be able to do one of the following to see the partially
    registered entity
    
    	DIRECTORY NODE4 .GUFFAW
    	DIRECTORY NODE4 FLYROC_NS:.GUFFAW
    
    Note that the following is different from above, in that the name(s) above
    are namespace fullname, and the name in the following is Phase IV name
    
    	DIRECTORY NODE4 GUFFAW
    
    
    To deregister it, do one of the following
    
    	DEREGISTER NODE4 FLYROC_NS:.GUFFAW
    	DEREGISTER NODE4 .GUFFAW
    
    
    
    Please try the following to see if you can get the identifiers from the
    node4
    
    	SHOW NODE4 GUFFAW
    
    and also this to see if the Phase Name is in your NCP database
    
    	SHOW NODE4 0 REMOTE NODE GUFFAW
    
    
    One more thing, what is the node4 GUFFAW? Is it a VAX, or a PC running
    DECnet IV or what?
    
    /Ed
2230.2FLYROC::GOYETTEThu Jan 30 1992 18:5254

	GUFFAW is a vaxstation 3100...I get the same error trying to register
	other machines as well....all vaxes though...



DECmcc (T1.2.4)

MCC> DIRECTORY NODE4 .GUFFAW

Node4 FLYROC_NS:.GUFFAW
AT 30-JAN-1992 15:49:13

Directory successful, entity has only been partially registered.
                        Registered Name = FLYROC_NS:.GUFFAW
MCC> DIRECTORY NODE4 FLYROC_NS:.GUFFAW

Node4 FLYROC_NS:.GUFFAW
AT 30-JAN-1992 15:49:28

Directory successful, entity has only been partially registered.
                        Registered Name = FLYROC_NS:.GUFFAW
MCC> DIRECTORY NODE4 GUFFAW

Node4 GUFFAW
AT 30-JAN-1992 15:49:39

The entity Node4 GUFFAW  is not registered
                  Not Registered Entity = Node4 GUFFAW
MCC> SHOW NODE4 GUFFAW
Using default ALL IDENTIFIERS

Node4 31.652
AT 30-JAN-1992 15:50:49 Identifiers

Examination of Attributes shows:
                                Address = 31.652
                                   Name = GUFFAW
MCC> SHOW NODE4 0 REMOTE NODE GUFFAW
Using default ALL IDENTIFIERS

Node4 31.663 Remote Node 31.652
AT 30-JAN-1992 15:51:13 Identifiers

Examination of Attributes shows:
                                Address = 31.652
                                   Name = GUFFAW
MCC>


	Does this help at all ?

	Joe 8*)
2230.3See if you can create a link in DNSTRM::KWAKThu Jan 30 1992 19:1912
    
    RE:.0
    
    One possibility of getting PHASE4 AM Internal error during registration
    is that you do not have DNS access rights to create a Phase4 name
    in .DNA_NODESYNONYM directory.
    
    Please check if you can create a softlink in the directory:
    	$ mcr dns$control
    	DNS> create link .dna_nodesynonym.foo .foo
    
    
2230.4I can register your node4TOOK::TANEd TanThu Jan 30 1992 19:2747
    Well, I tried to register your node4 and I was successful:
    
    MCC> REGISTER NODE4 GUFFAW SYNONYM GUFFAW
    
    Node4 MCC1_NS:.GUFFAW
    AT 30-JAN-1992 15:34:22
    
    Registration successful.
    MCC> dir node4 MCC1_NS:.GUFFAW
    
    Node4 MCC1_NS:.GUFFAW
    AT 30-JAN-1992 15:37:49
    
    Directory successful.
                            Registered Name = MCC1_NS:.GUFFAW
                                       Name = GUFFAW
                                    Address = 31.652
    MCC> dir node4 GUFFAW
    
    Node4 GUFFAW
    AT 30-JAN-1992 15:37:55
    
    Directory successful.
                            Registered Name = MCC1_NS:.GUFFAW
                                       Name = GUFFAW
                                    Address = 31.652
    MCC> dir node4 31.652
    
    Node4 31.652
    AT 30-JAN-1992 15:38:00
    
    Directory successful.
                            Registered Name = MCC1_NS:.GUFFAW
                                       Name = GUFFAW
                                    Address = 31.652
    
    

    Did you say you have been successful registering SOME node4? If so, for
    registering these node4 successfully, were you logged onto a different
    user account than the account you use when registering unsuccessfully?
    
    In .3, William mentioned that not having the appropriate access right
    to the directory .DNA_NODESYNONYM will cause Phase IV AM to return
    that internal error message.
    
    /Ed
2230.5Still no go ....FLYROC::GOYETTEFri Jan 31 1992 13:36106


	RE:.3

$ dnscp
DNS> create link .dna_nodesynonym.foo foo
UID ________________________________ aa-00-04-00-97-7e-40-20-72-6a-67-57-95-00



	RE: .4

	Commands are from FLYROC::SYSTEM....

$ manage/ente
DECmcc (T1.2.4)

MCC> REGISTER NODE4 GUFFAW SYNONYM GUFFAW

Node4 FLYROC_NS:.GUFFAW
AT 31-JAN-1992 10:24:18

Partial registration success. Please retry later to complete the registration.
        Reason for Partial Registration = Internal error in DECnet Phase IV AM.


MCC> REGISTER NODE4 SHORT1 SYNONYM SHORT1

Node4 FLYROC_NS:.SHORT1
AT 31-JAN-1992 10:25:00

Registration successful.


$ DNSCP
DNS> SHO ACCESS DIR .DNA_NODESYNONYM

 Entry ______ FLYROC::DNS$SERVER _ (FLYROC_NS:.DNS$IV.FLYROC.DNS$SERVER)
  Flags _____ NOPROPAGATE
  Rights ____ READ WRITE DELETE TEST CONTROL

 Entry ______ FLYROC_NS:.flyroc_ch
  Flags _____ NOPROPAGATE
  Rights ____ READ WRITE DELETE TEST CONTROL

 Entry ______ *::* _ (FLYROC_NS:.DNS$IV.*.*)
  Flags _____ PROPAGATE
  Rights ____ READ WRITE DELETE TEST CONTROL

 Entry ______ *::* _ (FLYROC_NS:.DNS$IV.*.*)
  Flags _____ DEFAULT PROPAGATE
  Rights ____ READ WRITE DELETE TEST CONTROL

 Entry ______ FLYROC_NS:.dna_registrar
  Flags _____ PROPAGATE GROUP
  Rights ____ READ WRITE DELETE TEST CONTROL

 Entry ______ FLYROC_NS:.dna_registrar
  Flags _____ DEFAULT PROPAGATE GROUP
  Rights ____ READ WRITE DELETE TEST CONTROL

 Entry ______ FLYROC_NS:.*...
  Flags _____ PROPAGATE
  Rights ____ READ

 Entry ______ FLYROC_NS:.*...
  Flags _____ DEFAULT PROPAGATE
  Rights ____ READ

 Entry ______ zetar::* _ (FLYROC_NS:.DNS$IV.zetar.*)
  Flags _____ DEFAULT PROPAGATE
  Rights ____ READ WRITE DELETE TEST CONTROL

 Entry ______ FLYROC::SYSTEM _ (FLYROC_NS:.DNS$IV.FLYROC.SYSTEM)
  Flags _____ PROPAGATE
  Rights ____ READ

DNS> SHO DIR .DNA_NODESYNONYM LINK
 Link _______ AMUZED
 Link _______ EPSYS
 Link _______ FENNEL
 Link _______ FLYROC
 Link _______ foo
 Link _______ GIGGLS
 Link _______ HEEHEE
 Link _______ HOHO
 Link _______ ISE001
 Link _______ ISE002
 Link _______ ISE003
 Link _______ ISE005
 Link _______ ISE006
 Link _______ JOVIAL
 Link _______ LAFTER
 Link _______ ROSMRY
 Link _______ SHORT1
 Link _______ TTBPST
 Link _______ TTBR01
 Link _______ WITTY
 Link _______ ZETAR



	Anything else I can try ?

	Joe
2230.6TOOK::R_SPENCENets don't fail me now...Wed Feb 05 1992 13:146
    Hmm, in V1.1 if you tried that register directive I think it would
    complain about the registered name not being a "fullname" cause there
    was no dot in front of it (not that I think that it should be an
    issue). Maybe 1.2 changed something here?
    
    s/rob
2230.7Tried .6...FLYROC::GOYETTEWed Feb 05 1992 14:1442

POW$BUILD-> manage/enter
DECmcc (T1.2.4)

MCC> REGISTER NODE4 .GUFFAW SYNONYM GUFFAW

Node4 FLYROC_NS:.GUFFAW
AT  5-FEB-1992 11:09:45

The requested operation cannot be completed
                      MCC Routine Error = %DNS-E-DANGLINGLINK, Link points to
                                          nonexistant entry

POW$BUILD-> dnscp
DNS> sho dir .dna_nodesynonym kno links
 Link _______ AMUZED
 Link _______ EPSYS
 Link _______ FENNEL
 Link _______ FLYROC
 Link _______ GIGGLS
 Link _______ HEEHEE
 Link _______ HOHO
 Link _______ ISE001
 Link _______ ISE002
 Link _______ ISE003
 Link _______ ISE005
 Link _______ ISE006
 Link _______ JOVIAL
 Link _______ LAFTER
 Link _______ ROSMRY
 Link _______ SHORT1
 Link _______ TTBPST
 Link _______ TTBR01
 Link _______ WITTY
 Link _______ ZETAR


	Do you think my namespace is screwed up somehow ? Is there a way to
	remove all of the DECmcc dirs, objects, etc from it and start over ?

	Joe
2230.8look for backtranslationICS::WOODCOCKWed Feb 05 1992 14:4932
>The requested operation cannot be completed
>                      MCC Routine Error = %DNS-E-DANGLINGLINK, Link points to
>                                          nonexistant entry

>	Do you think my namespace is screwed up somehow ? Is there a way to
>	remove all of the DECmcc dirs, objects, etc from it and start over ?
	
Hi Joe,

I've seen this DANGLINGLINK error before. I think the problem was in 
backtranslation. You could try the following commands if your game:

DNS> show link .dna_backtranslation.%x49.%x0002.%xAA0004008C7E know attr

If the link is there try:

DNS> show link .dna_backtranslation.%x49.%x0002.%xAA0004000E08 attr DNS$LinkTarg
et

It should point to GUFFAW

then you could try:

DNS> delete link .dna_backtranslation.%x49.%x0002.%xAA0004008C7E


then:

MCC> register node4 .GUFFAW syn GUFFAW

regards,
brad...
2230.9Nope....FLYROC::GOYETTEWed Feb 05 1992 16:1913

DNS> show link .dna_backtranslation.%x49.%x0002.%xAA0004008C7E know attr
 %DNS-E-UNKNOWNENTRY, Requested entry does not exist


	No luck with that either.....

	Is there a way to clean out all of the MCC information from DNS ?

	I'd like to just start over if I can ( easily that is )....

	Joe
2230.10sorry, try thisICS::WOODCOCKWed Feb 05 1992 17:4226
>>DNS> show link .dna_backtranslation.%x49.%x0002.%xAA0004008C7E know attr
>> %DNS-E-UNKNOWNENTRY, Requested entry does not exist


>	No luck with that either.....

>	Is there a way to clean out all of the MCC information from DNS ?

>	I'd like to just start over if I can ( easily that is )....

>	Joe

Sorry Joe,

I gave you bum info. I was 'playing' with the commands for an area 2 node
and I transferred that with GUFFAW hardware address. The command should be:

DNS> show link .dna_backtranslation.%x49.%x001F.%xAA0004008C7E know attr
                                         ^^^^^^
                                         area 31

If this doesn't work I'm not sure what your best course is..

regards,
brad...
                                          
2230.11YES !FLYROC::GOYETTEWed Feb 05 1992 18:2140

	ALRIGHT !!!!!!!

	Now we're getting somewhere !!!!

POW$BUILD-> dnscp
DNS> show link .dna_backtranslation.%x49.%x001F.%xAA0004008C7E know attr
 Attribute (Set) ______ DNS$ACS
 Attribute (Single) ___ DNS$LinkTarget
 Attribute (Single) ___ DNS$LinkTimeout
 Attribute (Single) ___ DNS$UID
 Attribute (Single) ___ DNS$UTS

DNS> show link .dna_backtranslation.%x49.%x001F.%xAA0004008C7E attr DNS$LinkTarg
et
  Target __________________ FLYROC_NS:.DNA_NODE.GUFFAW
  Timestamp _ 18-FEB-1991 19:09:30.54 aa-00-04-00-97-7e
DNS> delete link .dna_backtranslation.%x49.%x001F.%xAA0004008C7E
DNS> exit

POW$BUILD-> manage/enter
DECmcc (T1.2.4)

MCC> REGISTER NODE4 GUFFAW SYNONYM GUFFAW

Node4 FLYROC_NS:.GUFFAW
AT  5-FEB-1992 15:18:09

Registration successful.


	Now....How the heck did you come up with that god awful string of
	characters which represent GUFFAW ?  I have a few other nodes which
	fail registration with the same error and I'd like to try this on
	them...

	Thanks a HUGE LOT for the help.....

	Joe 8*)
2230.12link id breakdownICS::WOODCOCKWed Feb 05 1992 20:4827

>	Now....How the heck did you come up with that god awful string of
>	characters which represent GUFFAW ?  I have a few other nodes which
>	fail registration with the same error and I'd like to try this on
>	them...
>
>	Thanks a HUGE LOT for the help.....
>
>	Joe 8*)

.dna_backtranslation.%x49.%x001F.%xAA0004008C7E


Glad to see it worked. The number above can be broken down to:

%x49 = IDP you set up the namespace as (currently all of DEC is most likely
       using this value, phase_v and mcc)

%x001F = the area number converted to hex (31=1F in hex)

%xAA0004008C7E = the physical address of the system without the dashes
                 (found by NCP> tel GUFFAW show exec status)


happy hunting,
brad...
2230.13FLYROC::GOYETTEThu Feb 06 1992 11:4710

	Got it...

	I was able remove the old DNS back translation links to the other
	nodes and the successfully register them again...

	Your assistance was much appreciated.

	Joe 8*)