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

CPI-C Calls
Send_Data (cmsend)
Chapter 3220
CM_OPERATION_INCOMPLETE
CM_OPERATION_NOT_ACCEPTED
CM_PIP_NOT_SPECIFIED_CORRECTLY
CM_PRODUCT_SPECIFIC_ERROR
CM_PROGRAM_ERROR_PURGING
CM_RESOURCE_FAILURE_NO_RETRY
CM_RESOURCE_FAILURE_RETRY
CM_SECURITY_NOT_VALID
CM_SVC_ERROR_PURGING
CM_SYNC_LVL_NOT_SUPPORTED_PGM
CM_SYNC_LVL_NOT_SUPPORTED_LU
CM_TP_NOT_AVAILABLE_NO_RETRY
CM_TP_NOT_AVAILABLE_RETRY
CM_TPN_NOT_RECOGNIZED
State When Issued
The conversation must be in Send or Send-Pending state when the
program issues this call.
State Change
When the return_code parameter is set to CM_OK, the new conversation
state depends on the send_type parameter, as shown in Table 3-12,
“State Changes for the Send_Data Call.”
For a return_code value of CM_PROGRAM_ERROR_PURGING or
CM_SVC_ERROR_PURGING, the conversation changes to Receive state. For
other non-OK values, the conversation changes to Reset state.
Table 3-12 State Changes for the Send_Data Call
send_type New state
CM_BUFFER_DATA Send
CM_SEND_AND_FLUSH Send
CM_SEND_AND_CONFIRM Send
CM_SEND_AND_PREP_TO_RE
CEIVE
Receive
CM_SEND_AND_DEALLOCATE Reset