| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 5582.1 | Need more info. | TAEC::LAVILLAT | | Thu Sep 09 1993 08:30 | 35 |
| Re .0:
>
> Ultrix 4.3, DECmcc1.3.
>
> I have a customer who has the following problem. I'm afraid I've no
> experience of this, thus I'm not sure if it will make sense. He's using the
> MCC call interface to perform a notify via the Notification FM. If the
> notify is cancelled, then the CVR invalid handle is returned. If however,
> the thread making MCC call is alerted and then cancels the notification,
> the cancel is successful. Turning notification FM logging on, it appears
> the notification is successfully cancelled in both cases.
>
Could you please explain what you mean by "If the notify is cancelled,"
The only way I know to cancel a notify is the second way you explain.
We (TeMIP) call the NOTIF FM via mcc_call and have no problem.
> The customer sees this as high priority, however, I noticed in 5314.1,
> by KAJUN::NELSON that the 'interface is essentially undocumented and
> very unsupported', so can we offer him any help please?
>
No ! KAJUN::NELSON was talking about the mcc_call_presentation
that allow PMs to communicate (PM to PM call) and not the standard
mcc_call (AM/FM to AM/FM) mechanism (mcc_call_access/mcc_call_function)
which is totally documented and supported.
> If any further details are required, then please say so and I'll ask
> the customer.
>
Yes, please ask them to explicit the first case.
> Cheers,
>
> Tim Moran UK/CSC
>
|
| 5582.2 | | BLKPUD::MORANT | Wanted: AK47 assault rife and 200 rounds! | Thu Sep 09 1993 10:25 | 20 |
|
Thankyou, I passed your question on to the customer. He replied thus:
(word for word).
"Basically we're using the Notification FM to collect events from a
specific domain. If the AM responsible for one of the members in that
domain is re-enrolled, the specialised exception unable_int is
returned. In this case we need to cancel and restart the notify. This
is the case that's causing us problems. If however the thread making
mcc_call is alerted and we then cancel the notify in the normal way,
there are no problems. In both cases the same function is used to
cancel the notify. This function successfully updates the handle via
mcc_ahs_cancel() before performing the mcc call which cancels the
notify".
Well, that's it. I hope that makes things a bit clearer. Any help is
greatly appreciated.
Tim
|
| 5582.3 | You are right | TAEC::LAVILLAT | | Thu Sep 09 1993 11:55 | 35 |
| Re .2:
>
> Thankyou, I passed your question on to the customer. He replied thus:
> (word for word).
>
> "Basically we're using the Notification FM to collect events from a
> specific domain. If the AM responsible for one of the members in that
> domain is re-enrolled, the specialised exception unable_int is
> returned. In this case we need to cancel and restart the notify. This
> is the case that's causing us problems. If however the thread making
> mcc_call is alerted and we then cancel the notify in the normal way,
> there are no problems. In both cases the same function is used to
> cancel the notify. This function successfully updates the handle via
> mcc_ahs_cancel() before performing the mcc call which cancels the
> notify".
>
> Well, that's it. I hope that makes things a bit clearer. Any help is
> greatly appreciated.
>
It is perfectly clear now.
Meanwhile, I have remembered a problem we had with the NOTIF FM,
which is ... yours !
We have observed exactly the same behavior. What we did is simply
ignore the error returned in this case, and we have no problem.
We ran regression tests cancelling hundreds of time calls to the
NOTIF FM, and had no error or invalid behavior.
Hope this helps.
Pierre.
|
| 5582.4 | | BLKPUD::MORANT | Wanted: AK47 assault rife and 200 rounds! | Thu Sep 09 1993 14:48 | 9 |
|
Pierre,
Thanks for that. The customer is prepared to live with it, although he
wouldn't mind seeing it fixed in the future.
Cheers,
Tim
|
| 5582.5 | more info on how to cancel | TOOK::CALLANDER | | Fri Sep 17 1993 15:07 | 24 |
| maybe I am really confused, but please note you do NOT cancel the
handle, the caller cancels the handle only.
Like this; if my module calls you and you decide that you want to
cancel, you return a CVR of canceled. Do NOT return a handle of cancel!
A handle of cancel is only passed from my module to yours. The caller
decides when it is time to clean up not the callee.
notif fm makes call
am decides to cancel
returns cvr cancel
notif fm cancels handle
calls am again with cancelled handle.
It shoulds like the AM is trying to decide to cancel the handle. If
their PM (the guy who started the mcc_call_function (NOTIFY)) is doing
it then this is really a bug (but mind you that is how all the PMs are
doing it any none of them are having problems) and a bug report should
be submitted; if their AM is canceling the handle then that is their
error.
|