[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

1790.0. "IMPM & MCC Entity Events" by NWACES::TRULL () Mon Nov 11 1991 11:18


   Is it possible to Notify an MCC Entity of an event via the Iconic Map?

   We have developed an AM whose management interface support events.
   The following is one event defined in the Notification Partition:

       EVENT PARTITION NOTIFICATION EVENTS = 16 :

         EVENT The UNKNOWN Switch Does Not Exist = 12 :
            DISPLAY = TRUE,
            SYMBOL  = EVT_NO_UNKNOWN_SP,
            TEXT    = "Reserved for future use",
            ARGUMENT Actual Error Text = 1 : Latin1String
               DISPLAY = TRUE,
               SYMBOL  = ARG_ERROR_TEXT
            END ARGUMENT Actual Error Text;
         END EVENT The UNKNOWN Switch Does Not Exist;

       END EVENT PARTITION NOTIFICATION EVENTS;

   An alarm is defined for this event as follows:

      ! Create alarm for SP_AM Notification Events
      CREATE MCC 0 ALARMS RULE SP_AM_NOTIFICATION_EVENT -
      EXPR=(OCCURS(MCC 0 SP_AM ANY NOTIFICATION EVENT)), -
      PERCEIVED SEVERITY = CRITICAL, -
      IN DOMAIN .MCCAW_DOMAIN

   On the iconic map, we have registered an MCC Entity and called it .SP_AM.
   (This is the entity which we want to recognize the MCC Alarms.)

   To test, we have MCC running using the Iconic Map and the MCC_PML_PM
   logical defined to be 3.  We also have Notification Enabled and the
   SP_AM_NOTIFICATION_EVENT alarm enabled.  In another window, we have
   FCL running with Notification Enabled and the SP_AM_NOTIFICATION_EVENT
   alarm enabled.

   When we force the event to occur, the FCL Window displays the following
   Notification:

!!!!!!!!!!!!!! Alarm, 11-NOV-1991 10:49:33 !!!!!!!!!!!!!!
Domain: TYSDAD_NS:.MCCAW_DOMAIN                       Severity: Critical
Entity: MCC 0 SP_AM
Rule Name: SP_AM_NOTIFICATION_EVENT
Rule Expression: (OCCURS(MCC 0 SP_AM ANY NOTIFICATION EVENT))
Rule SP_AM_NOTIFICATION_EVENT has fired
Data: MCC 0 SP_AM  The UNKNOWN Switch Does Not Exist has occurred 11-NOV-1991 10
:49:30.48 11-NOV-1991 10:49:30.48

   The IMPM trace window displays the following:

After mcc_call_function, ILV dump of P_OUT
[  1 ] (
    [  1 ] (
        [  25 ] (
            [  30 ]             01 18 53 50 5f 41 4d 5f 4e 4f 54 49 46 49 43 41
54 49 4f 4e
            5f 45 56 45 4e 54
            [  27 ] (
                [  1 ] (
                    [  1 ] (
                        [  0 ] (
                            [  1 ]                             01
                            [  2 ]                             07
                            [  3 ]                             0d
                            [  4 ]                             18
                            [  5 ]                             30  -- 0
                            )
                        [  1 ] (
                            [  1 ]                             01
                            [  2 ]                             5b  -- [
                            [  3 ]                             00
                            [  4 ]                             00
                            [  5 ]
                            )
                        )
                    [  2 ]                     54 68 65 20 55 4e 4b 4e 4f 57 4e
20 53 77 69 74 63 68 20 44
                    6f 65 73 20 4e 6f 74 20 45 78 69 73 74 20 68 61 73 20 6f 63
                    63 75 72 72 65 64 20 31 31 2d 4e 4f 56 2d 31 39 39 31 20 30
                    39 3a 33 31 3a 31 35 2e 37 34  -- The UNKNOWN Switch Does No
t Exist has occurred 11-NOV-1991 09:31:15.74
                    [  3 ]                     c0 25 5a 8c 26 a0 ca 01 ff ff ff
ff ff ff d4 1e
                    )
                )
            [  21 ]             28 4f 43 43 55 52 53 28 4d 43 43 20 30 20 53 50
5f 41 4d 20
            41 4e 59 20 4e 4f 54 49 46 49 43 41 54 49 4f 4e 20 45 56 45
            4e 54 29 29 00
            [  29 ]             01
            [  100 ] (
                [  0 ] (
                    [  1 ]                     01
                    [  2 ]                     07
                    [  3 ]                     0d
                    [  4 ]                     18
                    [  5 ]                     30  -- 0
                    )
                [  1 ] (
                    [  1 ]                     01
                    [  2 ]                     5b  -- [
                    [  3 ]                     00
                    [  4 ]                     00
                    [  5 ]
                    )
                )
            )
        )
    )
ILV dump of P_IN_ENTITY
depth=1 class code= 8 instance = �

ILV dump of P_OUT_ENTITY
depth=1 class code= 8 instance = �

   ...but the MCC .SP_AM icon does not light.

   Could the problem be in the AES which we pass along in the event_put?
   Is the AES used in the alarm creation correct?

   Thanx in advance,
   Bruce
    
T.RTitleUserPersonal
Name
DateLines
1790.1mcc entity is probably your problemTOOK::CALLANDERMCC = My Constant CompanionTue Jan 07 1992 11:3215
    my guess is that the problem has to do with the entity mcc .sp...
    
    Right now there are a number of problems with the name associated with
    the MCC entity. In the 1.1 kit I doubt that you will get the MCC entity
    to ever turn a color. In the 1.2 kit, you can make use of the
    targetting commands (Assign Target Domain <name> args...), but even
    1.2 notification still is having problems with the mcc entity. The
    problem derives from the fact that we try to translate all entities
    into what is known as their primary identifiers, for MCC this doesn't
    work as expected (because distribution isn't in place yet).
    
    More info later.
    
    jill