[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

941.0. "Where are reference attributes stored ?" by CCIIS1::ROGGEBAND (_ �hili��e _) Mon Apr 22 1991 12:39

    Hello,
    
    I am in the process of adding reference attributes to existing entities
    (customer requirement....). The SRM states that the registration FM
    stores reference attribute partitions for all entities in DNS, but when
    I walk through DNS using DNS$CONTROL, I am unable to find hem. Yet,
    they must be in there somewhere, because if I modify them from any
    point of the network, I still have a consistent value... So, where are
    the reference attributes stored ???? 
    
    I also wondered : if I augment an entity definition, do I have to
    de-register all known entities and re-register them, or can the
    registration FM cope with entities of the same class having different
    reference attibutes ?
    
    Thanks for your help,
    
    �hR.

T.R	Title	User	Personal Name	Date	Lines
941.1		NSSG::R_SPENCE	Nets don't fail me now...	`Mon Apr 22 1991 15:45`	5
	They are attributes of the object but the names are binary values that the distributed version of DNS$CONTROL can't display. I think someone has a version that shows them. s/rob
941.2		CCIIS1::ROGGEBAND	_ �hili��e _	`Tue Apr 23 1991 12:36`	15
	� They are attributes of the object but the names are binary values that � the distributed version of DNS$CONTROL can't display. I think someone � has a version that shows them. Ok, I guessed that the attribute names wouldn't be there, I suppose the code is sufficient. What about the values ? Most reference attributes are plain Latin1string, so they should be visible ? Can anyone answer the second part of my question in the basenote, i.e. do I have to re-register entities if I augment the reference atribute partition ? Thanks for your help, �hR.
941.3	reference attributes	B8OVEN::MULLIGAN		`Tue Apr 23 1991 17:53`	38
	> I also wondered : if I augment an entity definition, do I have to > de-register all known entities and re-register them, or can the > registration FM cope with entities of the same class having different > reference attibutes ? You do not have to deregister the entities. The Registration FM uses the dictionary to determine which reference attributes are defined for each entity class, once you update the dictionary and parse table with the new reference attribute codes you can use SET and SHOW to manipulate them. The previously stored attributes will not be affected. This assumes you use different codes for the new attributes and are not giving the old codes new meaning. You are adding new reference attributes as oppose to modifying the old ones? When you do a SET class instance new_reference_attribute value this command is dispatched to the Registration FM, which writes the attribute value in DNS keyed by the reference attribute code. When you do a SHOW class instance ALL REFERENCE the command is dispatched to the Registration FM which goes to the dictionary and finds all the reference attributes defined for this class. It then queries DNS using each reference attribute code for any value stored, and returns them to the caller. >I am in the process of adding reference attributes to existing entities >(customer requirement....). The SRM states that the registration FM >stores reference attribute partitions for all entities in DNS, but when >I walk through DNS using DNS$CONTROL, I am unable to find hem. Yet, >they must be in there somewhere, because if I modify them from any >point of the network, I still have a consistent value... So, where are >the reference attributes stored ???? As stated in .1 the reference attributes are stored as attributes of the DNS object, however these attributes are not visible using the DNS$CONTOL utility. Pat