Table of Contents
Advertisement
For example, if an acmsdi_call_task completion message is sent from the back
end, this is a pointer to the context supplied on the acmsdi_call_task call.
This pointer to a structure in the client application's memory is treated as
a 32-bit integer. To determine the structure being referenced, the client
application compares this value with the values returned by the acmsdi_
return_pointer service. Because data can be moved by memory management,
acmsdi_return_pointer calls must be issued within the same procedure as the
original call.
Return Status
The status values returned by the acmsdi_poll service are listed in Table 4–13.
Table 4–13 acmsdi_poll Return Status Values
Status
ACMSDI_CANCEL_DONE
ACMSDI_DONE
ACMSDI_ENABLE_EXCH
ACMSDI_EXCHACTV
ACMSDI_EXEC
ACMSDI_INSUFPRM
ACMSDI_INVSUBID
ACMSDI_INTERNAL
ACMSDI_MIXEDMODE
ACMSDI_NOMEMORY
ACMSDI_READY
ACMSDI_RECV_EXCH
ACMSDI_REQUEST_EXCH
ACMSDI_SEND_EXCH
Description
Task cancel call complete.
Sign-in, sign-out, or task call complete.
Enable exchange step has arrived.
Request is invalid while exchange step
processing is active.
No message from the back-end
available; call still executing.
Insufficient or conflicting parameters.
Invalid or obsolete submitter
identification.
Internal TP Desktop Connector error.
Not a forced nonblocking session call.
Insufficient memory.
No message from the back-end
available; no call executing.
Receive exchange step has arrived.
TDMS Request exchange step has
arrived.
Send exchange step has arrived.
(continued on next page)
Forced Nonblocking Client Services 4–31
acmsdi_poll
Advertisement
Table of Contents
