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

Conversation State Changes
Appendix B342
In some cases, the state change depends on the return code from the call;
in most cases, there is no state change for non-OK return codes. Where
no return codes are shown, a return code of CM_OK causes the state
change shown, and any non-OK return code causes no state change
(except as described in the note that follows). Where there are different
state changes according to the return code, the applicable values are
listed in the Return codes column.
The possible conversation states are shown as column headings. Against
each call, the following information is given under each heading to
indicate the results of issuing the call in this state:
X The call cannot be issued in this state.
T, I, II, S, SP, R, C, CS, CD, or PP Indicates the state of the conversation
after the call has completed: Reset (R), Initialize (I),
Initialize-Incoming (II), Send (S), Send-Pending (SP),
Receive (R), Confirm (C), Confirm-Send (CS),
Confirm-Deallocate (CD), or Pending-Post (PP).
(blank) The return code shown cannot occur in this state.
See function See the description of this function in Chapter 3, CPI-C
Calls, The changes in the conversation state depend on
the returned parameters from the call.
NOTE The conversation will always enter Reset state if any of the following
return codes are received:
• CM_ALLOCATION_FAILURE_NO_RETRY,
CM_ALLOCATION_FAILURE_RETRY
• CM_CONVERSATION_TYPE_MISMATCH
• CM_DEALLOCATED_NORMAL, CM_DEALLOCATED_ABEND
• CM_PIP_NOT_SPECIFIED_CORRECTLY
• CM_RESOURCE_FAILURE_RETRY, CM_RESOURCE_FAILURE_NO_RETRY
• CM_SECURITY_NOT_VALID, CM_SYNC_LVL_NOT_SUPPORTED_PGM,
CM_SYNC_LVL_NOT_SUPPORTED_LU
• CM_TPN_NOT_RECOGNIZED, CM_TP_NOT_AVAILABLE_RETRY,
CM_TP_NOT_AVAILABLE_NO_RETRY