[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

5808.0. "Registration FM Specialized exception handling" by ATYISA::ROGGEBAND (Unplugged) Thu Jan 06 1994 08:27

    Hello,
    
    We have observerd the following behaviour with the Registration FM with
    a home-written AM :
    
    If the REGISTER entry point of our access module returns a specialized
    exception, the REGISTRATION FM does not roll-back the creation of the
    entity, it does not call the "SHOW ALL IDENT" entry point of the AM,
    but it returns a "success" response to the PM. If we then try to access
    the entity, we get the usual "entity was partially registered" message.
    
    While the above behaviour may be "normal", I would have expected the
    REGISTRATION FM to return the same specialized exception to the caller? 
    
    Any comments?
    
    Philippe.

T.R	Title	User	Personal Name	Date	Lines
5808.1		TAEC::GUERTIN		`Thu Jan 13 1994 12:39`	12
	Does it say, "please retry later to complete the registration"? If it does, then it should display an MCC-Message containing the reason for the partial registration. If it doesn't display the MCC-Message information, then it's probably a bug in the Registration FM. If all else fails, you could try returning a common exception (like "cannot complete operation", with the reason as the argument). By the way, does your DEREGISTER entry point get called? -Matt.
5808.2		ATYISA::ROGGEBAND	Unplugged	`Mon Jan 17 1994 12:42`	24
	Matt, > Does it say, "please retry later to complete the registration"? If it > does, then it should display an MCC-Message containing the reason for > the partial registration. If it doesn't display the MCC-Message > information, then it's probably a bug in the Registration FM. Nope, it says "success", so I guess it's a bug. > If all else fails, you could try returning a common exception (like > "cannot complete operation", with the reason as the argument). The problem is that the reason is "Trigramme Invalide" (i.e. a customer-specific argument validation failure), which was why we wanted a specialized exception. > By the way, does your DEREGISTER entry point get called? I'll have to check, but I don't think so, as I have traces turned on, and don't remember seeing anything. Amicalement, Philippe.
5808.3	Anybody home?	ATYISA::ROGGEBAND	Unplugged	`Fri Jan 28 1994 04:47`	1

5808.4		ATYISA::ROGGEBAND	Unplugged	`Mon Feb 14 1994 11:08`	6
	Helmlo, My customer is getting a little bit impatient. Can anyone help me out on this one? �hR.
5808.5	Sounds like a bug	TAEC::FLAUW	Marc Flauw, CEM Technical Office, VBO	`Tue Feb 15 1994 10:44`	17
	Philippe, On a specialised exception from the AM, the Registration FM should return you the "partial registration" exception with the specialised exception attached in the arguments of this exception. If it doesn't do that, it's likely to be a bug that needs to be reported. One thing to check before that is whether there was already an entry in the namespce or not for that entity. Did you try to deregister or even to erase the entity from the namespace ? You can try also turning on the Registration FM log bits. You can try 0x5 or 0xC This should give you additional info. Hope this helps, Marc.