[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

294.0. "Registration FM and exceptions, what does it expect in out_p ?" by BYBLOS::TAMER () Thu Aug 30 1990 13:05

I am forcing my AM entry point for the Register directive to reject it (and
return to the Registartion FM as follows),

           ErrArgId = MCC_K_ARG_MCC_ERR;
           return (tp_am_put_exception(
                                MCC_K_CANNOT_COMPLETE,
                                &ErrArgId,
                                &status,
                                MCC_K_DT_UNSIGNED32,
                                MCC_S_COMMON_EXCEPTION,
                                p_dsc_out_p));
        }

where status is equal to MCC_S_BADVERB


However, the FCL PM returns the following to the screen:

MCC> register server .server.z synonym=z, node=byblos, association=TP$SSC
server TPEDNS_NS:.server.z
AT 30-AUG-1990 11:38:25


The requested operation cannot be completed
                      MCC Service Error = The requested operation cannot be
                                          completed  
                                           ^
                                           |
>>>>>My question is : should not     this  |  be the MCC_S_BADVERB message ?

                  

Below is the ILV dump of out_p:

ILV DUMP of OUTP:

[  19 ] (
    [  4 ] (
        [  1 ]         03 26 80 59
        [  2 ]         1d
        [  3 ] (
            [  0 ] (
                [  1 ]                 01
                [  2 ]                 33  -- 3
                [  3 ]                 01
                [  4 ]                 05
                [  5 ]                 aa 00 04 00 09 27 00 d3 9f 59 21 ba 93 00
 0d 00 01 06 73 65
                72 76 65 72 01 01 7a 00 00
                )
            )
        [  4 ] (
            [  2 ] (
                [  2 ]                 03 26 d0 2a
                )
            )
        )
    )
DUMP OF ENTITY IN:

depth=1 class code= 51 instance = �

DUMP OF ENTITY OUT:

depth=1 class code= 51 instance = �

CALL FMM STATE = 0


>>>>>>IT IS NOT VERY CLEAR TO ME WHERE AND WHAT INFORMATION GOT INSERTED IN 
      out_p. And is it correct ?

Finally, when will detailed information (such what the Registration FM expects 
in sucessess and failure cases) appear in the MM_programming manual ?

Thanks,
Phil
T.RTitleUserPersonal
Name
DateLines
294.1current functionalityTOOK::HAOFri Aug 31 1990 11:3414
    Phil,
    
    What you're seeing is the expected v1.0 functionality.  When you return
    an exception to Registration FM, it wraps up your exception as part
    of a common exception with datatype of MCCMessage.
    
    For V1.0, the output for a MCCMessage, is just the reply texts of all
    nested MCCMessages.  
    
    This will be extended such that arguments in the MCCMessage out_p  will 
    also be displayed.
    
    Christine
    
294.2Thanks.CLUSTA::TAMERTue Sep 04 1990 14:347
re: .1    
    Thanks, Christine.