Conference azur::mcc

4719.0. "%MCC-E-ILVTNF, specified tag not MCC-E-ILVTNF, specified tag not found within current constructor" by MASSIN::RAOULT () Thu Mar 18 1993 14:25

	Hi,

	Config:
		MCCBMS V1.2
	
		MCCTRANSLAN012 (official kit for customer)

		DNS V1.1
		Translan III v 6.10.2

		Translan 350 v 10.4.3
	
	
	I found a bug during registration of Tranlan entities on a customer site.
	Fisrt I was able to register/manage 4 translan III without any Pb.
	Then I registered two Translan's 350 without any error message, BUT :

		- I got the following message either through IMPM or FCL for
		  
                     MCC Routine Error = %MCC-E-ILVTNF,  specified tag not
                                          found within current constructor
	
	These 2 Translan 350 are reachable and manageable from my Designated
	root(translan III) with  vitalink commands.
	With DNS$control i didn't found the back link to their address for these 2
	entities.
	Back to the office I tried to register several translan easynet with
	my station running bms v1.2 but with local naming option.

	I found one translan 350 (fgttl1 08-00-7c-1d-2a) with the same pb.
	I set the logical  mcc_translan_am_log to track the errors
	Following the results :
			   
MCC> dir translan bug		

TRANSLAN LOCAL_NS:.bug
AT 18-MAR-1993 19:31:42

Directory successful.
	                                   Name = LOCAL_NS:.bug
				---> no address  <------

MCC> dir translan evttl2   (also Translan 350 with the same version)

TRANSLAN LOCAL_NS:.evttl2
AT 18-MAR-1993 19:31:50

Directory successful.
                                   Name = LOCAL_NS:.evttl2
                                Address = { 08-00-7C-00-1C-1E }
MCC> show translan bug
Using default ALL IDENTIFIERS

TRANSLAN LOCAL_NS:.bug
AT 18-MAR-1993 19:32:09 Identifiers

The requested operation cannot be completed

                     MCC Routine Error = %MCC-E-ILVTNF,  specified tag not
                                          found within current constructor

--->	trace found in mcc_translan_am.log 

DECmcc Debug logging turned on here.
Trace data starting at: 18-MAR-1993 19:32:09.87

*
* mcc_translan_am_show_bridge Entry Point
* 18-MAR-1993 19:32:09.91
*
*
* mcc_translan_am_show_bridge Exit Point
* 18-MAR-1993 19:32:09.97
*
*
MCC> show translan evttl2
Using default ALL IDENTIFIERS

TRANSLAN LOCAL_NS:.evttl2
AT 18-MAR-1993 19:32:20 Identifiers

Examination of attributes shows:
                                   Name = LOCAL_NS:.evttl2
                                Address = { 08-00-7C-00-1C-1E }

* mcc_translan_am_show_bridge Entry Point
* 18-MAR-1993 19:32:18.90
*
*
* mcc_bridge_am__call_cea -> mcc_ea_request_enet_packet. REQUEST:
* 18-MAR-1993 19:32:18.96
*
* Buffer Dump :
* Buffer Address = 001A0AB2  (   1706674 dec)
* Buffer size    = 0000000F  (        15 dec)
*
*                    Hex                                 Ascii        Offset
* A2 0D A1 0B A0 05 A0 03 C2 01 01 81 02 00 01     ...............   0000000F
*
*
* mcc_ea_request_enet_packet Completed. RESPONSE:
* 18-MAR-1993 19:32:19.09
*
* Buffer Dump :
* Buffer Address = 001A1150  (   1708368 dec)
* Buffer size    = 000000B5  (       181 dec)
*
*                    Hex                                 Ascii        Offset
* A3 81 B2 A1 81 AF 81 02 00 01 C5 01 01 C4 81 A5  ................  00000010
* 9F 81 03 06 08 00 7C 00 1C 1E 9F 84 00 06 00 00  ......|.........  00000020
* 00 34 FD 3E 9F C3 0F 01 00 9F 83 03 08 00 20 08  .4.>............  00000030
* 00 2B 19 85 4A 9F 82 08 08 00 7D 08 00 7C 00 1C  .+..J.....}..|..  00000040
* 1E 9F C2 08 02 00 01 9F C3 06 01 00 9F 83 05 04  ................  00000050
* 00 00 00 0A 9F 83 0A 02 00 01 9F 82 0E 02 00 01  ................  00000060
* 9F 83 0B 02 00 0F 9F 82 0F 02 00 0F 9F 83 0C 02  ................  00000070
* 00 1E 9F 82 10 02 00 1E 9F 82 09 01 0F 9F 82 0A  ................  00000080
* 01 05 9F 83 01 02 09 D6 9F 82 04 04 00 00 10 00  ................  00000090
* 9F C2 06 02 00 00 9F 82 07 01 1E 9F C2 20 01 01  ................  000000A0
* 9F 81 00 02 00 06 9F C1 01 06 31 30 2E 34 2E 33  ..........10.4.3  000000B0
* 9F C2 02 01 80                                   .....             000000B5
*
*
* mcc_bridge_am__call_cea -> mcc_ea_request_enet_packet. REQUEST:
* 18-MAR-1993 19:32:19.11
*
			and so on

	Thanks in advance.

							Fabrice.

		

    Hi,

        I found that the message "specified tag not found within current constru
ctor" is only the consequence of a bad registration.

        My customer gave me two bad addresses (for 2 translans not yet installed),
	and the translan on easynet was temporally disconnected.

        So,if you try to register a translan with an address = 00-00-00-00-00-00
        you will get from the AM a response message "successful registration".

        The bug is there,this AM doesn't check the full access on the entity when
        register it(or give always a successful I think because you can't find the
        address with: dir translan "bug",either with LNO or DNS)


        An official SPR is escalated through French Support Team .
	Regards.

						Fabrice.

    
    Hello,
    
    A customer is getting the same error with a translan 350 v10.4.2.
    
    He only gets it on one of his Translans and he has double checked the
    address. 
    
    The only difference between the Bridges as far as the customer can see
    is that the one he has problems with sais Rev A on the label on the
    back, while the ones that are OK have Rev C.
    
    Anyone any ideas?
    
    Thanks,
    
    Jon
    
    

    rev may well be significant. Best way to check is through the
    release notes or contacting the vendor.