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

Common Return Codes
Return Codes from Any Partner Program
Appendix A 335
End of Section CM_OPERATION_NOT_ACCEPTED The call cannot be issued because of one
of the following conditions:
• There is a nonblocking call outstanding on this
conversation. The program can continue with any
processing not related to this conversation
(including issuing CPI-C calls on other
conversations), but cannot issue most CPI-C calls
on this conversation.
For Unix At a later time, the application can issue
Check_For_Completion to determine whether an
outstanding nonblocking call has completed,
Wait_For_Conversation to wait for it to complete,
or Cancel_Conversation to cancel the outstanding
call and end the conversation.
• The program is running in a DCE multi-threaded
environment, and there is a call outstanding on
this conversation from another thread of the
program. Only one callfor each conversation canbe
outstanding at any one time.
For Windows If the application has used
Specify_Windows_Handle to 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 outstanding call
and end the conversation.
End of Section CM_PARAMETER_ERROR A parameter referred to by CPI-C is not valid. The
parameter that is not valid is one that can be supplied
either by the program or by another component outside
the program's control (such as the configuration file).
For example, the mode_name parameter may have been
specified by the program using Set_Mode_Name, or
may have been taken from the side information entry
specified by the sym_dest_name parameter.