Conference azur::mcc

1805.0. "RECORD DEFAULT values & IMPM : How, when ?" by TENERE::HAYES (A European Telecomet ...) Wed Nov 13 1991 04:38

	
		Hello,


	We want to use the DEFAULT clause in the MSL.

	The DEFAULT value is stored as a Latin1String in the dictionary.
	I wanted to know if putting defaults for constructed
	datatypes is possible like for a RECORD :                
    
        DEFAULT = "(CPU-type = M68000, Switch-type = Packet)", 

	We checked notes 1112, 1185, 1461, 1570, 1729 
	and our AM now decodes the default from the dictionary
	using mcc_dict_get_def_info.

	The problem is in the Iconic Map PM :
	
    	We would just want to see the default value
    	for this record appear for the attribute
    	by default, so :
	
	- Why are simple datatypes default correctly
	  displayed during CREATE/SET operations but
	  CONSTRUCTED datatypes like RECORD not correctly
	  supported (we get blank fields) ?
         
    
	- Can I get a list of IMPM supported datatypes for defaults ?

	- Will there be improvements in that area in V1.2 ?


        You will see attached an extract of my MSL.
	
        
	 	
		Best Regards


			Catherine






MANAGEMENT SPECIFICATION MCC_APBX_AM_SRVC_IF;
   VERSION = V1.1.0;
   SYMBOL-PREFIX = MCC_;


   TYPE NodeType = 3026 RECORD          
          CPU-type       = 0 : Latin1String;
          Switch-type    = 1 : Latin1String;
        END RECORD;     

   GLOBAL ENTITY APBX = 999 :
      IDENTIFIER = ( Name ),
      SYMBOL = CLASS_APBX,

   IDENTIFIER ATTRIBUTES
         ATTRIBUTE Name = 1 : FullName
            DNS_IDENT = PRIMARY_NAME,  
            ACCESS = NONSETTABLE,
            DISPLAY = TRUE,
            SYMBOL = ATTR_Name
         END ATTRIBUTE Name;
   END ATTRIBUTES; (* IDENTIFIER *)

   CHARACTERISTIC ATTRIBUTES
         ATTRIBUTE Type =  4: NodeType
            ACCESS = NONSETTABLE,
            DISPLAY = TRUE,
            DEFAULT = "(CPU-type = M68000, Switch-type = Packet)", 
            SYMBOL = ATTR_Node_type
         END ATTRIBUTE Type;
   END ATTRIBUTES; (* CHARACTERISTIC *)

END ENTITY APBX;

END SPECIFICATION MCC_APBX_AM_SRVC_IF;

    Could you please supply more info of how you are using DEFAULT.
    There has been a common mis-conception around its usage. It was
    primarily defined for output use only. If a response to a
    a request supplied the value "default" for an attribute, the
    value in the dictionary would be presented as the value
    for the attribute. Thus for records the user can always put
    the default value in as a Latin1String in the desired manner
    of display. The other simple datatypes were trivial to support
    but there was never any intention of storing defaults in the
    dictionary for any other use, thus anything beyond latin1string
    and integer was seriously considered for extensions.
    
    The common mis-conception has been that Sets would use the DEFAULT
    value in the dictionary. This is not the architected use of the
    DEFAULT property of an attribute/argument. It would help if the
    discussion in the SRM were clearer about this point.
    
    wally
    

Catherine,

For V1.2, the Iconic Map does not handle defaults for any constructor datatypes.

Sorry,
Verna