[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

1568.0. "enable alarm problem" by HGSWS1::SUSANCHAN () Tue Oct 01 1991 08:44

I got an information msg and alarm was not enabled when created the alarm in 
two line.  Whereas, alarm was enabled successfully when created in one line.
Will someone be able to explain?

Thanks,
Susan


*****  FIRST TRY : type the command in two line   *****
*****                                             *****
MCC> create mcc 0 alarm rule test-1 <CR>
EXPRESSION = (occurs (node4 schwep circuit sva-0 circuit down)) <CR>

MCC 0 ALARMS RULE test 
AT  1-OCT-1991 18:25:10 
Entity created successfully.


MCC> enable mcc 0 alarm rule test-1 <CR>

MCC 0 ALARMS RULE test-1 
AT  1-OCT-1991 18:25:18 

Data base error while reading rule information.
                             MIR Status = %MCC-S-ILVIMPLDEFAULT, 
                                          implementation-specific default value 
                                          found.


MCC> show mcc 0 alarm rule test-1 all status

MCC 0 ALARMS RULE test-1 
AT  1-OCT-1991 18:26:36 Status

Examination of attributes shows:
                                  State = Disabled


*****  SECOND TRY : type the command in one line  *****
*****                                             *****
MCC> create mcc 0 alarm rule test-2 expression = (occurs (node4 schwep circuit 
sva-0 circuit down))

MCC 0 ALARMS RULE test-2 
AT  1-OCT-1991 18:26:06 

Entity created successfully.


MCC> enable mcc 0 alarm rule test-2 <CR>

MCC 0 ALARMS RULE test-2 
AT  1-OCT-1991 18:26:14 

Normal operation has begun.


MCC> show mcc 0 alarm rule test-2 all status <CR>

MCC 0 ALARMS RULE test-2 
AT  1-OCT-1991 18:26:31 Status

Examination of attributes shows:
                                  State = Enabled
                               Substate = Running
              Result of Last Evaluation = In progress
T.RTitleUserPersonal
Name
DateLines
1568.1Add continuation characterNSSG::R_SPENCENets don't fail me now...Tue Oct 01 1991 12:3512
    You need to provide the "continuation line character" "-" (just like
    in VMS) so it knows that you still have more to come.
    
    Just put a " -" at the end of each line except the last one like
    
    MCC> create mcc 0 alarm rule test-1 -<CR>
    _MCC> EXPRESSION = (occurs (node4 schwep circuit sva-0 circuit down)) <CR>
    
    
    Ok?
    
    s/rob
1568.2This has been QARed and partially fixedTOOK::ORENSTEINTue Oct 01 1991 12:5253
    
    Yes, I can explain it.  We are broken.
    
    There are two poblems here.
    
    1.  The FCL is not consistant about passing down default values
        (not sure about whether this is fixed)
    
    2.  ALARMS did not handle default values very well.
        (fixed for NEXT release)
    
    I have set the MCC_FCL_PM_LOG to 8 to demonstrate the inconsitancy
    of the default values:
    
    TWO LINES:
    
    MCC> create mcc 0 alarms rule hello
    EXPRESSION = (this is an expression)
    
    ILV dump of IN_P:
    
    [  0 ] (
        [  21 ]     28 74 68 69 73 20 69 73 20 61 6e 20 65 78 70 72 65 73
    73 69
        6f 6e 29  -- (this is an expression)
        [  29 ] (
            [  5 ]
            )
        )
    
    The FIVE is a flag that means USE DEFAULT -- Alarms did not handle
    this correctly and stored it as an attribute.  Later when it was used,
    we issued a message that means "You have bogus attribute data"  Our fault.
    
    ONE LINE:
    
    MCC> create mcc 0 alarms rule hello expression = (this is an expression)
    
    ILV dump of IN_P:
    
    [  0 ] (
        [  21 ]     28 74 68 69 73 20 69 73 20 61 6e 20 65 78 70 72 65 73
    73 69
        6f 6e 29  -- (this is an expression)
        [  29 ]     00
    )
    
    Here, the actual value for PERCEIVED SEVERITY was passed from the FCL to
    ALARMS.  
    
    Sorry for the inconvenience.
    
    aud...
1568.3dash and return are not the sameTOOK::ORENSTEINTue Oct 01 1991 13:0119
    
    I guess Rob and I entered our last notes at the same instant.
    
    The "dash" allows yout to continue a command on another line.
    
    What the author of .0 had done was enter a RETURN to complete his
    command.  The FCL parser then looked at the line and decided that
    some required arguments were missing and prompted the user for more
    information -- in this case it was the EXPRESSION that was missing.
    This is called "FCL command-completion".
    
    If the user had used the "dash", the FCL would have peiced together
    the separte lines and considered it ONE line and would not have seen
    the problem he had seen.
    
    aud...