| 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 |
Hello,
I have an event sink using the callable MCC on VMS
(to be ported to Ultrix afterwards).
1- Can I use the mcc_thread routines of MCC ?
2- What is recommanded by you MCC NSM gurus !
a/- to use the mcc_thread routines rather than to attack
directly the CMA thread routines ? Why ?
b/- to use the CMA routines rather than to use
the MCC thread routines ? Why ?
c/- equivalent ? Why ?
3- Is the following strategy a possible one :
I use the callable MCC and communicate between the
event sink and the foreground AM with the event manager.
As far as thread manipulation is concerned,
each time I can use an MCC routine, I use - like
mcc_thread_create, mcc_thread_join_all...- I eventually
communicate between different threads using the event manager.
If I have to perform a more sophisticated function
which MCC does not provide like the CMA queues functionality
I attack directly the CMA library routines.
Thanks for any comment and help on this
Best Regards
CjH
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 2714.1 | Use DECthreads | TOOK::BURGESS | Fri Apr 10 1992 00:14 | 46 | |
> I have an event sink using the callable MCC on VMS
> (to be ported to Ultrix afterwards).
>
> 1- Can I use the mcc_thread routines of MCC ?
Yes
> 2- What is recommanded by you MCC NSM gurus !
>
> a/- to use the mcc_thread routines rather than to attack
> directly the CMA thread routines ? Why ?
> b/- to use the CMA routines rather than to use
> the MCC thread routines ? Why ?
> c/- equivalent ? Why ?
>
Use DECthreads. There are two APIs to choose from
with pluses and minus.
CMA - fixed API, but less portable to exotic (non-DEC) platforms.
POSIX 1003.whatever API portable open interface but still in draft form
and subject to change.
DCE uses the POSIX API.
MCC framework is currently layered on CMA api because that's
all that was available at the time. The MCC framework rtns
provide a transition for v1.0 and v1.1 source to DECthreads
implementation.
> 3- Is the following strategy a possible one :
>
> I use the callable MCC and communicate between the
> event sink and the foreground AM with the event manager.
> As far as thread manipulation is concerned,
> each time I can use an MCC routine, I use - like
> mcc_thread_create, mcc_thread_join_all...- I eventually
> communicate between different threads using the event manager.
> If I have to perform a more sophisticated function
> which MCC does not provide like the CMA queues functionality
> I attack directly the CMA library routines.
>
Don't rely on the CMA library rtns! libcmalib is not supported
for ULTRIX and OSF. It would be a good exercise to write your own
abstract monitors.
\Pete
| |||||