Conference azur::mcc

    The error that you're seeing is a dictionary error message.  The PMs,
    upon processing out_p, goes to the dictionary to get various pieces of
    data to figure out how to decode out_p.  In previous cases, whenever
    this message is seen, the dictionary was not correct in the sense that
    not all the info that the PMs need is there.
    
    Please check that the Response arguments are indeed there for the
    Create directive under the Physical Entry entity class.  
    
    Christine
    

Thanks, Christine,

	I did find a bug in .MS file, and FCL works fine now.

	IMPM, though, still returns a 'No such entity' error when
	Create returns an (empty) AttribList arg in Response. 

	All our Creates have attributes defined as Request arguments, i.e.,
	they combine Create & Set. This is why I need the Response argument.

	If AttribList is a problem for IMPM right now, I would appreciate
	some quick workaround.

Thanks,
Herman

Herman,

AttribList is not a problem for the Iconic Map. We handle empty AttribList
arguments for directory bridge forwarding database with no problem.

The operation you can do successfully in FCL is not the same operation that
the Iconic Map does.  We append the in domain qualifier to the operation.
Thus, to simulate the same thing, please try your create operation with
in domain at the end and let us know how it works.

Verna

	Verna, thanks a lot,
	I think I have found the source of the problem, following your
	suggestions. 

	The message is generated because the parent entity (Forwarding DB)
	of the entity being created has not been registered. 

	After I register the parent entity via FCL, a la
		register bridge xxx forwarding database

	the Creates for its children work just fine.

	This is, however, confusing for the users because:
		- IMPM displays the NOENTITY error message AFTER the actual
		  Create has already been done by AM; this may leave the user
		  confused as to the outcome of the Create, unless he/she
		  understands how it works;

		- the MCC Use manual just says vaguely that 'you can add the 
		  child (to the map) after the parent has been added. But,
		  in our case, the parent (Forw DB) is already displayed
		  on the map, like

			FORWARDING DATABASE
				PHYSICAL ENTRY
				MULTICAST ENTRY
				........
				STATIC ENTRY		  
		  
		  so it is not clear to the user, why the NOENTITY message.

		- if I register the parent via IMPM Add toolbox, IMPM
		  displays 'entity already exists' error message.
		  However, Creates work fine afterwards.
		 
	So, it seems that this needs a fix in IMPM, to avoid user confusion.

	(Or, am I confused and this is a feature?)
Thanks,
Herman