Conference azur::mcc

5360.0. "Phave V Event Dispatcher Problem" by EIGER::SCHNEIDERR () Tue Jul 20 1993 11:30

Hello,

The command

MCC> Show node ... event dispatcher outp stream ... all char

works fine. But if we do the same in the IMPM we get the errormessage
"target management module thread has abortet" (ULTRIC, MCC 1.3)
"software error, invalid handle parameter" (VMS, MCC 1.3)

All other partitions (counters, status, identifier) works fine in the IMPM. 
I think it has something to do with the record size of the datas we get back
from the Phase V system (We tested it with a DEMSA and a DECnis). Bacause in the
event disp outb stream characteristic you get a very long record back.

Does somebody know about this problem, is there a parameter to set? In the 
release notes of MCC V1.3 chaptr 3.8 is written that the command now is supported
but there are only FCL examples. Does this mean the IMPM doesn't support this
function?

thanks, regards Roland

    Known problem, and a fix will go out in the MUP.
    
    What is happening is that you probably have _lots_ of filters
    set up on that outbound stream and the data returned is larger
    than the default 1024 bytes the AM is given by the PM to return data.
    
    FCL gives the AM Dynamic memory so the AM itself can reallocate
    enough memory when this situation is detected and continue returning
    the data.
    
    The Iconic map however gives the AM Static memory.  Because of this
    the AM must hold onto the data and return to the caller that not
    enough memory was provided and wait for the caller to return with
    a larger buffer.
    
    The DNA5 AM had some bugs in this area which I found after V1.3 shipped
    but have since fixed.
    
    John