| >We wish to integrate a new action routine into PCM. We have a piece of C source
>code supplied by another site which compiles and links without errors. The code
>is designed to pick data out of a mailbox and fire it into ENS using
>CMUserSendEvent.
What your describing is *not* an action routine. Actions routines
typically receive events from ENS. Certainly an action routine could do
both by also calling CMUserSendEvent.
>However we have two problems :
>1. We have no detailed instructions on how to integrate this image into the PCM
>configuration.
If your program only calls CMUserSendEvent then it does not need to
be included into the config database.
>2. When trying to run up the image in an inreactive process it fails when
>executing the PCM callable interface routine CMUserInit.
No surprise their. CMUserInit expects to find a logical name pointing
to a mailbox. This logical name is defined by the ENS Daemon
but only if the ENS daemon started the program *as an action routine
process. The point is you don't use CMUserInit in applications like
yours. The latter assumes that you really only want to send events to
ENS via CMUserSendEvent. If that is your goal then remove the call to
CMuserInit as weel as the callback routines.
REgs,
Dan
Any help would be appreciated.
Thanks,
Alan Brodie
|