Conference azur::mcc

653.0. "Unknown Error during register" by TENERE::GUIVIER () Wed Jan 23 1991 15:16

    hi,
    
    I am developping an AM, and I support the REGISTER directive.
    When I want to register one of my entity, which is constitued 
    with 2 identifiers the primary is a fullname attribute, the
    alternate is a SIMPLENAME attribute.
    During the Register, the Config FM calls the Show all Id of my
    Am; as a result i receive this error messages :
    
    
    Member TENERE_NS:.s
    AT 23-JAN-1991 18:02:16
    
    The requested operation cannot be completed
                          MCC Routine Error = %DNS-E-INVALIDNAME, Invalid
                          name
    
    Is the simple name type rejected ??
    When the Show all id doesnot include this attribute the register is
    successfull ??
    Are some special processing to do using this type ? Or does the ILV
    list have special intermediate ids ?
    My identifier declaration is :
    
       IDENTIFIER ATTRIBUTES
    
             ATTRIBUTE Register_Name = 1 : FullName
                DNS_IDENT = PRIMARY_NAME,
                ACCESS = NONSETTABLE,
                DISPLAY = TRUE,
                SYMBOL = MBR_REGIST_NAME,
                CATEGORIES = ( CONFIGURATION )
             END ATTRIBUTE Name;
    
             ATTRIBUTE Name = 2 : SimpleName
                DNS_IDENT = ALTERNATE_NAME,
                ACCESS = NONSETTABLE,
                DISPLAY = TRUE,
                SYMBOL = MBR_NAME,
                CATEGORIES = ( CONFIGURATION )
             END ATTRIBUTE Name_bis;
    
       END ATTRIBUTES; (* IDENTIFIER *)
              
    Some ideas ???
    Thanks,
    Pascale.
     

Your two identifier attributes can't have 'similar' datatypes. See SRM V1.1,
page 127, under "IDENTIFIER".

It would be easier if MSL picked up this sort of error.

    
    Okay, Let's clarify something...
    
    I know this si some where else in the conference but it will take
    to long to find it.
    
    The parser uses the "NAME = (ident, ident...)" field to determine
    the order in which the identifiers are parsed for. In reality we
    can handle simple and fullnames as both being identifiers, BUT!!
    the PM is not the system. My guess is your NAME field in the SRM
    is stated as NAME= (simplename ident, fullname ident), because of
    this the command you typed must *NOT* have used a complete fullname
    and therefore been parsed as a simplename.
    
    Ex:
    
    register class name
    
    	-vs-
    
    register class nameserver:.dir.name
    
    In the first case name would have parsed as a simplename (given
    that the NAME field had this as the primary parsing identifier),
    and been passed to the registration FM as a simplename. The
    Registration FM *REQUIRES* that you register using a fullname.
    Therefore you have two choices...
    	1) dump the simplename identifier (simplename is a *subset*)
    	   of fullname
    	2) change the order in the NAME field (which means you will
           NEVER have a PM send you that identifier).
    
    And finally you can always do what the phase4 AM does; tell the
    user that they must explicitly state the fullname on the register
    command (phase4 names and addresses also parse legitimately as
    fullnames).
    
    jill