HP-UX SNAplus2 CPI-C Programmer's Guide (June 2003)

Common Return Codes
Return Codes from Any Partner Program
Appendix A334
• The local program issued the Cancel_Conversation
call, which cancels all outstanding asynchronous
CPI-C calls on the conversation.
CM_DEALLOCATED_NORMAL This return code does not indicate an error.
The partner program issued the Deallocate call with
the deallocate type set to one of the following:
• CM_DEALLOCATE_FLUSH
• CM_DEALLOCATE_SYNC_LEVEL with the
synchronization level of the conversation specified
as CM_NONE
CM_OK The call executed successfully.
CM_OPERATION_INCOMPLETE The call was issued successfully, and is
operating in nonblocking mode; that is, control has
been returned to the program even though processing
for the call has not yet completed.
The program can continue with any processing not
related to this conversation (including issuing CPI-C
calls on other conversations). On this conversation, it
can issue a limited range of CPI-C calls (such as the
Extract_* calls). This is different from the IBM CPI-C
2.0 specification in which the program cannot issue any
calls on this conversation except
Wait_For_Conversation or Cancel_Conversation.
For Unix At a later time, the application can issue
Check_For_Completion to determine whether the
outstanding nonblocking call has completed,
Wait_For_Conversation to wait for it to complete, or
Cancel_Conversation to cancel the outstandingcall and
end the conversation.
For Windows If the application has usedSpecify_Windows_Handleto
receive notification of asynchronous call completion, it
should not issue further calls on this conversation until
it has received this notification. Otherwise, the
application can issue Wait_For_Conversation to wait
for the nonblocking call to complete, or
Cancel_Conversation to cancel the outstandingcall and
end the conversation.