|  | 
Hello.
I faced same case, I defined environmental variables as follows to get 
MCC trace.
	setenv MCC_EVENT_LOG 0x1
	setenv MCC_EVENT_TRACE 0x180 
When I start mcc, mcc output messages as follows.
MCC> PID 21853, THRid 10003 Tracing error paths in Event Manager
PID 21853, THRid 10003 Tracing Event code path in GET
PID 21853, THRid 10003 Tracing Event code path in PUT
PID 21853, THRid 10003 Event_Get starting
PID 21853, THRid 10003 Event_Get Input Arguments ...
PID 21853, THRid 10003   in_entity =
        entity [0] wild = NOT_WILD class = 7 id = 0 type = 25
        instance = ....
        %X00000000
PID 21853, THRid 10003   Partition = 15
PID 21853, THRid 10003   Filter = MCC_K_NULL_PTR
PID 21853, THRid 10003   time_spec = MCC_K_NULL_PTR
PID 21853, THRid 10003         Handle context not set up yet
PID 21853, THRid 10003 Event_Get handle state = MCC_K_HANDLE_FIRST
PID 21853, THRid 10003 Event_Get requesting NEXT event
PID 21853, THRid 10003 Going to wait for the event now... RMB is : 803E30
Our develpoping environment not installed MCC Director, is this related ?
Or Event Manager's problem ?
Someone let me know.
Regards.
Motoshige.
 | 
|  |  Re .2 :
>When I start mcc, mcc output messages as follows.
>
>MCC> PID 21853, THRid 10003 Tracing error paths in Event Manager
>PID 21853, THRid 10003 Tracing Event code path in GET
>PID 21853, THRid 10003 Tracing Event code path in PUT
>PID 21853, THRid 10003 Event_Get starting
>PID 21853, THRid 10003 Event_Get Input Arguments ...
>PID 21853, THRid 10003   in_entity =
>        entity [0] wild = NOT_WILD class = 7 id = 0 type = 25
>        instance = ....
>        %X00000000
>PID 21853, THRid 10003   Partition = 15
>PID 21853, THRid 10003   Filter = MCC_K_NULL_PTR
>PID 21853, THRid 10003   time_spec = MCC_K_NULL_PTR
>PID 21853, THRid 10003         Handle context not set up yet
>PID 21853, THRid 10003 Event_Get handle state = MCC_K_HANDLE_FIRST
>PID 21853, THRid 10003 Event_Get requesting NEXT event
>PID 21853, THRid 10003 Going to wait for the event now... RMB is : 803E30
>
  Motoshige,
    What you see here is not a problem, but just a trace of the internal
    mcc_event_get started by the mcc kernel on the entity MCC 0.
    This event_get is waiting for 'mcc_kill' events.
    There is nothing wrong with that : you ask for traces, you get traces...
    Regards.
    Pierre.
 |