Conference azur::mcc

The iconic map currently uses the SHOW directive to get the contents of 
a domain.

The error message being displayed is not to helpful. The Iconic Map code
checks to makes sure that the class information of each entity returned from 
the SHOW DOMAIN operation is in the dictionary.  It appears that the open
domain operation is finding a domain member whose class information is not 
in the dictionary.  I don't understand why it occurs randomly.  


Try doing the following from the FCL.  

	SHOW DOMAIN <domain> MEMBER *

Let me know if there is an entity returned whose class information
is not in the dictionary after executing the above command a couple of times.  


Is anyone else experiencing this problem?


/Jim

MCC> show domain reolan member *
Using default ALL IDENTIFIERS
Domain IAN:.reolan Member Node IAN:.REO.ULTDNS
Identifiers
AT  1-AUG-1990 15:09:51


Examination of attributes shows
                             MemberName = Node IAN:.REO.ULTDNS
Domain IAN:.reolan Member Node IAN:.REO.ENGR11
Identifiers
AT  1-AUG-1990 15:09:54


Examination of attributes shows
                             MemberName = Node IAN:.REO.ENGR11
Domain IAN:.reolan Member Node IAN:.REO.ENGR12
Identifiers
AT  1-AUG-1990 15:09:55


Examination of attributes shows
                             MemberName = Node IAN:.REO.ENGR12
Domain IAN:.reolan Member Node IAN:.REO.ENGR25
Identifiers
AT  1-AUG-1990 15:09:55


Examination of attributes shows
                             MemberName = Node IAN:.REO.ENGR25
Domain IAN:.reolan Member Node IAN:.reo.engr27
Identifiers
AT  1-AUG-1990 15:09:56


Examination of attributes shows
                             MemberName = Node IAN:.reo.engr27
Domain IAN:.reolan Member
Identifiers
AT  1-AUG-1990 15:09:57


No such entity: Domain IAN:.reolan Member
                         Unknown Entity = Domain IAN:.reolan Member
MCC>

I have tried executing that command a number of times and cannot clear the error
The entities that are missing are 2 SNMP nodes. However SNMP is not the problem
as I only created this particular domain today, and I haven't been using the 
SNMP am from the icon interface before this morning - I have had the problem
with other domains. 

This doesn't make much sense...

I have another domain called PETE3 - from my workstation I can open this domain 
with no problems. Yet from a different account I get the same error message as 
.0 - and this domain was created from that account. 

MCC> show domain pete3 member *
Using default ALL IDENTIFIERS
Domain IAN:.pete3 Member Node IAN:.REO.ENGR25
Identifiers
AT  1-AUG-1990 15:46:51


Examination of attributes shows
                             MemberName = Node IAN:.REO.ENGR25
Domain IAN:.pete3 Member Node IAN:.reo.engr27
Identifiers
AT  1-AUG-1990 15:46:53


Examination of attributes shows
                             MemberName = Node IAN:.reo.engr27
Domain IAN:.pete3 Member Node4 IAN:.REO.ENGR20
Identifiers
AT  1-AUG-1990 15:46:54


Examination of attributes shows
                             MemberName = Node4 IAN:.REO.ENGR20
Domain IAN:.pete3 Member Node4 IAN:.REO.ENGR21
Identifiers
AT  1-AUG-1990 15:46:54


Examination of attributes shows
                             MemberName = Node4 IAN:.REO.ENGR21
Domain IAN:.pete3 Member Node4 IAN:.REO.ENGR22
Identifiers
AT  1-AUG-1990 15:46:55


Examination of attributes shows
                             MemberName = Node4 IAN:.REO.ENGR22
Domain IAN:.pete3 Member Node4 IAN:.REO.ENGR23
Identifiers
AT  1-AUG-1990 15:46:56


Examination of attributes shows
                             MemberName = Node4 IAN:.REO.ENGR23
Domain IAN:.pete3 Member Node4 IAN:.REO.A44RT7
Identifiers
AT  1-AUG-1990 15:47:02


Examination of attributes shows
                             MemberName = Node IAN:.REO.ULTDNS
MCC>

Hope that this is of some help.


Ian

Im guessing here but do both accounts have the same access to the 
mcc datafiles and DNS?   

	I am working on a similar problem on my DECmcc system (IFT 1.1)
	I get the same "funny" message when I try to open a domain demo1.
	I have done the following:

		1- I removed the MCC$_domain-name.DAT from my directory
		   ....> I can open the domain but the icons are not placed
			 and lines are missing (as expected).

		2- I have been removing items step by step and it seems that
		   I can't open the domain when I add either a bridge icon or
		   a domain, but just with node4 and station icons it works.

		3- By modifying the mcc_code of the icon description in the
		   MCC$_domain-name.DAT with a wrong value, I get the same 
		   error message.

	MCC> sho domain demo1 member *  (gives no error)

		hope this help,

			Manuel.

	I don't know the good mcc_code for icons but the problem seems to
	happen mainly with big mcc_code values:
	
	LANbridge 100 = 1224753456
	Dmain 	      = 1469100
	Vitalink TLans= 1162104654
	
	
		Manuel.

ps: lines and text are OK (no mcc_code)

re: .5

So if I understand this right, your map file has the mcc_code values listed
in .5?   

	I don't know how but mcc_code are taking wrong values in some of
	my map files.These are the bridge mcc_code (changes from 9 to something 
	very big) and the domain mcc_code that changes from 8 to 1469100.
	
	here follows an extract of one of my map that gives the error.
	If I restore the good mcc_code the display of the map works fine.
	
		Manuel.

 version 0
 domain DEMO1
 last_x 0.000000 last_y 4.317721

 object_type 1
   icon_file MCC_NODE4_WS_VAX_ICON.DAT
   mcc_code 12
   center_x 1.000705   center_y 5.546552
   text_x 0.948730   text_y 5.593954
   name   DNA_NODE.NICAE

 object_type 1
   icon_file MCC_NODE4_LAVC_ICON.DAT
   mcc_code 12
   center_x 0.693012   center_y 5.596448
   text_x 0.621287   text_y 5.641771
   name   DNA_NODE.MGTI51

 object_type 1
   icon_file MCC_BRIDGE_ICON.DAT
   mcc_code 1162104654				<******** pb with this one
   center_x 1.060291   center_y 4.546348	(vitalink translan)
   text_x 1.117464   text_y 4.526182
   name   A1VB3

 object_type 1
   icon_file MCC_BRIDGE_ICON.DAT
   mcc_code 1162084403				<******** pb with this one
   center_x 1.056133   center_y 4.783354	(vitalink translan)
   text_x 1.113306   text_y 4.767346
   name   E2VB3

 object_type 1
   icon_file MCC_DOMAIN_ICON.DAT
   mcc_code 1469100				<******** pb with this one
   center_x 1.230769   center_y 4.355080
   text_x 1.274428   text_y 4.338032
   name   LAN-ALGO1

 object_type 1
   icon_file MCC_BRIDGE_LANBRIDGE_200_ICON.DAT	<******** pb with this one
   mcc_code 1229016399
   center_x 0.661123   center_y 4.797907
   text_x 0.742204   text_y 4.779819
   name   LB200A

 object_type 1
   icon_file MCC_BRIDGE_LANBRIDGE_100_ICON.DAT
   mcc_code 1224753456				<******** pb with this one
   center_x 1.224532   center_y 5.032834
   text_x 1.301455   text_y 5.017866
   name   NETLAB

 object_type 2
   var 1
   width 0.006000
   start_x 0.332848 start_y 4.533459
   stop_x 0.332848 stop_y 4.684318


	 .... more info on lines (ok)

Jim,

Re .3 both accounts have the same access to DNS - all access is controlled by 
groups. 

Re. 4 and .5 I have the same.

My MCC$_REOLAN.DAT looks like this...


 version 0
 domain REOLAN
 last_x 0.000000 last_y 3.415801

 object_type 1
   icon_file MCC_NODE_DECNET_OSI_HOST_ICON.DAT
   mcc_code 1
   center_x 0.133056   center_y 4.787942
   text_x 0.046778   text_y 4.718919
   name   .REO.ULTDNS

 object_type 1
   icon_file MCC_NODE_L1_ICON.DAT
   mcc_code 1414288686
   center_x 0.124740   center_y 4.505198
   text_x 0.039501   text_y 4.424740
   name   .REO.ENGR11

 object_type 1
   icon_file MCC_NODE_L1_ICON.DAT
   mcc_code 1196311854
   center_x 0.376299   center_y 4.496881
   text_x 0.291060   text_y 4.416424
   name   .REO.ENGR12

 object_type 1
   icon_file MCC_NODE_L2_ICON.DAT
   mcc_code 5439556
   center_x 0.118503   center_y 4.214137
   text_x 0.033264   text_y 4.133679
   name   .REO.ENGR25

 object_type 1
   icon_file MCC_NODE_L2_ICON.DAT
   mcc_code 5439556
   center_x 0.376299   center_y 4.224532
   text_x 0.291060   text_y 4.144074
   name   .REO.ENGR27

 object_type 1
   icon_file MCC_SNMP_ICON.DAT
   mcc_code 18
   center_x 0.397089   center_y 4.775468
   text_x 0.345114   text_y 4.695010
   name   ULTDNS

 object_type 1
   icon_file MCC_SNMP_ICON.DAT
   mcc_code 18
   center_x 0.604990   center_y 4.775468
   text_x 0.550936   text_y 4.695010
   name   SMGULT

If I remove all mcc_codes with a large number, so that only the values 18 and 1 
are remaining then I can open up the domain okay.

Ian

    Manuel, Ian,
    
    The mcc_codes in the map files should match the mcc codes that are in
    the dictionary.  What are they in the dictionary?
    
    Fred

	Fred,

	In fact in my case, I can create new domains with icons and work
	with them for a while and sometimes when I try to open again
	a domain that was OK previously, I get the error.
	I tried to reproduce it on a working MAp, without success.It happens
	randomly (??) or
	it looks like after a specific update of the MAP file, wrong codes
	are entered in the description of the entities contained in that MAP file..

Anyway,here are the mcc codes in the disctionary, they seem OK.

		Thanks for your help.
			
				Manuel.


        DECmcc Dictionary Administrator Program   Version T1.0.1

DAP> show

   Class (1) : BRIDGE 9
   Class (1) : COMMON 52
   Class (1) : DOMAIN 8
   Class (1) : MCC 7
   Class (1) : NODE 1
   Class (1) : NODE4 12
   Class (1) : SAMPLE 15
   Class (1) : STATION 11

Fred,

As with Manuel my maps appear to corrupt after a time. the dictionary looks okay
though...
        DECmcc Dictionary Administrator Program   Version T1.0.1

DAP> show

   Class (1) : BRIDGE 9
   Class (1) : COMMON 52
   Class (1) : DOMAIN 8
   Class (1) : MCC 7
   Class (1) : NODE 1
   Class (1) : NODE4 12
   Class (1) : SAMPLE 15
   Class (1) : SNMP 18
   Class (1) : STATION 11

DAP>

Regards

Ian

Having just gotten to playing with maps with the iconic PM, the class code
values in my maps are also getting scrozzled. I haven't characterized the
pre-conditions yet.

 object_type 1
   icon_file MCC_DOMAIN_ICON.DAT
   mcc_code 1572164
   center_x 3.282502   center_y 7.512698
   text_x 3.157762   text_y 7.433280
   name   .KITTELL.CXN_SMD

That is a domain object, should be code 8.

I tried editing the .DAT file to fix the class codes. I was then able to
open the domain, but the map was incomplete. It turns out the map file
ended in the middle of the point list for an object 4 type.

It would seem that whatever trashes the class code may also be related to
the in-memory data structures not being completely written to the file.

    
    (I need an answer to this ASAP.  Posted once already, but no reply. 
    Feel free to forward to someone who can help.)
    
    I created a domain, then populated it with one of our global entities
    (called TPSYSTEMs).  These have special characters in them, because
    they are elements in a DCE namespace.  
    
    I was able to add the TPSYSTEM to the domain successfully, and operate 
    on it.  But once the domain was closed, it could never be reopened
    again.  I get the following error:
    
    Map Window Message: Entity instance syntax error.  Please check
    spelling.
    
    I am assuming it is because of the syntax of the entity instance (but
    why was I allowed to create such an entity instance?).  Is this a bug,
    or do I need to do something special to view a domain whose elements
    contain special characters?
    
    From the FCL, I issue the "show element *" command on the domain, and
    see that my TPSYSTEM is in fact there....
    
    MCC> show domain marc8 member *
    Using default ALL IDENTIFIERS
    
    Domain TPEDNS_NS:.marc8 Member TPEDNS_NS:."/.:/mgs_cd8_ns/mgs_tpsys"
    AT 14-APR-1993 10:00:20 Identifiers
    
    Examination of attributes shows
                           MemberName = TPEDNS_NS:."/.:/mgs_cd8_ns/mgs_tpsys"
    
        
    Any advice?
    
    Marc
          

    Marc,
    
    Try the following to see if you might possibly have registered the
    domain improperly.
    
    MCC> DIRECTORY DOMAIN *
    
    I have found that you can enter anything in the ID and DIRECTORY fields
    when creating a domain, and big problems result later.
    
    As a work around, create a new domain, populate it with the members of
    the TPSYSTEMs domain.
    
    I agree there should be more checking done for domain creation and
    entity registration.
    
    -Dan

    
>    Try the following to see if you might possibly have registered the
>    domain improperly.
    
>    MCC> DIRECTORY DOMAIN *
 
    Did it, here is the output (abridged):
    
    MCC>  DIRECTORY DOMAIN *
    
    Domain TPEDNS_NS:.marc8
    AT 14-APR-1993 12:45:17
    
    Directory successful.
                                 DomainName = TPEDNS_NS:.marc8
    
    Domain TPEDNS_NS:.marc9
    AT 14-APR-1993 12:45:18
    
    Directory successful.
                                 DomainName = TPEDNS_NS:.marc9
    
    Domain TPEDNS_NS:.QMA.EUROPE
    AT 14-APR-1993 12:45:26
    
    Directory successful.
    
    MCC>
    
    So I assume it was registered correctly.
       
    >I have found that you can enter anything in the ID and DIRECTORY fields
    >when creating a domain, and big problems result later.
    
    I had my agent running in the debugger, adn I saw the "register"
    successfully make calls to teh agent routines.
    
    
    >As a work around, create a new domain, populate it with the members of
    >the TPSYSTEMs domain.
    
    
    Tried it, same thing...
    
    
    >I agree there should be more checking done for domain creation and
    >entity registration.
    
    I'm less concerned about the checking on the create than I am about the
    possibility that I cannot use my entity naming convention for a global
    entity!  If the create would have the same checking as the "open",
    would it have rejected my entity being added to a domain?  Why?  It is
    a legal entity....
    
    

Were you able to add the entity via the iconic map?   The iconic map filters
off the "namespace:."  when writing to the map file.  It looks for ":."
to see if the namespace was entered.   

Edit the map file created and look for your entity in it.  I believe 
everything up to and including the ":." was stripped off.  

/jim

The iconic map takes the entity in the map file, parses it to build an
abstract entity spec, and then does an AES_EQUALS with the domain member
returned from the show domain member * call.   If the namespace is not
stripped off, the entities in the domain will not be equal to the 
entities in the map file when you change your namespace.

/Jim

    
    >Were you able to add the entity via the iconic map? 
    
    Yes, that is how the entity was created.
                                                             
>    Edit the map file created and look for your entity in it.  I believe
    everything up to and including the ":." was stripped off.
    
    That is correct.  Here is the map file:
    
     version 2
     domain marc6
     last_x 0.000000 last_y 4.043659
    
     object_type 1
       icon_file mcc_tpsystem_icon.dat
       mcc_code 35
       center_x 0.451143   center_y 4.810811
       text_x 0.228690   text_y 4.730353
       ident_dt 5
       name   /.:/mgs_cd8_ns/cd8j_macrow
    
    
    Now I'm concerned about the entity name.  When I created it, I enclosed
    the name in quotes (which was necessary with the FCL because of the
    special characters).  We rely on the quoted string in our entity name
    parsing.  Perhaps this is what is getting messed up?
    
    Because the output from the "SHOW DOMAIN marc6 MEMBER *" reveals the
    name as TPEDNS_NS:."/.:/mgs_cd8_ns/mgs_tpsys", the compare will NOT match
    because the entity name is quoted, correct?
     
                                                              

    I am sorta able to reproduce this using the REFERENCE entity.   I get
    the error message displayed on the status line but the domain still
    opens.  
    
    Now for a couple of questions...
    
    	1. what version of mcc
    	2. vms or ultrix
    	3. local_mir or DNS?
    
    thanks
    /Jim

    
    Thanks for the reply, Jim.
    
    1 what version of mcc?   DECmcc (V1.2.3)
    
    2 vms or ultrix    - VMS
    
    3 local_mir or DNS? - Um, being the agent developer and not the AM
    developer, I'm not sure I know what you mean.  The entity instance
    names are prefixed by DNS names, is that what you mean?  The global
    entity is registered with DNS, though if that is the correct answer..
    
    MGS
    

    MCC allows you to store your info in the DNS namespace or
    in a local repository (local_mir).   Show the logical
    MCC_DNS_SELECTION to find out if it is using MIR or DNS.
    
    /JIM

    
      "MCC_DNS_SELECTION" = "DNS"
    

There appears to be at least two problems.  

	1. the map save code filters out all quotes in the 
	   entity instance string before writing it to the 
	   file.  

	   this code was written in 1989 and I don't have a 
	   clue to why it is needed.    I removed the call from
	   a local copy and works ok.   

	2. On ULTRIX the parse routine doesn't accept quotes in
	   the fullname datatype!   

I qared both of these bugs (554,555 in MCC013_INT).

/Jim

    
    
    Jim,
    
    Do you know when I can expect to see a fix (particularly for the first
    problem in the previous reply) in a kit?
    
    Thanks,
    
    Marc