[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

6352.0. "How complex can be an ENTITY INSTANCE specifier ?" by KETJE::PACCO (Horum omnium fortissimi sunt Belgae) Fri Jul 28 1995 20:35

    Another nasty one.
    
    Defining a (child) entity, is it possible to have one with an instance
    name which use a constructed data type as identifier?
    
    example:
    would it be possible to have a child entity with a
    	data type = MCC_K_DT_RECORD.
        name = { part1 = "abc", part2 = "def" }
    
    I have not be able to manage such one yet,
    	neither to create a correct AES (MCC_E_INV_DESC).
    	neither to give something at the FCL_PM level.
    	(I tried SHOW ABC xxx DEF { part1 = "abc", part2 = "def" } all char
    	but it does not seem to work)
    
    Q1: Is it possible ?
    Q2: Which would be the syntax for e.g a SHOW command at FCL_PM level ?

T.R	Title	User	Personal Name	Date	Lines
6352.1		AZUR::DURIF		`Tue Aug 01 1995 11:15`	19
	There is no signature in this one but it is signed anyway. If you are going this way i think it may work with some AM or the AM you are designing. R1 : It may work but you may get some problems when using FM's. I cannot proof what i say but please take this point into account. R2 : the syntax you try is not too bad. What is the functionnal need leading to the use of record as identifiers ? Perhaps someone involved in Temip may tell what is done in Temip. Regards, Benoit
6352.2	Why make it complex ?	KETJE::PACCO	Horum omnium fortissimi sunt Belgae	`Tue Aug 01 1995 20:23`	28
	Benoit, Why take a RECORD data type as identifier ? My case: I want to define events I want to process. How can an event be defined: by its entity and event number (or name). I would like to create one 'management' entity per event I like to process. For instance such an entity could be 'Node * HDLC Logical Link * Logical Station * - Station Running' If you want to encode this uniquely, the RECORD type is the best suited. The First part would be of EntityClass data type, The second part of it would be EventTypeId (Or latin1String ?) That's it. For each instance one (I hm...) could create one entry in a MIR database to keep the instance list across MM reboot. On the contrary, if a Record instance is not possible (Who has already worked with such entities?) I have to create an hyerarchy. E.G level 1 -- EntityClass level 2 -- EventTypeId. But then you come into inconsistencies as 'an entityclass exist without an eventtypeid' What is the best ? Or should I put this in the TeMIP notes file? By the way, which is the name of the Temip Notes conference? Signed Dominique PACCO.
6352.3		AZUR::DURIF		`Mon Aug 07 1995 10:59`	18
	Bonjour Dominique, In the instance 'Node * HDLC Logical Link * Logical Station * - Station Running' (I think the "-" is an extra character) how do you do a getevent on that ? Is your need to add customized events to 'node * hdlc logical station ' entity? Is your need to perform getevent on 'node hdlc logical station *' ? Temip conference is TAEC::TEMIP. As i am not an architecture guru it may be usefull for you to get some consultancy from one. Regards, Benoit
6352.4	Constructor data type for Instance value ?	KETJE::PACCO	Horum omnium fortissimi sunt Belgae	`Mon Aug 07 1995 21:42`	26
	Hello Benoit, I want to create some 'instance', in fact a MANAGEMENT INTERFACE instance (not a SERVICE INTERFACE one). and associate some characteristics to it. That instance can best be described as 'The event Station Running of the Node child entity HDLC Logical Link * Logical Station ' Therefore my idea was to have Node HDLC Logical Link * Logical Station - Station Running being seen as the entity instance value of e.g DNA5_AM MAPPER (a new child entity of DNA5_AM). Because I cannot define both Node * HDLC Logical Link * Logical Station and Station Running under 1 'known DECmcc data type' I was thinking to use the 'constructor data type RECORD' for doing so. Part 1 would be : Node * HDLC Logical Link * Logical Station Part 2 would be : Station Running Part 1 could be mapped into MCC_T_EntityClass data type Part 2 could be mapped into MCC_T_Latin1string or MCC_T_EventId type. The question resumes to: Is this feasible, the best approach or is another approach better. Amities, Dominique.
6352.5	Record cannot be used as identifier	TAEC::FLAUW	Marc Flauw, TeMIP Technical Office, VBO	`Wed Aug 16 1995 16:45`	30
	Dominique, Most contructed datatypes are not working as identifiers. I think it is true of record. The main problem here is the MIR that does not support such complex datatypes. As to your original problem of DNA5 mapper AM, I assume you need access to individual events to store information related to the mapping to an OSI event/alarm. Does it need to be an identifier attribute ? It means that you define a new class of objects simply for describing the mapping information. There are a couple of alternatives worth discussing depending on the volume of information to be stored and the level of granularity required : - put everything under the self-management of your new AM. - use the node hierarchy and create a new partition for your own data at each level. This new partition will be managed by your new AM. (Creating child entities is likely not to work as it will conflict with the DNA5 AM, right ?) - use a simpler naming datatype, like a string and put the entity class and event name as characteristics of the object. We can discuss it off-line, if you wish. Best regards, Marc.