[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

5693.0. "Status of export entry changed?" by WARABI::CHIUANDREW () Thu Oct 28 1993 02:31

    HI,
    
    Customer has to use EXPORTER to produce link utilization reports on
    their WAN, but sometime MCC_EXPORTER batch just died without any
    warning. Then we think we can use ALARM to detect the execution of the
    EXPORTER, but here comes the questions:
    
    1) Using the following alarm rule, we can detect the status change of
    those export entries created in MCC:
    
    CREATE DOMAIN ABC RULE EXPORT_CHECK -
    EXPRESSSON=(OCCUR(MCC DECMCC EXPORTER_FM OPERATION STOPPED)) ,-
    ALARM FIRED PROCRDURE=MCC_ALARMS_LOG_ALARM.COM ,-
    ALARM FIRED PARAMETER=MCC_COMMON:MCC_ALARMS.LOG ,-
    BATCH=MCC$BATCH ,-
    SEVERITY=MAJOR ,-
    AUTO ENABLE = NO 
    
    When status of any export entries changed from ACTIVE to suppended,
    then I received a alarm notification.
    
    But, when I delete the MCC_EXPORTER_BACKGROUND batch, the status of
    those ACTIVE export entries DID NOT CHANGE (still remain ACTIVE), but
    gives the last export failure reason is "Background exporting
    process is not set up". 
    
    Will the status of those ACTIVE export entries be changed when the
    batch job died/stopped/remove/etc..?
    
    2) Other than method 1) outline above, is there any other way to detect
    the status of the MCC_EXPORTER_BACKGROUND_PROCESS?
    
    Thanks in advance for help!
    Andrew Chiu - NIS Sydney
T.RTitleUserPersonal
Name
DateLines