Conference azur::mcc

I'm confused.  Are you seeing the error from the common agent, or from DECmcc?
I thought the common agent only supported DECnet/OSI on VMS; why would you
be using the DNA4 AM?

-- Erik


            <<< Note 5661.0 by COOKIE::HOLSINGER "Carp� per diem" >>>
                    -< pb w/INVALID_USE_OF_WILDCARD reply >-

    MOM developer using MCC V1.3 is sees unexpected behavior when returning 
    Invalid Use of Wildcard exception to a Create directive. The exception 
    response and argument are described by DNA_CMIP_ACTION.MS as: 

        EXCEPTION Invalid Use Of Wildcard = 15394 :
                DNA_CMIP_INT = 15394,
                SYMBOL = INVALID_USE_OF_WILDCARD,
                TEXT = "Operation failed; Inappropriate use of wildcard",
                ARGUMENT Wild Reason = 1 : WildCardReason                      
                        DNA_CMIP_INT = 1,                                      
                        SYMBOL = WILD_REASON                                   
                END ARGUMENT Wild Reason;                                      
        END EXCEPTION Invalid Use Of Wildcard;

    The WildCardReason datatype is described by DNA_CMIP_TYPES.MS as: 

	TYPE
	    WildCardReason = 2049 (
	        Wild Card in Create = 0,
	        Invalid directive = 1,
	        Attribute group not universal = 2,
	        Filter used with wildcard = 3,
	        Wild Card Not At Lowest Level = 4);
    
    The exception OID returned by the server is: 

DBG> cal mom_dump_oid(4017536)
        1.3.12.2.1011.2.7.1.62.59.126.12.15394
Prefix: 1.3.12.2.1011.2   Correct EMA prefix
OID Type: (7) Action Exception
  Class Code Sequence: 1.62.59.126
  Action Code: 12
  Exception Code: 15394
value returned is 24

    The exception argument AVL returned by the server (in Common Agent 
    AVL format) is:

DBG> cal mom_dump_avl(4017360)
---------------------------------------
attribute id  =  1.3.12.2.1011.2.8.1.62.59.126.12.15394.1
Modifier = MAN_C_SUCCESS
Attribute type = ASN1_C_INTEGER
Attribute value:
        octet.data_type = ASN1_C_INTEGER
        octet.length    = 4
        octet.string    = 0
--------------------------------------
value returned is 39
 
    Note the octet value above is 0, which corresponds to the "Wild Card 
    in Create" enumeration, above. The MCC command and FCL-formatted response 
    were: 

PLOW> mcc
DECmcc (V1.3.0)

MCC> create node plow medialib fred_ml cartype foo* base=true, max comp=1

Node LOCAL_NS:.plow MediaLibrary LOCAL_NS:.fred_ml CarType foo%
AT 13-OCT-1993 11:03:28

Operation failed; Inappropriate use of wildcard
                            Wild Reason =
%MCC-E-NOENTITY,  no corresponding entity instance exists

%MCC-E-NOENTITY,  no corresponding entity instance exists

    The "foo%" returned is a by-product of the MOM's instance wildcard 
    handling and is uninteresting. The Common Agent's send_action_reply 
    function seems to have no problem accepting the reply from the MOM. 
    What is wrong with MCC's reply processing? 

    Comments or suggestions are appreciated. Dump with mcc_dna4_am_log 
    set is available upon request. 

    -Paul

re:              <<< Note 5661.1 by TOOK::MINTZ "Erik Mintz" >>>

>I'm confused.  Are you seeing the error from the common agent, or from DECmcc?
>I thought the common agent only supported DECnet/OSI on VMS; why would you
>be using the DNA4 AM?
>
>-- Erik

    Sorry, Erik. 
    The "mcc_dna4_am_log" was a typo. Sould have been "mcc_dna5_am_log". 
    There is no error reported by the Common Agent. So the problem is either 
    in CA's encoding of the reply argument into CMIP, or MCC's decode and/or 
    parse by the FCL, right? 

    Would the MCC session with "$ define mcc_dna5_am_log 2b" make this an 
    easy call for you? I have this, but I'm not very good at reading them. 

    Thanks, 
    -Paul

    Paul, set the MCC_DNA5_AM_LOG to 82d run it again and send
    me the trace dump.  If I get a chance today I'll try and look
    at it.  I'm at class all next week so try  to get it to me asap.
    
    I suspect the msl description is wrong but my pea-brain can't
    remember off hand what the correct syntax is without some searching.
    
    Dave, you out there?  How does his msl look?
    
    John
    

    
    I believe the problem is in the agent(MOM) side.  The wildcard reason is
    encoded in the the modifier field of the avl.  It is not encoded in the
    octet string portion of the avl.  Sorry to lead you astray!
    
    Russ

re:                   <<< Note 5661.4 by TOOK::RMURRAY >>>
    
    Russ, 
    I received a msg from John Purretta describing your (joint) opinion. 
    I still do not understand what our MOM is doing wrong. I would like to 
    continue this discussion in NOTED::COMMON-AGENT #262 if that's ok.

    -Paul