Conference azur::mcc

993.0. "MCC-E-NOENTITY problem" by LEVERS::LEVENSON () Tue May 07 1991 16:49

Hi,
	This is a question for both FCL and IMPM.

	I have a Bridge AM (enhanced), with a Create directive defined
	with arguments. The Request arguments are regular (primitive) data 
	types. 
	The Response agument is defined as an AttributeList.

	The same code in AM supports two different (but similar) entity classes:
	Static Entries and Physical Entries.

	The Problem:  when I am applying the Create without (or with) input args
	to a bridge, it works successfully for both Static and Physical Entry 
	(see log below), but for a Physical Entry the PM displays a 
	MCC-E-NOENTITY message after reporting a successful Create. 

	As you can see in the ILV dump below, in both cases the AM is returning
	empty AttributeList argument in a success Response, and is copying 
	the In_Entity into the Out_Entity.

	I can't figure out the cause of the MCC-E_NOENTITY message, without
	knowing what is it that FCL (or IMPM) doesn't like.

	For IMPM, it is worse - for both Static and Physical Entries I see
	the NOENTITY error message (although the Create itself was a success).

	If I define Create without Response arguments, everything works fine.

	Would appreciate any suggestions. Could returning an empty AttributeList
	cause problems here? 

Thanks a lot,
Herman
=============================================================================
MCC> create bri ni3 fo da st en 08-00-2b-13-22-33	- (this works fine)
*****************************************************
*     FCL PM Arguments before call_function:        *
*****************************************************
VERB code:      12
PARTITION code: 10
AES dump of ENTITY IN:
depth=3 class code= 9 instance = �class code= 21 instance =  no curlen class cod
e= 9992 instance =
ILV dump of IN_P: in_p is NULL
ILV dump of IN_Q: in_q is NULL
TIME SPEC is: 0, NOW
%MCC-E-REVECTCONFLICT, revectoring conflict
-SYSTEM-F-DEBUG, command interpreter debugger signal at PC=0010A957, PSL=03C0000
0
**********************************************
FCL PM Arguments on return from call_function:
CVR returned:
%MCC-S-RESPONSE, success with response reply
ILV dump of OUT_P:

[  1 ] (
    [  1 ] (
        )
    )
AES dump of ENTITY OUT:
depth=3 class code= 9 instance = �class code= 21 instance =  no curlen class cod
e= 9992 instance =

BRIDGE DEGABA_NS:.ni3 FORWARDING DATABASE STATIC ENTRY 08-00-2B-13-22-33
AT  6-MAY-1991 18:43:41

Entry successfully created.
=============================================================================
MCC> create bri ni3 fo da ph en 08-00-2b-14-22-33  (this rtns with NOENTITY msg)
*****************************************************
*     FCL PM Arguments before call_function:        *
*****************************************************
VERB code:      12
PARTITION code: 10
AES dump of ENTITY IN:
depth=3 class code= 9 instance = �class code= 21 instance =  no curlen class cod
e= 36 instance =
                           
ILV dump of IN_P: in_p is NULL
ILV dump of IN_Q: in_q is NULL
TIME SPEC is: 0, NOW
%MCC-E-REVECTCONFLICT, revectoring conflict
-SYSTEM-F-DEBUG, command interpreter debugger signal at PC=0010A957, PSL=03C0000
0
**********************************************
FCL PM Arguments on return from call_function:
                                         
CVR returned:
%MCC-S-RESPONSE, success with response reply
ILV dump of OUT_P:

[  1 ] (
    [  1 ] (
        )
    )
AES dump of ENTITY OUT:
depth=3 class code= 9 instance = �class code= 21 instance =  no curlen class cod
e= 36 instance =

BRIDGE DEGABA_NS:.ni3 FORWARDING DATABASE PHYSICAL ENTRY 08-00-2B-14-22-33
AT  6-MAY-1991 18:44:40

Entity successfully created.
                                                       
%MCC-E-NOENTITY,  no corresponding entity instance exists

    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