[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

1465.0. "PROB: with error-handling" by STKHLM::BERGGREN (Nils Berggren EIS/Project dpmt, Sweden DTN 876-8287) Mon Sep 09 1991 06:59

Hello,
    
I have defined a COMMON-EXCEPTION in my MSL for both the GETEVENT- and
SHOW-directives (CANNOT_COMMUNICATE). When returning MCC_S_COMMON_EXCEPTION
from the SHOW-directive-routine and the code for that exception ILV-encoded
in out_p, I get the reply-text as defined in MSL. 

However, when doing the same from the GETEVENT-routine I don't get any
error-message in FCL and in the IMPM when enabling an alarms-rule I first
get "Normal operation has begun" and after a short while when looking at 
the status for that rule I get
"Error Condition: %MCC-E-INV_HANDLE_STAT, software error: invalid handle state"

The errorcondition in my routine is raised as the last thing in the
INIT_HANDLE_FIRST-routine, before any call to MCC_EVENT_GET.

The handle-state is FIRST when my getevent-routine gets called (as it should
be the first time)  as well as when returning with the status=
MCC_S_COMMON_EXCEPTION. 

1) Why do I get "%MCC-E-INV_HANDLE_STAT" ?  
2) Why don't I get that status in FCL?
3) Why the difference between SHOW and GETEVENT? (up to the error, the two
   routines works exactly the same)
4) What should I do?

        Thanks 
    /Nils
T.RTitleUserPersonal
Name		DateLines
1465.1You should define SPECIALIZED exceptionsTOOK::ORENSTEINTue Sep 10 1991 18:0228
    >> I have defined a COMMON-EXCEPTION in my MSL for both the GETEVENT- and
    >> SHOW-directives (CANNOT_COMMUNICATE).
    
    Common exceptions are already defined for you and are stored in the 
    dictionary under CLASS COMMON DIRECTIVE COMMON.   The MS will allow
    you to define SPECIALIZED EXCEPTIONS.
    
    SRM section 4.3.2.2 states:
    
    "A failure in the service, defined in its Management Specification, is
    handled as an exception indicated by a CVR of MCC_S_SPECIALIZED_EXCEPTION.
    Errors common to many services are universally defined and are indicated 
    by a CVR or MCC_S_COMMON_EXCPTION."
    
    Did you give these exceptions that you defined, values that are
    different than those of the common exceptions -- if so there could be
    some confusion in decoding.  You should use the common exceptions
    supplied (and take them out of you MS) or you should define specialized 
    exceptions and return a CVR of MCC_S_SPECIALIZED_EXCEPTION.
    
    >> "Error Condition: %MCC-E-INV_HANDLE_STAT, software error: invalid handle state"
    
    Are the rules that give you this error using your GETEVENT routine?  If
    so,  let me know what happens after the exception codes are
    straightened out.
    
    aud...
1465.2SPECIALIZED exception - the solution!STKHLM::BERGGRENNils Berggren EIS/Project dpmt, Sweden DTN 876-8287Thu Sep 12 1991 05:527
    repl .1
    
    Thanks, I just found it myself.  I changed it to spec-exception and it
    works OK.
    
      Thanks,
    Nils