[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

5980.0. "How to do name manipulation in ASSIGN TARGETS ?" by KETJE::PACCO (Horum omnium fortissimi sunt Belgae) Thu May 05 1994 14:17

    Is there any solution today ?
    
    I would greately appreciate a powerful way of retargetting events
    to a target entity which is different from the managed object.
    
    What I want to do is to retarget an event from
    
    NODE ns:.x.y.nodename HDLC LINK linkname
    to
    CIRCUIT ns:.z.nodename-linkname
    
    If I say:
    Managed object 	NODE * HDLC LINK *
    I get the (full) entity NODE name in #1
    	    and the child entity LINK in #2
    and I can only have a target entity in which I use #1 and/or #2.
    
    The main problem is the FULLNAME of NODE of which in fact I require only the
    relevant SIMPLE NAME.  Is there any way to solve this?
    
    The second problem is that I should sometimes retarget to
    CIRCUIT ns:.z.nodename-linkname, sometimes to CIRCUIT ns:.z.linkname-nodename
    depending on 'nodename' and 'linkname'. Is this (already complex)
    manipulation of names possible too ?
    
    Kind regards
    	Dominique.
T.RTitleUserPersonal
Name
DateLines
5980.1nothing elegant availableMSBCS::CALLANDERWed Jun 01 1994 12:5224
    the existing targetting functions can not handle the complexity
    you are asking for.  Currently the only work around I can see for
    you is to have an OCCURS alarm rule that monitors for the events. The
    rule fired procedure could do the name manipulation for you and
    then using the data collector could send in a new event for you
    with the correct entity specification you are interested in.
    
    Sorry this isn't more elagant but off the top of my head it is all
    I came up with.
    
    If you hadn't registered the nodes and circuits in different locations
    in the dns hierarchy you might have been able to do something like
    
    	node ns:.nodename HDLC LINK linkname
    	NODE #1 HDLC LINK #2
    
    	translating to a target entity of
    
    	circuit ns.nodename-linkname
    	CIRCUIT #1-#2
    
    I haven't explicitly tested this but I believe that it should work.