[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

5876.0. "SCRIPT AM - how to know what went wrong?" by STKHLM::BERGGREN (Nils Berggren EIS/Project dpmt, Sweden DTN 876-8287) Wed Feb 23 1994 04:30

    Hi,
    
    I have an alarm-rule which polls a script command entity and triggers
    on a change on one of the output arguments.
    
    Doing a SHOW ALL STATUS on the entity always works OK (at least I never
    got any errors), but the alarm-rule every now and then fires an 
    INDETERMINATE alarm telling me that the script produced an errror.
    
    Now, is there a way to get the information about what went wrong in the
    script.  
    
    Can I set any LOG-bits for the Script AM (this has been asked before,
    but no answer as far as I know)?
    
    Sometimes I find files named MCC_SCRIPT_AM_nnnnnnn.ERROR, .OUTPUT and
    .COMMAND but the .ERROR and .OUTPUT files usually are empty.  How does
    SCRIPT AM do regarding these files, when and why are they kept/deleted?
    Any way to make SCRIPT keep the files?
    
    
    	Thanks
    	Nils Berggren
T.RTitleUserPersonal
Name		DateLines