Conference azur::mcc

> 1. I do not properly understand what is the purpose of an Alarm Notification
>    procedure; more precisely, refering to the Alarm FM Use, p4-6, I do not
>    precisely understand what is meant by "whenever an error condition occur
>    during the processing of an alarm": what is the processing of the alarm ?
>    Is it a) the evaluation of a rule (in this case what could go wrong) 
>         b) the batch processing of the notification script command procedure
    
    When evaluating a rule many things can go wrong:
    o	The entity could be de-registered.
    o	The entity does not respond so you cannot determine if the
    	conditions for firing the rule have been met.
    o	The entity returns an error message when you request parameters
    	needed to evaluate the rule.
    
    When one of the above continions exist it is impossible to tell if
    the conditions for firing the rule have been met, thus an exception
    procedure is executed rather than the normal alarm notification
    procedure.  
    
    I agree that the documentation should explain what the 'processing'
    of an alarm means.
    
    - Mike
                

    Mike,
    
    Thank you for your reply.
    
    About the second question I had, I think that I have been "victim" of
    my hardware/software environment:
    
    I work on a VAXstation 2000 - color monitor. 
    My station is used as an EWS (V1.1) terminal, connected to a host system 
    (TPLAB), a VAX 6430, running VAX VMS 5.5, DECwindow/Motif. 
    
    As a consequence, I already experienced some color issues.
    
    In the experiment I made in .0, the alarm severity was such that
    the fired entity (circuit BNA-0) should have been hilighted
    in yellow.
    
    In the meantime I redo the experiment, changing the alarm severity
    (corresponding now to red). This time, the iconic map displayed the
    fired entity.
    
    I redo again the experiment, resetting the initial alarm severity
    (corresponding to yellow). This time, the iconic map did not display the
    fired entity. However, I received a message window with the error
    "ILVTNF - specified tag not found within current constructor.".
    Having a lot of windows opened, I should have missed that message
    the first time I made the experiment.
    
    But... the next question is:
    shouldn't this message ("ILVTNF - specified tag not found within
    current constructor.") have been written in a file 
    MCC_COMMON:MCC_ALARMS_<today-date>_ERROR.LOG ?
    No such file is existing.
    
    Maurice.

>    "ILVTNF - specified tag not found within current constructor.".

This error is reported due to a parameter passing problem.
It may be coming from somewhere other than the alarms module, and
so is not written to the log file.

While on the surface this indicates a coding problem, it often
actually indicates a resource limitation.  Have you checked your
sysgen parameters and available pagefile space?

  > While on the surface this indicates a coding problem, it often
  > actually indicates a resource limitation.  Have you checked your
  > sysgen parameters and available pagefile space?

    Eric,
    
    Could you please indicate me which sysgen parameter I should check
    (and what should be their value) and what should be the available
    pagefile space.
    
    Thank you,
    
    Maurice.
    

The installation guide has a list of sysgen parameters, and pagefile
recommendations.  You could also contact Rob (TOOK::R_SPENCE) Spence
and ask about his audit command file.

-- Erik

    Erik,
    
    Having changed my Page file quota (from 30,000 to 50,000), 
    the message "ILVTNF - specified tag not found within current
    constructor" does not appear anymore.
    
    Thank you.
    
    Maurice.
    
    PS: many thanks to Rob for his audit tool which works fine.